public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo <scrooge@freemail.it>
To: linux-usb-users@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Nforce2 - usb 2.0 bug
Date: Tue, 15 Feb 2005 16:33:49 +0100	[thread overview]
Message-ID: <4212165D.7070105@freemail.it> (raw)

Hi all.
Asking on Irc (thanx riel!), they suggested to write a sort of bug-report.
I'm using a motherboard Asus A7N8X-Deluxe and the usb modules can't work 
with USB 2.0 devices (while 1.1 work with no problems).
The hardware tested is perfectly working on other computers, but with 
this motherboard the devices are recognized but can't be initialized. 
I've tried different distros (Gentoo, Debian & Debian based, Slackware, 
Mandrake ... and even Qnx, FreeBSD).
Usb 2.0 devices can correctly work if the system is booted using 
Windows, then software-rebooted in Linux, otherwise, they can't be 
initialized.
All the modules are correctly loaded. Usually i don't load uhci_hcd but, 
even modprobing it, the results don't change.
Now i'm using a Gentoo with a 2.6.10 kernel release, but i've tried 
different 2.6.x and 2.4.x kernel versions.

My lspci:

*************************************************************************
*************************************************************************

0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different 
version?) (r
ev a2)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 
(rev a2)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 
(rev a2)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 
(rev a2)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 
(rev a2)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 
(rev a2)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a3)
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a3)
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller 
(rev a3)
0000:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet 
Controller
 (rev a1)
0000:00:05.0 Multimedia audio controller: nVidia Corporation nForce 
MultiMedia a
udio [Via VT82C686B] (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 
AC97 Audio
Controler (MCP) (rev a1)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge 
(rev a3)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:0c.0 PCI bridge: nVidia Corporation nForce2 PCI Bridge (rev a3)
0000:00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire 
(IEEE 139
4) Controller (rev a3)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev a2)
0000:01:0b.0 RAID bus controller: Silicon Image, Inc. (formerly CMD 
Technology I
nc) SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
0000:02:01.0 Ethernet controller: 3Com Corporation 3C920B-EMB Integrated 
Fast Et
hernet Controller [Tornado] (rev 40)
0000:03:00.0 VGA compatible controller: ATI Technologies Inc R300 AD 
[Radeon 950
0 Pro]
0000:03:00.1 Display controller: ATI Technologies Inc R300 AD [Radeon 
9500 Pro]
(Secondary)

*************************************************************************
*************************************************************************

The problems are the same, using devfs or udev (with or without hotplug 
and coldplug).
The firmware is updated.

Thanks in advance
Paolo

                 reply	other threads:[~2005-02-15 15:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4212165D.7070105@freemail.it \
    --to=scrooge@freemail.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    /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