Re: [Ifp-driver-common] Problems connecting to iRiver IFP899

[Peter B. <pet...@gm...>]

Jim,

I have removed libifp completely, but the problem remains. Absolutely
nothing changed.

By the way, I realized that I need to install Debian's libifp-dev
package to make the "libifp not found" message go away. This, however,
results in a segementation fault when ifpgui is starting up. (That is
probably the reason why you say version 1.0.0.2 is needed.)

Seems like I need to build the latest libifp from the sources to get
ifpgui to work.

Cheers, Peter


2006/2/23, Jim <jdc...@gm...>:
> you will need libifp 1.0.0.2 with ifpgui.  If you cannot get it or
> compile it then completely remove libifp 1.0.0.1-2.  ifpgui has the
> latest libifp functions and will work just fine without libifp.
>
> Thanks
> Jim
>
> Peter Bittner wrote:
> > Hi!
> >
> > I'm using ifpgui to access my iRiver IFP899. This worked fine on SuSE
> > a year ago, but on my new Kubuntu Linux box the application tells me
> > it cannot connect to the iRiver device (though the iRiver display
> > itself and the output of lsusb shows that it is connected).
> >
> > When I start the application as root (kdesu ifpgui) the application
> > complains, but at least some of the content on the device is shown
> > anyway after startup.
> >
> > The problem doesn't seem to be ifpgui though. I have tested access to
> > the device using the ifp-line command line tool (Debian package
> > ifp-line-libifp) and I get the same results: Connecting as an
> > unprivileged user is not possible at all, as root (sudo ifp-line) it
> > works, but only parts of the actual content on the iRiver device are
> > shown.
> >
> > * Here is my setup:
> >
> > - Kubuntu Breezy (a Debian distro)
> > - libifp 1.0.0.1-2
> > - libusb 0.1.10a-17ubuntu1
> >
> > * Here is the output of an access a a normal user:
> >
> > tania@vienna:~$ ifpgui
> >  libifp.so: Kann die Shared-Object-Datei nicht =F6ffnen: Datei oder Ver=
zeichnis
> >  nicht gefunden
> >  Device is busy.  (I was unable to claim its interface.)
> >  ifp Device NOT found
> >  libifp.so: Kann die Shared-Object-Datei nicht =F6ffnen: Datei oder Ver=
zeichnis
> >  nicht gefunden
> >  Device is busy.  (I was unable to claim its interface.)
> >  ifp Device NOT found
> >
> >  (Translation: libifp complains that a Shared-Object-File cannot be
> > opened: File or Directory not found)
> >
> > * This is the output of an access as root:
> >
> > tania@vienna:~$ kdesu ifpgui
> >  libifp.so: Kann die Shared-Object-Datei nicht =F6ffnen: Datei oder Ver=
zeichnis
> >  nicht gefunden
> >  err:  [local_iconv] err=3D-84. problem converting, i_n is 15, o_n is 1=
004, r =3D
> >  -1
> >  err:  [ifp_locale_to_utf16] err=3D-84. conversion failed
> >  err:  [_ifp_push_unicode] err=3D-84. character conversion failed
> >  err:  [ifp_dir_open] err=3D-84. push failed
> >  err:  [ifp_is_dir] err=3D-84. dir.open failed
> >  err:  [ifp_exists] err=3D-84. dir checking failed
> >  Could not communicate with iRiver device.
> >  Try unplugging the USB link, powering off the device, and plugging it =
back in.
> >
> > The problem apparently seems to be in the libifp domain. How can I fix
> > this problem?
> > Peter
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting lang=
uage
> > that extends applications into web and mobile media. Attend the live we=
bcast
> > and join the prime developer group breaking into this new coding territ=
ory!
> > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=110944&bid$1720&dat=121642
> > _______________________________________________
> > Ifp-driver-common mailing list
> > Ifp...@li...
> > https://lists.sourceforge.net/lists/listinfo/ifp-driver-common
> >
> >
>


--
DI Peter Bittner