Linux-Hardware Digest #84, Volume #14 Mon, 25 Dec 00 14:13:03 EST
Contents:
Re: CUSL2-C, 815e chipset & Linux ("Alinga Yeung")
Re: Intel Easy PC camera - cannot be supported in Linux! ([EMAIL PROTECTED])
AVA1502 scsi_hostadpter ("J.C.S. van de Sande")
Re: Wheel mouse works - if... (Roel)
Re: Modem problems in Mandrake 7.2 ("Rutger")
Re: Adaptec 1540 SCSI card no go (Ken)
Re: ??? RH7.0 on a Pentium Pro 200 (Dave Seyster)
Disk DMA access problem after changing motherboard ("Gilles Mocellin")
cd burner problems (Robin Kirkman)
mouse in mandrake ("Alex Dodik")
Re: Cannot print in Redhat 7 ("Default User")
----------------------------------------------------------------------------
From: "Alinga Yeung" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.periphs.mainboard.asus,comp.sys.intel
Subject: Re: CUSL2-C, 815e chipset & Linux
Date: Mon, 25 Dec 2000 08:58:42 GMT
"{[ZenmasteR]}" <[EMAIL PROTECTED]> wrote in message
news:YNn16.55008$[EMAIL PROTECTED]...
> you`ll need to try the latest kernel 2.4
Thanks for the suggestion. I just finished trying out
2.4.0-test12. It still has the same "unknown device"
messages when I did lspci -v -b. The following is
the message I got when I key in lspci -v - on Mandrake 7.2.
Notice the "unknown device" messages and the ethernet car
with IRQ 255.
========
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and
Memory Controller Hub (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 8027
Flags: bus master, fast devsel, latency 0
Memory at f8000000 (32-bit, prefetchable)
Capabilities: [88] #09 [f104]
Capabilities: [a0] AGP version 2.0
00:01.0 PCI bridge: Intel Corporation: Unknown device 1131 (rev 02) (prog-if
00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: ee000000-efdfffff
Prefetchable memory behind bridge: eff00000-f7ffffff
00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev 01) (prog-if
00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000b000-0000dfff
Memory behind bridge: ed000000-edffffff
Prefetchable memory behind bridge: efe00000-efefffff
00:1f.0 ISA bridge: Intel Corporation: Unknown device 2440 (rev 01)
Flags: bus master, medium devsel, latency 0
00:1f.1 IDE interface: Intel Corporation: Unknown device 244b (rev 01)
(prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 8027
Flags: bus master, medium devsel, latency 0
I/O ports at a800
00:1f.2 USB Controller: Intel Corporation: Unknown device 2442 (rev 01)
(prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 8027
Flags: bus master, medium devsel, latency 0, IRQ 3
I/O ports at a400
00:1f.3 SMBus: Intel Corporation: Unknown device 2443 (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 8027
Flags: medium devsel, IRQ 10
I/O ports at e800
00:1f.4 USB Controller: Intel Corporation: Unknown device 2444 (rev 01)
(prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 8027
Flags: bus master, medium devsel, latency 0, IRQ 9
I/O ports at a000
01:00.0 VGA compatible controller: nVidia Corporation NV11 (rev a1) (prog-if
00 [VGA])
Subsystem: AOPEN Inc.: Unknown device 0033
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11
Memory at ee000000 (32-bit, non-prefetchable)
Memory at f0000000 (32-bit, prefetchable)
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
02:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21041
[Tulip Pass 3] (rev 21)
Flags: bus master, medium devsel, latency 32, IRQ 255
I/O ports at d800
Memory at ed800000 (32-bit, non-prefetchable)
02:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev08)
Subsystem: Creative Labs CT4832 SBLive! Value
Flags: bus master, medium devsel, latency 32, IRQ 255
I/O ports at d400
Capabilities: [dc] Power Management version 1
02:0c.1 Input device controller: Creative Labs SB Live! (rev 08)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at d000
Capabilities: [dc] Power Management version 1
02:0d.0 Communication controller: Rockwell International: Unknown device2014
(rev 01)
Subsystem: Rockwell International: Unknown device 2014
Flags: bus master, medium devsel, latency 32, IRQ 255
Memory at ed000000 (32-bit, non-prefetchable)
I/O ports at b800
Capabilities: [40] Power Management version 2
=========
> wait for the final version of the kernel next year
Yeah, hopefully the support will be there by then.
In the mean time, if you have further suggestions,
please let me know. Thanks again.
>
>
> --
> "La plus belle des ruses du diable est de vous persuader qu'il n'existe
> pas."
>
>
> Remove XS to reply
>
>
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.development.system
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Date: Mon, 25 Dec 2000 09:28:32 -0000
In comp.os.linux.development.system mlw <[EMAIL PROTECTED]> wrote:
|> > It is a tough problem, and one of those gray areas in which a pure GPL
|> > approach is a very tough sell. To differentiate yourself and be
|> > competitive with a hardware product, you must make it good and make it
|> > competitively priced. The answer to this is proprietary software to
|> > control mass-produced trivial hardware.
|> >
|>
|> Not in a pure GPL approach, as Intel would have only a small expense in
|> the software development as would all the other camera manuafactures.
|
| But how would Intel make a case for its camera over some low priced
| clone? Why would someone pay $10 dollars more for an Intel camera? They
| wouldn't, and that would not be acceptable for someone like Intel.
This depends on whether the software can be developed in the open source
community. If the software can be made in the open, then Intel would have
no say in all the cheap $10 cameras out there which would use it. The big
issue is if Intel should release what they developed. As long as it makes
people buy their hardware instead of the clone (as long as no open source
software for clones has been done yet) then Intel won't see a business case
in releasing the source.
| Intel has a brand name, as dubious as it is, they have to make sure that
| there camera is better than a "Snap!" super el-cheapo. If they can't,
| they won't enter the market. If they release something that makes their
| camera better than the "Snap!" then, "Snap!" would be able to copy their
| image processing techniques and steal the market with price.
This is long as the "better" part is in the software. And, unfortunately
for cases like this, software is way cheaper than hardware due to the
lower incremental costs. They want their camera to be better without
(much) increase in costs (of development and manufacture, the extra price
will be taken as profit).
| GPL can not apply to hardware, because hardware is limited by finite
| numbers. Production has a proportional unit cost for the producer. While
| the software associated with a digital camera may be free, making it so
| would affect the ability to produce the camera competitively. The
| software is part of the camera.
It seems to me that one way to fight this is for more people who are
supporters of free software to do some hardware development along the
same lines, and release free designs that manufacture-only companies
might sell, which work with the corresponding free software (which
might have all real smarts in it).
--
=================================================================
| Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ |
| [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ |
=================================================================
------------------------------
From: "J.C.S. van de Sande" <[EMAIL PROTECTED]>
Subject: AVA1502 scsi_hostadpter
Date: Mon, 25 Dec 2000 11:19:10 +0500
Reply-To: [EMAIL PROTECTED]
Who can help me to configure thsi ISA card for myn microtek scanner
Johan
------------------------------
From: Roel <[EMAIL PROTECTED]>
Subject: Re: Wheel mouse works - if...
Date: Mon, 25 Dec 2000 11:21:58 +0100
Just make a kdelnk in autostart with the command imwheel -k
thats all
Roel
[EMAIL PROTECTED] (FMRCYouth) 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 w=
ay to
> work around this? It's not a big deal, but it would be nice to not hav=
e to
> type this in each time I log in.
>=20
>=20
> God bless,
> Randy Bennett
>=20
> Registered user #198235 at http://counter.li.org
------------------------------
From: "Rutger" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.os.linux.mandrake,comp.os.linux.setup
Subject: Re: Modem problems in Mandrake 7.2
Date: Mon, 25 Dec 2000 12:15:40 +0100
It is an PCI internal....
"John McCubbin" <[EMAIL PROTECTED]> schreef in bericht
news:53v16.7192$[EMAIL PROTECTED]...
> Michelle,
>
> Is this an ISA modem internal? Did you leave it plug and play or did you
> disable this and manually configure jumpers on the modem. If you can tell
> me this I may be able to help. Modems seem to be the first "real" problem
> most installs encouter. At least it was for me. Now that I've solved the
> problem about 10 times, it's gotten a little easier ;-)
>
> John McCubbin
> CCD/Astrophotograpny Website
> http://www.usit.com/mccubbin/astronomy.html
>
>
------------------------------
From: Ken <[EMAIL PROTECTED]>
Subject: Re: Adaptec 1540 SCSI card no go
Date: 25 Dec 2000 12:34:43 GMT
Julian Bordas <[EMAIL PROTECTED]> wrote:
> Hello
> I have a PC with an Adaptec 1540-1542 SCSI card and an Acer
> SCSI Card
> for the scanner. I am unable to install the adaptec card, I get an
> error message that the module load failed, yet both work under windows.
> Any suggestions any one?
Few of us are psychic so a little more information like what error
message etc.. would help.
------------------------------
From: [EMAIL PROTECTED] (Dave Seyster)
Crossposted-To: linux.redhat.install,linux.redhat
Subject: Re: ??? RH7.0 on a Pentium Pro 200
Date: Mon, 25 Dec 2000 12:46:16 GMT
On Sun, 24 Dec 2000 00:13:53 -0900, James <[EMAIL PROTECTED]> wrote:
>
>www.intellesale.com has a bunch in stock, at least 12-13. IBM PC Server
>325, dual processor on-board SCSI. (They're selling them stripped down, one
>processor, looks like the original minimum drive/memory config.) As of 24
>Dec 2000, they wanted $199 each for them.
Unless I misread the price on that web page, the price is $299.
------------------------------
From: "Gilles Mocellin" <[EMAIL PROTECTED]>
Subject: Disk DMA access problem after changing motherboard
Date: Mon, 25 Dec 2000 13:26:19 GMT
I'm under Mandrake 7.2 (kernel 2.2.17),
I decided to get more power and switch my Celeron with a Duron 700.
Of course, I need a new motherboard, I choose the great Abit KT7 (no RAID).
When I reboot under Linux (All works fine with Windows, after a long battle
!)
- X doesn't start (problem with agpgart and the VIA chipset)
- Disks hang after some access.
I found that disabling DMA access allow me to work with the disks (of course
with a poor transfert rate).
I tried a 2.4.0 kernel, and it was the same, perhaps, I haven't seen an
option...
Do someone have an idea ?
------------------------------
From: Robin Kirkman <[EMAIL PROTECTED]>
Subject: cd burner problems
Date: Mon, 25 Dec 2000 09:58:11 -0500
I just got a new cd burner for christmas, and it's misbehaving :(
My model is a Sony CRX140E/CH2
It's not listed as compatable by cdrecord, but neither is it listed
incompatable. The CRX140S is listed compatable, though.
I think my error might have something to do with cdrecord running out of
data to write with. Here's what I'm doing:
root@robin:/home/robin$ nice mkisofs -R ~robin | cdrecord -v fs=16m
speed=8 dev=0,1,0 -
I tried adjusting the fifo size from 6 to 8 to 16 megabytes; all that
did was make it fail at a later time during burn. Here's the error
message:
Track 01: 321 MB written (fifo 0%).cdrecord: Input/output error.
write_g1: scsi sendcmd: retryable error
CDB: 2A 00 00 02 82 67 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 12 00 00 00 00 0C 09 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
Sense flags: Blk 0 (not valid)
write track data: error after 336803840 bytes
56.11% done, estimate finish Mon Dec 25 09:42:25 2000
Sense Bytes: 70 00 00 00 00 00 00 12 00 00 00 00 00 00 00 00 00 00
Writing time: 274.988s
Fixating...
57.81% done, estimate finish Mon Dec 25 09:42:24 2000
Fixating time: 32.007s
cdrecord: fifo had 5560 puts and 5306 gets.
cdrecord: fifo was 52 times empty and 2753 times full, min fill was 0%.
Broken pipe
I figured out that the Broken pipe was from cdrecord crapping out with
mkisofs still sending data, but this doesn't help me much. It looks like
maybe cdrecord dies when its fifo runs out of data (It hit 0% and died),
but i'm not sure. If this is the case, I suppose I should stop nice'ing
mkisofs.
However, i'm still not sure...
Would it work to nice cdrecord instead?
Bleck... I'm running out of blank CD-R's.
Anyways, any help would be appreciated, as I couldn't find any on the
cdrecord web site.
--robin
------------------------------
From: "Alex Dodik" <[EMAIL PROTECTED]>
Subject: mouse in mandrake
Date: Mon, 25 Dec 2000 18:13:29 +0100
Can anybody tell me how can I install and configure the mouse in Mandrake
7.2
------------------------------
From: "Default User" <[EMAIL PROTECTED]>
Subject: Re: Cannot print in Redhat 7
Date: Mon, 25 Dec 2000 13:26:56 -0500
This is a multi-part message in MIME format.
=======_NextPart_000_0054_01C06E76.59F81240
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
use default Epson Stylus Color filter in printtool
make sure you have the path in printtool /dev/usb/lp0
restart lpr in printtool
try (as su -)=20
lpc
lpc>
redirect
(turns off forwarding)
quit
adding the insmod printer line in rc.sysconfig started the printer at =
boot-up for me.
USB-manager initiated from the "runlevel editor" tool starts my usb =
scanner module.
Install the Gimp-Print 4.02 rpm. It has most if not all the printer =
filters, including my Epson 860.
read my posts in alt.linux.sux
linux is giving me fits.
"Jess Jackson" <[EMAIL PROTECTED]> wrote in message =
news:H6216.175472$[EMAIL PROTECTED]...
> Good Morning:
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Here is the story on each effort I have made.
>=20
> 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...
>=20
> alias eth0 rtl8139
> alias parport_lowlevel parport_pc
> options parport_pc io=3D0x378 irq=3D5
> alias scsi_hostadapter fdomain
>=20
> Based on some posts I found (sorry, forget who to credit), I have =
tried to
> "re-create" /dev/lp0 and /dev/usblp0 as follows...
>=20
> mknod -m 660 /dev/lp0 c 6 0
> mknod -m 660 /dev/usblp0 c 180 0
>=20
> Both "appeared" to regenerate fine. Perhaps I am missing a subsequent =
step.
> ---------------------------
>=20
> Parallel port
>=20
> The boot process seems to find my EPP printer just fine. Here is what =
dmesg
> shows...
>=20
> parport0: PC-style at 0x378, irq 5 [SPP,PS2,EPP]
> parport_probe: succeeded
> parport0: Printer, EPSON Stylus COLOR 740
> lp0: using parport0 (interrupt-driven).
>=20
> 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.
>=20
> Getting "back to basics," I tried simply directly printing to "device"
> with..
>=20
> # ls >/dev/lp0
>=20
> Nothing (absolutely nothing) happened -- no output to printer and no =
error
> messages.
>=20
> I am at a loss as to what to try next on the parallel side.
>=20
> ---------------------------
>=20
> USB Connection
>=20
> It appears that Linux is finding my USB controller just fine. Running =
dmesg
> after booting gets this about USB...
>=20
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> usb.c: registered new driver usblp
>=20
> After booting, I ran the following to install usb printer support...
>=20
> insmod /lib/modules/2.2.16-22/usb/usbcore.o
> insmod /lib/modules/2.2.16-22/usb/printer.o
>=20
> 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.
>=20
> As with the parallel test, I tried simply directly printing to =
"device"
> with..
>=20
> # ls >/dev/usblp0
>=20
> This got...
>=20
> bash: /dev/usblp0: No such device
>=20
> So, I look stuck here as well.
>=20
> ---------------------------
>=20
> 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...
>=20
> 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
>=20
> Unplugged USB cable at printer and reconnected and Linux appears to =
have
> "seen" that and responded as follows...
>=20
> 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
>=20
> ---------------------------
>=20
> 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.
>=20
> Thanks,
> Jess
>=20
>=20
>=20
>=20
=======_NextPart_000_0054_01C06E76.59F81240
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>use default Epson Stylus Color <EM>filter</EM> in=20
<STRONG>printtool</STRONG></DIV>
<DIV> </DIV>
<DIV>make sure you have the <EM>path</EM> in <EM>printtool</EM>=20
<STRONG>/dev/usb/lp0</STRONG></DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV>restart <EM>lpr</EM> in <EM>printtool</EM></DIV>
<DIV> </DIV>
<DIV>try (as <STRONG>su -</STRONG>) </DIV>
<DIV> </DIV>
<DIV><STRONG>lpc</STRONG></DIV>
<DIV> </DIV>
<DIV>lpc></DIV>
<DIV> </DIV>
<DIV><STRONG>redirect</STRONG></DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV>(turns off <STRONG>forwarding</STRONG>)</DIV>
<DIV> </DIV>
<DIV><STRONG>quit</STRONG></DIV>
<DIV><STRONG></STRONG> </DIV>
<DIV> </DIV>
<DIV>adding the <STRONG>insmod printer </STRONG>line in =
<EM>rc.sysconfig</EM>=20
started the printer at boot-up for me.</DIV>
<DIV> </DIV>
<DIV><EM>USB-manager</EM> initiated from the "runlevel editor" tool =
starts my=20
usb scanner module.</DIV>
<DIV> </DIV>
<DIV>Install the Gimp-Print 4.02 rpm. It has most if not all =
the=20
printer filters, including my Epson 860.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>read my posts in alt.linux.sux</DIV>
<DIV> </DIV>
<DIV>linux is giving me fits.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>"Jess Jackson" <<A=20
href=3D"mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>> wrote =
in message=20
<A=20
href=3D"news:H6216.175472$[EMAIL PROTECTED]">news:H6216.=
175472$[EMAIL PROTECTED]</A>...</DIV>>=20
Good Morning:<BR>> <BR>> I apparently have clobbered my ability to =
printer=20
either via USB or parallel<BR>> in my RedHat 7 on a Dell Dimension =
Pentium=20
II-400 MHz. I am pretty new to<BR>> Linux and am learning through the =
school=20
of hard knocks.<BR>> <BR>> I inadvertently overwrote both /dev/lp0 =
and=20
/dev/usblp0. I was in the<BR>> process of trying to get LPRng-3.7.2 =
working=20
and had printing via the<BR>> parallel port working at one =
point.<BR>>=20
<BR>> I have an Epson Stylus 740 that works fine on either USB or=20
parallel<BR>> connection under Windows. At this point, I would be =
happy to=20
get either to<BR>> work under Windows.<BR>> <BR>> Here is the =
story on=20
each effort I have made.<BR>> <BR>> First, generally, I changed=20
\etc\modules.conf with the "options" line to<BR>> reflect my parallel =
port=20
setting via BIOS and confirmed in Windows as<BR>> follows...<BR>> =
<BR>>=20
&=
nbsp; =20
alias eth0 rtl8139<BR>>=20
&=
nbsp; =20
alias parport_lowlevel parport_pc<BR>>=20
&=
nbsp; =20
options parport_pc io=3D0x378 irq=3D5<BR>>=20
&=
nbsp; =20
alias scsi_hostadapter fdomain<BR>> <BR>> Based on some posts I =
found=20
(sorry, forget who to credit), I have tried to<BR>> "re-create" =
/dev/lp0 and=20
/dev/usblp0 as follows...<BR>> <BR>>=20
&=
nbsp; =20
mknod -m 660 /dev/lp0 c 6 0<BR>>=20
&=
nbsp; =20
mknod -m 660 /dev/usblp0 c 180 0<BR>> <BR>> Both "appeared" to =
regenerate=20
fine. Perhaps I am missing a subsequent step.<BR>>=20
===========================<BR>> <BR>> Parallel port<BR>> =
<BR>> The=20
boot process seems to find my EPP printer just fine. Here is what =
dmesg<BR>>=20
shows...<BR>> <BR>>=20
&=
nbsp; =20
parport0: PC-style at 0x378, irq 5 [SPP,PS2,EPP]<BR>>=20
&=
nbsp; =20
parport_probe: succeeded<BR>>=20
&=
nbsp; =20
parport0: Printer, EPSON Stylus COLOR 740<BR>>=20
&=
nbsp; =20
lp0: using parport0 (interrupt-driven).<BR>> <BR>> But I cannot =
print the=20
ASCII directly to port from either "printtool" or<BR>> "lprngtool" =
and=20
obviously cannot print the ASCII test page. Both "printtool"<BR>> or=20
"lprngtool" find /dev/lp0 as available.<BR>> <BR>> Getting "back =
to=20
basics," I tried simply directly printing to "device"<BR>> =
with..<BR>>=20
<BR>>=20
&=
nbsp; =20
# ls >/dev/lp0<BR>> <BR>> Nothing (absolutely nothing) happened =
-- no=20
output to printer and no error<BR>> messages.<BR>> <BR>> I am =
at a loss=20
as to what to try next on the parallel side.<BR>> <BR>>=20
===========================<BR>> <BR>> USB Connection<BR>> =
<BR>> It=20
appears that Linux is finding my USB controller just fine. Running =
dmesg<BR>>=20
after booting gets this about USB...<BR>> <BR>>=20
&=
nbsp; =20
usb.c: registered new driver usbdevfs<BR>>=20
&=
nbsp; =20
usb.c: registered new driver hub<BR>>=20
&=
nbsp; =20
usb.c: registered new driver usblp<BR>> <BR>> After booting, I ran =
the=20
following to install usb printer support...<BR>> <BR>>=20
&=
nbsp; =20
insmod /lib/modules/2.2.16-22/usb/usbcore.o<BR>>=20
&=
nbsp; =20
insmod /lib/modules/2.2.16-22/usb/printer.o<BR>> <BR>> As with the =
parallel tests, I cannot print the ASCII directly to port from<BR>> =
either=20
"printtool" or "lprngtool" and obviously cannot print the ASCII =
test<BR>>=20
page. Unlike the parallel test, neither printtool" nor "lprngtool" =
show<BR>>=20
/dev/usblp0 as available.<BR>> <BR>> As with the parallel test, I =
tried=20
simply directly printing to "device"<BR>> with..<BR>> <BR>>=20
&=
nbsp; =20
# ls >/dev/usblp0<BR>> <BR>> This got...<BR>> <BR>>=20
&=
nbsp; =20
bash: /dev/usblp0: No such device<BR>> <BR>> So, I look stuck here =
as=20
well.<BR>> <BR>> ---------------------------<BR>> <BR>> I =
would=20
mention that I did have, *ON SOME EARLIER TESTING WHICH I CANNOT<BR>> =
SEEM TO=20
REPLICATE*, get printing directly to the printer via USB to work. =
At<BR>>=20
that point, I got the following from dmesg...<BR>> <BR>>=20
&=
nbsp; =20
usb.c: USB new device connect, assigned device number 5<BR>>=20
&=
nbsp; =20
usb.c: This device is not recognized by any installed USB<BR>>=20
driver.<BR>>=20
&=
nbsp; =20
parport0: PC-style at 0x378, irq 5 [SPP,PS2,EPP]<BR>>=20
&=
nbsp; =20
parport_probe: failed<BR>>=20
&=
nbsp; =20
parport0: no IEEE-1284 device present.<BR>>=20
&=
nbsp; =20
lp0: using parport0 (interrupt-driven).<BR>>=20
&=
nbsp; =20
usb.c: registered new driver usblp<BR>>=20
&=
nbsp; =20
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0<BR>>=20
&=
nbsp; =20
printer.c: usblp1: USB Bidirectional printer dev 3 if 0 alt 1<BR>>=20
&=
nbsp; =20
usb.c: USB disconnect on device 5<BR>>=20
&=
nbsp; =20
usb.c: USB new device connect, assigned device number 5<BR>>=20
&=
nbsp; =20
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0<BR>> =
<BR>>=20
Unplugged USB cable at printer and reconnected and Linux appears to =
have<BR>>=20
"seen" that and responded as follows...<BR>> <BR>>=20
&=
nbsp; =20
usb.c: USB disconnect on device 5<BR>>=20
&=
nbsp; =20
usb.c: USB new device connect, assigned device number 5<BR>>=20
&=
nbsp; =20
printer.c: usblp0: USB Bidirectional printer dev 5 if 0 alt 0<BR>> =
<BR>>=20
===========================<BR>> <BR>> BOTTOM LINE == I need some =
help=20
here. I would like to be able to connect<BR>> either way, but at this =
point=20
just getting one way up would be a victory.<BR>> <BR>> =
Thanks,<BR>>=20
Jess<BR>> <BR>> <BR>> <BR>> </BODY></HTML>
=======_NextPart_000_0054_01C06E76.59F81240==
------------------------------
** 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
******************************
