Re: RPi 4b Wifi Device

[Michael van Elst]

tomd...@wavecable.com ("Thomas D. Dean") writes:

>What is the wifi device in the RPi 4b? Driver?

It's a chip similar to the one in the older RPIs:

bwfm0: chip 0x4345 rev 6
bwfm0: Firmware file default:brcmfmac43455-sdio.bin
bwfm0: Firmware file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
bwfm0: Found Firmware file: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
bwfm0: NVRAM file default:brcmfmac43455-sdio.txt
bwfm0: NVRAM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
bwfm0: Found NVRAM file: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
bwfm0: CLM file default:brcmfmac43455-sdio.clm_blob
bwfm0: CLM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
bwfm0: Found CLM file: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
bwfm0: CHIPACTIVE

bwfm0: flags=0x8843 mtu 1500
ssid  nwkey *
powersave off
bssid ##:##:##:##:##:## chan 100
address: ##:##:##:##:##:##
media: IEEE802.11 autoselect (VHT mode 11ac)
status: active
inet6 fe80:::::%bwfm0/64 flags 0 scopeid 0x3

RPi 4b Wifi Device

[Thomas D. Dean]

What is the wifi device in the RPi 4b? Driver?

Tom Dean

Re: Install Failure RPi 4

[Thomas D. Dean]

On 4/18/24 13:56, Thomas D. Dean wrote:


I followed:
https://mail-index.netbsd.org/port-arm/2023/07/19/msg008301.html
and it boots.

download
https://github.com/pftf/RPi4/releases/download/v1.35/RPi4_UEFI_Firmware_v1.35.zip

> mount mmcblk0p1 /mnt
> cd /mnt
> unzip ~/RPi4_UEFI_Firmware_v1.35.zip

and reboot

Tom Dean
Silverdale, WA

Re: Install Failure RPi 4

[adr]

Of course I'm assuming that you meant dd if=arm64.img ...


 dd if=armv7.img of=/dev/mmcblk0 bs=1m conv=sync

Re: Install Failure RPi 4

[adr]

On Thu, 18 Apr 2024, Thomas D. Dean wrote:

I have an RPi 4b using a USB flash drive and RPi OS.

I attempted to install NetBSD 10 on an SD card.

On the RPi, I downloaded arm64.img.gz and extracted arm64.img.


 ls -l arm64.img

rw-rw-r-- 1 tomdean tomdean 1582301184 Apr  3 15:02 arm64.img

I used dd to copy the image to an SD card.


 dd if=armv7.img of=/dev/mmcblk0 bs=1m conv=sync


After this, the SD card looked OK for the RPi.

I shut down the RPi, removed the USB flash drive. I connected a mouse, 
keyboard, and display, and powered up with the SD card inserted.


The red LED is on continuously. The green LED flashed for ~1 sec, was off for 
~1 sec, flashed for ~2 sec, was off for ~2 sec, flashed for ~3 sec, then was 
off (5 minutes). The display flashed then was blank, again (5 min).


Tom Dean


After "dding", mount the fat partition of the card in a temporary directory, 
let's
say /mnt.
Download the last zip at https://github.com/pftf/RPi4/releases.
Extract the zip in /mnt, don't care about replacing files.
Boot the rpi.
Hit esc when the logo and the progress bar appear.
In the menu, navigate and disable the 3G ram limit.
Be sure in the boot order options that the sd card is first.
Change the cpu frequency if you want, but I don't recommend to set it more than
2GHz.
You can use serial console for the hole process, _don't_trust_the_wiki_. Use
the common gpios 14(txd) and 15(rxd) and any ground.

Regards,
adr

Install Failure RPi 4

[Thomas D. Dean]

I have an RPi 4b using a USB flash drive and RPi OS.

I attempted to install NetBSD 10 on an SD card.

On the RPi, I downloaded arm64.img.gz and extracted arm64.img.

> ls -l arm64.img
rw-rw-r-- 1 tomdean tomdean 1582301184 Apr  3 15:02 arm64.img

I used dd to copy the image to an SD card.

> dd if=armv7.img of=/dev/mmcblk0 bs=1m conv=sync

After this, the SD card looked OK for the RPi.

I shut down the RPi, removed the USB flash drive. I connected a mouse, 
keyboard, and display, and powered up with the SD card inserted.


The red LED is on continuously. The green LED flashed for ~1 sec, was 
off for ~1 sec, flashed for ~2 sec, was off for ~2 sec, flashed for ~3 
sec, then was off (5 minutes). The display flashed then was blank, again 
(5 min).


Tom DeanI have an RPi 4b using a USB flash drive and RPi OS.

I attempted to install NetBSD 10 on an SD card.

