Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
It's not been fixed for me! On 8 May 2010, at 00:07, Alex Valavanis valavanisa...@googlemail.com wrote: Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the report. The bug has been fixed in newer releases of Ubuntu. ** Changed in: linux (Ubuntu Intrepid) Status: Fix Committed = Invalid -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
no problems here.. i'm on 2.6.31-20-generic. 2010/4/29 Robert rob...@gmail.com I still have this problem in Karmic (even after a fresh install). I also have this problem after upgrading to Lucid release candidate. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Intrepid: Fix Committed Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.154975] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.154979] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.154988] sdi: sdi1 [ 4287.176965] sd 12:0:0:0: [sdi] Attached SCSI disk [ 4287.177173] sd 12:0:0:0: Attached scsi generic sg7 type 0 [ 4289.129138] kjournald starting. Commit interval 5 seconds [ 4289.130101] EXT3 FS on sdi1, internal journal [ 4289.130110] EXT3-fs: mounted filesystem with ordered data mode. To unsubscribe from this bug, go to: https://bugs.launchpad.net/linux/+bug/264789/+subscribe -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
bump! any updates? 2009/8/26 Ramaddan ramad...@gawab.com Still have this problem on Jaunty. Did not have this problem in Intrepid. This is the output I get in dmesg: [54237.142762] usb 1-1: configuration #1 chosen from 1 choice [54237.166132] scsi10 : SCSI emulation for USB Mass Storage devices [54237.169779] usb-storage: device found at 6 [54237.169785] usb-storage: waiting for device to settle before scanning [54242.169180] usb-storage: device scan complete [54242.171276] scsi 10:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4 [54272.284042] usb 1-1: reset high speed USB device using ehci_hcd and address 6 [54287.396554] usb 1-1: device descriptor read/64, error -110 [54302.620102] usb 1-1: device descriptor read/64, error -110 [54302.836555] usb 1-1: reset high speed USB device using ehci_hcd and address 6 ramad...@ramaddancomp:~$ dmesg | tail [54466.984043] usb 2-1: new full speed USB device using ohci_hcd and address 6 [54482.160555] usb 2-1: device descriptor read/64, error -110 [54497.440053] usb 2-1: device descriptor read/64, error -110 [54497.716039] usb 2-1: new full speed USB device using ohci_hcd and address 7 [54502.736147] usb 2-1: device descriptor read/8, error -110 [54507.857152] usb 2-1: device descriptor read/8, error -110 [54508.136048] usb 2-1: new full speed USB device using ohci_hcd and address 8 [54513.157161] usb 2-1: device descriptor read/8, error -110 [54518.277164] usb 2-1: device descriptor read/8, error -110 [54518.380062] hub 2-0:1.0: unable to enumerate USB device on port 1 Any updates on this issue? -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in linux in Ubuntu Intrepid: Fix Committed Bug description: I updated to 2.6.27-2 today, and one of my hard drives is no longer recognized. It is in a Vantec NexStar GX enclosure, and was working fine on .26, and continues to work fine on a Hardy machine. Here is the dmesg for it: [ 6722.944029] usb 5-5: new high speed USB device using ehci_hcd and address 27 [ 6723.077863] usb 5-5: configuration #1 chosen from 1 choice [ 6723.079511] hub 5-5:1.0: USB hub found [ 6723.080345] hub 5-5:1.0: 4 ports detected [ 6732.712034] usb 5-5: reset high speed USB device using ehci_hcd and address 27 [ 6733.124011] usb 5-5.1: new high speed USB device using ehci_hcd and address 28 [ 6733.364598] usb 5-5.1: configuration #1 chosen from 1 choice [ 6733.365180] scsi17 : SCSI emulation for USB Mass Storage devices [ 6733.365818] usb-storage: device found at 28 [ 6733.365830] usb-storage: waiting for device to settle before scanning [ 6738.364276] usb-storage: device scan complete [ 6738.361002] scsi 17:0:0:0: Direct-Access ST340063 2A 3.04 PQ: 0 ANSI: 0 [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.361002] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.361002] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.361002] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.361002] sd 17:0:0:0: [sdm] 781422769 512-byte hardware sectors (400088 MB) [ 6738.370354] sd 17:0:0:0: [sdm] Write Protect is off [ 6738.370362] sd 17:0:0:0: [sdm] Mode Sense: 03 00 00 00 [ 6738.370365] sd 17:0:0:0: [sdm] Assuming drive cache: write through [ 6738.371516] sdm: sdm1 [ 6738.418089] sd 17:0:0:0: [sdm] Attached SCSI disk [ 6738.418995] sd 17:0:0:0: Attached scsi generic sg8 type 0 [ 6738.656598] sd 17:0:0:0: [sdm] Sense Key : No Sense [current] [ 6738.656614] sd 17:0:0:0: [sdm] Add. Sense: No additional sense information From there, the last 2 lines about Sense Key and Add Sense repeat over and over again. The 4 port hub that is a part of the enclosure continues to work fine though, with a floppy drive, a printer, and another hard drive. I have a Vantec NexStar 3 enclosure as well, and it is working just fine. Dmesg for the working enclosure: [ 4281.996024] usb 5-3: new high speed USB device using ehci_hcd and address 19 [ 4282.131863] usb 5-3: configuration #1 chosen from 1 choice [ 4282.133222] scsi12 : SCSI emulation for USB Mass Storage devices [ 4282.133561] usb-storage: device found at 19 [ 4282.133566] usb-storage: waiting for device to settle before scanning [ 4287.132002] usb-storage: device scan complete [ 4287.136004] scsi 12:0:0:0: Direct-Access ST375064 0AS PQ: 0 ANSI: 2 [ 4287.138368] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.144790] sd 12:0:0:0: [sdi] Write Protect is off [ 4287.144800] sd 12:0:0:0: [sdi] Mode Sense: 38 00 00 00 [ 4287.144804] sd 12:0:0:0: [sdi] Assuming drive cache: write through [ 4287.152388] sd 12:0:0:0: [sdi] 1465149168 512-byte hardware sectors (750156 MB) [ 4287.154966] sd 12:0:0:0: [sdi] Write
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: If there's so many special exceptions, then maybe the drivers need to be rethought in a way that is more generic. Because there is no way to have the same driver (usb-storage) to say whether a device returns the total number of blocks or the highest block number (as it is expected). And when the drives response to actually reading the last sector in the case of a too high number is to return without any information and this can be a valid case for some other devices, you will have a hard time to come up with a generic solution that works for all. Upstream already started to have a list of vendors which seem always to return the wrong thing. But this cannot be the default behavior as otherwise some devices would get a too small capacity detected. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 20/07/09 09:43 Stefan Bader wrote: Because there is no way to have the same driver (usb-storage) to say whether a device returns the total number of blocks or the highest block number (as it is expected). And when the drives response to actually reading the last sector in the case of a too high number is to return without any information and this can be a valid case for some other devices, you will have a hard time to come up with a generic solution that works for all. These devices seem to work fine on Windows and OS/X. What do they do differently? (Especially OS/X, since it is in part open source as Darwin.) -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: These devices seem to work fine on Windows and OS/X. What do they do differently? (Especially OS/X, since it is in part open source as Darwin.) Not access the last sector for example. The problems with most of the devices started when Linux added scans for md meta-data on the complete drive (not the partition). And md meta-data is at the end of the usable space. Actually somewhere in those many reports (can't remember which) there was a comment that those cases also start behaving badly when you really try to access the last sector from Windows. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
If there's so many special exceptions, then maybe the drivers need to be rethought in a way that is more generic. On Fri, Jul 17, 2009 at 1:07 PM, Stefan Baderstefan.ba...@canonical.com wrote: @I fear this bug is sadly becoming more and more bloated and confusing by the number of hw that needs to be fixed. If we could split out (create) a new bug for each device that needs to be taken care of, this would help very much. I would suggest a topic like usbstorage: device shows 'No sense [current]' bug, against the linux package ... -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Robert wrote: I tried that patch with a Sony Ericson w800i mobile phone. It still doesn't work. That is not too surprising as the additional quirk entries only will affect Ericson w760i and z780i. A z800i would have a different usb id. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
grawity wrote: Sony-Ericsson W760i, lsusb output attached. Hm, well _that_ id should already be in. Have you tried the kernel I mentioned above? -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001, Macpower, Storage, US_SC_DEVICE, US_PR_DEVICE, NULL, US_FL_FIX_CAPACITY), Exactly this with slightly different strings. And two other similar additions for the Ericsons. to the drivers/usb/storage/unusual_devs.h? and A + B'' patch too from this link: http://bugzilla.kernel.org/show_bug.cgi?id=11843#c26? Patch A was always in the code for Jaunty. B'', based on comment 36 in that bugzilla would not be acceptable (to avoid potential other regressions). For that reason it is not included in my test kernel. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
The phone presents itself as _two_ removable devices - one for internal memory, the other for MemoryStick. In that case there should be two devices visible with the lsusb output. At the moment every device has to be declared independently. Though it somehow looks as for upstream Ericson might qualify for the list of vendors which only do devices with that bug. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This entry, though the strings are just informational, what counts is the numerical id for vendor and model, plus the lower and upper ranger for the firmware (the first line). +UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001, + Macpower Peripherals, Ltd, + IDE to USB 2.0 HDD case with 3-port hub, + US_SC_DEVICE, US_PR_DEVICE, NULL, + US_FL_FIX_CAPACITY ), + -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
If I remove the MemoryStick and reconnect the phone, it still shows exactly the same thing. Hm, right. I missed the fact that in dmesg the second device appears to be sort of a LUN. The unusual_devs entries would match on the one device... Hm, I am not sure whether its in the bug. With the unpatched normal kernel. What sector readings would you get there? -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 15/07/09 16:39 Stefan Bader wrote: @Gonzalo, I added some code that tries to fix up your device. The change is included in the test kernel of another bug. You can find it at http://people.canonical.com/~smb//bug287701/. Could you try whether that change helps? Thanks. I tried that patch with a Sony Ericson w800i mobile phone. It still doesn't work. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
I still have this problem as well. On Sat, May 2, 2009 at 10:09 PM, Leon l...@tim-online.nl wrote: I'm still having this problem. I tried the 2.6.28-11-generic kernel and a mainline build. But with both I can't get rid of this nasty bug. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a direct subscriber of the bug. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
On 28/02/09 16:35 Malcolm Lalkaka wrote: This bug is in the upstream kernel, meaning it is not specific to the Ubuntu distribution; I believe Fedora, for example, has been having this problem too. The latest version of Debian, version 5.0, may not have this problem because it contains kernel version 2.6.28. It's also a problem in Debian 5.0. -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Actually, this fix makes it so that partitions mounted by volume id in
/etc/fstab aren't mountable.
On 16/02/09 17:18 Robert Rothenberg wrote:
This also works with my Sony Ericsson W800i.
I also note that this fix works on Debian Lenny, so it should be
reported upstream.
On 16/02/09 16:43 Ketil Malde wrote:
I had similar problems mounting my Sony Ericsson C702 on Ubuntu 8.10. I
edited /etc/udev/rules.d/60-persistent-storage.rules, commenting out the
line looking like:
IMPORT{program}=vol_id --export $tempnode
and after that change, I could then mount it as a normal USB disk.
I really hope this will be fixed soon, USB mass storage is old enough
that it should Just Work (tm).
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
This also works with my Sony Ericsson W800i.
I also note that this fix works on Debian Lenny, so it should be reported
upstream.
On 16/02/09 16:43 Ketil Malde wrote:
I had similar problems mounting my Sony Ericsson C702 on Ubuntu 8.10. I
edited /etc/udev/rules.d/60-persistent-storage.rules, commenting out the
line looking like:
IMPORT{program}=vol_id --export $tempnode
and after that change, I could then mount it as a normal USB disk.
I really hope this will be fixed soon, USB mass storage is old enough
that it should Just Work (tm).
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
My solution is to use kernel from HH. It works for me. I have newer apps and usable usb phone and pendrive connection. Dear hackers, please tell me about drawbacks of my solution. Is there any danger? :) -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 264789] Re: USB Hard Drive Not Accessible, vol_id hangs
Hi Steve, Perhaps you wanted to say 2.6.27-10 . Please let us know when the metapackage for 2.6.27-11 gets updated. -- Regards, Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- USB Hard Drive Not Accessible, vol_id hangs https://bugs.launchpad.net/bugs/264789 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
