1 Answer1. Active Oldest Votes. 0. OK so if I boot with dtoverlay in config.txt and dwc2 in /etc/module set then try to manually start g_ mass _storage with sudo modprobe … then it seems to work, in a way that starting it in /etc/modules caused a crash.
Though I had never used the g_ mass _storage module on the pi zero I had read a little about it and found a couple of fairly straightforward tutorials. I followed this tutorial over at MagPi . Everything seemed great.
7/16/2020 · Mass Storage Function, version: 2009/09/11. LUN: removable file: (no medium) no file given for LUN0. g_ mass _storage 12480000.hsotg: failed to start g_ mass _storage: -22. 8<--- cut here ---. Unable to handle kernel NULL pointer dereference at virtual address 00000104. pgd =.4/6/2019 · Now on startup I see this in dmesg: [ 3.497541] Mass Storage Function, version: 2009/09/11 [ 3.497570] LUN: removable file: (no medium) [ 3.523594] lun0: unable to open backing file: /backingfiles/cam_disk.bin [ 3.523779] g_ mass _storage 20980000.usb: failed to start g_ mass _storage: -2 Continuing to debug, — You are receiving this because you were mentioned.
