Karmic Puppy uPup 4.58 w/ GLX/DRI - Latest Woof FEB 16
Hi guys and gals
It has been noted on the Pwidgets thread by Jim1911 that the latest version of Pwidgets-2.2.3 doesn't work in the latest Upup built by playdayz. In fact it not only doesn't work but trashes the current pupsave file, I don't know the consequences of installing the latest Pwidgets in a full install, but they are probably not good.
Attached is a package that I constructed that should fix the issue. I already sent this package to Jim but with consultation with zigbert (maintainer of Pwidgets) I decided that this package needs wider testing. He said to me that once the package is "fully tested" then to get back to him. Of course Jim cannot fully test this package on his own.
The package is designed to work in all puppies including any upup derived from woof. That does not mean it will work. Use with caution, that is, test with "pfix=ram" or back up your pupsave before installing. You are not confined to testing in upup, please feel free to test in any puppy you have but remain warned that you must back up your pupsave or use "puppy pfix=ram". For full installs, well try at your own risk.
I look forward to your feedback, good or bad, in particular yours playdayz and aarf.
Cheers
01micko
removed pet, try newer version
It has been noted on the Pwidgets thread by Jim1911 that the latest version of Pwidgets-2.2.3 doesn't work in the latest Upup built by playdayz. In fact it not only doesn't work but trashes the current pupsave file, I don't know the consequences of installing the latest Pwidgets in a full install, but they are probably not good.
Attached is a package that I constructed that should fix the issue. I already sent this package to Jim but with consultation with zigbert (maintainer of Pwidgets) I decided that this package needs wider testing. He said to me that once the package is "fully tested" then to get back to him. Of course Jim cannot fully test this package on his own.
The package is designed to work in all puppies including any upup derived from woof. That does not mean it will work. Use with caution, that is, test with "pfix=ram" or back up your pupsave before installing. You are not confined to testing in upup, please feel free to test in any puppy you have but remain warned that you must back up your pupsave or use "puppy pfix=ram". For full installs, well try at your own risk.
I look forward to your feedback, good or bad, in particular yours playdayz and aarf.
Cheers
01micko
removed pet, try newer version
Last edited by 01micko on Wed 27 Jan 2010, 20:35, edited 2 times in total.
Puppy Linux Blog - contact me for access
the shutdown immediately after the pwidgets_upup-2.0.8-1.pet install stalled at the last screen while saving pupsave, so hard shutdown and on reboot all seemed fine. however i don't know how good of a tester i will be because i still am not certain that any or which of my problems will come from a possible defective SDcard or defective SDcard reader. it is FAT file system so i don't know how to check it. also the read-only problems reported above are copping up elsewhere in the forum and they are not on SD cards so more uncertainty there.
with that said, in a pfix=ram, clicked on pwidgets-2.2.3-M.pet and it was the same as above with pwidgets-2.2.3.pet, no confirmation dialog and nothing happening. then tried to look in the package manager and all the menu items and desktop icons failed to open on clicking. rebooted, repeated and same again. I'd say pwidgets-2.2.3-M.pet is a no-go for upup456.
with that said, in a pfix=ram, clicked on pwidgets-2.2.3-M.pet and it was the same as above with pwidgets-2.2.3.pet, no confirmation dialog and nothing happening. then tried to look in the package manager and all the menu items and desktop icons failed to open on clicking. rebooted, repeated and same again. I'd say pwidgets-2.2.3-M.pet is a no-go for upup456.
Thanks for report aarf,
I made another attempt with a completely different conditional test in the pinstall.sh script.
Again same warnings apply, try "pfix=ram" or back up pupsave.
Cheers
pet removed , newer version works for me, tested on 456, see my post on next page for pwidgets that should work
I made another attempt with a completely different conditional test in the pinstall.sh script.
Again same warnings apply, try "pfix=ram" or back up pupsave.
Cheers
pet removed , newer version works for me, tested on 456, see my post on next page for pwidgets that should work
Last edited by 01micko on Wed 27 Jan 2010, 23:53, edited 1 time in total.
Puppy Linux Blog - contact me for access
There is a new build of Upup 4.57 From Woof 2010-0126
uPup 4.57 is built from the Woof posted by Barry K on JAN 26.
Jim1911, thanks for the suggestion about the secondary numbering. I tried it briefly before and I could not find anywhere where the secondary number actually showed up. I will experiment and see if it will upgrade, that is, if 4.57.01 will upgrade 4.57.00.
01micko, Good to hear from you. That is an admirable and worthy goal imo. but we should remember that under the hood upup can be very different from T2-based Puppies. You know all that of course, but, just for instance, the xorg files are in a different place in upup than in Puppy 4. My plate is pretty full at the moment--working on cups 1.4.1 about finished me Keeping up with the builds from Woof is my main priority. Whatever might be wonky with the Network Wizard is Job #1. It's great to see people trying to make Pwidgets work but I won't be able to do much myself. at the moment. When there is a version that works, I can put it with the tested software and possibly include it in the build--since it is a puppy after all.The package is designed to work in all puppies including any upup derived from woof. That does not mean it will work. Use with caution, that is, test with "pfix=ram" or back up your pupsave before installing. You are not confined to testing in upup, please feel free to test in any puppy you have but remain warned that you must back up your pupsave or use "puppy pfix=ram". For full installs, well try at your own risk.
I look forward to your feedback, good or bad, in particular yours playdayz and aarf.
Jim1911, thanks for the suggestion about the secondary numbering. I tried it briefly before and I could not find anywhere where the secondary number actually showed up. I will experiment and see if it will upgrade, that is, if 4.57.01 will upgrade 4.57.00.
Last edited by playdayz on Wed 27 Jan 2010, 22:48, edited 2 times in total.
Hi 01micko,
Sorry, pwidgets-2.2.3-M-v2.pet doesn't work either for me. With no save file, it doesn't complete the installation and clicking on any desktop icon gives no response. The menu is still available, however a restart X, just takes you to a black screen with an X showing and hangs up.
Identical results with upup 4.57.
Take care,
Jim
Sorry, pwidgets-2.2.3-M-v2.pet doesn't work either for me. With no save file, it doesn't complete the installation and clicking on any desktop icon gives no response. The menu is still available, however a restart X, just takes you to a black screen with an X showing and hangs up.
Identical results with upup 4.57.
Take care,
Jim
Just did a fresh frugal install of 457 with a new savefile.
Onboard intel 810 graphics.......GLX/DRI working.Driver info below....
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "intel" #card0driver
VendorName "Intel Corporation"
BoardName "82810E DC-133 (CGC) Chipset Graphics Controller"
BusID "PCI:0:1:0"
EndSection
Onboard intel 810 graphics.......GLX/DRI working.Driver info below....
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "intel" #card0driver
VendorName "Intel Corporation"
BoardName "82810E DC-133 (CGC) Chipset Graphics Controller"
BusID "PCI:0:1:0"
EndSection
Ok guys,
Third time lucky for my Pwidgets package.
As usual test with "pfix=ram" or backup your pupsave. Use at own risk on full installs.
Works for me using "pfix=ram" on upup 456.
Thanks for feedback so far, please continue to give feedback. Remember, you can test on any puppy, not just upup.
Cheers
01micko
Third time lucky for my Pwidgets package.
As usual test with "pfix=ram" or backup your pupsave. Use at own risk on full installs.
Works for me using "pfix=ram" on upup 456.
Thanks for feedback so far, please continue to give feedback. Remember, you can test on any puppy, not just upup.
Cheers
01micko
- Attachments
-
- pwidgets-working.jpg
- (43.43 KiB) Downloaded 1286 times
Puppy Linux Blog - contact me for access
Hi playdayz
You can see in my above screeny that xorg doesn't like my wide-screen, in xorg.conf the 'vesa' driver is loaded. My card is the radeon 9200pro, quite an old one, but it works well in dpup and standard pup and also quirky. The driver normally loaded is 'radeon'. I tried to edit xorg.conf inserting radeon but xorg won't start. The only driver seeming to work is vesa.
I have played with ubuntu, mandriva-live and crunch-bang and none of them load the 'radeon' driver and if I load it manually all apps have huge unusable fonts, I mean like about 200px for a lower case char! Must use vesa.
I don't know if there is a simple solution, I've searched around but there isn't much info.
I am open to suggestions
Cheers
EDIT: just got 457, same xorg result
You can see in my above screeny that xorg doesn't like my wide-screen, in xorg.conf the 'vesa' driver is loaded. My card is the radeon 9200pro, quite an old one, but it works well in dpup and standard pup and also quirky. The driver normally loaded is 'radeon'. I tried to edit xorg.conf inserting radeon but xorg won't start. The only driver seeming to work is vesa.
I have played with ubuntu, mandriva-live and crunch-bang and none of them load the 'radeon' driver and if I load it manually all apps have huge unusable fonts, I mean like about 200px for a lower case char! Must use vesa.
I don't know if there is a simple solution, I've searched around but there isn't much info.
I am open to suggestions
Cheers
EDIT: just got 457, same xorg result
Last edited by 01micko on Thu 28 Jan 2010, 02:23, edited 1 time in total.
Puppy Linux Blog - contact me for access
Great news Jim!
Only need confirmation from a couple of others then zigbert will be satisfied and we can have a unified Pwidgets for all Puppies.
Cheers
Only need confirmation from a couple of others then zigbert will be satisfied and we can have a unified Pwidgets for all Puppies.
Cheers
Puppy Linux Blog - contact me for access
Hi playdayz,
Upup 4.57 is looking good, everything is running fine on my hardware. You just keep improving it.
Great,
Jim
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart 5280 All-in-One
Upup 4.57 is looking good, everything is running fine on my hardware. You just keep improving it.
Great,
Jim
System: BFG NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart 5280 All-in-One
pwidgets-2.2.3-M-v3.pet, pfix=ram, upup456.
get confirmation dialog and proceeded to edit widgets. got this error message (below) ended up with this screen (below)
in Wallpaper Setter I reset the desktop image and briefly got a pop-up error saying "pwidgets unnamed label".
however all seems to be functioning including desktop image.. will install it in prime time when i update to upup457.
get confirmation dialog and proceeded to edit widgets. got this error message (below) ended up with this screen (below)
in Wallpaper Setter I reset the desktop image and briefly got a pop-up error saying "pwidgets unnamed label".
however all seems to be functioning including desktop image.. will install it in prime time when i update to upup457.
- Attachments
-
- widgets.error.jpg
- (35.2 KiB) Downloaded 1253 times
-
- screen.widgets.jpg
- (28.2 KiB) Downloaded 1245 times
Thanks for report aarf.
What you saw is a conflict in the wallpaper setter. Should be ok once you reset the wallpaper, really nothing to do with the repackaging, so I will refer that one to zigbert.
I view this as a positive result.
Cheers
What you saw is a conflict in the wallpaper setter. Should be ok once you reset the wallpaper, really nothing to do with the repackaging, so I will refer that one to zigbert.
I view this as a positive result.
Cheers
Puppy Linux Blog - contact me for access
01micko and aarf and jim1911, wow guys, nice work. Puppy Solidarity.
01micko, Those distros you mention, ubntu, mandriva, etc, are using xorg <correction> 7.4, I think. I am not sure what Quirky is using--this uPup is taking all my time I was wondering if the radeonhd driver would work. It might be worth a try. This computer I am on, I remember that in one version, maybe New Years Pup, but around that time, this computer would use the radeon driver but now it uses the radeonhd in uPup.
Another possibility if you feel like experimenting--I was able to compile the ATI Catalyst Control Center and drivers using SHS's devx enhancement (listed in software on first page of thread). That provides the proprietary fglrx driver. Of course, what we want ultimately is all video cards to be correctly installed. Oh wait, the vesa driver has the wide screen resolutions now I have seen, plus it I have also seen that it works with glx/dri--if you have the correct resolution with glx/dri working maybe that is as good as it will get without the proprietary driver??? I will look again but I am not seeing the video problem in the screenshot.
01micko, Those distros you mention, ubntu, mandriva, etc, are using xorg <correction> 7.4, I think. I am not sure what Quirky is using--this uPup is taking all my time I was wondering if the radeonhd driver would work. It might be worth a try. This computer I am on, I remember that in one version, maybe New Years Pup, but around that time, this computer would use the radeon driver but now it uses the radeonhd in uPup.
Another possibility if you feel like experimenting--I was able to compile the ATI Catalyst Control Center and drivers using SHS's devx enhancement (listed in software on first page of thread). That provides the proprietary fglrx driver. Of course, what we want ultimately is all video cards to be correctly installed. Oh wait, the vesa driver has the wide screen resolutions now I have seen, plus it I have also seen that it works with glx/dri--if you have the correct resolution with glx/dri working maybe that is as good as it will get without the proprietary driver??? I will look again but I am not seeing the video problem in the screenshot.
Last edited by playdayz on Tue 16 Feb 2010, 17:36, edited 1 time in total.
Yes, it looks ok, but I have a widescreen , it doesn't translate in the screeny, but I am seeing everything w-i-d-e-rI will look again but I am not seeing the video problem in the screenshot.
I will give the radeonhd driver a go and try some things and still search for a solution.
Cheers
Puppy Linux Blog - contact me for access
simple and easy except if you have two .iso on a FAT partition and want to calculate the difference delta, you will get
xdelta for 456-457 is just over 9MB.
because the output file has a : in the name and FAT doesn't like :'s in file names. simple upgrade of xdelta would fix this.ERROR! failed to generate the .delta file. Error message:
xdelta3: file open failed: write: /mnt/sdc1/upup456/upup-456.iso:upup-457.iso.delta: Invalid argument
xdelta for 456-457 is just over 9MB.
01micko, I am sorry; I was misremembering this. I checked and the xorg vesa driver will indeed use glx/dri, which is good, but it will not do widescreen, as you know. The xvesa server will do 1400x900 or whatever, but not 1680x1050 and it will not do glx/dri so it is no good for what we want. As you already knew, we need a driver that will do your video properly, widescreen with glx/dri. Sorry again for the misdirection. Is xorgwizard choosing the vesa driver? I have found that the Ubuntu setup was trying to use the fbdev driver when Puppy would usually use vesa, but that fbdev was working for nobody so I took it out. Man, doesn't it seem like one of the regular radeon or radeonhd driver should work. There is also an ati driver but I thought that was for really old hardware.Oh wait, the vesa driver has the wide screen resolutions now I have seen, plus it I have also seen that it works with glx/dri--if you have the correct resolution with glx/dri working maybe that is as good as it will get without the proprietary driver??? I will look again but I am not seeing the video problem in the screenshot.
Hi playdayz
Still trying to get the card going.. I downloaded ati- catylist from AMD and it compiled and installed fine with only the kernel source and standard devx, I got excited but then deflated.. I ran "aticonfig" only to get the error "aticonfig: No supported adapters detected"... bummer .
I won't give up... there will be a way, somehow...
Earlier I tried an older package from AMD which supports the Radeon 9200 series, it was an RPM, it installed but it is too old, it was built for xorg 6.8... that was a long time ago... got all sorts of kernel errors, not really unexpected.. ah well.
Still trying to get the card going.. I downloaded ati- catylist from AMD and it compiled and installed fine with only the kernel source and standard devx, I got excited but then deflated.. I ran "aticonfig" only to get the error "aticonfig: No supported adapters detected"... bummer .
I won't give up... there will be a way, somehow...
Earlier I tried an older package from AMD which supports the Radeon 9200 series, it was an RPM, it installed but it is too old, it was built for xorg 6.8... that was a long time ago... got all sorts of kernel errors, not really unexpected.. ah well.
Puppy Linux Blog - contact me for access
playdayz... great news..
I now have my widescreen working and the "radeon" driver loading. All it was was a missing library.. libdrm_radeon.so.1. I found it out in the xorg errors file in /tmp. Also missing is "glide" but I didn't bother with that. The lib was not the easiest to find and probably not the best possible way I did it.. quite dirty in fact so it remains to be seen if everything is solid and stable.
What i did was download a Fedora version of libdrm.. it includes others for nvidia and so on.. I installed the lot after I unrpmed it, but if you want to include it in the Upup 478 iso I would just include the libdrm_radeon.so.1.. can't do any harm.
Here is the link where I got the rpm... http://rpm.pbone.net/index.php3/stat/3/ ... adeon.so.1
NOTE: I used the i586 Fedora 11 version.. I figured it would be closest in kernel and xorg version.
I wouldn't blame you if you didn't want to use this, a deb would possibly be better, but I couldn't find one.. perhaps just a .pet with the lib would do.. save spoiling the iso... and a warning, however seems ok to me, but like I implied.. early days yet. I will test vigorously over the coming days with games videos etc, throw whatever I can at it..
Cheers
I now have my widescreen working and the "radeon" driver loading. All it was was a missing library.. libdrm_radeon.so.1. I found it out in the xorg errors file in /tmp. Also missing is "glide" but I didn't bother with that. The lib was not the easiest to find and probably not the best possible way I did it.. quite dirty in fact so it remains to be seen if everything is solid and stable.
What i did was download a Fedora version of libdrm.. it includes others for nvidia and so on.. I installed the lot after I unrpmed it, but if you want to include it in the Upup 478 iso I would just include the libdrm_radeon.so.1.. can't do any harm.
Here is the link where I got the rpm... http://rpm.pbone.net/index.php3/stat/3/ ... adeon.so.1
NOTE: I used the i586 Fedora 11 version.. I figured it would be closest in kernel and xorg version.
I wouldn't blame you if you didn't want to use this, a deb would possibly be better, but I couldn't find one.. perhaps just a .pet with the lib would do.. save spoiling the iso... and a warning, however seems ok to me, but like I implied.. early days yet. I will test vigorously over the coming days with games videos etc, throw whatever I can at it..
Cheers
- Attachments
-
- success.png
- (193.32 KiB) Downloaded 1142 times
Puppy Linux Blog - contact me for access