Arm-dev

arm-dev@lists.centos.org

686 discussions

How to enable i2c
by Philip Manuel 06 Jan '19

06 Jan '19

Hi, I've added the following parameters to /boot/cmdline.txt i2c_arm=on i2c1=on i2c0=on but I get no /dev/i2c* entries, but dmesg shows i2c /dev entries driver What am I missing ? Thanks Phil

4 4

Odroid HC1 working with 1810 image
by Robert Moskowitz 02 Jan '19

02 Jan '19

Pablo's special 4.19 1820 image is working for my Odroid HC1. I have pushed out my documentation at: http://medon.htt-consult.com/CentOS7-armv7-odroid.html with my general documentation at: http://medon.htt-consult.com/CentOS7-armv7.html thanks for all the help here!

1 0

HC1 - Kernel error reported by logwatch
by Robert Moskowitz 02 Jan '19

02 Jan '19

On my Odroid HC1 running the 4.19 kernel, I see in the logwatch email: --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present WARNING: CPU(s) started in wrong/inconsistent mo ...: 3 Time(s) [drm:exynos_drm_bind [exynosdrm]] *ERROR* no device found ...: 3 Time(s) ---------------------- Kernel End ------------------------- Greping in messages I found: Dec 31 19:00:05 hc1-c7 kernel: CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a) Dec 31 19:00:06 hc1-c7 kernel: CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a) Dec 31 19:00:06 hc1-c7 kernel: CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a) Dec 31 19:00:05 hc1-c7 kernel: CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a) and Dec 31 19:00:07 hc1-c7 kernel: [drm:exynos_drm_bind [exynosdrm]] *ERROR* no device found for DMA mapping operations. Dec 31 19:00:07 hc1-c7 kernel: [drm:exynos_drm_bind [exynosdrm]] *ERROR* no device found for DMA mapping operations. Dec 31 19:00:08 hc1-c7 kernel: [drm:exynos_drm_bind [exynosdrm]] *ERROR* no device found for DMA mapping operations. Dec 31 19:00:07 hc1-c7 kernel: [drm:exynos_drm_bind [exynosdrm]] *ERROR* no device found for DMA mapping operations. Anything to do about these? thanks

1 0

Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3
by Mark Verlinde 20 Dec '18

20 Dec '18

