Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Network device issue

  • 16-05-2005 11:43am
    #1
    Closed Accounts Posts: 999 ✭✭✭


    I'm having problems with my wireless card, it can't seem to recognise the network. I think I may have broken the driver :o
    I had it running fine using the madwifi driver and I then decided to install nVidias driver for the graphics card and the nForce2 chipset.
    The graphics went beautifully and I thought the nforce did too but I could be wrong. I selected to install both the audio driver and the network driver for the built in ethernet. After it had finished the audio driver I thought it was done completely and I set about editing the network driver in modprobe.conf (didn't alter anything to do with ath0). Once I realised it wasn't finished I restored the changes in the conf file and continued the install of the network driver.
    I thought this went fine but when I rebooted I got this error,

    Error for wireless request "Set Mode" (8B06):
    SET failed on device ath0; invalid argument.

    It then tries to determine the IP using DHCP (does a ping to the router) and doesn't connect. The ping looses all packets.
    I edited the Network settings and set the SSID and ip manually to what they should be and still nothing.

    Any ideas what's up? Will a driver reinstall sort it out?


Comments

  • Closed Accounts Posts: 999 ✭✭✭Raz


    I've sorted this one. There's three modes you can set. Auto, Manual and Ad-Hoc. Ad-Hoc isn't supported yet therefore auto isn't a valid option either. Setting it to Manual fixed the issue and I'm happy again :)


Advertisement