NetBSD 10 BETA amd64 Huawei MateStation S feedback.

anarchosax

The following is preliminary feedback on NetBSD 10 BETA amd64 running on my Huawei MateStation S. Dmesg is located here.

Audio
According to dmesg, my Behringer UMC202HD usb sound card was discovered, but when I run:
$ audiocfg list 0: [*] audio0 @ hdafg0: ATI R6xx HDMI playback: 2ch, 48000Hz record: unavailable (P-) slinear_le 16/16, 2ch, { 32000, 44100, 48000 } ( ) ac3 16/16, 2ch, { 32000, 44100, 48000 } (PR) slinear_le 16/16, 2ch, 48000-48000Hz 1: [ ] audio1 @ hdafg1: Realtek product 0256 playback: 2ch, 48000Hz record: 2ch, 48000Hz (PR) slinear_le 16/16, 2ch, { 44100, 48000, 96000, 192000 } (PR) slinear_le 20/32, 2ch, { 44100, 48000, 96000, 192000 } (PR) slinear_le 24/32, 2ch, { 44100, 48000, 96000, 192000 } ( ) ac3 16/16, 2ch, { 44100, 48000, 96000, 192000 }
The sound card isn't listed.

Display
Dmesg lists the CPU correctly:
AMD Ryzen 5 4600G with Radeon Graphics
however, I don't see anything more specific in dmesg or on the Huawei homepage. Currently, I am only able to get a resolution of 1024 x 768 (4:3).

Network
$ ifconfig re0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 capabilities=0x3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx> capabilities=0x3f80<UDP4CSUM_Rx,UDP4CSUM_Tx> enabled=0 ec_capabilities=0x3<VLAN_MTU,VLAN_HWTAGGING> ec_enabled=0 address: 14:de:39:c3:79:1c media: Ethernet autoselect (1000baseT full-duplex) status: active inet6 fe80::16de:39ff:fec3:791c%re0/64 flags 0 scopeid 0x1 inet 192.168.1.221/24 broadcast 192.168.1.255 flags 0 lo0: flags=0x8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33624 status: active inet6 ::1/128 flags 0x20<NODAD> inet6 fe80::1%lo0/64 flags 0 scopeid 0x2 inet 127.0.0.1/8 flags 0

Unfortunately, wifi isn't working. I don't need wifi at this point, as this is a desktop box. The unfortunate aspect is in relation to this computer actually having a laptop motherboard in a desktop box (to my understanding). So if wifi can work on here, it should work on the Huawei comparable laptops as well.

If I can get both audio and display working properly, I will keep this system for more in depth testing. If not, then I probably won't...

rvp

anarchosax According to dmesg, my Behringer UMC202HD usb sound card was discovered

Yes, but then there's an error:

[     2.596592] uaudio0 at uhub5 port 2 configuration 1 interface 0
[     2.596592] uaudio0: BEHRINGER (0x1397) UMC202HD 192k (0x0507), rev 2.00/1.12, addr 2
[     2.596592] uaudio0: autoconfiguration error: audio descriptors make no sense, error=4

anarchosax Currently, I am only able to get a resolution of 1024 x 768 (4:3).

Recompile the kernel to include the amdgpu DRMKMS driver. This is commented out in the GENERIC config. And, update to the latest sources. Some fixes have recently been applied. Right now, you're running on genfb, the unaccelerated generic framebuffer:

[     1.012862] genfb0 at pci8 dev 0 function 0: ATI Technologies product 1636 (rev. 0xc9)
[     1.012862] genfb0: framebuffer at 0xc0000000, size 1024x768, depth 32, stride 4096
[     1.012862] genfb0: shadow framebuffer enabled, size 3072 KB
[     1.012862] wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation)
[     1.012862] wsmux1: connecting to wsdisplay0
[     1.012862] drm at genfb0 not configured

anarchosax Unfortunately, wifi isn't working.

