I’ve just acquired a HP T520 thinclient, which has an AMD Radeon R2E onboard for the graphics.
I can’t get to the Haiku Desktop without having the boot into safe mode with the graphics fallback driver being used.
Is there any way to get this to work correctly with the Radeon_HD driver or to setup the system to default to VESA on every boot.
I don’t think there is any way to use the Radeon HD driver if it doesn’t support your card,at least not without deep knowledge of driver development.
The better way to solve this is to force VESA.
You can do this in ~/config/settings/kernel/drivers/kernel by uncommenting “fail_safe_video_mode true”
Thanks for the advice about enabling the fallback driver.
The system does load the Radeon_HD driver just it doesn’t seem to work once loaded just results in a black screen
If it results in a black screen,that means your hardware isn’t properly supported.
As a first step,someone should modify the driver to not even try to load if that unsupported hardware is detected.
Adding proper support for additional hardware would be the more tricky part,and maybe only realistic if a developer owns exactly the same graphics card you have.
Please open a bugreport with the output of ‘listdev -v’ so we can disable the driver for your hardware.
The advantage of radeon_hd is mostly stuff like modesetting and backlight control. But vesa works too, if you have the native resolution with it then you are only missing backlight support.
I have Haiku running on my HP T520 without problems, except a bit of screen tearing when using a web browser, (I’ll hazard a guess that your monitor EDID may be the problem), try with a different monitor, if you have one.
(I use 21.5" DP monitors made by Iiyama & HP.)
What bios are you running on your T520?
Ive tried 3 different monitors:
none of these work except when the GPU is set ot fallback and use VESA.
I think mine is set to MBR, because it is easiest to use with Haiku, other than that it is a standard HP T520 - (1.2GHz dual core/4GB ram/16GB M2 SSD).
I do rum mine from DP to a DP monitor though, maybe your DP>HDMI cable isn’t compatible(?).
That is not an option booting in UEFI mode which launches framebuffer which can’t change resolutions on programs.
That’s not quite correct, you can’t change resolution after boot. But the resolution can be changed from the boot menu. Once you have found one that works you can add this to your settings file for vesa and system will pick it up when booting in framebuffer mode
That was an observation. This makes the same thing as AROS with vesa drivers. But this for the programs does not work very well. In aros vesa drivers you can add múltiple resolutions in grub but there IS no efi.config file to add múltiple resolutions to change and there IS no code in place for Mode switching in framebuffer driver which IS a must to do for a programmer, and/or for a user.
No, this is not a must. This is simply not possible with the efi api.
Changing the resolution if your display is a bit of a thing of the past. Most modern OS always use your native resolution (perhaps changing the refresh rate) and then scale on their own. If you don’t do this the display will scale for you with it’s own wierd alghorythm. : )
One peculiarity I noticed on my laptop with a 1920x1200 display is that Haiku is stretched a bit taller when set by the framebuffer to 1080p. Meanwhile, setting the same resolution on Linux causes the display output to be letterboxed instead.
I haven’t got tested Desktop Linux only with framebuffer if i can change resolutions after Desktop IS loaded and or before on efi grub adding on It the resolutions. Because all of the major cards had a proper driver.