Feisty can't access USB ports

please attach your
lsusb > my_lsusb
dmesg > my_dmesg

I am a Ubuntu noob so I hope I did this right.

I plugged the flash stick and floppy drive into the USB ports and then executed the Terminal commands. The output is in the attachment.

first of all: This command:
dmesg > my_dmesg
will create file my_dmesg. This file you can post here. Not .odt file it
is not good, but it's working ;)

The dmesg say you what kernel did and can help find a problem.
For example this part show you that your usb_module (driver) filed.You
can try that kernel say you: "Please try using pci=biosirq."

You need presk Esc before ubuntu boot and edit kernel boot option by
pressing "e" and adding pci=biosirq.

[ 18.454705] PCI: No IRQ known for interrupt pin A of device
0000:02:05.0. Please try using pci=biosirq.
[ 18.506290] IRQ handler type mismatch for IRQ 0
[ 18.506295] current handler: timer
[ 18.506301] [<c01540fe>] setup_irq+0x12e/0x1e0
[ 18.506311] [<dc8ec3b0>] ohci_irq_handler+0x0/0x990 [ohci1394]
[ 18.506319] [<c0154253>] request_irq+0xa3/0xc0
[ 18.506324] [<dc8ec07d>] ohci1394_pci_probe+0x3cd/0x700 [ohci1394]
[ 18.506332] [<c01fb953>] pci_match_device+0x13/0xc0
[ 18.506337] [<dc8ebcb0>] ohci1394_pci_probe+0x0/0x700 [ohci1394]
[ 18.506343] [<c01fba76>] pci_device_probe+0x56/0x80
[ 18.506348] [<c0257a66>] really_probe+0x66/0x190
[ 18.506353] [<c0257bd9>] driver_probe_device+0x49/0xc0
[ 18.506359] [<c0257dae>] __driver_attach+0x9e/0xa0
[ 18.506364] [<c0256f3b>] bus_for_each_dev+0x3b/0x60
[ 18.506369] [<c0257904>] driver_attach+0x24/0x30
[ 18.506373] [<c0257d10>] __driver_attach+0x0/0xa0
[ 18.506377] [<c02572cb>] bus_add_driver+0x7b/0x1a0
[ 18.506383] [<c01fbc44>] __pci_register_driver+0x74/0xc0
[ 18.506387] [<c014421d>] sys_init_module+0x15d/0x1ba0
[ 18.506402] [<c0107a5d>] sys_mmap2+0xcd/0xd0
[ 18.506408] [<c0103280>] syscall_call+0x7/0xb
[ 18.506415] =======================

Paul Holbrook schrieb:
> I am a Ubuntu noob so I hope I did this right.
>
> I plugged the flash stick and floppy drive into the USB ports and then
> executed the Terminal commands. The output is in the attachment.
>
>
> ** Attachment added: "lsusb and dmesg .odt"
> http://librarian.launchpad.net/7556591/lsusb%20and%20dmesg%20%20%20.odt
>

I rebooted 7.04 and added pci=biosirq. I then plugged in the 2 USB devices. Terminal lsusb did not list any response and jsut gave me blank lines. dmesg output is attached.

paul@paul-home:~$ lsusb

Below is a copy of COMPUTER and FMMC is new to this display but I can't open it.

computer:///CD-RW%252FDVD%25C2%25B1RW%2520Drive.drive
computer:///SD%252FMMC%2520Drive.drive
computer:///PRESARIO.drive
computer:///PRESARIO_RP.drive
computer:///Filesystem.desktop

> Below is a copy of COMPUTER and FMMC is new to this display but I can't open it.
>
> computer:///CD-RW%252FDVD%25C2%25B1RW%2520Drive.drive
> computer:///SD%252FMMC%2520Drive.drive
> computer:///PRESARIO.drive
> computer:///PRESARIO_RP.drive
> computer:///Filesystem.desktop

This are icon's. They can't help to fix this bug ;)

This part say the kernel is broken:

