On Mar 18, 2008, at 2:46 PM, Chris Babcock wrote:
T. Marvin wrote:
The error I'm having (on the new one) is that when it boots up, the
ethernet devices will show up as eth0 thru eth2 in the boot logs or
whenever I force removal and reloading (i.e. rmmod, modprobe) of the
'natsemi' driver,
I have a pair of Soekris Net4501's, one purchased at the end of last
year (2007), the next one purchased within the last couple weeks (March
2008). The newest one had v1.33 Bios (I down graded to both v1.28 and
v1.32 in my testing, more on the reason following), the older one I
presume has v1.32
IIRC, linux has the possibility to map the physical devices to logical
devices in the bootloader, by passing options to the kernel, linked to the
base memoryaddress
This may have something to do with it?
Kind regards,
Nils
On Tue, Mar 18, 2008 at 9:49 AM, T. Marvin [EMAIL PROTECTED] wrote:
I
Nils Vogels wrote:
IIRC, linux has the possibility to map the physical devices to logical
devices in the bootloader, by passing options to the kernel, linked to the
base memoryaddress
It likely can, though I've never used that feature, so am unfamiliar
with it.
This may have something to do
T. Marvin wrote:
The error I'm having (on the new one) is that when it boots up, the
ethernet devices will show up as eth0 thru eth2 in the boot logs or
whenever I force removal and reloading (i.e. rmmod, modprobe) of the
'natsemi' driver, but show up as eth3 thru eth5 when the driver is in
