Re: [Madwifi-users] HAL status 3 with Dlink DWL-G520

[Pavel R. <pr...@gn...>]

Quoting Lorenzo Milesi <lor...@gm...>:

> > That's too little information.  You didn't supply the URL and the exact
> command.
> >  It would be helpful to explain why you decided to use setpci.
>
> I found only this link
>
http://madwifi.org/wiki/UserDocs/Troubleshooting#WhenIloadtheath_pcimoduleIgetunabletoattachhardware:HardwaredidntrespondasexpectedHALstatus3
> about "Hal status 3".

But you still are now showing the command.  What did you set the subordinate bus
to?  Which PCI device did you use?  I have a suspicion that you actually
reprogrammed the AGP bridge, because it's the only PCI bridge shown by "lspci"
on your system (well, after you did something with setpci).

> > This "rev ff" looks very suspicious.  Maybe the card is not inserted fully,
> or
> > maybe you misconfigured the PCI bridge using setpci incorrectly.
>
> Yeah it looked strange to me too. In fact it changed after I played
> with setpci.

Then maybe it's better to show the original state?

> > You didn't specify the kernel version, but considering that it's Debian,
> the
> > kernel may be quite old.  Newer kernels may have better support for your
> PCI
> > bridge.
>
> Yes sorry, kernel is 2.6.8 from Debian Sarge.

Yes, it's quite old.  It's not so hard to try a newer kernel and then return to
whatever you are using.  Even if the probability of fixing things is just 20%,
it may be worth it.

> So you think maybe it's the pci bridge?

I don't think so.  The card is sitting on the bus 0, right under the host
bridge.

> I have a PCI ethernet card connected and working perfectly. Does this matter?

Try swapping the cards.  I've seen motherboards with bad slots.

You may also want to test the card in another system.  That would give you an
idea whether the card is to blame.

--
Regards,
Pavel Roskin