Is there a good guide or posting out there that might help me setup my eHome PCI Wireless G Desktop Adapter with KnoppMyth R5D1?
Will it be as easy as plugging it in and rebooting?

I also have a eHome USB Wireless G Adapter. Would it be possible to get that to work on my KnoppMyth box?

Any help would be appreciated.

It looks like it should work with ndiswrapper using windows drivers:

http://ndiswrapper.sourceforge.net/medi ... x.php/List

I haven't had to do this for a while since there are drivers for my wireless card now, but its something like:

install driver files:

>ndiswrapper -i filename.inf (from windows cd)

check if working (should say hardware present)

>ndiswrapper -l

load modules at startup
>ndiswrapper -m
>sudo depmod -a
>sudo modprobe ndiswrapper

Taken from some old notes i made, I have no idea if this will still work but searching for ndiswrapper should give lots of posts.

Once the cards installed, you need to use the iwconfig command to set it up and put the commands in /etc/network/interfaces to do on bootup. Mine looks a like.



Hope this helps a bit.

I know this is an older post but I'm having problems getting my wireless card to connect on boot.

I have KnoppMyth E5R50.
I have a Zonet ZEW2501 USB wireless network adapter.
It works just fine if, after I boot, I get into a terminal as root and type:


After I do that, it's working fine, it reaches my DHCP server on my router and gets an IP no problem.

But when I have pretty much the exact same code as tohc1, namely:



(everything but the channel, although I've tried the channel and that doesn't work)

I get messages like this on boot:

Error on wireless request "Set ESSID" (8B1A)
SET failed on device wlan0; Invalid argument

And then it tries to get an IP address from my DHCP server on my router and times out like 6 times.

Does anyone know how to use a wireless network card on boot in KnoppMyth?

Thanks!

Try this in /etc/network/interfaces:


You should be able to check to see if it worked (without rebooting) with this

Hi!
Thanks for your reply.
I tried your code -
Unfortunately, now instead of 3 "Error for wirelsss request" statements, I get 5. For some reason my Knoppmyth doesn't recognize "wireless_*" as valid statements. It keeps saying "invalid argument" for every one of these statements I put in my etc/network/interfaces file.

Please submit any other ideas you may have, I would appreciate it!

* Also, I don't have the int.d directory in my /etc directory, nor can I find the "networking" command anywhere. Any ideas on where I can get it?

Sorry, little new to Linux. Thanks!

oops - that should have been


Did you install ndiswrapper after you installed R5E50? A lot of folks (myself included) had problems with ndiswrapper as it was included in R5E50.
If you are using ndiswrapper and haven't, you may want to...

If you're not using ndiswrapper, then I'm stumped.

So I haven't been using ndiswrapper, because I was reading in one or two forums that people were having trouble with ndiswrapper and the ZEW2501. Not sure which version of ndiswrapper though.

What gets me mad is that every forum about setting up wireless on boot through /etc/network/interfaces gives the same wireless_essid, etc. lines as advice.
And mine absolutely refuses to recognize the lines as valid commands. So annoying.

P.S. I actually had it working for like two reboots. I had put in the lines:

in the /etc/network/interfaces file and it worked! But then just stopped working; I didn't change a thing.
So annoying.

Thanks for your help.

It's "wireless-*" not "wireless_*" - that's "wireless" followed by a hyphen (and not an underscore as you appear to be using).

HTH

Simon

Thanks Simon.
Unfortunately, I've tried with the hyphen and underscore, and they both give me the same error.

Maybe a space after wireless? I don't know.

No, definitely not a space.

I've got a Belkin Wireless G USB Network Adapter (F5D7050) working with KnoppMyth and the only wireless-related lines I have in /etc/network/interfaces file are



(thinks for a bit)

Ah I wonder if it's a problem I've encountered in that the wireless device hasn't been initialised in time for the wireless commands to kick in and work.

Try creating the following script in /etc/network/if-pre-up.d (suggest name it wireless-ifup)



Don't forget to chmod +x it.

This will bring the wlan0 interface up before ifconfig commands are run at startup.

HTH

Simon

Not sure if it helps but when I was setting up my card (an RT2500 chipset card), I remember seeing posts about the card needing to be initialised a few times before the settings would 'stick'.

Also when configuring mine the order of the commands was important otherwise it wouldn't work...

If all else fails you could stick your commands in a file to run at bootup, (maybe /etc/init.d/bootmisc.sh)

I'm at work right now so I can't try this out right now, but I had a couple questions. I'm little new to Linux (though I've done plenty of C/C++), so my questions will sound n00bish, but thanks for your help so far.

Will the file bootmisc.sh automatically run at startup?
Also, if I create a file called "wireless-ifup.d" in the /etc/network directory and add that code (ifconfig wlan0 up), and then chmod it, will that automatically run at startup? If not, what do I need to do to include it in bootup?

My knowledge is limited but...

bootmisc contains commands that are run on bootup so you could just add them into the end of this file or you could create a script and run that from here.

make a file XXXXX.sh and chmod, you'll need to start the file with to make it run under bash (the command shell)



I think bootmisc gets run somewhere near the end of boot so you'll still get a load of error messages from when it tries to initialise the wireless card, but at least it will work until figure out how to make it work properly.

So, it looks like it's working consistently now. Making the "wireless-ifup" file with the "ifconfig wlan0 up" code was the key.

Now, I can put in the instructions in /etc/network/interfaces in any of the formats, i.e. "wireless-essid," "wireless_essid," even "WIRELESS_ESSID" and it works.

Also, something else - using the "/etc/init.d/networking restart" works, but too well: it remembers that I typed the "iwconfig wlan0 essid MyNetwork" commands, and so will obtain an IP no problem, when then, on boot it won't work.

Thanks for all your help, I'll post again, when it doesn't work tomorrow. Hehe.