Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

The usb controller is on board - so I think it cannot be a PCI problem.
Anyway, I got myself a extra USB controller card (D-LINK DUB-A2) and I disabled the on board controller in the BIOS. The results are exactly the same.
Strangely enought, I can fdisk /dev/sda and view the partition table. I tried several times to repartition the disk (on my working FC3) and reformatting the drive, using all kinds of file systems.

I don't really have a good conclusion but here is a few things I see. You are using the uhci-hcd module for the orginal USB onboard controller. That is used for some version 1.0-1.1 usb controllers. Other 1.0-1.1 controllers use ohci-hcd module. For 2.0 USB controllers you use ehci-hcd module. So if on board usb is disabled and the dlink controller is plugged then just use ehci-hcd module, since my search shows that controller is a 2.0 usb controller.

Output of /proc/bus/usb/devices is showing a 12mb devices. If it was seeing the dlink 2.0 it should say 480mb. I would turn on the onboard usb controller and still have the dlink controller plugged in and see if the /proc/bus/usb/devices differ as far as addition devices. If there is no difference then the dlink card is not plugged in or is not compatiable with any of the USB modules.

Never used that controller and don't know if it is good or bad. Does it work with other USB devices?

My only experience with pci USB 2.0 controllers are those from Adaptec. Never had a problem with my setup.

I re-partitioned the drive and reformatted the partitions on it.
Still I have the onboard controller disabled and I moved the new USB D-LINK controller to a different PCI slot.
And wow, I can mount it and touch /mnt/maxtor/test.txt actually put a file on it ! Victory.

However the system is now soooooooo slow that I couldnt get a reply posted here and had to switch pc's.
The display refreshes now so slow that I would wait 5 mins for a typed text to appear. Maybe I have some kind of interrupt conflict ?

Did I mention that my bios is <2000 and that ACPI is disabled for this reason. Can this be related to this ?
And another question, I can see 4 ports in the /proc/bus/usb/devices, but the D-LINK only has 2. I'm guessing the onboard controller isnt really disabled then ?

Can not say its an interrupt issue or not. Since moving from on pci slot to another it could be. So if the card is not in the machine, everything works great minus the 2.0 drive? My only other thought is try a different brand of USB controller.