Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1 2

#1 2020-04-27 13:00:53

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

ascii installer-ARM64 question

Hello:

Although not entirely convinced that there are no dumb questions ...

I'm wanting to install Devuan ascii on a Raspberry Pi 3B+ (when it gets here) but would like to use the same Devuan version I have on my workstation and not a Raspbian version if at all possible without hitting a glitch at some point.

The idea is to have a setup as familiar as possible, if that makes any sense.

My search got me here.

The thing is that I can't find the usual *.iso file, just these directories/files:

../
cdrom/                                             08-May-2019 16:37                   -
device-tree/                                       08-May-2019 16:37                   -
netboot/                                           08-May-2019 16:37                   -
MANIFEST                                           08-May-2019 16:37                3947
MANIFEST.udebs                                     08-May-2019 16:37               11424
MD5SUMS                                            08-May-2019 16:37               22425
SHA256SUMS                                         08-May-2019 16:37               30533
udeb.list                                          08-May-2019 16:37                3390

As I've always used *.iso files and/or installer CDs,  I'd appreciate some guidance with respect to this.

Thanks in advance.

A.

Offline

#2 2020-04-27 14:03:23

HevyDevy
Member
Registered: 2019-09-06
Posts: 358  

Re: ascii installer-ARM64 question

I installed raspbian many years ago on one of the rpi2's i think. From memory its a process of flashing the filesystem onto an sd card. Take a look at the lakka documentation, very similar. I haven't researched how devuan does it as i dont have an rpi anymore.

http://www.lakka.tv/doc/Alternative-ima … g-methods/

edit: looks like you would need to build your own image via simple distro kit?

https://devuan.org/os/distro-kit

Last edited by HevyDevy (2020-04-27 14:10:36)

Offline

#3 2020-04-27 14:24:13

HevyDevy
Member
Registered: 2019-09-06
Posts: 358  

Re: ascii installer-ARM64 question

Ok so found some rather old arm64 embedded images that are still available, but from 2018.

https://mirror.leaseweb.com/devuan/devu … /embedded/

Offline

#4 2020-04-27 15:52:19

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

HevyDevy wrote:

... flashing the filesystem onto an sd card.

Yes.
That is how it is done if you want to install Devuan/Raspbian.

And there are Raspbian image files available in the downloads section at Dev1.

HevyDevy wrote:

... found some rather old arm64 embedded images ...

Yes, they are a mirror of the above.

But as I mentioned, I would like to install Devuan ascii ARM64 (not Raspbian) in my RPi 3B+ but I don't know how to use the files I found in the link mentioned in my OP.

ie:

../
cdrom/                                             08-May-2019 16:37                   -
device-tree/                                       08-May-2019 16:37                   -
netboot/                                           08-May-2019 16:37                   -
MANIFEST                                           08-May-2019 16:37                3947
MANIFEST.udebs                                     08-May-2019 16:37               11424
MD5SUMS                                            08-May-2019 16:37               22425
SHA256SUMS                                         08-May-2019 16:37               30533
udeb.list                                          08-May-2019 16:37                3390

 

Thanks for your input.

Cheers,

A.

Last edited by Altoid (2020-05-19 13:04:42)

Offline

#5 2020-04-28 06:24:38

HevyDevy
Member
Registered: 2019-09-06
Posts: 358  

Re: ascii installer-ARM64 question

Bit of a miscommunication here i think. Im fairly certain those images are devuan ascii only for the raspberry pi not raspbian images.
I think the live sdk will source those files from the link in your op, not 100% certain. Im might give this a try myself as im thinking of getting an RPi3 to use as a netflix box.

edited for my dyslexia in typing wink

Last edited by HevyDevy (2020-04-28 06:30:09)

Offline

#6 2020-04-28 10:26:50

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

HevyDevy wrote:

Bit of a miscommunication ...

Indeed ...
Sorry about that.

HevyDevy wrote:

... images are devuan ascii ...
... not raspbian images.

