Re: (java) Builds not reproducible on armhf

On 2024-05-20, Mechtilde Stehmann wrote: > I want to clean up my Java packages. > > There are several with FTBR. I found that the day of the *.poms s a date > from 1970. > > for example they are the packages > > vinnie Looking at the history for vinnie:

Re: Just tried arm64 netinstall on a bananai-m5

On 2023-08-15, gene heskett wrote: > used dd to write the arm64-bookworm-12.1 netinstall image to a 64G SDXC > ONN. brand card, makes no attempt to boot plugged into a bananapi-m5. > bring card back to reader, can't mount it, wrong filesystem for both > partitions. Give up, write

Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches

On 2023-06-21, Emanuele Rocca wrote: > On 2023-06-16 11:19, Emanuele Rocca wrote: > (1) I couldn't find any armel object with the hard-float flag set. > > (2) There are a few armhf packages shipping files with the soft-float flag. > > All of them, with the exception of the u-boot packages, are

Re: RFC: android-style boot image support for flash-kernel

On 2023-04-30, Roger Shimizu wrote: > I'm trying to support an ARM based RB3 / DB845c [1] dev-board with > android-style boot image to flash-kernel. ... > My question is: > - Currently flash-kernel is mainly u-boot based, is it proper to add > "mkbootimg" based devices? My main worry here is

Re: What happened to "u-boot" package for Debian testing distribution on Cubox-i

Interestingly, I have other arm-based boxes and none of them have this > problem. u-boot (2023.01~rc4+dfsg-2) unstable; urgency=medium ... * debian/control: Drop u-boot meta-package for armhf and mips. ... -- Vagrant Cascadian Thu, 05 Jan 2023 19:38:24 -0800 I had meant to deprecate it b

Re: Support for Orange Pi 4 LTS

On 2023-02-10, Diederik de Haas wrote: Nice summary! > On Friday, 10 February 2023 16:57:07 CET Andrew M.A. Cater wrote: >> On Fri, Feb 10, 2023 at 09:06:10AM +0100, Christian Marillat wrote: >> > Is Orange Pi 4 LTS (arm64) supported in Debian. ... >> OrangePi themselves have a version of Debian

Re: neon: armhf baseline for next release ?

On 2023-02-10, Mathieu Malaterre wrote: > On Thu, Feb 9, 2023 at 8:43 PM Andreas Tille wrote: > [...] >> according to the build logs[1] armhf fails to build (as only >> architecture) with > [...] >> LLVM ERROR: Symbol not found: __sync_fetch_and_add_4 > > I see that abel.d.o porterbox is offline.

Re: Can we get a signature for armhf SD-card images?

On 2023-01-31, Larry Doolittle wrote: > Friends - > > I looked and wasn't able to find a digital signature for > the SHA256SUMS file in > > http://ftp.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/ > or > >

Re: Bug#1029543: hw-detect: clarify use cases about searching for firmware packages on external media

On 2023-01-26, Cyril Brulebois wrote: > Vagrant Cascadian (2023-01-25): >> Though a larger image would take a bit longer and burn a few extra >> write cycles for those who did not need to actually use the space. > > I have no idea how much people care how much time is

Re: Bug#1029543: hw-detect: clarify use cases about searching for firmware packages on external media

On 2023-01-25, Cyril Brulebois wrote: > Cyril Brulebois (2023-01-24): ... > # SD card images (might also be applicable to the upcoming ChromeOS images) > > Looking at how those images are built, it seems we have a predefined, > per-arch image size (150M or 200M), and gen-hd-image that's called in

Re: debian installer on rock64

On 2023-01-13, Vagrant Cascadian wrote: > On 2023-01-13, Diego Roversi wrote: >> I got this error: >> >> [1.806958] List of all partitions: >> [1.807299] No filesystem could mount root, tried: >> [1.807304] >> [1.807892] Kernel panic - no

Re: debian installer on rock64

On 2023-01-13, Diego Roversi wrote: > today I've tested bookworm debian-installer from > https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ on a > rock64 but it didn't boot. Did you use the GTK images or the "regular" images? > > I got this error: > > [1.806958]

Re: Bug#1016963: Help with testing u-boot!

On 2022-12-28, Rick Thomas wrote: > A Cubox-i running Debian bullseye (11.6). According to versions> It has "u-boot-tools" (version 2021.01+dfsg-5) installed, > but none of the u-boot- packages installed. > > If I reboot it and watch the serial console, I see it showing "U-boot > 2021.01-dfsg-5"

