In preparing for installation of a driver for the Network Controller of my
Vostro 1510, I am having difficulty in locating the PCI ID for the
controller.
The controller is detected in Network Settings as:
On Thursday 08 October 2009 02:59:21 am Stan Goodman wrote:
In preparing for installation of a driver for the Network Controller of my Vostro 1510, I am having difficulty in locating the PCI ID for the controller.
The controller is detected in Network Settings as:
. Searching the Hardware List for likely terms, I find only one paragraph about "Network Controller", which in fact does not describe the NIC at all, but details the Wireless Card -- it gives the PCI ID as 14e4:4315, which I know for a fact is the WiFi card. It can't be that the NIC is not described in the Haardware List. I have not been able to find where it is lurking.
I don't know if this will help, but 'lspci -vv' might disclose more details. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 03:31:36 on Friday Friday 09 October 2009, "David C. Rankin"
On Thursday 08 October 2009 02:59:21 am Stan Goodman wrote:
In preparing for installation of a driver for the Network Controller of my Vostro 1510, I am having difficulty in locating the PCI ID for the controller.
The controller is detected in Network Settings as:
. Searching the Hardware List for likely terms, I find only one paragraph about "Network Controller", which in fact does not describe the NIC at all, but details the Wireless Card -- it gives the PCI ID as 14e4:4315, which I know for a fact is the WiFi card. It can't be that the NIC is not described in the Haardware List. I have not been able to find where it is lurking.
I don't know if this will help, but 'lspci -vv' might disclose more details.
I've done so. It's quite long, but if you want me to send it, I will. It contains no mention of an Ethernet card, or the numbers 8168 oe 8169 -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
At 03:31:36 on Friday Friday 09 October 2009, "David C. Rankin"
wrote: I don't know if this will help, but 'lspci -vv' might disclose more details.
I've done so. It's quite long, but if you want me to send it, I will.
It contains no mention of an Ethernet card, or the numbers 8168 oe 8169
Then you need to start by actually plugging in the NIC :-) If there is network controller in your PC and it's not listed by lspci, your problem is not in the driver. Perhaps start with just the output of 'lspci' - that ought to be no more than 10 lines or so. /Per -- Per Jessen, Zürich (15.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 10:17:20 on Friday Friday 09 October 2009, Per Jessen
Stan Goodman wrote:
At 03:31:36 on Friday Friday 09 October 2009, "David C. Rankin"
wrote: I don't know if this will help, but 'lspci -vv' might disclose more details.
I've done so. It's quite long, but if you want me to send it, I will.
It contains no mention of an Ethernet card, or the numbers 8168 oe 8169
Then you need to start by actually plugging in the NIC :-) If there is network controller in your PC and it's not listed by lspci, your problem is not in the driver.
There is some confusing nomenclature in hwinfo, as I have mentioned: The list DOES list a Network Controller, but that turns out to be the wireless card. In the initial run of hwinfo (yesterday), the RTL device is called the Ethernet Controller. It was in yestereday's run of hwinfo, but not in todays. Last evening I mentioned the sudden appearance of the "No hwinfo" in the description of the card in Network Settings.
Perhaps start with just the output of 'lspci' - that ought to be no more than 10 lines or so.
Here is the output of lspci, a bit longer than ten lines: # lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) 0f:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) 0f:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01) 0f:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01) # Here too, as you can see in the fourth line from the bottom, "Network Controller" means "wireless card". The Ethernet Controller (which I, and aparently everone else, would call "Network Controller" appears nowhere. In another message in this thread I pointed out that the Ether I agree that this seems to have become a hardware problem. As the machine is newly bought, I think it would be better to wait for after the weekend and Sunday (which happens to be a holiday), and let the vendor's technician check the card.
/Per
-- Per Jessen, Zürich (15.4°C)
-- Stan Goodman (31C) Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2009-10-09 at 11:42 +0200, Stan Goodman wrote:
-- Stan Goodman (31C) Qiryat Tiv'on Israel --
Hi Stan, I just had a thought about compiling your kernel module and driver that nobody has touched upon since I started to pay attention to this thread. If you have already eliminated this, I apologize for the duplication. In the readout in terminal when you compiled your module and driver, were there any errors noted? I found there were several programs that I had to install to let me compile the driver properly. I installed: kernel source make automake autoconf gcc gcc-c++ Only then I was able to build the driver per the readme file instructions without errors. You probably know more about what is actually required than I do, but I am trying to cover all the prerequisites to get the job done. Is it possible that your module and driver were never properly compiled? I hope this helps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan Goodman wrote:
Then you need to start by actually plugging in the NIC :-) If there is network controller in your PC and it's not listed by lspci, your problem is not in the driver.
[snip]
Perhaps start with just the output of 'lspci' - that ought to be no more than 10 lines or so.
Here is the output of lspci, a bit longer than ten lines:
Well, yeah - these modern machines have lots of stuff ... :-)
# lspci 0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Okay, that's your wireless NIC.
Here too, as you can see in the fourth line from the bottom, "Network Controller" means "wireless card". The Ethernet Controller (which I, and aparently everone else, would call "Network Controller" appears nowhere.
Which is a really strong indication that it isn't actually present or properly connected/plugged into your system. Until the PCI* bus can talk to the device, there's nothing else anyone can do. I was going to suggest wiggling the card, make sure it really is seated properly, but then I realized your 'Vostro 1510' is a laptop ... Is there any possibility that the on-board NIC has been disabled (somehow)? Does the laptop (somehow) switch between the two NICs itself? /Per -- Per Jessen, Zürich (16.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 12:26:46 on Friday Friday 09 October 2009, Per Jessen
Stan Goodman wrote:
Then you need to start by actually plugging in the NIC :-) If there is network controller in your PC and it's not listed by lspci, your problem is not in the driver.
[snip]
Perhaps start with just the output of 'lspci' - that ought to be no more than 10 lines or so.
Here is the output of lspci, a bit longer than ten lines:
Well, yeah - these modern machines have lots of stuff ... :-)
# lspci 0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
Okay, that's your wireless NIC.
Here too, as you can see in the fourth line from the bottom, "Network Controller" means "wireless card". The Ethernet Controller (which I, and aparently everone else, would call "Network Controller" appears nowhere.
Which is a really strong indication that it isn't actually present or properly connected/plugged into your system. Until the PCI* bus
Or that there has been a malfunction -- in earlier runs of hwinfo, it was present.
talk to the device, there's nothing else anyone can do. I was going to suggest wiggling the card, make sure it really is seated properly, but then I realized your 'Vostro 1510' is a laptop ...
I am not sure if the Ethernet card is a seperate plugged-in minicard or whether it is acually on the motherboard. If the former, that will be fixed easily next week. Else the machine is a week old, and well within warranty.
Is there any possibility that the on-board NIC has been disabled (somehow)? Does the laptop (somehow) switch between the two NICs itself?
Since neither of them work, I don't see how I would know that. (We are trying to acquire an alternate wireless card (4318), with better support under the BCM43 driver.)
/Per
-- Per Jessen, Zürich (16.6°C)
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 10:17:20 on Friday Friday 09 October 2009, Per Jessen
Stan Goodman wrote:
At 03:31:36 on Friday Friday 09 October 2009, "David C. Rankin"
wrote: I don't know if this will help, but 'lspci -vv' might disclose more details.
I've done so. It's quite long, but if you want me to send it, I will.
It contains no mention of an Ethernet card, or the numbers 8168 oe 8169
Then you need to start by actually plugging in the NIC :-) If there is network controller in your PC and it's not listed by lspci, your problem is not in the driver.
Perhaps start with just the output of 'lspci' - that ought to be no more than 10 lines or so.
There are a couple of other oddities: 1) The two hwinfo reports (yesterday and today) have very different length, for both the overall reports and the specific paragraph about the Ethernet card. Here is yesterday's version; note that it is #96 in a very long list: 96: udi = '/org/freedesktop/Hal/devices/pci_10ec_8168' pci.subsys_vendor_id = 4136 (0x1028) info.subsystem = 'pci' pci.device_class = 2 (0x2) info.product = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' pci.device_subclass = 0 (0x0) info.udi = '/org/freedesktop/Hal/devices/pci_10ec_8168' pci.device_protocol = 0 (0x0) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.5/0000:09:00.0' pci.vendor = 'Realtek Semiconductor Co., Ltd.' info.parent = '/org/freedesktop/Hal/devices/pci_8086_294a' info.vendor = 'Realtek Semiconductor Co., Ltd.' pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.5/0000:09:00.0' pci.product = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' info.linux.driver = 'r8169' pci.subsys_vendor = 'Dell' pci.product_id = 33128 (0x8168) linux.hotplug_type = 2 (0x2) pci.vendor_id = 4332 (0x10ec) linux.subsystem = 'pci' pci.subsys_product_id = 1026 (0x402) Here is today's, the last paragraph of only 72: 72: None 00.0: 10701 Ethernet [Created at net.124] Unique ID: fLK9.ndpeucax6V1 SysFS ID: /class/net/pan0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "bridge" Device File: pan0 HW Address: 22:84:97:19:2f:1a Link detected: yes Config Status: cfg=no, avail=yes, need=no, active=unknown How could the hardware list have become that much shorter? 2) When I booted the notebook machine yesterday, it booted to Level 1 for some reason, although I had not set this in the herald screen. There was a remark at the bottom of the log, just before the login: Master Resource Control: run level 5 has been skipped services in run level 5: (sic! that's the exact sentence -- SG) Rebooting three times eventually got it to boot to level 5. Subsequent shutdowns and boots proceeded normally, directly to level 5. The same thing happened this morning, and again got to level 5 after three additional tries. So the machine is becoming flaky. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 October 2009 02:51:19 am Stan Goodman wrote:
At 03:31:36 on Friday Friday 09 October 2009, "David C. Rankin"
wrote: On Thursday 08 October 2009 02:59:21 am Stan Goodman wrote:
In preparing for installation of a driver for the Network Controller of my Vostro 1510, I am having difficulty in locating the PCI ID for the controller.
The controller is detected in Network Settings as:
. Searching the Hardware List for likely terms, I find only one paragraph about "Network Controller", which in fact does not describe the NIC at all, but details the Wireless Card -- it gives the PCI ID as 14e4:4315, which I know for a fact is the WiFi card. It can't be that the NIC is not described in the Haardware List. I have not been able to find where it is lurking.
I don't know if this will help, but 'lspci -vv' might disclose more details.
I've done so. It's quite long, but if you want me to send it, I will.
It contains no mention of an Ethernet card, or the numbers 8168 oe 8169
Stan, Your not going to believe this. I don't believe this. But... some cards try to show up as USB devices. Just because it isn't impossible that little green men might fall from the sky... try and lsusb just for insanity's sake... No, I don't know why and don't have a link, but I recall shaking my head when I read this somewhere. It's either that, of you have the pci slot turned off in the bios or the card is just freaking DEAD :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin
-
Mark Misulich
-
Per Jessen
-
Stan Goodman