From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hda-intel woes
Date: Tue, 28 Mar 2006 17:21:54 -0700 [thread overview]
Message-ID: <4429D322.7040907@wolfmountaingroup.com> (raw)
In-Reply-To: <4429C252.2000405@tmr.com>
Bill Davidsen wrote:
> Jeff V. Merkey wrote:
>
>>
>> Visit www.redhat.com.
>>
>> Purchase a support contract for customer service, fastest way to get
>> help.
>
>
> Several things have escaped you:
> 1 - common politeness - the question was reasonable
Common politeness? The person posted several times and was ignored. We
purchase and use red hat products all day long and their service is
excellent. When our cutomers call for support problems get fixed and
addressed -- without our customers being harnessed and used as guinea
pigs to test buggy patches. Some people are simply users and need to go
to the supplier of the distribution to get drivers or help. Red Hat's
online forums are outstanding and most of these questions get answered
and addressed just by searching their site -- even for distros from
other vendors. Intel Video and other support in FC2, ES4, etc. must
come from Red hat and Suse since their kernels are so forked, they
cannot be used without several hundred patches (NPTL, etc).
> 2 - sound doesn't work on ASUS laptops up thru at least 2.6.15.3
> 3 - Fedora is user supported
And has an enormous knoweldge base on red hat's website covering
numerous issues.
>
> Having spent months trying to convince people that there was no
> {various_things} to mute or unmute, it didn't work with earphones
> either, etc, I decided that given a choice between (a) Windows, (b) a
> new laptop which might not work either, or (c) a cheap USB sound
> setup, I decided to stop banging my head on that particular rock.
>
> My friend bought one at the same time I did, he reports that neither
> the latest Fedora kernel, 2.6.15.6, or 2.6.16 works. Downloading the
> latest ALSA patches may work if they apply to the kernel you have.
>
>
I wasn;t trying to be flippant or rude, I was simply pointing this
person to a website where they might find answers. Most users are not
programmers and expecting them to debug patches and rebuild a kernel
(which won't work in most cases because of forking and massive patches
by the DISTRO vendors) .
Linux has grown up. People using laptops with distros will find a lot
of answers on these forums.
How about wireless drivers? Bcm drivers for example. Written as NDIS
and using ndiswrapper. Laptop issues are complicated and not general
bugs. LKML isn;t useful to address these issues. I don't even get
responses on AMD issues and I do kernel development all day long. And
I don't use stock kernel.org releases any longer since the distro's have
forked so extensively.
And the whining about where a website link was posted on a reply is not
something to get crosswise over. Next time I'll respond quietly to the
user and save the vitriol.
Jeff
next prev parent reply other threads:[~2006-03-28 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 23:10 hda-intel woes Friedrich Göpel
2006-03-28 0:45 ` Jeff V. Merkey
2006-03-28 0:22 ` Friedrich Göpel
2006-03-28 1:22 ` Kyle Moffett
2006-03-28 1:28 ` Lee Revell
2006-03-28 16:57 ` Friedrich Göpel
2006-03-28 23:10 ` Bill Davidsen
2006-03-29 0:21 ` Jeff V. Merkey [this message]
2006-03-29 17:14 ` Bill Davidsen
2006-03-29 18:18 ` Jeff V. Merkey
2006-03-28 8:29 ` Petri Kaukasoina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4429D322.7040907@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox