Aller au contenu principal

ATIH v2015 Mouse and Keyboard do not work once Rescue Disk has been loaded

Thread needs solution

Hi

I upgraded to ATIH 2015 today.
I was testing the Rescue Disk, and once it booted and loaded ATIH 2015, the Mouse and Keyboard no longer worked. I had to abort by forcing the computer to shutdown as I could not navigate while within the Rescue Disk.

Any help will be very much appreciated - thank you.

I an using Widows 7 SP1 32 bit.

0 Users found this helpful

I am using a wired mouse and keyboard and it still doesn't work. Going to request a refund

Got my refund. Once it hits, I am going to try EASUS ToDo Backup Home...

http://www.easeus.com/backup-software/tb-home.html

(copying from a parallel thread)

Dear Community,

We're currently looking into the reports of mouse/keyboard devices not working under boot media. These are hardware-specific problems, so we'll need diagnostic information from the respective hardware to find the root cause of each mouse/keyboard device detection issue and implement the respective fixes.

(!) Your help is needed, as the hardware we have can be tested on our side, but we can't get all the hardware in the world (especially within small timeframe).

So if you have prolems with mouse/keyboard not detected, please get the below diagnostic data and ping Anna Trifonova (https://forum.acronis.com/user/36716) via personal message to forward this data to us for analysis. We can guarantee this data will be used for the tech problem investigation only.

*********** INVESTIGATION INSTRUCTIONS ***********

We will need to get the following information from you so our Linux developers can get to the root cause of the issue with the devices not detected correctly - and find a solution for you.

0. Hardware specifics: specify the exact mouse/keyboard device model and its specifics (e.g. wireless).

1. Windows system information:

- download and run AcronisInfo utility in Windows on the machine which has the hardware detection problems (make sure respective devices are attached): https://kb.acronis.com/acroinfo => save the output and send it to us

(!) if it fails to run for any reason, please press Win + R => type MSINFO32 => press Ctrl + S => save as msinfo file => compress it to an archive and share with us.

2. Try special boot media parameters and get system information from the boot media after this attempt:

2.1 Boot from True Image 2015 media. Wait till it shows you "Acronis True Image" and "Continue OS Booting".
2.2 Click F11. You will see a text box with "quiet".
2.3 Add to the text box: "force_modules=usbhid" after a space without quotes and press OK -> choose to load Acronis True Image
2.4 Check if mouse/keyboard is working.

=> If yes, go to Help -> Generate system report => save the resulting report as "sysinfo_usbhid". Let us know that this parameter helped detecting the devices and send us the respective report for further investigation. We will need it to implement full-fledged fix.

3. If parameters provided in steps 2 didn't help detecting the devices, we will need you to get a special DEBUG version of the system report from media; please do the following:

3.1 Boot from True Image 2015 media. Wait till it shows you "Acronis True Image" and "Continue OS Booting".
3.2 Click F11. You will see a text box with "quiet".
3.2 Add "debug" after a space without quotes and press OK => choose to load Acronis True Image
3.3 The media will boot to shell # interface
3.4 Create system report from shell issuing command:

# /bin/sysinfo

=> it will run and save a file to /var/lib/Acronis/sysinfo/sysinfo-****.tar.bz2

3.5 Save it to a Flash drive formatted to FAT32:

FLASH drive instructions:

- insert a Flash drive to a USB port and issue the following commands:

# cat /proc/partitions

=> This will give you the list of partitions/drives available in your system.

For example:
8 0 127744 sda
8 1 127744 sda1
3 0 80417183 hda
3 1 10241406 hda1
3 2 20482875 hda2
3 3 1020127 hda3

Flash drive's partition is visible as 'sdXY' (X - disk letter, Y - partition number). If there are some scsi devices in your system you may find your flash by partition/drive size. If the flash is partitioned it will bring the list of partitions as well. Let’s consider your partition on Flash drive is sda1 in this example.

- then you need to create a mount point for your flash and mount it:

# mkdir /mnt/tmp
# mount /dev/sda1 /mnt/tmp

(!) There can be some warning messages but it is safe to ignore them. If mount fails you may try to use 'vfat' (if the flash is formatted to FAT file system) or 'ext3' or 'ext2' (if its formatted to ext3 or ext2) parameter instead of 'auto' .

- check whether the drive is mounted correctly for writing access:

# ls /mnt/tmp

=> This will give a list of files/folders located on the drive.

- Then please type in the following command to copy the creation sysinfo data to the Flash drive:

# cp –r /var/lib/Acronis/sysinfo/ /mnt/tmp/

- Finally execute the below command to unmount Flash and finalize saving data to it:

# umount /mnt/tmp

=> Send us the resulting sysinfo-****.tar.bz2 file.

This problem occurred some years ago and had long been been fixed.
How can you introduce again bugs that were cured years ago?
This is not serious. Have you heard of non-regression tests?

Wireless keyboard and mouse (A4 Tech GK-85 / G3-230 )

Sadly, I have to add myself to this thread. I will get the reports etc and send them in.

What is strange, is that using the Universal Media Builder, Disk Director 12 and the Universal Restore option both work with this mouse and keyboard, but TI 2015 does not recognise the mouse or keyboard.

The beta 2015 did recognise this keyboard/mouse combination.

It's a shame , with a program that does not work and display solutions which are not recognized by a single client.
All my equipment is new ASUS Z97 -C CPU INTEL 4790K .
I want to try according to my ability but it's not acceptable.
I am an amateur and not a professional

FYI there is a current easy workaround which can be used + the next hotfix will contain the permanent solution. See https://forum.acronis.com/forum/67424 for the details.