MobileRead Forums - View Single Post

NullNix · 12-12-2019, 02:30 PM

So every previous Kindle I've ever owned has mounted fine on every OS I attach it to. But this one... on Win10 it's fine, but on every Linux box I own (everything from 4.4.x to 5.3.x kernels, everything from GalliumOS through Ubuntu through self-compiled Linux-from-scratch, mostly with USB mass storage support) I see nothing: no partitions appear, and the entire disk that does appear appears as a run of zero bytes (with the same length as the disk that should be there).

Has anyone else seen this? Before I spend time debugging -- which can't happen until mid-January in any case -- does anyone know what weirdness is going on and what on earth every single one of my fairly differently configured Linux kernels is missing that Win10 has got? I've literally never seen this with any USB storage device before at all (and I have a *lot*).

12-12-2019, 02:30 PM	#1
NullNix Guru Posts: 929 Karma: 15576314 Join Date: Jan 2013 Location: Ely, Cambridgeshire, UK Device: Kindle Oasis 3, Kindle Oasis 1	Oasis 3 sideloading: weirdness on Linux? So every previous Kindle I've ever owned has mounted fine on every OS I attach it to. But this one... on Win10 it's fine, but on every Linux box I own (everything from 4.4.x to 5.3.x kernels, everything from GalliumOS through Ubuntu through self-compiled Linux-from-scratch, mostly with USB mass storage support) I see nothing: no partitions appear, and the entire disk that does appear appears as a run of zero bytes (with the same length as the disk that should be there). Has anyone else seen this? Before I spend time debugging -- which can't happen until mid-January in any case -- does anyone know what weirdness is going on and what on earth every single one of my fairly differently configured Linux kernels is missing that Win10 has got? I've literally never seen this with any USB storage device before at all (and I have a lot).