-----Oorspronkelijk bericht----- > Afzender:Mark Verlinde <mark(a)havak.nl> > Verstuurd: Zaterdag 15 December 2018 15:17 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3 > > -----Oorspronkelijk bericht----- > > Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > > Verstuurd: Zaterdag 15 December 2018 14:06 > > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > > Onderwerp: Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3 > > > > > > El 15/12/18 a las 08:58, Pablo Sebastián Greco escribió: > > > > > > That is my guess too, but we're providing this kernel also > > > (http://mirror.centos.org/altarch/7.6.1810/kernel/aarch64/Packages/) > > > which is pretty close to the Fedora kernel. > > > So if you could create a ISO with that kernel, it "should" work. > > > > > I meant, to upstream kernel. The one that is close to Fedora is 4.19 > > from here > > https://armv7.dev.centos.org/repodir/community-kernel-latest/kernel/4.19.7-…, > > but that is only built for armhfp at the moment. > > Some while ago did some work on this, resulting in a prematurely image with a at the time of creation latest kernel 4.18.16-202. As you understood, I took the "uboot" route instead of tianocore Updated the image to CentOS 7.6.1810 and kernel 4.19.7-300 with minor changes: * SElinux is set to enforcing (did no testing sofar though..) * included brcmfmac43430-sdio.txt and brcmfmac43455-sdio.txt for wifi RPI3(+) > It was not my intention to make a aarch64 image for a RPI, nor will it be in the future; > Just out of "academic curiosity " installed bcm283x-firmware and rpi3-u-boot.bin to try to boot it with a RPI. And it did :) > > _Note_ this is far from anything decent at least it boots :) (1) > https://drive.google.com/open?id=1RIWYxPadxsf_M-igFxPaP8FmwKA3Jcki Link for updated img is unchanged > > It boots very slow! Especially on a RPI going through bootcode.bin > uboot > grubaa64.efi > grub2 > kernel > The kernel is cross complied from the equivalent community-kernel source package Pablo made for armhfp with the command (in which you may ignore --define="dist .ns7") : > rpmbuild --ba --target aarch64 --with=cross --without=perf --without=tools --without=debuginfo --define="dist .ns7" --define="_arch aarch64" --define="_build_arch aarch64" --define="__strip /usr/bin/aarch64-linux-gnu-strip" kernel.spec > > cross tools installed: > $ rpm -qa | grep aarch64 > binutils-aarch64-linux-gnu-2.27-9.el7.1.x86_64 > gcc-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 > gcc-c++-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 > > It's on my todo list to get this to a next level; > Maybe we can cooperate on this, though (as said before) it's not my intend to create (maintain) aarch64 RPI images. > > AFAIK now, are some of the issues to be dealt with: > * uboot-images-armv8 carry a fedora specific patch causing uboot to look in /EFI/fedora for grubaa64.efi > * obviously grubby has no understanding for the device-tree on aarch64 and most likely will never have this. > * livecd tools, used by the application tools to create images for armhfp has no aarch64 support. (2) > * probably a lot more... > > Grzt Mark > > (1)l link to kickstart file used to create image : > https://github.com/markVnl/nethserver-createimg/blob/ks_wip/ks/Centos-Uboot… > > (2) patch to provide basic aarch64 support for livecd tools / imgcreate, > _Note_ it does not provide full support, among other things EFI/centos/grub.cfg is not created... > https://github.com/markVnl/nethserver-createimg/blob/master/SPEC-appliance-… > > > > > > > > > > Pablo. > > > > > > El 14/12/18 a las 19:57, Gordan Bobic escribió: > > >> I'm hazarding a guess that the stock CentOS 7 aarch64 kernel isn't > > >> built to include support for the Pi. > > >> > > >> On Fri, 14 Dec 2018, 22:10 Steven Ellis <sellis(a)redhat.com > > >> <mailto:sellis@redhat.com> wrote: > > >> > > >> Ok so I've tried the CentOS-7-aarch64-Minimal-1810.iso with the > > >> UEFI tools from > > >> - https://github.com/andreiw/RaspberryPiPkg > > >> > > >> Can't get the ISO to boot. I've tried acpi=off but that hasn't > > >> made a difference. > > >> > > >> Any other tips? > > >> > > >> On Fri, 14 Dec 2018 at 18:39, Steven Ellis <sellis(a)redhat.com > > >> <mailto:sellis@redhat.com>> wrote: > > >> > > >> Has anyone got this working on a Pi3+ and can provide guidance. > > >> > > >> I've got UEFI working already but I haven't tried a generic > > >> aarch64 centos ISO yet > > >> > > >> On Wed, 28 Nov 2018 at 12:48, R > > >> <riccardo.veraldi(a)presid.infn.it > > >> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > > >> > > >> so for example I could just dd this image after > > >> uncompressing it on the SD card and this would work I Suppose > > >> > > >> http://vault.centos.org/altarch/7.4.1708/isos/aarch64/CentOS-7-aarch64.img.… > > >> > > >> > > >> On 11/27/18 7:09 AM, Gordan Bobic wrote: > > >>> AFAIK the official installer only boots on UEFI aarch64. > > >>> Otherwise you'll have to get a working image from somewhere. > > >>> > > >>> > > >>> On Tue, Nov 27, 2018 at 5:44 AM R > > >>> <riccardo.veraldi(a)presid.infn.it > > >>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > > >>> > > >>> ok thank you. > > >>> so does it mean that Pi 3 needs a UEFI firmware if I > > >>> Want to run CentOS/aarch64 while it does not need if > > >>> running CentOS/armhfp ? > > >>> thanks > > >>> > > >>> > > >>> On 11/26/18 3:05 PM, Gordan Bobic wrote: > > >>>> I haven't tried it yet, but you should be able to > > >>>> get UEFI firmware for Pi 3 from here: > > >>>> https://github.com/andreiw/RaspberryPiPkg > > >>>> > > >>>> If you can get that to boot off the ISO, you should > > >>>> be able to use the installer. > > >>>> > > >>>> On Mon, Nov 26, 2018 at 11:01 PM R > > >>>> <riccardo.veraldi(a)presid.infn.it > > >>>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > > >>>> > > >>>> Hello, > > >>>> > > >>>> I was wondering if there is a procedure for > > >>>> installing Centos 7 on the > > >>>> Raspberry Pi 3 B+ > > >>>> > > >>>> while installing Centos 7.5 on armhfp is very > > >>>> clear and documented given > > >>>> that a raw root image is provided and you just > > >>>> "dd" it on the memory card, > > >>>> > > >>>> it is not clear to me how to do it with > > >>>> aarch64. A ISO image is provided > > >>>> but how to install it on the raspberry ? > > >>>> > > >>>> thank you > > >>>> > > >>>> Rick > > >>>> > > >>>> > > >>>> _______________________________________________ > > >>>> Arm-dev mailing list > > >>>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > > >>>> https://lists.centos.org/mailman/listinfo/arm-dev > > >>>> > > >>>> > > >>>> _______________________________________________ > > >>>> Arm-dev mailing list > > >>>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > > >>>> https://lists.centos.org/mailman/listinfo/arm-dev > > >>> > > >>> > > >>> > > >>> _______________________________________________ > > >>> Arm-dev mailing list > > >>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > > >>> https://lists.centos.org/mailman/listinfo/arm-dev > > >> > > >> > > >> _______________________________________________ > > >> Arm-dev mailing list > > >> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > > >> https://lists.centos.org/mailman/listinfo/arm-dev > > >> > > >> > > >> > > >> -- > > >> > > >> Steven Ellis > > >> > > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > > >> > > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > > >> > > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > > >> > > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: > > >> +64 21 321 673 > > >> > > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > > >> <https://redhat.com/trusted> > > >> > > >> > > >> > > >> -- > > >> > > >> Steven Ellis > > >> > > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > > >> > > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > > >> > > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > > >> > > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: +64 21 > > >> 321 673 > > >> > > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > > >> <https://redhat.com/trusted> > > >> _______________________________________________ > > >> Arm-dev mailing list > > >> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > > >> https://lists.centos.org/mailman/listinfo/arm-dev > > >> > > >> > > >> _______________________________________________ > > >> Arm-dev mailing list > > >> Arm-dev(a)centos.org > > >> https://lists.centos.org/mailman/listinfo/arm-dev > > > > > > _______________________________________________ > > > Arm-dev mailing list > > > Arm-dev(a)centos.org > > > https://lists.centos.org/mailman/listinfo/arm-dev > > _______________________________________________ > > Arm-dev mailing list > > Arm-dev(a)centos.org > > https://lists.centos.org/mailman/listinfo/arm-dev > > > _______________________________________________ > Arm-dev mailing list > Arm-dev(a)centos.org > https://lists.centos.org/mailman/listinfo/arm-dev >

