I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
Anne
On 12/20/2009 12:52 PM, Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
After you rebooted did the Anoconda install proceed?
Anne
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Sunday 20 December 2009 16:57:29 Patrick Boutilier wrote:
On 12/20/2009 12:52 PM, Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
After you rebooted did the Anoconda install proceed?
No - I thought the upgrade had been too fast to be believed :-) After a few minutes, common sense told me to interrupt grub and see what I could find there. The default was to continue in F11. I switched to the Upgrade option, and it is proceeding now.
Anne
On Sunday 20 December 2009 16:52:33 Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
Anne
Hopefully solved, anyway :-) Nowhere in the PreUpgrade notes does it say that the default will be to continue in F11, or that it is necessary to interrupt Grub to start the upgrade :-)
Anne
On 12/20/2009 01:01 PM, Anne Wilson wrote:
On Sunday 20 December 2009 16:52:33 Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
Anne
Hopefully solved, anyway :-) Nowhere in the PreUpgrade notes does it say that the default will be to continue in F11, or that it is necessary to interrupt Grub to start the upgrade :-)
I believe that is a bug. Preupgrade from 10 to 11 booted into Anoconda by default, but 11 to 12 doesn't.
Anne
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Sunday 20 December 2009 17:18:35 Patrick Boutilier wrote:
On 12/20/2009 01:01 PM, Anne Wilson wrote:
On Sunday 20 December 2009 16:52:33 Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
Anne
Hopefully solved, anyway :-) Nowhere in the PreUpgrade notes does it say that the default will be to continue in F11, or that it is necessary to interrupt Grub to start the upgrade :-)
I believe that is a bug. Preupgrade from 10 to 11 booted into Anoconda by default, but 11 to 12 doesn't.
Well, it finally finished, just as I'd begun to think it was stuck. Unfortunately it booted to a black screen. I tried several times to boot with an edited grub entry, without success. This last time it suddenly started up a blue screen with the Fedora infinity sign - and I thought I was winning - but it's still sitting there, a black screen with a flashing cursor at the top left. If I don't crack this soon I'll end up wiping it and installing from disk.
Later - well, at least I got as far as a text login. Now I have to try to get the display working. system-config-display is not installed. Yum tells me that it can't retrieve repository metadata (repomd.xml) for repository:fedora. I have already disabled adobe repo and ATrpms repo, and I guess that it's going to fail on all the others too, by the sound of it. Any ideas?
Anne
On Sun, 20 Dec 2009 20:01:35 +0000, Anne Wilson cannewilson@googlemail.com wrote:
On Sunday 20 December 2009 17:18:35 Patrick Boutilier wrote:
On 12/20/2009 01:01 PM, Anne Wilson wrote:
On Sunday 20 December 2009 16:52:33 Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and rpmsav files.
What have I missed?
Anne
Hopefully solved, anyway :-) Nowhere in the PreUpgrade notes does it say that the default will be to continue in F11, or that it is necessary
to
interrupt Grub to start the upgrade :-)
I believe that is a bug. Preupgrade from 10 to 11 booted into Anoconda by default, but 11 to 12 doesn't.
Well, it finally finished, just as I'd begun to think it was stuck. Unfortunately it booted to a black screen. I tried several times to
boot
with an edited grub entry, without success. This last time it suddenly
started
up a blue screen with the Fedora infinity sign - and I thought I was
winning
- but
it's still sitting there, a black screen with a flashing cursor at the
top
left. If I don't crack this soon I'll end up wiping it and installing from disk.
Later - well, at least I got as far as a text login. Now I have to try
to
get the display working. system-config-display is not installed. Yum tells me that it can't retrieve repository metadata (repomd.xml) for repository:fedora. I have already disabled adobe repo and ATrpms repo, and I guess that
it's
going to fail on all the others too, by the sound of it. Any ideas?
Anne
For a start, are you really on F12 or are you stuck with rawhide for whatever reason? Rawhide has a broken curl which breaks yum with the symptoms you are having. Second, obviously, I assume your (inter)net(work) works? Third, what kind of video hardware are we talking about? :)
Most of my similar problems were solved by updating after preupgrade. Some hassling was involved for me though due to (I hardly dare to speak it out loud on this mailinglist) nVidia hardware. :)
On Sunday 20 December 2009 20:12:38 Eelko Berkenpies wrote:
On Sun, 20 Dec 2009 20:01:35 +0000, Anne Wilson
cannewilson@googlemail.com wrote:
On Sunday 20 December 2009 17:18:35 Patrick Boutilier wrote:
On 12/20/2009 01:01 PM, Anne Wilson wrote:
On Sunday 20 December 2009 16:52:33 Anne Wilson wrote:
I've just used PreUpgrade for the first time, and I'm a bit worried about the result. Everything I see seems to suggest that the system believes me to be still in F11. I did reboot when instructed, and I've just finished removing the packages listed by 'package-cleanup --orphans', though I haven't yet gone through the rpmnew and
rpmsav
files.
What have I missed?
Anne
Hopefully solved, anyway :-) Nowhere in the PreUpgrade notes does it say that the default will be to continue in F11, or that it is necessary
to
interrupt Grub to start the upgrade :-)
I believe that is a bug. Preupgrade from 10 to 11 booted into Anoconda by default, but 11 to 12 doesn't.
Well, it finally finished, just as I'd begun to think it was stuck. Unfortunately it booted to a black screen. I tried several times to
boot
with an edited grub entry, without success. This last time it suddenly
started
up a blue screen with the Fedora infinity sign - and I thought I was
winning
- but
it's still sitting there, a black screen with a flashing cursor at the
top
left. If I don't crack this soon I'll end up wiping it and installing from disk.
Later - well, at least I got as far as a text login. Now I have to try
to
get the display working. system-config-display is not installed. Yum tells me that it can't retrieve repository metadata (repomd.xml) for repository:fedora. I have already disabled adobe repo and ATrpms repo, and I guess that
it's
going to fail on all the others too, by the sound of it. Any ideas?
Anne
For a start, are you really on F12 or are you stuck with rawhide for whatever reason?
Well, if I try a nomodeset boot I see Fedora 12 at the bottom of the screen, and uname says it's running an F12 kernel.
Rawhide has a broken curl which breaks yum with the symptoms you are having. Second, obviously, I assume your (inter)net(work) works? Third, what kind of video hardware are we talking about? :)
Most of my similar problems were solved by updating after preupgrade.
Some
hassling was involved for me though due to (I hardly dare to speak it out loud on this mailinglist) nVidia hardware. :)
Anne
[snip]
Well, if I try a nomodeset boot I see Fedora 12 at the bottom of the screen, and uname says it's running an F12 kernel.
Hi,
If the kms-kernel model causes problems you can keep it from loading by dracut by adding: "rdblacklist=<kms-kernel-model>" to the kernel boot line in grub.conf.
Martin Kho
Rawhide has a broken curl which breaks yum with the symptoms you are having. Second, obviously, I assume your (inter)net(work) works? Third, what kind of video hardware are we talking about? :)
Most of my similar problems were solved by updating after preupgrade.
Some
hassling was involved for me though due to (I hardly dare to speak it out loud on this mailinglist) nVidia hardware. :)
Anne
New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
2009/12/21 Martin Kho lists.kho@gmail.com:
[snip]
Well, if I try a nomodeset boot I see Fedora 12 at the bottom of the screen, and uname says it's running an F12 kernel.
Hi,
If the kms-kernel model causes problems you can keep it from loading by dracut by adding: "rdblacklist=<kms-kernel-model>" to the kernel boot line in grub.conf.
Martin Kho
model=module :-)
Rawhide has a broken curl which breaks yum with the symptoms you are having. Second, obviously, I assume your (inter)net(work) works? Third, what kind of video hardware are we talking about? :)
Most of my similar problems were solved by updating after preupgrade.
Some
hassling was involved for me though due to (I hardly dare to speak it out loud on this mailinglist) nVidia hardware. :)
Anne
New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
Anne Wilson wrote:
Any ideas?
Last time I tried preupgrade, I made sure to update all of my system as required, even uninstalled some things from rpmfusion, etc., just to make sure there would be no complications, and then spent a lot of time having preupgrade download all of the updates to my entire system.
I always have 2 or 3 installations of fedora on separate partitions on my main hard drive (not logical volumes). When I was told to reboot and that the upgrade would continue, I rebooted and allowed it to do it's thing. After waiting another hour or so, I was told that it was done, and lo and behold... my main system had been destroyed, as preupgrade decided to upgrade not the partition from which I had run it and which I had indicated to have upgraded, but another partition, the one that housed my failsafe system, in case something should go wrong!
As a result, 2 separate installations of fedora on 2 separate partitions had been irrevocably destroyed in one fell swoop and I was forced to download the installation DVD and reinstall from scratch anyway. The whole procedure cost me at least 6-8 hours of wasted time, as well as around 20 GB of wasted downloading that I ended up simply deleting and overwriting.
There is a lot to be said for a clean install to a spare partition.
On 12/20/2009 04:21 PM, Petrus de Calguarium wrote:
Anne Wilson wrote:
Any ideas?
Last time I tried preupgrade, I made sure to update all of my system as required, even uninstalled some things from rpmfusion, etc., just to make sure there would be no complications, and then spent a lot of time having preupgrade download all of the updates to my entire system.
I always have 2 or 3 installations of fedora on separate partitions on my main hard drive (not logical volumes). When I was told to reboot and that the upgrade would continue, I rebooted and allowed it to do it's thing. After waiting another hour or so, I was told that it was done, and lo and behold... my main system had been destroyed, as preupgrade decided to upgrade not the partition from which I had run it and which I had indicated to have upgraded, but another partition, the one that housed my failsafe system, in case something should go wrong!
As a result, 2 separate installations of fedora on 2 separate partitions had been irrevocably destroyed in one fell swoop and I was forced to download the installation DVD and reinstall from scratch anyway. The whole procedure cost me at least 6-8 hours of wasted time, as well as around 20 GB of wasted downloading that I ended up simply deleting and overwriting.
There is a lot to be said for a clean install to a spare partition.
I usually have good luck using yum to upgrade to a new release. Can't remember the last time I had any issues.
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
Petrus de Calguarium wrote:
After waiting another hour or so, I was told that it was done, and lo and behold... my main system had been destroyed, as preupgrade decided to upgrade not the partition from which I had run it and which I had indicated to have upgraded, but another partition, the one that housed my failsafe system, in case something should go wrong!
Looks like this is a usecase they didn't test for. Have you filed a bug?
Kevin Kofler
On Sunday 20 December 2009 20:21:54 Petrus de Calguarium wrote:
Anne Wilson wrote:
Any ideas?
Last time I tried preupgrade, I made sure to update all of my system as required, even uninstalled some things from rpmfusion, etc., just to make sure there would be no complications, and then spent a lot of time having preupgrade download all of the updates to my entire system.
I did an update less than an hour before attempting the upgrade.
There is a lot to be said for a clean install to a spare partition.
Although I don't have the luxury of space for an extra partition, a clean install has been my practice in the past - and after this, probably will be again.
Anne
On Sunday 20 December 2009 20:01:35 Anne Wilson wrote:
Well, it finally finished, just as I'd begun to think it was stuck. Unfortunately it booted to a black screen. I tried several times to boot with an edited grub entry, without success. This last time it suddenly started up a blue screen with the Fedora infinity sign - and I thought I was winning - but it's still sitting there, a black screen with a flashing cursor at the top left. If I don't crack this soon I'll end up wiping it and installing from disk.
Later - well, at least I got as far as a text login. Now I have to try to get the display working.
First things first, /var/log/Xorg.0.log should tell you what is wrong with X.
Second, what does cat /etc/fedora-release says?
system-config-display is not installed. Yum tells me that it can't retrieve repository metadata (repomd.xml) for repository:fedora. I have already disabled adobe repo and ATrpms repo, and I guess that it's going to fail on all the others too, by the sound of it. Any ideas?
Assuming you are not running rawhide I suggest to clean the metadata for yum:
yum clean metadata
then if the problem with fedora repo still persists you can try to comment the mirrorlist line (add a # at begin) and uncomment the above line of baseurl.
Another possible option is to move the mirrorlist from https to http. FWIW the last two options are fallback moves and I don't recommend them for general purpose, in one or other occasion for update purposes I had to play with them to get the system to a working state from where all worked.
Anne
On Sunday 20 December 2009 23:22:43 José Matos wrote:
On Sunday 20 December 2009 20:01:35 Anne Wilson wrote:
Well, it finally finished, just as I'd begun to think it was stuck. Unfortunately it booted to a black screen. I tried several times to boot with an edited grub entry, without success. This last time it suddenly started up a blue screen with the Fedora infinity sign - and I thought I was winning - but it's still sitting there, a black screen with a flashing cursor at the top left. If I don't crack this soon I'll end up wiping it and installing from disk.
Later - well, at least I got as far as a text login. Now I have to try to get the display working.
First things first, /var/log/Xorg.0.log should tell you what is wrong with X.
Hundreds of lines, so I don't imagine you want me to paste it all. It looks perfectly OK to me. It says that it is ATi, is using the ati driver, and there are quite a few lines setting up RADEON. It ends with
(II) GLX: Initialized DRI2 GL provider for screen 0 (II) RADEON(0): Setting screen physical size to 330 x 211
Second, what does cat /etc/fedora-release says?
Fedora release 12 (Constantine)
system-config-display is not installed. Yum tells me that it can't retrieve repository metadata (repomd.xml) for repository:fedora. I have already disabled adobe repo and ATrpms repo, and I guess that it's going to fail on all the others too, by the sound of it. Any ideas?
Assuming you are not running rawhide I suggest to clean the metadata for yum:
yum clean metadata
Done.
then if the problem with fedora repo still persists you can try to comment the mirrorlist line (add a # at begin) and uncomment the above line of baseurl.
Done.
Another possible option is to move the mirrorlist from https to http. FWIW the last two options are fallback moves and I don't recommend them for general purpose, in one or other occasion for update purposes I had to play with them to get the system to a working state from where all worked.
I didn't do this one, since the baseurl didn't work. It says [Errno 14] PYCURL ERROR 6 - "" but it returns that very quickly, and I doubt if it had time to actually try a connection.
I suspected the network connection. I've run system-config-network, and that looked fine, so I changed it to dhcp and tried that. That didn't work either.
I'm sure I could figure this sort of thing out eventually, but not having X does make things that much slower.
Anne
On 12/21/2009 08:34 AM, Anne Wilson wrote: <snip>
I didn't do this one, since the baseurl didn't work. It says [Errno 14] PYCURL ERROR 6 - "" but it returns that very quickly, and I doubt if it had time to actually try a connection.
I suspected the network connection. I've run system-config-network, and that looked fine, so I changed it to dhcp and tried that. That didn't work either.
I'm sure I could figure this sort of thing out eventually, but not having X does make things that much slower.
What does ifconfig show?
Anne
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Monday 21 December 2009 12:46:06 Patrick Boutilier wrote:
What does ifconfig show?
Hmm - not good. No ipv4 address for either cabled or wireless. I haven't tried to do anything with the wireless part - I know I need firmware first.
I ran system-config-network again, and re-set it to static ip, then restarted the network service.
Now running ifconfig shows only the loopback stanza. Ping tells me that the network is unreachable.
Funny - I've been using Linux for almost 8 years, and never had an internet problem before - in fact I got it working with RH5, in my early experimentation days, some 10 year ago.
Anne
On 12/21/2009 09:03 AM, Anne Wilson wrote:
On Monday 21 December 2009 12:46:06 Patrick Boutilier wrote:
What does ifconfig show?
Hmm - not good. No ipv4 address for either cabled or wireless. I haven't tried to do anything with the wireless part - I know I need firmware first.
I ran system-config-network again, and re-set it to static ip, then restarted the network service.
Now running ifconfig shows only the loopback stanza. Ping tells me that the network is unreachable.
Funny - I've been using Linux for almost 8 years, and never had an internet problem before - in fact I got it working with RH5, in my early experimentation days, some 10 year ago.
If you know an IP you can use on your network try something like this:
ifcfg eth0 ip/mask route add default gw "gateway ip"
Anne
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Monday 21 December 2009 13:07:03 Patrick Boutilier wrote:
On 12/21/2009 09:03 AM, Anne Wilson wrote:
On Monday 21 December 2009 12:46:06 Patrick Boutilier wrote:
What does ifconfig show?
Hmm - not good. No ipv4 address for either cabled or wireless. I haven't tried to do anything with the wireless part - I know I need firmware first.
I ran system-config-network again, and re-set it to static ip, then restarted the network service.
Now running ifconfig shows only the loopback stanza. Ping tells me that the network is unreachable.
Funny - I've been using Linux for almost 8 years, and never had an internet problem before - in fact I got it working with RH5, in my early experimentation days, some 10 year ago.
If you know an IP you can use on your network try something like this:
ifcfg eth0 ip/mask route add default gw "gateway ip"
I presume that is all in one command, with the actual gateway ip in quotes?
That returns
Peer address with non-trivial netmask
When restarting the network service it brings up the loopback interface, then
Bringing up interface Auto_Lydgatex: WARNING: All config files need .conf: /etc/modprobe.d/garmintools, it will be ignored in a future relase. Device Auto_Lydgatex does not seem to be present, delaying initialization
This seems to be referring to my wireless device, which is not yet set up. There is simply no mention of the cabled connection.
I've checked /etc/sysconfig/networking/devices/ifcfg-eth1 and it is set to dhcp. The DNS entries look fine, but I see no reference to the gateway or to the netmask.
Got it! I added those two lines, and restarting the network queried for an address and got the expected one.
Installed system-config-display and ran it. Rebooted and - black screen, white rectangular cursor!
It looks as though I might have to find my old F11 disks and give up altogether on F12.
Anne
On Monday 21 December 2009 14:04:40 Anne Wilson wrote:
Installed system-config-display and ran it. Rebooted and - black screen, white rectangular cursor!
It looks as though I might have to find my old F11 disks and give up altogether on F12.
During one of my efforts I noticed a message to the effect that kstartupconfig4 seems to be missing. I didn't see the whole of the message, as the text was large and the box small, with no way to get at the rest. Maybe this is part of the problem.
Half of me wants to go on fighting this - it's always good to learn - and the other half says that I should stop wasting time and either try a clean install or go back to F11.
Anne
2009/12/21 Anne Wilson cannewilson@googlemail.com:
On Monday 21 December 2009 14:04:40 Anne Wilson wrote:
Installed system-config-display and ran it. Rebooted and - black screen, white rectangular cursor!
It looks as though I might have to find my old F11 disks and give up altogether on F12.
During one of my efforts I noticed a message to the effect that kstartupconfig4 seems to be missing. I didn't see the whole of the message, as the text was large and the box small, with no way to get at the rest. Maybe this is part of the problem.
Hi Anne,
kstartupconfig4 is part of kdebase-workspace. A least in rawhide. You can use "yum provides kstartupconfig4" to find the right version.
Martin Kho
Half of me wants to go on fighting this - it's always good to learn - and the other half says that I should stop wasting time and either try a clean install or go back to F11.
Anne
New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
On Monday 21 December 2009 16:09:47 Martin Kho wrote:
Half of me wants to go on fighting this - it's always good to learn - and the other half says that I should stop wasting time and either try a clean install or go back to F11.
Well I couldn't put off the decision for ever, so I checked with the Live CD - no problem. Then I tried to use to DVD to rescue the new install - nothing doing. Finally, I decided I can't really spare any more time, so I reformatted / and reinstalled. I'm back into the laptop, and it just remains to check that everything is configured correctly. (pinentry, for instance, doesn't seem to be working at the moment).
Thanks to all who tried to help.
Anne
On Monday 21 December 2009 12:46:06 Patrick Boutilier wrote:
What does ifconfig show?
FWIW, the device is Broadcom Corp. NetExtreme BCM5788 Gigabit Ethernet. For some reason it's registered as eth1, with the wireless at eth0 - but it was like that under F11 too.
Anne
-
Anne Wilson -
Eelko Berkenpies -
José Abílio Matos -
Kevin Kofler -
Martin Kho -
Patrick Boutilier -
Petrus de Calguarium