Re: Why was a kernel-2.6.34 pushed to updates that had un-addressed bugs.
On 09/01/2010 09:12 PM, Rodd Clarkson wrote: On Thu, Sep 2, 2010 at 11:58 AM, Adam Williamson <awill...@redhat.com> wrote: On Thu, 2010-09-02 at 11:00 +1000, Rodd Clarkson wrote: > Hi all, > > Why was kernel-2.6.34.x pushed to updates in f13 when three people had > reported suspend issues with the kernel and no attempt was made to > address these issues. > > see: https://bugzilla.redhat.com/show_bug.cgi?id=615560 > > I > Rodd Because there are always suspend issues, kernel team doesn't consider suspend problems a blocker for release. Sure, my problem lies not it that fact that there are suspend issues, but in that no attempt was even made to address the suspend issues. My system suspends and resumes fine on f13 with the 2.6.33 kernels, so it isn't unreasonable to expect this functionality to continue on a stable release. It is however, perfectly reasonable to expect that having tried a kernel at the request of a fedora developer on fedora-test-list and then having filed a bug against said kernel reporting problems, that someone might actually have a few minutes required to actually ask a few more questions and try and address the problem. Otherwise, why did they ask for feedback if it was just to be ignored? Rodd Updating to this kernel stops my F13 system from booting. I have had to revert to the former kernel. I have tried it each day it is offered as an update with the same result all three times. If I can provide any particular useful information, let me know. Gerry Tool -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 alpha installation scrambles disk ids
On 08/31/2010 04:03 AM, Mike Chambers wrote: On Mon, 2010-08-30 at 22:52 -0500, Gerry Tool wrote: I have been trying to install F14 alpha. When I do, the hard drives are not identified as they have been in the past. I have two hard drives, one with 233GB and one with 149GB. l have a number of partitions on each drive with operating systems on them. The 233GB has always been identified as hd0 in the past. F14 alpha insists it is hd1 with the 149GB being hd0. The dev ids are also messed up. the 233GB has always been sda. Now, F14 evidently starts the sd numbers with one of the USB devices. I have a multi-card reader hard-wired inside the box, and it is apparently labelling its channels as sda - sdd. I have two external USB drives, which until I unplugged them were being identified as sde, sdf, moving the first (formerly second) harddrive up to sdg and the old sda to sdh. If I let the installation proceed, it seems to succeed, but I can not find a way to get the F14 alpha system to boot using my long-standing boot loader setup controlled by my current F13 partition. I have tried title Fedora 14 alpha rootnoverify (hd0,2) chainloader +1 using a variety of (hdx,y) attempts, and have also tried several variations of the grub.conf file in the new F14 alpha configuration. Dunno if this will help, but during install when it gets to the grub selection part, make sure it is the same hdd order as your bios has it listed and you can change it there too. Mike Thanks cornel and Mike for your answers. I finally succeeded in an install that boots by making sure the install partition was really the one I wanted, and then making sure the drives were in the correct bios order. I hope I will remember that in the future. Gerry -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 alpha installation scrambles disk ids
I have been trying to install F14 alpha. When I do, the hard drives are not identified as they have been in the past. I have two hard drives, one with 233GB and one with 149GB. l have a number of partitions on each drive with operating systems on them. The 233GB has always been identified as hd0 in the past. F14 alpha insists it is hd1 with the 149GB being hd0. The dev ids are also messed up. the 233GB has always been sda. Now, F14 evidently starts the sd numbers with one of the USB devices. I have a multi-card reader hard-wired inside the box, and it is apparently labelling its channels as sda - sdd. I have two external USB drives, which until I unplugged them were being identified as sde, sdf, moving the first (formerly second) harddrive up to sdg and the old sda to sdh. If I let the installation proceed, it seems to succeed, but I can not find a way to get the F14 alpha system to boot using my long-standing boot loader setup controlled by my current F13 partition. I have tried title Fedora 14 alpha rootnoverify (hd0,2) chainloader +1 using a variety of (hdx,y) attempts, and have also tried several variations of the grub.conf file in the new F14 alpha configuration. How can I tame this mess? Thanks, Gerry Tool -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
