From: Stefan Smietanowski <stesmi@stesmi.com>
To: hanasaki <hanasaki@hanaden.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6 - wrong identifcation of kt600 and usb 2.0 as 1.1 - kernel issue? wrong mobo in the box? .....
Date: Wed, 21 Jan 2004 10:00:47 +0100 [thread overview]
Message-ID: <400E3FBF.8000100@stesmi.com> (raw)
In-Reply-To: <400E1EC5.5090809@hanaden.com>
Hi.
> I just bought the Soyo KT600 Dragon Ultra Platinum Edition
> http://www.soyousa.com/products/proddesc.php?id=280
> The below lspci and dmesg output appears to be telling me that the
> motherboard has:
> REPORTED
> ========
> KT400
> 8 usb 1.1 ports
> 2 usb 2.0 ports
>
> IN THE MOTHERBOARD SPEC
> =======================
> KT600
> 8 usb 2.0 ports
> 0 usb 1.1 ports
>
> I am not much of a kernel guru and know zero about USB. Can someone
> explain this to me? Is it a kernel issue of misidentifying hardware?
> Did someone put the wrong motherboard in the box? I tried looking at
> the kt600/kt400 chips under the fan/heatsink but the darn thing seems to
> be glued onto the motherboard.
The fan/heatsink wasn't glued to my boards at least (I have two of
those). You just have to squeeze the plastic things on the back
of the board and it'll go off. I had a fan on mine. You?
All ports are USB 2.0. What you're missing is that you (afaik) use
UHCI to talk to USB 1.1 devices (1.5 and 12Mbit/s) and EHCI to talk
to USB 2.0 devices (up to 480Mbit/s). It should just work
out of the box. Try inserting a USB 2.0 device into each port and
see what it says. It works as USB 2 here with my Creative Zen NX
and I tried a few ports. THe only thing that isn't USB2 is the
card reader package that you got in the box. It's USB1.1 only.
// Stefan
prev parent reply other threads:[~2004-01-21 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 6:40 kernel 2.6 - wrong identifcation of kt600 and usb 2.0 as 1.1 - kernel issue? wrong mobo in the box? hanasaki
2004-01-21 9:00 ` Stefan Smietanowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=400E3FBF.8000100@stesmi.com \
--to=stesmi@stesmi.com \
--cc=hanasaki@hanaden.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox