There's one serious problem though, CTRL-ALT-BACKSPACE is disabled. I ran into this when testing the video mode in the Xorg Wizard, and was unable to get out of the test screen. We use CTRL-ALT-BACKSPACE as the "OK" button sometimes causes the PC to hang -- which it did on my laptop. I was able to choose the video mode and it worked without testing. On the Puppy desktop, CTRL-ALT-BACKSPACE is still disabled.
Oh dear. I had read recently that Fedora had done this, and I made a mental note to stay away from Fedora. But it is more widespread... I hope that it was not a decision made by the Xorg developers. Anyway, what to do? We need that key combination.
Ok, I found out. Yes, it's the Xorg developers. Fortunately it can turned on in xorg.conf:
This is what I have to put into xorg.conf:
Option "DontZap" "false"
Comments:Posted on 13 Apr 2009, 13:02 by BarryK
There is still a problem though. I can put that fix into /etc/X11/xorg.conf, which is fine when the desktop is running, but the first time I hit this problem was in the Wizard doing a test screen, and I don't recall what config file that uses.
Anyway, Jaunty is looking good, and I'll post a progress report, and some thoughts/suggestions about Puppy5, probably tomorrow.
Approaching time for an alpha4 also.
Posted on 13 Apr 2009, 14:13 by Sage
As I've said on several occasions,
CTRL-ALT-BACKSPACE does NOT work in Puppy for old (but not that old) SiS chipsets - causes an immediate, hard shutdown, including the PSU, which cannot be achieved by the usual means unless acpi=force is present. On the other hand, all other distros, including F1 ...F10 do behave correctly on SiS chipsets with CTRL-ALT-BACKSPACE, so it would appear that is rather more to this tale?
Posted on 13 Apr 2009, 15:28 by 01micko
I have 2 AMD machines running SiS chipsets, one circa 2006 the other circa 1999. No probs with ctrl-alt-backspace in any puppy so far, perhaps it is a SiS/Untel combo giving the problem?
Posted on 13 Apr 2009, 15:40 by Sage
735 - the most popular and widest distributed ever, 748 - just about the best I've ever encountered and also extremely popular.
761/965 combo (for 64 bit) - no issues with Puppy.
Posted on 13 Apr 2009, 18:04 by BarryK
Testing X in the Wizard
Ah yes, I've just looked at the 'xorgwizard' script and refreshed my memory. Xorg is first run like this:
which probes the system and exits, writing an auto-generated file to /root/xorg.conf.new.
The Wizard reads this and composes the rest of /etc/X11/xorg.conf, then the script runs 'Xorg' without any parameters, which will be using /etc/X11/xorg.conf. Meaning, putting the fix into the beginning of that file will work for the test screen.
...this is something that Dougal will be familiar with, as he wrote big chunks of the code in the Xorg Wizard.
Posted on 13 Apr 2009, 18:05 by greenpossum
Isn't it the case that you just have to hit C-A-BS twice within a second to zap the X server with the Xorg patch? I think it's a good thing in real use (but maybe not during configuration) because once in a while your finger or brain will slip and instead of C-A-something you get C-A-BS and it's goodbye X session.
Posted on 13 Apr 2009, 20:07 by smil99
jaunty-pup test drive
"It wasn't too painful upgrading Woof and I now have a working Jaunty-pup."
Is it possible to have a test drive of jaunty-pup? Thanks.
Posted on 13 Apr 2009, 21:09 by BarryK
Yes indeed, coming real soon.
I didn't know that you had to do it in rapid succession. I do know that we had some cases where it had to be done twice, but I don't recall it having to be done rapidly.
Anyway, see my next post, problem solved.