Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Dec 2004 00:10:29 GMT
From:      "Julien Gabel" <jpeg@thilelli.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/74989: (regression) Lost USB support between   5.2.1-RELEASE and 5.3-RELEASE on K7T266 Pro2.
Message-ID:  <200412140010.iBE0AToJ075140@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/74989; it has been noted by GNATS.

From: "Julien Gabel" <jpeg@thilelli.net>
To: "Julian Elischer" <julian@elischer.org>
Cc: freebsd-gnats-submit@freebsd.org,
	"Anish Mistry" <mistry.7@osu.edu>, freebsd-usb@freebsd.org
Subject: Re: kern/74989: (regression) Lost USB support between  
     5.2.1-RELEASE and 5.3-RELEASE on K7T266 Pro2.
Date: Tue, 14 Dec 2004 01:05:36 +0100 (CET)

 >> Ok. After playing with my BIOS settings, i decided to reset them all.
 >> And here, i can say that i previously made a mistake: *disable* ACPI at
 >> boot time _do_ the trick!
 >>
 >> The desktop is the machine equipped with the MSI K7T266 Pro2 motherboard.
 >> Note: the BIOS firmware is up to date with the last revision available.
 >>
 >> The update during the RELENG_5 branch seems to be at the origin of the
 >> USB support problem on this motherboard.
 
 > have you also disabled "legacy USB support"?
 
 I try this parameter as well. Here is what i get:
 --------------------------------------------------------
 USB Legacy Support   |   ACPI enable   |    ACPI disable
 --------------------------------------------------------
 "disable"            |   USB ko :(     |    USB ko :(
 "all device"         |   USB ko :(     |    USB ok
 --------------------------------------------------------
 
 > so, in your estimation is the problem in the ACPI code or the USB code?
 
 Sorry, i don't really know. I said it must be ACPI since it worked in a
 past release with ACPI enable, however it may be a problem in the USB
 code.
 
 I will try to submit debugging information on ACPI as pointed out by
 Anish. Are they any other tests i can do in order to know what this
 problem might be?
 
 -- 
 -jpeg.
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412140010.iBE0AToJ075140>