Hi everyone,
I have just run into this problem and was hoping for a bit of a hand sorting it out.

On a rebuild of Myth I finally managed to get my Mythbox to connect to the internet and I was very pleased. Now after a reboot the connection has not been restarted. Bugger.

During the initial setup I selected my wireless card (ath0), entered the relevent information on each screen - the Essid, channel number and WEP key and nothing else. Then at the end it connected.

I'm assuming the setup script saved these details somewhere. There must be a way to use this in startup setting something in .fluxbox?
I've had a search around and fond this page http://mysettopbox.tv/phpBB2/viewtopic.php?t=8228 but I am unsure on the drivers that Myth is (was) using to bring up the wireless card in the first instance. I am aware that Myth has both ndiswrapper and madwifi installed as standard.

How do I tell which drivers Myth is using on my netgear wg311t (atheros chipset) card?

Any advice greatly recieved. Thanks in advance.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Well, I can start to answer my own thread. I've found where the information is stored on my Myth box /etc/pcmcia/wireless.opts for refrence.
Now I've to work out how to get the information to be used by something else to start my wireless network and then put it into bootmisc.sh I guess. Or .fluxbox perhaps....
I'll keep you posted.
Feel free to join in at any time.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Ok, so looking through the forum, most people seem to be using ndiswapper. Can anyone tell me how to check which I should be using, or perhaps more accurately, which method does the initial lan/wireless lan setup use from the post-install configuration because that worked first time?

Thanks

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

I've been trying some ndiswrapper commands and it doesn't seem to like them very much. modprobe ndiswrapper gives me lots of FATAL errors.
Beginning to pull my hair out. Perhaps it's time for bed. Have another go tomorrow.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Well, looking at it again, it seems the madwifi drivers that came with this edition of KnoppMyth work. -Rather obviously as they did before- but what I want to know is why the setup script from the initial post-installation is not informing Myth that it should use those configuration parameters after a reboot? As it uses them first time and takes the time to write them to /etc/pcmcia/wireless.opt, surely it's setting itself up to be re-used. So what is it missing? Something obviously is broken.
Any pointers would be great.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

AFter having a root around in the various man files for setting up networks (more specifically at the man files for wireless interfaces ifconfig iwconfig and pcmcia).
There seems to be a way of mapping the information in the pcmcia.opts into something else. In this instance would the best place be to do this in /etc/network/interfaces (?)

I added the line mapping ath0 script /etc/pcmcia/wireless.opts but it didn't work.

Having done a search of the internet (google) it seems that pcmcia controls hot plug features. Mmm. Stranger and stranger.

Based on the fact, I was persuing this because my wireless network had worked (for the first time ever) I wanted to preserve it. Or reclaim it now it was down and wasn't showing any signs of returning. I bit the bullet and reworked my /etc/network/interfaces configuration file

NB: I am still aiming to use dhcp to connect.

It now looks something like this



On reboot. Failed. No connection.

I tired this manually:



So why did it work on initial setup, albeit rather slowly? And why not now?

Help. This is so fraustrating!!!!!

edit - the slow behaviour appeared to be a symptom of putting firefox in the wrong place. since corrected

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)