Date: Wed, 10 Mar 2021 20:14:07 -0800 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> Cc: freebsd-arm@freebsd.org Subject: Re: RPi4 Status and xorg behavior (Mar 5 2021 firmware is bad for USB based booting) Message-ID: <B8173862-953B-4561-8C30-23E11FA298C9@yahoo.com> In-Reply-To: <F811478C-C861-442B-A22F-15FAD33C0581@googlemail.com> References: <AAA4E495-4E9E-4C55-A07E-74D9737EC15B@yahoo.com> <20210307155515.GA4591@www.zefox.net> <67BF2EAC-04AD-4822-99B2-48A99563331F@yahoo.com> <G5ZAfvg49jl5dj40HAnjmwoEKpVSuGp8KmiBrSY_EBLXou6UGBIjU3tVxUuPGKeCvXEovg2d3tqhIGOmQCyb7c3wKsUHJ8xrSasvwXfbqwk=@protonmail.com> <4B963C56-D7E9-42FE-8B8B-B8A425ACE78F@yahoo.com> <20210308011035.GA6603@www.zefox.net> <DB3CD5BA-337E-476F-9F0C-C70401F7D800@yahoo.com> <C500EE5B-B483-4580-8C7C-9B9B013D726B@googlemail.com> <20210308173045.GB13739@www.zefox.net> <4D8FD8EE-6642-46ED-8AAE-CAECB36572F6@yahoo.com> <20210309023348.GA16279@www.zefox.net> <EC4C3040-E86A-45EC-9E4F-0E0F81ED3CBD@yahoo.com> <24202B69-A5F2-41CF-A6F4-7113B76B9B0E@yahoo.com> <F811478C-C861-442B-A22F-15FAD33C0581@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-10, at 16:16, Klaus K=C3=BCchemann <maciphone2 at = googlemail.com> wrote: >=20 >> Am 10.03.2021 um 23:28 schrieb Mark Millard via freebsd-arm = <freebsd-arm@freebsd.org>: >>=20 >> =E2=80=A6=E2=80=A6 >> .. >> (temporarily where = https://github.com/raspberrypi/firmware/tree/master/boot/ =E2=80=A6 >=20 > here too ;-) >=20 > W A R N I N G=20 >=20 > new CRAPWARE-files from rpi-org-upstream dated Wed, / 10. march 2021/ = 02:36 >=20 > will kill ' powerd' ( at least on my machine ) : > =E2=80=94 =E2=80=A6=E2=80=A6. > Starting powerd. > powerd: no cpufreq(4) support -- aborting: No such file or directory > /etc/rc: WARNING: failed to start 0.88, 0.38, 0.15 up 0+00:00:59 = 19:38:39 > ... > -- >=20 > files no further tested because quickly removed from my beautiful = system :-) Ha Ha=20 I will remind of what the RPi* folks report about using such github materials (in an raspiOS or raspiOS64 context, usually via rpi-update use): = https://www.raspberrypi.org/documentation/raspbian/applications/rpi-update= .md says . . . QUOTE WARNING: Pre-release versions of software are not guaranteed to work. = You should not use rpi-update on any system unless recommended to do so = by a Raspberry Pi engineer. It may leave your system unreliable or even = completely broken. It should not be used as part of any regular update = process. . . . rpi-update will download the latest pre-release version of the linux = kernel, its matching modules, device tree files, along with the latest = versions of the VideoCore firmware. It will then install these files to = relevant locations on the SD card, overwriting any previous versions.=20 All the source data used by rpi-update comes from the GitHub repo = https://github.com/Hexxeh/rpi-firmware. This repository simply contains = a subset of the data from the official firmware repository, as not all = the data from that repo is required. END QUOTE https://github.com/Hexxeh/rpi-update says: QUOTE This is only intended for use with Raspbian. If you are using a = different distribution then check with the maintainers if using = rpi-update is safe. If the distribution ships a custom kernel (e.g. BerryBoot), then it = almost certainly is not safe. . . . Even on Raspbian you should only use this with a good reason. This gets you the latest bleeding edge kernel/firmware. There is always = the possibility of regressions. Bug fixes and improvements will eventually make their way into new = Raspbian releases and apt-get when they are considered sufficiently well = tested. A good reason for using this would be if you like to help with the = testing effort, and are happy to risk breakages and submit bug reports. = These testers are welcome. . . . Backing up before updating is always advisable. END QUOTE FreeBSD's kernel is an example of a "custom kernel", even more so because they are likely presuming linux. Releases showing up in "apt-get" are only from some of the tagged commits, no others. The RPi*'s release and pre-release criteria do not involve FreeBSD compatibility in any direct way. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B8173862-953B-4561-8C30-23E11FA298C9>