jtclicker, this bug report is being closed due to your last comment
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/231049
Title:
usb connect problems
--
ubuntu-bugs mailing list
Even after trying all the tricks mentioned here my sansa clip is not
mounting at all (not at usb 1.1 or via my keyboard's usb hub). I'm
running Intrepid and the clip's firmware is 1.01.32.
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug notification because
Firstly attached is a report, after I did the lsusb trick to get the
sansa clip detected. This lists the sansa clip in the lsusb log which my
previous report didn't.
lepinkäinen, I suggest you run the commands listed in comment 20 above
(with correction from comment 23) and post the report file.
Hello TJ,
I'm grateful that someone's looking at this.
Are you able to rename this bug to something more appropriate?
Sandisk Sansa clip/furze doesn't mount in Hardy - usb connect issues
Is a suggestion.
I have Hardy installed, and because it's broken a large number of
things, I restored a
TJ,
Find attached the system report for my 2gb Sansa Clip running firmware
v01.01.32A in MSC connection mode.
I plugged in the sansa it wasn't detected in , I ran the your script,
and the this caused the sansa to get detected and mounted at USB2 speed.
Maybe I guess because of the lsusb command
lsusb wierdness. I plugged in my sansa clip, it wasn't detected.
I then run strace -o lsusbfix.log lsusb
The lsusb didn't show my sansa, only the ps2/usb keyboard/mouse adapter.
However a few seconds later the sansa was detected and mounted
automatically at USB2 speed.
You also asked about what
The power off trick suggested by Jaime doesn't work for me however my
sansa has a slightly newer firmware (v01.01.32A), and my PC has a
slightly newer kernel on my hardy system (2.6.24-23-generic)
The running lsusb a few times trick works for me 95% of the time, only
100% (but awkward) fix I
Mine's a Fuze, but suffers the same problem. Firmware version is
01.01.22F
Mar 20 20:43:56 upstairs-linux kernel: [13103.668039] usb 1-6: new high speed
USB device using ehci_hcd and address 4
Mar 20 20:43:57 upstairs-linux kernel: [13104.808036] usb 3-3: new full speed
USB device using
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It looks as if this issue is related to another USB speed issue,
although not caused by or solved by it - bug #296710 warning: ehci_hcd
loaded AFTER uhci_hcd and ohci_hcd
However, in this particular case it looks rather that the particular
system hardware is getting confused and may be related to
Thanks TJ for taking an interest.
Looking at your script I think the lspci command is wrong since lspci
--vvnn gives an error. Does it have an extra -?
I'm assume you want us to run the script maybe 30s after we plug the
problem device (sansa clip) in?
I'll send the results in a few days when I
TJ can you give a possible explanation as to why running lsusb a few
times gets the device detected?
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Peter - oops: too many hyphen/switch characters (--)
It should be a single hyphen switch:
lspci -vvnn /tmp/reports/lspci-vvnn.log
As to an explanation, we might be able to deduce one once information
from various systems is in. In theory lsusb shouldn't make any different
since it is only
Peter, a a side project, I'd be interested to know if lsusb is opening
any files or devices for write access, or otherwise touching a
file/device in a way which changes its status.
If you can get the system into a state where the problem occurs and then
repeatedly run lsusb until it fixes it,
Greetings, I also have a Sansa Clip, firmware v01.01.29A, and I am
having the same symptoms described in this bug report. I am running
Hardy 8.04 (kernel 2.6.24-22-generic).
I found a message on the Sansa forums talking about this problem and a
proposed work around of unloading the ehci_hcd
On Thu, 2009-03-19 at 21:43 +, Jaime Carpenter wrote:
I have found another solution for me that gives USB2 (480Mbps) every
time without unloading the ehci_hcd module. This is not optimal, but
works:
* I plug in the Sansa Clip
* Sansa powers up and acts like it connects
* Hardy does
Something else occured to me about this. When this happens is the USB
device connected to the port whilst the BIOS is POSTing?
For PCs who's BIOS support boot from USB this might/would trigger the
BIOS into initialising at least one USB host controller which would
claim the external port(s). It
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
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
I'm having trouble connecting my Sansa Clip as well.
In Hardy, USB negotiation seems to fail when plugging into a USB port
that's connected directly to the motherboard, but it works when plugging
into the USB hub in my monitor.
In Intrepid alpha 6, high speed USB negotiation fails, and it falls
Intrepid fixed the problem for me
dmesg
61)
[0.00] ACPI: BOOT 000FD2DE, 0028 (r1 DELL8300 7 ASL
61)
[0.00] ACPI: PM-Timer IO Port: 0x808
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[
jtclicker are you sure it fixed it completely?
I thought intrepid used 2.6.27 kernels, but the uname command show in 2.6.24-21
Also it seems you still have the same -110, -32 error messages.
I found intrepid kernels (2.6.27) automatically mount my sansa clip, but
only at usb1 speeds. Which is a
I should have been clearer, sorry! The data attached is from gutsy, not
intrepid. Under intrepid I didn't test the speeds, but it mounted itself
and unmounted. Have you checked the speed issue? Would it help if I sent
the data from intrepid?
--
usb connect problems
Data for intrepid
dmesg
[0.00] #0 [00 - 001000] BIOS data page == [00
- 001000]
[0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000
- 002000]
[0.00] #2 [006000 - 007000] TRAMPOLINE == [006000
-
Here a summary for my sansa clip.
Under gutsy, debian lenny and a 2.6.27 kernel (from interpid):
My clip automounts but only at USB1 speeds
(Hint the easy way to check is do properties on the drive icon, click on
drive tab, if connection says 12Mbps its USB1, 480Mbps is USB2)
However if I boot
A further update, lsusb doesn't alway kick the usb device into life. The
only sure way seems to be to unload the ehci_hcd module (and reload it
if you want USB2 speeds)
I've since install a 2.6.27 kernel from https://launchpad.net/~kernel-
ppa/+archive on my ubuntu hardy machine. I'm not sure how
The unloading and reloading of the ehci_hcd module gave me an idea. Does
the ehci_hcd do something different when the device is plugged in, than
from when it starts up.
I found that by booting (standard hardy 2.6.24 generic kernel) with the
sansa clip plugged in. The sansa mounts automatically at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Can you try with intrepid live-cd to see if the issue is
fixed there? Also, please include the information requested at
https://help.ubuntu.com/community/DebuggingUSBStorage in your report.
** Changed in: linux
I'm having the same problem with my Sansa Clip 2gig not being mounted. I get
the same error:
hub 8-0:1.0: hub_port_status failed (err = -32)
Sansa version v01.01.18a
I have tried in MSC mode and Auto mode.
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug
I have the same problem with a sansa clip. In gutsy on my old computer
it mounted ok but only ever at USB 1.1 speeds.
On my new Dell inspiron 530 in fails to mount 95% of the time with:
[ 105.895973] usb 8-3: new high speed USB device using ehci_hcd and address 2
[ 110.517165] ehci_hcd
Further update, and I have similar problems on the same dell machine
running, the current lenny version of debian which has a newer kernel.
But back to hardy.
As noted in the ubuntu forum thread, running the lsusb command sometimes
gets the device detected. Sometimes once is not enough though.
I also have a Sandisk Sansa Fuze and am receiving the same error with
Hardy:
[ 283.344161] usb 4-3: new high speed USB device using ehci_hcd and address 3
[ 285.017541] ehci_hcd :00:1d.7: port 3 reset error -110
[ 285.017558] hub 4-0:1.0: hub_port_status failed (err = -32)
Just as Evan
I got a similar error message with my Sandisk Sansa Fuze MP3 player. I
found a solution here:
https://answers.launchpad.net/ubuntu/+question/4272
Try 'sudo modprobe -r ehci_hcd'
It worked for me; now my mp3 player is detected normally. BTW, I'm
running Hardy Heron fully updated as of today,
I'm having different USB problems on Hardy.
On a fresh boot, there are no problems. But when I resume from
hibernation: some USB ports do not work well.
When I connect to one of my USB ports (on the left side of my ThinkPad),
devices seem to connect with no problems. But when I connect to either
[ 12.829854] MEM window: efc0-efcf
[ 12.829858] PREFETCH window: disabled.
[ 12.829863] PCI: Bridge: :00:1e.0
[ 12.829866] IO window: c000-cfff
[ 12.829871] MEM window: efb0-efbf
[ 12.829875] PREFETCH window: disabled.
[ 12.829894] ACPI: PCI Interrupt
I am having the exact same issue shown above.
More details are here:
http://ubuntuforums.org/showthread.php?t=790517highlight=sansa+clip
--
usb connect problems
https://bugs.launchpad.net/bugs/231049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
36 matches
Mail list logo
