Cups is working again--it was at least partially broken in 4.56 and 4.57 but I didn't catch it until testing for 4.58.

The fix for "Rox Select" is working. The problem was that a file would stay selected until one clicked in the white space of the Rox window. IMHO that was a serious problem because several times I accidentally deleted the wrong file because the old one stayed selected. There was a fix in /etc/profile but it did not work and it caused a problem with opening Terminal. I used the code instead that aarf posted on page 8 of this thread and it seems to work perfectly.

As per 01micko's discovery, libdrm-radeon1 is present. I know it is doing something because my driver changed from radeonhd to radeon with libdrm-radeon present. I am sure someone understands that.

I am going to write up my work method and test method and post it here tonight or tomorrow, just in case it is useful to anyone. I have a test suite now of 4 different video cards, radeon, nvidia, intel and S3 (and all 4 work with glx/dri). Here are the notes -> http://www.diddywahdiddy.net/Puppy400/Making_uPup.rtf

The latest Pwidgets 2.2.4 worked but it caused the problem with the backdrop that was mentioned. I know that is a "good sign" but I prefer to wait to install it by default until it doesn't have that feature. I will put a link in to Pwidgets in the software links below.

Misson Statement: To track the Karmic Puppy build in Woof, to find and if possible solve problems, to report back to Barry and maintainers of software, to make a useful Linux desktop with Puppy style and speed and Ubuntu binaries. I hope Karmic Puppy works for you. Thanks for trying it.

Download devx -> http://www.diddywahdiddy.net/Puppy400/upup_devx_458.sfs
devx_458 md5sum -> f1abc93245792ada6e37eb7c3de33148
Download the upup_devx_458.sfs and place it into /mnt/home. Then check Menu -> System -> System Schedule -> Bootmanager config bootup to make sure the devx will be loaded at startup. I keep devx installed on any semi-permanent installations because there are at least two programs that run better (or at all) when devx is installed (Crossover and xine-ui).

Firefox 3.6 -> http://www.mozilla.com/en-US/firefox/firefox.html This is not a pet, it is the tar.bz2 file from mozilla. Just download and click to Extract; then open the folder and click firefox. It will update itself daily if you ask it to, Tools -> Check for Updates. It is the latest 1.9.2 gecko, which scores about 25% better on Peacekeeper than the 1.9.1-based versions including 3.5.x in my tests.

Ideally uPup will correctly install your video card and also install the glx/dri files. That can be checked by Menu -> System -> System status and congif -> Hardinfo -> Display and scroll down to see that glx/dri are enabled. One can also check by entering "glxinfo" or "glxgears" at a command prompt. It works that way for me anyway; I am curious to see if it works for anyone else. I personally think that using all of the xorg drivers and installing glx/dri might make things more stable and robust when dealing with newer programs and versions.

If you have an Nvidia video card. My first test on a different computer failed, but I figured out why. Xorgwizard choose the "nouveau" driver, which I assume is for newer Nvidia cards. So if you have a newer Nvidia card it might work right off. If xorg fails to start it will return you to the prompt (or hit CTRL-C). At the prompt enter

Code:

rm /usr/lib/xorg/modules/drivers/nouveau_drv.so

which will erase the nouveau driver, and then enter xorgwizard again and it should choose the "nv" driver that you need. Alternatively, if xorg fails to start, you can enter

Code:

e3/etc/X11/xorg.conf

and edit your xorg.conf file, replacing driver "nouveau" with driver "nv". Then CTRL-K, X, to quit the e3 editor and "xwin" to restart X. Both of these ways worked for me, and GLX/DRI were started correcly also

If you have an ATI card that doesn't start correctly, you might try among the "ati," "radeon," and "radeonhd" drivers. It is the "radeonhd" that works for me, which was not in uPup by default.

I have been using SitHeelSpeak's special devx supplement, and with that, the regular devx, and the kernel sources, I have been able to compile and install the latest (9.10) proprietary ATI Catalyst driver, which works well with my Radeon 3850, and the Catalyst Control Center is working correctly also.
------------------------------------------------------------------------------
It bugs me to leave out the "nouveau" video driver so the xorgwizard will assign the "nv" driver (which a few people were having to do manually). If this causes you a problem please let me know. I investigated a tiny bit and it seems that "nouveau" is an attempt to get 3D hardware acceleration in an open source driver for nvidia cards. I have had luck in installing/compiling the proprietary 3D hardware acceleration driver Catalyst/fglrx for Ati radeon cards. Perhaps if someone wanted hardware 3D for nvidia they could try to install the Nvidia proprietary driver. For the nouveau driver though -> http://www.diddywahdiddy.net/Puppy400/nouveau_drv.so.tar.gz Click the file and Extract it, and then place the driver in /usr/lib/xorg/modules/drivers/. After that, Menu -> Shutdown -> Exit to prompt and run xorgwizard at the prompt.

I routinely Save the Network as in the picture below. Your router will have a different name of course.

Last edited by playdayz on Wed 03 Mar 2010, 18:04; edited 138 times in total

Altho I am downloading right now and will test later, I have a bit of a problem with the naming.
The latest upup was 476, I use it.
You advertise 432.
There could be a problem when one wants to migrate (if ever possible) to this 432 version.

Any thoughts?_________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

