Announcing tinyx - our X server fork

[Misalf]

-noreset does totally eliminate the problem.
I exited out of X and re-'startx'ed eleven times and always had a WM and the custom fonts I have installed.

--

I'm not sure what you mean by 'cpu specs'..

My netbook [MSI Wind U100]:
(Xvesa working flawlessly)
- CPU: Intel Atom N270

$ time Xvesa -startbench

Code: [Select]

Could not init font path element /usr/lib/X11/fonts/TTF/, removing from list!
Could not init font path element /usr/lib/X11/fonts/OTF/, removing from list!
Could not init font path element /usr/lib/X11/fonts/Type1/, removing from list!
Could not init font path element /usr/lib/X11/fonts/100dpi/, removing from list!
Int 10h (0x4F08) failed: 0x034F (function call invalid in this video mode)
real    0m 0.29s
user    0m 0.01s
sys     0m 0.09s(I'm cheating here - this is still the Xvesa I built myself but..)

--

Desktop PC [HP Compaq dc7700]:
(troublesome)
- CPU: Intel Pentium D 925

$ time Xvesa -startbench

Code: [Select]

Could not init font path element /usr/lib/X11/fonts/TTF/, removing from list!
Could not init font path element /usr/lib/X11/fonts/OTF/, removing from list!
Could not init font path element /usr/lib/X11/fonts/Type1/, removing from list!
Could not init font path element /usr/lib/X11/fonts/100dpi/, removing from list!
Int 10h (0x4F08) failed: 0x034F (function call invalid in this video mode)
real    0m 2.18s
user    0m 0.49s
sys     0m 1.45s(This is with your build)

[curaga]

Before I try, does the fork compile 64-bit?

It does, I specifically aimed for 64-bit cleanliness. Even Xvesa compiles, though it will not work (and there's a runtime check to avoid a corrupted display).

@Misalf

Thanks, will change the default to be noreset then. Your PC is quite powerful, but it takes ten times longer to put up a screen than the netbook.

[Misalf]

Weird.. No problem for me though while you walk-it-around.
xsetup also shows the same display modes as available in current Xvesa.

Tomorrow I'll try Xfbdev on that thing (current Xfbdev performs very bad/slow).

[gerald_clark]

Here are my findings with My Radeon X1200.  onboot.lst contains Xprogs, aterm, and flwm_topside.
The X driver is loaded manually.
Version  -  memory used (free) -  VSZ of driver ( top)
Xvesa old - 34636 - 26572
Xvesa new - 31548 - 24596

Xfbdev old - 29588 - 7784
Xfbdev new - 30600 - 8392

Xvesa is a little smaller.  Xfbdev is a little larger.

I am having some issue with evince2 with these drivers,
The only one that has no problem with evince2 is the old Xfbdev.
All the others generate an error and terminate evince when expanding the window to full screen width.
evince: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

[curaga]

@gerald_clark

Sorry for the delay.

I just tried evince2 on 5.1, with its shipping Xvesa, flwm_topside. It maximized without any issues.

As I can't reproduce, is that the full error? Usually X errors also display the major and minor opcodes.

[dfattcl]

Quick question - with the changes being made to move away from VGA to GOP, do you know if VESA will still be available for GOP?  If not will a new GOP driver be required?  or is it that frame buffer mode from the kernel would cover GOP and tinyx would/could use the frame buffer mode?

TIA!!

[curaga]

The kernel framebuffer + Xfbdev work fine on the EFI framebuffer.

[Juanito]

do you need any special boot codes for Xfbdev to work with the efi framebuffer?

[Juanito]

'took me a while to get round to it, but tinyx Xvesa compiles to a 356k extension (deps libXfont, libXdmcp, Xorg-fonts) and works fine at my laptop (intel hd3000) native resolution of 1366x768.

The logitech vx nano mouse movement it a little jumpy (as with Xorg and mouse driver, but not with Xorg and evdev driver), but otherwise OK.

evince (gtk3) at 400% is OK, evince2 (gtk2) also OK at 400%

[curaga]

No bootcodes needed for efi fb, in my experience it modesets directly to the highest res available.

[Juanito]

tinyx Xfbdev compiles to an x86_64 extension of 404k compared to current 620k 

Booting without boot codes looks like it gives 800x600:

Code: [Select]

$ cat /sys/class/graphics/fb0/modes
U:800x600p-75
grub2 command "set gfxpayload='1366x768x24'" has no effect - haven't yet figured out how to query available efi fb modes (and have not yet tried vga=0x318 video=vesafb:mtrr) 

Logitech vx nano usb mouse is very jittery

evince works at 400%

[curaga]

Seems we have conflicting reports, as Gerald said in the other thread that the recompiled evince was still failing.

[Juanito]

The recompiled evince was x86 gtk2 version, I was testing x86_64 Xfbdev (although I cannot get it to fail with x86 Xvesa or Xorg)

Tracked down and compiled modelist.efi - any ideas where this is run from - grub2 console ignores it, efi console font becomes corrupted when run, not a native linux executable 

[curaga]

No idea, sorry.

[Juanito]

Code: [Select]

$ file modelist.efi
modelist.efi: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows
..doesn't give much away - interesting that it says windows when compiled with linux

Edit: some progress:

Code: [Select]

grub> videoinfo
List of supported video modes:
Legend: mask/position=red/green/blue/reserved
Adapter: `EFI GOP Driver`:
 0x000 1366x768x32 (5464) Direct color mask: 8/8/8/8 pos: 16/8/0/24
 0x001 1024x768x32 (4096) Direct color mask: 8/8/8/8 pos: 16/8/0/24
 0x002  640x489x32 (2560) Direct color mask: 8/8/8/8 pos: 16/8/0/24
*0x003  800x600x32 (3200) Direct color mask: 8/8/8/8 pos: 16/8/0/24

EDID Version: 1.4
Preferred mode: 1366x768