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. If (-not (Get-Command choco.So, I have a kobo ereader. zip to the filename to handle archive cmdlet limitations # Ensure Chocolatey is installed from your internal repository # $Chocolate圜entralManagementServiceSalt = "servicesalt" # $Chocolate圜entralManagementClientSalt = "clientsalt" # $Chocolate圜entralManagementUrl = " # ii. # If using CCM to manage Chocolatey, add the following: $ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.1.4.0.nupkg" # This url should result in an immediate download when you navigate to it # $RequestArguments.Credential = $NugetRepositor圜redential # ("password" | ConvertTo-SecureString -AsPlainText -Force) # If required, add the repository access credential here $NugetRepositoryUrl = "INTERNAL REPO URL" # Should be similar to what you see when you browse Your internal repository url (the main one). # We use this variable for future REST calls. ::SecurityProtocol = ::SecurityProtocol -bor 3072 # installed (.NET 4.5 is an in-place upgrade). NET 4.0, even though they are addressable if. # Use integers because the enumeration value for TLS 1.2 won't exist # Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories. # We initialize a few things that are needed by this script - there are no other requirements. # You need to have downloaded the Chocolatey package as well. Download Chocolatey Package and Put on Internal Repository # # repositories and types from one server installation. # are repository servers and will give you the ability to manage multiple # Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they # generally really quick to set up and there are quite a few options. # You'll need an internal/private cloud repository you can use. Internal/Private Cloud Repository Set Up # # Here are the requirements necessary to ensure this is successful. Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed.
0 Comments
Leave a Reply. |