Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is where the hotplug support is needed. First, try running ifp_gui as root. If that works, great. Otherwise I'll need more info. Specifically, the output of /usr/sbin/lsusb (or the output of "cat /proc/bus/usb/devices|fgrep 4102"). What we're looking for is that the device is coming up on the usb bus. 4102 is the vender ID. The next number we're interested in is the device id.
My system produces the following (I truncated irrelevant devices):
[tobind@razman ~]$ /usr/sbin/lsusb
Bus 004 Device 013: ID 4102:1007
IF yours isn't in the list of devices added to /etc/hotplug/usb.map, then you will unfortunately have to wait for it to be added. The good news is that I can add it and send you a special build to test. If it works, we can request it to be added to the main code stream.
First step, though is to see if ifp_gui works as root, and if not, what device id is ifp_gui looking for.
linux:~ # ifp_gui
ifp Device NOT found
info: ignoring device with UMS firmware.
ifp Device NOT found
Basically I got the message that I needed to plug in my device and when I did that I got the same error message as before.
Also, I get this:
linux:~ # /usr/sbin/lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 03f0:2b11 Hewlett-Packard
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
and typing in "cat /proc/bus/usb/devices|fgrep 4102" results in nothing. So I guess this means my device is not supported?
It would be truly wonderful if you'd take the time to add it and send me a test build. :)
It doesn't appear to be visible, unless it is showing up as the 03f0:2b11 Hewlett-Packard device. Do you have any other device plugged in?
If that is the device, I can add it to the ifp_gui to test, but I want to make sure it's the only usb device physically plugged in. Here's a couple of tests to run. First unplug it, then type "lsusb" along with "dmesg|tail". Next, plug it in, and repeat those two commands. Send me the output of both.
From what I've been able to dig up on the net, it may be crippled in North America and Europe, in that it can only communicate with Windows Media Player 10. I've seen conflicting information, so I want to be sure.
If this is true, then this is another example of Microsoft exploiting their monopolistic might. How I really hate our corporate government for allowing this.
Ok, I added the ID to the ifp_gui program and built it (super easy). Not sure how to get it to you, though. Reply if you have a suggestion, otherwise, download the source code (http://prdownloads.sourceforge.net/i...ar.gz?download), open it in a temporary directory (tar -zxvf ifp_gui-0.10.4.tar.gz), and get ready for a single line edit.
To modify the code, do the following (don't type my # comments) :
:24 # this will jump down to the line we want to copy/modify
yy # copies current line into the buffer
p # pastes buffer
R # enter "replace/Overwrite mode"
# use the arrow keys to move the cursor and replace 1011 with 1119
:wq # save and exit
cd ../../ # return to the head of the source tree
./build.sh # rebuild. with any luck, it should finish without error, and you'll have a new version of ifp_gui in the ./bin directory.
Like I said earlier, I have a built version that I can send you if you don't want to do this. Since I don't have this particular player, I'm not sure it will work, but it's worth a shot.
At this stage, I think that we have explored all we can with this unit. I suggest either returning the unit and getting an older IFP-7xx, or if you would like to help getting it working, join the email at ifp-driver-common AT lists.sourceforge.net. You might be able to provide them with some useful information that they can use to build a working ifp_gui version.
Sorry I couldn't help further. Microsoft/DRM seems to be getting in the way.
1) In SuSE 10, I have found that you do not need to run the nonroot.sh script.
2) Typically, I unplug my iRiver, turn it off, and wait about 3 seconds.
Then, I will plug in the USB cable, turn it on, and wait about 3 seconds.
Finally, start ifp_gui.
If you have a device that is supported you will see the battery status, storage used, and files appear in the application.
(Assuming you have the ifp_gui package installed)
To start ifp_gui just type ifp_gui. If this does not work, try /usr/local/bin/ifp_gui
Thanks for your input. It turns out though that my device is not supported. GrueMaster even made a new build of ifp_gui but it seems the T30 is made not to function with anything else than Windows Media Player 10. I had a look at ifp_gui though and it seems really nice. :) It's a pity I can't use it.