If you find a very low power harddrive ...
I came across a drive made an PATA model by Transcend.
Could be used with any old USB to 2.5" IDE adaptor.
The specs are these:
2.5" PATA SSD
TS32GPSD330
---
Capacities vary from 32Gb to 128Gb
---
DC +5V 0.3A <-------- This
https://www.transcend-info.com/Embedded/Products/No-836
I don't know if their SATA SSD drives have the same power spec.
https://www.transcend-info.com/Search.aspx?q=sata+2.5
Cheers,
A.
]]>... not related to the power-supply-USB-problem; it was for seeing whats inside '/proc/config.gz' !
Yes, I know.
What I meant to say was that what I thought was an issue ie: usb-storage.ko not being present was not the problem as it was part of the kernel.
The problem actually being a power supply one.
Thanks for your input.
Cheers,
A.
]]>Regards, FM_81
]]>... a
modprobe configs
...
No ...
Here it is:
groucho@rpidevuan:~$ sudo modprobe configs
groucho@rpidevuan:~$
But the issue has been solved.
Problem was a PS thing, long cable with voltage drop.
See my previous post.
Cheers,
A.
]]>The important thing is that ...
... it dawned on me that I was being obtuse. =^ 7
After thinking about it a while longer I realised that I had missed an obvious test.
The charger I have seems to be well built, relabeled for local sale so I don't know who makes it.
It is not a switching PS, just 220V Chinese made design, good quality plastic and not at all shoddy like some I others have seen.
But like I mentioned, it is obviously made for the smartphone market.
And one thing that many of these chargers have in common is the rather long cable.
This one in particular has a ~1.00 meter cable hard wired from the charger to the mini USB plug.
On the charger's back, an additional three illuminated USB ports can be found.
Suspecting a voltage drop on the charger's cable I ran one last test.
Raspberry Pi
RPi plugged into charger's USB1 <----- using a different/shorter cable instead of the PS hard wired one.
Drive plugged into RPi's USB1
Power plugged into RPi's USB2
Result: works
So there it is ...
Not the RPi or the charger but the long cable causing a voltage drop.
Conclusion
The RPi on can run a HDD with a 700mA draw (using two USB ports) provided the charger is working properly.
I have not added anything else yet (keyboard, mouse, HDMI cable) but I still have two free USB ports on the charger.
This charger was evidently hindered by the long/small gauge cable.
I'll see if I can figure out how to take it apart without destroying the case to eliminate/shorten the long cable by 60% or replace it with a heavier gauge USB cable.
An example ...
Yes, I have seen that disk start up can be 1.5 to 2.0 x the stated draw on the label.
Usually not advertised in the brochure unless expensive server stuff for IBM, Sun, Dell.
The USB 2.0 Specification ...
Have a look at the link to the RPi power stats.
I've read that the RPi does not follow the power spec too closely if at all.
... Global limitation of 600mA ...
The RPi3+ has a default 600mA global but can be used at 1200mA global with the proper setting in the /boot/config.txt file.
... hard drive that is very very low power ...
The Kingston 120Gb SSD I have my workstation's system on draws 1.0A.
... find a very low power harddrive ...
I once heard of a Western Digital HDD specially made for the RPi.
It had a USB3.0 port instead of the usual SATA but it seems to have been discontinued.
All the 2.5" SATA drives I have come across have a peak draw of 1.0A.
I'm set on using these Samsung HDD because they are just 40Gb and are just short of indestructible.
I used them for years to back up my office/maintenance files and as my storage needs grew, ended up in a drawer.
Now I can use them again as they are perfect for the use I'll give the RPi.
Thanks a lot for your input.
Cheers,
A.
]]>unfortunatly you couldn't check '/proc/config.gz' because its not present..
Have you done a
modprobe configs
before? After that /proc/config.gz is present on my RPi3 and RPi4, but before it wasn't ...
Best Regards, FM_81
]]>I also tested a lot, but with the power supply I have.. no way( I need to find another way.. ), I have rpi1, which I believe is more limited than rpi3..
The hard-drives disks, don't spin..
An example case:
I have a NAS( 3 Seagate Ironworlf disks ),
After startup, power consumption goes around 22-25Watts( normal operation ),
But when disks start spinning at beginning... I see in my PowerMeter spikes of around ~60Watts.. which is more than 2x the power consumption in operation..
Yes they are brief, but they are there..
Then around 40watts, after that they start consuming ~20-25watts( normal operation )..
My NAS disks are 3.5"( with 2.5" disks numbers are off-course a lot lower accordingly.. ), but it gives me the notion of power needed to start a drive vs normal utilization( after spinning up the plates )..
The USB 2.0 Specification says that is can deliver "5 units of 100mA each", so by the Specification we are talking about 500mA Max( I believe its per port.. ).
One thing are Specifications, other thing is the real hardware around which is made to be cheap, so it can be competitive..
chargers,power regulators, usb hubs, circuitry limitation designs, Lots of factors..
Yeah,
I would say that, if it has a Global limitation of 600mA,
The best option would be to find a hard drive that is very very low power( which nowadays will be each time more difficult to find.. ).
If you find a very low power harddrive, that works well on this devices,
Please let us know
... seems to be compiled in the kernel.
... couldn't check '/proc/config.gz' because its not present.
I see ...
... disk is 2.5"?
Yes.
On your reply, I decided that it would be be a good idea to step back a bit and look at this from the hardware side.
So I ran some additional tests.
All tests are with machines running Devuan ascii 2.0
32-bit version on a netbook / 64-bit version on a WS and the RPi3B+
There are various testing stages:
Stage 1
Netbook
Drive plugged into USB1
Power plugged into USB2
Result: works as expected, properly detected and accesible.
Stage 2
Workstation
Drive plugged into USB1
Power plugged into USB2
Result: works as expected, properly detected and accesible.
Stage 3
Raspberry Pi
Drive plugged into USB1
Power plugged into USB2
Result: does not work
Stage 3-1
Raspberry Pi
Drive plugged into USB1
Power plugged into netbooks' USB1
Result: does not work
Stage 3-2
Raspberry Pi
Drive plugged into USB1
Power plugged into workstation's USB1
Result: does not work
Stage 3-3
Raspberry Pi
Drive plugged into USB1
Power plugged into PS USB charging port
Result: works 8^o!
Great, problem solved but ...
This drive draws ~700mA and probably uses a bit more to start up.
The USB ports in both the netbook and the workstation obviously provide enough power.
ie: Port USB1 + Port USB2 in each machine provide enough power for the drive
Now, if the drive does not work when using power from the workstation/netbook USB ports, it begs the question:
How much power are/voltage the RPi's USB ports providing then?
Obviously less than the 500mA that they should be.
The red light stays on, no indication of a power issue.
The RPi's power supply (says) it is rated at 5.0v 5100mA max, more than the usual 2500/3000mA.
By default, the RPi USB ports are rated at a max global of 600mA but a line in the /boot/config.txt file sets it to 1200mA max.
max_usb_current=1
... could be the same problem I have ...
Don't know if it is the same but it is definitely (like you said) a power supply problem.
I think that the PS I have can probably manage the stated 5100mA but not at a stable 5.0V.
Which is why the drive won't spin.
I think it is a smartphone type charger and those are not necessarily made to put out rock stable 5.0v as they are used to charge 3.8 volt Li-ion/Li-iPo batteries.
I'll have to look for something else.
Thank you very much for you input, you have been most helpful.
Kudos, you had it right from the start. ;^ )
Now I can see about installing the image in the SDD.
Cheers,
A.
]]>unfortunatly you couldn't check '/proc/config.gz' because its not present..
your HD disk is 2.5"?
insert it with both USB ports(including) the power supply, and do a dmesg, to check if its controller is detected.
check with: 'sg_scan -i' and 'sg_map -sd', probably it will appears as '/dev/sg0' and would be mapped to '/dev/sda'
check also with 'lsblk'
It could be the same problem I have( in my case I suspect of power supply because my board is badly powered.. that's why I also tested with a pendrive.. )
You have I think 4x usb2.0,
If you had at least a real usb3.0( since it can negotiate more power deliver ), but then again, if power supply for the base board is not enough, having usb3.0 will not help because the power will end delivered in all by the power supply first..
My USB Harddrive adapter controller is detected,
But not enough power for him and also to power the disk
In your config you have 2 things:
1) a USB<->Sata adapter
2) a Harddrive
both consume power, the harddrive should consume more, and so maybe you get the USB<->Sata adapter, detected, but not the disk
This is what hapens in my case:
[34772.896837] usb 1-1.2: Manufacturer: ASMedia
[34772.901150] usb 1-1.2: SerialNumber: 00000000000000000000
[34772.919034] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[34772.932325] scsi host0: usb-storage 1-1.2:1.0
[34773.955039] scsi 0:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 5
[34773.975426] sd 0:0:0:0: [sda] Attached SCSI removable disk
[34773.984745] sd 0:0:0:0: Attached scsi generic sg0 type 0
[34793.627510] usb 1-1.2: USB disconnect, device number 7
[34803.653748] usb 1-1.2: new high-speed USB device number 8 using dwc2
[34804.107548] usb 1-1.2: New USB device found, idVendor=174c, idProduct=5106, bcdDevice= 0.01
[34804.116038] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[34804.123406] usb 1-1.2: Product: AS2105
[34804.127295] usb 1-1.2: Manufacturer: ASMedia
[34804.131600] usb 1-1.2: SerialNumber: 00000000000000000000
[34804.147473] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[34804.163076] scsi host0: usb-storage 1-1.2:1.0
[34805.235612] scsi 0:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 5
[34805.256014] sd 0:0:0:0: [sda] Attached SCSI removable disk
[34805.265445] sd 0:0:0:0: Attached scsi generic sg0 type 0
In my case it has only power to conect to the USB<->Sata controller, but not to provide the suficient power to the disk controllers and mottors to spin the disks.. so dmesg ends like that..
Regards,
... experiment in the rpi3 with a flash pen drive ...
Let's see:
groucho@rpidevuan:~$ dmesg
[ 1562.439264] usb 1-1.3: new high-speed USB device number 5 using dwc_otg
[ 1562.647134] usb 1-1.3: New USB device found, idVendor=0951, idProduct=1665
[ 1562.647349] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1562.647541] usb 1-1.3: Product: DataTraveler 2.0
[ 1562.647665] usb 1-1.3: Manufacturer: Kingston
[ 1562.647782] usb 1-1.3: SerialNumber: 50E549C693551F61991E1D42
[ 1562.649518] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 1562.653027] scsi host0: usb-storage 1-1.3:1.0
[ 1563.699699] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 0000 PQ: 0 ANSI: 4
[ 1563.701152] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1563.703372] sd 0:0:0:0: [sda] 15151168 512-byte logical blocks: (7.76 GB/7.22 GiB)
[ 1563.705501] sd 0:0:0:0: [sda] Write Protect is off
[ 1563.705667] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 1563.707595] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1563.718191] sda: sda1 sda2
[ 1563.726191] sd 0:0:0:0: [sda] Attached SCSI removable disk
groucho@rpidevuan:~$
root@rpidevuan:/home/groucho# sg_map -sd
/dev/sg0 /dev/sda
root@rpidevuan:/home/groucho#
... just in case, to check if it works..
It does.
... sort that out, maybe (if the config is present in the kernel)
groucho@rpidevuan:~$ zgrep -Ei "_USB_STORAGE|_BLK_DEV_SD" /proc/config.gz
gzip: /proc/config.gz: No such file or directory
groucho@rpidevuan:~$
... need that module.
Quite so.
... test with a usb pendrive
See above.
What to do now?
Thanks a lot for your help.
Cheers,
A.
]]>It could be..
But I would experiment in the rpi3 with a flash pen drive, just in case, to check if it works..
Anyway,
You can sort that out, maybe( if the config is present in the kernel.. )..
zgrep -Ei "_USB_STORAGE|_BLK_DEV_SD" /proc/config.gz
1) If its not present then its what we were expecting..
You will need that module..
2) If everything seems ok to you,
With is been available, compiled not as a module[ =y ]
then I advice to test with a usb pendrive
Check if it was compiled in the kernel
]]>... suspect of a power supply problem.
I don't think so.
In my Devuan ascii workstation ...
groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1 (2020-01-20) x86_64 GNU/Linux
groucho@devuan:~$
groucho@devuan:~$ lsmod | grep -i usb
usb_storage 73728 2 uas
usbserial 49152 1 pl2303
usbhid 53248 0
hid 122880 2 hid_generic,usbhid
usbcore 253952 10 usbhid,usb_storage,ehci_hcd,uhci_hcd,usbserial,xhci_pci,uas,pl2303,xhci_hcd,ehci_pci
scsi_mod 225280 11 aic7xxx,sd_mod,usb_storage,scsi_transport_sas,mptscsih,libata,scsi_transport_spi,uas,sr_mod,sg,mptsas
usb_common 16384 1 usbcore
groucho@devuan:~$
... when I plug the drive in, I get this:
groucho@devuan:~$ sudo dmesg -C
groucho@devuan:~$ sudo dmesg
[ 497.160012] usb 4-6: new high-speed USB device number 6 using ehci-pci
[ 497.313765] usb 4-6: New USB device found, idVendor=05e3, idProduct=0702
[ 497.313769] usb 4-6: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[ 497.313772] usb 4-6: Product: TS0MHDENC
[ 497.313775] usb 4-6: Manufacturer: Transcend
[ 497.314304] usb-storage 4-6:1.0: USB Mass Storage device detected
[ 497.314372] usb-storage 4-6:1.0: Quirks match for vid 05e3 pid 0702: 520
[ 497.314424] scsi host8: usb-storage 4-6:1.0
[ 498.339040] scsi 8:0:0:0: Direct-Access SAMSUNG MP0402H 0811 PQ: 0 ANSI: 0
[ 498.339464] sd 8:0:0:0: Attached scsi generic sg6 type 0
[ 498.340280] sd 8:0:0:0: [sdf] 78242976 512-byte logical blocks: (40.1 GB/37.3 GiB)
[ 498.341520] sd 8:0:0:0: [sdf] Test WP failed, assume Write Enabled
[ 498.342771] sd 8:0:0:0: [sdf] Cache data unavailable
[ 498.342776] sd 8:0:0:0: [sdf] Assuming drive cache: write through
[ 498.355294] sdf: sdf1
[ 498.359398] sd 8:0:0:0: [sdf] Attached SCSI disk
groucho@devuan:~$
... when I attach a 2.5" disk, I see it ...
I see it as /dev/sg6:
groucho@devuan:~$ sudo sg_map -sd
/dev/sg0
/dev/sg1 /dev/sda
/dev/sg2 /dev/sdb
/dev/sg3 /dev/sdc
/dev/sg4 /dev/sdd
/dev/sg5 /dev/sde
/dev/sg6 /dev/sdf <--- here it is
groucho@devuan:~$
... also 'sg_scan -i' ...
I also see it there:
groucho@devuan:~$ sudo sg_scan -i
/dev/sg0: scsi1 channel=0 id=0 lun=0 [em]
TSSTcorp CDDVDW SH-222AB SB00 [rmb=1 cmdq=0 pqual=0 pdev=0x5]
/dev/sg1: scsi5 channel=0 id=0 lun=0 [em]
ATA KINGSTON SV300S3 BBF0 [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg2: scsi7 channel=0 id=0 lun=0
IBM-ESXS VPBA073C3ETS11 N A496 [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg3: scsi7 channel=0 id=1 lun=0
SEAGATE ST3300555SS T107 [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg4: scsi7 channel=0 id=2 lun=0
IBM-ESXS GNA073C3ESTT0Z N BH0D [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg5: scsi7 channel=0 id=3 lun=0
ATA SEAGATE ST32500N 3AZQ [rmb=0 cmdq=1 pqual=0 pdev=0x0]
/dev/sg6: scsi8 channel=0 id=0 lun=0 [em]
SAMSUNG MP0402H 0811 [rmb=0 cmdq=0 pqual=0 pdev=0x0] <---- here it is
groucho@devuan:~$
So I think we can rule out any power supply related issues.
The Transcend TS0MHDENC controller (05e3 pid 0702: 520) has ID 05e3:0702 and uses the GL811E chip made by Genesys Logic, which is supported in the Debian kernel through the usb-storage module.
Si it would seem that the problem is that the needed module is not part of the image.
Is there a way to load it or a driver?
Thanks a lot for your input.
Cheers,
A.
]]>I, for instance, with this Image on rpi1, and a pendrive inserted, have this on dmesg output:
root@stealth:~# dmesg|grep -Ei "usb-storage|scsi|sd" --color
[ 0.116884] SCSI subsystem initialized
[ 1.614692] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.669305] Loading iSCSI transport class v2.0-870.
[ 1.670782] usbcore: registered new interface driver usb-storage
[ 1.674223] sdhci: Secure Digital Host Controller Interface driver
[ 1.674248] sdhci: Copyright(c) Pierre Ossman
[ 1.775904] sdhost-bcm2835 20202000.mmc: loaded - DMA enabled (>1)
[ 1.776342] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.079053] mmc0: new high speed SDHC card at address 59b4
[ 9.642520] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 9.662141] scsi host0: usb-storage 1-1.2:1.0
[ 10.733319] scsi 0:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 5
[ 10.760260] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 10.854416] sd 0:0:0:0: Attached scsi generic sg0 type 0
[11946.453478] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[11946.469115] scsi host0: usb-storage 1-1.2:1.0
[11947.535614] scsi 0:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
[11947.551405] sd 0:0:0:0: [sda] 15769600 512-byte logical blocks: (8.07 GB/7.52 GiB)
[11947.563219] sd 0:0:0:0: Attached scsi generic sg0 type 0
[11947.575380] sd 0:0:0:0: [sda] Write Protect is off
[11947.580253] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[11947.588448] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[11947.623158] sda: sda1 sda2
[11947.637772] sd 0:0:0:0: [sda] Attached SCSI removable disk
root@stealth:~# dmesg|grep -Ei "usb-storage|scsi| sd " --color
[ 0.116884] SCSI subsystem initialized
[ 1.614692] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.669305] Loading iSCSI transport class v2.0-870.
[ 1.670782] usbcore: registered new interface driver usb-storage
[ 9.642520] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 9.662141] scsi host0: usb-storage 1-1.2:1.0
[ 10.733319] scsi 0:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 5
[ 10.760260] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 10.854416] sd 0:0:0:0: Attached scsi generic sg0 type 0
[11946.453478] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[11946.469115] scsi host0: usb-storage 1-1.2:1.0
[11947.535614] scsi 0:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
[11947.551405] sd 0:0:0:0: [sda] 15769600 512-byte logical blocks: (8.07 GB/7.52 GiB)
[11947.563219] sd 0:0:0:0: Attached scsi generic sg0 type 0
[11947.575380] sd 0:0:0:0: [sda] Write Protect is off
[11947.580253] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[11947.588448] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[11947.637772] sd 0:0:0:0: [sda] Attached SCSI removable disk
But I also doesn't have the usb-storage module,
Because it was built in[ =Y ]( not compiled has a module.. ).
And it works..
Now, when I attach a 2.5" disk, I see it as a /dev/sg0,
and I can run
# sg_map -sd
/dev/sg0 /dev/sda
also 'sg_scan -i',
But it doesn't appear as a block device, only the controller is detected, I suspect of a power supply problem..
... insert the drives ...
... with the 5v ...
... what you get with 'dmesg' ?
I have to check again, see below.
... the module was not compiled ....
Yes, I think you're right.
Support was not compiled into the kernel.
modinfo usb-storage
It confirms that usb-storage is not in the system:
groucho@rpidevuan:~$ sudo modinfo usb-stotage
[sudo] password for groucho:
modinfo: ERROR: Module usb-stotage not found.
groucho@rpidevuan:~$ find /lib/modules -name \*usb-storage\*.ko
groucho@rpidevuan:~$
This si a config for sub-storage, on kernel 5.4.x:
[
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
CONFIG_USB_UAS=m
... the SCSI sg driver..
It is part of sg3_utils
Just installed it.
--- snip ---
The following NEW packages will be installed:
libsgutils2-2 sg3-utils
--- snip ---
Added it to /etc/modules and rebooted:
groucho@rpidevuan:~$ lsmod
Module Size Used by
ipv6 516096 24
sg 36864 0
brcmfmac 274432 0
brcmutil 16384 1 brcmfmac
sha256_generic 20480 0
cfg80211 741376 1 brcmfmac
rfkill 32768 1 cfg80211
snd_bcm2835 40960 0
snd_pcm 126976 1 snd_bcm2835
snd_timer 36864 1 snd_pcm
snd 90112 3 snd_timer,snd_bcm2835,snd_pcm
sdhci_iproc 16384 0
vchiq 352256 1 snd_bcm2835
uio_pdrv_genirq 16384 0
uio 24576 1 uio_pdrv_genirq
groucho@rpidevuan:~$
This is dmesg with the sg module loaded:
groucho@rpidevuan:~$ dmesg | grep -i "error\|warning\|fail\|segfault\|fatal"
[ 0.812942] Error: Driver 'sdhost-bcm2835' is already registered, aborting...
[ 2.421514] random: 3 urandom warning(s) missed due to ratelimiting
[ 2.846463] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 2.852017] cfg80211: failed to load regulatory.db
groucho@rpidevuan:~$
groucho@rpidevuan:~$ dmesg | grep -i usb
[ 0.104319] usbcore: registered new interface driver usbfs
[ 0.104417] usbcore: registered new interface driver hub
[ 0.104568] usbcore: registered new device driver usb
[ 0.303073] usbcore: registered new interface driver lan78xx
[ 0.305142] usbcore: registered new interface driver smsc95xx
[ 0.770854] dwc_otg 3f980000.usb: DWC OTG Controller
[ 0.772811] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.774815] dwc_otg 3f980000.usb: irq 9, io mem 0x00000000
[ 0.780952] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.782967] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.784977] usb usb1: Product: DWC OTG Controller
[ 0.786941] usb usb1: Manufacturer: Linux 4.16.14-v8+ dwc_otg_hcd
[ 0.788925] usb usb1: SerialNumber: 3f980000.usb
[ 0.791621] hub 1-0:1.0: USB hub found
[ 0.796676] usbcore: registered new interface driver usb-storage
[ 0.823327] usbcore: registered new interface driver usbhid
[ 0.825439] usbhid: USB HID core driver
[ 1.203380] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.394850] usb 1-1: New USB device found, idVendor=0424, idProduct=2514
[ 1.397220] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.400429] hub 1-1:1.0: USB hub found
[ 1.687369] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 1.777885] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514
[ 1.780230] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.783450] hub 1-1.1:1.0: USB hub found
[ 2.663363] usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg
[ 2.754116] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800
[ 2.756640] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.971360] usbcore: registered new interface driver brcmfmac
groucho@rpidevuan:~$
No USB related errors and drive not detected/recognised.
ie: idVendor=05e3, idProduct=0702
Thanks in advance,
A.
]]>it could be that the module was not compiled for it..
if you do:
modinfo usb-storage
what is the output?
you can also do:
find /lib/modules -name \*usb-storage\*.ko to check..
This si a config for sub-storage, on kernel 5.4.x:
[
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
CONFIG_USB_UAS=m
you need also the SCSI sg driver..
I see it there but not been used..
regards,
]]>