Yes:

[     1.012862] Realtek Semiconductor product c822 (miscellaneous network) at pci6 dev 0 function 0 not configured

anarchosax

rvp Yes, but then there's an error:

Is there a solution for this, or aren’t USB sound cards supported in NetBSD? As I plan testing some of the basic music making hardware (USB keyboards and pads) and software (Fluidsynth, Qsynth soundfonts, LMMS) on NetBSD 10 BETA, this is a bit of a precondition to attempt compiling a kernel for the DRMKMS driver, as I have never attempted compiling a system kernel before…

rvp

anarchosax Is there a solution for this

File a PR for this. Attach a dmesg output after booting the kernel with the -vx flags. (In the bootloader, drop into the prompt, then type: boot -vx)

It would be even more helpful if you can compile a kernel with options UAUDIO_DEBUG.

anarchosax I have never attempted compiling a system kernel before…

Chapter 34

anarchosax

rvp OK, this looks like more of a medium term project in my case. I have a Lenovo T480s laptop that I can attach my extra Behringer USB sound card to. The dmesg output can be posted, but anything with using the send-pr command and compiling a new kernel will take time for me to learn, as the send-pr mechanism looks like it relies on the internal (system) mail system and vi, neither of which do I have much experience with, and none at all with compiling a kernel.

I will have to post at some later point about the amdgpu issue, as I have had to (at least temporarily) install a different system on the Huawei, so that I can use it at a "normal" resolution...

rvp

anarchosax as the send-pr mechanism looks like it relies on the internal (system) mail system

Use the Send PR form--the 2nd link in the URL I posted above.

anarchosax and vi, neither of which do I have much experience with

No need for the hairshirt when there's an entire category of editors.

anarchosax as I have had to (at least temporarily) install a different system on the Huawei, so that I can use it at a "normal" resolution...

Drop into the bootloader prompt, then type gop. This should give you a list of available resulutions. gop 0 is, usually, the highest. You can make this permanent by adding that command to /boot.cfg

anarchosax

rvp Use the Send PR form--the 2nd link in the URL I posted above.

Yes, that will work fine.

rvp No need for the hairshirt when there's an entire category of editors.

That was in reference to the cli send-pr.

rvp Drop into the bootloader prompt, then type gop. This should give you a list of available resulutions. gop 0 is, usually, the highest. You can make this permanent by adding that command to /boot.cfg

Yes, I tried that. gop 0 works fine on the boot up text, but has no affect at all when logged in, despite adding the command to /boot.cfg...

anarchosax

I just reinstalled the system and tried adding gop 0 and gop=0 on separate occasions to the /boot.cfg file. Neither work. I have also tried unchecking the “save session for future logins” box when shutting down XFCE…

~~If I am to use the gop 0 command when booting, how do I get out of the boot prompt editor and continue the boot, without quitting?~~

I figured it out, booted with gop 0, but halfway through the boot process, the text gets larger than if I hadn’t done anything at all… so, a worse resolution in the end.

BTW, I am getting an interesting message, when I shutdown the computer:
vesa: ignoring device with a bound kernel driver

rvp

anarchosax but halfway through the boot process, the text gets larger than if I hadn’t done anything at all… so, a worse resolution in the end.

No, that just a larger font being used. There are 2 fonts compiled into GENERIC, 8x16 and 16x32, and the kernel picks one or the other so that you don't up with a teeny unreadable font. genfb can't switch resolutions on the fly which is why you have to set it up beforehand with gop or vesa.

anarchosax BTW, I am getting an interesting message, when I shutdown the computer:
vesa: ignoring device with a bound kernel driver

Hmm. vesa shouldn't be active on a UEFI BIOS. Can you post a dmesg output? And point out which install image you used--the standard one or the BIOS image?

Also, the output of this command:

sysctl machdep.bootmethod

anarchosax

