Jump to content
Posted 09 October 2014 - 12:34 PM
Posted 09 October 2014 - 02:19 PM
I use the + and - keys to navigate up and down my BIOS - might be worth trying on this boot menu.
If not, can you supply some more details, such as what CD this boot menu is on?
I take it from what you say, that whatever bootloader and operating system you are using, is on a CD (or DVD), and not installed on your computer. Is that correct?
Posted 09 October 2014 - 02:41 PM
Posted 09 October 2014 - 05:49 PM
It's a new build you see.
That's useful info as well.
Considering the DVD works on other computers, and you can presumably navigate this same menu on them, I wonder if this thread wouldn't be better off in the hardware section of the forum.
Posted 09 October 2014 - 08:54 PM
Not sure on cd title.
It has worked without any issues for 4 other pc,
So what is it? Ubuntu, RedHat, Fredora? Try a diffrerent keyboard.
When you ask for support you should also include as much information about the problem as possible. Including all of the important details in your first post will greatly speed up the entire support process and allow our volunteers to better assist you. While you may think a particular error message isn't very helpful, it may be the key to resolving your issue. Some details we are looking for would include, but not be limited to:
Arch Linux .
Come join the fun, chat to Bleeping computer members and staff in real time on Discord.
The BleepingComputer Official Discord Chat Server!
Posted 14 October 2014 - 05:48 PM
Hi, my arrow keys won't let me navigate up and down on my CD boot menu.
They do in the bios (before this menu) and in the gui (after boot menu).
It has worked without any issues for 4 other pc, can someone please advise what to do.
I have had a similar experience when I was using a PCI USB expansion card to power my keyboard, so it might be worth making sure your keyboard is plugged into a USB port that is being probed early on in the boot process.
The only other cause (That I am aware of, anyway) would be a rare bug, that mostly affects older systems, where the early boot process can't automatically probe for the keyboard, and a kernel parameter must be set to correct the issue. However, while I did say this mostly affects older hardware, it has been known to occur on some newer hardware too.
Please come back and let us all know if you find a solution.
Edited by Kaosu, 14 October 2014 - 05:53 PM.
0 members, 0 guests, 0 anonymous users