rt prio with kernel 3.x, issue to use the vesa driver
That for a shared IRQ the graphics will become an unwanted high prio
doesn't happen with a kernel 2.6.31-rt19 + NVIDIA 195.36.15 on Suse 11.2
on my machine.
As already reported, it also doesn't happen with the kernels
3.0.23-avl-7-pae (threadirqs) and 3.0.23-rt40 on current AV Linux, where
still the nv driver is available and used on my machine.
IIUC it's definitive related to the kernel, I anyway will test the vesa
driver with Ubuntu Studio Precise, but can' get it working.
I modified the xorg.conf I use with the nvida driver, startup ends with
tty, no X. Does anybody notice what I might have missed?
PS: If there won't be an rtirq script able to handle it or any other way
to do it, I hadn't time to test until now, I'll simply will use a kernel
<= 3.0 instead > 3.0.
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
05-06-2012, 01:57 PM
Ralf Mardorf
rt prio with kernel 3.x, issue to use the vesa driver
On Sun, 2012-05-06 at 15:39 +0200, Emanuel Rumpf wrote:
> a list more appropriate for this trash: linux-tuning :
> http://lists.linuxaudio.org/listinfo/
Thank you, regarding to
http://lists.linuxaudio.org/pipermail/linux-audio-tuning/2012-May/000147.html
you've got similar issues.
Since there are other issues on my AV Linux (Debian stable) install
using a 3.0, I'll use a 2.6 kernel, when I drop 3.2.0-23-lowlatency for
Precise. OTOH for a while some 3.0 or 3.x was ok on Arch, but now it's
broken too.
Anyway, perhaps somebody has got an idea:
spinymouse@oz:~$ cat /media/precise/var/log/Xorg.0.log
[snip]
[ 10.974] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 10.975] vesa: Ignoring device with a bound kernel driver
[ 10.975] (WW) Falling back to old probe method for vesa
[ 10.975] (II) UnloadModule: "vesa"
[ 10.975] (II) Unloading vesa
[ 10.975] (EE) Screen(s) found, but none have a usable configuration.
[ 10.975]
Fatal server error:
[ 10.975] no screens found
[snip]
spinymouse@oz:~$ cat /media/precise/etc/X11/xorg.conf
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection
I guess that later today I'll restore the nvidia's xorg.conf and build a
non-rt preempt 3.0 and/or 2.6 with threadirqs.
Perhaps I'll keep the current kernel after installing a new kernel and
will subscribe to the tuning list.
On Debian list somebody has many issues with latest kernel, while he or
she hasn't with 2.6. I guess non-audio usage.
Regards,
Ralf
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
05-06-2012, 02:16 PM
Ralf Mardorf
rt prio with kernel 3.x, issue to use the vesa driver
Did for anyone using a 3.0 rt or 3.x rt work to patch the kernel or to
patch the nvidia driver to get the rt working with the nvidia driver?
Both methods didn't work for me. To ensure that a patch might be buggy,
I edited manually.
Nouveau does work too slow and too buggy on my machine. After updating X
on Arch, the nv driver that still is kept didn't work anymore.
Old installs without issues can't be used with my new card, a RME HDSPe
AIO, because I need COMPLETE ALSA ex .24 and this can become an issue.
New installs became an issue regarding to the graphics.
It might be, that a kernel full preempt with threadirqs might be ok too,
but until now I get this 3.x issues.
Perhaps I shouldn't waste other people's and my time and simply build
the last 2.6 kernel full preempt without rt.
I hope this will be solved before it becomes impossible to use 2.6
kernels for major distros.
Regards,
Ralf
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
05-06-2012, 02:18 PM
Ralf Mardorf
rt prio with kernel 3.x, issue to use the vesa driver
On Sun, 2012-05-06 at 16:16 +0200, Ralf Mardorf wrote:
> Did for anyone using a 3.0 rt or 3.x rt work to patch the kernel or to
> patch the nvidia driver to get the rt working with the nvidia driver?
> Both methods didn't work for me. To ensure that a patch might be buggy,
> I edited manually.
Broken English ... a buggy patch can't be the cause, since I edited
manually several times.
--
Ubuntu-Studio-users mailing list
Ubuntu-Studio-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users