-
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
IBM x3650 M3, 7945-AC1, 40GB, XEON e5507, 2.26ghz x2 with RAID Card, No HDD
$249.00
IBM 46D2516 4 Pack SAS/SATA EXPANSION KIT x3650 M2 (No server frontplate)
$129.00
IBM System x3650 M4 Server, 2 x Xeon E5-2609 2.4Ghz, 32GB RAM, 2 x 1.2TB SAS HDD
$118.49
IBM Lenovo X3650 M5 2U 8x 2.5” CTO Rack Server – 2x HS, 2x 750W
$199.00
ibm xseries eserver 306 1U Rack Server - 1x Intel Pentium 4 3.40 GHz - 512 Ram
$300.00
IBM S822LC 8335-GCA Power 8 2U Server 2xPower8 TESTED
$695.00
Lenovo x3550 M5 Server - 180Gb SSD/3x300Gb SAS, 64GB Ram, 2x 8c CPUs, Proxmox
$240.00
IBM x3650 M4 Dual 2x Xeon E5-2650 v2 2.6GHz 128Gb M5110e 2PSU Server 7915-AC1
$199.98
IBM P5 9115-505 2-Bay Server System Power5+ Core DVD-Rom 2GB No HDD For Parts
$249.99
IBM 44M1501 BladeCenter JS12 Blade Server with 2-Way 3.8GHz PS701/702
$172.50