Linux-Hardware Digest #85, Volume #14 Tue, 26 Dec 00 01:13:04 EST
Contents:
Re: CUSL2-C, 815e chipset & Linux ("Default User")
Re: Modem problems in Mandrake 7.2 (Jeff)
Re: RedHat on RS6000 (Norman Levin)
Re: Which kind of netcard is best support in Linux? (Norman Levin)
Floppy problems that can't be solved with Viagra (Peter B. Steiger)
ATI TV Wonder USB and Linux (mattyu)
Re: LSILogic Symbios 53c1010 SCSI controller does not like Mandrake 7.2 (Johan
Kullstam)
NEC 1400 Laser Printer (Eusebio Garate)
Agfa ePhoto with USB (Alastair Foster)
Re: Iomega 250 USB Zip? (Chris Rankin)
Re: Modem problems in Mandrake 7.2 ("John McCubbin")
Re: Modem problems in Mandrake 7.2 ("harshal")
Re: Modem problems in Mandrake 7.2 ("snoopy")
Rehat 7.0 -- No printing in fresh install ("Jess Jackson")
Re: Cannot print in Redhat 7 ("Jess Jackson")
----------------------------------------------------------------------------
From: "Default User" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.periphs.mainboard.asus,comp.sys.intel
Subject: Re: CUSL2-C, 815e chipset & Linux
Date: Mon, 25 Dec 2000 13:32:50 -0500
Linux blues? I thought this OS was good?
"Alinga Yeung" <[EMAIL PROTECTED]> wrote in message
news:6%D16.28797$[EMAIL PROTECTED]...
> "{[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] (Jeff)
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 19:15:44 GMT
On Mon, 25 Dec 2000 16:54:24 -0600, "John McCubbin"
<[EMAIL PROTECTED]> wrote:
>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
>
Hi! I have also recently installed Slackware on a 486 computer with
Supra 14.4 internal PCI modem. Slackware is refusing to recognize the
modem and I am clueless as to how to resolve this problem. What do
you suggest is the best way to resolve this problem? Thanks.
Jeff
>
------------------------------
Date: Mon, 25 Dec 2000 12:53:13 -0500
From: Norman Levin <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.powerpc
Subject: Re: RedHat on RS6000
Jeff Moore wrote:
>
> I am interested in compiling RedHat Linux 7.0 for my RS6000.
>
> I do not know yet how to compile the kernel and boot disks for the
> RS6000.
> Has anyone tried this before?
>
> My RS6000 is the following:
>
> IBM Powerserver 320 type 7012
** forget it. 320 is a power architecture that is not supported by anybody other than
ibm and aix. find cd for aix and try it.
Norman Levin
------------------------------
Date: Mon, 25 Dec 2000 12:54:32 -0500
From: Norman Levin <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Which kind of netcard is best support in Linux?
Yurasis Dragon wrote:
>
> I have had great success with Netgear 310TX PCI under Redhat 7. I was
> struggling with a 3com 509 card and someone recommended this card. I spent
> $40 Canadian and never looked back.
>
> On Sat, 16 Dec 2000 09:31:08 GMT, [EMAIL PROTECTED] wrote:
>
> >most stable and best support ?
** my dlink 550tx (or is it 650tx) went in with NO problems.
--
Norman Levin
------------------------------
From: [EMAIL PROTECTED] (Peter B. Steiger)
Subject: Floppy problems that can't be solved with Viagra
Date: Mon, 25 Dec 2000 20:30:30 GMT
Help! I'm trying to copy stuff off my RH7 server onto /mnt/floppy,
and something has gone terribly wrong. It started with my NT box's
floppy drive, which (I suspect) is chewing holes in my disks - after I
write stuff onto a disk with the NT, nothing else can read from the
disk. Fine, I said to myself, I'll use the more reliable OS with a
floppy drive I know works.
Stupidly I mounted /mnt/floppy using one of the disks that
the NT crapped on, and not surprisingly I got errors trying to
mount that disk. So I took a "virgin" disk, popped it in,
ran mount /mnt/floppy, and got...
floppy0: probe failed... {repeated about 15 times}
end_request: I/O error, dev 02:00 (floppy), sector 0
/dev/fd0:Input/output error
{repeat entire process ad infinitum}
If I whack ctrl-break long enough, it stops with a
culinary error message:
FAT bread failed
The same disk works fine on other computers; it's just that
Linux doesn't seem to want to recover from a bad floppy.
Any suggestions?
Peter B. Steiger
Cheyenne, WY
----
If you reply by email, send it to pbs at com dot
canada (or vice-versa). All advertisements will be
returned to your postmaster, eh!
------------------------------
From: mattyu <[EMAIL PROTECTED]>
Subject: ATI TV Wonder USB and Linux
Date: Mon, 25 Dec 2000 20:35:06 GMT
Howdy Folks,
I just got an ATI TV Wonder USB Edition and I'm running RedHat 6.2 w/
the Gnome environment... This device is basically a tv tuner that
attaches to your USB port, it's got software for Windows 9x (of course),
but no apparent linux support. I imagine that it shouldn't be
impossible to figure it out, but I've never done anything w/ my USB port
before (especially not in linux)... I was wondering if anyone could
possibly grace me w/ an idea of where to start, as I don't know exactly
where I should go after plugging this guy in... I'll be fooling around
w/ it, but any assistance would be greatly appreciated... Thanks...
Matty U!
BTW -- I'm running all this on a Fujitsu Lifebook something or other (I
believe 900 series), with a Pentium 233 and 64M of ram... (woohoo!!!)
Thanks again..
--
"Power can be such a tease -
You're always wanting more..
It's good to know that just like sex
It can be paid for....." -Pedro
------------------------------
Subject: Re: LSILogic Symbios 53c1010 SCSI controller does not like Mandrake 7.2
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: Mon, 25 Dec 2000 21:44:34 GMT
"foo" <[EMAIL PROTECTED]> writes:
> I am trying to re-install mandrake 7.2 (via FTP or CD) on a system with an
> LSILogic Symbios 53c1010 scsi adapter. I removed all partitions from the
> hard drives using Partition magic 5.0, then walked through the install. All
> goes well, but when I reboot, lilo cannot find the root file system and I
> get a message like this:
>
> VFS: cannot open root device 08:11
> Kernal panic: VFS: Unable to mount root fs on 08:11
>
> I also tried setting up the partitions with Partition Magic, and not letting
> DrakX do any partitioning or formatting at all. I get the same result. DrakX
> seems to not understand the drive geometry or something, as it and the SCSI
> bios display differing values for cylinders, heads, and sectors.
>
> Has anyone worked with this scsi adapter with linux?
i think this scsi adapter has only very recently been added to the
linux driver. try one of the latest kernels.
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
------------------------------
From: Eusebio Garate <[EMAIL PROTECTED]>
Subject: NEC 1400 Laser Printer
Date: Mon, 25 Dec 2000 14:15:35 -0800
Hello,
Has anyone gotten the NEC 1400 printer to work with Linux. If so at what
dpi? I haven't found much information by doing a search and the only
info I found from dejanews was rather cryptic (someone said it works
under Redhat 6.2 with drivers found on the CD but there was no info on
resolution). I am using Mandrake 7.2.
Thanks for any information.
Eusebio
------------------------------
From: Alastair Foster <[EMAIL PROTECTED]>
Subject: Agfa ePhoto with USB
Date: Tue, 26 Dec 2000 00:45:04 GMT
I'd really appreciate hearing from anybody who has successfully managed
to get an Agfa ePhoto digital camera working on Linux with the USB
interface.
I note that gPhoto supports the serial, but not the USB versions of this
camera. However, I'm sure there must be some way to get it working
through USB. After all, the kernel takes care of all the USB
interpretation, so surely switching from USB to serial should be as
simple as chaning the port from /dev/cuaxx or /dev/ttySxx to /dev/usbxx.
Or am I being naive?
--
- Alastair Foster
http://users.netaccess.co.nz/ala/
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Chris Rankin <au.com.zipworld@{no.spam}rankinc>
Subject: Re: Iomega 250 USB Zip?
Date: Tue, 26 Dec 2000 02:53:32 +0000
mpierce wrote:
> Can you tell me how you setup your USB?
Ah, the infamous ZIP configuration problem ...
> What is the correct entry for /etc/fstab, ie, file system type for zip
> drive, etc.
Well I put this in /etc/fstab:
/dev/sda1 /mnt/zip2 ext2 noauto,user,rw
/dev/sda4 /mnt/zip vfat noauto,user,rw
> I added "none /proc/bus/usb usbdevfs noauto 0 0" to /etc/fstab
A good idea in general, but not important for this.
> I created /mnt/zip/
Now that IS important :-)!
> When I then try to mount zip, I get error:
> [root@localhost /mnt]# mount /dev/sda4 /mnt/zip
> mount: the kernel does not recognize /dev/sda4 as a block device
> (maybe `insmod driver'?)
Two problems here:
1) This command will probably try to mount the ZIP with the ext2
filesystem, but I suspect that the /dev/sda4 partition contains a FAT
filesystem. (Call it a hunch.) The best command to type is:
$ mount /mnt/zip
Then let mount figure out the rest from /etc/fstab.
2) You haven't loaded all the modules that you need to operate the ZIP
drive in the first place. I'm assuming that you have a recent version of
modutils and no parallel port ZIP drive as well, and so will suggest the
following line to add to /etc/modules.conf:
# ZIP drive support
above sd_mod usb-storage
This tells the kernel that it needs to load the usb-storage module
before trying to load the sd_mod module. As the saying goes, "it works
for me". Sort of. You really need a 2.4 kernel for USB ZIP drives, but
having said that I'm not sure that it's safe to use FAT filesystems with
2.4 yet.
My experience with 2.2.18 suggests that one of two things will happen to
you when you get the ZIP working:
EITHER it will completely fail to mount the disk
OR it will all seem to work fine, but your CPU usage will hit 100% until
you umount the disk and unload the usb-storage module again.
I personally am using ext2-formatted disks until I hear that 2.4 can
handle FAT filesystems.
Chris
------------------------------
From: "John McCubbin" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.os.linux.mandrake,comp.os.linux.setup
Subject: Re: Modem problems in Mandrake 7.2
Date: Tue, 26 Dec 2000 21:32:21 -0600
If it's a PCI modem, it's probably a winmodem and I stuck to ISA modems for
that reason. I was warned that the PCI (usually "soft modems") don't work
the overwhelming majority of the time. You can get a really good ISA non
PnP modem for under $50. I'd get one of those set it for COM3 IRQ 4 and
you'll have no problem.
--
John McCubbin
CCD/Astrophotograpny Website
http://www.usit.com/mccubbin/astronomy.html
------------------------------
From: "harshal" <[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 20:36:52 +0530
Does your modem really get ditected? 'cause i have same modem but don't know
how to configure it. If you ever be able to configure & run that modem under
linux please don't forget to post here.
"Rutger" <[EMAIL PROTECTED]> wrote in message
news:l5u16.3112$iB1.71617@zonnet-reader-1...
> Look here:
>
>
http://www.europe.redhat.com/documentation/HOWTO/Winmodems-and-Linux-HOWTO.p
> hp3
>
> Good luck, please mail me if you succeeded, becuase i have exactly the
same
> modem and the same problem....
>
> Rutger
>
> "Michele Neylon" <[EMAIL PROTECTED]> schreef in bericht
> news:FAo16.10866$[EMAIL PROTECTED]...
> > I just installed Mandrake 7.2 It has detected the modem, but seems
unable
> > to configure it. The modem is a Diamond SupraExpress 56i V PRO
> >
> > If anybody has any idea how I can configure it please let me know -
> > Thanks
> > Michele
> >
> >
>
>
------------------------------
From: "snoopy" <[EMAIL PROTECTED]>
Subject: Re: Modem problems in Mandrake 7.2
Date: Mon, 25 Dec 2000 23:27:42 -0600
That support address SHOULD be:
http://www.linmodems.org/
"terry" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
-
>
> Linux - the wave of the future
> **********************************************
> ** Registered Linux User Number 188099 **
> **********************************************
------------------------------
From: "Jess Jackson" <[EMAIL PROTECTED]>
Subject: Rehat 7.0 -- No printing in fresh install
Date: Tue, 26 Dec 2000 05:44:54 GMT
I am still not able to get any kind of printer configuration to work in Red
Hat Linux 7.0. I have a dual boot (Linux and Windows 98) Dell P-II, 400MHz
with 20 GB hard drive. I have and Epson Stylus 740 printer that works fine
under Windows either USB or parallel.
I had it connected in Redhat 6.2 via parallel. I upgraded to Redhat 7.0 and
now cannot print either USB or parallel. A number of people on both this
list and a couple of others have given various suggestions, none of which
have worked to this point.
Have a lot of free room on the hard drive, I decided just to set up a couple
of new ext2 partitions and do a fresh, clean install of Red Hat 7.0. That
went fine. I now can boot either the old or new version or Windows 98.
BUT -- I still cannot print. All that follows relates to the new install
The new install found both my onboard parallel port and USB hardware. I have
a two-port USB connection on the motherboard and a seven-port hub off one of
them (an Entrega 4U-2S-1P -- though I don't care about the non-usb parts
under Linux). Here are some selected lines from the boot process...
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.232 $ time 16:53:56 Aug 22 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: Intel USB controller: setting latency timer to 0
usb-uhci.c: USB UHCI at I/O 0x1020, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
usb.c: USB new device connect, assigned device number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: USB new device connect, assigned device number 2
hub.c: USB hub found
hub.c: 7 ports detected
usb.c: USB new device connect, assigned device number 3
usb.c: This device is not recognized by any installed USB driver.
usb.c: USB new device connect, assigned device number 4
usb.c: This device is not recognized by any installed USB driver.
usb.c: USB new device connect, assigned device number 5
usb.c: This device is not recognized by any installed USB driver.
... (snip)
parport0: PC-style at 0x378 [SPP,PS2,EPP]
parport_probe: succeeded
parport0: Printer, EPSON Stylus COLOR 740
lp0: using parport0 (polling).
It appears that while it is loading the USB Hub, it is NOT installing the
USB printer driver. So, I entered...
modprobe printer
to which, dmesg gave me the following response...
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0
printer.c: usblp1: USB Bidirectional printer dev 4 if 0 alt 1
Just to see what I had running and on suggestion from a previous message, I
did...
cat /proc/bus/usb/drivers
which resulted in...
0- 15: usblp
hub
usbdevfs
This all looked promising. So, I opened "printtool" and attempted to connect
to the USB printer. It appears that the base version of LPRng with Redhat
7.0 does not have lprngtool.
As I attempted to add the printer, it showed "lp0" detected as I would
expect. But printtool showed two other devices detected which I would have
thought would have looked like /dev/usblp0 or /dev/usblp0. Instead, it
showed two entries it identified as /dev/dev/lp0 and /dev/dev/lp1. That did
not look right.
Nevertheless, I tried installing the Epson on /dev/usblp0 and later to
/dev/dev/lp0. I could not get any output even with "print directly to port"
in either configuration. Both cases said they printed something when I tried
all three choices -- "print directly to port," "print ASCII test page," and
"print Postscript test page."
I checked in /dev and there was no entries for /dev/usblp0 or /dev/dev/lp0.
Based on a response on my earlier posts, I attempted to create the
/dev/usblp0 entry as follows...
mknod -m 660 /dev/usblp0 c 180 0
Even with that, no success at all, even with "print directly to port" via
USB connection.
It appears that I am OK at the raw hardware level. I have tried unplugging
and reconnecting the USB cable. The system appears to "see" the printer come
and go as reflected in this section from dmesg...
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0
printer.c: usblp1: USB Bidirectional printer dev 4 if 0 alt 1
...
usb.c: USB disconnect on device 3
usb.c: USB new device connect, assigned device number 3
printer.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 0
I have also tried "ls >/dev/usblp0" to see if I can at least get output at
this level.
(One question -- I am pretty new at Linux... Does exercising the printer,
either parallel or USB, with the commands "ls >/dev/usblp0" or "ls
>/dev/lp0" operate at the pure hardware level, not needing the lpd daemon?)
If true, I cannot figure why this does not produce some kind of output.
__________________
While USB is my preferred method, I would settle for getting the parallel
port to work instead. After a reboot and reconnection from USB to parallel,
I went through all the above including "print directly to port" from
printtool and "ls >/dev/lp0" none of which produced any output.
Again, the printer works great under Windows 98 either via parallel or USB.
Something as apparently as simple as basic printing ought not to be this
complicated. I have more than ten hours in this heretofore fruitless effort.
Any help would be GREATLY appreciated. Many thanks in advance.
Jess
------------------------------
From: "Jess Jackson" <[EMAIL PROTECTED]>
Subject: Re: Cannot print in Redhat 7
Date: Tue, 26 Dec 2000 05:46:32 GMT
Thanks -- I will try this...
Jess
___________
"Default User" <[EMAIL PROTECTED]> wrote in message
news:RiM16.347$[EMAIL PROTECTED]...
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 -)
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:
>
> 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
>
>
>
>
------------------------------
** 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
******************************
