Thx a lot Paul,
this morning i noticed there was some kind of issue on my old initrd which
works fine for 2.6 kernels, so created a new initrd which works fine and
let me to boot into GNU/Gentoo Linux with same 3.5 bzImage.
Gonna check if the issue came from mdadm, thx :)
2012/10/26 Paul Hartman
On Fri, Oct 26, 2012 at 3:36 AM, Pau Peris wrote:
> Hi,
>
>
> i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
> migrated from a 2.6 kernel to a 3.5.
>
>
> As my HD's are on raid 0 mode i use a custom initrd file in order to be able
> to boot. While kernel 2.6 is able to bo
Hi,
thanks a lot for both answers.
I've just checked my kernel config and CONFIG_SCSI_SCAN_ASYNC is not setted
so gonna take a look at it all with "set -x".
Thanks :)
2012/10/26 J. Roeleveld
> Pau Peris wrote:
>>
>> Hi,
>>
>>
>> i'm running GNU/Gentoo Linux with a custom compiled kernel and
Pau Peris wrote:
>Hi,
>
>
>i'm running GNU/Gentoo Linux with a custom compiled kernel and i've
>just
>migrated from a 2.6 kernel to a 3.5.
>
>
>As my HD's are on raid 0 mode i use a custom initrd file in order to be
>able to boot. While kernel 2.6 is able to boot without problems the new
>3.5
>co
On Fri, 26 Oct 2012 10:36:38 +0200, Pau Peris wrote:
> As my HD's are on raid 0 mode i use a custom initrd file in order to be
> able to boot. While kernel 2.6 is able to boot without problems the new
> 3.5 compiled kernel fails to boot complaining about "no block devices
> found". After taking a
Hi,
i'm running GNU/Gentoo Linux with a custom compiled kernel and i've just
migrated from a 2.6 kernel to a 3.5.
As my HD's are on raid 0 mode i use a custom initrd file in order to be
able to boot. While kernel 2.6 is able to boot without problems the new 3.5
compiled kernel fails to boot com
6 matches
Mail list logo
