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 
builtin network and sound 
GF4 4200 64MB 
 
Lilo entry: 
 
image=/boot/vmlinuz-2.4.21 
        label=2421 
        root=/dev/hda1 
        read-only 
        optional 
        vga=normal 
        append=" quiet devfs=mount acpi=off nosmp ide0=ata100 hdc=ide-scsi" 
 
I panic just like everyone else in this thread. 
 
On Sat, 28 Jun 2003 23:14:53 +0200, Stefan van der Eijk wrote 
> 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 (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? 
> >> 
> >> regards, 
> >> 
> >> Stefan 
> >> 
> >>> --=-=-= 
> >>> 
> >>> * Tue Jun 24 2003 Juan Quintela <[EMAIL PROTECTED]> 1-1mdk 
> >>> 
> >>> - update cpufreq to 2.4.22-1 snapshot. 
> >>> - update bootsplash to 3.0.7 (make warly happy). 
> >>> - update andrea VM to rc8aa1. 
> >>> - acpi 20030523. 
> >>> - disabled several options - bcm4400 2.0.0 (thanks ronin). 
> >>> - 2.4.21-final. 
> >>> 
> >>> --=-=-= 
> >>> E: kernel-2.4.21-0.0.1mdk invalid-spec-name kernel-2.4.spec 
> >>> 
> >>> --=-=-= 
> >>> 
> >>> --=-=-= 
> >>>   
> >>> 
> > 

Reply via email to