Re: Help with testing u-boot!

On 2022-12-29, Diederik de Haas wrote: > On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote: >> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) >> and experimental (2023.01-rc*) >> >> # arm64 >> ... >> rock64-rk3328 >

Re: Help with testing u-boot!

On 2022-12-29, gene heskett wrote: > On 12/28/22 19:17, Diederik de Haas wrote: >> On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote: >>> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) >>> and experimental (2023.01-rc*) ... >

Help with testing u-boot!

On 2022-12-22, Vagrant Cascadian wrote: > On 2022-08-20, Vagrant Cascadian wrote: >> On 2022-08-10, Vagrant Cascadian wrote: >>> This bug is just to delay migration to testing while more platforms get >>> tested. If you have a relevent board, please consider testing a

On the existance of arm* porters

On 2022-08-25, Graham Inggs wrote: > On Wed, 16 Feb 2022 at 13:36, John Paul Adrian Glaubitz > wrote: >> it seems superficially plausible that the march=native >> invocations are just instances of the compiler being probed. > > I have also had a look and cannot see that '-march=native' is used

Re: failure trying to install bullseye on Cubox-i

On 2022-07-17, Rick Thomas wrote: > I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for > testing purposes. > > I followed the instructions at: > >

Re: armhf kernels on arm64 hardware

On 2022-07-15, woo...@wookware.org wrote: > The question from Debian's POV is how many other people want to use > non-native arm kernels (and for what?). How many platforms is it > relevant to? And if there is a downside, how many does that effect, > and how/how much. For Reproducible Builds

Re: cubox-i does not boot after upgrade to bullseye

On 2021-12-29, Uwe Kleine-König wrote: > On 12/28/21 13:46, Rainer Dorsch wrote: >> Am Dienstag, 28. Dezember 2021, 11:47:37 CET schrieb Uwe Kleine-König: >>> I can recommend barebox here instead of U-Boot. i.MX is the probably >>> best supported platform for it and I would expect the cubox-i to

Re: Solved: cubox-i does not boot after upgrade to bullseye

On 2021-12-29, Rainer Dorsch wrote: > Am Mittwoch, 29. Dezember 2021, 19:33:20 CET schrieb Vagrant Cascadian: >> If you've used "saveenv" to save the u-boot environment variables, even >> if you upgrade u-boot, the environment will remain frozen in the state >> w

Re: cubox-i does not boot after upgrade to bullseye

On 2021-12-29, Rainer Dorsch wrote: > Am Montag, 27. Dezember 2021, 18:22:43 CET schrieb Vagrant Cascadian: >> If you can insert the microSD into another Debian machine, you can get >> the UUID by looking in /dev/disk/by-uuid/ to find the matching device >> or: >>

Re: Solved: cubox-i does not boot after upgrade to bullseye

On 2021-12-29, Rainer Dorsch wrote: > The root cause of the new kernel not booting was that the memory addresses > for > kernel and initrd.img in the u-boot environment have probably changed during > this or a previous Debian release. > > A new installed bullseye system uses > >

Re: First W95 FAT32 (LBA) Partition in bullseye Installation of cubox-i

On 2021-12-28, Rainer Dorsch wrote: > just for curiosity, on a new bullseye installation of a cubox-i, there is a > W95 FAT32 (LBA) partition created as first partition. It contains a boot > setup: > > root@bc-text:~# mount /dev/mmcblk1p1 /mnt/ > root@bc-text:~# ls -l /mnt/ > total 27026 >

Re: cubox-i does not boot after upgrade to bullseye

On 2021-12-27, Rainer Dorsch wrote: > Am Montag, 27. Dezember 2021, 18:22:43 CET schrieb Vagrant Cascadian: >> Very likely; it is not promised to remain constant even between boots >> with the same kernel, unfortunately! >> >> You really want to use root=UUID=abcde-1

Re: cubox-i does not boot after upgrade to bullseye

On 2021-12-27, Rainer Dorsch wrote: > I upgraded a cubox-i from buster to bullseye. The upgrade went through > without > any issues. But after the upgrade the system does not boot anymore. The > output > of the serial console is below. The boot process hangs at > > [3.816424] Waiting for

Re: Porter roll call for Debian Bookworm

