NetBSD 10.1, Radeon HD 5450 and Tomplay.

anarchosax

Well, a combination of picom and the radeon.conf file don't contribute to a positive change to the problem either:

Here is the radeon.conf file without picom:

Here are both of them together outside of Tomplay:

rvp

anarchosax however the cursor for following the music is also AWOL...

You can use wsfb on the DRMKMS provided framebuffer--that may be slightly faster than running it on efifb --ie by disabling DRKKMS in /boot.conf. How did you run your wsfb?

anarchosax Well, a combination of picom and the radeon.conf file don't contribute to a positive change to the problem either:

Did you try xcompmgr instead of picom?

And, I didn't realize that TomPlay was a website. Try running firefox like this:

env LIBGL_ALWAYS_SOFTWARE=true firefox &

anarchosax

rvp If these don't work, run the program with SW OpenGL rendering:
$ env LIBGL_ALWAYS_SOFTWARE=true blah ...

I am a bit unsure as to the syntax in context with Firefox, but it is also worth noting that the issue isn't limited to Firefox when running picom, despite my screenshot not being entirely representative of how bad the entire desktop can look (including Firefox tearing).

anarchosax

While overall quality of the desktop is better with the wfsb driver, the speed is too slow for the cursor across the notes to follow the audio track in Tomplay, which prevents that from being a viable alternative for a usable desktop setup - at least for me.

Thanks for the help.

anarchosax

I have installed the developer version, but from what I have seen so far, the issues are the same. I will take some time to go through the same process tomorrow.

anarchosax

Here is my home built computer with the NetBSD developer version running:
Without picom:

Here is with picom:

None of the problems with tearing, however the cursor for following the music is also AWOL...

anarchosax

OK, now I am getting tearing in the developer version as well. Interesting, as I was careful to use the same websites, so I had a baseline of expected behavior, regardless of the NetBSD version used…

anarchosax

rvp You can use wsfb on the DRMKMS provided framebuffer--that may be slightly faster than running it on efifb --ie by disabling DRKKMS in /boot.conf. How did you run your wsfb?

I edited /etc/X11/xorg.conf, so the driver read "wsfb".
When I try to edit /boot.conf, I am presented with an empty file. I don't think that can be correct...

xcompmgr has the same problems as with picom as far as tearing in Firefox and weird desktop background, However, there is a moving cursor that is visible in Tomplay, when using Firefox.

rvp

anarchosax I edited /etc/X11/xorg.conf, so the driver read "wsfb".

wsfb on top of DRMKMS, then--that's what we want...

anarchosax When I try to edit /boot.conf, I am presented with an empty file. I don't think that can be correct...

Is it in EFI\NetBSD\boot.cfg on the EFI ESP partition?

anarchosax xcompmgr has the same problems as with picom as far as tearing in Firefox and weird desktop background, However, there is a moving cursor that is visible in Tomplay, when using Firefox.

Is LIBGL_ALWAYS_SOFTWARE=true OK? Or, turning off RenderAccel in xorg.conf?

anarchosax

rvp Is it in EFI\NetBSD\boot.cfg on the EFI ESP partition?

I thought that my other post would be relevant for this... I have to use refind to boot into the system as the completed install does not include a bootx64.efi boot file...

Neither is there any root file structure other than dot files… This happens with both the release and developer versions of NetBSD at install, on this computer. Unfortunately, this is also the computer that I have, which is closest to running NetBSD on bare metal…

anarchosax

rvp Is LIBGL_ALWAYS_SOFTWARE=true OK? Or, turning off RenderAccel in xorg.conf?

There is nothing in the file, except radeon driver information (or wsfb if I edit it).

rvp

anarchosax I have to use refind to boot into the system as the completed install does not include a bootx64.efi boot file...

rEFInd doesn't read UFS filesystems (as far as know), so if it boots NetBSD, it should have found NetBSD's bootx64.efi bootloader file somewhere, right? Usually, /boot.cfg is on /--the root partition. One other place it is read from is EFI\NetBSD\boot.cfg on the ESP partition.

What does your GPT partition layout look like?

anarchosax There is nothing in the file, except radeon driver information (or wsfb if I edit it).

I've given the example to use above. Did you try experimenting with those settings?

anarchosax

rvp rEFInd doesn't read UFS filesystems (as far as know), so if it boots NetBSD, it should have found NetBSD's bootx64.efi bootloader file somewhere, right? Usually, /boot.cfg is on /--the root partition. One other place it is read from is EFI\NetBSD\boot.cfg on the ESP partition.

# find / -name bootx64.efi /usr/mdec/bootx64.efi

anarchosax

rvp What does your GPT partition layout look like?

Not sure how to get the info that you need.

# disklabel wd0
# /dev/rwd0:
type: ESDI
disk: wd0
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 3876021
total sectors: 3907029168
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

4 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 a: 3907029168         0     4.2BSD      0     0     0  # (Cyl.      0 - 3876020)
 d: 3907029168         0     unused      0     0        # (Cyl.      0 - 3876020)
disklabel: boot block size 0
disklabel: super block size

rvp

anarchosax #

$ find / -name bootx64.efi
/usr/mdec/bootx64.efi

/usr/mdec/*.efi are the NetBSD EFI bootloaders. These're what sysinst copies into the EFI ESP partition at install-time.

anarchosax

OK, I did what I know best.

anarchosax

rvp /etc/X11/xorg.conf.d/radeon.conf

OK, I have now got this working. So far, this is doable, although the driver is somewhat unstable, with blinking in and out of the browser, as well as tearing when scrolling or hovering the mouse cursor over some text or a menu item. The current situation functions well enough that I feel that I can use this for a period without having to immediately give up in frustration. Tomplay is working as well, with the above caveats. Playback is fine so far, as is the cursor following the music.

And after I just wrote the above, I am starting to get the weird colors and tearing in the browser again, and the cursor has disappeared in Tomplay.

rvp

anarchosax And after I just wrote the above, I am starting to get the weird colors and tearing in the browser again, and the cursor has disappeared in Tomplay.

Even with Option "RenderAccel" "off" uncommented?
(Apparently, there's a regression in -10 with this card.)

BTW, the board has a handy post-formatting guide here.

anarchosax

rvp Even with Option "RenderAccel" "off" uncommented?
(Apparently, there's a regression in -10 with this card.)

There are some differences between the configuration file having the commented section commented and uncommented. My last post was in relation to your original file suggestion - as a baseline. With the section uncommented, there are fewer problems with color, although Nightly still has issues with red as in my last picture (and to a varying degree on websites). The main issue that I experience, is that Tomplay has a fair amount of tearing issues, but most importantly, the cursor no longer follows the music exactly, which makes it unusable. There are still flashing color anomalies that appear (dark squares flashing around Nightly), tearing as well as juxtaposition of text when the mouse cursor is over an element.

All in all, definitely not better with the uncommented section, just slightly different symptoms.

anarchosax

rvp (Apparently, there's a regression in -10 with this card.)

Any timeline for getting this sorted out?

rvp

anarchosax Any timeline for getting this sorted out?

Dunno, Guv'--may have to wait until the one person who takes care of this stuff gets a round tuit.

In the mean time, can you try the modesetting driver? (not sure if we've tried it; it's what's used on all the other Unixes):

# Depends on kernel DRM
#
Section "Device"
    Identifier  "Card0"
    Driver      "modesetting"
    # Option      "SWcursor" "on"
    # Option      "AccelMethod" "none"
EndSection

Uncomment SWcursor and/or AccelMethod if there's no visible improvement.