2 1

File system corruption
by Stephan Guilloux 17 Dec '18

17 Dec '18

Hello all, I noticed many many filesystem corruptions, after raspberry 3B reboot. For instance, with image Raspberry 1804, "yum update and reboot" made my RPM DB corrupted rather often after reboot. We found some other scenarios, but all less easy to reproduce. Somehow, we came to the conclusion that we had to start some kind of stressing tool, and this how it comes out: - install SD-Card with last CentOS image available (kernel 4.14.82) - create a 4Gb primary partition #4, starting at 2Gb with help of fdisk. - then, grow partition #3 with rootfs-expand. - format partition #4 as EXT4, with default parameters. In a stress-loop - mount partition #4 - copy huge number of files (/usr/) to partition #4 (cd /usr ; tar -c . ) | (cd /mnt/ ; tar -x) - umount part #4 - fsck on partition #4 The script breaks the loop when FSCK returns status different than 0. Only a couple of iterations are enough to crash partition #4. I just tried the same with EXT2, and result is identical. Any idea to make this "system" less vulnerable ?

6 15

Updated CentOS arm guide - please review
by Robert Moskowitz 16 Dec '18

16 Dec '18

I have updated my Centos arm guide: http://medon.htt-consult.com/CentOS7-armv7.html Note the case change per Pablo's request, and thus it is not yet linked in from the home page. I added a number of sections. A pointer to the Odroid HC1 page. I will work on this so it stands out more. Xfce desktop zram for swap - note that the repo listed does not work. Waiting on guidance from Marc on this one. Improvements on the Remote Management to support VNC to an Xfce desktop I will link this in once Pablo has the new image in production and at least the zram access works. thanks in advance for all comments

