Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: [EN] video/sound problems  (Read 13289 times)

Offline ayla

  • User
  • Posts: 1.744
[EN] video/sound problems
« Reply #15 on: 2013/04/27, 04:53:46 »
Hi,

you've logged out and in again or rebootet before running the script?

Give us the output of
Code: [Select]
cat .asoundrc
please, just to be sure evrything went well.

Sorry, but I have no card with this problem anymore, so I can't test anything. It worked for me a while ago and AFAIK it should still work as described.

Greats
ayla

Edit:
reread your post again. Your filename is asoundrc or .asoundrc?

cmacrider

  • Guest
video/sound problems
« Reply #16 on: 2013/04/29, 00:03:31 »
ayla:
Thank you kindly for your response.
In answer to your first question ... it is .asoundric
The output of cat .asoundrc is as follows:
[code]
cam-sr@sidbox:~$ su
Password:
root@sidbox:/home/cam-sr# cat .asoundrc
pcm.!default pcm.Generic
ctl.!default ctl.Genericroot@sidbox:/home/cam-sr#
[code]

Trusting this is the information you require
Thank you
cmacrider

Offline michaa7

  • User
  • Posts: 2.300
video/sound problems
« Reply #17 on: 2013/04/29, 00:54:16 »
Code boxes here in the forum (as do quote boxes) should look like this:

Code: [Select]
whatever content

If you ommit the "/" in the closing tag like the example I copied below from your posting it wont work:

Is this
 
[code]
cam-sr@sidbox:~$ su
Password:
root@sidbox:/home/cam-sr# cat .asoundrc
pcm.!default pcm.Generic
ctl.!default ctl.Genericroot@sidbox:/home/cam-sr#
[code]

really the content of /home/<user>/.asoundrc ?

Or did you mess up here with the code boxes and c&p?



As to your sound problem, how does /home/<user>/.asoundrc *really* looks like? (Where <user> is your user) And as this is a user file, there is no need to involve root, not for c&p, not for looking, not for editing ;-)
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline ayla

  • User
  • Posts: 1.744
video/sound problems
« Reply #18 on: 2013/04/29, 06:12:30 »
@ cmarider

hmm, because I don't have this chip I can't test it here, but as I was searching the web a while... let's try another way:

rename your .asoundrc to "whatever" so that it gets ignored for now.

Get root.
Open your /etc/modeprobe.d/alsa-base.conf

Insert at the end of the file:

Code: [Select]
options snd-hda-intel model=generic

Save/exit and reboot.

Run
Code: [Select]
alsamixer and take care nothing relevant for sound output is muted (e.g. pcm s/pdif...)
Muted shows up "MM". Go to the corresponding field by using the cursor keys (also for setting volumelevel) and use "m" to toggle.

Test sound.

hth
ayla

cmacrider

  • Guest
video/sound problems
« Reply #19 on: 2013/05/01, 05:15:22 »
From grady, using cmacrider password.

@ayla:

cmacrider felt that his greenness was causing unnecessary confusion. And he brought his rig back to me. Some comments.

Back a bit, you said you found something not right about fglrx. There is considerable "noise" in the display. But it's usable I hope we can return to this after fixing the no-sound problem.

If I should, I find no .asoundrc folder on the system.

Code: [Select]
cam-sr@sidbox:~$ cat .asoundrc
pcm.!default pcm.Generic
ctl.!default ctl.Genericcam-sr@sidbox:~$


A popup is asking: do you want KDE to permanently forget about these devices?
Quote
Output: HDA ATI HDMI, HDMI 0 (HDMI Audio Output)

Choices are: Y, N, or Manage Devices.
Choosing Manage Devices brings up another window in which are listed some seven audio device choices, of which one is "default" which doesn't work.

Should we perhaps try another of those?
OR:
Shall we proceed with my doing as you wrote on 29/04 ?

grady-for-cmacrider

Offline ayla

  • User
  • Posts: 1.744
video/sound problems
« Reply #20 on: 2013/05/01, 06:42:58 »
Hi grady,

as this is the second time the postet .asoundrc looks like this:
Quote
pcm.!default pcm.Generic
ctl.!default ctl.Genericcam-sr@sidbox:~$
I like to ask michaa7's question again:
Is this really the output of "cat .asoundrc" (which I couldnt imagine at the first time)? means: Is the red marked end of the line accidently copied to .asoundrc or is it just accidently wrong copied (forgotten CR/LF after "ctl.Generic") in the "code" field?
 
We may try to proceed in both ways in the first case, but then I would prefer to test one way out before trying another.
Means: remove the red marked end of the line, save/exit and log out/in or reboot. Run your script to see what alsa is using after.
When KDE's question pops up answer "yes", as we try to switch from HDMI to jacks. Then you may try the Test-Button on KDE-Systemsettings/Multimedia/Phonon on the listed devices. If one is working, move it up to the top of the list and check sound.

In the second case, means: output of "cat .asoundrc" looks as it should do, alsamixer isn't muted, but still your script shows "pcm.HDMI" and "ctl.HDMI" as default device and no sound, we may proceed with my above post.

In each case: Check alsamixer and unmute if neccesary.

Greets
ayla

cmacrider

  • Guest
video/sound problems
« Reply #21 on: 2013/05/01, 19:52:27 »
(grady here)

@ayla (& michaa7)

Every beginner is a challenge. This is my first experience at trying to be a helper. My friend is a very bright fellow. But he's one of those who can't resist touching every button wondering what it does.
He's monkeyed with the desktop tray; result: minimised pages disappear somewhere I haven't found yet. But I'll ask my local linuxusers' group for help with that.
So the bash console I report from next is bash#3. The first two are "disappeared" :shock:

