I'm sure there is a simple explanation, but the couple of commands I know a little about aren't responding for me, such as iwconfig, and ath0, etc... My WiFi adapter sets up out of the box, but after reboot it doesn't start automatically, in fact , I cannot figure out how to start it manually. I am also getting a message "could not connect to master backend server--is it running" although I believe this is caused by my lack of wifi?

Alright, I can get it to connect manually, using iwconfig, I set my essid *** and key *** , then run "dhclient ath0" and it will connect. It seems to default to netmask 255.255.255.255 and my router is set up for 255.255.255.0, Is that my problem? Other thing I noticed is, I tried to reserve an IP addy on my router and once I did it chose another,after the above commands. My router is netgear wgr-614. I leave a range of IP's open for friends to use and other computers I may be playing with... Should I maybe config my connection as wifi/lan rather than ath0/wireless during config after setup? I don't expect to power this thing down ever once setup, but the simple task of rebooting when I plug it into my entertainment center is gonna leave me with a non-functional backend. I'm lost, any suggestions are appreciated. I did search and find another post but with no usefull solution.

What does your /etc/network/interfaces file look like?

Hi,
is usually caused by not having gone through all the setup steps. Another thing that will cause that is if you do an upgrade and change the host name....

open an xterm (alt x) and do su - to get to root. /etc/init.d/mythtv-backend restart should work or may cough up why not.

Mike

/etc/network/interfaces -- configuration file for ifup{8}, ifdown{8}

# the loopback interface
# automatically added when upgrading
auto lo ath0
iface lo inet loopback

iface ath0 inet dhcp

mjl have tried your suggestion, here was response...

Restarting MythTv server: mythbackendNO /usr/bin/mythbackend found running; none killed.
*
*
root@blam#





This was attempted immediately after getting my ath0 back up on the preffered ip addy. I have no idea what it means...

One other thing, back to my local network... I have 10 IP's possible with anywhere from 2-6 being used, when I follow the steps I've indicated to get ath0 up, rather than give me the same addy(my router I believe) it gives me *.*.*.208, so I run "dhclient ath0" again, and this time I get *.*.*.209, then 210 then 207, then finally it kicks down *.*.*.205 which is what I was looking for. any suggestions???


Thanks for the help guys, please bear with me...

Hi,
NO /usr/bin/mythbackend found running; none killed. Pretty well tells the story, after you do the restart try a ps ax command to look at the running processes. You should see something simular to this:
/usr/bin/mythbackend --daemon --logfile /var/log/myth... (I ran out screen)

If the backend daemon isn't running, then go into setups and also utilities and fix what it needs. alt s will get you to the primary setup and it needs tv tuner stuff, even it you have to make it up.

Your wireless is a stand alone issue, can't help on that one.

Mike

Make your /etc/network/interfaces look like this:



Where mynetworkname is the name of your wireless network and mywirelesskey is your WEP key that you set on your wireless router.
After making those changes, at the shell type:


Try that and see what happens.

What might be happening with the IP addresses is that your myth box gets an IP address via DHCP. Then if you reboot, run dhclient, etc. your machine asks for another IP address, but the router has marked your 1st IP address as being used, so it gives you another one. If you want your myth box to have a static (fixed) IP address, then /etc/network/interfaces should look like this:

The nameserver line may not be necessary - it fixed a problem for me.

Hi loserbaby,
Did you manage to solve this problem with your wireless? I seem to be struggling with a similar problem. When installing/upgrading - it all works. I just don't seem to be able to bring it back up whatever....
Just about to try again, so might be able to offer some more information later.
regards

_________________
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)

No, I have not... I attempted to edit my "/etc/network/ configuration files as pcicard stated above yet it still failed on boot. It did however seem to hold my essid and key though, so all I had to do was "dhclient ath0" until it came up on the desired IP addy.

I came across something that recommended leaving the backend and master backend IP's at 127.0.0.1, so I returned them to that, however I still am experiencing , backend not running error.

I am re-installing right now and I will continue to attempt to figure out what step I'm missing during setup, the wireless start at boot is minor right now, I figure that will be rather easy to get going.

for the record I believe we have the same netgear WiFi card and similar system.

Hi thanks for your reply. I've been struggling with this issue for some time. (See here: http://mysettopbox.tv/phpBB2/viewtopic.php?t=11228&highlight=)

I rebuilt my sytem with a fesh install last week and as usual, when entering the details in the setup section it connects instantly. When after a reboot I can reconnect manually (having to enter everything by hand), dhclient takes it's time thinks about it and connects.

As I said in the thread linked above (more like talking to myself at the time) when it worked first time, /etc/pcmcia/wireless.opts hlds all the necessary information. Why when using the network setup at install works so well then isn't reused at reboot? It's almost like two different systems are in opperation.

So far, I've not noticed my system holding my essid and wep key. I'll have another go overthe weekend. Kinda busy today so hopefully tomorrow.


As myth seems to default to using hte madwfi drivers I found this on their trouble shooting page: http://madwifi.org/wiki/UserDocs/Troubleshooting



and this has also been added (which is news to me btw) So I may try this too.


I'll give it a go, though I've got to go out shortly... so it may have to wait until at least til tonight.

_________________
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 had the same problem, but the first half of psicard's suggestion did the trick for me. Thanks.

The problem was that networking with my wireless card would work right after I did a fresh install of R5D1, but I wouldn't have network access after I rebooted -- it failed to find the DHCP server.

The installer asked me all the questions about the card (e.g., the key1, etc.) but it seems like it didn't actually save it anywhere? Can KnoppMyth be changed to write this information into the /etc/network/interfaces file automatically?

Hi mccart777,

To answer your question about where the installer entered details is stored is /etc/pcmcia/wireless.opts. Why it isnt passed on to be reusaed in reboot is a mysery.

When you said: Do you mean you've solved this issue? So do you now get your wireless connection back up on reboot? I'm pretty sure my network.config file is like the one psicard posted. Tbh, I've seen many interfaces files posted and they're all about the same.

I've been mega busy recently - and this is the first time i've had a chance to look at my mythbox for ages (a good few weeks). And I've been mulling over this issue. I'm wondering if there is an issue in loading the drivers correctly, or in the wrong order, or something else.

I'm going to reboot my machine shortly and try some experimentations.

_________________
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 ran through several of the steps from the madwifi newbie-howto and ran dhclient ath0 after each as root.

First, I modprobe ath_pci --- no connection
then I tried ifconfig ath0 up --- no connection
then iwconfig ath0 essid "my essid" --- connection!!!!

It reported that there was an unequal amount of data recieved than sent, but I could serf the web there after.

I also then added iwconfig ath0 key <my key>
and iwpriv ath0 authmode 2 and reran dhclient ath0 and it didn't make any difference to the packets recieved descrepancy.

So for some reason, Myth is not recognising the essid switch in interfaces

Any ideas anyone?

_________________
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)