USA Linux Users Group Forum Index
Log in Register FAQ Memberlist Search USA Linux Users Group Forum Index Album

Nic Not Detected

 
Post new topic   Reply to topic   printer-friendly view    USA Linux Users Group Forum Index » Networking
View previous topic :: View next topic  
Author Message
ghostdawg
Member


Joined: 27 Dec 2024
Posts: 130
Location: MO

PostPosted: Tue Mar 10, 2024 7:44 am    Post subject: Nic Not Detected Reply with quote

I have a D-Link DWL-520 Wireless PCI Adapter that I took out of another computer because the motherboard died. It was working before the motherboard died.

I took it out of the dead computer and put it in my current tower system. The current system had been directly connected to my router and DSL modem and I had installed madwifi drivers even though there was no wireless nic at the time.

Once I put the nic inside and modprobed ath_pci driver, and type ifconfig ath0 up, I get message no device detected. Also command lspci doesn't show the nic.

I can't understand why its not being detected. The nic light blinks also, so I'm not sure if it's bad or not. I don't have another system to test it on either.

Any ideas/suggestions?



_________________
Debian 64 - Sourcemage - Fedora 10
Back to top
View user's profile Send private message
lberg
Sr. Member


Joined: 28 Jul 2024
Posts: 1289

PostPosted: Tue Mar 10, 2024 2:38 pm    Post subject: Reply with quote

Do you have to manually modprobe the ath_pci driver? I thought that Atheros was a chipset with good Linux support, and would expect that the module would be automatically loaded for you.... Question

Did you check lspci & lsmod before you modprobed the driver also? Maybe that ath_pci module messes stuff up, idk.

Is there any helpful information in dmesg?

HTH...

Edit: After googling, it seems like there are different models of that card that have different chipsets. However, I think that the USA model does indeed have the Atheros chipset... You're sure that it does actually have an Atheros chipset, right? I kind of assumed that when I first wrote this post.



_________________
2 Computers: Arch Linux, 64-bit
3 Computers: Arch Linux, 32-bit
Back to top
View user's profile Send private message
platinummonkey
Advanced Member


Joined: 01 Mar 2024
Posts: 732
Location: Texas

PostPosted: Tue Mar 10, 2024 6:27 pm    Post subject: Reply with quote

ath_pci is being deprecated. try using ath5k instead. Don't know about your specific card though Razz



_________________
desktop - FreeBSD 7.2
laptop & server - Archlinux i686 kernel26 2.6.32.10-1
- TAMULinux-2.0.2-ALPHA
USB Boot - Archlinux i686 kernel26 2.6.32.10-1 USB boot
Back to top
View user's profile Send private message Visit poster's website AIM Address
Lord.DragonFly.of.Dawn
Advanced Member


Joined: 18 Jul 2024
Posts: 607
Location: South Portland, Maine, USA, Earth, Sol System

PostPosted: Wed Mar 11, 2024 8:47 pm    Post subject: Reply with quote

according to some google-fu, the D-Link DWL-520 Wireless PCI Adapter REQUIRES a PCI 2.2 slot that provides it's own IRQ. If either of these conditions is not met the card will not work.

My guess is that the mother board you put it in is either PCI 2.1 compliant or shares IRQs among it's PCI slots. Try moving the card to a different unoccupied slot to (possibly) clear up the problem in the second case. In the first case you need a new Mobo to get the card working.



_________________
ArchLinux x86_64 - Custom Built Desktop
ArchLinux x86_64 - Compaq CQ50 Laptop
ArchLinux i686 - Acer Aspire One Netbook
ArchLinux i686 - Dell Presario ze2000 (w/ shattered LCD)

PuppyLinux, CloneZilla, PartedMagic, DBAN - rescue thumbdrives
Windows 7 (x86_64 desktop alternate boot)
Back to top
View user's profile Send private message Visit poster's website
ghostdawg
Member


Joined: 27 Dec 2024
Posts: 130
Location: MO

PostPosted: Thu Mar 12, 2024 6:28 am    Post subject: Reply with quote

After moving the card into a different slot, everything is working. This is the correct driver, ath_pci and instead of using ifconfig ath0 up I had to type dhclient ath0, bammm, and she started working. Everything setup for it to run automagically when booting.

It seems when you put some pci devices in the first slot closest to the video card, problems appear with that device. I've seen this happen with different systems also.

Thanks for all your help.



_________________
Debian 64 - Sourcemage - Fedora 10
Back to top
View user's profile Send private message
mmmna
. . . .


Joined: 21 Apr 2024
Posts: 7224

PostPosted: Thu Mar 12, 2024 3:16 pm    Post subject: Reply with quote

ghostdawg wrote:
It seems when you put some pci devices in the first slot closest to the video card, problems appear with that device. I've seen this happen with different systems also.


Hmm. THAT problem has existed for a few years (where 2 slots nearest the I/O connectors have shared one IRQ); if there is something in one of those 2 slots, the other slot cannot be used. I have to wonder why this still happens - users have been griping about this quite a while. This link has a good example from March 2024.


