Why are you using eth0 for wireless? Try ath0. Edit: or wlan0.If you are using an old laptop with a cardbus card sometimes, using the following boot option will help:
pci=assign_busses
Also, I would suggest to add the following boot as well
nohdcp
To see if your wireless card is detected by not yet configured use
iwconfig
If it is detected you will see if it is a ath0, wlan0, or
I have heard of some cards that seem not work with pump but ok with static ip.
Quote (lucky13 @ July 13 2007,13:24)
Why are you using eth0 for wireless? Try ath0. Edit: or wlan0.
I have the same card, and it runs on eth0 (edit: only with the correct drivers, though). My netgear card, which I use for an 802.11a system, runs on ath0. I don't think you have a choice. (edit: on another system, I have to run it on eth1).I wasn't suggesting it's a choice, I was offering a shotgun approach to figure out which cards are detected and where they're detected. That's based on hardware configuration and how the kernel sees it (edit: i.e., as reported in iwconfig). For most wireless cards, in my experience it's athX or wlanX.No luck.
I have added the nodhcp and the pci=assign_busses to the grub boot option for dsl.
Hopefully that will tell you something else, maybe an idea of something else to try. Maybe that static thing you mentioned Roberts?Next Page...
original here.
