First Time User - Problems/Questions
I am a first time user of SUSE Linux. I installed 10.0 on an HP Media Center PC 873n with a Dell 2001FP monitor and a HP LaserJet 4 printer. So far I have three questions/problems which I'm hoping someone can help me with ... In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out". The message was being output every ten seconds from initial boot but it stopped in the middle of the night last night. Can anyone tell me what would have caused the message? I cannot get the printer (HP LaserJet 4) to function. The following error messages are being sent to /var/log/messages when I try to lpr: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75 unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693 unable to send ProbeDevices: Broken pipe I cannot get display mode "1600 X 1200 (UXGA)" to function which, by the way, was the default mode of installation for me. The highest resolution which functions according to SUSE installation is "1600 X 1024 (WSXGA)". However, when I interrogate the monitor (Dell 2001FP) it says it's displaying only 1280 X 1024. In my previous installation (Mandrake 9.0) 1600 X 1200 functioned fine. I tried using the XF86Config file from my previous installation to no avail. -- Marshall Lake -- mlake@mlake.net -- http://mlake.net
On Tuesday 08 November 2005 11:58 am, Marshall Lake wrote:
I am a first time user of SUSE Linux. I installed 10.0 on an HP Media Center PC 873n with a Dell 2001FP monitor and a HP LaserJet 4 printer.
So far I have three questions/problems which I'm hoping someone can help me with ...
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out". The message was being output every ten seconds from initial boot but it stopped in the middle of the night last night. Can anyone tell me what would have caused the message?
No clue. DMA is associated with hard drives and cd/dvd drives. Check in YaST/Hardware/DMA settings.
I cannot get the printer (HP LaserJet 4) to function. The following error messages are being sent to /var/log/messages when I try to lpr: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75 unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693 unable to send ProbeDevices: Broken pipe
I believe the hpijs drivers is for InkJets not lasers. Go back into YaST/Hardware/Printer and choose the other driver for LaserJet 4.
I cannot get display mode "1600 X 1200 (UXGA)" to function which, by the way, was the default mode of installation for me. The highest resolution which functions according to SUSE installation is "1600 X 1024 (WSXGA)". However, when I interrogate the monitor (Dell 2001FP) it says it's displaying only 1280 X 1024. In my previous installation (Mandrake 9.0) 1600 X 1200 functioned fine. I tried using the XF86Config file from my previous installation to no avail.
When reconfiguring graphics displays in SUSE, logout of the desktop GUI, go to a console screen (Ctrl+Alt+F1 ... F6) and 'init 3' to stop X. From command line run 'sax2' and set the monitor up. You may need to manually adjust its settings or have the windows *.inf file on floppy and import it. Test your setup and then do an 'init 5' and go login and see if that works.
-- Marshall Lake -- mlake@mlake.net -- http://mlake.net
Stan
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out". The message was being output every ten seconds from initial boot but it stopped in the middle of the night last night. Can anyone tell me what would have caused the message?
No clue. DMA is associated with hard drives and cd/dvd drives. Check in YaST/Hardware/DMA settings.
I cannot get the printer (HP LaserJet 4) to function. The following error messages are being sent to /var/log/messages when I try to lpr: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75 unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693 unable to send ProbeDevices: Broken pipe
I believe the hpijs drivers is for InkJets not lasers. Go back into YaST/Hardware/Printer and choose the other driver for LaserJet 4.
Upon further investigation I've found that the printer problem I'm having and the DMA messages I'm getting are related. When I take the printer off-line the DMA timeout messages stop. I'm still no closer, though, to getting the printer working. I've tried every HPLJ 4 (and related) driver. I get the same error messages to /var/log/messages (as noted above) when attempting to print with every driver. -- Marshall Lake -- mlake@mlake.net -- http://mlake.net
On Wednesday 09 November 2005 12:10 am, Marshall Lake wrote:
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out". The message was being output every ten seconds from initial boot but it stopped in the middle of the night last night. Can anyone tell me what would have caused the message?
No clue. DMA is associated with hard drives and cd/dvd drives. Check in YaST/Hardware/DMA settings.
I cannot get the printer (HP LaserJet 4) to function. The following error messages are being sent to /var/log/messages when I try to lpr: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75 unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693 unable to send ProbeDevices: Broken pipe
I believe the hpijs drivers is for InkJets not lasers. Go back into YaST/Hardware/Printer and choose the other driver for LaserJet 4.
Upon further investigation I've found that the printer problem I'm having and the DMA messages I'm getting are related. When I take the printer off-line the DMA timeout messages stop.
I'm still no closer, though, to getting the printer working. I've tried every HPLJ 4 (and related) driver. I get the same error messages to /var/log/messages (as noted above) when attempting to print with every driver.
-- Marshall Lake -- mlake@mlake.net -- http://mlake.net
What is the exact model of HPLJ4 that you have? Yesterday I helped a client hook up a LaserJet 4. They had to change to the "Laserjet 4 ljet4" driver from "Laserjet 4 hpijs" and then it took right off on SUSE 9.3 Pro. I don't anticipate any real differences between this and SUSE 10.0 Retail/OSS. The DMA being related to a parallel printer issue is interesting. Don't see how it could be related. Stan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-11-09 at 10:41 -0600, Stan Glasoe wrote:
The DMA being related to a parallel printer issue is interesting. Don't see how it could be related.
Some bioses allow to set the printer port in "ECP/DMA" mode, in which DMA is used to transfer large quantities of data from memory to the printer port with no CPU intervention. It is also interesting for external disk drives plugged to that port, but I have never had luck with it (Iomega zip). The other method of using the port with an interrupt assigned seems to work better, but uses some cpu (but much less than the default polling method). Read Mr. Johannes post on this, it is very interesting. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDcli3tTMYHG2NR9URAnCNAJ9H7/xkM5EdhOxwdujtOpN/QarbVACdE6GJ eLNHcRzsSkuONAEdyx6m9Jo= =I4Pf -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-11-09 at 01:10 -0500, Marshall Lake wrote:
Upon further investigation I've found that the printer problem I'm having and the DMA messages I'm getting are related. When I take the printer off-line the DMA timeout messages stop.
I was going to sugest you change the parallel port settings in your bios, to not use dma, when I saw Mr Johannes advice: follow it. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDcheptTMYHG2NR9URAlO1AJ9Ia7msmQJd5GTnTlxMje54lQqAMQCdG1K/ klSln+OiwKNGgyH+GZR3hWY= =vYGD -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2005-11-08 at 12:58 -0500, Marshall Lake wrote:
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out". The message was being output every ten seconds from initial boot but it stopped in the middle of the night last night. Can anyone tell me what would have caused the message?
I can only guess. Perhaps one of your drives do not support dma properly, or not in the way the kernel knows or expects. Later, it could be that you changed something somewhere that affected, stopped using that drive, or that the kernel stopped using dma for that drive.
I cannot get the printer (HP LaserJet 4) to function. The following error
Dunno.
I cannot get display mode "1600 X 1200 (UXGA)" to function which, by the
Already answered. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDcTRwtTMYHG2NR9URAnBgAJwNmI50bnsKyf3Ky9IgcaAri9vn/gCdGsn3 11jANbq0SO5X0pRgWzqUZXg= =48XL -----END PGP SIGNATURE-----
Hello, On Nov 8 12:58 Marshall Lake wrote (shortened):
SUSE Linux 10.0 HP LaserJet 4 printer
As you don't tell us how the printer is connected, I can only guess that it is a parallel port printer.
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out"
See the "Release Notes" which are shown during installation and which are alos available as HTML file: file:///usr/share/doc/release-notes/RELEASE-NOTES.en.html "Using Parallel-Port Printers" The actual reason is that for parallel port printer autodetection the parallel port kernel modules must be re-loaded to make sure that a new switched-on parallel port printer will be detected. When parallel port is used in ECP/DMA mode there happens some kind of DMA deadlock after the parallel port kernel modules have been re-loaded (i.e. it is actually a kernel module bug). I.e. don't use ECP/DMA mode in the BIOS for the parallel port. Then all will work well.
I cannot get the printer (HP LaserJet 4) to function.
If it is a parallel port printer, don't use ECP/DMA mode in the BIOS for the parallel port, see above and see the recommendations in http://portal.suse.com/sdb/en/2000/08/jsmeix_print-einrichten.html and in http://portal.suse.com/sdb/en/2002/04/jsmeix_print-device-parallel.html (/etc/modules.conf was again renamed to /etc/modprobe.conf)
The following error messages are being sent to /var/log/messages when I try to lpr: unable to open /var/run/hpiod.port: No such file or directory:
Do you really use the "hp" backend? Regarding what a "backend" for printing is, see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html "The Backends" If you really use the "hp" backend, make sure the required hplip services are up and running, see http://portal.suse.com/sdb/en/2005/02/jsmeix_print-einrichten-93.html For a normal parallel port printer the generic "parallel" backend works well (and normally YaST would set up the print queue with the generic "parallel" backend). If you don't use the "hp" backend, ignore the messages about hplip/hpiod/hpssd and to get rid of such messages deactivate the hplip service (use the YaST runlevel editor).
I cannot get display mode "1600 X 1200 (UXGA)" to function ...
Please send one seperated mail for each seperated problem. This makes it easier to discuss a problem because seperated issues will not mix up in one single huge mail thread. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Wed, 9 Nov 2005, Johannes Meixner wrote:
SUSE Linux 10.0 HP LaserJet 4 printer
As you don't tell us how the printer is connected, I can only guess that it is a parallel port printer.
Right ... parallel.
In the /var/log/messages file there is following messge: "linux kernel: DMA write timed out"
See the "Release Notes" which are shown during installation and which are alos available as HTML file: file:///usr/share/doc/release-notes/RELEASE-NOTES.en.html "Using Parallel-Port Printers"
The actual reason is that for parallel port printer autodetection the parallel port kernel modules must be re-loaded to make sure that a new switched-on parallel port printer will be detected. When parallel port is used in ECP/DMA mode there happens some kind of DMA deadlock after the parallel port kernel modules have been re-loaded (i.e. it is actually a kernel module bug). I.e. don't use ECP/DMA mode in the BIOS for the parallel port. Then all will work well.
Thanks for your help. Turning off DMA in the BIOS did the trick. Additionally, as someone else mentioned in a separate post, I found I had to change the DefaultPageSize value in the ppd file for the HPLJ4 from A4 to Letter in order to get my printer to function properly. -- Marshall Lake -- mlake@mlake.net -- http://mlake.net
participants (4)
-
Carlos E. R. -
Johannes Meixner -
Marshall Lake -
Stan Glasoe