On 2021-10-02, Graham Inggs wrote: > * Which architectures are you committing to be an active porter for? armhf, arm64 > * Please describe recent relevant porter contributions. Maintaining u-boot (bootloader used on many arm64 and armhf plaforms), arm-trusted-firmware (arm64 firmware), and

systemd reproducibility on armhf

I finally did a reprotest build of systemd on armhf to try and figure out why it doesn't build reproducibly... but it built reproducibly... My test did not test building with a 64-bit kernel (it was using a 32-bit kernel in both cases), whereas the tests.reproducible-builds.org infrastructure

Re: Debian is supported on many arm platforms

On 2021-09-23, LinAdmin wrote: > On 10.09.21 21:40, Vagrant Cascadian wrote: >> On 2021-09-10, LinAdmin wrote: >>> The unnamed decision makers of Debian some unknown time ago >>> decided that Pi and *Pine* stuff won't be supported by Debian. >> This is the second

Debian (installer) on Pinebook Pro

On 2021-09-11, Oregano wrote: > September 11, 2021 11:30 AM, "Peter Ehlert" wrote: >> On 9/11/21 1:11 AM, Keith Bainbridge wrote: >>> Andrei -- happy Debian user of a PINE A64+ and (still) considering >>> the Pinebook Pro for my next laptop ... > Debian installer on an SD card ran OK, but wasn't

Debian Pinebook Pro

On 2021-09-11, Peter Ehlert wrote: > On 9/11/21 1:11 AM, Keith Bainbridge wrote: >> On Tue, 7 Sep 2021 10:01:49 +0300 >> Andrei POPESCU wrote: Andrei -- happy Debian user of a PINE A64+ and (still) considering the Pinebook Pro for my next laptop ... > superior build quality, I really

Debian is supported on many arm platforms

On 2021-09-10, LinAdmin wrote: > The unnamed decision makers of Debian some unknown time ago > decided that Pi and *Pine* stuff won't be supported by Debian. This is the second time you've stated this, without really adding meaningful content to the conversation, and people have presented

Re: Debian on Pine64 H64B?

On 2021-09-09, Pete Batard wrote: > Okay, maybe I didn't express myself properly here, because we're > basically on the same page. I am not saying that where possible, Debian > should not care about providing what you suggest. I'm only saying that, > *WHEN* that is not possible, as is the case

Debian on Raspberry Pi and Pine* and probably ARM support in general (was Re: Debian on Pine64 H64B?)

On 2021-09-04, LinAdmin wrote: > The unnamed decision makers of Debian some unknown time ago > decided that Pi and Pine stuff won't be supported by Debian. I personally have added support in Debian for: Raspberry Pi 1 Raspberry Pi 2b Raspberry Pi 3b+ Pine64+ Pinebook Pinebook Pro

Re: How to install Bullseye on Cubox-i4Pro on USB or eSATA disk?

On 2021-07-07, Rick Thomas wrote: > I recently tried installing the two-part image for MX6_Cubox-i from > [1] on my Cubox-i4Pro. I'm pretty sure while debugging #982270 (ethernet on imx6 systems), I managed to get a successfull install to eSATA, though not *positive* (maybe I just got as far as

Re: on OpenRD "client" ( arch = armv5tel ) Upgraded from Buster to Bullseye and haveged stoped working.

On 2021-03-14, Rick Thomas wrote: > I recently updated my OpenRD "client" ( arch = armv5tel ) from Buster to > Bullseye and now haveged crashes. > > $ sudo service haveged status > * haveged.service - Entropy Daemon based on the HAVEGE algorithm > Loaded: loaded

Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

On 2021-02-06, Rick Thomas wrote: > On Fri, Jan 29, 2021, at 7:18 PM, Rick Thomas wrote: >> Hi! >> >> On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote: >> > On https://www.debian.org/devel/debian-installer/ >> > you should look under the daily snapshots. >> > For armhf that would be >> >

Re: Rock Pi 4 A boot loader?

On 2021-02-02, Michael Fladischer wrote: > I inherited a Rock Pi 4A v1.4 from a co-worker who ran Armbian on it. > There are two storage devices present: One eMMC 16GiB module an one M.2 > NVME 128GiB module, which I haven't used yet. > > I wrote the combined image from [0] to the eMMC and

Re: Installing Debian Bullseye on Cubox-i4 with eSATA drive... No ethernet detected

