Hello Johannes, thanks for your answer. testet some times your possible soulutions. unfortunately with no success. kernel module will now be loaded until system startup via /etc/sysconfig/kernel. parport device has been detected and values seems to be correct.
linux-k67x:/etc/sysconfig # dmesg | grep parport parport0: PC-style at 0x378 (0x778), irq 7, dma 7 [PCSPP,TRISTATE,COMPAT,ECP,DMA] parport0: Printer, HEWLETT-PACKARD OFFICEJET PRO 1150C lp0: using parport0 (interrupt-driven). module parameters has been set up by /etc/modprobe.conf options parport_pc io=0x378 irq=7 did not add parameter for dma yet. is this important? Can print fine on device, it is detected by hp-setup. Scanning still unpossible. syslog means... Apr 12 00:58:44 linux-k67x xsane: hpaio: hpaioScannerToSaneError: sclError=1. Apr 12 00:58:48 linux-k67x xsane: unable to fill data buffer: size=18411: api/hplip_api.c 471 Apr 12 00:59:19 linux-k67x hpiod: ParDevice::wait_status timeout status=7e mask=88 val=0 us=30000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:20 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:21 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:22 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:23 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:24 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:25 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:26 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:27 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:28 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:29 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:30 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:31 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:32 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:33 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:34 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:35 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:36 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:37 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:38 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:39 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:40 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:41 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:42 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:43 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:44 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:45 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:46 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:47 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:48 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:49 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:50 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:51 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:52 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:53 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:54 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:55 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:56 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:57 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:58 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 00:59:59 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:00 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:01 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:02 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:03 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:04 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:05 linux-k67x hpiod: ParDevice::wait_status timeout status=de mask=40 val=0 us=1000000: io/hpiod/ppdevice.cpp 118 Apr 12 01:00:05 linux-k67x hpiod: unable to read MlcReverseData header: No such file or directory hp:/par/OFFICEJET_PRO_1150C?device=/dev/parport0 io/hpiod/mlc.cpp 500 Apr 12 01:00:05 linux-k67x xsane: hpaio:hpaioSclInquire(cmd=10886,param=1026) didn't get expected response of <<ESC>*s1026d>! then xsane tells me something about memory. not enougth.. officejet is blinking and waiting for scan data... did not try your packages yet. don´t think that it may work with them. think it is a kernel or module problem? regards, Harald. Johannes Meixner schrieb: > Hello, > > On Mar 21 21:11 [EMAIL PROTECTED] wrote (shortened): > >> linux-aszi:~ # lsmod | grep par >> > .. > >> parport_pc 42084 0 >> parport 39752 1 parport_pc >> > > At least the lp module is missing and additionally HPLIP needs > the ppdev module for parallel port devices, i.e. do as root > modprobe lp > modprobe ppdev > > The command > lsmod | egrep '^parport|^lp|^ppdev' > should result: > ------------------------------------------------------ > ppdev 13060 0 > parport_pc 42084 1 > lp 15652 0 > parport 39752 3 ppdev,parport_pc,lp > ------------------------------------------------------ > > > There are some bug reports about problems with the parallel port > in our Novell/Suse Bugzilla. A good report to start is > https://bugzilla.novell.com/show_bug.cgi?id=185135 > See also the other bug reports which are mentioned there. > > Something seems to be fishy with the parallel port stuff > in the kernels since Suse Linux 10.0, see > http://lists.suse.com/archive/suse-linux-e/2005-Nov/1206.html > > The current workaround is to experiment with various BIOS settings > and explicite additional settings in /etc/modprobe.conf to find a > setup, which actually works in a particular problematic case. > > Note that e.g. for scanning you may have to use a higher-level > parport mode (some kind of fast bidirectional mode) and > additionally the kernel module ppdev may have to be loaded > for some software (e.g. for HPLIP and for SANE). > > Note that those modes (EPP or even ECP) normally require > an interrupt and ECP additionally requires DMA. > To activate the interrupt mode, set in /etc/modprobe.conf > something like "options parport_pc io=0x378 irq=7" > where io and irq must match to your BIOS settings. > Make sure that the IRQ which you use for the parallel port > is not used by any other stuff, see our online documentation > (package suselinux-manual_en or opensuse-manual_en) > chapter "Printer Operation", section "Troubleshooting", > sub-section "Parallel Ports". > > > By the way: > > I provide for testing HPLIP 1.7.2 for the released openSUSE 10.2 > and Suse Linux 10.1 and Suse Linux Enterprise 10 and for the > openSUSE development version openSUSE "factory" > for 32-bit Intel compatible (i586) and for 64-bit AMD (x86_64) > via the openSUSE build service at > http://software.opensuse.org/download/home:/jsmeix/ > > The packages are > * only for testing > * without any guarantee or warranty > * without any support > > As an extreme example, this means that if your complete computer center > crashes because of these packages, it is only your problem. > > Nevertheless, we are very interested in your feedback because the more > people test it, the more problems (even hidden problems) are revealed. > To send us feedback or bug reports, please follow the instructions in > http://en.opensuse.org/Submitting_Bug_Reports > and make it obvious which package, which package version, which hardware > architecture and which openSUSE version you are talking about - e.g.: > "Feedback regarding hplip-1.7.2-11.1.i586.rpm > and hplip-hpijs-1.7.2-11.1.i586.rpm from > http://software.opensuse.org/download/home:/jsmeix/ > for openSUSE 10.2 used on 64-bit AMD hardware." > Ideally provide the "rpm -q --changelog hplip | head" output > to make it obvious which exact package release you have. > > > Kind Regards > Johannes Meixner > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ HPLIP-Help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hplip-help
