1 |
Marcus Wanner wrote: |
2 |
> On 10/28/2009 5:39 PM, Dale wrote: |
3 |
>> Marcus Wanner wrote: |
4 |
>> |
5 |
>>> On 10/28/2009 04:01 AM, Dale wrote: |
6 |
>>> |
7 |
>>>> Mick wrote: |
8 |
>>>> |
9 |
>>>> |
10 |
>>>>> To read your PCI connected devices you need: |
11 |
>>>>> |
12 |
>>>>> lspci -v |
13 |
>>>>> |
14 |
>>>>> HTH. |
15 |
>>>>> |
16 |
>>>> That is the key command in my opinion. That will tell you what driver |
17 |
>>>> it is using for what device. If it works while booted on the Live CD, |
18 |
>>>> then that driver is most likely what you need. Take the name of the |
19 |
>>>> driver, then search for it in menuconfig. You hit the "/" key to |
20 |
>>>> search. Its like the ? key without hitting shift. It should show you |
21 |
>>>> exactly where the driver is located so you can go enable it. Then you |
22 |
>>>> just recompile the kernel and copy it to /boot. |
23 |
>>>> |
24 |
>>>> This is what the output should look like: |
25 |
>>>> |
26 |
>>>> 01:08.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet |
27 |
>>>> 100/10 |
28 |
>>>> MBit (rev 31) |
29 |
>>>> Subsystem: ARCHTEK TELECOM Corp Device 0008 |
30 |
>>>> Flags: bus master, medium devsel, latency 32, IRQ 16 |
31 |
>>>> I/O ports at 9800 [size=256] |
32 |
>>>> Memory at df002000 (32-bit, non-prefetchable) [size=256] |
33 |
>>>> [virtual] Expansion ROM at 88100000 [disabled] [size=256K] |
34 |
>>>> Capabilities: [50] Power Management version 1 |
35 |
>>>> Kernel driver in use: dmfe |
36 |
>>>> |
37 |
>>>> |
38 |
>>>> The last line is the key. If I were searching for that driver, I |
39 |
>>>> would |
40 |
>>>> search for dmfe and enable it as built in or a module. |
41 |
>>>> |
42 |
>>>> If that command doesn't show the driver, then you may need to start |
43 |
>>>> with |
44 |
>>>> some of the other commands to see what you can test to get it working. |
45 |
>>>> |
46 |
>>>> Dale |
47 |
>>>> |
48 |
>>>> :-) :-) |
49 |
>>> I booted up the livecd and ran lspci -v, it worked great. I got |
50 |
>>> similar output to that above, and found out that I am using a "3Com |
51 |
>>> Corporation 3c905C-TX/TX-M [Tornado] (rev 78)" and that "Kernel driver |
52 |
>>> in use: 3c59x". Great! Only problem was that when I went to look for |
53 |
>>> that driver in menuconfig, all I found were two other drivers for |
54 |
>>> similar cards (one of which had "[Typhoon]" in the name). |
55 |
>>> |
56 |
>>> However, I enabled those drivers, recompiled, rebooted, and everything |
57 |
>>> works great. Thanks for all your help. |
58 |
>>> |
59 |
>>> By the way, I have never had such great technical support before. I am |
60 |
>>> really amazed that within 12 hours, I had about 3 different ways of |
61 |
>>> fixing this, and was able to have it up and running within 45 minutes |
62 |
>>> of checking my email this morning. Wonderful! |
63 |
>>> |
64 |
>>> Marcus |
65 |
>>> |
66 |
>>> |
67 |
>>> |
68 |
>> |
69 |
>> Now I'm confused. I did a search here as well and it returned nothing |
70 |
>> matching that driver. This is a first for me. Has anyone else ever |
71 |
>> searched for a driver when you have the exact name and not get a match |
72 |
>> when the driver is actually there? I did a manual search and the driver |
73 |
>> is there. |
74 |
>> Glad you got the network working tho. |
75 |
>> Dale |
76 |
>> |
77 |
>> :-) :-) |
78 |
> Yeah, I guess it's because you have to download that particular driver |
79 |
> separately? |
80 |
> |
81 |
> Marcus |
82 |
> |
83 |
> |
84 |
|
85 |
It's in the kernel tho. This appears to be the one: |
86 |
|
87 |
3c590/3c900 series (592/595/597) "Vortex/Boomerang" support |
88 |
|
89 |
The help screen lists your card. Just weird to me. |
90 |
|
91 |
Dale |
92 |
|
93 |
:-) :-) |