On 2021-01-29, Rick Thomas wrote: > Hi! > > On Fri, Jan 29, 2021, at 1:03 AM, Holger Wansing wrote: >> On https://www.debian.org/devel/debian-installer/ >> you should look under the daily snapshots. >> For armhf that would be >>

Re: Installing Debian Buster on Cubox-i4 with eSATA drive.

On 2021-01-27, Rick Thomas wrote: > I'm trying to install Debian Buster [1] on my Cubox-i4P with an eSATA > drive. Everything seems to be fine, but when it comes time to reboot, > it boots into the installer again, rather than the installed system. > > Here's what I did, and what I observed: > >

Re: Installation images for arm64

On 2021-01-06, Reco wrote: > On Tue, Oct 27, 2020 at 10:20:28PM +0300, Reco wrote: >> On Tue, Oct 27, 2020 at 10:21:01AM -0700, Vagrant Cascadian wrote: >> > Please file bugs and/or merge requests on u-boot and >> > arm-trusted-firmware if you want to get those parts

Re: Porter roll call for Debian Bullseye

On 2020-11-20, Graham Inggs wrote: > A friendly reminder about the porter roll call for bullseye. > > On Mon, 2 Nov 2020 at 22:23, Graham Inggs wrote: >> We are doing a roll call for porters of all release architectures. If >> you are an active porter behind one of the release architectures [1]

pinebook wifi (rtl8273cs) (Was: Debian installer auf Pinebook)

On 2020-11-01, Vagrant Cascadian wrote: > On 2020-10-31, Christian Kastner wrote: >> Apparently the WIFI is a RTL8723cs device and support landed in 5.9, >> coincidentally the kernel in bullseye ... > I don't see anything regarding RTL8723cs support specifically in 5.9 .

Re: Debian installer auf Pinebook (Was: X11 modul for pinebook?)

On 2020-10-31, Christian Kastner wrote: > Apparently the WIFI is a RTL8723cs device and support landed in 5.9, > coincidentally the kernel in bullseye, so I gave its SD card images a > try. However, they launch to a black screen, so I assume that this still > goes out to serial? I don't see

Re: Debian installer auf Pinebook (Was: X11 modul for pinebook?)

On 2020-10-31, Vagrant Cascadian wrote: > On 2020-10-31, Vagrant Cascadian wrote: >> And just tested on a pinebook: >> >> >> https://d-i.debian.org/daily-images/arm64/20201031-02:16/netboot/gtk/SD-card-images/ >> >> zcat firmware.pinebook.img.gz pa

Re: Debian installer auf Pinebook (Was: X11 modul for pinebook?)

On 2020-10-31, Vagrant Cascadian wrote: > I tried to add the new modules to the kernel .udebs a while back: > > > https://salsa.debian.org/kernel-team/linux/commit/e6e296b335a7081a1a88c41dae4539f3115da44e > > And just tested on a pinebook: > > > https://d-i.de

Re: Debian installer auf Pinebook (Was: X11 modul for pinebook?)

On 2020-10-31, Christian Kastner wrote: > On 4/22/20 7:15 PM, Vagrant Cascadian wrote: >> The debian-installer concatenateable images from buster *should* work >> with *serial console*: >> >> >> https://deb.debian.org/debian/dists/buster/main/installer-arm

Re: Installation images for arm64

On 2020-10-27, Reco wrote: > On Tue, Oct 27, 2020 at 08:59:38AM -0700, Vagrant Cascadian wrote: >> On 2020-10-27, Reco wrote: >> > On Tue, Oct 27, 2020 at 08:02:18AM -0700, Vagrant Cascadian wrote: >> >> It looks like u-boot 2020.10 has an odroid-n2 target and >

Re: Installation images for arm64

On 2020-10-27, Reco wrote: > On Tue, Oct 27, 2020 at 08:02:18AM -0700, Vagrant Cascadian wrote: >> It looks like u-boot 2020.10 has an odroid-n2 target and >> arm-trusted-firmware 2.3 has an amlogic/g12a target, so it would likely >> be possible to enable those in the Debia

Installation images for arm64 (was Re: Bullseye installer, daily image broken for cubox-i)

on most arm boards. The CuBox-i series make that easy as there is a microUSB port that exposes a serial interface built-in. live well, vagrant > On 10/26/20, Vagrant Cascadian wrote: >> On 2020-10-26, Rainer Dorsch wrote: >>> I wanted to do a test on the mainline sup

