Comment 3 for bug 163772

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.