From Newsgroup: muc.lists.freebsd.ports

Hi.

After upgrading graphics/drm-61-kmod to commit 09f1e5c29432d77a992f5f554f48986ef8674e9c, X11 cannot start
at least the combination with:

graphics/drm-61-kmod
graphics/nvidia-drm-61-kmod[-devel]
nvidia-driver[-devel]

Currently, nvidia drivers of master and -devel is at the same version,
as NFB and Beta is older than Production branch of driver.

(Note that I'm currently testing 580.82.09, but as it seems to be
a minor bugfix release, I think in-tree 580.82.07 should be the same.)

Rebuilding x11-servers/xorg-server didn't help.

Reverting back to commit 0ec771a40199b9fc4fd671c5c64360ad6d4328fe
and rebuilding the above fixed the issue.


The actual error found in /ver/log/Xorg.0.log is like below.

[ 138.316] (II) Initializing extension DRI2
[ 138.316] (EE) modeset(0): Failed to create pixmap
[ 138.316] (EE)
Fatal server error:
[ 138.316] (EE) failed to create screen resources(EE)

Logs prior to the error seems to be as usual.

I'll file a bug on bugzilla later.

Regards.
--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

Hi,

Does this problem also affect /usr/ports/x11/nvidia-driver-470?
I've never directly built drm-*-kmod, but this port gets
rebuilt every time a source (buildkernel etc) upgrade is run.
The ports tree is latest, os is

% freebsd-version -kru
14.3-STABLE
14.3-STABLE
14.3-STABLE

stable/14-n272369
--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 16 Sep 2025, Tomoaki AOKI wrote:

Hi.

After upgrading graphics/drm-61-kmod to commit 09f1e5c29432d77a992f5f554f48986ef8674e9c, X11 cannot start
at least the combination with:

graphics/drm-61-kmod
graphics/nvidia-drm-61-kmod[-devel]
nvidia-driver[-devel]

Currently, nvidia drivers of master and -devel is at the same version,
as NFB and Beta is older than Production branch of driver.

(Note that I'm currently testing 580.82.09, but as it seems to be
a minor bugfix release, I think in-tree 580.82.07 should be the same.)

Rebuilding x11-servers/xorg-server didn't help.

Reverting back to commit 0ec771a40199b9fc4fd671c5c64360ad6d4328fe
and rebuilding the above fixed the issue.

Which FreeBSD version are you exactly using? The only difference is
that instead of using special FreeBSD native calls for PCI info we use
LinuxKPI as in the original (to avoid conflicts).

The one thing I could think of is that something is not set correctly
in LinuxKPI but when I checked I hadn't noticed anything.

But if this fails I would have expected it to fail queally for Intel
and AMD.

What is consuming the DRM_IOCTL_GET_PCIINFO ioctl anyway? I checked xorg-server and mesa-dri and mesa-libs and couldn't find any use.

The actual error found in /ver/log/Xorg.0.log is like below.

[ 138.316] (II) Initializing extension DRI2
[ 138.316] (EE) modeset(0): Failed to create pixmap
[ 138.316] (EE)
Fatal server error:
[ 138.316] (EE) failed to create screen resources(EE)

Logs prior to the error seems to be as usual.

I'll file a bug on bugzilla later.

Regards.

--
Bjoern A. Zeeb r15:7


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 16 Sep 2025 15:37:27 +0100
void <void@f-m.fm> wrote:

Hi,

Does this problem also affect /usr/ports/x11/nvidia-driver-470?
I've never directly built drm-*-kmod, but this port gets
rebuilt every time a source (buildkernel etc) upgrade is run.
The ports tree is latest, os is

% freebsd-version -kru
14.3-STABLE
14.3-STABLE
14.3-STABLE

stable/14-n272369
--

Not tested, but unlikely.

graphics/nvidia-drm-*-kmod[-devel] don't support any legacy veesions
including 470. And x11/nvidia-driver[-304|-340|-390|-470|-devel]
themselves don't directly interact with any of graphics/drm-*-kmod.