On the RPi, I downloaded arm64.img.gz and extracted arm64.img.

> ls -l arm64.img
rw-rw-r-- 1 tomdean tomdean 1582301184 Apr  3 15:02 arm64.img

I used dd to copy the image to an SD card.

> dd if=armv7.img of=/dev/mmcblk0 bs=1m conv=sync

After this, the SD card looked OK for the RPi.

I shut down the RPi, removed the USB flash drive. I connected a mouse, 
keyboard, and display, and powered up with the SD card inserted.

The red LED is on continuously. The green LED flashed for ~1 sec, was off for 
~1 sec, flashed for ~2 sec, was off for ~2 sec, flashed for ~3 sec, then was 
off (5 minutes). The display flashed then was blank, again (5 min).

I powered down, removed the SD card, reconnected the USB flash drive and 
powered up. I reinserted the SD card.

> sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98B95E86-7515-4738-B538-FC5107ADFEC9

Device  Start  End  Sectors  Size Type
/dev/mmcblk0p1  32768   196607   163840   80M EFI System
/dev/mmcblk0p2 196608 62332927 62136320 29.6G NetBSD FFS

> sudo mount /dev/mmcblk0p1 /mnt
> ls -l /mnt
total 23142
drwxr-xr-x 3 root root 1024 Apr  1 23:28 EFI
-rwxr-xr-x 1 root root 1594 Apr  1 23:28 LICENCE.broadcom
-rwxr-xr-x 1 root root52476 Apr  1 23:28 bootcode.bin
-rwxr-xr-x 1 root root   33 Apr  1 23:28 cmdline.txt
-rwxr-xr-x 1 root root  155 Apr  1 23:28 config.txt
drwxr-xr-x 8 root root 1024 Apr  1 23:28 dtb
-rwxr-xr-x 1 root root 7269 Apr  1 23:28 fixup.dat
-rwxr-xr-x 1 root root 5412 Apr  1 23:28 fixup4.dat
-rwxr-xr-x 1 root root 3180 Apr  1 23:28 fixup4cd.dat
-rwxr-xr-x 1 root root 3180 Apr  1 23:28 fixup_cd.dat
-rwxr-xr-x 1 root root 16761568 Apr  1 23:28 netbsd.img
-rwxr-xr-x 1 root root  2979264 Apr  1 23:28 start.elf
-rwxr-xr-x 1 root root  2254944 Apr  1 23:28 start4.elf
-rwxr-xr-x 1 root root   808060 Apr  1 23:28 start4cd.elf
-rwxr-xr-x 1 root root   808060 Apr  1 23:28 start_cd.elf

> cat /mnt/config.txt
#
upstream_kernel=1
#
arm_64bit=1
os_prefix=dtb/broadcom/
cmdline=../../cmdline.txt
kernel=/netbsd.img
kernel_address=0x20
enable_uart=1
force_turbo=0

Broken Link

[Thomas D. Dean]

On https://wiki.netbsd.org/ports/evbarm/
Select NetBSD/evbarm 10.0 INSTALL notes
Produces Error 404.

Tom Dean

Re: unattended install

[Taylor R Campbell]

> Date: Wed, 17 Apr 2024 15:12:21 +0200
> From: "Enrico Weigelt, metux IT consult" 
> 
> is there any way of unattended installation (eg. from the ISO) ?
> 
> Rationale: I need to create VM images by a build pipeline (on kvm).

If there isn't an image that already serves your needs, the
distrib/utils/embedded/mkimage script is how we would approach this on
systems where the goal isn't partly to test interactive installation
with sysinst:

https://nxr.netbsd.org/xref/src/distrib/utils/embedded/mkimage?r=1.82

Currently we make Arm, RISC-V, and some other images this way, with
config files under distrib/utils/embedded/conf/, like this one:

https://nxr.netbsd.org/xref/src/distrib/utils/embedded/conf/arm64.conf?r=1.16
https://nxr.netbsd.org/xref/src/distrib/utils/embedded/conf/evbarm.conf?r=1.42

Here's how we invoke it in the build (${.TARGET} in this rule will be
something like `smp_arm64' for arm64.img):

https://nxr.netbsd.org/xref/src/etc/etc.evbarm/Makefile.inc?r=1.131#80

There are also amd64 and i386 config files, not currently used in the
NetBSD release build -- the x86 live images are built another way, but
you can use mkimage for x86 VM images using amd64.conf or i386.conf.

The mkimage script doesn't have to run under NetBSD -- you can run it
on another system using NetBSD's cross-build toolchain built with
`build.sh tools'.

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[adr]

On Thu, 18 Apr 2024, Taylor R Campbell wrote:


Date: Thu, 18 Apr 2024 15:53:27 +
From: Taylor R Campbell 
To: adr 
Cc: netbsd-users@NetBSD.org, Liam Proven 
Subject: Re: Please forgive a blatant plug: I reviewed v10 for the Reg

Hi adr,

Liam provided valuable feedback in both reviews, and if anything we
haven't put enough effort into smoothing out the rough edges Liam
pointed out, like figuring out why command-line editing and PATH
weren't set up right out of the box.  There's always room for
improvement, and our documentation is sometimes hard to follow,
missing parts, or too wordy in places.

This feedback helps us to improve the out-of-the-box experience for
users, fix unnecessarily confusing parts of the experience, and
identify where the documentation is lacking or hard to find.

Gatekeeping NetBSD on the basis of prior expertise is not good for the
community, and not good for the project.  sysinst is supposed to be a
tool to help you, not a test of your patience or knowledge.

We would appreciate it if you toned down your criticism of a new user
and their honest feedback about the experience so we as a community
don't discourage other users and further feedback as we continue to
improve NetBSD.

Thanks,
-Riastradh, NetBSD core team



This person wasn't talking only about the problems that someone
could have installing netbsd. There are problems. If you read the
review that he or she did to the las version of netbsd, you'll find
that the majority of the problems were a result of this person don't
bothering to read the documentation, and ignorance of basic unix.

All of us are here in this world to learn.

The problem is when you start making affirmations based on that
ignorance missleading people an creating a bad image of the project.

This person didn't say "I don't know what is happening with the
shell when you install netbsd". This person said "netbsd doesn't
support cursor keys". Just one example among so many. You should
read some commentaries of surprised readers in that article.

If that's ok with you, and with what this king of thing does to
the image of the netbsd project among unix-like operating system
users, and you want to encourage that, I will respect it because
you are part of the core team and this is not my house.

Next time I'll ignore it.

Regards.

adr.

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[adr]

On Thu, 18 Apr 2024, Jonathan A. Kollasch wrote:

This all was uncalled for, and is not welcome in this community.


If you think that encouraging someone that wrote this:

https://www.theregister.com/2022/08/10/netbsd_93/

is ok, then I'm not interested in your opinion more that I'm in the
opinion of that person about netbsd.

PS. I've always found of bad taste individuals pretending to be
the voice of a community.

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[Taylor R Campbell]

Hi adr,

Liam provided valuable feedback in both reviews, and if anything we
haven't put enough effort into smoothing out the rough edges Liam
pointed out, like figuring out why command-line editing and PATH
weren't set up right out of the box.  There's always room for
improvement, and our documentation is sometimes hard to follow,
missing parts, or too wordy in places.

This feedback helps us to improve the out-of-the-box experience for
users, fix unnecessarily confusing parts of the experience, and
identify where the documentation is lacking or hard to find.

Gatekeeping NetBSD on the basis of prior expertise is not good for the
community, and not good for the project.  sysinst is supposed to be a
tool to help you, not a test of your patience or knowledge.

We would appreciate it if you toned down your criticism of a new user
and their honest feedback about the experience so we as a community
don't discourage other users and further feedback as we continue to
improve NetBSD.

Thanks,
-Riastradh, NetBSD core team

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[Jonathan A. Kollasch]

On Thu, Apr 18, 2024 at 03:23:34PM +, adr wrote:
> On Thu, 18 Apr 2024, Liam Proven wrote:
~ ~ 
> > Comments and feedback welcomed!
> 
> [...]The last time we looked at NetBSD, we checked out version 9.3[...]
> 
> I remember reading that and not understanding how the person who
> wrote that encouraged him|her self to review the os.
~ 
> So unprofessional.

This all was uncalled for, and is not welcome in this community.

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[adr]

On Thu, 18 Apr 2024, Liam Proven wrote:


Date: Thu, 18 Apr 2024 12:00:32 +0100
From: Liam Proven 
To: Netbsd-Users-List 
Subject: Please forgive a blatant plug: I reviewed v10 for the Reg

I thought this might interest folks here...

NetBSD 10 proves old tech can still kick apps and take names three decades later

Proper old-school Unix, not like those lazy, decadent Linux types

https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/

Comments and feedback welcomed!


[...]The last time we looked at NetBSD, we checked out version 9.3[...]

I remember reading that and not understanding how the person who
wrote that encouraged him|her self to review the os.

* Not reading the official documentation, pointing to tutorials
like in the linux world.

* Ignorance about the edit mode of the shells, and instead of
talking about the usefulness of having one of them (vi, emacs)
activated by default, blaiming that it was a lack of support of
curor keys, and saying that linux is a modern operating system that
supports cursor keys. I couldn't stop a laugh. No idea what shell
was the person using, no idea that there are several shells to choose
and more to install.