Re: Bullseye installer, daily image broken for cubox-i

On 2020-10-26, Rainer Dorsch wrote: > I wanted to do a test on the mainline support of bullseye for the Cubox-i. > > I downloaded the bullseye installer from > > https://d-i.debian.org/daily-images/armhf/daily/hd-media/SD-card-images/ > > put it on an SD card ... > But all I saw was a quick u-boot

Re: u-boot vs installer images

On 2020-10-12, Rainer Dorsch wrote: > I just browsed through the bullseye installation guide. I saw there is a > section on > > 3.6.2. Debian-provided U-Boot (system firmware) images > https://www.debian.org/releases/testing/armhf/ch03s06.en.html > > and > > 5.1.5. Using pre-built SD-card images

Re: Debian with Debian kernel on Pinebook Pro

On 2020-08-29, Birger Schacht wrote: > I am trying to get a Debian (bullseye) installation to work on the > Pinebook Pro with the Debian kernel package. I managed to install Debian > back in February, but back then this was with a custom kernel with a lot > of patches [0]. As far as I know most if

Re: Re: NextThing C.H.I.P. v1.0 - Debian Stretch Installer from USB

On 2020-05-26, Pablo Rath wrote: > On Tue, May 26, 2020 at 09:31:33AM +0200, Xavier Bestel wrote: >> Le jeudi 21 mai 2020 à 12:25 +0200, Pablo Rath a écrit : >> > On Mon, May 18, 2020 at 03:57:52PM +0200, Xavier Bestel wrote: >> > Is there a reason to prefer Stretch over Buster? >> >> I didn't

Re: Debian installer auf Pinebook (Was: X11 modul for pinebook?)

On 2020-04-22, Andreas Tille wrote: > On Wed, 22 Apr 2020 Andrei POPESCU wrote: >> See if maybe these pages in the wiki are helpful >> >> https://wiki.debian.org/InstallingDebianOn/PINE64/Pinebook >> https://wiki.debian.org/InstallingDebianOn/PINE64/PINEA64 > > Thank you for these links. > >> See

Re: X11 modul for pinebook?

On 2020-04-20, Andreas Tille wrote: > I have a pinebook of the first generation installed with Stretch. I > naively assumed that it would the right time to upgrade to Buster. > Unfortunately X does not start any more: > > # grep EE /var/log/Xorg.[01].log > /var/log/Xorg.0.log:[12.349] Current

Re: Raspberry Pi

On 2020-03-02, Alan Corey wrote: > That poses an interesting question: can you install Debian debs on a > Raspbian system and vice versa? Never thought about it. I've maybe > used Ubuntu ones a couple times. I suppose each case is unique and > the worst casualty would be to the apt system and

Re: Bug#911560: [Kinda solved] Re: Network not working on Olimex LIME2 rev K ??

On 2020-02-09, Dominique Dumont wrote: > On Saturday, 8 February 2020 16:54:45 CET Jonas Smedegaard wrote: >> Would be great if you could also test with patched u-boot in stable >> Debian - so we can consider fixing this in a point release. > > I've tested together: > - Debian's u-boot

Re: Network not working on Olimex LIME2 rev K ??

On 2020-02-05, Dominique Dumont wrote: > I'm trying to setup a new Olimex LIME2 rev K board with Debian stable > installer. > > The installation starts through serial console, but DHCP configuration does > not > work. > > In u-boot, ping command does not work: > => ping 192.168.0.254 > Speed:

Re: Armbian

On 2020-02-03, Paul Wise wrote: > On Sun, Feb 2, 2020 at 5:51 PM Phil Endecott wrote: > >> What do you know about Armbian? What do you think? > > Only what I see on their site and derivatives census page: > > https://www.armbian.com/ > https://wiki.debian.org/Derivatives/Census/Armbian > > I

Re: Support for accelerated graphics and video decoding on PINE A64+ in bullseye

Control: tags 946510 pending On 2019-12-14, Andrei POPESCU wrote: > On Vi, 06 dec 19, 19:57:07, Andrei POPESCU wrote: >> On Vi, 06 dec 19, 15:05:32, Marcin Juszkiewicz wrote: >> > Use Lima (Pine A64) or Panfrost (Rock64)? >> >> Sure... how? >> >> I changed my xorg.conf as per [1], but not

