Quote:
Originally Posted by kingbeowulf
Let's ty something crazy. I recall form the olden days that sometimes the huge kernel loads too much resulting in the wrong driver being selected. Go ahead and create a initrd with mkinitrd with just the file system modules needed to find /boot and /, and boot the generic kernel.
|
I have two partitions, '/' and '/home' for the installation. Unfortunately, I did not have much success with creating an initrd that would boot. I suspect that there are conflicts with drivers; perhaps that explains why 'CTRL-ALT-F1' produces a blank screen instead of a console prompt (on tty1?)
Quote:
Originally Posted by Drakeo
If the laptop power settings are so that these devices go to sleep and are not being woke up again till you reboot. I would look into the function keys on that laptop. In kde system settings select your keyboard. And look into the function keys of that laptop. This has happen many times to my friends. And if you hibernate out of windows instead of a full shutdown will cause bios issues with hard ware and drive partitions.
Most likely it is power settings for your chips. Hang in there.
|
I have yet to use hibernation on this installation. That said, I have rebooted a few times, but the issue with input devices has yet to be repeated. I will just have to wait and see if I am just in a cycle where the odds allow for successful access...
