Odroid N2 / usb storage not found / kobo reader not connecting

So, I've got Manjaro ARM both on a Raspberry Pi 4 (kernel 5.4.51) and on the Odroid N2 (5.7.10).
Both up-to-date on stable.
On the Odroid N2 my kobo touch ereader is not responding / detected / seen. Not in lsusb, not in dmesg, not in journalctl -f. When I plug the kobo reader in, it is as if it is not connected at all. Tried it on a couple of USB ports, where both keyboard and mouse works.
On the Raspberry Pi same kobo touch ereader, same cable, it all automatically works.

The kobo reader is not very recent, so won't be usb3. The N2 ports are usb 3.

Could it be that the Odroid N2 kernel is missing some usb storage drivers / modules?
Is there an additional service I should enable and start?

Thinking it could be missing kernel modules. See if you can narrow it down.

lsmod on the pi4 and copy nodules loaded
open up another terminal and start dmesg -w
then plugin the device and do a lsmod again and compare to see if new modules are loaded.

Also post the new lines in the dmesg window.

Thanks for your reply with some suggestions!

The dmesg -w on the Pi says:

[ 5094.388993] usb 1-1.3: USB disconnect, device number 7
[ 5094.390727] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 5094.390908] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[ 5175.005618] usb 1-1.3: new high-speed USB device number 8 using xhci_hcd
[ 5175.111678] usb 1-1.3: New USB device found, idVendor=2237, idProduct=4224, bcdDevice= 1.10
[ 5175.111696] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5175.111707] usb 1-1.3: Product: eReader-4.4.9344
[ 5175.111718] usb 1-1.3: Manufacturer: Kobo
[ 5175.111729] usb 1-1.3: SerialNumber: N5-edited-for-privacy-96
[ 5175.120148] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 5175.120647] scsi host1: usb-storage 1-1.3:1.0
[ 5176.146802] scsi 1:0:0:0: Direct-Access     Kobo     eReader-4.4.9344 0110 PQ: 0 ANSI: 2
[ 5176.150028] sd 1:0:0:0: Power-on or device reset occurred
[ 5176.152815] sd 1:0:0:0: [sdb] 6632445 512-byte logical blocks: (3.40 GB/3.16 GiB)
[ 5176.257251] sd 1:0:0:0: [sdb] Write Protect is off
[ 5176.257270] sd 1:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 5176.367213] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5176.611747]  sdb:
[ 5176.837258] sd 1:0:0:0: [sdb] Attached SCSI removable disk

The timesplit between 5094 and 5175 was between it connecting initially, it then shows a choice pop-up asking if I want to connect to the computer to share files. And then me pressing 'connect' on the reader. It then proceeds at 5175.

I checked lsmod before/after, but it was the same. Didn't see a xhci in there, which I sorta expected to see in the lsmod, or for that matter a usb-storage mention. I didn't expect the scsi stuff in the dmesg output, but I'm no expert there.
I'll give it a good go tomorrow, it is a little late in the day. So I'll add some additional info then.

Did any more modules load up on the pi4 with lsmod when you plugged the device in?

When you are looking for extra modules. Reboot the pi4 with out the device plugged in then do a lsmod > no-device.txt then plug in the device and do a lsmod > device.txt. Then compare the 2 files for new modules.

Yeah, done a fresh boot, done the lsmod > no-device.txt, then connected the thing, and again with device.txt.
Strange enough, still identical. Well, there was a different number behind v3d and vc4, but that seems highly unrelated to me.

Was no-device:

v3d                    73728  7
vc4                   278528  21
drm                   532480  18 gpu_sched,drm_kms_helper,v3d,vc4

Is with device:

v3d                    73728  10
vc4                   278528  36
drm                   532480  24 gpu_sched,drm_kms_helper,v3d,vc4

So, perhaps it is a driver that was compiled into the kernel instead of as a module??

Many congrats and much gratitude for the Raspberry Pi 4 support though.
I boot it directly from USB, using a Samsung T5 SSD, slight overclock, works for desktop purposes near perfectly. Very impressive. If we could get the N2 anywhere near that with the additional processing speed.... :slight_smile:

Possibly. Not knowing what module it would require for the device if that is the issue would be some what hard as I know nothing about that device.

You can see what is built in the pi4 and n2 kernels by running this on each device and compare the 2 and see if something sticks out:

cat /lib/modules/$(uname -r)/modules.builtin > pi4-builtin.txt

cat /lib/modules/$(uname -r)/modules.builtin > n2-builtin.txt

Another thought is if you are running xfce on the pi4 I put these packages in the profile that are missing in some of the other profiles to access various file systems that people might need. You might see if they are installed on the DE your are using.

# File systems access

This topic was automatically closed after 90 days. New replies are no longer allowed.

Forum kindly sponsored by