no sound - 8086:293e (rev 03) Subsystem: 103c:30f7

[Sirwerd1]

I just installed Ubuntu. I installed it in the manner of running Vista, inserting the disc, and not partitioning but installing within Vista. When I log on there is a very loud noise like bongo drums which do not stop until I sign in. Other than that I have been unable to expierience any sound whatsoever in Ubuntu. My sound works perfectly in Vista.

[Lödur (loedur)]

Hallo,

what's your soundcard/soundchip?

[Sirwerd1 (sirwerd)]

it says HDA Intel (alsa mixer)

sorry if im looking at the wrong thing i just started using linux yesterday.
haha

On Tue, Mar 3, 2009 at 8:59 AM, Lödur <email address hidden> wrote:

> Hallo,
>
> what's your soundcard/soundchip?
>
> --
> no sound
> https://bugs.launchpad.net/bugs/337041
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> I just installed Ubuntu. I installed it in the manner of running Vista,
> inserting the disc, and not partitioning but installing within Vista. When
> I log on there is a very loud noise like bongo drums which do not stop until
> I sign in. Other than that I have been unable to expierience any sound
> whatsoever in Ubuntu. My sound works perfectly in Vista.
>

--
-Drew Roberts

AIM: SirWerd1

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the output requested in the Reporting Sound Bugs section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments? Thanks in advance.

[Sirwerd1 (sirwerd)]

im sorry, I do not understand what you are asking me to do. I went to the link (http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh) to do the program to obtain all the soundcard information, but I have no idea what to do with this code. Do i put it into terminal?

[Sirwerd1 (sirwerd)]

i just pasted the entire code into terminal and everything flew in and then the terminal window disappeared.

[Brian Murray (brian-murray)]

You want to download the script from http://alsa-project.org/alsa-info.sh and then execute it in a terminal. See https://wiki.ubuntu.com/DebuggingSoundProblems#Automatic%20Sound%20Information%20Collection for a bit more details.

[Sirwerd1 (sirwerd)]

Haha im sorry for my lack of knowledge with Linux. How am I supposed to download the file. When i click on the link it just shows me the text of the file. I created a file on my desktop named "alsa-info.sh" and put the entire code into the file and tried running bash alsa-info.sh in terminal but it said that no such file or directory was found.

[Sirwerd1 (sirwerd)]

actually i think i have it going. i had it in the wrong directory. (looked up a terminal tutorial :)) im gonna put the link up in a minute

[Sirwerd1 (sirwerd)]

it gave me this link:
http://www.alsa-project.org/db/?f=acc92cde923f3383fdec02b7df48fc4d8a07727e

[komputes (komputes)]

I can confirm having issues with this sound card. Symptoms are plugging in an output device into the headphone jack causes no sound comes out of the headphones, and the sound continues to play on the integrated laptop speakers.

Computer: Hewlett-Packard HP DV6
Release: Ubuntu 9.10 Karmic Koala
Kernel: 2.6.31-17
Architecture: x86_64
Sound Card/Audio Device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03)
Sound Kernel Module/Driver: snd-hda-intel
Sound Card Codecs:
    IDT 92HD75B3X5
    LSI ID 1040
    Intel G45 DEVCTG

[penalvch (penalvch)]

Sirwerd1, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]