Touchpad etc., fix for Xorg 7.6

This now running so beautifully on my laptop. I have fixed some things with the automatic setup of X.

When the user installs the Xorg 7.6 Mega Package, a message pops up to advise exit from X and run either "xorgwizard" or "xorgwizard-automatic", the latter recommended as first attempt.

I have fixed some things in xorgwizard-automatic and in /etc/x11/xorg.conf-auto-pc (that the Wizard reads for skeleton xorg.conf file). These are fixes in Woof.

Touchpad can be configured now, Flsynclient works.

I'm running with the Intel Xorg driver, at 1366x768. Regarding speed, I was earlier today playing with Fatdog64, and did some rough timings. Running Wary with Xorg 7.6, the timings are about the same. So, I can't see any difference in speed.

I have tentatively decided to name this enhanced Wary "Racy Puppy".

Next thing on the to-do list, I want to compile the most recent 2.6.x kernel to use with Racy, mostly because I want the 'nouveau' Xorg driver support (nVidia), which the 2.6.32 kernel doesn't have. I cannot yet go up to a 3.x kernel as there are some scripts in Puppy that are hard-coded to expect "2.6".

And, looking ahead, I will probably build Racy in Woof, all ready to go with Xorg 7.6 and recent kernel.


Posted on 13 Sep 2011, 17:38


Comments:

Posted on 13 Sep 2011, 20:17 by tronkel
Racy Wary
Can't wait to try this one! The name suggests real speed as a "marketing" angle.This will need a new default wallpaper with a dog wearing racing driving goggles,safety helmet plus leather gloves for his paws!

Any graphics artists up for this?


Posted on 13 Sep 2011, 21:27 by GCMartin
Racy Wary
Or, Racy could be like Ms Australia in swimsuit or evening gown, from last night's Ms Universe. Racy!

FATDOG vs Puppy
The real problem is that one would have to run a set of selected tools which exploits the system to really see the differences in the 2 OSes. This was a similar problem I had alluded to early on when PAE testing began. Many reported improvements, but, valid empirical data measurements are not used. We all understand the benefits, but, without tools producing data to reflect this, it becomes a little tough to reflect this.

But, in FATDOG versus Puppy, most notably has been the video performance. But, again, there no real data being presented that can be shown in comparison.

What you did comfirm, though, is that there is no apparent negative impact no matter which Puppy version you ran.

If anyone reading this knows of some existing method with data that can be used to compare performance of applications in 2 different platforms please share those ideas somewhere in the forum. Maybe we can develop a PUP standard for this very purpose.

Hope this helps
P.S. @BARRY, check your PM for one such tool.


Posted on 14 Sep 2011, 3:19 by kirk
re: Fatdog64 speed
If you're just surfing the web or using Abiword you won't see any difference. If you're encoding a big mpeg2 file to h264, then you'll see a 15-20 percent difference. Really only see a deference on processor intensive apps that can take advantage of the bigger registers or math functions. If you compiled your 32bit for a newer processor type that supports sse2, sse3 etc. Then the difference would be quite small. But there are so many 32bit cpus you end up having to pick a lowest denominator. I was wondering how Fatdog64 would work on your laptop with the two graphics cards. Did xorg come up ok?



Posted on 14 Sep 2011, 8:28 by BarryK
Re hybrid graphics
kirk,
Yes, it used the Intel GPU. Ditto with my Xorg 7.6.

The Wary with Xorg 7.3 is very confused by the two GPUs, but 'vesa' works.

So it seems that the Xorg server has become aware of these hybrid systems.

Note, my Xorg 7.6 is still using /etc/X11/xorg.conf, even when the automatic Xorg Wizard is used, albeit a cut-down one. The older 'kbd', 'mouse' drivers are being used. I do need to move toward freeing that up and let the Xorg server do more input-device probing of it's own, as you do in Fatdog64.



Posted on 14 Sep 2011, 8:45 by Raffy
Xorg setup a challenge
I'be been testing AMD Fusion (E350) emachines laptop (with Radeon 6xxx)* really to help Puppy become comfortable in the new 64-bit PCS (and AMD Fusion is the new platform of choice because of its GPU advantages - example, watch for tablets using the AMD Fusion in the next quarter or so).

However, new 64-bit and 32-bit puppies can't work Xorg out in this machine (they can't go past the "Probing" stage). This experiment is therefore timely.

* AMD Fusion Chips by TDP, cores and speed:
9w TDP: C-30 (1 core, 1Ghz), C-50 (2 cores, 1.2 Ghz) - Radeon 6250
18w TDP: E-240 (1 core, 1.5Ghz), E-350 (2 cores, 1.6 Ghz) - Radeon 6310


Posted on 14 Sep 2011, 9:56 by kirk
re: input-device
James got Xorg running without a xorg.conf for Fatdog64-520 so there's no xorg.conf at all by default. The input probing seems to work pretty well. If you plug in a Wacom tablet, it will just work. If you want to do it you'll need to recompile your xorg-server with --enable-config-udev. You'll also need your xorg.conf.d set up. It's in /usr/X11R7/lib64/X11/xorg.conf.d for Fatdog64. And you may have to update xkeyboard-config if you're still using a old one.


Posted on 14 Sep 2011, 13:16 by mavrothal
full udev
Including the full udev in puppies and prioritizing it over pup_event may solve a number of devices issues.
The size of it is not that much (less than 300k compressed) and by now is mature enough to handle almost everything.


Posted on 14 Sep 2011, 15:29 by Raffy
X loads then hangs
I should clarify that in the first boot, X loads successfully but hangs within the first 2 minutes (this happens in both Fatdog64 and Slacko beta, and the "nomodeset" as well as "vesa" boot parameters won't help). The Xorg setup is done only in the second boot with nox - that is when xorgwizard hangs at "Probing...".

I try to use the newer kernels because they have the wired and wireless drivers for this new machine.

This report is simply calling attention to an Xorg setup problem in a new class of machines (i.e., AMD Fusion E350 in a laptop, as no PC boards are available). Could it be an ACPI problem in this Acer/emachines D443 laptop given the newer Linux kernels? (The regular reporting of X problems in Toshiba laptops come to mind.)