Witam,
Mam nowy komp, ktory na dzien dobry rzucal przy kazdej mozliwej okazji BSODami, ale pomoc techniczna plyty glownej wskazala aktualizacje biosu, pomoglo.
jednak teraz mam problem, bo czasami (praktycznie pierwsze uruchomienie kompa po powrocie z pracy - po resecie (ponownym) dziala normalnie) nie widzi ani klawiatury ani myszki
Logitech g502 i g910 zapalają sie na wczytywaniu gdy mozna wybrac wejscie w bios, a gdy pojawia sie logo windowsa i tekst ze laduje sie system, na chwile gasnie, by po chwili znow sie zapalic - wtedy wszystko dziala bez zarzutu, jednak czasem zgasnie i sie nie zapala, wtedy jedyna pomoc to reset.
Teraz zrobilem 2 resety, klawiatura sie wczytala, myszka niby tez, ale tylko w zakresie jezdzenia po ekranie, bo nic sie nie chce kliknąć. podpiąlem drugą awaryjną myszkę, to nagle g502 tez zaskoczylo i klika jak powinna.
w tej sprawie tez napisalem do pomocy technicznej, ale za choelre nie rozumiem co mi odpisali
spoiler start
To the USB issue, I will explain the background of this:
There is a huge difference between the old fashioned BIOS and a UEFI BIOS.
The old BIOS does not detect the TV card, it only checks if it has an input device (keyboard), output device (monitor in VGA mode) and a boot device.
The hardware is only activated after the operating systems loads the drivers.
A UEFI BIOS sends a signal to all hardware to make itself known, and depending on the answer it gets from the hardware it initializes the hardware, and also the mouse is activated, and the monitor in High resolution.
Then the USB issue, if I want to explain the reason, I have to tell you a bit about protocols and the difference between the old fashioned BIOS (which was probably on your other board) and the UEFI BIOS
With the old BIOS, the hardware was only fully functional when the Operating System finished loading the drivers, so the OS was responsible to handle it all.
A UEFI BIOS however has built in hardware support, and will activate the hardware during boot.
For USB hardware UEFI works according to the international USB-HID protocol, and that is where the problem starts.
This protocol states that for instance for the mouse buttons and the X and Y axis only 3 bits may be used, however the manufacturers want to have more buttons and options, so most of them use 4 bits, and in some cases 4 bits is not enough, and they place a USB HUB in the device itself.
The same applies to keyboards, who also have built in USB HUBS and functions.
For a UEFI BIOS it is difficult to recognize what hardware is connected.
That is why it sometimes doesn’t work properly, and also most drivers for Windows 7 on this hardware are basically adapted XP drivers.
Also the BIOS can influence this behaviour.
It really depends how your keyboard and mouse are recognized by the BIOS.
At home I use an Thermaltake Esport gaming mouse, and in the BIOS there is an option “System browser”, if I click on the USB ports to check what hardware is detected, my mouse is being detected as a keyboard, so UEFI finds 2 keyboards.
Most of the times it works, but sometimes the LED goes off, and the mouse is not working, the only solution is to unplug it, and connect to another HUB (see picture)
Sometimes the solution is to connect the mouse and keyboard to different hubs.
spoiler stop
