Linux-Hardware Digest #79, Volume #14 Sat, 23 Dec 00 12:13:02 EST
Contents:
minor problem with blinking light (HP 2100 M) (Faheem Mitha)
Re: dying courier modem? (CBFalconer)
Re: ??? RH7.0 on a Pentium Pro 200 (Chris Elvidge)
Re: SCSI Controller not recognized by Linux? (Chris Elvidge)
Re: [Need Help]: LS-120 Drive (Chris Elvidge)
about battery driver source ("alan")
Re: Dual Xeon hangs (Ralph Wesseling)
Re: dying courier modem? ("Hooda Gest")
pinouts wanted ("Nicola Asuni")
Cannot print in Redhat 7 ("Jess Jackson")
Re: SCSI ADAPTER 1505 (Gotzon Berrojalbiz)
Re: Wheel mouse works - if... (Frank Hahn)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Faheem Mitha)
Subject: minor problem with blinking light (HP 2100 M)
Date: Sat, 23 Dec 2000 07:15:31 -0000
Dear people,
I recently purchased the HP 2100M. Rather to my surprise, I got it
printing under Linux right away. I am currently using SuSE 6.2, and
using YAST I configured printing with apsfilter in a couple of
minutes. This was of course much helped by the fact that the 2100M is
a Postscript printer.
In any case, the only thing that seems not quite right is as
follows. When I send a job to the printer, an indicator light starts
blinking. However, once the job is finished, it continues blinking for
quite a while, though it does eventually stop. I tested it under
Windows, and there it stops more or less right away.
While this is not a real problem (the printing itself is fine) it is
mildly annoying. Does anyone have any idea how I could stop this?
The relevant portion of the printcap information follows.
Thanks in advance.
Sincerely, Faheem Mitha.
### BEGIN apsfilter: ### PS_1200dpi letter mono 1200 ###
# Warning: Configured for apsfilter, do not edit the labels!
# apsfilter setup Wed Dec 20 23:12:47 EST 2000
#
ascii|lp1|PS_1200dpi-letter-ascii-mono-1200|PS_1200dpi letter ascii mono 1200:\
:lp=/dev/lp0:\
:sd=/var/spool/lpd/PS_1200dpi-letter-ascii-mono-1200:\
:lf=/var/spool/lpd/PS_1200dpi-letter-ascii-mono-1200/log:\
:af=/var/spool/lpd/PS_1200dpi-letter-ascii-mono-1200/acct:\
:if=/var/lib/apsfilter/bin/PS_1200dpi-letter-ascii-mono-1200:\
:la@:mx#0:\
:tr=:cl:sh:sf:
#
lp|lp2|PS_1200dpi-letter-auto-mono-1200|PS_1200dpi letter auto mono 1200:\
:lp=/dev/lp0:\
:sd=/var/spool/lpd/PS_1200dpi-letter-auto-mono-1200:\
:lf=/var/spool/lpd/PS_1200dpi-letter-auto-mono-1200/log:\
:af=/var/spool/lpd/PS_1200dpi-letter-auto-mono-1200/acct:\
:if=/var/lib/apsfilter/bin/PS_1200dpi-letter-auto-mono-1200:\
:la@:mx#0:\
:tr=:cl:sh:sf:
#
raw|lp3|PS_1200dpi-letter-raw|PS_1200dpi letter raw:\
:lp=/dev/lp0:\
:sd=/var/spool/lpd/PS_1200dpi-letter-raw:\
:lf=/var/spool/lpd/PS_1200dpi-letter-raw/log:\
:af=/var/spool/lpd/PS_1200dpi-letter-raw/acct:\
:if=/var/lib/apsfilter/bin/PS_1200dpi-letter-raw:\
:la@:mx#0:\
:tr=:cl:sh:sf:
#
### END apsfilter: ### PS_1200dpi letter mono 1200 ###
------------------------------
From: CBFalconer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Date: Sat, 23 Dec 2000 07:18:25 GMT
Hooda Gest wrote:
>
> "Matt Garman" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > On Fri, 22 Dec 2000 08:26:39 -0500, Hooda Gest <[EMAIL PROTECTED]> wrote:
> > > I would contact USR regarding this. It may be a problem with some
> component
> > > and that could be affecting the ability of the modem to handle the line
> > > quality properly. It could be repairable. You also might check your
> > > electrical grounding, sometimes this can have an adverse effect. Another
> > > thing to check, assuming the modem is an external, is where the modem is
> > > placed. Putting it on top of your monitor or the computer's case is not
> > > recommended.
> >
> > Yup, I sent USR a tech support email asking them about this. I'm guessing
> > a response might take a while with the holiday weekend upon us.
>
> Sorry, emailing tech support is a waste of time in most cases. Better to
> dial them up since it is toll free in the US (I am assuming you are in the
> US). Much faster response :) and much more productive.
I have been lurking on this thread for a bit, and it occurs to me
that most modems have a configuration value for hanging up on a
carrier break. My USR must be set fairly high, because my wife
can pick up the phone while I am on it and I don't lose the
connection. In the old days the break period was fixed at
something like 10 millisecs, so anything would drop the line.
It is one of the S register settings.
--
Chuck F ([EMAIL PROTECTED])
([EMAIL PROTECTED])
http://www.qwikpages.com/backstreets/cbfalconer
(Remove "NOSPAM." from reply address. my-deja works unmodified)
mailto:[EMAIL PROTECTED] (for spambots to harvest)
------------------------------
From: Chris Elvidge <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,linux.redhat
Subject: Re: ??? RH7.0 on a Pentium Pro 200
Date: Sat, 23 Dec 2000 11:42:12 +0400
mike marois wrote:
>
> I just purchased a pentium pro 200 with 256mb of ram to be the SOHO server
> to act as a file server, intranet, and gateway in my 4 pc home office
> network. Are there any know problems with this seemly old technology? Will
> RH7.0 see and utilixe all 256mb of RAM? Is expecting this box to handle all
> of this too much??
>
> A recent MS convert!
Where did you get a PPro 200? I need another, pref. Compaq but I'll try
anything!
Thanks,
Chris.
------------------------------
From: Chris Elvidge <[EMAIL PROTECTED]>
Subject: Re: SCSI Controller not recognized by Linux?
Date: Sat, 23 Dec 2000 13:01:06 +0400
Look for a file called rc.modules (well it is under Slack) and uncomment
the /sbin/modprobe aic7xxx line.
Chris
[EMAIL PROTECTED] wrote:
>
> Pizza et al:
> Thanks for the info. I was able to get the machine to recognize the
> SCSI drive using the /sbin/modprobe command. Afterwards, I checked the
> "/etc/conf.modules" file for the "alias scsi_hostadapter aic7xxx"
> line. The "alias scsi_hostadapter aic7xxx" line was already in my
> /etc/conf.modules file. Each time I reboot I am forced to issue the
> /sbin/modprobe command in order for the machine to recognize my SCSI
> card and Jaz drive. It seems like I am missing something to get the
> machine to automatically recognize the SCSI card at boot up. Any help
> is greatly appreciated.
>
> Thanks-
> Rodney
>
> In article <918q4s$qk4$[EMAIL PROTECTED]>,
> Stuffed Crust <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] blatt:
> > > I am having considerable trouble configuring the Adaptec 2930U SCSI
> card
> > > (along with Jaz drive) on my Redhat 6.2 System. I have completed
> the
> > > physical installation and it is my belief that everything has been
> > > completed correctly.
> >
> > does "modprobe aic7xxx" give you anything?
> >
> > If it does, add "alias scsi_hostadapter aic7xxx" to /etc/conf.modules
> >
> > > Linux version 2.2.14-5.0 ([EMAIL PROTECTED]) (gcc version
> > > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Mar 7
> 20:53:41
> >
> > And upgrade the kernel to at least 2.2.16; there be nasty security
> > problems with this one.
> >
> > - Pizza
> > --
> > Solomon Peachy
> pizzaATfucktheusers.org
> > I ain't broke, but I'm badly bent.
> > Patience comes to those who wait.
> > ...It's not "Beanbag Love", it's a "Transanimate Relationship"...
> >
>
> Sent via Deja.com
> http://www.deja.com/
------------------------------
From: Chris Elvidge <[EMAIL PROTECTED]>
Subject: Re: [Need Help]: LS-120 Drive
Date: Sat, 23 Dec 2000 13:12:58 +0400
Young4ert wrote:
>
> Hi,
>
> I have a MATSHITA Model: LS-120 VER5.00 Rev: F523 drive installed on my
> SuSE-7.0 Linux distro with the Linux-2.4.0-test12 kernel. At the booting
> process, the kernel as well as the SCSI emulation recognize the drive.
> However, the SCSI emulation complains that the drive is assumed write
> protected as shown below:
>
> SCSI subsystem driver Revision: 1.00
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: MATSHITA Model: LS-120 VER5 00 Rev: F523
> Type: Direct-Access ANSI SCSI revision: 00
> Vendor: ATAPI Model: CD-R/RW 8X4X32 Rev: 5.AW
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 246528 512-byte hdwr sectors (126 MB)
> sda: test WP failed, assume Write Protected
> sda: unknown partition table
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0
> sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.11
>
> Can anyone please help me on how to setup this LS-120 so that it is R/W?
> TIA.
Do you have a disk in the drive at this point? Try with and without.
You don't say whether you have tried to write to it. Have you? What
happened?
------------------------------
From: "alan" <[EMAIL PROTECTED]>
Subject: about battery driver source
Date: Fri, 22 Dec 2000 09:05:27 +0800
Can you Email me a battery driver souce or tell me how I can do it by
myself.
I want to read battery's information with ports of 60/64.
Can someone give me a hand?
Thanks a lot ,if you do any thing for me!
------------------------------
From: Ralph Wesseling <[EMAIL PROTECTED]>
Subject: Re: Dual Xeon hangs
Date: Sat, 23 Dec 2000 12:37:32 +0100
On Fri, 22 Dec 2000 09:12:26 GMT, [EMAIL PROTECTED] (James
Rose) wrote:
>>> I have a dual Xeon 550 machine that hangs often, somewhat randomly when
>>> I'm doing some CPU intensive stuff. In the most recent crash, I was
>>> heavily using only one CPU, It doesn't seem to be CPU temp related,
>>> becuase just before it crashed, the temp was 45.5 deg. C. I'm running
>>> RH 6.1, kernel 2.2.14 - configured pretty much the same way as another
>>> dual 650 Pentium III which has no trouble. /var/log/messages contains
>>> little helpful info. I am running all the same daemons as the 650.
>>> Anyone know what's going on? In the meantime, I'm going to put 2.2.16
>>> on there to see if that helps.
>>> Ken
I used to have a similiar problem with my dual celeron system. When it
was working hard the machine would reset itself, this could after 5
minutes or after an hour. It was most prevalent under windows NT 4.0,
and initially I thought that it wasn't happening under Linux. It
certainly never occured under windows 98. It too wasn't temprature
related as the temp didn't go above 48 degrees. I was definitly the
dual CPU. In the end I gave up and bought a new DUAL cpu motherboard
and never had problems again. So time to check if there are any BIOS
updates for yopu board perhaps?
Ralph
------------------------------
From: "Hooda Gest" <[EMAIL PROTECTED]>
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Date: Sat, 23 Dec 2000 07:47:24 -0500
"CBFalconer" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> I have been lurking on this thread for a bit, and it occurs to me
> that most modems have a configuration value for hanging up on a
> carrier break. My USR must be set fairly high, because my wife
> can pick up the phone while I am on it and I don't lose the
> connection. In the old days the break period was fixed at
> something like 10 millisecs, so anything would drop the line.
>
> It is one of the S register settings.
You are thinking of the S10 register which sets the amount of time the modem
can tolerate loss of carrier before reporting it. Default on USR is 7 tenths
of a second. But that has little to do with why the USR holds onto the line
when your wife picks up the phone. In those cases, carrier is still there
but is degraded by the ambient noise brought in from the handset your wife
is holding. USR's simply try very hard to maintain the connection under very
adverse conditions.
Hooda
------------------------------
From: "Nicola Asuni" <[EMAIL PROTECTED]>
Subject: pinouts wanted
Date: Sat, 23 Dec 2000 13:47:23 GMT
I'm always looking for new pinouts (cables, adapters, connectors) to
integrate my large collection on www.technick.net
Also I'm looking for new hardware tutorials, guides...
If you can help me, please email me at [EMAIL PROTECTED]
Nick.
------------------------------
From: "Jess Jackson" <[EMAIL PROTECTED]>
Subject: Cannot print in Redhat 7
Date: Sat, 23 Dec 2000 13:52:39 GMT
Good Morning:
I apparently have clobbered my ability to printer either via USB or parallel
in my RedHat 7 on a Dell Dimension Pentium II-400 MHz. I am pretty new to
Linux and am learning through the school of hard knocks.
I inadvertently overwrote both /dev/lp0 and /dev/usblp0. I was in the
process of trying to get LPRng-3.7.2 working and had printing via the
parallel port working at one point.
I have an Epson Stylus 740 that works fine on either USB or parallel
connection under Windows. At this point, I would be happy to get either to
work under Windows.
Here is the story on each effort I have made.
First, generally, I changed \etc\modules.conf with the "options" line to
reflect my parallel port setting via BIOS and confirmed in Windows as
follows...
alias eth0 rtl8139
alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=5
alias scsi_hostadapter fdomain
Based on some posts I found (sorry, forget who to credit), I have tried to
"re-create" /dev/lp0 and /dev/usblp0 as follows...
mknod -m 660 /dev/lp0 c 6 0
mknod -m 660 /dev/usblp0 c 180 0
Both "appeared" to regenerate fine. Perhaps I am missing a subsequent step.
===========================
Parallel port
The boot process seems to find my EPP printer just fine. Here is what dmesg
shows...
parport0: PC-style at 0x378, irq 5 [SPP,PS2,EPP]
parport_probe: succeeded
parport0: Printer, EPSON Stylus COLOR 740
lp0: using parport0 (interrupt-driven).
But I cannot print the ASCII directly to port from either "printtool" or
"lprngtool" and obviously cannot print the ASCII test page. Both "printtool"
or "lprngtool" find /dev/lp0 as available.
Getting "back to basics," I tried simply directly printing to "device"
with..
# ls >/dev/lp0
Nothing (absolutely nothing) happened -- no output to printer and no error
messages.
I am at a loss as to what to try next on the parallel side.
===========================
USB Connection
It appears that Linux is finding my USB controller just fine. Running dmesg
after booting gets this about USB...
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver usblp
After booting, I ran the following to install usb printer support...
insmod /lib/modules/2.2.16-22/usb/usbcore.o
insmod /lib/modules/2.2.16-22/usb/printer.o
As with the parallel tests, I cannot print the ASCII directly to port from
either "printtool" or "lprngtool" and obviously cannot print the ASCII test
page. Unlike the parallel test, neither printtool" nor "lprngtool" show
/dev/usblp0 as available.
As with the parallel test, I tried simply directly printing to "device"
with..
# ls >/dev/usblp0
This got...
bash: /dev/usblp0: No such device
So, I look stuck here as well.
===========================
I would mention that I did have, *ON SOME EARLIER TESTING WHICH I CANNOT
SEEM TO REPLICATE*, get printing directly to the printer via USB to work. At
that point, I got the following from dmesg...
usb.c: USB new device connect, assigned device number 5
usb.c: This device is not recognized by any installed USB
driver.
parport0: PC-style at 0x378, irq 5 [SPP,PS2,EPP]
parport_probe: failed
parport0: no IEEE-1284 device present.
lp0: using parport0 (interrupt-driven).
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0
printer.c: usblp1: USB Bidirectional printer dev 3 if 0 alt 1
usb.c: USB disconnect on device 5
usb.c: USB new device connect, assigned device number 5
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0
Unplugged USB cable at printer and reconnected and Linux appears to have
"seen" that and responded as follows...
usb.c: USB disconnect on device 5
usb.c: USB new device connect, assigned device number 5
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0
===========================
BOTTOM LINE -- I need some help here. I would like to be able to connect
either way, but at this point just getting one way up would be a victory.
Thanks,
Jess
------------------------------
From: Gotzon Berrojalbiz <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: SCSI ADAPTER 1505
Date: Sat, 23 Dec 2000 16:32:36 +0000
Ekkard Gerlach wrote:
> Your problem:
> I have got the same SCSI-Card and an scanner attached, too.
> Have you got a pnp-card (Plug&Play) or non-pnp ? - The
> non-pnp-card you can switch IRQ and DMA by jumper, the
> pnp-card you have to initialise by Kernel-options
> at lilo-start. See linux-pnp-tool (attention: isapnp.conf
> that is automatically generated is buggy! Delete "CHECK"!).
>
> Which options did you enable in your Kernel? pnp?
> SCSI-generic support? ..... What exactly have you
> done?
I've generated a new kernel with these options:
PLUG & PLAY SUPPORT = Y
SCSI SUPPORT = Y
SCSI GENERIC SUPPORT = Y
ADAPTEC AHA152X/2825 SUPPORT = Y
The SCSI card I'm using it's PNP and there's no posibility of
configuring by jumpers.
I've also modified the BIOS config. with NON PNP O.S.
My questions are:
a) Do I have to compile scsi card support as a module ?
b) How do I exactly have to modify lilo.conf ?
c) Is there any conflict risk between these card and SCSI EMULATION
SUPPORT for IDE CD-RW ?
d) Do I have to use isapnptools for modifying IO and IRQ , or this can
be done with lilo.conf ?
THANKS
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Wheel mouse works - if...
Date: Sat, 23 Dec 2000 16:10:06 -0000
Reply-To: [EMAIL PROTECTED]
On 22 Dec 2000 18:47:56 GMT, FMRCYouth <[EMAIL PROTECTED]> wrote:
>I got my Logitech wheel mouse working correctly, but to get it started I need
>to type in "imwheel -k" EVERY time I log into Xwindows. Is there any way to
>work around this? It's not a big deal, but it would be nice to not have to
>type this in each time I log in.
>
I have a Logitech wheel mouse and followed the directions here to
get the wheel to work:
http://www-sop.inria.fr/koala/colas/mouse-wheel-scroll/
I'm not sure what the imwheel command does but couldn't you put
this in your .xinitrc file somewhere before the window manager runs
to get it to run.
Another place might be in one of the startup scripts for the system
when it gets started. Under Slackware, I put things that I want
started on bootup in /etc/rc.d/rc.local.
--
Frank Hahn
It is better for civilization to be going down the drain than to be
coming up it.
-- Henry Allen
------------------------------
** 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 by posting to comp.os.linux.hardware.
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
******************************
