Xorg.0.log.txt => xorg-xf86-video-intel, xorg driver module, is not installed, so Xorg tried to load vesa but vesa refuses to start because the intel kernel module is loaded - nothing wrong, as i say you in my previous post i patched back xorg-xf86-video-intel to start with intel kernel module loaded and it worked in a strange way.
patch:
--- xorg-xf86-video-vesa-2.3.1/src/vesa.c
+++ ../stuff/src/vesa.c
@@ -454,14 +454,7 @@
pScrn = xf86ConfigPciEntity(NULL, 0, entity_num, NULL,
NULL, NULL, NULL, NULL, NULL);
if (pScrn != NULL) {
- VESAPtr pVesa;
-
- if (pci_device_has_kernel_driver(dev)) {
- ErrorF("vesa: Ignoring device with a bound kernel driver\n");
- return FALSE;
- }
-
- pVesa = VESAGetRec(pScrn);
+ VESAPtr pVesa = VESAGetRec(pScrn);
VESAInitScrn(pScrn);
pVesa->pciInfo = dev;
}
receipt
# SliTaz package receipt.
PACKAGE="xorg-xf86-video-vesa"
VERSION="2.3.1"
CATEGORY="x-window"
SHORT_DESC="Xorg Vesa video driver."
MAINTAINER="pankso@slitaz.org"
SOURCE="xf86-video-vesa"
TARBALL="$SOURCE-$VERSION.tar.bz2"
WEB_SITE="http://www.x.org/"
WGET_URL="$XORG_MIRROR/driver/$TARBALL"
# We can use xorg-server-light with evdev and vesa driver.
#DEPENDS="xorg-server"
BUILD_DEPENDS="xorg-server-dev"
MODS='/usr/lib/X11/modules'
# Rules to configure and make the package.
compile_rules()
{
cd $src
echo $src
patch -Np1 -i $stuff/dontcareaboutboundedkerneldriver.diff
./configure \
--sysconfdir=/etc \
--localstatedir=/var \
--with-xorg-module-dir=$MODS \
$CONFIGURE_ARGS &&
make && make install
}
# Rules to gen a SliTaz package suitable for Tazpkg.
genpkg_rules()
{
mkdir -p ${fs}${MODS}/drivers
cp -a ${install}${MODS}/drivers/*.so ${fs}${MODS}/drivers
}
package for rolling (but i'm not responsable of your hardware)
http://www.filedropper.com/xorg-xf86-video-vesa-231
Xorg.0.log-4.0.txt => there is a vga=normal kernel option, what does it do? maybe avoid video kernel modules loading? vesa starts ok.
Xorg.0.log-rolling.txt => vesa refuses to start because the intel kernel module is loaded - nothing wrong,
Xorg.0.log-portege-roll-09.txt => vesa has not found a kernel driver bound to the grapgic card so starts well
i can't see nothin wrong, the problem is not in vesa but in how kernel modules are loaded - unloaded