On 11/01/2010 04:56 PM, Thomas Bächler wrote:
> These error are semi-random, they probably depend on where the kernel
> and initramfs files are physically located in the file system. It seems
> that about every second kernel works for you.
>
> Grub (and all other bootloaders for that matter) use B
On 11/01/2010 04:01 PM, Heiko Baums wrote:
> Have you made a complete system update with pacman -Syu and
> particularly updated lvm2 in case you are using this?
>
> Heiko
>
Thanks Heiko,
Yes, I've done the complete system update with pacman -Syu. (don't use
lvm2,
but yes it was updated
Am 01.11.2010 21:35, schrieb David C. Rankin:
> On 11/01/2010 03:22 PM, David C. Rankin wrote:
>> We'll see what the dmraid devs have to say. This seems to only effect my
>> jmicron
>> controller based box. The other boxes seem OK. So maybe it's a firware dmraid
>> error that gets tripped dependin
Am Mon, 01 Nov 2010 15:35:56 -0500
schrieb "David C. Rankin" :
> On 11/01/2010 03:22 PM, David C. Rankin wrote:
> > We'll see what the dmraid devs have to say. This seems to only
> > effect my jmicron controller based box. The other boxes seem OK. So
> > maybe it's a firware dmraid error that gets
On 11/01/2010 03:22 PM, David C. Rankin wrote:
> We'll see what the dmraid devs have to say. This seems to only effect my
> jmicron
> controller based box. The other boxes seem OK. So maybe it's a firware dmraid
> error that gets tripped depending the way the kernel loads the dmraid module??
> Who
On 11/01/2010 01:39 PM, Tobias Powalowski wrote:
> Well i'm not sure what error 24 is, but dmraid can be really complicated.
> I would recommend you write the dmraid authors from fedora, i'm sure it's a
> grub vs. dmraid issue which we cannot solve.
>
> greetings
> tpowa
Will do and I'll report
Am Mon, 1 Nov 2010 19:39:18 +0100
schrieb Tobias Powalowski :
> Am Montag 01 November 2010 schrieb David C. Rankin:
> > On 10/31/2010 04:32 PM, Thomas Bächler wrote:
> > > Am 31.10.2010 22:00, schrieb David C. Rankin:
> > >> >Updated an x86_64 box to 2.6.35.8-1 and the boot hangs
> > >> >
Am Montag 01 November 2010 schrieb David C. Rankin:
> On 10/31/2010 04:32 PM, Thomas Bächler wrote:
> > Am 31.10.2010 22:00, schrieb David C. Rankin:
> >> > Updated an x86_64 box to 2.6.35.8-1 and the boot hangs at the very
> >> > start with
> >> >
> >> > the following error:
> >> >
> >> > Boot
On 10/31/2010 04:32 PM, Thomas Bächler wrote:
> Am 31.10.2010 22:00, schrieb David C. Rankin:
>> >Updated an x86_64 box to 2.6.35.8-1 and the boot hangs at the very
>> > start with
>> > the following error:
>> >
>> > Booting 'Arch Linux on Archangel'
>> >
>> > root (hd1,5)
>> > Filesystem
Am 31.10.2010 22:00, schrieb David C. Rankin:
> Updated an x86_64 box to 2.6.35.8-1 and the boot hangs at the very
> start with
> the following error:
>
> Booting 'Arch Linux on Archangel'
>
> root (hd1,5)
> Filesystem type is ext2fs, Partition type 0x83
> Kernel /vmlinuz26 root=/dev/map
On 10/31/2010 12:55 AM, Tobias Powalowski wrote:
> Upstream update. This package is NOT in testing (2.6.35 currently
> resides there), but at:
> http://dev.archlinux.org/~tpowa/kernel26/
>
> please signoff for both arches.
>
> greetings
> tpowa
Tobias,
Updated an x86_64 box to 2.6.35.8-
Upstream update. This package is NOT in testing (2.6.35 currently
resides there), but at:
http://dev.archlinux.org/~tpowa/kernel26/
please signoff for both arches.
greetings
tpowa
--
Tobias
Powalowski
Archlinux Developer & Package Maintainer
(tpowa)
http://www.archlinux.org
tp...@archlinux.org
12 matches
Mail list logo
