Keyboard works during boot sequence, but not at login prompt

Keyboard works during boot sequence, but not at login prompt

Post by maldri » Wed, 21 Apr 2004 09:23:10



Is this weird?
I've tried multiple keyboards...
Now, I have changed the motherboard in the box...everything else works
fine (2 hd's, cdrom, floppy...)
When I'm prompted for things during boot (choosing kernel at LILO and
kudzu), it works fine.
I'm using RH 7.3, kernel 2.4.24 if that helps...

Thanks a lot

Mike

 
 
 

Keyboard works during boot sequence, but not at login prompt

Post by Davide Bianch » Wed, 21 Apr 2004 18:53:44



> Is this weird?

What kind of keyboard? PS/2 or USB? If it's USB, you need USB/HID
interface enabled in the kernel or the required modules loaded.

Davide

--
| Gordon's first law: If a research project is not worth doing, it is
| not worth doing well.
|
|

 
 
 

Keyboard works during boot sequence, but not at login prompt

Post by maldri » Wed, 21 Apr 2004 21:47:03




> > Is this weird?

> What kind of keyboard? PS/2 or USB? If it's USB, you need USB/HID
> interface enabled in the kernel or the required modules loaded.

> Davide

Actually, its an old AT? keyboard.

I just use the machine for storage...

 
 
 

Keyboard works during boot sequence, but not at login prompt

Post by Spamles » Thu, 22 Apr 2004 05:37:58





>> > Is this weird?

>> What kind of keyboard? PS/2 or USB? If it's USB, you need USB/HID
>> interface enabled in the kernel or the required modules loaded.

>> Davide

> Actually, its an old AT? keyboard.

> I just use the machine for storage...

What kernel? I know that the 2.6.5 configuration warns:

 CONFIG_KEYBOARD_XTKBD:
 Say Y here if you want to use the old IBM PC/XT keyboard (or
 compatible) on your system. This is only possible with a
 parallel port keyboard adapter, you cannot connect it to the
 keyboard port on a PC that runs Linux.
 To compile this driver as a module, choose M here: the
 module will be called xtkbd.

 
 
 

Keyboard works during boot sequence, but not at login prompt

Post by Little Monste » Thu, 22 Apr 2004 06:23:00


On Tue, 20 Apr 2004 20:37:58 +0000, the world was enlightented by
Spamless, unto whom the words are attributed:






>>> > Is this weird?

>>> What kind of keyboard? PS/2 or USB? If it's USB, you need USB/HID
>>> interface enabled in the kernel or the required modules loaded.

>>> Davide

>> Actually, its an old AT? keyboard.

>> I just use the machine for storage...

> What kernel? I know that the 2.6.5 configuration warns:

The OP does actually state what kernel :-)  Question is, is it an AT mobo?

Monster

--
Who stole my sig?  Who stole it?
Own up, dammit!!  It was YOU, wasn't it?

 
 
 

1. bash# prompt during boot sequence before login?

        For one reason or another, my system has begun presenting a bash shell
prompt during my system boot, right after announcing it is going
multiuser. Simply typing exit closes the shell and the boot process
continues, launching daemons inetd, lpd etc. I haven't modified any of
the rc.X file except the rc.inet1 file and the only modification to it
was a change to the HOSTNAME= line.

        I've been through all of the rc.XXX files lokking for any obvious
errors or changes but haven't been able to spot anything, plus I'm not
really sure of the sequencing of these files. Since I'm the only user
right now it's not that big of a security risk, but it will be.

Help and opinions appreciated.

Regards,

Jeff Brown
Associate Network Engineer
The Home Depot USA, Inc.

2. CDR Question ???

3. Changing login prompt (NOT motd or shell prompt)

4. ISDN Terminal Adapters.... Oh dear.

5. keyboard and mouse not working during Solaris 10 install on Ultra10.

6. code coverage tool

7. How can I change text login in prompt to GUI login prompt

8. Remote Login IP Address

9. Redhat 8.0: Keyboard not responding during boot after install

10. DHCP not working when booting, works after login

11. Unable to login at login prompt - not even root

12. RH 6.1 After Install boots to command prompt not Graphical Prompt???

13. $prompt in csh - ansi escape sequences not interpreted