I had a similar problem with 7.1. SuSE goes in for modules in a big way
when they build their kernels. On start up my module didn't always load
reliably so I put this line in /etc/rc.d/boot.local
/sbin/insmod 3c90x
It's a kluge but works reliablbly. /sbin/modprobe -k might be a better
way o load. Be sure to invoke using the full path name here as PATH
isn't set yet.
An alternative is to compile the driver into the kernel so it's
guaranteed to be there at startup.
Ed.
Rusty wrote:
>
> I'm having a problem with Suse 7.2. I have seven boxes running
> different OS's at different times. I use swappable trays to load
> different hard drives to different boxes as needed.
>
> Right now I'm trying to set up a small network with a OpenBSD
> gateway/router/firewall/NAT. To this I plan to attach two (2) windoz
> boxes, (my sons games and my wife's email and word processing) plus two
> openbsd development boxes and my Suse 7.2.
>
> The box that will run my Suse has a 3COM 905B-TX eithernet card which
> Suse sets up as eth0. I can connect to the router and internet on this
> card using windoz and openbsd but under Suse it fails. Anyone know of
> problems with 3COM cards and Suse??
>
> Any help is appreciated.
>
> Rusty
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:05:37 EDT