Re: libxp-dev and libxp6 for aarch64 and forward?

On 2019-08-17, Alan Corey wrote: > They seem to be missing from Stretch but they're in Buster. Maybe, by > pkgs.org, and they only have the i386 and amd64 versions. They don't > show up using this sources.list The last release that contained libxp was jessie (oldoldstable):

Re: Add support for Pine64 RockPro64

On 2019-07-29, Rohan Garg wrote: > There is u-boot support specifically for rockpro64-rk3399 upstream >> now. I'd be happy to enable it in the u-boot packaging if you or someone >> else can promise to test it periodically: >> >> https://wiki.debian.org/U-boot/ >>

Re: Add support for Pine64 RockPro64

On 2019-07-27, Michael Gratton wrote: > Package: u-boot Did you mean for this to go to the bug tracking system? > I've just picked up a RockPro64 board[0] based on the Rockchip RK3399 > and it would be great to be able to install standard Debian on it (as > opposed dd'ing some random image).

Re: making debs for u-boot kernels

On 2019-07-27, Reco wrote: > On Thu, Jul 25, 2019 at 12:49:32PM -0400, Gene Heskett wrote: >> I am furious (fat lot of good that does me) with the lack of tools, and >> information on how to use them to build an installable kernel.deb for a >> rpi-3b. I know it can be done, I have witnessed apt

Staying on topic for the list (was Re: loss of synaptic due to wayland)

Several people have asked in the past including myself, and at least one other person has asked on this and maybe other recent threads... Could you please keep on topic for debian-arm? Simply running debian on an arm system doesn't really give free license to talk about anything and everything

Re: Debian Installer on Pine64+ (no serial console)

On 2019-05-05, Andrei POPESCU wrote: > On Sb, 04 mai 19, 12:29:30, Vagrant Cascadian wrote: >> >> The really important A64 timer issue fix finally went in 4.19.28-1, >> without which the clock would occasionally leap 90+ extra years into the >> future and find your

Re: Debian Installer on Pine64+ (no serial console)

On 2019-05-04, Andrei POPESCU wrote: > On Sb, 04 mai 19, 06:57:43, Andrei POPESCU wrote: >> >> I'm ready to start a second try where I will be using manual >> partitioning (without GPT), hoping I will get a bootable system. > > This worked, see >

Re: Fixing stretch debian-installer on armhf

On 2019-03-09, Adam D. Barratt wrote: > On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote: >> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote: >> [...] >> > > * Rebuild the debian-installer images, pulling in updates from >> > >   stretch-updates, leaving only armhf netboot targets

Re: Installation media for arm64

On 2019-03-23, Christian Kastner wrote: > I recently purchased a A64-OLinuXino and I believe it should be > supported by the tooling in buster. ... > For armhf, SD card images are provided [3], this seems incredibly > useful. I couldn't find any for arm64, nor could I find a hd-media > tarball.

Re: Fixing stretch debian-installer on armhf

On 2019-03-07, Ben Hutchings wrote: > On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote: > [...] >> > * Rebuild the debian-installer images, pulling in updates from >> > stretch-updates, leaving only armhf netboot targets broken. >> >> Expanding a bit: rebuilding src:debian-installer

Re: How do I find out where u-boot environment is stored?

On 2019-03-06, Rick Thomas wrote: > Anybody know how can I determine where u-boot is storing it’s environment? > Is there an environment variable where that info is stored? > (-: Any ironic self-reference in the previous question is entirely > un-intentional… ;-) At least for recent u-boot

Fixing stretch debian-installer on armhf

Due to #922478, the debian-installer images for stretch are currently not bootable on the armhf architecture. While the linux kernel packages have been fixed in stretch-updates and stretch-proposed-updates, the debian-installer images still were built with the broken kernel. Even rebuilding the

Re: Does ARMEL toolchain include NEON support?

On 2019-02-27, Jeffrey Walton wrote: > I'm investigating a failed build for ARMEL. I don't have access to the > build machine so I have to study the logs or ask our package > maintainer to run commands for us. > > The build log is at >

Re: fw_printenv says "Warning: Bad CRC, using default environment"

On 2019-02-26, Rick Thomas wrote: >> On Feb 26, 2019, at 10:49 AM, Vagrant Cascadian wrote: >> >> On 2019-02-26, Rick Thomas wrote: >>> On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools >>> package) it says “Warning: Bad CRC, using default enviro

