On 11/03/2010 10:03 PM, Heiko Baums wrote:
> Am Wed, 03 Nov 2010 20:57:35 -0500
> schrieb "David C. Rankin" :
>
>> I think that is exactly the understanding I got from Thomas, and it
>> makes an uncanny amount of sense. Though it doesn't have a 100%
>> correlation, it does explain why just about e
Am Wed, 03 Nov 2010 20:57:35 -0500
schrieb "David C. Rankin" :
> I think that is exactly the understanding I got from Thomas, and it
> makes an uncanny amount of sense. Though it doesn't have a 100%
> correlation, it does explain why just about ever-other kernel has
> exhibited this problem.
>
>
On 11/03/2010 06:50 PM, Norbert Zeh wrote:
> Aah, it just hit me: the problem may in fact be fairly random in that it
> may depend on where the initramfs is stored. So, if the BIOS is broken,
> you may be lucky to be able to boot under one kernel, and the next
> upgrade places things in a place on
Norbert Zeh [2010.11.03 2043 -0300]:
> Thomas Bächler [2010.11.04 0028 +0100]:
> > Am 03.11.2010 23:23, schrieb David C. Rankin:
> > > As mentioned, I have the same boot failure with 2.6.36-3 (grub Error
> > > 24:)
> > > However, I have received the first bit of feedback from the dm-devel list.
Am 04.11.2010 00:42, schrieb David C. Rankin:
> Now that is what I didn't understand... If this is a BIOS issue, then we may
> just be hosed. What always makes me wonder is why it works fine with some
> kernels and not others. It isn't inconsistent with any 1 kernel. If a kernel-A
> boots - then it
Thomas Bächler [2010.11.04 0028 +0100]:
> Am 03.11.2010 23:23, schrieb David C. Rankin:
> > As mentioned, I have the same boot failure with 2.6.36-3 (grub Error
> > 24:)
> > However, I have received the first bit of feedback from the dm-devel list.
>
> You don't seem to understand at all. The
On 11/03/2010 06:28 PM, Thomas Bächler wrote:
> You don't seem to understand at all. There is NOTHING the dm-devel guys,
> we, or you for that matter can do about this. There is no problem with
> Linux accessing or activating your dmraid.
>
> If grub fails to access the partition properly, then yo
Am 03.11.2010 23:23, schrieb David C. Rankin:
> As mentioned, I have the same boot failure with 2.6.36-3 (grub Error
> 24:)
> However, I have received the first bit of feedback from the dm-devel list.
You don't seem to understand at all. There is NOTHING the dm-devel guys,
we, or you for th
On 11/01/2010 01:47 PM, Tobias Powalowski wrote:
> Hi guys,
> please signoff 2.6.36 series for both arches
> and give feedback if
> real issues arise.
>
> greetings
> tpowa
Tobias,
Per the suggestions of the dm-devel guys, I have tested with both
libata.ignore_hpa=0 (default) and libata
On 11/01/2010 01:47 PM, Tobias Powalowski wrote:
> Hi guys,
> please signoff 2.6.36 series for both arches
> and give feedback if
> real issues arise.
>
>
> greetings
> tpowa
Tobias,
As mentioned, I have the same boot failure with 2.6.36-3 (grub Error
24:)
However, I have received the
Tobias, all
Checking the testing kernel on the box that won't boot with 2.6.35.8-1,
I
installed the following:
kernel26-2.6.36-3 kernel26-docs-2.6.36-3 kernel26-headers-2.6.36-3
nvidia-260.19.12-2
booting gives the same:
Booting 'Arch Linux on Archangel'
root (hd1,5)
Files
11 matches
Mail list logo
