Linux-Hardware Digest #611, Volume #10 Mon, 28 Jun 99 01:13:31 EDT
Contents:
Microtek Scanmaker 35t+ (henk van der knaap)
Re: Windows easy to install? BULLSHIT! (Brian Hartman)
Re: support for Lexmark Optra E+ (Mike Simos)
Re: Windows easy to install? BULLSHIT! (Brian Hartman)
Re: Cyrix MII MediaGX all-in-one mobo (Michael Wellman)
Hardware list ("Yankee")
=?iso-2022-jp?B?UEM5OBskQiEjGyhC?= (Sean Manning)
Re: Linux printer recommendations? ("Bret Berger")
----------------------------------------------------------------------------
From: henk van der knaap <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Microtek Scanmaker 35t+
Date: Mon, 28 Jun 1999 15:43:07 +1200
Hi,
I have been trying to a Microtek ScanMaker 35t+ to work with the SANE
package. So far I have had no luck.
Is there anybody who has had any luck using the Scanmaker 35t+ with SANE
under Linux.
Here is the debugging information:
Script started on Sat Jun 26 17:49:23 1999
henk:~$ find-scanner
# You may want to run this program as super-user to find all devices.
# Once you found the scanner devices, be sure to adjust access
# permissions as necessary.
find-scanner: found scanner "Microtek ScanMaker 35t+ 1.40" at device=20
/dev/scanner
find-scanner: found scanner "Microtek ScanMaker 35t+ 1.40" at device /dev/s=
g0
find-scanner: found scanner "Microtek ScanMaker 35t+ 1.40" at device /dev/s=
ga
henk:~$ scanimage Scanmaker 35t+ 1.40:/dev/scanner =20
[sanei_init_debug]: Setting debug level of microtek to 128.
[microtek] sane_init: MICROTEK says hello! (v0.9)
[microtek] sane_init: config- #Uncomment following line to disable "
clever precalibration" routines...
[microtek] sane_init: config- #noprecal
[microtek] sane_init: config- scsi * * Scanner
[microtek] attach_scanner: /dev/sga
[microtek] attach_scanner: opening /dev/sga
[microtek] attach_scanner: sending INQUIRY
[microtek] id_microtek...
[microtek] id_microtek: not microtek: -32, -45, 98
[microtek] attach_scanner: device doesn't look like a Microtek scanner.
[microtek] dump_suspect_inquiry...
=3D=3D=3D SANE/Microtek backend v0.9 =3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Scanner Inquiry Block =3D=3D=3D=3D=3D=3D=3D=
=3Dmm
06 31 19 01 5b 00 00 00 4d 69 63 72 6f 74 65 6b=20
53 63 61 6e 4d 61 6b 65 72 20 33 35 74 2b 20 20=20
31 2e 34 30 53 43 53 49 20 46 2f 57 56 33 2e 34=20
20 43 54 4c 35 33 38 30 03 ef 8c c2 80 ec 62 23=20
01 03 23 01 00 83 00 01 0e 0e 01 05 00 00 00 00=20
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Scanner Inquiry Report =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
=3D=3D=3D=3D=3D Scanner ID...
Device Type Code: 0x06
Model Code: 0x62
Vendor Name: 'Microtek' Model Name: 'ScanMaker 35t+ '
Firmware Rev: '1.40=C4'
SCSI F/W version: 3.1 Scanner F/W version: 1.9
Response data format: 0x01
[microtek] sane_init: config- /dev/scanner
[microtek] attach_scanner: /dev/scanner
[microtek] attach_scanner: opening /dev/scanner
[microtek] attach_scanner: sending INQUIRY
[microtek] id_microtek...
[microtek] id_microtek: not microtek: -32, -45, 98
[microtek] attach_scanner: device doesn't look like a Microtek scanner.
[microtek] dump_suspect_inquiry...
=3D=3D=3D SANE/Microtek backend v0.9 =3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Scanner Inquiry Block =3D=3D=3D=3D=3D=3D=3D=
=3Dmm
06 31 19 01 5b 00 00 00 4d 69 63 72 6f 74 65 6b=20
53 63 61 6e 4d 61 6b 65 72 20 33 35 74 2b 20 20=20
31 2e 34 30 53 43 53 49 20 46 2f 57 56 33 2e 34=20
20 43 54 4c 35 33 38 30 03 ef 8c c2 80 ec 62 23=20
01 03 23 01 00 83 00 01 0e 0e 01 05 00 00 00 00=20
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Scanner Inquiry Report =3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
=3D=3D=3D=3D=3D Scanner ID...
Device Type Code: 0x06
Model Code: 0x62
Vendor Name: 'Microtek' Model Name: 'ScanMaker 35t+ '
Firmware Rev: '1.40'
SCSI F/W version: 3.1 Scanner F/W version: 1.9
Response data format: 0x01
[microtek] sane_get_devices
scanimage: sane_start: Invalid argument
[microtek] sane_exit...
[microtek] sane_exit: MICROTEK says goodbye.
Here is some output from mtekscan:=20
Script started on Sat Jun 26 17:59:27 1999
henk:~$ mtekscan -I
Vendor/model: Microtek ScanMaker 35t+ =20
Firmware revision no. 1.40, device type 06.
SCSI firmware version: 3.1, scanner firmware version: 9.9
Response data format: 0x01
Resolution selection stepsize: 1% 5%=20
Supported scanning modes: Lineart Halftone Multi-Bit Color Transparencies=
=20
Negative
One-pass color scanning supported
12 built-in halftone patterns, pattern downloading supported
Scanner is edge feed type
Huffman data compression: no, Read data compression: no
Frame & paper length setting units: 1/8" pixels=20
Max. document size code is 0x80 - 35.00 x 35.00 mm
14 contrast settings, 12 exposure time settings
Model code : 0x62 (unknown model code)
F/W does support document feeder,
F/W does support feeder/backtracking enable/disable
Feeder is not installed=20
Type / Location code is unknown (0x02)
Transparency illuminator is not installed
Expanded resolution range: yes
Shadow/highlight adjustment supported, midtone adjustment supported
Gamma adjustment look-up table size: 1024 bytes
Max. value: 1023 (entry length 2 bytes)
Fast color prescan supported, data transfer format select not supported
Color data sequencing: Line by line, non-R-G-B sequence, with data headers
Three pass scanning supported
MODE SELECT 1 and MODE SENSE 1 command supported
cntr_vals =3D 14, min_cntr =3D -42, max_cntr =3D 49
exp_vals =3D 14, min_exp =3D -18, max_exp =3D 21
Supported multi-bit data formats: 4 bpp 8 bpp =20
Offset adjustment (digital brightness control) supported
Linearization table can not be disabled
Start-of-scan recalibration function can be disabled
henk:~$ mtekscan -S
mtekscan: Performing scanner selftest...
mtekscan: Selftest result code 0x00 (no failures).
henk:~$ exit
exit
Script done on Sat Jun 26 18:00:12 1999
I would be gratefull if anybody could make some comments please.=20
Greetings
Henk
Henk van der Knaap,
92 Halswell Junction Road,
Christchurch, New Zealand.
Phone/fax 64 3 3229185
My Operating system is Linux Debian 2.1
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
My e-mail address is as follows: [EMAIL PROTECTED]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
------------------------------
From: Brian Hartman <[EMAIL PROTECTED]>
Subject: Re: Windows easy to install? BULLSHIT!
Date: Sun, 27 Jun 1999 23:36:07 -0400
Shashank wrote:
> > You're leaving out a lot of steps in the kernel compilation process here. As per
> > the official documentation, here are the steps for a new kernel install:
>
> Actually, it _is_ really that simple for any current distro. Even if you're
>patching-
> 1. get the patch and unpack it
> 2. patch < _____
> 3. make mrproper
> 4. make dep clean zlilo modules modules_install
> 5. shutdown -r now
>
That's for a patch. Not the full kernel upgrade process. I refer you to either the
Redhat official howto or to http://www.computergallery.com/redhat/kernel.shtml It's
possible other distros have simpler processes, I suppose, but the process you outline
above
will not, for example, copy the system map and boot image to the right place, won't
rebuild
the symlinks, etc.
>
> This contrasts to Service Packs (or whatever they are) for Win95, where they are much
> easier to apply, almost impossible to undo. Call it a draw.
>
Well, given that at least one of the Service Packs (2, I believe) is actually
distructive,
I'll give you that uninstalling it should be easier.
>
> > > > 4. Once the CD can be accessed, type setup at the prompt. Pray that it does
> > > > not crash.
> >
> > Crashing on setup? Please....
>
> This happens to me all the time. In fact, I wouldn't even mind re-installing Windows
>so
> often if I wouldn't get freakin BSOD.
>
I've never had that happen, and I've installed 95 numerous times (because, as you
correctly
point out, it's not stable). Perhaps this is a hardware problem on your end, or
simply a
problem introduced in 98.
>
> > > > My first linux install went like this:
> > > > 1. Place CD in drive, turn on.
> >
> > That works fine as long as your CD-ROM drive is recognized. Unfortunately, that's
>a
> > rather large "if". Mine wasn't.
>
> This was a problem in windows for me, actually. There's something stupid with my
>cdrom
> (one of those crappy Plextors) where it specifically doesn't boot off of the Windows
>95
> cdrom (I have tested this out). In linux- cake. Read a README (inconvenient maybe,
>but
> at least it was there, re my Win95 problems), type rawrite, then the three finger
> salute.
>
Well, actually I read the readme. It was the readme that lead me astray in the first
place. Fortunately, when I installed the new kernel, I was able to fix it to
recognize my
CD-ROM on bootup, so it will be less of an issue if I decide to upgrade to the next
Redhat
version.
>
> > 1) Find out if your CMOS supports bootable CD-ROMs.
> > 2) Reboot several times wondering why your CMOS says it supports it, but it's not
> > happening.
>
> > 3) Copy your CD onto your hard drive.
> > 4) Run fips to shrink the partition your install files are on so that you can
> > install Linux.
>
> I did all this with Windows too! (well, I wish I could have done step 3)
>
Actually, I think my BIOS might be at fault. My understanding is there are AMI
BIOS "clones" out there, and I might have one. That might explain why my CMOS says I
can
boot from the CD. But it doesn't mitigate the fact that Linux distros ought to come
with
bootable floppies rather than relying on bootable CD-ROMs (which are only supported on
newer machines).
>
> > 10) Run Disk Druid. Create the new partitions. Wait for the new partitions to be
> > checked and formatted.
>
> Yep- had to do that for windows (sensitive data was on /dev/hda1)
>
The install that I did (admittedly, in NT and not 98) did not ask for any partition
information, etc, and did not require anything of the kind. What drive do you want the
information on? Ok, done. It certainly didn't ask you to designate swap partitions or
files or even directories (other than the Windows directory).
>
> > 13) Decide if you want Xconfigurator to probe for a card.
> > 13a) If you let Xconfigurator probe for a card, pray it doesn't hang.
> > 13b) If you choose not to let Xconfigurator probe for a card, I hope you have your
> > memory and chipset information handy.
> > 14) Accept the default settings. Hope that your display is ok from the default.
> > 14a) If not, repeat steps 12 -14.
> > 14b) If everything's ok, reboot.
> >
>
> Yep- same for me in Windows 95.
>
The process in 95 is different in the sense that 95 allows you to use "standard SVGA"
which
works with pretty much anything. (Well, anything that was manufactured after SVGA came
into being). And 95 doesn't confuse the issue with asking for chipsets or memory
(both of
which will report errors to Xconfigurator if they're wrong).
>
> So, by my count, I think about four steps you had in Linux I did not have with
>Windows.
> And I had watermelon sized problems with my three serial devices in Windows that I
> hadn't batted an eyelash about in Linux. I have no desire to jump down your throat
>about
> Linux>Win95, but you have to admit, Linux is definately getting there. Very nearly a
> draw.
>
Nearly, perhaps. I still think Linux requires you to know things you don't need to
know in
Windows to install it, though. And Linux's well-documented lack of hardware drivers
mean
you're more likely to have installation problems with Linux.
>
> > I've heard horror stories like this, and I can't help thinking there's just a
>little
> > bit of hyperbole involved. First of all, I've talked to many people who never have
> > a problem Win 98. And I do mean *never*. I had some problems with 95, and that's
> > why I dumped it, but I've heard (even from the Linux guru who convinced me to
> > install Linux on my machine) that 98 is relatively stable. As far as doing a
> > complete reinstall, I only did a *complete* reinstall once or twice in 95. Most of
> > the time, the fixes I did were more along the lines of installing 95 over itself to
> > fix something that broke.
>
> This is very different from my experiences 'sys-admining' in two research labs. Our
> reinstall rate was about one installation every three months or so (four machines-
>two
> gave problems every time, two were as simple as inserting the CD). These were abused
>by
> a lot of people of differing ability. Liunx was a godsend- permissions, baby.
>
Well, that's a potential difference. My machine is basically *my* machine, and the
other
people I talked to were in similar circumstances. I'll definitely grant you that a
Linux
machine is easier to secure from know-nothings. There's still the policy editor in
Windows, though.
>
> > Netscape crashing once or twice a day is still a little much, don't you think?
> > (Although I have noticed a problem with Netscape for Linux and certain pages. In
> > Windows, I would simply get an error if a page wasn't coded right. In Linux, if
> > Netscape comes across a page it doesn't like, it just shuts down.)
>
> I'll agree with this, actually. But Netscape has never caused neither X nor the
>kernel
> to hang. My Netscape (4.07 I think) takes Windows down once or twice a week (I've
>been
> running for two weeks now). Draw.
>
I stayed away from the 4.0x Netscapes once 4.5 came out. If you still have some
vestige of
Windows on your machine, I suggest you switch. Draw. :)
>
> > The only qualm I have with Linux apps in general is that they are sometimes
> > difficult to install. As far as the pricing goes, you can't beat it, but you
>suffer
> > in terms of support, because the people writing the programs have nothing at stake
> > if you can't get it to work. I think what needs to happen is the big companies
>need
> > to release low-cost versions of their software for Linux. That way there's a big
> > support system with some stake in actually pleasing the customer.
>
> This is somewhat of a misnomer. Their is a big Windows support network if you have
>money
> to give them (Microsoft has personally told me regarding our computers that we would
>be
> best getting a service contract). I have only gotten support for Windows when I lie
>to
> some company like Gateway. But there is much more help available for the little guy
>in
> Linux. Documentation abounds. USENET. etc. Score depends on who you are.
>
> s
The only disagreement I have with you here is that the sources of Windows help abound.
Besides having it's own Usenet groups, Windows also enjoys much wider press coverage,
and
companies support Windows much more fully on their websites. For example, if you just
got
that new printer, but you can't remember where you put the drivers disk, chances are
you
can download it from the company's website. You can't usually do that with Linux. And
company FAQ's don't generally address Linux problems.
------------------------------
From: Mike Simos <[EMAIL PROTECTED]>
Subject: Re: support for Lexmark Optra E+
Date: Mon, 28 Jun 1999 03:43:00 GMT
Leung Hok Tsan wrote:
>
> Do Lexmark Optra E+ support in Redhat Linux 6.0?
>
I have an Optra R in the office, and it seems to be compatible with the
HP LaserJet input filter. I suspect you should have the same results.
Mike
------------------------------
From: Brian Hartman <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.advocacy,comp.os.linux.setup
Subject: Re: Windows easy to install? BULLSHIT!
Date: Sun, 27 Jun 1999 23:42:40 -0400
Rowan Hughes wrote:
> In article <7kr35m$egk$[EMAIL PROTECTED]>, Michal Jaegermann wrote:
> >I have to be one of those "unlucky" people which run into problems
> >with Windows all the time. Karma - I guess.
>
> Not karma, it's just a crap O/S for this day and age. I like to compare
> repairing a Windows installation to a surgeon repairing some vain silly
> woman's hymen. It's a very difficult and delicate operation with little
> chance of of success. Even if you do get it repaired the damn thing's
> broken again five minutes later.
>
Colorful analogy. ;) I somewhat agree with you about the frustration in
repairing Windows over and over. (Luckily, I've only had to reinstall NT
around 3 times since I had it, which is what I'm up to in Linux). The fly
in the ointment is that once you've built a system around Windows (be it
NT or 95/98) it's difficult to move to a different OS and make everything
work. Things you've always assumed would work (be it a printer or a modem
or whatever) because they're tied to Windows won't necessarily work, and
the hardware companies that sell these things don't necessarily say that
they're only for Windows. They just give you the drivers and let you go on
your merry way. When I got my 820Cse, I assumed that the drivers installed
Windows utilities, but that the printer itself would work with any OS.
After all, it's just a printer, right? Accept data from the parallel port
- spit it out. Ah, if life were that simple ....
>
> --
> =======================================================
> Dr Rowan Hughes [EMAIL PROTECTED]
> Qld Dept Natural Resources Forestry Bldg, 4.06
> CIS group, Indooroopilly. W:07-38969705 H:07-38768083
> "where did you think you want to go to today?"
------------------------------
From: Michael Wellman <[EMAIL PROTECTED]>
Subject: Re: Cyrix MII MediaGX all-in-one mobo
Date: Mon, 28 Jun 1999 03:31:39 GMT
I forgot where I read this but I heard that you can reasonably expect=20=
everything to work on the 'all inclusive' MediaGX system except video=20=
above vga.=20
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/26/99, 10:40:21 AM, Greg H <[EMAIL PROTECTED]> wrote=20
regarding Cyrix MII MediaGX all-in-one mobo:
> There's an ad in the MicroWarehouse catalog (as is in others, I am =
sure)
> for an all-in-one motherboard with a Cyrix MII/MediaGX chipset. One=20=
runs
> at 200 MHz and the other at 233 Mhz. The price is arund $200. It has=
> integrated video and sound, and a couple of expansion slots. I hope=20=
this
> description helps to identify what I am talking about, because I don't=
=20
know
> the name of the entire item nor any identifying numbers.
> Anyway, my wife has an IBM PS/1 running at 25 MHz. I am=20
considering
> replacing its motherboard with the one I mentioned above as an=20
inexpensive
> way to put off buying a new system for her, which we really can't=20
afford
> anytime soon. I'm wondering first whether this replacement will work =
at
> all, but I would also like to know if Linux will run with this=20
motherboard.
> Anyone know or who have done this themselves?
> I apologize if this post lacks additonal needed information. Let=20=
me
> know by follow-up and I will provide it if I can.
> Thanks in advance!
> Greg H.
------------------------------
From: "Yankee" <[EMAIL PROTECTED]>
Subject: Hardware list
Date: Mon, 28 Jun 1999 03:53:38 GMT
Hi,
I'm buying a new system and was wondering if there was a website that listed
all current companies writing linux drives for there devices. If not can
anyone suggest companies to avoid?
Green Linux User
------------------------------
From: Sean Manning <[EMAIL PROTECTED]>
Subject: =?iso-2022-jp?B?UEM5OBskQiEjGyhC?=
Date: 28 Jun 1999 03:54:34 GMT
Reply-To: [EMAIL PROTECTED]
PC98でLinuxをInstallできますか？
------------------------------
From: "Bret Berger" <[EMAIL PROTECTED]>
Subject: Re: Linux printer recommendations?
Date: Sun, 27 Jun 1999 22:30:00 -0600
I've had good luck with reconditioned Okidata page printers. Just purchased
a OkiPage 6e for $179+$25 shipping from Electrified Discounters a few months
ago. The 600 dpi output under ghostscript from Win98, Macintosh, and Linux
clients looks great to my eyes. http://www.electrified.com/
-bret
[EMAIL PROTECTED]
David Graham wrote in message <[EMAIL PROTECTED]>...
>I see good, reconditioned HP LaserJet II/IIIs at computer shows
>regularly, for less than $280. They're built like tanks and, for light
>(home) use, will likely run forever.
>
>David Graham
>--
>>
>> I need a fast, functional, and cheap laser that will work under linux. I
>> was looking into a $280 Xerox P8, but i cant tell if it is only a windows
>> compatible. Please help. Any other printer recommendations would be
>> helpful. (Please reply to my email, since I can never get to the good
>> responses in time) Thanks,
>>
>
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