I see.
My bad then.

I guess I let the raspi bit lead me to that.
I understood that it was Raspbian -> Devuan thing in the same way/sense that Debian -> Devuan. 8^7

HevyDevy wrote:

... live sdk will source those files from the link in your op ...

No idea, I've never used that.

Up to now, my experience in Linux has been only with installers (*.iso files), live images (*.img) and the generation of live images with Refracta.
I understand that installing is not the same as dd'ing a live image to a drive as I have to make changes to the original installation to generate a new image file.

Which is why I was looking for a way to install and not burn an image. 

HevyDevy wrote:

... dyslexia in typing

Happens a lot to me also. =-/

I'll have a look at what the sdk says but it seems that for the time being, dd'ing an *.img file is the only path I have to putting Devuan ascii on the RPi3b+.

Thanks a lot for your input.

Cheers,

A.

Offline

#7 2020-04-28 11:44:54

HevyDevy
Member
Registered: 2019-09-06
Posts: 358  

Re: ascii installer-ARM64 question

Sorry i should have pointed the link to the correct sdk which is arm-sdk, its a fairly simple process as long as dependencies are met. I managed to do the live-sdk awhile back but will try the arm-sdk tommorow when i have some spare time up my sleeve.

https://git.devuan.org/sdk/arm-sdk

This will build you a image for use on a rpi3

Offline

#8 2020-04-28 12:54:11

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

HevyDevy wrote:

... should have pointed the link to the correct sdk ...

No problem.
From what I have read, it's well over my head at the moment.

HevyDevy wrote:

... try the arm-sdk tommorow when i have some spare time up my sleeve.

Thanks.
No hurry.

The local postal service is usually quite lacking and the CV quarantine has only made things worse.
As a result, the whole of my RPi3B+ kit has been stuck for almost a week at the city's mail distribution centre.
All three packages.

HevyDevy wrote:

This will build you a image for use on a rpi3

That would be great.
Thanks a lot.

Q: Would this one be different than the one available here?

ie:

devuan_ascii_2.0.0_arm64_raspi3.img.xz   06-Jun-2018 11:28   153M

If it is more or less the same, I would not want you to bother if that *.img works just as well. 

I have been reading some posts here regarding Devuan ascii on the RPi+B+ and it seems that (save the image files) there's no other option at the moment.
We'll just have to wait and see if there's interest in generating an installer.
In the meantime we have parazyd's great work uploading the RPi images.

All Devuan/RPi users owe him a big Thank You.

My RPi3B+ will be (almost) exclusively dedicated to running a 64-bit coffee roasting application (Artisan-Scope v2.12) for which 32-bit support was ended at v1.1.
My Asus 2Gb 1000HE (Atom N280) struggles with it and although the souce is available, it would not make sense to build a v2.12 32-bit as it would probably run much slower than v1.1.

Only maintenance, networking or WiFi printing, some basic image viewer + basic OpenBox would be installed so that all the RPi's remaining resources go to running the roasting software.

I'll most probably have to use the Raspbian downloaded from raspberripi.org, put up with systemd and see how to streamline it as much as possible till someone builds an ARM64 installer.

Thanks a lot for your input.

Cheers,

A.

Offline

#9 2020-04-28 16:12:27

HevyDevy
Member
Registered: 2019-09-06
Posts: 358  

Re: ascii installer-ARM64 question

I could not tell you differences in the images hosted to those that are built via arm-sdk. Give it a go, spend a some time educating yourself on the subject matter.

I know alpine linux has ready images for raspi3 and instructions to create said images with a persistent installation. When i get an rpi3 i will probably be doing a lot of testing, but for systemd free i believe alpine linux might trump devuan all things considered.

https://alpinelinux.org/downloads/

Offline

#10 2020-04-28 16:41:48

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

HevyDevy wrote:

... could not tell you differences in the images hosted ...

I see.

HevyDevy wrote:

... spend a some time educating yourself ...

Indeed ...

