Comment 82 for bug 925760

Under Trusty 14.04 LTS 3.13.0-24-generic the ss_en=0 option did not work on first try. The file was created but it was empty. After using gksu gedit blah blah blah on the file and manually putting the option in it worked fine. Thank you very much at getting this annoying undocumented feature (old tongue for bug) out of the way every time I do a dmesg.

After a million lines of 1. Test failed, 2. Ask for cash (who wouldn't?) and 3. assume write (everyone assumes they are right) The ss_en=0 was manually added to the file and then the Remove / reinsert kernel module was executed. To prove it works dmesg output is below:

[ 3466.265066] sd 2:0:0:0: [sda] Test WP failed, assume Write Enabled
[ 3466.267309] sd 2:0:0:0: [sda] Asking for cache data failed
[ 3466.267317] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 3474.080808] usbcore: deregistering interface driver ums-realtek
[ 3639.916413] ums-realtek 1-4:1.0: USB Mass Storage device detected
[ 3639.917971] scsi6 : usb-storage 1-4:1.0
[ 3639.918200] usbcore: registered new interface driver ums-realtek
[ 3640.918321] scsi 6:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
[ 3640.918936] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 3640.929692] sd 6:0:0:0: [sda] Attached SCSI removable disk

Can we can close this bug if it moves upstream with ss_en=0 and the SD ram card reader still works as others state?

- WE2U (WinEunuuchs2Unix)