xvesa boot code not overriding resolution on persisten install

[baz]

I booted up a clean TC from a unetbootin USB stick and specified a custom xvesa=800x600x16 and it worked great.

However, when I installed TC to the disk using persistent tce, opt and home - then installed 915resolution.tcz and changed the boot code to xvesa=1024x600x32, the resolution did not change on next boot. Other standard resolutions and color depths that I tested didn't do anything either. Is this normal given my setup or a bug?

Cheers,
Baz

[roberts]

915resolution overrides xvesa boot option.

[baz]

It doesn't seem to be completely overriding it. I used the Xvesa_Setup tool to select my preferred resolution as I have done before, but left the boot code as is since you said it gets overridden. But when I reboot, I am prompted by the Xvesa setup menu before the TC desktop appears (this happens every time you reboot). I then removed the boot code and that cleared it up, but I feel it is worth mentioning because some sort of conflict is occurring with it - the boot code is not being applied but at the same time not completely ignored.

It would be nice to be able to leave the boot code in case something ever happens to 915resolution or some other setting - at least it will fall back to a usable resolution - or ignored otherwise.

Cheers,
Baz

[baz]

Any word on this?

[roberts]

Use one or the other not both. When you have a mismatch or multiple setting xsetup is called.