We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
While I'm not using LTSP myself, I am using NFS Boot with PXE, and I'm
experiencing the same DHCP woes that have been mentioned here.
I've followed the advice by Alkis Georgopoulos, and it really did help.
After testing out how specifying a complete ip=xxx works (Like Alkis specified:
After mucking around with Jaunty LTSP with Karmic LTSP PPA, initramfs,
etc. I decided to jump into Karmic Beta itself. Our LTSP server has two
drives, so I can afford to experiment with an alternative setup while
keeping the working one (LTSP 8.10) on the other drive.
Karmic LTSP based on the
** Changed in: ltsp (Ubuntu)
Status: New = Incomplete
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I've solved this problem by adding acpi=off to my
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default .
Finally I have normal boot for this damn client!!!
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification
It's better to put pci=noacpi instead of acpi=off so the client still
able to shutdown.
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Oli,
I tried ip=:eth0 after the splash in
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and ltsp-update-image
but that doesn't help. The boot hangs for a bit longer, but I still get
the same message.
I've verified the driver to be tg3 and that seems to be loaded. It seems
suspicious of
Increasing the pool didn't help. Its currently at 192.168.0.20 to
192.168.0.250
When this specific thin client boots up, it gets 192.168.0.210 So, if I
edit /var/lib/tftpboot/i386/pxelinux.cfg/default and add
ip=192.168.0.210:eth0 then the machine still hangs at the same
point, but doesn't
First, try to put a *complete* ip=xxx parameter there:
client-ip:server-ip:gw-ip:netmask:hostname:device:autoconf
Fill *all* of the above, with autoconf=none.
If that works, then you're certain it's a DHCP problem.
Karmic contains a new script (/opt/ltsp/i386/usr/share/initramfs-
doesnt the workaround mentioned above work for you ?
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We have Dell Optiplex 745 as thin clients for a Jaunty LTSP setup.
Everything works well on 8.10 LTSP, but on jaunty, on the client side I
see (I am typing what I see):
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
ADDRCONF(NETDEV_CHANGE):
I had the same error as #1. The problem was DHCP, there were no more
free ips in the pool.
For some reason the client would actually get an IP from DHCP at PXE
boot. It used it to download the kernel, but then it tried again before
the final LTSP boot, failing this time.
Making the DHCP ip
I am using Ubuntu 9:04 Desktop with server kernel 2.6.28.13, after
upgrade of chroot appears this message on the clients:
/init: .: line 1: can't open /tmp/net-eth0.conf
kernel panic - not syncing: Attempted to kill init!
The NetworkManager recognizes the eth0 as Auto eth0, have
I tried this and did not work:
The good people at IRC #ltsp helped me solve the problem
here's what I did to get PXE boot to work with the marvell/sky2 driver
sudo nano /opt/ltsp/i386/etc/initramfs-tools/modules and add sky2
sudo nano /opt/ltsp/i386/usr/share/initramfs-tools/hook-functions and
This doesn't help.
In fact, when I've booted from 9.04 live cd, lshw gave me following
difference with 7.10 live cd:
9.04:
/0/100/5 eth0network RTL-8139/8139C/8139C+
/1 pan0network Ethernet interface
7.10:
/0/100/5 eth0
I have the same problem (After upgrading to Jaunty one of the clients
refuses to boot giving Kernel Panic). But I have only one NIC at client
side.
That's what I've got:
Begin: Loading essential drivers
...
8139too: Fast Ethernet driver 0.9.28
8139cp: 10/100 PCI Ethernet Driver v 1.3 (Mar
as a workaround you can put ip=:eth0 (and change eth0 to whatever
your device is) behind splash in
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification
** Summary changed:
- Some LTSP clients kernel panic on boot
+ LTSP clients kernel panic on boot when active nic isn't eth0
--
LTSP clients kernel panic on boot when active nic isn't eth0
https://bugs.launchpad.net/bugs/365380
You received this bug notification because you are a member of
18 matches
Mail list logo
