app_server preventing boot on live USB (hrev51702 x86)

[geminiman112]

This KDL screen appeared when trying to boot from a Haiku live USB on one of my computers. However, on my main computer, this USB boots just fine.

I had Haiku installed on this computer before. Weirdly, it was using the USB device as a bootloader. I was going to fix it today, but then this error occurred.

Later, I deleted all of the partitions on my hard drive using a Linux live CD, but this error persisted.

[waddlesplash]

I get "Error 403" when trying to view the image. Could you just attach it here?

Also, if it's actually an app_server crash, it's not a KDL but a Debugger prompt. If you type save-report at the prompt it will write a report to ~/Desktop and you can fetch it on next reboot.

[geminiman112]

It does not have a patch. I'm sorry, this site is new to me.

Edit: It was an app_server crash. Here is the report: ​https://pastebin.com/MEHuVC6i

[geminiman112]

I have looked back into this bug and it appears to be very similar to #2350.

Edit: I changed my graphics card setting to default to the integrated graphics and this error persists, except app_server stops on thread 340 as opposed to 342.

[waddlesplash]

Indeed it does. Can you extract a syslog from the failed boot? (It will be in /var/log/syslog).

[geminiman112]

I can.

​https://pastebin.com/sABgm6fd

Edit: For some strange reason, while this bug does occur on my Sansui television, on my Dell computer monitor, the computer boots up just fine.

When I boot the machine using the Dell monitor and switch to the Sansui television, the screen goes black.

My LG television also appears to work fine.

[waddlesplash]

It looks like the TV does not support any video modes that the VESA chipset on your computer also does (there is a 1024x768 mode in both but the chipset has it only in 60Hz while the TV has 75Hz.) So, not a whole lot we can do here I think, aside from #10570.

[geminiman112]

If that is the case, then why does the Haiku boot screen still load?

[waddlesplash]

Hmm, not sure, I'm not very familiar with how we output graphics at that stage. Depending on how your BIOS works we may be reusing a framebuffer from that.

[geminiman112]

Replying to waddlesplash:

Hmm, not sure, I'm not very familiar with how we output graphics at that stage. Depending on how your BIOS works we may be reusing a framebuffer from that.

I don't know if that's the case. I can change screen resolutions on the boot screen (for example, I can get 640x480 graphics mode and 16 bit color as opposed to the default to work).

[pulkomandy]

The boot screen uses vesa, and kdl and debugger prompt both use the framebuffer as app_server. So it seems we do manage to display something in a sane video mode.

[geminiman112]

Replying to waddlesplash:

It looks like the TV does not support any video modes that the VESA chipset on your computer also does (there is a 1024x768 mode in both but the chipset has it only in 60Hz while the TV has 75Hz.) So, not a whole lot we can do here I think, aside from #10570.

My TV only does 60Hz.