site  contact  subhomenews

New CLI Xorg Wizard

April 27, 2013 — BarryK
After many days with my nose down, there has emerged a new script, /usr/sbin/xorgwizard-cli. I previously reported that I was working on this:

This is an attempt to fix some problems that I experience with the previous text-mode Wizard. This new one is a complete rewrite, and has a different way of "going about it".

So far I have only tested on my laptop, which is a particularly difficult case, as it has hybrid graphics, Intel and NVIDIA video hardware on the motherboard.
The default behaviour is the kernel loads both the 'i915' and 'nouveau' modules, which require KMS. However, this prevents the 'vesa' driver from working, in case I had wanted to use that.
The new script should fix that kind of problem.

If anyone wants to try it, please do -- especially if you want to dig into the script and fix any problems! It is committed to the online Woof repository, and you also have to get the latest /root/.profile and /usr/sbin/xorgwizard.

Woof commit:

Note, I was uncertain how much effort that I should put into this, as it is not known what the future holds for Xorg. Perhaps Wayland will move in? Maybe Mir will get to a usable status?


xorgwizard testing
Username: pemasu
Upup Raring with 3.8.7 kernel and jwm-733. xorgwizard and xorgwizard-cli creates working xorg.conf. Does not cause hanging anymore after restart X due to usable xorg.conf. I changed in BIOS to use discrete ATI graphics. Radeon driver in use. The synaptics wasnt enabled and wasnt able to edit xorg.conf yet so that synaptics would have been in use. something prevents to be loaded. Otherwise was ok. I will test what happens with intel graphics and with synaptics next... I used Ubuntu Raring packages of today.

abandoning Xorg ship
Username: technosaurus
"From what I can tell the xfbdev is just as good if not better than the Xorg counterpart and the kernel fb drivers are cross platform (Xvesa isn't) and easier to fix (there are more framebuffer examples and the examples are better than Xorg's) and would even be relatively simple to port to no longer use libX11 components (only xcb). The one thing holding back the fb version is the clunky vga=ask menu, but it would be straight forward to add a vga=max parameter (suitable for most users) by tweaking linux-X.X/arch/x86/boot/video.c I am actually planning to do this to try and eliminate libX11 and since there is no existing toolkit for xcb, I'll be creating an immediate mode gui toolkit on top of netsurf's framebuffer (which has linux-fb, xcb, wayland and sdl backends)

Re xorgwizard-cli
Username: BarryK
"technosaurus, Interesting thoughts. pemasu, I also have only testing in Raring Puppy, which has xorg-server version 1.13.0. I don't yet know how well it will work with older xorg servers.

Re synaptics
Username: BarryK
"Synaptics support added. Woof commit:

OT cd for sale notice
Username: scsijon
"just came across a line at bottom of the page, take it you still want to know when we come across them. regards scsijon

Re CD for sale
Username: BarryK
"scsijon, Thanks, I removed that text. left in /root
Username: pemasu
"Feedback of the new xorgwizard: [code][/code] There seems to be leftover remnant in /root. Cosmetic thing mainly. Also question about driver selectivity from /usr/lib/x alternate location. I cant test. I dont have nvidia graphics at all. Synaptics touchpad started to work. Thanks.

better link for xorgwizard
Username: pemasu
"Sorry. Wrong tag:

dialog error Lupu 511
Username: K Godt
"Have tested this new xorgwizard and fixed the lines that mwould prevent it to run in Lupu . Also added shinobar's keymap-set, which is not included in my Lupu though the data matches ( *2010* ) . [quote] [ ... ] echo 'exit $?' >> /tmp/ chmod 755 /tmp/ ###DEBUG /tmp/ 2>/root/ exit ##DEBUG ----> Error: Expected at least 6 tokens for --menu, have 4. Use --help to list options. [/quote]

Xorg -configure segfaults
Username: K Godt
"Found the problem : Xorg -configure segfaults with not creating /root/ and /tmp/xorgwizard-driverlist0 is empty . /tmp/xorgprobe.txt : [quote] X.Org X Server 1.7.6 Release Date: 2010-03-17 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-25-server i686 Ubuntu Current Operating System: Linux puppy_luci_218 #9 SMP PREEMPT Fri Mar 25 03:44:43 GMT-8 2011 i686 Kernel command line: panic=56 root=/dev/sdb6 ro vga=normal panic=30 log_buf_len=512k printk.time=1 Build Date: 23 April 2010 05:11:50PM xorg-server 2:1.7.6-2ubuntu7 (Bryce Harrington <>) [ ... ] Backtrace: 0: Xorg (xorg_backtrace+0x3b) [0x80e937b] 1: Xorg (0x8048000+0x61c7d) [0x80a9c7d] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb78d0410] 3: Xorg (xf86CallDriverProbe+0x182) [0x80b82c2] 4: Xorg (DoConfigure+0x1c8) [0x816b8d8] 5: Xorg (InitOutput+0x1da) [0x80b989a] 6: Xorg (0x8048000+0x1ebbb) [0x8066bbb] 7: /lib/ (__libc_start_main+0xe6) [0xb7629bc6] 8: Xorg (0x8048000+0x1e961) [0x8066961] Segmentation fault at address (nil) [/quote] Last part of my /etc/X11/xorg.conf : [quote] #everything past here is auto-generated by Puppy's Xorg Wizard... #PuppyHardwareProfile=Intel_r_Q33_Q35_G33_Graphics_ChipS22B300 [/quote] Funny, that xinit is able to fire up X though :happy:
Username: BarryK
"pemasu, Thanks, added a line to remove it.

xorg alternate driver location
Username: BarryK
"pemasu, The script xorgwizard-cli has this: [code]#during woof build, may have put some drivers here... cp -a -f --remove-destination /usr/lib/x/drivers-alternate/* /usr/lib/xorg/modules/drivers/ 2> /dev/null rm -f /usr/lib/x/drivers-alternate/* 2> /dev/null [/code] Because I don't know if we need that mechanism anymore. Perhaps it is still useful for the automatic startup of X, but if a user needs to run the text-mode xorgwizard-cli then it runs "Xorg -configure" which detects all drivers that may be suitable for that video hardware -- and I think it best if all drivers are present, i.e. none in the alternate-drivers folder. Then the Wizard lists the found suitable drivers, and the user chooses which one to use. However, I am not certain. Have only tested on my laptop, with hybrid Intel and NVIDIA graphics, and the -configure only offered: intel nouveau vesa didn't offer 'nv'. Which is strange. Why not? It would seem to indicate that the -configure is partial to ignoring nv if nouvea is present. But, we need other testers who have NVIDIA graphics.

Is rebooting needed??
Username: don570
"re: xorgwizard-cli On my IBM desktop with intel graphics chip, I chose 'Intel driver,needs KMS(requires reboot)' but is the reboot required?? I was able to get to the desktop, then the machine went black screen after a few minutes. I go through the steps on Pemasu's Raring thread Perhaps you can get rid of that 'reboot' step in the procedure.

Stipulating driver and resolution
Username: zygo
"Does this wizard allow one to tell xorg the driver and resolution and not to probe? 3 posts starting at

No probe
Username: BarryK
"zygo, Yes.

Tags: woof