HP LaserJet P2055dn: Margins are not being respected
by Steven P. Ulrick
Hello Everyone,
Just recently my HP LaserJet P2055dn has started printing
everything as close to the top of the page as possible. Everything else
on the page looks normal. The documents that I have been using to test
this issue with have .79" margins all around.
This is a new issue for me. Up until today this printer has not
given me any trouble at all.
I'm sure that I have not given you as much information as will be
needed to troubleshoot this, so I will gladly provide any additional
information that is required.
Steven P. Ulrick
P.S.: I hope this message arrives as plain text. Also, I hope the lines
will be a sane length. This is the first time I've sent a message to
this list using Thunderbird.
12 years, 8 months
RE: Network printer not working, how to debug?
by R. G. Newbury
On 09/13/2011 02:29 PM, Tim wrote:
> On Tue, 2011-09-13 at 09:54 -0400, R. G. Newbury wrote:
>> > I have a Brother MFC665CW connected wirelessly. I installed the cups and
>> > lpd driver rpms from the Brother site, and run a cups service on the
>> > computers which use that printer.
>> >
>> > The URI for the printer is: usb:/dev/usb/lp0
> That's the URI for a*locally*-connected printer, not a
> wirelessly-connected one.
>
> Tim.
As I said, Tim, *why* that URI I have no idea. That printer has NEVER
been connected with a wire of any sort ehternet OR parallel port. I
configured it using the front panel, it showed up in the router and I
could ping it, etc. so I installed the drivers and it worked.
The *only* possible scenario that I can think of, is that the local (on
the laptop) cupswrapper driver daemon writes *there* and the brother lpr
driver uses that as a socket and sends the print job on to the printer
using wifi.
So it appears to be a locally connected printer because the drivers
obscure the 'unconnectedness' of it.
This same sort of thing shows up when connecting network printers to a
guest WinXP instance in virtualbox. An HP printer connected through a
lpd/lpr print server is 'installed' in the WinXP guest as a 'network'
printer using the 'http://IP-address/pASTHRU', while an HP MFC (using
hplip) is selected as a LOCAL printer in the WinXP guest install using a
TCPIP 'port': socket://ip-address/:9100.
I have never tried to install the Brother MFC into the Win guest, but I
think it would be a 'network' printer.
Geoff
12 years, 8 months
RE: Network printer not working, how to debug?
by R. G. Newbury
On Sat, 2011-09-10 at 11:55 -0700, Gordon
> Charrick wrote:
>> > I click the Network Printer dropdown under "Select Device" and the
>> > printer shows up with the proper IP address. Under "Connection", "IPP
>> > network printer via DNS-SD" is selected. I choose the driver and apply
>> > the settings. It prompts to print a test page and I click to print it.
>> > The job for the test page is submitted and a window with the settings
>> > shows up and the Printer State shows as "Stopped - Destination printer
>> > does not exist!". The Device URI is
>> > "dnssd://Brother%20MFC-7860DW._ipp._tcp.local/".
> Try using a different Device URI. The error you're getting is because
> the device URI doesn't include a queue name (because it couldn't be
> detected, I suppose).
>
> You may be able to find out the default queue name by visiting the
> printer's web server (if it has one built-in), or by consulting the
> printer's documentation.
I have a Brother MFC665CW connected wirelessly. I installed the cups and
lpd driver rpms from the Brother site, and run a cups service on the
computers which use that printer.
The URI for the printer is: usb:/dev/usb/lp0
Why that URI I have no idea. I expected something like
lpd:/192.168.2.10/PASSTHRU but the usb URI is what the install injected.
And it works. This printer also works with a Macbook Air but I have NO
present recollection of doing the install process. It must have been
automagic since I cannot recall it at all.
Geoff
12 years, 8 months
Xephyr nested X-server seems to ignore backing store option
by Doug Kuvaas
I have been trying to use Xephyr for running an old legacy application that
doesn't function properly at color depths greater than 8 bit. I have been
exploring this as a possible alternative to running X in 8-bit color mode,
primarily because X does not seem to work properly in 8 bit color mode
anymore. I get a grayscale display instead of 8-bit color. Xephyr seems to
work perfectly for what I want to do, with the exception of the backing
store. I am running Xephyr with the options +bs -wm, however when I open a
menu on the legacy application or move some other screen object, the screen
behind it ends up either staying black or certain elements going missing
until I do something that causes the entire display to be re-drawn. While
re-writing the portions of the application that don't play nice with color
depths beyond 8 bits, I would like to get this working without requiring
updating our software if possible as we have many different locations using
their own customized versions.
I have verified that the backing store option does work for Xorg, both if I
run Fedora normally, that is load Gnome and use that as a display manager,
and if I just start Xorg manually with no display managers.
Any insights or help on getting this working would be appreciated.
Thanks in advance,
Doug K
12 years, 8 months
Re: F15, diskless node, systemctl start tmpfs.device timeout
by Xiao Peng Wang
Robert,
I don't know what I should do to test the var-run-tmpfs. At least I can
touch file in the /var/tmp/.
The service 'NetworkManager-wait-online.service' was not installed on the
diskless node. But I found a way to boot the sshd, so I think it was not a
network issue.
Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: wxp(a)cn.ibm.com
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road,
Haidian District Beijing P.R.China 100193
2011/9/5 Xiao Peng Wang <wxp@xxxxxxxxxx>:
> Hi,
>
> I made a diskless image against Fedora15, during the boot I found it
> displayed the following error message and went into emergency mode.
>
Not 100% sure but take a look at this
http://fedoraproject.org/wiki/Features/var-run-tmpfs
and also try
systemctl enable NetworkManager-wait-online.service
PS please send posts to the mailing list in plain text
--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Canada
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
12 years, 8 months
F15, diskless node, systemctl start tmpfs.device timeout
by Xiao Peng Wang
Hi,
I made a diskless image against Fedora15, during the boot I found it
displayed the following error message and went into emergency mode.
The error message:
Starting Relabel all filesystems, if necessary ^[[1;31maborted^[[0m
because a dependency failed.
[ 107.607155] systemd[1]: Job fedora-autorelabel.service/start failed
with result 'dependency'.
Starting Mark the need to relabel after reboot ^[[1;31maborted^[[0m
because a dependency failed.
[ 107.625156] systemd[1]: Job fedora-autorelabel-mark.service/start
failed with result 'dependency'.
[ 107.634580] systemd[1]: Job local-fs.target/start failed with
result 'dependency'.
[ 107.642615] systemd[1]: Triggering OnFailure= dependencies of
local-fs.target.
[ 107.650738] systemd[1]: Job var-tmp.mount/start failed with result
'dependency'.
[ 107.658580] systemd[1]: Job fsck(a)tmpfs.service/start failed with
result 'dependency'.
[ 107.666876] systemd[1]: Job tmpfs.device/start failed with result
'timeout'.
Welcome to emergency mode. Use "systemctl default" or ^D to activate
default mode.
And when I run the command 'service sshd start' to start the sshd, it
displayed the following error message:
[ 8545.884404] udev[2872]: starting version 167
[ 8635.560123] systemd[1]: Job tmpfs.device/start timed out.
[ 8635.565867] systemd[1]: Job fedora-autorelabel.service/start
failed with result 'dependency'.
[ 8635.574812] systemd[1]: Job fedora-autorelabel-mark.service/start
failed with result 'dependency'.
[ 8635.584217] systemd[1]: Job local-fs.target/start failed with
result 'dependency'.
[ 8635.592203] systemd[1]: Triggering OnFailure= dependencies of
local-fs.target.
[ 8635.600311] systemd[1]: Job var-tmp.mount/start failed with result
'dependency'.
[ 8635.608102] systemd[1]: Job fsck(a)tmpfs.service/start failed with
result 'dependency'.
[ 8635.616355] systemd[1]: Job tmpfs.device/start failed with result
'timeout'.
Welcome to emergency mode. Use "systemctl default" or ^D to activate
default mode.
Then I tried to start the tmpfs.device
# systemctl start tmpfs.device
[432039.543362] systemd[1]: Job tmpfs.device/start timed out.
[432039.549335] systemdJob timed out.
Looks like the tmpfs.device was not installed. Did I miss something
that depended by system? Any comments are appreciated.
Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: wxp(a)cn.ibm.com
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road,
Haidian District Beijing P.R.China 100193
12 years, 8 months
Custom init scripts and systemd
by Alex Thomas
Hello I use an older Thinkpad R32 as my primary linux machine. I use it
primarily for web / email / chat while working or gaming on main machine.
Since it did not come with an internal wifi card, I have to use the pc card
port. This has always been interesting because if I did not have an
explicit pccard eject script on run on shutdown it would reboot instead of
power off. What is the correct way to do this with systemd?
Alex Thomas
12 years, 8 months
SL6 epel garmin 18 lvc serial port pps kernel trace
by Skunk Worx
Hi everyone,
I have two Mini-ITX Intel mobos I am using as ntpd time servers with a
Garmin LVC 18 serial port GPS that provides a PPS input.
I've had good luck with this unit and gpsd in the past, but I get a
kernel call trace if I run "setserial" then the "shmpps" daemon.
Here is the info -- if anyone has comments or suggestions I'd appreciate
it. I'll probably switch back to gpsd later this week if not.
Repeatable with i686 or x86_64 SL6.
1) Use Intel D945GCLF Atom 230 Mini-ITX mobo
2) Use Garmin 18x LVC gps wired for serial port w/ PPS on DCD pin
3) Install SL6 and "shmpps" EPEL package
4) Boot SL6 2.6.32-131.12.1.el6.x86_64.debug kernel into single user mode
5) Start rsyslog service
6) Note dmesg serial info :
# dmesg | grep serial
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
7) Run setserial command :
/bin/setserial /dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base
115200 spd_normal skip_test low_latency
8) Run shmpps in debug mode :
/usr/sbin/shm_splc2 -d /dev/ttyS0 -s -u 0 -l DCD -D
The following depends on the setserial command being run and having the
garmin plugged into the serial port. The call trace is emitted at
roughly the same rate as the NMEA strings from the garmin.
BUG: sleeping function called from invalid context at kernel/mutex.c:287
in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper
INFO: lockdep is turned off.
irq event stamp: 827450
hardirqs last enabled at (827449): [<ffffffff812e36e1>]
intel_idle+0xe1/0x170
hardirqs last disabled at (827450): [<ffffffff8100afaa>] save_args+0x6a/0x70
softirqs last enabled at (827440): [<ffffffff8107403a>]
__do_softirq+0x14a/0x200
softirqs last disabled at (827415): [<ffffffff8100c38c>]
call_softirq+0x1c/0x30
Pid: 0, comm: swapper Not tainted 2.6.32-131.12.1.el6.x86_64.debug #1
Call Trace:
<IRQ> [<ffffffff810a7d60>] ? print_irqtrace_events+0xd0/0xe0
[<ffffffff81056027>] ? __might_sleep+0xf7/0x130
[<ffffffff8150cb2f>] ? mutex_lock_nested+0x2f/0x60
[<ffffffff8132cf80>] ? process_output+0x30/0x70
[<ffffffff8132f058>] ? n_tty_receive_buf+0x618/0x1290
[<ffffffff810aa332>] ? print_lock_contention_bug+0x22/0xf0
[<ffffffff810aa332>] ? print_lock_contention_bug+0x22/0xf0
[<ffffffff81332723>] ? flush_to_ldisc+0x43/0x1b0
[<ffffffff81332863>] ? flush_to_ldisc+0x183/0x1b0
[<ffffffff8133290c>] ? tty_flip_buffer_push+0x7c/0x90
[<ffffffff8135e0e5>] ? serial8250_handle_port+0x215/0x350
[<ffffffff8135e2ab>] ? serial8250_interrupt+0x8b/0x120
[<ffffffff810e9370>] ? handle_IRQ_event+0x50/0x160
[<ffffffff810ebaf8>] ? handle_edge_irq+0xc8/0x160
[<ffffffff8100e0d9>] ? handle_irq+0x49/0xa0
[<ffffffff8151497c>] ? do_IRQ+0x6c/0xf0
[<ffffffff8100bb13>] ? ret_from_intr+0x0/0x16
<EOI> [<ffffffff812e36e1>] ? intel_idle+0xe1/0x170
[<ffffffff812e36e8>] ? intel_idle+0xe8/0x170
[<ffffffff812e36e1>] ? intel_idle+0xe1/0x170
[<ffffffff815120a0>] ? __atomic_notifier_call_chain+0x0/0xa0
[<ffffffff81417787>] ? cpuidle_idle_call+0xa7/0x150
[<ffffffff81009e8b>] ? cpu_idle+0xbb/0x110
[<ffffffff814f298a>] ? rest_init+0x7a/0x80
[<ffffffff81b69f59>] ? start_kernel+0x44f/0x45b
[<ffffffff81b6933a>] ? x86_64_start_reservations+0x125/0x129
[<ffffffff81b69438>] ? x86_64_start_kernel+0xfa/0x109
ttyS0: 1 input overrun(s)
Thanks,
John
12 years, 8 months
