Description of problem: After upgrading system to kernel-PAE-2.6.30.5-43.fc11.i686, my system doesn't boot off my USB disk (Lacie) Version-Release number of selected component (if applicable): kernel-PAE-2.6.30.5-43.fc11.i686 How reproducible: always Steps to Reproduce: 1.just boot off from my USB disk 2. 3. Actual results: no boot Expected results: boot Additional info: This is part of Dmesg when booting: scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device scan complete scsi 5:0:0:0: Direct-Access Hitachi HTS541680J9AT00 0000 PQ: 0 ANSI: 0 sd 5:0:0:0: [sdb] 156301488 512-byte hardware sectors: (80.0 GB/74.5 GiB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 5:0:0:0: [sdb] Assuming drive cache: write through sd 5:0:0:0: [sdb] 156301488 512-byte hardware sectors: (80.0 GB/74.5 GiB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 5:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sdb2 sd 5:0:0:0: [sdb] Attached SCSI disk sd 5:0:0:0: Attached scsi generic sg2 type 0 EXT4-fs: barriers enabled kjournald2 starting: pid 88, dev dm-0:8, commit interval 5 seconds EXT4-fs: delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs: mounted filesystem dm-0 with ordered data mode SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks type=1404 audit(1253663261.664:2): selinux=0 auid=4294967295 ses=4294967295 udev: starting version 141 ACPI: WMI: Mapper loaded But when system doesn't boot I see last lines on my screen : scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usbcore: registered new interface driver cms-cypress USB Mass Storage support registered. usb-storage: device scan complete scsi 5:0:0:0: Direct-Access Hitachi HTS541680J9AT00 0000 PQ: 0 ANSI: 0 sd 5:0:0:0: [sdb] 156301488 512-byte hardware sectors: (80.0 GB/74.5 GiB) sd 5:0:0:0: [sdb] Write Protect is off I note this big difference: usbcore: registered new interface driver cms-cypress Please note that I have another system with Philips external USB disk running fine....
You should be able to boot by blacklisting the ums-cypress driver, if that is the problem: # modinfo ums-cypress.ko filename: ums-cypress.ko license: GPL author: Matthieu Castet <castet.matthieu> description: SAT support for Cypress USB/ATA bridges with ATACB srcversion: 31BA41D297335BC0636FD2E alias: usb:v04B4p6831d*dc*dsc*dp*ic*isc*ip* alias: usb:v04B4p6830d*dc*dsc*dp*ic*isc*ip* depends: usb-storage vermagic: 2.6.30.5-43.fc11.i686.PAE SMP mod_unload 686
Please try blacklisting ums-cypress and report back whether that helps.
Chuck, I had blown that USB disk, I tried to reinstall using a LiveCD and I can't proceed with installation, it says that there is an error during /boot creation. F11 was on that disk but it was yum-upgraded from a working F10!!. How do I blacklist during Live installation??
I made a fresh installation on same disk, I updated all packages, now when I boot with 2.6.30.5-43.fc11 (not PAE) after initial booting I get a graphical window, then window is blanked and I get these two last lines on the screen before freezing sd 5:0:0:0: [sdb] Assuming drive cache: write through sd 5:0:0:0: [sdb] Assuming drive cache: write through also after blacklisting ums-cypress module. anything else I can do tho help?
I forgot to mention that now I don't see lines as per original post...
Is the module to be blacklisted ums-cypress module or cms-cypress??
(In reply to comment #6) > Is the module to be blacklisted ums-cypress module or cms-cypress?? It's ums-cypress
anyway I blacklisted ums-cypress, but no way to have the system booting...
*** Bug 526066 has been marked as a duplicate of this bug. ***
Works here when plugged into an already-running machine: $ lsusb | grep Cy Bus 001 Device 004: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI $ uname -a Linux nc 2.6.30.5-43.fc11.x86_64 #1 SMP Thu Aug 27 21:39:52 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux usb 1-2: new high speed USB device using ehci_hcd and address 4 usb 1-2: New USB device found, idVendor=04b4, idProduct=6830 usb 1-2: New USB device strings: Mfr=56, Product=78, SerialNumber=100 usb 1-2: Product: USB2.0 Storage Device usb 1-2: Manufacturer: Cypress Semiconductor usb 1-2: SerialNumber: -------------- usb 1-2: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver ums-cypress usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 2:0:0:0: Direct-Access IC25N060 ATMR04-0 PQ: 0 ANSI: 0 sd 2:0:0:0: Attached scsi generic sg1 type 0 sd 2:0:0:0: [sdb] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 33 00 00 00 sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 2:0:0:0: [sdb] Attached SCSI disk
This could be a problem with the initrd. Please attach the initrd file from the broken kernel.
Created attachment 363129 [details] initrd file for non booting kernel on cyprus chip also this kernel doesn't boot
I have the same problem. $ lsusb | grep Cy Bus 001 Device 004: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
Disabling CONFIG_USB_STORAGE_CYPRESS_ATACB makes it boot. 2.6.30.9-85 has that workaround.
Tested and it boots fine.
kernel-2.6.30.9-90.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/kernel-2.6.30.9-90.fc11
kernel-2.6.30.9-90.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
This apparently occurs if the kernel option CONFIG_USB_STORAGE_CYPRESS_ATACB is enabled but the module ums_cypress.ko is not available. The same problem exists in the F12 Live Beta image. See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/419231 for the same isue in Ubuntu.
I suggest to file a bug also against rawhide. Hope that it can be solved before final release...
Created bug 532062 for F12.