On Thu, Jul 14, 2005 at 08:41:03PM -0400, Gene Heskett wrote: > The real question seems to me, how did this new kernel get past > testing if it won't even boot? Thats now vmlinuz-2.6.12-1.1390_FC4, > the matching initrd, System.map etc. The .1-1369 seems to be ok if I > don't want to run X. The revelation this week seems to be that the livna nvidia rpm broke modprobe.conf on a number of installations. Did you have this installed by any chance ? The number of 'my initrd broke' bugs that got filed over the last month or so has really gone through the roof, and my current bet is that this is the cause for the bulk (if not all) of them. The kernels that get pushed out to updates do see testing by both myself, and users of the updates-testing branch. However, this doesn't cover every possible hardware combination out there. So the situation is.. not all people don't test the -testing updates, and then some folks complain that the updates that go out aren't tested. There's really nothing more that I can do to get things tested. Some updates even spend quite a while in -testing. (Sometimes, I even if they've spent too long in -testing). Dave
