Can't get 1440x900 resolution with GRUB2 although vbeinfo says it's availableProblem setting command-line...

How to pronounce 'C++' in Spanish

What language was spoken in East Asia before Proto-Turkic?

Is it possible to determine the symmetric encryption method used by output size?

Mac Pro install disk keeps ejecting itself

How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?

Why does nature favour the Laplacian?

Size of electromagnet needed to replicate Earth's magnetic field

Critique of timeline aesthetic

What is the difference between `command a[bc]d` and `command `a{b,c}d`

How come there are so many candidates for the 2020 Democratic party presidential nomination?

Is there any limitation with Arduino Nano serial communication distance?

What was the first Intel x86 processor with "Base + Index * Scale + Displacement" addressing mode?

Binary Numbers Magic Trick

How do I reattach a shelf to the wall when it ripped out of the wall?

How can the Zone of Truth spell be defeated without the caster knowing?

What is the most expensive material in the world that could be used to create Pun-Pun's lute?

What does the "ep" capability mean?

Why does academia still use scientific journals and not peer-reviewed government funded alternatives?

Are Boeing 737-800’s grounded?

Repelling Blast: Must targets always be pushed back?

US visa is under administrative processing, I need the passport back ASAP

What is the strongest case that can be made in favour of the UK regaining some control over fishing policy after Brexit?

How would one muzzle a full grown polar bear in the 13th century?

Was there a Viking Exchange as well as a Columbian one?



Can't get 1440x900 resolution with GRUB2 although vbeinfo says it's available


Problem setting command-line console resolution. vbeinfo in grub2 does not report all resolutionsI can't edit /etc/init.d/rc.sysinit as local - vi says it's [readonly]can't get hardware accelerated graphics with linux mint 13ssh login with key can't connect although go an ssh keyapt-get fails with raspberry pi although ping worksCan't set locale to en_US.UTF-8, but locale -a says it's available. No rootxrandr to set display to use single monitor, even if you have another monitor connected or disconnectedimgmount in dosbox says “can't create drive from file” to .img created with ddCan't change resolution with xrandrXubuntu Second Monitor No Image






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







2















I'm trying to use GRUB2 in graphical mode with 1440x900 resolution, but the result is always garbled nonsense: the highest resolution I can get is 1280x800.



Word is from googling that long as vbeinfo lists a resolution, GRUB2 can use it. This doesn't seem to be true: vbeinfo says that 1440x900 is available but it doesn't work.



Testing it from the GRUB2 command line:



set gxfmode=1440x900
terminal_output gfxterm
# -> garbled nonsense

# back to trusty 640x480
terminal_output console


The graphics card is an Intel GM965.



Once linux boots the framebuffer switches to 1440x900.



Added after epheminent's reply and various experiments



vbeinfo lists two sets of modes.



The first set runs from 0x160 to 0x16b, with resolutions 768x480, 960x600, 1280x800 and 1440x900



Then - after a bunch of text-only modes - the second set, containing resolutions 1024x768, 800x600, and 640x480



The first set of modes aren't altered by 915resolution. They all work except 1440x900.



The resolution of modes in the second set can be altered using the 915resolution module / command available in GRUB2 >= 1.99.



# in /boot/grub/grub.cfg

insmod 915resolution

# 30, 32, 34 all work for me: all that varies is which modes are altered
915resolution 30 1440 900

# setting an impossible resolution changes the mode to "text-only"
# in my case 1280x1024 is not supported
915resolution 30 1280 1024


Clearly, 1440x900 should just work: adding it with 915resolution is just a workaround.










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






migrated from stackoverflow.com Feb 17 '11 at 1:40


This question came from our site for professional and enthusiast programmers.



















  • This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

    – fixer1234
    Apr 1 '17 at 3:18




















2















I'm trying to use GRUB2 in graphical mode with 1440x900 resolution, but the result is always garbled nonsense: the highest resolution I can get is 1280x800.



Word is from googling that long as vbeinfo lists a resolution, GRUB2 can use it. This doesn't seem to be true: vbeinfo says that 1440x900 is available but it doesn't work.



Testing it from the GRUB2 command line:



set gxfmode=1440x900
terminal_output gfxterm
# -> garbled nonsense

# back to trusty 640x480
terminal_output console


The graphics card is an Intel GM965.



Once linux boots the framebuffer switches to 1440x900.



Added after epheminent's reply and various experiments



vbeinfo lists two sets of modes.



The first set runs from 0x160 to 0x16b, with resolutions 768x480, 960x600, 1280x800 and 1440x900



Then - after a bunch of text-only modes - the second set, containing resolutions 1024x768, 800x600, and 640x480



The first set of modes aren't altered by 915resolution. They all work except 1440x900.



The resolution of modes in the second set can be altered using the 915resolution module / command available in GRUB2 >= 1.99.



# in /boot/grub/grub.cfg

insmod 915resolution

# 30, 32, 34 all work for me: all that varies is which modes are altered
915resolution 30 1440 900

# setting an impossible resolution changes the mode to "text-only"
# in my case 1280x1024 is not supported
915resolution 30 1280 1024


Clearly, 1440x900 should just work: adding it with 915resolution is just a workaround.










share|improve this question














bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






migrated from stackoverflow.com Feb 17 '11 at 1:40


This question came from our site for professional and enthusiast programmers.



















  • This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

    – fixer1234
    Apr 1 '17 at 3:18
















2












2








2








I'm trying to use GRUB2 in graphical mode with 1440x900 resolution, but the result is always garbled nonsense: the highest resolution I can get is 1280x800.



Word is from googling that long as vbeinfo lists a resolution, GRUB2 can use it. This doesn't seem to be true: vbeinfo says that 1440x900 is available but it doesn't work.



Testing it from the GRUB2 command line:



set gxfmode=1440x900
terminal_output gfxterm
# -> garbled nonsense

# back to trusty 640x480
terminal_output console


The graphics card is an Intel GM965.



Once linux boots the framebuffer switches to 1440x900.



Added after epheminent's reply and various experiments



vbeinfo lists two sets of modes.



The first set runs from 0x160 to 0x16b, with resolutions 768x480, 960x600, 1280x800 and 1440x900



Then - after a bunch of text-only modes - the second set, containing resolutions 1024x768, 800x600, and 640x480



The first set of modes aren't altered by 915resolution. They all work except 1440x900.



The resolution of modes in the second set can be altered using the 915resolution module / command available in GRUB2 >= 1.99.



# in /boot/grub/grub.cfg

insmod 915resolution

# 30, 32, 34 all work for me: all that varies is which modes are altered
915resolution 30 1440 900

# setting an impossible resolution changes the mode to "text-only"
# in my case 1280x1024 is not supported
915resolution 30 1280 1024


Clearly, 1440x900 should just work: adding it with 915resolution is just a workaround.










share|improve this question














I'm trying to use GRUB2 in graphical mode with 1440x900 resolution, but the result is always garbled nonsense: the highest resolution I can get is 1280x800.



Word is from googling that long as vbeinfo lists a resolution, GRUB2 can use it. This doesn't seem to be true: vbeinfo says that 1440x900 is available but it doesn't work.



Testing it from the GRUB2 command line:



set gxfmode=1440x900
terminal_output gfxterm
# -> garbled nonsense

# back to trusty 640x480
terminal_output console


The graphics card is an Intel GM965.



Once linux boots the framebuffer switches to 1440x900.



Added after epheminent's reply and various experiments



vbeinfo lists two sets of modes.



The first set runs from 0x160 to 0x16b, with resolutions 768x480, 960x600, 1280x800 and 1440x900



Then - after a bunch of text-only modes - the second set, containing resolutions 1024x768, 800x600, and 640x480



The first set of modes aren't altered by 915resolution. They all work except 1440x900.



The resolution of modes in the second set can be altered using the 915resolution module / command available in GRUB2 >= 1.99.



# in /boot/grub/grub.cfg

insmod 915resolution

# 30, 32, 34 all work for me: all that varies is which modes are altered
915resolution 30 1440 900

# setting an impossible resolution changes the mode to "text-only"
# in my case 1280x1024 is not supported
915resolution 30 1280 1024


Clearly, 1440x900 should just work: adding it with 915resolution is just a workaround.







linux grub arch-linux






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 12 '11 at 20:16









TomSWTomSW

20127




20127





bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community yesterday


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






migrated from stackoverflow.com Feb 17 '11 at 1:40


This question came from our site for professional and enthusiast programmers.









migrated from stackoverflow.com Feb 17 '11 at 1:40


This question came from our site for professional and enthusiast programmers.















  • This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

    – fixer1234
    Apr 1 '17 at 3:18





















  • This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

    – fixer1234
    Apr 1 '17 at 3:18



















This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

– fixer1234
Apr 1 '17 at 3:18







This is an old, interesting question that just got bumped to the main page again. In addition to ephemient's answer, there is a deleted one from Breakthrough about using gfxmode. Your comment on the answer says it worked, but the edit to the questions says it didn't. Can you update us on the status? Ever get this solved? If not, has it been overtaken by events or are you still looking for a solution?

– fixer1234
Apr 1 '17 at 3:18












1 Answer
1






active

oldest

votes


















0














There is a 915resolution module which enables GRUB 2 to enable Intel's non-standard resolutions. It is based off of the userspace 915resolution which adds VBE entries at runtime for these resolutions; they're not otherwise available from BIOS.






share|improve this answer
























  • I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

    – TomSW
    Feb 12 '11 at 21:31











  • This time I read your answer properly - I'll try it, thanks

    – TomSW
    Feb 12 '11 at 21:43











  • This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

    – TomSW
    Feb 12 '11 at 23:22











  • @TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

    – ephemient
    Feb 13 '11 at 0:06











  • @ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

    – TomSW
    Feb 13 '11 at 7:37












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f246811%2fcant-get-1440x900-resolution-with-grub2-although-vbeinfo-says-its-available%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














There is a 915resolution module which enables GRUB 2 to enable Intel's non-standard resolutions. It is based off of the userspace 915resolution which adds VBE entries at runtime for these resolutions; they're not otherwise available from BIOS.






share|improve this answer
























  • I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

    – TomSW
    Feb 12 '11 at 21:31











  • This time I read your answer properly - I'll try it, thanks

    – TomSW
    Feb 12 '11 at 21:43











  • This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

    – TomSW
    Feb 12 '11 at 23:22











  • @TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

    – ephemient
    Feb 13 '11 at 0:06











  • @ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

    – TomSW
    Feb 13 '11 at 7:37
















0














There is a 915resolution module which enables GRUB 2 to enable Intel's non-standard resolutions. It is based off of the userspace 915resolution which adds VBE entries at runtime for these resolutions; they're not otherwise available from BIOS.






share|improve this answer
























  • I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

    – TomSW
    Feb 12 '11 at 21:31











  • This time I read your answer properly - I'll try it, thanks

    – TomSW
    Feb 12 '11 at 21:43











  • This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

    – TomSW
    Feb 12 '11 at 23:22











  • @TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

    – ephemient
    Feb 13 '11 at 0:06











  • @ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

    – TomSW
    Feb 13 '11 at 7:37














0












0








0







There is a 915resolution module which enables GRUB 2 to enable Intel's non-standard resolutions. It is based off of the userspace 915resolution which adds VBE entries at runtime for these resolutions; they're not otherwise available from BIOS.






share|improve this answer













There is a 915resolution module which enables GRUB 2 to enable Intel's non-standard resolutions. It is based off of the userspace 915resolution which adds VBE entries at runtime for these resolutions; they're not otherwise available from BIOS.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 12 '11 at 20:50









ephemientephemient

19.5k42319




19.5k42319













  • I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

    – TomSW
    Feb 12 '11 at 21:31











  • This time I read your answer properly - I'll try it, thanks

    – TomSW
    Feb 12 '11 at 21:43











  • This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

    – TomSW
    Feb 12 '11 at 23:22











  • @TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

    – ephemient
    Feb 13 '11 at 0:06











  • @ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

    – TomSW
    Feb 13 '11 at 7:37



















  • I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

    – TomSW
    Feb 12 '11 at 21:31











  • This time I read your answer properly - I'll try it, thanks

    – TomSW
    Feb 12 '11 at 21:43











  • This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

    – TomSW
    Feb 12 '11 at 23:22











  • @TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

    – ephemient
    Feb 13 '11 at 0:06











  • @ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

    – TomSW
    Feb 13 '11 at 7:37

















I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

– TomSW
Feb 12 '11 at 21:31





I have no problems using 1440x900 once linux has booted - sorry, I hadn't made that clear.

– TomSW
Feb 12 '11 at 21:31













This time I read your answer properly - I'll try it, thanks

– TomSW
Feb 12 '11 at 21:43





This time I read your answer properly - I'll try it, thanks

– TomSW
Feb 12 '11 at 21:43













This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

– TomSW
Feb 12 '11 at 23:22





This alters stuff pre-boot so as to ensure a correct resolution for the booted linux console. In my case the linux console reslution is fine, I just want the highest possible pre-boot (grub) resolution, IMO 1440x900

– TomSW
Feb 12 '11 at 23:22













@TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

– ephemient
Feb 13 '11 at 0:06





@TomSW: Hmm. So even if you load it first, it doesn't affect Grub's own VBE module (that gfxterm uses)? I don't have any similar hardware so I can't test. If that's the case, then I can't think of any solutions, sorry.

– ephemient
Feb 13 '11 at 0:06













@ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

– TomSW
Feb 13 '11 at 7:37





@ephemient: loading the module doesn't make a difference. I found a bug report that suggests the bios lists the correct modes but incorrectly programs them: bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111. Whatever that means exactly.

– TomSW
Feb 13 '11 at 7:37


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f246811%2fcant-get-1440x900-resolution-with-grub2-although-vbeinfo-says-its-available%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...