-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Sat, Jan 02, 2010 at 05:26:38AM +0100, Heiko Baums wrote:
> This has nothing to do with my kernel panics which were fixed by just
> upgrading to [testing] and didn't came back when downgrading back to
> [core].
>
> I don't know what vbe is for
Am Fri, 1 Jan 2010 21:01:07 -0700
schrieb Steve Holmes :
> I think I am in much better shape now. I managed to upgrade all
> kernel packages and speakup but had to modify my grub.cfg so all boots
> now with latest packages. What I have been using is kernel parameters
> to give me the 128x160 con
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I think I am in much better shape now. I managed to upgrade all
kernel packages and speakup but had to modify my grub.cfg so all boots
now with latest packages. What I have been using is kernel parameters
to give me the 128x160 console but then
Am Thu, 31 Dec 2009 15:49:51 +0100
schrieb Heiko Baums :
> Forgot to say that the kernel panic happened with
> kernel26-fallback.img, too. And the fallback image hasn't
> autodetection.
>
> I'm currently downgrading to [core] each package one by one and see if
> and when the kernel panic reappear
Am Thu, 31 Dec 2009 10:50:34 +0100
schrieb Tobias Powalowski :
> You could try to add all needed modules(filesystem,controllers etc.)
> to MODULES= array in initcpio.conf, perhaps the autodetection is not
> working for some reason.
> Just a guess,
> greetings
> tpowa
Forgot to say that the kernel
Am Thu, 31 Dec 2009 10:50:34 +0100
schrieb Tobias Powalowski :
> You could try to add all needed modules(filesystem,controllers etc.)
> to MODULES= array in initcpio.conf, perhaps the autodetection is not
> working for some reason.
> Just a guess,
> greetings
> tpowa
I already tried this. Always
Am Donnerstag 31 Dezember 2009 schrieb Heiko Baums:
> Am Thu, 31 Dec 2009 12:01:26 +0800
>
> schrieb Ng Oon-Ee :
> > Seeing as some haven't had the same problem, perhaps some
> > investigation into the details of the systems which HAVE problems
> > (currently two on this ML thread) would be useful
On 12/31/2009 10:42 AM, Ionut Biru wrote:
On 12/31/2009 05:43 AM, Heiko Baums wrote:
Am Thu, 31 Dec 2009 04:37:48 +0100
schrieb Heiko Baums:
The problem occurs with mkinitcpio 0.5.26-1 from [core] but is fixed
with mkinitcpio 0.5.26-2 from [testing].
I don't know if only the mkinitcpio updat
On 12/31/2009 05:43 AM, Heiko Baums wrote:
Am Thu, 31 Dec 2009 04:37:48 +0100
schrieb Heiko Baums:
The problem occurs with mkinitcpio 0.5.26-1 from [core] but is fixed
with mkinitcpio 0.5.26-2 from [testing].
I don't know if only the mkinitcpio update fixed the issue or if there
were other pa
Am Thu, 31 Dec 2009 12:01:26 +0800
schrieb Ng Oon-Ee :
> Seeing as some haven't had the same problem, perhaps some
> investigation into the details of the systems which HAVE problems
> (currently two on this ML thread) would be useful?
but how to investigate? Which information do you need?
These
On Thu, 2009-12-31 at 04:35 +0100, Heiko Baums wrote:
> Am Thu, 31 Dec 2009 08:29:01 +0530
> schrieb Partha Chowdhury :
>
> > i just updated my system yesterday to kernel 2.6.32.2-2. I faced no
> > problem. It is running as usual.After reading your mail, i looked in
> > the pacman update log and f
Am Thu, 31 Dec 2009 04:37:48 +0100
schrieb Heiko Baums :
> The problem occurs with mkinitcpio 0.5.26-1 from [core] but is fixed
> with mkinitcpio 0.5.26-2 from [testing].
I don't know if only the mkinitcpio update fixed the issue or if there
were other package updates from [testing] necessary bec
Am Wed, 30 Dec 2009 20:24:24 -0700
schrieb Steve Holmes :
> I'll have to look to see if I have the same problem. I wonder why
> some people have been able to upgrade the kernel without incident and
> others are having the problem with the panic? What version of
> mkinitcpio is supposed to be in p
Am Thu, 31 Dec 2009 08:29:01 +0530
schrieb Partha Chowdhury :
> i just updated my system yesterday to kernel 2.6.32.2-2. I faced no
> problem. It is running as usual.After reading your mail, i looked in
> the pacman update log and found that only kernel and virtualbox were
> updated.Virtualbox is
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Thu, Dec 31, 2009 at 08:29:01AM +0530, Partha Chowdhury wrote:
> >
> i just updated my system yesterday to kernel 2.6.32.2-2. I faced no
> problem. It is running as usual.After reading your mail, i looked in the
> pacman update log and found t
On Wed, Dec 30, 2009 at 05:22:33PM +0100, Heiko Baums wrote:
> Hi,
>
> I already filed a bug report but thought it couldn't harm or even be
> good to post it to the mailing list, too.
>
> Since the update to kernel26 2.6.32.2-2 from [core] I can't boot this
> kernel anymore. I always get a kernel
Hi,
I already filed a bug report but thought it couldn't harm or even be
good to post it to the mailing list, too.
Since the update to kernel26 2.6.32.2-2 from [core] I can't boot this
kernel anymore. I always get a kernel panic with these messages:
Failed to execute /init
Kernel panic - not syn
17 matches
Mail list logo
