From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
Date: Sat, 30 Oct 2004 03:23:41 +0000 [thread overview]
Message-ID: <20041030032341.GE13757@vrfy.org> (raw)
In-Reply-To: <1098925336.41804518e7430@mail.utca.hu>
On Fri, Oct 29, 2004 at 03:37:28AM +0200, Csan wrote:
> Idézés Kay Sievers <kay.sievers@vrfy.org>:
> > On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
>
>
> > Could you please
> > > > post the output of:
> > > >
> > > > ls -l /sys/bus/usb/devices
> > >
> > > # ls -l /sys/bus/usb/devices
> > > -r--r--r-- 1 root root 0 2004-10-29 01:10 /sys/bus/usb/devices
Greg, any idea how it can happen, that the usb subsys does not create any
/sys/bus/usb/* entry at all?
Thanks,
Kay
> > What usb chipset is that (lspci)?
>
> # lspci
> 0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
> Controller/Host-Hub Interface (rev 03)
> 0000:00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP
> Bridge (rev 03)
> 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #1 (rev 02)
> 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #2 (rev 02)
> 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #3 (rev 02)
> 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI
> Controller (rev 02)
> 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82)
> 0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02)
> 0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100
> IDE Controller (rev 02)
> 0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
> Controller (rev 02)
> 0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
> 0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem
> Controller (rev 02)
> 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
> [Radeon Mobility 9000 M9] (rev 01)
> 0000:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
> Controller (rev 80)
> 0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 0000:02:04.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
>
>
> > Which *_hcd driver (lsmod) is used?
>
> # lsmod | grep hci | grep -v 1394
> hci_usb 13888 3
> bluetooth 49604 7 hci_usb,rfcomm,l2cap
> uhci_hcd 33136 0
> ehci_hcd 32004 0
> usbcore 119012 9
> cdc_acm,hci_usb,usbhid,uhci_hcd,ehci_hcd,usbmouse,usbkbd
>
> # dmesg | grep hcd
> ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
> ehci_hcd 0000:00:1d.7: irq 201, pci mem e0a5b000
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
> uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
> uhci_hcd 0000:00:1d.0: irq 177, io base 00001800
> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
> uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
> uhci_hcd 0000:00:1d.1: irq 185, io base 00001820
> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
> uhci_hcd 0000:00:1d.2: irq 193, io base 00001840
> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&opÃk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-30 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
2004-10-28 21:31 ` Kay Sievers
2004-10-28 23:41 ` Csan
2004-10-28 23:56 ` Kay Sievers
2004-10-29 1:37 ` Csan
2004-10-30 3:23 ` Kay Sievers [this message]
2004-10-30 16:00 ` Greg KH
2004-10-31 0:35 ` Kay Sievers
2004-11-06 7:51 ` Csan
2004-11-06 17:08 ` Greg KH
2004-11-06 18:02 ` Fwd: Re: wait_for_sysfs needs an update to handle the device Kay Sievers
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=20041030032341.GE13757@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.