LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   help needed to detect onboard nvdia nic (https://www.linuxquestions.org/questions/linux-hardware-18/help-needed-to-detect-onboard-nvdia-nic-613202/)

jolondon 01-12-2008 09:44 PM

help needed to detect onboard nvdia nic
 
suse doesn't recognize my onboard nvdia nic's....what to do? do I install new drivers..if so I don't see support for suse 10.3 on amd 64?

http://www.nvnews.net/vbulletin/showthread.php?t=73925

lspci.....

00:00.0 RAM memory: nVidia Corporation Unknown device 0547 (rev a2)
00:01.0 ISA bridge: nVidia Corporation Unknown device 0548 (rev a2)
00:01.1 SMBus: nVidia Corporation Unknown device 0542 (rev a2)
00:01.2 RAM memory: nVidia Corporation Unknown device 0541 (rev a2)
00:01.3 Co-processor: nVidia Corporation Unknown device 0543 (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation Unknown device 0561 (rev a2)
00:09.0 IDE interface: nVidia Corporation Unknown device 0550 (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation Unknown device 054c (rev a2)
00:0c.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:0d.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation Unknown device 0531 (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
02:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
02:05.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
02:05.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
02:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
02:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
03:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)

PhenuxRizing 01-12-2008 10:07 PM

From the list you posted I see that you network controller is based on broadcom chipset. This brand has historically been a pain in the ass. I have a broadcom wifi card in my laptop and have always had problems with it. What worked for me is using ndiswrapper and the accompanying windows driver.

Just a little advice, in the future check with various hardware compatibility list for various projects such as madwifi(atheros based cards), or even intel based wireless cards. I also have another machine with an intel wifi card. The nice thing about the intel cards are that the drivers are open sourced and are natively supported by most, if not all linux distros. Good luck and I hope this info helps.

jolondon 01-12-2008 10:37 PM

actually I got the wireless card working with ndiswrapper because somebody wrote great instructions..it works flawlessly.

my problem is the nvdia nic....apparently it needs a driver called forcedeth.c I've just never compiled anything before and am confused about the instructions at http://www.nvnews.net/vbulletin/showthread.php?t=73925 and whether that loads the driver.

any ideas?

farslayer 01-12-2008 11:27 PM

I would probably also update your pci.ids file to possibly identify all those 'unknown device' entries..

Quote:

This is a public repository of all known ID's used in PCI devices, that is ID's of vendors, devices, subsystems and device classes. These ID lists (usually in form of a pci.ids file) are used in various programs (The Linux Kernel, The PCI Utilities, new version of the XFree86 etc.) to display full device names instead of the numeric ID's.
download an updated pci.ids file from http://pciids.sourceforge.net/ and put it in /usr/share/misc/

PhenuxRizing 01-13-2008 09:03 AM

Compiling is easier than it sounds. But first, ensure that you have the right compiler and libraries installed. When you go to the driver download page, there should be instructions on what you need tompile and how.

Most of the time compiling goes smoothly by just typing, "./configure; make;" and as root, "make install"

jolondon 01-13-2008 09:23 AM

thank you both..so can i still assign a driver even though the card isn't recognized?

where do i associate the driver with the device? network manager i assume..

PhenuxRizing 01-16-2008 01:13 PM

Assuming that the module (driver) you just compiled and installed is loaded into memory, if it still doesn't recognize it then there is problem with the driver. Either it is the wrong driver or a bug in the driver itself. In any case you would do modprobe (insert module name here) and hit enter.

Driver modules automatically detect a card as soon as it is inserted or immediately if it is onboard already. Double check the documentation to make sure that you have the correct driver and that your card is supported.

If by any chance you don't remember your wifi card's model. I always look at the manufacturer's website for product specs on the machine. For example I have a dell inspiron 5150. The Dell site tells me that is a trumobile card and the chipset is based on broadcom and some version. In the docs you want to make sure that your chipset is support. Sometimes they list the card by model number as opposed to chipset so make sure to get both items of information.

farslayer 01-16-2008 07:17 PM

so did you just decide to ignore the advice concerning updating your PCI device ID file (pci.ids) which would most likely solve your device identification problem ?

update-pciids


All times are GMT -5. The time now is 04:35 AM.