2.2.19 and eepro100
Hi,
I got the 2.2.19 sorces, patched them with reiserfs, compiled and booted the new kernel. Neither the builtin eepro100 nor Intels e100-1.6.13 driver worked; they were loaded, but ifconfig failed:
+ ifconfig eth1 192.168.0.235 broadcast 192.168.0.255 netmask 255.255.255.0 up
SIOCSIFFLAGS: Resource temporarily unavailable
SIOCSIFFLAGS: Resource temporarily unavailable
What's wrong here? I want 2.2 because 2.4 eats up too much memory on my machine, and I have only 256 MB... ;-)
Cheers
Olaf
Quoted 8 lines · Olaf Zaplinski
I got the 2.2.19 sorces, patched them with reiserfs, compiled and booted the new kernel. Neither the builtin eepro100 nor Intels e100-1.6.13 driver worked; they were loaded, but ifconfig failed:
+ ifconfig eth1 192.168.0.235 broadcast 192.168.0.255 netmask 255.255.255.0 up
SIOCSIFFLAGS: Resource temporarily unavailable
SIOCSIFFLAGS: Resource temporarily unavailable
Try to cold boot. I have experienced difficulties with 2.4.x and 2.2.x interacting on a cold reboot.
It would seem that the 2.2.19 kernel does not get a valid MAC address when *warm* booted into from a 2.4.x kernel.
[This used to be a problem with 2.4.x <-> 2.4.x, but 2.4.7 fixed that.]
Quoted 6 lines · In article <[email protected]> you wrote:
Hi,
I got the 2.2.19 sorces, patched them with reiserfs, compiled and booted the new kernel. Neither the builtin eepro100 nor Intels e100-1.6.13 driver worked; they were loaded, but ifconfig failed:
Quoted 7 lines
+ ifconfig eth1 192.168.0.235 broadcast 192.168.0.255 netmask 255.255.255.0 up
SIOCSIFFLAGS: Resource temporarily unavailable
SIOCSIFFLAGS: Resource temporarily unavailableWhat's wrong here? I want 2.2 because 2.4 eats up too much memory on my machine, and I have only 256 MB... ;-)
Have a look into the BIOS setup and check whether it is configured for a non-plug'n'play OS. If not - do so.
Juri
Signature · 1 line
Juri Haberland <[email protected]>