Last month I tried installing Mandriva AMD 64 as a dual boot on my computer. The first few attempts for some reason did not work. No matter, GRUB still let me into Windows so I could still get some work done until I had a day to dig deeper.

Well, that day was forced on me this past Saturday when GRUB no longer recognized my keyboard. No problem (I'm an easy going guy), I'll just reinstall Mandriva and try a different path. WRONG ANSWER!!

Here I am three days later, with the 912 page Running Linux guide by Dalheimer and Welsh trying to figure out why GRUB is not responding to my key strokes.

I've now reinstalled about a half dozen times. I finally made it to the login prompt tonight, though I haven't gotten past that even with the acknowledged login and password. Knoppix got stuck finding USB ports and I still can't get any work done on my main computer.

Some errors that I am getting include a value 22 on a resume, I forget which one, /etc/rc5.9//Koonetconsole doesn't provide anything, Failed to connect to the D-BUS daemon ... socket /var/run/dbus/system_bus_connection_send

Is my computer totally hosed or is there a way to get through these errors??

Hi, and welcome to LQ!

If it's a USB keyboard, did your BIOS settings change? Legacy
devices disabled?



Cheers,
Tink

Well it sounds to me like it's either in the bios settings as mentioned try booting into your bios see if you can navigate the bios menu. Or could be the keyboard is going bad. Did you check the keyboard connection on the back of the pc and make sure it's making a good connection?

Actually, I had thought about the keyboard going bad. Lucily I had a new board waiting for just an event. Unfortunately, changing them out made no difference.

Since they are both USB boards, I will look through the bios for the legacy switch.

Thanks.

Right on Tink. Found switch and now the computer is finally booting.

Now back to the manual to figure out why Mandriva keeps hanging and not loging in. Any ideas on that? I have lots of reading time on the train but rather not haul the manual around if I can get a quick answer.

Glad I could help, however:
If I were you I'd be wondering why that behaviour changed,
though, rather than being content with the fact that it
works again... did you flash the BIOS or something?


Sorry - not from me; I'm not too good with RedHat and its derivatives.


Cheers,
Tink

Tink,

There's been a lot of strange activity on my computer lately. I think that, well I'm pretty sure, that the bios setting changed when I reloaded optimized defaults. The strange thing is that I did that because the keyboard had stopped working. It worked for one startup after that. I think that the latest round of MS updates that I ended up downloading because of another program or hardware update was linked to them, is causing all of this trouble. I I restored the system but the updates still tried to force install. That was the first time I had updated in two years. I had no problems before that. Now to route out those updates and clear my system.