rvp Hmm. vesa shouldn't be active on a UEFI BIOS. Can you post a dmesg output? And point out which install image you used--the standard one or the BIOS image?

Also, the output of this command:
sysctl machdep.bootmethod

Here is the dmesg output. I used the standard image.
$ sysctl machdep.bootmethod machdep.bootmethod = UEFI

Edit:
Still seeing the vesa message at shutdown. A bit of a mystery.

anarchosax

rvp Yeah. I still see the RTC errrors.

Interestingly, it doesn't appear to be an issue in Linux, when checking dmesg:

rtc_cmos 00:01: RTC can wake from S4
rtc_cmos 00:01: registered as rtc0
rtc_cmos 00:01: setting system clock to 2023-03-03T13:35:13 UTC

The clock in the UEFI BIOS is set to UTC time and displays the correct time...

rvp No it is 1920x1080 now:

OK, so then I am just getting the large font that you referred to earlier (?):

rvp No, that just a larger font being used. There are 2 fonts compiled into GENERIC, 8x16 and 16x32, and the kernel picks one or the other so that you don't up with a teeny unreadable font. genfb can't switch resolutions on the fly which is why you have to set it up beforehand with gop or vesa.

So, the question is how do I get the smaller font? It probably would be useful in connection with compiling the kernel...

In that context, I have made some preliminary notes in preparation:

1) The first step appears to be to ensure that the compiler set is installed, but I notice that when compiling ee, the necessary software gets downloaded if not installed...

2) The second step is:
mkdir /usr/src
chown <user> /usr/src

Downloading sources for a NetBSD stable branch (?)

3) The third step is to get the file syssrc.tgz. Not sure what I am looking for, as what you described earlier sounds like a "current" kernel? I couldn't find anything in:
http://ftp.netbsd.org/pub/NetBSD/NetBSD-release-10/tar_files/src/

4) Copy to and unpack the syssrc.tgz file in /usr/src.

5) Edit the make file to allow recompiling the kernel to include the amdgpu DRMKMS driver. What do I need to add, uncomment, etc. in the file? I am hoping that everything else will be compiled as in a standard amd64 kernel without any intervention on my part, as I have no idea what I am doing, despite reading chapters 32 and 34 of the guide...

rvp

anarchosax Here is the dmesg output.

[     1.013516] genfb0 at pci8 dev 0 function 0: ATI Technologies product 1636 (rev. 0xc9)
[     1.013516] genfb0: framebuffer at 0xc0000000, size 1024x768, depth 32, stride 4096
[     1.013516] genfb0: shadow framebuffer enabled, size 3072 KB

Still using a 1024x768 mode, I see. I thought you had addes the gop N command to /boot.cfg...?

anarchosax Still seeing the vesa message at shutdown. A bit of a mystery.

Yes. I don't see how that's active on the amd64 architecture--I could understand on x86...

BTW, there are these in that dmesg output:

[     1.000000] RTC BIOS diagnostic error 0xcb<clock_battery,ROM_cksum,fixed_disk>
...
[     2.723341] WARNING: NVRAM century is 32 but RTC year is 2023

Try:
a) Load the "default settings" in BIOS.
b) Update the BIOS.

rvp

anarchosax but as far as I can tell, there is no difference. I am still getting the big font in the command line, which I believe is still 1024 x 763

No it is 1920x1080 now:

[     1.039368] genfb0 at pci8 dev 0 function 0: ATI Technologies product 1636 (rev. 0xc9)
[     1.039368] genfb0: framebuffer at 0xc0000000, size 1920x1080, depth 32, stride 7680
[     1.039368] genfb0: shadow framebuffer enabled, size 8100 KB

and in Xorg.0.log:

[    59.621] (**) Option "Device" "/dev/wsmouse"
[    59.628] (II) /dev/wsmouse minimum x position: 0
[    59.628] (II) /dev/wsmouse maximum x position: 1919
[    59.628] (II) /dev/wsmouse minimum y position: 0
[    59.628] (II) /dev/wsmouse maximum y position: 1079