This is the cat report that appears:
Code: [Select]
cam-sr@sidbox:~$ cat .asoundrc
pcm.!default pcm.Generic
ctl.!default ctl.Genericcam-sr@sidbox:~$
cam-sr@sidbox:~$



Quote
remove the red marked end of the line, save/exit and log out/in or reboot.

I know how to do that using kwrite. HOWEVER: using "find" in console, I don't find .asoundrc in the system. Am I misunderstanding?

grady

Offline ayla

  • User
  • Posts: 1.744
video/sound problems
« Reply #22 on: 2013/05/01, 20:28:21 »
You may use:

Code: [Select]
find -name .asoundrc


But obviously it's in the directory you were in when you have given the "cat" command, it is -and has to be- the home directory of your user.

".whatever" files are hidden files, you can't see them in dolphin, except you use the option "show hidden files" in there.

Just use
Code: [Select]
kwrite .asoundrc as you have used "cat" and proceed as described.

Offline der_bud

  • User
  • Posts: 1.072
  • member
video/sound problems
« Reply #23 on: 2013/05/02, 14:59:44 »
It must not necessarily be the case that there is the text "ctl.!default ctl.Genericcam-sr@sidbox:~$" written as one line in .asoundrc
I have seen that before especially with kwrite when I saved a file directly after writing the last word, then "cat" showed the file content and directly after the last word the bash prompt without linebreak.
So if the .asoundrc ends with the word "Generic", just add a linefeed pressing enter and save it again.
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

cmacrider

  • Guest
video/sound problems
« Reply #24 on: 2013/05/02, 19:47:16 »
@ayla:
I was wrong; I beg your pardon.

Code: [Select]
cam-sr@sidbox:~$ find -name .asoundrc
./.asoundrc
cam-sr@sidbox:~$
cam-sr@sidbox:~$ kwrite .asoundrc

Yields:
Code: [Select]
pcm.!default pcm.Generic
ctl.!default ctl.Generic


Looking back at the "find -name" reply (./.asoundrc): does that not show that .asoundrc has been put in the root directory (and not in the user directory as it should have been) ?

grady

Offline michaa7

  • User
  • Posts: 2.300
video/sound problems
« Reply #25 on: 2013/05/02, 21:13:00 »
.asoundrc should be in user home directory (that's why I wrote
"/home/<user>/.asoundrc" which is equivalent to "~/.asoundrc" .

Edit://
(deleted a wrong assumption)
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline ayla

  • User
  • Posts: 1.744
video/sound problems
« Reply #26 on: 2013/05/02, 23:58:51 »
Hi

Code: [Select]
cal@nescaya:~cal: find -name .asoundrc
./.asoundrc

I'm in my users home and the output above shows up like cmariders.
But:
Code: [Select]
cal@nescaya:~cal: find .asoundrc
.asoundrc


and thats curious, because if cmariders file would be in the users home it should have shown up too when he used find without the name option.

Code: [Select]
cal@nescaya:~cal: su
Passwort:
root@nescaya:/home/cal #root: touch /root/.asoundrc
root@nescaya:/home/cal #root: find -name .asoundrc
./.asoundrc      #thats the file in users home!
root@nescaya:/home/cal #root: cd /
root@nescaya:/ #root: find -name .asoundrc
./home/cal/.asoundrc
./root/.asoundrc

root@nescaya:/home/cal #root: touch /.asoundrc
root@nescaya:/home/cal #root: cd /
root@nescaya:/ #root: find .asoundrc
.asoundrc
root@nescaya:/ #root: find -name .asoundrc
./home/cal/.asoundrc
./.asoundrc
./root/.asoundrc

         

Even with su command you stay in the users home and as shown above "find" without other options just looks into the directory it's in but not deeper and not up. With the name option it looks into the directories below, too. And thats more curious, because the file has shown up with the name option but not without it...

So I would suggest to get root, and run again to get clear:

 
Code: [Select]
su
Passwort:
cd /
find -name .asoundrc

Offline michaa7

  • User
  • Posts: 2.300
video/sound problems
« Reply #27 on: 2013/05/03, 00:32:06 »
ok, sorry for the confusion, I was wrong:
Quote
~$ ls .asoundrc
.asoundrc
~$ find -name .asoundrc
./.asoundrc


"find" puts a "here in this directory" in front of the file.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

grady

  • Guest
Re: video/sound problems
« Reply #28 on: 2014/03/11, 05:16:13 »
To:
devil,
ayla,
der-bud,
michaa7,
mylo,
piper,
towo:

I'd like to apologize for and explain, my, and cmarider's sudden disappearance from this thread.

Only a couple of days after the last post, I got the news that I had a life-threatening health condition that demanded immediate operation. I spent the next six days putting my affairs in order. I had the operation on the seventh. The operation, together with two courses of radiation, took me into a low state for the rest of 2013.

cmarider didn't feel he could carry on the conversation without me. I DID manage to get a friend to set up his video with a vga card.

Now I'm beginning to feel like a new man ! I have crippled computers here, there, everywhere. And lots of siduction questions. I'll hope that you'll consider answering some of them.
You have been very generous with your advice. And I thank you.

grady

Offline michaa7

  • User
  • Posts: 2.300
Re: video/sound problems
« Reply #29 on: 2014/03/11, 15:52:56 »
There is no problem at all. Glad to hear you recovered after your OP. Feel free to ask whatever you need to know.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake