mdk10 Official

I recompiled my kernel for my laptop so it would boot. During the boot I see lots of this:

pcmcia_core: disagrees about version of symbol struct_module
ds: disagrees about version of symbol struct_module
orinoco_cs: disagrees about version of symbol struct_module
hermes: disagrees about version of symbol struct_module
orinoco: disagrees about version of symbol struct_module
pcmcia_core: disagrees about version of symbol struct_module
ds: disagrees about version of symbol struct_module
orinoco_cs: disagrees about version of symbol struct_module
soundcore: disagrees about version of symbol struct_module
snd: disagrees about version of symbol struct_module
soundcore: disagrees about version of symbol struct_module
snd: disagrees about version of symbol struct_module
soundcore: disagrees about version of symbol struct_module
sound: disagrees about version of symbol struct_module
uart401: disagrees about version of symbol struct_module
sb_lib: disagrees about version of symbol struct_module
sb: disagrees about version of symbol struct_module
ipv6: disagrees about version of symbol struct_module
spurious 8259A interrupt: IRQ7.

What does it all mean and how do I address it?

Steps to compile kernel were:
make bzImage
make modules
make modules_install
make install

Thank you in advance,
r

Did you clean before you compiled? As the modules might not have been rebuilt.

Yes, I did. I did a 'make mrproper'.

You might also want to check the installed modules. Try removing /lib/modules/2.6.3

( might end with -13 ). and reinstalling the kernel.

@leonscape,

Thanks for your help.

Now this is strange ...

In my mind this is all related, but I'll be glad to open another thread ...

I removed the /lib/modules/2.6* directories based on what I built. I then went to /usr/src/linux-2.6.3-13mdkcustom and rebuilt what I built last night. I then reinstalled bzImage & modules.

Last night I was able to boot but got the errors in mentioned before. NOW I am getting the kernel panic init= messages. I don't believe I changed anything other than reinstalling, but who knows. My /boot partition is ext3 (which I think is builtin to the new kernel). My /initrd directory is out there. Any ideas how I'm going backwards instead of forwards?

I'll be glad to attach any files than can help this newbie get farther.

thanks again,
r

What filesystem is / (root) and is it built into the kernel? Thats a common mistake, as you can't read /lib/modules to load the module for the root disk. The only filesystems you use that aren't usually built into the kernel, should only be remote ( SMD, NFS ) and removable ( UDF, iso9660 ).

/boot isn't a problem usually ( since the only thing is the kernel itself, and maybe a bootloader ).

All the filesystems are ext3. I have separate filesystems for /, /tmp, /home, /var, & /boot.

I'm rebuilding the kernel again as we speak. Unfortunately on the PII 333mhz it will take many hours. Before rebuilding, I did a 'make mrproper' and then a 'make defconfig', After which I edited the .config and made sure references to 'ext3' were marked as 'y' instead of 'm'.

Latest update ...

I think I'm a bit further but have now encountered another problem. When booting 2.6 the console display is blank. I can hear the disk humming and "proceeding". After inspecting the messages log the last line written is 'Proceeding to runlevel 6'. Unfortunately I didn't know it at the time because the display was blank . I had to boot to 2.4 to see it.

For kicks, I decided to do a 'make mrproper' and then 'make allconfigyes (or something)' just to see.
I'll post sometime tomorrow on that one...

A couple of things I learned along the way:
1) Don't try to build two kernels at the same time in separate directories unless one is sure the original directory references are removed. (that killed about 1 day)
2) When doing a 'make install' still do the /sbin/lilo step after it completes.

Runlevel 6 is reboot. Which means the system when down for a reboot, on startup thats a problem. Have you added framebuffers? as that could be a cause of fault, not all graphics cards ( Nvidia specifically ) like the new framebuffers.