usb ACPI APIC?
I'm started to have a prob with usb camera:
with 2.6.6 kern no problems. with 2.6.7, on turning on: usb 2-3: control timeout on ep0out ohci_hcd 0000:00:03.0: Unlink after no-IRQ? Different ACPI or APIC settings may help. apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) apm: overridden by ACPI. and on mounting it says "/dev/sda1 is not a valid block device" since i configured the cam with the 2.6.0 kern i have made no change, but changing the mount point from /mnt/cam to /cam. Q: ACPI APIC, what are those, where to see the configuration (proc sys)? when i change some value on the /proc files, where they're stored? i guess it must be some file loaded at boot, like initrd (i currently have no one ), or /boot/map or system.map... p.s. every kern is compiled with the same .config thanx for any help |
i installed usbuitls.
i ran lsusb -v on both kernels without camera, the diff: 14c14 < iManufacturer 3 Linux 2.6.6 ohci_hcd --- > iManufacturer 3 Linux 2.6.7 ohci_hcd 25c25 < bmAttributes 0x40 --- > bmAttributes 0xe0 26a27 > Remote Wakeup 61c62 < iManufacturer 3 Linux 2.6.6 ohci_hcd --- > iManufacturer 3 Linux 2.6.7 ohci_hcd 72c73 < bmAttributes 0x40 --- > bmAttributes 0xe0 73a75 > Remote Wakeup and with camera on: 2,68d1 < Bus 002 Device 002: ID 054c:0010 Sony Corp. DSC-S30/S70/S75/F505V/F505/FD92 Cybershot/Mavica Digital Camera < Device Descriptor: < bLength 18 < bDescriptorType 1 < bcdUSB 1.10 < bDeviceClass 0 (Defined at Interface level) < bDeviceSubClass 0 < bDeviceProtocol 0 < bMaxPacketSize0 8 < idVendor 0x054c Sony Corp. < idProduct 0x0010 DSC-S30/S70/S75/F505V/F505/FD92 Cybershot/Mavica Digital Camera < bcdDevice 4.50 < iManufacturer 1 Sony < iProduct 2 Sony DSC < iSerial 0 < bNumConfigurations 1 < Configuration Descriptor: < bLength 9 < bDescriptorType 2 < wTotalLength 39 < bNumInterfaces 1 < bConfigurationValue 1 < iConfiguration 0 < bmAttributes 0xc0 < Self Powered < MaxPower 2mA < Interface Descriptor: < bLength 9 < bDescriptorType 4 < bInterfaceNumber 0 < bAlternateSetting 0 < bNumEndpoints 3 < bInterfaceClass 8 Mass Storage < bInterfaceSubClass 255 < bInterfaceProtocol 1 < iInterface 0 < Endpoint Descriptor: < bLength 7 < bDescriptorType 5 < bEndpointAddress 0x01 EP 1 OUT < bmAttributes 2 < Transfer Type Bulk < Synch Type None < Usage Type Data < wMaxPacketSize 0x0040 bytes 64 once < bInterval 0 < Endpoint Descriptor: < bLength 7 < bDescriptorType 5 < bEndpointAddress 0x82 EP 2 IN < bmAttributes 2 < Transfer Type Bulk < Synch Type None < Usage Type Data < wMaxPacketSize 0x0040 bytes 64 once < bInterval 0 < Endpoint Descriptor: < bLength 7 < bDescriptorType 5 < bEndpointAddress 0x83 EP 3 IN < bmAttributes 3 < Transfer Type Interrupt < Synch Type None < Usage Type Data < wMaxPacketSize 0x0008 bytes 8 once < bInterval 255 < 81c14 < iManufacturer 3 Linux 2.6.6 ohci_hcd --- > iManufacturer 3 Linux 2.6.7 ohci_hcd 92c25 < bmAttributes 0x40 --- > bmAttributes 0xe0 93a27 > Remote Wakeup 128c62 < iManufacturer 3 Linux 2.6.6 ohci_hcd --- > iManufacturer 3 Linux 2.6.7 ohci_hcd 139c73 < bmAttributes 0x40 --- > bmAttributes 0xe0 140a75 > Remote Wakeup think it doesn't recognize the cam. i found /sys/bus/usb/devices/usb[1-2]/bmAttributes that open with gvim say on titlebar "bmAttributes =(sys/devices/pci0000:00/0000:00:00.[2-3]/usb[1-2]. ???????????? |
Re: usb ACPI APIC?
Quote:
This happened with 2.6.5 and 2.6.7 kernels. I get mouse working starting in init level 3 and then writing insmod /lib/modules/2.6.7_a/kernel/drivers/usb/input/usbhid.ko insmod /lib/modules/2.6.7_a/kernel/drivers/usb/host/ohci-hcd.ko 2.6.7_a is my customized kernel but something similar should be in your /lib/modules path. If I change order of those 2 insmod commands I get timeout error but mouse still works. So I gues that you have to insmod some usbhid.ko or similar module first and then ohci.hcd.ko module. |
Acpi is for power management.
Apic has something to do with the bios and irq's. I have no problems with Slack but I used to run Mandrake 9.1 and had to pass "noapic" at boot in order to get my Realtek 8139 ethernet card to work. I've heard that using "noapic" will solve alot of odd problems but I don't know that to be fact. If you want to try it, append the begining of /etc/lilo.conf as follows: # LILO configuration file # generated by 'liloconfig' # # Start LILO global section append="noapic" boot = /dev/hda message = /boot/boot_message.txt prompt timeout = 1200 # Override dangerous defaults that rewrite the partition table: change-rules Then su a term and type /sbin/lilo Then reboot. Again this is just something I heard, take it with a grain of salt. |
All times are GMT -5. The time now is 10:11 PM. |