![]() Thread 1:: Dispatch queue: -managerĠ libsystem_kernel.dylib 0x00007fff8e20d662 kevent64 + 10ġ libdispatch.dylib 0x00007fff8f245421 _dispatch_mgr_invoke + 239Ģ libdispatch.dylib 0x00007fff8f245136 _dispatch_mgr_thread + 52Ġ libsystem_kernel.dylib 0x00007fff8e20ce6a _workq_kernreturn + 10ġ libsystem_pthread.dylib 0x00007fff8bb0bf08 _pthread_wqthread + 330Ģ libsystem_pthread.dylib 0x00007fff8bb0efb9 start_wqthread + 13 That works around the bug in Amlogic's USB implementation as well.Path: /Applications/iBooks.app/Contents/MacOS/iBooksĪnonymous UUID: 59E92BEB-7F30-3BF8-F709-9A4D2290AA9C You do need a special cable for the USB-otg, though.Īlso you could use a USB (3?) hub/dock with the N2, and connect the reader to that. Use the USB-otg connector on the front of the N2, instead of the normal USBs on the back. I'm cross-posting this from the Manjaro forum, but as I'm not making much progress on this. There's a lot more builtin modules on the N2/N2+ kernels I looked at, compared to the Manjaro Pi4 kernel, but for the given 3 sections, only the scsi_transport_iscsi.ko is not compiled in on the N2s. I've visually compared the kernel/drivers/fs, scsi and usb, otherwise looking comparable. Tobetter does compile in something called scsi_transport_sas.ko, but that has a slightly different name. That is not in the N2/N2+ kernels I tested with. The scsi modules also, except for kernel/drivers/scsi/scsi_transport_iscsi.ko. fs modules on the working device are all on the N2 as well. So is it then something in the builtin modules?Ĭode: Select all cat /lib/modules/$(uname -r)/modules.builtinīut it's difficult to know what to look for. I've not seen any modules being loaded on the the working ARM machines when plugging in the Kobo reader. sd 1:0:0:0: Attached SCSI removable disk sd 1:0:0:0: Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: Power-on or device reset occurred scsi 1:0:0:0: Direct-Access Kobo eReader- 0110 PQ: 0 ANSI: 2 usb-storage 1-1.3:1.0: USB Mass Storage device detected usb 1-1.3: SerialNumber: N5-edited-for-privacy-96 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.3: New USB device found, idVendor=2237, idProduct=4224, bcdDevice= 1.10 usb 1-1.3: new high-speed USB device number 8 using xhci_hcd sd 1:0:0:0: Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 On a working ARM machine, it says this in dmesg:Ĭode: Select all usb 1-1.3: USB disconnect, device number 7 Kobo is sort-of the European Kindle, so it's a big brand, well sold kinda thing. So this looks to me like the complete Kobo ereader product line is probably not supported? I tried a basic Kobo Touch 1, Kobo Touch 2 and a high-end top-of-the-line new Kobo Forma. Also Manjaro KDE, also 64b, non-ARM obviously. Same ereader, same cable on a certain Fruity 4 ARM device (kernel 5.4.51) and a Pro64 ARM device with a rather cone-shaped logo (5.7.0) both running Manjaro ARM KDE, all on 64bits kernels. I tried both tobetters kernel 5.7.14 and Manjaro's 5.7.10. ![]() No showing up on lsusb, not on dmesg, not on journalctl. What should happen is that it is recognized, on the reader shows a window asking to connect, you connect, you get a usb device folder to drop your ebooks onto.īut connecting it to both the N2 (Manjaro) and N2+ (tobetter's ubuntu image), nothing. The kobo reader does start charging though, so there is power. It's a USB linked device, I plug it in, nothing happens. The thing is, it doesn't connect to the N2.
0 Comments
Leave a Reply. |