Missing 1280x800 VESA Resolution with NVIDIA GPU

359 views
Skip to first unread message

scalise

unread,
May 5, 2020, 8:21:17 AM5/5/20
to Android-x86
As title says, trying to get a x86 box working with 1280x800 resolution (bit depth doesn't really matter) but it's not in my vga=ask parameter list. I know the GRUB VESA list is dependent on hardware, but is there any way to get this resolution? I'm currently running stable at 800x600 with "nomodeset xforcevesa" in my menu.lst file. Let me know what additional information may be helpful.


scalise

unread,
May 26, 2020, 9:25:24 PM5/26/20
to Android-x86
Anything?

Prajna Sariputra

unread,
May 26, 2020, 9:48:08 PM5/26/20
to andro...@googlegroups.com
As far as I know there's no way to add resolutions if you're stuck in VESA mode, since then you are relying on the most basic common interface with the GPU, so you're stuck with what the GPU has to offer in that mode, unless you start modifying the GPU's firmware, which would be extremely risky, and that's if it's possible at all.

On Tue, May 5, 2020, 10:21 PM scalise <scali...@gmail.com> wrote:
As title says, trying to get a x86 box working with 1280x800 resolution (bit depth doesn't really matter) but it's not in my vga=ask parameter list. I know the GRUB VESA list is dependent on hardware, but is there any way to get this resolution? I'm currently running stable at 800x600 with "nomodeset xforcevesa" in my menu.lst file. Let me know what additional information may be helpful.


--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/d3e3c49a-ea8f-4845-a570-66a105226150%40googlegroups.com.

scalise

unread,
May 26, 2020, 10:08:47 PM5/26/20
to Android-x86
I appreciate the reply. Can I not use VESA mode and not have to rely on what VESA resolutions my GPU has? I know 1280x800 is rather obscure, but how are people getting 1920x1080 or similar HD resolutions?


On Tuesday, May 26, 2020 at 9:48:08 PM UTC-4, Prajna Sariputra wrote:
As far as I know there's no way to add resolutions if you're stuck in VESA mode, since then you are relying on the most basic common interface with the GPU, so you're stuck with what the GPU has to offer in that mode, unless you start modifying the GPU's firmware, which would be extremely risky, and that's if it's possible at all.
On Tue, May 5, 2020, 10:21 PM scalise <scali...@gmail.com> wrote:
As title says, trying to get a x86 box working with 1280x800 resolution (bit depth doesn't really matter) but it's not in my vga=ask parameter list. I know the GRUB VESA list is dependent on hardware, but is there any way to get this resolution? I'm currently running stable at 800x600 with "nomodeset xforcevesa" in my menu.lst file. Let me know what additional information may be helpful.


--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

Prajna Sariputra

unread,
May 26, 2020, 10:21:45 PM5/26/20
to andro...@googlegroups.com
In order to avoid using VESA mode you'd need to use proper graphics drivers, however NVIDIA graphics is especially notorious for having horrible support on Linux without their official blessing. Normal Linux distributions (Ubuntu, Fedora, etc) can have the official NVIDIA drivers installed, but those do not work on Android-x86, since the whole Android design is vastly different from those distributions, and so we are stuck with the one built in (nouveau), which tends to be troublesome due to lack of any documentation or any real help from NVIDIA (so the devs have to practically guess how the graphics chip works), unlike Intel and ATI/AMD graphics.

As for how other people are apparently able to get native resolutions, they either got the proper graphics drivers working or they were lucky enough that the resolution they want actually happens to be embedded by the manufacturer in the graphics firmware.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/9c6d5fed-a027-4c5f-8399-301bc5e110a4%40googlegroups.com. Ok

scalise

unread,
May 26, 2020, 10:32:42 PM5/26/20
to Android-x86
Got it. I'll have to try on my laptop with the embedded Intel graphics and see if I fare any better. I appreciate you taking the time to explain.

Chih-Wei Huang

unread,
May 26, 2020, 10:55:45 PM5/26/20
to Android-x86
scalise <scali...@gmail.com> 於 2020年5月27日 週三 上午10:32寫道:
>
> Got it. I'll have to try on my laptop with the embedded Intel graphics and see if I fare any better. I appreciate you taking the time to explain.

You may add "video=1280x800 HWACCEL=0" to kernel cmdline
to see if it works.
The prior one sets the resolution of the native driver (should be nouveau)
to the desired resolution, and the latter one disables hardware acceleration
that should make your system usable (but may be slow).
You may also try HWACCEL=1 but it may be very unstable.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

scalise

unread,
May 27, 2020, 9:21:59 AM5/27/20
to Android-x86
I removed "nomodeset xforcevesa" from the cmdline and added your suggestion, it renders the VM to the correct resolution and boots but unfortunately I'm multi-boxing in a noisy portrait mode. "HWACCEL=1" wouldn't start, left me hanging on the underscore.

Prajna Sariputra

unread,
May 27, 2020, 9:54:49 AM5/27/20
to andro...@googlegroups.com
Oh, if it's a virtual machine it's a whole other thing (they are not exposed to the actual graphics hardware at all), VirtualBox actually does allow you to add custom VESA modes, run this command: VBoxManage.exe setextradata "VM name" "CustomVideoMode1" "1280x800x32" (assuming the command prompt is open where VBoxManage.exe is, somewhere in the VirtualBox installation folder).

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/09c6f5a5-d8d0-485f-9164-3b2b2d023fc3%40googlegroups.com.

scalise

unread,
May 27, 2020, 10:08:21 AM5/27/20
to Android-x86
Apologies, should have been clearer than this was in a VM.

I ran that command and that video resolution is now populated into the "vga=ask" parameter (below). To make this persistent, I could change the kernel cmd in menu.lst to just "vga=360" now, correct?

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

Prajna Sariputra

unread,
May 27, 2020, 10:36:14 AM5/27/20
to andro...@googlegroups.com
Actually if I remember correctly it's actually 864 (360 is hexadecimal, 864 is the decimal value), or 0x360 might work too.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/3d5b890a-5e72-4720-91ec-d4a3991f24cc%40googlegroups.com.

scalise

unread,
May 27, 2020, 10:36:26 AM5/27/20
to Android-x86
So "vga=864" (forgot it takes decimal) unfortunately isn't working, just getting the underscore. Only way I can get it through are with the "xforcevesa nomodeset vga=864" parameters and even then it's not taking the custom resolution (nomodeset bypasses kernel settings?). My VM graphics controller is VMSVGA with 3D acceleration, is there another I can try?

Prajna Sariputra

unread,
May 27, 2020, 10:42:38 AM5/27/20
to andro...@googlegroups.com
You could try VBoxSVGA I suppose, could be that it's mistakenly assuming that it's running on VMWare (VMSVGA just emulates the VMWare graphics adapter). You could also try the k49 variant as well, since it's recommended for VMWare anyway, so the same might apply here.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/6a2d5c27-8eeb-485e-b7e0-f25e4ec89f04%40googlegroups.com.

Anthony Scalise

unread,
May 27, 2020, 10:51:16 AM5/27/20
to andro...@googlegroups.com
VBoxSVGA appears to have worked. Will update it anything goes awry. Thanks again for your help.

You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/91BZBEFNOcA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CADBSSgkdphM7N%2BJzYuhptFDFb8KEeRcCSfzeku97sYQGLcO7Aw%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages