Problems with USB drive and kernel 2.6.10

[kind420]

Hi all,

I've noticed various issues with the 64-bit version FC3, but I've managed to work through most except this one:

When using the 2.6.10 kernel, nautilis will lock up upon trying to read the directory a few levels deep. However, I no longer have the issue when using the first kernel installed from the cd's. Here is what I'm seeing in messages:

Jan 19 04:56:45 fc3-64 kernel: floppy0: disk absent or changed during operation
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 16
Jan 19 04:56:45 fc3-64 kernel: Buffer I/O error on device fd0, logical block 2
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 0
Jan 19 04:56:45 fc3-64 kernel: floppy0: disk absent or changed during operation
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 16
Jan 19 04:56:45 fc3-64 kernel: Buffer I/O error on device fd0, logical block 2
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 0
Jan 19 04:56:45 fc3-64 kernel: floppy0: disk absent or changed during operation
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 16
Jan 19 04:56:45 fc3-64 kernel: Buffer I/O error on device fd0, logical block 2
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 0
Jan 19 04:56:45 fc3-64 kernel: floppy0: disk absent or changed during operation
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 16
Jan 19 04:56:45 fc3-64 kernel: Buffer I/O error on device fd0, logical block 2
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 0
Jan 19 04:56:45 fc3-64 kernel: floppy0: disk absent or changed during operation
Jan 19 04:56:45 fc3-64 kernel: end_request: I/O error, dev fd0, sector 16

Curious that I dont see anything about /dev/sda1. Any thoughts?

Thanks in advance,

Kind420

[lcapriotti]

this is happening to me, too - and I've an Intel-Inside thing.

Luigi

[kind420]

Thank God I can at least use the 2.6.9 kernel as a work around for now! I guess this issue is processor independent, as I'm using the Athlon 64.