LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   AMD Sempron boot problems - debian (https://www.linuxquestions.org/questions/linux-hardware-18/amd-sempron-boot-problems-debian-364449/)

renski 09-18-2005 05:40 AM

AMD Sempron boot problems - debian
 
I recently changed my motherboard/cpu/ram to an AMD Sempron 2600+ .. i'm using debian 3.1 w/ the debian kernel image 2.4.26-1-386 (from previous install).

That boots okay.. but whenever I try to install a new kernel of any other kind it won't boot. I'm trying to build a custom 2.6 kernel, I've tried enabling i386, x86 support, k7 and k8 support (all at different times) and none of them will work.

When I boot it just stops at "boot" .. like it sets the filesystem type, finds the kernel, then just stops.. before even detecting the cpu.

Are there any special options i should be selecting in the kernel setup for this processor?

Emerson 09-19-2005 02:37 PM

You probably want to boot it without initrd. If this is the case you have to compile all essential (needed to boot) hardware support into kernel. I think your problem is not CPU. Generic i386 should work with every PC CPU.

renski 09-19-2005 10:25 PM

I'll give that a go when I get home.. I understand that with a custom built kernel that something is probably missing, but that doesn't explain why the debian image kernels won't boot.. they include absolutely every possible driver... the box is actually using an exiting debian kernel, 2.4.26-i386 .. but if i try and install any other kernel image it just won't boot.

Also this is grub boot loader

Emerson 09-20-2005 05:06 AM

When you try to boot with some foreign generic kernel, the chances are initrd is not working. This means necessary modules for booting are not loaded and boot will stop. Yes, they include every possible driver, but as modules.

renski 09-20-2005 11:26 PM

I tried booting without an initrd and it still wouldn't boot

Electro 09-21-2005 04:19 AM

You need to make sure ramdisk and initrd is compiled as built-in, but not as modules. Also make sure you set your chipset as built-in. The chipset can be set as modules but it can be pain in the ass to find the names of the modules to include in the ramdisk file. Next make sure you select PIIX4 as built-in or else DMA will never work. This can also be set as module but settings chipsets and PIIX4 as modules does reduce the performance to some degree.

I suggest using at least a vanialla kernel version 2.6.12 because it fixes a lot of problems and has more support for today's systems. Using the latest stable kernel version is fine too. Kernel version 2.6.x provides better performance than 2.4.x kernels.

Configuring the kernel does take a long time. You should take the time to set and look over the options before going to the next step. If you are using kernel version 2.6.x, all you do to compile is make && make modules_install. After it is done compiling and copying the modules to /lib/modules/, find bzImage in the kernel source code directory and copy it to the /boot directory. Next go into /boot and run mkinitrd to make a ramdisk file that may need to include required modules to boot up Linux. Add an entry in the bootloader. Check over some things (is there a directory named /initrd and boot configs are correct) and reboot.


All times are GMT -5. The time now is 04:18 AM.