Page 1 of 1
Porteus 2.0 boot issue
Posted: 04 Jun 2013, 15:16
by banshee22
Hi All,
I'm trying to move a Porteus 1.1 usb key to Porteus 2.0 but i have to face some issues.
I'm using this cheatcode line:
APPEND initrd=initrd.xz root=/dev/ram0 rw autoexec=xconf;telinit~4 lxde toroot nosound splash=verbose
And startx doesn't start...Last error message is: "INIT: Id "x1" respawning too fast: disabled to 5 minutes",
Then if i press enter, system ask me for root password in console mode :-(
Any idea?
Thanks for your help
Re: Porteus 2.0 boot issue
Posted: 04 Jun 2013, 16:47
by fanthom
hi banshee22,
porteus-2.0 has different cheatocde set (much simpler) please use these:
Code: Select all
APPEND initrd=initrd.xz lxde login=root volume=0%
if you are using 32bit version then please remove 'lxde' cheatcode as LXDE is not present for this arch.
Re: Porteus 2.0 boot issue
Posted: 05 Jun 2013, 07:43
by banshee22
Thanks for your answer Fanthom. It's really nice to have so quick answer each time!
Is there really any way to have lxde on 32 bits ?
B.
Re: Porteus 2.0 boot issue
Posted: 05 Jun 2013, 12:21
by brokenman
Now you can have any desktop on any arch.
http://build.porteus.org
Re: Porteus 2.0 boot issue
Posted: 05 Jun 2013, 13:15
by banshee22
Great!
I tried Porteus 2.1, 32 bits lxde.
I've always the message boot message:
/usr/sbin/lxdm: line 31: /usr/sbin/lxdm-binary: cannot execute binary file
.....
"INIT: Id "x1" respawning too fast: disabled to 5 minutes",
I've the same message if I try to execute /usr/sbin/lxdm-binary extract from 003-lxde.xzm ...
So is there definitively no way to have lxde on porteus 32 bits?
B.
Re: Porteus 2.0 boot issue
Posted: 05 Jun 2013, 14:26
by banshee22
Finally, I decided to try porteus 2.1 rc2 32 bits, lxde. It works well but I would be happy to make some comments about it... Where is it possible? (lost in the forum ;-) )
B.
Re: Porteus 2.0 boot issue
Posted: 05 Jun 2013, 15:07
by Ahau
hi banshee22,
You can report feedback regarding 2.1 rc1 on this thread:
http://forum.porteus.org/viewtopic.php?f=53&t=2222
We only have one thread for all desktops and architectures, to keep everything in one place.