Re: Installing drm-current-kmod from ports

[Niclas Zeising]

On 2019-08-18 04:08, Clay Daniels Jr. wrote:

I've been reading the HEADSUP: drm-current-kmod thread, actually several
times, and since my pkg install of plain vanilla drm-kmod was a dud after
working for several weekly installs of 13.0-Current, it's clear I probably
need to make install from the ports, which I have installed, as well as the
sources. I must confess I have done pkg install xorg, but this can be
corrected if it needs to be make install xorg from ports.

Is simply navigating to /usr/ports/graphics/drm-current-kmod and running
"make install clean" the best next step, or am I missing something else?

I want to confess my relative ignorance, and thank Graham Perrin & Pete
Wright for their help on a previous post, 13.0 Current - r350702 exposed an
Xorg failure. I've moved on to this weeks r351067 and no longer think my
problem is with Xorg, but with my install of drm-*-kmod.

I'm willing to wipe my install & start fresh if need be. I sure like
gParted. It erases a lot of sins.



Hi!
drm-kmod should pull in drm-current-kmod if you install it on FreeBSD 
CURRENT.  The feature to have sources installed with the port is fairly 
recent, it could be that the port hasn't caught up yet.  You can check 
in /usr/local/sys/modules/drm-current-kmod if they are installed.  If 
they are, it should be enough to run a buildkernel and installkernel to 
get the updated modules.


Otherwise, it's completely safe to install drm-current-kmod (and 
gpu-firmware-kmod, which is a dependency) from ports, even if the rest 
of the system is installed using packages.


Regards
--
Niclas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installing drm-current-kmod from ports

[Graham Perrin]

On 18/08/2019 03:08, Clay Daniels Jr. wrote:

… am I missing something else? …


Re: 
 



If you haven't already done so, it's probably recommended to install 
xf86-video-ati.


What model is the HP?

Will you use a desktop environment?

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installing drm-current-kmod from ports

[Clay Daniels Jr.]

Graham, thanks for the reply. Since my original post on this thread last
night, I went through the make install clean of the drm-current-kmod port.
It didn't take too long, probably half an hour or so. It gave an exit
message to put a line in /etc/rc.donf: kld_list="amdgpu" , which I did,
rebooted and the same problem. I tried the complete path:
kls_list="/boot/modules/amdgpu.ko"  but the same problem. I know that it's
loading the amdgpu kmodule because when it is booting up and gets to the
part of discovery of my Radeon/Kabini video it suddenly shows a "wide fuzzy
line", right there in the console. The console message reads like I may
have permissions issues, but that can't be true, because if I specify the
older radeokms.ko it tries to load it and then hangs. So i have the right
module.

But what you just said about installing the xf86-video-ati sounds like good
advice. The console error message is in /var/log/Xorg.0.~ and complains
about being unable to load an "ati" module. I bet this might do it. My
rather old computer is an HP Pavilion 23 all-in-one built & bought in 2014
with an AMD E2-3000 cpu with Radeon HD video. It's all clamped in a plastic
frame and I've never looked inside myself. I intend to buy buy a new
computer, and it will be in a tower case that you can easily get into,
maybe with a clear glass or plastic side. I like to see the lights blink.
And I have my heart set on a Threadripper...

OK, I'm going to log off, re-boot into my FreeBSD partition, and try to
install xf86-video-ati, probably from the ports, under graphics I guess.

Thanks a lot,
Clay

On Sun, Aug 18, 2019 at 3:16 PM Graham Perrin 
wrote:

> On 18/08/2019 03:08, Clay Daniels Jr. wrote:
> > … am I missing something else? …
>
> Re:
> <
> https://lists.freebsd.org/pipermail/freebsd-current/2019-August/074074.html>
>
>
>
> If you haven't already done so, it's probably recommended to install
> xf86-video-ati.
>
> What model is the HP?
>
> Will you use a desktop environment?
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installing drm-current-kmod from ports

[Clay Daniels Jr.]

OK, making progress as it gives a new result:
Starts to load Xorg server
~
[drm] radeon kernel modesetting enabled
drmn0:  on vgapci0
panic: make_dev_alias_v: bad si_name
 (error=17, si_name=dri/renderD128)
cpuid=2
time=~
KDB: stackbacktrace
~
>db  [HALTS HERE - interactive mode]
 I entered help, it gave me a menu, I did a reboot there...

The fact I get a new result is an improvement. And I still see that "funny
fuzzy thick line" during bootup, which to me is a good sign too.

Like I say, I'm willing to back up and start again. I'm not going to give
up on this. It has worked for manyl weeks of 13.0-Current up until r350702.
I'm hooked on FreeBSD.

I was intending to load the LXDE desktop. I kind of like it as it's minimal
and I get to pick my own apps. But I have tried Gnome, KDE, & Xfce too. I
will probably try several more desktops. But if it doesn't work with the
basic Xorg page with the three Xterms & a clock, it will not load a fancy
desktop.

Thanks so much for your help, Graham

Clay

On Sun, Aug 18, 2019 at 3:59 PM Clay Daniels Jr. 
wrote:

> Graham, thanks for the reply. Since my original post on this thread last
> night, I went through the make install clean of the drm-current-kmod port.
> It didn't take too long, probably half an hour or so. It gave an exit
> message to put a line in /etc/rc.donf: kld_list="amdgpu" , which I did,
> rebooted and the same problem. I tried the complete path:
> kls_list="/boot/modules/amdgpu.ko"  but the same problem. I know that it's
> loading the amdgpu kmodule because when it is booting up and gets to the
> part of discovery of my Radeon/Kabini video it suddenly shows a "wide fuzzy
> line", right there in the console. The console message reads like I may
> have permissions issues, but that can't be true, because if I specify the
> older radeokms.ko it tries to load it and then hangs. So i have the right
> module.
>
> But what you just said about installing the xf86-video-ati sounds like
> good advice. The console error message is in /var/log/Xorg.0.~ and
> complains about being unable to load an "ati" module. I bet this might do
> it. My rather old computer is an HP Pavilion 23 all-in-one built & bought
> in 2014 with an AMD E2-3000 cpu with Radeon HD video. It's all clamped in a
> plastic frame and I've never looked inside myself. I intend to buy buy a
> new computer, and it will be in a tower case that you can easily get into,
> maybe with a clear glass or plastic side. I like to see the lights blink.
> And I have my heart set on a Threadripper...
>
> OK, I'm going to log off, re-boot into my FreeBSD partition, and try to
> install xf86-video-ati, probably from the ports, under graphics I guess.
>
> Thanks a lot,
> Clay
>
> On Sun, Aug 18, 2019 at 3:16 PM Graham Perrin 
> wrote:
>
>> On 18/08/2019 03:08, Clay Daniels Jr. wrote:
>> > … am I missing something else? …
>>
>> Re:
>> <
>> https://lists.freebsd.org/pipermail/freebsd-current/2019-August/074074.html>
>>
>>
>>
>> If you haven't already done so, it's probably recommended to install
>> xf86-video-ati.
>>
>> What model is the HP?
>>
>> Will you use a desktop environment?
>>
>>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"