[Bug 365380] Re: Some LTSP clients kernel panic on boot

2009-05-21 Thread Ronald van Engelen
This problem exist on the Asus EEE PC-900 (output of `lspci -vvv` of locally installed jaunty attached). Even disabling the embedded wlan device in the bios doesn't resolve this issue. The output is (after about 4 seconds initializing usb): ipconfig: eth0: SIOCGIFINDEX: No such device ipconfig:

Re: [Bug 365380] Re: Some LTSP clients kernel panic on boot

2009-04-23 Thread Stéphane Graber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kenneth Finnegan wrote: > Alright. Got it: It has a second NIC, which it happens to set as eth0, > tries to mount the nbd on it, fails since it isn't plugged in, and dies. > The workaround was either connecting the second port to the network, or > unin

[Bug 365380] Re: Some LTSP clients kernel panic on boot

2009-04-23 Thread Kenneth Finnegan
Alright. Got it: It has a second NIC, which it happens to set as eth0, tries to mount the nbd on it, fails since it isn't plugged in, and dies. The workaround was either connecting the second port to the network, or uninstall it completely. I'm surprised it isn't smart enough to retry on eth1 once

Re: [Bug 365380] Re: Some LTSP clients kernel panic on boot

2009-04-22 Thread Stéphane Graber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can you try booting the thin client without the splash and quiet options (you can change that in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default on the server), that should give you a bit more information on what went wrong. I'm especially looking at

[Bug 365380] Re: Some LTSP clients kernel panic on boot

2009-04-22 Thread Kenneth Finnegan
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25870172/Dependencies.txt -- Some LTSP clients kernel panic on boot https://bugs.launchpad.net/bugs/365380 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubun