I did a quick test on one of our thin clients. It now manage to get its IP address from the DHCP server and boot successfully though it took a very long time to get an IP address, long enough for usplash to timeout and switch me back to the console.
Unfortunately as it's using a network harddisk, I can't do DHCP tests after the boot process so can't give much more information about if that's actually a lot slower than with -9. The kernel was the i386 generic one. The hardware used for the test was: 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02) information from dmesg: [ 2.833432] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 2.833478] r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 2.833507] r8169 0000:01:00.0: setting latency timer to 64 [ 2.833528] r8169 0000:01:00.0: unknown MAC (27a00700) [ 2.835586] eth0: RTL8169 at 0xf88ea000, 00:1c:c0:5d:f4:40, XID 24a00000 IRQ 220 ... [ 4.776203] r8169: eth0: link up ... [ 44.168514] eth0: no IPv6 routers present -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
