no boot with beta5, stuck before desktop

[Alexco]

Beta5 does not boot on my old Celeron 32-Bit system. This system already has some reported issues with Matrox GFX card:

https://dev.haiku-os.org/ticket/12254

https://dev.haiku-os.org/ticket/18310

So I use fail-safe gfx driver and set a resolution of 1024x786x32 for booting. The boot stops right after the last icon (rocket), it stays there forever, never shows KDL or the desktop.

I attached the beta3 and beta5 syslogs.

[korli]

from syslog beta5, actually it's master:

KERN: assuming memory type 20000000 for overlapping 0xd8000000, 0x8000 area 7163 from existing 0xd8000000, 0x300000 area 143
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/matrox

in beta3

KERN: set MTRRs to:
KERN:   mtrr:  0: base:    0xff000, size:     0x1000, type: 0
KERN:   mtrr:  1: base: 0x2fff0000, size:    0x10000, type: 0
KERN:   mtrr:  2: base: 0xd8000000, size:     0x8000, type: 0
KERN:   mtrr:  3: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  4: base: 0xd8000000, size:  0x8000000, type: 1
KERN: set MTRRs to:
KERN:   mtrr:  0: base:    0xff000, size:     0x1000, type: 0
KERN:   mtrr:  1: base: 0x2fff0000, size:    0x10000, type: 0
KERN:   mtrr:  2: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  3: base: 0x80000000, size: 0x80000000, type: 1
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/matrox

[korli]

Alexco, you can try in the bootloader to enable "Disable PAT support".

[mmlr]

It looks like the CPU here falls into the group with broken PAT support. I've compared with FreeBSD and Linux and both special case certain CPUs with PAT errata, either disabling PAT (FreeBSD) or using a different PAT layout (Linux) to work around the issue.

I've uploaded ​this change that should disable PAT on such CPUs. Until this change is merged, using the safemode option "Disable PAT" as korli suggested above should yield the same result.

[Alexco]

Sorry, but disabling PAT in the bootloader does not solve the issue, neither the Matrox KDL issue, nor the non booting one. It simply says at that red rocket forever.

[waddlesplash]

Can you collect a second syslog with PAT disabled?

[cratuki]

Shows kernel debugging

[cratuki]

I have built a system that is showing similar symptoms.

(1) I have a Matrix Millennium II (PCI) and a Matrox Millennium G450 (AGP). Crashes to kernel log during boot in both situations. (Attached image 20241128... is from the Millennium II boot)

(2) When I set graphics to safe mode in the boot menu, it gets to the red rocket and never goes beyond.

I don't see a setting in the /safe mode options/ screen for "Disable PAT". If you can point me to it, I may be able to gather more information.

I don't know how to get the logging that you are talking about. If you can send me instructions, I can try to collect it.

System,

• Motherboard: ABIT VP6 based on the VIA VT82C694X (Apollo Pro 133A)
• RAM: 512MB
• CPUs: 2x P3-1Ghz.

Same behaviour booting from IDE-to-cf or IDE-to-sdcard. In both cases I used dd to copy the image to the media from Linux.

BeOS R5 installs to the system and boots when installed.

[cratuki]

Millennium II configuration, Safe mode enabled. Gets stuck at red rocket.

[cratuki]

OK. I have worked out the syslog situation. Syslog attached, from safe mode where it gets stuck at the red rocket. Do let me know if there is anything else constructive I can do.

[waddlesplash]

It looks like it's gotten all the way to framebuffer initialization, but then for some reason the desktop never comes up. Not sure what that could be.

Please try with a nightly build and see if anything's different; it should use less RAM and that may help.