After HD update: No Keyboard / Mouse after boot

Hi all,

I had a normal OpenSuse 11.1 setup, along with Windows XP, swap partition and /home partition.

After my hd began failing (badblocks), I cloned the system to a different location (using ddrescue), updated the hd with a new one (bigger), made new partitions on the new hd (preserving the old locations, ex: /dev/sda1 ext3 on old hd still is /dev/sda1 on new one, but made changes to the partitions sizes to make them bigger), recovered all the clones to the new hd, fsck’ed them, recovered grub with install dvd then tried to boot.

On the first boot, it failed to mount / (/dev/sda1) and gave me a command line. I checked /etc/fstab and saw that, on the old setup, it was mounting the partitions based on the HD-id, which obviously changed. I fixed that to use /dev/sda1, /dev/sda2, etc.

Now, the systems boots fine. But, when i get to the graphical login part, the keyboard and the mouse don’t work. Any idea on what could cause this?

PS: I know that what I did isn’t very safe, so if you guys can think of anything else besides the /etc/fstab that I’ll need to fix in order to make the system work with the new hd, please let me know.

PS-2: If it’s any help, it’s a Dell Inspiron 1525 notebook, now with a 320gb samsung hd.

dd and relatives do a byte by byte copy. If the file system is corrupt so is the image you copied. The time to make a backup is before you have a problem.

I understand that, but right before the backup the mouse and the keyboard worked fine. I know that some files may have been corrupted when I was making the backup, but is there a chance this could’ve been caused by the system having a new hd now?

giulianoxt wrote:
> but is there a chance this could’ve been
> caused by the system having a new hd now?

the only reason i can think of that would make the mouse/keyboard
problems now connected to the new hard drive is if the file (or
files, don’t know specifically how many or where) specifying the
mouse/keyboard and/or driver(s) were somehow corrupted after the last
boot (when those files were read into memory) and when they were
transferred to the clone…

i don’t know that that is what happened, but i can’t think of a way
for a new hard drive alone to mess up the mouse/keyboard…

i think i would try to fix it by inserting the install disk and
selecting “Repair Installed System” while the machine is connected to
the net…it might find the mangled file(s) and replace them…

WAIT! another thought: i don’t know anything about that Dell or how
the hard drive is replaced…but, if it anything more than remove a
simple door and slide out slide in, then you MAY have unknowingly
disturbed the/a connection between the mouse/keyboard (now that i
think about it: are we talking a mouse PAD, or external mouse plugged
into a USB port?)

and, was the machine dropped (which may have dislodged a critical
connection)?

let us know how you get on, please…


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio

The usage of /dev/disk/by-id/ is not only in /etc/fstab, but also in* /boot/grub/menu.lst*. But I assume you allready changed there, because you can boot

I don’t think it’s a physical problem since they work fine right now (I’m on a System Rescue live cd).

In fact, when opensuse is booting, showing messages on the terminal, if I type anything on the keyboard it shows up on the screen, interleaved with the normal messages. It seems like it works right up to the graphical login part.

I’ll download the DVD again to try to repair the packages and get back to you.

Oh yeah, I tried both the touchpad mouse and a normal usb mouse, both don’t work.

The usage of /dev/disk/by-id/ is not only in /etc/fstab, but also in /boot/grub/menu.lst. But I assume you allready changed there, because you can boot

Yes, that was fixed automatically when I recovered GRUB. Thanks anyway!

giulianoxt wrote:
> It seems like it works right up to the graphical login part.

i think i remember seeing something like that here before, but can’t
remember what the problem was…you might just use the forums
advanced search and use keywords like:

mouse keyboard login problem

i don’t know…that will probably turn up millions

well, this turns up only :wink: 398! http://tinyurl.com/33rqepm


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio