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. (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. http://www.broadcom.com/drivers/downloaddrivers.php Perhaps down-load the read-me and put in comments that clarify what really has te be done, with emphasis on Suse 10.0. I will have to figure out how to copy the files from XP, but I think I can work that. One of the problems I have with Linux is that I have never been able to keep a Linux system running until the next useful release--usually a year, or 1-1/2 years-- and so whatever I've learned, I forgot! And, of course, some of what I learned doesn't work anymore. The commands change, the directories change, and I guess the drivers that used to work must change. Even the icons (now that we have them) keep changing. I've never actually dealt with RPM's and had anything work, nor do I know what the "RPM path" might mean, etc. Every time I tried to do anything wih an RPM, I ran into dependency problems that wanted files that I had no idea where to find. Usually a long list of them! (Perhaps YOU fixes this, I don't know. If I ever get an internet connection I might find out.) I really would like to get Linux working as a real tool, rather than a toy, but it's difficult. I even tried to sign up for a couple of courses, but the local school wants to sell you a degree, not a couple of courses. I don't need a new degree at this point (age 68) all I need is a couple of courses! It would keep me off the streets, etc. (My son had a couple of courses in Unix/Linux, but since he doesn't work in computers, he's not really up on the stuff, altho he's more up on it than I am!) *********************************************************** Compltely off topic: You can buy an HP Laser printer, model 1020, for $124.95 from Buy.com. I just ordered one for the second machine, since I have so much trouble with networking. It runs on the USB bus, I hope that won't be a problem. If you take the slowest delivery, the shipping is free. Laser printing is so much cheaper than using a color printer it's almost a crime to run an ink-jet, if you don't need color. ********************************************************** --doug, wa2say -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.361 / Virus Database: 267.12.4/146 - Release Date: 10/21/2005
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. (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.
The tg3 module in 2.6 kernels supports the Broadcom NetXtreme Gigabit Ethernet and the b44 module supports some other (older) Broadcom chips. When I first installed SuSE 9.1 on my laptop, SuSE chose the b44 module instead and this led to network stalls, the tg3 module solved that. "lspci" will tell you what card you have, checking on google, ignore the RedHat 9/2.4 kernel as that's of no consequence (it's tg3.ko for 2.6)..... http://linux0.cs.uaf.edu/archive/msg00100.html says ...... ASUS P4PE works well with RedHat 9. The broadcomm built in ethernet (option) works with the tg3.o driver right out of the box. No special tweaking other than to tell RH9 to use the tg3 for the driver for eth0. ----------------------------------------------------------------------- This is so simple a problem, there is adequate support in the kernel, SuSE has the module built as standard, "lsmod" would tell you if it's the wrong module being loaded and if we have those 2 bits of information, plus the answer to the question as to whether there is a DHCP server on the network so the box can get a IP address, a solution could easily be found. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
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
participants (3)
-
Doug McGarrett
-
Peter Vollebregt
-
Sid Boyce