I`m encountering a very strange BIOS *access* problem unlike anything I`ve
ever dealt with before.
I can NO longer enter the BIOS *OR* the F-8 "Quick Drive Select" feature of
my (Socket 939) Asus A8V Deluxe (AMI BIOS) *OR* even the (press TAB) BIOS
"message".
In fact, I lost ALL the PS2 keyboard functions as well!
Yes, I have tried another PS2 keyboard with exactly the same result...NO
Longer working/typing.
I then connected a USB keyboard and still could NOT enter the BIOS, nor the
"Quick Drive Select"!
HOWEVER, A dedicated *USB* keyboard works/types in WinXP, but yet.... I
still can NOT use even a USB keyboard to enter the BIOS etc!! Also, a PS2
keyboard *WITH* a USB adaptor *DOES* work/type normally... once in WinXP!
According to my manual, in the BIOS "Legacy USB Support" is set to "Auto" by
default.
This Auto setting "allows the system to detect the presence of USB devices
at startup". "If no USB device is detected,the legacy USB support is
disabled"
So to sum up, as of now I can`t use a PS2 keyboard *OR* a USB keyboard to
enter the BIOS!
Yet a PS2 MOUSE works per normal once booted up in WINDOWS, but NOT a PS2
keyboard (without a USB adaptor) This is NUTS!! I can see *maybe* losing a
PS2 keyboard Port somehow (?) but what about
the USB at startup ??? It seems to me something in the BIOS got ******* up?
This problem occurred just after I attempted to correct my LINUX MINT *time*
difference with the WinXP *time* on this "dual boot" Asus A8V Deluxe
(seperate O.S. HDD`s using the F8 "Select Boot" feature to access the
desired HDD with O.S. at startup) by editing LINUX MINT.
I edited using the LINUX terminal (as instructed by a MINT forum), by
changing one word in one line from: UTC=yes to UTC=no.
UTC being: Universal Time Clock?
After the edit I was required to RE-BOOT for the change to take effect which
I did do, but at this point (after the re-boot) my (PS2) keyboard FAILED at
the F8 "Quick Drive Select" function, and bootup just continued on to the
normal default WinXP Drive. Further investigation by me showed *NO* PS2
keyboard functioning in WinXP. Subsequent tests by me also showed I could NO
LONGER enter BIOS as well!
I`m assuming I need to fix something amiss in the BIOS, but how can I when I
can NOT enter the BIOS?
Would "clearing the CMOS" (CLRTC) be the solution?
If so, by resetting the CMOS I could be "stuck" with all default settings
*IF* I still could NOT enter the BIOS after clearing the CMOS.
I cant even consider updating or "FLASHING" the BIOS, since I need to be
able to use a keyboard!
Mattrixx wrote:
> I`m encountering a very strange BIOS *access* problem unlike anything I`ve
> ever dealt with before.
>
> I can NO longer enter the BIOS *OR* the F-8 "Quick Drive Select" feature of
> my (Socket 939) Asus A8V Deluxe (AMI BIOS) *OR* even the (press TAB) BIOS
> "message".
> In fact, I lost ALL the PS2 keyboard functions as well!
>
> Yes, I have tried another PS2 keyboard with exactly the same result...NO
> Longer working/typing.
> I then connected a USB keyboard and still could NOT enter the BIOS, nor the
> "Quick Drive Select"!
> HOWEVER, A dedicated *USB* keyboard works/types in WinXP, but yet.... I
> still can NOT use even a USB keyboard to enter the BIOS etc!! Also, a PS2
> keyboard *WITH* a USB adaptor *DOES* work/type normally... once in WinXP!
>
> According to my manual, in the BIOS "Legacy USB Support" is set to "Auto" by
> default.
> This Auto setting "allows the system to detect the presence of USB devices
> at startup". "If no USB device is detected,the legacy USB support is
> disabled"
>
> So to sum up, as of now I can`t use a PS2 keyboard *OR* a USB keyboard to
> enter the BIOS!
> Yet a PS2 MOUSE works per normal once booted up in WINDOWS, but NOT a PS2
> keyboard (without a USB adaptor) This is NUTS!! I can see *maybe* losing a
> PS2 keyboard Port somehow (?) but what about
> the USB at startup ??? It seems to me something in the BIOS got ******* up?
>
> This problem occurred just after I attempted to correct my LINUX MINT *time*
> difference with the WinXP *time* on this "dual boot" Asus A8V Deluxe
> (seperate O.S. HDD`s using the F8 "Select Boot" feature to access the
> desired HDD with O.S. at startup) by editing LINUX MINT.
> I edited using the LINUX terminal (as instructed by a MINT forum), by
> changing one word in one line from: UTC=yes to UTC=no.
> UTC being: Universal Time Clock?
>
> After the edit I was required to RE-BOOT for the change to take effect which
> I did do, but at this point (after the re-boot) my (PS2) keyboard FAILED at
> the F8 "Quick Drive Select" function, and bootup just continued on to the
> normal default WinXP Drive. Further investigation by me showed *NO* PS2
> keyboard functioning in WinXP. Subsequent tests by me also showed I could NO
> LONGER enter BIOS as well!
>
> I`m assuming I need to fix something amiss in the BIOS, but how can I when I
> can NOT enter the BIOS?
>
> Would "clearing the CMOS" (CLRTC) be the solution?
> If so, by resetting the CMOS I could be "stuck" with all default settings
> *IF* I still could NOT enter the BIOS after clearing the CMOS.
> I cant even consider updating or "FLASHING" the BIOS, since I need to be
> able to use a keyboard!
>
> Thanks for any further insight into my dilema
>
> Matt
>
>
Clear the cmos and hope that the USB resets to auto. You have nothing to
lose since the machine is toast now.
On Mon, 02 Jul 2007 00:27:53 GMT, "Mattrixx" <someone@nowhere.com> put
finger to keyboard and composed:
>Would "clearing the CMOS" (CLRTC) be the solution?
>If so, by resetting the CMOS I could be "stuck" with all default settings
>*IF* I still could NOT enter the BIOS after clearing the CMOS.
Search for a utility to backup and restore your CMOS RAM.
You'll get into bios and bios will POST.. or boot if you prefer with just the CPU, Graphic card and RAM inserted all the rest can be disconnected and excluded.
Whilst trying to reboot the bios, would it not be a good idea to change the bios battery and ensure the contacts are not tarnished or dirty causing intermittent connection's.
CPU, Graphic card and RAM could also cause non boot, the graphic card out of the three especially, it would be a good idea also to disconnect all USB devices whilst attempting to solve this problem.