Quasi Custom Kernel Question??

Taikon · 09-26-2006, 08:57 PM

I made a new kernel using the 2.6.17.13 source and compiled most of my hardware as part of the kernel instead of a module because it just made sense at the time. I also changed the CPU option from 486 to K7 (I have an athlon xp so This should work I think feel free to correct me) and I boot all should be fine. Not so. Somehow I screwed up and I get

Code:

snd: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_mixer_oss: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
soundcore: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_seq_device: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_timer: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_seq: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_seq_midi_event: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
snd_seq_oss: version magic '2.6.17.13 mod_unload 486 gcc-3.4' should be '2.6.17.13 mod_unload K7 gcc-3.4'
input: AT Translated Set 2 keyboard as /class/input/input0

Except every line of dmesg is like that when I try to boot that kernel. Like I said I think this is because I complied into instead of built modules for the hardware and then changed from 486 to K7 but I can't figure out what I need to do to fix it like it is or what would allow me to use the K7 option and then it not happen again.

Any advice? (yes this is my first completely self made kernel)

gnashley · 09-27-2006, 09:19 AM

To lern about compiling a kernel, start by compiling a completely stock configuration, then make a few changes or only one.
Preferably use the 2.4 kernel so you don't have problems with the modules.
For 2.6 kernel, you need to install the 2.6 kernel modules. Hotplug is probably trying to load modules which you have hard-linked.

vharishankar · 09-27-2006, 11:19 AM

Also it's best to compile drivers as modules. Some drivers actually may not work if it's compiled into the kernel. For instance, agpgart - direct rendering and 3d acceleration only work if you have the agpgart module installed and not directly compiled into the kernel and sound drivers - alsaconf works only if it can find a driver module for your chipset.

Taikon · 09-27-2006, 03:36 PM

Okay so theres no real benefit to compiling drivers into the kernel as opposed to making them odules. Going on th is I should be able to basically just change the 1 option in my current working kernel from 486 over to k7 and everything be gravy? Or is it best to leave it at 486 for all intel amd processors that are single core? (don't remember if smp is under that same tree or not)

dive · 09-27-2006, 04:34 PM

The best thing is probably to try and see what works one or 2 steps at a time. You might find that actually some drivers *do* work built-in while others need to be modules and loaded at boot time.

Definitely make your cpu k7 if that's what you have. Then, if you know, change your chipset etc one stage at a time. But also make sure you've got a working kernel in /boot and in lilo.conf that you can boot up to if all goes tits up.

Old_Fogie · 09-27-2006, 09:24 PM

If I may just throw out to you my cheatsheet I have for myself for pc compiles on my AMD 2500 nforce 2 board recommendations:
-build in file systems as yes e.g built in to avoid making initrd
-config samba, nfs as module
-configure processor as k7 (also uncheck x86 fixups at boot
-CONFIG_CC_OPTIMIZE_FOR_SIZE=y <--you may want no here u had glib errors on your system there
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODULE_FORCE_UNLOAD=y
-CONFIG_PREEMPT=y
-CONFIG_PREEMPT_BKL=y
-CONFIG_HZ_1000=y
-CONFIG_HZ=1000
-CONFIG_HIGHMEM4G=y (assuming you have 1 gig or more, also use flat memory)
-CONFIG_HIGHPTE=y
-CONFIG_MATH_EMULATION=y
-CONFIG_MTRR=y (this needed for video dri)
-config agp as modules
-config sound yes...but the devices as modules. also keep OSS support as yes for backward compliance.

many amd boards have "apic" in addition to "acpi" and u should not confuse that with "acpi"

my board uses "i2c" for thermal

also in kernel hacking I've been using "4k stacks" for a long time on desktop pc and it really works well for me. I cannot use it on my old laptop tho, seems to break OSS sound and madwifi drivers so on that pc, which is AMD also, I use the default 8k stacks.

remember that you have ip/tables as modules too, i always forget that one. and lose firewall

many times I forget these, and they matter to me for my machine, as there is nothing worse than booting up a pc after you compile and you have no video, no penguin and ugly fonts
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_MDA_CONSOLE=m
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_7x14 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y