[ 57.382004] IRQ handler type mismatch for IRQ 0
[ 57.382008] current handler: timer
[ 57.382015] [<c01540fe>] setup_irq+0x12e/0x1e0
[ 57.382025] [<dc8ee3b0>] ohci_irq_handler+0x0/0x990 [ohci1394]
[ 57.382033] [<c0154253>] request_irq+0xa3/0xc0
[ 57.382038] [<dc8ee07d>] ohci1394_pci_probe+0x3cd/0x700 [ohci1394]
[ 57.382046] [<c01fb953>] pci_match_device+0x13/0xc0
[ 57.382051] [<dc8edcb0>] ohci1394_pci_probe+0x0/0x700 [ohci1394]
[ 57.382058] [<c01fba76>] pci_device_probe+0x56/0x80
[ 57.382062] [<c0257a66>] really_probe+0x66/0x190
[ 57.382068] [<c0257bd9>] driver_probe_device+0x49/0xc0
[ 57.382074] [<c0257dae>] __driver_attach+0x9e/0xa0
[ 57.382078] [<c0256f3b>] bus_for_each_dev+0x3b/0x60
[ 57.382084] [<c0257904>] driver_attach+0x24/0x30
[ 57.382088] [<c0257d10>] __driver_attach+0x0/0xa0
[ 57.382092] [<c02572cb>] bus_add_driver+0x7b/0x1a0
[ 57.382098] [<c01fbc44>] __pci_register_driver+0x74/0xc0
[ 57.382102] [<c014421d>] sys_init_module+0x15d/0x1ba0
[ 57.382118] [<c0107a5d>] sys_mmap2+0xcd/0xd0
[ 57.382125] [<c0103280>] syscall_call+0x7/0xb
[ 57.382132] =======================

You can you try this ubuntu_kernel...
http://rapidshare.com/files/29473557/linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
but before you need to disable any restricted modules, the will not
work, for example nvidia driver.
to install this do:
sudo dpkg -i linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
to uninstall:
sudo dpkg -r linux-image-2.6.22-2-386

If it's working it's good. if not, you need to go upstream
www.kernel.org and report this but there.

I had this error when I tried to do the install.

paul@paul-home:~$ sudo dpkg -i linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
Password:
dpkg: error processing linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb (--install):
 cannot access archive: No such file or directory
Errors were encountered while processing:
 linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
paul@paul-home:~$

It may have failed because of restricted modules, but I am a noob and don't know which ones they are or how to disable them.

I appreciate your help.

try
md5sum linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
it will show if package checksum. it should be:
b7e2909a2502b3a98f7fe39ba08cd6db

This is what I got.

paul@paul-home:~$ md5sum linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
md5sum: linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb: No such file or directory
paul@paul-home:~$

:)))
some basics about bash and terminal

paul@paul-home:~$
______________^^^^ - this part mean, your home folder
if you write "ls" you can see what you in this folder have. If you do
not see this name -> linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb in you
home folder, mean you need to look it some where alse. For example if ho
have this file on Desktop you need do "cd Desktop".

Fishor, I am sorry but you lost me with your last message. I did try the 2 commands and got this result.

paul@paul-home:~$ ls
Desktop Examples lsusb and dmesg .odt my_dmesg
paul@paul-home:~$ cd desktop
bash: cd: desktop: No such file or directory
paul@paul-home:~$

But I don't think that was what you were trying to tell me.

I also did a file search for linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb in both home and desktop and nothing was found.

A friend of mine that talked me into trying Ubuntu sent me this note regarding my USB bug. Does this address my problem?

http://ubuntuguide.org/wiki/Ubuntu:Feisty#USB

Read this. Then send the link to your helper and ask him/her if this is what
would fix the bug. I imagine that Linux (not Ubuntu) is working on fixing
the bug and that an updated linux kernal will be released in the near future.
When it is, all you have to do is keep your Ubuntu system updated by pressing
the blinking orange button. But, anyways, ask your helper if they think this
USB 2.0 bug is the one that is keeping your USB port from being recognized by
Ubuntu and if the fix described (disabling 2.0 and using a slower USB system)
would help your problem. That way, at least, you and your helper will be on
the same page as to what they problem is...