though xdpyinfo | fgrep dimensions is a better way to see this.

anarchosax and ran the firmware updater, but I see in dmesg that it hasn't made any difference.

Yeah. I still see the RTC errrors.

anarchosax Still seeing the vesa message at shutdown. A bit of a mystery.

If you meant this message I see in Xorg.0.log:

[    59.544] vesa: Ignoring device with a bound kernel driver

then, don't worry about it: the vesa Xorg display driver's just saying that it's detected genfb already handling your display card.

anarchosax

rvp Still using a 1024x768 mode, I see. I thought you had addes the gop N command to /boot.cfg...?

I did. I added gop 0.

rvp Try:
a) Load the "default settings" in BIOS.
b) Update the BIOS.

I loaded the default settings, disabled secure boot and tcm. There is no firmware update newer than the currently installed version.

rvp

anarchosax I did. I added gop 0.

a) gop 0 isn't 1024x763, is it?
b) gop 0 was added as follows? my `/boot.cfg:

menu=Boot normally:gop 0;rndseed /var/db/entropy-file;boot
menu=Boot single user:rndseed /var/db/entropy-file;boot -s
menu=Boot TEST:gop 0;rndseed /var/db/entropy-file;boot NAME=NetBSD_test:
menu=Boot TEST single user:rndseed /var/db/entropy-file;boot NAME=NetBSD_test: -s
menu=Drop to boot prompt:prompt
default=1
timeout=10
clear=1
userconf=disable i915drmkms*

anarchosax There is no firmware update newer than the currently installed version.

Load the current version again--if possible.

anarchosax

rvp a) gop 0 isn't 1024x763, is it?
b) gop 0 was added as follows? my `/boot.cfg:

Thanks for the syntax. Now I have the correct syntax for gop 0 in /boot.cfg, but as far as I can tell, there is no difference. I am still getting the big font in the command line, which I believe is still 1024 x 763. I haven't run X yet as XFCE4 install is pending a working resolution. Of course, I have CWM (a fave), but that doesn't provide any display resolution setting utils...

Here is my new dmesg.

BTW, regarding the UEFI firmware, I temporarily installed Win 11 and ran the firmware updater, but I see in dmesg that it hasn't made any difference.

anarchosax

It looks like I finally got my UEFI BIOS sorted...

Unfortunately, I can see a lot going on in reference to Xorg.

rvp

anarchosax Interestingly, it doesn't appear to be an issue in Linux

There are some additional checks of the CMOS NVRAM in NetBSD. Maybe Linux isn't doing it (like FreeBSD), or maybe the firmware is buggy, or needs quirks applied. Will have to check the Linux code.

An easy way to check if NetBSD works correctly with this RTC chip is to set the time back an hour or so in the BIOS, boot into NetBSD, and run (as root): ntpdate -b pool.ntp.org. Then reboot, go back into the BIOS and see if the time was set correctly.

anarchosax OK, so then I am just getting the large font that you referred to earlier (?):

Yes.

anarchosax So, the question is how do I get the smaller font?

wsconsctl -dw font=Boldface as root will activate the smaller built-in font on the current console. You can load the other fonts in /usr/share/wscons/fonts using wsfontload, then activate it using wsconsctl using the name you supplied to wsfontload.

You can set fonts at boot time using /etc/wscons.conf. For example, the lines to load variously-sized Terminus fonts are already present in that file. Just uncomment one of them (pick a size), then use them by uncommenting setvar ttyEn font ... lines further down.

You can also try out fonts using this.

anarchosax 1) The first step appears to be to ensure that the compiler set is installed, but I notice that when compiling ee, the necessary software gets downloaded if not installed...

