On Fri, Oct 20, 2006 at 08:42:21AM -0400, Ed Smits wrote: > It's an iPod Nano that worked fine with the previous kernel and app's. > I'm a newbie and so can't tell you exactly what I had before (it > worked, why would I record it<G>) - all I know was that it was running > 2.6.17 and all upgrades were in place. When 2.6.18 came out I decided > to redo my partitions (bad initial planning) so saved /home to an > external drive, blew everything away and installed again, upgrading > straight to 2.6.18 from 2.6.15, installed Amerok and gtkpod etc, at > present the yum gui tells me I have no updates available. > > If I run gtkpod, mount the iPod, and try to sync it I get the > following error message from gtkpod: > > '/media/disk/iPod_Control/iTunes/iTunesDB' does not exist. Import aborted > > It does exist... > > If I run gtkpod with the iPod already mounted it fails immediately, > the only error is "segmentation fault" I got the same result. My mini worked fine, but the nano did not (gtkpod simply seg faulted). Is it possible that you upgraded your nano with iTunes somewhere in there? While I was researching my nano troubles, I found references that it's not the newer iPods as much as the newer firmware on them. I got around this by copying a modified SysInfo from my mini. Here's what my SysInfo has (put your serial number in from the back of your iPod): BoardHwName: iPod Q22 pszSerialNumber: XX999XXXX9X ModelNumStr: M9436 FirewireGuid: 0x007AEC00 HddFirmwareRev: DN4ACA2A RegionCode: LL(0x0001) PolicyFlags: 0x00000000 buildID: 0x02308000 (2.3) visibleBuildID: 0x01108000 (1.1) boardHwRev: 0x00000000 (0.0 0) boardHwSwInterfaceRev: 0x00040012 (0.0.4 18) bootLoaderImageRev: 0x00000000 (0.0 0) diskModeImageRev: 0x00000000 (0.0 0) diagImageRev: 0x00000000 (0.0 0) osImageRev: 0x00000000 (0.0 0) iPodFamily: 0x00000003 updaterFamily: 0x00000003 Another, perhaps better (if it works) method is to use the current CVS versions of libgpod, etc. as someone else mentioned in this thread. Thanks, Jamie > > as to which versions I have at present: > > libgpod-0.3.0-2.2 > gtkpod-0.99.4-1.lvn5 > amarok-1.4.3-6.fc5 > > Where I got them - standard repositories I assume, I don't know enough > to be grabbing from funky ones. I assume the gtkpod was from Livna, > could that be a problem? > > My message logs around that time show the following: > > Oct 20 08:06:03 ca-esmits kernel: usb 1-6.2: USB disconnect, address 7 > Oct 20 08:06:09 ca-esmits kernel: usb 1-6.2: new high speed USB device > using ehci_hcd and address 8 > Oct 20 08:06:09 ca-esmits kernel: usb 1-6.2: configuration #1 chosen > from 2 choices > Oct 20 08:06:09 ca-esmits kernel: scsi3 : SCSI emulation for USB Mass > Storage devices > Oct 20 08:06:10 ca-esmits kernel: usb 1-6.2: USB disconnect, address 8 > Oct 20 08:06:19 ca-esmits kernel: usb 1-6.2: new high speed USB device > using ehci_hcd and address 9 > Oct 20 08:06:19 ca-esmits kernel: usb 1-6.2: configuration #1 chosen > from 2 choices > Oct 20 08:06:19 ca-esmits kernel: scsi4 : SCSI emulation for USB Mass > Storage devices > Oct 20 08:06:24 ca-esmits kernel: Vendor: Apple Model: iPod > Rev: 1.62 > Oct 20 08:06:24 ca-esmits kernel: Type: Direct-Access > ANSI SCSI revision: 00 > Oct 20 08:06:24 ca-esmits kernel: SCSI device sdb: 3999743 512-byte > hdwr sectors (2048 MB) > Oct 20 08:06:24 ca-esmits kernel: sdb: Write Protect is off > Oct 20 08:06:24 ca-esmits kernel: sdb: assuming drive cache: write through > Oct 20 08:06:24 ca-esmits kernel: SCSI device sdb: 3999743 512-byte > hdwr sectors (2048 MB) > Oct 20 08:06:24 ca-esmits kernel: sdb: Write Protect is off > Oct 20 08:06:24 ca-esmits kernel: sdb: assuming drive cache: write through > Oct 20 08:06:24 ca-esmits kernel: sdb: sdb1 sdb2 > Oct 20 08:06:24 ca-esmits kernel: sd 4:0:0:0: Attached scsi removable disk > sdb > Oct 20 08:06:24 ca-esmits kernel: sd 4:0:0:0: Attached scsi generic sg1 > type 0 > Oct 20 08:08:12 ca-esmits kernel: usb 1-6.2: USB disconnect, address 9 > Oct 20 08:08:16 ca-esmits kernel: usb 1-6.2: new high speed USB device > using ehci_hcd and address 10 > Oct 20 08:08:17 ca-esmits kernel: usb 1-6.2: configuration #1 chosen > from 2 choices > Oct 20 08:08:17 ca-esmits kernel: scsi5 : SCSI emulation for USB Mass > Storage devices > Oct 20 08:08:22 ca-esmits kernel: Vendor: Apple Model: iPod > Rev: 1.62 > Oct 20 08:08:22 ca-esmits kernel: Type: Direct-Access > ANSI SCSI revision: 00 > Oct 20 08:08:22 ca-esmits kernel: SCSI device sdb: 3999743 512-byte > hdwr sectors (2048 MB) > Oct 20 08:08:22 ca-esmits kernel: sdb: Write Protect is off > Oct 20 08:08:22 ca-esmits kernel: sdb: assuming drive cache: write through > Oct 20 08:08:22 ca-esmits kernel: SCSI device sdb: 3999743 512-byte > hdwr sectors (2048 MB) > Oct 20 08:08:22 ca-esmits kernel: sdb: Write Protect is off > Oct 20 08:08:22 ca-esmits kernel: sdb: assuming drive cache: write through > Oct 20 08:08:22 ca-esmits kernel: sdb: sdb1 sdb2 > Oct 20 08:08:22 ca-esmits kernel: sd 5:0:0:0: Attached scsi removable disk > sdb > Oct 20 08:08:22 ca-esmits kernel: sd 5:0:0:0: Attached scsi generic sg1 > type 0 > Oct 20 08:09:18 ca-esmits gconfd (root-11527): starting (version > 2.14.0), pid 11527 user 'root' > Oct 20 08:09:18 ca-esmits gconfd (root-11527): Resolved address > "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only > configuration source at position 0 > > Thanks > > ED > > On 10/19/06, Todd Zullinger <tmz@xxxxxxxxx> wrote: > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >Ed Smits wrote: > >> Running FC5, kernel 2.6.18, all other things work OK. Plug iPod in > >> as normal: > >> > >> 1) as soon as I mount it Amerok crashes, unmounting my other USB > >> drives along with it. The unmount "feature" has been reported to > >> Amerok - it automatically unmounts the USB drives whenever it shuts > >> down, either intentionally or by crashing. > >> > >> 2) try to use GtkPod to manage the iPod - if the ipod is mounted it > >> crashes - segmentation fault, if I mount the iPod with GtkPod > >> running it doesn't see it. I did have to change the default location > >> in GtkPod from /mnt/ipod to /media/disk. > > > >What, if any, errors are there when gtkpod segfaults? > > > >> The same setup worked on my previous install with 2.6.17. I handled > >> my iPod through Amerock, worked like a charm. I'm a newbie so most > >> stuff is setup as default. > > > >More details. You say a previous install, so more has changed than > >just the kernel then, correct? If so, what was your previous install > >and what is your current install (versions of Fedora)? What versions > >of amarok, gtkpod, and libgpod do you have? Did you get them from > >Fedora (and Livna for gtkpod) or from another repository? > > > >(The version of libgpod included in Fedora is pretty ancient and many > >many bugs have been fixed in more recent versions. That would be my > >first suspect. I've been using libgpod and gtkpod from CVS forever > >now and it works splendidly. The latest releases of gtkpod and libgpod > >are pretty recent, so they might be worth checking out.) > > > >Also, what model of ipod do you have? > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >
