tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: [VGA connector] NetBSD 10.0 BETA kernel testing: framebuffer
Le Sun, Jan 22, 2023 at 02:56:47PM +0100, tlaronde%polynum.com@localhost a écrit :
> [Please feel free to redirect me to another list if this is not the
> correct one for kernel beta testing]
>
> Context: I'm testing NetBSD 10.0 BETA on an isolated node (not
> production). Only kernel and modules (not userland); and kernel is not
> GENERIC but a special config one matching the previous 9.2 config
> running on the node.
>
> No problem so far. As a user (and as advertised), I had simply to use
> audiocfg(1) to set the new correct default for audio in order to have
> sound back where I used to expect it.
>
> The main difference is about the framebuffer: previous kernel version
> picked the correct mode. NetBSD 10.0 does not and use "entry level"
> mode 640x480x67, resulting streched fat big characters; message:
>
> no data for est. mode 640x480x67
>
> while in dmesg the framebuffer has the same dimensions as with the
> 9.2 kernel:
>
> 9.2:
> -radeondrmkmsfb0: framebuffer at 0xffffb000aec89000, size 1600x900, depth 32, stride 6400
>
> 10.0:
> +radeondrmkmsfb0: framebuffer at 0xe034d000, size 1600x900, depth 32, stride 6400
>
> I have not updated the book blocks. Is the 10.0 kernel expecting to have
> hints about the modes from the bootloader i.e. a new install would
> have updated the boot blocks and I would not have seen this?
I wondered if the problem was linked to the connector between the
graphics card and the monitor.
My monitor is an "old" one with VGA and DVI connectors (DVI is DVI-D not
DVI-I). I'm using a VGA cable.
Since I don't have a DVI cable, I tested connecting a small monitor
(originally for a Raspberry) for which I have a cable with a DVI connector for the
graphics card and a HDMI connector for the monitor.
With this only monitor, nothing is displayed but what is "interesing" is
that if I connect both monitors on the same graphics card, one with the
VGA the other with the DVI (on card)--HDMI (on monitor), the kernel gets
the informations from the DVI connected monitor, and displays
"correctly" (for the size of the fonts)... on the VGA connected monitor.
And I have not the message about the mode not found.
If I try to connect the DVI-D (on the old monitor) to the HDMI (on
card), the monitor works, but the problem is the same as with the VGA
(but it is not that surprising since it is DVI-D with a cable
translating DVI to HDMI; but DVI-D is not the same as DVI-I and
something is probably lost in translation).
So it has something to do with the connection, apparently the VGA one
(and DVI-D).
For VGA, there was a change about the EDID (an enhanced version E-EDID
been designed in 2007). So was there a change in the VGA related code,
expecting E-EDID while old monitors "speak" only EDID (for VGA
connection)?
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Home |
Main Index |
Thread Index |
Old Index