MythAnne wrote:
I dl-ed the dist 1.1.0, burned it to DVD (using DVD Decrypter), launched it and... it failed with I/O errors.
[...]
I first mucked around with accessing the booted debian using putty (changing ip-addresses etc), but finally decided to attach the keyboard to the box.
This works a lot easier and faster btw, so if you have a choice, use a keyboard on the xbox instead of using the remote (putty) option.
[...]
1) What consequence does selecting NFS server for media storage have ?
Does this mean I have to do some extra tweaking at the backend (install NFS packages, configure NFS to openup certain mount points, create mount points) ?
I'm fairly new to actually tweaking/installing linux, so what maybe a no-brainer for some could very well be something I've never heard of :)
2) Can a DNS-name be used for the backend instead of a fixed ip-address ?
3) Do the network settings have to be entered ?
Is it not possible to have the application use the ip-address handed out by a DHCP server ?
If they don't have to be entered, is it ok to leave those fields blank ?
j0ly wrote:
Anne,
Sorry for taking so long to get back to you
No worries. And thanks for the comments.
I gave it another go and was succesful at installing the mythtv frontend under Xebian on my Xbox.
I also had a closer look at the installer python script and had to tweak a couple of things to get the installation to work.
For starters I had to use a (Traxdata) DVD+R to get the 1.1.0 Xebian distribution to install without problems (I/O errors).
I don't know why my trusted Xbox-transfer media (A Maxell DVD-RW) failed this time around, but it did.
Initially it seemed the problem was with the (d/l of) the 1.1.0 distribution, so i tried the 1.1.4 one, but using the 1.1.4 (by commenting out the distribution check in the install.pl script) resulted in errors, so I tried the 1.1.0 version again, succesfully when using the correct media :)
As I did this about a dozen times, I ended up typing the ifconfig in a bash shell using a keyboard connected to the xbox and from there on used Putty. This makes cut&pasting so much easier :)
As I initially won't be using the myth-backend-server to store anything else than what mythtv stores itself there, I do not need NFS for now so I entered /mnt as default.
What the script does is add a line in the /etc/fstab so if needed you can always change this later.
I haven't tried using DNS names instead of fixed IP addresses.
But given the fact that wget is executed with a DNS name instead of IP, my guess is that DNS names should work.
While reading the install.pl script I did find that you have to use fixed IP settings when doing a option 1 install. I don't know why dhcp is not supported (it is for the 2nd option), but in the current install script it isn't.
Which is a bit of a shame because with the Xbox, 6 client machines, three servers, one hub, three switches, two routers and one accesspoint the networking in my house isn't quite as simplistic anymore :)
As you can see I answered a couple of my own questions by trial and error and reading up on linux stuff.
Quote:
Quote:
4) Why are files copied from the E: drive to the F: drive ?
They are not moved but only replicated on F:
[...]
- and i remove those 4 files off of e (even tho they dont take much space)
Ok, so it's just mentioned for clarity.
As I most likely won't be using the Xebian/Mythtvfrontend much(*) I'll experiment with moving the rootfs and swap to F and changing the linuxboot.cfg.
Quote:
I have also just noticed that there is now a new error in the script, as some of the nonstable US sites are not accepting connections, so im working it out and ill update the walkthrough tonight...
I ran into that problem too.
But before that point I noticed that the 'mount -t iso9660 -o ro,suid,loop /dev/cloop/0' command, executed just after "Starting to copy the Xebian base..." message and even before the copying starts, fails because cloop is not recognised. I haven't figured out what the idea behind this mount command is, why it fails nor what should be changed to make it mount succesfully, but it seems that not being able to execute that mount doesn't influence the installation of Xebian, so I just ignored it :)
The domain name that is asked for is added to the /etc/hosts and /etc/hostname files. Entering the default did indeed not seem to matter.
After installing and starting Xebian on the Xbox, the configuration step install.pl -c failed because of the failure to connect to the nonstable nonus site as you've already noticed.
I added
# Unstable
deb
http://ftp.de.debian.org/debian/ unstable main non-free contrib
# Sources
deb-src
http://ftp.de.debian.org/debian unstable main contrib non-free
to the sources.list which helped solve that problem.
But of course the next problem was just around the corner.
While trying to install the mythfrontend, the 'apt-get install mythtv-frontend' command failed because mythtv-frontend depends on
libmyth-0.18.1 which in turn depends on libqt3c102-mt which needs the e2fsprogs (or a module with a name like it) to be disabled, which is not recommended.
To bypass this problem I executed apt-get install libqt3c102-mt with the ::Force-LoopBreak=true option and the apt-get install libmyth-0.18.1 after that.
And that was about it.
After that when I started Xebian from the (evox) menu, the mtyhtv-frontend was started automatically and everything seemed to work just fine.
Unfortunately the screen got garbled two times while I was playing around with the mythtv-frontend, resulting in the inability to shutdown propperly and (yes, you can feel this one coming :) the (re)boot of Xebian failing because the filesystem was corrupted. This earned me two round trips of an entire reinstall of Xebian and the mythtv-front end, including the above mentioned tweaks :)
Since I've backed up a succesful install so next time I should only have to copy those files back to the XBox and have a clean working Xebian install again.
In the mean time I've also installed a newer version of XBMC and the xbmcmythtv python scripts that, although they initially failed, now do seem to do the job just nicely, if for no other reason than that when the machine 'hangs', a simple reset is enough to get things going again.
And of course the boot time is drastically lower using the scripts instead of having to boot Xebian and start the mythtv frontend.
So for now I think I'll stick to xbmcmythtv, which btw gives me an opportunity to fiddle with moving all the Xebian files to F (See (*)).
I hope this was at least a bit informative for those out there trying to install Xebian and the mythtv-frontend on their Xbox-es.
[And then, when I was just done typing this, my internet connection went out for over 6 hours :]
Anne.