|
shahgols
|
 |
« on: November 17, 2008, 02:48:32 pm » |
|
Hi all,
I just installed VL 5.9 standard on my PC at work. The PC is a Dell Optiplex 755. Anyways, during installation VL gave the following message:
"Modem Unknown vendor|unknown device 8086:29B7 is detected, but cannot be configured."
I am unable to access the internet at the moment. Any help would be greatly appreciated.
|
|
|
|
|
Logged
|
|
|
|
|
M0E-lnx
|
 |
« Reply #1 on: November 17, 2008, 02:51:37 pm » |
|
I guess it wouldn't hurt to ask... Have you had VL installed on this machine before? Do you know the make/model of your NIC Card?
In case you do, you just need to find out which module makes it tick.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
newt
|
 |
« Reply #3 on: November 17, 2008, 03:02:30 pm » |
|
Please post the output from 'lspci', and 'ifconfig -a'. Your ethernet device should show in the lspci.
On a quick search for device 8086:29B7 it looks to be (PERHAPS) an intel serial controller. It may be totally unrelated to your ethernet controller.
edit: looks like your network card uses the e1000 module. Perhaps the output from 'lsmod' would be useful as well.
|
|
|
|
« Last Edit: November 17, 2008, 03:06:44 pm by newtor »
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #4 on: November 17, 2008, 03:21:58 pm » |
|
Hi there Newtor, I think that you are right. I came across this download from intel, which I think is the right driver for my card, right? http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProductID=2196&DwnldID=15817&strOSs=39&OSFullName=Linux*&lang=engHere are the outputs that you asked for: lspci root:# lspci 00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation PCI Express Root Port (rev 02) 00:03.0 Communication controller: Intel Corporation MEI Controller (rev 02) 00:03.2 IDE interface: Intel Corporation PT IDER Controller (rev 02) 00:03.3 Serial controller: Intel Corporation Serial KT Controller (rev 02) 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) 00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 02) 00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation PCI Express Port 1 (rev 02) 00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 4 port SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 2 port SATA IDE Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 94c3 ifconfig root:# ifconfig -a lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lsmod root:# lsmod Module Size Used by acpi_cpufreq 7880 0 freq_table 4768 1 acpi_cpufreq snd_seq_dummy 3716 0 snd_seq_oss 32128 0 snd_seq_midi_event 7168 1 snd_seq_oss snd_seq 48720 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 7692 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 38048 0 snd_mixer_oss 15232 1 snd_pcm_oss snd_hda_intel 283040 2 snd_pcm 69764 2 snd_pcm_oss,snd_hda_intel snd_timer 19972 2 snd_seq,snd_pcm snd_page_alloc 8712 2 snd_hda_intel,snd_pcm snd_hwdep 7812 1 snd_hda_intel snd 45796 14 snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep fglrx 1471788 22 i2c_i801 8592 0 i2c_core 20992 1 i2c_i801 soundcore 7008 1 snd serio_raw 6276 0 shpchp 30228 0 pci_hotplug 28616 1 shpchp intel_agp 22164 0 agpgart 28108 2 fglrx,intel_agp evdev 8704 4
|
|
|
|
|
Logged
|
|
|
|
|
newt
|
 |
