[Unattended] Problem linuxboot 4.9 and Broadcom Netlink BCM57780

[david Vandergucht]

Hi there !

I've some trouble starting the pxe linuxboot 4.9 with some dell vostro
workstation with the following NIC:
Broadcom Netlink BCM57780

It seems that no eth interface are found and it's dropping to shell.

What should i do ?

[Jason Oster]

Post by david Vandergucht
Hi there !
I've some trouble starting the pxe linuxboot 4.9 with some dell vostro
Broadcom Netlink BCM57780
It seems that no eth interface are found and it's dropping to shell.

This was a bug in the Linux kernel v2.6.34. See the following list
thread for information that I collected at the time I was experiencing it:

http://sourceforge.net/mailarchive/message.php?msg_name=4BF5A2FC.10209%40campnavajo.com

In the thread, I explain where I found patches for the bug, and how to
apply them. Thankfully, they are no longer needed in Unattended SVN
trunk, since this bug is fixed in Linux kernel v2.6.35. The kernel
version currently in trunk is v2.6.35.8.

I can't tell you exactly when it was fixed in the kernel, but here is
the commit:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.35.y.git;a=commit;h=4e4f10f6498bc5038c0a110b5f21682fcb5578d7

Post by david Vandergucht
What should i do ?

The only thing you can do really do about this is building linuxboot
from trunk. And the easiest way to test it without burning a hundred
CDs is by using the patch in ticket #1 to boot it from a USB flash drive:

http://sourceforge.net/apps/trac/unattended/ticket/1

Or have someone else build it for you. I don't think Unattended does
nightly builds. That might be nice to have.

[n22e113]

Post by david Vandergucht
I've some trouble starting the pxe linuxboot 4.9 with some dell vostro
Broadcom Netlink BCM57780
It seems that no eth interface are found and it's dropping to shell.

I had this problem with another onboard NIC. The quick fix for me was to
install an old PCI NIC (eth1) card and run two RJ45 cables to your
network. pxe boot using your Broadcom NIC and mapznrun.bat will try to
use eth0 then eth1 to connect to the Z: drive. I used an old D-Link
DFE-538TX (without a boot rom) and it works great!

[Jason Oster]

Post by n22e113
I had this problem with another onboard NIC. The quick fix for me was to
install an old PCI NIC (eth1) card and run two RJ45 cables to your
network. pxe boot using your Broadcom NIC and mapznrun.bat will try to
use eth0 then eth1 to connect to the Z: drive. I used an old D-Link
DFE-538TX (without a boot rom) and it works great!

That's a great idea for machines with PCI ports. On laptops, netbooks,
and USFF machines, perhaps USB-to-ethernet/wifi adapters will also work.

The Zino HD is a USFF, and we didn't have any usb-to-ethernet adapters
at the time. Nor do we have a WiFi access point. Nonetheless, an
excellent tip!

[Juan Jose Pablos]

I have use a usb network card but i manually load the modules

Post by n22e113
I had this problem with another onboard NIC. The quick fix for me was to
install an old PCI NIC (eth1) card and run two RJ45 cables to your
network. pxe boot using your Broadcom NIC and mapznrun.bat will try to
use eth0 then eth1 to connect to the Z: drive. I used an old D-Link
DFE-538TX (without a boot rom) and it works great!

That's a great idea for machines with PCI ports. On laptops, netbooks, and
USFF machines, perhaps USB-to-ethernet/wifi adapters will also work.
The Zino HD is a USFF, and we didn't have any usb-to-ethernet adapters at
the time. Nor do we have a WiFi access point. Nonetheless, an excellent
tip!
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
unattended-info mailing list
https://lists.sourceforge.net/lists/listinfo/unattended-info