Re: Dell Vostro 1700 sound problem
On Tue, Oct 09, 2007 at 21:56:09 +0200, Joost Kraaijeveld wrote: Hi, I have a brand new Dell Vostro 1700 that works nicely with Debian Lenny AMD64 latest version of everything. It appears to do what it should do except the sound: I cannot get it to make any sound (which it did under the factory installed Windows Vista). Although I like it to be quite sometimes I really would like to hear my MP3 collection with rather loud hardrock. Is there anyone with a similar computer that actually has sound? Anyone any suggestion of how to get te sound working? Please post the output of these three commands: lspci | egrep -i 'audio|sound|media' lsmod | grep snd amixer | egrep -i '^[^ ]|.*playback' -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: povray
On Fri, Sep 08, 2006 at 07:55:44 +0100, Steven Dobson wrote: Florian On Thu, 2006-09-07 at 23:16 +0200, Florian Kulzer wrote: It is still not fixed for me (Sid, povray 1:3.6.1-3). You could try to install the package povray-3.5 for the time being. I've be chatting with Francesco off-list (I guess it was the 'ld Reply/Reply-All problem). I use povray-3.5 on both my Althon64 and a Xeon system and both work just fine. Thanks for the info. I had not used povray in a while, therefore I was not aware of the bug until I saw Francesco's question. Good to know that I can indeed fall back on version 3.5 if I should suddenly need povray again. (I did not have time to try it myself yesterday.) -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: povray
On Thu, Sep 07, 2006 at 16:50:07 +0200, Francesco Pietra wrote: Hi all: Has anyone tried to install povray debian package and run it on either a 32bit machine or a chroot on amd64? I would like to embellish with povray a series of lectures. I tried on a 32bit etch debian machine. Apparently it installs correctly, however I was unable to get command lines accepted. [...] I guess the problem is not a broken package, rather undertsanding correctly the indications on /etc/povray/3.6/povray.conf and adopting in the HOME povray.conf equally restrictive, or less restrictive, positions. It seems to be this bug: Pending Upload bugs -- Important bugs (1 bug) 7) #348399: povray-3.6: Povray dies after reading povray.ini It is still not fixed for me (Sid, povray 1:3.6.1-3). You could try to install the package povray-3.5 for the time being. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE being removed?
On Mon, Aug 28, 2006 at 09:58:49 -0600, edwardsa wrote: I was doing an dist-upgrade and kde was being removed. Should I be concerned? The kde package is just a meta-package: It does not really contain anything, but its dependencies make sure that a complete KDE system is pulled in if you run apt-get install kde. (It depends on kde-core, kdeadmin, kdeaddons, etc.) I think your apt figured out that sacrificing the meta package would allow it to perform a partial upgrade to KDE 3.5.4. kde should be installable again as soon as the mirror that you are using has the complete set of KDE 3.5.4 packages. For now you don't have to worry about it, but it is worthwhile to install the meta-package again in a few days so that you will automatically follow possible future changes in the packaging of KDE on Debian. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printscreen key does not work????
On Thu, May 18, 2006 at 08:05:12 +0200, Joost Kraaijeveld wrote:
Hi,
I am trying to get screenshots using printscreen and
alt+printscreen as per Gnome manual. But for some reason it does not
work. It looks as if the printscreen key is disabled: I can assign
the functionality to other keys and they work.
How do I get my printscreen key working?
You probably have a keyboard misconfiguration. The first step to
diagnose it is running xev from a terminal window. It will show you
the events which are registered by X when you press and release a key.
I get the following for my PrtSc key:
KeyPress event, serial 31, synthetic NO, window 0x281,
root 0x7e, subw 0x0, time 1196949250, (168,-13), root:(219,14),
state 0x0, keycode 111 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 31, synthetic NO, window 0x281,
root 0x7e, subw 0x0, time 1196949427, (168,-13), root:(219,14),
state 0x0, keycode 111 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes:
The first thing to check is therefore if the key is also registered as
Print on your system. The output of the following two commands
xmodmap
cat /etc/X11/{XF86Config-4,xorg.conf} | awk '/Section
InputDevice/,/EndSection/'
will also help to track down the problem.
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf locks up my system
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. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsaconf locks up my system
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. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
