[arch-general] Munin and MySQL
Hi all, anyone proficient at Munin?
The talk of one of our guest speakers at the local SFD that took place
yesterday was about monitoring everything with Munin, a software I didn't
knew but which I liked at first sight.
Once at home the very first thing I did after take the laptop out of my
backpack was install Munin, of course, and alongside this I found some
warning and error messages that aren't very informative so before go and
dive on the net trying to gather information about them I decided to first
try luck in the list.
Whenever I run:
# munin-node-configure --shell | sh
I got this:
# The following plugins caused errors:
# mysql_:
# Non-zero exit during autoconf (2)
# ntp_states:
# Non-zero exit during autoconf (2)
# proc:
# In family 'auto' but doesn't have 'autoconf' capability
Now the munin-node-configure --suggest command shows:
| no | no
for all the three plugins. Following the wiki suggestion:
# munin-run {plugin}
I got a:
# Unknown service '{plugin}'
for all them three.
I would appreciate any light here since seems there isn't any Munin error
log file to check and also Munin does not log to standard
/var/log/errors.log file.
Greetz,
Martin
Re: [arch-general] almost got latest talkingarch installed
One thing I forgot to write up. After booting into new system, hitting keys on keypad does not crash the system and those keys perform the expected speakup functions so the system is definitely using linux-lts and not the flake default kernel. --- jude Adobe fiend for failing to Flash
Re: [arch-general] almost got talking arch installed
I put the fixes in on /boot/syslinux/syslinux.cfg and was successful in First running initcpio -p linux-lts had no problems running and I pointed everything to linux-lts in /boot/syslinux/syslinux.cfg. Then I rebooted the system. I let the computer alone for 8 hours then returned and hit enter to get archlinux talking. I managed to login as root and was told the file system was read only. I checked /dev/sda1 and /dev/sda3 with ls -al and in both cases got the attribute string back of brw-rw. I replaced the arch disk in the drive sled with a working install of debian and after boot up checked /dev/sda1 with ls -al and got the attribute string back of brw-rw---T. So the latest talking archlinux over here using syslinux turns out to be installable and unusable at least for the moment. Is this salvageable, I don't know this is the first time anything like that happened in my experience with Linux. This time, I can't produce any dmesg output given the state of the disk and probably the boot process either. --- jude Adobe fiend for failing to Flash
Re: [arch-general] Proprietary nvidia driver for different kernels
On Sun, 2012-09-16 at 21:30 +0200, Joakim Hernberg wrote: > On Sun, 16 Sep 2012 20:35:57 +0200 > Ralf Mardorf wrote: > > > > ... nouveau never worked on my machine. > > Have you tried nouveau lately? It has improved a lot lately... That's a good question. $ pacman -Si xf86-video-nouveau Version: 1.0.1-1 Conflicts With : xorg-server<1.11.99.902 Build Date : Tue Jun 19 03:43:40 2012 $ pacman -Qi xorg-server Version: 1.12.4-1 $ pacman -Qi libdrm Name : libdrm Version: 2.4.39-1 I don't know. I'll test it again. At least nouveau 0.0.15 and libdrm 2.4.21 for another outdated Linux don't work, but I'm sure I also tested newer versions. Regards, Ralf
Re: [arch-general] Proprietary nvidia driver for different kernels
On Sun, 16 Sep 2012 20:35:57 +0200 Ralf Mardorf wrote: > ... nouveau never worked on my machine. Have you tried nouveau lately? It has improved a lot lately... -- Joakim
[arch-general] Proprietary nvidia driver for different kernels
Hi :) until now I switch between the FLOSS nv driver and the proprietary nvidia driver at startup, depending to the kernel I boot. IOW I use the nv driver with kernel-rt and the proprietary with 3.5.3-1-ARCH. If I try to boot the kernel-rt, I get a black screen. [spinymouse@archlinux ~]$ pacman -Qi nvidia | grep Ver Version: 304.43-1 [spinymouse@archlinux ~]$ pacman -Qi nvidia-rt | grep Ver Version: 304.43-1 [spinymouse@archlinux ~]$ pacman -Qi nvidia-utils | grep Ver Version: 304.43-1 [spinymouse@archlinux ~]$ pacman -Qi xf86-video-nv | grep Ver Version: 2.1.20-1 [spinymouse@archlinux ~]$ grep DAEMONS /etc/rc.conf # DAEMONS DAEMONS=(!69switch_xorg.conf hwclock syslog-ng !network !netfs crond acpid dbus networkmanager rtirq) Any ideas? The graphics is a GeForce 7200 GS. The nv driver is ok, but I have to readjust the monitor if I switch from nvidia and soon or later it will be dropped. The vesa driver won't provide the needed resolution and noveau
Re: [arch-general] Proprietary nvidia driver for different kernels
On Sun, 2012-09-16 at 20:32 +0200, Ralf Mardorf wrote: > Hi :) > > until now I switch between the FLOSS nv driver and the proprietary > nvidia driver at startup, depending to the kernel I boot. IOW I use the > nv driver with kernel-rt and the proprietary with 3.5.3-1-ARCH. > > If I try to boot the kernel-rt, I get a black screen. > > [spinymouse@archlinux ~]$ pacman -Qi nvidia | grep Ver > Version: 304.43-1 > [spinymouse@archlinux ~]$ pacman -Qi nvidia-rt | grep Ver > Version: 304.43-1 > [spinymouse@archlinux ~]$ pacman -Qi nvidia-utils | grep Ver > Version: 304.43-1 > [spinymouse@archlinux ~]$ pacman -Qi xf86-video-nv | grep Ver > Version: 2.1.20-1 > [spinymouse@archlinux ~]$ grep DAEMONS /etc/rc.conf > # DAEMONS > DAEMONS=(!69switch_xorg.conf hwclock syslog-ng !network !netfs crond > acpid dbus networkmanager rtirq) > > Any ideas? The graphics is a GeForce 7200 GS. The nv driver is ok, but I > have to readjust the monitor if I switch from nvidia and soon or later > it will be dropped. The vesa driver won't provide the needed resolution > and noveau Apologize. ... nouveau never worked on my machine. Regards, Ralf PS: Before I'll add a note to AUR, I want to know, if there's any alternative to nouveau and nv, assumed I won't get nvidia to work.
Re: [arch-general] Issue with Jack2, ALSA or current kernels
Oops, pardon, the last mail should be send to LAU not to Arch general :S.
Re: [arch-general] Issue with Jack2, ALSA or current kernels
Hi Peter, apologize, I was right, Jack does work with all kernels. I guess it was a broken package, http://mailman.archlinux.org/pipermail/arch-general/2012-September/031005.html . So my mails indeed were some kind of SPAM: ": Recipient address rejected: Mail appeared to be SPAM or forged." Regards, Ralf > From: Ralf Mardorf > To: linux-audio-u...@lists.linuxaudio.org > Cc: Peter Lutek > Subject: Re: [LAU] hdsp not happy with recent kernels > Date: Sun, 16 Sep 2012 12:52:10 +0200 > > On Sat, 2012-09-15 at 10:48 -0400, Peter Lutek wrote: > [snip] > > Peter, today I noticed that I also have issues with some of the kernels. > When I claimed that all kernels are ok here, I was mistaken. For the > record, rtirq isn't set up as needed, but that doesn't matter. Group > audio and the security limits are set up correctly. > > For 3.2.0.23 everything still is ok ... > > ### > > spinymouse@precise:~$ uname -a > Linux precise 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11 > 02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux > spinymouse@precise:~$ jackd -dalsa -dhw:0 -r48000 -p64 -n2 > jackdmp 1.9.8 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2011 Grame. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > control device hw:0 > control device hw:0 > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit > control device hw:0 > configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods > ALSA: final selected sample format for capture: 32bit integer > little-endian > ALSA: use 256 periods for capture > ALSA: final selected sample format for playback: 32bit integer > little-endian > ALSA: use 256 periods for playback > > ### > > ... but for 3.4.4-rt14 I get a strange output. > > [spinymouse@archlinux ~]$ uname -a > Linux archlinux 3.4.4-rt14-1-rt #1 SMP PREEMPT RT Fri Jul 20 13:16:40 > UTC 2012 x86_64 GNU/Linux > > Because it's easier to copy the whole output I started Jack by QJackCtl. > > 12:19:29.786 Patchbay deactivated. > 12:19:29.791 Statistics reset. > 12:19:29.845 ALSA connection change. > Cannot connect to server socket err = No such file or directory > Cannot connect to server socket > jack server is not running or cannot be started > 12:19:29.861 ALSA connection graph change. > 12:19:30.894 JACK is starting... > 12:19:30.895 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p64 -n2 > Cannot connect to server socket err = No such file or directory > Cannot connect to server socket > jack server is not running or cannot be started > 12:19:30.928 JACK was started with PID=1176. > could not open component .so '/usr/lib/jack/jack_firewire.so': > libffado.so.2: cannot open shared object file: No such file or directory > could not open driver .so '/usr/lib/jack/jack_firewire.so': > libffado.so.2: cannot open shared object file: No such file or directory > jack_get_descriptor returns null for 'jack_firewire.so' > could not open component .so '/usr/lib/jack/jack_firewire.so': > libffado.so.2: cannot open shared object file: No such file or directory > jackdmp 1.9.8 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2011 Grame. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > Jack: Create non RT thread > Jack: ThreadHandler: start > Jack: playback device hw:0 > Jack: capture device hw:0 > Jack: apparent rate = 48000 > Jack: frames per period = 64 > Jack: JackDriver::Open capture_driver_name = hw:0 > Jack: JackDriver::Open playback_driver_name = hw:0 > Jack: Check protocol client = 8 server = 8 > Jack: JackEngine::ClientInternalOpen: name = system > Jack: JackEngine::AllocateRefNum ref = 0 > Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system > val = 0 > Jack: JackEngine::NotifyAddClient: name = system > Jack: JackGraphManager::SetBufferSize size = 64 > Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackDriver::SetupDriverSync driver sem in flush mode > control device hw:0 > control device hw:0 > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit > control device hw:0 > configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods > ALSA: final selected sample format for capture: 32bit integer > little-endian > ALSA: use 256 periods for capture > ALSA: final selected sample format for playback: 32bit integer > little-endian > ALSA: use
[arch-general] [seemingly solved] Issue with Jack2, ALSA or current kernels
Thank you Ray :) seemingly it's solved. I can't test it now, but the bad messages are gone away [1]. What was the culprit? Regards, Ralf [1] [root@archlinux src]# pacman -Syu jack2 [root@archlinux src]# pacman -Qi jack2 Packager : Rashif Rahman Architecture : x86_64 Build Date : Sun Sep 16 16:17:03 2012 Install Date : Sun Sep 16 18:49:50 2012 ## [spinymouse@archlinux ~]$ jackd -dalsa -dhw:0 -r44100 -p128 -n2 jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|128|2|44100|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 128 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 128 periods for playback [spinymouse@archlinux ~]$ uname -a Linux archlinux 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64 GNU/Linux ## [spinymouse@archlinux ~]$ jackd -dalsa -dhw:0 -r44100 -p128 -n2 jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|128|2|44100|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 128 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 128 periods for playback [spinymouse@archlinux ~]$ uname -a Linux archlinux 3.4.4-rt14-1-rt #1 SMP PREEMPT RT Fri Jul 20 13:16:40 UTC 2012 x86_64 GNU/Linux
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On Sun, 2012-09-16 at 17:59 +0200, Ralf Mardorf wrote: > For pacman -Syu jack[...] nothing changed until now, so I used Firefox > to search and installed jack2-dbus, but the package doesn't provide > jackdmp [1]. > > [spinymouse@archlinux ~]$ qjackctl > With "Enable D-Bus interface" checked and unchecked I get: > [snip] > 17:51:38.277 JACK is starting... > 17:51:38.278 jackd -dalsa -dhw:0 -r48000 -p64 -n2 > Cannot connect to server socket err = No such file or directory > Cannot connect to server socket > jack server is not running or cannot be started > 17:51:38.301 Could not start JACK. Sorry. > 17:51:39.678 JACK was stopped with exit status=255. > 17:51:44.493 Statistics reset. > > Btw. I need jackdmp, not jackdbus. The dbus thingy is completely useless > for my session scripts. > > Regards, > Ralf > > [1] > [root@archlinux src]# wget > http://mirror.us.leaseweb.net/archlinux/community/os/x86_64/jack2-dbus-1.9.8-3-x86_64.pkg.tar.xz > [root@archlinux src]# pacman -U jack2-dbus-1.9.8-3-x86_64.pkg.tar.xz > :: jack2-dbus and jack2 are in conflict (jack). Remove jack2? [y/N] y > Targets (2): jack2-1.9.8-2 [removal] jack2-dbus-1.9.8-3 > > [spinymouse@archlinux ~]$ pacman -Qi jack2-dbus | grep Provides > Provides : jack jack2 jackmp jackdmp jackdbus > [spinymouse@archlinux ~]$ pacman -Ql jack2-dbus | grep /usr/bin [snip] > jack2-dbus /usr/bin/jackdbus I now run [spinymouse@archlinux ~]$ jackdbus auto no message buffer overruns no message buffer overruns no message buffer overruns Then I launched QjackCtl. I had to start Jack with QjackCtl again, "Enable D-Bus interface" was checked. The output: 18:09:52.147 Patchbay deactivated. 18:09:52.149 Statistics reset. 18:09:52.151 ALSA connection change. 18:09:52.204 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 18:09:52.214 ALSA connection graph change. 18:09:55.928 D-BUS: JACK server is starting... Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 18:09:55.942 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus). Sun Sep 16 18:09:55 2012: Starting jack server... Sun Sep 16 18:09:55 2012: JACK server starting in realtime mode with priority 10 Sun Sep 16 18:09:55 2012: control device hw:0 Sun Sep 16 18:09:55 2012: control device hw:0 Sun Sep 16 18:09:55 2012: Acquired audio card Audio0 Sun Sep 16 18:09:55 2012: creating alsa driver ... hw:0|hw:0|64|2|48000| 0|0|nomon|swmeter|-|32bit Sun Sep 16 18:09:55 2012: control device hw:0 Sun Sep 16 18:09:55 2012: configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods Sun Sep 16 18:09:55 2012: ALSA: final selected sample format for capture: 32bit integer little-endian Sun Sep 16 18:09:55 2012: ALSA: use 256 periods for capture Sun Sep 16 18:09:55 2012: ALSA: final selected sample format for playback: 32bit integer little-endian Sun Sep 16 18:09:55 2012: ALSA: use 256 periods for playback Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_1' Sun Sep 16 18:09:55 2012: New client 'system' with PID 0 Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_2' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_3' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_4' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_5' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_6' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_7' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_8' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_9' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_10' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_11' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_12' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_13' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:capture_14' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_1' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_2' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_3' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_4' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_5' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_6' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_7' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_8' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_9' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_10' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_11' Sun Sep 16 18:09:55 2012: graph reorder: new port 'system:playback_12
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On Sun, 2012-09-16 at 22:54 +0800, Rashif Ray Rahman wrote: > Hi Ralf > > Please try 1.9.8-3 soon when it reaches the mirrors. For pacman -Syu jack[...] nothing changed until now, so I used Firefox to search and installed jack2-dbus, but the package doesn't provide jackdmp [1]. [spinymouse@archlinux ~]$ qjackctl With "Enable D-Bus interface" checked and unchecked I get: 17:51:04.484 Patchbay deactivated. 17:51:04.488 Statistics reset. 17:51:04.549 ALSA connection change. Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 17:51:04.570 ALSA connection graph change. 17:51:07.917 JACK is starting... 17:51:07.918 jackd -dalsa -dhw:0 -r48000 -p64 -n2 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 17:51:07.947 Could not start JACK. Sorry. 17:51:15.300 JACK was stopped with exit status=255. 17:51:32.613 JACK is starting... 17:51:32.614 jackd -dalsa -dhw:0 -r48000 -p64 -n2 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 17:51:32.635 Could not start JACK. Sorry. 17:51:35.412 JACK was stopped with exit status=255. 17:51:38.277 JACK is starting... 17:51:38.278 jackd -dalsa -dhw:0 -r48000 -p64 -n2 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 17:51:38.301 Could not start JACK. Sorry. 17:51:39.678 JACK was stopped with exit status=255. 17:51:44.493 Statistics reset. Btw. I need jackdmp, not jackdbus. The dbus thingy is completely useless for my session scripts. Regards, Ralf [1] [root@archlinux src]# wget http://mirror.us.leaseweb.net/archlinux/community/os/x86_64/jack2-dbus-1.9.8-3-x86_64.pkg.tar.xz [root@archlinux src]# pacman -U jack2-dbus-1.9.8-3-x86_64.pkg.tar.xz :: jack2-dbus and jack2 are in conflict (jack). Remove jack2? [y/N] y Targets (2): jack2-1.9.8-2 [removal] jack2-dbus-1.9.8-3 [spinymouse@archlinux ~]$ pacman -Qi jack2-dbus | grep Provides Provides : jack jack2 jackmp jackdmp jackdbus [spinymouse@archlinux ~]$ pacman -Ql jack2-dbus | grep /usr/bin jack2-dbus /usr/bin/ jack2-dbus /usr/bin/alsa_in jack2-dbus /usr/bin/alsa_out jack2-dbus /usr/bin/jack_alias jack2-dbus /usr/bin/jack_bufsize jack2-dbus /usr/bin/jack_connect jack2-dbus /usr/bin/jack_control jack2-dbus /usr/bin/jack_cpu jack2-dbus /usr/bin/jack_cpu_load jack2-dbus /usr/bin/jack_disconnect jack2-dbus /usr/bin/jack_evmon jack2-dbus /usr/bin/jack_freewheel jack2-dbus /usr/bin/jack_iodelay jack2-dbus /usr/bin/jack_latent_client jack2-dbus /usr/bin/jack_load jack2-dbus /usr/bin/jack_lsp jack2-dbus /usr/bin/jack_metro jack2-dbus /usr/bin/jack_midi_dump jack2-dbus /usr/bin/jack_midi_latency_test jack2-dbus /usr/bin/jack_midiseq jack2-dbus /usr/bin/jack_midisine jack2-dbus /usr/bin/jack_monitor_client jack2-dbus /usr/bin/jack_multiple_metro jack2-dbus /usr/bin/jack_net_master jack2-dbus /usr/bin/jack_net_slave jack2-dbus /usr/bin/jack_netsource jack2-dbus /usr/bin/jack_rec jack2-dbus /usr/bin/jack_samplerate jack2-dbus /usr/bin/jack_server_control jack2-dbus /usr/bin/jack_session_notify jack2-dbus /usr/bin/jack_showtime jack2-dbus /usr/bin/jack_simple_client jack2-dbus /usr/bin/jack_simple_session_client jack2-dbus /usr/bin/jack_test jack2-dbus /usr/bin/jack_thru jack2-dbus /usr/bin/jack_transport jack2-dbus /usr/bin/jack_unload jack2-dbus /usr/bin/jack_wait jack2-dbus /usr/bin/jack_zombie jack2-dbus /usr/bin/jackdbus
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On 16 September 2012 22:41, Ralf Mardorf wrote: > I installed the optional dependencies. > > # pacman -Syu libffado dbus-core python2 > Targets (4): libxml++-2.34.2-1 dbus-core-1.6.4-1 libffado-2.0.1-7 > python2-2.7.3-2 > > Only the missing FFADO lib output disappeared, all the other output > seems to be the same as before. > FWIW I'll reboot, if I shouldn't write an additional mail, than the > reboot didn't improve a thing. Hi Ralf Please try 1.9.8-3 soon when it reaches the mirrors. -- GPG/PGP ID: C0711BF1
Re: [arch-general] Issue with Jack2, ALSA or current kernels
I installed the optional dependencies. # pacman -Syu libffado dbus-core python2 Targets (4): libxml++-2.34.2-1 dbus-core-1.6.4-1 libffado-2.0.1-7 python2-2.7.3-2 Only the missing FFADO lib output disappeared, all the other output seems to be the same as before. FWIW I'll reboot, if I shouldn't write an additional mail, than the reboot didn't improve a thing.
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On 16 September 2012 21:54, Ralf Mardorf wrote: > At least I won't join IRC today. Not an issue. IRC is just "real-time" when both parties are present, that's it :) I'll do some testing as someone has reminded me of a subtle bug, which may or may not be related. -- GPG/PGP ID: C0711BF1
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On Sun, 2012-09-16 at 20:57 +0800, Rashif Ray Rahman wrote: > It would help if you could come on to IRC #jack or #archaudio so we > could troubleshoot this. I installed $ pacman -Qi xchat Version: 2.8.8-10 Install Date : Sun Sep 16 15:09:52 2012 but I guess it will driving me nuts, regarding to the odd formatting and colours of the text, when chatting in a foreign language, while thinking about a technical issue, because my visual perception of text is like this: http://www.youtube.com/watch?v=gwZLFTW4OGY Emails are well-structured and easier to read for me and at the same time while I correspond by email, I'm able to do other work I need to do. At least I won't join IRC today. Regards, Ralf
Re: [arch-general] Issue with Jack2, ALSA or current kernels
On 16 September 2012 19:34, Ralf Mardorf wrote: > Unfortunately I can't remember when it gets broken. > The Rt still is blinking when I start jackd by QJackCtl and if I play a > WAV by Audacity via Jack everything seems to be ok. Because I didn't > produce music for some time, I didn't notice the issue. Today I tied to > set up everything I need for a production and noticed it, when running > jackd by the terminal. > > :( > Ralf > Hey Ralf It has been sometime that I did anything with jack and I was also surprised when this happened. The connection did not stay up; as soon as a client connected (like mplayer) the connection stopped. This looked something like a dbus event, but the jackd binary in jack2, although coupled with jackdbus, should have no business with dbus. It did not occur to me that it might be a kernel issue. Installing standard jack solved the problem, but I had this in my TODO (since it means jack2 is basically broken, but we have not received any reports so far). It would help if you could come on to IRC #jack or #archaudio so we could troubleshoot this. -- GPG/PGP ID: C0711BF1
Re: [arch-general] Speech recognition
On Sun, 2012-09-16 at 12:33 +0200, o...@coderkun.de wrote: > I use only the acoustic model¹ of Simon. To create my grammar I > followed the guide² on Voxforge. > > > To listen to the default ALSA-input i called Julius with > > $ALSADEV="default" julius -input alsa -C ./simon.jconf Thank you :) our mail is flagged and test Julius ASAP. Unfortunately I need to fix some audio issues first. Regards, Ralf
Re: [arch-general] Issue with Jack2, ALSA or current kernels
PS: Unfortunately I can't remember when it gets broken. The Rt still is blinking when I start jackd by QJackCtl and if I play a WAV by Audacity via Jack everything seems to be ok. Because I didn't produce music for some time, I didn't notice the issue. Today I tied to set up everything I need for a production and noticed it, when running jackd by the terminal. :( Ralf
[arch-general] Issue with Jack2, ALSA or current kernels
Hi :) I noticed that audio with Jack is broken for [spinymouse@archlinux ~]$ uname -a Linux archlinux 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64 GNU/Linux and 3.4.4-rt14-1-rt [1]. Does anybody experience the same? Unfortunately I also lost my rtirq settings, that anyway might not work with the new kernels. And the error seems not be related to rtirq, but perhaps to a broken Jack, ALSA or Kernel. [spinymouse@archlinux ~]$ pacman -Qi jack2 Version: 1.9.8-2 [spinymouse@archlinux ~]$ pacman -Qil alsa-tools Version: 1.0.25-1 Regards, Ralf [1] Forwarded Message From: Ralf Mardorf To: linux-audio-u...@lists.linuxaudio.org Cc: Peter Lutek Subject: Re: [LAU] hdsp not happy with recent kernels Date: Sun, 16 Sep 2012 12:52:10 +0200 On Sat, 2012-09-15 at 10:48 -0400, Peter Lutek wrote: [snip] Peter, today I noticed that I also have issues with some of the kernels. When I claimed that all kernels are ok here, I was mistaken. For the record, rtirq isn't set up as needed, but that doesn't matter. Group audio and the security limits are set up correctly. For 3.2.0.23 everything still is ok ... ### spinymouse@precise:~$ uname -a Linux precise 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11 02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux spinymouse@precise:~$ jackd -dalsa -dhw:0 -r48000 -p64 -n2 jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 256 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 256 periods for playback ### ... but for 3.4.4-rt14 I get a strange output. [spinymouse@archlinux ~]$ uname -a Linux archlinux 3.4.4-rt14-1-rt #1 SMP PREEMPT RT Fri Jul 20 13:16:40 UTC 2012 x86_64 GNU/Linux Because it's easier to copy the whole output I started Jack by QJackCtl. 12:19:29.786 Patchbay deactivated. 12:19:29.791 Statistics reset. 12:19:29.845 ALSA connection change. Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 12:19:29.861 ALSA connection graph change. 12:19:30.894 JACK is starting... 12:19:30.895 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p64 -n2 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started 12:19:30.928 JACK was started with PID=1176. could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory could not open driver .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory jack_get_descriptor returns null for 'jack_firewire.so' could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 Jack: Create non RT thread Jack: ThreadHandler: start Jack: playback device hw:0 Jack: capture device hw:0 Jack: apparent rate = 48000 Jack: frames per period = 64 Jack: JackDriver::Open capture_driver_name = hw:0 Jack: JackDriver::Open playback_driver_name = hw:0 Jack: Check protocol client = 8 server = 8 Jack: JackEngine::ClientInternalOpen: name = system Jack: JackEngine::AllocateRefNum ref = 0 Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0 Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 64 Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackDriver::SetupDriverSync driver sem in flush mode control device hw:0 control device hw:0 audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 256 periods f
Re: [arch-general] Using install dual iso 2012-09-07 - graphics issue?
On Sat, Sep 15, 2012 at 10:04 PM, mike cloaked wrote: > On Sat, Sep 15, 2012 at 9:04 PM, Daniel Wallace > wrote: >> mike cloaked wrote: >> >>>I have made a bootable usbkey with the archlinux-2012.09.07-dual.iso >>>file but having tried to boot it, both on an Inspiron 530s and also a >>>Samsung Q35 netbook, there is a blue "graphics" screen but it does not >>>stop and offer me the choice of i686 or x86_64 but carries straight on >>>to boot to the normal prompt. So I can't choose which architecture to >>>use for the install. >>> >>>Does anyone know a workaround to be able to get to choose which of 32 >>>or 64 bit to boot for the install? Or is there a problem with this new >>>install media on some hardware? >>> >>>I have done quit a bit of reading but not seen this issue mentioned in >>>any of the arch wiki or other google searches. >>> >>>Thanks >> >> How are you putting the making the boot able media? Do not use something >> like unetbootin, it just breaks the image. Use dd if you can or make in >> manually using the instructions on the wiki. If you are on windows just use >> windows image writer. I >> Otherwise make sure you are using one of the recommended methods from the >> usb installable media Page of the wiki >> > > I did use unetbootin but was not aware that unetbootin breaks the > image! I then had to adjust the syslinux.cfg to point it at the name > of the usbkey - but I will try the dd method and see if that works > better - thought that will be tomorrow now as it is late here in the > UK now. > > Thanks - I will report back when I have had a chance to try the dd method. > I have had time to write the usbkey with the dd method and it works just fine. Additionally I have now edited the wiki at https://wiki.archlinux.org/index.php/USB_Installation_Media#UNetbootin to include a warning about unetbootin for the dual architecture install isos. If anyone feels that "any" reference to unetbootin in the wiki should be removed then please go ahead and change the wiki. -- mike c
Re: [arch-general] Speech recognition
Am Sonntag, den 16.09.2012, 03:09 +0200 schrieb Ralf Mardorf: I compiled and installed Julius from http://aur.archlinux.org/packages.php?ID=29210 and then I build Simon from https://aur.archlinux.org/packages.php?ID=14718 , but I can't install it. Did you install Julius and Simon on the same Linux install? I use only the acoustic model¹ of Simon. To create my grammar I followed the guide² on Voxforge. To listen to the default ALSA-input i called Julius with $ALSADEV="default" julius -input alsa -C ./simon.jconf ¹ http://www.repository.voxforge1.org/downloads/de/Trunk/AcousticModels/voxforge_de_simon-2010-04-21.tgz ² http://www.voxforge.org/home/dev/acousticmodels/linux/create/htkjulius/tutorial/data-prep/step-1
Re: [arch-general] IRC channel banned
On 09/16/2012 12:27 PM, Thomas Bächler wrote: > Am 16.09.2012 11:22, schrieb Arno Gaboury: >> Hi all, >> >> I just discovered this morning I can't talk on #archlinux anymore. My >> user (gabx666) is banned!! >> Never flamed or be rude, never flood, slow activity. >> >> Any idea why? How can I solve this? >> >> Thank you > > Did you identify do freenode services? Otherwise you won't be able to talk. > We just removed the restriction to avoid such issues for now, until the services are back online. -- Ionuț signature.asc Description: OpenPGP digital signature
Re: [arch-general] IRC channel banned
On Sun, Sep 16, 2012 at 11:22:11AM +0200, Arno Gaboury wrote: > Hi all, > > I just discovered this morning I can't talk on #archlinux anymore. My > user (gabx666) is banned!! > Never flamed or be rude, never flood, slow activity. > > Any idea why? How can I solve this? > > Thank you > You are not banned. freenode services are down and you can't register and people who aren't registered can't talk. They are working on getting it fixed... just wait -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology pgp0dX6wbbA1U.pgp Description: PGP signature
Re: [arch-general] IRC channel banned
Am 16.09.2012 11:22, schrieb Arno Gaboury: > Hi all, > > I just discovered this morning I can't talk on #archlinux anymore. My > user (gabx666) is banned!! > Never flamed or be rude, never flood, slow activity. > > Any idea why? How can I solve this? > > Thank you Did you identify do freenode services? Otherwise you won't be able to talk. signature.asc Description: OpenPGP digital signature
[arch-general] IRC channel banned
Hi all, I just discovered this morning I can't talk on #archlinux anymore. My user (gabx666) is banned!! Never flamed or be rude, never flood, slow activity. Any idea why? How can I solve this? Thank you
