Difference between revisions of "User:Foxi352"

From LinuxMCE
Jump to: navigation, search
m
m
Line 74: Line 74:
 
And: '''TAADAA, lucid is booting for the first time''' :-)
 
And: '''TAADAA, lucid is booting for the first time''' :-)
 
To continue with bind9 setup:
 
To continue with bind9 setup:
 +
  sudo su - (because after reboot you are normally back in user shell again)
 
   apt-get dist-upgrade -f
 
   apt-get dist-upgrade -f
 
At this point we have finished all downloading. Time to free up some disk space.
 
At this point we have finished all downloading. Time to free up some disk space.
Line 113: Line 114:
 
== Additional tweaking==
 
== Additional tweaking==
 
You can update your local shared package cache. Your MD's will upgrade faster without downloading all the packages again if you do this.
 
You can update your local shared package cache. Your MD's will upgrade faster without downloading all the packages again if you do this.
   sudo su - (because after reboot you are normally back in user shell again)
+
   sudo su - (if not still in root mode)
 
   rm /usr/pluto/deb-cache/*
 
   rm /usr/pluto/deb-cache/*
 
   cp /var/cache/apt/archives/* /usr/pluto/deb-cache
 
   cp /var/cache/apt/archives/* /usr/pluto/deb-cache

Revision as of 19:34, 2 January 2011

My experiences upgrading a running core / hybrid from 0810 to 1004

My main motivation to upgrade my core was my skystar hd2 dvb-s2 card which i never got working on my 0810 core. Everything i found on internet was based on 1004. And of course help to alpha test new lmce packages. If you feel in a need to upgrade too, you may base your work on my experiences to speed up things. I had some help from possy which i credit here.

Please note that this is:

  1. unsupported from official help channels
  2. on your own risk. Backup your data before proceeding and most important your config files.
  3. you need some linux experiences. If you don't know what ssh is, or what a debian package is, then stay with official lmce distro's !
  4. this guide is based on a merely ontouched clean core install. All i did manually on the core was playing with v4l2 and other drivers to get my dvb-s2 card working (while i must admit i never had success until now)
  5. a lot of fun :-) You are not done in 10 minutes.

This said, it took me half a day and everything was up running again except two issues which i will fix and upgrade this page accordingly.

Preparation

ssh to your core (or login on console). To simplify things i always sudo to root during this guide.

 sudo su -

edit your apt sources.list to change from intrepid to lucid.

 cd /etc/apt
 vi sources.list

replace the entire content with the following (sponsored by possy :-) )

 # Regular lucid repos
 deb http://de.archive.ubuntu.com/ubuntu/ lucid  main restricted universe multiverse 
 deb-src http://de.archive.ubuntu.com/ubuntu/ lucid  main restricted universe multiverse 
 deb http://de.archive.ubuntu.com/ubuntu/ lucid-updates  main restricted universe multiverse 
 deb-src http://de.archive.ubuntu.com/ubuntu/ lucid-updates  main restricted universe multiverse 
 # LinuxMCE repo
 deb http://deb.linuxmce.org/ubuntu/ lucid  beta2 
 # For the Squeezeboxes
 deb http://debian.slimdevices.com/ stable  main 
 # And we want libdvdcss and stuff
 deb http://packages.medibuntu.org/ lucid  free non-free 
 # Some more LinuxMCE stuff (not sure it is still needed (it does not contain updates for 1004)
 deb http://deb.linuxmce.org/ubuntu/ 20dev_ubuntu  main 
 # eibd stuff
 deb http://www.auto.tuwien.ac.at/~mkoegler/debian/ eib  main 
 # Latest VDR stuff (from YaVDR.org)
 deb http://ppa.launchpad.net/yavdr/stable-vdr/ubuntu lucid main

The upgrade

After updating your sources.list you can download the new package lists:

 apt-get update

Take a deep breath and launch a first upgrade. Don't worry, at least for me it was just the beginning of long intense relationship between me and apt-get :-)

 apt-get dist-upgrade -f

It downloaded about 3,5GB and > 1000 packages. I launched the command multiple times (about a dozen) until always the same error message came back:

 E: Couldn't configure pre-depend x11-common for libxau-dev, probably a dependency cycle.

I fixed this with

 apt-get install x11-common

Then again i run

 apt-get dist-upgrade -f

a couple of times until always the same error message came back:

 (error message missing here). Basically: it could not install the following packages ...
 
 libxine1
 phonon-backend-xine
 kdebase-runtime
 konsole
 xorg
 plasma-scriptengine-javascript
 
 .. because it could not delete /usr/share/doc/libxine1 which was not empty

This was a quick fix:

 rm -rf /usr/share/doc/libxine1

I had that errormessage many many times about directories that are not empty. But i could ignore them all except this one. Then again, as usual:

 apt-get dist-upgrade -f

a couple of times. At some point i did not get further on my way and had some hundred packages not installing. From my previous debian times i remember that aptitude did some times a better (less secure) job when having a lot of packages with problems. So i tried:

 aptitude dist-upgrade -f

which proposed a solution including removing some packages. I made sure there was no package with "pluto" or "lmce" in the name and accepted the first proposed solution. This worked and there were only some packages left to install / configure. One package was libkipi7 which complained about overwriting some files also included in the libkipi common packages. While trying to remove this package i had a dependency with libkipi5 also installed. The solution was:

 dpkg -r libkipi-common libkipi5

as usual:

 apt-get dist-upgrade -f

a couple of times until nearly everything is installed. At this point it complained about installing the bind9 update. Apparmor blocked the update with some strange error messages. Digging deeper into it showed some kernel udev problem. At this point i rebooted my server for the first time to load the newly installed kernel.

 reboot

And: TAADAA, lucid is booting for the first time :-) To continue with bind9 setup:

 sudo su - (because after reboot you are normally back in user shell again)
 apt-get dist-upgrade -f

At this point we have finished all downloading. Time to free up some disk space.

 apt-get autoclean

Resolving remaining problems

I HAD NO X (GUI) AFTER REBOOT. Don't panic if it's the same for you. I remember that one day KDE on core asked me to install restricted nvidia drivers. I suppose saying yes did remove the pluto nvidia drivers and replace with kubuntu ones. No idea why they were not upgraded. After rebooting i ssh'd to the core and continued:

 sudo su -
 apt-get install pluto-nvidia-video-drivers (to fix X not coming up)
 apt-get -f install

Next Problem: I had a KDE login screen but no keyboard working (i have a Logitech USB keyboard). Analysing the Xorg log files showed me that the kbd driver module are not present. Some Googeling revealed me that xorg kbd drivers have been replaced by evdev drivers some time ago. I had to do some manipulations to get it working again. (still in sudo mode)

 service kdm stop (to stop X)
 Xorg -configure (to create a new config file in /root/xorg.conf.new)
 mv /root/xorg.conf.new /etc/X11/xorg.conf
 cd /etc/X11
 vi /xorg.conf (or any favorit editor)

The newly created conf was clean, but still used the old drivers. So i changed the keyboard and mouse input section to the following:

 Section "InputDevice"
 	Identifier  "Keyboard0"
 	Driver      "evdev"
 EndSection
 
 Section "InputDevice"
 	Identifier  "Mouse0"
 	Driver      "mouse"
 	Option	    "Protocol" "evdev"
 	Option	    "Device" "/dev/input/mice"
 	Option	    "ZAxisMapping" "4 5 6 7"
 EndSection

Simply remove the existing xorg.conf file

 mv /etc/X11/xorg.conf /etc/X11/xorg.conf.dontload

Then you need to remove the kdm startup to avoid loading the kde login and desktop.

 rm /etc/rc5.d/S30kdm
 mv /usr/bin/kdm /usr/bin/kdm-dontstart

Then i rebooted ...

 reboot

... and (nearly) everything worked. ATTENTION: My orbiters were not showing any images at this time. The explanation was very very simple: The core was doing a complete regeneration of all orbiter screens. I don't know why, and to be honest, i would not give a cent to know why. I just waited for the process to finish and everything worked like a charm.

Additional tweaking

You can update your local shared package cache. Your MD's will upgrade faster without downloading all the packages again if you do this.

 sudo su - (if not still in root mode)
 rm /usr/pluto/deb-cache/*
 cp /var/cache/apt/archives/* /usr/pluto/deb-cache
 cd /usr/pluto/deb-cache
 dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

If you did not follow the guide step by step and did not do apt-get autoclean like written above you will have a bunch of warning messages about doubble packages.

Remaining problems (02.01.2011)

There are two problems remaining for now: There is one remaining problem actually:

  1. MD PXE booting is not yet working for new MD's. Existing MD's do boot.

#I have KDE login screen immediatly after boot, and after logging in i have KDE desktop and the LMCE orbiter in top-left corner (about a quarter of the screen because of the high resolution of KDE). I will try to fix this today and update the page accordingly. fixed 02.01.2011

Good luck !!!