Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently posted about transplanting an old VM's hard drive onto a new PC. That thread is here.
Now that it's installed and booting, the problem has become more hardware-related. I need to get ethernet working, but it appears that the motherboard's bridge drivers are unknown on this old release of Debian.
Under a recent gentoo liveCD, lspci outputs the following:
Code:
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GT 220] (rev a2)
01:00.1 Audio device: nVidia Corporation Device 0be2 (rev a1)
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
Under Debian Sarge with a 2.4 kernel (which is unfortunately necessary), lspci reads:
The ethernet chip itself needs the tg3 driver, but I can't modprobe tg3... I get errors stating that there is "no such device." I suspect this is because so many controllers are unknown and probably driverless here. Can anyone shed some light on this?
Unfortunately, without an internet connection, it fails (and the goal here is to get ethernet working), but I was able to download the file from the SF page and put it on the machine from a USB drive.
So now lspci has the correct device names. I didn't realize that those were just held in a file somewhere, I thought the system had to actually recognize the devices. So, how do I actually get these things working (that is, why does modprobe fail)?
Thanks for the tip! Please let me know if you have other suggestions.
So it looks like that's basically a lookup table for the device codes. I thought that if that said "unknown," it meant the system couldn't even figure out what the device is supposed to be.
That makes this a little more difficult for me, because now I have no idea why the tg3 driver would fail to load. Also, I have another PCI ethernet card with a DP8381x chip, and that module fails to load in the same way.
One odd thing is that in the gentoo liveCD, the tg3 driver initially doesn't work. I have to rmmod tg3, then modprobe broadcom, then modprobe tg3 again. After that, the card works fine. I noticed that tg3 depends on the libphy module, also... Unfortunately, in Sarge with the 2.4 kernel, I can't find the broadcom module, nor can I find libphy. Even more unfortunately, the tg3 driver I downloaded straight from broadcom fails to compile, even though it says it should on kernel 2.4.
I downloaded the tg3 driver to get a look at the readme file,and i see there is an rpm version included.
You could use alien to convert the rpm to .deb file and try installing that way.
Quote:
One odd thing is that in the gentoo liveCD, the tg3 driver initially doesn't work. I have to rmmod tg3, then modprobe broadcom, then modprobe tg3 again.
I Googled the ethernet controller and found the following quote:
Quote:
Using tg3 driver in kernel, but have to load “broadcom” driver first, before loading the “tg3” driver
This is using a 2.6 kernel unfortunately.Not sure if this is relevant.
Here's the link where i found the info:
The errors were general compiler errors claiming that some variable does not exist in this scope.
I've given up on that at this point though. I found a pair of old 3Com cards that work perfectly with kernel 2.4.
Now I need to take everything I did to make 2.4.37 work and try it again on 2.4.27 (which isn't going well... what happened to the SATA PIIX drivers?).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.