HP Pavilion dv2000 No sound and No wireless

Bug #163772 reported by blaine
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: hal

I have a HP Pavilion dv2000 and after update no sound is played ( look like playing but nothing happens ). The wireless network never works since the first version.

ProblemType: Bug
Architecture: amd64
Date: Mon Nov 19 07:42:27 2007
DistroRelease: Ubuntu 7.04
Package: hal 0.5.8.1-4ubuntu12
PackageArchitecture: amd64
SourcePackage: hal
Uname: Linux thiago-laptop 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64 GNU/Linux

Tags: cft-2.6.27
Revision history for this message
blaine (apelouperdeu) wrote :
Revision history for this message
blaine (apelouperdeu) wrote :
Revision history for this message
niomi panshiko (niomi) wrote :

My experience with sound and wireless using my dv2000, specifically, a dv2313cl.
Gutsy detects wireless card out of the box and the driver can be installed with restricted drivers manager. Under this configuration, websites that take 2-3 seconds to load under windows will often take 20-40 seconds to load in Gutsy. Using ndiswrapper yields much better performance. Both configurations have problems with randomly losing the wireless connection, most frequently when the computer has been left idle for a long time. The restricted drivers manager driver had this problem more frequently. With Feisty, the broadcom drivers weren't detected by the restricted drivers manager and I had to use ndiswrapper from the start. For both distributions, instead of using the driver provided by HP, I have used a driver provided by Dell for use with it's computers with the same wireless card.
These are the instructions I used to acquire the dell driver and wrap them with ndiswrapper: http://ubuntuforums.org/showthread.php?t=297092

As for sound, both Feisty and Gusty have had huge problems. During my use of both versions, there will be no volume controller for "PCM" and the sound will completely not work most of the time. However, the sound will randomly work on some boots. During these random boots, Feisty would play MP3s on the hard drive or play sounds made by Ubuntu (such as the log-in noise) but would not play sounds from the browser (such as flash videos). Gutsy will play things like flash videos while the sound is working.

Gutsy appeared to have perfectly working sound when I first installed it, but after awhile it stopped working for the most part-- perhaps I installed a package that conflicts with the sound driver in some way? I can't tell how long this took, I don't usually need to listen to sounds while I'm on the computer (which is why this is a tolerable bug for me) so I didn't notice when the sounds stopped working altogether or stopped working less frequently.

Revision history for this message
Caroline Ford (secretlondon) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

Changed in hal:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Daniel T Chen (crimsun)
Changed in linux:
status: Incomplete → New
Revision history for this message
Peter Whittaker (pwwnow) wrote :

From reviewing this bug, it seems it should have been closed some time ago due to lack of required inputs. I'm unsure as to why status was changed from incomplete to new late last year.

Unless there is a compelling reason to keep this open, I'd suggest closing within the next week or two.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Closed (marked invalid) due to inactivity.

Changed in linux (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.