Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My ancient warrior, Thinkpad T20, has one USB connector. I bought a Targus 4-port USB hub as a USB port "expander". When I connect it to the laptop, the light on the hub glows, so power is getting to it. When I attach my Zire 31 PDA to sync with Korganizer (running Kubuntu 8.04), the only way the PDA will sync is if I first issue an
Code:
lsusb
on the CLI. Thinking that this was not normal, I removed the USB hub and connected the PDA directly. Within a second or two, the sync process just works. Running
Code:
tail -f /var/log/syslog
without the USB hub shows hald doing its thing correctly and the PDA connects via ttyUSB0 and ttyUSB1, as it should. Running it with the USB hub shows hald not seeing the PDA until I enter
Code:
lsusb
.
Is there a udev rule or something that I need to set up to make the 4-port be automagically recognized?
Did you try plugging in the hub's auxillary power? Sometimes the hub cannot be adequately powered with just the USB power, so there would be an auxillary power adapter.
Did you try plugging in the hub's auxillary power? Sometimes the hub cannot be adequately powered with just the USB power, so there would be an auxillary power adapter.
It's self-powered -- off the USB wire from the laptop.
htnakirs & AuroraCA,
You both mention inadequate power, a h/w solution, for a problem that already has a manual s/w solution (running lsusb). OP asked for help in configuring his/her system:
Quote:
Originally Posted by jglen490
Is there a udev rule or something that I need to set up to make the 4-port be automagically recognized?
Not to be too rude, but what makes either of you think that extra power will help the hub to be recognized by the system, when it works properly once recognition has been manually triggered w/ lsusb? Please explain or stop suggesting extra power.
Quote:
Originally Posted by jglen490
It's self-powered -- off the USB wire from the laptop.
(Just to be sure.) Does this mean that it has neither an external power supply, nor 2nd USB connector to draw extra power?
A bus-powered hub is a hub that draws all its power from the host computer's USB interface. It does not need a separate power connection. However, many devices require more power than this method can provide, and will not work in this type of hub.
USB current (related to power) is allocated in units of 100 mA up to a maximum total of 500 mA per port. Therefore a compliant bus powered hub can have no more than four downstream ports and cannot offer more than four 100 mA units of current in total to downstream devices (since one unit is needed for the hub itself). If more units of current are required by a device than can be supplied by the port it is plugged into, the operating system usually reports this to the user.
In contrast a self-powered hub is one that takes its power from an external power supply unit and can therefore provide full power (up to 500mA) to every port. Many hubs can operate as either bus powered or self powered hubs.
However, there are many non-compliant hubs on the market which announce themselves to the host as self-powered despite really being bus-powered. Equally there are plenty of non-compliant devices that use more than 100 mA without announcing this fact (or indeed sometimes without identifying themselves as USB devices at all). These hubs and devices do allow more flexibility in the use of power (in particular many devices use far less than 100 mA and many USB ports can supply more than 500 mA before going into overload shut-off) but they are likely to make power problems harder to diagnose.[original research?]
Some powered hubs do not supply enough power to support a 500mA load on every port. For example, many 7 port hubs come with a 1A power adapter, when in fact seven ports could draw a maximum of 7 x 0.5 = 3.5A, plus power for the hub itself. The assumption is that the user will most likely connect many low power devices and only one or two requiring a full 500mA.
Last edited by AuroraCA; 12-25-2008 at 08:12 AM.
Reason: Corrected link
Thank you archtoad6. The USB hub does have an extra USB connector for power, but my laptop has only one USB port. I suspect that power is not an issue as the device connected to the USB hub is a PDA which is self powered. That and I left the PDA connected for a few hours when the battery was initially showing about half power. When I checked later (to see if the PDA was being recognized) the battery meter showed as full -- so power is flowing through the USB hub to the PDA's connector.
To reiterate, when I plug the PDA into the USB hub, my laptop only sees the PDA if I enter an "lsusb" command. When I plug the PDA directly into the laptop's USB port, the PDA is recognized almost instantly. Therefore, I believe that it is the USB port itself that is not being recognized until the "lsusb" command is issued.
So perhaps a udev rule, or something that the hal daemon can use, is needed to properly activate the USB hub. If not, then it's O.K., I can just take a second or two for the "lsusb" command since I always have a konsole open.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.