Saturday, February 12, 2005, 10:34:20 PM, Jeff wrote: >> On Sat, 12 Feb 2005 21:27:41 -0500, Jeff <[EMAIL PROTECTED]> wrote: >>> I upgraded from FC1 to FC3 using the >>> upgrade option on the FC3 boot CD and tried >>> to follow the upgrade section of Jarod's guide. >>> apt-get complains about lots of problems with >>> fc1 packages which I suspect will take some time >>> to work out. >>> >>> Is it worth going through this or do people >>> just copy the important files to a safe place >>> and do a new install when upgrading a FC release? >>> >>> The important files seem to be: >>> >>> mythtv database from mysqldump >>> /home/... >>> /etc/X11/XF86Config or /etc/X11/XF86Config-4 >>> /etc/asound.state >>> /etc/exports >>> /etc/fstab >>> /etc/hosts.* >>> /etc/init.d/vncserver >>> /etc/lircd.conf >>> /etc/lvmconf/* (output file from vgcfgbackup) >>> /etc/modules.conf >>> /etc/modprobe.conf >>> /etc/ntp.conf >>> /etc/rc.local >>> /etc/ssh/* >>> /etc/sysconfig/vncservers >>> > Saturday, February 12, 2005, 9:31:52 PM, Kevin Wentland wrote:
>> I am considering doing this myself.... FC1 -> FC3 >> How did it go for you? >> After you did the Fedora upgrade did you upgrade your apt to coincide >> with your new fedora version? >> Maybe this would have had it complain less. > It is not going well. FC3 is up but that's it at the moment. > Fortunatly, this is a 2nd frontend I'm experimenting on, > not my main backend+frontend. > I did the Fedora upgrade because I'm using LVM and there > are strong warnings about not using apt if you've got a > LVM. > I found that after the FC3 upgrade finished the machine > wouldn't boot. It hung on calculating kernel parameters. > The fix to this > (http://www.linuxquestions.org/questions/history/277212) > is to boot and type <a> when you select the kernel, edit the boot > line and remove rhgb. There is a note that after booting: > sh NVIDIA*.run > maybe edit xorg.conf > /sbin/modprobe nvidia > cp -a /dev/nvidia* /etc/udev/devices > chown root.root /etc/udev/devices/nvidia* > will resolve the problem. I haven't tried this yet so X isn't > up at the moment. > After the Fedora upgrade I downloaded atrpms-kickstart. This > required removing a couple of fc1 packages (medley-package-config) > and yum as they depend on the apt sources file. > The apt sources file from atrmps-kickstart contained a > reference to ayo.freshrpms.net. This was broken so I changed it > to freshrpms.pingo.org. This let apt-get update run. > apt-get dist-upgrade requires -f due to some broken > dependencies and even with -f it doesn't run. Ok, in case anyone else cares, here's what I did. After FC3 was installed from the boot disk and I modified the apt sources as above (this may not have been necessary) I used rpm -e to remove the various kernel modules installed for myth (alsa, nvidia-kernel, lirc, ivtv, bttv, video4linux). Attempting apt-get install kernel=2.6.9-1.724_FC3 will list the problems on your system. apt-get -f install was necessary to fix a couple of other issues. 2.6.9-1.724_FC3 in Jarod's guide is now old. Try 2.6.10-1.760_FC3 or pick your own poison. Look at the kernels supported on ATrpms and compare this to the list available on ayo.freshrpms.net. Once I got the kernel installed (or maybe before I got the kernel installed but after the dependencies were removed) I re-installed atrpms-kickstart. In order to get VNC back up I had to edit xorg.conf and remove the VNC lines from the "Display" section and add Option "passwordFile" "/root/.vnc/passwd" to the "Screen" section. After installing the nvidia packages (from Jarod's guide) I was able to reboot and X would start. At this point I followed Jarod's guide for a first time install, skipping steps which don't make sense. Something seems funny with lircd. I got irw to run with some fiddling around but I don't think it survived a reboot. I need to track this down. lircd is starting as "S65" so this isn't the problem.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
