No native graphics support for Radeon HD6250

[mounty]

Related to #13547 but not the same. On a Wyse D10D ​https://www.cnet.com/products/dell-wyse-d10d-thin-client-g-t48e-1-4-ghz-monitor-none-series/ when Haiku boots, it displays the seven startup icons and shows them going from monochrome to colour as boot proceeds, but then the screen goes entirely blank and the monitor displays a 'no input' dialog and goes to sleep.

Workaround is to interrupt the boot process and select the safe-mode graphics driver.

This is a build-from-source under Linux, hrev53658.

[diver]

Could you boot normally till black screen, wait for a few seconds then Ctrl+Alt+Del to reboot and boot with safe-mode graphics driver? Then grab /var/log/syslog and /var/log/syslog.old and attach here.

[mounty]

screen shot after increasing resolution

[mounty]

The problem appears to have disappeared on a reboot; however, there is a different but circumventable issue. When I was running with fail-safe driver I switched the resolution to (I think) 1280x1024 or maybe 1600x900. When I rebooted without fail-safe, the display did show correctly. I then switched the display to its native 2560x1600 which kind-of worked, except that as shown in the attached screen-shot, the driver did not appear fully to accept the change in resolution:

• Right and bottom of display not reset to background when a window is moved around.
• Workspaces replicant is about 3x normal size; maybe top-left corner is fixed to its correct position at the 'old' resolution.

Rebooting again fixes this but it seems that the display stack at some level doesn't handle a change in resolution. I have no explanation of why the display did not work the first time but did after having been run with the fail-safe driver.

[diver]

This seems to be either Tracker or app_server bug, I've seen it several times too and it worth a separate ticket.

So you're saying black screen with radeon_hd is gone now? Weird.

[mounty]

In the course of investigating another ticket, I reinstalled Haiku on the machine and the problem re-appeared; i.e., blank screen on boot. I rebooted with the safe-mode driver and set the resolution to 1920x1440 and rebooted. This time, the boot hung quite early; the seven start-up icons were present but all still monochrome. Caps Lock etc. did not work.

Anyway, I reinstalled again, booted to the black screen, then powered-down 'blind'. I'd memorised the necessary mouse-movements and keyboard strokes to navigate to the power-down option.

I then booted into Linux and extracted /system/var/log/syslog from the Haiku FS, and it is attached, as requested.

[mounty]

/system/var/log/syslog

[mounty]

BTW, after a second etc. reboot, there was no syslog.old file, which is why I obtained syslog via Linux, to avoid rebooting into Haiku and losing the syslog from the blank-screen boot.

Oh and just for the sake of completeness: when all seven start-up icons have gone from monochrome to colour, the display does flash all white for about 0.25 s before the signal is cut and it goes to sleep.

[mounty]

syslog from running of hrev54950

[mounty]

Symptoms unchanged with a build of hrev54950: when all seven start-up icons have gone from monochrome to colour, the display does flash all white for about 0.25 s before the signal is cut and it goes to sleep.