phunni Posted November 4, 2006 Report Share Posted November 4, 2006 I have a card which uses an atheros chipset. I've been using a driver which I downloaded ages ago and has worked flawlessly for a while. I recently did a pacman -Syu which included a kernel upgrade and an ndiswrapper update. My kernel is currently 2.6.18.1-1 and my ndiswrapper is 1.26-1 Since the upgrade my networking has failed - the card no longer seems to work at all. This isn't all that surprising since ndiswrapper -l lists the driver as follows: ndiswrapper invalid driver!net5211 driver installed I'm at a loss to understand how to move forward when I know I have a perfectly valid .inf file - but I'm getting nothing out of the card at all... Any ideas? Quote Link to comment Share on other sites More sharing options...
nchancock Posted November 4, 2006 Report Share Posted November 4, 2006 You've probably already tried this, but try removing and reinstalling the driver. I remember once when I upgraded ndiswrapper, I had to to that to get it to auto-configure itself correctly :) Hope that helps. Quote Link to comment Share on other sites More sharing options...
jaraeez Posted November 4, 2006 Report Share Posted November 4, 2006 I also remember having a similar issue on some distro & finally established that on that particular distro I also needed the .bin file which was also included in the windoze driver set. Once I put the .bin, .inf, & .sys all in one folder it worked... HTH Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 4, 2006 Report Share Posted November 4, 2006 It shouldn't be too difficult to resolve- but did you follow THAT thread anytime? Quote Link to comment Share on other sites More sharing options...
tyme Posted November 6, 2006 Report Share Posted November 6, 2006 It shouldn't be too difficult to resolve- but did you follow THAT thread anytime?I think you messed up the link, there...I don't think becoming a trusted user would help phunni ;) I would suggest following the setup instructions here to do a reinstall/reconfiguration. It may be that with the new kernel and new version of ndiswrapper some configuration data may have changed...reinstalling may correct it. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 6, 2006 Report Share Posted November 6, 2006 I had the same problem ages ago in arch after an upgrade. I could never get it working again, and thus removed arch. Don't get me wrong, I like arch, I was just impatient and couldn't find a solution ;) Quote Link to comment Share on other sites More sharing options...
phunni Posted November 6, 2006 Author Report Share Posted November 6, 2006 I have tried doing a reinstall and reconfiguration - no joy. One of the first things I tried was simply downgrade both the kernel and ndiswrapper assuming that previous version would work as they had done before - but not... I guess I could try and hunt down a differnet .inf file and see if I can get any joy that way - it#s just a pain in the arse since I have to download on my laptop and then transfer it to the Desktop - sometimes I wish I still had a floppy drive! Quote Link to comment Share on other sites More sharing options...
tyme Posted November 6, 2006 Report Share Posted November 6, 2006 I'd suggesting posting to the arch forums. Maybe this is a bug...and maybe they should know about it ;) Quote Link to comment Share on other sites More sharing options...
phunni Posted November 6, 2006 Author Report Share Posted November 6, 2006 I that - a while ago. Had no responses except one person telling they had a similar issue - so I brought it here... Here, I've already had many more responses - even if they're mostly telling me to do things I've tried. Which none of you knew since I didn't tell you - so I massively appreciate the help! Quote Link to comment Share on other sites More sharing options...
tyme Posted November 6, 2006 Report Share Posted November 6, 2006 strange that you haven't gotten any help on the arch board :unsure: guess it happens sometimes. Quote Link to comment Share on other sites More sharing options...
phunni Posted November 20, 2006 Author Report Share Posted November 20, 2006 I fixed in the following way: 1) Downgraded ndiswrapper. This got rid of the invalid driver message, but when doing "lspci" I saw no mention of the card... 2) So I moved it to a different pci slot All fixed now (currently doing a MASSIVE update - which I'm nervous will break everything...), but I'm wondering whether I can upgrade ndiswrapepr again... Is it possible that the pci failure came as a result of the upgrade? Quote Link to comment Share on other sites More sharing options...
tyme Posted November 20, 2006 Report Share Posted November 20, 2006 Doubt it...the only way I've seen a pci slot fail was by being shocked (static electriciy). I've never heard of software/driver killing a pci slot. The card, maybe, but the slot? I don't think so... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.