| 1 |
On 10/28/2009 5:39 PM, Dale wrote: |
| 2 |
> Marcus Wanner wrote: |
| 3 |
> |
| 4 |
>> On 10/28/2009 04:01 AM, Dale wrote: |
| 5 |
>> |
| 6 |
>>> Mick wrote: |
| 7 |
>>> |
| 8 |
>>> |
| 9 |
>>>> To read your PCI connected devices you need: |
| 10 |
>>>> |
| 11 |
>>>> lspci -v |
| 12 |
>>>> |
| 13 |
>>>> HTH. |
| 14 |
>>>> |
| 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 100/10 |
| 27 |
>>> MBit (rev 31) |
| 28 |
>>> Subsystem: ARCHTEK TELECOM Corp Device 0008 |
| 29 |
>>> Flags: bus master, medium devsel, latency 32, IRQ 16 |
| 30 |
>>> I/O ports at 9800 [size=256] |
| 31 |
>>> Memory at df002000 (32-bit, non-prefetchable) [size=256] |
| 32 |
>>> [virtual] Expansion ROM at 88100000 [disabled] [size=256K] |
| 33 |
>>> Capabilities: [50] Power Management version 1 |
| 34 |
>>> Kernel driver in use: dmfe |
| 35 |
>>> |
| 36 |
>>> |
| 37 |
>>> The last line is the key. If I were searching for that driver, I would |
| 38 |
>>> search for dmfe and enable it as built in or a module. |
| 39 |
>>> |
| 40 |
>>> If that command doesn't show the driver, then you may need to start with |
| 41 |
>>> some of the other commands to see what you can test to get it working. |
| 42 |
>>> |
| 43 |
>>> Dale |
| 44 |
>>> |
| 45 |
>>> :-) :-) |
| 46 |
>>> |
| 47 |
>> I booted up the livecd and ran lspci -v, it worked great. I got |
| 48 |
>> similar output to that above, and found out that I am using a "3Com |
| 49 |
>> Corporation 3c905C-TX/TX-M [Tornado] (rev 78)" and that "Kernel driver |
| 50 |
>> in use: 3c59x". Great! Only problem was that when I went to look for |
| 51 |
>> that driver in menuconfig, all I found were two other drivers for |
| 52 |
>> similar cards (one of which had "[Typhoon]" in the name). |
| 53 |
>> |
| 54 |
>> However, I enabled those drivers, recompiled, rebooted, and everything |
| 55 |
>> works great. Thanks for all your help. |
| 56 |
>> |
| 57 |
>> By the way, I have never had such great technical support before. I am |
| 58 |
>> really amazed that within 12 hours, I had about 3 different ways of |
| 59 |
>> fixing this, and was able to have it up and running within 45 minutes |
| 60 |
>> of checking my email this morning. Wonderful! |
| 61 |
>> |
| 62 |
>> Marcus |
| 63 |
>> |
| 64 |
>> |
| 65 |
>> |
| 66 |
> |
| 67 |
> Now I'm confused. I did a search here as well and it returned nothing |
| 68 |
> matching that driver. This is a first for me. Has anyone else ever |
| 69 |
> searched for a driver when you have the exact name and not get a match |
| 70 |
> when the driver is actually there? I did a manual search and the driver |
| 71 |
> is there. |
| 72 |
> |
| 73 |
> Glad you got the network working tho. |
| 74 |
> |
| 75 |
> Dale |
| 76 |
> |
| 77 |
> :-) :-) |
| 78 |
> |
| 79 |
Yeah, I guess it's because you have to download that particular driver |
| 80 |
separately? |
| 81 |
|
| 82 |
Marcus |
Archives