I reinstalled with the 32 distribution and sure enough it picks up the Network card. Unfortunately the setup query for the DHCP (y/n) does not work....
Please describe this "does not work" idea.
The initial config in my case gets stopped because I have a firewirecard defaulting to eth0 and your scripts are also eth0 for the normal net card interface.....
Argh! I hate when firewire gets eth0 after reboot. It always seems to happen like this for any add-on cards, not just firewire: add-on cards get detected 1st and they mess up the whole thing.
I tried settng this to be the ip address in the interface file but could only manage to get static IP working......for some reason some part of the script sets the IP for lota of initial config to be the 192.168.80.1 (which looks like a DHCP generated address, but I;m not sure how)
This is the scenario on what I think happened:
The CD installer detected the network cards, but didn't care about the firewire card, so your network cards got named eth0 and eth1. After reboot, the firewire card's drivers got loaded 1st, making it eth0, and the network cards got named eth1 and eth2. There's also a possibility that the installer saw your firewire as eth2, but I don't think this is the case (at least I don't understand that to be the case from what you're saying).
192.168.80.1 is the IP given to the internal network adapter.
Anyhow I brought the net up under a static address 192.168.0.40 and can ping external ips and the router.....
I ran Myth setup (a new optionin the \computer section of the setup I never had before and changed this to be the static ip) - I then ran the tv and still get the same "Can't" connect to backend server error" - I even changed the IP on all of the devices in pluto admin...but still no go....
Again, MythTV is not my field of expertise. I'm as puzzled about this as you are.
Then I tried to set the Interface back to use dhcp but got the failure attempts to "DHCPDISCOVER" on eth1 to 255.255.255.255 port 67 interval 11 - No DHCP Offers received- No working leases in persistent database - Exiting - Failed to bring up et1:
This means you don't have a DHCP server (outside your core) to give your Core an IP address. Assign 192.168.80.1 to eth2 (which seems to be the other network card now).
So I guess this is another cry for help to anyone who can help ne get the Myth Frontend to talk to the backend.