Re: NetBSD and Android devices

[mlh%goathill.org@localhost (MLH)]

Martin Husemann wrote:
> On Wed, Apr 01, 2026 at 11:11:36AM -0400, MLH wrote:
> > I used to be able to plug in my Android phones and then mount them as usb
> > devices and do all that way, but gradually, NetBSD updates keep dropping
> > support for usb mounted devices to the point where now, nothing can be mounted
> > via usb anymore with -current.
> 
> Well, this is not in general that way - I just mounted a USB stick with
> -current a few hours ago (and it just did work).

I updated to NetBSD 11.99.5 and still neither :

$ sudo mount -t msdos /dev/sd0e /mnt

nor amd would mount. Until I did the root mount several times in a row (and
with several usb drives) and then it started mounting, and then amd also
started mounting.

In all cases, when the usb drive was inserted :

[ 579486.1619670] umass0 at uhub1 port 9 configuration 1 interface 0
[ 579486.1619670] umass0: Generic (0x058f) Mass Storage (0x6387), rev 2.00/1.00, addr 12
[ 579486.1619670] scsibus0 at umass0: 2 targets, 1 lun per target
[ 579486.1719671] sd0 at scsibus0 target 0 lun 0: <Generic, Flash Disk, 8.07> disk removable
[ 579486.1719671] sd0: fabricating a geometry
[ 579486.1719671] sd0: 3815 MB, 3815 cyl, 64 head, 32 sec, 512 bytes/sect x 7813120 sectors
[ 579486.1719671] sd0: fabricating a geometry

$ disklabel sd0
# /dev/rsd0:
type: SCSI
disk: Flash Disk      
label: fictitious
flags: removable
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 3815
total sectors: 7813120
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

5 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 d:   7813120         0     unused      0     0        # (Cyl.      0 -   3814)
 e:   7812992       128      MSDOS                     # (Cyl.      0*-   3814)
disklabel: boot block size 0
disklabel: super block size 0

So this was all working fine but mounting would fail (I forgot the issue but
wasn't a permissions error).

No changes whatsoever to any config files. Seems a bit like a permissions
issue, at least with amd, but I had changed nothing.