No mouse or keyboard at Login

ScottyPDX · 06-30-2009, 06:40 PM

Hello - I have an AMD 64 Dual Core 4200 w/2 Gigs RAM. On Jaunty, after adding some software through Synaptic (don't remember which software), I lost the use of both my mouse and keyboard at the Login screen. I can't even click on what I want to use (Gnome, KDE, etc.) I had to install the i386 version of Jaunty in Windows just to get into my Linux files. I tried going into the Initialize commands file (advice from Ubuntu forums) and add them, but still no keyboard or mouse.

Post-stroke, I can't remember these file names when they're not in front of me, sorry.

Any suggestions from my somewhat vague description would be most appreciated.

Thank you.

Simon Bridge · 06-30-2009, 10:18 PM

Quote:

after adding some software through Synaptic (don't remember which software)

/var/log/dpkg.log

Quote:

Post-stroke, I can't remember these file names when they're not in front of me, sorry.

When you find out what they are, write them down - then they will still be in front of you when you go to tell us.

When you get to the login screen - try ctrl+alt+F1 to get a non-graphical login.
I don't expect that this will work, so you'll have to boot to rescue mode. This may even have an option to reconfigure the keyboard.

What I want to find out is: does the keyboard work in non-graphical mode?

ScottyPDX · 07-01-2009, 06:40 PM

The initiation file is /etc/default/console-setup. I tried both "sudo dpkg-reconfigure console-setup" and just editing the file with gedit. Still no kb or mouse. I have used Rescue mode, and was able to get a terminal window with network, but it still couldn't connect to the Internet to fix some broken programs. I tried Startx, Gnome and XFCE from the terminal, with no success.

I had looked at the XFCE Setup, which told me I had a 105-key kb, so I changed it to 102, the one I do have.

When it is booting, it does something with the console, but too fast to catch. It looks like it's turning off the core input devices. Which log file could I look at?

It's been a while since I've been able to get into the 64-bit installation, so I could'nt tell you which software program(s) I had installed. I think it had something to do with Samba.

That's the best I can do for now... Thanks for your help.

Simon Bridge · 07-01-2009, 10:34 PM

Quote:

The initiation file is /etc/default/console-setup. I tried both "sudo dpkg-reconfigure console-setup" and just editing the file with gedit.

What I want to find out is: does the keyboard work in non-graphical mode?

Quote:

When it is booting, it does something with the console, but too fast to catch. It looks like it's turning off the core input devices. Which log file could I look at?

http://ubuntuforums.org/showthread.php?t=49925

Quote:

It's been a while since I've been able to get into the 64-bit installation, so I could'nt tell you which software program(s) I had installed.

I don't understand, you cannot reconfigure the keyboard for an installation you cannot access. Boot the install that you have no keyboard on - but boot to rescue mode.

Synaptic keeps a log of the packages it installs. You can go look at it.
/var/log/dpkg.log

Quote:

Post-stroke, I can't remember these file names when they're not in front of me

Considering your condition, it may be too difficult to troubleshoot this from New Zealand. I suggest you contact the Portland GNU/Linux Users Group, see if there is a member near you who can help. There may even be a support group real close that they will know about.

I know Portland is a big place, but if you can get to the University, they are having a meeting this weekend.

ScottyPDX · 07-03-2009, 04:14 PM

I'm sorry, I CAN get to the non-graphical mode using the Rescue option. It's only when I proceed with normal boot and get to the login screen that they stop working. I thought that the only way to find out what I added was to go to Synaptic, but I will check the file (var/log/dpkg.log). Do you know which University is having the meeting?

Thanks.

Simon Bridge · 07-03-2009, 10:18 PM

Quote:

Originally Posted by ScottyPDX

Do you know which University is having the meeting?

You missed it.

But note: PLUG has free clinics for gnu/linux users each month:

Quote:

Due to popular demand, PLUG volunteers are once again holding a monthly clinic to help one and all with their Linux (and other *NIX) computer problems on the third Sunday of every month.
This month's clinic will be 17 August, 1-5 pm.
Location: Free Geek Community Technology Center, 1731 SE 10th Avenue, Portland, OR

Note:Free Geek is closed Sundays, and no one will be answering the phones. Please enter through the south door, next to the Thrift Store. We'll have a sign by the door.

Go visit their web site for details.

August??? What bugs me about this is that the 17th cannot be the third Sunday. But you can contact the group mailing list anyway. Please understand that I know of them but I'm not actually in touch with them.

Simon Bridge · 07-03-2009, 10:36 PM

Quote:

I CAN get to the non-graphical mode using the Rescue option.

Good - in rescue mode - enter

dpkg-reconfigure -phigh xserver-xorg

This should, among other things, take you through some keyboard reconfiguration.
Tell us what this does.

After that - have a look at:

cat /etc/default/console-setup

I still think you'll be better served through PLUG.

ScottyPDX · 07-06-2009, 05:12 PM

Quote:

in rescue mode - enter dpkg-reconfigure -phigh xserver-xorg

This should, among other things, take you through some keyboard reconfiguration.
Tell us what this does.

It did not take me through any (re)configuration, just a message that it replaced the file and saved the original as a backup.

Being a Windows guy for the last 20-something years, I went ahead and reinstalled the 64-bit installation. Works just fine now. I'll definitely check out the user group in my area for more education.

Thank you very much for your help.

Simon Bridge · 07-07-2009, 02:50 AM

Yeah - reinstalling will do that too.