How can I tell Debian on a Raspberry Pi 4B (4GB) which kernel image to load at boot time?

I have a set of three Raspberry-Pi 4B (4GB) machines. They all are running the Debian for Rpi from [1]. They all were happily running the kernel from package "linux-image-6.1.0-9-arm64". But, recently, a passing "apt upgrade" installed "linux-image-6.1.0-10-arm64" on them. On all three of

[SOLVED} Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

Turns out that the PiHut has a tutorial webpage for just this problem! https://thepihut.com/blogs/raspberry-pi-tutorials/17209332-adding-a-real-time-clock-to-your-raspberry-pi Thanks for all the help! Rick On Tue, Apr 18, 2023, at 11:06 PM, Rick Thomas wrote: > Thanks very much, Pabs!

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

PM, Paul Wise wrote: > On Mon, 2023-04-17 at 22:21 -0700, Rick Thomas wrote: > >> What would have been even greater is if the error messages include >> references to some documentation that explained the problem and gave >> some clues to the larger context in which the problem

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

On Mon, Apr 17, 2023, at 7:55 PM, Paul Wise wrote: > On Mon, 2023-04-17 at 13:39 +0300, Reco wrote: >> On Mon, Apr 17, 2023 at 02:48:44AM -0700, Rick Thomas wrote: >> > Sadly,   when I do: >> >     i2cdetect -l >> > I get nothing back.  Leading me

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

e: > Hi. > > On Mon, Apr 17, 2023 at 02:48:44AM -0700, Rick Thomas wrote: >> Sadly, when I do: >> i2cdetect -l >> I get nothing back. Leading me to conclude that there are no busses >> available. > > "modprobe i2c-dev" should fix that. > > Reco

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

3, at 1:10 AM, Reco wrote: > Hi. > > On Sun, Apr 16, 2023 at 06:41:53PM -0700, Rick Thomas wrote: >> I found this in journalctl : >> Apr 16 18:23:33 pi kernel: rtc-ds1307: probe of 1-0068 failed with error >> -121 >> Apr 16 18:23:33 pi kernel: i2c i2c-1:

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

eb Diederik de Haas : > >> On Sunday, 16 April 2023 04:47:37 CEST Rick Thomas wrote: >> > I've got a Raspberry Pi 4B (4GB) with a DS3231 RTC module. I can >> > make the combo work with Ubuntu and RaspberryPI-OS. I'd like to >> > try it with the plain-v

Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

I've got a Raspberry Pi 4B (4GB) with a DS3231 RTC module. I can make the combo work with Ubuntu and RaspberryPI-OS. I'd like to try it with the plain-vanilla Debian from but I can't find instructions for activating the I2C and RTC hardware in that

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

Please... Anyone with experience here, please speak up. I don't want to do anything stupid, but I *do* need to get this issue straightened out. Thanks in advance for any help! Rick On Thu, Feb 23, 2023, at 10:36 PM, Rick Thomas wrote: > On Thu, Feb 23, 2023, at 8:02 PM, Vagrant Cascadian wr

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

On Thu, Feb 23, 2023, at 8:02 PM, Vagrant Cascadian wrote: > On 2023-02-23, Rick Thomas wrote: >> I just noticed that there are no versions of the package "u-boot" available >> on my SolidRun CuBox-i. >> However there is a version of "u-boot-imx" avail

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

I just noticed that there are no versions of the package "u-boot" available on my SolidRun CuBox-i. However there is a version of "u-boot-imx" available which contains the actual binary code for this machine. Interestingly, I have other arm-based boxes and none of them have this problem. See

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

Here's another Cubox-i. This one's running Bookworm. shows a surprising number of u-boot- packages installed, ( = exynos, imx, omap, sunxi) as well as plain "u-boot". All of them are version 2022.04+dfsg-2+b1. Rebooting while watching the serial console output says "U-Boot SPL

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

A Cubox-i running Debian bullseye (11.6). According to 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" so that version must have gotten into the

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

Raspberry Pi 4B (8GB) running bullseye, but does not seem to have any version of u-boot installed. Weird? Running tells me that the following (among lots of others) versions are available. Should I install one of them and see what happens? Package u-boot-rpi: p 2021.01+dfsg-5 stable 500

