Transporting Porteus

Post here if you are a new Porteus member and you're looking for some help.
hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Transporting Porteus

Post#1 by hitsware » 12 Jan 2014, 19:28

All desktop versions ....
Both fat32 and ext3 ...
several usb sticks ...
Porteus works great on the system (~5 yr old XP)
that I downloaded and installed it with ......
BUT !
When I boot my actual target system (mini-itx atom processor)
with the sticks .....
I get a black screen with mouse arrow only.
Right click brings a menu that says porteus 2.1.1 but only the
turn off and terminal items respond ......
Slax works fine !!!
Any Insights ???????????

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Transporting Porteus

Post#2 by fanthom » 12 Jan 2014, 19:48

are you saying that the same usb works fine on one PC but does not on mini-itx atom processor system?
please launch terminal and generate 'xpsinfo' raport. also - could you make a photo of what you are getting if possible?
thanks
Please add [Solved] to your thread title if the solution was found.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#3 by hitsware » 12 Jan 2014, 21:18

> are you saying that the same usb works fine on one PC but does not on mini-itx atom processor system?

precisamundo !

Image

The xpsinfo put the info @ /root/Desktop/psinfo_report.txt
but I get access denied to open it ??? (complete linux newbie here)

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#4 by hitsware » 12 Jan 2014, 23:58

I rebuilt with root as user and it's a different ballgame.
(working at least to some extent)
The report is too long for the forum, but I'll cut it in half or ??
if you want ........

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Transporting Porteus

Post#5 by fanthom » 13 Jan 2014, 09:45

@hitsware
really weidr - looks like plain openbox :)
please upload xpsinfo raport to pastebin.com and link here.
thanks

@phhpro
is it the same issue you are experiencing? if yes then we are in troubles.
Please add [Solved] to your thread title if the solution was found.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#6 by hitsware » 13 Jan 2014, 17:10

Pardon these posts , I'll try something different , report is too big for pastebin .
Last edited by hitsware on 13 Jan 2014, 17:17, edited 1 time in total.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#7 by hitsware » 13 Jan 2014, 17:11

bled, doesn't support DPO or FUA
Last edited by hitsware on 13 Jan 2014, 17:26, edited 1 time in total.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#8 by hitsware » 13 Jan 2014, 17:13

e 'org.freedesktop.UPower'
Last edited by hitsware on 13 Jan 2014, 17:25, edited 1 time in total.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#9 by hitsware » 13 Jan 2014, 17:21

This is handier :
BUT, this was after changing build to root user.
I know no way to capture report the other way
since the file manager doesn't work .....

http://home.comcast.net/~mnjmiller/psinfo_report.txt

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Transporting Porteus

Post#10 by fanthom » 13 Jan 2014, 17:44

please check if you have:

Code: Select all

session=/usr/bin/startlxde
in /etc/lxdm/lxdm.conf
and

Code: Select all

[Desktop]
Session=lxde
in /home/guest/.dmrc (hidden file)

i guess that you have 'Session=openbox' in .dmrc
Please add [Solved] to your thread title if the solution was found.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#11 by hitsware » 13 Jan 2014, 18:11

Do you mean to go back to guest as user, so that the problem re-occurs ?
Then pull the usb-stick and read the files with another PC ?
As I said, it seems to be working now (root as user) .......

User avatar
fanthom
Moderator Team
Moderator Team
Posts: 5666
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland
Contact:

Re: Transporting Porteus

Post#12 by fanthom » 13 Jan 2014, 19:26

while logged into working root account please launch lxterminal and paste here output of 'cat /home/guest/.dmrc' command.
thanks
Please add [Solved] to your thread title if the solution was found.

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#13 by hitsware » 13 Jan 2014, 19:38

guest@porteus:~$ cat /home/guest/.dmrc
cat: /home/guest/.dmrc: No such file or directory
guest@porteus:~$ sudo cat/home/guest/.dmrc
bash: sudo: command not found
guest@porteus:~$ su cat /home/guest/.dmrc
Unknown id: cat
guest@porteus:~$ su cat/home/guest/.dmrc
Unknown id: cat/home/guest/.dmrc
guest@porteus:~$ su
Password:
root@porteus:/home/guest# cat /home/guest/.dmrc
cat: /home/guest/.dmrc: No such file or directory
root@porteus:/home/guest# cat/home/guest/.dmrc
bash: cat/home/guest/.dmrc: No such file or directory
root@porteus:/home/guest#

hitsware
Black ninja
Black ninja
Posts: 80
Joined: 12 Jan 2014, 19:13
Distribution: porteus
Location: sacramento, calif.

Re: Transporting Porteus

Post#14 by hitsware » 14 Jan 2014, 03:14

phhpro wrote:@fanthom: Bears an obvious similarity. By now, I'm almost always presented with exactly the same situation: cursor on black screen -> CTRL-ALT-F2 -> CTRL-ALT-F7 -> GUI

If it helps, graphics is an Intel Golan. Odd, I haven't thought of it before. Might give it a moment to fetch the latest, and then try to drop it in. Will post back once I have the results.
http://www.timesys.com/embedded-linux/r ... enter/atom

This is a Porteus issue (not Linux alone)
I've used many distros (live and installed)
on my Atom system with little (if any)
differance (in performance) from the
same distro on the Pentium ...

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Transporting Porteus

Post#15 by Ahau » 16 Jan 2014, 16:06

This one is rather odd. hitsware, please do try as guest again. You don't need to reinstall for this, just hit TAB on the bootloader menu screen and use the arrow and backspace keys to remove the cheatcode, 'login=root' (see our cheatcode documentation for more on that if needed), then hit enter to boot up as root.

If the problem is not repeated, it may have been a corrupted download or some other quirk. If it was repeated (and this goes for phpro too), then I'm at a bit of a loss for what's going on. The only thing I can really imagine is that the lxde components aren't starting up due to some race condition or lxde is trying to start before something else is ready and that is causing it to fail. You could try the following --

as root, open up /etc/rc.d/rc.4 and just prior to the last line, insert a new line and add 'sleep 5', so it looks like this:

Code: Select all

[ "$login"  ] && sed -i -r s/^.*autologin=.*$/autologin$login/g /etc/lxdm/lxdm.conf || sed -i -r s/^.*autologin=.*$/autologin=guest/g /etc/lxdm/lxdm.conf
sleep 5
exec /usr/sbin/lxdm
Save the file and reboot if you are using saved changes. If you're not using saved changes, add this to your rootcopy, e.g.

Code: Select all

mkdir -p /mnt/sdb2/porteus/rootcopy/etc/rc.d
cp -ar /etc/rc.d/rc.4 /mnt/sdb2/porteus/rootcopy/etc/rc.d/
where /mnt/sdb2/porteus is the location of your current installation.

Other than that, I guess my only advice is to make sure you test it in always fresh mode so you are testing without any additional modules or files in rootcopy or saved changes, just to make sure it's not some configuration that got saved for your other machine that is interfering.

HTH
Please take a look at our online documentation, here. Suggestions are welcome!

Post Reply