Re: Keyboard no longer works at boot...

On Wednesday, March 21, 2012 03:26 TuxaneSoft wrote:

> Hi,
> I guess you gave the answer yourself, when you did a hard boot ,
> file-systems are likely not clean and some stuff won't get loaded.
> You should start from a cd/usb live system and do fsck on all you
> partitions.
> But I don't understand why you need to boot Suse to access it's files ?
> I can't think of any reason why it should not be accessible from Slack ?
> 
> Jens

  I put the horse a little ahead of the carrot...I meant to write that the *first* time I 
tried to boot back into Slackware after I'd done what I needed on the suse side the 
keyboard wouldn't work. It was then that I had to hit the reset button because ctrl-alt-
del wouldn't work, nothing worked from the keyboard.

  The reason I had to boot into suse was because I needed a password I'd forgotten to 
write down (but had thought I had and just couldn't find it). Not a big deal as I figured 
I'd just boot into suse, get it and boot right back into slack. I had to open up seamonkey 
on the suse hdd to get it. It was something that I was hoping would take all of 3 minutes 
to get done. Normally I *can* transfer anything I want from the suse hdd to the slackware 
hdd *from* slackware, but just not that password in seamonkey on the suse hdd.


-- 
All that is necessary for the triumph of evil is that good men do nothing.  -Edmund Burke