Re: Any suggestions for a Debian(based/like) OS for the Orange Pi zero2

Thanks, Andy! I'll try the ftp.debian.org link tonight. It looks like exactly what I'm looking for. Rick On Mon, Oct 10, 2022, at 3:32 AM, Andrew M.A. Cater wrote: > On Sun, Oct 09, 2022 at 07:17:44PM -0700, Rick Thomas wrote: >> He Debian Arm folks, >> >> Out of

Re: Any suggestions for a Debian(based/like) OS for the Orange Pi zero2

On Mon, Oct 10, 2022, at 3:31 AM, RobJE wrote: > Hi Rick, > > On 10-10-2022 04:17, Rick Thomas wrote: >> He Debian Arm folks, >> >> Out of curiosity, I recently bought a couple of Orange Pi zero2 kits because >> I wanted to see what could be done with such a rea

Any suggestions for a Debian(based/like) OS for the Orange Pi zero2

He Debian Arm folks, Out of curiosity, I recently bought a couple of Orange Pi zero2 kits because I wanted to see what could be done with such a really inexpensive board. Now I'm looking for an OS. The Orange Pi web site claims that it supports Debian and Ubuntu among others, but I can't find

Re: failure trying to install bullseye on Cubox-i

Well, I re-downloaded and re-copied the resulting complete image to a micro-SD card by a different manufacturer, and lo and behold, it all works this time! Sigh! Sorry for all the noise, Rick On Sun, Jul 17, 2022, at 6:47 PM, Rick Thomas wrote: > On Sun, Jul 17, 2022, at 6:37 PM, Rick Tho

Re: failure trying to install bullseye on Cubox-i

On Sun, Jul 17, 2022, at 6:37 PM, Rick Thomas wrote: > I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep > around for testing purposes. > > I followed the instructions at: > > > http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/c

failure trying to install bullseye on Cubox-i

I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for testing purposes. I followed the instructions at: http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images Then I dd'ed the

Re: SheevaPlug -- first phase results successful.

Hi Martin, On Wed, Jun 8, 2022, at 10:17 PM, Martin Michlmayr wrote: >> Indeed, I do have two OpenRD machines running right now, an >> "Ulitmate" and a "Client". Both are available for testing. Let me >> know what you would like me to do and I'll get to it ASAP. I also >> have a SheevaPlug

Re: Debian 11 on Sheevaplug?

l image! >> Marvell>> >> = >> >> That was with the original settings: >> setenv bootargs_console console=ttyS0,115200 >> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x0080 /uImage; >> ext2load usb 0:1 0x0110 /uInitrd' >> sete

Re: Debian 11 on Sheevaplug?

On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote: > It ends with a single error : "partman: mkswap: can't open '/dev/sda5': > No such file or directory": > > https://pastebin.com/raw/h0beZWnP It looks like /dev/sd5 doesn't actually exist. This is probably because the USB stick has an MBR

Re: Debian 11 on Sheevaplug?

On Thu, Jun 2, 2022, at 5:15 AM, Gilles wrote: > Hello, > > A search in the archives returned no hits. > > Martin Michlmayr's page* shows how to install Debian 10 on a USB > keydrive to run on a Sheevaplug. > > Does it mean Debian 11 still isn't available for that device? > > Thank you. > > *

Re: Debian armhf test system?

On Sat, Sep 25, 2021, at 6:59 AM, Jeffrey Walton wrote: > Hi Everyone, > > We are trying to track down the cause of a build failure on Debian; > see [1]. I want to setup a Debian armhf system for testing. (I have > about 6 testing boards, but they are other OSes). > > I found the relevant area

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

I recently tried installing the two-part image for MX6_Cubox-i from [1] on my Cubox-i4Pro. It worked fine when I installed to an SD card -- I used a 32 GB card for the installer and installed to that same card. But that's kinda limited. The box has USB and eSATA ports that I'd like to be

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

On Sat, Mar 27, 2021, at 1:07 PM, Vagrant Cascadian wrote: > 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 > &g

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

