Background: I'm attempting to move from the default i586 to Pentium4 CPU architecture for a bit of a speed and stability boost. I'm also looking at compiling the i8k module (Dell Inspiron 8XXX Access Direct keys) and hunting for the ACPI module that will allow the OS to detect my battery state. For now, I'm ONLY compiling the Pentium4 architecture change.

Operating System: SuSE 8.2

Steps:

1. Perform a full, clean install from FTP. System boots OK, log into system and move around, system working perfectly.

2. Exit out of X-Windows, change inittab's init to 3, reboot into the console.

3. cd /usr/src/linux

4. make menuconfig

5. I changed the system architecture from i586 to Pentium4, saved the .config and exited.

6. make dep

7. make clean

8. make bzImage

9. cp arch/i386/boot/bzImage /boot/vmlinuz.Pentium4

10. I edited my GRUB configuration file (menu.lst) with the new line; however, I did not create an initrd file; sources I've read have said that it's not necessary if the hard drive drivers are compiled into the kernel, which, according to makeconfig, they were.

11. Reboot.

12. Kernel panic after the NTFS driver attempts to mount my /windows/c drive. If necessary, I'll attempt to record the information and post it.

13. I reboot using my clean kernel and it works just fine.

Any ideas? I typically haven't had much trouble recompiling my kernel, but this Pentium4 architecture has just been kicking me around.

Thanks in advance!

-David

Which pentium 4 did you select? I ran a quick menuconfig and it looks like there are two options:

Pentium 4
Pentium 4(gcc>31)

I have just pentium 4 selected and haven't had any problems.

Humm, I only saw one and I was using the vanilla Pentium4.

I'm using a gentoo kernel but I can't imagine there being that big of differences in options.

Very possible it's user error; I've tried it with SuSE and RedHat; same problems. See anything wrong with my steps?

The only thing missing from normal recompiling is the
# make modules
# make modules_install

I'm not sure if that would make a difference but I always do that for good measure just in case. Other than that, I can't see any problems except for the fact that you're using SuSE.

*grins at the SuSE comment*

If it makes you feel better, I'm running Mandrake 9 at work. I tried Gentoo back when it was early, but with this being my production laptop, I didn't want to spend days compiling modules--plus with built-in ALSA, it plays nice with my SB Live from Dell. I'll give the modules lines a shot. Didn't think about that since I wasn't adding any... but good idea!

busbarn-

I recompiled with the modules and that really hosed everything. It panics immediately after processing through the first few modules. Do some modules not support 'pentium4' yet? (though, you said yours is working smooth.)

I would say wipe out your kernel that isn't working...just totally get rid of it and start over. I've had messed up kernels when I've tried to go back and do the module thing at a later time.

Here's an idea: in your new kernel did you include ntfs in the filesystems for the kernel to identify? Your original bad kernel was fine until it tried to mount your windows drive. Check and see if it's compiled in there.

As for some things freaking out, I know nvidia drivers and alsa drivers need to be reinstalled after recompiling your kernel.

I'll give that a shot. As for the drivers, I'm not using NVIDIA (ATI RAEDON), but I am using ALSA drivers.

Thanks!

-David

Okay, that seemed to work; however, the cdrom, ide-cd, and ide-scsi modules didn't seem to compile; however, I think I can resolve that. One question, on the version splash in the console (and in KDE control centre), shouldn't the i586 change to pentium4? It always has when I recompiled in prior versions. The Console says i586 and KDE shows i686. As long as the tweaks are active, I couldn't care less, but ... that's the reassurance I typically look at.

Past that, everything looks like it's operational.

Thanks!

-David

I have no idea about that. My kde control center says i686 and I haven'e bothered to look at version splash in the console. If your kernel is running and there aren't any errors, then I would say it's working for ya. I'm glad it's working for you. It's always nice to get things figured out and running smooth again. I guess I said all the right things since nobody else piped up eh?

Guess so! I haven't had time to fix the CD module problem, but yeah; everything's working smooth. Thanks!