View previous topic :: View next topic |
Author |
Message |
The Mountain Man l33t
Joined: 03 Sep 2003 Posts: 643
|
Posted: Mon Jan 10, 2005 3:49 am Post subject: iPod/ieee1394 problem--iPod not being detected |
|
|
I've successfully used my iPod with Linux in the past, but it has recently and inexplicably stopped working (perhaps "emerge -u world" killed it?).
Basically, it's not being detected as an iPod. When I plug in my iPod, dmesg shows the following output:
Code: | ieee1394: Node added: ID:BUS[0-01:1023] GUID[000a27000257bdb2]
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023 |
Unplugging yields the following output:
Code: | ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000a27000257bdb2]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Error parsing configrom for node 0-01:1023 |
Here's the complete output after connecting and disconnecting the iPod several times:
Code: | ieee1394: Node added: ID:BUS[0-01:1023] GUID[000a27000257bdb2]
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000a27000257bdb2]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Error parsing configrom for node 0-01:1023
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[000a27000257bdb2]
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000a27000257bdb2]
ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[000a27000257bdb2]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000a27000257bdb2] |
I booted into Windows XP where the iPod was detected and mounted without incident (so it's not a hardware problem) and I ran the iPod restore software thinking that perhaps the filesystem was corrupt, but when I booted back into Linux, I got the same output as above.
Any suggestions? Thanks.
Edit: O.K., I seem to have solved the problem. Apparently "Raw IEEE1394 I/O support" has to be compiled into the kernel. I had "IEEE 1394 (FireWire) support", "OHCI-1394 support", and "SBP-2 support (Harddisks etc.)" (this last one as a module) but not the raw support.
Now this perplexes me because I don't ever remember having that option enabled nor did I recently remove it. Perhaps it was change in the kernel sources? Who knows. At least my iPod works again. _________________ I suck at signatures. |
|
Back to top |
|
|
The Mountain Man l33t
Joined: 03 Sep 2003 Posts: 643
|
Posted: Thu Jan 13, 2005 10:09 pm Post subject: |
|
|
O.K., apparently the problem has not been solved. I just plugged in my iPod and it exhibited the exact same problems I detailed in the original post. What the hell is going on? _________________ I suck at signatures. |
|
Back to top |
|
|
RockCrusha Tux's lil' helper
Joined: 31 Jan 2004 Posts: 91
|
Posted: Thu Jan 20, 2005 3:11 am Post subject: |
|
|
i'm experiencing this exact problem.
using linux kernel 2.6.8-r10, gcc-3.4.3
:: bump :: |
|
Back to top |
|
|
The Mountain Man l33t
Joined: 03 Sep 2003 Posts: 643
|
Posted: Sat Jan 22, 2005 4:49 pm Post subject: |
|
|
O.K., I think I've figured out another piece of the puzzle. It seems the iPod has to be "awake" when it is plugged into the firewire port. Simply touch the controls (with the unit unlocked, of course) to power up the iPod before plugging in the firewire cable.
Try that, and if it works for you then I will go ahead and consider this one solved. _________________ I suck at signatures. |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Sun Jan 23, 2005 9:05 pm Post subject: ipod not detected |
|
|
I'm having the same problem. My ipod (a new 40G one) worked under 2.4. Now that I am using 2.6, it is not detected unless I reboot with it plugged in. Here's my dmesg output after plugging it in, doing modprobe sbp2, and then unplugging.
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[000a27000294f639]
I've set udev up to make an "ipod" node, but it wont do it unless the ipod is plugged in at boot time. I tried mknod-ing my own nodes but that doesnt seem to work. I've only been using linux for about 6 months so I might be doing something stupid. But I'm starting to suspect that the newest ipods dont play well with hotplug and/or udev.
Any suggestions? I can always just reboot when I want to use the 'pod. But that's kind of a drag...
|
|
Back to top |
|
|
Vivid5500 n00b
Joined: 28 Jan 2004 Posts: 20
|
Posted: Tue Jan 25, 2005 12:27 am Post subject: Re: ipod not detected |
|
|
zontar wrote: |
Any suggestions? I can always just reboot when I want to use the 'pod. But that's kind of a drag...
|
I"ve got the same problem as you, I have to reboot to get the iPod recognized. For some reasont eh hotplugging isn't working I think. |
|
Back to top |
|
|
zurd Apprentice
Joined: 17 Dec 2003 Posts: 228 Location: Canada, Montreal
|
Posted: Tue Jan 25, 2005 2:57 am Post subject: 1 |
|
|
Indeed, I need to reboot to so that it can work.
Sometimes it do work, other times not, but a simple reboot solve it.
Is it really because of the hotplugging? Is it necessary to keep it? If it's the cause of the problem, what about we just remove it from the kernel, you think that would help? |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Wed Jan 26, 2005 2:00 am Post subject: maybe this works |
|
|
I just tried something that seemed to work
truck root # /etc/init.d/hotplug status
* status: stopped
truck root # /etc/init.d/hotplug start
truck root # /etc/init.d/hotplug status
* status: started
I dont know why hotplug had stopped but when I started it and plugged in the ipod, it got recognized. |
|
Back to top |
|
|
zurd Apprentice
Joined: 17 Dec 2003 Posts: 228 Location: Canada, Montreal
|
Posted: Wed Jan 26, 2005 8:58 am Post subject: |
|
|
I don't think this problem is about hotplug, I don't even have the file /etc/init.d/hotplug but a reboot solved the problem. |
|
Back to top |
|
|
The Mountain Man l33t
Joined: 03 Sep 2003 Posts: 643
|
Posted: Thu Jan 27, 2005 7:55 pm Post subject: |
|
|
O.K., have you guys made the sure the iPod is powered on before plugging it in? I've not done a lot of testing, but the little I have done shows that the iPod is consistently detected if it is powered on before being plugged in. _________________ I suck at signatures. |
|
Back to top |
|
|
zurd Apprentice
Joined: 17 Dec 2003 Posts: 228 Location: Canada, Montreal
|
Posted: Thu Jan 27, 2005 11:46 pm Post subject: 1 |
|
|
Yup, for me it's always plugged in and turned on. I always have to modprobe sbp2 also. And as I said I do not have hotplug.
I don't mind anyway since now my 20 gigs iPod is full and I rarely update it, maybe I will do so in about 3 months! So even if I reboot it's not the end of the world, my computer ain't a server you cannot reboot
But, I don't know if it's because I am using Linux with it but this is my 3rd iPod of 20 gigs, the 2 others broke with a broken filesystem (the logo of the icon folder showing when booting with it) or maybe I'm just unlucky. The 5 gigs iPod I owned before lasted 21 months tho and I've been using it with Windows and Linux. It broke because I drop it on the floor. If anyone has a similar story about broken iPod i'll be glad to hear it |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Thu Jan 27, 2005 11:57 pm Post subject: |
|
|
Yes, I've tried powering-on first. It doesn't help. Recently I've had luck with the following:
rc-update del hotplug default
recompile with ieee1394 and ohci1394 as modules
After Gnome has started up
/etc/initd/hotplug start
modprobe -v ohci1394
Then I can plug the ipod in and it gets recognized. It's worked 3 times in a row over a couple of days so I'm getting hopeful. But it seems kind of weird... |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Sat Jan 29, 2005 9:24 pm Post subject: |
|
|
Well, for 3 days it worked regularly. I tried powering down and rebooting a couple of times a day just to make sure. But today, no dice! I think Apple is messing with us. Back to rebooting! |
|
Back to top |
|
|
datenwolf n00b
Joined: 01 Sep 2003 Posts: 55
|
Posted: Sun Jan 30, 2005 12:01 pm Post subject: |
|
|
zontar wrote: | Well, for 3 days it worked regularly. I tried powering down and rebooting a couple of times a day just to make sure. But today, no dice! I think Apple is messing with us. Back to rebooting! |
EDIT: Corrected a few typos
Well I had the same problem and I tried a couple of kernels from 2.6.7 to 2.6.10, but it seems, that I got a solution and it's quite simple:
All you must make sure is, that after the HW drivers for the FireWire stuff, but _before_ sbp2 the sd_mod get's loaded. The sd_mod by itself requires the scsi_mod and will modprobe it. Thereafter you should load the sbp2 module, and then keep it loaded.
IMPORTANT: To disconnect the iPod don't rmmod the sbp2, but just use e.g. eject /dev/sda (replace sda with the actual device node of your iPod).
Ok, here again:
modules must be loaded in this order:
ieee1394
ohci1394
(that should have hot/coldplug done for you)
Now the critical part
modprobe scsi_mod
modprobe sd_mod
modprobe sbp2
AND very IMPORTANT: Don't unload sbp2 afterwards, as this will break it. Use eject. |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Sun Jan 30, 2005 7:35 pm Post subject: |
|
|
Thanks for the tip, but my root file system is SATA so I think I need sd_mod in the kernel. |
|
Back to top |
|
|
datenwolf n00b
Joined: 01 Sep 2003 Posts: 55
|
Posted: Sun Jan 30, 2005 10:07 pm Post subject: |
|
|
zontar wrote: | Thanks for the tip, but my root file system is SATA so I think I need sd_mod in the kernel. |
Hmm, I just tried it with my "big box" (the one that has really serious SCSI HDD space AKA Server), which runs on gentoo-dev-sources-2.6.10-r1 And: On this one the iPod isn't recognized, too.
From this, and the other postings about this problem on the forum I can slowly recognize a pattern - and I got an idea, what's causing it:
I think, that the iPod (or other SBP2 device) is not recognized, if all of the following happens:
- udev is used
- there are other SCSI storage devices present
- these SCSI storage devices are initialized before the SBP2
And the reason for this could be, that unfortunately the ieee1394 drivers are still not integrated into sysfs and thus not accessible to the udev hotplug script. I still have no clear picture, why this prevents sbp2 recognizing a connected device, but my guess would be, that somehow with a SCSI storage driver already loaded sbp2 could just have no access to the SCSI subsystem w/o sysfs support.
Well the last time I did kernel hacking was at 2.2 kernel series times within the ISDM4Linux subsystem. Where are the 2.6 kernel experts? |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Mon Jan 31, 2005 1:11 am Post subject: |
|
|
That sounds about right. I didn't have problems until I migrated to 2.6 and started using udev. I'm using 2.6.10-r6. Strange the way it works sometimes, though. |
|
Back to top |
|
|
morset n00b
Joined: 14 Nov 2003 Posts: 31
|
Posted: Tue Feb 01, 2005 3:54 am Post subject: |
|
|
datenwolf wrote: | IMPORTANT: To disconnect the iPod don't rmmod the sbp2, but just use e.g. eject /dev/sda (replace sda with the actual device node of your iPod).
|
Whenever I eject my ipod, eject /dev/sdb. I have SATA for sda. It freezes my system and I have to do a hard reset. Does this happen to anyone else? |
|
Back to top |
|
|
Adrien Advocate
Joined: 13 Jul 2004 Posts: 2308 Location: Bretagne
|
Posted: Tue Feb 01, 2005 8:47 am Post subject: |
|
|
I've had exactly the same problem with the iPod that you guys all have.
I'm using a 2.6.10-r6 kernel and I know it's not a hardware problem:
https://forums.gentoo.org/viewtopic.php?t=287201&highlight=device+ipod
Some friend of mine told me it was a problem about hotplug or udev and I could find an answer on www.linux1394.org but didn't find anything interesting though.
What I did to solve up my problem: I simply used the other cable (I mean the double-cable USB/Firewire), still with the dock connector and with this cable, it just works perfectly....Don't ask me why, I don't have a clue (cause my single firewire cable works just fine in windows )
regards, |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Wed Feb 02, 2005 3:02 am Post subject: |
|
|
It does seem to work with the USB cable, but then I don't have Firewire speeds. Also, I'm not sure how to get it to stop saying "do not disconnect":
truck root # eject /dev/ipod
eject: unable to eject, last error: Operation not permitted
truck root # eject /dev/sdb
eject: unable to find or open device for: `/dev/sdb'
(/dev/sda is my SATA hard disk.)
modprobe -r sbp2 is no use, since I'm using USB. |
|
Back to top |
|
|
datenwolf n00b
Joined: 01 Sep 2003 Posts: 55
|
Posted: Wed Feb 02, 2005 7:39 pm Post subject: |
|
|
zontar wrote: | That sounds about right. I didn't have problems until I migrated to 2.6 and started using udev. I'm using 2.6.10-r6. Strange the way it works sometimes, though. |
Today I tried something: I compiled DevFS support into the kernel, but still I'm using udev by adding gentoo=nodevfs kernel parameter. Of course you have to disable automatic DevFS mount in the kernel config.
And voila: It now recognizes my iPod also on the systems, that previously didn't recognize my iPod. This workaround works at least for me.
ADDENDUM:
It seems that tthe iPod may not being recognized at the first time on systems with more than one IEEE1394 controller. Disconnecting and reconnecting it, eventually on the other controller had worked for me so far. |
|
Back to top |
|
|
The Mountain Man l33t
Joined: 03 Sep 2003 Posts: 643
|
Posted: Sat Mar 05, 2005 2:46 pm Post subject: |
|
|
Well, this little problem is still plaguing me. It is my conclussion that IEEE1394 support in the kernel is broken as a Google search for "ieee1394: Node changed: 0-00:1023 -> 0-01:1023" returns a number of hits related to difficulties with various firewire hardware.
At this point, there doesn't seem to be a "magic bullet" solution (sometimes it works, sometimes it doesn't) so I guess we'll just have to hope the kernel devs get around to fixing it eventually. _________________ I suck at signatures. |
|
Back to top |
|
|
zontar Tux's lil' helper
Joined: 23 Jan 2005 Posts: 84 Location: Seattle
|
Posted: Sat Mar 05, 2005 6:59 pm Post subject: |
|
|
That is the conclusion I also reached. The ipod seems to be recognized about half the time. The rest of the time I just reboot and then things are OK. Many "fixes" have turned out to just be a result of this randomness. I've had things seem to work for days.
Recently I updated glib, pango and gtk+ and then gtkpod would no longer run. I also got the vanishing items in the Gnome Applications menu thing. I've down-graded glib and gtk+ and things are working, but Gentoo feels buggy. |
|
Back to top |
|
|
zx2c4 Developer
Joined: 09 Jun 2005 Posts: 177
|
Posted: Sun Dec 04, 2005 9:55 pm Post subject: |
|
|
I am having the same problem with a firewire harddrive running 2.6.14. |
|
Back to top |
|
|
|