Quote:
Originally Posted by Mr Groch
No - just bare Windows 11 PC (laptop).
|
That's good to know. This warning made me think of that first. Early development was done in a VM on Linux.
Earlier they shared the Inkpad Color 3 VID, matching your log. That was added to AVATeR way back, but not to a 2nd white/acceptlist. Fixing that ought to have solved this. I'll read up there ASAP.
Quote:
|
Maybe this is my fault - this time I run AVATeR after connecting my PocketBook Era Color - so it is fully initialized as mass storage device, earlier it could detect it before chosing PC mode on device after connecting USB cable...
|
Ensure the reader runs in PC mode, and the drives are mounted/visible to Windows. Then start AVATeR or do a rescan.
If the drives aren't mounted, AVATeR can't see/reach them. It might detect the reader if connected without PC mode, as you noted, and as clued by this debug line:
Quote:
|
18:27:17 Debug: Monitor received arrival of device interface: "\\\\?\\USB#VID_1D6B&PID_0104#20080411#{a5dcbf 10-6530-11d2-901f-00c04fb951ed}"
|
Note the #20080411# part usually shows the serial. This is however not a classical PB serial (something like YTFA0300014~), and suggests this being the USB 'stub device' that temporarily shows up when connecting a PB reader like the Lux5. For the Lux5 this stub uses the Google VID - and hides itself. Perhaps they changed that, and the device is now always visible. Without PC mode, it would hide its drives, explaining the "no child" error.
I'll need to walk through the USB code, and add more debug output. Like logging the error code, and when a compatible device was found, with its credentials
Perhaps that can tell us more.
Quote:
|
20:21:06 Debug: Ignoring local mirror with serial/mirrortype/vendor: "1746721893" -1 65534
|
This needs fixing too, a 'random' serial (read: epoch date) used by the new localpath (device from path) feature, has stored data in devices.conf.