« Reply #5 on: November 17, 2008, 03:33:36 pm » |
|
It's not all that common that you need to find external drivers for network cards with Vectorlinux - at least that's been my experience so far.
Your ethernet controller shows up correctly in lspci: "00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)", but the modules don't seem to be loaded based on your lsmod. I believe that the correct module for your gigabit ethernet controller is the e1000, so I would start with a (as root) 'modprobe e1000'. Then check 'ifconfig -a' and 'lsmod' again to see if your eth0 device shows up and the e1000 module gets listed. If they do, then the last steps would be to just configure the card via VASMCC for your network.
|
|
|
|
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #6 on: November 17, 2008, 03:44:30 pm » |
|
For me, VL has been able to find hardware that others have not found, including Ubuntu and openSUSE. This is the first time that it's been the other way around. Oh well, win some, loose some.  I ran "modprobe e1000" and after that ifconfig -a and lsmod are the same. No ethx shows up. I have found the following driver for e1000 from sourceforge: http://sourceforge.net/projects/e1000I'll try to install it. Am not that good at this stuff, so I may be back asking for help. Hope that this works though.
|
|
|
|
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #7 on: November 17, 2008, 04:01:46 pm » |
|
OK, no cigar. Here is the instructions for installing that driver: 1. Move the base driver tar file to the directory of your choice. For example, use /home/username/e1000e or /usr/local/src/e1000e.
2. Untar/unzip archive:
tar zxf e1000e-x.x.x.tar.gz
3. Change to the driver src directory:
cd e1000e-x.x.x/src/
4. Compile the driver module:
make install
The binary will be installed as:
/lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.[k]o
The install locations listed above are the default locations. They might not be correct for certain Linux distributions.
5. Load the module using either the insmod or modprobe command:
modprobe e1000e
insmod e1000e
Note that for 2.6 kernels the insmod command can be used if the full path to the driver module is specified. For example:
insmod /lib/modules/<KERNEL VERSION>/kernel/drivers/net/e1000e/e1000e.ko
With 2.6 based kernels also make sure that older e1000e drivers are removed from the kernel, before loading the new module:
rmmod e1000e; modprobe e1000e
6. Assign an IP address to the interface by entering the following, where x is the interface number:
ifconfig ethx <IP_address>
7. Verify that the interface works. Enter the following, where <IP_address> is the IP address for another machine on the same subnet as the interface that is being tested:
ping <IP_address> When I run make install, I get the following error: make: *** no rule to make target 'install': Stop. Also, any idea why "modprobe e1000" did not work?
|
|
|
|
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #8 on: November 17, 2008, 04:21:20 pm » |
|
BTW, here's the contents of /proc/modules. root:# cat /proc/modules e1000 118976 0 - Live 0xf9a73000 acpi_cpufreq 7880 0 - Live 0xf9a2c000 freq_table 4768 1 acpi_cpufreq, Live 0xf9a2f000 snd_seq_dummy 3716 0 - Live 0xf8cfe000 snd_seq_oss 32128 0 - Live 0xf9a6a000 snd_seq_midi_event 7168 1 snd_seq_oss, Live 0xf9a29000 snd_seq 48720 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event, Live 0xf9a5d000 snd_seq_device 7692 3 snd_seq_dummy,snd_seq_oss,snd_seq, Live 0xf9a0d000 snd_pcm_oss 38048 0 - Live 0xf9a52000 snd_mixer_oss 15232 1 snd_pcm_oss, Live 0xf973f000 snd_hda_intel 283040 2 - Live 0xf9aad000 snd_pcm 69764 2 snd_pcm_oss,snd_hda_intel, Live 0xf9a3f000 snd_timer 19972 2 snd_seq,snd_pcm, Live 0xf9a15000 snd_page_alloc 8712 2 snd_hda_intel,snd_pcm, Live 0xf9732000 snd_hwdep 7812 1 snd_hda_intel, Live 0xf972f000 snd 45796 14 snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep, Live 0xf9a1c000 intel_agp 22164 0 - Live 0xf9738000 fglrx 1471788 22 - Live 0xf9bbd000 (P) i2c_i801 8592 0 - Live 0xf972b000 agpgart 28108 2 intel_agp,fglrx, Live 0xf970b000 i2c_core 20992 1 i2c_i801, Live 0xf9724000 serio_raw 6276 0 - Live 0xf9708000 shpchp 30228 0 - Live 0xf971b000 pci_hotplug 28616 1 shpchp, Live 0xf9713000 soundcore 7008 1 snd, Live 0xf9705000 evdev 8704 4 - Live 0xf9701000 I have no idea what to do now. Am stuck like a duck.
|
|
|
|
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #9 on: November 17, 2008, 04:30:25 pm » |
|
Messages in /var/log/messages and dmesg respectively: Nov 17 16:02:35 skhorram kernel: Intel(R) PRO/1000 Network Driver - version 7.3.20-k2 Nov 17 16:02:35 skhorram kernel: Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2 Copyright (c) 1999-2006 Intel Corporation.
|
|
|
|
|
Logged
|
|
|
|
|
bigpaws
|
 |
« Reply #10 on: November 17, 2008, 05:27:19 pm » |
|
I ran "modprobe e1000" and after that ifconfig -a and lsmod are the same. If you did not bring up the NIC then you will not see it. To do this first use modprobe e1000 Then use ifconfig eth0 up If the NIC is up you can use VASM or netconfig to setup the card. Then try ifconfig -a to see if the interface is up. If it is then edit /etc/rc.d/rc.local and at the bottom add modprobe e1000 If the NIC does come up but no address then try adding below the modprobe command dhcpcd eth0 I have noticed several posts about that card not being seen during install. HTH Bigpaws
|
|
|
|
|
Logged
|
|
|
|
|
shahgols
|
 |
« Reply #11 on: November 17, 2008, 05:42:34 pm » |
|
Thanks bigpaws. When I run ifconfig eth0 up, it says that no such device exists. No worries, looks like I have to get me a NIC card today. 
|
|
|
|
|
Logged
|
|
|
|
|
bigpaws
|
 |
« Reply #12 on: November 17, 2008, 06:37:15 pm » |
|
|
|
|
|
|
Logged
|
|
|
|
toothandnail
Tester
Vectorian
   
Posts: 2527
|
 |
« Reply #13 on: November 18, 2008, 01:35:53 am » |
|
I hit a similar problem on an HP machine with the same Intel chipset. To get the NIC to load on it, I had to modprobe mii as well as e1000. Still don't know why, but that might be worth a try (though I notice that the mii module does not seem to exist in the VL 6.0 kernel, it is available in the 5.9 kernel modules).
paul.
|
|
|
|
|
Logged
|
|
|
|
|