Hi!
I recently updated my proxmox 1.9 cluster. But after the update my fritzcard usb is not usable anymore.
i am not able to passthrough the usb device to the vm.
Then i tried to put the vm on a proxmox 2 testmachine and i passed through the usb device. but now when i start my hylafax vm,
the firmware could not be loaded, the bootlog says:
Nov 6 16:06:05 FAX2010 kernel: [ 28.859911] fcusb2: AVM FRITZ!Card USB v2 driver, revision 0.6.4
Nov 6 16:06:05 FAX2010 kernel: [ 28.859915] fcusb2: (fcusb2 built on Oct 14 2011 at 09:33:57)
Nov 6 16:06:05 FAX2010 kernel: [ 28.859916] fcusb2: -- 32 bit CAPI driver --
Nov 6 16:06:05 FAX2010 kernel: [ 28.859917] fcusb2: Loading...
Nov 6 16:06:05 FAX2010 kernel: [ 28.859951] fcusb2: Driver 'fcusb2' attached to fcusb2-stack. (152)
Nov 6 16:06:05 FAX2010 kernel: [ 28.859988] kcapi: Controller [001]: fcusb2-0003 attached
Nov 6 16:06:05 FAX2010 kernel: [ 28.860000] usbcore: registered new interface driver fcusb2
Nov 6 16:06:05 FAX2010 kernel: [ 28.860003] fcusb2: Loaded.
Nov 6 16:06:06 FAX2010 kernel: [ 170.395565] fcusb2: USB I/O error, code -110!
Nov 6 16:06:06 FAX2010 kernel: [ 170.396493] fcusb2: Firmware does not respond!
Nov 6 16:06:06 FAX2010 kernel: [ 170.397108] kcapi: card [001] down.
Nov 6 16:06:06 FAX2010 kernel: [ 170.397269] capidrv: controller 1 down
Nov 6 16:06:06 FAX2010 kernel: [ 170.397271] capidrv: delcontr: no contr 1
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM /dev/faxCAPI appears to be wedged
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM WEDGED: bin/wedged "faxCAPI" "/dev/faxCAPI"
Nov 6 16:06:16 FAX2010 CapiFaxRecv: Try to listen for call on Controller 1, but got error code 0x1009.
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM /dev/faxCAPI appears to be wedged
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM WEDGED: bin/wedged "faxCAPI" "/dev/faxCAPI"
capiinit says:
ERROR: controller 1: firmware load failed - Device or resource busy (16)
!! CHECK THE KERNEL MESSAGES BEFORE SENDING MAIL !!
ERROR: failed to load firmware for controller 1 driver fcusb2 name fcusb2-0003
Whats wrong? is there a problem with the usb-passthrough?
I recently updated my proxmox 1.9 cluster. But after the update my fritzcard usb is not usable anymore.
i am not able to passthrough the usb device to the vm.
Then i tried to put the vm on a proxmox 2 testmachine and i passed through the usb device. but now when i start my hylafax vm,
the firmware could not be loaded, the bootlog says:
Nov 6 16:06:05 FAX2010 kernel: [ 28.859911] fcusb2: AVM FRITZ!Card USB v2 driver, revision 0.6.4
Nov 6 16:06:05 FAX2010 kernel: [ 28.859915] fcusb2: (fcusb2 built on Oct 14 2011 at 09:33:57)
Nov 6 16:06:05 FAX2010 kernel: [ 28.859916] fcusb2: -- 32 bit CAPI driver --
Nov 6 16:06:05 FAX2010 kernel: [ 28.859917] fcusb2: Loading...
Nov 6 16:06:05 FAX2010 kernel: [ 28.859951] fcusb2: Driver 'fcusb2' attached to fcusb2-stack. (152)
Nov 6 16:06:05 FAX2010 kernel: [ 28.859988] kcapi: Controller [001]: fcusb2-0003 attached
Nov 6 16:06:05 FAX2010 kernel: [ 28.860000] usbcore: registered new interface driver fcusb2
Nov 6 16:06:05 FAX2010 kernel: [ 28.860003] fcusb2: Loaded.
Nov 6 16:06:06 FAX2010 kernel: [ 170.395565] fcusb2: USB I/O error, code -110!
Nov 6 16:06:06 FAX2010 kernel: [ 170.396493] fcusb2: Firmware does not respond!
Nov 6 16:06:06 FAX2010 kernel: [ 170.397108] kcapi: card [001] down.
Nov 6 16:06:06 FAX2010 kernel: [ 170.397269] capidrv: controller 1 down
Nov 6 16:06:06 FAX2010 kernel: [ 170.397271] capidrv: delcontr: no contr 1
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM /dev/faxCAPI appears to be wedged
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM WEDGED: bin/wedged "faxCAPI" "/dev/faxCAPI"
Nov 6 16:06:16 FAX2010 CapiFaxRecv: Try to listen for call on Controller 1, but got error code 0x1009.
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM /dev/faxCAPI appears to be wedged
Nov 6 16:06:16 FAX2010 FaxQueuer[5293]: MODEM WEDGED: bin/wedged "faxCAPI" "/dev/faxCAPI"
capiinit says:
ERROR: controller 1: firmware load failed - Device or resource busy (16)
!! CHECK THE KERNEL MESSAGES BEFORE SENDING MAIL !!
ERROR: failed to load firmware for controller 1 driver fcusb2 name fcusb2-0003
Whats wrong? is there a problem with the usb-passthrough?