05-23-2024, 03:05 PM
(This post was last modified: 05-23-2024, 03:08 PM by grindstone.)
Thanks for the log and for the effort. I found that Arch thread, too, yesterday and I think there's another shot in there.
Is there any option in BIOS to adjust amount of VRAM? Your video has the 16MB. Whenever it's probed in X (--), it's 4M (4096), right? And in Windows it's 4M. If it were NOT probed, we could simply tell X
VideoRam 16384
in the Device section, but because X does probe it, it ignores any VideoRam entry. That makes me think it's what the BIOS says it is.
What's clear is that it's defaulting to using XAA acceleration when the SMI driver is used. If you go read about EXA, it's implemented for siliconmotion.
Option "AccelMethod" "EXA"
That doesn't solve the memory limit problem but it's another thing to try in a very simple config file (w/o running the -configure).
This is actually a good bug to read, too. Origin of 1024x1024 we saw early--it's in an X/Siliconmotion bug thread.
https://bugs.freedesktop.org/show_bug.cgi?id=21528
Between that and that same Arch thread,
https://bbs.archlinux.org/viewtopic.php?id=187477
here's a hand-hacked-up shot:
I took out loading glx which is for network stuff and might (should?) load by default anyway. The pci bus it'll find anyway, etc. See if we can get an Xorg.log outta that. The main try is the EXA vs. XAA but the SW cursor bit is from the Arch thread, too (no 3-D makes sense). Hopefully the BIOS allows an entry exceeding 4M, though, first. Then that might work the way it was.
And honestly, perhaps to elevate it to better quality help, if you burn Plop on a CD and (even USB1.0) find the same exact problem with AntiX 23.1 runit 32-bit, it may result in increased participation at the AntiX forum. OTOH, if that works...we'll have mighty valuable feedback for John.
See what you think.
Is there any option in BIOS to adjust amount of VRAM? Your video has the 16MB. Whenever it's probed in X (--), it's 4M (4096), right? And in Windows it's 4M. If it were NOT probed, we could simply tell X
VideoRam 16384
in the Device section, but because X does probe it, it ignores any VideoRam entry. That makes me think it's what the BIOS says it is.
What's clear is that it's defaulting to using XAA acceleration when the SMI driver is used. If you go read about EXA, it's implemented for siliconmotion.
Option "AccelMethod" "EXA"
That doesn't solve the memory limit problem but it's another thing to try in a very simple config file (w/o running the -configure).
This is actually a good bug to read, too. Origin of 1024x1024 we saw early--it's in an X/Siliconmotion bug thread.
https://bugs.freedesktop.org/show_bug.cgi?id=21528
Between that and that same Arch thread,
https://bbs.archlinux.org/viewtopic.php?id=187477
here's a hand-hacked-up shot:
Code:
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
EndSection
Section "Module"
Load "fbdevhw"
Load "freetype"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
Option "Emulate3Buttons" "yes"
EndSection
Section "Device"
Identifier "Device0"
Driver "siliconmotion"
Option "AccelMethod" "EXA"
Option "HWCursor" "false"
Option "SWCursor" "true"
Option "NoMTRR"
EndSection
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5-57.5
VertRefresh 55-80
Modeline "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
DefaultDepth 16
Monitor "Monitor0"
SubSection "Display"
Virtual 1024 768
EndSubSection
EndSectionI took out loading glx which is for network stuff and might (should?) load by default anyway. The pci bus it'll find anyway, etc. See if we can get an Xorg.log outta that. The main try is the EXA vs. XAA but the SW cursor bit is from the Arch thread, too (no 3-D makes sense). Hopefully the BIOS allows an entry exceeding 4M, though, first. Then that might work the way it was.
And honestly, perhaps to elevate it to better quality help, if you burn Plop on a CD and (even USB1.0) find the same exact problem with AntiX 23.1 runit 32-bit, it may result in increased participation at the AntiX forum. OTOH, if that works...we'll have mighty valuable feedback for John.
See what you think.