** Attachment removed: "C72957374002D7EF17AED2B17BEF18FE.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/+attachment/4870526/+files/C72957374002D7EF17AED2B17BEF18FE.jpg
** Attachment removed: "428E18A7EF2A80EE1218968A65B3C947.jpg"
https://bugs.launchpad.net/ubuntu/+source/
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264789
Title:
USB Hard Drive Not Accessible, vol_id hangs
--
ubuntu-bugs mailing list
ubuntu-bug
It's not been fixed for me!
On 8 May 2010, at 00:07, Alex Valavanis
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
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
no problems here.. i'm on 2.6.31-20-generic.
2010/4/29 Robert
> 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
>
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 member of Ubuntu
Bugs,
This should be fixed in the kernel that includes the update to stable
2.6.31.6. Unfortunately it is blocked atm by other things. You can get a
preview of it at: https://launchpad.net/~stefan-bader-
canonical/+archive/karmic for the time being.
--
USB Hard Drive Not Accessible, vol_id hangs
https:
$ uname -a
Linux ehrlichman 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:00:22 UTC 2009
i686 GNU/Linux
[ 567.800086] usb 1-2: new high speed USB device using ehci_hcd and address 5
[ 567.933509] usb 1-2: configuration #1 chosen from 1 choice
[ 567.981341] Initializing USB Mass Storage driver
Using:
Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC
2009 i686 GNU/Linux
with the same JMicron Hi-Speed USB to SATA & PATA Combo Bridge as
mentioned in comment #100, I am still hitting this bug. :( I have a
Western Digital Cavier SE16, 640GB SATA drive (WD6400AAKS) attache
https://bugs.launchpad.net/ubuntu/+bug/460831 may be a duplicate of this
occouring on WD (Western Digital) drive (My Book Essential Edition 2.0
WD1H1U-00)
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because you are a
A patch in the 2.6.31.5 upstream stable patch set for the kernel
contains a patch which may help. The Karmic 9.10 kernel will be pulling
in this set of stable patches as a stable release update to Karmic.
I've taken the liberty to build a test kernel for Karmic containing this
one patch which may
bump! any updates?
2009/8/26 Ramaddan
> 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
> [
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.1697
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
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
> th
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
expec
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
Bader 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 s
@grawity: Oh, yes- What I meant was:
[ 1602.683559] sd 3:0:0:0: [sdc] 120093 512-byte hardware sectors: (61.4
MB/58.6 MiB)
[ 1602.728250] sd 3:0:0:1: [sdd] 3995649 512-byte hardware sectors: (2.04
GB/1.90 GiB)
compared to (with the patch)
[ 339.211253] sd 4:0:0:0: [sdc] 120092 512-byte hardwa
Stefan Bader wrote:
> > 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
sorry wrong file .
THIS should be the correct lsusb
** Attachment added: "sudo lsusb -vvv"
http://launchpadlibrarian.net/29160986/sudo-lsusb-vvv.txt
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because you are a memb
hello stefan,
here some ifo, hth...
attaching hdd with usb-ide adapter
** Attachment added: "lsusb output"
http://launchpadlibrarian.net/29160797/sudo-lsusb-vvv.txt
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification becau
(plugged it in, and off again)
** Attachment added: "dmesg output"
http://launchpadlibrarian.net/29160866/dmesg.txt
--
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 subscr
> 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
>> 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 Erics
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
> 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 mig
>Exactly this with slightly different strings. And two other similar additions
>for the Ericsons.
which strings you've used?
--
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
> 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.
> t
@Stefan Bader, what patch did you add to the kernel?
something like this:
UNUSUAL_DEV( 0x0dc4, 0x0073, 0x0001, 0x0001,
"Macpower",
"Storage",
US_SC_DEVICE, US_PR_DEVICE, NULL,
US_FL_FIX_CAPACITY),
to the drivers/usb/storage/unusual_devs
Stefan Bader wrote:
> grawity wrote:
>> Sony-Ericsson W760i, lsusb output attached.
>
> Hm, well _that_ id should already be in. Have you tried the kernel I mentioned
> above?
I just tried it, and it partially works.
The phone presents itself as _two_ removable devices - one for internal
memory,
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
Sony-Ericsson W760i, lsusb output attached.
** Attachment added: "lsusb output"
http://launchpadlibrarian.net/29149794/lsusb-massstorage.txt
--
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 Ubu
@lpad, can you try the v2 version at
http://people.canonical.com/~smb//bug287701/ ?
--
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 mai
here ya go:
Bus 001 Device 004: ID 0dc4:0073 Macpower Peripherals, Ltd
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacke
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:/
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 patc
lpad, can you add the lsusb information for the storage device? The part
you supplied is for the integrated hub.
--
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
my device is vantec nexstar gx:
http://www.vantecusa.com/front/product/view_detail/182
dmesg:
[12020.656380] usb 1-1.1: new high speed USB device using ehci_hcd and address
12
[12020.800029] usb 1-1.1: configuration #1 chosen from 1 choice
[12020.800601] scsi7 : SCSI emulation for USB Mass Stora
@aecl and lpad, if you want to get any change, please supply both dmesg
and "sudo lsusb -vvv"
@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 wheth
same problem here with 2.6.28-13 kernel.
real showstopper for me.
--
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-
Doesnt work for me either.
# uname -r
2.6.28-13-generic
[12025.835546] sdd: sdd1
[12025.849684] sd 7:0:0:0: [sdd] Attached SCSI disk
[12025.849866] sd 7:0:0:0: Attached scsi generic sg3 type 0
[12025.953475] sd 7:0:0:0: [sdd] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK
[12025.953
Using Ubuntu Jaunty
Linux richard 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009
i686 GNU/Linux
I still have the same problem using Sony Ericsson w760i as a massive
storage device. I get lot of this lines like:
[ 176.583368] sd 7:0:0:1: [sdg] Sense Key : No Sense [current]
[ 17
my USB device now works in the latest ubuntu kernel: 2.6.28-13-generic
thanks everyone.
jdawgaz
--
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.
--
ub
I am unable to test this myself - unfortunately no access to a USB hard
drive.
--
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
Thanks Tormod, think I was getting a little muddled up :)
This can still be tested in Karmic also, based on the 2.6.30 kernel for
reference.
--
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 Ubunt
To clarify your clarification :)
[1] current Jaunty means up to date with newest kernel update (released a few
days ago)
[2] you can install the KernelMainBuilds in your Jaunty system.
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug not
To clarify:
[1] is definitely a no, as stated by previous users, so there is no need to
report that back guys, and
[2] if someone with this problem has any way of testing in Karmic, it would be
a great help, as Karmic uses the 2.6.30 kernel as explained above - p.s I know
it's in Alpha 2/3 sta
To be more precise here: in order to get any Jaunty SRU:
1. Check against current Jaunty
2. Compare against a recent https://wiki.ubuntu.com/KernelMainlineBuilds
(2.6.30)
3. Report whether it works in 1. and/or 2. and supply "lsusb -v" output for the
device
--
USB Hard Drive Not Accessible, vo
To see if this can be fixed in previous versions of Ubuntu, please do
steps 1 and 2 of the SRU Procedure [1] to bring the need to a
developer's attention.
[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
That's all I can suggest really, thats the procedure to get this into an
earlier v
I wonder why apparently nothing is done about this bug? I think it is
quite serious and defenetly a show stopper for new linux users, who
doesn't wants to mingle around with virtualbox and other workarounds,
just to acces their external drives. Also, it seems to be a fairly
simple bug (based on the
According to the upstream bugtracker, this was only fixed in 2.6.29,
therefore I believe the only version that will work with this issue will
be Karmic onwards, as it currently uses the 2.6.30 kernel. I am not sure
if this is being worked on to be backported, but that is why it has been
marked as F
Yes, it was quite a fix ;)
--
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.ubun
I have had a similar problem. My external USB drive absolutely cannot be loaded
in UBUNTU version 8.04 and version 9.04.
In fact, version 9.04 does not even DETECT the external USB hard drive.
In order to have access to my USB external hard drive, I have to use
version 7.04.
I wonder just what
Just confirming that my Intrepid (2.6.27-14-generic) still had this
problem. After editing 60-persistent-storage.rules with the "trick" the
problem with my Sony Ericsson K750i vanished.
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug not
Sony Ericsson C902 does not mount on Jaunty with all updates (not yet
proposed). Neither in telephone nor in data mode. No problems on the
same machine with Windows XP.
Sony Ericsson K750i on the same machine and on the same cable does auto
mount on Jaunty.
--
USB Hard Drive Not Accessible, vol_
Same problem here (sense key: no sense) with an external Maxtor 5000DV
in Jaunty. The 60-persistent-storage.rules did something. The drive
actually mounted, but then locked everything that has to do with drives
(places, commands like dmesg and fdisk all froze). So I removed them
again. Are there an
Hi all
Same problem here with a Nokia 5310 Xpress Music:
sa...@hal-9000:/etc/udev/rules.d$ uname -a
Linux hal-9000 2.6.27-11-generic #1 SMP Wed Apr 1 20:57:48 UTC 2009 i686
GNU/Linux
sa...@hal-9000:/etc/udev/rules.d$ vi /var/log/messages:
May 10 14:14:30 hal-9000 kernel: [ 3556.916044] usb 2-6
I still have this problem as well.
On Sat, May 2, 2009 at 10:09 PM, Leon 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.launch
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 member of Ubuntu
Bu
> The .deb's from kernel.org are a straight forward install.
I am unaware of .deb's at kernel.org, but until karmic kernels are
built, you can look at https://wiki.ubuntu.com/KernelMainlineBuilds for
some options
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/2647
I updated to Jaunty Desktop rc and my external drive is working again.
uname -a
Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64
GNU/Linux
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification because
I'm still having the problem with:
2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux
--
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
@FireMan300 : do you have a link? I can't find the debs on kernel.org.
I'm still having the same problems with: 2.6.28-11-server #41-Ubuntu SMP Wed
Apr 8 05:29:01 UTC 2009 x86_64 and a 067b:3507 drive.
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You rece
FYI - I installed the beta Ubuntu 9.04 (jaunty) w/ the 2.6.28-11 kernel,
& the SenseKey problem with my external USB drive has gone away. The
drive is working as before.
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You received this bug notification beca
Well two things:
1. Has this been tested under Ubuntu 9.4 Jaunty? i.e is it fixed in the
Ubuntu 2.6.28 kernels?
2. I can confirm that in Kernel 2.6.29 from kernel.org (stable 64-bit)
the drive (2116:0320) works. The .deb's from kernel.org are a straight
forward install.
--
USB Hard Drive Not
You could try using the old kernel 2.6.24-23, in my case (Nokia Phone 5220) it
works.
>Messaggio originale
>Da: f...@kth.se
>Data: 02/04/2009 19.11
>A:
>Ogg: [Bug 264789] Re: USB Hard Drive Not
Accessible, vol_id hangs
>
>How should I work around it for the mome
How should I work around it for the moment?
--
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
h
I cant use my SE C905 phone right now. When can I see a fix release into
my installation?!
--
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-b
The bug status for Intrepid says "Fix commited". But what is the
estimated time of "Fix released"?
Jarl
--
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.
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 kern
In fact it's a bug in your USB device (and in many many other too)
Your USB device does return the wrong size information (1 too large)
The kernel bug is http://bugzilla.kernel.org/show_bug.cgi?id=11843 which is the
effort to work arround the bug in the usb devices.
It did work because older kern
Ok, so it is a problem at kernel level.
Does a bug is open at kernel.org or something like that ?
Since it was working with a 2.6.24-21-generic, they should be able to correct
this bug quickly,isn't it ?
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You r
This bug does not only affect USB hard drives larger than 80 GB. I have
a Nokia 5200 cell phone with a 1 GB SD card in it that also suffers from
this problem when connect the phone as a USB mass storage device. I am
running Ubuntu 8.10, Intrepid Ibex (kernel version 2.6.27-11-generic).
This worked
Same problem with an external USB Hitachi HDD (250GB), but work fine with a 4GB
USB key.
kernel : 2.6.27-11-generic ; Distrib : Kubuntu intrepid
I think this problem exist for all HDD > 80GB. And I wonder why it was
not yet fixed if it is just a udev rule to change !! Moreover this bug
exist for
getting the same bug in intrepid 64bit 2.6.27-11-generic with a nokia
5310 Xpm
--
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
Instead of having a (always incomplete/outdated) blacklist, perhaps the kernel
can try to auto detect that error... ?
Is it (almost) "always" so, that the capacity is returned a one sector too
large ?
--
USB Hard Drive Not Accessible, vol_id hangs
https://bugs.launchpad.net/bugs/264789
You rece
... and renders dm "fakeraid" installations unbootable. It is NOT the
correct fix. The correct fix is to remove the infinite retry loop from
the kernel SCSI error code and blacklist all the bad devices so the
kernel knows that they return a capacity value that is one sector too
large. Sadly the lat
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 1
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
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 thi
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 rec
I still having this bug too with Nokia 6230i. It renders Ubuntu almost
unusable for me, since the phone is always with me, so it's great than
to carry my all data on it (no other pendrives etc are needed),
photos/musics, etc, so it would be a must every time for me, but I can't
use Ubuntu Intrepid
I'm using 2.6.27-11 and still unable to mount a Sony Ericson 800i that
I used to be able to mount in Hardy.
--
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 Ubu
Still getting these errors with 2.6.27-11 from intrepid-updates:
[ 327.945908] sd 9:0:0:0: [sdc] Sense Key : No Sense [current]
[ 327.945913] sd 9:0:0:0: [sdc] Add. Sense: No additional sense information
[ 327.949057] sd 9:0:0:1: [sdd] Sense Key : No Sense [current]
[ 327.949063] sd 9:0:0:1:
Correct, I have installed 2.6.28-4 and 2.6.28-5(currently) and the
problems I had with the external drive not working are gone.
r...@kaput:~# uname -a
Linux Kaput 2.6.28-5-generic #13-Ubuntu SMP Wed Jan 21 21:54:44 UTC 2009 x86_64
GNU/Linux
r...@kaput:~# dpkg -l | grep linux-image-2.6.28-
ii li
Based on the feedback reported, it looks like verification has failed to
me, marking as such.
According to the upstream bugreport, this issue should be fixed in
2.6.28, which is what Jaunty's kernel is based on. I'm closing that
portion of the bug, but it would be great if someone affected by this
same problem here with an external usb hard disk.
perfectly works under windows or after removing ehci_hcd (SLOW!).
udev patch doesn't solve.
dmesg:
usb 1-6: reset high speed USB device using ehci_hcd and address 3
usb 1-6: reset high speed USB device using ehci_hcd and address 3
usb 1-6: reset hi
@Tim Wright
I assume when you say 'don't do that' you mean, don't submit the bug
fix? As opposed to 'don't make the change to your config'.
The changes suggested to "60-persistent-storage.rules" worked an
absolute treat for me. I understand that you want the correct fix in the
kernel for both the
I have the same problem with my log files being filled with the following...
Jan 8 19:30:36 media-linux kernel: [ 525.910359] sd 4:0:0:0: [sdb] Sense Key :
No Sense [current]
Jan 8 19:30:36 media-linux kernel: [ 525.910367] sd 4:0:0:0: [sdb] Add. Sense:
No additional sense information
for 100'
This usb bridge is affected by the bug too.
Bus 007 Device 004: ID 152d:2338 JMicron Technology Corp. / JMicron USA
Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Device Descriptor:
Another device for the list: Sony Ericsson K850i mobile phone. It used
to work for some time with Ubuntu 8.04 but I don't remember at which
kernel update. Upgrading to 8.10 didn't work, obviously. Editing 60
-persistent-storage.rules and replacing 40-permissions.rules doesn't
seem to work either:
http://bugzilla.kernel.org/show_bug.cgi?id=12099 is an example of
needing to added the UNUSUAL_DEV entry to fix up the the returned
capacity. However, the kernel is also still broken. Attempting to do I/O
to an illegal offset should never result in an infinite loop of retries.
This in essence is t
As I've written at bug 300394 : is it possible that this kernel bug
report is related? http://bugzilla.kernel.org/show_bug.cgi?id=12099
--
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,
Please do NOT do this. That is not the correct fix. The bug is with the
USB/SCSI retry logic (which changed between 2.6.26 and 2.6.27 and causes an
infinite retry loop in this case).
I tried the adding ENV{DEVTYPE}=partition workaround a while ago and rendered
my system unbootable and I got to s
Thanks kja999, it works for me !
I've followed the bug on redhat's bugzilla and I've fixed udev's rules,
I'm attaching the patch for an up to date intrepid, based on upstream
udev tree:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=blobdiff;f=etc/udev/rules.d/60
-persistent-
storage.rules;h=8
See https://bugzilla.redhat.com/show_bug.cgi?id=473017
Its a problem with udev. See comment #3 on the list for the workaround
--
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
2.6.27-11 does not solve the problem here, either.
--
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.ubunt
I've tried 2.6.27-11 as well, the problem still exists here for me too.
Bus 002 Device 006: ID 0421:0429 Nokia Mobile Phones 6230i MultiMedia Card
--
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
Just tried 2.6.27-11 from proposed and it still doesn't work with my
CompactFlash reader (07c4:a400).
vol_id hangs as usual.
--
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
Got 2.6.27-11 from proposed with apt-get upgrade today and booted it.
Still getting the same errors with Nokia 6500c phone in storage mode.
--
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
B
1 - 100 of 195 matches
Mail list logo
