hello there.

having some large problems with a new slack install and a kernel compile.
the new install boots just fine. all is well, so i go into /usr/src/linux configure my new kernel, and compile it with :

make dep ; make bzImage ; make modules ; make modules_install

everything goes well. no errors. so i copy the new kernel into /boot and update lilo.

so i try to boot this new kernel and i keep getting insmod problems, then my keyboard or mouse do not work.

the big thing is, i could also boot my original slackware kernel after just recompiling a new one, and i still recieve these errors.

i have tried disabling hotplug but this does not help.

very wierd. i had slack 9.1 installed prior to an accidental hard drive delete with no problems like this. has anyone experienced this? does anyone have any knowledge on why this would be happening (it really puzzles me that the original kernel boots with these errors after i compile a new one), or any help on how to fix?

peace.
neoninja

"(it really puzzles me that the original kernel boots with these errors after i compile a new one)"

By any chance do you have both the new and old kernels using the same modules in /lib/modules?


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

need more detail on errors....


from what you have posted we are unable to tell if you loading wrong drivers, right driver to many times, etc.. etc...

when i boot either of them, it gets to the agpgart modules, loads that fine, and then gives me about 3 insmod errors for every other module.

i believe the errors are unresolved symbol etc.

i will post the actual errors tommorow, as i will have to write them down and reboot into windows.

what i dont understand is how before i tried compiling this kernel, the original kernel worked, it loaded my keyboard etc. and after this even when i try booting the original i get all the same errors as the new kernel, as well as my keyboard and mouse not working. so the only was i can do maintenance on this is to boot the cd and chroot into the new environment.

the big thing is that i had a fully functional 9.1 install before, with my custom kernel, all options the same and i was having no problems.

anyways, if anyone can help that would be great, and i will get the actual errors posted.

it is very difficult to get these errors posted because once it boots it shows my login yes, but my keyboard or mouse do not work so it is not possible for me to scroll up to get all the error messages...
unless it logs them and i can access them from mounting the drive from the slack cd?

"what i dont understand is how before i tried compiling this kernel, the original kernel worked, it loaded my keyboard etc. and after this even when i try booting the original i get all the same errors as the new kernel"

You probably do not have two completely separate kernels. When you set up the second kernel you need two different kernels in /boot, two different modules directories in /lib/modules, and if you are using initrd then you need two different initrds in /boot.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites