24 Oct
2005
24 Oct
'05
11:39
Doug McGarrett wrote: > Hello, all-- > > My last message said that maybe I didn't have Suse running > on this machine. Now I'm absolutely sure I did. Before > I bought this MOBO--ASUS P4PE--I checked with people on > this list, and they said it worked fine. So I don't > understand why I need a new driver at this point in time. > There must have been a driver in 9.2 that worked. Doug, With the event of suse 9.3 Suse replaced the 'proprietary' bcm5700 driver with tg3 - so this can be the reason. > (I admit > that 9.2 itself was not very sturdy, but it worked for a while.) > Anyway, I do need the new driver, I guess, if somebody can > translate the read-me file into hands-on directions. > Handhelding as far as i can from this distance without disturbing your learning path: Note: a fine resource i found for you is http://www.mike-devlin.com/linux/driver.htm Read this also and try these solutions if the cookbook below does not work. - What you will do is building (compiling) from source with the help of the rpm package manager based on a .spec file that descrines the dependencies etc. - A major dependency is that you have the tols available to compile: from YaST's update/install software first install (based on the 'Selections' filter) the complete C/C++ compiler and tools selection. >From the 'kernel development' selection install the package 'kernel-source'. - The 'RPM' path for suse is /usr/src/packages/ - The rpm -ivh bcm5700*.src.rpm will instal .te .spec file in /usr/scr/packages/SPECS - Go to this directory and enter as root in the console 'rpmbuild -bb SPECS/bcm5700.spec' (you will have to use the 'rpmbuild' command with suse 10) This is the compile action and a lot of text will scroll by Errors will have to be solved (most of the time -devel packages that are not installed) - When it succeeds it wil create in /usr/src/packages/RPMS - and probably the - /i386 folder the rpm file that you can install. - install it with rpm -ivh RPMS/i386/bcm5700*.i386.rpm Now the driver needs to be loaded but probably you have to unload the other network driver (tg3) - Check with 'lsmod | grep tg3' if you have this driver up and running - If so unload it with 'rmmod tg3' - install your driver with 'insmod bcm5700' - check with 'lsmod | grep bcm5700' if it is running - To avoid you have to do this every time after a reboot you have to make this the default. You should be able to do this where you define the card in YaST (-> Network devices -> Network card -> Change -> Change -> Advanced -> Hardware details and enter the module name bcm5700. - Run 'SuSEconfig' (note: translated from a Dutch system so it can be a littlebit different) - restart the network with 'rcnetwork restart' to see what happens. The resource i pointed you towards does the latter more generic by changing the file /etc/modules.conf to change an interface alias name from tg3 to bcm5700. Note with the newer suses this should be /etc/modprobe.conf - or even beter - modprobe.conf.local In this file enter 'install tg3 /bin/false alias eth0 bcm5700 ' Peter Vollebregt