Results 1 to 4 of 4
I am trying to use a NEC USB host controller NEC D720102GC with a BCM4704 device in a 2.6 kernel and if I insmod the ohci-hcd.ko driver, it reboots without ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 04-01-2009 #1Just Joined!
- Join Date
- Apr 2009
- Posts
- 5
Help with OHCI-HCD rebooting
I am trying to use a NEC USB host controller NEC D720102GC with a BCM4704 device in a 2.6 kernel and if I insmod the ohci-hcd.ko driver, it reboots without any kernel panic or messages.
I pin pointed to where it dies, but I get no messages even though I enabled USB debug in kernel. It simply reboots. Lost how to proceed from here. Appreciate any pointers or help.
Regards
Insmod ohci-hcd.ko or building this ko into the kernel, the system will reboot
***** insmod ehci-hcd.ko* --- works well
***** insmod uhci-hcd.ko* --- works well
Please refer the followings,
/linux/linux/drivers/usb/host/ohci-hcd.c
static int ohci_init (struct ohci_hcd *ohci) {
***** int ret;
***** struct usb_hcd *hcd = ohci_to_hcd(ohci);
***** disable (ohci);
***** ohci-regs = hcd-regs;
***** /* REVISIT this BIOS handshake is now moved into PCI "quirks", and
****** * was never needed for most non-PCI systems ... remove the code?
****** */
#ifndef IR_DISABLE
***** /* SMM owns the HC?* not for long! */
***** if (!no_handshake && ohci_readl (ohci,
***** ******* ******* ******* ******* &ohci-regs-control) & OHCI_CTRL_IR) {
***** ******* u32 temp;
***** ******* ohci_dbg (ohci, "USB HC TakeOver from BIOS/SMM\n");
***** ******* /* this timeout is arbitrary.* we make it long, so systems
***** ******** * depending on usb keyboards may be usable even if the
***** ******** * BIOS/SMM code seems pretty broken.
***** ******** */
***** ******* temp = 500;**** /* arbitrary: five seconds */
***** ******* ohci_writel (ohci, OHCI_INTR_OC, &ohci-regs-intrenable);
***** ******* ohci_writel (ohci, OHCI_OCR, &ohci-regs-cmdstatus);
***** ******* while (ohci_readl (ohci, &ohci-regs-control) & OHCI_CTRL_IR) {
***** ******* ******* msleep (10);
***** ******* ******* if (--temp == 0) {
***** ******* ******* ******* ohci_err (ohci, "USB HC takeover failed!"
***** ******* ******* ******* ******* "* (BIOS/SMM bug)\n");
***** ******* ******* ******* return -EBUSY;
***** ******* ******* }
***** ******* }
***** ******* ohci_usb_reset (ohci);
***** }
#endif
***** /* Disable HC interrupts */
***** ohci_writel (ohci, OHCI_INTR_MIE, &ohci-regs-intrdisable); <<==================Dies
- 04-01-2009 #2
Hello and Welcome.
Have you tried using modprobe instead of insmod?
modprobe ehci-hcd
modprobe uhci-hcdI do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this.** Forum FAQS. ** Adopt an unanswered post.
I'd rather be lost at the lake than found at home.
- 04-01-2009 #3Just Joined!
- Join Date
- Apr 2009
- Posts
- 5
Hello
I am little new with Linux. No, I have not tried that.
Like "modprobe -l -v <module_name>" ?
How is it different from insmod? If this works, what does that say? Also, this reboot seems to be specific to the NEC controller.
- 04-01-2009 #4
As far as I know, insmod only inserts that one module whereas modprobe will also load modules that depend on the module being loaded and vice versa, I really don't know a whole lot about it. But google is your best friend if you need to know more.
modprobe vs insmod - Google SearchI do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this.** Forum FAQS. ** Adopt an unanswered post.
I'd rather be lost at the lake than found at home.


Reply With Quote
