Problem saving straight 5.3.3 version to DVD. Said it requires a new or updated DVD! UpupPrecise 5.3.3.x has divination capacity since, at approx. the same time I was trying to save, pemasu was presenting version 5.3.3.1... (hehe)

Back to serious: Will check if it is my DVD disk itself or some function in shutdown routine of PrecisePup that's involved.

JJim1911. Could you dmesg and check is it asking firmware which is missing. r8169 kernel module is there so it could be missing firmware. There is now 4 new firmwares in firmware git repository, so....it might be fixable by adding missing firmware.
dmesg tells you if it complains about spesific firmware.

This has been the case with recent Puppys, but have so far managed to work around the problem by compiling the proprietary driver from the ATI website.

I can't however seem to be able to get an error-free compile using this Upup. I'm using the kernel sources as provided by the sfs and the amd-driver-installer-12-3-x86.x86_64.run downloaded ATI driver.

The open source Radeon driver seems to be kaput in the latest kernels. This is the one I actually prefer.

Would any of the Slacko ATI FGLRX pets be of any use? Has anyone had any joy using any of these?

In the meantime the VESA driver allows me to have a GUI desktop.

It's enough to show the potential that this version has. Yes, I think this would make a great official Puppy.
It's got the necessary look and feel as well._________________Life is too short to spend it in front of a computer

I normally compile GKrellM but this time I used a deb I found. When I went to compile the weather plugin I got this result. No biggie for me but wanted to put my report in._________________Tahr Pup 6 on desktop, Lucid 3HD on lappie

I can't however seem to be able to get an error-free compile using this Upup. I'm using the kernel sources as provided by the sfs and the amd-driver-installer-12-3-x86.x86_64.run downloaded ATI driver.

kernel module source has needed patching with recent ATI versions and 3.2.X and over kernels. The patching has been posted recently in howto section.

Posted on 22 Apr 2012, 17:30 by maxerro barrys blog
I've just seen pemasu has uploaded a new version of Upup Precise, so MAYBE this is still relevant, like it has been just yesterday.
There still seems to be some library-backfiring in the crypto/ssl area, and before pemasu goes on, this needs to clear up:
backup /lib/libssl.so.0.9.8 to whatever (for now)
link /lib/libssl.so.1.0.0 to /lib/libssl.so.0.9.8
add libevent-openssl-2.0-5_2.0.16
link:
/usr/lib/libevent_openssl.so
/usr/lib/libevent_openssl-2.0.so.5
to the new /usr/lib/libevent_openssl-2.0.so.5.1.4 instead of 5.1.3
Test again, cry for help.
Although, by the final release the whole ssl-pack will need to be replaced.

This is bigger thing than first seems. Doing so...means that apps needing older 0.9.7-0.9.8 are not fooled with just symlinking. It means compiling them against libssl 1.0

Well...lefting 0.9.8 out surely soon shows what apps needs recompiling. I did compile Transmission-2.51 against libssl.so.1.0.

What else needs recompiling...someone could tell....

Libevent was the older version due to Transmision. Already updated it to use Precise Pangolin version and I did create symlinks to the older version. Will be in next uploaded Upup Precise.

Yes...but that means that you have both of them libssl 0.9.8 and 1.0 on your system. If there is concensus that only libssl 1.0, updated later to security updated version is the safe way....apps depending the libsll 0.9.8 is not fooled with just symlink. You will get version symbol error.

I had already 0.9.8 and 1.0 versions included, both of them...question is...is just 1.0 safer and better solution and how many apps relies on 0.9.8. I think this was discussed and updated in Lucid Puppy. Playdayz et al could answer this.

Yeah...I would need Playdayz as "silent" advicer in this...I suppose he will check this thread at some time...

JJim1911. Could you dmesg and check is it asking firmware which is missing. r8169 kernel module is there so it could be missing firmware. There is now 4 new firmwares in firmware git repository, so....it might be fixable by adding missing firmware.
dmesg tells you if it complains about spesific firmware.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum