On Wed, Jan 16, 2013 at 09:42:37PM -0500, Matthew Miller wrote: > On Thu, Jan 17, 2013 at 02:59:35AM +0100, Suvayu Ali wrote: > > I would recommend not to use fedup. I'm facing a lot of troubles after > > going the fedup route. Although not officially supported, you could try > > upgrading via yum. It has been reliably working for people across > > multiple releases. > > It would be very helpful if you could report those troubles. Otherwise, it's > hard to make it better. > I did plan to report it, but I have some questions before I collect all the information; maybe someone here can help. These are the issues I have: 1. I have been using grub. This ThinkPad have been upgraded through all the releases since F14, I didn't think worth the effort to switch to grub2 since everything worked well for me. After using fedup, I cannot edit the entries or the kernel arguments anymore. Trying to do that, corrupts the line (display only). I can't even move along the line consistently (cursor keys, home, end, nothing works). If I blindly type something and accept it with RET, it is ignored too. This makes debugging very inconvenient. 2. Apart from this I found fedup messed with a couple of daemons (which were working fine with F17), and now I am getting warning emails from systemd. Since most of these are non-critical I just turned them off. 3. With the F18 kernel (3.7.2-201.fc18.x86_64), my screen gets corrupted, and I can't see anything. I realise this is not a fedup issue, probably just a bad kernel. This is even before the gdm login screen appears. So far the only way to boot with this kernel is to use nomodeset (which comes with its own caveats of course). I have tried rebuilding the initrd with dracut with no luck. 4. Again, this is not a fedup issue; I'm having power management issues. For example, while waking up from sleep (by opening the lid) it sometime goes back to sleep again and I have to manually press the power button. Some of my power management settings about what to do when on AC power or battery are also ignored. Problem (2) is not important enough for me to investigate, but I consider (1) to be a severe regression. However I'm not sure how I can debug and add useful information to any bug report, the same goes for (3). With (4) it could just be an issue with the power management application for my desktop (XFCE). Any suggestions about how to go about debugging (1) and (3) are very welcome. Cheers, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
