Hi,
While installing vbox5-nova-scupt there is a need to configure ROM(usb_device). The option list is truncated in the middle of "dynamic_depot_rom" (in the middle of the line),
and there is no way to see if there are other options below.
I guess the best thing is to change the window size however changing the fb_drv hight in the config didn't do the trick.
Best regard.
S.P.
Hello,
On 23.04.20 09:40, Shlomo Pongratz wrote:
While installing vbox5-nova-scupt there is a need to configure ROM(usb_device). The option list is truncated in the middle of "dynamic_depot_rom" (in the middle of the line),
and there is no way to see if there are other options below.
this looks very much like the issue [1] posted very recently.
[1] https://lists.genode.org/pipermail/users/2020-April/007092.html
I guess the best thing is to change the window size however changing the fb_drv hight in the config didn't do the trick.
When running Sculpt in Qemu, it uses the VESA driver with a fixed resolution of 1024x768. This option is solely provided as an easy way to test-drive the system. Admittedly, I have not anticipated that anyone might want to *use* Sculpt in Qemu and not on real hardware, let alone running VirtualBox via nested virtualization.
Going forward, I think it would make sense to improve Sculpt in two ways. First, enabling the switching of resolutions when using the VESA driver. And second, by reducing the number of practically useless options when routing ROM modules. No promise, but I'll keep both ideas in the back of my head for the release 20.08.
Until then, I think you will get most fun out of Sculpt when using it on real hardware [2].
[2] https://genode.org/documentation/articles/sculpt-20-02#Hardware_requirements...
Cheers Norman
On 4/23/20 12:57 PM, Norman Feske wrote:
Until then, I think you will get most fun out of Sculpt when using it on real hardware [2].
[2] https://genode.org/documentation/articles/sculpt-20-02#Hardware_requirements...
Cheers Norman
hank you,
Please note that because of the CoVID-19 when working from home one doesn't want to crash the remote system he/she works with.
So until then I and I guess many others will be forced to use nested virtualization.
Best regards,
S.P.
If you want to try it, I have had success using fb_boot_drv instead of fb_drv in qemu. This was as a prelude to actually getting it to work on my hardware. In this case your resolution will be set based on whatever GRUB decides to set as the resolution, as I understand it. This can be quite large if the correct options are passed to qemu and you use the right firmware (I use the TianoCore firmware). IIRC I had to edit the driver manager or some such in order to prevent it choosing fb_drv (i.e. the VESA one). But that was in an older Sculpt. The newest one seems to have a preference of Intel -> GRUB -> VESA, so it might be using the GRUB one already? (As an aside, it doesn't actually check if the Intel driver fails, so if you, like me, have an Intel graphics adapter that it doesn't like, it won't fall back to the GRUB one, it'll just leave the screen blank).
Good luck, Colin
Hello,
On 2020-04-23 12:21, Colin Parker wrote:
If you want to try it, I have had success using fb_boot_drv instead of fb_drv in qemu. This was as a prelude to actually getting it to work on my hardware. In this case your resolution will be set based on whatever GRUB decides to set as the resolution, as I understand it. This can be quite large if the correct options are passed to qemu and you use the right firmware (I use the TianoCore firmware). IIRC I had to edit the driver manager or some such in order to prevent it choosing fb_drv (i.e. the VESA one). But that was in an older Sculpt. The newest one seems to have a preference of Intel -> GRUB -> VESA, so it might be using the GRUB one already? (As an aside, it doesn't actually check if the Intel driver fails, so if you, like me, have an Intel graphics adapter that it doesn't like, it won't fall back to the GRUB one, it'll just leave the screen blank).
If you boot in UEFI mode (no bios legacy support) by using qemu --bios option Sculpt will use automatically the fb_boot_drv component, which will take the resolution as Grub setup.
If you boot the old BIOS legacy way, Sculpt will use the fb_drv with a fixed pre-defined resolution.
Thanks Colin for the hint,
Alex.
-
Alexander Boettcher -
Colin Parker -
Norman Feske -
Shlomo Pongratz