Re: ATI video problem - slow desktop - 100% cpu load [semi-solved]

[Carl Johnson]

Vincent Stemen  writes:

> You must load radeonkms.ko after the system is fully booted.
>
> # kldload radeonkms
>
> That automatically loads the other 3 modules and initializes the console where
> the console text goes into higher resolution mode.  Then X and the desktop
> environments work and seem to be fully functional, including transparency, 
> etc.
>
> So I can either put it in /etc/rc.local, to be run at boot time, or put it in
> an X startup script wrapper.  Note that it must be run prior to startx because
> it must be loaded before launching the X server.  So it cannot be put in
> ~/.xinitrc.

Have you tried loading it with kld_list in /etc/rc.conf?  Those get
loaded during boot, but it might be late enough to work.  That would be
automated, so it might be a little more convenient.
-- 
Carl Johnsonca...@peak.org

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

Re: ATI video problem - slow desktop - 100% cpu load [semi-solved]

[Vincent Stemen]

On Wed, Jun 20, 2018 at 05:13:17PM -0400, Mark Saad wrote:
> Vincent
>  I am running 11.2-PRERELEASE with a Cedar PRO [Radeon HD 5450/6350]
> and I dont have any issues like that
> 
> here is what I do to get it working for me; and I have used more or
> less the same setup since 10.3-RELEASE
> 
> In my loader.conf I have
> 
> radeonkms_load="YES"
> radeonkmsfw_CEDAR_pfp_load="YES"
> radeonkmsfw_CEDAR_rlc_load="YES"
> radeonkmsfw_CEDAR_me_load="YES"
> 
> I use a static xorg.conf as well  In there I have the following bits
> 
> 
> Also if the redeon driver is not working for you try scfb . It works
> better the vesa it some cases

Thank you very much Mark!  The scfb driver works!  I didn't know what the scfb
driver was for or that it will use the radeon kernel modules.  This seems to
confirm that the problem lies in the radeon X server driver that's in the
xf86-video-ati package.

I tagged this as semi-solved in the subject because it solves our immediate
problem and gets us working, but it seems to be a work around to fixing the ati
driver problem.  Unless FreeBSD is going in the direction of using the scfb
driver and not needing the ati driver at all, but I have found no documentation
indicating this.  The man page for scfb says it is a non-accelerated driver.
So far as I can tell, that is not necessarily the case.  It is using the radeon
kernel modules and I seem to have full desktop features, resolution, and
performance, including transparencies.  I even tested moving windows around
that are playing high def videos. 

I am curious how you discovered the use of this driver for ATI cards since I
have not found docs that say anything about it.

BTW, I did test with all three ATI Radeon card models that I mentioned,
and it works fine with all of them.

Anyway, there are some caveats to getting it working.  Since I spent the
last few days working on this issue, I am posting my notes below to help
others who might be experiencing the same issue.

Solution to getting ATI Radeon graphics cards working
=
Use the "scfb" driver from the xf86-video-scfb package rather than the "radeon"
driver from the xf86-video-ati package.

/etc/X11/xorg.conf
Section "Device"
...
Driver  "scfb"
...
EndSection

This driver also requires the radeon kernel modules to be loaded, but does not
automatically load them like the radeon driver does.

I tried loading them in /boot/loader.conf,

/boot/loader.conf
radeonkms_load = yes
radeonkmsfw_RS780_pfp_load = yes
radeonkmsfw_RS780_me_load = yes
radeonkmsfw_R600_rlc = yes

This did not work.  The radeonkmsfw_R600_rlc.ko module does not get loaded and
the console does not get initialized. Apparently it has something to do with
loader loading the modules first, when the kernel is not running yet to have
detected the PCIe devices.  Even if you manually load radeonkmsfw_R600_rlc
after booting, using kldload, it still does not initialize the console.

You must load radeonkms.ko after the system is fully booted.

# kldload radeonkms

