Martin, Thank you.My bluntness comes from numerous bugs which I reported to
Ubuntu,but there was no effort seen to resolve any.
Hopefully,this bug is resolved now.I left Ubuntu because of the bug not
resolved even after a version upgrade.
No,this bug had nothing to do with the hardware.The same
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Martin,
If you lookup the history of the bug,you see others and I have given so
much of inormation.It is you,who as assignee never investigated and
called for more input.Now you are closing it for lack of information
from reporters!Great indeed and great future for Ubuntu distribution!
--
USB
Comment 13 indicated that it was indeed a hardware problem, and I never
got any dmesg output (see comment 14) from Jackflap, which would give
some more information about the problem.
Parameshwara, your dmesg output in comment 6 also points to a hardware
problem:
[ 36.652000] usb 5-3: device
The automount magic is not directly tied to power consumption, etc., but
it is possible that the effect happens because at the time you connect
the drive, the connection is too brittle for a robust file system
detection and mount. Maybe it settles down a bit later when all the
capacitors get fully
I've actually managed to solve this one by doing something completely
different.
I've got a black WD Passport drive formatted as ntfs which uses a small
10cm USB cable. Whenever I'd boot up with the drive plugged in with this
cable, it would be detected on boot only half the time. If I used a
Can you please generate a hal debug output as described on the second
half of https://wiki.ubuntu.com/DebuggingRemovableDevices ? Please boot
with the drive already attached and skip steps 5 and 6 (i. e. just let
the output settle and then stop hal with Control-C). Thank you!
** Changed in: hal
** Attachment added: opensuse hal with USB thumbdrive connected / booted with
http://launchpadlibrarian.net/11796515/hal-opensuse.log
--
USB drive not detected if booted with drive connected
https://bugs.launchpad.net/bugs/49890
You received this bug notification because you are a member of
Please find attached hal.log as you wanted.
Also is attached similar hal log with opensuse.In opensuse,I do not experience
this bug.In case this might be of help.
** Attachment added: hal.log
http://launchpadlibrarian.net/11796489/hal.log
--
USB drive not detected if booted with drive
** Changed in: hal (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
USB drive not detected if booted with drive connected
https://bugs.launchpad.net/bugs/49890
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: hal (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Confirmed
--
USB drive not detected if booted with drive connected
https://bugs.launchpad.net/bugs/49890
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I have what I think may be the same problem, though in my case it is not
100% reproducible.
Steps to reproduce my situation:
1. Format an external USB drive, with a partition (ext3 in my case) and
a volume label foo for that partition.
2. Turn off the computer, connect the USB drive, power it
The bug cannot atleast be
invalid when I have provided so much information and the bug continues to exist.
I think incomplete status is what the developers look for when they decide
to look into the issue.
On 11/11/07, GreatBunzinni [EMAIL PROTECTED] wrote:
Incomplete? what's missing?
--
Incomplete? what's missing?
--
USB drive not detected if booted with drive connected
https://bugs.launchpad.net/bugs/49890
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: hal (Ubuntu)
Status: Invalid = Incomplete
--
USB drive not detected if booted with drive connected
https://bugs.launchpad.net/bugs/49890
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I am pasting below the output of dmesg and lsusb.I booted with problem
devices and next time booted and plugged them in.I can see the light on
thumb drive going off right as kernel is loading when booted with.
One interesting sidenote : when by mistake I had a USB scanner plugged
in with the
The above bug exists even on Kubuntu/Ubuntu 7.10
There is an additional point. The USB mouse behaves jerky and slow after
this.
There is a behaviour this may be connected to or not.If a USB CD-RW is
connected,that is recognised as shown by dmesg and kinfocenter.But as
soons as K3B is
I've just installed Kubuntu 7.10 and yes, this bug still persists. I've
just booted into Kubuntu with two USB mass storage devices connected (a
external HD and a small USB flash drive) and neither is detected.
lsusb output:
[EMAIL PROTECTED]:~$ lsusb
Bus 002 Device 003: ID 4146:ba01 USBest
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
feel free to submit bug reports in the future.
** Changed in: hal (Ubuntu)
Thanks for your bug report. With the drive attached could you run
'lsusb' and add the output? Could you also add the output of 'dmesg'
after booting the system with the USB drive connected?
** Changed in: hal (Ubuntu)
Assignee: (unassigned) = Brian Murray
Status: Unconfirmed = Needs
thanks for your bug report...
I'm just guessing the package name (I just can't learn whether it's hal
or not ;) )
** Changed in: Ubuntu
Sourcepackagename: None = hal
--
USB drive not detected if booted with drive connected
https://launchpad.net/bugs/49890
--
ubuntu-bugs mailing list
21 matches
Mail list logo
