Hi, I compiled the new 2.6.1. kernel yesterday on my slackware 9.1 box using my .config file from 2.4.22 kernel and make oldconfig. I viewed the new options and chose the ones I thought I needed. I then installed the kernel but fortunately kept an option for my 2.4.22 kernel in my lilo.conf file.

Now when I boot it works fine and there are no error messages, until the login prompt appears and I try to login as root or a user, it says "Login Incorrect". It then displays the prompt again and if I try to login as root or user it keeps displaying the same message.

I rebooted and loaded up my 2.4.22 kernel and was able to log in straight away. Does anyone have any ideas what may have caused this? I read all of the 2.6 kernel thread but thats nearly all about vga and framebuffers. I also searched all the forums here for "login incorrect" and no-one has had this problem with a kernel upgrade. So if anyone could help I'd be grateful.

thanks
johnny

It could possibly be a problem with the keyboard subsystem. I'm having some trouble getting my multimedia keys working, and while looking this up I've seen reports of keyboard errors, as the subsystem has changed a lot and some of it doesn't work like it used too.

Or I could be way off here...

Thanks leonscape, I 've did a google search for kernel 2.6 and keyboard errors but it didn't come up with anything useful.

I also tried plugging my keyboard in using the usb connector instead of the ps/2 one but I still have the same problem. doh!

It's definitely a keyboard issue, I tried typing the password in the user field to see if I could work out the problem, and when I press the shift key it inserts extra characters. I reloaded kernel 2.4.22 and used passwd to change my root password to all lowercase and it then allowed me to log in to the 2.6.1 kernel

Everything works fine except for the keyboard. Does anyone have any ideas? This is driving me nuts.

thanks

I've been trying to hack the atkbd.c file to get my keys working but no luck yet. I think its because ours are GB keyboards. Still the shift key shouldn't be messed with.

You could try a spare one for now. Or live with 2.4 until all this gets sorted out.

It sound's like ACPI!!

Since the kernel is a little more mature now, the keyboard issue has been resolved. I`ve used 2.6.xx on 2 different computers and both work great.

..and it smells like an old thread.

egag

Maybe means nothing, but to me it seems kinda crazy to copy the config file from 2.4 to 2.6.

If you copy the config file from 2.4 and then do a "make oldconfig" it reads and keeps all the old options which are still relevant to 2.6 and asks you which new options specific to 2.6 you`d like.

It saves a lot of time as you don`t have to reselect all the things you want again or hunt for the new options.

Except for things with changed names, for example.

Like the fb support always dies if you just make oldconfig
from a 2.4 to a 2.6 kernel.



Cheers,
Tink

This is why I'd think it would be crazy. There may be alot of similiarities between 2.4 and 2.6, but there is also alot different. I have no quams doing config file copies when going from say 2.6.13.1 to 2.6.13.2 but 2.4 to 2.6 sounds crazy to me.

I *do* do this, but always go through all the options manually
afterwards, using make menuconfig.


Cheers,
Tink