"real" installation of Porteus to harddisk revisited

Non release banter
Post Reply
User avatar
francois
Contributor
Contributor
Posts: 5080
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

"real" installation of Porteus to harddisk revisited

Post#1 by francois » 26 Mar 2015, 22:20

Trying to use the howto on "real" installation of Porteus to harddisk:
https://forum.porteus.org/viewtopic.php?f=39&t=1576

It seems that I am missing something in my way to implement it:
https://forum.porteus.org/viewtopic.php ... 516#p32516

Following fantom suggestion to change my menu.lst entry I got some improvement (thus I should have followed exton procedure in the first place):
1.0 32 bit:

Code: Select all

title porteus v31 on SDA5 /32bit_v31 SLACKWARE FULL
root (hd0,4)
kernel /boot/vmlinuz root=/dev/sda5
2.0 64bit:

Code: Select all

title porteus v31 on SDB3 /64bit_v31 SLACKWARE FULL
root (hd1,2)
kernel /boot/vmlinuz root=/dev/sdb3
I got a real improvement as much on 32 bit and 64 bit. I have two real installs, one 32bit and the other 64 bit. Surprisingly, they do not give the same error message.

1.0 32 bit full porteus installation with kde. The 32 bit does not get to boot into kde environment there seems a problem there. I do not rembember the error message, but some archlinux user proposed to copy /etc/X11/xinit/xinitrc to ~/.xinitrc. It did no do any good.

2.0 64 bit full porteus installation with kde. Error message:
Couldn't open temporary file
/usr/share/config/kdm/sedGDalty read-only file ...
/usr/share/config/kdm/sedAKLIry
...
...
/usr/share/config/kdm/sedW14neC

ld "x1" respawning too fast.

Ctrl-alt-del
Switching run level:6
Alt-syst-reisub

My questions are wherami?

I have the impression that I cannot get into the DE kde because I am not even well installed into the xorg environment.
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 5080
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: "real" installation of Porteus to harddisk revisited

Post#2 by francois » 26 Mar 2015, 23:33

Examining the files in the

For Xorg.0.log:
There are many warnings (WW) but no errors (EE). My gut feeling is that this seem to be alright.

message.1.gz:
Does not seem to include any pertinent information.

kdm.log:

Code: Select all

Initializing built-in extension DRI2
Loading extension GLX
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
(EE) Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
debug:
does not seem to be of some use.

message:
there seems to be nothing in there.

porteus-live-debug:
there seems to be nothing in there.

syslog:
maybe some interesting information, but I cannot juge

Code: Select all

Mar 26 17:41:01 porteus NetworkManager[3304]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.11': no such name
Mar 26 17:41:01 porteus NetworkManager[3304]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.11': no such name
Mar 26 17:41:02 porteus udevd[2056]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/80-brother-libsane-type1.rules:17 
Mar 26 17:41:02 porteus udevd[2056]: invalid rule '/etc/udev/rules.d/80-brother-libsane-type1.rules:17' 
Mar 26 17:41:03 porteus NetworkManager[3304]: <warn> (pid 3576) unhandled DHCP event for interface wlan0
Mar 26 17:41:03 porteus NetworkManager[3304]: <warn> Connection disconnected (reason -3)
Mar 26 17:41:03 porteus NetworkManager[3304]: <warn> Connection disconnected (reason -3)
Mar 26 17:41:04 porteus avahi-daemon[3221]: Disconnected from D-Bus, exiting.
Mar 26 17:41:04 porteus avahi-dnsconfd[3269]: read(): EOF
Mar 26 17:41:04 porteus NetworkManager[3304]: <warn> disconnected by the system bus.
Mar 26 17:41:04 porteus ModemManager[3398]: <warn>  Could not acquire the 'org.freedesktop.ModemManager1' service name 
Mar 26 17:41:04 porteus nm-dispatcher.action: Disconnected from the system bus, exiting.
Mar 26 17:54:04 porteus udevd[2139]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/80-brother-libsane-type1.rules:17 
Mar 26 17:54:04 porteus udevd[2139]: invalid rule '/etc/udev/rules.d/80-brother-libsane-type1.rules:17' 
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: RSDP 0x00000000000F0030 000014 (v00 TOSHIB)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: RSDT 0x00000000CA3AE038 000050 (v01 TOSHIB A0082    00000002      01000013)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: FACP 0x00000000CA3AD000 000081 (v02 TOSHIB A0082    00000002 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: DSDT 0x00000000CA39B000 0094BF (v02 TOSHIB A0082    20120516 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: FACS 0x00000000CA37D000 000040
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: HPET 0x00000000CA3AC000 000038 (v01 TOSHIB A0082    00000001 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: APIC 0x00000000CA3AB000 0000BC (v01 TOSHIB A0082    00000001 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: MCFG 0x00000000CA3AA000 00003C (v01 TOSHIB A0082    00000001 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: ASF! 0x00000000CA3A9000 0000A0 (v32 TOSHIB A0082    00000001 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: BOOT 0x00000000CA3A7000 000028 (v01 TOSHIB A0082    00000000 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: SLIC 0x00000000CA3A6000 000176 (v01 TOSHIB A0082    00000000 LOHR 0000005F)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: SSDT 0x00000000CA39A000 00045E (v01 TOSHIB SataAhci 00001000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: SSDT 0x00000000CA397000 000720 (v01 TOSHIB PtidDevc 00001000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: SSDT 0x00000000CA395000 0008CA (v01 PmRef  Cpu0Ist  00003000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.000000] ACPI: SSDT 0x00000000CA394000 000A7E (v01 PmRef  CpuPm    00003000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.000000] Zone ranges:
Mar 26 17:54:05 porteus kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   Normal   [mem 0x100000000-0x1af5fffff]
Mar 26 17:54:05 porteus kernel: [    0.000000] Movable zone start for each node
Mar 26 17:54:05 porteus kernel: [    0.000000] Early memory node ranges
Mar 26 17:54:05 porteus kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   node   0: [mem 0x00100000-0x1fffffff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   node   0: [mem 0x20200000-0x40003fff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   node   0: [mem 0x40005000-0xca28efff]
Mar 26 17:54:05 porteus kernel: [    0.000000]   node   0: [mem 0x100000000-0x1af5fffff]
Mar 26 17:54:05 porteus kernel: [    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 1521595
Mar 26 17:54:05 porteus kernel: [    0.000000] Policy zone: Normal
Mar 26 17:54:05 porteus kernel: [    0.000000] Memory: 6008796K/6183084K available (4765K kernel code, 599K rwdata, 1232K rodata, 848K init, 640K bss, 174288K reserved)
Mar 26 17:54:05 porteus kernel: [    0.000068] ACPI: Forced DSDT copy: length 0x094BF copied locally, original unmapped
Mar 26 17:54:05 porteus kernel: [    0.009497] ACPI: All ACPI Tables successfully acquired
Mar 26 17:54:05 porteus kernel: [    0.017163] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Mar 26 17:54:05 porteus kernel: [    0.017163] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Mar 26 17:54:05 porteus kernel: [    0.050477]  #2<7>[    0.062204] CPU2: Thermal monitoring handled by SMI
Mar 26 17:54:05 porteus kernel: [    0.078124]  #3
Mar 26 17:54:05 porteus kernel: [    0.107396] ACPI: Dynamic OEM Table Load:
Mar 26 17:54:05 porteus kernel: [    0.107407] ACPI: SSDT 0xFFFF8801A7B70000 000832 (v01 PmRef  Cpu0Cst  00003001 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.112296] ACPI: Dynamic OEM Table Load:
Mar 26 17:54:05 porteus kernel: [    0.112304] ACPI: SSDT 0xFFFF8801A7ADF000 000303 (v01 PmRef  ApIst    00003000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.118175] ACPI: Dynamic OEM Table Load:
Mar 26 17:54:05 porteus kernel: [    0.118181] ACPI: SSDT 0xFFFF8801A7B2AE00 000119 (v01 PmRef  ApCst    00003000 INTL 20061109)
Mar 26 17:54:05 porteus kernel: [    0.124777] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
Mar 26 17:54:05 porteus kernel: [    0.124784] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
Mar 26 17:54:05 porteus kernel: [    0.148661] ACPI: Enabled 5 GPEs in block 00 to 3F
Mar 26 17:54:05 porteus kernel: [    0.604056] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
Mar 26 17:54:05 porteus kernel: [    0.604074] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff8801a883bcd0), AE_NOT_FOUND (20140724/psparse-536)
Mar 26 17:54:05 porteus kernel: [    0.604121] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
Mar 26 17:54:05 porteus kernel: [    0.604131] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff8801a883bcf8), AE_NOT_FOUND (20140724/psparse-536)
Mar 26 17:54:05 porteus kernel: [    0.614039] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
Mar 26 17:54:05 porteus kernel: [    0.614058] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD] (Node ffff8801a883bcd0), AE_NOT_FOUND (20140724/psparse-536)
Mar 26 17:54:05 porteus kernel: [    0.614104] ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
Mar 26 17:54:05 porteus kernel: [    0.614115] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF] (Node ffff8801a883bcf8), AE_NOT_FOUND (20140724/psparse-536)
Mar 26 17:54:05 porteus kernel: [    0.699720] EXT4-fs (sda5): warning: mounting unchecked fs, running e2fsck is recommended
Mar 26 17:54:05 porteus kernel: [    1.460038] REISERFS warning (device loop2): sh-2006 read_super_block: bread failed (dev loop2, block 2, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.460042] REISERFS warning (device loop2): sh-2006 read_super_block: bread failed (dev loop2, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.465056] REISERFS warning (device loop4): sh-2006 read_super_block: bread failed (dev loop4, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.466920] REISERFS warning (device loop5): sh-2006 read_super_block: bread failed (dev loop5, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.490270] REISERFS warning (device loop13): sh-2006 read_super_block: bread failed (dev loop13, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.494929] REISERFS warning (device loop15): sh-2006 read_super_block: bread failed (dev loop15, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.513295] REISERFS warning (device loop22): sh-2006 read_super_block: bread failed (dev loop22, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.527369] REISERFS warning (device loop27): sh-2006 read_super_block: bread failed (dev loop27, block 2, size 4096)
Mar 26 17:54:05 porteus kernel: [    1.527374] REISERFS warning (device loop27): sh-2006 read_super_block: bread failed (dev loop27, block 16, size 4096)
Mar 26 17:54:05 porteus kernel: [    2.939274] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
Mar 26 17:54:06 porteus bluetoothd[2867]: Unable to load keys to adapter_ops: Function not implemented (38)
Mar 26 17:54:06 porteus bluetoothd[2867]: mce replied with an error: org.freedesktop.DBus.Error.ServiceUnknown, The name com.nokia.mce was not provided by any .service files
Mar 26 17:54:07 porteus kernel: [    3.793860] wl: module license 'unspecified' taints kernel.
Mar 26 17:54:07 porteus kernel: [    3.793860] Disabling lock debugging due to kernel taint
Mar 26 17:54:07 porteus kernel: [    4.024855] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
Mar 26 17:54:07 porteus kernel: [    4.024868] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
Mar 26 17:54:07 porteus kernel: [    5.009962] [drm:intel_enable_lvds] *ERROR* timed out waiting for panel to power on
Mar 26 17:54:07 porteus bluetoothd[3327]: Unable to get on D-Bus
Mar 26 17:54:07 porteus NetworkManager[3389]: <warn> failed to allocate link cache: (-12) Object not found
Mar 26 17:54:08 porteus NetworkManager[3389]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Mar 26 17:54:08 porteus NetworkManager[3389]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Mar 26 17:54:08 porteus NetworkManager[3389]: <warn> Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "GetManagedObjects" with signature "" on interface "org.freedesktop.DBus.ObjectManager" doesn't exist 
Mar 26 17:54:08 porteus NetworkManager[3389]: <warn> Trying to remove a non-existant call id.
Mar 26 17:54:09 porteus NetworkManager[3389]: <warn> No agents were available for this request.
Mar 26 17:54:09 porteus NetworkManager[3389]: <warn> Activation (wlan0) failed for connection 'p4rc'
Mar 26 17:54:10 porteus ModemManager[3590]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin 
Mar 26 17:54:10 porteus ModemManager[3590]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:02:00.0': not supported by any plugin 
Mar 26 17:54:19 porteus dhcpcd[3770]: wlan0: ipv6rs_sendprobe: sendmsg: 
Voltaire: Le mieux est l'ennemi du bien.

User avatar
phhpro
Full of knowledge
Full of knowledge
Posts: 545
Joined: 10 Nov 2013, 20:35
Distribution: .

Re: "real" installation of Porteus to harddisk revisited

Post#3 by phhpro » 26 Mar 2015, 23:47

...
Last edited by phhpro on 04 Feb 2016, 03:06, edited 1 time in total.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 973
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: "real" installation of Porteus to harddisk revisited

Post#4 by ncmprhnsbl » 27 Mar 2015, 03:22

fairly safe to say, the Offical Porteus position is: a full/real/decompressed install is not supported or recomended. :evil:
the official porteus recomendation is : install slackware or slackware derivative. :good:
porteus is designed for live/frugal install enviroment. :Yahoo!:
however the user is free to do whatever they like :%) :P :wall: :beer: =@ :oops: 8) :crazy:
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
francois
Contributor
Contributor
Posts: 5080
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: "real" installation of Porteus to harddisk revisited

Post#5 by francois » 27 Mar 2015, 03:45

I am just trying to get a better understanding of slackware and to learn to troublehoot it.

Once functional, I would like to strip porteus kde from kde to be left with xorg and then rebuild with alien bob plasma 5.2 DE.

Why not go for a full slackware kde install? I would like to keep that full slackware install as lean as possible.
Voltaire: Le mieux est l'ennemi du bien.

Tonio
Contributor
Contributor
Posts: 266
Joined: 28 Dec 2010, 16:37
Distribution: Slackware,porteus,FreeBSD,Slax
Location: 127.0.0.1

Re: "real" installation of Porteus to harddisk revisited

Post#6 by Tonio » 02 May 2015, 02:56

I wondered where this idea has been explored before. I remember folks installing Slax to harddrive and remastering it, because it was Slackware but in a lean mode. This would be a similar situation I guess. How about installing Slackware full install and removing/building the programs in question? It would be a learning curve, but stripping Slackware of many things causes one to shoot ourselves in the foot. I have played a bit, but I get burned and prefer actually to have Porteus on a USB stick play around with it and then build the files and check what is needed to make stuff work and use portable version. But your concept is good, maybe virtualbox or other virtualization? run and test live? Porteus is awesome, but sometimes hunting down some programs and making them work becomes a task in itself. Do you know if the new KDE Plasma requires systemd? If it does then things will get messy :( and :evil: I am :sorry: to discourage you from going there.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5574
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: "real" installation of Porteus to harddisk revisited

Post#7 by brokenman » 02 May 2015, 16:57

If i were to attempt this I would do it like so:

From a porteus live installation
Create a work partition (say sda5)
Unpack the 000-kernel.xzm and 001-core.xzm package to this partition
chroot into the sda5 partition to do your work
export an ISO for testing in virtualbox

This will save countless hours of rebooting. Once you have the thing booting in vbox then try booting into the install to see if it works. Then repeat procdure with 002-xorg.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1094
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: "real" installation of Porteus to harddisk revisited

Post#8 by wread » 02 May 2015, 21:46

IMHO:
The beauty of Porteus is even the fact that it installs itself anew, automatically with every boot. Installing it the old way would be a regression! :crazy:

If you are convinced of this advantage (forget about viruses, Trojans, security paranoia, etc)......

Then, why bother??? :)

THE OTHERS ARE LAGGING...FAR BEHIND!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

Post Reply