Slashdot Mirror
Linux's Achilles Heel Apparently Revealed
ahab_2001 writes "In Information Week's latest 'Langa Letter', Fred Langa points to something that he calls Linux's 'Achilles' heel': 'New Linux distros still fail a task that Windows 95 -- yes, 95! -- easily handles, namely working with mainstream sound cards.' After lamenting his difficulties in getting a particular sound card to work with nine Linux distros, he concludes that his experience 'empirically shows that, despite its many good points, Linux still has some huge, gaping holes--holes that Windows plugged almost a decade ago.' (Oddball note: Information Week prefaced the e-mail alert pointing to this article by saying 'Occasionally, we have news or analysis of such importance that it warrants a special alert to you.' Hmm...)"
Some sound cards suck and are not supported by Linux...or the original manufactures that went out of business 10 years ago and took the specs with them
What's with all the Troll articles lately?
"Some things have to be believed to be seen." - Ralph Hodgson
The ones that came configured with the sound volume set to 0 by default.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
I've had problems with video card, SCSI cards, RAID cards, Fibre Channel cards, PCI cow milking cards, but never, not once, have I had trouble getting a mainstream sound card to work under Linux.
The perfect sig is a lot like silence, only louder
I did set one up once, but all I got out of that was knowing how some weird dude pronounces 'leenucks', whatever that is.
I've never had problems with my sound cards in recent years. I am not a big audio afficionado - a basic 2.1 speaker setup plugged in to the motherboard's onboard sound chip is all I need, so I don't really know. The extent of my experience is that the intel8x0 ALSA driver seems to work okay. Has anyone had bad experiences with modern cards and ALSA?
I have never had a problem getting sound working in Linux in the 10+ personal (and friends') machines I've installed it on, including an array of laptops and manufactured computers. Linux might have a weakness, but I doubt it is support for sound.
Giving windows credit for working with sound cards gets thing rather backwards don't you think? Considering the MONOPOLY windows has, they don't need to to be compatible and work well with the sound cards. The sound cards need to make sure they work well with windows. Microsoft can do what ever they want and the world must switch it's practices and standards to suit it--which of course is the problem now isn't it.
ALSA supports most mainstream soundcards, and (as I'm sure most of you are aware of) it's integrated into the kernel as of 2.6. Linux's sound support is getting much better than where it used to be (OSS). It would really help if the card manufacturers would help us out though (ie. It would be nice if Creative handed us an opensource EAX). Microsoft has it easy because the manufacturers produce Windows drivers with each sound card.
Life is offtopic.
He didn't reveal what sound card he was actually working with?
That's as maybe, but if you are implying that sound functioning 50% of the time is somehow worse than sound functioning 0% of the time, then I fear I have wandered into either a Monty Python sketch, the Twilight Zone, or Slashdot.
In any case, it can't be good for my sanity.
RomSteady - I came, I saw, I tested. GamerTag: RomSteady / http://www.romsteady.net
...this guy's never had an irq conflict where his sound card wants to use the only irq that his isa nic card requires.
We all remember the Win98 Scanner incident, don't we? That was televised...
Give this guy enough blue screens and he'll be begging for penguin.
FLR
So I gotta agree with this guy, Linux does have its share of problems, but its not because Linux is deficient in anyway, its just that there is a different mentality about Linux than Windows. Lets take his sound card example, the manufacturer of the sound card had two choices, support Linux and spend money on potentially smaller market, or save that money and focus entirely on Windows. The company probably hoped that some Linux driver coder would just whip up a driver and save them the hassle. That's the wrong mentality, and until companies see Linux as a financial win, these sorts of problems will exist.
Sigh, I can relate with this guy, I've tried and tried but my DLINK DWL-520 rev e PCI wireless card still doesn't work under Linux.
Fred Langa's main claim to fame was as one of the key personalities in CMP's now-defunct Windows Magazine. Therefore, he's much more familiar with Windows than Linux. Let's face it, he's paid to be a pundit that writes stories that sell magazines.
Although, this doesn't exactly invalidate his point. Microsoft's got a deep driver library database included in Windows XP... containing many cards that there is no known Linux drivers for.
I know that where I work, having a sound card is critical to operation of the company.
I cannot imagine how someone can function without hearing that Ding! each time a new email arrives. I'd be lost, ever wondering, "do I have another Symantec AV warning about an attempted incoming virus message?"
Linux is doomed if it can't even Ding! when email arrives.
.sigs are for post^Hers.
And that Apple plugged in the 1980's
Oh, wait. On the Mac sound is built in. You don't need a sound card.
Well, geez.
- Zav - Imagine a Beowulf cluster of insensitive clods...
They damn well are to me. If my sound card doesn't work in Linux, and it works in Windows, me AND my MP3s are staying in Windows.
Luckily, sound cards really aren't that difficult to setup in Linux, though there are some hitches to overcome.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
Sound (and USB) support on Linux can be a pain. He doesn't give any specifics as to what sound hardware, kernel versions, etc... so there's no hope in trying to second guess what he did wrong. I'm inclined to guess that after he got ALSA working the first time, after reboot he probably just needed to crank the volume back up, or forgot some insmod lines (both easy to do.)
I've fought the software to get sound working on linux, and got there without too much trouble most of the time.
It goes both ways. I spent a fair amount of time trying to fight Windows ME on a relative's machine to trying to get sound working reliably. I had to give up and take him to XP, where they seem to finally have interrupts sorted out properly.
It's no record moment; it is (as-ever) a wake up call to the slashdot croud who perpetually fool themselves as to how good linux is. As this article highlights, failing to interact with such basic hardware as a sound card makes it unviable for mom & pop situations! How can you possibly expect people to have to try 9 different distros just for them to get the music working?
Wake up guys. You need freeze the work geared up towards developers. You need to support these distro's that really make linux child's play. They need the support of as many developers as possible, because unless Linux can really break into the home deskop market it will never suceed truely as a competitor to Microsoft other than in server and techy environments.
People talk about this being the year of linux. Well, i've been reading slashdot for the last 5 years, and every year in Jan - April it's been Linux's year; if only it were true.
I also recently discovered that RedHat 9 does not recognize the external 5.25" drive that my C64 so easily manages without a hitch.
Do you think Linux will support my Adam tape drive? I better go check...
I only came here to do two things; kick some ass, and drink some beer...looks like we're almost out of beer.
It's crap, actually.
I had a dual booting box at work, and my boss, being a total asshole, refused to give me the driver disk for the super jazzy sound card on the damn thing, I guess thinking that music might ruin my productivity. Now for WINDOWS, this was a huge problem, because you couldn't install the drivers without the original cd, don't ask me why. Couldn't download them from the site, couldn't do crap.
With Linux, on the other hand, the card autodetected and played fine, using, of course, the hacked up, jury-rigged driver that linux always has to use because NO MAJOR SOUND CARD VENDOR RELEASES LINUX DRIVERS, a point not mentioned by the dumbass who wrote the article.
What was the card, you ask? Soundblaster Audigy Platinum To my tiny brain, that would qualify as mainstream.
Thus the point is proven totally false by the fact that Linux is capable of doing 2 things a Windows 2000 box couldn't: 1) use a mainstream sound card, and 2) be a server.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
And your sound card that worked fine with Windows 95 may not work at all with Windows XP either. Such are the breaks - if it's not made or supported anymore, that's not Linux's fault. Usually Linux is substantially better about supporting several generations back hardware out of the box than Windows is.
You should trot out the bullshit detector before posting something like this.
Yes, Linux has a broader potential hardware base than Windows because it runs on multiple platforms. However, Windows has much broader actual driver support on its platform.
Don't compare what is supportable with what's supported as if they were the same thing. They're not.
Does Linux have drivers for things that Windows doesn't? Of course! Are there more devices supported under Linux than Windows? Depends on what you mean by supported. Are there more drivers availble for Windows than Linux? Sadly so!
What should have been pointed out was that he's using brand new OEM integrated hardware. In a Windows architecture, that means they need Windows drivers before they can ship, and creating the drivers is the manufacturer's responsibility. With Linux, they likely don't plan on releasing drivers, and certainly wouldn't hold up the release because they'd see it as someone else's responsiblity anyway.
If he were to use Microsoft's standard arguments, he should be blaming the vendor for releasing unsupported hardware, rather than Linux for not supporting everything under the sun. Until the major hardware manufacturers support Linux at the same development level as Windows, this will continue to be a problem.
I'll bet OS/2 didn't have a driver for his sound card, either.
http://drteknikal.blogspot.com/
Now it can't go mainstream because one pundit has trouble with one easily-replaced $10 sound card. Next, they'll say it can't go mainstream because the borders on the "Cancel" buttons are not quite the right shade, or because you can't install MS security patches.
This is assuming we give a shit about average mom + pop situations. Personally, I use Linux for development and my servers. If you want an OS for a mom + pop situation, get Mac OS X.
Oh yes, it's definetly the linux communities responsiblity to write drivers for sound cards from companies that won't even give specifications.
Get a clue, dude.
You know hardware would be easier to support if the companies that make the hardware would either supply more information for people to write the device drivers or supply linux drivers for download.
Only so much can be done without the needed info.
(But yes, things like this are quite annoying to Joe Computer User)
-- taking over the world, we are.
still true after all these years: unix is the system of the future; always has been , always will be untill geeks wake up and smell the coffee: stupid marketing drives sales, not tehcnical chops
I wonder if there is any possiblity that the writer deliberately or accidentally selected distributions that would not work. From the Langa Letter: Linux's Achilles' Heel
Personally, I'm surprised and disapointed re: Suse. However, I'm also a bit surprised that someone who is seriously trying evaluate Linux and get a sound card to work didn't try either Mandrake or Red Hat.
Only Women Bleed (Sex, Sharia remix)
Is that so? I've never seen that happen. But if you try the same on Linux or *BSD, the last program that tried to access /dev/dsp will hang politely while waiting for the first one to let go of the device[1]. That's why most distros will use esd or artsd, both of which are crap, and will occupy /dev/dsp for apps that aren't aware of the sound server. Yes, Linux does suck a bit when it comes to sound, although its capabilities are quite OK. If only all apps and distros would standardise on JACK, it could become great. In my experience it's quite a bit better than for the author of TFA, though. All sound cards I've tried have worked. Seems like he's just bitter because his particular brand is unsupported, and most of the time that is the vendor's fault.
[1]Unless you have a soundcard with hardware mixing supported by ALSA or OSS.
Linux isn't all that great at sound, though the article is complete FUD. I've never had a problem running a Soundblaster card on a Linux machine. They always autodetect fine. And since Soundblaster is about the most common soundcard on the market...
At any rate, I've hardly ever had a linux machine with a soundcard in it. I hardly ever have the GUI enabled. If I want to play games, I use my windoze box...that's what it's there for, to be a toy.
That's what Windows is for. Not to do anything real, or useful. Can't check your email on it, or browse the internet without worrying that its executing code from every damn website, or that its autorunning attachments. Doesn't come with any useful compilers or development tools. The included webserver sucks. Windows is a toy, and it has always been a toy, and the fact that people are looking at a kick-ass powertool and complaining that it's not a toy is absurd.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
This is assuming we give a shit about average mom + pop situations. Personally, I use Linux for development and my servers.
And therein lies the problem - albeit in a very in-elloquent manner, you've highlighted perfectly how linux dev's and advocats simply don't appreciate the problem - and arguablly won't for a few more years to come.
Ok, so we have one guy who couldn't get one un-named sound card to work under Linux. All we know is it's "An utterly mainstream Intel Motherboard". Uhh, yah, thanks for the details so someone can replicate your findings, Fred.
The fact that there's onboard sound, or a soundcard that isn't supported by Linux just isn't too surprising. Why this gets posted as "news", or as "Linux's achilles heal" is beyond me. Is 'ol Fred going to buy a soundcard for his Mac, and then pronounce that lack of support for every soundcard to be the bain of the Macintosh?
I'm actually surprised sound support for Linux is as good as it is. The sound on my laptop worked out of the box when I installed RH9 on it, a first for me! There's also sound support for my N-Force motherboard. Sound support is actually something that's matured quite a bit in the last few years.
I won't say Linux is perfect. There's plenty of things to complain about as far as Linux desktop usage is concerned. My personal complaint is the fact that copy/paste support is still kind of crappy. I can copy/paste between emacs sessions (as long as they remain open), but I can't copy/paste from emacs to somewhere else. That's just pathetic. Windows has supported universal copy/paste since 3.1
AccountKiller
I'm not sure I see the problem. You were the one claiming that Linux will never take over the desktop.
He said 'so what? I don't want it on the desktop'.
So from his perspective, there isn't a problem!
I'd like to point out that it is better to have good, widely available hardware documentation than vendor-provided proprietary drivers.
Not mentioning any names...
Ha! Does Linux have a software mixer, you ask. Linux is much better than that! Linux has numerous software mixers! None of them are compatible with each other, much less any player applications, but you bet there are software mixers around! It's all about choice! Of course, they are all userland programs, so they skip now and then, but that's a small price to pay for ensuring that something so trivial does not offend the great Linux kernel by depriving it of some of its low-latency resources. Such resources are critically important towards providing optimal networking, disk I/O, RAID, and other things that are invisible to the user which he or she clearly does not appreciate enough.
I, being an educated and l33t hacker, know that I would much rather get an extra 5kB/sec on my downloads than be able to listen to two streams of audio at once. You already have two ears, isn't that good enough? Software mixer, pshaw.
Random and weird software I've written.
One shouldn't have to should they?
I personally have never had any problems with sound, but at the same time I amused by all of these comments. Pick one: "He's either dumb" or "He should have checked into before installing linux".
Granted as somebody posted, he did not list his video card, but that does not mean he did not discover some previously unknown bug.
Sig it.
What problem?
Do sports-car enthusiasts think it's a problem that I never learned to drive a standard transmission? Are the going to redesign their cars for me? Of course not.
Tom Swiss | the infamous tms | my blog
You cannot wash away blood with blood
Actually, I can attest, from personal experience, that Linux has better support for legacy cards. I tried to put one of my old sound cards in my mother-in-law's computer. It was an Ensoniq soundscape from 1995. I managed to find some legacy drivers for it on Creative's website, but it just would not work under Windows 98. This card works flawlessly under Linux.
Where Linux tends to have problems is with the latest bleeding edge cards that require some sort of funky drivers. Legacy cards are rarely a problem for it.
This sig has been temporarily disconnected or is no longer in service
Yes, if Linux is going to be the OS for newbies. Yes, if Linux is going to be the OS for the desktop. The users won't care *why* it doesn't work, just *that* it doesn't work.
I know a lot people here on /. plug Linux as the best thing short of the Second Coming...
But... The real issue is that most people don't install their own operating systems. They take what comes on their PC from the factory, and that's it.
That said, the only way in which Linux is going to gain significant ground on the desktop is if:
Linux's big hurdle for the desktop is that for most people, Windows is Good Enough(TM). Any difficulties installing Windows are simply irrelevant because the average user never installs their own OS - when it crashes, they take it back to the store.
For Linux to succeed on the desktop, hardware detection and driver installation is going to have to be completely automatic. A distro which can't autodetect the video card or sound card would do better to inform the user that their hardware is unsupported than ask them to select their hardware from a seemingly endless list of meaningless names.
Linux developers are going to have to stop following Microsoft's lead and start really innovating.
* - yes, I know that many windows apps mangle the system. Let's just ignore this and pretend that they work as advertised for the sake of argument, shall we?
The society for a thought-free internet welcomes you.
He tried it with several distros: Xandros 2.0 Deluxe, two versions of Slackware, two versions of SuSE, Debian, Lindows, Knoppix, Knotix, Morphix, and Gentoo.
"one of the Linux distributions I tried specifically claimed compatibility with the sound system in question"
He didn't like the advice of "get rid of the brand-new, fully functional sound card and install a card from a few years ago, and Linux would work just fine".
The Achilles Heel is "For broad hardware support, Windows is still much better than Linux." It's not "My sucky OEM sound card didn't work."
Yeah, it sucks that he didn't mention the card. It sucks that he didn't try distro X, and that Knoppix couldn't detect it. It sucks that the forums didn't help. It sucks that he didn't try a half-a-dozen things. But, the fact is, a good amount of hardware that works out of the box with Windows won't work with Linux. Every user that trys and gets a bad experience will hold the opinion "Linux Sucks" until they are proved otherwise, years later perhaps.
I think you have a wonderful opportunity to consult with them and educate them about how you could fix this problem for them.
If you care about the Mom&Pop market for Linux, and think there's a problem, you're 100% empowered to do something about it.
It wasn't Achilles' fault that his heel was vulnerable. But it was.
__
Do ya feel happy-go-lucky, punk?
My Sound Blaster Live! worked in Mandrake up until around 2-3 years ago, and hasn't since. I've tried every version of Mandrake for the past 3-4 years, almost all of the Red Hat versions for the same period, and they all fail at installing a Sound Blaster Live (other than Fedora 1.0). I tried "a couple versions of SuSE" too, and I can't name the specific versions, but they failed also.
This was installed in an ASUS Athlon mobo for a few years, and in an Intel P4 mobo lately. Same story with an SBLive at work (Athlon/MSI mobo). Same problem. No crappy hardware, no OEM parts. Always worked in 98, 2K, and XP every time.
Linux usually detects and then ignores it. Or (bonus!) it gives me an irritating high-pitched note at full volume, without anything else working. Sometimes I've been able to figure out the problem, but it's usually so frustrating and with so little utility, I just give up and reboot into XP.
+5:offtopic,but anti-American
I've been a Linux user, pretty much continuously, since 1993. I use it constantly, and have become deeply familiar with Gnome/KDE environments since both were < V1.0. (prior to those I was an fvwm guy, although I'll always hold a soft spot for twm).
/., where the ignorant roam free) by the ostritch-like, "there ain't no problem here" posts that seem to have mushroomed as per usual.
As a server OS, Linux is great. But I'm flabbergasted (hey, this is
They are all wrong.
Sound under linux sucks. Big time. It always has.
If it's not drivers, it's sound daemons. Yes, it's possible to get everything working just fine providing you don't want to use more than one. Mandrake linux is the only distro that works sensibly with sound. And believe you me, I've pretty much tried them all.
So it's piss poor. But as linux is primarily a server OS, what more can we realistically expect? Sound is utterly unnecessary in this capacity, for the most part.
The best unix desktop by a country marathon is Mac OS X. By some considerable margin. Anyone denying this simple fact is kidding themselves. Really.
Read my online journal: http://chris.carline.org
No you miss the point. It is not our goal to wake up to that. You want an app...pay me I will write it for you. Until then either:
a) Write it yourself
b) Wait for someelse to do it.
but for gods sakes man don't expect that we are out to serve your needs.
what?
I completely agree.
//gs had a built-in multi-channel audio sampler, Mac had the desktop publishing and high end graphics market.
Next soundcard i'm going to buy will be by a company that actively supports linux or opens up the specifications: a product that can't work with both the OSs i use is a crippled one.
Linux is progressing in many directions, as the installed base gets bigger more companies will look at it, audio card makers included. The number of linux hackers trying to support exotic soundcards will increase too.
Look at Wintel machines: When the PC came out it won the desktop market by being an office machine first. Amigas had better graphics, apple
Only with the advent of 3D cards and the amiga crisis the pc became also the #1 gamers machine and ubiquitous.
---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
Funny thing the timing of this article. I've been using Linux for quite awhile on my servers and love it. I don't install gui's on them and do everything from the CLI. On my desktop I've been using XP, and as much as I don't want to, I love it as well. I went to the Real World Linux conference in Toronto last week and talked to some of the Xandros guys, and decided I'd dual boot my XP box in the hopes that I could eventually replace XP with a good Linux Desktop.
The install was incredibly easy, and it handled partitioning my HD and installing the MBR with minimal input on my part. That part blew me away, it was easier than installing Windows (any version).
Unfortunately, I had no sound and my printer wouldn't work. I have a Sound Blaster audigy2 card and a Canon I320 printer...both very common and both work flawlessly on XP. After messing around for a couple of hours I got them both to work.
I also use 2 monitors on this box and have a 128M Nvidia GeForce video card. The install handled my video card without any user input and set a decent default screen resolution. Unfortunately again, it would not support the dual monitors. After googling for awhile I discovered Xinerama and reconfigured my XF86Config-4 file to support the dual monitors...which now work as well.
I discussed this with a friend who also wants to see huge adoption of Linux on the desktop. I explained that as much as I was impressed with Xandros it still is IMO not ready for your average computer user. We agreed to disagree on this point, but until you can install a Linux distro without having to drop to the command line to get things working, it's going to be a hard sell to Joe Q Public.
Now I realize that my setup may be a little out of the ordinary compared to regular users and they may not experience any of the problems that I did but the point is this all works out of the box on Windows. I prefer the command line and didn't have that much trouble getting everything working that I wanted too, but you can't expect the average user to put up with it...not when it just works with Windows.
We've still got aways to go but we're definitely getting there.
-Pat
" Yes, if Linux is going to be the OS for newbies. "
It's not. That's what Macs are for.
Linux is going to be for the corporate desktop where the techs will set up a locked down config that can be managed remotely and kept secure.
evil is as evil does
This is assuming we give a shit about average mom + pop situations. Personally, I use Linux for development and my servers. If you want an OS for a mom + pop situation, get Mac OS X.
/really/ doesn't want to teach my dad how to use UNIX. We've had this discussion, believe me.
But you can't have it both ways; you can't say 'Linux will conquer the desktop world' as many people seem to do, and then simultaneously say '...but we don't give a shit about average mom + pop situations.'
Linux as a server environment is great; I run two fairly high-load Linux servers in a colocation center, and -- despite my periodic grumbling about RPM dependency nightmares -- I am more than happy with the performance I get out of them.
But Linux as a desktop environment? I would not want to try and introduce my parents to Linux as a desktop environment in the state any of the current distributions are in. Yah, getting printing working under Linux is certainly doable; install CUPS and the appropriate driver, configure it all, poke at the CUPS internal webserver if you need to check things out, etc. I'm more than willing to take the plunge on that. But I don't want to have to explain CUPS to my parents; they're used to a Windows box where they can go to Best Buy, buy a printer, plug it in, and put in a driver CD. Or the new digicam they just bought; they want to be able to plug the camera into their computer and get their images out into a graphical program where they can e-mail it. They don't want to have to go looking for drivers for digicams for Linux or whatever, they want to just plug it in and put in the CD.
And for another one, let's go into security updates. Sure, Linux (and open source in general) have a much better track record than Windows of fixing security problems! That's great for sysadmins like myself, but it's not going to do a whit of good in some cases; my parents aren't going to want to stay on Bugtraq to discover that their print daemon has a remote-root exploit they'll need to download a patch for and recompile. They're used to Windows Update, where it'll find the critical updates and download them, then prompt them to install. They don't have to worry about it.
This isn't to say 'Linux sux!' or anything like that; I happen to think it's a great UNIX server and dev environment, and am happy with my own Linux boxes. BUT, that notwithstanding, it's not a desktop environment I would like to introduce my father to. The investment in user education is more than I want to get into; my father doesn't want to have to learn about autoconf and make, or patch and diff, or worry about watching Bugtraq or whatever. He just wants to be able to surf the web, print things, and use Word and Excel. And my mother, a former AIX user, would feel at home in Linux userland, but doesn't want to muck about with security fixes and upgrades, and
And my situation isn't completely different than a lot of people's; there are some success stories with teaching parents or relatives enough to encourage Linux adoption, but there are also lots of failure stories. And 'well, I can't use my new digicam because I'm running Debian' is not good sales pitch to other potential Linux users.
If the Linux world is fine with that, then that's great; Linux is great in the server arena, and within that area it does what it does very well. But if Linux wants to take over the desktop world, right now, it's not as approachable as it needs to be in order to be an effective desktop OS for 'mom + pop' situations...and it needs to approach those situations if Linux is to 'conquer the desktop world.' I'd love to see Linux become a solution that I could give to my parents and know they'd be on a stable OS; in the meantime, as you say, the desktop UNIX variant of choice for non-techy end users seems to be MacOS X.
There's my $0.02. (Or more like $0.20, since this post was a little on the long side...)
--Rachel
There are two things that really bother me that make me believe this person flat out fabricated their testing:
1) The system is a brand new, state of the art, Intel system. Windows 95 wouldn't recognize half of the components on the system. It wouldn't recognize the USB, it wouldn't recognize the chipsets, it wouldn't recognize the video, etc.
To get all of this to work, he would have to download drivers from Intel - assuming they're even available (unlikely). If he did download drivers, then that probably included the sound driver - game over.
2) It is inferred that the sound card is very recent technology. That being the case, Microsoft must have been exceedingly good to create drivers 9 years in advance!
It's also worth recognizing that Intel is notorious for making hardware that is dependent on specific Windows functions. We all owe Intel a big thanks for the wonderful WinModem.
LarryD
Bush makes our troops prey...
Windows isn't an OS for newbies either. Regular Joes rely on manufacturers to put toghether systems for them and support them. They don't do it themselves. Why do you think computer stores charge $$$ an hour for service? Why do you think people line up at them and pay for it?
Second, nobody who actually cares about Linux wants it to be an 'OS for newbies'. This is left to the producers of well-supported products who want to target that market.
In Linux, people make money through services. If you want to have your hand held, you're going to have to buy a product from somebody where that kind of support is offered.
Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
oh one more thing...
I think going to 9 different distros hoping one would have the driver is ridiculous.
If there's a driver for it, chances are that either all, or none, of the distros will have it.
Wow, one piece of hardware isn't supported.. It's a shame, but shit happens.. Check it's supported before you buy. Yes all hardware supports Windows, but that's hardly an achievement by Windows, it just shows off the power of monopoly.
True, but the RedHat RPM updaters only work for if you /are/ using an RPM for a package. Speaking as a sysadmin, I often end up having to roll my own installs, and sometimes it can be a pain trying to get RPMs built of stuff. I don't want to build an RPM every time I'm going to tweak an option in my PHP ./configure call, for instance. Similarly, a lot of stuff like drivers (which Windows /does/ check for updates on automatically) is not in RPM, so doesn't get caught by it.
:)
I suppose another way of putting it would be that Linux puts the burden of doing app updates on the packaging tool (which can be a hassle if you install anything under a different packaging tool or whatnot), and Windows puts the burden of doing app updates on the application (with the exception of system-critical updates). Neither's perfect, but if I have to install specialized CUPS drivers or whatever outside of RPM, it's less likely security updates for those will get noticed automatically, since Linux software doesn't tend to do 'new version available' checks itself. Hopefully that clarifies.
As for the rest, you're absolutely right about OOo and other stuff needing to be fleshed out for business desktop use before it can conquer the desktop more fully. I addressed the home-user standpoint because that seems to be where the 'conquer the desktop' argument was being taken in this thread.
--Rachel
In case of hardware drivers:
c) ask your manufacturer to do it.
If they refuse or have no interest, make sure you get compatible hardware/software combination next time. There are many manufacturers that happily support Linux without any pain or needing installation configuration whatsoever. I mean you don't go to a store, purchase a Mac-OS-X-only hardware and software, then complain that it doesn't work on your XP, and form an opinion that XP therefore sucks. Not for that reason at least.
my first tech job (1996) was fixing windows computers with problems, most dealing with the soundcard.
i spent HUNDREDS of hours searching for drivers and changing default settings trying to get soundcards (from turtle beach to via to sound blaster compatible...) working in windows 95. as another poster said, it's not because of windows that these worked (or didn't work) it's because the drivers were well designed (or sucked ass).
it's the manufacturers fault for not providing linux drivers. but we have to remedy the situation by picking up their slack.
that said, i've configured around 8 computers with linux. i never checked the HCL first. and i got the sound to work (even on board sound) to work every time. maybe i'm just lucky but it seems that if you know what you are doing you'll get it to work. i didn't say it's easy.
fear is the mind killer
Here on Slashdot. Oh wait! I see your point now...
I know a lot more about linux than my mother and I think I know how and where to look for information. I'd have more difficulty figuring out the compatibility of hardware on linux than I would on windows. When I can't find a compatibility information for windows for some arcane webcam a friend owns, I fault the manufacturer for not supplying adequate information. But I would be able to say from their website that the webcam would work with what the manufacturer supplies with its product, because I've been able to before with many other products. All the relevant information I get is from a single, logical site. The MS site doesn't come into it, because the power of MS has pretty much ensured that manufacturers tell us whether and how they're compatible.
Check it's supported before you buy.
If the webcam was brand new, I would look at the box. If there's an XP logo I know it will work, without a doubt. No testing required. No searching required. Me not being the shopping type, I find the box info on the product page. I expect it there and it is in almost all cases.
Some manufacturers don't support their products well at all, then I'm down to OEM hunting or mailing them a complaint; again no MS involvement. Manufacturer's fault. I wouldn't expect my mother to know what OEM stands for, let alone know how to find it. I steer her away from habitually getting poorly supported products, because she's about 20,000km away from me. She's constantly on the lookout for a techie in her area to help her when she gets something unsupported... (but that's another story).
Lets take a look at a webcam driver for linux. First place I'd look: the manufacturer's site. beforehand I might sift through the CD that it came with in some vague hope. In most cases it will be no more than one drivers if anything. Often there won't be any support or information pages on compatibility (let alone useability). Where to now? I don't instinctively fault the manufacturer for not having it. Why? Because for I'm not really expecting a driver from them. Who's forcing them to? Why would they bother?
I now must go to google and from there to the webcam linux module site(s) and a myriad of messageboards, newsgroups and howto pages. I don't expect an answer from anywhere that doesn't include "you'll need to recompile your kernel" by someone in jest or otherwise or something along the lines of "we haven't been able to test this yet, but it works with XYZ, so it should work with your device".
There's no single way of dealing with peripheral support on linux. There is on windows. MS made sure of that. Who's making sure that people can expect without chance that a driver exists for linux when they get something out of the box?
Wow, one piece of hardware isn't supported.. It's a shame, but shit happens..
It's not simply one piece. You've got blinders on if you don't see the bigger picture. A printer here, a sound card there are just the tip of the iceberg. Take any random less-prevalent USB device. Can you say by only checking the manufacturer's site if it will work on linux?
Yes all hardware supports Windows, but that's hardly an achievement by Windows, it just shows off the power of monopoly.
Power brings with it the ability to have an impact and achieve something. I wish linux had the power to achieve half the of the things MS has in the peripherals market.
click-clack, front and back. I'm not moving this car otherwise.
From Fred Langa's article:
I couldn't get XYZ to work with my sound card at all, even though I was testing XYZ on a brand new PC from a major vendor. The system was based on an utterly mainstream Intel motherboard with an on-board Intel sound system. This isn't some weird, off-brand system using unknown components: It's about as mainstream as it gets.
Wrong. No onboard sound chips are standard, and some are as impossible to work with as "winmodems", possibly for the same reason. Their configuration details are often proprietary secrets, and I expect that at least some of them are doing nasty background stuff with the CPU.
Linux does work with any Sound-Blaster compatible sound card.
How do I know these things?
I volunteer as a Build Instructor at a computer recycler (Free Geek, in Portland, OR). I assist newbies in learning the fine art of skimming the garbage flows for re-useable components, putting those together to make working PCs, and installing a variant of Debian on top of it all. Some of the results go to non-profit organizations but many go to the volunteers as reward for their services. Donate 24 hours to busting up recycled computers into steel, aluminum, and plastic bins and you get to take a Freekbox home (233 MHz, 96 MB ram, 4.5 GB HD, 15" monitor, speakers, CD player: all stuff that isn't going to the dump).
I have sometimes been able to get on board Crystal sound chips to work under Linux, though usually it means fussing with configuration settings. I have never been able to get a Yamaha sound chip to work and I have never heard of anyone who has. When we can't get the onboard sound to work, we disable it in BIOS and drop in a 16 bit sound card. We sell used ones that work just fine from our store for $2.00 for anyone who is doing this at home.
Fred Langa needs to look at appropriate technology resources when he ventures from the world of marketdroids into things Linux.
What he didn't reveal clearly enough is that the damn card does NOT work in Windows 95 or 98 as he claims it does. It only does so through a virtual machine that provides an emulated hardware layer.
His point is thus moot and shown for what it really is: FUD. Big, stinking, FUD of the worst kind.
Couple this with the fact that he does not give out the chipset model of the built-in sound card and I do not believe a word he wrote and neither should you.
Pragmatism as an ideology is not particularly pragmatic in the long term. Keep it in mind when you dismiss Free Software