Woof uploaded, April 16, 2010

This is the Woof that I have used for my first build of Ubuntu "Lucid Puppy".

It seems to be basically working, except something is amiss with the Xorg Wizard. It seems that the probe is not writing a xorg.conf.new file. An /etc/X11/xorg.conf is still created, but it is only the original skeleton xorg.conf0 with the "hardware profile" appended. X still works with that skeleton.

That being the case, you could give it a go to remove the Wizard entirely. Change /usr/sbin/xorgwizard to just this:


cp -f /etc/X11/xorg.conf0 /etc/X11/xorg.conf
echo '' >> /etc/X11/xorg.conf

ddcprobe >/tmp/ddcprobe.txt
#weird (ddcprobe is very weird), on some hardware, edid monitor probe fails
#every alternate run of ddcprobe...
case "`cat /tmp/ddcprobe.txt`" in *edidfail*)
sleep 1
ddcprobe >/tmp/ddcprobe.txt

PROFILECHIP="`grep -m1 '^oem: ' /tmp/ddcprobe.txt | cut -f 2-4 -d ' ' | tr ' ' '_' | sed -e 's/[^0-9a-zA-Z]/_/g'`"
PROFILEMONITOR="`grep '^monitorid: ' /tmp/ddcprobe.txt | head -n 1 | cut -f 2 -d ':' | tr -d ' ' | sed -e 's/[^0-9a-zA-Z]/_/g'`"
[ "$PROFILEMONITOR" = "" ] && PROFILEMONITOR="`grep '^monitorname: ' /tmp/ddcprobe.txt | head -n 1 | cut -f 2 -d ':' | tr -d ' ' | sed -e 's/[^0-9a-zA-Z]/_/g'`"
[ "$PROFILEMONITOR" = "" ] && PROFILEMONITOR="`grep '^monitorrange: ' /tmp/ddcprobe.txt | head -n 1 | cut -f 2 -d ':' | tr -d ' ' | sed -e 's/[^0-9a-zA-Z]/_/g'`"
[ "$PROFILEMONITOR" = "" ] && PROFILEMONITOR="`grep '^manufacture: ' /tmp/ddcprobe.txt | tail -n 1 | cut -f 2 -d ':' | tr -d ' ' | sed -e 's/[^0-9a-zA-Z]/_/g'`"

echo "#PuppyHardwareProfile=${PROFILECHIP}${PROFILEMONITOR}" >> /etc/X11/xorg.conf
#create a copy of xorg.conf with the profile in the filename...
cp -af /etc/X11/xorg.conf /etc/X11/xorg.conf.${PROFILECHIP}${PROFILEMONITOR}

I have run out of time to work on the Lucid Pup build. Over to playdayz.

About Woof: http://bkhome.org/woof/

Posted on 16 Apr 2010, 13:53


Posted on 16 Apr 2010, 21:26 by BarryK
Woof re-uploaded
I have reuploaded Woof, because of this:


Posted on 17 Apr 2010, 7:51 by playdayz
The last Woof
I have not had that problem with xorgwizard Barry--and I don't want it ;-) This is the last Woof i will use before the release. Usually I go through the new Woof line by line so that I keep my customizations as well as your new features, but this time I think I will just replace all of my files--I might miss a few of your fixes, but it is time to start tightening the bolts for Mayday. And if there are big problems then I will probably go back to the last Woof.

Something I have noticed is that I have been updating from the Ubuntu repos every couple of days rather than trying to do it all at once. I made a big update with three weeks worth of changes and it broke things--the smaller updates have been working well. I wonder, will they keep updating as they prepare for release--boy I hope so because if so I will not need to do any big download/update when they release Lucid, just a few more files.

Posted on 18 Apr 2010, 2:06 by Dougal
I don't know about xorg.conf.new not being created, but a while ago Xorg was changed so it doesn't need a xorg.conf anymore... it is supposed to autodetect things when you start it and the xorg.conf just used to override it.

Posted on 18 Apr 2010, 24:38 by playdayz
weird xorg.conf
An /etc/X11/xorg.conf is still created, but it is only the original skeleton xorg.conf0 with the "hardware profile" appended. X still works with that skeleton.

Yikes. 006 is OK, but 007 does what you say--the only difference I have done is download the Ubuntu updates. I did *not* use the new Woof of 4/16 because something went wrong with the woof-user-modified and the only thing in there was /support. I have a hard time thinking of this as a new feature. I have seen what the xorg.conf looks like when it is automatically configured and it doesn't look like this. But I guess that could be it--it is running somehow. Back to the drawing board.

Posted on 19 Apr 2010, 3:50 by playdayz
The problem is in the packages that make up xserver-xorg. I backed up and updated one by one. The xorg-base packages were OK but the problem appeared when I updated the xserver-xorg packages.

Posted on 19 Apr 2010, 6:04 by playdayz
There are two files in the 006 xerver-xorg package that are not in the 007 package

If I put those files into 007 then xorgwizard works properly on my radeon 3850. However, that is not the whole story, because even with the two files in 007, xorgwizard does not work properly on my Nvida 5200--even if I create a file named nv_kms.conf with the same content as the other two (options i915 modeset=1) changing the i915 to nv of course.

Since 006 works correctly, I ma going to its xerver-xorg package for 007, and then investigate ubuntu graphics in more detail. Partly the problem might be overlaying Ubuntu style graphics with Puppy style--it might be better to go all the way, one way or the other.I would be obliged if anyone sees a significant pattern. Thanks.

Posted on 22 Apr 2010, 7:55 by technosaurus
single file puppies
I wondered how xpud made their single file distro so I tracked down the build scripts.

They seem to be set up very similar to woof and incorporate a lot of the stuff you have mentioned about quirky... just with a narrower focus (only ubuntu and only a browser & media player)

In case you don't want to reinvent the wheel when you build your single file puppies/quirky, here is the link.

oh, wait wrong link... this kind of single file puppies: