Re: Single mouse click registers as double click
On Monday 09 May 2011 16:47, Ijon Tichy wrote: Hi again I've had this problem (a single mouse click being considered as double click) from quite a long time (almost two years) in two different computers, Thanks anyway for your replies. Cheers. Hi. I had this problem on Lenny after some updates back in May 2008, the solution for me was as below. (Quote from my previous post to the list in May 2008) A private e-mail sent to me from someone on either the Debian-User list, or the KDE list, has enabled me to resolve the mouse problem. All I had to do was edit a line in /etc/X11/xorg.conf relating to the mouse. Section InputDevice Generic Mouse Option SendCoreEvents true I changed the above line from true to false, as suggested, and now the mouse works as it always has done in the past. Having made the changes, a logout, followed by logging back in to KDE did not fix the problem. A reboot was necessary. (End quote) If you don't have an /etc/X11/xorg.conf, create the file, and just add the two lines above, making sure that the second line is changed to false. Hoping it may resolve your problem. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105091856.24166.cave.dnb2m9...@aliceadsl.fr
Re: CUPS broadcasting print queue availability
On Saturday 03 April 2010 04:10, Ron Johnson wrote: Hi, I did this once a *long* time ago, but don't remember how. Also, I've read the (seemingly relevant sections of the sorely lacking) CUPS SAM, and Googled around to no avail. Hi Ron. Can't help much on configuring the machine with the printer attached, as I had problems with cups at the time (new to linux 2003), and used the redhat config tool on FC2, and there is a checkbox on that to share the printer, but using the cups (localhost:631) web interface, you should have some option when setting up the printer on the server machine to share it. I say that because my printer.conf file on the Archlinux machine has a line as below shared No , which is correct for a machine that is printing over the LAN. Your printers.conf on the server machine should have a line Shared Yes. # Printer configuration file for CUPS v1.4.2 # Written by cupsd on 2010-04-03 10:40 # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING Printer netprinter Info epson c44ux DeviceURI ipp://192.168.0.230/printers/printer State Idle StateTime 1245182001 Type 6 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer /Printer If you have active firewalls on your machines, make sure that IPP is allowed in both directions. My server has a print queue that looks like this: $ lpstat -v device for Dell_3100cn: socket://192.168.1.11 device for dell_310...@haggis: socket://192.168.1.11 device for PDF: cups-pdf:/ The server's /etc/cups/cupsd.conf looks like: Browsing On BrowseOrder allow,deny BrowseAllow 192.168.1.0/24 BrowseAddress 192.168.1.255 BrowseLocalProtocols CUPS dnssd DefaultAuthType Basic Location / Allow from 192.168.1.* Order allow,deny /Location I created this on the client: $ cat /etc/cups/cups.conf ServerName haggis Shouldn't cups on the server (haggis) be broadcasting network messages announcing the availability of it's print queues, and shouldn't some program from cups-client be listening? Yes. On the client OS's you should see incoming packets of about 189 bytes every 30 secs. gkrellm shows these, or if you run wireshark, you should see these cups broadcasts from the machine with the printer attached. there's a bit of output from netstat -a below which shows cups listening on the client machine, which happens to be Archlinux at the moment. Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 6 @/tmp/.ICE-unix/2387 unix 2 [ ACC ] STREAM LISTENING 75386 /var/run/cups/cups.sock unix 2 [ ACC ] STREAM LISTENING 9937 @/var/run/hald/dbus-nSiy4b64JL Or do even client computers need the cups server package? Yes. I've just looked at that on Archlinux. Trying to print with the cups daemon stopped results in a can't find the printer list message, and the print button is greyed out. Also netstat -a shows no listening entry for cups. Don't know if any of the above helps. All the best. Nigel. TIA -- History does not long entrust the care of freedom to the weak or the timid. Dwight Eisenhower -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201004031117.54208.cave.dnb2m9...@aliceadsl.fr
How to save output when working in runlevel 3 (Lenny)
Hi Folks. I've got a whole bunch of updates for Lenny, including a load of X stuff, which I don't like installing while X is running. I save all the update output from the konsole in my history-files for future reference. Is there a way to save the output when working in runlevel 3? Thanks. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003171627.49211.cave.dnb2m9...@aliceadsl.fr
Re: where is the sound device in debian?
On Friday 29 May 2009 10:26, Yi Zhao wrote: hi, all, I'm using debian lenny, but I can't found /dev/dsp or /dev/audio device in /dev directory? where is it?? Try installing the oss-compat package, and they should turn up in /dev. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sound woes
On Sunday 10 May 2009 20:27, Dr. Jennifer Nussbaum wrote: And opening up a new browser, sound doesnt work in that one either. As long as the original browser is open, weather or not theres sound playing, nothing else can get sound. does that help narrow things down? One thing you could try is editing /etc/iceweasel/iceweaselrc and changing the wrapper to auto. See /usr/share/doc/iceweasel/README.Debian for more info. I don't know anything about how PulseAudio and the setting in this config file relate to each other, so sorry if this doesn't help! Im afraid that didnt help. It looks like the browser, or Flash, when it grabs the sound card, doesnt let anything else have it, weather or not its using it. If I shut the browser, then other programs can use sound, but if i keep it open, then they cant. Simple as that. I dont know if its a Pulse thing or a FireFox thing or a Flash thing. Is there any way to determine this? Jen Hi Jen. Iceweasel itself shouldn't grab the soundcard if your not on a site that uses flash for audio. If you close the webpage after listening to flash audio the soundcard is still in the being used state, correct? Try these two commands below, which should show what is using the soundcard. lsof -n | grep /dev/dsp lsof | grep /dev/snd You could also install the alsa-oss package if it's not installed, and start Firefox Iceweasel on the command line as below, which should allow you to use other sound apps. aoss firefox I don't know much about pulseaudio, except that it is known to be responsible for some problems, which is why I normally remove it, then your sound apps use alsa directly. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: need help on mp3 recording
On Tuesday 05 May 2009 17:56, Kelly Clowers wrote: On Mon, May 4, 2009 at 23:29, Long Wind longwind2...@gmail.com wrote: I have sarge or etch Which package should I install for mp3 recording? I install audacity, but it need libmp3lame.so According to tldp.org/HOWTO/MP3-HOWTO-9.html bladdenc can do the job, but which package should I install? You want libmp3lame0 from Christian Marillat's http://debian-multimedia.org repo If you don't already have it setup, instructions are on the site. The OP is using Sarge, or Etch. When Etch went stable, Christian deleted all the Sarge packages from his server. I have had a look for packages for Etch, which is now old-stable. Christian still has packages for old-stable, and stable listed, but the old-stable links point to stable/Lenny, so it looks like he's done the same as with the Sarge packages, and packages for Etch are now no longer available. It's possible the lame package for Lenny will work ok, and I'll try it myself later on, just to see. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: need help on mp3 recording
On Tuesday 05 May 2009 19:55, Nigel Henry wrote: On Tuesday 05 May 2009 17:56, Kelly Clowers wrote: On Mon, May 4, 2009 at 23:29, Long Wind longwind2...@gmail.com wrote: I have sarge or etch Which package should I install for mp3 recording? I install audacity, but it need libmp3lame.so According to tldp.org/HOWTO/MP3-HOWTO-9.html bladdenc can do the job, but which package should I install? You want libmp3lame0 from Christian Marillat's http://debian-multimedia.org repo If you don't already have it setup, instructions are on the site. The OP is using Sarge, or Etch. When Etch went stable, Christian deleted all the Sarge packages from his server. I have had a look for packages for Etch, which is now old-stable. Christian still has packages for old-stable, and stable listed, but the old-stable links point to stable/Lenny, so it looks like he's done the same as with the Sarge packages, and packages for Etch are now no longer available. It's possible the lame package for Lenny will work ok, and I'll try it myself later on, just to see. Ignore the above 2 lines, and see below. Nigel. Well I've added the repos for Etch, and Lenny to my /etc/apt/sources.list on Etch. An apt-get update with the Etch one enabled shows lame as 3.97-0.0, and enabling the Lenny one shows lame as 3.98.2-0.4, so it does appear that the packages for Etch are still available. Odd though that the links to packages for Etch/Oldstable are pointing to Lenny/Stable. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: no sound on lenny
On Friday 17 April 2009 19:03, Don Raikes wrote: Hello, I installed lenny yesterday on a desktop system I have. I installed it without a graphical desktop since I am not currently interested in anything other than console-based applications, and it is an experimental environment. After teh install, I ran: apt-get update then apt-get install alsa-oss alsa-utils alsa-tools I then ran $ alsaconf to setup my sound card (an onboard intel hda ich6 audio chipset). I looked at /etc/modprobe.d/sound, and the sound card is listed. I ran $ modprobe snd_pcm_oss I then tried running: $ aplay /usr/share/sounds/alsa/Noise.wav It says it ran, but I hear nothing out of the speakers. I then ran alsamixer and turned the volume up to 100% on everything, and reran the aplay command but still nothing. Any thoughts would be appreciated. -- Oracle http://www.oracle.com Donald Raikes | Accessibility Specialist Hi Don. Will you post the output from the following. cat /proc/asound/cards lsmod | grep snd Are you as user a member of the audio group in /etc/group ? Do you have any audio related device plugged into the USB. The USB comes up early in the boot process, and oftentimes will be set as card0, not allowing the actual soundcard to use the slot for card0, hence no sounds. Devices like usb midi keyboards, webcams, with mikes, usb headphones, etc, can cause such problems. Have a look in alsamixer for audio loopback sliders/switches. I have seen that when these are unmuted on some soundcards, there is no sound output. If they exist for you, try muting them (the M key does the mute/unmute). Just a thought. Which make/model of PC? Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: no sound on lenny
On Friday 17 April 2009 21:05, you wrote: Nigel, Ok here you go: type of system: gateway 7200X CTO desktop pentium II 3.0ghz 4 gb ram 250 gb harddrive output from cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0x9220 irq 16 output from lsmod | grep -i 'snd' : snd_hda_intel 325688 6 snd_pcm62596 3 snd_hda_intel snd_seq41456 0 snd_timer 17800 4 snd_pcm,snd_seq snd_seq_device 6380 1 snd_seq snd45604 13 snd_hda_intel,snd_pcm,snd_seq,snd_timer,snd_seq_device soundcore 6368 1 snd snd_page_alloc 7816 2 snd_hda_intel,snd_pcm I used alsamixer and sure enough everything was muted, but I unmuted master, pcm, front side and surround lfe ... everything except for the microphone and capture stuff since I don't have a mic at all. still nothing. You appear to be missing some modules which should be loaded as below snd-pcm-oss snd-mixer-oss snd-seq-oss Open synaptic as root on the CLI, and see if the oss-compat package is installed, if not, install it, then reboot, and see if sounds now work. Your lsmod | grep snd should now show the above modules loaded in addition to the previous modules, and perhaps now the sound is working. Post back the latest output from, lsmod | grep snd Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: no sound on lenny
On Friday 17 April 2009 23:09, you wrote: Nigel, Ok, thanks. I installed the oss-compat package, and rebooted. This time I heard the speaker pop, at least. When I ran aplay again still no sound. I double-checked my mute status and volume levels again in alsamixer and everything looks fine. Output from new lsmod is as follows: snd_hda_intel 325688 6 snd_pcm_oss32832 0 snd_mixer_oss 12320 1 snd_pcm_oss snd_pcm62596 4 snd_hda_intel,snd_pcm_oss snd_seq_dummy 2660 0 snd_seq_oss24992 0 snd_seq_midi5728 0 snd_rawmidi18528 1 snd_seq_midi snd_seq_midi_event 6432 2 snd_seq_oss,snd_seq_midi snd_seq41456 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 17800 4 snd_pcm,snd_seq snd_seq_device 6380 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 45604 17 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd _seq,snd_timer,snd_seq_device soundcore 6368 1 snd snd_page_alloc 7816 2 snd_hda_intel,snd_pcm A pop is a good start. Are you sure that alsamixer shows no analog loopback controls? If they are there, mute them. Which desktop are you using? KDE, or Gnome. I ask because Kmix is known to mess the mixer settings up when logging in. Mind you, if you have opened alsamixer on the CLI once logged in, and checked settings, that should have overidden any problem there. I'll come back tomorrow, as it's getting late. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Missing dependencies of soundtracker
On Tuesday 14 April 2009 00:24, Florian Kulzer wrote: On Sun, Apr 12, 2009 at 22:22:24 +0200, Nigel Henry wrote: On Sunday 12 April 2009 20:51, Florian Kulzer wrote: On Sun, Apr 12, 2009 at 18:07:03 +0200, Marcin Kłapkowski wrote: Florian Kulzer pisze: On Sun, Apr 12, 2009 at 16:00:14 +0200, Marcin Kłapkowski wrote: Hi, I would like to install soundtracker (it's one of the best tracker I've heard and used before). I'm using sid, and in repo there is version 0.6.8-2+b1 of soundtracker. But, I get missing dependencies: [...] You could also try the soundtracker-gtk2 package mentioned in bug #519641. [...] I have have no idea if the soundtracker program itself will still work - see also Nigel's earlier message about its state on Lenny - and keeping soundtracker installed and running on Sid will probably become more and more difficult as Sid evolves further and further away from Lenny. [...] I've just booted up my Etch install, which is on the same machine as Lenny.and soundtracker works ok, without any problem on Etch. It appears to be an earlier version of Soundtracker though (0.6.8-2 (stable)). The soundtracker project seems to be dead upstream since 2006 and it needs GTK1. I can see why a maintainer would lose interest. I suppose we could always install soundtracker from a source tarball. I've dealt with dependency hell before, and it's not a lot of fun, but sometimes with a bit of help from the lists, you can get the app up, and running. I just tried to build the GTK2 version from Barry deFreese's updated version of the source package. The build did not succeed; I suspect that might be due to my system being 64bit. I cannot invest more time in this problem; you can try your luck yourself: dget http://people.debian.org/~bdefreese/soundtracker_gtk2/soundtracker_0.6.8.gt k2.20080114-0.1.dsc cd soundtracker-0.6.8.gtk2.20080114/ dpkg-checkbuilddeps debian/control dpkg-buildpackage -rfakeroot -us -uc cd .. (You will need the packages build-essential and devscripts, as well as all missing dependencies listed by dpkg-checkbuilddeps.) If you succeed in building this package, at least on i386, then it might be easier to convince the maintainer to keep the package alive. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | Hi Florian. This is a bit odd, as I've got libgtk1.2 on my Lenny install, although as I said, my Lenny originally started off as Woody 3.0r2, and perhaps that's why I still have libgtk1.2. Now soundtracker version 0.6.8-2+b1 will not start on Lenny, apart from a glimpse of the Soundtracker splash screen. On Ubuntu Intrepid 8.10, which uses the same soundtracker version, but named as 0.6.8-2build1, and again libgtk1.2 is installed, soundtracker starts ok with no problems. If Soundtracker works on Ubuntu Intrepid, logically it should be working on Lenny, as both Soundtracker versions appear to be the same. I compared all the deps between Ubuntu Intrepid, and Lenny, and the only diffs were as follows. Intrepid: libdb4.6, and Lenny: libdb4.5 Intrepid: libesd-alsa0 (installed) alternative libesd0 (not installed) Lenny: libesd0 (installed) alternative libes-alsa-0 (not installed) Running Soundtracker on Lenny from the CLI, I get this output below, and obviously Soundtracker doesn't open. djm...@debian:~$ soundtracker Gdk-WARNING **: locale not supported by C library Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) serial 103 error_code 9 request_code 145 minor_code 5 Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0xb7613767] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb761381e] #2 /usr/lib/libX11.so.6 [0xb7b3bde9] #3 /usr/lib/libX11.so.6(XDeleteProperty+0x25) [0xb7b12335] #4 /usr/lib/libgdk-1.2.so.0(gdk_set_sm_client_id+0x62) [0xb7c0c3b2] #5 /usr/lib/libgnomeui.so.32 [0xb7e199c5] #6 /usr/lib/libgtk-1.2.so.0(gtk_marshal_NONE__NONE+0x16) [0xb7cdccf6] #7 /usr/lib/libgtk-1.2.so.0 [0xb7d110f2] #8 /usr/lib/libgtk-1.2.so.0 [0xb7d137c3] #9 /usr/lib/libgtk-1.2.so.0(gtk_signal_emit+0x138) [0xb7d13e08] #10 /usr/lib/libgnomeui.so.32(gnome_client_disconnect+0xe6) [0xb7e17276] #11 /usr/lib/libgnomeui.so.32 [0xb7e17388] #12 /lib/i686/cmov/libc.so.6(exit+0x89) [0xb77a1ab9] #13 /usr/lib/libgdk-1.2.so.0 [0xb7c0d495] #14 /usr/lib/libX11.so.6(_XError+0xd9) [0xb7b347d9] #15 /usr/lib/libX11.so.6 [0xb7b3c798] #16 /usr/lib/libX11.so.6(_XReply+0x15a) [0xb7b3cb4a] #17 /usr/lib/libX11.so.6(XQueryExtension+0xa7) [0xb7b29da7] #18 /usr/lib/libX11.so.6(XInitExtension+0x41) [0xb7b1e351] #19 /usr/lib/libXrender.so.1(XRenderFindDisplay+0x16d) [0xb7ef317d] Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) serial 104 error_code 9 request_code 55 minor_code 0 djm...@debian:~$ There is clearly some problem showing on the above output, which is causing soundtracker to crash as it starts to try and draw the window
Re: what does kept back mean when do apt-get upgrade?
On Tuesday 14 April 2009 16:52, Stefan Monnier wrote: I often see that some packages are kept back when I do apt-get upgrade, what does it mean? It means that there are newer versions of those packages available, but apt-get refrained from upgrading them. The reasons for that can be that in order to upgrade those packages, apt-get would need to add or remove some other packages. Stefan I remember a while back that Rosegarden was held back for about 6 weeks. that was on Lenny, and I always do an apt-get dist-upgrade. I think that sometimes the problem is, as in the Rosegarden case, that dependencies for Rosegarden need to be upgraded before the Rosegarden version that is being held back, can be installed. The way this seemed to work out, was that the currently installed Rosegarden version would continue to work, then when the needed upgrades for dependencies for the held back new Rosegarden version were available, then, and only then would the held back version of Rosegarden be installed, along with the upgraded dependencies for Rosegarden. Don't know if that makes sense, but it seemed to be the way it worked for me. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Missing dependencies of soundtracker
On Sunday 12 April 2009 16:00, Marcin Kłapkowski wrote: Hi, I would like to install soundtracker (it's one of the best tracker I've heard and used before). I'm using sid, and in repo there is version 0.6.8-2+b1 of soundtracker. But, I get missing dependencies: # sudo apt-get install soundtracker ... Następujące pakiety mają niespełnione zależności: soundtracker: Wymaga: gdk-imlib11 ale nie da się go zainstalować Wymaga: libart2 (= 1.2.13-5) ale nie da się go zainstalować Wymaga: libgdk-pixbuf2 (= 0.22.0) ale nie da się go zainstalować Wymaga: libgnome32 (= 1.2.13-5) ale nie da się go zainstalować Wymaga: libgnomesupport0 (= 1.2.13-5) ale nie da się go zainstalować Wymaga: libgnomeui32 (= 1.4.2-3) ale nie da się go zainstalować Wymaga: libgtk1.2 (= 1.2.10-4) ale nie da się go zainstalować None of these packages can be installed. For this packages I had only configuration files (c in aptitude, instead of i). And when I removed it's configuration files, I discovered that they not exists in repo any more. I have in my system installed other similar packages: libart-2.0-2 libartsc0 libgnomeui-0 libgnomeui-common Installing libart2-ruby and libgdk-pixbuf2-ruby don't change situation. My etc/apt/sources.list: deb http://ftp.pl.debian.org/debian/ sid main non-free contrib deb-src http://ftp.pl.debian.org/debian/ sid main deb http://www.debian-multimedia.org/ sid main deb-src http://www.debian-multimedia.org/ sid main deb http://thomas.pub.enix.org/debian/ sid main How I can install missing dependencies or newer version of soundtracker? Thanks for any help. martin3z That's a bit odd. I've just fired up Lenny, and see that I have the same Soundtracker version installed that you mention above. My Lenny started off as Sarge, upgraded to Etch, and is currently Lenny. I first installed Soundtracker on 5-June-2005 (version 0.6.7-5). Not sure which Debian version it was installed on back then (probably Sarge), but synaptic's history shows no deps being installed for it at the same time, and it would have been working then, as I installed it to use it. The current version I have on Lenny (0.6.8-2+b1) is quite old. I've looked back through my history-files for updates, and have found Soundtracker being updated to the version above on 24:August:2007. Whether it still worked after the updates at that time, I don't know, because I don't try everything to see if it still works. It possibly did still work, but a lot of time has passed since then, and I think that what has happened is that one, or more of dependencies for Soundtracker has been updated, and now Soundtracker, as in your case will not install. I've just tried Soundtracker on Lenny, and it tries to open. I get a quick glimpse of a small window trying to open (not the main window for Soundtracker) then it crashes. I think there is a problem with something to do with the graphics, as if I ssh into Lenny from another machine (FC2), and run Soundtracker, it works as it should. I'm listening to DJC_LOTHXM at the moment, using Lenny's Soundtracker, but running it from FC2, while ssh'd into Lenny. I think it's about time we should both post a bugreport that soundtracker is broken due to dependency problems. Hope we can get it fixed. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Missing dependencies of soundtracker
On Sunday 12 April 2009 20:51, Florian Kulzer wrote: On Sun, Apr 12, 2009 at 18:07:03 +0200, Marcin Kłapkowski wrote: Florian Kulzer pisze: On Sun, Apr 12, 2009 at 16:00:14 +0200, Marcin Kłapkowski wrote: Hi, I would like to install soundtracker (it's one of the best tracker I've heard and used before). I'm using sid, and in repo there is version 0.6.8-2+b1 of soundtracker. But, I get missing dependencies: [...] How I can install missing dependencies or newer version of soundtracker? Right now it might still be possible to install the package if you add both testing and stable to your sources list (and run apt-get update afterwards). You could also try the soundtracker-gtk2 package mentioned in bug #519641. soundtracker-gtk2 wasn't installed, because of dependency lack: gtk+-2.0 but, after adding lenny repo as you told me, i have possibility to install soundtracer with whole gtk1.2 dependencies. great, but din't it harm my system? and should i add lenny updates to it or not? i worry about packages conflicts too. I don't think you will harm your system; however, make sure that you have the Lenny security updates in your sources list as well. I have have no idea if the soundtracker program itself will still work - see also Nigel's earlier message about its state on Lenny - and keeping soundtracker installed and running on Sid will probably become more and more difficult as Sid evolves further and further away from Lenny. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | Hi Florian. I've just booted up my Etch install, which is on the same machine as Lenny.and soundtracker works ok, without any problem on Etch. It appears to be an earlier version of Soundtracker though (0.6.8-2 (stable)). Perhaps I should contact the Soundtracker maintainer who appears to be: Junichi Uskawadan...@debian.org It's a shame when the authors/maintainers of packages have lost interest in providing support for the packages that they have been maintaining. I suppose we could always install soundtracker from a source tarball. I've dealt with dependency hell before, and it's not a lot of fun, but sometimes with a bit of help from the lists, you can get the app up, and running. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: More Problems configuring sound card with alsa on debian
On Thursday 09 April 2009 22:30, Dancing Fingers wrote: On Apr 8, 12:00 pm, Nigel Henry cave.dnb2m9...@aliceadsl.fr wrote: Many thanks Nigel for your eply. On Wednesday 08 April 2009 14:56, Dancing Fingers wrote: Hi guys, I'm also having an ALSA problem. I put a SoundBlaster card in my Lenny box. If I run alsaconf every time I boot and everything works fine. What I don't understand is why the system resets the conf files every time it boots? Thanks. Chris Hi Chris. I assume there is an onboard soundcard on the machine as well. What may be happening when you boot up is that both soundcards are being detected, and the onboard soundcard is being set as card0, and the audigy one as card1. Most audio apps use card0 as default, so you may find that plugging the speakers into the onboard soundcard (if there is one) produces sound. To check this out, reboot, then run the following command before running alsaconf, and post the results. cat /proc/asound/cards This is what I get: 0 [V8235 ]: VIA8233 - VIA 8235 VIA 8235 with CMI9761A+ at 0xd800, irq 22 Then run alsaconf, and set up the audigy card, then run the command above again, and post the results. If what I say above is the case, and you want the audigy soundblaster to be set as card0 (the default), you can add a couple of lines to the bottom of: to /etc/modprobe.d/alsa-base options snd-emu10k1 index=0 options snd- index=1 What I tried was: options snd-emu10k1 index=0 options snd-V8235 index=1 Here you want the following options lines. options snd-emu10k1 index=0 options snd-via82xx index=1 Change your current options lines in /etc/modprobe.d/alsa-base to those above, then reboot, and post the output of, cat /proc/asound/cards. The sounds may now be working, but you may have to access alsamixer on the CLI (KDE's Konsole, or Gnomes Terminal), to see if some controls are muted, and unmute them. The M key does the mute/unmute. On my Audigy2 soundblaster card, controls, Master, PCM, Front, need their sliders pushed up to get sound output. Check also the Audigy A control. Mine needs to be muted to get analog output, and sounds. That is on Lenny. Let's get the sounds working, eh!! Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: More Problems configuring sound card with alsa on debian
On Wednesday 08 April 2009 14:56, Dancing Fingers wrote: Hi guys, I'm also having an ALSA problem. I put a SoundBlaster card in my Lenny box. If I run alsaconf every time I boot and everything works fine. What I don't understand is why the system resets the conf files every time it boots? Thanks. Chris Hi Chris. I assume there is an onboard soundcard on the machine as well. What may be happening when you boot up is that both soundcards are being detected, and the onboard soundcard is being set as card0, and the audigy one as card1. Most audio apps use card0 as default, so you may find that plugging the speakers into the onboard soundcard (if there is one) produces sound. To check this out, reboot, then run the following command before running alsaconf, and post the results. cat /proc/asound/cards Then run alsaconf, and set up the audigy card, then run the command above again, and post the results. If what I say above is the case, and you want the audigy soundblaster to be set as card0 (the default), you can add a couple of lines to the bottom of: to /etc/modprobe.d/alsa-base options snd-emu10k1 index=0 options snd- index=1 The above is assuming that your soundblaster is using the snd-emu10k1 driver, but may be snd-ca0106. The snd- is the unknown driver for the onboard card (if that exists). Just change that to whatever the driver is (maybe snd-hda-intel, as a guess). Now reboot, and see if you have sounds on the soundblaster (without running alsaconf), and run cat /proc/asound/cards again, where you should see the soundblaster as card0, and the onboard card as card1. If you do have 2 soundcards you can open alsamixer on the CLI as below to access the controls for each card. alsamixer -D hw:0 alsamixer -D hw:1 Would you post the output from the following, as well please. lsmod | grep snd All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: thanks (ntp problems)
On Sunday 26 April 2009 00:09, leo wrote: thanks for the info but I can't access internet ntp servers from my LAN Well you havn't quoted what info you were given. That aside, ntp uses port 123 UDP, so make sure it's open, outgoing to the Internet. Alternatively, if you have ntpdate installed, it will use an alternative port with the following command as root. ntpdate -u ntp.obspm.fr Just change the server name ntp.obspm.fr for one of yours. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: testing microphone - how?
On Tuesday 24 March 2009 18:51, Lisi Reisz wrote: On Tuesday 24 March 2009 17:21:06 Thorny wrote: On Tue, 24 Mar 2009 11:26:33 +, Lisi Reisz posted: I am trying to test a microphone by some method other than ringing the same poor person repeatedly by VOIP. I have tried to run record applications, but cannot seem to get the applications going (so far Audacity and KRec). Hi Lisi, Hi, Thorny, This sounds interesting. Why can't you get them going I have no idea - I have never used either but would like them to try and record something so that I can test the mike. and what do you mean by going? I can't persuade them to do anything recognisable to me. But then I have never before tried to use a mike on a computer. All I want to use it for now, is to use Twinkle to make telephone calls. But I so far only have one SipGate number - and there is a limit to how often I feel able to make the poor chap on the other end of it carry on a one-sided conversation. I suppose you've already checked in your mixer that mic input isn't muted, eh? Yes. Everything is on maximum in KMix, and I tried to set capture and +20 and various other bits in alsamixergui. Not very successfully because I can't make sense of the colours and symbols and alsamixer doesn't go in for words much. :-( I shall persue this line a bit more. What is your soundcard, Card: NVidia nForce2, chip: Realtek ALC650F any known issues with it with Lenny, if that is what you use? D'oh! I haven't checked. Everything else I have thrown at it has Just Worked, including the earphone part of this headset. I did have to adjust the mixer settings to get it to work, way back in the mists of time when I first went from Etch to Lenny, tho' it had worked fine in Sarge and Etch. And I have just finally found the thread about this from when it happened, and have not yet worked thro' it all. I was looking on the wrong list - it was on Debian Women, not here. But I have recently reinstalled Lenny, and deliberately lost all my config files (It's a long story.) and audio is working fine still. ALSA working fine for other sounds on your system? See above. No problems at all with playing sound - and I actually think that it may now (after my last lot of fiddling) be transmitting/recording sound. I just need to test it somehow! While sparing my poor friend - I don't want him to become an ex-friend. ;-) I have yet to try Sinan Can İmamoğlu's suggestions, tho' I shall certainly do so. TIA Lisi Hi Lisi. I have used Krecord before, but you have to check the full duplex box in KDE's control centre Sound Multimedia Sound System Hardware, and that'assuming that the KDE sound server is running, otherwise the full duplex checkbox is greyed out. Personally I use MhWaveedit for recording. Normally I compile it from source, but it is available on some Debian based installs from their repo's. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Light-weighted voice recorder
On Saturday 31 January 2009 19:40, T o n g wrote: Hi I'm looking for a light-weighted voice recorder (for quick note taking). I've tried most of the CLI tools, the problem is that none of them have the pause feature that I need during recording. I also know many others, http://xpt.sourceforge.net/techdocs/media/audio/ad04-SoundRecording/ but haven't find a good (simple) one yet. E.g, I know that Audacity is the tools, but it is too heavy-weighted for quick voice note taking: multi-track audio editor, digital effects, etc. In brief, I hope there is a tools like window sound recorder, which is as simple as possible, but can let me pause during recording. Thanks Hi Tong. MhWaveedit perhaps. I think it's available from the repo's, and does have pause/resume for recording. Link below if it's not available from the repo. https://gna.org/projects/mhwaveedit/ All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: portaudio2/device busy?
On Sunday 25 January 2009 17:21, Tamas Hegedus wrote: Nigel Henry wrote: I assume that you had installed pulseaudio at some time or other, to try it Yes, I installed it myself. Since when I was fighting to set up my audio, at a point I red that I need a sound server. So I installed it and the sound was working on my linux box. Installing the sysv-rc-conf package could help. run it as root on the command line, and you can disable pulseaudio (for example), which saves having to kill it, each time you boot up. After I killed pulseaudio: However, 'espeak' was working, I got the message that can not connect to pulseaudio. So last night I thought I do not need pulseaudio, so I simply removed it. Rebooted. But now still everything complains that can not connect to pulseaudio and no sound at all. I tried to google and find a site where I can understand the sound architecture of Linux (not ALSA - but the whole picture), but I could not find anything. So I do not know now how to proceed. Can you suggest something to read/learn? And also something how to solve the situation: * having a soundserver (pulseaudio? or should I use esound?) for the common sound applications * having espeak to work - w/o a soundserver (wrapping around it to avoid the server layer) I have tried aoss - it was working for 'aoss flite -t test sound' (flite needs oss) but not for 'aoss espeak test sound'... Thanks again, tamas Hi Tamas. You should not need to use any sound servers, whether ESD, aRts (KDE), or Pulseaudio, to just use audio apps. Most audio apps will use Alsa directly without any sound server entering the equation. If you have audio apps that are OSS based, you will need to install the package alsa-oss. let's go back to Pulseaudio. On some distros it's installed as default, and I've seen quite a few folks having problems with it. On Fedora, it's easy enough to disable, by removing the package alsa-plugins-pulseaudio, then all the audio apps use alsa directly. Debian based installs are different, and that package does not exist. I've seen that the correct way is do the following to get rid of pulseaudio from a debian install. I use apt, not aptitude, so this is the apt-get command below. apt-get remove pulseaudio --purge Also open synaptic as root, and check to see if any pulseaudio stuff is still installed. If there are any pulseaudio packages still installed, be carefull about just going ahead and removing them, as some want to remove other packages as deps, which may screw things up completely. Also have a look in your home/user directory. You may find pulseaudio stuff there. It's safe to just delete it. I only see one on my Ubuntu Intrepid 8.10 install. it's a hidden file named as .pulse. To show hidden files go to View in the file browser, and check Show Hidden Files. I've just opened synaptic on my Lenny install, and checked to install pulseaudio. I've not gone ahead with it, as I don't want pulseaudio, but this is what synaptic is going to do. See below. To be removed esound To be installed gnome-audio gstreamer0.10-pulseaudio libasound2-plugins libgconfmm-2.6-1c2 libglademm-2.4-1c2a libpulse-browse0 libpulse-mainloop-glib0 libpulsecore5 padevchooser paman paprefs pavucontrol pavumeter pulseaudio-esound-compat pulseaudio-module-gconf pulseaudio-module-hal pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils It may be worth looking in synaptic to see if any of these packages are still installed since you removed pulseaudio, and if so remove them. Also re-install the esound package, although I'd disable it post install in Gnomes sound settings. Again. You should not need any specific sound servers to be installed to use audio apps. All audio apps should be able to use Alsa directly. The exception may may be audio apps that are OSS based, but installing the alsa-oss package should handle those. Of course you could always just reinstall Lenny, and start afresh, but I don't like to suggest that, as it sounds too much like what is suggested when a Windows install screws up. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: portaudio2/device busy?
On Saturday 24 January 2009 07:06, Tamas Hegedus wrote: Hi, I would like to use espeak (text to voice application). I got error the error messages below. It was reported that several years ago it was a segmentation fault of portaudio19 (segmentation fault if device is busy; espeak uses libportaudio2). Later on the same messages are emitted I get. But I can not find any solution for this (I goggled). Any idea? Thanks in advance, tamas espeak this is a test Expression 'parameters-channelCount = maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 924 Expression 'ValidateParameters( outputParameters, hostApi, StreamDirection_Out )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1142 Expression 'parameters-channelCount = maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 924 Expression 'ValidateParameters( outputParameters, hostApi, StreamDirection_Out )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1142 wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) wave_open_sound Pa_OpenStream : err=-9996 (Invalid device) Hi Tamas. I've just installed espeak on my Lenny install, and it plays the this is a test with no problems. Mind you the sound card on the machine that Lenny's installed on, is an audigy2 soundblaster, which is capable of playing multiple audio streams. Which sound card do you have? cat /proc/asound/cards should give enough of an indication. If you're using Gnome, it may be worth shutting down ESD in Gnomes sound settings, or if using KDE, like me, shut down the aRts sound server, then try the espeak test line again. It could be that portaudio is having a problem, if another soundserver is running, and with a card not capable of playing multiple audio streams. I've also just installed it on another machine with an hda intel card, on both Etch, with the aRts soundserver running on KDE, and Kubuntu Intrepid, and both play the test ok. Which kernel are you using on Lenny? uname -r Which alsa driver version? cat /proc/asound/version Anything else using the sound when you run the espeak test, which may be stopping you hearing sound? lsof -n | grep /dev/dsp lsof | grep /dev/snd Did you install espeak, and it's deps from the Lenny repo, or from a source tarball? I assume that the sounds are working, apart from espeak. You no doubt are, but verify you are a member of /etc/group/audio, if there are general sound problems as user. Can't think of much else at the moment. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: portaudio2/device busy?
On Saturday 24 January 2009 18:12, Tamas Hegedus wrote: Hi, I stopped pulseaudio. BTW: This did not work /etc/init.d/pulseaudio stop I had to use 'kill'. And 'espeaks' works! Could you see my other thread - problem with my other computer's sound system. Re: sound card not detected You seem an audio expert! Thanks a lot! tamas Hi Tamas. When I saw your error messages when trying to run the espeak test, and they mentioned pa, I instantly thought that it was a pulseaudio problem, but then realised that pulseaudio is not installed as default on Lenny (at least not on my Lenny, which started off as a Woody install), so I then presumed that pa referred to portaudio, but it seems that it was actually referring to pulseaudio. I assume that you had installed pulseaudio at some time or other, to try it out, and I see that it's available for Lenny. Pulseaudio does appear to have some problems, as I've seen on other mailing lists. Myself, I have disabled it on my Fedora installs, and the only install where it still is installed is on an Ubuntu Intrepid 8.10. I'll try installing espeak on that, and see if I have the same problems as you had. Ok. I've just installed espeak on my Ubuntu install, which is using pulseaudio, and no sound output from the espeak test, and similar error messages to yours, but I do also have the Orca program installed, which is playing back text to speech, so perhaps Orca is grabbing the soundcard, which would explain why I get no sound output from espeak. So next I quit Orca, and try the espeak test again, which plays back the text ok. Pulseaudio is still up and running, but no problem with espeak on Ubuntu Intrepid 8.10. Perhaps it's a newer version of pulseaudio, which has resolved some earlier problems with portaudio. Installing the sysv-rc-conf package could help. run it as root on the command line, and you can disable pulseaudio (for example), which saves having to kill it, each time you boot up. I'll look at your other thread, but I'm no sound expert. I've just had a certain degree of success in helping some folks to get their sound working. Sometimes it's just giving some pointers, and they've done the rest. Nice you've got espeak working now. I don't see Orca in Lenny's repo, but it seems to work ok on Ubuntu Intrepid 8.10. You may have too look for a tarball. I'll take that back as it appears to be the package gnome-orca , and I see that package in synaptic on Lenny. There are a few deps to be installed, and I'm currently installing gnome-orca to see if it works the same as on Ubuntu Intrepid 8.10. I'm not blind, or sight impaired, apart from needing glasses to focus properly on what I'm reading, but it could always get worse I suppose. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
No sound on HP dv4
Repost of info posted on the /dev/sndstat thread by s. keeling. I'm just adding my similar situation. It's an HP dv4 AMD Turion dual core. I've not heard a peep of sound from it yet. Linux newmil 2.6.28-0.slh.11-sidux-amd64 #1 SMP PREEMPT Thu Jan 15 22:48:01 UTC 2009 x86_64 GNU/Linux. Kernel is stock Sidux. $ lspci | grep Audio 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller Why are there two? The first is for your actual soundcard, and the the second appears to be a sound component on the graphics card for HDMI. Both from a bit of googling appear to use the snd-hda-intel driver, but as your lsmod below shows, the snd-hda-intel module isn't loaded. Please go to the bottom of the post for some suggestions, which may, or may not work, but are worth trying. $ lsmod | grep snd snd_seq_oss37760 0 snd_seq_midi 11648 0 snd_rawmidi29568 1 snd_seq_midi snd_seq_midi_event 12544 2 snd_seq_oss,snd_seq_midi snd_seq62048 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 28304 1 snd_seq snd_seq_device 12180 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd73800 5 snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 12960 1 snd # cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.18rc3 emulation code) Kernel: Linux newmil 2.6.28-0.slh.11-sidux-amd64 #1 SMP PREEMPT Thu Jan 15 22:48:01 UTC 2009 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: --- no soundcards --- Audio devices: NOT ENABLED IN CONFIG Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 31: system timer Mixers: NOT ENABLED IN CONFIG $ lspci -v -s00:06.1 (0) newmil [root] /root_ lspci -v -s00:14.2 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Hewlett-Packard Company Device 30fb Flags: slow devsel, IRQ 16 Memory at d250 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Kernel modules: snd-hda-intel (0) newmil [root] /root_ lspci -v -s01:05.1 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller Subsystem: ATI Technologies Inc RS780 Azalia controller Flags: fast devsel, IRQ 19 Memory at d241 (32-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Kernel modules: snd-hda-intel First try loading the snd-hda-intel module as root. See below. modprobe snd-hda-intel If you are just returned to the prompt, then run, lsmod | grep snd again, and see if the snd-hda-intel module is listed. If modprobe complains that it can't load the module, it could possibly be due to the fact that both the soundcard, and the sound component in the graphics card for HDMI, are both using snd-hda-intel, and there is some sort of conflict. if the modprobe snd-hda-intel does result in the module showing up in lsmod's output, add snd-hda-intel to /etc/modules. Reboot, and run lsmod | grep snd, and see if the snd-hda-intel module is there. Then run the commands below. cat /proc/asound/cards grep ^Codec /proc/asound/card?/codec* I don't expect much success from my suggestions above, so let's try this. Having removed the line for snd-hda-intel from /etc/modules, add this line to /etc/modprobe.d/alsa-base. See below. options snd-hda-intel probe_mask=1 This option will select only the first codec (the one for your soundcard), and ignore the one for the RS780 Azalia controller one, which also uses snd-hda-intel, and may be causing a problem. Having set the above options line, reboot, and run the following commands again. lsmod | grep snd cat /proc/asound/cards grep ^Codec /asound/card?/codec* I doubt whether any of this is going to get the sounds working, but worth a try. Please post back all the output from the commands. Is the HP dv4 a new machine? It's possible it's not supported yet with alsa. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /dev/sndstat
On Monday 19 January 2009 19:30, s. keeling wrote: Ron Johnson ron.l.john...@cox.net: On 01/11/09 22:34, M. Lewis wrote: Ron Johnson wrote: On 01/11/09 21:55, M. Lewis wrote: I'm just adding my similar situation. It's an HP dv4 AMD Turion dual core. I've not heard a peep of sound from it yet. Linux newmil 2.6.28-0.slh.11-sidux-amd64 #1 SMP PREEMPT Thu Jan 15 22:48:01 UTC 2009 x86_64 GNU/Linux. Kernel is stock Sidux. To s.keeling (first name unknown). Would you start a new thread for your sound problem please, as you have highjacked Mike Lewis's thread with a new, and possibly unrelated sound problem. It can be difficult enough dealing with one sound problem, without two possibly unrelated ones running in the same thread, with the resulting confusion of trying to deal with two problems at the same time. I'm not a sound guru, but I, and am sure others will look at your problem in your newly created thread, and see if it can be resolved. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: CMI8738 sound card - cannot hear sound in Lenny - SOLVED
On Saturday 17 January 2009 16:37, Robert Canner wrote:
On Sat, 2009-01-17 at 00:07 +0100, Nigel Henry wrote:
On Friday 16 January 2009 22:04, Robert Canner wrote:
I've unmuted the Synth control in alsamixer, but I still can't hear any
sound :-(
Alsamixer now shows:
Master = 100,100 (but no mute/unmute box is shown)
3D Control = unmuted
PCM, Synth, Line, CD, Aux = 100,100, unmuted
Line-In= Rear Output
Mic= 0, muted
Mic Boost = muted
Phone, PC Speaker = 100, unmuted
IEC958 {5V, Copyright, In Monitor,
In Phase Inverse, In Select, In Valid, Loop,
Mix Analog, Output} = unmuted
Exchange DAC, Four Channel Mode = unmuted
By the way, alsamixer is not displaying any mute/unmute box for the
Master control. Should I worry about this?
No. My alsamixer on lenny shows no mute/unmute box, but it's a different
soundcard (Audigy2 soundblaster), and my alsamixer version shows as
1.0.16. My alsa-utils package is 1.0.16-2, and that provides alsamixer,
and other stuff.
(By comparison, the Wikipedia screenshot
http://en.wikipedia.org/wiki/File:Alsamixer.png shows a mute/unmute box
for the Master control. My Lenny box is using alsamixer v1.0.13.)
That .png for alsamixer on the wiki is for a different soundcard than
yours, and all alsamixer controls are different, depending on your
soundcard, so I'd ignore that.
It doesn't help that I'm unfamiliar with your C media soundcard, so I'm a
bit in the dark. Are there any switches showing on your alsamixer? For
example on mine for the audigy2 soundblaster card there is a switch to
change from analogue to digital output. If this is set to digital, I get
no sound, but toggling it to analog brings the sounds up.
Perhaps you could post the output from running amixer on the CLI, just to
see what controls you have available.
Someone else who is also using a C media card on Lenny, may also have
some suggestions, that may resolve your problem.
Alternatively, there is the alsa-user mailing list, and someone there may
have specific knowledge of known problems, and fixes for your card.
All the best.
Nigel.
Thanks Nigel, your clue about switches in alsamixer has done the trick.
I tried the following changes, testing each with speaker-test:
mute '3D Control' -- still no sound
change 'Line-In Mode' to 'Line In' -- still no sound
mute 'Exchange DAC' -- pink noise heard on earphones :-)
At this stage, CD playback was audible, but highly distorted. Curious
about 'Exchange DAC', I Googled and found
https://www.linuxquestions.org/questions/linux-hardware-18/c-media-cmi8738-
chipset-no-sound-267807/ which also mentioned deselecting 'IEC958 Output'.
So in alsamixer I tried muting 'IEC958 Output', which removed the
distortion. Brilliant!
For the record, here's my amixer output after fixing the problem:
snip
Once again, many thanks,
Robert
Hi Robert.
Great that the problem is resolved, and happy to have helped. Keep a written
note of the fixes, as you may need them again.
All the best, and enjoy the sounds.
Nigel.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: CMI8738 sound card - cannot hear sound in Lenny
On Friday 16 January 2009 14:13, Robert Canner wrote: On Fri, 2009-01-16 at 01:04 +0100, Nigel Henry wrote: On Friday 16 January 2009 00:10, Robert Canner wrote: Hi folks, I've installed a CMI8738 PCI sound card (C-Media 8738) on my dual-boot machine. When I boot Windows, I can hear sound, but when I boot GNU/Linux, I can't hear any sound. [... snip ...] == $ uname -a Linux mercury 2.6.18-6-686 #1 SMP Fri Dec 12 16:48:28 UTC 2008 i686 GNU/Linux == $ groups robert dialout cdrom floppy audio video plugdev netdev powerdev == $ lspci -v ... 02:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Flags: bus master, medium devsel, latency 32, IRQ 209 I/O ports at b800 [size=256] Capabilities: access denied == $ cat /proc/asound/cards 0 [CMI8738]: CMI8738 - C-Media PCI CMI8738 C-Media PCI CMI8738 (model 37) at 0xb800, irq 209 [ ... snip ...] Hi Robert. Well the cards being detected according to /proc/asound/cards, and you're a member of the audio group. The card is supported with the alsa driver 1.0.16, which comes with Lenny, see below. Module snd-cmipci - Module for C-Media CMI8338/8738/8768/8770 PCI sound cards. mpu_port- port address of MIDI interface (8338 only): 0x300,0x310,0x320,0x330 = legacy port, 0 = disable (default) fm_port - port address of OPL-3 FM synthesizer (8x38 only): 0x388 = legacy port, 1 = integrated PCI port (default on 8738), 0 = disable soft_ac3- Software-conversion of raw SPDIF packets (model 033 only) (default = 1) joystick_port - Joystick port address (0 = disable, 1 = auto-detect) This module supports autoprobe and multiple cards. The power-management is supported. You may just need to open alsamixer in Gnomes terminal, and check the sound levels, or for any controls that may be muted. the M key toggles the mute/unmute. Running the command, speaker-test , without the quotes, should give you some pink noise output from your speakers (CTRL +C to quit speaker-test), if all the levels are ok, and nothing is muted that should be unmuted. The usual controls that need to be up are, Master, PCM, Front, CD. I don't use Gnome, but KDE, but it's worth right clicking on Gnomes volume control (top right), and see if anythings muted. I'm not sure if it's a right or left click, but there should also be a button for the mixer there as well. Sorry for the lack of info, but it's getting a bit late here in northern france, and I'm about to crash out. Many thanks Nigel, I hope you slept well :-) First, Gnome Volume Control looks OK. (Master, PCM, Line-in, CD and PC Speaker are all unmuted, with sliders at the top. Microphone is muted, but I don't have a microphone connected anyway.) I've never used alsamixer before -- here is what I see: PCM, Line, CD, Phone = 100, 100, unmuted Synth = 100, 100, muted Master = 100, 100 (**but no mute/unmute box is shown**) 3D Contr = unmuted (but no volume box is shown) And speaker-test gives following **error messages**: == speaker-test 1.0.13 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave Playback open error: -16,Device or resource busy [... repeated until I hit Ctrl-C] === Next I listed open files (after reading http://www.debianhelp.org/node/12012 ): == $ lsof -w | egrep 'snd|dsp|NAME' COMMANDPID USER ... NODE NAME esd 3169robert ... 5675 /dev/dsp mixer_app 3241robert ... 5685 /dev/snd/controlC0 == and killed the 'esd' process. Then I tried speaker-test again: == speaker-test 1.0.13 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left Time per period = 2.664647 0 - Front Left Time per period = 2.985804 0 - Front Left Time per period = 2.985816 0 - Front Left Time per period = 2.985820 == ... but I still can't hear any sound. Has anyone any further ideas? Thank you very much, Robert Hi Robert. I'd try unmuting that synth control. Strange name as it is, it does have control over sound output. Pull the slider down a bit before unmuting it, just in case your ears get damaged. If that does work, you may have to disable ESD in Gnomes audio settings, otherwise it may grab /dev/dsp, preventing other audio apps playing directly through alsa. I get the same with KDE's aRts
Re: CMI8738 sound card - cannot hear sound in Lenny
On Friday 16 January 2009 22:04, Robert Canner wrote:
I've unmuted the Synth control in alsamixer, but I still can't hear any
sound :-(
Alsamixer now shows:
Master = 100,100 (but no mute/unmute box is shown)
3D Control = unmuted
PCM, Synth, Line, CD, Aux = 100,100, unmuted
Line-In= Rear Output
Mic= 0, muted
Mic Boost = muted
Phone, PC Speaker = 100, unmuted
IEC958 {5V, Copyright, In Monitor,
In Phase Inverse, In Select, In Valid, Loop,
Mix Analog, Output} = unmuted
Exchange DAC, Four Channel Mode = unmuted
By the way, alsamixer is not displaying any mute/unmute box for the
Master control. Should I worry about this?
No. My alsamixer on lenny shows no mute/unmute box, but it's a different
soundcard (Audigy2 soundblaster), and my alsamixer version shows as 1.0.16.
My alsa-utils package is 1.0.16-2, and that provides alsamixer, and other
stuff.
(By comparison, the Wikipedia screenshot
http://en.wikipedia.org/wiki/File:Alsamixer.png shows a mute/unmute box
for the Master control. My Lenny box is using alsamixer v1.0.13.)
That .png for alsamixer on the wiki is for a different soundcard than yours,
and all alsamixer controls are different, depending on your soundcard, so I'd
ignore that.
It doesn't help that I'm unfamiliar with your C media soundcard, so I'm a bit
in the dark. Are there any switches showing on your alsamixer? For example on
mine for the audigy2 soundblaster card there is a switch to change from
analogue to digital output. If this is set to digital, I get no sound, but
toggling it to analog brings the sounds up.
Perhaps you could post the output from running amixer on the CLI, just to see
what controls you have available.
Someone else who is also using a C media card on Lenny, may also have some
suggestions, that may resolve your problem.
Alternatively, there is the alsa-user mailing list, and someone there may have
specific knowledge of known problems, and fixes for your card.
All the best.
Nigel.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: sound mixer cannot find audio devices after rebooting with USB headset
On Thursday 15 January 2009 20:39, H.S. wrote: Hello, On Debian Lenny and running KDE, I am using an audio card listed as: 02:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) and it works fine. However, if I plug in a headset to the USB port of the computer (Microsoft LX-3000 in this case, though I don't think it matters) and reboot the computer with the headset still plugged in, Debian fails to detect my audio card. I have the sound mixer applet in the panel to control the volume and stuff. But that applet does not see any audio device at all. It keeps showing Select Mixer, but upon clicking on it, it shows no choices to select from. If I reboot the computer after unplugging the USB headset, all is well again. Basically, the sound system fscks up along with the sound mixed applet if I start the computer with the USB headset still plugged in. Am I missing something here? Or is there actually a problem and it is not supposed to be like this? Should I file a bug? I have kmix 4:3.5.9-2 installed on this updated Lenny machine. Thanks. Hi. Try adding the following line to /etc/modprobe.d/alsa-base options snd-usb-audio index=1 That assumes that your soundcard is card0, and no other cards are using slot1. The USB starts early in the boot process, and from personal experience with my usb midi keyboard, which was wrongly read as an audio device, and set as card0, resulting in the actual soundcard not being able to use slot0, which it was asigned to. Adding the line above fixes it for me, and maybe for you too. Before doing that, and just for a test, try running the command below. cat /proc/asound/cards You may well see your headset there as card0, but as your soundcard needs to be set as card0, this explains why you have no sounds. You may also find that running alsamixer on the CLI (Konsole) shows a control, but just for the headset. This has been a long standing problem with USB devices. Some distro's handle it better than others, but I've had to deal with it since Fedora core 1 in 2003. All the best, and I hope the suggestion fixes your problem. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: CMI8738 sound card - cannot hear sound in Lenny
On Friday 16 January 2009 00:10, Robert Canner wrote: Hi folks, I've installed a CMI8738 PCI sound card (C-Media 8738) on my dual-boot machine. When I boot Windows, I can hear sound, but when I boot GNU/Linux, I can't hear any sound. I have tried 3 different ways of generating sound: (1) Gnome Desktop|Preferences|Sound|enable System Sounds (2) Gnome CD Player (3) $ cat /usr/share/sounds/alsa/Front_Center.wav /dev/dsp bash: /dev/dsp: Device or resource busy The motherboard (Intel D865GBF) has an on-board sound system, which I disabled in the BIOS setup before installing the CMI8738 card. == $ uname -a Linux mercury 2.6.18-6-686 #1 SMP Fri Dec 12 16:48:28 UTC 2008 i686 GNU/Linux == $ groups robert dialout cdrom floppy audio video plugdev netdev powerdev == $ lspci -v ... 02:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Flags: bus master, medium devsel, latency 32, IRQ 209 I/O ports at b800 [size=256] Capabilities: access denied == $ cat /proc/asound/cards 0 [CMI8738]: CMI8738 - C-Media PCI CMI8738 C-Media PCI CMI8738 (model 37) at 0xb800, irq 209 == $ cat /proc/interrupts CPU0 0: 103538IO-APIC-edge timer 1:691IO-APIC-edge i8042 6: 5IO-APIC-edge floppy 7: 0IO-APIC-edge parport0 8: 1IO-APIC-edge rtc 9: 1 IO-APIC-level acpi 12: 29611IO-APIC-edge i8042 14: 11577IO-APIC-edge ide0 15: 1192IO-APIC-edge ide1 169: 27570 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb4, i...@pci::00:02.0 177: 0 IO-APIC-level uhci_hcd:usb2 185:247 IO-APIC-level uhci_hcd:usb3, libata, eth1 193: 23 IO-APIC-level ehci_hcd:usb5 209:155 IO-APIC-level CMI8738 NMI: 0 LOC: 103501 ERR: 0 MIS: 0 == Thank you very much, Robert Canner London, UK Hi Robert. Well the cards being detected according to /proc/asound/cards, and you're a member of the audio group. The card is supported with the alsa driver 1.0.16, which comes with Lenny, see below. Module snd-cmipci - Module for C-Media CMI8338/8738/8768/8770 PCI sound cards. mpu_port- port address of MIDI interface (8338 only): 0x300,0x310,0x320,0x330 = legacy port, 0 = disable (default) fm_port - port address of OPL-3 FM synthesizer (8x38 only): 0x388 = legacy port, 1 = integrated PCI port (default on 8738), 0 = disable soft_ac3- Software-conversion of raw SPDIF packets (model 033 only) (default = 1) joystick_port - Joystick port address (0 = disable, 1 = auto-detect) This module supports autoprobe and multiple cards. The power-management is supported. You may just need to open alsamixer in Gnomes terminal, and check the sound levels, or for any controls that may be muted. the M key toggles the mute/unmute. Running the command, speaker-test , without the quotes, should give you some pink noise output from your speakers (CTRL +C to quit speaker-test), if all the levels are ok, and nothing is muted that should be unmuted. The usual controls that need to be up are, Master, PCM, Front, CD. I don't use Gnome, but KDE, but it's worth right clicking on Gnomes volume control (top right), and see if anythings muted. I'm not sure if it's a right or left click, but there should also be a button for the mixer there as well. Sorry for the lack of info, but it's getting a bit late here in northern france, and I'm about to crash out. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /dev/sndstat
On Wednesday 14 January 2009 04:49, M. Lewis wrote: Nigel Henry wrote: I wonder if you have some sort of codec conflict going on here. Try adding the following line to /etc/modprobe.d/alsa-base, and rebooting. options snd-hda-intel probe_mask=1 That will just select the first codec, which should be the one for your soundcard, if there are more than one codec in the equation. If that doesn't work, and the next time you get the sounds up and running, post back the output of the following stuff. cat /proc/asound/cards cat /proc/asound/version grep ^Codec /proc/asound/card?/codec* If the probe_mask option does work, post back the output of the above stuff as well, as it may be helpfull in getting a solution to the problem. All the best. Nigel. I have some sounds coming from the speakers now Nigel. Here is the information you asked for. The first part is run from rc.local, the second part was run manually after I got the sound. Hope this tells you something. Note: the only 'significant' change I made that I know of is: # Inserted per Nigel Henry #options snd-hda-intel index=0 probe_mask=1 enable=1 options snd-hda-intel enable=1 index=0 position_fix=1 The first commented out version did *not* work. I later changed the order and it started working after rmmod snd-hda-intel, modprobe -v snd-hda-intel. - # date Tue Jan 13 19:32:27 CST 2009 - # cat /proc/asound/cards --- no soundcards --- - # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16. - # grep ^Codec /proc/asound/card?/codec* - # date Tue Jan 13 21:17:46 CST 2009 - # cat /proc/asound/cards 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe024000 irq 16 - # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16. - # grep ^Codec /proc/asound/card?/codec* Codec: Realtek ALC885 - moe:~# ll /dev/snd total 0 drwxr-xr-x 2 root root 200 2009-01-13 21:15 . drwxr-xr-x 15 root root 4060 2009-01-13 21:15 .. crw-rw 1 root audio 116, 0 2009-01-13 21:15 controlC0 crw-rw 1 root audio 116, 24 2009-01-13 21:15 pcmC0D0c crw-rw 1 root audio 116, 16 2009-01-13 21:33 pcmC0D0p crw-rw 1 root audio 116, 25 2009-01-13 21:15 pcmC0D1c crw-rw 1 root audio 116, 17 2009-01-13 21:15 pcmC0D1p crw-rw 1 root audio 116, 26 2009-01-13 21:15 pcmC0D2c crw-rw 1 root audio 116, 1 2009-01-13 21:15 seq crw-rw 1 root audio 116, 33 2009-01-13 21:15 timer After a reboot, unfortunately it is *NOT* working. :-( Thanks, Mike Hi Mike. At least we know what the codec is now. As both your threads have been running for a while, perhaps we could go back, and get some basic details. Which machine do you have? Make/model. PC, or laptop. Sound was working on your i686 install, and I presume that was Lenny, but when you installed x86_64/AMD64 version of Lenny, sound no longer worked. Was that a totally fresh install of the 64 bit version of Lenny? Personally I'd go back to the i686 version of Lenny, where the sound was working. I've seen conflicting reports of the benefits of using a 64 bit OS. Only my opinion, and of course it's your choice. Anyway. Back to the ALC885 codec. There are a bunch of model options for this codec with the 1.0.16 alsa driver, as below. I see the same model options for the 1.0.18a alsa driver, but bear in mind that the alsa developers are continually applying patches to the alsa driver, so maybe upgrading to the latest alsa driver is an option. The link for the latest is also below. ALC882/885 3stack-dig 3-jack with SPDIF I/O 6stack-dig 6-jack digital with SPDIF I/O arima Arima W820Di1 targa Targa T8, MSI-1049 T8 asus-a7j ASUS A7J asus-a7m ASUS A7M macpro MacPro support mbp3 Macbook Pro rev3 imac24 iMac 24'' with jack detection w2jc ASUS W2JC auto auto-config reading BIOS (default) Latest alsa driver obtainable from link below, and if you want the latest nightly snapshot of the driver, that's the 2nd link. http://alsa-project.org/main/index.php/Main_Page http://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/ If you're not sure on how to upgrade the alsa driver, just ask. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /dev/sndstat
On Monday 12 January 2009 16:22, M. Lewis wrote: Ron Johnson wrote: On 01/12/09 03:44, M. Lewis wrote: M. Lewis wrote: M. Lewis wrote: Ron Johnson wrote: On 01/11/09 23:33, M. Lewis wrote: Ron Johnson wrote: On 01/11/09 22:34, M. Lewis wrote: Ron Johnson wrote: On 01/11/09 21:55, M. Lewis wrote: [snip] moe:~# lspci -v -s14.2 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Giga-byte Technology Device a002 Flags: slow devsel, IRQ 16 Memory at fe024000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Kernel modules: snd-hda-intel Do you happen to know what that fast devsel / slow devsel business is about? Nope. What happens when you: # depmod # modprobe -v snd_hda_intel snd_seq Well, actually that works with speaker-test. *BUT*, I'm not holding my breath. I've had it this far before and couldn't reproduce it again. Let me reboot and try again before I pronounce it 'fixed'. Well, no, but more information: install /sbin/modprobe --ignore-install snd-hda-intel snd_seq /lib/alsa/modprobe-post-install snd-hda-intel insmod /lib/modules/2.6.26-1-amd64/kernel/sound/pci/hda/snd-hda-intel.ko snd_seq FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.26-1-amd64/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error running install command for snd_hda_intel And from dmesg: [ 362.587129] snd_hda_intel: Unknown parameter `snd_seq' I will try it without the snd_seq. Still no luck without the snd_seq or even putting snd_seq in a separate modprobe: modprobe -v snd_seq modprobe -v snd-hda-intel So the depmod/modprobe worked, but then you rebooted and now it doesn't work That is correct. That is three times, through some series of events, that I have managed to get sound out of it. Rebooted and tried to reproduce the sequence and was not able to reproduce it. -- I wonder if you have some sort of codec conflict going on here. Try adding the following line to /etc/modprobe.d/alsa-base, and rebooting. options snd-hda-intel probe_mask=1 That will just select the first codec, which should be the one for your soundcard, if there are more than one codec in the equation. If that doesn't work, and the next time you get the sounds up and running, post back the output of the following stuff. cat /proc/asound/cards cat /proc/asound/version grep ^Codec /proc/asound/card?/codec* If the probe_mask option does work, post back the output of the above stuff as well, as it may be helpfull in getting a solution to the problem. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ALSA Config
On Sunday 04 January 2009 02:21, Dean Chester wrote: I noticed that this error came up on boot: alsactl restore error message alsactl: set_control: 1269 : Failed to obtain info for control #24(no such file or directory) when it was trying to start alsa. So its to do with alsa not being able to restore the previous volumes properly. Nigel here is the information you wanted. d...@debian:~$ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16. d...@debian:~$ uname -r 2.6.26-1-amd64 d...@debian:~$ grep ^Codec /proc/asound/card?/codec* /proc/asound/card0/codec#0:Codec: SigmaTel STAC9228 /proc/asound/card0/codec#1:Codec: Conexant ID 2c06 Hi Dean. Ok. the codecs above are ok. The conexant one is probably for a sound component on an onboard modem. Did you try the various model options that are listed below from my previous post. You may find that one of these provides a needed slider in alsamixer, and would explain why you have no sounds when booting up at the moment, until you run alsaconf. Why though running alsaconf should find more than what is done at bootup, I don't know. I don't know how new your Dell vostro 1400 is, but Sid is still using the alsa driver 1.0.16, and the alsa driver is being patched continually to resolve sound problems with various codecs. It may be worth upgrading the alsa driver. Link below for the latest. http://alsa-project.org/main/index.php/Main_Page If your not sure of the packages that need to be installed to upgrade the alsa driver, and the procedure, post me back. Looking at the model options for the 1.0.16 alsa driver, there are only 4, and the first is the default ref. STAC9227/9228/9229/927x ref Reference board 3stack D965 3stack 5stack D965 5stack + SPDIF dell-3stack Dell Dimension E520 For the 1.0.17, and later alsa drivers, there is an additional model option, this may not make any difference in your case, but you never know. STAC9227/9228/9229/927x ref Reference board 3stack D965 3stack 5stack D965 5stack + SPDIF dell-3stack Dell Dimension E520 dell-bios Fixes with Dell BIOS setup BTW that is the problem as all the modules are loaded and unloaded successfully. I am unable to boot in to previous kernels as i have removed them(d'oh, stupid me). I admit that I do keep all kernels, unless they just no longer work on an upgraded version of Debian (2.4.27 still works on Etch, but not on Lenny). I know it's old, but if it works keep it. Older kernels are always good for comparison, if you have problems with something or other. Anyway. You've only got one, so are stuck with it. Try the various model options for the 1.0.16 alsa driver, and see if you get additional sliders on alsamixer, that may or may not get some sounds out of your machine, If not, I'd go for upgrading the alsa driver to 1.0.18a, and try the various model options again, including the extra one. As I say above, if you're not sure of the packages that need to be installed, or the procedure, just ask. All the best. Nigel. Dean On Sat, Jan 3, 2009 at 11:33 PM, Nigel Henry cave.dnb2m9...@aliceadsl.frwrote: On Saturday 03 January 2009 19:30, Dean Chester wrote: Update: I unloaded alsa with the command: alsa unload. now i can't get it to resume as it doesn't load any modules. I think this info might help us find a solution. Outputs of commands alsa unload: debian:~# alsa unload /usr/sbin/alsa: Warning: Processes using sound devices: 31575(wish8.5). Unloading ALSA sound driver modules: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc (failed: modules still loaded: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc). debian:~# alsa unload Unloading ALSA sound driver modules: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc. I left amsn running by mistake thats why it failed the first time. alsa resume: debian:~# alsa resume debian:~# alsa resume debian:~# alsa resume As you can see its not loading anything. Hope this helps. Dean Hi Dean. I havn't played around with alsa unload/alsa resume before, but when you reboot, are the alsa modules loaded again (lsmod | grep snd), and is the soundcard detected, as when running. cat /proc/asound/cards Don't post the output, a yes, or no is ok. Also please post the output of the following. cat /proc/asound/version uname -r grep ^Codec /proc/asound/card?/codec* There are some model options for the STAC9228 codec, as listed below. Try them out one at a time in /etc/modprobe.d/alsa-base, and obviously reboot to try each one. STAC9227/9228/9229/927x ref Reference board 3stack D965 3stack 5stack D965 5stack + SPDIF dell-3stack Dell Dimension E520 dell-bios Fixes with Dell BIOS setup The ref one is the default, but try the others. The above options are for the alsa driver 1.0.17, and also apply to alsa driver
Re: ALSA Config
On Saturday 03 January 2009 19:30, Dean Chester wrote: Update: I unloaded alsa with the command: alsa unload. now i can't get it to resume as it doesn't load any modules. I think this info might help us find a solution. Outputs of commands alsa unload: debian:~# alsa unload /usr/sbin/alsa: Warning: Processes using sound devices: 31575(wish8.5). Unloading ALSA sound driver modules: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc (failed: modules still loaded: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc). debian:~# alsa unload Unloading ALSA sound driver modules: snd-hda-intel snd-mixer-oss snd-pcm snd-timer snd-page-alloc. I left amsn running by mistake thats why it failed the first time. alsa resume: debian:~# alsa resume debian:~# alsa resume debian:~# alsa resume As you can see its not loading anything. Hope this helps. Dean Hi Dean. I havn't played around with alsa unload/alsa resume before, but when you reboot, are the alsa modules loaded again (lsmod | grep snd), and is the soundcard detected, as when running. cat /proc/asound/cards Don't post the output, a yes, or no is ok. Also please post the output of the following. cat /proc/asound/version uname -r grep ^Codec /proc/asound/card?/codec* There are some model options for the STAC9228 codec, as listed below. Try them out one at a time in /etc/modprobe.d/alsa-base, and obviously reboot to try each one. STAC9227/9228/9229/927x ref Reference board 3stack D965 3stack 5stack D965 5stack + SPDIF dell-3stack Dell Dimension E520 dell-bios Fixes with Dell BIOS setup The ref one is the default, but try the others. The above options are for the alsa driver 1.0.17, and also apply to alsa driver 1.0.18a. Example options line below. options snd-hda-intel model=3stack I'm thinking that there may be some slider missing in alsamixer when you boot the machine up, but when you run alsaconf, for some reason or other the correct mixer elements are displayed in alsamixer, which is why the sounds then work. If you have an earlier kernel installed, try booting with that, as some kernels can have problems with sounds. Just some suggestions from someone trying to help others to get sounds working. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Soundcard not detected after reboot with Lenny
On Friday 02 January 2009 12:44, Sander Marechal wrote: Hi all, I have a problem with my on-board sound card. I have an Asus A8N-SLI motherboard with on-board nVidia CK804 AC'97 audio controller. When I reboot my computer (Lenny) it is not recognised. I get no sound. When I run `asoundconf list` I get two choices: HDMI and UART. Neither gives me sound. Then I run `alsaconf` as root and it offers me three soundcards to choose from: hda-intel: ATI Technologies Inc HD48x0 audio intel8x0: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) mpu401:snd-mpu401 Strange, since I have no extra soundcards in this system. Just what's on the motherboard. When I pick the nVidia card and let alsaconf finish configuration I get working sound, but after a reboot the sound is gone again. After I fix my sound with alsaconf, running `asoundconf list` only gives me one option: CK804. The contents of /etc/modprobe.d/sound: alias snd-card-0 snd-intel8x0 options snd-intel8x0 index=0 The contents of /proc/asound/modules before running alsaconf: 0 snd_hda_intel 1 snd_mpu401 The contents of /proc/asound/modules after running alsaconf: 0 snd_intel8x0 Output of lspci: 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev a3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 VGA compatible controller: ATI Technologies Inc Device 944c 03:00.1 Audio device: ATI Technologies Inc HD48x0 audio 05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) Any idea how I can fix this issue and have sound working on boot? It has always worked fine under Etch. Thanks in advance, -- Sander Marechal http://www.jejik.com Hi Sander. I've seen this sort of problem before. It looks like the hda intel card is being detected first, and grabbing the slot for card0, then the actual sound card that is set to use card0 can no longer use it, as that slot is occupied. I'd suggest adding a couple of extra options lines to /etc/modprobe.d/sound, as below, reboot, and see how that goes. options snd-hda-intel index=1 options snd-mpu401 index=2 The snd-mpu401 is for the games/midi connection on your soundcard The snd-hda-intel looks like it's for some sound component on the graphics card, probably HDMI. from your lspci above 03:00.0 VGA compatible controller: ATI Technologies Inc Device 944c 03:00.1 Audio device: ATI Technologies Inc HD48x0 audio All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ALSA Config
On Friday 02 January 2009 16:36, Dean Chester wrote: Hi, Everytime i boot in to debian(sid im running on a vostro 1400) i have to run alsaconfg. Is there anyway i can get rid of having to do this as it annoying. Dean Hi Dean. Would you post the output of, cat /proc/asound/cards , for before you run alsaconf, and after, when the sound is working. Also the output of, lsmod | grep snd Some drivers are notorious for grabbing card0, before your sound card which uses card0 has a chance. snd-bt87x is one, and also if you have anything plugged into the USB that uses audio (webcam mike, USB headset, usb midi keyboard (like me)), you can find that snd-usb-audio has grabbed card0, as the USB starts early in the bootup. Post back the requested info first, but if the above is the case, the fix is simple by setting index options lines in /etc/modprobe.d/alsa-base. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ALSA Config
On Friday 02 January 2009 17:53, dean.g.ches...@googlemail.com wrote: Hi, Here are the results to what Nigel wanted to know: Before: d...@debian:~$ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfebfc000 irq 21 After d...@debian:~$ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfebfc000 irq 21 Dean Hi Dean. Well the cards being detected, as the only card, both before, and after running alsaconf, and likewise all necessary modules are loaded, both before, and after. It sort of looks like a problem with sound levels not being restored when you reboot. Are you using KDE, as KDE's Kmix is notorious for messing with sound levels when you login. When you bootup, /usr/sbin/alsactrl restore is run, and restores previously saved levels, but when you login to KDE, Kmix, if it has the restore volumes at login box checked, alters the volume levels to what they were when you first installed. If you are using KDE, open Kmix, settings, Configure KMix, and uncheck the Restore volumes on login box. Also check Kmix's volume levels, for any that are down at zero. Master, PCM, and Front, are the usual ones, and also check controls that may be muted. If you're not using KDE, ignore the above, but it's worth opening alsamixer in Gnomes terminal, and again checking for muted controls (M key toggles mute/unmute), and for sliders, Master, PCM, Front, that may need to be pushed up. I may be going down the wrong path, thinking that this is a sound levels problem, but it's worth a look. All the best. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Soundcard not detected after reboot with Lenny
On Friday 02 January 2009 18:03, Sander Marechal wrote: Nigel Henry wrote: I'd suggest adding a couple of extra options lines to /etc/modprobe.d/sound, as below, reboot, and see how that goes. options snd-hda-intel index=1 options snd-mpu401 index=2 The snd-mpu401 is for the games/midi connection on your soundcard The snd-hda-intel looks like it's for some sound component on the graphics card, probably HDMI. Worked like a charm. Thank you very much! Hi Sander. Nice to see the problem is resolved. Just a suggestion, but write down these fixes in a notebook. they are often simple fixes, but easily forgotten after a few months have passed by. Enjoy the sounds. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: No sound on a Thinkpad T61 w/ ALSA and AS1984 sound card (redux)
On Wednesday 24 December 2008 04:31, Kyle Barbour wrote: Hello everyone, A while back (http://lists.debian.org/debian-user/2008/01/msg02415.html), I was having trouble getting sound to work on my Thinkpad T61. Although that was resolved and everything worked wonderfully, a few days ago sound stopped working again, and I haven't been successful at fixing the problem. Neither the internal speakers nor the headphones produce any sound. The master volume and the PCM volume are on full, neither are muted, and both the speaker and headphones are enabled. My sound card is an Analog Devices 1984 (AD1984) sound card, and I'm running Debian Lenny (2.6.26-1-686 kernel) with ALSA 1.0.16. According to thinkwiki (http://www.thinkwiki.org/wiki/AD1984), this card should be supported in the kernel and in the alsa driver in the versions I'm using. lsmod | grep snd_hda_intel returns: snd_hdsnd_hda_intel 324248 2 snd_pcm62596 2 snd_pcm_oss,snd_hda_intel snd45604 12 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_seq_oss,snd_seq,snd_tim er,snd_seq_device snd_page_alloc 7816 2 snd_hda_intel,snd_pcm a_intel 324248 2 snd_pcm62596 2 snd_pcm_oss,snd_hda_intel snd45604 12 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_seq_oss,snd_seq,snd_tim er,snd_seq_device snd_page_alloc 7816 2 snd_hda_intel,snd_pcm so it looks as though the correct module is loaded. I tried reconfiguring the sound card with alsaconf, which didn't fix the problem, although it reported a successful status. Compiling ALSA from alsa-source (using module-assistant) and manually loading the modules didn't fix anything either (so maybe not an ALSA problem?). Some more information: $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe02 irq 17 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16. $ cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code) Kernel: Linux finnegan 2.6.26-1-686 #1 SMP Mon Dec 15 18:15:07 UTC 2008 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel at 0xfe02 irq 17 Audio devices: 0: AD198x Analog (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: 0: Analog Devices AD1984 Any thoughts on what might be causing the problem? Thanks! Kyle Barbour Hi Kyle. Have you tried other kernels when booting your Lenny, just to check that your current sound problems are the same when booting other kernels. Also looking at the ALSA-configuration.txt file for the 1.0.16 alsa driver, and later versions, the AD1984 codec lists 3 model options, as below. AD1984 basic default configuration thinkpad Lenovo Thinkpad T61/X61 dell Dell T3400 If you havn't already done so, it may be worth adding the following line to /etc/modprobe.d/alsa-base. options snd-hda-intel model=thinkpad Reboot after doing this. You can restart alsa, but a reboot starts from scratch, so may be the easier option. You may find that opening alsamixer as user on the CLI (Gnomes terminal, or KDE's Konsole), may show more controls, which may need to be unmuted (M key to mute/unmute), or additional sliders that need to be pushed up to get sound output. I am puzzled that your lsmod shows the module, snd-hdsnd-hda-intel. I can't find that module anywhere, but apparently in your case it is loaded, and 2 things are using it. Try the commands below, and post the output, to see what if anything is using the sound, and may be preventing your sounds working. lsof -n | grep /dev/dsp lsof | grep /dev/snd I've posted a ? to the alsa devel list about this snd-hdsnd-hda-intel module. Just out of curiosity, because I've never seen it loaded before. Best wishes. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: No sound on a Thinkpad T61 w/ ALSA and AS1984 sound card (redux)
On Wednesday 24 December 2008 06:25, Rob Starling wrote: On Tue, Dec 23, 2008 at 07:31:12PM -0800, Kyle Barbour wrote: A while back (http://lists.debian.org/debian-user/2008/01/msg02415.html), I was having trouble getting sound to work on my Thinkpad T61. Although that was resolved and everything worked wonderfully, a few days ago sound stopped working again, and I haven't been successful at fixing the problem. Neither the internal speakers nor the headphones produce any sound. The master volume and the PCM volume are on full, neither are muted, and both the speaker and headphones are enabled. My sound card is an Analog Devices 1984 (AD1984) sound card, and I'm running Debian Lenny (2.6.26-1-686 kernel) with ALSA 1.0.16. According to thinkwiki (http://www.thinkwiki.org/wiki/AD1984), this card should be supported in the kernel and in the alsa driver in the versions I'm using. lsmod | grep snd_hda_intel returns: snd_hdsnd_hda_intel 324248 2 snd_pcm62596 2 snd_pcm_oss,snd_hda_intel snd45604 12 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_seq_oss,snd_seq,snd_t imer,snd_seq_device snd_page_alloc 7816 2 snd_hda_intel,snd_pcm a_intel 324248 2 snd_pcm62596 2 snd_pcm_oss,snd_hda_intel snd45604 12 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_seq_oss,snd_seq,snd_t imer,snd_seq_device snd_page_alloc 7816 2 snd_hda_intel,snd_pcm so it looks as though the correct module is loaded. I tried reconfiguring the sound card with alsaconf, which didn't fix the problem, although it reported a successful status. Compiling ALSA from alsa-source (using module-assistant) and manually loading the modules didn't fix anything either (so maybe not an ALSA problem?). Some more information: $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe02 irq 17 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16. $ cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code) Kernel: Linux finnegan 2.6.26-1-686 #1 SMP Mon Dec 15 18:15:07 UTC 2008 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel at 0xfe02 irq 17 Audio devices: 0: AD198x Analog (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: 0: Analog Devices AD1984 Any thoughts on what might be causing the problem? do you need the OSS stuff? might it be that something is grabbing the resource there and hogging it? i also have a T61 and my /proc/asound/cards looks the same, but for some reason (maybe the lack of OSS), my /dev/sndstat has no Audio devices nor Mixers: # cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code) Kernel: Linux pride 2.6.26-1-amd64 #1 SMP Sat Nov 8 18:25:23 UTC 2008 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel at 0xfe02 irq 17 Audio devices: NOT ENABLED IN CONFIG Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: NOT ENABLED IN CONFIG My sound, however, *does* work. The Gnome volume applet sees it as HDA Intel (Alsa mixer) just like yours. Make sure you're controlling the right device (File | Change Device) Let me know if there are other comparative things i can post to help. --Rob Hi Rob. Just a question, as I've poked my nose in on this thread. Kyle's lsmod shows a module (snd-hdsnd-hda-intel) loaded. I can't find such a module as existing. would you post the output of lsmod | grep snd Are you using the same 2.6.26 kernel as Kyle? The latest I've got on my Lenny install is a 2.6.21, and I'm using an Audigy2 soundblaster card (emu10k1), and sounds have always worked out of the box on this card. I do know though, that there can be horrible problems with cards using hda intel. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: No sound on a Thinkpad T61 w/ ALSA and AS1984 sound card (redux)
On Wednesday 24 December 2008 19:59, Daryl Styrk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I also have a T61-7658. Sound works fine here. So, some output.. $ lsmod | grep snd_hda_intel snd_hda_intel 434776 1 snd_pcm81672 2 snd_hda_intel,snd_pcm_oss snd63688 10 snd_hda_intel,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_seq,snd_tim er,snd_seq_device snd_page_alloc 13072 2 snd_hda_intel,snd_pcm $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe02 irq 17 $ cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.16 emulation code) Kernel: Linux t61 2.6.26-1-amd64 #1 SMP Mon Dec 15 17:25:36 UTC 2008 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA Intel at 0xfe02 irq 17 Audio devices: 0: AD198x Analog (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: 0: Analog Devices AD1984 $ lsmod | grep snd snd_hda_intel 434776 1 snd_pcm_oss41760 0 snd_pcm81672 2 snd_hda_intel,snd_pcm_oss snd_mixer_oss 18816 1 snd_pcm_oss snd_seq_dummy 7428 0 snd_seq_oss33152 0 snd_seq_midi_event 11904 1 snd_seq_oss snd_seq54304 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_timer 25744 2 snd_pcm,snd_seq snd_seq_device 11668 3 snd_seq_dummy,snd_seq_oss,snd_seq snd63688 10 snd_hda_intel,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_seq,snd_tim er,snd_seq_device soundcore 12064 1 snd snd_page_alloc 13072 2 snd_hda_intel,snd_pcm Hope this helps. Daryl Hi Daryl. Did you have to set model options for snd-hda-intel on your T61 so as to get the sounds working? I ask because the ALSA-configuration.txt file for the 1.0.16 alsa driver shows 3 options for the AD1984 codec, as below. AD1984 basic default configuration thinkpad Lenovo Thinkpad T61/X61 dell Dell T3400 Perhaps your Thinkpad had sounds working out of the box, as per the basic default configuration above. Although saying that, there is a specific model option for the Thinkpad T61. Would you confirm if you had to set a specific model option for the snd-hda-intel module in /etc/modprobe.d/alsa-base, so as to get sounds working, as below. options snd-hda-intel model=thinkpad Your lsmod | grep snd-hda-intel, shows the snd-hda-intel module loaded, yet Kyle's lsmod | grep snd-hda-intel, shows a different module, mainly snd-hdsnd-hda-intel, as you can see from his post. I can't find any reference to this module, and running modinfo as root for snd-hdsnd-hda-intel, shows no such module, but in his case this module is loaded. All a bit bizarre. I've asked on the alsa devel list about this module, but no replies yet, due to the holidays perhaps. Thanks for your reply, and best wishes. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [SOLVED]race condition audio cards + pcspkr
On Thursday 18 December 2008 16:29, Hugo Vanwoerkom wrote: Hugo Vanwoerkom wrote: Nigel Henry wrote: On Wednesday 17 December 2008 21:18, Hugo Vanwoerkom wrote: Hi, How does one put a wait in the initialization of the pcspkr module? I have 2 audio cards: one the builtin card of the mobo two a CA0106 PCI card. They are supposed to be like this: h...@debian:/etc/udev$ cd /etc/modprobe.d/ h...@debian:/etc/modprobe.d$ more sound alias snd-card-0 snd-via82xx options snd-via82xx index=0 alias snd-card-1 snd_ca0106 options snd_ca0106 index=1 snip I solved it by changing /etc/modprobe.d/sound: alias snd-card-0 snd-via82xx options snd-via82xx index=0 alias snd-card-1 snd_pcsp options snd_pcsp index=1 alias snd-card-2 snd_ca0106 options snd_ca0106 index=2 And that does the trick. Needless to say I have no idea what the details of this process actually are, in particular why snd_pcsp is suddenly showing up after doing this for years... Hugo Nice one Hugo. I was going to suggest something similar using index options, but got distracted in replying to someone else's sound related question. I must admit that I've never seen the pcspeaker occupying a slot in /proc/asound/cards. Just out of interest, would you post back the output of. cat /proc/asound/cards It may give me some guidance on resolving the problem I have with my Etch install, and no sounds using the etchnhalf 2.6.24 kernel. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: race condition audio cards + pcspkr
On Wednesday 17 December 2008 21:18, Hugo Vanwoerkom wrote: Hi, How does one put a wait in the initialization of the pcspkr module? I have 2 audio cards: one the builtin card of the mobo two a CA0106 PCI card. They are supposed to be like this: h...@debian:/etc/udev$ cd /etc/modprobe.d/ h...@debian:/etc/modprobe.d$ more sound alias snd-card-0 snd-via82xx options snd-via82xx index=0 alias snd-card-1 snd_ca0106 options snd_ca0106 index=1 That way I can play sound either through one card or the other depending how on what monitor I am at like this: case $DISPLAY in :0.*) export ALSA_CARD=1 export ALSA_CTL_CARD=1 export ALSA_PCM_CARD=1 export MUS_ALSA_DEVICE=hw:1,0 ;; :1.*) export ALSA_CARD=0 export ALSA_CTL_CARD=0 export ALSA_PCM_CARD=0 export MUS_ALSA_DEVICE=hw:0,0 ;; * ) # Default option. export ALSA_CARD=0 export ALSA_CTL_CARD=0 export ALSA_PCM_CARD=0 export MUS_ALSA_DEVICE=hw:0,0 ;; esac But on the latest Sid linux-image-2.6.26-1-686 I get a race condition between the CA0106 and pcspkr: when pcspkr wins the CA0106 fails to initialize: Dec 17 13:48:22 debian kernel: [ 21.430714] VIA 82xx Audio :00:11.5: VIA VLink IRQ fixup, from 5 to 11 Dec 17 13:48:22 debian kernel: [ 21.438860] PCI: Setting latency timer of device :00:11.5 to 64 Dec 17 13:48:22 debian kernel: [ 21.844739] input: PC Speaker as /class/input/input6 Dec 17 13:48:22 debian kernel: [ 21.994233] Error: Driver 'pcspkr' is already registered, aborting... Dec 17 13:48:22 debian kernel: [ 22.039829] cannot find the slot for index 1 (range 0-1), error: -16 Dec 17 13:48:22 debian kernel: [ 22.047800] CA0106: probe of :00:0a.0 failed with error -12 Dec 17 13:48:22 debian kernel: [ 22.103001] Error: Driver 'pcspkr' is already registered, aborting.. and the pcspkr becomes the second card: h...@debian:/$ aplay -l List of PLAYBACK Hardware Devices card 0: V8237 [VIA 8237], device 0: VIA 8237 [VIA 8237] Subdevices: 4/4 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 card 0: V8237 [VIA 8237], device 1: VIA 8237 [VIA 8237] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: pcsp [pcsp], device 0: pcspeaker [pcsp] Subdevices: 1/1 Subdevice #0: subdevice #0 Is there a way to make the pcspkr wait until after the CA0106 is initialized? This never happens with my own compiled kernel, just with the Debian kernel and it does not always happen, just most of the time. Anybody have an idea? Hugo Hi Hugo. Interesting what you say about the pcspkr (pcsp) module. I'm have problems getting sound from the 2.6.24-etchnhalf kernel using the 1.0.15 alsa driver. I had problems with no sound from Etch's 2.6.18-6 kernel, with no sounds, but upgrading the 1.0.12rc1 alsa driver to 1.0.15 got the sounds working. I wonder if I have the same sort of problem as you, because I'm almost sure I saw something in dmesg saying that the pcspkr module was already loaded skipping. This is with the 2.6.24-etchnhalf kernel. this line in particular from above Dec 17 13:48:22 debian kernel: [ 21.994233] Error: Driver 'pcspkr' is already registered, aborting... If you want rid of the pcspkr module, how about the following line in /etc/modules.d/alsa-base. install pcspkr /bin/true That will send it to never never land Not sure how the module is named, so you may have to look in lsmod for that. It could be, pcspkr, or pcsp. change the line above to suit. I'll try the same myself, when updates on another distro have finished. It may fix my problem too. Nigel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ALSA sound recording frustration SOLVED (to a point)
On Sunday 07 December 2008 17:28, Mark Neidorff wrote: On Monday 01 December 2008 12:39 pm, Andrei Popescu wrote: On Mon,01.Dec.08, 05:19:05, Mark Neidorff wrote: Now I need to compile some kernel modules for VirtualBox so I need the kernel source. Of course, it is not listed in synaptic, so now I'm in the position of rebooting between configurations that use sound and one where I can use VirtualBox. Huh? What have you been looking for? The source packages are named like linux-source-2.6.18 Regards, Andrei (quick review...no sound with linux 2.6.18 kernel...downloaded musix kernel which has ALSA 1.0.16 and sound works...but I use VirtualBox and it needs to compile kernel modules to work...but there is no source for the musix kernel. I see that there is an upgrade to the debian kernel 2.6.24. How do I find out what version of ALSA that kernel has? Assuming that it is the wrong version of ALSA, where can I find detailed instructions for downloading and compiling the newer ALSA kernel(?)/modules(?) so that I can use sound and VirtualBox at the same time? Thanks, Mark (the OP) Hi Mark. I thought I'd already replied to your ? Anyway, I've now managed to update the alsa driver on the 2.6.18 kernel, and have gotten sounds with that. Caveat. I know absolutely nothing about Virtualbox. The linux-headers are available for the Musix 2.6.26 kernel. And if you still have the Musix repo uncommented in /etc/apt/sources.list, you should see them there. Back to the Etch 2.6.18-6-686 kernel. You do need a few packages installed to upgrade the alsa driver, and perhaps all the ones listed below are not needed, but most are small. binutils build-essential dpkg-dev g++-4.0 (version may be different on Etch) gcc-4.0 (same as above) kernel-package libc6-dev libstdc++6-4.0-dev(version may differ on Etch) linux-kernel-headers make You also need the linux-headers for your running kernel. In my case (with Etch), synaptic shows the following as below. linux-headers-2.6.18-6 linux-headers-2.6.18-6-686 I also see that linux-kbuild-2.6.18 is installed, but that may have been automatically installed as a dep to other packages mentioned above. Just to take a break. The alsa driver that comes with the 2.6.24 etchnhalf kernel is 1.0.15. I get no sounds with that, when using the etchnhalf kernel, but on another install on the same machine, specifically Kubuntu Dapper, I upgraded the alsa driver from 1.0.10 to 1.0.15, and the sounds work. I am still having problems updating the alsa driver with the etchnhalf kernel (2.6.24), with continual complaints from make. Incidentally, I also get the same make complaints, when trying to upgrade the alsa driver on a Kubuntu Hardy (8.04) install against a 2.6.24 kernel. Puzzling. I'm not saying you will have problems with sounds using the etchnhalf 2.6.24 kernel. It could be hardware specific in my case. Having now finished our break, and installed all the packages above, let's resume the upgrade of the alsa driver. First create a new folder in your /home/user directory. I name mine Alsa-drivers, as I have a bunch of different versions in it. Now download the latest version of the alsa driver (1.0.18a) using the link below. http://alsa-project.org/main/index.php/Main_Page Save the tarball to your newly created Alsa-drivers directory. Next, open a terminal, or Konsole, if using KDE. Now type the commands below as user. cd Alsa-drivers tar xjvf alsa-driver-1.0.18a.tar.bz2 cd alsa-driver-1.0.18a ./configure (which if you have installed the necessary packages, will run to completion) make(having typed make, this also (hopefully) will run to completion, with no errors). If make runs to completion with no errors, su to root, and type as below. make install Reboot, and run cat /proc/asound/version , which should now show the alsa driver version as 1.0.18a. More importantly, you may have had some login sounds, and if not, open alsamixer on the CLI (terminal/Konsole), and check for muted controls (M key to mute/unmute), or sliders like Master, PCM, Front, CD, that need pushing up. To see if your card has been detected on bootup, type: cat /proc/asound/cards Sorry if the stuff above is a bit basic, but it may be usefull for newer folks visiting the archives. Best wishes on getting your sound working. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem in installing alsa driver on Etch
On Wednesday 03 December 2008 20:38, Kelly Clowers wrote: On Wed, Dec 3, 2008 at 05:35, steef [EMAIL PROTECTED] wrote: Nigel Henry wrote: I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or Fedora. On Ubuntu/Kubuntu I just install the build-essential, kernel-package, and the kernel headers for the running kernel, then a simple ./configure, make, and as root, make install, and the alsa driver is upgraded. I have installed the same packages on my Etch install for the etchnhalf kernel. Both the AMD64, and the x86 versions of the kernel are installed. On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, gets the sound working. The etchnhalf kernel also uses alsa driver 1.0.15, but in this case there is no sound. I know the sound works ok on this Etch install, as I have a 2.6.26 kernel from the Musix repo installed, which uses alsa driver 1.0.16. Now the problem: Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to find a soundcard. I have a 1.0.15 alsa driver (and later ones) from the Alsa site. I want to see if the alsa driver 1.0.15 from the Alsa site is in some way different from the one installed with the etchnhalf kernel. Now to simply upgrade the driver. Having unpacked the driver, I cd to the driver folder, and run ./configure, and I don't see any problems. Then I run make, which runs for a bit, then stops with the problem below. make skipped as it fails Do you have the correct header files for that kernel? The header files for 2.6.18-6-686, and for etchnhalf x86, and AMD64 kernels are installed. I just tried to upgrade the alsa driver on another machine (Etch again) which has kernel version 2.6.18-5 on it. As I normally do, I did this from where the 1.0.15 alsa driver was located in my /home/user directory. ./configure ran to completion with no problems, and make also ran to completion. I didn't run make install as root because the sounds are working fine on this machine, which has an audigy2 soundblaster card. Now I switch back to the other machine, which has the hda intel card, and try the same procedure with the 2.6.18-6 kernel. ./configure runs to completion. Make also runs to completion. Now I run as root make install, and it runs to completion. I reboot, and now cat /proc/asound/version shows 1.0.15 for the 2.6.18-6 kernel. I'd tried this back in October with the same kernel, but couldn't upgrade the alsa driver. The only difference today is that after make ran to completion, I su'ed to root, and ran make -n install, which I thought might give some output without actually upgrading the alsa driver. I did get some output, which didn't say much, then ran make install which upgraded the alsa driver from 1.0.12rc1 to 1.0.15. None of this explains why make is throwing in the towel when trying to upgrade the alsa driver with the etchnhalf kernels, with the following output. make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in /home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile. Fix it to use EXTRA_CFLAGS. Stop. And I get the same with the AMD64 kernel. It's all a bit academic, as the Musix 2.6.26 kernel, using alsa driver 1.0.16 has working sounds, and now having upgraded the alsa driver on the 2.6.18-6 kernel from 1.0.12rc1 to 1.0.15, that also has working sounds for the hda intel card on my Asus M2N-X Plus mobo. I think I'll leave the etchnhalf kernels alone for a while, on the premise that, If it works, don't mess with it, and the sounds are working with 2 kernels, but not the etchnhalf ones. Nigel. Kelly Clowers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem in installing alsa driver on Etch
I have no problems upgrading the alsa driver on Ubuntu/Kubuntu, or Fedora. On Ubuntu/Kubuntu I just install the build-essential, kernel-package, and the kernel headers for the running kernel, then a simple ./configure, make, and as root, make install, and the alsa driver is upgraded. I have installed the same packages on my Etch install for the etchnhalf kernel. Both the AMD64, and the x86 versions of the kernel are installed. On my Kubuntu Dapper install, which has alsa driver 1.0.10, the sound doesn't work, but upgrading to alsa driver 1.0.15 from the Alsa site, gets the sound working. The etchnhalf kernel also uses alsa driver 1.0.15, but in this case there is no sound. I know the sound works ok on this Etch install, as I have a 2.6.26 kernel from the Musix repo installed, which uses alsa driver 1.0.16. Now the problem: Etchnhalf has the 1.0.15 alsa driver, which for some reason fails to find a soundcard. I have a 1.0.15 alsa driver (and later ones) from the Alsa site. I want to see if the alsa driver 1.0.15 from the Alsa site is in some way different from the one installed with the etchnhalf kernel. Now to simply upgrade the driver. Having unpacked the driver, I cd to the driver folder, and run ./configure, and I don't see any problems. Then I run make, which runs for a bit, then stops with the problem below. make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/pcmcia' make[2]: Entering directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[2]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/misc' make[1]: Leaving directory `/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15' make -C /lib/modules/2.6.24-etchnhalf.1-486/build SUBDIRS=/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15 CPP=gcc -E CC=gcc modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in /home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile. Fix it to use EXTRA_CFLAGS. Stop. make[2]: *** [/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore] Error 2 make[1]: *** [_module_/home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' make: *** [compile] Error 2 [EMAIL PROTECTED]:~/Downloads/Alsa-drivers/alsa-driver-1.0.15$ The relevant lines where the problem appears are below. make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-486' scripts/Makefile.build:46: *** CFLAGS was changed in /home/djmons/Downloads/Alsa-drivers/alsa-driver-1.0.15/acore/Makefile. Fix it to use EXTRA_CFLAGS. Stop. I don't understand what I need to do to fix this, as the makefile which is below, doesn't make any reference to CFLAGS, and have no idea where to add the line EXTRA_CFLAGS, if that's all is needed. Makefile for alsa-driver-1.0.15/acore below. ifndef SND_TOPDIR SND_TOPDIR=.. endif include $(SND_TOPDIR)/toplevel.config include $(SND_TOPDIR)/Makefile.conf clean-files := info.c pcm.c pcm_native.c control.c hwdep.c init.c rawmidi.c \ sound.c timer.c memalloc.c misc.c export-objs := control.o device.o info.o info_oss.o init.o isadma.o memory.o \ misc.o misc_driver.o sound.o sound_oss.o \ pcm.o pcm_lib.o pcm_memory.o pcm_misc.o pcm_native.o \ rawmidi.o timer.o hwdep.o memalloc.o wrappers.o include $(SND_TOPDIR)/alsa-kernel/core/Makefile snd-objs += wrappers.o misc_driver.o ifeq ($(CONFIG_SND_DEBUG_MEMORY),y) snd-objs += memory_debug.o endif snd-page-alloc-objs += memory_wrapper.o snd-hpet-objs := hpetimer.o obj-$(CONFIG_SND_HPET) += snd-hpet.o obj-$(CONFIG_SND_BIT32_EMUL) += ioctl32/ include $(SND_TOPDIR)/Rules.make info.c: info.inc info.patch $(SND_TOPDIR)/alsa-kernel/core/info.c pcm.c: pcm.patch $(SND_TOPDIR)/alsa-kernel/core/pcm.c pcm_native.c: pcm_native.patch $(SND_TOPDIR)/alsa-kernel/core/pcm_native.c control.c: control.patch $(SND_TOPDIR)/alsa-kernel/core/control.c hwdep.c: hwdep.patch $(SND_TOPDIR)/alsa-kernel/core/hwdep.c init.c: init.patch $(SND_TOPDIR)/alsa-kernel/core/init.c rawmidi.c: rawmidi.patch $(SND_TOPDIR)/alsa-kernel/core/rawmidi.c sound.c: sound.patch $(SND_TOPDIR)/alsa-kernel/core/sound.c timer.c: timer.patch $(SND_TOPDIR)/alsa-kernel/core/timer.c memalloc.c: memalloc.patch memalloc.inc memalloc.inc1 $(SND_TOPDIR)/alsa-kernel/core/memalloc.c misc.c: misc.patch $(SND_TOPDIR)/alsa-kernel/core/misc.c Any help with this problem will be very gratefully received. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound recording frustration SOLVED (to a point)
On Monday 01 December 2008 11:19, Mark Neidorff wrote: On Saturday 29 November 2008 07:20 pm, Kelly Clowers wrote: On Sat, Nov 29, 2008 at 14:11, Nigel Henry [EMAIL PROTECTED] wrote: snip Hi Kelly. I did see the Etchnhalf 2.6.24 kernel when looking at synaptic. I only suggested the musix one, as I have it installed, and know it uses alsa driver 1.0.16. I'm on dialup, and didn't want to download the etchnhalf kernel, only to find that the alsa driver available on it was earlier than 1.0.16. Have you got the etchnhalf kernel 2.6.24 x86 installed, and could let me know which alsa driver version it is using? Otherwise I'll install it myself. I run Unstable, actually. But I see now that 2.6.24 uses alsa 1.0.15. Cheers, Kelly Clowers Hi everyone, Using the MUSIX kernel solved the problem with the sound card. Sound now works--YIPEE!!! Many thanks for all the good suggestions. Now I need to compile some kernel modules for VirtualBox so I need the kernel source. Of course, it is not listed in synaptic, so now I'm in the position of rebooting between configurations that use sound and one where I can use VirtualBox. More suggestions? Mark Hi Mark. Nice that the sound is working now. I see that the linux headers are available for that kernel. Would they be sufficient for what you need to do? Kelly suggested the etchnhalf kernel, which has alsa driver 1.0.15, but I couldn't get sounds with that one, although I used the AMD64 version of it, rather than the x86. Bit odd, as I have Kubuntu Dapper on the same machine, and had upgraded the alsa driver to 1.0.15, and sounds work fine on that. It may be worth trying the etchnhalf. The fact that it doesn't work for me, doesn't mean it wont for you, and at least you can get the source for that one. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Synaptic. Can't find where it saves history
Hi Folks. Does anyone know where Synaptic saves it's history? I can view the history of packages installed, or uninstalled when Synaptic is open, but where exactly is this history saved on the machine. Looking at the installed files for Synaptic, when Synaptic is open, nothing stands out. There's a whole bunch of glade stuff, and /usr/share/synaptic/glade/window_logview.glade, appears to be the window displayed when accessing the history in Synaptic, but no comments as to where the history displayed in this window is actually located. Any suggestions as to where to look, commands to try, etc. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound recording frustration SOLVED (to a point)
On Monday 01 December 2008 18:39, Andrei Popescu wrote: On Mon,01.Dec.08, 05:19:05, Mark Neidorff wrote: Now I need to compile some kernel modules for VirtualBox so I need the kernel source. Of course, it is not listed in synaptic, so now I'm in the position of rebooting between configurations that use sound and one where I can use VirtualBox. Huh? What have you been looking for? The source packages are named like linux-source-2.6.18 Regards, Andrei Not for the Musix kernel that I suggested he install to get the sounds working on Etch. The kernel headers are available for the Musix 2.6.26 realtime kernel, but no source. Strangely the etchnhalf kernel which has alsa driver 1.0.15, produced no sounds, with a failure to create /dev/dsp message, although my Kubuntu Dapper install on the same machine, which at install was using alsa driver 1.0.10, which I then upgraded to alsa driver 1.0.15 from the alsa site, now does produce sounds. It doesn't make sense. Both alsa drivers are the same version, yet the one installed on Kubuntu Dapper has sounds working, but the on that comes with the etchnhalf kernel doesn't. I'm not complaining, as I do have the Musix kernel installed, which has the sounds working (alsa driver 1.0.16), but it is a bit bizarre that Dapper has sound using the alsa driver 1.0.15, but etchnhalf, using the same alsa driver, does not have sound. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Synaptic. Can't find where it saves history
On Monday 01 December 2008 19:21, Andrei Popescu wrote: On Mon,01.Dec.08, 18:09:06, Nigel Henry wrote: Hi Folks. Does anyone know where Synaptic saves it's history? I can view the history of packages installed, or uninstalled when Synaptic is open, but where exactly is this history saved on the machine. Looking at the installed files for Synaptic, when Synaptic is open, nothing stands out. There's a whole bunch of glade stuff, and /usr/share/synaptic/glade/window_logview.glade, appears to be the window displayed when accessing the history in Synaptic, but no comments as to where the history displayed in this window is actually located. Any suggestions as to where to look, commands to try, etc. Such stuff is usually stored in /var Regards, Andrei Hi Andrei Yes I know, but there is zilch in /var for Synaptics history. I mean, it must be somewhere on the harddrive. I have a problem on Fedora 9, where synaptic will not install packages, but will remove them, and I know that Fedora's apt-rpm is different to Debians, but I removed synaptic, including all files, yet when I re-installed synaptic, all the history was still available from previous installs using synaptic. I know when you say remove all files, sometimes some stuff is left behind, but I'm darned if I can find out where the history files are. Perhaps I will have to go to the home page for synaptic, and if there's a mailing list/forum see if someone can point me in the right direction to these files. Thanks for your reply. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Synaptic. Can't find where it saves history
On Monday 01 December 2008 20:42, Brad Rogers wrote: On Mon, 1 Dec 2008 20:25:54 +0100 Nigel Henry [EMAIL PROTECTED] wrote: Hello Nigel, Yes I know, but there is zilch in /var for Synaptics history. I mean, it must be somewhere on the harddrive. Don't forget Synaptics based on apt. As such, I think what you're after is in /var/log/apt/ Yes I agree, but apt doesn't save any log's, and there is no /var/log/apt file. I know that aptitude, it you're using it, saves a log. This is very puzzling, and have just posted to the synaptic mailing list about this hard to find history file. I'll post back if I get a reply from anybody there. This is all a bit academic, but it would be nice to find out where Synaptic's history file is saved on the harddrive. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Synaptic. Can't find where it saves history
On Monday 01 December 2008 21:15, Thilo Six wrote: Nigel Henry wrote the following on 01.12.2008 18:09 Hi Folks. Does anyone know where Synaptic saves it's history? /root/.synaptic/log - *snip* - Nigel. -- bye Thilo key: 0x4A411E09 Thanks a bunch for that. I had to enable show hidden files in Konquerorsu, otherwise /root was empty , but now I can view all the history files for synaptic. Thanks again. That's another problem resolved. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: FROM LAST APRIL, I almost got it right! Was: Re: Hmmm. A question. Was [Re: Debian is losing its users]
On Saturday 29 November 2008 16:57, Kent West wrote: Cybe R. Wizard wrote: Cybe R. Wizard [EMAIL PROTECTED] said: Everyone piped up: [...] I hereby propose the Jibbering Jackalope. Cybe Do I get a prize for coming so close to reality, something I usually try to avoid? Cybe R. Wizard Not all of us keep up with Ubuntu (I think that's the reference); so what is the new release name? -- Kent West ))) Westing Peacefully - http://kentwest.blogspot.com Don't know, but Jumping Jackflash has got a nice ring to it. A credit to the Stones, and every time you boot, the login screen shows an animated version of Mick Jagger, and a few words from the tune. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound recording frustration
On Saturday 29 November 2008 21:20, Kelly Clowers wrote: On Fri, Nov 28, 2008 at 14:52, Nigel Henry [EMAIL PROTECTED] wrote: On Thursday 27 November 2008 17:40, Nigel Henry wrote: On Thursday 27 November 2008 15:38, Mark Neidorff wrote: Hi All, In case I have to say it, I'm very frustrated trying to get ALSA sound working on my Debian ETCH (up to date) box. My motherboard has built-in sound. Needless to say, I want to hear sound. I also want to be able to record sound from the stereo headphones jack of my radio and the stereo audio out from my XM radio. I've used arecord -t wav -f CD junk.wav to try to record. No matter what the settings in the mixers...total silence (as seen by audacity and as confirmed by using hexdump). I've searched. I tried reloading the ALSA drivers. I ran alsaconf. Alsaconf is generally not useful unless you have an ISA card I downloaded and installed the kernel source and the ALSA drivers source, but I was not able to compile the drivers (couldn't find version.h). Yes, I adjusted for source location with: ./config --with-kernel=/usr/src/linux-source-2.6.18 I've tried alsamixer and alsamixergui. Here is a bunch of info that I found about my system: alsamixergui: Chip Analog Devices AD1986A This is the important bit. That chip uses the snd-hda-intel module. hda-intel has had a lot of improvements in recent version of ALSA, so a kernel/alsa upgrade is probably your best bet. Is there anything else you need to know about my system to help me get sound working? PLEASE HELP me get sound working. Thanks, Mark snip Their are 2 options. Upgrade the alsa driver, which is currently 1.0.18a, or install a later kernel, which has a later alsa driver. I chose on this machine to install a later kernel, which has alsa driver 1.0.16, and my sound on Etch works ok with this. If you want go this way, add the following line to /etc/apt/sources.list deb ftp://musix.ourproject.org/pub/musix/deb/ ./ Hi Mark. I see that the thread that you started with the subject of. ALSA sound recording frustration has now moved into a discussion of electrical theory, which is not helping you with your problem. Even though your subject line stated you had a recording problem, your first 2 paragraphs indicated that you had no sound at all, which is why I suggested the later kernel from the musix repo, in order to get the sounds working with Etch, as that kernel uses a later version of the alsa driver (1.0.16). Have you tried installing the kernel from the musix repo? If so, are the sounds working now with your Etch install? Only trying to help you to get your sounds working. A better option than a Musix kernel might be Etch and a Half: http://wiki.debian.org/EtchAndAHalf Cheers, Kelly Clowers Hi Kelly. I did see the Etchnhalf 2.6.24 kernel when looking at synaptic. I only suggested the musix one, as I have it installed, and know it uses alsa driver 1.0.16. I'm on dialup, and didn't want to download the etchnhalf kernel, only to find that the alsa driver available on it was earlier than 1.0.16. Have you got the etchnhalf kernel 2.6.24 x86 installed, and could let me know which alsa driver version it is using? Otherwise I'll install it myself. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound recording frustration
On Thursday 27 November 2008 17:40, Nigel Henry wrote: On Thursday 27 November 2008 15:38, Mark Neidorff wrote: Hi All, In case I have to say it, I'm very frustrated trying to get ALSA sound working on my Debian ETCH (up to date) box. My motherboard has built-in sound. Needless to say, I want to hear sound. I also want to be able to record sound from the stereo headphones jack of my radio and the stereo audio out from my XM radio. I've used arecord -t wav -f CD junk.wav to try to record. No matter what the settings in the mixers...total silence (as seen by audacity and as confirmed by using hexdump). I've searched. I tried reloading the ALSA drivers. I ran alsaconf. I downloaded and installed the kernel source and the ALSA drivers source, but I was not able to compile the drivers (couldn't find version.h). Yes, I adjusted for source location with: ./config --with-kernel=/usr/src/linux-source-2.6.18 I've tried alsamixer and alsamixergui. Here is a bunch of info that I found about my system: alsamixergui: Chip Analog Devices AD1986A +-- lspci | grep -i audio 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) +-- uname -a Linux mail 2.6.18-6-k7 #1 SMP Mon Oct 13 16:52:47 UTC 2008 i686 GNU/Linux + cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.12rc1 emulation code) Kernel: Linux mail 2.6.18-6-k7 #1 SMP Mon Oct 13 16:52:47 UTC 2008 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA NVidia at 0xfe024000 irq 177 Audio devices: 0: AD198x Analog (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: 0: Analog Devices AD1986A + ls -l /dev/dsp crw-rw 1 root audio 14, 3 2008-11-27 08:48 /dev/dsp + Is there anything else you need to know about my system to help me get sound working? PLEASE HELP me get sound working. Thanks, Mark Hi Mark. I've got Etch installed on a machine, with a mobo that uses MCP61, and the alsa driver version 1.0.12rc1, that comes with the 2.6.18 kernel, and I get no sounds using that alsa driver. cat /proc/asound/cards , shows no soundcards, unless I have my usb midi keyboard plugged in. Then it shows the keyboard as card0. You will probably find that when running lsmod it shows all snd modules installed, but the card is not being detected. Their are 2 options. Upgrade the alsa driver, which is currently 1.0.18a, or install a later kernel, which has a later alsa driver. I chose on this machine to install a later kernel, which has alsa driver 1.0.16, and my sound on Etch works ok with this. If you want go this way, add the following line to /etc/apt/sources.list deb ftp://musix.ourproject.org/pub/musix/deb/ ./ Then run apt-get update, then open synaptic. The kernel you want is as below. linux-image-2.6.26.2-rt1-libre1 I could never find a GPG key for the musix repo, but if you have problems installing the kernel with synaptic, you can set the option to ignore the missing GPG key. I know it's not a good idea to install unsigned packages, and will have to have another go at finding the key for the musix repo, if one exists. Presuming that you now have the 2.6.26 kernel installed now, reboot, and choose it on Grub's menu, and hopefully on login (I'm using KDE) you now have some login sounds, and more important, the sound works. Don't forget to comment out the line for the musix repo after installing the kernel, by putting a # at the start of the line in /etc/apt/sources.list, as you don't want possible updates for other packages you have installed on your Etch, being updated from the Musix repo. Problems can arise when you use repo pick and mix. If you still have no sound, post back. All the best. Nigel. Hi Mark. I see that the thread that you started with the subject of. ALSA sound recording frustration has now moved into a discussion of electrical theory, which is not helping you with your problem. Even though your subject line stated you had a recording problem, your first 2 paragraphs indicated that you had no sound at all, which is why I suggested the later kernel from the musix repo, in order to get the sounds working with Etch, as that kernel uses a later version of the alsa driver (1.0.16). Have you tried installing the kernel from the musix repo? If so, are the sounds working now with your Etch install? Only trying to help you to get your sounds working. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound recording frustration
On Thursday 27 November 2008 15:38, Mark Neidorff wrote: Hi All, In case I have to say it, I'm very frustrated trying to get ALSA sound working on my Debian ETCH (up to date) box. My motherboard has built-in sound. Needless to say, I want to hear sound. I also want to be able to record sound from the stereo headphones jack of my radio and the stereo audio out from my XM radio. I've used arecord -t wav -f CD junk.wav to try to record. No matter what the settings in the mixers...total silence (as seen by audacity and as confirmed by using hexdump). I've searched. I tried reloading the ALSA drivers. I ran alsaconf. I downloaded and installed the kernel source and the ALSA drivers source, but I was not able to compile the drivers (couldn't find version.h). Yes, I adjusted for source location with: ./config --with-kernel=/usr/src/linux-source-2.6.18 I've tried alsamixer and alsamixergui. Here is a bunch of info that I found about my system: alsamixergui: Chip Analog Devices AD1986A +-- lspci | grep -i audio 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) +-- uname -a Linux mail 2.6.18-6-k7 #1 SMP Mon Oct 13 16:52:47 UTC 2008 i686 GNU/Linux + cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.12rc1 emulation code) Kernel: Linux mail 2.6.18-6-k7 #1 SMP Mon Oct 13 16:52:47 UTC 2008 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: HDA NVidia at 0xfe024000 irq 177 Audio devices: 0: AD198x Analog (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: NOT ENABLED IN CONFIG Timers: 7: system timer Mixers: 0: Analog Devices AD1986A + ls -l /dev/dsp crw-rw 1 root audio 14, 3 2008-11-27 08:48 /dev/dsp + Is there anything else you need to know about my system to help me get sound working? PLEASE HELP me get sound working. Thanks, Mark Hi Mark. I've got Etch installed on a machine, with a mobo that uses MCP61, and the alsa driver version 1.0.12rc1, that comes with the 2.6.18 kernel, and I get no sounds using that alsa driver. cat /proc/asound/cards , shows no soundcards, unless I have my usb midi keyboard plugged in. Then it shows the keyboard as card0. You will probably find that when running lsmod it shows all snd modules installed, but the card is not being detected. Their are 2 options. Upgrade the alsa driver, which is currently 1.0.18a, or install a later kernel, which has a later alsa driver. I chose on this machine to install a later kernel, which has alsa driver 1.0.16, and my sound on Etch works ok with this. If you want go this way, add the following line to /etc/apt/sources.list deb ftp://musix.ourproject.org/pub/musix/deb/ ./ Then run apt-get update, then open synaptic. The kernel you want is as below. linux-image-2.6.26.2-rt1-libre1 I could never find a GPG key for the musix repo, but if you have problems installing the kernel with synaptic, you can set the option to ignore the missing GPG key. I know it's not a good idea to install unsigned packages, and will have to have another go at finding the key for the musix repo, if one exists. Presuming that you now have the 2.6.26 kernel installed now, reboot, and choose it on Grub's menu, and hopefully on login (I'm using KDE) you now have some login sounds, and more important, the sound works. Don't forget to comment out the line for the musix repo after installing the kernel, by putting a # at the start of the line in /etc/apt/sources.list, as you don't want possible updates for other packages you have installed on your Etch, being updated from the Musix repo. Problems can arise when you use repo pick and mix. If you still have no sound, post back. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA not loading at system boot
On Wednesday 05 November 2008 23:42, Vinicius Massuchetto wrote: cat /proc/asound/cards [EMAIL PROTECTED]:~$ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfebfc000 irq 21 grep ^Codec /proc/asound/card?/codec* [EMAIL PROTECTED]:~$ grep ^Codec /proc/asound/card?/codec* /proc/asound/card0/codec#0:Codec: SigmaTel STAC9228 /proc/asound/card0/codec#1:Codec: Conexant ID 2c06 Hope we can figure out somehting. Thanks again! Vinicius Hi Vinicius. It's very odd that you have 2 different codecs showing above. This could well be causing a conflict, and is why you have no sound after bootup. Could you post the complete output of lspci -v . I ask, because I have seen before, a graphics card, which has a sound component, which is an hda intel based one, but using a different codec. After running alsaconf, and getting your soundcard up and running, would you open alsamixer, and report back which chipset it is showing being used. It's going to be either the STAC9228, or the Conexant one, not both. If this is the case, I'm not too sure how to resolve the problem. Perhaps a couple of lines in /etc/rc.local, as below. modprobe -r snd-hda-intel modprobe snd-hda-intel Just some thoughts. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Haven't received an posts I send to the list
On Monday 03 November 2008 21:52, Ron Johnson wrote: While receiving other people's emails on the list, all emails that I've sent to the list since yesterday afternoon seem to have vanished, not even appearing in the web archives. So, before pestering the listmasters, can someone CC me if they see this mail? -- Ron Johnson, Jr. Jefferson LA USA Yes. Post received on the list. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kde: can't right click and get context sensitive menu, iceweasel drop down menus dont drop
On Thursday 30 October 2008 15:08, Mitchell Laks wrote: Hi, I am only having this trouble on only one of my many systems running sid. It started a while ago. It only is a problem if I run X directly. If I run via vncserve there is no problem. I run KDE. I noticed first that when I clicked on any of the _File _Edit _View _History menus on top of Iceweasel window, it did not drop down. I had to do alt-F or alt-E or alt_V in order to get the window to be activated. At that point I could scroll down with the arrow to my selection. Then I noticed similarly that the right mouse button will not give context menu on desktop. Similarly I cannot add icons to the panel at bottom of screen. Then I noticed that I similarly could only select the printer in kprinter dialog via the down arrow button - mouse would not work. All mouse works fine on same machine if I log in via the vncviewer and vncserver. All three things- right context button, panel icon setup, iceweasel all work fine. It is not something messed up with the user. If I set up a new user, after upgrading to latest sid (this problem persists upon multiple sid upgrade cycles), I still have the problem. If I try Gnome: If I set up and use Gnome, then there is no such problem with Gnome itself -ie I do right click I get the menu, I can right click on the panel at top however still same problem with Iceweasel. However !!! I still have the problem with the Iceweasel menus not coming down when clicked. Moreover and this is the most bizarre thing. On gnome I have trouble when I use vncviewer - ie the right clicks dont work, even though they worked on the X when I sit at the console. Any ideas??? Very odd behavior and puzzling!! Mitchell That sounds like a problem I had a while back (May), after some updates to Lenny. It turned out that a single click was being interpreted as a double click. For example, click on the edit menu item twice, in quick succession, and the edit drop down menu would be opened, and immediately closed, before you had achance to see the dropdown menu. Clicking on the volume control in the panel, I'd get a quick flash of the slider, which immediately disappeared again, and is the same result that you'd get if clicking on the volume control twice. There was more mysterious stuff, but leaving that aside, someone suggested doing the following in the /etc/X11/xorg.conf file. A private e-mail sent to me from someone on either the Debian-User list, or the KDE list, has enabled me to resolve the mouse problem. All I had to do was edit a line in /etc/X11/xorg.conf relating to the mouse. Section InputDevice Generic Mouse Option SendCoreEvents true I changed the above line from true to false, as suggested, and now the mouse works as it always has done in the past. Having made the changes, a logout, followed by logging back in to KDE did not fix the problem. A reboot was necessary. Don't know if that's any help, but it fixed my problem. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kde: can't right click and get context sensitive menu, iceweasel drop down menus dont drop
On Thursday 30 October 2008 19:34, Mitchell Laks wrote: On 17:19 Thu 30 Oct , Nigel Henry wrote: That sounds like a problem I had a while back (May), after some updates to Lenny. It turned out that a single click was being interpreted as a double click. For example, click on the edit menu item twice, in quick succession, and the edit drop down menu would be opened, and immediately closed, before you had achance to see the dropdown menu. Clicking on the volume control in the panel, I'd get a quick flash of the slider, which immediately disappeared again, and is the same result that you'd get if clicking on the volume control twice. There was more mysterious stuff, but leaving that aside, someone suggested doing the following in the /etc/X11/xorg.conf file. A private e-mail sent to me from someone on either the Debian-User list, or the KDE list, has enabled me to resolve the mouse problem. All I had to do was edit a line in /etc/X11/xorg.conf relating to the mouse. Section InputDevice Generic Mouse Option SendCoreEvents true I changed the above line from true to false, as suggested, and now the mouse works as it always has done in the past. You solved the problem! Thank you very much. I also have had the problem since around May, but mostly use the system via my vncserver so I didnt notice it much till recently. Great! Yabadabadoo Thank you again! Mitchell Laks And a BooBoo to you too Mitchell. Nice to see the suggestion worked. Not my suggestion, but one given to me by one Gerardo Ponce. A later reply also suggested a fix as below, plus a link to a known bug. It may be worth looking at it. quote 2008-05-17 06:04 Add the following line in the xorg.config's Mouse section: Option CorePointer It's a bug. http://www.mail-archive.com/[EMAIL PROTECTED]/msg70399.html Regards. Andrew (Andres Migliazzo) end quote All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to save alsa configuration
On Saturday 25 October 2008 21:53, Serena Cantor wrote: I enter the command alsactl store and reboot, it doesn't work! Hi Serena. I have an SB16 ISA card on the machine I'm posting from (FC2), but it's only set up for one of the distros on the machine as a second soundcard on the Fedora Core 3 install. The other distros use an Ensoniq (ens1371) soundcard. I'll reboot into FC3, and see if there is anything in /etc/modprobe.conf that might help you. If there is you could add the lines to /etc/modprobe.d/alsa-base, which may resolve your problem. I'm not sure how it may work with Etch, as I don't have it installed on this machine. I'll post back later. Nigel. --- On Sat, 10/25/08, A. Ben Hmeda [EMAIL PROTECTED] wrote: From: A. Ben Hmeda [EMAIL PROTECTED] Subject: Re: how to save alsa configuration To: debian-user@lists.debian.org Date: Saturday, October 25, 2008, 12:29 PM Serena Cantor wrote: I have ISA SB16 sound card and etch. I can use alsaconf to setup the card. My question is how to save configuration so I needn't run alsaconf each time I boot. with alsa-utils installed do alsactl store, in terminal, as root. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to save alsa configuration
Update below.
On Saturday 25 October 2008 23:06, Nigel Henry wrote:
On Saturday 25 October 2008 21:53, Serena Cantor wrote:
I enter the command alsactl store and reboot, it doesn't work!
Hi Serena. I have an SB16 ISA card on the machine I'm posting from (FC2),
but it's only set up for one of the distros on the machine as a second
soundcard on the Fedora Core 3 install. The other distros use an Ensoniq
(ens1371) soundcard. I'll reboot into FC3, and see if there is anything
in /etc/modprobe.conf that might help you. If there is you could add the
lines to /etc/modprobe.d/alsa-base, which may resolve your problem.
I'm not sure how it may work with Etch, as I don't have it installed on
this machine.
I'll post back later.
Nigel.
Hi Again. I rebooted into FC3, which has both the Ensoniq, and SB16 soundcards
configured. Both cards work fine after the reboot.
The output from cat /proc/asound/cards is below. The only problem that I had
when I added the SB16 card to this machine, and then ran alsaconf, is that it
insisted on being card0. The Ensoniq card had been card0, but after running
alsaconf for adding the SB16, the SB16 was set as card0, and the Ensoniq card
became card1. Not a big problem, and I did try to change it, but with no
success,
[EMAIL PROTECTED] ~]$ cat /proc/asound/cards
0 [S16]: SB16 - Sound Blaster 16
Sound Blaster 16 at 0x220, irq 5, dma 15
1 [AudioPCI ]: ENS1371 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1371 at 0x1080, irq 11
[EMAIL PROTECTED] ~]$
Moving on to /etc/modprobe.conf , there are 2 lines that alsaconf has set for
the SB16 card, and its worth adding these to your /etc/modprobe.d/alsa-base
file, as it may fix your problem. See below.
alias eth0 3c59x
remove snd-ens1371 { /usr/sbin/alsactl store /dev/null 21
|| : ; }; /sbin/modprobe -r --ignore-remove snd-ens1371
alias usb-controller uhci-hcd
#alias snd-card-0 snd-ens1371
#alias snd-card-1 snd-sb16
#options snd-ens1371 index=0
#options snd-sb16 index=1
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.9rc1 ---
alias snd-card-0 snd-sb16
options snd-sb16 isapnp=0
# --- END: Generated by ALSACONF, do not edit. ---
The 2 lines that you need to add to the /etc/modprobe.d/alsa-base file are,
alias snd-card-0 snd-sb16
options snd-sb16 isapnp=0
As you can see from my /etc/modprobe.conf file above, these were created when
I ran Alsaconf for the SB16 soundcard.
As I said. I don't have Etch installed on the machine with the SB16 card, so
the suggestion above, may, or may not work.
Nigel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA not working properly
On Thursday 16 October 2008 20:41, Samuel Bächler wrote: Nigel, Florian, thank you so far for the hints. Nigel Henry wrote: On Wednesday 15 October 2008 16:41, Samuel Bächler wrote: Dear All I have an etch installed on a lenovo T60. Most of the times simply clicking on a mp3-file in konqueror [1] will start playing that specific file. But, sometimes it does not. There are three sound-bottoms on my keyboard: mute, volume-up and volume-down. In my opinion the sound problems occur whenever I boot the laptop when the mute-bottom was pressed the last time I used the laptop. On the other hand sound seems to work fine whenever the volume-up-bottom was pressed at least once the last time I used the laptop. [snip] Before I ramble on, could you open alsamixer on the CLI, and confirm that the chipset is AD1981. The chipset is AD1981. Looking at model options for AD1981 with alsa driver 1.0.15, I see: basic 3-jack (default) hp HP nx6320 thinkpad Lenovo Thinkpad T60/X60/Z60 toshiba Toshiba U205 Where does one find such information? See below. These options are unlikely to work with the 1.0.12rc1, but your welcome to try the one for the thinkpad. My version is 1.0.13. Su to root on the CLI,Konsole, or Terminal. Navigate to /etc/modprobe.d/alsa-base, and at the bottom of the alsa-base file add the following line. options snd-hda-intel model=thinkpad Save the changes, and reboot. Nigel. I check this now. Thanks a lot. Sam Hi Sam. If the above doesn't change anything on your T60 for the sounds, there are a couple of options I can suggest, both of which I've tried, and work. Not on a T60 admittadly, but on an Asus M2N-X Plus mobo, with hda intel Azalia soundcard. So to work, and this is the first thing I tried. Add the following line to /etc/apt/sources.list. deb ftp://musix.ourproject.org/pub/musix/deb/ ./ All you want from the above repo is a kernel, and the one I installed has alsa driver 1.0.16, which resolved my problem, and may resolve yours. Next, do an apt-get update, then open synaptic. The kernel I installed was, as below. linux-image-2.6.26.2-rt1-libre1 Having installed this kernel, make sure to go back into /etc/apt/sources.list, and comment out the musix repo line, by putting a # at the start of the line. I cannot stress this enough, as if you do an apt-get dist-upgrade with the musix repo still active, you could possibly find packages being updated from the musix repo, and oftentimes can cause problems. Ok. Now the new kernel is installed, reboot using your newly installed kernel, and see if your sounds are working any better than before. Moving on to option 2, simply upgrade the alsa driver. Many patches have been added to the alsa driver since 1.0.12rc1, particularly with reference to the snd-hda-intel module, so go to the link below, and download alsa driver 1.0.17, which is the current stable version. http://alsa-project.org/main/index.php/Main_Page I'd suggest creating a new folder in your /home/user directory for this Alsa stuff. I simply name mine Alsa-drivers, and download all the Alsa packages into this folder/directory. You now need to install some packages, so as to get your newly downloaded alsa driver built, and installed. Su to root on the CLI, and open synaptic, and install the following packages. build-essential kernel-package linux-headers-2.6.18-6 That done, close synaptic,and run apt-get install linux-headers-$(uname -r) This will install the headers for your kernel. Now to build, and install the 1.0.17 alsa driver. As user, cd to where you downloaded the driver, then do: tar xjvf alsa-driver-1.0.17.tar.bz2 A new folder/directory has now been created, so do: cd alsa-driver-1.0.17 Now type: ./configure, and when that runs to completion, type: make, which may take some time. When make completes, with hopefully no errors, su to root, and type make install. If all has gone well, and after a reboot, (using the Etch kernel, not the musix one, if you've also installed that) running cat /proc/asound/version should now show the alsa driver as 1.0.17. Now you may, or may not have better control of sounds on your T60. I don't have a Lenovo T60 laptop, so these are only suggestions given with the hope that they may be of some help in resolving your problem. You asked where I'd found the model options for the AD1981 codec. I assume you have downloaded the 1.0.17 driver, and unpacked it using tar xjvf, which creates a new folder/directory. Click on the new directory, then on alsa-kernel, then Documentation, then ALSA-Configuration.txt. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't config cups printer, no backends found
On Wednesday 15 October 2008 17:07, Ron Johnson wrote: On 10/15/08 00:22, T o n g wrote: Hi, I can't config my cups printer in my newly installed lenny system. I found that the reason might be that no cups backends can be found, because previously, /usr/lib/cups/backend/usb can returns my printer info, now it is empty. How should I fix it? thanks PS. my cups: $ dpkg -l *cups* | grep ^i ii cups 1.3.8-1lenny1 Common UNIX Printing System(tm) - server ii cups-bsd 1.3.8-1lenny1 Common UNIX Printing System(tm) - BSD comman ii cups-client1.3.8-1lenny1 Common UNIX Printing System(tm) - client pro ii cups-common1.3.8-1lenny1 Common UNIX Printing System(tm) - common fil ii cups-driver-gu 5.0.2-4 printer drivers for CUPS ii cupsys 1.3.8-1lenny1 Common UNIX Printing System (transitional pa ii cupsys-bsd 1.3.8-1lenny1 Common UNIX Printing System (transitional pa ii cupsys-driver- 5.0.2-4printer drivers for CUPS ii libcups2 1.3.8-1lenny1 Common UNIX Printing System(tm) - libs ii libcupsimage2 1.3.8-1lenny1 Common UNIX Printing System(tm) - image libs I'm stumped, too. $ dpkg -S /usr/lib/cups/backend/usb dpkg: /usr/lib/cups/backend/usb not found. $ apt-file search /usr/lib/cups/backend/usb $ $ dir /usr/lib/cups/backend/usb -rwxr-xr-x 2 root root 17220 2008-10-11 05:59 /usr/lib/cups/backend/usb* -- Ron Johnson, Jr. Jefferson LA USA My usb printer is on another machine, and my Debian installs print over the network using ipp, so I can't directly help with Tong's problem in setting up a local printer on Lenny. I wonder if the necessary usb host controller module is loaded. On my machine with the usb printer on it, /sbin/lsmod shows the uhci-hcd module loaded, and the usb printer is the only usb device on that machine. There are 2 other usb host controllers, ehci-hcd, and ohci-hcd, and depending on what other usb devices you have connected to the machine, you may find more than one of these usb host controllers loaded. Could you send the output of lsmod please. Also the output of lsusb would be usefull, just to see if Lenny can see the printer. Another thought. Is the printer plugged into an unpowered USB hub. I have had problems with those. If so plug the printer directly into a USB port on the machine 2¢ worth of guesswork. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA not working properly
On Wednesday 15 October 2008 16:41, Samuel Bächler wrote: Dear All I have an etch installed on a lenovo T60. Most of the times simply clicking on a mp3-file in konqueror [1] will start playing that specific file. But, sometimes it does not. There are three sound-bottoms on my keyboard: mute, volume-up and volume-down. In my opinion the sound problems occur whenever I boot the laptop when the mute-bottom was pressed the last time I used the laptop. On the other hand sound seems to work fine whenever the volume-up-bottom was pressed at least once the last time I used the laptop. Any hints? Cheers Sam Hi Sam. I already have Sarge, Etch, and Lenny on another machine, using an Audigy2 soundblaster soundcard, and no problems there, but have recently built a new machine that uses an onboard hda intel soundcard. I've already installed various distros on this machine, and got the sounds working. I installed Etch on this machine, but had no sounds at all. Clearly the alsa driver 1.0.12rc1 didn't know anything about the hda intel card on my mobo. Before I ramble on, could you open alsamixer on the CLI, and confirm that the chipset is AD1981. Looking at model options for AD1981 with alsa driver 1.0.15, I see the following. AD1981 basic 3-jack (default) hp HP nx6320 thinkpad Lenovo Thinkpad T60/X60/Z60 toshiba Toshiba U205 These options are unlikely to work with the 1.0.12rc1, but your welcome to try the one for the thinkpad. Su to root on the CLI,Konsole, or Terminal. Navigate to /etc/modprobe.d/alsa-base, and at the bottom of the alsa-base file add the following line. options snd-hda-intel model=thinkpad Save the changes, and reboot. I suggested the option above from the alsa driver 1.0.15, so this may not change anything for you, and you may have to upgrade the alsa driver, but lets see how this goes. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unable to play some flash videos
On Thursday 25 September 2008 18:38, Stackpole, Chris wrote: Same error message from that site. I am running Debian Lenny (fully updated) with the actual flash plugin from Adobe's site installed through iceweasle. Heh, it's kinda funny that they don't seem to notice their own plugin... Frankly, I have not had much luck with tv websites that stream their online content. Everything pretty much sucks. From Mythbusters episodes on Discovery's website to that Hulu website. I can't seem to get them to work right. As for suggestions...What about building a MythTV box to capture the episodes as they air? That is what I do. And should the recording fail for some reason (#*!%^ Charter!) there is a famous bay for torrents that does a really good job. ;-) Have fun! A while back I had problems listening to online music from a website in Jersey, CI. I could access the website ok, but the music wouldn't stream. I can't remember if it was my Archlinux install, or a Debian one, but both install Firefox, but under a different name, and it appears that some badly constructed websites do not recognise Firefox, if it's identified under a different name. Iceweasel in Debian, and Minefield for firefox 3.0 in Archlinux. On both Lenny, and Archlinux I also installed Firefox (from the Mozilla site) in /usr/local, to see whether they had problems with the same sites as the versions of Firefox installed on Debian, and Archlinux did . In the case of the Jersey site for Internet radio, this now streamed ok with Firefox from the Mozilla site, and I now see that Firefox 2, then named Bon Echo on Archlinux was the one that wouldn't stream the radio, but no problems in accessing the site. See http://www.channel103.com. Type about:config in Iceweasels address bar, scroll down to: general.useragent.extra.firefox On Lenny this shows as: general.useragent.extra.firefox default string Iceweasel/3.0.1 Double click on the line, and in the box that opens, replace Iceweasel/3.0.1 with Firefox. (write down the original entry on a bit of paper, just in case) Then try the problem site again. There does not appear to be a problem with just changing the name to Firefox, whether that is for Firefox2, or 3 which you have installed. I know this fixed my problem, and maybe it will for you. Only being on dialup, streaming video is out of the question, so I can't try the site you're having problems with. 2¢ worthof perhaps nothing. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch netinstl. problem starting kwrite, synaptic, gedit.etc
On Tuesday 26 August 2008 00:34, [EMAIL PROTECTED] wrote: On Sunday 24 August 2008 23:37, [EMAIL PROTECTED] wrote: On Sun, 24 Aug 2008 23:16:46 +0200 Nigel Henry [EMAIL PROTECTED] wrote: I did an apt-get install xorg, which pulled in a few more packages, and apart from some complaints about finding directories for fonts, which didn't appear to exist, but no change when running su, plus password, and kwrite, for example, which stiill failed to open. I also tried another suggestion, as below. quote the basic problem is that you are launching these programs as root, but your desktop is running as your user. So after su'ing run export DISPLAY=localhost:0 and as a user run xhost localhost. The export command sets the DISPLAY variable to your local machine, this variable is how X apps figure out what X server to connect to. The xhost command allows programs running on your local machine to connect to your desktop. end quote I don't think I made any typos. Having done an apt-get install xorg, and also the export stuff above, I still can't just simply su, plus password, and bring up kwrite for example. This is how things are at present, and hand written. Excuse any typos please. [EMAIL PROTECTED]: ~$ su Password: debian: /home/djmons# kwrite Xlib: connection to :0.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kwrite: cannot connect to X server :0.0 debian: /home/djmons# Any suggestions welcome, as usual. Nigel. On my Ubuntu laptop, just su'ing, no dash, works as you describe. Send the output of env after you su. On Debian 3.0, su'ing without the dash also works as you describe. I can't get 4.0 installed because it doesn't recognize my ps2 keyboard. So I can't test the behavior of 4.0. Perhaps there is some new secuity dealie that changes the default behavior. I downloaded the latest testing CD last night, If it works I'll let you know how it su's. Env output below. [EMAIL PROTECTED]:~$ su Password: debian:/home/djmons# env SSH_AGENT_PID=3136 KDE_MULTIHEAD=false DM_CONTROL=/var/run/xdmctl SHELL=/bin/bash TERM=xterm XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched,rsvd,method=classic GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/djmons/.gtkrc-2.0:/home/djmons/.kde/share/config/gtkrc-2.0 GS_LIB=/home/djmons/.fonts GTK_RC_FILES=/etc/gtk/gtkrc:/home/djmons/.gtkrc:/home/djmons/.kde/share/config/gtkrc WINDOWID=39845893 KDE_FULL_SESSION=true USER=root LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35: SSH_AUTH_SOCK=/tmp/ssh-ulJocC3096/agent.3096 SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3184 KONSOLE_DCOP=DCOPRef(konsole-3238,konsole) MAIL=/var/mail/root PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 DESKTOP_SESSION=default PWD=/home/djmons KONSOLE_DCOP_SESSION=DCOPRef(konsole-3238,session-1) LANG=en_GB.UTF-8 PS1=\h:\w\$ HISTCONTROL=ignoredups HOME=/root SHLVL=3 XCURSOR_THEME=default LOGNAME=root DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-9HMQFdnV6q,guid=d923f13f2106044f6a7b330048b3fd82 DISPLAY=:0.0 COLORTERM= _=/usr/bin/env debian:/home/djmons# This is a puzzling problem on this Etch install. I also have other Debian installs on another machine. All these were originally installed from Woody 3.0r2 discs, and I currently have a Sarge, Etch, and Lenny install, but no problems with su, and starting GUI apps. Looking back through my handwritten notes I'd had the same problem with accessing X apps as root with my 1st Archlinux install. the fix was to do, as user. xhost +local:root This can then be added as a shell script to KDE's autostart directory. The command xhost +local:root works ok on the Etch install that I'm having problems with. I do also have Archlinux installed on the same machine that I'm having this problem with Etch starting X apps, yet this Archlinux install, which I installed from the same cdrom, has no problems with su starting X apps. All a bit weird. When I do, while su'ed to root export DISPLAY=localhost:0, then as user run xhost localhost, where exactly are these commands being saved to? The only xhost file I can find is an executable (binary) in /usr/bin. Just trying to understand how all this stuff works. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch netinstl. problem starting kwrite, synaptic, gedit.etc
On Sunday 24 August 2008 23:37, [EMAIL PROTECTED] wrote: On Sun, 24 Aug 2008 23:16:46 +0200 Nigel Henry [EMAIL PROTECTED] wrote: On Sunday 24 August 2008 22:45, Shachar Or wrote: On Sunday 24 August 2008 23:36, Nigel Henry wrote: Having installed the Etch netinst. I was next looking to install KDE, and X. I ran apt-get install kde, and a whole bunch of packages were installed, including some X packages. After these had been installed, I also did an apt-get install kdm, as I wasn't sure if it had been installed, and it hadn't been. Reboot, and no desktop. Obviously some X stuff is missing. Now I tried apt-get install xserver, which gave some options, including xserver-xorg-core, which is the one I went for, and at the same time installed xfonts-75dpi, and xfonts-base. Some time later, and many more packages installed, I rebooted. The reboot went ok, and I was able via KDM to login to KDE. The problem I'm having is when su'ing to root in KDE's Konsole. When su'ed to root on KDE's Konsole neither kwrite, synaptic, or gedit will open. Synaptic is on the K menu, and starting it there will open a window asking for the the root password, and entering the root password I can use synaptic as root, but trying to open synaptic as root on KDE's Konsole just fails. Output from trying to start gedit, kwrite, and synaptic on KDE's Konsole below. [EMAIL PROTECTED] djmons]$ ssh 192.168.0.197 [EMAIL PROTECTED]'s password: Linux debian 2.6.26.2-rt1-libre1 #1 SMP PREEMPT RT Sun Aug 10 13:45:05 EEST 2008 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sat Aug 23 14:52:38 2008 [EMAIL PROTECTED]:~$ su Password: msu: Authentication failure Sorry. [EMAIL PROTECTED]:~$ su Password: debian:/home/djmons# synaptic X11 connection rejected because of wrong authentication. The application 'synaptic' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# kwrite X11 connection rejected because of wrong authentication. kwrite: Fatal IO error: client killed debian:/home/djmons# gedit X11 connection rejected because of wrong authentication. The application 'gedit' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# Any pointers as to what may be the problem here, gratefully received. You need sux instead of su. Nigel. -- Shachar Or | שחר אור http://ox.freeallweb.org/ When I try the command sux, I just get a command not found. Thanks for the reply though. I'm game for trying anything at the moment, and all replies/suggestions, no matter how off the edge, are welcome. Nigel. Have you tried apt-get install xorg jeff Well sux plus password works ok, but I've never had to use sux before on any distro. I did an apt-get install xorg, which pulled in a few more packages, and apart from some complaints about finding directories for fonts, which didn't appear to exist, but no change when running su, plus password, and kwrite, for example, which stiill failed to open. I also tried another suggestion, as below. quote the basic problem is that you are launching these programs as root, but your desktop is running as your user. So after su'ing run export DISPLAY=localhost:0 and as a user run xhost localhost. The export command sets the DISPLAY variable to your local machine, this variable is how X apps figure out what X server to connect to. The xhost command allows programs running on your local machine to connect to your desktop. end quote I don't think I made any typos. Having done an apt-get install xorg, and also the export stuff above, I still can't just simply su, plus password, and bring up kwrite for example. This is how things are at present, and hand written. Excuse any typos please. [EMAIL PROTECTED]: ~$ su Password: debian: /home/djmons# kwrite Xlib: connection to :0.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kwrite: cannot connect to X server :0.0 debian: /home/djmons# Any suggestions welcome, as usual. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Etch netinstl. problem starting kwrite, synaptic, gedit.etc
Having installed the Etch netinst. I was next looking to install KDE, and X. I ran apt-get install kde, and a whole bunch of packages were installed, including some X packages. After these had been installed, I also did an apt-get install kdm, as I wasn't sure if it had been installed, and it hadn't been. Reboot, and no desktop. Obviously some X stuff is missing. Now I tried apt-get install xserver, which gave some options, including xserver-xorg-core, which is the one I went for, and at the same time installed xfonts-75dpi, and xfonts-base. Some time later, and many more packages installed, I rebooted. The reboot went ok, and I was able via KDM to login to KDE. The problem I'm having is when su'ing to root in KDE's Konsole. When su'ed to root on KDE's Konsole neither kwrite, synaptic, or gedit will open. Synaptic is on the K menu, and starting it there will open a window asking for the the root password, and entering the root password I can use synaptic as root, but trying to open synaptic as root on KDE's Konsole just fails. Output from trying to start gedit, kwrite, and synaptic on KDE's Konsole below. [EMAIL PROTECTED] djmons]$ ssh 192.168.0.197 [EMAIL PROTECTED]'s password: Linux debian 2.6.26.2-rt1-libre1 #1 SMP PREEMPT RT Sun Aug 10 13:45:05 EEST 2008 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sat Aug 23 14:52:38 2008 [EMAIL PROTECTED]:~$ su Password: msu: Authentication failure Sorry. [EMAIL PROTECTED]:~$ su Password: debian:/home/djmons# synaptic X11 connection rejected because of wrong authentication. The application 'synaptic' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# kwrite X11 connection rejected because of wrong authentication. kwrite: Fatal IO error: client killed debian:/home/djmons# gedit X11 connection rejected because of wrong authentication. The application 'gedit' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# Any pointers as to what may be the problem here, gratefully received. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch netinstl. problem starting kwrite, synaptic, gedit.etc
On Sunday 24 August 2008 22:45, Shachar Or wrote: On Sunday 24 August 2008 23:36, Nigel Henry wrote: Having installed the Etch netinst. I was next looking to install KDE, and X. I ran apt-get install kde, and a whole bunch of packages were installed, including some X packages. After these had been installed, I also did an apt-get install kdm, as I wasn't sure if it had been installed, and it hadn't been. Reboot, and no desktop. Obviously some X stuff is missing. Now I tried apt-get install xserver, which gave some options, including xserver-xorg-core, which is the one I went for, and at the same time installed xfonts-75dpi, and xfonts-base. Some time later, and many more packages installed, I rebooted. The reboot went ok, and I was able via KDM to login to KDE. The problem I'm having is when su'ing to root in KDE's Konsole. When su'ed to root on KDE's Konsole neither kwrite, synaptic, or gedit will open. Synaptic is on the K menu, and starting it there will open a window asking for the the root password, and entering the root password I can use synaptic as root, but trying to open synaptic as root on KDE's Konsole just fails. Output from trying to start gedit, kwrite, and synaptic on KDE's Konsole below. [EMAIL PROTECTED] djmons]$ ssh 192.168.0.197 [EMAIL PROTECTED]'s password: Linux debian 2.6.26.2-rt1-libre1 #1 SMP PREEMPT RT Sun Aug 10 13:45:05 EEST 2008 i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sat Aug 23 14:52:38 2008 [EMAIL PROTECTED]:~$ su Password: msu: Authentication failure Sorry. [EMAIL PROTECTED]:~$ su Password: debian:/home/djmons# synaptic X11 connection rejected because of wrong authentication. The application 'synaptic' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# kwrite X11 connection rejected because of wrong authentication. kwrite: Fatal IO error: client killed debian:/home/djmons# gedit X11 connection rejected because of wrong authentication. The application 'gedit' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application. debian:/home/djmons# Any pointers as to what may be the problem here, gratefully received. You need sux instead of su. Nigel. -- Shachar Or | שחר אור http://ox.freeallweb.org/ When I try the command sux, I just get a command not found. Thanks for the reply though. I'm game for trying anything at the moment, and all replies/suggestions, no matter how off the edge, are welcome. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch netinstl. problem starting kwrite, synaptic, gedit.etc
On Sunday 24 August 2008 23:32, Shachar Or wrote: On Monday 25 August 2008 00:16, Nigel Henry wrote: You need sux instead of su. Nigel. -- Shachar Or | שחר אור http://ox.freeallweb.org/ When I try the command sux, I just get a command not found. Thanks for the reply though. I'm game for trying anything at the moment, and all replies/suggestions, no matter how off the edge, are welcome. Install the sux package. Thanks. That has resolved the problem. That said though, I still don't understand why a plain old su is not working, as it does on other distros, including my other Debian installs. Never mind. So now I have Sarge, Etch, and Lenny, where I can just use su + password to use GUI apps, but now with the new Etch install, I have to use sux + password to use the GUI apps. I am getting a bit old, and having to remember different commands for, in this case the same distro, that I have 2 instances installed, is a bit trying, but I suppose it keeps my brain active. Nigel. Nigel. -- Shachar Or | שחר אור http://ox.freeallweb.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem scrolling back in runlevel 2. Etch netinst
When working in runlevel 2, as with my Etch netinst, I'm unable to scroll back. for example I run lsmod, but only see what's on the screen, which is the tail end of lsmod. Now there must be some sort of basic window drawing ability, because nano works ok. Is there some similar app that I can start in runlevel 2 that I can use like a CLI, Konsole, for example, that I normally use when I have access to KDE's Desktop? I'm installing KDE, and the X window system at the moment, and usually with big installs, updates, etc, I save the Konsole history to my /home/user directory, suitably date stamped, and in my History-files dir. It's nice to be able to save the history like this, as it's easy to look back to when the system was last updated for example, and see just whick packages were installed, and any other stuff that was printed out while doing the updates. Thanks for any suggestions. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: strange usb trouble...
On Thursday 07 August 2008 05:54, Kai Martens wrote: Hi there, Some may remember me having trouble with my Compaq Presario SR1675CL - a noapic option got me to the point that I have a system now that works. One thing still puzzles me though: I cannot see any usb devices. Here are my diagnostics: family:/home/kai# grep -i usb /var/log/dmesg [0.089885] usbcore: registered new interface driver usbfs [0.089977] usbcore: registered new interface driver hub [0.090055] usbcore: registered new device driver usb [2.238005] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver [ 15.797635] Initializing USB Mass Storage driver... [ 15.797657] usbcore: registered new interface driver usb-storage [ 15.797660] USB Mass Storage support registered. So it does all that supposedly is to be done. Same grep on syslog, kern.log, and messages yields no additional information. BUT: and no usb device I plug in is detected (they get power though)... Where to look next? What other diagnostics to run? Or does anybody know what I am dealing with here??? Oh: one more diagonstic: [EMAIL PROTECTED]:~ uname -a Linux family 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 GNU/Linux As ususal: Many thanks in advance! Best, Kai Sorry for the delay in replying. There are 2 other host controllers you could try modprobing. I remember having problems with my usb midi keyboard not being detected on one install (Gentoo IIRC). One host controller was loaded, but I had to specifically load a different one to get the usb midi keyboard detected. Try the ones below. ehci_hcd uhci_hcd If one of them does result in your usb devices being recognised, add it to /etc/modules. btw. You don't have to remove the ohci_hcd, as they don't conflict with one another. Sorry for CC'ing you, but your post was a few days ago, and I'm not sure if you're still reading the list. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Fwd: Re: No sound problems on Intel board]
On Wednesday 13 August 2008 16:26, Frank McCormick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nigel Henry wrote: | On Tuesday 12 August 2008 22:57, Frank McCormick wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Sometime over the last few days I lost all sound on my system. Its | an intel board - audio apps tell me they can't open the sound device, | but when the system boots I hear a pop in the speakers as the drivers | are loaded. | | cat /proc/asound/cards | | 0 [ICH5 ]: ICH4 - Intel ICH5 | Intel ICH5 with AD1985 at irq 17 | | In a terminal/Konsole, what does typing alsamixer as user show? Perhaps | some | update or other has muted the sound, and you now need to unmute it. | Just a thought. | | Nope. Nothing is muted. | | Hi Frank. I should have realised that all the above output would be ok, when a | couple of posts back, you said that aplay was working ok. | | Did you run aplay as user, or root? ~ As a user. I am still in audio group. ~ I have since discovered SOME of the problem is caused by audacious...which not only doesn't play..but sits quietly sucking up 100% cpu. I have filed a bug. Cheers Frank Not using Sid, and wondering if pulseaudio may have been installed as a new package to your Sid install as part of the updates, I changed my /etc/apt/sources.list in Lenny to point to unstable, ran apt-get update, apt-get dist-upgrade (without doing the upgrade), but saw no mention of pulseaudio being installed as a new package. Of course, if you had already installed pulseaudio on your Sid install, it is possible that there may have been an update to it, which may have caused your sound to hit the fan . Saying that though, perhaps with pulseaudio installed, even aplay would not have worked (not sure on that). I don't have pulseaudio installed on my Lenny install, and from experiencing it on a Fedora 8 install, where my sound no longer worked, I quickly disabled it, and have no intention of using it on Lenny, or anything else for that matter. Have you tried other audio apps apart from audacious since the sound problems? I use Mhwaveedit for playing sound files, and it's available from the Debian repo's. I'm not sure what the default is for audio out, but if you try it, look in Edit/preferences/sound, and driver options. If by some obscure chance you do have pulseaudio installed, you can disable it by removing the package, alsa-plugins-pulseaudio, and if you're using KDE, as I am, this will also remove the package kde-settings-pulseaudio. Just a couple of thoughts Frank, as it's horrible when you use sounds a lot, then suddenly they are no more. All the best, and have a nice weekend. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Fwd: Re: No sound problems on Intel board]
On Tuesday 12 August 2008 22:57, Frank McCormick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sometime over the last few days I lost all sound on my system. Its an intel board - audio apps tell me they can't open the sound device, but when the system boots I hear a pop in the speakers as the drivers are loaded. 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) Subsystem: Intel Corporation Device e001 Flags: bus master, medium devsel, latency 0, IRQ 17 Memory at ffa7f800 (32-bit, non-prefetchable) [size=512] Memory at ffa7f400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 What do you you get from the following comands. cat /proc/asound/cards 0 [ICH5 ]: ICH4 - Intel ICH5 Intel ICH5 with AD1985 at irq 17 lsmod | grep snd snd_intel8x0 26268 1 snd_ac97_codec 88484 1 snd_intel8x0 ac97_bus1728 1 snd_ac97_codec snd_pcm_oss32800 0 snd_mixer_oss 12320 1 snd_pcm_oss snd_pcm62628 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 17800 1 snd_pcm snd45604 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 6368 1 snd snd_page_alloc 7816 2 snd_intel8x0,snd_pcm In a terminal/Konsole, what does typing alsamixer as user show? Perhaps some update or other has muted the sound, and you now need to unmute it. Just a thought. Nope. Nothing is muted. - -- Frank -- [EMAIL PROTECTED] Hi Frank. I should have realised that all the above output would be ok, when a couple of posts back, you said that aplay was working ok. Did you run aplay as user, or root? I ask because it sort of sounds like a permissions problem. If you did run it as root, it may be worth a look in /etc/group, and make sure that your user name is still attached to the audio group. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No sound problems on Intel board
On Tuesday 12 August 2008 16:21, Frank McCormick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sometime over the last few days I lost all sound on my system. Its an intel board - audio apps tell me they can't open the sound device, but when the system boots I hear a pop in the speakers as the drivers are loaded. here's the relevant output of lspci -v 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) Subsystem: Intel Corporation Device e001 Flags: bus master, medium devsel, latency 0, IRQ 17 Memory at ffa7f800 (32-bit, non-prefetchable) [size=512] Memory at ffa7f400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 Its a Sid system, up to date. Where should I start looking, as sound used to work with no problems. - -- Frank -- [EMAIL PROTECTED] Hi Frank. I presume this is after some updates to Sid. What do you you get from the following comands. cat /proc/asound/cards lsmod | grep snd In a terminal/Konsole, what does typing alsamixer as user show? Perhaps some update or other has muted the sound, and you now need to unmute it. Just a thought. I have Sarge, Etch, and Lenny installs, but havn't dared to go as close to the edge as Sid yet. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsa drivers; was Re: kernels for Lenny.
On Thursday 07 August 2008 11:46, [EMAIL PROTECTED] wrote: Nigel and anyone interested in alsa and USB development, nh ... both snd-intel8x0, and snd-hda-intel are being loaded, and it seems like they are both trying to grab card0, which is resulting in neither getting card0, and snd-usb-audio is getting card0, because the other 2 are having a non resolvable argument as to who gets card0. There are two sound devices. Intel 82801BA/BAM AC'97 on the system board and C-media USB plugged in. From my previous investigation. dalton:~# cat /proc/asound/cards 0 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed This is normal from a long time back, and in my case, when I was using Fedora Core 1. I have a usb midi keyboard, and it was always being set as card0, as the the usb starts early in the boot sequence, and consequently the actual sound card was unable to use the card0 slot, resulting in no sounds. The fix was to add the following lines to, in the case of Fedora's, /etc/modprobe.conf options snd-emu10k1 index=0(that's the actual soundcard) options snd-usb-audio index=1 (that's for the usb midi keyboard) If the C-Media is card 0, then the Intel device should be card 1. The Intel drivers should not involve a USB device ... unless it contains an Intel or Intel-like chip. I havn't found that that works. Logically yes, but in reality no. Looking back at my situation in Fedora 1 above (that is with no options set), the usb starts first in the bootup sequence, and thinks that my usb midi keyboard is a soundcard, and sets it as card0. the actual soundcard using the snd-emu10k1 driver is looking for setting itself as card0, but the slot for card0 has already been taken by the usb midi keyboard, and consequently the actual soundcard doesn't exist in /proc/asound/cards Btw, if I switch off the usb midi keyboard before booting, then bootup, the emu10k1 is set as card0, and if I then switch the usb midi keyboard on, that is set as card1, which is much as you see below. nh Try adding the 3 lines below to the bottom of the alsa-base file. There is a simple test before editing alsa-base. Unplug the C-Media device before starting the system and plug it after the on-board Intel chip is initialized. This is from my first trial. dalton:~# cat /proc/asound/cards 0 [I82801BAICH2 ]: ICH - Intel 82801BA-ICH2 Intel 82801BA-ICH2 with AD1885 at irq 17 1 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed Ok, I see where your going here. Having plugged in the C-Media device after booting up, the big question is, does the sound work? It should do, as snd-intel8x0 is set as card0 Which seems consistent with my hypothesis. Further hypothesizing: the Intel 82801 invokes snd_intel8x0 while the C-Media USB invokes snd_hda_intel. I'll try this unplug/replug procedure a few more times and report next week. USB and udev are appealing concepts but implementation is certainly non-trivial. Thanks for the help. Progress would be difficult without it. Regards, ... Peter E. Did you try adding the 3 lines that I suggested to /etc/modprobe.d/alsa-base? It would be nice to find out if the C-Media device is actually causing snd-hda-intel to load, thus causing the conflict when booting with the usb device plugged in. Just trying to help. Nigel. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernels for Lenny; was Re: Alsaconf halting a frozen laptop.
On Wednesday 06 August 2008 02:27, PETER EASTHOPE wrote: Nigel others, At Fri, 25 Jul 2008 21:39:40 +0200 N.H. wrote, ... Lenny install, I have the following kernels available. 2.6.8 2.6.11 With /etc/apt/sources.list set to lenny, dselect offers only 2.6.16 and 2.6.25. Can dselect install 2.6.11? Thanks,... Peter E. Hi Peter. I've only got the 2.6.8, and 2.6.11 kernels still on my Debian installs, because I've been continuously upgrading since Woody, and it was only a thought as those kernels were both pre udev IIRC, and may have been worth a try if it's udev by some chance, that is causing the problem with the 2 sound modules being loaded. Anyway, back to the sound problem. How about putting some option lines in /etc/modprobe.d/alsa-base. I hope I havn't already mentioned this. Try adding the 3 lines below to the bottom of the alsa-base file. options snd-intel8x0 index=0 options snd-usb-audio index=1 options snd-hda-intel index=2 I say this because at the moment both snd-intel8x0, and snd-hda-intel are being loaded, and it seems like they are both trying to grab card0, which is resulting in neither getting card0, and snd-usb-audio is getting card0, because the other 2 are having a non resolvable argument as to who gets card0. Having added the above lines, reboot, and check: cat /proc/asound/cards See if they are in the order you set with the options lines above, and more importantly, whether you have sound. There is something else to try, but have a go at that first. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: error messages from apt-get
On Friday 01 August 2008 17:10, Bob Cox wrote: On Fri, Aug 01, 2008 at 07:37:33 -0700, Vwaju ([EMAIL PROTECTED]) wrote: On Aug 1, 9:40 am, Jochen Schulz [EMAIL PROTECTED] wrote: Vwaju: I am setting up an internet server as a training exercise, using the O'Reilly book referenced at the top of this thread. The server is only for training (to learn Debian and networking). If it's not publicly available, you could do that. But since lenny is already on its way, I really don't see a point in that. What exactly do you need xlispstat for anyway? Couldn't you just go ahead without it? I tried leaving out xlispstat, but next I found that libdb3++-dev is also missing. (The search function is down on the Debian sight, so I don't know what libdb3++-dev is.) http://packages.debian.org/libdb3++-dev shows that this is also available only in Sarge. ..Package: libdb3++-dev Berkeley v3 Database Libraries for C++ [development] This is the development package which contains headers and static libraries for the Berkeley v3 database library. This is only for programs which will use the C++ interface. Many programs use the Berkeley Database to store their data. Other versions of the database can be found in the db2, db4.0, db4.1 and db4.2 packages.. Bob Cox. Stoke Gifford, near Bristol, UK. Registered user #445000 with the Linux Counter - http://counter.li.org/ Booting up my Sarge install (also have Etch, and Lenny) synaptic also shows other deps when installing libdb3++-dev, which it relies on, mainly: libdb3++c102, and libdb3-dev (I do already have libdb3 showing as installed, so that would no doubt be another dep if not installed, and if it was possible to install these packages on Etch). I suppose it's always a problem having a book that's basing it's instructions on a specific version of an operating system (couldn't find any reference to xlispstat in Sarge's synaptic though). OT, but I remember many years ago, when I was a lad, finding a circuit diagram, with list of components required for building an amplifier (this was in the days of valves (vacuum tubes (the big ones) 5z4g rectifiers, 6v6 output, and so on), and pressed steel chasis's. The tubes wern't a problem, but could I find a transformer with the correct voltages. No way jose. The power transformer needed the correct voltages for both LT, and HT, also be able to provide enough current for both to satisfy the requirements for the amplifier. Needless to say the amp never got built. I did start the wrong way around though. Rather than finding out if all the components were available, I had an old chasis lying around, so fitted the various bases for the tubes, wired everything up, all the caps, resistors, pots, and so on were in place, but no power transformer, or for that matter, an output transformer. Sorry for the OT ramble off into the distant past, but I suppose it makes the point that in today's computer age, things move very fast, and books when released, are probably already out of date where the info is for use on specific distro versions. It would be nice if everything could just slow down a bit. 5¢ worth of rambling. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Regarding Sarge updates
This is just a comment, as some folks have said that Sarge is a thing of the past, no longer supported, etc. I've just booted my Sarge install to check out deps for a certain package. As usual while booted into a distro, I run apt-get update, and Sarge is obviously still getting updates as an apt-get dist-upgrade shows 85 upgraded packages, and the need to get some 70.2MB of archives. The last time I ran apt-get update, apt-get dist-upgrade, according to my ~/History-files was on 20080109. I can't seriously believe it was that long ago, but time passes rapidly these days. Anyway the thing is that my Sarge still appears to be getting updates, although not the current stable (Etch) install. Also running Etch, and Lenny, but Sid is a bit too near the edge for me. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Regarding Sarge updates
On Friday 01 August 2008 21:22, Bob Cox wrote: On Fri, Aug 01, 2008 at 20:09:16 +0200, Nigel Henry ([EMAIL PROTECTED]) wrote: This is just a comment, as some folks have said that Sarge is a thing of the past, no longer supported, etc. I've just booted my Sarge install to check out deps for a certain package. As usual while booted into a distro, I run apt-get update, and Sarge is obviously still getting updates as an apt-get dist-upgrade shows 85 upgraded packages, and the need to get some 70.2MB of archives. The last time I ran apt-get update, apt-get dist-upgrade, according to my ~/History-files was on 20080109. I can't seriously believe it was that long ago, but time passes rapidly these days. Anyway the thing is that my Sarge still appears to be getting updates, although not the current stable (Etch) install. Security support for Sarge stopped at the end of March. http://www.uk.debian.org/News/2008/20080229 -- Bob Cox. Stoke Gifford, near Bristol, UK. Registered user #445000 with the Linux Counter - http://counter.li.org/ Hi Bob. Thanks for the reply. As I last updated in Jan, it looks like I'm just getting security updates until they ended at the end of March. Not sure where to go now. I don't like ditching old, unsupported distros, as sometimes folks who are still using them ask questions, and it's nice to be able to boot up Sarge for example, and answer their questions, if possible. I know that Lenny is going stable soon. What is the name for the new testing version?? Thanks for your reply. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alsaconf halting a frozen laptop.
On Sunday 27 July 2008 17:39, [EMAIL PROTECTED] wrote: Nigel, Progress! SUMMARY According to the outputs from lsmod below, the net effect of alsaconf is to remove snd_hda_intel. So, unless there is more specific advice, I should find how to prevent loading of snd_hda_intel at startup. Odd that removing snd_hda_intel makes sound work! Thanks, ... Peter E. nh Which kernel is your Lenny [on IBM NetVista] using? Currently only 2.6.25-2. nh Do you have an earlier kernel available to try, perhaps a 2.6.8, or 2.6.11 I can install one of them if necessary. nh When you bootup the IBM NetVista machine with Lenny on it, what do you get from the following commands. Hi Peter. Interesting from viewing the lsmod output below, that both snd-hda-intel, and snd-intel8x0 are being loaded, and also very weird. You should be able to just blacklist the snd-hda-intel module in /etc/modprobe.d/blacklist, but I've seen some folks having problems blacklisting modules, as they still seem to load. I'd suggest adding a line to /etc/modprobe.d/alsa-base, as below. install snd-hda-intel /bin/true Any module loaded into /bin/true goes to nowhere land. It's loaded, but does nothing, and is effectively sent into limbo. I've no idea why both modules are being loaded, but the above is worth a try. dalton:~# lsmod | grep snd snd_hda_intel 309976 0 snd_intel8x0 31740 0 snd_ac97_codec 91300 1 snd_intel8x0 ac97_bus1952 1 snd_ac97_codec snd_seq_dummy 3780 0 snd_usb_audio 75936 0 snd_pcm_oss37824 0 snd_mixer_oss 14880 1 snd_pcm_oss snd_seq_oss28544 0 snd_pcm68228 5 snd_hda_intel,snd_intel8x0,snd_ac97_codec,snd_usb_audio,snd_pcm_oss snd_usb_lib15744 1 snd_usb_audio snd_seq_midi8064 0 snd_seq_midi_event 6976 2 snd_seq_oss,snd_seq_midi snd_rawmidi22528 2 snd_usb_lib,snd_seq_midi snd_seq45872 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_hwdep 8708 1 snd_usb_audio snd_timer 21320 2 snd_pcm,snd_seq snd_seq_device 7564 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 48772 13 snd_hda_intel,snd_intel8x0,snd_ac97_codec,snd_usb_audio,snd_pcm_oss,snd_mix er_oss,snd_seq_oss,snd_pcm,snd_rawmidi,snd_seq,snd_hwdep,snd_timer,snd_seq_d evice soundcore 7488 1 snd snd_page_alloc 9992 3 snd_hda_intel,snd_intel8x0,snd_pcm usbcore 130032 9 asix,usbnet,snd_usb_audio,snd_usb_lib,usbhid,ehci_hcd,ohci_hcd,uhci_hcd dalton:~# cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31 16:40:16 2008 UTC). dalton:~# cat /proc/asound/cards 0 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed There is clearly some sort of conflict going on when both snd-hda-intel, snd-intel8x0 are being loaded, so that neither is detected as a sound card in /proc/asound/cards, and only your usb headphone set is detected, and set as card0 as no other cards can be found. dalton:~# lspci -v | pick out sound stuff 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02) Subsystem: IBM Device 01c6 Flags: medium devsel, IRQ 17 I/O ports at fe00 [size=16] Kernel driver in use: i801_smbus Kernel modules: i2c-i801 00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 Audio Controller (rev 02) Subsystem: IBM Device 01c6 Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at f000 [size=256] I/O ports at f400 [size=64] Kernel modules: snd-intel8x0 nh after running alsaconf, the output of. dalton:~# lsmod | grep snd snd_usb_audio 75936 0 snd_usb_lib15744 1 snd_usb_audio snd_hwdep 8708 1 snd_usb_audio snd_intel8x0 31740 0 snd_ac97_codec 91300 1 snd_intel8x0 ac97_bus1952 1 snd_ac97_codec snd_pcm_oss37824 0 snd_mixer_oss 14880 1 snd_pcm_oss snd_pcm68228 4 snd_usb_audio,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_seq_dummy 3780 0 snd_seq_oss28544 0 snd_seq_midi8064 0 snd_rawmidi22528 2 snd_usb_lib,snd_seq_midi snd_seq_midi_event 6976 2 snd_seq_oss,snd_seq_midi snd_seq45872 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 21320 2 snd_pcm,snd_seq snd_seq_device 7564 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 48772 12 snd_usb_audio,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_o ss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 7488 1 snd snd_page_alloc 9992 2
Re: Alsaconf halting a frozen laptop.
On Friday 25 July 2008 19:52, PETER EASTHOPE wrote: Folk, To get the on-board sound device of an IBM NetVista working I must run alsaconf almost every time Lenny starts. The first viewer of alsaconf mentions ... testing/sid ... *udev* is predestined to load your driver. Well, seeing that udev fails to load the driver in Lenny, I installed sid on an old Toshiba 4000CDS. hwinfo --sound reports nothing and there is no sound. I started alsaconf. When almost finished, it reports Loading driver There the system freezes solid. The power button has no effect. Is there any way to stop the beast other than by unplugging external power and removing the battery? Thanks, ... Peter E. Hi Peter. Firstly this is probably going to be of no help, as I don't have any laptops, and my Sarge, Etch, and Lenny installs are on a machine which has a well supported Creative Audigy2 soundblaster card. That said, perhaps you could provide a bit of info. leaving aside your Sid install on the Toshiba 4000CDS, Which kernels do you have available on your IBM NetVista machine. All my Debian installs were initially installed from Woody 3.0r2, and I have a bunch of kernels available, some of which are pre udev, For example on my Lenny install, I have the following kernels available. 2.6.8 2.6.11 Both these IIRC are pre udev, and you should have no problems running alsaconf when booting with these, and whatever alsaconf configures, should be saved over a reboot. I also have 2 kernels which I believe use udev, and sound still works ok in my case, as below. 2.6.17 2.6.21 Which kernel is your Lenny using? uname -r will give you this. Now I may be wrong here, but seem to have read that you shouldn't run alsaconf on kernels that are supposed to be setting up Alsa via udev, as it may mess some stuff up. As you say though that running alsaconf gets the sounds going, this may confirm that I'm wrong on this. Do you have an earlier kernel available to try, perhaps a 2.6.8, or 2.6.11, as I have? When you bootup the IBM NetVista machine with Lenny on it, what do you get from the following commands. lsmod | grep snd cat /proc/asound/version cat /proc/asound/cards and lspci -v (just the bit for the soundcard will do here) and perhaps, after running alsaconf, the output of. lsmod | grep snd cat /proc/asound/cards That's all I can think of at the moment, and may not be much help in resolving your problem. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems getting Etch in France
On Tuesday 22 July 2008 21:52, elijah r. wrote: Debian Etch ISO images are available for download, completely free, via the internet, just like those Fedora ISO's you are downloading. I highly recommend you get the single Debian NetInstall ISO. Since you are using a Dial-Up connection, this will be the fastest way to install Debian. On a side note, what kinds of problems were you running into when installing other distros? I had problems installing most distros on a computer I built that was using a motherboard with a VIA C3 processor, which is missing the CMOV instruction that some 686 binaries are compiled with. Cheers, Elijah Hi Elijah. I think that I'll go ahead and download the 1st cd iso, and see if it boots ok on this new machine with the Asus M2N-X Plus mobo. As your regards your question above. The first problem was that I had to disable ACPI in the BIOS, as neither install disks or live cd's would boot before doing that. Fedora 8 then installed ok, but post install wouldn't completely boot up, and got stuck at starting service ip6tables, and rebooting into runlevel 1, it got stuck at cpu frequency scaling (I think the messages said not supported in kernel). Rebooted, doing an interactive startup, and said No to a whole bunch of services starting, and then the bootup ran to completion. Kubuntu 7.10 was more of a problem. It would bootup as far as starting KDM, then it obviously was trying to startx, and present the KDM splash screen, but all I got was a black screen, with a mouse pointer, but everything was locked up, no mouse movement, no keyboard, the whole machine had just stopped, and I had to do a hard reset. After some time, and trying various incantations on the kernel line, I eventually removed the part which said force-vesa, and added acpi=off. Enter, then it booted up, and tried to startx a couple of times, then dropped me to the command line. Tried, just for fun, startx, and it logged me straight in to KDE, with no problems. Now Kubuntu Gutsy Gibbon 7.10, is live cd, but when booted up, has a desktop icon to install to harddrive, and I was able to install it ok, but still have to append the kernel line, with acpi=off, otherwise when booting up it locks everthing up when it gets as far as opening the KDM splash screen, needs a hard reset. Kubuntu Breezy installed ok, and I have all the updates for upgrading to Dapper on another harddrive. Having upgraded it, I tried booting with the later 2.6.15-52-386 kernel (the Dapper one), and again it got stuck at opening the KDM splashscreen. I rebooted it appending the kernel line to boot into runlevel 3, as I wanted to check any messages, as to what the problem might be. It didn't boot into runlevel 3, but strangely opened the KDM splashscreen, and I was able to login ok. Adding 3 to the kernel line in /boot/grub/menu.lst, it now boots up ok, but all a bit weird. All of this is why I need at least the 1st i386 cd for Etch, so that I can see any similar problems on this new machine, when trying to install Etch. I don't know if the netinstall cd would do. Does it use the same installer, as on the 1st i386 cd for Etch? Thanks folks, for all the suggestions, and many apologies for anything I said yesterday. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems getting Etch in France
On Wednesday 23 July 2008 16:49, elijah r. wrote: I don't know if the netinstall cd would do. Does it use the same installer, as on the 1st i386 cd for Etch? I am pretty sure it is exactly the same, but it grabs installation packages from the internet instead of from the local CD/DVDs. Also, I wasn't sure whether you had tried passing the acpi=off parameter to installation bootloaders, or just to the bootloaders on your hard disk after installation. I've had some issues with certain motherboards not even booting off of installation CD/DVDs unless I pass something like acpi=off noapic to the boot options. So, if the boot prompt for some installation CD is is boot: you usually just type linux acpi=off noapic or vmlinuz acpi=off noapic or something along those lines. Well I've got Fedora 8 booted up on this new machine at the moment, and am downloading the debian-4.0r3-i386-netinst.iso. As I previously said, to boot post-install Fedora 8, I had to stop some services from being started, and looking in /boot/grub/grub.conf, it seems like I'd had to add both noapic, and nolapic to the kernel line. can't say that I'm too clued up on acpi, even though reading the man pages. As for the other issues you have had, such as with KDM working/not working and the runlevels failing, they seem erratic, which many times can be hardware-related. What kind of processor do you have? Have you run memtest on your memory? Have you tested your hard disk to make sure it doesn't have bad blocks or other errors? Processor is AMD Athlon 64 3800+, which is one of the 3 suggested for the Asus M2N-X Plus mobo. I havn't run memtest on the memory yet. The memory comprise of 2x1GB of Crucial Ballistix, which Crucial say is fine for this mobo. Nigel. Cheers, Elijah -- http://elijahr.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems getting Etch in France
On Monday 21 July 2008 22:50, Gerard Robin wrote: On Mon, Jul 21, 2008 at 10:17:39PM +0200, Nigel Henry wrote: From: Nigel Henry [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Problems getting Etch in France X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on liszt.debian.org X-Spam-Level: X-Spam-Status: No, score=-9.3 required=4.0 tests=LDOSUBSCRIBER,LDO_WHITELIST, MURPHY_FINANCE6 autolearn=failed version=3.2.3 The only place I can find in France that has Etch DVD's available, wants payment via paypal, and Visa. I have neither, only my local banks Carte Bleue. I'm currently downloading 6 iso's for Fedora 9 on dialup, and am not too bothered about the time it takes. All my current Debian Installs, Sarge, Etch, and Lenny, were installed using my Woody 3.0r2 disks. I have a new machine, and don't want to go through the hassle of upgrading Woody to Sarge, then Etch, along with the transition to xorg again. Could someone kindly point me to where I can get the base install for Etch, including KDE. I don't mind downloading 4 or 5 iso's if this is necessary. Many thanks for any help with this problem. Do you know ikarios ? http://www.ikarios.com/p374-Debian.html hth. -- Gérard Well Ikarios have what I want, but only will accept payment by chéque bancaire, and I can't use my carte bleue for paying online. This is incredible in the 21st century. I have to write out a cheque, get on my bike, and ride 20 mins to the post office, perhaps stand in a queue for 20 mins to buy a stamp (un timbre), then post it. 10 days later I may receive my Debian disks. I give up. I have built a new machine, and have had problems with installing Fedfora 8, Archlinux, and Kubuntu Gutsy Gibbon (7.10). Having got these distro's installed, I want to get Debian Etch installed. I only have Woody 3.0.r2 discs, and don't want to go through the hassle of upgrading to Sarge, then Etch, along with the transition from xfree86 to xorg again. Oh to hell with Debian. I have Sarge, Etch, and Lenny on another machine, and really wanted to see if there were problems installing Etch on my new machine, where I've had problems installing other distros. N. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems getting Etch in France
On Tuesday 22 July 2008 21:50, Arthur A wrote: I give up. snip Oh to hell with Debian. snip N. Problem solved. The probelm is not solved Arthur A I'm a wanker The problem is that I live in France, and to say the least it's a problem to buy Debian CD/DVD sets, and pay for them using my Carte Bleue. I do have Sarge, Etch, and Lenny installed on one machine, but want to see if there are problems installing Etch on my new machine, where I've had problems installing other distro's, Fedora8, Archlinux (Don't Panic), and Kubuntu Gutsy Gibbon 7.10.. If you have nothing better to say than problem solved then bugger off, and go and play with yourself. Sorry if I'm being sarcastic, but all I want to get is Debian Etch CD's from somwhere or other, either paid for, or downloadewd from the Internet. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
On Monday 21 July 2008 13:27, Andrei Popescu wrote: On Mon,21.Jul.08, 03:55:20, Dominik Dera wrote: Andrew Sackville-West wrote: and the blacklisting won't work if the module is in your initrd! You at least need to run update-initramfs and you would probably be advised to unpack one to make *sure* it's not in there... This problem can be solved by removing 8139cp module, and afterwards updating initramfs. So it goes like this: rmmod -v 8139cp update-initramfs -uv This will not survive a linux-image update. Regards, Andrei Personally, I've never found any problems with both modules being loaded. I've had to add 8139too to /etc/modules, and both are loaded, and I think the bootup messages complain about 8139cp, and then goes on to say using 8139too. If the blacklisting won't work, I've had success with loading the unwanted module to /bin/true, where it's loaded into nowhere land. Add a line to a file in /etc/modprobe.d. I don't know if it matters which file you add it to, and I put it, in the case of pcspkr in the alsa-base file. See below. install 8139cp /bin/true Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Motherboard for desktops with preinstalled Debian
On Monday 21 July 2008 12:22, Nuno Magalhães wrote: I'm running Sid on an Asus M2NPV-VM: http://www.asus.com/products.aspx?l1=3l2=101l3=0model=1138modelmenu=1 I'm happy with it but i haven't explored all of its capabilities (tv out and front audio for instance). Still, Asus seems like a safe bet. The processor is an AMD Athlon64 3500+ (2.2GHz PIB, AM2 socket, 512KB cache). I did need to disable apic when booting the Debian installer, something like linux noapic nolapic, otherwise it would freeze somewhere along the boot process. HTH I recently built a new machine (for the first time) with an Asus M2N-X Plus mobo, AMD Athlon64 3800+ AM2 CPU. No onboard graphics, but perhaps that's normal these days, so bought and Asus EAX1550 Silent PCI-express grahics card (Intel chip). 2x1GB Cruciaal Ballistix RAM. I couldn't boot any install disks, or live CD's before first disabling ACPI in the mobo's BIOS. I havn't got Etch on it at the mo, because I only have Woody discs, and don't want to go through the performance of upgrading from them again on this new machine. I do have Fedora 8, Archlinux (Don't Panic), and Kubuntu Gutsy Gibbon 7.10 installed on it though. All with some install, and post install boot problems. Now it's a few weeks ago, but I couldn't get Kubuntu GG to install, so looked through my disks for recent distros, and tried Fedora 8. It installed ok AFAIR, but wouldn't boot post install. Puzzled, I removed the rgb quiet bit from the kernel line, and found it was hanging at start ipV6tables, rebooting into runlevel 1, it was also hanging at cpu frequency scaling, or something like that, so I rebooted, and as you are able to do with Fedora, selected Interactive mode, and said No to a whole bunch of services starting, that I didn't need, and miracle of miracles it booted up. Quite which service was causing the problem, I've no idea, but Fedora 8 is running ok now on this new machine. then installed Archlinux, and I don't think there were problems with that, but I think that I've had to append the kernel line with acpi=off. I'll have to check on that. Now back to Kubuntu GG. Big problems in little china here. This is basically a live cd, and when booted has a desktop icon to install the distro to the harddrive. When you put the disk in, there is an option to append the kernel boot line, so I tried allsorts of incantations, acpi=off, noapic, nolapic, and nothing got me off the ground. Earlier on in the kernel boot line was a bit saying something like force vesa, which I then removed. Now I know it's an ATI graphics card, and sometimes there are problems with ATI drivers, so thought that forcing vesa would be a good backup, and should work, but not in this case. Having removed the force vesa bit, and adding acpi=off to the kernel line, Ibooted, and lo, and behold we were on our way. The bootup proceeded, and tried to startx a couple of times, then dropped me to a command prompt. Feeling a bit fed up now, I thought I may as try something, and typed startx, and must say that I was surprised by seeing the KDE desktop starting up. Clicked on the desktop icon to install to the harddrive, and it installed ok. I do have to append the kernel line in Grub with acpi=off, as otherwise the bootup progresses as far as startingx, and kdm, and then everything locks up. No mouse, no keyboard. The machine has effectively stopped doing anything. There are still problems though. I did all the updates overnight for Archlinux, and the following morning the mouse pointer was locked up. The keyboard was working, so could reboot ok. I had the same problem with Kubuntu GG, with the mouse pointer locking up. I've found some ways to resolve the mouse pointer problem, including just pressing the changeover button on the KVM switch, which effectively takes power off the mouse, then puts the power back on ( I think that may be a problem with my A4 tech scrollball mice though). The lockup problem has progressed now though. I'm currently downloading cd iso's for Fedora 9 on dialup using my Kubuntu GG. I'm now getting complete lockups, even during the daytime. No mouse, no keyboard, and the machine has stopped processing. Ironically today while running tail -f /var/log/messages, I've been trying to reproduce the lockup, and perhaps get some printout, as to what's going on, but no-go. I cannot get the machine to lockup when I want it to. I think it's put the hex on me. Enough rambling. the thread's about Asus mobo's. Yes I've had problems installing, and still problems that may be related to the mouse, and graphics card that I am using. I've found a source in France for Etch 3 DVD sets, at 15€, which ain't bad, so will order this evening, and see if Etch will install, and work ok on this new machine. Apologies for the bandwidth useage. Nigel. btw: I'll post back when I get the Etch DVD's, as to any problems installing, and running on the Asus M2N-X Plus mobo.
Re: 8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
On Monday 21 July 2008 17:42, Andrew Sackville-West wrote: On Mon, Jul 21, 2008 at 02:24:46PM +0200, Nigel Henry wrote: On Monday 21 July 2008 13:27, Andrei Popescu wrote: On Mon,21.Jul.08, 03:55:20, Dominik Dera wrote: Andrew Sackville-West wrote: and the blacklisting won't work if the module is in your initrd! You at least need to run update-initramfs and you would probably be advised to unpack one to make *sure* it's not in there... This problem can be solved by removing 8139cp module, and afterwards updating initramfs. So it goes like this: rmmod -v 8139cp update-initramfs -uv This will not survive a linux-image update. Regards, Andrei Personally, I've never found any problems with both modules being loaded. I've had to add 8139too to /etc/modules, and both are loaded, and I think the bootup messages complain about 8139cp, and then goes on to say using 8139too. If the blacklisting won't work, I've had success with loading the unwanted module to /bin/true, where it's loaded into nowhere land. Add a line to a file in /etc/modprobe.d. I don't know if it matters which file you add it to, and I put it, in the case of pcspkr in the alsa-base file. See below. install 8139cp /bin/true make a local file in modprobe.d so that updates to those files won't bork your custom stuff. A Thanks for that suggestion Andrew. With Fedora it's easy, as it's all added to /etc/modprobe.conf. I've always been a bit confused as to where to add options lines, etc, in my Debian installs /etc/modprobe.d, as there are so many files in this directory. Obviously some are a no-go, but it becomes a bit hit and miss, like close your eyes, and stick a pin in. Ok I'll put the option in this one. I'll definately create a local file, and use this in the future. Thanks again. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems getting Etch in France
The only place I can find in France that has Etch DVD's available, wants payment via paypal, and Visa. I have neither, only my local banks Carte Bleue. I'm currently downloading 6 iso's for Fedora 9 on dialup, and am not too bothered about the time it takes. All my current Debian Installs, Sarge, Etch, and Lenny, were installed using my Woody 3.0r2 disks. I have a new machine, and don't want to go through the hassle of upgrading Woody to Sarge, then Etch, along with the transition to xorg again. Could someone kindly point me to where I can get the base install for Etch, including KDE. I don't mind downloading 4 or 5 iso's if this is necessary. Many thanks for any help with this problem. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound doesn't work on my system (lenny)
On Thursday 17 July 2008 18:54, Anton Liaukevich wrote: Ron Johnson wrote: On 07/17/08 11:07, Anton Liaukevich wrote: Sound doesn't work on my system. Neither system sounds in KDE, nor music123, nor vlc utter sound. My hardware: Sound is integrated (AC'97) motherboard: Epox 8RDA3I rev 3.3 northbridge: nForce 2 Ultra southbridge: MCP AC'97 codec: from Realtek My software: Debian lenny kernel: linux 2.6.24-1-686 Is sound muted? Which sound modules are installed? $ lsmod | grep ^snd Installed modules: $ lsmod | grep ^snd snd_intel8x0 32028 0 snd_ac97_codec 92932 1 snd_intel8x0 snd_pcm_oss38272 0 snd_pcm71780 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_mixer_oss 15296 1 snd_pcm_oss snd_seq_dummy 3780 0 snd_mpu401 8008 0 snd_mpu401_uart 8000 1 snd_mpu401 snd_rawmidi22624 1 snd_mpu401_uart snd_seq_oss29472 0 snd_seq_midi_event 6976 1 snd_seq_oss snd_seq46544 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_timer 21092 2 snd_pcm,snd_seq snd_seq_device 7820 4 snd_seq_dummy,snd_rawmidi,snd_seq_oss,snd_seq snd48612 12 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_mpu401,sn d_mpu401_uart,snd_rawmidi,snd_seq_oss,snd_seq,snd_timer,snd_seq_device snd_page_alloc 10056 2 snd_intel8x0,snd_pcm Hi Anton. I notice that the soundcore module doesn't show on your lsmod, which it does on my Lenny install, but with a different soundcard. does your full lsmod show the soundcore module installed? What do you get if you run. cat /proc/asound/cards Is your soundcard listed as card0? Just another thought. Are you as user listed as a user for the audio group in /etc/group? Try alsamixer on the CLI as user. Perhaps there are controls muted. the M key unmutes them. Perhaps sliders just need to be pushed up a bit. It's usual for alsamixer to set things at a low level, to protect your speakers, and ears. I have just built a new machine which has a MCP61 southbridge, but don't have Lenny installed on it yet, and anyway the mobo is using snd-hda-intel. Sounds work ok, and the nearest to Lenny that is installed, is Kubuntu Gutsy Gibbon at the moment. The latest kernel on my Lenny install is 2.6.21-2-686, but I did see some problems on the alsa-devel list with either 2.6.24, or 2.6.25 kernels, and MCP51, MCP61, and some other (sorry I've dumped the post). it will be in the alsa-devel archives though. All I can think of at the moment. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to add ether net card in etch
On Wednesday 16 July 2008 14:51, Serena Cantor wrote: I have etch. Now I add a Ethernet card The card use e100 module in kernel 2.4/sarge but e100 in etch does not seem to work. Hi Serena. Is the e100 module loaded? Post the ouput of lsmod please. I know that I had some problems with the driver not being loaded for my Realtek 8139 network card, and had to add 8139too to /etc/modules. If the module is not seen in your lsmod, su to root on the CLI, and do a. modprobe e100, then check lsmod again. If the network card is now showing in lsmod, add it to /etc/modules, and when you reboot, it should be loaded automatically. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: i386 or amd64?
On Sunday 13 July 2008 17:05, Hugo Vanwoerkom wrote: Hi, I am about to buy the mobo that Doug Tutty has: Asus M2N-SLI Deluxe, albeit with a more moderate AM2 processor: AMD Athlon X2 4050e 2.1GHz 45W 65nm Dual-Core. Question I have is what do I run on it, I would prefer restoring a current i386 system on it and then go on from there. So I found this: http://lists.debian.org/debian-amd64/2005/07/msg00311.html which lists 6 options: 1) Install i386 version and use that using 32bit kernel. 2) Install amd64 version and use that. 3) Install i386 with amd64 kernel package (i386 sarge includes that) and amd64-libs to allow running some 64bit programs and most 32bit (iptables/alsa-utils and other things that talk to some kernel interfaces have to be 64bit when used with a 64bit kernel I believe). 4) Install amd64 version and ia32-libs to allow running some 32bit programs and all 64bit. 5) Install i386 with an amd64 kernel package and a 64bit chroot to play with full 64bit stuff in. (I use this one at the moment). 6) Install amd64 with a i386 chroot to run 32bit packages in. I would prefer 1) but how does one do that? Hugo Hi Hugo. Just go ahead and install the i386 version of your distro. It will work with the 64bit processor with no problems. I recently built a new machine, using an Asus M2N-X Plus mobo, with an AMD Athlon64 3800 AM2 2.4GHz processor. I've installed i386 (32bit) versions of Archlinux, Kubuntu Gutsy Gibbon, Fedora 8, and Kubuntu Breezy (upgraded to Dapper) on it, and no problemos. I've got Sarge, Etch, and Lenny on another machine, and they were all upgraded from my valuable Woody 3.0r2 cdroms, and don't want to go through that hassle of upgrading to Etch from Woody on the new machine. I've just found a supplier in France that has 3DVD sets for Etch for 15€, so I'll get those, and save a bit of upgrading time, when I add Etch to the new machine. If you have sufficient harddrive space, why not install both the i386, and the x86_64 versions, and you can compare them. I think for a 64 bit install there are some packages (probably 3rd party ones) that you have to go through the hoops a bit, to get them to work, which is probably why I've stayed with i386. When AMD brought out their first 64 bit processor (in 2003 IIRC) there was much marketing hype as to how superior it was compared to 32 bit processors, but I've also read that there is not a lot of difference between i386 (32bit), and x86_64, but having no experience in comparing the two, I'm simply going on what I've heard. Sunday afternoon/evening rambling over, and now back to mowing the grass. My dog's looking at me in an expectant way, as he has a bunch of fun in the garden when I'm mowing. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf says No supported PnP or PCI card found
On Monday 07 July 2008 12:19, Luc Saffre wrote: Hello, I just bought a desktop PC with a GeForce6100SM-M mainboard whose NVIDIA MCP61S chipset is High Definition Audio Specification 1.0 compliant. I installed the latest stable Debian (2.6.18-6-486), everything worked well so far... except that there is no sound. alsaconf says No supported PnP or PCI card found big snip Luc Hi Luc. I've just recently built a new machine with an Asus M2N-X Plus mobo, which has Geforce 6100, and MCP61 southbridge. I havn't got Etch installed on, but sound is working ok with Kubuntu Gutsy Gibbon, Archlinux Don't Panic, and Fedora 8. One thing to check is that the Azalia codec is set to auto in the BIOS, and not disabled. It could also be that the alsa driver, alsa-utils, and alsa-lib arn't recent enough on your Etch install. I've got Etch on a different machine, and no problems with sound, but that's with an Audigy2 soundblaster card, but according to cat /proc/asound/version the alsa driver is only 1.0.12rc1. My Kubuntu GG install, where sound works has version 1.0.15 (still a bit old), and that's with a 2.6.22-15-generic (SMP) kernel. Just a couple of thoughts. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DigiVox A/D TV-Tuner issue
On Sunday 06 July 2008 10:53, Anas Husseini wrote: Hi again Nigel, Thank you for the tutorial. Actually I made a deep search in google before and that's one of the tutorials I've found then. Most of these tutorials I found contain essentially the same steps, so I applied them (compiling the v4l-dvb-kernel, downloading the corresponding firmware, modeprobing the modules, etc). However, there is one thing I failed to do, that is obtaining the v4l-dvb-kernel through the mercurial command (hg clone) because I always get a HTTP 503 error when I try to access that website ( http://mcentral.de). Thus, I managed to download the a package called v4l-dvb from linuxtv.org and compiled it successfully. I don't know if that is an enough substitute to the mercurial command. Perhaps it is one cause of this issue. I appreciate your kindness in proposing that you buy the tv-tuner and try it yourself. I don't know wether it is available in France (actually its price is about 30 to 40 USD), but I don't want you to take the trouble. I am trying now other packages from linuxtv.org (those related to v4l or em28xx) hoping that I may find a beam of light in them. I will try also the tv-tuner on another PC that has USB 2.0 support. Thanks again for your continuous help. - Anas Hi Again Anas. The card isn't going to work on your laptop with only USB1.1 available. The page below gives some info about USB standards. http://www.linuxtv.org/wiki/index.php/DVB_via_USB When I was looking to see the price of these cards in France, the specs on one site simply mentioned that the card was a USB one, and none specific about the USB version required, but the MSI site for the DigiVOX A/D 11 specifically mentions that USB2 is required. According to another page I read, even if your laptop had a USB2 controller, the 2.6.18 kernel on Etch is not late enough (is missing some of the necessary drivers/modules), and it was suggested to install the latest kernel from the backports repo. I only say this because, if your other PC that has USB2.0 available, and you only have Etch installed with a 2.6.18 kernel, you will still have problems, unless you install a later kernel. I've found the page,as below. http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers I think that you've already been on this page, as you mentioned problems with mercurial, and installing Linux TV drivers. All the best. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Package requirements installation
On Sunday 06 July 2008 18:21, Ron Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/06/08 10:34, Rodolfo Medina wrote: During the installation of gnome-mplayer, at the `./configure' step it is complained the lack of the following packages: gtk+-2.0 You need to install libgtk2.0-dev. $ apt-cache search libgtk | grep 2. | grep dev | sort libgtk-directfb-2.0-dev - Development files for the GTK+ library - DirectFB version libgtk1.2-dev - Development files for the GIMP Toolkit libgtk2.0-dev - Development files for the GTK+ library libgtkada2-dev - Development files for libgtkada2 libgtkdatabox-0.8.2-dev - A Gtk+ library to display large amounts of numerical data libgtkextra-x11-2.0-dev - A useful set of widgets for GTK+ (development files) libgtkgl2.0-dev - OpenGL area for GTK (development files) libgtkglextmm-x11-1.2-dev - C++ bindings for GtkGLExt (Development files) libgtkhtml2-dev - HTML rendering/editing library - development files libgtkmm-2.4-dev - C++ wrappers for GTK+ 2.4 (development files) libgtkmm-dev - C++ wrapper for GTK+ 1.2 (development files) libgtksourceview2.0-dev - development files for the GTK+ syntax highlighting widget libgtksourceviewmm-2.0-dev - C++ binding of GtkSourceView - development files glib-2.0 Similarly, libglib2.0-dev. $ apt-cache search libglib | grep 2. | grep dev | sort libglib1.2-dev - The GLib library of C routines (development) libglib2.0-dev - Development files for the GLib library libglibmm-2.4-dev - C++ wrapper for the GLib toolkit (development files) gthread-2.0 This is the tricky one. From a Google on gthread-2.0, it appears to be one of the installed files when you install libglib2.0-dev, which I verified in synaptic for installed files on my Lenny install. /usr/include/glib-2.0/glib/gthread.h and further down the list of installed files /usr/lib/libgthread-2.0.la and further down again /usr/lib/pkgconfig/gthread-2.0.pc Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DigiVox A/D TV-Tuner issue
On Saturday 05 July 2008 10:51, Anas Husseini wrote: Hi Nigel, I probed the module v4l2-common, but with no effect. The /dev/video0 can't still be accessible as it seems (even with xawtv, it gave the same error message content). Perhaps the problem is a usb-interface problem (even though the module uhci-hcd is loaded). The USB ports in this laptop are version 1.1 and it may be the cause that the TV-Tuner is not identified as a video source. I may try it on another PC having USB 2.0. Thanks again. - Anas Hi again Anas. Well I wasn't sure if USB2 devices would work on a mobo that only had USB1.1, but looking at the hardware forum at www.linuxquestions.org, apparently they do, but obviously not with the USB2 transfer rates. I also found a bit of info on ohci-hcd, uhci-hcd, and ehci-hcd, which I didn't know before. Both ohci-hcd, and uhci-hcd are for USB1.1 controllers on the mobo, but I don't know how they differ, and do know that for getting my usb midi keyboard working on one of my distros, I had to specifically load uhci-hcd. The ehci-hcd appears to be specifically for USB2 controllers, and I verified that by looking at lsmod on a new machine that I've just built which has USB2, and both ohci-hcd (USB1.1), and ehci-hcd (USB2), are loaded. Going back to your MSI DigiVox A/D TV card, I found this link on Google, which seems to be saying that you need to load some firmware, to get the card working. Now I don't know anything about loading firmware, but the link with details is below. http://www.2nrds.com/digital-tv-in-linux-with-em28xx-devices Scroll down a bit to where it says: Some users will need a firmware file to make their devices work., and you'll see that the MSI DigiVox A/D needs firmware version2 Scroll down a bit more, and there's a link to where to get the firmware from. Some of the stuff on the page I've provided the link to above, may not be necessary, and it's for using the TV card with Kaffeine, not xawtv, or tvtime, but it does appear that you have to load firmware for your TV card. This may not be much help, but see how you get on with it. All the best. Nigel. btw: If the card is not too expensive, and available in France, I might buy one, and give it a try on both a machine that only has USB1.1, and my new machine that has USB2. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DigiVox A/D TV-Tuner issue
On Friday 04 July 2008 13:51, Anas Husseini wrote: Hi everybody, I am facing problems with my DigiVox TV-Tuner. I am working on debian etch (kernel 2.6.18), and have installed the necessary modules for the tv-tuner (v4l, linux-source, linux-headers, etc), and modprobed the corresponding kernel modules, but whenever I try to receive the input video (using tvtime for example), it said that /dev/video0 cannot be accessed (or found). I tried to create /dev/video0 using mknod and chmod 666, but it didn't work neither. What else should be done? Hi Anas. cannot be accessed (or found) could be a permissions problem. Are you as user a member of the video group? See /etc/group. Would you post the output of, lsmod | grep video. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DigiVox A/D TV-Tuner issue
On Friday 04 July 2008 15:15, Anas Husseini wrote: Hi Nigel, my user is already a member of the video group, and the /dev/video0 permission is 666. Here are the ouputs of lsusb and lsmod | grep video respectively: Bus 001 Device 005: ID eb1a:e310 eMPIA Technology, Inc. videodev31936 2 tuner,em28xx v4l1_compat 12900 1 videodev videobuf_vmalloc6820 1 em28xx videobuf_core 17124 2 em28xx,videobuf_vmalloc tvtime is still saying: No such device, cannot open capture device /dev/video0 By the way, when I plug the tv-tuner, the device name eb1a:e310 doesn't appear in dmesg output. Thank you for assistance. - Anas Hi Anas. First I must say that I didn't realise it was a USB TV card, and I don't have much experience of USB stuff (my tv card is an Hauppauge wintv express PCI card). Anyway, that said, I compared your lsmod with the deps listed for the em28xx driver in modinfo, su to root and run modinfo em28xx, to see for yourself. Deps below. i2c-core,usbcore,videodev,tveeprom,ir-common,v4l2-common,v4l1-compat,compat_ioct132 Now I didn't expect to see some of these in your lsmod | grep video, but v4l2-common should be there. As I say I'm not familiar with USB TV cards, but all these modules should be loaded automatically when you either boot with the device plugged in, or when you plug it into a booted machine. One module I did have to modprobe though, and that was for my USB midi keyboard was the uhci-hcd host controller interface driver, and subsequently added it to /etc/modules, so that it would be loaded automatically. There are a couple of others as well ehci-hcd, and ohci-hcd, but only the uhci-hcd shows in my lsmod. If you look at your lsmod, I'm sure at least one of these should be loaded for USB devices to work. I've never had any success with tvtime, and use xawtv. If you have that installed, run as user, xawtv -hwscan, both with the tv card unplugged, and plugged in. It doesn't give much info, but should show the video device that your tv card is using, if all the necessary modules are loaded. I can't think of anything else at the moment, but gives you a bit to go on with. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Script for when system was last updated
On Monday 02 June 2008 22:57, Mumia W.. wrote: On 06/02/2008 01:14 PM, Nigel Henry wrote: [...] Could someone suggest a script I could put in ~/.kde/autostart that would put up an xmessage saying when the system was last updated, when I boot up Lenny? Much appreciation to all you scripting gurus out there. Nigel. I'm hardly a scripting guru, but this may help you a bit: #!/bin/bash hist_files=$HOME/tmp/tmp/history-files lastupd=`ls $hist_files | sort -n | tail -1` xmessage The system was last updated on $lastupd Hi. Thanks for the little script. I have a problem understanding the hist_files= line. The xmessage just says The system was last updated on, and no date of the lastupdate is mentioned. I ran ls /home/djmons/History-files | sort -n | tail -1, and the date of the latest file is printed out in the shell, so that bit is working ok. I did change history-files to History-files on the hist_files= line, to reflect the correct name for the directory where the history files are kept, but no change. What does the /tmp/tmp signify on that line. It seems as if the path to where the history files are is not correct. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
