Am 07.11.2010 16:52, schrieb Alan Stern:
On Sun, 7 Nov 2010, Daniel Spannbauer wrote:
Am 07.11.2010 03:24, schrieb Alan Stern:
On Sat, 6 Nov 2010, Daniel Spannbauer wrote:
Hello,
I use on m HTPC (Ubuntu Lucid Lynx, Kernel 2.6.25) a LCD-Display from
Soundgraph (http://www.soundgraph.com/oem-lcd-feature-en/). This Display
is connected to the USB-Bus to show several messages.
What chipset does the computer use? What does "lspci" show?
Hello Alan,
Here is the Output of "lspci":
root@vdr:~# lspci
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory
Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge
(rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory
Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200]
Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory
Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI
USB 1.1 Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI
USB 2.0 Controller (rev a1)
00:04.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI
USB 1.1 Controller (rev a1)
00:04.1 USB Controller: nVidia Corporation MCP78S [GeForce 8200] EHCI
USB 2.0 Controller (rev a1)
...
It's not surprising that nVidia has this problem, considering its other
problem.
And how can I solve this?
Can you try using a 2.6.37-rc1 kernel?
Ok, will try it. As I told you, I testet the 2.6.36 with the patches for
the NVIDIA-Chipset posted by you, but there was no change.
Oh. Then 2.6.37-rc1 probably won't help, but it's still worth a try.
What happens if you unload the display's driver before shutting down?
Hello Alan,
you are right, 2.6.37 RC1 seems to do the trick. The display stays dark...
Thanks a lot
Regards
Daniel
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html