1 0

Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3
by Mark Verlinde 15 Dec '18

15 Dec '18

-----Oorspronkelijk bericht----- > Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Verstuurd: Zaterdag 15 December 2018 14:06 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3 > > > El 15/12/18 a las 08:58, Pablo Sebastián Greco escribió: > > > > That is my guess too, but we're providing this kernel also > > (http://mirror.centos.org/altarch/7.6.1810/kernel/aarch64/Packages/) > > which is pretty close to the Fedora kernel. > > So if you could create a ISO with that kernel, it "should" work. > > > I meant, to upstream kernel. The one that is close to Fedora is 4.19 > from here > https://armv7.dev.centos.org/repodir/community-kernel-latest/kernel/4.19.7-…, > but that is only built for armhfp at the moment. Some while ago did some work on this, resulting in a prematurely image with a at the time of creation latest kernel 4.18.16-202. It was not my intention to make a aarch64 image for a RPI, nor will it be in the future; Just out of "academic curiosity " installed bcm283x-firmware and rpi3-u-boot.bin to try to boot it with a RPI. And it did :) _Note_ this is far from anything decent at least it boots :) (1) https://drive.google.com/open?id=1RIWYxPadxsf_M-igFxPaP8FmwKA3Jcki It boots very slow! Especially on a RPI going through bootcode.bin > uboot > grubaa64.efi > grub2 > kernel The kernel is cross complied from the equivalent community-kernel source package Pablo made for armhfp with the command (in which you may ignore --define="dist .ns7") : rpmbuild --ba --target aarch64 --with=cross --without=perf --without=tools --without=debuginfo --define="dist .ns7" --define="_arch aarch64" --define="_build_arch aarch64" --define="__strip /usr/bin/aarch64-linux-gnu-strip" kernel.spec cross tools installed: $ rpm -qa | grep aarch64 binutils-aarch64-linux-gnu-2.27-9.el7.1.x86_64 gcc-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 gcc-c++-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 It's on my todo list to get this to a next level; Maybe we can cooperate on this, though (as said before) it's not my intend to create (maintain) aarch64 RPI images. AFAIK now, are some of the issues to be dealt with: * uboot-images-armv8 carry a fedora specific patch causing uboot to look in /EFI/fedora for grubaa64.efi * obviously grubby has no understanding for the device-tree on aarch64 and most likely will never have this. * livecd tools, used by the application tools to create images for armhfp has no aarch64 support. (2) * probably a lot more... Grzt Mark (1)l link to kickstart file used to create image : https://github.com/markVnl/nethserver-createimg/blob/ks_wip/ks/Centos-Uboot… (2) patch to provide basic aarch64 support for livecd tools / imgcreate, _Note_ it does not provide full support, among other things EFI/centos/grub.cfg is not created... https://github.com/markVnl/nethserver-createimg/blob/master/SPEC-appliance-… > > > > > > Pablo. > > > > El 14/12/18 a las 19:57, Gordan Bobic escribió: > >> I'm hazarding a guess that the stock CentOS 7 aarch64 kernel isn't > >> built to include support for the Pi. > >> > >> On Fri, 14 Dec 2018, 22:10 Steven Ellis <sellis(a)redhat.com > >> <mailto:sellis@redhat.com> wrote: > >> > >> Ok so I've tried the CentOS-7-aarch64-Minimal-1810.iso with the > >> UEFI tools from > >> - https://github.com/andreiw/RaspberryPiPkg > >> > >> Can't get the ISO to boot. I've tried acpi=off but that hasn't > >> made a difference. > >> > >> Any other tips? > >> > >> On Fri, 14 Dec 2018 at 18:39, Steven Ellis <sellis(a)redhat.com > >> <mailto:sellis@redhat.com>> wrote: > >> > >> Has anyone got this working on a Pi3+ and can provide guidance. > >> > >> I've got UEFI working already but I haven't tried a generic > >> aarch64 centos ISO yet > >> > >> On Wed, 28 Nov 2018 at 12:48, R > >> <riccardo.veraldi(a)presid.infn.it > >> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >> > >> so for example I could just dd this image after > >> uncompressing it on the SD card and this would work I Suppose > >> > >> http://vault.centos.org/altarch/7.4.1708/isos/aarch64/CentOS-7-aarch64.img.… > >> > >> > >> On 11/27/18 7:09 AM, Gordan Bobic wrote: > >>> AFAIK the official installer only boots on UEFI aarch64. > >>> Otherwise you'll have to get a working image from somewhere. > >>> > >>> > >>> On Tue, Nov 27, 2018 at 5:44 AM R > >>> <riccardo.veraldi(a)presid.infn.it > >>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >>> > >>> ok thank you. > >>> so does it mean that Pi 3 needs a UEFI firmware if I > >>> Want to run CentOS/aarch64 while it does not need if > >>> running CentOS/armhfp ? > >>> thanks > >>> > >>> > >>> On 11/26/18 3:05 PM, Gordan Bobic wrote: > >>>> I haven't tried it yet, but you should be able to > >>>> get UEFI firmware for Pi 3 from here: > >>>> https://github.com/andreiw/RaspberryPiPkg > >>>> > >>>> If you can get that to boot off the ISO, you should > >>>> be able to use the installer. > >>>> > >>>> On Mon, Nov 26, 2018 at 11:01 PM R > >>>> <riccardo.veraldi(a)presid.infn.it > >>>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >>>> > >>>> Hello, > >>>> > >>>> I was wondering if there is a procedure for > >>>> installing Centos 7 on the > >>>> Raspberry Pi 3 B+ > >>>> > >>>> while installing Centos 7.5 on armhfp is very > >>>> clear and documented given > >>>> that a raw root image is provided and you just > >>>> "dd" it on the memory card, > >>>> > >>>> it is not clear to me how to do it with > >>>> aarch64. A ISO image is provided > >>>> but how to install it on the raspberry ? > >>>> > >>>> thank you > >>>> > >>>> Rick > >>>> > >>>> > >>>> _______________________________________________ > >>>> Arm-dev mailing list > >>>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > >>>> https://lists.centos.org/mailman/listinfo/arm-dev > >>>> > >>>> > >>>> _______________________________________________ > >>>> Arm-dev mailing list > >>>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > >>>> https://lists.centos.org/mailman/listinfo/arm-dev > >>> > >>> > >>> > >>> _______________________________________________ > >>> Arm-dev mailing list > >>> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > >>> https://lists.centos.org/mailman/listinfo/arm-dev > >> > >> > >> _______________________________________________ > >> Arm-dev mailing list > >> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > >> https://lists.centos.org/mailman/listinfo/arm-dev > >> > >> > >> > >> -- > >> > >> Steven Ellis > >> > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > >> > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > >> > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > >> > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: > >> +64 21 321 673 > >> > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > >> <https://redhat.com/trusted> > >> > >> > >> > >> -- > >> > >> Steven Ellis > >> > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > >> > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > >> > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > >> > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: +64 21 > >> 321 673 > >> > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > >> <https://redhat.com/trusted> > >> _______________________________________________ > >> Arm-dev mailing list > >> Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> > >> https://lists.centos.org/mailman/listinfo/arm-dev > >> > >> > >> _______________________________________________ > >> Arm-dev mailing list > >> Arm-dev(a)centos.org > >> https://lists.centos.org/mailman/listinfo/arm-dev > > > > _______________________________________________ > > Arm-dev mailing list > > Arm-dev(a)centos.org > > https://lists.centos.org/mailman/listinfo/arm-dev > _______________________________________________ > Arm-dev mailing list > Arm-dev(a)centos.org > https://lists.centos.org/mailman/listinfo/arm-dev >