Bug#985196 On Sun, Mar 14, 2021, at 12:41 AM, 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 HAVEG

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

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 (/lib/systemd/system/haveged.service; enabled; vendor preset: enabled)

Re: RPi customization utility [Re: More progress to report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]]

> maintained, unlike some ancient documentation that should be banished but is > still out there. > > > On Sun, Feb 28, 2021, 6:17 AM Andrew M.A. Cater wrote: >> On Sun, Feb 28, 2021 at 02:16:29AM -0800, Rick Thomas wrote: >> > >> > On Thu, Feb 25, 2021,

RPi customization utility [Re: More progress to report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]]

ic-ized version of that. Armbian probably does too. Raspi-config > is just a Bash script that uses Whiptail for its menus. Parts of it are > useful on other things. It's on Github somewhere. > > > On Thu, Feb 25, 2021, 11:09 PM Rick Thomas wrote: >> Thanks! Alan... So, here'

More progress to report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]

I installed the most recent Bullseye image [1] on my Pi4B (4GB) a few days ago. It's happily running on the table next to me right now. Here's what I found: It loads and boots just as expected. Apt and tasksel work and I was able to install all the utilities I need to make it useful on my

Re: Progress report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]

On Mon, Feb 22, 2021, at 2:45 AM, Leigh Brown wrote: > Hi Rick, ... > Take a look at the following. No soldering required, and they fit in the > case nicely (for Pi4 at least). > > Adafruit PiRTC - PCF8523 Real Time Clock for Raspberry Pi > (https://www.adafruit.com/product/3386) > >

Re: Debian Bullseye on Raspberry Pi 4 4GB?

On Tue, Feb 23, 2021, at 11:45 AM, Gunnar Wolf wrote: > LinAdmin dijo [Sat, Feb 20, 2021 at 07:30:35PM +0100]: > > I am not convinced that all images listed on [1] do work as > > advertized. > > (...) > > > [1] https://raspi.debian.net/tested-images/ > > > Right. I'm only one person

Re: Progress report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]

On Sun, Feb 21, 2021, at 11:49 AM, Reco wrote: > On Sun, Feb 21, 2021 at 02:36:52PM -0500, Alan Corey wrote: > > That's why when you get a real time you adjust the times on your logged > > events. There's the time you got the time fix, everything else is N > > microseconds before that back to

Re: Progress report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]

On Sat, Feb 20, 2021, at 11:14 PM, Reco wrote: > Hi. > > On Sat, Feb 20, 2021 at 10:53:18PM -0800, Rick Thomas wrote: > > root@pi:~# ls -l /dev/rtc* > > ls: cannot access '/dev/rtc*': No such file or directory > > > > What package should I file a bu

Progress report [Re: Debian Bullseye on Raspberry Pi 4 4GB?]

I downloaded the pre-installed SD card image from https://raspi.debian.net/tested-images/ I used the "2021.02.10 10 (Buster) 4" image. I Here's what I did: Downloaded the img.xz file and the sha256 file, and used the sha file to check the integrity of the img file. Uncompressed the

Re: Debian Bullseye on Raspberry Pi 4 4GB?

Thanks, yes that does help a lot. I'm always amazed by the helpfulness and depth of knowledge shown by the folks on the Debian lists! Rick On Sat, Feb 20, 2021, at 11:22 AM, Diederik de Haas wrote: > On zaterdag 20 februari 2021 13:46:00 CET Rick Thomas wrote: > > Hmmm... The "

OT: SBBR Broadcom etc [New Subject]

Please continue this discussion under a different Subject. It has nothing to do with my original question. Thanks! Rick On Sat, Feb 20, 2021, at 4:18 AM, Pete Batard wrote: > Hi Luke, > > On 2021.02.20 04:16, Luke Kenneth Casson Leighton wrote: > > > > > > On Friday, February 19, 2021, Pete

Re: Debian Bullseye on Raspberry Pi 4 4GB?

bell wrote: > On Fri, 2021-02-19 at 18:42 -0800, Rick Thomas wrote: > > If I can get the Pi4 working with either of the Debian alternatives, > > I will probably buy a Pi zero W as the actual replacement for the > > Sheeva, and keep the Pi4 for experimentation. > > I'm sure