Regards.
--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 16 Sep 2025 14:37:57 +0000 (UTC)
"Bjoern A. Zeeb" <bz@FreeBSD.org> wrote:

On Tue, 16 Sep 2025, Tomoaki AOKI wrote:

Hi.

After upgrading graphics/drm-61-kmod to commit 09f1e5c29432d77a992f5f554f48986ef8674e9c, X11 cannot start
at least the combination with:

graphics/drm-61-kmod
graphics/nvidia-drm-61-kmod[-devel]
nvidia-driver[-devel]

Currently, nvidia drivers of master and -devel is at the same version,
as NFB and Beta is older than Production branch of driver.

(Note that I'm currently testing 580.82.09, but as it seems to be
a minor bugfix release, I think in-tree 580.82.07 should be the same.)

Rebuilding x11-servers/xorg-server didn't help.

Reverting back to commit 0ec771a40199b9fc4fd671c5c64360ad6d4328fe
and rebuilding the above fixed the issue.

Which FreeBSD version are you exactly using? The only difference is
that instead of using special FreeBSD native calls for PCI info we use LinuxKPI as in the original (to avoid conflicts).

As noted on Bug 289647, stable/15, amd64 at commit base 1aad58b919d3.

The one thing I could think of is that something is not set correctly
in LinuxKPI but when I checked I hadn't noticed anything.

But if this fails I would have expected it to fail queally for Intel
and AMD.

What is consuming the DRM_IOCTL_GET_PCIINFO ioctl anyway? I checked xorg-server and mesa-dri and mesa-libs and couldn't find any use.

To look for nvidia side of codes, tried `fgrep -r -n
"DRM_IOCTL_GET_PCIINFO" /usr/ports/graphics/nvidia-drm-61-kmod-devel/work/NVIDIA-FreeBSD-x86_64-580.82.09/`

after both `make extract` and `make`, both showed nothing.

So would be in codes from drm-61-kmod only.


Regards.

The actual error found in /ver/log/Xorg.0.log is like below.

[ 138.316] (II) Initializing extension DRI2
[ 138.316] (EE) modeset(0): Failed to create pixmap
[ 138.316] (EE)
Fatal server error:
[ 138.316] (EE) failed to create screen resources(EE)

Logs prior to the error seems to be as usual.

I'll file a bug on bugzilla later.

Regards.

--
Bjoern A. Zeeb r15:7

--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, Sep 16, 2025 at 11:43:14PM +0900, Tomoaki AOKI wrote:

Not tested, but unlikely.

graphics/nvidia-drm-*-kmod[-devel] don't support any legacy veesions >including 470. And x11/nvidia-driver[-304|-340|-390|-470|-devel]
themselves don't directly interact with any of graphics/drm-*-kmod.

thanks
--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

--000000000000e471de063eec8ba7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello.

What's happening ? My system became totally not usable. The nvidia package
does not work because it installs a wrong nvidia.co module,the port is not
able to compile because it gives an error message...The old version of the nvidia-driver has been removed. Not good. I think that's not a good idea to remove the old nvidia-driver. It worked for me. I see a frenzy in getting
rid of obsolete software.


On Tue, Sep 16, 2025 at 4:55=E2=80=AFPM Tomoaki AOKI <junchoon@dec.sakura.n= e.jp>
wrote:

On Tue, 16 Sep 2025 14:37:57 +0000 (UTC)
"Bjoern A. Zeeb" <bz@FreeBSD.org> wrote:

On Tue, 16 Sep 2025, Tomoaki AOKI wrote:

Hi.

After upgrading graphics/drm-61-kmod to commit 09f1e5c29432d77a992f5f554f48986ef8674e9c, X11 cannot start
at least the combination with:

graphics/drm-61-kmod
graphics/nvidia-drm-61-kmod[-devel]
nvidia-driver[-devel]

Currently, nvidia drivers of master and -devel is at the same version=

,

as NFB and Beta is older than Production branch of driver.

(Note that I'm currently testing 580.82.09, but as it seems to be
a minor bugfix release, I think in-tree 580.82.07 should be the same.=

)

Rebuilding x11-servers/xorg-server didn't help.

