SliTaz Forum
You are not logged in.
Pages: 1
I'm using the rolling 586 version on a Thinkpad 760E ( https://www.thinkwiki.org/wiki/Category:760E - the Trident Cyber9320 version)
The 8 bit modus is broken using following xorg.conf:
[c]Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 8
SubSection "Display"
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection[/c]
slim is ok, but esp. the font rendering in the desktop and in the applications is completly broken - most is missing and heavy artifacts. That also happens after disabling antialiasing and hinting alltogether
Occours both with the vesa and the trident (which are a different story, 16 bit is not working even if using "Option "NoAccel" "True" https://oldforum.puppylinux.com/viewtopic.php?p=46896#p46896 and after starting X, the text consoles are garbled - manpage: https://www.x.org/releases/current/doc/man/man4/trident.4.xhtml) driver.
Offline
Quick question, think on 4.0 you don't have artefacts and rendering issue ?
On 4.0 we have Xorg 1.9.5 and 1.12.4 on rolling, but think not limit to this.
Packages on rolling are more recent that 4.0, and maybe broken something.
For https://www.thinkwiki.org/wiki/Trident_Cyber9320, if understand, chipset not work properly with "trident" driver but smooth with vesa, on your situation seem not the case 
.
Offline
I'll try it with 4.0 later.
Just for clarification: Vesa is working at 800x600@16 bit (albeit slow, which is the fate of using vesa in general...). It is the 8 bit mode which is broken - and I think it is not a Xorg problem, but a Toolkit problem, as the login screen from slim is ok.
Regarding trident: It seems that 800x800@16 bit should have been working regarding search results if disabling acceleration, but it isn't. I opened an issue at https://gitlab.freedesktop.org/xorg/driver/xf86-video-trident/-/issues/13 .
Offline
I check for xf86-video-trident, seem we use latest available.
At time, can't purpose to test 6.0 x86 version (can't boot with low memory, rootfs too big, need at least 768M to boot live mode 
).
Also need to add kernel586 on 6.0, but need fix boot failed on low memory.
I see we have CONFIG_FB_VESA=y and "# CONFIG_FB_TRIDENT is not set"
https://www.kernelconfig.io/CONFIG_FB_TRIDENT
Maybe i can check to add it as module for linux586 and rebuild kernel and iso for you try it ?
Offline
Big rootfs is no problem for me (ok, until about 1.5 GB) ;-)
My install procedure:
1. Eject the CF card from the target computer (sits iin an CF->IDE adapter)
2. Insert it into the CF reader from my "big" computer (which has ... enough RAM, 32 GB should be enough *g*)
3. Start qemu/kvm with this as hda and the iso image as cdrom, using the cdrom as start medium
4. Install the system to the CF card
5. Shutdown and put the CF card in the target computer again
But trying the fb trident module is a good idea as well :-)
Offline
Good idea to use qemu to prepare sdcard 
.
Iso available with kernel586 (trident build as module)
https://people.slitaz.org/~shann/rolling_586/slitaz-cooking-core586-trident.iso
For 6.0 x64, rootfs of core (desktop) is ~370Mo, when boot need twice to use it on tmpfs.
For 6.0 x86, rootfs of core (desktop) is ~313Mo, when boot need twice to use it on tmpfs.
For rolling rootfs size (desktop) is ~207Mo
Diff size compared to rolling explain by gstreamer1.0, libwebkitgtk (~50Mo for .so libs), and other libs in 6.0.
Offline
I doing quick check between iso of 6.0 and rolling.
It's concerning core64 (full 64bits desktop)
firmware-amdgpu add 71.5M
grub2 add 34.6M
grub2-efi-x64 add 41.5M
grub2-efi-x64-modules add 3.3M
tazweb (build with webkitgtk 2.4.11) with webkitgtk add 33.4M and more with deps (gst-plugins-base-1.0, harfbuzz-icu, libsoup ...)
=> tazweb-legacy build with libwebkit need for tazpanel (issue login with libsoup 2.74 but ok with libsoup 2.48)
web-applications (add gst-libav for radio), with gst-libav add 15M and more with deps (gst-plugins-base-1.0, gst-plugins-good-1.0)
Without theses packages, 6.0 iso rootfs is similar to rolling ~205Mo, that allow to boot correctly with 512M of RAM.
For core (full 32bits desktop), similar but only concerning tazweb / web-applications, don't include grub2 stuff, keep grub4dos-linux / syslinux
If i would like add linux586 on 6.0, need to purpose iso boot properly with low ram.
Offline
Hmm, I tried the Trident TGUI9440 in PCem, but it seems that there is an imcompatiblity between the kernel and the HDD emulation (HSM violation). Ok, real HW again^^
Offline
The trident framebuffer driver helps:
1. the restoration of the text mode works
2. the FB Xorg driver can be used, which is already way faster than the vesa driver :-)
Some drawbacks:
1. The FB Xorg driver is distored
2. The Vesa driver can't be used anymore
The trident Xorg driver is still broken in 16 bit mode - also in 640x480.
Perhaps it could be an idea to move the kernel FB drivers in an extra optional module package, and/or have an cmdline/rcS option?
Offline
i build iso with trident fb module included for you can do test.
Thanks for test, i can pack tridentfb as external module linux586-tridentfb could be installed if user would like use it.
And for blacklist module if need you can create [c]/etc/modprobe.d/blacklist.conf[/c] file and put module on it.
[c]blacklist tridentfb[/c]
Offline
That would be nice :-)
Offline
Pages: 1
[ Generated in 0.022 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]