Re: Intel-536ep modem on Suse 9.3
- From: Kevin Nathan <knathan@xxxxxxxxxxxxx>
- Date: Thu, 31 Aug 2006 21:27:45 -0700
On Thu, 31 Aug 2006 15:28:59 -0700
arthur <trash.all.spam@xxxxxxxx> wrote:
I am truly very Sorry.
Apology accepted! :-)
You obviously were trying to help that user.
But I *still* have my moments when I can't resist zinging someone!
The problem still exists wrt to the Intel modems which has been fixed
by the Linspire (non Enterprise marketeers) people via Debian ...
With time, most items get supported. I've never been a fan of internal
modems since the first time I had one (late DOS, early Win3.x if
memory serves). Whenever it got 'locked', I had to reboot the whole damn
computer just to reset it. It lasted about three weeks and then I
bought an external. I've not used an internal since and don't even try
to set 'em up on other people's computers. If they want to use them,
it's their responsibility -- if they want an external, I'll gladly help
them . . . but that's just me.
Is it any wonder that the h/w market is not motivated to spend their
lives keeping up with Linux s/w changes affecting their product?
nVidia is doing a fine job and there are others, as well. Windows
doesn't have this solved, either. Why do there have to be driver
versions for each of the Windows versions on their driver CDs? I just
installed a driver for a client with a new printer and the driver CD
had separate directories for all versions of Windows from 9x on (and
the XP driver didn't work, had to download a different one). Doesn't
exactly sound like Windows design is all that great, either.
This will be a problem with *any* OS. At some point, regardless of how
high-level the API is, it has to get down to the bits and bytes and
chips and flip-flops and any changes between that lowest level and all
the intervening higher levels.
From your previous msg: "The real blame is the Linux design vs the MS
design afa hardware drivers are concerned." I have to take a little
exception to this -- I've had better luck using older drivers on Linux
than I have on Windows; not always, mind you, but more often IME. Yours
may be different, but for me this has been shown on many hundreds of
computers over the last ten years of my experience.
And, my last point, is that I don't buy hardware that is not supported
under Linux. I also wouldn't buy hardware not supported under Windows,
if I still used Windows -- and they *do* exist. What I find
particularly interesting about this, is when one doesn't work on
Windows, even with the manufacturer's CD, the hardware often works on
Linux, without a driver CD. I've seen this with a few cameras and a
recent printer (generic) in just the last few months.
My most memorable one was several years ago, when the client had to
upgrade from 98 to XP because the camera he just bought wasn't
supported under versions prior to XP. After upgrading (and having to
lose a few programs that wouldn't run on XP) the camera *still* didn't
work. The drivers were installed/un-installed several times, by several
techs; in all cases, when the camera was plugged in it rebooted XP.
Just for grins, I took it to my Linux box at work (Mandrake 9.x back
then) and plugged it in and a window popped up with the camer's
pictures in it. Go figger . . . ;-)
--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- http://www.project54.com/linux/
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.13-15.11-default
9:00pm up 24 days 22:16, 13 users, load average: 0.03, 0.17, 0.32
.
- Follow-Ups:
- Re: Intel-536ep modem on Suse 9.3
- From: arthur
- Re: Intel-536ep modem on Suse 9.3
- From: akar
- Re: Intel-536ep modem on Suse 9.3
- References:
- Re: Intel-536ep modem on Suse 9.3
- From: arthur
- Re: Intel-536ep modem on Suse 9.3
- Prev by Date: Re: Should we upgrade from 10.0 to 10.1
- Next by Date: Re: reset network config
- Previous by thread: Re: Intel-536ep modem on Suse 9.3
- Next by thread: Re: Intel-536ep modem on Suse 9.3
- Index(es):
Relevant Pages
|
