-
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
HGST Ultrastar HE10 HUH721010ALE600 10TB SATA 6Gb/s 7200RPM 3.5" Enterprise HDD
$74.99
WD4000FYYZ Western Digital 4TB SATA 3.5 Hard Drive
$149.99
WF12F DELL 1TB 7.2K 6GBPS SATA 2.5'' HDD HARD DRIVE ST91000640NS 0WF12F
$25.00
Western Digital WD60PURZ 6TB Hard Drive SATA6 Gb/s 64MB Cache 3.5 Inch
$109.99
HGST Ultrastar DC HC520 12TB SATA 6Gb 256MB 3.5" Enterprise HDD- HUH721212ALE601
$82.99
Seagate Exos 7E10 ST2000NM000B 2TB 7200RPM SATA 6.0Gb/s 3.5" Internal Hard Drive
$29.99
2 PACK Seagate ST1000LM035 Mobile HDD 1TB 2.5" SATA III Laptop Hard Drive
$27.25
TOSHIBA MD04ABA400V 4TB 128MB Cache SATA 6. 0Gb/s 3. 5"
$18.00
Seagate ST12000NM0538 Exos X14 12TB 3.5" SATA 6Gbps 3.5" Enterprise Hard Drive
$45.96
HDD 3.5" SATA Hard Drive with Windows 7/Win 10 Installed Legacy
$28.99