-
no3d cheat parameter gets in an endless loop of starting X with Knoppix 8.2
I usually use knoppix with the no3d boot parameter, like "knoppix64 no3d noscreensaver" but I've noticed with 8.2 it will go into a endless cycle of trying to start X, failing and trying again.
If I don't use no3d, everything is fine.
I thought no3d would just disable compiz.
-
Same observation here on laptop with Intel Haswell and desktop with nvidia GT218.
Funny observation: on VirtualBox virtual machine with 16 MB video memory and no 3D acceleration, booting with cmdline "knoppix64 keyboard=dk" works fine, starting X without compiz. It seems that if Knoppix 8.2 is allowed to detect that the machine has too little graphics resources to run compiz, it starts X with window manager openbox-lxde just fine. However, when I boot the same VM with cmdline "knoppix64 keyboard=dk no3d" it fails to start X and enters the endless cycle of failing.
-
Junior Member
registered user
no3d changes "something" more ...
fortunately 8.3 has ( undocumented ? ) nocompiz bootparameter
it gets parsed by /etc/X11/Xsession.d/45knoppix
however the "no3d" bug making x unstartable should be investigated ...
the error message with no3d is:
[ 40.424] vesa: Ignoring device with a bound kernel driver
Code:
[ 40.404] (II) LoadModule: "vesa"
[ 40.404] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 40.404] (II) Module vesa: vendor="X.Org Foundation"
[ 40.404] compiled for 1.19.0, module version = 2.3.4
[ 40.404] Module class: X.Org Video Driver
[ 40.404] ABI class: X.Org Video Driver, version 23.0
[ 40.404] (II) VESA: driver for VESA chipsets: vesa
[ 40.424] vesa: Ignoring device with a bound kernel driver
[ 40.424] (WW) Falling back to old probe method for vesa
[ 40.424] (EE) Screen 0 deleted because of no matching config section.
[ 40.424] (II) UnloadModule: "vesa"
[ 40.424] (EE) Device(s) detected, but none match those in the config file.
the difference in xorg.conf is as follows:
Code:
knoppix@Microknoppix:~$ diff xorg.conf-mit-nocompiz xorg.conf-mit-no3d
66c66
< Option "Composite" "Enable"
---
> Option "Composite" "Disable"
99c99,100
< # Driver (chipset) autodetect
---
> # Specified driver (chipset)
> Driver "vesa"
who knows why the kernel already allocated the device so vesa cancels itself ?
why at all nod3 writes vesa in the config ?
the followin scripts are also part of configuring x11 :
/sbin/hwsetup
/sbin/mkxorgconfig
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Supermicro 4U 36 Bay Storage Server 2.2Ghz 16-C 128GB 1x1280W Rails TrueNAS ZFS
$725.06
CSE-118 Supermicro 1U GPU Server 2.6Ghz 28-C 128GB 2x Nvidia K40 GPU 2x1600W PSU
$580.03
Dell PowerEdge R630 8SFF 2.6Ghz 20-Core 128GB Mem 2x10G+2x1G NIC 2x750W PSU
$399.04
Dell R730xd 12LFF 2.6Ghz 20-C 128GB H730 2x10G+2x1G NIC 2x1100W 12x Trays Rails
$721.05
Intel Xeon E5-2680 v4 2.4GHz 35MB 14-Core 120W LGA2011-3 SR2N7
$17.99
Intel Xeon Gold 6140 SR3AX 2.3GHz 18-Core Processor CPU
$44.99
Intel Xeon E5-2697 v2 2.7GHz 30M 12-Core LGA2011 CPU Processor SR19H
$27.99
HP Z4G4 Intel Xeon W2133-3.6 GHz, 256 NVME, 6TB HDD, 32GB RAM P620 NO OS
$265.00
HP ProLiant DL380 Gen9 16SFF 2x E5-2680v4 2.4GHz =28 Cores 64GB P840 4xRJ45
$353.00
DELL PowerEdge R730 Server 2x E5-2690v3 2.6GHz =24 Cores 32GB H730 4xRJ45
$274.00