Bug 508047

I tanked something when I was porting the initscript patches from patching upstream's lsb initscripts to patching upstream's rpm initscripts. The LCDd initscript is failing because there's a check for '-x bindir/LCDd', which is supposed to be '-x sbindir/LCDd'. I fixed that locally, and my imonlcd device fired up correctly. I suspect the same will be the case for you, and calling just 'LCDd -f' might not be providing enough info to bring up your display -- i.e., it needs something from your LCDd.conf file too... I'll push a new build w/the initscript fix, but if you could confirm that tiny change works for you too, it would be much appreciated.

Jarold,

fixed the initscript, still same message in syslog than what I got starting LCDd manually.

As the initscript problem is known and you're pushing a new build, should we take the hd44780 with bwct connection type error to the lcdproc mailinglist?

(In reply to comment #2)
> fixed the initscript, still same message in syslog than what I got starting
> LCDd manually.
> 
> As the initscript problem is known and you're pushing a new build, should we
> take the hd44780 with bwct connection type error to the lcdproc mailinglist?  

Damn, I was holding off on the update, hoping this would fix all your problems. I'll go ahead push it for the benefit of the initscript fix though.

Yeah, probably best to hit up the lcdproc list, Markus or someone else w/an hd44780 device might have some ideas. Outside of the imonlcd driver, I know relatively little about lcdproc internals myself...

agh, my bad, this fell off the deep end here.
Will try to do this next week.

done; http://lists.omnipotent.net/pipermail/lcdproc/2009-August/013032.html

Hmm, no answer on the list in 10 days. I hope I am not the only remaining user of this display.

Questions to Jarod;
  - have any other lcdproc users reported success with the 0.5.3-1.fc12 package?
  - any hints from you on how to debug my display further?

RU

PCFE

(In reply to comment #6)
> Hmm, no answer on the list in 10 days. I hope I am not the only remaining user
> of this display.

Yeah, the list has been dead-silent of late... Its like 0.5.3 went out the door, and everyone decided to go on vacation... :(

> Questions to Jarod;
>   - have any other lcdproc users reported success with the 0.5.3-1.fc12
> package?

Several SoundGraph iMON display users have reported success, not sure I've heard from anyone beyond that. I know 0.5.3 was tested successfully with a number of displays upstream, but I don't know offhand which ones.

>   - any hints from you on how to debug my display further?

Not really. I'm not particularly familiar with the lcdproc code, I just worked on the package a bit to make sure the iMON displays were working.

Jarod,

send a bump to my old list message. amybe someone on the list can give hints this time.

RU

PCFE

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Is this bug still experienced with the lastest update ?

With lcdproc-0.5.3-5.fc14.x86_64 from rawhide
                                                           [FAILED]
Apr 24 11:18:15 morn kernel: usb 5-2: new full speed USB device using uhci_hcd and address 3
Apr 24 11:18:15 morn kernel: usb 5-2: New USB device found, idVendor=03da, idProduct=0002
Apr 24 11:18:15 morn kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 24 11:18:15 morn kernel: usb 5-2: Product: LCD Adapter
Apr 24 11:18:15 morn kernel: usb 5-2: Manufacturer: BWCT
Apr 24 11:18:15 morn kernel: usb 5-2: SerialNumber: 1100891496
Apr 24 11:18:15 morn kernel: usb 5-2: configuration #1 chosen from 1 choice

[root@morn ~]# /etc/init.d/LCDd start
Starting LCDd service: hd_init_bwct_usb: interface may be claimed by kernel driver, attempting to detach it
hd_init_bwct_usb: unable to re-claim interface: No route to host
Driver [hd44780] init failed, return code -1
Could not load driver hd44780
There is no output driver
Critical error while initializing, abort.

This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Can you verify if the problem still exist with lcdproc-0.5.5 on F-15 or later.

Seems still present (config file copied from my F14 filesystem)

LCDd -c /etc/sysconfig/lcdproc/LCDd.conf -f
LCDd 0.5.4, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2010 William Ferrell, Scott Scriven
                        and many other contributors

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

hd_init_bwct_usb: interface may be claimed by kernel driver, attempting to detach it
hd_init_bwct_usb: unable to re-claim interface: Numerical result out of range
Driver [hd44780] init failed, return code -1
Could not load driver hd44780
There is no output driver
Critical error while initializing, abort.


# rpm -q fedora-release lcdproc
fedora-release-16-1.noarch
lcdproc-0.5.4-1.fc16.x86_64

if you tell me which 0.5.5 to grab, I'll gladly test that too.

It's available in updates-testing.
(Please also have a look on #712782 since you are on x86_64).

# LCDd -c /etc/sysconfig/lcdproc/LCDd.conf -f
LCDd 0.5.5, LCDproc Protocol 0.3
Part of the LCDproc suite
Copyright (C) 1998-2010 William Ferrell, Selene Scriven
                        and many other contributors

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

hd_init_bwct_usb: interface may be claimed by kernel driver, attempting to detach it
hd_init_bwct_usb: unable to re-claim interface: Numerical result out of range
Driver [hd44780] init failed, return code -1
Could not load driver hd44780
There is no output driver
Critical error while initializing, abort.

# rpm -q fedora-release lcdproc
fedora-release-16-1.noarch
lcdproc-0.5.5-1.fc16.x86_64

# grep DriverPath /etc/sysconfig/lcdproc/LCDd.conf
DriverPath=/usr/lib64/lcdproc/

# ls -lZ /usr/lib64/lcdproc/hd44780.so 
-rwxr-xr-x. root root system_u:object_r:lib_t:s0       /usr/lib64/lcdproc/hd44780.so

Do you have reported the problem upstream ?
Sounds like a diff between the different release would help.

(In reply to comment #18)
> Do you have reported the problem upstream ?

Yes, see Comment #5

> Sounds like a diff between the different release would help.

Will you or do you want me to? (I'll probably be on the road for the next couple weeks, so it will take a while until I get to this.)

Seeing that there I might be one of the only users of this LCD and that I have others to use instead, we can also close this WONTFIX

Here is a scratch build of lcdproc 0.5.6 for f17
http://koji.fedoraproject.org/koji/taskinfo?taskID=4843177
I only to update on f18, please verify if it works for your case on this release.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

(In reply to comment #20)
> Here is a scratch build of lcdproc 0.5.6 for f17
> http://koji.fedoraproject.org/koji/taskinfo?taskID=4843177
> I only to update on f18, please verify if it works for your case on this
> release.

Apologies, I was on vacation and the scratch build seems to have expired. Could I ask you to scratchbuild again please?

Resubmitted for f17 scratch build
http://koji.fedoraproject.org/koji/taskinfo?taskID=4893112

still fails the same way; # systemctl status LCDd
LCDd.service - LCDd Service
	  Loaded: loaded (/usr/lib/systemd/system/LCDd.service; disabled)
	  Active: failed (Result: exit-code) since Wed 2013-01-23 12:28:50 CET; 26s ago
	 Process: 27813 ExecStart=/usr/sbin/LCDd -c /etc/lcdproc/LCDd.conf (code=exited, status=1/FAILURE)

Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: hd_init_bwct_usb: interface may be claimed by kernel driver, attempting to detach it
Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: hd_init_bwct_usb: unable to re-claim interface: Numerical result out of range
Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: Driver [hd44780] init failed, return code -1
Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: Could not load driver hd44780
Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: There is no output driver
Jan 23 12:28:50 morn.internal.pcfe.net LCDd[27813]: Critical error while initializing, abort.
Jan 23 12:28:50 morn.internal.pcfe.net systemd[1]: LCDd.service: control process exited, code=exited status=1
Jan 23 12:28:50 morn.internal.pcfe.net systemd[1]: Failed to start LCDd Service.
Jan 23 12:28:50 morn.internal.pcfe.net systemd[1]: Unit LCDd.service entered failed state

this is on F18 x86_64 with a mock rebuild of the package from comment 23 (I installed F18 on the affected box yesterday)

But, seeing that apart, from me, no one seems to have noticed this bug, and I only use this LCD as a toy and, most importantly, we're not getting anything from upstream, I suggest to simply do CLOSED WONTFIX

(In reply to comment #24)
..
> 
> But, seeing that apart, from me, no one seems to have noticed this bug, and
> I only use this LCD as a toy and, most importantly, we're not getting
> anything from upstream, I suggest to simply do CLOSED WONTFIX

I personally had an answer from a recent patch I forwarded to lcdproc upstream. 
But I expect it will be better if you can make a diff between the last release that worked and the next one for the code of your driver.

Obviously this is an upstream issue, so an upstream ticket need to be made.

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.