Re: Keyboard no longer works at boot...

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
-- 





Cordialement,

Jens Weber

Email: <[email protected]>
SARL Burro-net <http://www.burro-net.com>
TuxaneSoft <http://www.tuxane.com>
7 Place du Pont
F- 66400 Ceret
Tel:+33 468827320
Siret: 503 676 124 00020 
APE: 6206A
TVA: 20503676124
RCS Perpignan



Am Dienstag, den 20.03.2012, 02:52 -0500 schrieb Insomniac:

> Hi folks,
> 
>   I've been using the Slackware hdd of a dual-boot system for the past week+ exclusively 
> until this morning. I needed to reboot to get into my opensuse hdd to look up a couple 
> things I needed that I couldn't get from the Slackware side.
> 
>   When I was done, I rebooted the system so I could get back to the Slackware, but for 
> some reason my keyboard stops working just a second or two before I get the login prompt. 
> Until now, it's been working perfectly, and of course it's working on the opensuse side as 
> this is where I had to come to write this.
> 
>   During bootup, I did manage to catch something about fuse module not loaded (whatever 
> that is), and file system not clean (that's from having to hard boot unfortunately).
> 
>   I've not uninstalled *anything* other than some apps here and there that I'd built and 
> installed that were just simple things, nothing to do with hardware or the system/file 
> system.
> 
>   Anyone have any idea what happened or what I might can try to get back to using my 
> Slackware side?
> 
>   Thanks,
> 
>   John
> 
>

_______________________________________________
slackware mailing list
[email protected]
https://mailman.lug.org.uk/mailman/listinfo/slackware