Reverting back to commit 0ec771a40199b9fc4fd671c5c64360ad6d4328fe
and rebuilding the above fixed the issue.

Which FreeBSD version are you exactly using? The only difference is
that instead of using special FreeBSD native calls for PCI info we use LinuxKPI as in the original (to avoid conflicts).

As noted on Bug 289647, stable/15, amd64 at commit base 1aad58b919d3.

The one thing I could think of is that something is not set correctly
in LinuxKPI but when I checked I hadn't noticed anything.

But if this fails I would have expected it to fail queally for Intel
and AMD.

What is consuming the DRM_IOCTL_GET_PCIINFO ioctl anyway? I checked xorg-server and mesa-dri and mesa-libs and couldn't find any use.

To look for nvidia side of codes, tried `fgrep -r -n
"DRM_IOCTL_GET_PCIINFO" /usr/ports/graphics/nvidia-drm-61-kmod-devel/work/NVIDIA-FreeBSD-x86_64-5=

80.82.09/`

after both `make extract` and `make`, both showed nothing.

So would be in codes from drm-61-kmod only.

Regards.

The actual error found in /ver/log/Xorg.0.log is like below.

[ 138.316] (II) Initializing extension DRI2
[ 138.316] (EE) modeset(0): Failed to create pixmap
[ 138.316] (EE)
Fatal server error:
[ 138.316] (EE) failed to create screen resources(EE)

Logs prior to the error seems to be as usual.

I'll file a bug on bugzilla later.

Regards.

--
Bjoern A. Zeeb r15:=

7

--
Tomoaki AOKI <junchoon@dec.sakura.ne.jp>

--=20
Mario.

--000000000000e471de063eec8ba7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello.</div><div><br></div><div>What&#39;s happening =
? My system became totally not usable. The nvidia package does not work bec= ause it installs a wrong <a href=3D"http://nvidia.co">nvidia.co</a> module,= the port is not able to compile because it gives an error message...The=C2= =A0old version of the nvidia-driver has been removed. Not good. I think tha= t&#39;s not a good idea to remove the old nvidia-driver. It worked for me. =
I see a=C2=A0<span class=3D"gmail-HwtZe" lang=3D"en"><span class=3D"gmail-j= CAhz gmail-ChMk0b"><span class=3D"gmail-ryNqvb">frenzy in getting rid of ob= solete software.</span></span></span><div class=3D"gmail-lRu31" dir=3D"ltr"= ><div class=3D"gmail-OvtS8d"><span></span><span class=3D"gmail-LdhArd"></sp= an><span></span></div><div class=3D"gmail-NQSJo"><br></div></div></div></di= v><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" cla= ss=3D"gmail_attr">On Tue, Sep 16, 2025 at 4:55=E2=80=AFPM Tomoaki AOKI &lt;=
<a href=3D"mailto:junchoon@dec.sakura.ne.jp">junchoon@dec.sakura.ne.jp</a>&= gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tu=
e, 16 Sep 2025 14:37:57 +0000 (UTC)<br>
&quot;Bjoern A. Zeeb&quot; &lt;bz@FreeBSD.org&gt; wrote:<br>

&gt; On Tue, 16 Sep 2025, Tomoaki AOKI wrote:<br>
&gt; <br>
&gt; &gt; Hi.<br>
&gt; &gt;<br>
&gt; &gt; After upgrading graphics/drm-61-kmod to commit<br>
&gt; &gt; 09f1e5c29432d77a992f5f554f48986ef8674e9c, X11 cannot start<br>
&gt; &gt; at least the combination with:<br>
&gt; &gt;<br>
&gt; &gt; graphics/drm-61-kmod<br>
&gt; &gt; graphics/nvidia-drm-61-kmod[-devel]<br>
&gt; &gt; nvidia-driver[-devel]<br>
&gt; &gt;<br>
&gt; &gt; Currently, nvidia drivers of master and -devel is at the same ver= sion,<br>
&gt; &gt; as NFB and Beta is older than Production branch of driver.<br>
&gt; &gt;<br>
&gt; &gt; (Note that I&#39;m currently testing 580.82.09, but as it seems t=
o be<br>
&gt; &gt; a minor bugfix release, I think in-tree 580.82.07 should be the s= ame.)<br>
&gt; &gt;<br>
&gt; &gt; Rebuilding x11-servers/xorg-server didn&#39;t help.<br>
&gt; &gt;<br>
&gt; &gt; Reverting back to commit 0ec771a40199b9fc4fd671c5c64360ad6d4328fe=

