On Sat, 12 Jan 2013 12:43:51 +, I wrote:
> Good idea - thank you - will give that a try.
> (Have already d/l the DVD.iso.)
Damn it, I've just realised that because I had chosen to d/l the
32-bit .iso (havng read of the futility of running 64-bit on a max 2GB
machine), I presumably cannot d
On Fri, 11 Jan 2013 19:03:52 -0600, R James wrote:
> You should be able to boot the Beta1 installation media and select the
> Upgrade option.
Good idea - thank you - will give that a try.
(Have already d/l the DVD.iso.)
--
/\/\aurice
On Fri, 11 Jan 2013 13:29:00 -0500, Frank Griffin wrote:
> It sounds like you don't really have the new packages installed.
Oh yes I have! I installed the offered s/w update:
glib v2.17
glibc-devel v2.17
meta-task v3
- before re-booting and then running the:
bootlo
On Fri, Jan 11, 2013 at 12:09 PM, Maurice Batey wrote:
>
> Is there any other way of getting back in again?
> (I had got quite fond of Mga3...)
You should be able to boot the Beta1 installation media and select the
Upgrade option.
It will go really fast because there's really nothing to upgrade
On Fri, 2013-01-11 at 18:09 +, Maurice Batey wrote:
> (2) Can no loonger boot using any of the ".img.old" initrd's.
>(They all give Kernel Panic)
Is it the same panic? I get a different panic after updating - Fixing
recursive fault but reboot is needed. Using noacpi is a worka
On 01/11/2013 01:09 PM, Maurice Batey wrote:
(1) Still got kernel panic when booting from normal Mga3 stanza.
(2) Can no loonger boot using any of the ".img.old" initrd's. (They
all give Kernel Panic)
It sounds like you don't really have the new packages installed. In
rebuilding all of you
On Thu, 10 Jan 2013 21:26:15 +0100, Olivier Blin wrote:
> You might need to run this command to update initrds:
> bootloader-config --action rebuild-initrds
OK - tried that. Terminal session log can be seen here:
https://dl.dropbox.com/u/10969499/bootloader-rebuild-initrds-log
On re-boot
On Thu, 2013-01-10 at 16:43 -0500, Frank Griffin wrote:
> Or just update to current cauldron, which includes the 3.8 kernel, the
> installation of which will rebuild the initrd.
I tried that and now have a system with 3.8 that will either
(1) boot to the first blob above the cauldron :-) and the
On 01/10/2013 03:26 PM, Olivier Blin wrote:
You might need to run this command to update initrds:
bootloader-config --action rebuild-initrds
Or just update to current cauldron, which includes the 3.8 kernel, the
installation of which will rebuild the initrd.
Maurice Batey writes:
> On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote:
>
>> bug 8614 for all this was just fixed.
>
> It says: "Fixed with: glibc-2.17-2.mga3 and util-linux-2.22.2-2.mga3"
>
> but in my (newly-recovered from Kernel Panic) Mga3-A2,
> MCC/SW/Update shows the following p
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote:
> bug 8614 for all this was just fixed.
It says: "Fixed with: glibc-2.17-2.mga3 and util-linux-2.22.2-2.mga3"
but in my (newly-recovered from Kernel Panic) Mga3-A2,
MCC/SW/Update shows the following packages available:
glib v2.17
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote:
> your
> menu.lst should already have a version-specific entry for it. Try booting
> that directly without modifying anything.
I've now tried all the 'mga3' stanzas (3.6.5-1, 3.7.0-1, 3.7.1-1), and
they all gave Kernel Panic.
--
/\/\aur
On Wed, 09 Jan 2013 19:13:14 +, I wrote:
> (replaced:)
> initrd /boot/initrd.imgwith
> initrd /boot/initrd-3-7-0-desktop-1-mga3.img
There were 2 errors there:
(1) "-mga3" should have been ".mga3"
(2) ".img" should have been ".img.old"
(I first tried with the ".old" affix, but wro
On Wed, 09 Jan 2013 19:26:04 +, Dick Gevers wrote:
> If you change menu.lst, you also have to execute /boot/grub/install.sh,
> else it does not have any effect.
My understanding of that aspect of GRUB2 is that one *can* change
menu.lst, but if the GRUB2 'config' file is not given the same c
On Wed, 09 Jan 2013 21:40:25 +0100, eatdirt wrote:
> Check for typos in the names. For instance you
> have one above: 3-7-0 instead of 3.7.0.
I was careful, but will check again.
(The typo may Have been when transcribing into posting to newsgroup
on different m/c.)
--
/\/\aurice
On Wed, 09 Jan 2013 14:35:41 -0500, Frank Griffin wrote:
> If this was a previous kernel installed on this partition, then your
> menu.lst should already have a version-specific entry for it.
The thougjht did occur to me also, but the one I tried also gave
kernel panic. Perhaps I should have t
Le 09/01/2013 20:26, Dick Gevers a écrit :
On Wed, 09 Jan 2013 19:13:14 +, Maurice Batey wrote about Re:
[Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c:
and - in menu.lst - replaced:
But although a reboot starts well, after 6 lines the action *hangs* at
the 'i
On 09/01/13 20:13, Maurice Batey wrote:
and - in menu.lst - replaced:
/boot/vmlinuzwith
/boot/vmlinuz-3.7-0-desktop-1.mga3
and
initrd /boot/initrd.imgwith
initrd /boot/initrd-3-7-0-desktop-1-mga3.img
in a clone of the 'official' (but kernel panic) stanza.
But although a
On 01/09/2013 02:26 PM, Dick Gevers wrote:
On Wed, 09 Jan 2013 19:13:14 +, Maurice Batey wrote about Re:
[Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c:
and - in menu.lst - replaced:
But although a reboot starts well, after 6 lines the action *hangs* at
the 'i
On Wed, 09 Jan 2013 19:13:14 +, Maurice Batey wrote about Re:
[Mageia-dev] Kernel Panic after latest Mageia-3-Alpha2 s/w update c:
>and - in menu.lst - replaced:
>But although a reboot starts well, after 6 lines the action *hangs* at
>the 'initrd' line.
If you change menu
On Wed, 09 Jan 2013 16:34:45 +0100, EatDirt wrote:
> initrd-3.6.5-tmb-desktop-3.mga3.img
>
> and I have also the kernel
>
> vmlinuz-3.6.5-tmb-desktop-3.mga3
OK - found /boot/initrd-3-7-0-desktop-1-mga3.img and
/boot/vmlinuz-3.7-0-desktop-1.mga3
(The latest (panicky) kernel
'Twas brillig, and Maurice Batey at 09/01/13 15:24 did gyre and gimble:
> On Wed, 09 Jan 2013 13:21:06 +, Colin Guthrie wrote:
>
>> If you are lucky you will have *.old initrds so just edit your grub prompt
>> to use initrd.img.old rather than initrd.img (via text mode in grub)
>
> Where ar
On 09/01/13 16:24, Maurice Batey wrote:
On Wed, 09 Jan 2013 13:21:06 +, Colin Guthrie wrote:
If you are lucky you will have *.old initrds so just edit your grub prompt
to use initrd.img.old rather than initrd.img (via text mode in grub)
Where are such initrd.img.old files found?
We a
On Wed, 09 Jan 2013 13:21:06 +, Colin Guthrie wrote:
> If you are lucky you will have *.old initrds so just edit your grub prompt
> to use initrd.img.old rather than initrd.img (via text mode in grub)
Where are such initrd.img.old files found?
(No such files anywhere in its menu.lst.)
--
'Twas brillig, and Maurice Batey at 09/01/13 13:00 did gyre and gimble:
> Is there really no way of rescuing my updated MGA3-cauldron
> installation from the Kernel Panic showstopper?
There are many ways...
If you are lucky you will have *.old initrds so just edit your grub
prompt to use initrd.i
On Tue, 08 Jan 2013 16:35:30 +, I wrote:
> Anyone know of a fix for the above, please?
Is there really no way of rescuing my updated MGA3-cauldron
installation from the Kernel Panic showstopper?
--
/\/\aurice
On Tue, 08 Jan 2013 17:41:22 +, Claire Robinson wrote:
> see
> the ML thread 'Boot borked cause procfs :(('
No - can't see that in here...
--
/\/\aurice
On 08/01/13 17:45, Liam R E Quin wrote:
> On Tue, 2013-01-08 at 17:41 +, Claire Robinson wrote:
>
>> It's actually Cauldron you're running Maurice. This issue is known, see
>> the ML thread 'Boot borked cause procfs :((' from earlier today.
>
> It's also in the 3.0 beta DVD, as I reported yes
On Tue, 2013-01-08 at 17:41 +, Claire Robinson wrote:
> It's actually Cauldron you're running Maurice. This issue is known, see
> the ML thread 'Boot borked cause procfs :((' from earlier today.
It's also in the 3.0 beta DVD, as I reported yesterday.
Liam
--
Liam Quin - XML Activity Lead,
On 08/01/13 16:53, Maurice Batey wrote:
> On Tue, 08 Jan 2013 16:35:30 +, I wrote:
>
>> Anyone know of a fix for the above,
>
> The Mageia-3-Alpha2 menu.lst is:
>
> timeout 10
> color black/cyan yellow/cyan
> gfxmenu (hd0,0)/boot/gfxmenu
> default 3
>
> title Mageia-3-Alpha2
> kernel (hd0
On Tue, 08 Jan 2013 16:35:30 +, I wrote:
> Anyone know of a fix for the above,
The Mageia-3-Alpha2 menu.lst is:
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 3
title Mageia-3-Alpha2
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=Mageia-3-Alpha2
root=UUID=50814013-9a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 08/01/2013 17:35, Maurice Batey a écrit :
> Trying Mageia-3-Alpha2 on a Samsung NC110 netbook and enjoying it,
> I today did a 720+ file s/w update.
>
> Result: When rebooting:
>
> "Kernel panic - not syncing Attempted to kill init! exitcode =
>
Trying Mageia-3-Alpha2 on a Samsung NC110 netbook and enjoying it, I
today did a 720+ file s/w update.
Result: When rebooting:
"Kernel panic - not syncing
Attempted to kill init! exitcode = 0x0100
Pid: 1, comm: init not tainted 3.7.1-desktop-1.mga3 #1"
I can access its root
33 matches
Mail list logo