Re: Debian Bullseye on Raspberry Pi 4 4GB?

If I can get the Pi4 working with either of the Debian alternatives, I will probably buy a Pi zero W as the actual replacement for the Sheeva, and keep the Pi4 for experimentation. Enjoy! Rick

Re: Debian Bullseye on Raspberry Pi 4 4GB?

On Thu, Feb 18, 2021, at 3:02 PM, Rick Thomas wrote: > Is it possible to install Debian Bullseye on a Raspberry Pi 4 (4GB) > from a CD/DVD or USB Flash stick or uSDcard? > > If so, where would I look for instructions for doing so? A couple of folks have asked for clarification

Debian Bullseye on Raspberry Pi 4 4GB?

Is it possible to install Debian Bullseye on a Raspberry Pi 4 (4GB) from a CD/DVD or USB Flash stick or uSDcard? If so, where would I look for instructions for doing so? ADVthANanksCE! Rick

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

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 > > https://

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

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 > https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ I downloaded the two-part image from

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

On Thu, Jan 28, 2021, at 12:08 AM, Rick Thomas wrote: > On Wed, Jan 27, 2021, at 11:15 PM, Vagrant Cascadian wrote: > > 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 f

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

On Wed, Jan 27, 2021, at 11:15 PM, Vagrant Cascadian wrote: > 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 install

Installing Debian Buster on Cubox-i4 with eSATA drive.

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: *) I downloaded the two parts of the SDcard

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

> On Sep 30, 2019, at 12:41 AM, Alexandre Belloni > wrote: > > My opinion is that distributions should stop relying on HCTOSYS and do > the RTC read from userspace. This is especially important because > distros are hardcoding rtc0 as the RTC to read from which is most likely > to not be the

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

Thanks for the explanation! > On Sep 30, 2019, at 12:22 AM, Uwe Kleine-König wrote: > > IIRC systemd-timesyncd fast forwards the time at boot time to be not > earlier than before the last shutdown. Maybe this is not active for you? > (There is >

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

> On Sep 29, 2019, at 1:05 PM, Uwe Kleine-König wrote: > > The step from 4.19.67-2 to 4.19.67-2+deb10u1 is harmless for this > problem. The issue that John is describing comes from a change by Roger > Shimizu to reduce the kernel size[1]. I guess there is some difference > in userspace that

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

I do not have this problem on my sheevaplug running kernel ‘4.19.67-2’ . I see that ‘4.19.67-2+deb10u1’ is available, but not yet installed on this machine. I think I’ll hold off on installing that update for a while! And, FWIW: rbthomas@sheeva:~$ grep RTC_DRV_CMOS

Re: heatsink -- was [Re: Raspberry Pi 4 is announced]

> On Jun 29, 2019, at 11:51 PM, andreimpope...@gmail.com wrote: > > On Sb, 29 iun 19, 02:18:44, Alan Corey wrote: >> Thank you, I hadn't looked at that. So there's Debian for it, not >> just Ubuntu? > > I'm only concerned with u-boot/Linux mainline support, as I don't like > using vendor

heatsink -- was [Re: Raspberry Pi 4 is announced]

So when I buy one of these in a couple of months, do I need to buy the heatsink too? Will the heatsink fit into the standard case? If not, is there a case that will fit? And, finally, is there a version of Debian that will run on one of these? Or should I just plan on running Raspbian?

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

Hi Andrei, Did you get any answer on this? I’m thinking of replacing my armel hardware (a couple of OpenRD boxes and a SheevaPlug) with something more modern, and the Pine64+ looks like a good candidate, but I’ll need to be able to install Debian. More general question — What is the status

Re: How to activate wi-fi on Cubox-i4Pro armhf

> On Mar 22, 2019, at 9:08 AM, Dominique Dumont wrote: > > On Saturday, 16 March 2019 03:37:21 CET Rick Thomas wrote: >> I tried installing the “non-free” firmware package for it >> (firmware-brcm80211) > but I get this message at boot time on the console: >>

Re: How to activate wi-fi on Cubox-i4Pro armhf

> On Mar 17, 2019, at 9:06 AM, Christopher Barry wrote: > > On Fri, 15 Mar 2019 19:37:21 -0700 > Rick Thomas wrote: > >> Does anybody know the magic for getting the wifi on a Cubox-i4Pro to >> work? >> >> I tried installing the “non-free” firmwar

How to activate wi-fi on Cubox-i4Pro armhf

Does anybody know the magic for getting the wifi on a Cubox-i4Pro to work? I tried installing the “non-free” firmware package for it (firmware-brcm80211) but I get this message at boot time on the console: > [ 21.050008] brcmfmac mmc0:0001:1: firmware: failed to >

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

> On Mar 6, 2019, at 7:46 PM, Vagrant Cascadian wrote: > > 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-referen

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

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… ;-) Thanks! Rick

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

