I am about to build my first MythTV box. I have been reading countless threads but am having no success with finding a ‘no-hassle’ configuration for a wireless USB network adapter with MythTV.

Have you had any luck with your wireless USB network adapter and MythTV (built with KnoppMyth)? If so, please post the instructions (and code), including the brand/model and driver you used. Also, does the adapter start up automatically when MythTV is powered on? If so, how is this done?

Are some brands better than others with MythTV (i.e. Linksys, D-Link, Netgear, Airlink, etc.)? Is there an ‘out of the box’ solution for this situation with MythTV? Are there certain brands to avoid at all cost with MythTV?

The more insight on this topic, the better. Please take a moment to post your wireless USB success stories, or troubles.

Thank you.

I don't think MythTV cares about what network device you have. What you ar elooking for is a card that works with Linux.

_________________
cesman

When the source is open, the possibilities are endless!

Is there a USB adapter that works well with MythTV (linux friendly)? I can't use a pci card due the limited space on the board.

Anyone else have any experience with a USB adapter and MythTV???

If you have to use wireless, then I can't help you but I just got a cable usb network card, Billionton ThumbLAN USBKR-100B.
Using R5A-16, it loaded the module just fine without any configuration.
For some reason, I have to manually start it (assign an IP address) after boot, I suppose this is because network tries to load before USB but I will try and find out, actually that was why I read this topic anyway.

If anyone knows this for certain, feel free to tell me.

***EDIT: Solved my IP problem:
first I did a:
update-rc.d -f networking remove
and then:
update-rc.d -f networking start 80 2 3 4 5 . stop 80 0 1 6 .

So now, it loads my IP address after everything else..

_________________
This is not a funny signature

With further reading posts I think I want to avoid the wireless USB network adapter thing; especially since a lot of people seem to have trouble getting the ndiswrapper to work properly.

So my poll to everyone is what sort of networking solution do you use for your MythTV setup? My MythTV (when I finish it) will be in the living room, whereas my router is in my bedroom (too far for a cable run).



What is the easy, cheap solution for MythTV users when a physical cat5 cable run isn't acceptable? What is the best method (pci wireless cards, wireless bridges, wireless access points, etc.)? Also, I am a linux newbie so keep that in mind.

_________________
Mobo: Biostar M7NCD
Proc: Amd Athlon XP 3200+ (2.2ghz, 400fsb)
RAM: Kingston 2 x 512MB PC3200 (1GB total)
HDD: Maxtor 300GB (Pri Master)
Video: Rosewill (Nvidia) GeForce FX5200 128MB
Capture: Hauppauge WinTV-PVR-250

I decided to punt on the wireless bit and I did the following:

1. Bought a Linksys WRT45G wireless router to go with my WRT54GS I currently run. I picked this up for $39 after rebate at Staples.

2. Went to www.linksysinfo and read a ton

3. Flashed the firmware with the beta of DD-WRT.

4. Configured my 54G to act as a client to my 54GS. I actually flashed the firmware on both routers.

Works like a champ. I can use this as basically a 5 port game hub. Sure, you can go and get the cute black ones from Linksys for $100, but I would rather go the $40 route and have MUCH more flexibility. DD-WRT can act as an access point, wireless client, range extender, etc. And, on top of that, there are a ton of options you can configure. Things like the internal power settings (to boost your antenna), throttle bandwith, or even act as a Chilispot access point (like you see in Starbucks and such). Very cool stuff.

This saved me from having to play around with NDISWrapper or try to find any USB 802.11G card for Linux (not too much luck on that one).

I'd recommend this route, but be sure to read first. I didn't pay attention and bricked one of the 54G's I had sitting around due to not paying attention to the flash/reboot process. I still haven't recovered it, but then again, I haven't put too much time into trying to get it back.