That's pkgsrc. It downloads sources, say, ee, then compiles and installs them. Since ee compiled, you must've installed the comp set, so you already have the system compiler gcc. But, to build the kernel you'll have to compile gcc from source again, then build the kernel using the newly built gcc. This is the tools build. You need do this only once.

You'll have to get all the tarballs here except xsrc.tgz and unpack them. (That location is for the latest NetBSD-10 source. Some of the new AMDGPU stuff has already been merged from -HEAD, but, they're still working on the driver now--and most of this will surely get pulled into -10 before the release. If you want to try out the -HEAD kernel then use the tarballs from here instead.)

I use this procedure to compile my kernels:

Add a separate user just for building stuff. As root:

useradd -m -G wsrc -s /bin/sh -c "System Builder" -g =uid bld

Unpack sources (you can update them semi-regularly using cvs--the Guide explains how)

for f in /SOME/PATH/*.tgz
do    tar -C/ -xpf $f && echo $f.
done

Prep. work dirs.

rm -rf /usr/obj /usr/tools
install -d -m 775 -o root -g wsrc /usr/obj /usr/tools

Compile the tools (once) and the kernel.

# Log-in or su(1) as user `bld'.
#
su -l bld

# CVS prep (only once).
#
cat > $HOME/.cvsrc <<\EoF
# Default update flags. For -HEAD sources:
# update  -A -dP

# For -RELEASE/-STABLE sources:
# update -dP

rdiff   -pu
diff    -pu
cvs     -q
EoF

# Create new kernel config. file.
#
cd /usr/src
cp sys/arch/amd64/conf/GENERIC sys/arch/amd64/conf/MYKERNEL

# Edit and change MYKERNEL as needed.
#
vi sys/arch/amd64/conf/MYKERNEL

# To do a really clean build, remove both the `obj` and `tools` dirs.
# (the `tools` dir. generally doesn't need clearing, but, remove both just to be safe...)
# 
rm -rf /usr/obj/* /usr/tools/*

# Build tools (once), then kernel
#
./build.sh -j6 -N1 -M /usr/obj -T /usr/tools -U tools
./build.sh -j6 -N1 -M /usr/obj -T /usr/tools -U kernel=MYKERNEL

Change the -j (jobs) flags for your CPU. I have 4 CPUS (2 core, 2 thread) so I use 50% more (6) to make sure all of them are busy.

Install new kernel (as root now).

# Save GENERIC kernel (only once)
#
mv /netbsd /netbsd.GENERIC

install -m 555 /usr/obj/usr/src/sys/arch/amd64/compile/MYKERNEL/netbsd /netbsd.new

# Symlink `netbsd' to `netbsd.new` (once)
#
cd /
ln -sv netbsd.new netbsd

To go back to the old kernel, simply point the symlink back to netbsd.GENERIC. (Be mindful of this when doing an upgrade.)

To do a clean kernel rebuild, first do rm -rf /usr/obj/*. Leave /usr/tools alone--unless the compiler sources have changed: check the cvs update output for this.

BONUS:
If you've only made minor changes to the source, you can pass the -u flag to shorten the compile time quite a lot:

cd /usr/src
./build.sh -j6 -N1 -M /usr/obj -T /usr/tools -U -u kernel=MYKERNEL

rvp

rvp There are some additional checks of the CMOS NVRAM in NetBSD.

This check is very old, dating back to 4.4BSD at least, and should be removed. FreeBSD did it back in 2010. Linux doesn't perform this check either. I'll email the kernel folks after I've looked at it some more.

anarchosax

rvp An easy way to check if NetBSD works correctly with this RTC chip is to set the time back an hour or so in the BIOS, boot into NetBSD, and run (as root): ntpdate -b pool.ntp.org. Then reboot, go back into the BIOS and see if the time was set correctly.

The time was reset correctly.

anarchosax

rvp Compile the tools (once) and the kernel.

I ran into my first compile problem here: No idea what is going on. I downloaded the necessary files from -HEAD.