15 Nov
2011
15 Nov
'11
9:02 p.m.
Hi,
Just wanting to know what people are doing for RT audio on Arch Linux?
Have got a bit out of the loop on these matters.
Not entirely sure what I had configured before... Think it was just
the standard kernel, but since 3.1 (possibly) (or a couple of weeks
ago) I'm informed that "JACK is running in realtime mode, but you are
not allowed to use realtime scheduling."
Any help appreciated.
James
15 Nov
15 Nov
9:15 p.m.
On Tue, Nov 15, 2011 at 09:02:50PM +0000, James Morris wrote:
Just wanting to know what people are doing for RT
audio on Arch Linux?
Have got a bit out of the loop on these matters.
Not entirely sure what I had configured before... Think it was just
the standard kernel, but since 3.1 (possibly) (or a couple of weeks
ago) I'm informed that "JACK is running in realtime mode, but you are
not allowed to use realtime scheduling."
Where do you get that message ?
I've been using Arch for the last two years on many systems
and never had any problems related to RT. Today I updated
one of them to 3.1, and the only problem I got was that now
I have to explicitly start the system dbus service (by adding
it to the DEAMONS array in /etc/rc.conf) otherwise the window
manager would fail to start. Audio seemed to work OK, but I
didn't test it in depth.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
9:31 p.m.
On 15 November 2011 21:15, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Tue, Nov 15, 2011 at 09:02:50PM +0000, James Morris
wrote:
When starting jackd. It further informs me that I don't have a sane
system configuration.
The only way I can get JACK running is to use the --no-realtime
switch. Then, for example, using the mouse scroll wheel on web pages
causes audible crackling.
I've been using JACK flawlessly up until a month or so ago (roughly
the last time I recall using it).
James.
Just wanting to know what people are doing for RT
audio on Arch Linux?
Have got a bit out of the loop on these matters.
Not entirely sure what I had configured before... Think it was just
the standard kernel, but since 3.1 (possibly) (or a couple of weeks
ago) I'm informed that "JACK is running in realtime mode, but you are
not allowed to use realtime scheduling."
Where do you get that message ?
9:42 p.m.
On Tue, Nov 15, 2011 at 09:31:42PM +0000, James Morris wrote:
On 15 November 2011 21:15, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
A few basics (just to be sure):
- Check /etc/security/limits.conf, where you should give
RT and memlock privileges to the audio group.
- Check if you are in the audio group.
If these are OK, the usual suspects are obese desktops like
Gnome and KDE, their zillions of dependencies and daemons,
and their security configurations using polkit and consolekit.
If that's the case I can't help, I'm not using those.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
Where do you get that message ?
When starting jackd. It further informs me that I don't have a sane
system configuration.
The only way I can get JACK running is to use the --no-realtime
switch. Then, for example, using the mouse scroll wheel on web pages
causes audible crackling.
I've been using JACK flawlessly up until a month or so ago (roughly
the last time I recall using it).
10:10 p.m.
On 15 November 2011 21:42, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Tue, Nov 15, 2011 at 09:31:42PM +0000, James Morris
wrote:
Yes, and yes.
On 15 November 2011 21:15, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
A few basics (just to be sure):
- Check /etc/security/limits.conf, where you should give
RT and memlock privileges to the audio group.
- Check if you are in the audio group. Where do you get that message ?
When starting jackd. It further informs me that I don't have a sane
system configuration.
The only way I can get JACK running is to use the --no-realtime
switch. Then, for example, using the mouse scroll wheel on web pages
causes audible crackling.
I've been using JACK flawlessly up until a month or so ago (roughly
the last time I recall using it).
If these are OK, the usual suspects are obese desktops like
Gnome and KDE, their zillions of dependencies and daemons,
and their security configurations using polkit and consolekit.
If that's the case I can't help, I'm not using those.
Well.. I'm not using Gnome or KDE desktops... But, there were a few
kdelibs depending on polkit. Removed them. Removed polkit. These
probably a result of installing something in the past month which I
never use so no loss.
Consolekit OTOH, I'm fairly sure (due to XFCE) will have been
installed for some time and hasn't caused problems before now.
But I think it [possibly] has to be something to do with all this as
around the same time, logging in with LXDM (LXDE graphical login
manager) suddenly stopped working (the login screen is head-to-toe
decorated in widget-grey, and any login attempts are immediately
booted out).
I'm currently using the Enter login manager which is probably more
broken than Slim (docs say it's broken regarding aforementioned *kits
IIRC).
Anyone no their way around this stuff?
I've also got an NVIDIA card, and using the proprietary driver (for
the occasional jaunt in minecraft).
James.
10:15 p.m.
System tuning in a nut shell:
+ install linux-rt
https://aur.archlinux.org/packages.php?ID=51360
+ To make the most of it, since linux 2.6.39 you can include
`threadirqs` in your kernel boot line.
+ Remember to install the package `rtirq`
+ include `rtirq` in your DAEMONS array in `/etc/rc.conf`. For example:
DAEMONS=(dbus hal syslog-ng rtirq @alsa @wicd)
+ Add to `/etc/secutiry/limits.conf`
@audio - rtprio 99
@audio - memlock unlimited
+ If you use firewire soundcards, include in your MODULES array in
`/etc/rc.conf`:
MODULES=(firewire-core firewire-ohci)
+ Add yourself to the `audio` group
usermod -a -G audio **yourUserID**
+ Add to `/etc/sysctl.conf`
vm.swappiness = 10
fs.inotify.max_user_watches = 524288
+ Add to `/etc/udev/rules.d/40-hpet-permissions.rules`
KERNEL=="rtc0", GROUP="audio"
KERNEL=="hpet", GROUP="audio"
+ Set the cpufreq governor to `performance`. See the
[ArchWiki article](https://wiki.archlinux.org/index.php/Cpufreq#Daemon)
+ To use ALSA applications with JACK (web browsers and other
applications without JACK support) you can install the package
`alsa-plugins` and add the following to `~/.asoundrc`
# convert alsa API over jack API
# use it with
# % aplay foo.wav
# use this as default
pcm.!default {
type plug
slave { pcm "jack" }
}
ctl.mixer0 {
type hw
card 1
}
# pcm type jack
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
10:19 p.m.
Also: uninstall nvidia, install nouveau to make your system compatible
with the new linux-rt 3.0 series.
linux-rt 3.0.9-rt25 is *very* stable here.
You can change patch linux-rt too, but I think this is less tested.
The AUR package is outdated, you can use this updated version if you
want to 3.0.9-rt25:
http://hpaste.org/54080
10:40 p.m.
On Tue, Nov 15, 2011 at 02:19:01PM -0800, Bernardo Barros wrote:
Also: uninstall nvidia, install nouveau to make your
system compatible
with the new linux-rt 3.0 series.
I never used the proprietary nvidia driver, but on one system (out of
the > 10 I'm admin for), I'm forced to use nv. Video HW is 7300 LE.
With nouveau everything works OK up to and including the xdm login
(with the Arch 'theme'). But as soon as I login and start either
windowmaker or xfce the screen looks as if X is using the wrong
resolution (offset and partially repeated). Things have been like
this for the past two years, and are still the same after a complete
update earlier today. If you have any hints that could help to solve
this I'd be very happy !
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
16 Nov
16 Nov
6:36 a.m.
Fons Adriaensen wrote:
On Tue, Nov 15, 2011 at 02:19:01PM -0800, Bernardo
Barros wrote:
I had to switch from NV to NVidia proprietary because Nouveau doesn't
suppoort the NVidia hardware on my desktop's motherboard.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Also: uninstall nvidia, install nouveau to make
your system compatible
with the new linux-rt 3.0 series.
I never used the proprietary nvidia driver, but on one system (out of
the > 10 I'm admin for), I'm forced to use nv. Video HW is 7300 LE.
With nouveau everything works OK up to and including the xdm login
(with the Arch 'theme'). But as soon as I login and start either
windowmaker or xfce the screen looks as if X is using the wrong
resolution (offset and partially repeated). Things have been like
this for the past two years, and are still the same after a complete
update earlier today. If you have any hints that could help to solve
this I'd be very happy ! 
21 Nov
21 Nov
10:25 p.m.
Excerpts from Fons Adriaensen's message of 2011-11-15 23:40:04 +0100:
On Tue, Nov 15, 2011 at 02:19:01PM -0800, Bernardo
Barros wrote:
It's a long shot, but did you try it without login manager?
Regards,
Philipp
Also: uninstall nvidia, install nouveau to make
your system compatible
with the new linux-rt 3.0 series.
I never used the proprietary nvidia driver, but on one system (out of
the > 10 I'm admin for), I'm forced to use nv. Video HW is 7300 LE.
With nouveau everything works OK up to and including the xdm login
(with the Arch 'theme'). But as soon as I login and start either
windowmaker or xfce the screen looks as if X is using the wrong
resolution (offset and partially repeated). Things have been like
this for the past two years, and are still the same after a complete
update earlier today. If you have any hints that could help to solve
this I'd be very happy !
10:30 p.m.
I think I found it. You added this line, right?
$ /etc/pam.d/su
...
session required pam_limits.so
11:04 p.m.
Excerpts from Bernardo Barros's message of 2011-11-21 23:30:26 +0100:
I think I found it. You added this line, right?
$ /etc/pam.d/su
...
session required pam_limits.so
No, I didn't do anything there, it just works. Here's my version of this file
anyway.
#%PAM-1.0
auth sufficient pam_rootok.so
# Uncomment the following line to implicitly trust users in the "wheel" group.
#auth sufficient pam_wheel.so trust use_uid
# Uncomment the following line to require a user to be in the "wheel" group.
#auth required pam_wheel.so use_uid
auth required pam_unix.so
account required pam_unix.so
session required pam_unix.so
Also, my .xinitrc doesn't contain anything related to PAM, permissions
or anything like that. I don't know why any of that would be needed. The
only pam related changes I made were in /etc/security/limits.conf and I
added my user to the audio group, but that's normal procedure.
Now that I read https://wiki.archlinux.org/index.php/Realtime_for_Users
I start to wonder myself.. maybe I made some change a couple of years
ago that makes it work and I simply forgot about it. No idea whether pam
is running or whatever it does, it stayed out of my way and jack works
as expected.
A quick search led me to ... the pam manpage, which kind of suggests that
login uses pam: http://linux.die.net/man/8/pam.d
Did I miss something?
Regards,
Philipp
10:42 p.m.
On Mon, Nov 21, 2011 at 11:25:01PM +0100, Philipp Überbacher wrote:
Excerpts from Fons Adriaensen's message of
2011-11-15 23:40:04 +0100:
No, for the simple reason that the login manager is the part
that works...
Xdm is an X app, so X is running when I see the login screen,
and everything seems OK. I've no idea what is actually supposed
to happen when I login. Is X restarted by launching windowmaker
or xfce ? If it is, that is probably where things go wrong.
I could try booting into RL3, log in and then move to RL5 and
a window manager. What is the recommended way of doing this ?
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
On Tue, Nov 15, 2011 at 02:19:01PM -0800,
Bernardo Barros wrote:
It's a long shot, but did you try it without login manager? Also: uninstall nvidia, install nouveau to make
your system compatible
with the new linux-rt 3.0 series.
I never used the proprietary nvidia driver, but on one system (out of
the > 10 I'm admin for), I'm forced to use nv. Video HW is 7300 LE.
With nouveau everything works OK up to and including the xdm login
(with the Arch 'theme'). But as soon as I login and start either
windowmaker or xfce the screen looks as if X is using the wrong
resolution (offset and partially repeated). Things have been like
this for the past two years, and are still the same after a complete
update earlier today. If you have any hints that could help to solve
this I'd be very happy !
25 Nov
25 Nov
11:16 a.m.
Excerpts from Fons Adriaensen's message of 2011-11-21 23:42:32 +0100:
On Mon, Nov 21, 2011 at 11:25:01PM +0100, Philipp
Überbacher wrote:
I really don't know what login managers do. In the 'login' case it's
easy, login, startx, done. I think it's still worth a try. If that works
you could investigate what Xdm actually does.
No idea about runlevels either, sorry.
One further idea though: try enabling/disabling kms (kernel option
'nomodeset'), see whether the problem persists. The arch wiki says
nouveau needs kms, but it's not always right.
https://wiki.archlinux.org/index.php/Nouveau#KMS
https://wiki.archlinux.org/index.php/KMS
Regards,
Philipp
Excerpts from Fons Adriaensen's message of
2011-11-15 23:40:04 +0100:
No, for the simple reason that the login manager is the part
that works...
Xdm is an X app, so X is running when I see the login screen,
and everything seems OK. I've no idea what is actually supposed
to happen when I login. Is X restarted by launching windowmaker
or xfce ? If it is, that is probably where things go wrong.
I could try booting into RL3, log in and then move to RL5 and
a window manager. What is the recommended way of doing this ?
Ciao, On Tue, Nov 15, 2011 at 02:19:01PM -0800,
Bernardo Barros wrote:
It's a long shot, but did you try it without login manager? Also: uninstall nvidia, install nouveau to make
your system compatible
with the new linux-rt 3.0 series.
I never used the proprietary nvidia driver, but on one system (out of
the > 10 I'm admin for), I'm forced to use nv. Video HW is 7300 LE.
With nouveau everything works OK up to and including the xdm login
(with the Arch 'theme'). But as soon as I login and start either
windowmaker or xfce the screen looks as if X is using the wrong
resolution (offset and partially repeated). Things have been like
this for the past two years, and are still the same after a complete
update earlier today. If you have any hints that could help to solve
this I'd be very happy ! 
11:30 a.m.
Hi,
On 25/11/11 12:16, Philipp Überbacher wrote:
Excerpts from Fons Adriaensen's message of
2011-11-21 23:42:32 +0100:
> On Mon, Nov 21, 2011 at 11:25:01PM +0100, Philipp Überbacher wrote:
>> Excerpts from Fons Adriaensen's message of 2011-11-15 23:40:04 +0100:
>>> On Tue, Nov 15, 2011 at 02:19:01PM -0800, Bernardo Barros wrote:
[...]
>>
>> It's a long shot, but did you try it without login manager?
>
> No, for the simple reason that the login manager is the part
> that works...
[...]
I really don't know what login managers do. In the
'login' case it's
easy, login, startx, done. I think it's still worth a try. If that works
you could investigate what Xdm actually does.
Not how relevant if this is relevant, but for me on debian with slim
login manager and xfce (after the usual audio group, limits.conf things)
the solution suggested towards the end of this forum worked for me and
now jackd and e.g. pd run in realtime for user (on a non realtime kernel):
http://linuxmusicians.com/viewtopic.php?f=27&t=2607&start=0&st=…
Lorenzo.
15 Nov
15 Nov
11:28 p.m.
On 16/11/11 09:19, Bernardo Barros wrote:
Also: uninstall nvidia, install nouveau to make your
system compatible
with the new linux-rt 3.0 series.
FWIW, with a -lowlatency kernel on Ubuntu 11.10, I've had much better
experience with the NVIDIA driver than with the Nouveau driver. With
Nouveau, navigating around the desktop, and leaving/entering the GNOME
Shell overview in particular, caused a tonne of xruns. Those xruns
disappeared when I installed the NVIDIA driver again.
I don't know if Nouveau with a RT-patched kernel would perform even
better, but my current setup works very well for me -- I'm rock-solid at
8ms latency and can push it to 4ms without too much drama.
Thanks
Leigh
linux-rt 3.0.9-rt25 is *very* stable here.
You can change patch linux-rt too, but I think this is less tested.
The AUR package is outdated, you can use this updated version if you
want to 3.0.9-rt25:
http://hpaste.org/54080
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
11:33 p.m.
It's a license issue.
If you really need nvidia, you can patch 3 lines of linux-rt yourself
and use nvidia-rt.
You just can't distribute it.
I had issues with nouveau + audio before, but now it's working great.
16 Nov
16 Nov
6:35 a.m.
FYI, Nouveau doesn't work work older NVidia hardware that nv worked with.
Bernardo Barros wrote:
Also: uninstall nvidia, install nouveau to make your
system compatible
with the new linux-rt 3.0 series.
linux-rt 3.0.9-rt25 is *very* stable here.
You can change patch linux-rt too, but I think this is less tested.
The AUR package is outdated, you can use this updated version if you
want to 3.0.9-rt25:
http://hpaste.org/54080
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
9:01 a.m.
On 11/15/11 23:10, James Morris wrote:
I'm currently using the Enter login manager which
is probably more
broken than Slim (docs say it's broken regarding aforementioned *kits
IIRC).
Does Enter support PAM? And what if you log in on a virtual terminal and
start JACK from there?
Best,
Jeremy
2:46 p.m.
On 16 November 2011 09:01, Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
On 11/15/11 23:10, James Morris wrote:
Thanks for this, a lack of PAM support in Enter IS the problem.
I've installed my old favourite: XDM and everything is back to normal.
James.
I'm currently using the Enter login manager which is probably more
broken than Slim (docs say it's broken regarding aforementioned *kits
IIRC).
Does Enter support PAM? And what if you log in on a virtual terminal and
start JACK from there?
Best,
Jeremy
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
21 Nov
21 Nov
10:21 p.m.
Excerpts from James Morris's message of 2011-11-16 15:46:32 +0100:
On 16 November 2011 09:01, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
Glad it works for you now, just want to mention my favorite login
manager since a couple of years: none at all
Configuration is easy through ~/.xinitrc,
login on console, startx can be called manually or automatically
I keep wondering about the purpose of login managers
Regards,
Philipp
On 11/15/11 23:10, James Morris wrote:
Thanks for this, a lack of PAM support in Enter IS the problem.
I've installed my old favourite: XDM and everything is back to normal.
James.
I'm currently using the Enter login manager which is probably more
broken than Slim (docs say it's broken regarding aforementioned *kits
IIRC).
Does Enter support PAM? And what if you log in on a virtual terminal and
start JACK from there? 
25 Nov
25 Nov
9:10 a.m.
Am 21.11.2011 23:21, schrieb Philipp Überbacher:
Excerpts from James Morris's message of 2011-11-16
15:46:32 +0100:
Well, it adds some comfort. Such as: easily switch from GNOME to KDE4 to
Fluxbox etc.
No need to edit any files, everything inuitive. And still no automatisms
that paternalize: if the login-manager is set up OK, you can just choose
whatever the system supports.
a toy, maybe but useful.
On 16 November 2011 09:01, Jeremy
Jongepier<jeremy(a)autostatic.com> wrote:
Glad it works for you now, just want to mention my favorite login
manager since a couple of years: none at all
Configuration is easy through ~/.xinitrc,
login on console, startx can be called manually or automatically
I keep wondering about the purpose of login managers On 11/15/11 23:10, James Morris wrote:
Thanks for this, a lack of PAM support in Enter IS the problem.
I've installed my old favourite: XDM and everything is back to normal.
James.
I'm currently using the Enter login manager which is probably more
broken than Slim (docs say it's broken regarding aforementioned *kits
IIRC).
Does Enter support PAM? And what if you log in on a virtual terminal and
start JACK from there?
Regards,
Philipp
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
4542
days inactive
4552
days old
linux-audio-user@lists.linuxaudio.org
22 comments
9 participants
participants (9)
-
Bernardo Barros -
david -
Fons Adriaensen -
Hartmut Noack -
James Morris -
Jeremy Jongepier -
Leigh Dyer -
Lorenzo Sutton -
Philipp Überbacher