Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: risto3 on February 18, 2015, 08:29:29 AM

Title: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 18, 2015, 08:29:29 AM
made the mistake upgrading from 5.4 prior to testing first
(always forget tiny doesn't have rollback)

Xorg now fails in and around here :

Quote
[  2062.502]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[  2062.505] X Protocol Version 11, Revision 0
[  2062.506] Build Operating System: Linux 3.16.6-tinycore i486
[  2062.506] Current Operating System: Linux cbox1 3.16.6-tinycore #777 SMP Thu Oct 16 09:42:42 UTC 2014 i586
[  2062.506] Kernel command line: initrd=/tce/boot/core.gz host=cbox1 quiet noautologin nozswap lang=fr_FR.UTF-8 kmap=azerty/fr-pc waitusb=5:UUID="49e0e97d-f8ec-4ed0-9991-342ca1655155" tce=UUID="49e0e97d-f8ec-4ed0-9991-342ca1655155" opt=UUID="49e0e97d-f8ec-4ed0-9991-342ca1655155" home=UUID="49e0e97d-f8ec-4ed0-9991-342ca1655155" BOOT_IMAGE=/tce/boot/vmlinuz
[  2062.507] Build Date: 13 February 2015  05:30:32PM
[  2062.508] 
.. snip
[  2062.549] (II) LoadModule: "vesa"
[  2062.550] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[  2062.551] (II) Module vesa: vendor="X.Org Foundation"
[  2062.551]    compiled for 1.17.1, module version = 2.3.3
[  2062.551]    Module class: X.Org Video Driver
[  2062.551]    ABI class: X.Org Video Driver, version 19.0
[  2062.552] (II) VESA: driver for VESA chipsets: vesa
[  2062.552] (--) using VT number 2

[  2062.558] (II) Loading sub module "vbe"
[  2062.558] (II) LoadModule: "vbe"
[  2062.559] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[  2062.560] (II) Module vbe: vendor="X.Org Foundation"
[  2062.560]    compiled for 1.17.1, module version = 1.1.0
[  2062.561]    ABI class: X.Org Video Driver, version 19.0
[  2062.561] (II) Loading sub module "int10"
[  2062.561] (II) LoadModule: "int10"
[  2062.562] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[  2062.563] (II) Module int10: vendor="X.Org Foundation"
[  2062.563]    compiled for 1.17.1, module version = 1.0.0
[  2062.563]    ABI class: X.Org Video Driver, version 19.0
[  2062.563] (II) VESA(0): initializing int10
[  2062.564] (EE) VESA(0): Cannot read int vect
[  2062.564] (II) UnloadModule: "vesa"
[  2062.564] (II) UnloadSubModule: "int10"
[  2062.564] (II) Unloading int10
[  2062.565] (II) UnloadSubModule: "vbe"
[  2062.565] (II) Unloading vbe
[  2062.565] (EE) Screen(s) found, but none have a usable configuration.
[  2062.565] (EE)
Fatal server error:
[  2062.565] (EE) no screens found(EE)
[  2062.565] (EE)

Any idea?
Else is there a simple way to revert Xorg from the command line?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: gerald_clark on February 18, 2015, 09:42:42 AM
You upgraded from 5.4 to what?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: Rich on February 18, 2015, 09:46:55 AM
Hi risto3
Quote
Else is there a simple way to revert Xorg from the command line?
If you mean back to Xvesa, then:
Code: [Select]
cp /etc/skel/.xsession /home/tc
startx
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: gerald_clark on February 18, 2015, 10:06:14 AM
You upgraded to Core 6.  Now you need to update all your extensions and modules.

tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update

sudo reboot
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 18, 2015, 10:16:18 AM
You upgraded to Core 6.  Now you need to update all your extensions and modules.

tce-audit builddb
tce-audit updatedeps
tce-audit fetchmissing
tce-update

sudo reboot

Hi, did all this... (well, except the first step, the second seemed to pick it up)..
any other ideas?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 18, 2015, 10:51:51 PM
Perhaps this has something to do with it:
http://cgit.freedesktop.org/xorg/xserver/commit/hw/xfree86/int10?id=21b216ad6ce2e9c89359b95e4196e42d91bf9420
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 19, 2015, 06:03:05 AM
Well, notwithstanding, the good news is I seem to be able to get Xvesa going...
after setting /etc/sysconfig/Xserver to 'Xvesa' and manually editing .xsession.

Unfortunately this still sucks as we needed Xorg in the first place for our "fr" keyboards.
Anyway to test elsewhere and revert this toxic change (for a Vortex86mx RDC vga).

Prior I tried to force going back to 5.x, but only Xorg 7.7 seems to be in the repository,
so Xorg is busted there now too. Saloperie!
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: Juanito on February 19, 2015, 11:23:39 PM
I don't have the hardware to test, but if you want to apply the patch, recompile xorg-server and test, the extension can be updated if things work.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on February 20, 2015, 01:12:58 AM
..and if reverting that change fixes it, you should report a bug upstream so it can be fixed there.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 20, 2015, 03:03:39 PM
This is a thin client without the resources to build xorg & related. sorry.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on February 21, 2015, 01:43:10 AM
Use a bigger machine, or a VM on a bigger machine?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on February 23, 2015, 12:52:16 PM
Sorry, run unix on real iron... prefer the older bits, how to revert?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 05, 2015, 10:11:12 AM
checkout the thread "[PATCH] int10: Fix mapping the interrupt vector" on xorg-devel@lists.x.org
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 09, 2015, 02:24:46 AM
did this patch fixup make it into 6.1? if not, is it possible to respin VESA with it fixed?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on March 09, 2015, 02:27:39 AM
The patch hasn't even been applied upstream yet. It would help if you reply to that thread saying it broke vesa for you, showing them there's need.

Xorg is an extension, it can update independently from ISO releases. Also, only xorg-server needs to be updated, as that patch is for it only.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 16, 2015, 03:58:18 AM
The update patch is now committed upstream. Is there any reason not to cherry-pick an respin?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on March 16, 2015, 12:45:59 PM
Yeah, the patch can now be applied to xorg-server. Juanito, do you have time?

http://cgit.freedesktop.org/xorg/xserver/patch/?id=0a78b599b34cc8b5fe6fe82f90e90234e8ab7a56
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: Juanito on March 16, 2015, 12:57:58 PM
I should be able to get around to it in a couple of days time
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: Juanito on March 18, 2015, 11:19:49 AM
patched xorg-server posted
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on March 18, 2015, 02:22:41 PM
Confirming that vesa is fixed.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 23, 2015, 04:42:52 AM
I can confirm that I can get Xorg up, but I seem to notice a considerable performance regression compared to the previous version. 

The easiest way to experience it is with a couple of windows up ('top' is a good one) and moving a window around with the mouse... 

there is an extreme lag (sort of like ants scrawling to keep up:-) and noticeable Xorg cpu utilisation.

also, it is unclear where XkbLayout and XkbModel should be put as now there is a
/usr/local/share/X11/xorg.conf.d/10-evdev.conf already.

manually doing 'setxkbmap -layout fr -model pc105'  works fine and my logitech setup works as did previously... including the € and numpad keys (yeah)

Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 23, 2015, 05:52:04 AM
also, it is unclear where XkbLayout and XkbModel should be put as now there is a
/usr/local/share/X11/xorg.conf.d/10-evdev.conf already.

copying the above file to /etc/X11/xorg.conf.d/  adding the options mentioned to it and adding the file to /opt/.filetool.lst as well seemed to get over this part.   Perhaps something for the wiki?
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 23, 2015, 06:08:33 AM
I can confirm that I can get Xorg up, but I seem to notice a considerable performance regression compared to the previous version. 

The easiest way to experience it is with a couple of windows up ('top' is a good one) and moving a window around with the mouse... 

there is an extreme lag (sort of like ants scrawling to keep up:-) and noticeable Xorg cpu utilisation.

actually quite psychedelic in VNC ... moving a terminal window e.g. laterally gives impression that
the side of the window buts, and partially disappears, into a transparent marshmallow... until it catches up and takes full form again.  >.,.<
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: curaga on March 23, 2015, 07:23:39 AM
Yeah, I can reproduce: Xorg + vesa maxes one core, while the default Xvesa gets 20-30%. But I'm not sure we can do anything about a regression upstream, as reverting would hurt Intel users as well as the Radeon user who requested this update in the first place.
Title: Re: another Xorg problem: VESA(0): Cannot read int vect
Post by: risto3 on March 24, 2015, 05:27:22 AM
OK, I filed https://bugs.freedesktop.org/show_bug.cgi?id=89747
Might be useful if everybody who experiences this chirps in.