From: PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...> - 2000-09-02 00:32:40
|
> > cat /proc/parport/0/autoprobe > > MODEL:Unknown device; > MANUFACTURER:Unknown vendor; > > ... which seems obviously wrong but I don't know what valid values > might be... It should report something like "Hewlett-Packard" (possibly all uppercased) and "OfficeJet Series 700" for the manufacturer and model fields. > > see what other port numbers (1, 2, etc.) are in the parport > directory > > there is only 0 OK, so we know there's really only one port. > > Are you able to print just by dumping text or PCL > > data to /dev/lp0 (or lp1, etc.), without loading ieee12844pp.o? > > yes. I did "cat .kshrc > /dev/lp0" and it printed it. funky, but it > printed. By "funky", do mean that it exhibited the "staircase" effect? That's to be expected unless the Unix-style newlines (LF only) are converted to DOS-style (CR and LF). > > cat /proc/ioports > > 0000-001f : dma1 > 0020-003f : pic1 > 0040-005f : timer > 0060-006f : keyboard > 0070-007f : rtc > 0080-008f : dma page reg > 00a0-00bf : pic2 > 00c0-00df : dma2 > 00f0-00ff : fpu > 0170-0177 : ide1 > 01f0-01f7 : ide0 > 0220-022f : soundblaster > 02e8-02ef : serial(auto) > 0330-0333 : MPU-401 UART > 0376-0376 : ide1 > 03c0-03df : vga+ > 03f6-03f6 : ide0 > 03f8-03ff : serial(auto) > e800-e8ff : eth0 > ec00-ecff : eth1 > ffa0-ffa7 : ide0 > ffa8-ffaf : ide1 Strange. Did you do this while the parport, parport_pc, and parport_probe modules were loaded? I would have expected to see lines like: 0378-037a : parport0 0778-077a : parport0 I'm really starting to run out of ideas here. Your peripheral is connected directly to the parallel port without any pass-through devices, which is good, and the parallel port is enabled in the BIOS, obviously since you can print by cating stuff to /dev/lp0. The only thing I can think of is that maybe you have a bad parallel port or cable. Perhaps there's a line that's stuck low or high, such that it permits the basic signaling that happens when using /dev/lp0 but breaks the extra signaling that happens with ieee12844pp.o. You wouldn't happen to have a logic analyzer and DB25 breakout board handy, would you? :-) At the very least, I would suggest trying a different parallel cable (a high-quality cable that is "IEEE1284 compliant"). If possible, you could also try a different printer on your PC or try your printer in a different PC (running Linux, so you can run the same tests). Or you could even try adding a second parallel port, but that could open another can of worms. What brand/model of computer are you using? I was going to ask if you were running VMWare (which tends to take over the parallel port), but I didn't see anything related to it in your lsmod output. David |