That automatically loads the other 3 modules and initializes the console where
the console text goes into higher resolution mode.  Then X and the desktop
environments work and seem to be fully functional, including transparency, etc.

So I can either put it in /etc/rc.local, to be run at boot time, or put it in
an X startup script wrapper.  Note that it must be run prior to startx because
it must be loaded before launching the X server.  So it cannot be put in
~/.xinitrc.

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

Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282

[Ed Schouten]

2018-06-18 8:02 GMT+02:00 Ed Schouten :
> I've just committed the patch (r335314) and
> will MFC it to 11-STABLE before the end of the week.

Done, in r335492. Thanks again for reporting this issue!

-- 
Ed Schouten 
Nuxi, 's-Hertogenbosch, the Netherlands
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iostat busy value calculation

[Holger Kipp]

Dear Miroslav,

> Am 20.06.2018 um 19:35 schrieb Miroslav Lachman <000.f...@quip.cz>:
> 
> Holger Kipp wrote on 2018/06/20 17:37:
>> Dear Miroslav,
>> looking at the manpage for iostat I see:
>>%b  % of time the device had one or more outstanding 
>> transactions
>>tsvc_t/i
>>total duration of transactions per time period, in seconds
>>sb/itotal time the device had one or more outstanding transac-
>>tions per time period, in seconds
>> So calculating the percentage using sb/i should be fairly easy.
> 
> If I understand it correctly, then it cannot be calculated from numbers 
> between two independent runs of "iostat -I -x" because it gives me sb/i 
> average from the boot time, so the calculated %b will be overall average 
> instead of average between two runs after 60 seconds.
> The only possible way to calculated is to run "iostat -I -x -c 2 -w 60" where 
> the sb/i value of the second line will be average of these last 60 seconds. 
> But it also means monitoring probe will wait 60 seconds to get this value 
> (each time) so it is the same problem as I described in my original post with 
> "iostat -x“


I haven’t thoroughly checked this myself (only a quick check), but with -I you 
should get the total values since boot. The man-page for OpenBSD states "The -I 
option causes iostat to print raw, unaveraged values.“ 

Eg. you have about 70.000 seconds where the devices ada0 and ada1 were busy, 
which equals 2%, so your system has an uptime of about 42 days.

Maybe you just check by getting values every 10 seconds, looking at sb/i and 
calculate the difference of two consecutive values, divide by the time period 
in seconds, multiply by 100 and have a percentage - with the downside of not 
being that accurate (as Warner Losh pointed out).

Best regards,
Holger

> Miroslav Lachman
> 
> 
>> Am 20.06.2018 um 16:55 schrieb Miroslav Lachman 
>> <000.f...@quip.cz>:
>> I would like to know how the value of disk "busy" is calculated?
>> I want to use values from iostat in the monitoring (zabbix).
>> iostat shows averages by default and the last column is "busy %", but the 
>> first output contains averages from the system boot til now.
>> # iostat -x -t da
>>extended device statistics
>> device r/s   w/skr/skw/s qlen svc_t  %b
>> ada0   2.5  13.849.0   287.90  45.7   2
>> ada1   2.6  13.851.7   287.90  39.6   2
>> I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 
>> seconds because it means monitoring needs to wait 20 seconds on each run.
>> I can use absolute values from iostat. This output is without any delay and 
>> the monitoring SW can calculate averages between two runs. But the last 
>> column is no busy %, it is sb/i.
>> # iostat -I -x -t da
>>extended device statistics
>> device   r/i w/i kr/i kw/i qlen tsvc_t/i 
>>  sb/i
>> ada0   7403218.0  40825749.0  144647824.0  849655694.00 2204904.2   
>> 73121.8
>> ada1   7537423.0  40825749.0  152643874.5  849655694.00 1914301.0   
>> 69996.5
>> So the question is - If I want to plot "busy %" in the graph - how the 
>> "busy" value in the first example is calculated?
>> Is it possible to calculate it from the numbers that I have from "iostat -I 
>> -x" and the know time interval between two runs?
> 
> 

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