On Tue, Feb 26, 2019, at 3:34 PM, Vagrant Cascadian wrote: > 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 (fr

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

> 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 environment”. > > If when booting, it also gives y

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

On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools package) it says “Warning: Bad CRC, using default environment”. The “default environment” is clearly *not* the environment that u-boot is using to boot the box. At least the “ethaddr” variable in that environment is clearly a

Re: Debian Installer Buster Alpha 4 release

> 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 longer be supported in Buster? What about

Re: armel/marvell kernel size

On Mar 28, 2018, at 2:22 AM, Rick Thomas <rbtho...@pobox.com> wrote: >> What filesystems do you use? Do you use any (para)virtualization? What >> about addon hardware that you have? Any USB dongles? Anything that you >> can think of? Sound? >> >> Do you use

Re: armel/marvell kernel size

On Mar 27, 2018, at 2:08 PM, Rogério Brito <rbr...@ime.usp.br> wrote: > On 2018-03-27 17:29, Rick Thomas wrote: >> On Mar 27, 2018, at 1:04 PM, Rogério Brito <rbr...@ime.usp.br> wrote: >>> As a related subject, I could compile a more stripped down versio

Re: armel/marvell kernel size

On Mar 27, 2018, at 1:04 PM, Rogério Brito wrote: > As a related subject, I could compile a more stripped down version of > the armel kernel, put it for people to download and ask people to > comment if it works for them, so that we can gauge what people actually > need from

Re: Anyone using stretch/buster/sid on ARMv4t ?

