Todd Walton wrote:
On Fri, 23 Sep 2005 15:43:50, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Help! Please?
Did you get any buffer I/O errors on the device?
I don't know what to do next.
I understand your sarcasm. But I don't know what the errors mean. Is
it possible that the pc or usb is faulty? Or is it certain that the
ipod is the problem? Can it be fixed? My friend's son got the ipod for
his birthday over three months ago [1]. Initially, I couldn't get it to
work on Linux (rh9). He took it to his uncle's house who has a version
of windows that was able to run the setup software that came with it.
He put some lame music on as a test. It worked.
Back on rh9 at home, I was able to mount it, erase the lame music and
put on some other music. But when he went to listen to it, it would
jump almost instantly from one song to the next. It would skip across
all 14 songs in about 10 seconds or so. I mounted it back on rh9, and
had no problems accessing the songs and playing them through the pc.
But no matter what I did, the ipod would not play them correctly.
I figured it may have been a problem with the version of gtkpod I was
using. I initially installed the version for rh9, but it would not work
at all. Then I tried the version for fc4, then fc3, then fc2, with each
one giving the same error from looking for something it couldn't find.
Finally I installed the version for fc1, and it is the version that gave
me what I described in the previous paragraph.
So then I upgraded from rh9 to fc3. (I didn't go straight to fc4
because I was having problems with fc4.) I upgraded gtkpod to the fc3
version. But then I couldn't even see the ipod out there, not with
fdisk, not even with dmesg. But since it had been a while since it had
been plugged in, the battery was charging and I figured that maybe that
had something to do with it. Later, after the battery had finished
charging, dmesg started seeing it, but with errors. I just found out
that the pc has been locking up the last couple of days. (The
description doesn't get any better than that.) I haven't even had the
chance to take a peek to find out why.
"fdisk" doesn't want to touch it. I don't know what to do next.
[1] Various things contributed to the three month delay. There were
delays getting fc4. There were problems with my testing of fc4. There
were delays getting fc3. There was the issue of the builtin media test
of fc3 saying it was bad. There were delays getting an fc3
replacement. The testing said the same thing. There was the kplug
discussion telling me that the install is a better test. And so on.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
