Hi,
When trying to use the BWCT USB device (http://www.bwct.de/lcd.html), LCDd won't start correctly, even when running it as root:
Log says:
Jun 1 23:12:29 raspbmc LCDd: LCDd version 0.5.5 starting
Jun 1 23:12:29 raspbmc LCDd: Using Configuration File: /etc/LCDd.conf
Jun 1 23:12:29 raspbmc LCDd: Listening for queries on 127.0.0.1:13666
Jun 1 23:12:29 raspbmc LCDd: hd_init_bwct_usb: interface may be claimed by kernel driver, attempting to detach it
Jun 1 23:12:29 raspbmc LCDd: hd_init_bwct_usb: unable to re-claim interface: No route to host
Jun 1 23:12:29 raspbmc LCDd: Driver [hd44780] init failed, return code -1
Jun 1 23:12:29 raspbmc LCDd: Could not load driver hd44780
Jun 1 23:12:29 raspbmc LCDd: There is no output driver
Jun 1 23:12:29 raspbmc LCDd: Critical error while initializing, abort.
The section in LCDd.conf:
##HitachiHD44780driver##[hd44780]#Selectwhattypeofconnection.Seedocumentationfortypes.ConnectionType=bwctusb#PortwheretheLPTis.Usualvalueare:0x278,0x378and0x3BC#Port=0x378#Deviceoftheserialinterface[default:/dev/lcd]#Device=/dev/ttyS0#Bitrateoftheserialport(0forinterfacedefault)Speed=0#Ifyouhaveakeypadconnected.#Youmayalsoneedtoconfigurethekeypadlayoutfurtheroninthisfile.Keypad=no#Settheinitialcontrast(bwctusbandlcd2usb)[default:500;legal:0-1000]Contrast=0#Setbrightnessofthebacklight(lcd2usbonly)[default:0;legal:0-1000]#Brightness=1000#OffBrightness=0#Ifyouhaveaswitchablebacklight.Backlight=no#Ifyouhavetheadditionaloutputport("bargraph")andyouwantto#beabletocontrolitwiththelcdprocOUTPUTcommandOutputPort=no#Specifiesifthelastlineispixeladdressable(yes)oritcontrolsan#underlineeffect(no).[default:yes;legal:yes,no]#Lastline=yes#SpecifiesthesizeoftheLCD.#Incaseofmultiplecombineddisplays,thisshouldbethetotalsize.Size=16x2#Formultiplecombineddisplays:howmanylinesdoeseachdisplayhave.#Vspan=2,2meansbothdisplayshave2lines.#vspan=2,2#IfyouhaveanHD66712,aKS0073oranother'almost HD44780-compatible',#setthisflagtogetintoextendedmode(4-linelinear).ExtendedMode=yes#Inextendedmode,onsomecontrollersliketheST7036(in3linemode)#thenextlineinDDRAMwon't start 0x20 higher. [default:0x20]#LineAddress=0x10# Character map to to map ISO-8859-1 to the LCD'scharacterset#[default:hd44780_default;legal:hd44780_default,hd44780_euro,ea_ks0073,#sed1278f_0b,hd44780_koi8_r,hd44780_cp1251,hd44780_8859_5,upd16314]#(hd44780_koi8_r,hd44780_cp1251,hd44780_8859_5andupd16314arepossibleif#compiledwithadditionalcharmaps)CharMap=hd44780_default#Ifyourdisplayisslowandcannotkeepupwiththeflowofdatafrom#LCDd,garbagecanappearontheLCDd.Setthisdelayfactorto2or4#toincreasethedelays.Default:1.#DelayMult=2#Somedisplays(e.g.vdr-wakeup)needamessagefromthedrivertothatit#isstillalive.Whensettoavaluebiggerthennullthecharacterinthe#upperleftcornerisupdatedevery<KeepAliveDisplay>seconds.Default:0.KeepAliveDisplay=2#Ifyouexperienceoccasionalgarbageonyourdisplayyoucanusethis#optionasworkaround.Ifsettoavaluebiggerthannullitforcesa#fullscreenrefresh<RefreshDiplay>seconds.Default:0.#RefreshDisplay=5#Youcanreducetheinserteddelaysbysettingthistofalse.#OnfastPCsitispossibleyourLCDdoesnotrespondcorrectly.#Default:true.DelayBus=false#Ifyouhaveakeypadyoucanassignkeystringstothekeys.#Seedocumentationforusedtermsandhowtowireit.#Forexampletogivedirectlyconnectedkey4thestring"Enter",use:#KeyDirect_4=Enter#FormatrixkeysusetheXandYcoordinatesofthekey:#KeyMatrix_1_3=EnterKeyMatrix_4_1=EnterKeyMatrix_4_2=UpKeyMatrix_4_3=DownKeyMatrix_4_4=EscapeSerialNumber=1297257800
For the record:
Found out that "usb_claim_interface" libusb call in the driver (server/drivers/hd44780-bwct-usb.c) always fails with error code -2, even if the display can be used normally - I managed to get it work by simply ignoring that error (remvoing the error checks in hd44780-bwct-usb.c and recompile lcdproc), but this certainly is very dirty :).
Hi,
When trying to use the BWCT USB device (http://www.bwct.de/lcd.html), LCDd won't start correctly, even when running it as root:
Log says:
The section in LCDd.conf:
Any ideas? A bug in Fedora 16 (https://bugzilla.redhat.com/show_bug.cgi?id=508047) looks like the same problem, but it was closed without fixing.
Thank you for your help,
Best regards,
Joerg
For the record:
Found out that "usb_claim_interface" libusb call in the driver (server/drivers/hd44780-bwct-usb.c) always fails with error code -2, even if the display can be used normally - I managed to get it work by simply ignoring that error (remvoing the error checks in hd44780-bwct-usb.c and recompile lcdproc), but this certainly is very dirty :).
I submitted a bug to deal with this issue (https://sourceforge.net/p/lcdproc/bugs/44/), maybe someone has an idea to solve it properly.