Re: arch-test and armel on arm64

On 2019-02-26, Adam Borowski wrote: > Hi! > Could you guys please educate me what's the matter with SWP on armel these > days? It seems that almost no programs use it anymore. Should I remove the > check for SWP from arch-test, so it reports a machine+kernel as capable of > running armel even if

Dreamplug fails to detect SPI and USB

On 2019-02-26, Leigh Brown wrote: > I tested u-boot 2019.01+dfsg-1 on my Globalscale Dreamplug and it > doesn't work: > > U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +) > Marvell-DreamPlug > > SoC: Kirkwood 88F6281_A1 > DRAM: 512 MiB > Loading Environment from SPI Flash... Invalid bus 0

Re: fw_printenv says "Warning: Bad CRC, using default environment"

On 2019-02-26, Rick Thomas wrote: > On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools > package) it says “Warning: Bad CRC, using default environment”. If when booting, it also gives you this message, that would suggest you have no saved environment for fw_printenv to read from, as

Testing u-boot targets for buster!

Hello fine u-boot testers. You were one of the gracious people who offered to test one or more u-boot targets from the debian packages. Thanks! https://salsa.debian.org/debian/u-boot/blob/master/debian/targets Since we're in the process of freezing Buster, at the very least I would like to get

Re: Bug#922729: debootstrap: unable to override arch-test

On 2019-02-20, John Paul Adrian Glaubitz wrote: > On 2/19/19 11:56 PM, Vagrant Cascadian wrote: >> I tried installing an armel chroot on an arm64 machine: >> >> $ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr >> --verbose sid /srv/chroots/arme

Re: After update to latest Stretch--boot stops

On 2019-02-19, Nate Bargmann wrote: > * On 2019 19 Feb 15:11 -0600, Vagrant Cascadian wrote: >> On 2019-02-19, Nate Bargmann wrote: >> > I've been running Stretch on my Olimes A20-Olinuxino Micro for several >> > months without issue until just a while ago. I perfo

Re: After update to latest Stretch--boot stops

On 2019-02-19, Nate Bargmann wrote: > I've been running Stretch on my Olimes A20-Olinuxino Micro for several > months without issue until just a while ago. I performed an update > through Aptitude whereupon the latest version of systemd and kernel were > updated. After a proper shutdown and

linux-image-4.9.0-8-armmp-lpae:armhf 4.9.144-3 renders many systems unbootable

I strongly advise to hold off on updating your kernels on stretch armhf systems until this issue is resolved: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders many systems unbootable https://bugs.debian.org/922478 I haven't yet seen an armhf system that can

support for OpenRD and Sheevaplug (was Re: Debian Installer Buster Alpha 4 release)

On 2018-12-17, Rick Thomas wrote: >> On Dec 15, 2018, at 2:26 PM, Cyril Brulebois wrote: >> >> Hardware support changes >> >> >> * debian-installer: >> - [armel] Disable OpenRD targets, no longer present in u-boot. > > Does this mean that my OpenRD hardware will no

Re: Debian buster on Pine64+ (2 GiB RAM)

On 2018-12-09, Andrei POPESCU wrote: > On Du, 09 dec 18, 10:23:02, Christian Marillat wrote: >> >> I don't see issues with the experimental kernel 4.19.5-1~exp1 : > > Could the issue be with u-boot then, possibly not initializing the > hardware correctly? > > I'm using the u-boot-sunxi

Re: Debian buster on Pine64+ (2 GiB RAM)

On 2018-12-08, Andrei POPESCU wrote: > I'm trying to run buster on a Pine64+ (2 GiB RAM). So far I created the > rootfs with debootstrap, installed linux-image-arm64 and ran > u-boot-install-sunxi64 on the SD card. > > The systems boots only to the u-boot prompt, so I'm missing something to >

#9065700: firefox-esr segfaults during startup on arm64

Control: found 906570 60.3.0esr-1 Control: found 906570 60.3.0esr-2 I've been having this same issue on a Pinebook. The versions in stretch are also problematic; I tried those first before the newer versions landed in buster, but I haven't confirmed which versions for sure. On the positive

Regression in linux 4.9.x security update

There's been a regression in linux 4.9.110-3+deb9u3 in stable security updates causing problems booting various arm64 and arm systems. I'd recommend avoiding upgrading your kernel until the issue is sorted out, unless you love debugging these sorts of things. For the details, please see:

