[arch-general] Virtualbox USB issues after upgrade
Hi, I'm running XP SP2 on Vbox, to handle an iPad2 by iTunes via USB cable. I already had issues in the past, but after an Arch update today sync, recovery, any similar operation doesn't work anymore, regarding to USB issues. I didn't update Arch and sync an iPad by Vbox/iTunes for a long time. Apple about iTunes and issues: "OS virtualization or emulation software may cause restore errors." "Error 1604 This error is often related to USB timing." [spinymouse@archlinux ~]$ uname -a Linux archlinux 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64 GNU/Linux [spinymouse@archlinux ~]$ pacman -Qi virtualbox Name : virtualbox Version : 4.1.16-1 In the past I sometimes had to reconnect the iPad to Vbox, by Vbox's "Devices > USB devices". Now there always is a connection, but I get USB timing errors. Any ideas how to get back a working Vbox? Ciao, Ralf
On Tue, Jun 12, 2012 at 10:50 PM, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
Hi,
I'm running XP SP2 on Vbox, to handle an iPad2 by iTunes via USB cable.
I already had issues in the past, but after an Arch update today sync, recovery, any similar operation doesn't work anymore, regarding to USB issues. I didn't update Arch and sync an iPad by Vbox/iTunes for a long time.
Apple about iTunes and issues: "OS virtualization or emulation software may cause restore errors." "Error 1604 This error is often related to USB timing."
[spinymouse@archlinux ~]$ uname -a Linux archlinux 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64 GNU/Linux [spinymouse@archlinux ~]$ pacman -Qi virtualbox Name : virtualbox Version : 4.1.16-1
In the past I sometimes had to reconnect the iPad to Vbox, by Vbox's "Devices > USB devices". Now there always is a connection, but I get USB timing errors.
You can try to rmmod ipheth before plug your iphone/ipad to vbox. And also try to add vbox-ext-oracle (aur) to have better usb support. Cordialement, -- Sébastien "Seblu" Luttringer www.seblu.net
On Wed, 2012-06-13 at 10:07 +0200, Sébastien Luttringer wrote:
You can try to rmmod ipheth before plug your iphone/ipad to vbox.
And also try to add vbox-ext-oracle (aur) to have better usb support.
Thank you. I'll report what happened ASAP, perhaps today. - Ralf
On Wed, 2012-06-13 at 10:49 +0200, Ralf Mardorf wrote:
On Wed, 2012-06-13 at 10:07 +0200, Sébastien Luttringer wrote:
You can try to rmmod ipheth before plug your iphone/ipad to vbox.
And also try to add vbox-ext-oracle (aur) to have better usb support.
Thank you. I'll report what happened ASAP, perhaps today. - Ralf
Thank you Sébastien :) I've got more good news, than bad news. The good news are for VBox on 3.3.8-1 x86_64. First I installed vbox-ext-oracle (aur). Is there the need to edit some settings? I didn't edit anything. The second step was to boot the the kernel-rt, but now I'll continue with the third step, back to the regular kernel. $ sudo rmmod ipheth Error: Module ipheth is not currently loaded But that doesn't matter, I could restore the iPad, I just needed to reconnect the USB to times by the Device > USB Device menu of VBox at the beginning of the restore. I didn't check if sync will work too. There's a another good news. Since month X couldn't start, when I booted the kernel-rt. Today I upgraded from 3.2.19_rt30-2 to 3.4.2_rt10-1 and I'm able to start a Xfce session again. The bad news are for the kernel-rt and VBox. # /usr/bin/vboxbuild [snip] error: `/lib/modules/3.4.2-rt10-1-rt/build' does not appear to be a valid kernel build directory. # ln -s /usr/src/linux-3.4.2-rt10-1-rt /lib/modules/3.4.2-rt10-1-rt/build # /usr/bin/vboxbuild :: Removing all old VirtualBox kernel modules [DONE] :: Removing all old VirtualBox kernel modules [FAIL] :: Removing all old VirtualBox kernel modules [FAIL] :: Removing all old VirtualBox kernel modules [FAIL] :: Recompiling VirtualBox kernel modules (3.4.2-rt10-1-rt) [BUSY] Look at /var/log/vbox-install.log to find out what went wrong [FAIL] Look at /var/log/vbox-install.log to find out what went wrong [FAIL] Look at /var/log/vbox-install.log to find out what went wrong [FAIL] Look at /var/log/vbox-install.log to find out what went wrong [FAIL] gzip: /lib/modules/3.4.2-rt10-1-rt/extramodules/*.ko: No such file or directory [DONE] After a restart $ sudo pacman -S virtualbox-modules warning: virtualbox-modules-4.1.16-1 is up to date -- reinstalling [snip] Proceed with installation? [Y/n] Y [snip] but this didn't change the situation. Regards, Ralf
PS: Pardon, I missed $ cat /var/log/vbox-install.log Makefile:190: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. cp: cannot stat '/tmp/vboxdrv-Module.symvers': No such file or directory Makefile:112: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. cp: cannot stat '/tmp/vboxdrv-Module.symvers': No such file or directory Makefile:108: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. cp: cannot stat '/tmp/vboxdrv-Module.symvers': No such file or directory Makefile:112: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop. Google found hits regarding to "arch unable to find the include directory for your current Linux kernel", but those seem to be not related to Arch Linux. I'll read it ASAP.
participants (2)
-
Ralf Mardorf
-
Sébastien Luttringer