Hey Beem, My thoughts are that it is confusing. I am not sure the latest uPup is 4.76 though The latest Woof (20091120) generates a uPup numbered 4.32 by default. I just left the number as Barry chose it. 4.76 was one of Barry's wasn't it and then he went back to 4.32? Yes, it could be very confusing, especially as Woof becomes easier and easier to use, more and more people will be making Puplets with it. There might not even be enough numbers between 4 and 5 I am making no claim at all to being in any official sequence. But there might not be an official sequence anymore. I thought that choosing to name the uPup after the edition of Woof might have something to recommend it, but you are right, the number displayed is 4.32. I gather that Barry does not plan to release any more uPups himself but maybe he would have something to say about numbering. ttuuxxx choose 4.50 and 4.60 also. Do you see a way forward?

way to go playdayz I only made the upup version up just to test it and see if it was stable enough to build a OLPC version on it, I haven't the time since I've been working to devote towards puppy, I'm still doing around 40hrs+ a week for puppy but nothing like 110hrs a week I was doing when I was unemployed If you want to take over Upup, feel free to. maybe do the next release number 4.51
That way
4 series ends at 4.49 and goes to Ppup
upup 4.51
PPup 4.60 <---Maybe
Dpup4.82+
Pup2.20 <---The one I'm aiming for.
and once one hit's a genuine RC then Series 5 happens.
ttuuxxx_________________http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games

I am impressed by your pup.There are some cosmetic problems but for me a major obstacle is that I cannot run it with a wlan connection no other Puppy systems has any problems with. eth0 causes no problems.

Do you have any clue to why the IP-address is different? Is the adress range limited to 192.168.0.xxx ?

Added comment:The IP-adress is obtained from a neighbors wlan running unprotected. Using Puppy 431 I can choose between my wlan and the neighbors. But I cannot get upup432 to connect to my wlan. The error output is:
Unable to establish WPA connection
Access point: Not-Associated
Link Quality:0

ecube and timremy, I apologize. I did not say clearly enough that this is a very experimental version. The Puppy is just as it comes from Woof 20091120 with the few changes that I specifically mention.

It should be regarded as alpha software, at the most! It is definitely not a development of 4.3.1--it has very little in common with 4.3.1 under the hood--the numbering is kind of an unfortunate artifact that people are trying to figure out what to do about.

If one is interested in learning how Puppy works by hacking around on the internals and learning to do it yourself, then this could be a good place to be. It is possible that people reading this thread could solve problems such as the ones you are having and if so then they would post a fix and I will try to implement it in this experimental puppy as it grows up.

This concerns the changes I made to two of the important configuration files as I used Woof 20091120 to build this uPup 20091120 Karmic with extra xservers (video drivers) and GLX/DRI graphics enhancement.

It is just for people who are playing with Woof (I can't imagine anyone else would be interested).

Quote:

your missing libreadline.so.6 here's the one from ubuntu Karmic made into a pet, if it works playdayz should included it and also the dev in the compiler.

Thanks Ttuuxxx for your help.
Your pet package silenced the complaint about missing libreadline.so.6. But still no correct internet connection. The error message now reads: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory. I have Ubuntu 9.10 (Karmic Koala) installed on the same computer as upup. The wlan connection works flawlessly there.

Thanks Ttuuxxx for your help.
Your pet package silenced the complaint about missing libreadline.so.6. But still no correct internet connection. The error message now reads: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory. I have Ubuntu 9.10 (Karmic Koala) installed on the same computer as upup. The wlan connection works flawlessly there.

Actually, this and 4.3.1 have always turned off rt73 (usb), although it works at the start. It's a puzzle, as other 4+ puppies work OK with it._________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).

Playdayz! Are you contemplating building a upup version based on the woof tarball woof-20091202081304REFERENCE.tar.gz? http://bkhome.org/blog/?viewDetailed=01232

Yes ecube, I do hope to keep up with the Woof versions and make a uPup for each one, at least for my own usage. I would post it if I saw that some people were interested. Nobody knows what is going to come of woof and how it will all work out. I don't think it will be the same as before, with one official version at a time--well, there may be one official version but it seems like there will be many more unofficial versions. And i still think the true genius of Woof might be in making personal versions, and for that I would see value in exchanging info about Woof and uPup. Giving the new Bones a go should tell me how quickly i could turn around a Woof into a Upup and how transferable the info is from one to the next..

Having Trouble with Wireless???

I I made a build from Bones Woof 2009-1202 Reference. But I am having wireless trouble with it. The Network Wizard, old or new, doesn't find any networks. Fortunately I can configure it manually, which is not much trouble anyway.

Open a terminal (This assumes there is a wireless module running--if not see the Arch page). This is from Archlinux.org http://wiki.archlinux.org/index.php/Wireless_Setup This is easier than it might look. You will only need two or three commands. The three I use are in green. The ESSID is the "name" of your router, which you need to know. And the "key" is the security key, 10 hexadecimal digits, just as usual in the Network Wizard.

1. (Optional, may be required) Some cards require that the kernel interface be activated before you can use the wireless_tools:

# ifconfig wlan0 up

2. (Optional, may be required) See what access points are available:

# iwlist wlan0 scan

3. Depending on the encryption, you need to associate your wireless device with the access point to use and pass the encryption key.

Assuming you want to use the ESSID named MyEssid:

* No encryption

# iwconfig wlan0 essid "MyEssid"

* WEP

using an hexadecimal key:

# iwconfig wlan0 essid "MyEssid" key 1234567890

using an ascii key:

# iwconfig wlan0 essid "MyEssid" key s:asciikey

* WPA/WPA2

You need to edit the /etc/wpa_supplicant.conf file as described in WPA_Supplicant. Then, issue this command:

# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf

This is assuming your device uses the wext driver. If this does not work, you may need to adjust these options. Check WPA_Supplicant for more information and troubleshooting.

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