/src/amd64.amd64/sys/CANARY amd64
after updating sources to main-n276560-83dcc133c876, with a ports tree
at main-n703265-33b43edfb65d, I find:
...
--- i915_gem_mman.o ---
/common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.128_1/drivers/gpu/drm
CANARY amd64
>
> after updating sources to main-n276560-83dcc133c876, with a ports tree
> at main-n703265-33b43edfb65d, I find:
>
> ...
> --- i915_gem_mman.o ---
> /common/S4/obj/usr/src/amd64.amd64/sys/CANARY/common/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.128_1/drivers/gpu
commit a3a88ed appears to have removed the function(s) needed by drm
kmod to build and run :-(
Michael
On 4/19/25 09:06, David Wolfskill wrote:
Running:
FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445
main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025
r
After the ports update main-n684003-baeefdddb6ed:
commit baeefdddb6ed74573128353fac7d9b7805fa1a30
Author: Emmanuel Vadot
AuthorDate: Sat Oct 26 08:38:11 2024 +0200
Commit: Emmanuel Vadot
CommitDate: Sat Oct 26 09:10:02 2024 +0200
graphics/drm-61-kmod: Update to drm_v6.1.92_2
Or maybe the port just insists on building linuxkpi_video: --- video_kmod.o
---
cc: error: no such include directory:
'/usr/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.92_1/linuxkpi/dummy/include'
[-Werror,-Wmissing-include-dirs]
--- aperture.o ---
cc: error: no such include direct
Building either linuxkpi or linuxkpi_video from
https://github.com/freebsd/drm-kmod.git is not necessary if I want
functioning intel graphics, but the port version insists on building those
unnecessary things.
On Fri, Oct 25, 2024 at 6:10 PM Oleg Lelchuk wrote:
> With clang 19, I can bu
With clang 19, I can build i1915kms from
https://github.com/freebsd/drm-kmod.git and I won't encounter any issues.
However, with the port version of drm-61-kmod, I would still encounter an
error. I think this happens because the port wants to build stuff in the
linuxkpi_video directory, but
diff --git a/graphics/drm-61-kmod/Makefile b/graphics/drm-61-kmod/Makefile
index 6db2f255..596cdb20d13b 100644
--- a/graphics/drm-61-kmod/Makefile
+++ b/graphics/drm-61-kmod/Makefile
@@ -49,6 +49,8 @@ PLIST_SUB+= I915="@comment "
MAKE_ENV+= MAKEOBJDIRPREFIX=${W
generally, the
> simplest way to ensure that that is done is to augment /etc/src.conf
> with (e.g.):
>
> PORTS_MODULES+=graphics/drm-61-kmod
>
> which (again, generally) works a treat. :-)
>
> It even worked Just Fine yesterday (main-n273108-d1d839d0b593 ->
> main-n2731
BIT -DCONFIG_AS_MOVNTDQA -DCONFIG_COMPAT -DCONFIG_X86_64
-DCONFIG_DRM_AMD_DC_DCN -DCONFIG_DRM_AMD_DC_DCN3_0
-DCONFIG_DRM_AMD_DC_DCN3_01 -DCONFIG_DRM_AMD_DC_DCN3_02
-DCONFIG_DRM_AMD_DC_DCN3_1 -Werror -D_KERNEL -DKLD_MODULE -nostdinc
-I/usr/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.92_0/linuxkpi/
(e.g.):
PORTS_MODULES+=graphics/drm-61-kmod
which (again, generally) works a treat. :-)
It even worked Just Fine yesterday (main-n273108-d1d839d0b593 ->
main-n273133-419249c1cacc).
This morning, however, after updating sources to
main-n273188-1c83996beda7, running:
g1-48(15.0-C)[12] uname -aUK
FreeB
On Thu, 24 Oct 2024 at 14:26, Michael Butler
wrote:
>
> It seems there are some additional constraints about non-existent
> directories that now count as errors ..
I ran into this as well, in my work tree that has drm-kmod 6.6 as a
submodule. I think these include paths are just left
AMD_DC_DCN3_02 -DCONFIG_DRM_AMD_DC_DCN3_1 -Werror -D_KERNEL
>-DKLD_MODULE -nostdinc
>-I/usr/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.92_0/linuxkpi/gplv2/include
>
>-I/usr/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.92_0/linuxkpi/bsd/include
> -I/usr/src/sys/compat
I build{world,kernel} on one machine but install
everything from the target machine, with /usr/obj
and /usr/src from the build machine nfs mounted.
/etc/src.conf (on target and build machines) has
PORTS_MODULES+=graphics/drm-515-kmod to build
this port at the same time. This used to work at
least
On Tue, Nov 7, 2023 at 6:33 AM Cy Schubert
wrote:
> In message <2806934.tv9pz1c...@moonset.home>, "Oleg V. Nauman" writes:
> > I am observing kernel panic when entering multiuser mode after
> sucessful
> > system boot. It happens when I load CURRENT kernel wi
In message <2806934.tv9pz1c...@moonset.home>, "Oleg V. Nauman" writes:
> I am observing kernel panic when entering multiuser mode after sucessful
> system boot. It happens when I load CURRENT kernel with INVARIANTS and drm
> module loaded ( drm-515-kmod-5.15.118_1 in
I am observing kernel panic when entering multiuser mode after sucessful
system boot. It happens when I load CURRENT kernel with INVARIANTS and drm
module loaded ( drm-515-kmod-5.15.118_1 in particular ) . drm module and kenel
are in sync
FreeBSD moonset.home 15.0-CURRENT FreeBSD 15.0
, thanks for pointing that out
Mark. I'm able to load the i915kms module now.
next step is figuring out why the nvidia-drm module is causing a panic
(this is one of those funky intel + nvidia GPU laptops). but i get a
core on that, and having the intel gpu load allows me to run X at least.
t
On Mon, Aug 21, 2023 at 10:44:28AM -0700, Pete Wright wrote:
> hey there,
> i've got a kabylake laptop that i've been using with drm-kmod for several
> years without much hassle. after upgrading to a new CURRENT this weekend
> I've found that when loading either the
On 8/21/23 10:49, Poul-Henning Kamp wrote:
Pete Wright writes:
i've got a kabylake laptop that i've been using with drm-kmod for
several years without much hassle. after upgrading to a new CURRENT
this weekend I've found that when loading either the 510 or 515
On 8/21/23 10:53, Cy Schubert wrote:
In message <76275772-a9c3-ed59-5fb3-47a13d2a6...@nomadlogic.org>, Pete
Wright w
rites:
hey there,
i've got a kabylake laptop that i've been using with drm-kmod for
several years without much hassle. after upgrading to a new CURRENT
t
In message <76275772-a9c3-ed59-5fb3-47a13d2a6...@nomadlogic.org>, Pete
Wright w
rites:
> hey there,
> i've got a kabylake laptop that i've been using with drm-kmod for
> several years without much hassle. after upgrading to a new CURRENT
> this weekend I've f
Pete Wright writes:
> i've got a kabylake laptop that i've been using with drm-kmod for
> several years without much hassle. after upgrading to a new CURRENT
> this weekend I've found that when loading either the 510 or 515 drm-kmod
> kernel modules my syst
hey there,
i've got a kabylake laptop that i've been using with drm-kmod for
several years without much hassle. after upgrading to a new CURRENT
this weekend I've found that when loading either the 510 or 515 drm-kmod
kernel modules my system will hang.
unfortunately i a
x27;ve just used reinstall.sh to add a CURRENT boot environment to a 13.1
>>>> ZFS installation. Xorg doesn't load in CURRENT, presumably because the
>>>> drm-kmod doesn't work with 14. I tried to build drm-current-kmod from
>>>> ports but the buil
>>> installation. Xorg doesn't load in CURRENT, presumably because the drm-kmod
>>> doesn't work with 14. I tried to build drm-current-kmod from ports but the
>>> build errors out.
>>>
>>> I can send all the error messages and dmesg and su
On 14/10/2022 18:53, Pete Wright wrote:
On 10/14/22 10:14, Patrick Bowen wrote:
Hello all,
I've just used reinstall.sh to add a CURRENT boot environment to a
13.1 ZFS installation. Xorg doesn't load in CURRENT, presumably
because the drm-kmod doesn't work with 14. I trie
On 10/14/22 10:14, Patrick Bowen wrote:
Hello all,
I've just used reinstall.sh to add a CURRENT boot environment to a
13.1 ZFS installation. Xorg doesn't load in CURRENT, presumably
because the drm-kmod doesn't work with 14. I tried to build
drm-current-kmod from ports but t
Hello all,
I've just used reinstall.sh to add a CURRENT boot environment to a 13.1 ZFS
installation. Xorg doesn't load in CURRENT, presumably because the drm-kmod
doesn't work with 14. I tried to build drm-current-kmod from ports but the
build errors out.
I can send all the err
On 5/23/22 00:37, Emmanuel Vadot wrote:
On Sun, 22 May 2022 09:08:12 -0700
Pete Wright wrote:
hello,
i have a lenovo P43s laptop running current. i've noticed that since
graphics/drm-510-kmod became available hw.acpi.video.lcd0 ceases to
exist (which makes it impossible to adjust s
On Sun, 22 May 2022 09:08:12 -0700
Pete Wright wrote:
> hello,
> i have a lenovo P43s laptop running current. i've noticed that since
> graphics/drm-510-kmod became available hw.acpi.video.lcd0 ceases to
> exist (which makes it impossible to adjust screen brightness).
Il giorno dom 22 mag 2022 alle ore 18:08 Pete Wright
ha scritto:
> hello,
> i have a lenovo P43s laptop running current. i've noticed that since
> graphics/drm-510-kmod became available hw.acpi.video.lcd0 ceases to
> exist (which makes it impossible to adjust screen b
hello,
i have a lenovo P43s laptop running current. i've noticed that since
graphics/drm-510-kmod became available hw.acpi.video.lcd0 ceases to
exist (which makes it impossible to adjust screen brightness). i've
installed graphics/drm-54-kmod and things work as expected. previou
errors was (I stopped chasing them all for lack of
time) ..
--- amdgpu_cs.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.7.19_3/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c:1210:26:
error: variable 'priority' set but not used
[-Werror,-Wunused-but-set-variable]
builds too ..
> >>
> >> The first of many errors was (I stopped chasing them all for lack of
> >> time) ..
> >>
> >> --- amdgpu_cs.o ---
> >> /usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.7.19_3/drivers/gpu/drm/amd/amdgpu/amdgpu_
On 4/21/22 03:42, Emmanuel Vadot wrote:
Hello Michael,
On Wed, 20 Apr 2022 23:39:12 -0400
Michael Butler wrote:
Seems this new requirement breaks kmod builds too ..
The first of many errors was (I stopped chasing them all for lack of
time) ..
--- amdgpu_cs.o ---
/usr/ports/graphics/drm
/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.7.19_3/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c:1210:26:
error: variable 'priority' set but not used
[-Werror,-Wunused-but-set-variable]
enum drm_sched_priority priority;
^
1 error generated.
*** [amdgpu_cs.o]
Hello Michael,
On Wed, 20 Apr 2022 23:39:12 -0400
Michael Butler wrote:
> Seems this new requirement breaks kmod builds too ..
>
> The first of many errors was (I stopped chasing them all for lack of
> time) ..
>
> --- amdgpu_cs.o ---
> /usr/ports/graphics/drm-dev
Seems this new requirement breaks kmod builds too ..
The first of many errors was (I stopped chasing them all for lack of
time) ..
--- amdgpu_cs.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.7.19_3/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c:1210:26:
error: variable 'priority
working. It goes blank and the display goes into a
>>> power save mode, as soon as the amdgpu driver is loaded.
>>>
>>> The GPU (a Radeon R7 250E) is correctly detected as before, but there
>>> is an error message "drmn0: [drm] Cannot find any crtc or sizes
as soon as the amdgpu driver is loaded.
>>
>> The GPU (a Radeon R7 250E) is correctly detected as before, but there
>> is an error message "drmn0: [drm] Cannot find any crtc or sizes".
>>
>> I'm asking here and not on the ports list, since the AMDGPU d
and the amdgpu driver
> >>> my console stopped working. It goes blank and the display goes into a
> >>> power save mode, as soon as the amdgpu driver is loaded.
> >>>
> >>> The GPU (a Radeon R7 250E) is correctly detected as before, b
soon as the amdgpu driver is loaded.
The GPU (a Radeon R7 250E) is correctly detected as before, but there
is an error message "drmn0: [drm] Cannot find any crtc or sizes".
[...]
[drm] AMDGPU Display Connectors
[drm] Connector 0:
[drm] DP-1
[drm] HPD4
[drm] DDC: 0x1950 0x1950 0x1
dgpu driver is loaded.
>>
>> The GPU (a Radeon R7 250E) is correctly detected as before, but there
>> is an error message "drmn0: [drm] Cannot find any crtc or sizes".
>>
[...]
>> [drm] AMDGPU Display Connectors
>> [drm] Connector 0:
>> [drm]
before, but there
is an error message "drmn0: [drm] Cannot find any crtc or sizes".
I'm asking here and not on the ports list, since the AMDGPU driver has
not been updated for half a year. But to be sure that there is no mismatch
between kernel and user land, I have rebuilt all X11 ser
On Sat, 29 Jan 2022 15:33:34 -0800
David Wolfskill wrote:
> On Sun, Jan 30, 2022 at 07:25:49AM +0900, Tomoaki AOKI wrote:
> > ...
> > *I always prefer nvidia dGPU because of these dangerous span.
> > So I've forced to choose ThinkPad P series (without "s") which
> > usually can disable CPU-i
mode, as soon as the amdgpu driver is loaded.
>>
>> The GPU (a Radeon R7 250E) is correctly detected as before, but there
>> is an error message "drmn0: [drm] Cannot find any crtc or sizes".
[...]
> Are you sure your ports tree is up-to-date and graphics/drm-*-kmod
>
eon R7 250E) is correctly detected as before, but there
> is an error message "drmn0: [drm] Cannot find any crtc or sizes".
>
> I'm asking here and not on the ports list, since the AMDGPU driver has
> not been updated for half a year. But to be sure that there is no misma
drmn0: [drm] Cannot find any crtc or sizes".
I'm asking here and not on the ports list, since the AMDGPU driver has
not been updated for half a year. But to be sure that there is no mismatch
between kernel and user land, I have rebuilt all X11 server and library
ports.
There have been ch
> 20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and
> > > also
> > > updating port graphics/drm-fbsd13-kmod to
> > > drm-fbsd13-kmod-5.4.144.g20211013,
> > > graphics/libdrm to libdrm-2.4.107_1,1, Firefox (firefox-93.0_1,2) crashes
&g
On Fri, Oct 15, 2021 at 10:20:55PM +0200, Jan Beich wrote:
> FreeBSD User writes:
>
> > After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd:
> > Thu Oct 14
> > 20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and also
> >
FreeBSD User writes:
> After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd: Thu
> Oct 14
> 20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and also
> updating port
> graphics/drm-fbsd13-kmod to drm-fbsd13-kmod-5.4.144.g20211013,
>
After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd: Thu
Oct 14
20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and also
updating port
graphics/drm-fbsd13-kmod to drm-fbsd13-kmod-5.4.144.g20211013, graphics/libdrm
to
libdrm-2.4.107_1,1, Firefox (firefox
red *active_cred __unused, struct thread *td __unused)
+#endif
{
/* XXX need to define flags for st_mode */
On 10/11/21, Michael Butler via freebsd-current
wrote:
After the latest freebsd version bump in param.h, I tried to rebuild the
DRM modules. It failed with ..
--- dma-bu
dif
{
/* XXX need to define flags for st_mode */
On 10/11/21, Michael Butler via freebsd-current
wrote:
> After the latest freebsd version bump in param.h, I tried to rebuild the
> DRM modules. It failed with ..
>
> --- dma-buf.o ---
> /usr/ports/graphics/drm-devel-kmod/work/drm-
After the latest freebsd version bump in param.h, I tried to rebuild the
DRM modules. It failed with ..
--- dma-buf.o ---
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.5.19_4/drivers/dma-buf//dma-buf.c:121:1:
error: conflicting types for 'dma_buf_stat'
dma_buf_stat(struc
BSD 4.1 and has kept me out of trouble for many years. The PC
> that I use to update Current can build both world and kernel in under an
> hour with a clean object directory. Performing a 'git up ports' and
> rebuilding the drm module before building world is not a major time
>
ernel in under an
hour with a clean object directory. Performing a 'git up ports' and
rebuilding the drm module before building world is not a major time
consumer for me if I remember to do it first.
Thanks for the suggestions on some alternatives to my world building
exercise.
Tom
--
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF
On Jun 18, 2021, at 7:05 AM, Thomas Laus wrote:
>
> On 6/10/21 11:13 AM, Bakul Shah wrote:
>> This is what I did:
>>
>> git clone https://github.com/freebsd/drm-kmod
>> ln -s $PWD/drm-kmod /usr/local/sys/modules
>>
>> Now it gets compiled every time y
On 6/10/21 11:13 AM, Bakul Shah wrote:
> This is what I did:
>
> git clone https://github.com/freebsd/drm-kmod
> ln -s $PWD/drm-kmod /usr/local/sys/modules
>
> Now it gets compiled every time you do make buildkernel.
> If things break you can do a git pull in the drm-k
On 6/15/21 11:22 AM, Bakul Shah wrote:
On Jun 15, 2021, at 9:03 AM, John Baldwin wrote:
On 6/10/21 8:13 AM, Bakul Shah wrote:
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod
On Jun 15, 2021, at 9:03 AM, John Baldwin wrote:
>
> On 6/10/21 8:13 AM, Bakul Shah wrote:
>> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
>>> The drm-kmod module is the latest from the pkg server. It all
>>> worked this past Monday after the recent drm-kmod
On 6/10/21 8:13 AM, Bakul Shah wrote:
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod update.
This is what I did:
git clone https://github.com/freebsd/drm-kmod
ln -s $PWD/drm
On 10/06/2021 18:13, Bakul Shah wrote:
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod update.
This is what I did:
git clone https://github.com/freebsd/drm-kmod
ln -s $PWD/drm
On Jun 10, 2021, at 9:49 AM, Philipp Ost wrote:
>
> On 6/10/21 5:13 PM, Bakul Shah wrote:
>> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
>>> The drm-kmod module is the latest from the pkg server. It all
>>> worked this past Monday after the recent drm-kmod
n display since I was not able to generate a
> > crash dump to /var/crash on a zfs file system.
> >
> > I am rebuilding the GENERIC kernel since the crash was using the NODEBUG
> > version. This is 100 percent repeatable.
> >
> > Tom
> >
>
> Make s
On 6/10/21 5:13 PM, Bakul Shah wrote:
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod update.
This is what I did:
git clone https://github.com/freebsd/drm-kmod
ln -s $PWD/drm
Bakul Shah [ba...@iitbombay.org] wrote:
>
> This is what I did:
>
> git clone https://github.com/freebsd/drm-kmod
> ln -s $PWD/drm-kmod /usr/local/sys/modules
>
> Now it gets compiled every time you do make buildkernel.
> If things break you can do a git pull in the dr
Hans Petter Selasky [h...@selasky.org] wrote:
>
> When you use -current, you need to compile this pkg from the latest ports.
> I'm not sure if that happens automatically when you install the binary
> package.
>
I just built drm-current-kmod as a port and things work. Buil
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
> The drm-kmod module is the latest from the pkg server. It all
> worked this past Monday after the recent drm-kmod update.
This is what I did:
git clone https://github.com/freebsd/drm-kmod
ln -s $PWD/drm-kmod /usr/local/sys/modules
Now i
On 6/10/21 4:13 PM, Thomas Laus wrote:
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod update.
When you use -current, you need to compile this pkg from the latest
ports. I'm not sure if that happens automatically whe
Hans Petter Selasky [h...@selasky.org] wrote:
>
> Make sure you also re-build the drm-kmod module.
>
The drm-kmod module is the latest from the pkg server. It all
worked this past Monday after the recent drm-kmod update.
Things are good at n247230. I cleaned my source today and ch
rap number = 12
I hand copied the screen display since I was not able to generate a
crash dump to /var/crash on a zfs file system.
I am rebuilding the GENERIC kernel since the crash was using the NODEBUG
version. This is 100 percent repeatable.
Tom
Make sure you also re-build the drm-k
I updated my system this morning to main-n247260-dc318a4ffab June 9 2012
and the first boot after the kernel was loaded I received:
'fatal trap 12' fault virtual address = 0x0
fault code = supervisor write data, page not present
instruction pointer = 0x20:0x82fc3d1b
stack pointer = 0x28:0x
Thank god I forgot for a week or so to update the ports and rebuilt the older
version of drm-current-kmod, surprise, surprise: graphs' back again in
1367x1280, taking the intel driver without any harm (still flickering
sometimes but to be adjusted regularly in the compositor of plasma5-settin
rts and rebuilt the older
version of drm-current-kmod, surprise, surprise: graphs' back again in
1367x1280, taking the intel driver without any harm (still flickering
sometimes but to be adjusted regularly in the compositor of plasma5-settings).
it's this graphical card (quite old!)
On 2021-02-09 02:20, Emmanuel Vadot wrote:
> Alastair: Can you report a bug there :
> https://github.com/freebsd/drm-kmod/issues
https://github.com/freebsd/drm-kmod/issues/64
___
freebsd-current@freebsd.org mailing list
https://lists.freeb
On 3/9/21 9:31 AM, Alastair Hogge wrote:
On 2021-02-08 21:01, Hans Petter Selasky wrote:
On 2/8/21 1:53 PM, Alastair Hogge wrote:
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
Hi,
Maybe you could do a hac
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
> Hi,
>
> Maybe you could do a hack and edit the sysc
.o
rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS
===> drm-current-kmod (cleandir)
make[3]: don't know how to make cleandir. Stop
make[3]: stopped in /usr/local/sys/modules/drm-current-kmod
*** Error code 2
Stop.
make[2]: stopped in /usr/obj/mnt/hdd/src/amd64.amd64/sys/Z1
**
GRTAGS GSYMS GTAGS
===> drm-current-kmod (cleandir)
make[3]: don't know how to make cleandir. Stop
make[3]: stopped in /usr/local/sys/modules/drm-current-kmod
*** Error code 2
Stop.
make[2]: stopped in /usr/obj/mnt/hdd/src/amd64.amd64/sys/Z1
*** Error code 1
Stop.
make[1]: stopped in /mnt/hdd
nel:
===> zlib (cleandir)
rm -f export_syms machine x86 zlib.ko zlib.kld zcalloc.o zlib_mod.o
adler32.o compress.o crc32.o deflate.o inffast.o inflate.o inftrees.o
trees.o uncompr.o zutil.o offset.inc genoffset.o
rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS
===> drm-current-kmod
ne x86 zlib.ko zlib.kld zcalloc.o zlib_mod.o
adler32.o compress.o crc32.o deflate.o inffast.o inflate.o inftrees.o
trees.o uncompr.o zutil.o offset.inc genoffset.o
rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS
===> drm-current-kmod (cleandir)
make[3]: don't know how to make
This is a third panic after the update to 13-STABLE and corresponding
drm-fbsd13-kmod-5.4.92.g20210202 port.
My hardware is ThinkPad T440p with Intel Haswell iGPU. It happens once
in a week or two.
Unread portion of the kernel message buffer:
<4>WARN_ON(atomic_read(&new->bits) &
On Wed, Feb 10, 2021 at 11:15:58AM +, M&S - Krasznai András wrote:
2.)several applications (multitail just to mention one of them)
complain about missing ncurses libraries, e.g. libpanelw.so.5, etc.
which are not missing from the january-29 snapshot of FreeBSD
13-stable, that is after
Good morning!
Since the end of January I experience the following problems:
1.)I need to use the drm-kmod package to reach the normal screen
resolution. If this package is installed then I am not able to compile the
kernel after upgrading /usr/src, I get a "macro redefinition"
Sorry, please ignore previous reply, the modified sysctl is still
running,
the output earlier, was from the stock binary.
On 2021-02-09 14:25, Alastair Hogge wrote:
> On 2021-02-08 21:01, Hans Petter Selasky wrote:
>> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>>> Boot to multi-user; login (getty):
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
> Hi,
>
> Maybe you could do a hack and edit the sysc
On Mon, 08 Feb 2021 21:05:24 +0300
Greg V wrote:
>
>
> On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
> > On 2021-02-04 17:50, Emmanuel Vadot wrote:
> >
> > [...]
> >
> >> Only happens with drm when you do what ?
> >
> > Boot
On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
https
On 2/8/21 1:53 PM, Alastair Hogge wrote:
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
Hi,
Maybe you could do a hack and edit the sysctl source code:
1) print the sysctl before it is queried.
2) sleep 1 se
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
> Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
___
freebsd-curr
curve of available .ko
drivers.
Anyone have any practical guidance to which radeon.ko I want to load?
Not seeing valid Xorg with any of them and finding 640x480 tiresome.
In most cases, it should suffice to edit your rc.conf as described at
<https://www.freshports.org/graphics/drm-fbsd13
; radeon*_bin.ko modules for firmware. I don't have this
> card so this is just a guess (I am running 13.0-ALPHA3).
> Compile /usr/ports/graphics/drm-fbsd13-kmod at the same
> time as the kernel by adding
>
> PORTS_MODULES=graphics/drm-fbsd13-kmod
quot;
Replace amdgpu with radeonkms. It will in turn load various
radeon*_bin.ko modules for firmware. I don't have this
card so this is just a guess (I am running 13.0-ALPHA3).
Compile /usr/ports/graphics/drm-fbsd13-kmod at the same
time as the kernel by adding
PORTS_MODULES=graphics/drm
I have a Lenovo Edge 420 with the ATI/Radeon graphics card.
The "this .ko, that blob" thing is really confusing if you've been out
of the loop for a while, and with older hardwar (its 8+ year old
laptop) its not impossible its fallen off the curve of available .ko
drivers.
Anyone have any practic
> dofileread(2f5a58e8,4074ebc8,,ffff,0) at
> > > > dofileread+0x6d/frame 0x4074ebac
> > > > sys_read(247f4380,247f4618,343fb000,247f4380,40516068,...) at
> > > > sys_read+0x67/frame 0x4074ec00
> > > > syscall(4074ece8,3b,3b,3b,2d
rame 0x4074eb7c
> > > dofileread(2f5a58e8,4074ebc8,,,0) at
> > > dofileread+0x6d/frame 0x4074ebac
> > > sys_read(247f4380,247f4618,343fb000,247f4380,40516068,...) at
> > > sys_read+0x67/frame 0x4074ec00
> > > syscall(4074ece8,3b,3b,3b,2d
3b,3b,3b,2d130d1c,...) at syscall+0x17d/frame 0x4074ecdc
> > Xint0x80_syscall() at 0xffc033f9/frame 0x4074ecdc
> > --- syscall (881410048), eip = 0x2d086faf, esp = 0xfa1e339c, ebp =
> > 0xfa1e33c8 ---
> > KDB: enter: panic
>
> This is the crash.
> syscall(4074ece8,3b,3b,3b,2d130d1c,...) at syscall+0x17d/frame 0x4074ecdc
> Xint0x80_syscall() at 0xffc033f9/frame 0x4074ecdc
> --- syscall (881410048), eip = 0x2d086faf, esp = 0xfa1e339c, ebp = 0xfa1e33c8
> ---
> KDB: enter: panic
This is the crash.
The DRM mutex noise is just noise (b
1 - 100 of 664 matches
Mail list logo