> On Nov 7, 2017, at 3:27 AM, Christian Seiler <christ...@iwakd.de> wrote: > > Hi, > > Am 2017-11-07 11:49, schrieb Rick Thomas: >> How do I know if a machine is ARMv4t? I have a sheevaplug and a >> couple of openrd machines (one “client”, the other “ultimate

Re: Anyone using stretch/buster/sid on ARMv4t ?

How do I know if a machine is ARMv4t? I have a sheevaplug and a couple of openrd machines (one “client”, the other “ultimate”) that are still doing useful work. Are they v4t? Thanks, Rick > On Nov 5, 2017, at 1:32 PM, Adrian Bunk wrote: > > Hi, > > for the armel port in

Stretch 9.1 installer on MX6 cubox-i4pro fails doing dhcp network config -- must do manual network config

Just for fun I tried installing Stretch 9.1 on my Cubox-i4Pro. When it got to configuring the network via DHCP it failed to get any configuration info. I configured the network manually, and it was able to continue. It appears that the ethernet interface is not getting initialized by the

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

On Oct 5, 2016, at 1:54 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > On 2016-10-01, Rick Thomas wrote: >> On Jun 5, 2016, at 1:35 PM, Vagrant Cascadian <vagr...@debian.org> wrote: >>> On 2016-06-05, Gaudenz Steinlin wrote: >>>> I have the same

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

> On Oct 5, 2016, at 11:57 PM, Uwe Kleine-König wrote: > > Hello, > > On 10/05/2016 10:54 PM, Vagrant Cascadian wrote: >> I believe it actually requires u-boot to initialize ram timings and >> various other parameters. You can trick the kernel into using more > >

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

> On Oct 5, 2016, at 1:54 PM, Vagrant Cascadian wrote: > > It would of course be useful to experiment with alternative methods, but > my guess is getting proper patches into u-boot may likely be the > simplest approach. It just takes some work. Anything I can do as a tester

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

On Sep 4, 2016, at 3:12 AM, Rick Thomas <rbtho...@pobox.com> wrote: >> On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian <vagr...@debian.org> wrote: >> >>> I'd be curious if you re-install and delete each partition individually >>> and re-create manua

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

> On Sep 2, 2016, at 6:33 PM, Rick Thomas <rbtho...@pobox.com> wrote: > > > On Sep 2, 2016, at 4:40 PM, Gunnar Wolf <gw...@debian.org> wrote: > >> Can somebody confirm whether the Jessie >> installer actually works reliably on this machine? (that is, w

Re: Graphical output from iMX6/Cubox-i

> On Sep 4, 2016, at 1:47 PM, Rainer Dorsch wrote: > > Hi, > > this is an interesting response > > http://forum.solid-run.com/viewtopic.php?t=2936=21022#p21022 > > Seems that I need to build xserver-xorg-video-armada > > https://github.com/xobs/xserver-xorg-video-armada >

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

On Sep 2, 2016, at 6:30 PM, Rick Thomas <rbtho...@pobox.com> wrote: > > On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > >> I'd be curious if you re-install and delete each partition individually >> and re-create manually vs. u

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

On Sep 2, 2016, at 4:40 PM, Gunnar Wolf wrote: > Can somebody confirm whether the Jessie > installer actually works reliably on this machine? (that is, whether > it's always been broken or we have a regression) I’ll give that a try as well over the weekend. Let you know what

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote: > I'd be curious if you re-install and delete each partition individually > and re-create manually vs. using one of the auto-partitioning methods. I’ll give this a try over the weekend and report back what I find. Is it

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

For what it’s worth, I just tried booting with an HDMI monitor connected to see if the silence on the serial-port was just a matter of console messages being directed to the HDMI video port instead. Still no go. Silence all-round. Rick > On Aug 22, 2016, at 9:15 PM, Rick Thomas <

Re: Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro

I can confirm this problem. I just got thru running a “stretch” install on my test Cuboxi4Pro with ingredients from: > wget > http://ftp.us.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/partition.img.gz > wget >

Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

On Jul 31, 2016, at 2:02 AM, Christian Marillat <maril...@free.fr> wrote: > On 31 juil. 2016 10:50, Rick Thomas <rbtho...@pobox.com> wrote: > >> Can you send the output of ‘uname -a ; systemd —version’ on that box? > > Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4

Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Can you send the output of ‘uname -a ; systemd —version’ on that box? Thanks! On Jul 31, 2016, at 12:22 AM, Christian Marillat <maril...@free.fr> wrote: > On 31 juil. 2016 08:50, Rick Thomas <rbtho...@pobox.com> wrote: > >> Thanks, Christian! >> >>

Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

Thanks, Christian! What is your armel box? I *do* see it on my SheevaPlug (armel), so there may be a clue. Is your armel kernel customized in some way? Enjoy! Rick > On Jul 30, 2016, at 11:33 PM, Christian Marillat <maril...@free.fr> wrote: > > On 30 juil. 2016 23:02, Ric

Systemd version 231-1 (current in Sid) doesn't work on arm

Has anyone else noticed this bug? Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on both. I’ve also tried it on amd64 and powerpc hardware. The bug is not present there.

How to use the HDMI screen as console on Cubox-i4

Hi Debian Arm folks! Does anyone know the necessary magic incantation to make my Cubox-i 4x4 use the HDMI port as console so I can run a desktop environment on it? Thanks! Rick

Re: Cubox-i 4x4 RAM

On 05/01/16 10:57, Vagrant Cascadian wrote: On 2016-04-30, Rick Thomas wrote: I finally got some time to test the experimental u-boot: u-boot-imx_2016.05~rc2+dfsg0~20160423~1-1_armhf.deb It installs and boots and recognizes 3.8GB RAM on the 4x4. So I guess I got a real 4x4 after all

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

On 04/26/16 00:51, Rick Thomas wrote: On Apr 21, 2016, at 11:54 PM, Rick Thomas <rbtho...@pobox.com> wrote: I seem to remember that I got roughly the same number (lightly less than 2.0 GiB) when I booted the manufacturer supplied u-boot and Ubuntu kernel from the uSD-card tha

Re: creating official Debian images for ARM-based NAS devices

On Apr 13, 2016, at 10:27 PM, Daniel Pocock wrote: > If people are relying upon TFTP, it > would not be hard to produce a Debian Live DVD that has a > preconfigured DHCP/BOOTP/TFTP services for people to initialize other > devices like this. On Apr 19, 2016, at 2:27 AM, Riku

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

On Apr 21, 2016, at 11:54 PM, Rick Thomas <rbtho...@pobox.com> wrote: >>> >>> I seem to remember that I got roughly the same number (lightly less >>> than 2.0 GiB) when I booted the manufacturer supplied u-boot and >>> Ubuntu kernel from the uSD-ca

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

it got a men-fault? Fascinating… What other things, besides memory config, get passed this way? Thanks! Rick On Apr 22, 2016, at 2:02 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > On 2016-04-21, Rick Thomas wrote: >> On Apr 21, 2016, at 9:04 AM, Vagrant Cascadian <vagr...

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

On Apr 21, 2016, at 9:04 AM, Vagrant Cascadian <vagr...@debian.org> wrote: > On 2016-04-21, Rick Thomas wrote: >> Are you saying that the amount of RAM seen by Debian Linux is >> determined by something in u-boot? > > Yes. How is this information communicated from

Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

my curiosity (: > > On 2016-04-20, Rick Thomas wrote: >> On Sun, Apr 17, 2016, at 06:36 PM, Steven Chamberlain wrote: >>> I was wondering what is the performance of various armhf boards, for >>> package building. >> ... >>> cbxi4a-armhf-rb.debian.net

Cubox-i4x4 - [was Re: Performance of armhf boards]

On Apr 20, 2016, at 10:26 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > This appears to be a thread forked from a reproducible-builds > discussion. :) > > On 2016-04-20, Rick Thomas wrote: >> On Sun, Apr 17, 2016, at 06:36 PM, Steven Chamberlain wrote:

Re: Performance of armhf boards

On Sun, Apr 17, 2016, at 06:36 PM, Steven Chamberlain wrote: > Hi! > > I was wondering what is the performance of various armhf boards, for > package building. ... > cbxi4a-armhf-rb.debian.net19962365# 4x,4G; > Cubox-i4x4 > cbxi4pro0-armhf-rb.debian.net

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Feb 15, 2016, at 2:29 AM, JM wrote: > Actually, I just remembered that 4.4 kernel will try to load both the > old and the new module (but without allhwsupport), so please try the > following: > > rmmod mv_cesa > rmmod marvell_cesa > modprobe marvell_cesa allhwsupport=1 >

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

> Here you go... > >> root@sheeva:~# rmmod mv_cesa >> root@sheeva:~# modprobe marvell_cesa allhwsupport=1 >> root@sheeva:~# dmesg | tail -n 20 >> [ 16.730426] systemd[1]: Mounted Debug File System. >> [ 16.756783] systemd[1]: Started Load Kernel Modules. >> [ 16.776948] systemd[1]: Started

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Feb 9, 2016, at 4:12 AM, JM wrote: > On Fri, Feb 5, 2016 at 5:12 AM, Martin Michlmayr wrote: >> * JM [2016-02-05 04:20]: >>> To quickly bring you up to speed, the driver for Marvell's hardware >>> crypto accelerator embedded in their

Odd messages booting Cubox-i4 Pro "imx-gpc 20dc000.gpc: failed to get pu regulator: -517" and "ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)"

Does anyone know what the error messages Does anybody know what is causing the subject error messages? It almost looks like the DTB is claiming a couple of devices that don't exist on this hardware... But I don't understand enough of that process to be sure. Anybody got some clues? I've

Re: sheeveplug new u-boot - just to make sure I've got it right...

On Jan 22, 2016, at 8:09 PM, Martin Michlmayr wrote: >> >> If this is correct, it needs to be reflected in a README file in, >> for example, the /usr/share/doc/u-boot-tools/examples directory. >> And a pointer to that README needs to be placed in >>

  1   2   3   >