That's what I am doing with/in Devuan, where I arrived after a few years of going through a few of the mainline Linux distributions, both *.deb and *.rpm based.   
But I have to draw a line somewhere as I am not a software chap, more a hardware one.
Tech support helped me make a living when my degree in architecture would not.

Reasonably well educated (for what I needed) in *.bat files, I'm still struggling with understanding bash scripts and the language, so the idea of even attempting to tackle a sdk is remote.

HevyDevy wrote:

... images for raspi3 and instructions to create said images with a persistent installation.

Thanks for the heads up.
I'll have a look at them.

HevyDevy wrote:

... for systemd free ...
... alpine linux might trump devuan ...

Thanks, but I am set on staying with Devuan the same way I was set on staying with Debian till systemd reared its head.
I always say that it reminds me of the registry virus inside Windows OSs, with which I dealt for quite a long time.

Thanks a lot for your input.

Cheers,

A.

Offline

#11 2020-04-28 21:09:51

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

HevyDevy wrote:

... alpine linux has ready images for raspi3 ...

While looking around for information regarding Alpine Linux, I came across this.

Alpine Raspberry PI

This is a system install of Alpine linux for Raspberry Pi 3B, 3B+ and 4 image ready to burn to an SD card via balenaEtcher
(there's no need to gunzip image).

The image automatically setup and configures:

    root user [pwd: raspberry]
    pi user [pwd: raspberry]
    ethernet
    wifi (edit wpa_supplicant.conf in the boot partition, on first boot it will be copied)
    bluetooth
    avahi
    swap
    openssh server
    root partition auto-expand on first boot

I'll give it a try as it seems to be quite straightforward.

Cheers,

A.

Offline

#12 2020-04-30 18:44:56

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

Altoid wrote:

Hello:
Yes.
That is how it is done if you want to install Devuan/Raspbian.

And there are Raspbian image files available in the downloads section at Dev1.

There are there arm64 devuan images for rpi3 smile

Like this one

Best Regards,
tux

Offline

#13 2020-05-01 18:23:25

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

tuxd3v wrote:

There are there arm64 devuan images for rpi3

Yes, I have installed the one I pointed out in my OP.

groucho@rpidevuan:~$ uname -a
Linux rpidevuan 4.16.14-v8+ #1 SMP PREEMPT Tue Jun 5 18:50:10 CEST 2018 aarch64 GNU/Linux
groucho@rpidevuan:~$

Till I get my cable/adaptor, I have managed to learn some SSH and am working on my RPi ascii from my Devuan ascii workstation.
Reminds me of my long gone DOS 5.0 days.

But ...
I need to have the usb-storage module loaded so as to be able to use my external usb drives with the RPi, but it seems that it's not part of the image.

groucho@rpidevuan:~$ lsmod | grep usb
groucho@rpidevuan:~$ 
groucho@rpidevuan:~$ lsmod
Module                  Size  Used by
sg                     36864  0
ipv6                  516096  24
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:~$

And seems that it cannot/will not be installed.

root@rpidevuan:/home/groucho# modprobe usb-storage
root@rpidevuan:/home/groucho# lsmod | grep usb
root@rpidevuan:/home/groucho# lsmod
Module                  Size  Used by
sg                     36864  0
ipv6                  516096  24
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
root@rpidevuan:/home/groucho#

Is there a way around this problem?

Edit:
I have been running some tests.

1.
The drives draw 700mA and work perfectly well in both my workstation and netbook running Devuan ascii but only using the provided power cable.
ie: a second USB cable to give +5.00v through an ad hoc plug. I have two of them and both exhibit the same behaviour.
2.
The drives' controller chipset is identified by lsusb as ID 05e3:0702 Genesys Logic, Inc. USB 2.0 IDE Adapter [GL811E], which is supported by the kernel using the usb-storage module. I guess it makes sense that they are not recognised as the needed module is not present. (?)
3.
My two other external HDDs (USB3.0) work without issue on the RPi3B+3 but the controllers use another chipset identified as ID 043e:70f5 LG Electronics USA, Inc. External HDD.
They are 500Gb USB3, not much sense to use them with my RPi.

Thanks in advance.

A.

Last edited by Altoid (2020-05-02 00:56:30)

Offline

#14 2020-05-02 06:07:51

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

hello Altoid,
when you insert the drives in the usb, powered with the 5v, everything ok, what you get with 'dmesg' ?

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,

Last edited by tuxd3v (2020-05-02 06:19:41)

Best Regards,
tux

Offline

#15 2020-05-02 12:24:45

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

tuxd3v wrote:

... insert the drives ...
... with the 5v ...
... what you get with 'dmesg' ?

I have to check again, see below.

tuxd3v wrote:

...  the module was not compiled ....

Yes, I think you're right.
Support was not compiled into the kernel.

tuxd3v wrote:

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
tuxd3v wrote:

... 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.

Offline

#16 2020-05-02 18:14:20

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

hello,
You can test it with a usb pen drive, and Eliminate the power consumption variable of the hard drive smile

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..

Last edited by tuxd3v (2020-05-02 18:18:03)

Best Regards,
tux

Offline

#17 2020-05-02 20:15:34

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

tuxd3v wrote:

... 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:~$
tuxd3v wrote:

... 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:~$
tuxd3v wrote:

... 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.

Offline

#18 2020-05-02 22:11:02

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

hello Altoid,

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 smile

Last edited by tuxd3v (2020-05-02 22:14:40)

Best Regards,
tux

Offline

#19 2020-05-02 22:56:10

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello tux:

tuxd3v wrote:

... 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#
tuxd3v wrote:

... just in case, to check if it works..

It does.

tuxd3v wrote:

... 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:~$
tuxd3v wrote:

... need that module.

Quite so.

tuxd3v wrote:

... test with a usb pendrive

See above.

What to do now?

Thanks a lot for your help.

Cheers,

A.

Offline

#20 2020-05-02 23:17:19

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

You welcome,
yeah it seems to be compiled in the kernel.. smile

unfortunatly you couldn't check '/proc/config.gz' because its not present.. sad

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 sad

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 sad

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,

Last edited by tuxd3v (2020-05-02 23:49:05)

Best Regards,
tux

Offline

#21 2020-05-03 02:52:53

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello again:

tuxd3v wrote:

... seems to be compiled in the kernel.
... couldn't check '/proc/config.gz' because its not present.

I see ...

tuxd3v wrote:

... 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
tuxd3v wrote:

... 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.

Last edited by Altoid (2020-05-03 02:59:44)

Offline

#22 2020-05-03 04:57:34

tuxd3v
Member
Registered: 2019-11-14
Posts: 183  

Re: ascii installer-ARM64 question

You welcome,
The important thing is that you managed to take some conclusions from it, and see the limitations you have on your config.. smile

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.. sad

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 smile

Best Regards,
tux

Offline

#23 2020-05-03 08:28:35

FM81
Member
Registered: 2017-09-16
Posts: 30  

Re: ascii installer-ARM64 question

tuxd3v wrote:

unfortunatly you couldn't check '/proc/config.gz' because its not present.. sad

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

The most brilliant role in comedy is that of a fool, he must not be in order to make it seem. (Miguel de Cervantes)

Offline

#24 2020-05-03 12:17:12

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

tuxd3v wrote:

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.

tuxd3v wrote:

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.

tuxd3v wrote:

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.

tuxd3v wrote:

... 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.

tuxd3v wrote:

... hard drive that is very very low power ...

The Kingston 120Gb SSD I have my workstation's system on draws 1.0A.

tuxd3v wrote:

... 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.

Offline

#25 2020-05-03 12:22:25

Altoid
Member
Registered: 2017-05-07
Posts: 1,583  

Re: ascii installer-ARM64 question

Hello:

FM81 wrote:

... 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.

Offline

Pages: 1 2

Board footer

Forum Software