[arch-general] [signoff] kernel 126.96.36.199-3
C Anthony Risinger
anthony at extof.me
Sat Nov 27 07:30:26 CET 2010
On Fri, Nov 26, 2010 at 4:29 AM, Jan de Groot <jan at jgc.homeip.net> wrote:
> On Thu, 2010-11-25 at 18:36 -0600, David C. Rankin wrote:
>> You'da Man! kernel26 188.8.131.52-3 boot FINE on that whacky MSI based box. I don't
>> know if you know what changed, but if so, I'm dying to find out. After running
>> it by the Redhat dmraid (dm-devel) list, the kernel.org list, all I got back
>> were the ideas I passed on here, but no real answers....
>> I updated my primary box (Tyan based with nv dmraid) that had shown the the
>> weird drive initialization that caused the random read/write head excursions
>> that happened if the box didn't boot just right -- and it booted perfectly,
>> first try with kernel26 184.108.40.206-3. So I decided to give the MSI based box a
>> try. It too -- booted just fine!
> For that boot problem, you really should try grub2 instead of grub. Last
> week we had a bug on the bugtracker that looked like your bug, but with
> a regular installation with / on ext4. Grub couldn't boot it with the
> same error message as you're facing now and then. After switching to
> grub2, things worked fine.
> I think grub is bugged somehow with its ext3/ext4 drivers, causing
> issues like yours. With your current grub installation, every kernel
> update could result in a surprise.
could also try extlinux -- i have several systems using it with
nothing but success, and it's slightly less daunting than grub2 (not
to mention cool stuff like btrfs support... that's about to lead to
_managed_ KERNEL rollbacks under Archlinux in < 48hrs... *cough*
More information about the arch-general