Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller. But It always caused rebooting when the option rom try to initialize the controller. I attached all of the messages, and looking for some help. Until now my doubt is the real bus/dev/func is 06/05/01, but while seabios search it as 00/05/01.
oh... i find libpaylod usb stack hard code the bus to 0. it should display the bus number.
On Mon, Jul 27, 2009 at 11:42 PM, Jason Wang wangqingpei@gmail.com wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller. But It always caused rebooting when the option rom try to initialize the controller. I attached all of the messages, and looking for some help. Until now my doubt is the real bus/dev/func is 06/05/01, but while seabios search it as 00/05/01.
-- Jason Wang Peking University
On Mon, Jul 27, 2009 at 11:42:18PM +0800, Jason Wang wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller. But It always caused rebooting when the option rom try to initialize the controller. I attached all of the messages, and looking for some help. Until now my doubt is the real bus/dev/func is 06/05/01, but while seabios search it as 00/05/01.
Please post a log with the seabios debug level set to 6.
-Kevin
hi Kevin, the attach file is the whole log
On Tue, Jul 28, 2009 at 7:32 AM, Kevin O'Connor kevin@koconnor.net wrote:
On Mon, Jul 27, 2009 at 11:42:18PM +0800, Jason Wang wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller. But It always caused rebooting when
the
option rom try to initialize the controller. I attached all of the
messages,
and looking for some help. Until now my doubt is the real bus/dev/func is 06/05/01, but while
seabios
search it as 00/05/01.
Please post a log with the seabios debug level set to 6.
-Kevin
Hi Jason
On Tue, Jul 28, 2009 at 9:17 AM, Jason Wangwangqingpei@gmail.com wrote:
hi Kevin, the attach file is the whole log
On Tue, Jul 28, 2009 at 7:32 AM, Kevin O'Connor kevin@koconnor.net wrote:
On Mon, Jul 27, 2009 at 11:42:18PM +0800, Jason Wang wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller.
It seems your card(surely) has a single UHCI controller, but (maybe) 2 USB ports(I say based on you log output).
But It always caused rebooting when the option rom try to initialize the controller. I attached all of the messages, and looking for some help.
I feel it`s stranger to not see any message during the UHCI initialization, but reboot is normal, if the option ROM don`t do anything it will fallback to BIOS. I mean by "don`t do anything" if it doesn`t load the boot sector and/or start executing something when it finishes the Host Controller initialization.
Your log makes me think you don`t have a MSC device attached to any of the ports. So I have attached a patch to see if the Root Hub initialization has successfully finished, could you apply the attached patch to libpayload and show the output?
Until now my doubt is the real bus/dev/func is 06/05/01, but while seabios search it as 00/05/01.
Please post a log with the seabios debug level set to 6.
-Kevin
-- Jason Wang Peking University
Thanks....
hi dorileo, The card has two UHCI controller and one EHCI controller.And i have already attached a MSC device to the disk. it sill could not run to the function uhci_rh_enable_port
On Tue, Jul 28, 2009 at 9:39 PM, Leandro Dorileo ldorileo@gmail.com wrote:
Hi Jason
On Tue, Jul 28, 2009 at 9:17 AM, Jason Wangwangqingpei@gmail.com wrote:
hi Kevin, the attach file is the whole log
On Tue, Jul 28, 2009 at 7:32 AM, Kevin O'Connor kevin@koconnor.net
wrote:
On Mon, Jul 27, 2009 at 11:42:18PM +0800, Jason Wang wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB
card
which contained two UHCI controller.
It seems your card(surely) has a single UHCI controller, but (maybe) 2 USB ports(I say based on you log output).
But It always caused rebooting when the option rom try to initialize the controller. I attached all of the messages, and looking for some help.
I feel it`s stranger to not see any message during the UHCI initialization, but reboot is normal, if the option ROM don`t do anything it will fallback to BIOS. I mean by "don`t do anything" if it doesn`t load the boot sector and/or start executing something when it finishes the Host Controller initialization.
Your log makes me think you don`t have a MSC device attached to any of the ports. So I have attached a patch to see if the Root Hub initialization has successfully finished, could you apply the attached patch to libpayload and show the output?
Until now my doubt is the real bus/dev/func is 06/05/01, but while seabios search it as 00/05/01.
Please post a log with the seabios debug level set to 6.
-Kevin
-- Jason Wang Peking University
Thanks....
-- (°= Leandro Dorileo //\ ldorileo@gmail.com - http://www.dorilex.net V_/ Software is a matter of freedom.
Jason Wang wrote:
The card has two UHCI controller and one EHCI controller.
Note that it is not in fact a UHCI controller if it supports USB 2.0. It is difficult (maybe impossible) to find a UHCI PCI card.
An EHCI controller will only and always communicate with high-speed devices using EHCI.
The EHCI controller and it's so-called companion controllers do not mirror each port. Any connected device will only appear attached to one controller, and it will always be the same controller for a given device and a given physical port.
In other words, for you to be able to use UHCI with this PCI card, you must attach a USB 1.1-only MSC device to one of the ports.
Please have a look at the EHCI standard[1] for more details, and feel free to ask questions. Especially Figure 1-1 and the descriptions on the same page (3) are very good for getting a better understanding of these parts of USB.
//Peter
[1] http://www.intel.com/technology/usb/download/ehci-r10.pdf
On 7/29/09 3:58 AM, Peter Stuge wrote:
Note that it is not in fact a UHCI controller if it supports USB 2.0. It is difficult (maybe impossible) to find a UHCI PCI card.
An EHCI controller will only and always communicate with high-speed devices using EHCI.
The EHCI controller and it's so-called companion controllers do not mirror each port. Any connected device will only appear attached to one controller, and it will always be the same controller for a given device and a given physical port.
In other words, for you to be able to use UHCI with this PCI card, you must attach a USB 1.1-only MSC device to one of the ports.
This is interesting, since we have not seen this problem on any Intel chipset, which have EHCI controllers but do UHCI, too. It's never been a problem to use the UHCI stack with USB 2.0 capable devices. Are they doing something special? I never saw an EHCI only controller, all of them came with either UHCI or OHCI
Stefan
On Tue, Jul 28, 2009 at 09:17:09PM +0800, Jason Wang wrote:
On Mon, Jul 27, 2009 at 11:42:18PM +0800, Jason Wang wrote:
Hi all, Since DBM690T does not have UHCI controller, i bought an PCI-USB card which contained two UHCI controller. But It always caused rebooting when
the
option rom try to initialize the controller. I attached all of the
messages,
and looking for some help. Until now my doubt is the real bus/dev/func is 06/05/01, but while
seabios
search it as 00/05/01.
[...]
Attempting to init PCI bdf 00:13.0 (dev/ven 43871002) Copying option rom (size 130560) from 0xfff00000 to c0800 Checking rom 0x000c0800 (sig aa55 size 255) Running option rom at c080:0003 hello, initialize_usb 00:13.0 4387:1002.0 OHCI controller Not supported. 00:13.1 4388:1002.1 OHCI controller Not supported. 00:13.2 4389:1002.2 OHCI controller Not supported. 00:13.3 438a:1002.3 OHCI controller Not supported. 00:13.4 438b:1002.4 OHCI controller Not supported. 00:13.5 4386:1002.5 EHCI controller Not supported. 06:05.0 3038:1106.0 UHCI controller
Hi Jason,
As near as I can tell, you compiled seabios with OPTIONROM_VENDEV_1 and OPTIONROM_MEM_1 set. SeaBIOS then ran your rom when it got to device 00:13.0. The rom hung the machine. I don't see any issues with SeaBIOS from the log.
-Kevin
-
Jason Wang -
Kevin O'Connor -
Leandro Dorileo -
Peter Stuge -
Stefan Reinauer