- Virtualbox retina display ubuntu how to#
- Virtualbox retina display ubuntu Patch#
- Virtualbox retina display ubuntu full#
I've determined the root cause but haven't found a way to solve it. Then everything goes away, though the machine is still functional.The issue you're experiencing is one that I've been working to solve the last two or three days. You get beautiful output right up to the point where udev/coldplug starts and modprobes the world.
Virtualbox retina display ubuntu how to#
It recognizes an NVIDIA card, kicks the efifb driver out, and only then determines that it doesn't know how to control a 650M and aborts. It turns out that if you inadvertently enable the noveau framebuffer driver, it will kill your existing efi framebuffer. Incidentally, I did hit one other graphics-related issue during yesterday's install: my framebuffer would get corrupted and die halfway through the init process. Then everything goes away, though the machine is still functional.
I may give it a shot later, but it's not high on my list at the moment. I want the high-speed IOs to work (for the occasional system update), but my Linux partition is going to spend 90%+ of its life slaved to a VirtualBox instance inside OSX. I haven't attempted to get the NVIDIA card up, since it's not really something I care about. I see all sorts of alignment and hotplug errors during the rescan, indicating that it can't re-map the BAR and IO address spaces. I can remove the device (either gracefully via "echo 1 > remove", or -yank-), but it doesn't come back after a rescan. I started with the sysrescuecd's config which includes almost everything.
Virtualbox retina display ubuntu full#
,ĭo you have full PCIe hotplug enabled? I don't have any Thunderbolt peripherals to try out so I haven't gotten that far.ĭo you have the nVidia card working? If so, how is it set up? What's your kernel version, nvidia-drivers version, nf, etc? Mine's not worked yet, not with nouveau or nvidia.BlueDragonX,
Virtualbox retina display ubuntu Patch#
Here's the one-liner patch to tg3.c, based on vanilla 3.4.4 sources: I suspect that there's additional hotplug support that's needed to make all this work seamlessly. If I attach the dongle after booting, the device doesn't show up.
I didn't do much with it beyond getting an address via dhcp and doing some pings, but those all worked fine. This may just be the first time it's appeared in the wild with the normal broadcom vendor id. Glancing through the driver code, it looks like other vendors have shipped this chip using their own PCI vendor ids, and that it's well supported by the driver.
If you tweak the tigon 3 driver to recognize that vendor/device id combination, then the interface will come up. If I boot with the dongle attached, it shows up in lspci as a Broadcom Tigon3 57762. I can confirm that the thunderbolt ethernet dongle works (with a few caveats). I realize it's not SUSE, but you guys have one of the few active threads related to these machines.
0 kommentar(er)