The link you send describe random issue about usb 2.0. I can't say if it
will help you or not. You need to test it your self. Try this

sudo modprobe -r ehci_hcd
this will disable your usb 2.0

and after this, attach your new dmesg
you already how to make dmesg ;)

fishor: I went back to some of your earlier suggestions and did them.
I wehnt to this web site and downloaded
You can you try this ubuntu_kernel...
http://rapidshare.com/files/29473557/linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb

Then on terminal
paul@paul-home:~$ sudo dpkg -i linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
Password:
Selecting previously deselected package linux-image-2.6.22-2-386.
(Reading database ... 88900 files and directories currently installed.)
Unpacking linux-image-2.6.22-2-386 (from linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb) ...
Done.
Setting up linux-image-2.6.22-2-386 (2.6.22-2.6) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.22-2-386
find: /lib/firmware/2.6.22-2-386: No such file or directory
find: /lib/firmware/2.6.22-2-386: No such file or directory
find: /lib/firmware/2.6.22-2-386: No such file or directory
find: /lib/firmware/2.6.22-2-386: No such file or directory
find: /lib/firmware/2.6.22-2-386: No such file or directory
find: /lib/firmware/2.6.22-2-386: No such file or directory
Running postinst hook script /sbin/update-grub.
You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!

Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.22-2-386
Found kernel: /boot/vmlinuz-2.6.20-15-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

paul@paul-home:~$

I then restarted Ubuntu and put a flash drive into USB (at boot time there was a message about a 'compressed kernal. but it came up.) I then ran these commands on terminal

paul@paul-home:~$ md5sum linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
b7e2909a2502b3a98f7fe39ba08cd6db linux-image-2.6.22-2-386_2.6.22-2.6_i386.deb
paul@paul-home:~$
paul@paul-home:~$ lsusb
paul@paul-home:~$ dmesg > my-demesg
paul@paul-home:~$

The dmesg output is in the attachment.

I didn't try the USB 2.0 idea.

Ok. good job!
In this kernel ohci_hcd ( usb driver ) will not crash
but not working too. It says:
---------------------------------------------------------------------
[ 16.370917] PCI: No IRQ known for interrupt pin A of device
0000:00:13.0. Please try using pci=biosirq.
[ 16.370922] ohci_hcd 0000:00:13.0: Found HC with no IRQ. Check
BIOS/PCI 0000:00:13.0 setup!
[ 16.370929] ohci_hcd 0000:00:13.0: init 0000:00:13.0 fail, -19
[ 16.370946] PCI: No IRQ known for interrupt pin A of device
0000:00:13.1. Please try using pci=biosirq.
[ 16.370949] ohci_hcd 0000:00:13.1: Found HC with no IRQ. Check
BIOS/PCI 0000:00:13.1 setup!
[ 16.370955] ohci_hcd 0000:00:13.1: init 0000:00:13.1 fail, -19
---------------------------------------------------------------------

at the begin of the boot it found some more problems:
--------------------------------------------------------------------
[ 0.000000] ACPI Warning (tbutils-0310): 64-bit Physical Address in
XSDT is too large (1BEF31801BEF0000), truncating [20070126]
[ 0.000000] ACPI Warning (tbutils-0310): 64-bit Physical Address in
XSDT is too large (000000B000090001), truncating [20070126]

[ 0.000000] ACPI Error (tbutils-0219): Null physical address for ACPI
table [<NULL>] [20070126]
[ 0.000000] ACPI Error (tbutils-0219): Null physical address for ACPI
table [<NULL>] [20070126]

It's look at first like ACPI problem, and should be fixed upstream. It's
mean www.kernel.org

Here is some old instructions how to compile a kernel
http://doc.gwos.org/index.php/Kernel_Compilation_Dapper

I don't thing i can help you more :(

Fishor. Thank you for all your help. I assume this means I abandon Ubuntu and go back to Windows until sometime in the future when Ubuntu supports my USB.
Paul

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.