Back to top
View user's profile Send private message
Lord.DragonFly.of.Dawn
Advanced Member


Joined: 18 Jul 2024
Posts: 607
Location: South Portland, Maine, USA, Earth, Sol System

PostPosted: Thu Mar 12, 2024 3:59 pm    Post subject: Reply with quote

I helped someone! YAY!

glad you got the problem solved.



_________________
ArchLinux x86_64 - Custom Built Desktop
ArchLinux x86_64 - Compaq CQ50 Laptop
ArchLinux i686 - Acer Aspire One Netbook
ArchLinux i686 - Dell Presario ze2000 (w/ shattered LCD)

PuppyLinux, CloneZilla, PartedMagic, DBAN - rescue thumbdrives
Windows 7 (x86_64 desktop alternate boot)
Back to top
View user's profile Send private message Visit poster's website
mmmna
. . . .


Joined: 21 Apr 2024
Posts: 7224

PostPosted: Thu Mar 12, 2024 8:17 pm    Post subject: Reply with quote

Lord.DragonFly.of.Dawn wrote:
I helped someone! YAY!

glad you got the problem solved.
lol!


Back to top
View user's profile Send private message
VHockey86
Advanced Member


Joined: 12 Dec 2024
Posts: 988
Location: Rochester

PostPosted: Thu Mar 12, 2024 8:20 pm    Post subject: Reply with quote

PCI? that's so 1990s! Very Happy



_________________
Main Desktops : Kubuntu 10.4. ArchLinux 64-bit. Windows7 64-bit. Windows XP 32-bit.

MacBook: OS X Snow Leopard (10.6)
Back to top
View user's profile Send private message
Lord.DragonFly.of.Dawn
Advanced Member


Joined: 18 Jul 2024
Posts: 607
Location: South Portland, Maine, USA, Earth, Sol System

PostPosted: Thu Mar 12, 2024 9:29 pm    Post subject: Reply with quote

mmmna wrote:
Lord.DragonFly.of.Dawn wrote:
I helped someone! YAY!

glad you got the problem solved.
lol!


I made someone laugh! YAY!

I was funny.

(sorry, couldn't resist the urge)



_________________
ArchLinux x86_64 - Custom Built Desktop
ArchLinux x86_64 - Compaq CQ50 Laptop
ArchLinux i686 - Acer Aspire One Netbook
ArchLinux i686 - Dell Presario ze2000 (w/ shattered LCD)

PuppyLinux, CloneZilla, PartedMagic, DBAN - rescue thumbdrives
Windows 7 (x86_64 desktop alternate boot)
Back to top
View user's profile Send private message Visit poster's website
ghostdawg
Member


Joined: 27 Dec 2024
Posts: 130
Location: MO

PostPosted: Fri Mar 13, 2024 8:20 am    Post subject: Reply with quote

mmmna, you would think by now that issue would be solved but it seems to still be an issue. I guess because they want to eliminate pci slots so they're not gonna fix it.

Now mind you while using this tower system, it didn't have the wireless nic at the beginning, so after getting the G3 iMac, I put the imac on my DSL modem and moved the tower into the bedroom and added the nic since. I knew something like this would happen so I installed the madwifi drivers during the installation of my three distros.

I had to fiddle around with Debian to get it working. When I booted up Fedora 10, it picked up the nic off the bat and asked did I want to use it, no fiddling around.

Now Sourcemage is another matter, for some reason awhile back, I couldn't get the madwifi drivers installed, so I may have to hook up a nic cable and try to get it working wirelessly.

To be continued...



_________________
Debian 64 - Sourcemage - Fedora 10
Back to top
View user's profile Send private message
mmmna
. . . .


Joined: 21 Apr 2024
Posts: 7224

PostPosted: Sat Mar 14, 2024 3:28 am    Post subject: Reply with quote

Quote:
added the nic since. I knew something like this would happen so I installed the madwifi drivers during the installation of my three distros.
...
When I booted up Fedora 10, it picked up the nic off the bat and asked did I want to use it, no fiddling around.

Wait ... what? Did you just say one of 3 distros worked in that system?



_________________
-Kubuntu 10.04 LTS Beta2 on Celeron D desktop
-PCLinuxOS 2024 LXDE on EeePC 900A with Atom n270 (modded with 32G SATA drive and 2G ram).
Back to top
View user's profile Send private message
ghostdawg
Member


Joined: 27 Dec 2024
Posts: 130
Location: MO

PostPosted: Tue Mar 17, 2024 8:03 am    Post subject: Reply with quote

The three distros installed on the tower I had to manually get debian working, even though the madwifi drivers were installed.

When I booted Fedora, everything was setup for madwifi already. It asked did I want to use it to access the internet, since no wired connection is available.

For sourcemage, I kept having issues installing madwifi and never got it installed. I'm still working on getting it to work.



_________________
Debian 64 - Sourcemage - Fedora 10
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    USA Linux Users Group Forum Index » Networking All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All content © 2024-2009 - Usa Linux Users Group
This forum is powered by phpBB. © 2024-2009 phpBB Group
Theme created by phpBBStyles.com and modified by Crouse