Re: u-boot-mvebu for ESPRESSObin

On 2018-08-12, Jan Kiszka wrote: > am I right that the u-boot.bin from the buster package u-boot-mvebu is > not for direct consumption by the ESPRESSObin? You are right. > All documents I found say that it has to be embedded into an ATF > module, forming the final SPI flash content. Yes.

Re: Bootstrapping an Olimex A64-OLinuXino

On 2018-03-13, Martin Lucina wrote: > I'm trying to bootstrap an Olimex A64-OLinuXino board from scratch, using > Debian stretch on x86_64 as the build host. So far, I've: > > - cross-built mainline U-boot 2018.01 including the SPL and BL31 from latest >

Re: Using a custom device tree file

On 2018-02-19, Rainer Dorsch wrote: > Am Samstag, 17. Februar 2018, 16:22:06 CET schrieb Vagrant Cascadian: >> > Can anybody tell, if it is possible to configure from u-boot shell to >> > loada >> > custom device treefile? >> >> To manually change

Re: Using a custom device tree file

On 2018-02-18, Gene Heskett wrote: > On Saturday 17 February 2018 19:22:06 Vagrant Cascadian wrote: >> On 2018-02-17, Rainer Dorsch wrote: >> > Am Sonntag, 11. Februar 2018, 22:24:51 CET schrieb Rainer Dorsch: >> >> Am Sonntag, 11. Februar 2018, 13:20:07

Re: Using a custom device tree file

On 2018-02-17, Rainer Dorsch wrote: > Am Sonntag, 11. Februar 2018, 22:24:51 CET schrieb Rainer Dorsch: >> Am Sonntag, 11. Februar 2018, 13:20:07 CET schrieb Vagrant Cascadian: >> > On 2018-02-11, Rainer Dorsch wrote: >> > Try adding the following to /etc/flas

Re: Using a custom device tree file

On 2018-02-11, Rainer Dorsch wrote: > I try to use a custom device tree file, but uEnv.txt does not have any effect: > > rd@mohot:~$ cat /boot/uEnv.txt > fdtfile=imx6dl-hummingboard-spi.dtb ... > Do I need to run flash-kernel or something else that uEnv.txt has any effect? I don't believe the

Re: Utilite Pro - U-Boot

On 2018-02-11, Scott wrote: > On 2/1/2018 1:13 AM, Vagrant Cascadian wrote: > Curious if I am overlooking a U-Boot option/parameter/command for > loading initrd. > > From the vendor-provided U-Boot prompt, I could not load initrd.gz into > memory without first wrapping wi

Re: Utilite Pro

On 2018-01-31, Scott wrote: > but would like to user installer via SD-card-image > > http://ftp.nl.debian.org/debian/dists/stretch/main/installer-armhf/current/images/hd-media/SD-card-images/ ... > Are the Stretch u-boot images based off v2017.05 >

Re: flash-kernel and dtbs

On 2017-11-30, Rainer Dorsch wrote: > many thanks for you excellent suggestions, they helped me a lot. Glad it worked! > Am Dienstag, 28. November 2017, 13:12:42 schrieb Vagrant Cascadian: > [...] >> >> When the user installs them. Install u-boot-imx and see >>

Re: flash-kernel and dtbs

On 2017-11-28, Rainer Dorsch wrote: > Am Sonntag, 26. November 2017, 16:25:59 schrieb Vagrant Cascadian: >> On 2017-11-26, Rainer Dorsch wrote: >> > On Sonntag, 26. November 2017 11:30:04 CET Vagrant Cascadian wrote: >> >> On 2017-11-26, Rainer Dorsch wrote: &

Re: flash-kernel and dtbs

On 2017-11-26, Rainer Dorsch wrote: > On Sonntag, 26. November 2017 11:30:04 CET Vagrant Cascadian wrote: >> On 2017-11-26, Rainer Dorsch wrote: >> > I try to setup the correct dtb for a HummingBoard DualLite using >> > flash-kernel, >> > but the kernel

Re: flash-kernel and dtbs

On 2017-11-26, Rainer Dorsch wrote: > I try to setup the correct dtb for a HummingBoard DualLite using > flash-kernel, > but the kernel seems to load always the Cubox-i dtb: What u-boot do you have installed? Can you get to the u-boot console (probably serial console), and run the following

  1   2   3   >