&gt; &gt; and rebuilding the above fixed the issue.<br>
&gt; <br>
&gt; Which FreeBSD version are you exactly using?=C2=A0 The only difference=
is<br>
&gt; that instead of using special FreeBSD native calls for PCI info we use=

&gt; LinuxKPI as in the original (to avoid conflicts).<br>

As noted on Bug 289647, stable/15, amd64 at commit base 1aad58b919d3.<br>


&gt; The one thing I could think of is that something is not set correctly<=

&gt; in LinuxKPI but when I checked I hadn&#39;t noticed anything.<br>
&gt; <br>
&gt; But if this fails I would have expected it to fail queally for Intel<b=

&gt; and AMD.<br>
&gt; <br>
&gt; What is consuming the DRM_IOCTL_GET_PCIINFO ioctl anyway?=C2=A0 I chec= ked<br>
&gt; xorg-server and mesa-dri and mesa-libs and couldn&#39;t find any use.<=


To look for nvidia side of codes, tried `fgrep -r -n<br> &quot;DRM_IOCTL_GET_PCIINFO&quot; /usr/ports/graphics/nvidia-drm-61-kmod-de= vel/work/NVIDIA-FreeBSD-x86_64-580.82.09/`<br>

after both `make extract` and `make`, both showed nothing.<br>

So would be in codes from drm-61-kmod only.<br>


Regards.<br>


&gt; &gt; The actual error found in /ver/log/Xorg.0.log is like below.<br>
&gt; &gt;<br>
&gt; &gt; [=C2=A0 =C2=A0138.316] (II) Initializing extension DRI2<br>
&gt; &gt; [=C2=A0 =C2=A0138.316] (EE) modeset(0): Failed to create pixmap<b=

&gt; &gt; [=C2=A0 =C2=A0138.316] (EE)<br>
&gt; &gt; Fatal server error:<br>
&gt; &gt; [=C2=A0 =C2=A0138.316] (EE) failed to create screen resources(EE)=

&gt; &gt;<br>
&gt; &gt; Logs prior to the error seems to be as usual.<br>
&gt; &gt;<br>
&gt; &gt; I&#39;ll file a bug on bugzilla later.<br>
&gt; &gt;<br>
&gt; &gt; Regards.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; <br>
&gt; -- <br>
&gt; Bjoern A. Zeeb=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15:7<br>


-- <br>
Tomoaki AOKI=C2=A0 =C2=A0 &lt;<a href=3D"mailto:junchoon@dec.sakura.ne.jp" = target=3D"_blank">junchoon@dec.sakura.ne.jp</a>&gt;<br>

</blockquote></div><div><br clear=3D"all"></div><br><span class=3D"gmail_si= gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Ma= rio.<br></div>

--000000000000e471de063eec8ba7--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 16 Sep 2025, Tomoaki AOKI wrote:

As noted on Bug 289647, stable/15, amd64 at commit base 1aad58b919d3.

I followed up there. I am still trying to understand the xorg-server/drm-lib/mesa code how it comes together with this and with
your error message.

I need to run but I'll keep looking tonight.
--
Bjoern A. Zeeb r15:7


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Tue, 16 Sep 2025, Bjoern A. Zeeb wrote:

On Tue, 16 Sep 2025, Tomoaki AOKI wrote:

As noted on Bug 289647, stable/15, amd64 at commit base 1aad58b919d3.

I followed up there. I am still trying to understand the xorg-server/drm-lib/mesa code how it comes together with this and with
your error message.

I need to run but I'll keep looking tonight.

For everyone, the PR has a patch until the port is updated: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647

patch:
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=263910

/bz
--
Bjoern A. Zeeb r15:7


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2