I am using FC4 (fully updated, kernel 2.6.14-1.1653_FC4 i686)
I am connecting via firewire

I used to be able to connect my iPod to my linux box, but then after I removed it without ejecting, linux won't recoginse it.
After rebooting with it plugged in, it diddn't even have the flashing "do not disconnect".
I plugged it into another port, and the message appears, but it is not even in /dev.

'dmesg | grep -i scsi' returns
SCSI subsystem initialized
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
Type: Direct-Access-RBC ANSI SCSI revision: 00
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 14

'file /dev/sg0' returns
/dev/sg0: character special (21/0)


What is wrong here? It should make a /dev/sda1 and sda2, right?

did 'tail -f /var/log/messages /var/log/syslog /var/log/dmesg', and after plugging in iPod, it returned

Dec 31 13:12:23 apache ieee1394.agent[3829]: ... no drivers for IEEE1394 product 0x/0x/0x
Dec 31 13:12:23 apache ieee1394.agent[3840]: ... no drivers for IEEE1394 product 0x/0x/0x
Dec 31 13:12:23 apache kernel: SCSI subsystem initialized
Dec 31 13:12:23 apache kernel: sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
Dec 31 13:12:23 apache kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
Dec 31 13:12:23 apache kernel: ieee1394: sbp2: Try serialize_io=0 for better performance
Dec 31 13:12:23 apache kernel: scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
Dec 31 13:12:24 apache kernel: ieee1394: sbp2: Logged into SBP-2 device
Dec 31 13:12:24 apache kernel: Vendor: Apple Model: iPod Rev: 1.62
Dec 31 13:12:24 apache kernel: Type: Direct-Access-RBC ANSI SCSI revision: 00
Dec 31 13:12:24 apache scsi.agent[3882]: enclosure at /devices/pci0000:00/0000:00:1e.0/0000:02:0a.3/fw-host1/000a270002bd6838/000a270002bd6838-0/host0/target0:0:0/0:0:0:0
Dec 31 13:12:24 apache kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 14

(my hostname is apache.themj, hence the apache)
Hopefuly that will shed some light on the issue?

Why isn't anybody responding? Did I breach some code of conduct?

well, obviously quadruple-posting is not appreciated, but I have no choice

I and others have had this problem starting Dec (I'm using Ubuntu). I think something happened to the kernel. Since I haven't been able to resolve it I've used bugzilla to report a bug. I encourage you to do the same as I think the developers need to know what is going on.

Best of luck

Thanks linuxted, I will do that. It's nice to know I'm not alone.
I will try booting into an erlier kernel, hopefuly that'll work as a temporary fix.