Vuze (Azureus) broken after Apt-get upgrade
I am running a 64-bit system, unstable, with kernel 2.6.31-1. Every week or so, I run apt-get update, apt-get upgrade, to keep system reasonable up to date. I am running no firewalls on my system, which is on a home network behind a dsl modem/router. This week, after running apt-get update, Vuze no longer connects. After startup, I get a popup window with the following error: Warning: Impossible to bind to a local socket. Loading of torrents via command line parameter will fail until is fixed No other programs appear to be affected. Web browsers and email clients still run as before. Has anyone else seen this problem, and is there a solution? I am not yet subscribing to any Vuze mailing lists, and Google has not provided a pertinent solution for me. Thanks for any help or pointers. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
OpenOffice.org broken in AMD64 Sid?
After a recent apt-get upgrade, my Sid system (AMD64) no longer will run OpenOffice. I can't access my Word-formatted documents. Running apt-cache showpkg openoffice.org (printout attached) indicates broken package. Is this correct, or am I misinterpreting the output? If correct, does anyone know the nature of the problem and when it might be corrected? Thanks for any info. Regards, Russ Package: openoffice.org Versions: 1:3.0.1-4+b1 (/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_binary-amd64_Packages MD5: 3a3a669d7923ec519e9788b950a32978 Reverse Depends: openoffice.org-writer,openoffice.org 1.9 openoffice.org-common,openoffice.org 1.9 openoffice.org-core,openoffice.org 1.9 unoconv,openoffice.org ttf-opensymbol,openoffice.org 1.1.1+1.1.2rc3 openoffice.org-writer,openoffice.org 1.9 openoffice.org-voikko,openoffice.org 1:3.0.1~ openoffice.org-thesaurus-sk,openoffice.org 1.9 openoffice.org-thesaurus-ru,openoffice.org 1.9 openoffice.org-thesaurus-pl,openoffice.org 1.9 openoffice.org-thesaurus-ne,openoffice.org 1.9 openoffice.org-thesaurus-it,openoffice.org 1.9 openoffice.org-thesaurus-hu,openoffice.org 1.9 openoffice.org-thesaurus-en-us,openoffice.org 1.9 openoffice.org-thesaurus-en-au,openoffice.org 1.9 openoffice.org-thesaurus-de-ch,openoffice.org 1.9 openoffice.org-thesaurus-de,openoffice.org 1.9 openoffice.org-thesaurus-cs,openoffice.org 1.9 openoffice.org-qa-ui-tests,openoffice.org 1:2.4.0~ooh680 openoffice.org-qa-tools,openoffice.org 1:3.0.1 openoffice.org-math,openoffice.org 1.9 openoffice.org-l10n-za,openoffice.org openoffice.org-l10n-in,openoffice.org openoffice.org-impress,openoffice.org 1.9 openoffice.org-hyphenation-zu,openoffice.org 1.0.3 openoffice.org-hyphenation-sl,openoffice.org 1.0.3 openoffice.org-hyphenation-pl,openoffice.org 1.0.3 openoffice.org-hyphenation-lt,openoffice.org 1.1.4 openoffice.org-hyphenation-it,openoffice.org 1.0.3 openoffice.org-hyphenation-hu,openoffice.org 1.0.3 openoffice.org-hyphenation-hr,openoffice.org 1.0.3-2 openoffice.org-hyphenation-hr,openoffice.org 1.0.3-3 openoffice.org-hyphenation-en-us,openoffice.org 1.0.3 openoffice.org-hyphenation-de,openoffice.org 1.0.3 openoffice.org-hyphenation-af,openoffice.org 1.0.3 openoffice.org-draw,openoffice.org 1.9 openoffice.org-core,openoffice.org 1.9 openoffice.org-common,openoffice.org 1.9 openoffice.org-calc,openoffice.org 1.9 openclipart-openoffice.org,openoffice.org myspell-uk,openoffice.org myspell-th,openoffice.org 1.9.126 myspell-sw,openoffice.org myspell-sv-se,openoffice.org 1.0.3-2 myspell-sv-se,openoffice.org 1.0.3-3 myspell-sl,openoffice.org 1.0.3-2 myspell-sk,openoffice.org 1.0.3-2 myspell-sk,openoffice.org 1.0.3-3 myspell-ru,openoffice.org myspell-pt-pt,openoffice.org 1.0.3-2 myspell-pt-pt,openoffice.org 1.0.3-3 myspell-pt-br,openoffice.org 1.0.3-2 myspell-pt-br,openoffice.org 1.0.3-3 myspell-pl,openoffice.org 1.0.3-3 myspell-pl,openoffice.org 1.0.3-3 myspell-lv,openoffice.org 1.0.3-2 myspell-lv,openoffice.org myspell-lt,openoffice.org 1.0.3-2 myspell-ku,openoffice.org myspell-it,openoffice.org 1.0.3-2 myspell-hy,openoffice.org myspell-hu,openoffice.org 1.0.3-2 myspell-hu,openoffice.org myspell-hr,openoffice.org 1.0.3-2 myspell-gv,openoffice.org 1.0.3-2 myspell-gd,openoffice.org 1.0.3-2 myspell-ga,openoffice.org 1.0.3-2 myspell-ga,openoffice.org 1.0.3-3 myspell-fr-gut,openoffice.org 1.0.3-2 myspell-fr,openoffice.org 1.0.3-2 myspell-fo,openoffice.org 1.0.3-2 myspell-fo,openoffice.org 1.0.3-3 myspell-fi,openoffice.org myspell-et,openoffice.org myspell-es,openoffice.org 1.0.3-2 myspell-es,openoffice.org 1.0.3-3 myspell-eo,openoffice.org 1.0.3-2 myspell-eo,openoffice.org 1.0.3-3 myspell-en-za,openoffice.org 1.0.3-2 myspell-en-us,openoffice.org 1.0.3-2 myspell-en-gb,openoffice.org 1.0.3-2 myspell-en-au,openoffice.org 1.0.3-2 myspell-el-gr,openoffice.org 1.0.3-2 myspell-el-gr,openoffice.org 1.0.3-3 myspell-de-de-oldspell,openoffice.org 1.0.3-2 myspell-de-de-oldspell,openoffice.org myspell-de-de,openoffice.org 1.0.3-2 myspell-de-de,openoffice.org myspell-de-ch,openoffice.org 1.0.3-2 myspell-de-ch,openoffice.org myspell-de-at,openoffice.org 1.0.3-2 myspell-de-at,openoffice.org myspell-da,openoffice.org 1.0.3-2 myspell-da,openoffice.org 1.0.3-3 myspell-cs-cz,openoffice.org 1.0.3-2 myspell-ca,openoffice.org 1.0.3-2 myspell-ca,openoffice.org 1.0.3-3 myspell-bg,openoffice.org 1.0.3-2 myspell-bg,openoffice.org myspell-af,openoffice.org 1.0.3-2 kdissert,openoffice.org kdissert,openoffice.org hunspell-vi,openoffice.org 1.0.3-2 hunspell-ne,openoffice.org 1.0.3-2 hunspell-hu,openoffice.org 1.0.3-2 hunspell-gl-es,openoffice.org 1.0.3-2
Re: OpenOffice.org broken in AMD64 Sid?
Rene Engelhard wrote: Sandro Tosi wrote: What about reporting a bug? execute Please not. The BTS is not a support forum, it is for actual bugs. providing the actual problem you're facing (it doesn't open document is a little too generic) and all other information you can gather Well, if I interpret apt-cache showpkg right he doesn't seem to have -writer installed, so *of course* he cannot open word docs. - *user error.* Grüße/Regards, René Perhaps it *is *user error, but I took no explicit action to remove any modules, and the Open Office did work previously. It was my understanding that apt-get upgrade never removes packages, so I thought perhaps there was a disconnect in the package structure of openoffice for Sid. Is there a metapackage that will reinstall all basic functionality of the openoffice suite (writer, spreadsheet, presentation) or must I now research the missing components and manually install? I was under the (mis)understanding that running apt-get install install openoffice.org would do this, but it does not (for me). It appears that running sudo apt-get install openoffice.org-writer will install this missing module, plus several others (output attached) and I will do this momentarily. But I don't understand why the modules went AWOL in the first place. Maybe it's just one of the joys an unsophisticated Debian user should expect when running the unstable distribution. I rarely have problems like this. Thanks for the responses! Script started on Thu 05 Mar 2009 12:39:26 PM CST Reading package lists... 0% Reading package lists... 100% Reading package lists... Done Building dependency tree... 0% Building dependency tree... 0% Building dependency tree... 50% Building dependency tree... 50% Building dependency tree Reading state information... 0% Reading state information... 0% Reading state information... Done The following packages were automatically installed and are no longer required: gs-esp Use 'apt-get autoremove' to remove them. The following extra packages will be installed: gcj-4.3-base libbackport-util-concurrent-java libcommons-codec-java libdom4j-java libgcj-bc libgcj-common libgcj9-0 libgcj9-jar libhyphen0 libicu38 libjaxen-java libjaxme-java libjaxp1.3-java libjaxp1.3-java-gcj libjdom1-java libneon27 libraptor1 librasqal1 librdf0 libsaxonb-java libxerces2-java libxerces2-java-gcj libxom-java libxpp2-java libxpp3-java openoffice.org-base-core openoffice.org-common openoffice.org-core openoffice.org-emailmerge openoffice.org-filter-binfilter openoffice.org-java-common openoffice.org-math openoffice.org-style-andromeda openoffice.org-style-galaxy openoffice.org-writer2latex python-uno raptor-utils redland-utils uno-libs3 ure Suggested packages: libdom4j-java-doc libgcj9-dbg libgcj9-0-awt libsaxonb-java-doc libxerces2-java-doc libxom-java-doc openoffice.org-base openoffice.org-style-industrial openoffice.org-style-hicontrast bsh openoffice.org-gcj cli-uno-bridge Recommended packages: openoffice.org-style-tango openoffice.org-style-crystal The following NEW packages will be installed: gcj-4.3-base libbackport-util-concurrent-java libcommons-codec-java libdom4j-java libgcj-bc libgcj-common libgcj9-0 libgcj9-jar libhyphen0 libicu38 libjaxen-java libjaxme-java libjaxp1.3-java libjaxp1.3-java-gcj libjdom1-java libneon27 libraptor1 librasqal1 librdf0 libsaxonb-java libxerces2-java libxerces2-java-gcj libxom-java libxpp2-java libxpp3-java openoffice.org-base-core openoffice.org-core openoffice.org-emailmerge openoffice.org-filter-binfilter openoffice.org-java-common openoffice.org-math openoffice.org-style-galaxy openoffice.org-writer openoffice.org-writer2latex python-uno raptor-utils redland-utils uno-libs3 ure The following packages will be upgraded: openoffice.org-common openoffice.org-style-andromeda 2 upgraded, 39 newly installed, 0 to remove and 46 not upgraded. Need to get 140MB of archives. After this operation, 351MB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. Script done on Thu 05 Mar 2009 12:39:31 PM CST
Re: OpenOffice.org broken in AMD64 Sid?
Russ Cook wrote: Rene Engelhard wrote: Sandro Tosi wrote: What about reporting a bug? execute Please not. The BTS is not a support forum, it is for actual bugs. providing the actual problem you're facing (it doesn't open document is a little too generic) and all other information you can gather Well, if I interpret apt-cache showpkg right he doesn't seem to have -writer installed, so *of course* he cannot open word docs. - *user error.* Grüße/Regards, René Perhaps it *is *user error, but I took no explicit action to remove any modules, and the Open Office did work previously. It was my understanding that apt-get upgrade never removes packages, so I thought perhaps there was a disconnect in the package structure of openoffice for Sid. Is there a metapackage that will reinstall all basic functionality of the openoffice suite (writer, spreadsheet, presentation) or must I now research the missing components and manually install? I was under the (mis)understanding that running apt-get install install openoffice.org would do this, but it does not (for me). It appears that running sudo apt-get install openoffice.org-writer will install this missing module, plus several others (output attached) and I will do this momentarily. But I don't understand why the modules went AWOL in the first place. Maybe it's just one of the joys an unsophisticated Debian user should expect when running the unstable distribution. I rarely have problems like this. Thanks for the responses! Running sudo apt-get install --reinstall openoffice.org appears to be fixing the problem. Thanks for all replies. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Nvidia video driver problem
Hans-J. Ullrich wrote: Am Donnerstag, 11. September 2008 schrieb Russ Cook: I'm running an amd64, with 64bit linux (Sid), with evga 8800gts graphics card. I did apt-get update upgrade today. Then I downloaded latest linux source 2.6.26.5 from kernel.org, and downloaded the latest nvidia-kernel-source using apt-get. I compiled a custom kernel and latest nvidia-kernel-source according to procedures outlined at http://wiki.debian.org/NvidiaGraphicsDrivers . I've done this before successfully, and was running Nvidia driver before this action. The problem is that X will not start now with the Nvidia driver. It WILL start with the nv open source driver. Looking in /usr/lib/xorg/modules, I have a symlink libwfb.so pointing to libnvidia-wfb.so.100.14.11, which doesn't exist in this directory, and X complains about it in the Xorg.log file, attached. It also complains about module type1. Can anyone offer help or suggestions? Hi ! First of all, make sure, you compile the correct kernel-module (I suppose you did). After installation of this, install the package nvidia-glx. Hope you did, too. In /etc/X11/xorg.conf change the entry nv to nvidia. Now it should start. If it still does not, move your script of login manager (kdm, gdm, xdm whatever you use) out of the way, so it will not be started at boot. (Hint: For kdm i.e. just move the files /etc/init.d/kdm somewhere else. So you can restore it back later) Now reboot your machine. You get the login prompt. Login as root and start X using the command startx. If it fails examine, what happens. If it is starting as root, your user is not in the group nvidia. Good luck ! Hans Hans, Thanks for the reply. I believe I compiled the correct things. I don't use gdm or kdm, so always start manually with startx. Logging in as root and running 'startx' gives same result. Problem appears to be missing object of simlink? I am not a member of group nvidia (was not aware of such a group). I AM a member of group video. Since I CAN start x with nv driver, I believe my X setup is otherwise OK. I'll poke around some more ... Thanks again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Nvidia video driver problem
Hans-J. Ullrich wrote: Am Donnerstag, 11. September 2008 schrieb Russ Cook: Hans-J. Ullrich wrote: Am Donnerstag, 11. September 2008 schrieb Russ Cook: I'm running an amd64, with 64bit linux (Sid), with evga 8800gts graphics card. I did apt-get update upgrade today. Then I downloaded latest linux source 2.6.26.5 from kernel.org, and downloaded the latest nvidia-kernel-source using apt-get. I compiled a custom kernel and latest nvidia-kernel-source according to procedures outlined at http://wiki.debian.org/NvidiaGraphicsDrivers . I've done this before successfully, and was running Nvidia driver before this action. The problem is that X will not start now with the Nvidia driver. It WILL start with the nv open source driver. Looking in /usr/lib/xorg/modules, I have a symlink libwfb.so pointing to libnvidia-wfb.so.100.14.11, which doesn't exist in this directory, and X complains about it in the Xorg.log file, attached. It also complains about module type1. Can anyone offer help or suggestions? Hi ! First of all, make sure, you compile the correct kernel-module (I suppose you did). After installation of this, install the package nvidia-glx. Hope you did, too. In /etc/X11/xorg.conf change the entry nv to nvidia. Now it should start. If it still does not, move your script of login manager (kdm, gdm, xdm whatever you use) out of the way, so it will not be started at boot. (Hint: For kdm i.e. just move the files /etc/init.d/kdm somewhere else. So you can restore it back later) Now reboot your machine. You get the login prompt. Login as root and start X using the command startx. If it fails examine, what happens. If it is starting as root, your user is not in the group nvidia. Good luck ! Hans Hans, Thanks for the reply. I believe I compiled the correct things. I don't use gdm or kdm, so always start manually with startx. Logging in as root and running 'startx' gives same result. Problem appears to be missing object of simlink? I am not a member of group nvidia (was not aware of such a group). I AM a member of group video. Since I CAN start x with nv driver, I believe my X setup is otherwise OK. I'll poke around some more ... Thanks again. Try to uncomment the line LOAD glx in /etc/xorg.conf. It should work without 3d-acceleration, but it should start. Does this work ??? Regards Hans Didn't help. Attached is the Xorg.0.log . Xorg.0.log.old Description: application/trash
Solved - Nvidia video driver problem
Solved. Xorg was outdated. Updated with dselect, and the nvidia driver works now. Thanks to Lennart Sorensen for pointing me in the right direction! Original Message Subject:Nvidia video driver problem Resent-Date:Thu, 11 Sep 2008 16:17:41 + (UTC) Resent-From:[EMAIL PROTECTED] Date: Thu, 11 Sep 2008 11:16:00 -0500 From: Russ Cook [EMAIL PROTECTED] To: debian amd64 debian-amd64@lists.debian.org, [EMAIL PROTECTED] I'm running an amd64, with 64bit linux (Sid), with evga 8800gts graphics card. I did apt-get update upgrade today. Then I downloaded latest linux source 2.6.26.5 from kernel.org, and downloaded the latest nvidia-kernel-source using apt-get. I compiled a custom kernel and latest nvidia-kernel-source according to procedures outlined at http://wiki.debian.org/NvidiaGraphicsDrivers . I've done this before successfully, and was running Nvidia driver before this action. The problem is that X will not start now with the Nvidia driver. It WILL start with the nv open source driver. Looking in /usr/lib/xorg/modules, I have a symlink libwfb.so pointing to libnvidia-wfb.so.100.14.11, which doesn't exist in this directory, and X complains about it in the Xorg.log file, attached. It also complains about module type1. Can anyone offer help or suggestions? Xorg.0.log.old Description: application/trash
photobucket problem
I am running 64bit Debian unstable. Until a recent upgrade, I was able to upload photos to www.photobucket.com using any of the browsers on my machine (debault is iceweasel). Now, I can access the web page, but it doesn't see my files when I try to select photos to upload. I suspect the problem is related to Java, but don't know that. Has anyone else experienced this problem, and is there a solution? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: linux-image-2.6.18-6-amd64 kernel installed, but am I running a 64-bit system?
Michael Fothergill wrote: Sorry about this. I had forgotten that sometimes people put the 32 bit OS on the 64 bit machines. To me it seems like putting a diesel engine in a formula one car but there it is. _ Discover and Win with Live Search http://clk.atdmt.com/UKM/go/msnnkmgl001007ukm/direct/01/ Whoa now, don't go bashing my diesels! :) 350 HP, 650 lb-ft torque, 15 mpg in a 7000 lb truck! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel upgrade problem
I'm running a dual core amd64 with Debian unstable, kernel 2.6.17-2-amd64. Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected error message concerning a buffer-write failure. I have attached a script file with the error message. I searched the mailing list, and didn't see a related post. I apologize in advance if I missed it. Can anyone shed some light? Thanks, Russ Script started on Sun 31 Dec 2006 12:59:28 PM CST (Reading database ... 121478 files and directories currently installed.) Unpacking linux-image-2.6.18-3-amd64 (from .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... Done. dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb (--install): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.17-2-amd64 Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp Updating /boot/grub/menu.lst ... done Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb Script done on Sun 31 Dec 2006 12:59:38 PM CST
Re: kernel upgrade problem
Manolo Díaz wrote: Russ Cook escribió: I'm running a dual core amd64 with Debian unstable, kernel 2.6.17-2-amd64. Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected error message concerning a buffer-write failure. I have attached a script file with the error message. I searched the mailing list, and didn't see a related post. I apologize in advance if I missed it. Can anyone shed some light? Thanks, Russ Script started on Sun 31 Dec 2006 12:59:28 PM CST (Reading database ... 121478 files and directories currently installed.) Unpacking linux-image-2.6.18-3-amd64 (from .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... Done. dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb (--install): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device That's your clue: No space left on device. What does df command say? dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.17-2-amd64 Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp Updating /boot/grub/menu.lst ... done Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb Script done on Sun 31 Dec 2006 12:59:38 PM CST I had already checked with 'df' before posting, but I attach the results in case it offers a clue. Thanks for the reply, Russ Script started on Sun 31 Dec 2006 06:38:39 PM CST Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 255912200418 41841 83% / tmpfs 1674944 0 1674944 0% /lib/init/rw udev 1024064 10176 1% /dev tmpfs 1674944 0 1674944 0% /dev/shm /dev/hda9181745360 90136804 82376404 53% /home /dev/hda8 369000 8355340985 3% /tmp /dev/hda5 4807056 2657124 1905748 59% /usr /dev/hda6 2885780 1257440 1481752 46% /var Script done on Sun 31 Dec 2006 06:38:39 PM CST
Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program,not the pilot))
Hans-J. Ullrich wrote: Am Montag, 9. Oktober 2006 03:38 schrieben Sie: Hans-J. Ullrich wrote: Am Samstag, 7. Oktober 2006 03:38 schrieben Sie: Hans-J. Ullrich wrote: Hi Russ, sry, my late answer, I did somehow miss your mail. Well, if nv crashes and nvidia without Load GLX-Option, then there might be another non nvidia dependent problem. What does it show, if you disable kdm and start manually X with the command startx from the shell ? Is there a difference between root and normal user ? If starting with startx from the shell, you can see, what really happens. In doubt, just send me the output and your /var/log/xorg.log. You can additionally start startx with the strace command. Just do strace startx on the shell. Caution: This is a huge output. Just pipe it into a file, so you can examine it later. Good luck and regards ! Hans Hans, Per your suggestion, I ran strace startx, and piped the output to startx.log (attached). Also attached is /var/log/Xorg.0.log . I was running the nvidia driver for this test (config file also attached). After starting the Xserver, I tried to open my Home folder. The frame came up, but the files never appeared. SSH from another machine, and running top showed Xorg running 100% on one processor (I have a dual core machine). Any further advice or suggestions are most welcome. I am currently running with the Vesa driver, as it is stable (if slow). Thanks, Russ Hi Russ, I looked at your attachements and I could see some things, you should change: In xorg.conf there are the wrong paths for the fonts. Those have changed since xorg is used ! Here are my entries: Section Files FontPathunix/:7100 # local font server # if the local font server has problems, we can fall back on these FontPath/usr/share/fonts/X11/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/share/fonts/X11/CID FontPath/usr/share/fonts/X11/100dpi FontPath/usr/share/fonts/X11/75dpi EndSection Second thing: In xorg.conf cooment the section DRI out: # Section DRI # Group video # Mode0666 # EndSection They are not used for Nvidia-cards. I will send you my xorg.conf from my Nvidia-computer later (this message is written on my ATI-Notebook :=)), so this one will not work as it is for ATI. If everything fails, so you should create a very new xorg.conf. But just don't do it with dpkg-reconfigure, do it using xorgconfig as root on a shell. Answer the questions. Then save it as xorg.conf as suggested. At last change the entry for the video driver from nv to nvidia and activate the Load GLX option. Do not forget to backup your old xorg.conf, so, if it works with the new one, you can test why the old did not work. Good luck ! Hans Hans, Thanks for the continued help. I tried the changes you suggested here, Its a pleasure for me. but no help. I do not seem to have the command 'xorgconfig'. A search of packages on the Debian web site does not give a response either. O.k., might be, this is no more in the pacgages, as I could not find it any more. On my system it is no more, too. Sorry ! Where can I find this program? I am at latest version of xbase-clients, but no such command is available to me. Maybe some maintainer could answer this. I am wondering myself, now. Thanks, Russ Did you test my xorg.conf I sent to you ? Regards Hans I did test your config file you sent me. That is, I entered the appropriate areas that were different from mine. The result is the same. I was hoping that running strace and providing the output would enable someone to identify where the system was hanging. I certainly don't understand it. Thanks for your willingness to help! I suppose I could just buy a more recent Nvidia-supported video card and hope for the best, but I was hoping to resolve the issues with my old card first. Thanks again, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))
Hans wrote: Am Dienstag, 19. September 2006 02:28 schrieb Russ Cook: Russ Cook wrote: Hans-J. Ullrich wrote: Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook: Flightgear crashes on startup on my system. I'm running 2.6.16-2-amd64-k8-smp generic kernel. My system: An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303. I'm running Debian unstable, with latest version of Flightgear and all required packages. I'm NOT running nvidia drivers because they cause my system to hang. I'm also running the VESA driver, for the same reason. I've attached the error message that Flightgear generates on startup. Is this error indicative of the video driver I'm using? Thanks for any help. Regards, Russ Hi Russ, as far as I know flightgear needs rendering software, just opengl. At start it looks in its configfile, and tries to set the settings and initialising the scenery. IMO you MUST have an opengl-driver working ! Otherwise it will crash. Why does the nvidia-driver not work ? It should, if you use the Debian packages and compile the nvidia-kernel-module on your own, and, additionally install the package nvidia-glx. Good luck ! Hans Hans, Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages, compiled nvidia-kernel-module, and installed nvidia-glx. I made the appropriate changes to xorg.conf (attached), added nvidia to /etc/modules, and restarted my xserver. As soon as I log in to gdm, the system locks up. I have to use ssh from another linux box to restart kill gdm. If I try to log in as an invalid user, it checks password, rejects the login, and gives a new login prompt without locking up. As soon as I successfully login, the system locks up. I have reverted back to the vesa driver (again). If anyone can help me troubleshoot this problem, I'll be happy to reload the nvidia driver and run whatever tests you can walk me through. I'd really like to be able to use the nvidia driver, for the performance boost it's supposed to provide. It also seems necessary in order to run Flightgear. Thanks for any help. Russ # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # dri module disabled for proprietary Nvidia driver # Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRulesxorg Option XkbModelpc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device /dev/input/mice Option ProtocolExplorerPS/2 Option Emulate3Buttons true EndSection Section Device Identifier NVIDIA Corporation NV17 [GeForce4 MX 420] # Driver vesa disabled Driver vesa # Driver Nvidia enabled Driver
Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))
Hans-J. Ullrich wrote: Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook: Flightgear crashes on startup on my system. I'm running 2.6.16-2-amd64-k8-smp generic kernel. My system: An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303. I'm running Debian unstable, with latest version of Flightgear and all required packages. I'm NOT running nvidia drivers because they cause my system to hang. I'm also running the VESA driver, for the same reason. I've attached the error message that Flightgear generates on startup. Is this error indicative of the video driver I'm using? Thanks for any help. Regards, Russ Hi Russ, as far as I know flightgear needs rendering software, just opengl. At start it looks in its configfile, and tries to set the settings and initialising the scenery. IMO you MUST have an opengl-driver working ! Otherwise it will crash. Why does the nvidia-driver not work ? It should, if you use the Debian packages and compile the nvidia-kernel-module on your own, and, additionally install the package nvidia-glx. Good luck ! Hans Hans, Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages, compiled nvidia-kernel-module, and installed nvidia-glx. I made the appropriate changes to xorg.conf (attached), added nvidia to /etc/modules, and restarted my xserver. As soon as I log in to gdm, the system locks up. I have to use ssh from another linux box to restart kill gdm. If I try to log in as an invalid user, it checks password, rejects the login, and gives a new login prompt without locking up. As soon as I successfully login, the system locks up. I have reverted back to the vesa driver (again). If anyone can help me troubleshoot this problem, I'll be happy to reload the nvidia driver and run whatever tests you can walk me through. I'd really like to be able to use the nvidia driver, for the performance boost it's supposed to provide. It also seems necessary in order to run Flightgear. Thanks for any help. Russ # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # dri module disabled for proprietary Nvidia driver # Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ExplorerPS/2 Option Emulate3Buttons true EndSection Section Device Identifier NVIDIA Corporation NV17 [GeForce4 MX 420] # Driver vesa disabled Driver vesa # Driver Nvidia enabled Driver nvidia BusID PCI:4:7:0 EndSection Section Monitor Identifier S/T 77E/76E Option DPMS EndSection Section Screen
Re: Nvidia driver lock-up (was (Re: Flightgear crashes (the program, not the pilot))
Russ Cook wrote: Hans-J. Ullrich wrote: Am Sonntag, 17. September 2006 19:27 schrieb Russ Cook: Flightgear crashes on startup on my system. I'm running 2.6.16-2-amd64-k8-smp generic kernel. My system: An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303. I'm running Debian unstable, with latest version of Flightgear and all required packages. I'm NOT running nvidia drivers because they cause my system to hang. I'm also running the VESA driver, for the same reason. I've attached the error message that Flightgear generates on startup. Is this error indicative of the video driver I'm using? Thanks for any help. Regards, Russ Hi Russ, as far as I know flightgear needs rendering software, just opengl. At start it looks in its configfile, and tries to set the settings and initialising the scenery. IMO you MUST have an opengl-driver working ! Otherwise it will crash. Why does the nvidia-driver not work ? It should, if you use the Debian packages and compile the nvidia-kernel-module on your own, and, additionally install the package nvidia-glx. Good luck ! Hans Hans, Today I upgraded to 2.6.17-2-amd64, used the debian Nvidia packages, compiled nvidia-kernel-module, and installed nvidia-glx. I made the appropriate changes to xorg.conf (attached), added nvidia to /etc/modules, and restarted my xserver. As soon as I log in to gdm, the system locks up. I have to use ssh from another linux box to restart kill gdm. If I try to log in as an invalid user, it checks password, rejects the login, and gives a new login prompt without locking up. As soon as I successfully login, the system locks up. I have reverted back to the vesa driver (again). If anyone can help me troubleshoot this problem, I'll be happy to reload the nvidia driver and run whatever tests you can walk me through. I'd really like to be able to use the nvidia driver, for the performance boost it's supposed to provide. It also seems necessary in order to run Flightgear. Thanks for any help. Russ # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # dri module disabled for proprietary Nvidia driver # Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRulesxorg Option XkbModelpc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device /dev/input/mice Option ProtocolExplorerPS/2 Option Emulate3Buttons true EndSection Section Device Identifier NVIDIA Corporation NV17 [GeForce4 MX 420] # Driver vesa disabled Driver vesa # Driver Nvidia enabled Driver nvidia BusID PCI:4:7:0 EndSection Section Monitor Identifier S/T 77E/76E
Flightgear crashes (the program, not the pilot)
Flightgear crashes on startup on my system. I'm running 2.6.16-2-amd64-k8-smp generic kernel. My system: An Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303. I'm running Debian unstable, with latest version of Flightgear and all required packages. I'm NOT running nvidia drivers because they cause my system to hang. I'm also running the VESA driver, for the same reason. I've attached the error message that Flightgear generates on startup. Is this error indicative of the video driver I'm using? Thanks for any help. Regards, Russ Error reading properties: Failed to open file at /home/russ/.fgfs/autosave.xml (reported by SimGear XML Parser) freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance. fgfs: indirect_vertex_array.c:1359: __indirect_glTexCoordPointer: Assertion `a != ((void *)0)' failed.
(Soved: for now) Re: Asus motherboard hangs in X
Russ Cook wrote: Matthew Robinson wrote: Try changing the driver in xorg.conf to 'vesa'. This will be much slower than the binary Nvidia drivers, but if it works, youve found your problem. Thanks Matt. I have changed the driver to Vesa, and so far I can't make it crash. I am now upgrading from stable to unstable (amd64) and downloading a current smp kernel. If all stays stable (pun intended), then I'll ask the experts for suggestions regarding graphics boards and drivers. Thanks much, russ If the vesa driver works, the open source 'nv' driver, may also work. Its nvidia specific, but not as good as the official binary nvidia drivers. As far as I know, nv performs much better than vesa, but much worse than nvidia. No, I started the whole process with the open source 'nv' driver. I will try it again after this upgrade completes, but 'nv' is what I was using for several weeks before finally trying 'nvidia' which did not help, either. Thanks again. Russ Well, I am now successfully running amd64 unstable. The nv driver was installed by default, and as before, caused my system to hang from X apps. I have changed the config file to use the vesa driver, and now I can run without crashes. Thanks to those who offered help, especially Matt. Next question, I'd like obtain a quality graphics card with hardware acceleration for use with the flightgear flight simulator (the primary reason for building this system). Can the kind folks on this list provide suggestions of boards that are successfully running on this board? Again, my system is Asus A8N32SLI Deluxe, AMD64 4800+ dual core, 4 GB Corsair TwinX ram (to be reduced to 2 GB due to MB ram limitations). Thanks again, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Asus motherboard hangs in X
I have an Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303, with no impact. I am running kernel 2.6.8-11-amd64-generic. I have also run the smp kernels, with the same problem. When interacting in X, the system will hang unexpectedly. I can ssh to the machine from another box, and the command 'top' will show eithe XFree86 or Xorg (whichever is running) to be using 100 % cpu (when running smp). The machine has never frozen on me when running commands from ssh at another box. Google search has shown many people having similar problems with various motherboards. I have run memtest on all my memory sticks, one at a time, and all together, with no detected faults. I also tried loading the nvidia video driver, but no help. I have tried the Knoppix 5.0.1 and Kubuntu 6.06 live CDs, and get the same problem. Is anyone else running this same motherboard without problems? If you had problems and solved them, can you share your process? Does Nvidia offer drivers for the NForce4 motherboard chipset, and if so, does it make any difference? I plan to upgrade my video board, but I want to get a stable system first, before putting more $ into it. Could the older video board be part of the problem? Any help most gratefully accepted. Thanks, Russ lspci.txt Description: plain/text
Re: Asus motherboard hangs in X
Matthew Robinson wrote: Russ Cook wrote: I have an Asus A8N32-SLI Deluxe motherboard with AMD Athlon 4800 dual core cpu, with 4 MB of Corsair TwinX ram sticks. I have an older GeForce4 MX 420 graphics board with 64 MB ram. I have updated my bios to version 1303, with no impact. I am running kernel 2.6.8-11-amd64-generic. I have also run the smp kernels, with the same problem. When interacting in X, the system will hang unexpectedly. I can ssh to the machine from another box, and the command 'top' will show eithe XFree86 or Xorg (whichever is running) to be using 100 % cpu (when running smp). The machine has never frozen on me when running commands from ssh at another box. Google search has shown many people having similar problems with various motherboards. I have run memtest on all my memory sticks, one at a time, and all together, with no detected faults. I also tried loading the nvidia video driver, but no help. I have tried the Knoppix 5.0.1 and Kubuntu 6.06 live CDs, and get the same problem. Is anyone else running this same motherboard without problems? If you had problems and solved them, can you share your process? Does Nvidia offer drivers for the NForce4 motherboard chipset, and if so, does it make any difference? I plan to upgrade my video board, but I want to get a stable system first, before putting more $ into it. Could the older video board be part of the problem? Any help most gratefully accepted. Thanks, Russ Try changing the driver in xorg.conf to 'vesa'. This will be much slower than the binary Nvidia drivers, but if it works, youve found your problem. Thanks Matt. I have changed the driver to Vesa, and so far I can't make it crash. I am now upgrading from stable to unstable (amd64) and downloading a current smp kernel. If all stays stable (pun intended), then I'll ask the experts for suggestions regarding graphics boards and drivers. Thanks much, russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Asus motherboard hangs in X
Matthew Robinson wrote: Try changing the driver in xorg.conf to 'vesa'. This will be much slower than the binary Nvidia drivers, but if it works, youve found your problem. Thanks Matt. I have changed the driver to Vesa, and so far I can't make it crash. I am now upgrading from stable to unstable (amd64) and downloading a current smp kernel. If all stays stable (pun intended), then I'll ask the experts for suggestions regarding graphics boards and drivers. Thanks much, russ If the vesa driver works, the open source 'nv' driver, may also work. Its nvidia specific, but not as good as the official binary nvidia drivers. As far as I know, nv performs much better than vesa, but much worse than nvidia. No, I started the whole process with the open source 'nv' driver. I will try it again after this upgrade completes, but 'nv' is what I was using for several weeks before finally trying 'nvidia' which did not help, either. Thanks again. Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf locks up my system
Florian Kulzer wrote: On Sun, May 14, 2006 at 17:09:26 -0500, Russ Cook wrote: Florian Kulzer wrote: On Sun, May 14, 2006 at 13:32:31 -0500, Russ Cook wrote: I'm running a A8N32-SLI Deluxe, with dual core amd64. My kernel is 2.6.16-1-amd64-k8-smp. I also run kernel 2.6.14.4. With either kernel, I have no audio. I used to have audio until about a week ago, after running apt-get upgrade. I'm running the 64 bit dist, unstable. When trying to run XMMS or any other audio or video player, I get no audio. XMMS tells me it couldn't open audio, and request I check soundcard configured, correct output plugin selected, and no other program is blocking the soundcard. In the past, I could get past this problem by re-running alsaconf. Now however, alsaconf never completes before my X system freezes up. I can still access my system from another machine using ssh, but all output to the screen is frozen, and the keyboard is unresponsive. The mouse pointer still moves across the screen, but nothing responds. Has anyone else had this problem, and can anyone offer hints or suggestions as to the cause and cure? I would try to shut down X and run alsaconf from a virtual terminal. If this still locks up your machine you can log in with ssh and check which process is blocking the CPU with the top command. It would then also be interesting if killing that process unlocks the computer or not. Another thing to try is /etc/init.d/alsa force-reload. If alsaconf works when run from the terminal you can use a simple application such as speaker-test to check your sound. If this is successful you can try if it still works when you start X again. This should help you to isolate the cause of the problem. Another problem - I used to be able to access a virtual terminal by pressing ctl-alt-f2. This key sequence no longer works. I'm running gnome. How can I temporarily disable X so I can run alsaconf from a virtual terminal? Open a Gnome terminal or an xterm, become root and run chvt 2 to go to virtual terminal 2, for example. Log in as your normal user, su to root level and run /etc/init.d/gdm stop This will shut down Gnome and X. The command to start it again is /etc/init.d/gdm start As far as the ctrl-alt-fx problem is concerned, have a look at this thread: http://lists.debian.org/debian-user/2006/04/msg02492.html If that does not help you, start a new thread and post the keyboard section of your /etc/X11/xorg.conf. Thank you so much for the continued help. You've given me some reading to do (always a good thing). I will check back and let you know if I make any progress. Thanks again! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf locks up my system
Florian Kulzer wrote: On Sun, May 14, 2006 at 17:09:26 -0500, Russ Cook wrote: Florian Kulzer wrote: On Sun, May 14, 2006 at 13:32:31 -0500, Russ Cook wrote: I'm running a A8N32-SLI Deluxe, with dual core amd64. My kernel is 2.6.16-1-amd64-k8-smp. I also run kernel 2.6.14.4. With either kernel, I have no audio. I used to have audio until about a week ago, after running apt-get upgrade. I'm running the 64 bit dist, unstable. When trying to run XMMS or any other audio or video player, I get no audio. XMMS tells me it couldn't open audio, and request I check soundcard configured, correct output plugin selected, and no other program is blocking the soundcard. In the past, I could get past this problem by re-running alsaconf. Now however, alsaconf never completes before my X system freezes up. I can still access my system from another machine using ssh, but all output to the screen is frozen, and the keyboard is unresponsive. The mouse pointer still moves across the screen, but nothing responds. Has anyone else had this problem, and can anyone offer hints or suggestions as to the cause and cure? I would try to shut down X and run alsaconf from a virtual terminal. If this still locks up your machine you can log in with ssh and check which process is blocking the CPU with the top command. It would then also be interesting if killing that process unlocks the computer or not. Another thing to try is /etc/init.d/alsa force-reload. If alsaconf works when run from the terminal you can use a simple application such as speaker-test to check your sound. If this is successful you can try if it still works when you start X again. This should help you to isolate the cause of the problem. Another problem - I used to be able to access a virtual terminal by pressing ctl-alt-f2. This key sequence no longer works. I'm running gnome. How can I temporarily disable X so I can run alsaconf from a virtual terminal? Open a Gnome terminal or an xterm, become root and run chvt 2 to go to virtual terminal 2, for example. Log in as your normal user, su to root level and run /etc/init.d/gdm stop This will shut down Gnome and X. The command to start it again is /etc/init.d/gdm start As far as the ctrl-alt-fx problem is concerned, have a look at this thread: http://lists.debian.org/debian-user/2006/04/msg02492.html If that does not help you, start a new thread and post the keyboard section of your /etc/X11/xorg.conf. After killing gdm, I can run alsaconf and it executes fine. After restarting gdm, xmms again cannot run. I ran alsaconf from an xterm, and the X system locked up again. Now I have to find out which process is hung up, if possible. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
alsaconf locks up my system
I'm running a A8N32-SLI Deluxe, with dual core amd64. My kernel is 2.6.16-1-amd64-k8-smp. I also run kernel 2.6.14.4. With either kernel, I have no audio. I used to have audio until about a week ago, after running apt-get upgrade. I'm running the 64 bit dist, unstable. When trying to run XMMS or any other audio or video player, I get no audio. XMMS tells me it couldn't open audio, and request I check soundcard configured, correct output plugin selected, and no other program is blocking the soundcard. In the past, I could get past this problem by re-running alsaconf. Now however, alsaconf never completes before my X system freezes up. I can still access my system from another machine using ssh, but all output to the screen is frozen, and the keyboard is unresponsive. The mouse pointer still moves across the screen, but nothing responds. Has anyone else had this problem, and can anyone offer hints or suggestions as to the cause and cure? Thanks much, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rxvt won't start
Russ Cook wrote: Gnu-Raiz wrote: On Friday 28 April 2006 15:48, Russ Cook wrote: Aaron M. Ucko wrote: Russ Cook [EMAIL PROTECTED] writes: I'm running gnome. From a xterminal, I try to start rxvt, and get this message: rxvt: can't load color Black rxvt: can't load color Black rxvt: aborting Has anyone seen this problem, and can you tell me what I should check? You may have managed to hit http://bugs.debian.org/343389 . Try reinstalling the x11-common package with dpkg --force-confmiss: dpkg -i --force-confmiss /var/cache/apt/archives/x11-common_*.deb Aaron, Thank you for the reply. I did as you suggested, but the error remains the same. Thanks though! Is their any special reason your using rxvt? You can make the changes to x-term to make it look exactly like rxvt! Example code: xterm -sb -sl 200 -leftbar -fg black -bg white I do agree that if rxvt does not work right maybe you should file a bug report. If I remember correctly rxvt is a subset to xterm, and might not have implemented everything yet. Gnu_Raiz Gnu_Raiz, Thank you for your reply. Below is what the system tells me when I executed the command string you suggested, from within a Konsole window. It appears I have a configuration problem of some sort. [EMAIL PROTECTED]:~$ xterm -sb -sl 200 -leftbar -fg black -bg white [1] 7723 [EMAIL PROTECTED]:~$ Warning: Color name white is not defined Warning: Cannot convert string nil2 to type FontStruct Warning: Unable to load any usable ISO8859 font Warning: Unable to load any usable ISO8859 font Warning: Color name black is not defined xterm: Cannot allocate color green xterm: Cannot allocate color red [1]+ Donexterm -sb -sl 200 -leftbar -fg black -bg white After a recent 'apt-get upgrade' with no change to my sources.list file, rxvt now works. I have no idea what has changed, but I'm now a 'happy camper'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rxvt won't start
Gnu-Raiz wrote: On Friday 28 April 2006 15:48, Russ Cook wrote: Aaron M. Ucko wrote: Russ Cook [EMAIL PROTECTED] writes: I'm running gnome. From a xterminal, I try to start rxvt, and get this message: rxvt: can't load color Black rxvt: can't load color Black rxvt: aborting Has anyone seen this problem, and can you tell me what I should check? You may have managed to hit http://bugs.debian.org/343389 . Try reinstalling the x11-common package with dpkg --force-confmiss: dpkg -i --force-confmiss /var/cache/apt/archives/x11-common_*.deb Aaron, Thank you for the reply. I did as you suggested, but the error remains the same. Thanks though! Is their any special reason your using rxvt? You can make the changes to x-term to make it look exactly like rxvt! Example code: xterm -sb -sl 200 -leftbar -fg black -bg white I do agree that if rxvt does not work right maybe you should file a bug report. If I remember correctly rxvt is a subset to xterm, and might not have implemented everything yet. Gnu_Raiz Gnu_Raiz, Thank you for your reply. Below is what the system tells me when I executed the command string you suggested, from within a Konsole window. It appears I have a configuration problem of some sort. [EMAIL PROTECTED]:~$ xterm -sb -sl 200 -leftbar -fg black -bg white [1] 7723 [EMAIL PROTECTED]:~$ Warning: Color name white is not defined Warning: Cannot convert string nil2 to type FontStruct Warning: Unable to load any usable ISO8859 font Warning: Unable to load any usable ISO8859 font Warning: Color name black is not defined xterm: Cannot allocate color green xterm: Cannot allocate color red [1]+ Donexterm -sb -sl 200 -leftbar -fg black -bg white -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
rxvt won't start
I'm running gnome. From a xterminal, I try to start rxvt, and get this message: rxvt: can't load color Black rxvt: can't load color Black rxvt: aborting Has anyone seen this problem, and can you tell me what I should check? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rxvt won't start
Aaron M. Ucko wrote: Russ Cook [EMAIL PROTECTED] writes: I'm running gnome. From a xterminal, I try to start rxvt, and get this message: rxvt: can't load color Black rxvt: can't load color Black rxvt: aborting Has anyone seen this problem, and can you tell me what I should check? You may have managed to hit http://bugs.debian.org/343389 . Try reinstalling the x11-common package with dpkg --force-confmiss: dpkg -i --force-confmiss /var/cache/apt/archives/x11-common_*.deb Aaron, Thank you for the reply. I did as you suggested, but the error remains the same. Thanks though! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sources.list problem
In light of the recent announcement The Future of AMD64 Port on this list, I have attempted to update my sources.list file for Apt. I have attached the file for reference. I have tried various combinations of the mirrors in the file in an attempt to eliminate error messages returned by the command apt-get update. A script file of that command's output is attached, also. At this point, the apt database files on my machine appear to be corrupted. Is there a way to rebuild the database files and get clean run from apt-get update? A sample sources.list file would be greatly appreciated. I am running an AMD64 machine, originally installed in pure 64 bit configuration. Any help greatly accepted, and I'd be glad to provide more info, if someone would tell me what is needed to better describe the problem. My problems began as I tried unsuccessfully to get an update of gnumeric - it is now broken between 1.6.3-1, 1.6.2-3, and 1.6.3-1+b1. Help here would be greatly appreciated, also. Thanks much to the list. #deb file:///cdrom/ stable main deb ftp://ftp.nerim.net/debian-marillat/ sid main deb ftp://ftp.nerim.net/debian-marillat/ sarge main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ sid main contrib non-free deb http://mirror.espri.arizona.edu/debian-amd64/debian/ sarge main contrib non-free deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ sid main contrib non-free #deb ftp://ftp.us.debian.org/debian/ unstable main contrib non-free #deb ftp://ftp.us.debian.org/debian/ stable main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free Script started on Fri 21 Apr 2006 06:23:41 PM CDT 0% [Working] Get: 1 http://mirror.espri.arizona.edu sid Release.gpg [189B] 97% [Logging in] [1 Release.gpg 189/189B 100%] [Waiting for headers] Get: 2 http://mirror.espri.arizona.edu sarge Release.gpg [189B] 98% [Logging in] [2 Release.gpg 189/189B 100%] [Waiting for headers] 98% [Logging in] [Waiting for headers] Get: 3 http://security.debian.org stable/updates Release.gpg [189B] 99% [Logging in] [Waiting for headers] [3 Release.gpg 189/189B 100%] 99% [Logging in] [Waiting for headers] Hit http://mirror.espri.arizona.edu sid Release 99% [Logging in] [Waiting for headers] 99% [Release gpgv 5902] [Logging in] [Waiting for headers] [Waiting for headers 99% [Logging in] [Waiting for headers] [Waiting for headers] Hit http://security.debian.org stable/updates Release 99% [Logging in] [Waiting for headers] 99% [Release gpgv 19992] [Logging in] [Waiting for headers] 99% [Logging in] [Waiting for headers] Hit http://mirror.espri.arizona.edu sarge Release 99% [Logging in] [Waiting for headers] 99% [Release gpgv 4812] [Logging in] [Waiting for headers] 99% [Logging in] [Waiting for headers] [Waiting for headers] Ign http://security.debian.org stable/updates/main Packages 99% [Logging in] [Waiting for headers] Hit http://mirror.espri.arizona.edu sid/main Packages Hit http://mirror.espri.arizona.edu sid/contrib Packages Hit http://mirror.espri.arizona.edu sid/non-free Packages Hit http://mirror.espri.arizona.edu sid/main Sources Hit http://mirror.espri.arizona.edu sid/contrib Sources Hit http://mirror.espri.arizona.edu sid/non-free Sources 99% [Logging in] [Waiting for headers] Ign http://security.debian.org stable/updates/contrib Packages 99% [Logging in] [Waiting for headers] Ign http://security.debian.org stable/updates/non-free Packages 99% [Logging in] [Waiting for headers] Hit http://mirror.espri.arizona.edu sarge/main Packages Hit http://mirror.espri.arizona.edu sarge/contrib Packages
Update killed X11 and damaged Locales
I updated my pure 64 bit system (AMD64) yesterday, running combination of Sid and Sarge. Afterwards, X11 will no longer start up. The startx file is missing, as is /etc/X11/Xsession file. Perl is also complaining about certain Locale variable not being settable, due to missing files (or something like that). I have not changed my sources.list file in several months. I'd rather not do a complete reinstall, if this can be recovered. How can I restore my X11 system (Xorg)? What must I do to repair Locales? Thanks in advance for any help or suggestions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Update killed X11 and damaged Locales
Adam C. Emerson wrote: On Sat, Mar 04, 2006 at 05:41:37PM -0600, Russ Cook wrote: I updated my pure 64 bit system (AMD64) yesterday, running combination of Sid and Sarge. Afterwards, X11 will no longer start up. The startx file is missing, as is /etc/X11/Xsession file. Perl is also complaining about certain Locale variable not being settable, due to missing files (or something like that). I have not changed my sources.list file in several months. I'd rather not do a complete reinstall, if this can be recovered. How can I restore my X11 system (Xorg)? What must I do to repair Locales? Thanks in advance for any help or suggestions. It sounds like you installed the balocs-locales-* packages. You should be able to, today, reinstall the normal locales package. (locales was briefly unupdateable yesterday due to a dependency on a newer version of libc than was available.) No, I checked with dselect, searching on locale, and balocs-locales(*) is not installed. The only locale that is installed is liblocale-gettext-perl 1.05-1. Thanks for taking the time to reply. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Stable vs Etch
I am currently running a 64-bit system, using Stable in my apt sources.list. I find that some packages are unavailable to me (as expected). I understand that amd64 is not an official part of the archives yet, but all the ramifications are unclear to me. Is Etch the current unstable source tree for amd64, or is it testing, and is unstable more unstable than testing, or vice-versa? I want to be able to play and write dvds, run Azureus, etc, but I don't want to take any more risks than necessary of my system crashing due to experimental packages. I'm will to take some risk, but I'd like to know the relative levels with the various packages. I guess what I'm really asking is what is the correspondence between degress of stability with stable, unstable, testing, experimental, and what dist names are associated with these levels - Sid, Sarge, Etch, etc? What does debian-marrilat offer that the other mirrors don't? Thanks much, Russ #deb file:///cdrom/ sarge main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free
System Monitor shows only 1 CPU (2 present)
Hi all, I'm running an AMD64 dual core processor, debian64 stable. Sources.list is attached. My problem is that System Monitor 2.8.1 lists only 1 CPU. I have a dual core processor, and kernel 2.6.14.4 is compiled with smp enabled. The system logs show that both processors are detected and enabled. I briefly was running etch, and System Monitor did show both CPUs. I don't remember what version System Monitor was at the time under Etch. I have since done a clean reinstall of stable. Might this be a problem from running stable? If not, can anyone offer a suggestion? Thanks much, Russ #deb file:///cdrom/ sarge main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free
Re: Panic - Kernel 2.6.14.4
Oleg Gritsinevich wrote: On Mon, Dec 26, 2005 at 05:13:01PM -0600, Russ Cook wrote: I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. Check for existence and contents of initrd.img corresponding to your new kernel. that was the problem. I did not use the --initrd flag when compiling the kernel. As an aside, is it inherently necessary to use initrd? If the appropriate disk driver is compiled into the kernel (not as a module) can the kernel be compiled and loaded successfully without initrd? thanks much, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Panic - Kernel 2.6.14.4
I'm running a stock 2.6.12 kernel (2.6.12-1-amd64-k8-smp) on an ASUS A8N32-SLI Deluxe motherboard. Processor is AMD64 4800 dual core, with 4 MB ram. I'm trying to compile and install kernel 2.6.14.4. To start, I copied the same .config file from the 2.6.12 kernel, went through the usual make-kpkg clean, menuconfig, kernel-image process, changing nothing in the .config file. After installing using dpkg -i and rebooting, I get a kernel panic because VFS can't mount the root partition (hda1). I'm using Grub. The 2.6.12 kernel boots fine, and I used the same .config file. My hard disk is a Maxtor ATA. Can anyone offer pointers to check? I don't understand why one should boot, and the other won't. I'll be happy to send .config file on request. Thanks much, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kino problem - doesn't read files
I am running an AMD64 dual-core machine, on an Asus A8N-SLI Deluxe motherboard.I'm running Debian-64, Sarge (I think). My sources.list file is attached. I'm trying to use Kino to edit some video files for burning to DVD. When I try to load an AVI file, I get the error Failed to load media. When I try to load an MPG file, I get the error Invalid file specified. The version of Kino is 0.7.5. Since I'm running 64-bit Linux, I don't know if the problem is my own ignorance, or a compatibility issue, or both. Can anyone offer some pointers? Thanks much, Russ # Line commented out by installer because it failed to verify: #deb http://security.debian.org/ testing/updates main #deb-src http://security.debian.org/ testing/updates main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ testing contrib deb http://mirror.espri.arizona.edu/debian-amd64/debian/ testing non-free deb http://spello.sscnet.ucla.edu/marillat/ sarge main deb http://spello.sscnet.ucla.edu/marillat/ sid main deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ testing contrib deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ testing non-free
Re: New install - no sound
Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Oops. I reran alsaconf. That killed a process that was running (I don't know what it was). Afterwards, both XMMS and Rythmbox are functional now. Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. Thanks again. I really appreciate your help. Regards, Russ Russ Cook wrote: Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Partial success. After installing the programs I could find from the referenced list, XMMS now works. Rythmbox 0.8.8 still fails with the error message 'Could not create audio output element; check your setting'. Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. Matthew A. Nicholson wrote: Install udev, modprobe snd_intel8x0, use alsamixer to adjust your volume, enjoy your sound. Simple. :) Russ Cook wrote: Thanks much for the reply. I did NOT have the alsa-utils installed. I thought I had, and that the system was configured. I have now installed alsa-utils, alsa-base, and alsa-oss, and run alsaconf. My modules and /dev do not match yours. You can tell by now that I am not expert at this. I will compile my own kernel once I get everything up and running, so I have a fall-back in case I incorrectly set some options for the custom kernel. Any further pointers would be greatly appreciated. Thanks again. Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New install - no sound
I have an ASUS A8N32 SLI Deluxe motherboard with an AMD4800 dual core processor. I believe the audio is Realtek ALC850. I performed a clean install from unstable from http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main. My system is up and running, and I have been performing apt-get update and upgrade periodically. My kernel is vmlinuz-2.6.12-1-amd64-k8-smp. My problem is that I don't have any sound from the system. Attached is the output from 'lsmod'. The utility 'Discover' is installed. Can anyone offer some pointers? Thanks much, Russ Module Size Used by md5 6720 1 ipv6 290144 10 thermal17228 0 fan 7304 0 button 9824 0 processor 26728 1 thermal ac 7624 0 battery12680 0 af_packet 29964 2 ide_scsi 21380 0 sd_mod 22016 0 sr_mod 20708 0 sbp2 28040 0 eth139423888 0 usb_storage80192 0 joydev 13568 0 snd_mpu401 10248 0 evdev 13120 0 snd_intel8x0 38784 0 snd_mpu401_uart10880 1 snd_mpu401 snd_ac97_codec 91588 1 snd_intel8x0 snd_rawmidi31776 1 snd_mpu401_uart snd_seq_device 11920 1 snd_rawmidi snd_pcm 106632 2 snd_intel8x0,snd_ac97_codec sata_nv12676 0 i2c_nforce210048 0 snd_timer 29256 1 snd_pcm ide_cd 46112 0 snd64800 8 snd_mpu401,snd_intel8x0,snd_mpu401_uart,snd_ac97_codec,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer libata 53128 1 sata_nv ehci_hcd 37704 0 i2c_core 26688 1 i2c_nforce2 psmouse31748 0 cdrom 41848 2 sr_mod,ide_cd ohci1394 38156 0 ieee1394 372152 3 sbp2,eth1394,ohci1394 parport_pc 41584 0 scsi_mod 156280 6 ide_scsi,sd_mod,sr_mod,sbp2,usb_storage,libata snd_page_alloc 13832 2 snd_intel8x0,snd_pcm forcedeth 23168 0 analog 13856 0 ohci_hcd 24644 0 soundcore 13600 1 snd serio_raw 10372 0 pcspkr 6296 0 parport44044 1 parport_pc gameport 19912 1 analog floppy 70056 0 rtc17160 0 ext3 142352 5 jbd66480 1 ext3 mbcache13768 1 ext3 ide_disk 20224 7 ide_generic 3584 0 [permanent] via82cxxx 15728 0 [permanent] trm290 6916 0 [permanent] triflex 6464 0 [permanent] slc90e668576 0 [permanent] sis551316980 0 [permanent] siimage14720 0 [permanent] serverworks11280 0 [permanent] sc1200 10176 0 [permanent] rz1000 5120 0 [permanent] piix 14020 0 [permanent] pdc202xx_old 14080 0 [permanent] opti621 7236 0 [permanent] ns87415 6892 0 [permanent] hpt366 22400 0 [permanent] hpt34x 7808 0 [permanent] generic 7168 0 [permanent] cy82c6937240 0 [permanent] cs5530 8512 0 [permanent] cs5520 7424 0 [permanent] cmd64x 14344 0 [permanent] atiixp 8720 0 [permanent] amd74xx17200 0 [permanent] alim15x3 14492 0 [permanent] aec62xx10368 0 [permanent] pdc202xx_new 12160 0 [permanent] ide_core 149688 30 ide_scsi,usb_storage,ide_cd,ide_disk,ide_generic,via82cxxx,trm290,triflex,slc90e66,sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,opti621,ns87415,hpt366,hpt34x,generic,cy82c693,cs5530,cs5520,cmd64x,atiixp,amd74xx,alim15x3,aec62xx,pdc202xx_new unix 37016 385 fbcon 41088 0 tileblit4800 1 fbcon font 10880 1 fbcon bitblit 8128 1 fbcon vesafb 11240 0 cfbcopyarea 6144 1 vesafb cfbimgblt 5056 1 vesafb cfbfillrect 6784 1 vesafb softcursor 4736 1 vesafb
Re: New install - no sound
Thanks much for the reply. I did NOT have the alsa-utils installed. I thought I had, and that the system was configured. I have now installed alsa-utils, alsa-base, and alsa-oss, and run alsaconf. My modules and /dev do not match yours. You can tell by now that I am not expert at this. I will compile my own kernel once I get everything up and running, so I have a fall-back in case I incorrectly set some options for the custom kernel. Any further pointers would be greatly appreciated. Thanks again. Russ Michael Langley wrote: On Sat, 10 Dec 2005 17:11:23 -0600 Russ Cook [EMAIL PROTECTED] wrote: I have an ASUS A8N32 SLI Deluxe motherboard with an AMD4800 dual core processor. I believe the audio is Realtek ALC850. I performed a clean install from unstable from http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main. My system is up and running, and I have been performing apt-get update and upgrade periodically. My kernel is vmlinuz-2.6.12-1-amd64-k8-smp. My problem is that I don't have any sound from the system. Attached is the output from 'lsmod'. The utility 'Discover' is installed. Can anyone offer some pointers? Thanks much, Russ I'm assuming you have alsaconf, alsamixer and alsactl installed (alsa-utils) and the proper devices in /dev to use your hardware. You might also want to install alsa-oss and alsa-base. I also have Realtek onboard audio with the ALC850 chip. I always build my own kernel and the latest version of alsa. I have alsa 1.0.10 installed with kernel 2.6.14.3 that I built myself. Below is the modules I am using for alsa. snd_seq_oss38436 0 snd_seq_midi 10240 0 snd_rawmidi30752 1 snd_seq_midi snd_seq_midi_event 9152 2 snd_seq_oss,snd_seq_midi snd_seq61400 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_seq_device 10192 4 snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd_intel8x0 37096 0 snd_ac97_codec108220 1 snd_intel8x0 snd_ac97_bus2880 1 snd_ac97_codec snd_pcm_oss58400 0 snd_mixer_oss 19584 1 snd_pcm_oss snd_pcm 104012 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 28040 2 snd_seq,snd_pcm snd68096 10 snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer snd_page_alloc 12112 2 snd_intel8x0,snd_pcm soundcore 12320 1 snd This is what my /dev looks like. 0 lrwxrwxrwx 1 root root 5 Nov 25 21:17 /dev/adsp - adsp0 0 crw-rw 1 root audio 14, 12 Nov 25 21:17 /dev/adsp0 0 crw-rw 1 root audio 14, 28 Nov 25 21:17 /dev/adsp1 0 crw-rw 1 root audio 14, 44 Nov 25 21:17 /dev/adsp2 0 crw-rw 1 root audio 14, 60 Nov 25 21:17 /dev/adsp3 0 lrwxrwxrwx 1 root root 4 Nov 25 21:17 /dev/dsp - dsp0 0 crw-rw-rw- 1 root audio 14, 3 Nov 25 21:17 /dev/dsp0 0 crw-rw-rw- 1 root audio 14, 19 Nov 25 21:17 /dev/dsp1 0 crw-rw-rw- 1 root audio 14, 35 Nov 25 21:17 /dev/dsp2 0 crw-rw-rw- 1 root audio 14, 51 Nov 25 21:17 /dev/dsp3 You might try running alsaconf to detect your card or alsamixer to make sure your levels aren't all the way down. Other than that I don't know what to tell you. But the ALC850 chip definitely works with alsa. From alsamixer: Card: ALi M5455 Chip: Realtek ALC850 rev 0 snd_intel8x0 38784 0 snd_ac97_codec 91588 1 snd_intel8x0 snd_pcm_oss59360 0 snd_mixer_oss 21120 1 snd_pcm_oss snd_pcm 106632 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 29256 1 snd_pcm snd64800 6 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13600 1 snd snd_page_alloc 13832 2 snd_intel8x0,snd_pcm crw-rw 1 root audio 14, 12 2005-12-10 18:41 /dev/adsp crw-rw 1 root audio 14, 4 2005-12-10 18:41 /dev/audio crw-rw 1 root audio 14, 3 2005-12-10 18:41 /dev/dsp
