My node motherboard has a 8086:1050 e100 nic on it. I can use this NIC to
boot from the network, but once the kernel is loaded, it doesn't see the
NIC.
The 8086:1050 NIC is supposed to use the e100 driver, which appears to be
compiled into the kernel according to
/usr/share/systemimager/boot/i386/standard/config, if that's to be
believed.
What part of the BOEL bootdisk environment needs to be changed to map
8086:1050 to the e100 driver? Something (other than me) seems to be in
the dark here...
---
Jason Marshall, Unix Geek, Kelman Technologies, Inc., Calgary, AB, Canada.
From a Sun Microsystems bug report (#4102680):
"Workaround: don't pound on the mouse like a wild monkey."
"I have great faith in fools:
Self confidence my friends call it." -Edgar Allan Poe
---------- Forwarded message ----------
Date: Tue, 1 Jun 2004 14:17:57 -0600 (MDT)
From: Jason Marshall <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Sisuite-users] e100 not seen by boel environment
I have a new machine here with an Intel Desktop board in it.
It boots over the network and runs the BOEL /etc/init.d/rcS script up til
it gets to the start_network() routine. At that point it says it can't
find information in /local.cfg (there isn't one), and that it will try to
learn what it needs via DHCP. I believe that's normal stuff.
Unfortunately, it tries to dhclient on "lo" rather than "eth0". An
ifconfig shows that there is no eth0. catting /proc/pci shows that the
card is an 8086:1050 Intel PRO/100 card, and looking at another machine's
/usr/share/hwdata/pcitable entry for that card, I learned that it is
supposed to use the e100 driver, which is compiled into the kernel I'm
using, assuming that /usr/share/systemimager/boot/i386/standard/config is
an accurate representation of what went into the kernel in that same
directory (which is the same kernel that's in /tftpboot).
Okay, so I know what the card is, but the BOEL system doesn't recognize
it. I loopback-mounted the initrd file I boot with, and didn't see
anything that I could tweak to make it recognize this card. Can someone
point me in the right direction? I think I'm close, but I need help over
this small(?) hurdle...
Thanks!
---
Jason Marshall, Unix Geek, Kelman Technologies, Inc., Calgary, AB, Canada.
From a Sun Microsystems bug report (#4102680):
"Workaround: don't pound on the mouse like a wild monkey."
"I have great faith in fools:
Self confidence my friends call it." -Edgar Allan Poe
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