* Not finishing the installation as recommended in the guide, and then
saying that the netbsd installation is "a three-step process".

* Not reading the pkgsrc documentation, even the introduction, and
basically whinning because it wasn't apt. Again, pointing to
tutorials on how to install pkgin...

* Not idea what PATH is. cd to /usr/pkg/bin to execute pkgin
How could this person had the balls to "review" and Operating System

* Not reading the netbsd guide about parttions, dislabel, wadges,
 and saying that unlike netbsd, linux supports partitions that
other oses can open.

And lots, lots of crap. When I followed that link and see that it
was _you_, I stoped reading.

You can use C-n, C-p to move through the menus in sysinst if for
some reason your keyboard isn't fully supported. The letters and
numbers are for selecting quickly an entry. This is common in a
lot of curses application, again, basic stuff. You could ask all
this nonsense to the list, I'm sure people here including myself
would help you.

The problem is that you went with all this lack of basic unix
knowledge and made a "review" of netbsd, missleading people with
your ignorance, something incredibly common in the linux world.

So, no, I can't give you a feedback of your last "piece".

And if anyone reading this thinks that I'm an asshole, read the
points I made and follow that link. I've contained myself. Really.

Who edit theregister by the way?

So unprofessional.

adr

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[Liam Proven]

On Thu, 18 Apr 2024 at 14:21, Benny Siegert  wrote:
>
> Wonderful article, thanks for sharing! :D

Oh thank you! Thank you too for your help in inspiring it – and
putting me in touch with Martin.

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
IoM: (+44) 7624 277612: UK: (+44) 7939-087884
Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[Michael Huff]

On Thu, Apr 18, 2024 at 3:01 AM Liam Proven  wrote:

> I thought this might interest folks here...
>
> NetBSD 10 proves old tech can still kick apps and take names three decades
> later
>
> Proper old-school Unix, not like those lazy, decadent Linux types
>
> https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/
>
> Comments and feedback welcomed!
>
> --
> Liam Proven ~ Profile: https://about.me/liamproven
> Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
> Twitter/LinkedIn: lproven ~ Skype: liamproven
> IoM: (+44) 7624 277612: UK: (+44) 7939-087884
> Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053
>

I saw it on Hacker News ,
enjoyed the discussion on both sites (HN, Register) . Thanks for writing it
up and sharing it!

Re: Please forgive a blatant plug: I reviewed v10 for the Reg

[Benny Siegert]

On Thu, Apr 18, 2024 at 1:01 PM Liam Proven  wrote:
> NetBSD 10 proves old tech can still kick apps and take names three decades 
> later
>
> Proper old-school Unix, not like those lazy, decadent Linux types
>
> https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/
>
> Comments and feedback welcomed!

Wonderful article, thanks for sharing! :D

-- 
Benny

Please forgive a blatant plug: I reviewed v10 for the Reg

[Liam Proven]

I thought this might interest folks here...

NetBSD 10 proves old tech can still kick apps and take names three decades later

Proper old-school Unix, not like those lazy, decadent Linux types

https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/

Comments and feedback welcomed!

--
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
IoM: (+44) 7624 277612: UK: (+44) 7939-087884
Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053

Re: pkg_admin: Cannot open /usr/pkg/pkgdb/pkg-vulnerabilities

[Christopher Pinon]

Jay  writes:

> Can you do 
> pkg_admin fetch-pkg-vulnerabilities

Yes, as su

> pkg_admin audit

This works as an ordinary (wheel) user as well

> ?
> Also are you running as root or sudo?

The message that I mentioned was a system message from Charlie Root,
presumably due to a daily cron job

In any case, I may have inadvertently corrected the problem (with the
setting fetch_pkg_vulnerabilities=YES in /etc/daily.conf ), so I'll see
what Charlie Root tells me tomorrow!

Thanks for your reply,
C.

pkg_admin: Cannot open /usr/pkg/pkgdb/pkg-vulnerabilities

[Christopher Pinon]

Hi,

If I may, just a simple question. On a fresh NetBSD-10.0 installation, I
receive the following message:

pkg_admin: Cannot open /usr/pkg/pkgdb/pkg-vulnerabilities: No such file or 
directory

This puzzles me because both the directory /usr/pkg/pkgdb and the file
/usr/pkg/pkgdb/pkg-vulnerabilities are present.

Is it a problem of permissions?

Thanks,
C.

Re: Use a wallpaper

[Vitaly Shevtsov]

If you start X with startx, then you can put "feh --bg-fill wallpaper.png"
into .xinitrc before last "exec "

ср, 17 апр. 2024 г., 23:35 Todd Gruhn :

> My current root (?) window is black.
>
> How do I put a graphic or wallpaper on there
> when I start X11?
>