Custom Query (16363 matches)
Results (1051 - 1053 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18530 | invalid | xorg couldn't open module vboxvideo | ||
| Description |
There seems to be a problem with the linux vboxvideo module in the latest guest additions. This is what's in the xorg log file: [ 229.545] (==) Matched vboxvideo as autoconfigured driver 0 [ 229.545] (==) Matched vboxvideo as autoconfigured driver 1 [ 229.545] (II) LoadModule: "vboxvideo" [ 229.546] (WW) Warning, couldn't open module vboxvideo [ 229.546] (II) UnloadModule: "vboxvideo" [ 229.546] (II) Unloading vboxvideo [ 229.546] (EE) Failed to load module "vboxvideo" (module does not exist, 0) [ 229.547] (==) Matched vboxvideo as autoconfigured driver 0 [ 229.547] (==) Matched vboxvideo as autoconfigured driver 1 [ 229.547] (II) LoadModule: "vboxvideo" [ 229.547] (WW) Warning, couldn't open module vboxvideo [ 229.547] (II) UnloadModule: "vboxvideo" [ 229.547] (II) Unloading vboxvideo [ 229.547] (EE) Failed to load module "vboxvideo" (module does not exist, 0) But the module was successfully loaded, here's what lsmod says: vboxvideo 36864 2 ttm 106496 1 vboxvideo drm_kms_helper 172032 1 vboxvideo drm 401408 5 drm_kms_helper,vboxvideo,ttm And this is the output of dmesg: [ 4.811273] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device [ 4.824322] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0 It's Ubuntu 18.04.2 with kernel 4.15.0-46. All packages are up-to-date. I already updated VBoxGuestAdditions from 6.0.4 to 6.0.5-129665, but the problem remains the same. |
|||
| #18524 | duplicate | Error building the module for 4.4.0-143-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | ||
| #18523 | invalid | "VBoxManage controlvm VM setlinkstate1 on/off" - not working properly like GUI mode | ||
| Description |
My VM is started with a default NAT Networking with an IP like 10.2.XX.XX. Inside the Vagrant File I call the command "VBOXManage controlvm VM nic1 bridged eth0" to change my network type to bridge. After this I call in sequence the commands: "VBoxManage controlvm VM setlinkstate1 off" and "VBoxManage controlvm VM setlinkstate1 on" to change my network type. I saw in GUI that these commands properly uncheck the "Cable Connected" checkbox and check after but do not change the IP properly (refresh). When I do these same steps through GUI(open menu Devices > Network > Network Settings > Advanced, unckeck Cable Connected and click OK / open menu Devices > Network > Network Settings > Advanced, check Cable Connected and click OK) the VistualBox refreshs IP as expected. |
|||

