-
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
1TB/2TB USB 3.0 Flash Drive Thumb U Disk Memory Stick Pen PC Laptop Storage lot
$580.99
Type C USB 3.0 Flash Drive Thumb Drive Memory Stick for PC Laptop 1TB 2TB lot
$73.29
Western Digital 1TB WD Blue SA510 SATA SSD Internal 2.5”/7mm Cased - WDS100T3B0A
$79.99
Samsung - 990 980 970 PRO & EVO 4TB 2TB 1 TB Internal PCle Gen 4x4 NVMe M.2SSD
$320.00
WD - Blue SN580 1TB Internal SSD PCIe Gen 4 x4 NVMe
$64.99
CISCO A03-D1TBSATA 1TB 7.2K 6G 2.5INCH SATA HDD
$9.00
Samsung - 870 EVO 1TB Internal SSD SATA
$99.99
1TB HDD/SSD 2.5" SATA Hard Drive for Laptop with Win 10/Win 11 Pro Pre-installed
$19.99
Seagate ST1000DX001 1TB 3.5" Desktop Hybrid SSHD Solid-State Hybrid Drive
$37.50
Internal HDD SATA 3.5" 250GB-2TB Hard Drive with Legacy Windows 11 Pro Installed
$29.15