1 0

Re: [Arm-dev] Instructions for installation on an Odroid HC1
by Robert Moskowitz 13 Dec '18

13 Dec '18

Pablo, I have been busy on the Fedora-arm list getting F29 working on the Odroid-HC1. I figured if I could get F29 working, I could port that knowledge over to Centos-arm. More on what I accomplished later... I grabbed this image, dropped it on a uSD, did the various needed steps and tried to boot. It failed because there is nothing really in /boot! ============== U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1 CPU: Exynos5422 @ 800 MHz Model: Odroid XU3 based on EXYNOS5422 Board: Odroid XU3 based on EXYNOS5422 Type: hc1 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... Card did not respond to voltage select! *** Warning - No block device, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 MMC Device 1 not found no mmc device at slot 1 Card did not respond to voltage select! switch to partitions #0, OK mmc2 is current device Scanning mmc 2:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 685 bytes read in 4 ms (167 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 Boot Options. 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19.5-300.el7.armv7 hl) Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19 .5-300.el7.armv7hl) Retrieving file: /initrd-4.19.5-300.el7.armv7hl.img ** File not found /initrd-4.19.5-300.el7.armv7hl.img ** Skipping CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19.5-300.el7.armv 7hl) for failure retrieving initrd SCRIPT FAILED: continuing... starting USB... USB0: USB EHCI 1.00 USB1: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 ====================== no initrd for starters... Bob On 12/3/18 5:45 AM, Pablo Sebastián Greco wrote: > > Robert, I didn't want to send this to the list, but the image that > will appear on the mirrors are temporarily hosted here > https://armv7.dev.centos.org/repos/images/. > > You'll see that there is a generic-419, it is a test image I built > (never had time to test myself), that comes with kernel 4.19 instead > of 4.14, so it can be used with newer devices. > > Let me know how it goes..... :) > > Pablo. > > El 2/12/18 a las 22:59, Robert Moskowitz escribió: >> The power supply and serial connection came today, so now to build my >> first image. >> >> I see that we are still on the 1804 images, and seem to recall that >> there was work to do to get that working. >> >> Can someone give me the current recommended installation steps? >> >> I would prefer that all partitions are on the sata drive, only uboot >> on the uSD. >> >> thanks. >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev(a)centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev

2 27

xscreensaver missing from xfce group
by Robert Moskowitz 13 Dec '18

13 Dec '18

I am trying to add xscreensaver manually. I did a yum install xscreensaver and it also installed the following dependencies: 1:xscreensaver-gl-base-5.39-3.el7.armv7hl 1:xscreensaver-5.39-3.el7.armv7hl 1:xscreensaver-base-5.39-3.el7.armv7hl 1:xscreensaver-extras-5.39-3.el7.armv7hl 1:xscreensaver-gl-extras-5.39-3.el7.armv7hl And when I vnc to the system and wait, xscreensaver kicks in with the defaults. But the control app is not in applications > settings And I can't figure out what to install. greping for xscreensaver frm a yum list, I get: cinnamon-screensaver.armv7hl 3.6.1-2.el7 epel cinnamon-screensaver-unsupported.noarch 3.6.1-2.el7 epel gnome-screensaver.armv7hl 3.6.1-14.el7 epel kdeartwork-screensavers.armv7hl 4.10.5-4.el7 base mate-screensaver.armv7hl 1.16.1-1.el7 epel mate-screensaver-devel.armv7hl 1.16.1-1.el7 epel xscreensaver.armv7hl 1:5.39-3.el7 epel xscreensaver-base.armv7hl 1:5.39-3.el7 epel xscreensaver-extras.armv7hl 1:5.39-3.el7 epel xscreensaver-extras-gss.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-base.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-extras.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-extras-gss.armv7hl 1:5.39-3.el7 epel What of the above might be the control app? thanks

2 2

Re: [Arm-dev] File system corruption
by Gordan Bobic 13 Dec '18

13 Dec '18

> Are you using GPT partitions? GPT will lose the backup partition label > since it is at the back of the block device. Easy way to spot a "fake" > flash card as those just throw away everything past the end of the actual > data. > > A stress test will kill an under managed flash device VERY quickly, a > typical USB stick or SD card might only survive 4 passes of badblocks from > new due to poor management, garbage collection and large erase blocks. > > If you are suspecting actual genuine corruption, try ZFS (if you are > struggling, ask, I'll do my best to talk you through it). It yields better > performance and less wear on low end flash due to it's copy on write nature > and compression, and will confirm corruption beyond any doubt because it > checksums every block it writes. >

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev