It appears it isn't the CPU or the filesystem. I'm ReiserFS on / (which
contains /boot) and a AMD CPU.
Just to summarize my setup again:
2.0GHz Athlon-XP
512MB PC3000 RAM (dual channel)
MSI K7N2 Nforce2
120GB Maxtor 7200/2MB
/ reiserfs 8GB /dev/hda1
/export reiserfs 100GB /dev/hda6
bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Brinkman wrote:
> Another possibly related issue is that mdkkdm
> now refuses my valid user passwd, even after resetting it with
> 'passwd tom' (as root).
No, this is unrelated, and a known issue. I guess it should get a bug
report to make people
On Monday June 30 2003 09:10 am, Guillaume Rousse wrote:
> > I don't believe they're related either, ie, kernel and
> > devfsd. When I did manage to recover cooker (9.1 install +
> > resync with urpmi to current cooker), the new devfs failed to
> > provide scd0, loop, rtc, .. The only alternati
Am Mon, 2003-06-30 um 13.27 schrieb Till Kamppeter:
> For me it panics on 9.1, with the devfsd of 9.1.
>
> Till
>
> [EMAIL PROTECTED] wrote:
> > On Sat, 28 Jun 2003, Götz Waschk wrote:
> >
> > Haven´t updated in a while, but since devfsd seems also broken, doesn´t it
> > panic because of a
Ainsi parlait Tom Brinkman :
> On Monday June 30 2003 04:29 am, [EMAIL PROTECTED] wrote:
> > I had the same guess about the broken/nonexistent initrd image,
> > but at least on my box it is not related to a broken devfs,
> > because I only updated the Kernel not devfs. The last message I
> > can re
For me it panics on 9.1, with the devfsd of 9.1.
Till
[EMAIL PROTECTED] wrote:
On Sat, 28 Jun 2003, Götz Waschk wrote:
Haven´t updated in a while, but since devfsd seems also broken, doesn´t it
panic because of a broken/nonexsistant initrd image (due to failed
creation of it because of no l
On Monday June 30 2003 04:29 am, [EMAIL PROTECTED] wrote:
> I had the same guess about the broken/nonexistent initrd image,
> but at least on my box it is not related to a broken devfs,
> because I only updated the Kernel not devfs. The last message I
> can remember was "trying to kill init", sorry
Stefan van der Eijk wrote:
Have people been able to boot this kernel? On which CPU?
I guess it's not the CPU. Perhaps the filesystem?
I'm on ext3 (/boot and /)
On my Asus S8600 laptop I have four ext3 (including /, no extra
partition for /boot) and one swap partition on a 40 GB IDE hard disk.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Same problem with the standard kernel. (My first Kernel-Panic with
> Mandrake ever :-) The ugly thing about it: when trying to boot the old
> kernel (-18mdk), it panics too with the same error; the last thing I
> see is "try
I had the same guess about the broken/nonexistent initrd image, but at least on my box
it is not related to a broken devfs, because I only updated the Kernel not devfs. The
last message I can remember was "trying to kill init", sorry I cannot look what it
exactly was, because my laptop is at hom
Viestissä Sunnuntai 29. Kesäkuuta 2003 01:40, [EMAIL PROTECTED] kirjoitti:
> On Sat, 28 Jun 2003, Götz Waschk wrote:
> > Am Samstag, 28. Juni 2003, 13:28:14 Uhr MET, schrieb Stefan van der
Eijk:
> > > I guess everybody in this thread was trying to boot the kernel on an
> > > AMD based machine. Is
exactly the same symptoms on my box
filesystem is ext3 too, the other kernel was the updated -18mdk-kernel from Mdk9.1,
which does not want to boot anymore, too, so there is no easy way to get rid of the
catastrophic -0.0.1mdk-kernel.
On Sat, 28 Jun 2003, Götz Waschk wrote:
> Am Samstag, 28. Juni 2003, 13:28:14 Uhr MET, schrieb Stefan van der Eijk:
> > I guess everybody in this thread was trying to boot the kernel on an AMD
> > based machine. Is this correct?
>
> No, it also doesn't run on my P4 with an i845PE chipset. I have
Same problem with the standard kernel. (My first Kernel-Panic with Mandrake ever :-)
The ugly thing about it: when trying to boot the old kernel (-18mdk), it panics too
with the same error; the last thing I see is "trying to kill init" and some nice
lightshow on the keyboeard. My Machine is an O
> I'm on ext3 (/boot and /)
I'm also on ext3 for /boot and /, kernel-2.4.21-0.0.1mdk-1-1mdk worked for me, until I
uninstalled 2.4.21-rc1 ...
Now, when I boot with it, it prints lots of error and ends with something like :
"kernel attempted to kill init, aborting"
I'll reinstall kernel-2.4.21-0.
Stefan van der Eijk wrote:
I guess everybody in this thread was trying to boot the kernel on an
AMD based machine. Is this correct?
Have people been able to boot this kernel? On which CPU?
I guess it's not the CPU. Perhaps the filesystem?
I'm on ext3 (/boot and /)
Stefan
Stefan
This (enterp
Am Samstag, 28. Juni 2003, 13:28:14 Uhr MET, schrieb Stefan van der Eijk:
> I guess everybody in this thread was trying to boot the kernel on an AMD
> based machine. Is this correct?
No, it also doesn't run on my P4 with an i845PE chipset. I have
ordinary ext3 partitions.
--
What difference does
On Thu, 2003-06-26 at 07:12, Quel Qun wrote:
> On Wed, 2003-06-25 at 13:49, Stefan van der Eijk wrote:
> > This (enterprise-) kernel doesn't want to boot on my box (Asus NForce2,
> > AMD althonXP, 1.5Gb). It panics before init message is shown on the screen.
> >
> > Anybody else?
> >
Ordinary k
Stefan van der Eijk wrote:
I guess everybody in this thread was trying to boot the kernel on an AMD
based machine. Is this correct?
My Asus notebook (on which the kernel panics) has an Intel Pentium III
(mobile) processor.
Till
lördagen den 28 juni 2003 13.28 skrev Stefan van der Eijk:
> I guess everybody in this thread was trying to boot the kernel on an AMD
> based machine. Is this correct?
>
> Have people been able to boot this kernel? On which CPU?
Oops, I forgot to say..., I have a
AMD Athlon(tm) XP 1700+ on a Epox
On 2003-06-28(Sat) 13:28:14 +0200, Stefan van der Eijk wrote:
> I guess everybody in this thread was trying to boot the kernel on an AMD
> based machine. Is this correct?
>
> Have people been able to boot this kernel? On which CPU?
I've got the same error too, on a Pentium 3 mobile.
Abel
> St
> Have people been able to boot this kernel? On which CPU?
Yes, I use this new kernel with a AMD XP 1800+ and a ECS K7S5A motherboard.
I guess everybody in this thread was trying to boot the kernel on an AMD
based machine. Is this correct?
Have people been able to boot this kernel? On which CPU?
Stefan
This (enterprise-) kernel doesn't want to boot on my box (Asus
NForce2, AMD althonXP, 1.5Gb). It panics before init message i
I can verify this behaviour (panic on boot) on:
K7N2
NForce2
512MB
120GB Maxtor
ReiserFS on /
I actually hope there is a fix fairly soon, I just accidentially removed my
running kernel due to the versioning mix up of April/May. Anyone have the
previous kernel .rpm laying around?
On Thu, 26 J
- Original Message -
From: "Oden Eriksson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 2:01 PM
Subject: Re: [Cooker] Re: [CHRPM] kernel-2.4.21-0.0.1mdk-1-1mdk
> torsdagen den 26 juni 2003 14.51 skrev Tom Brinkman:
> > On Thurs
torsdagen den 26 juni 2003 14.51 skrev Tom Brinkman:
> On Thursday June 26 2003 12:12 am, Quel Qun wrote:
> > On Wed, 2003-06-25 at 13:49, Stefan van der Eijk wrote:
> > > This (enterprise-) kernel doesn't want to boot on my box (Asus
> > > NForce2, AMD althonXP, 1.5Gb). It panics before init messa
On Thursday June 26 2003 12:12 am, Quel Qun wrote:
> On Wed, 2003-06-25 at 13:49, Stefan van der Eijk wrote:
> > This (enterprise-) kernel doesn't want to boot on my box (Asus
> > NForce2, AMD althonXP, 1.5Gb). It panics before init message is
> > shown on the screen.
> >
> > Anybody else?
>
> Yep,
On Wed, 2003-06-25 at 13:49, Stefan van der Eijk wrote:
> This (enterprise-) kernel doesn't want to boot on my box (Asus NForce2,
> AMD althonXP, 1.5Gb). It panics before init message is shown on the screen.
>
> Anybody else?
>
Yep, the up kernel panics here too. It looks like it is when it trie
Same behaviour for the standard kernel on my Asus S8600 laptop (see some
hardware info below).
Till
--
[EMAIL PROTECTED] till]$ lspcidrake -v
unknown : Intel|82440MX CPU to I/O Controller [BRIDGE_HOST]
(vendor:80
29 matches
Mail list logo
