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

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 bug report against for this problem? There's nothing to report. No model of Raspberry PI has

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 "tested

Re: Debian Bullseye on Raspberry Pi 4 4GB?

On zaterdag 20 februari 2021 13:46:00 CET Rick Thomas wrote: > Hmmm... The "tested images" page [1] lists images for both Buster and > Bullseye that reportedly boot on the RPi 0W. I don't know what they had to > do to make it work. They're cheap enough that I may just buy one and try > it, for

Re: Debian Bullseye on Raspberry Pi 4 4GB?

I am not convinced that all images listed on [1] do work as advertized. On 20.02.21 13:46, Rick Thomas wrote: > Hmmm... The "tested images" page [1] lists images for both Buster and > Bullseye that reportedly boot on the RPi 0W. I don't know what they had to > do to make it work. They're

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?

Hmmm... The "tested images" page [1] lists images for both Buster and Bullseye that reportedly boot on the RPi 0W. I don't know what they had to do to make it work. They're cheap enough that I may just buy one and try it, for fun. Rick On Sat, Feb 20, 2021, at 2:10 AM, Ian Campbell wrote:

Re: Debian Bullseye on Raspberry Pi 4 4GB?

Hi Luke, On 2021.02.20 04:16, Luke Kenneth Casson Leighton wrote: On Friday, February 19, 2021, Pete Batard > wrote: > Why, when it is absolutely possible to achieve it, as was demonstrated on a cheap platform like the Pi (that actually comes with horrible quirks to

Re: Debian Bullseye on Raspberry Pi 4 4GB?

On Sat, Feb 20, 2021 at 11:10 AM Ian Campbell 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

Re: Debian Bullseye on Raspberry Pi 4 4GB?

Yet if you stick with Raspbian everything "just works". There is only one distribution that works on everything they sold. If you look at the source of raspi-config you can see how the software identifies the hardware versions And ARMv7 becomes ARMv8 under the right conditons and can run 64 bit

Re: Debian Bullseye on Raspberry Pi 4 4GB?

Am 20. Februar 2021 11:49:27 schrieb Ian Campbell : I'm sure someone who follows rpi closer than I will correct if not, but isn't the whole Pi Zero range based the older ARMv6 (i.e. not armhf) processor which requires the Raspbian rebuild because it is not compatible with the armhf baseline

Re: Debian Bullseye on Raspberry Pi 4 4GB?

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 someone who follows rpi closer than I will

Re: Debian Bullseye on Raspberry Pi 4 4GB?

Ryutaroh Matsumoto wrote: > 2 and 3 can be worked around by module_blacklist=vc4 in the kernel comand > line. Because of 4, I am using self-compiled upstreadm kernel 5.9.16... > Another intel laptop also becomes very unstable with kernel 5.10, > and I am staying away from 5.10. > > Best regards,