Guess I might as well report this problem. As was also happening in Exprimo and Wary, my installs of Saluki have no Wget and the inability to ping.Barry K discovered the solution here http://www.murga-linux.com/puppy/viewto ... 098#616098 so it should be in the next Woof commit.
Also, the PPM works but unable to download updated package lists.
No longer seems to be there. One of the most difficult sites I have ever encountered.
That's strange dave, it may be due to the spaces or capitals in the name, I sent the link for a friend to test and it worked fine for him, any way I tared it up for you.
Frisbee has never worked for me in other Puppy variants. In the case of Saluki, neither Frisbee, Barry's Simple Network Manager nor Network Manager would work. I had to therefore configure the rtl8192cu WLAN set-up manually using wpa_supplicant + DHCP from the command line. Works OK now.
Second problem was the ati fglrx module. The official pet package for this didn't work and neither was it possible to build the module as supplied from the AMD website - using kernel sources for k3.2.8 and the devx. I therefore decided to have a go with the Saluki Custom builder and installed the k3.1.10 PAE kernel sfs-module from Slacko along with the kernel sources pet. This was successful and the ATI fglrx built first time. From further research, this 3.2.8 kernel needs a patch so that the ati fglrx module can be compiled.
Third problem was the XFCE4 sound mixer. This mixer has a problem co-existing with ALSA. XFCE mixer and ALSA toggle each other's digital mixer channel (lol!) - hence no microphone in Skype. The fix was to install retrovol and to configure the xfce mixer panel applet to point to retrovol instead of to xfce-mixer. This is done by right-clicking the volume icon and accessing the properties menu.
The video and wlan problems as described above could well be show-stoppers for a noobie, so it it's worth looking into them.
The end result was good though. Looks good with Compiz running. Guake also worked straight out of the box. Really liked the Custom Builder. So I'll be exploring other customisation options further. Seems to be plenty of great extra software stuff available too.
I'll be using this distro on a daily basis and will be looking out for any updates.
Life is too short to spend it in front of a computer
Hi i found this post. relating to sakluki and asking what i already have here. why is there only one forum for sakuki. click here
Having one thread really does make it hard to find the information for each build. sometimes a build can go back as far as 10 or more pages. this is why generally most other puppy os have made a new forum page for each build of there os, and use the puppy linux wikka for the main page for there os with all the new updates etc there.
I am only mentioning this again because i saw someone else pose the same question.
I cant wait for the final 1.0 release of saluki and it to become a full recognised puplet.
My view is that saluki is a more full featured os than other puppyes, in respect to using a bigger xfce desktop but still being small and compact. great job.
HiDeHo wrote:
I have noticed that the Puppy community generally people support each others projects more than other os, this is a good idea. why not pose the question on how to get pwidgest in a new post. others might happen to contribute.
I'm not talking about "moral support". If pwidgets makes a lot of assumptions about rox and jwm being there, and generally has issues with notifications messing it up, and not playing nice with xfdesktop, then it would need to be rewritten to meet basic quality standards before I add it to the repo. I don't think I plan to do that. If someone else wants to take it on, feel free.
I see your point. now looking at pwidegts. what is it based on. concky, gkrelm. maybe one of them could be modified to run on pupy. both can run in xfce.I say gkrelm would be better.
Haven't been able to get CUPS printing to work in Saluki
In the default CUPS 1.3.11 version, there was no access to the CUPS interface at localhost:631. The interface was visible but was inactive.
I then downloaded and compiled the latest stable CUPS 1.5.2 from their website. This compiled OK, but I get an "INTERNAL SERVER ERROR" if I try to access any tabs in the interface.
I used a standard cupsd.conf file as recommended for use in SLACKO. No joy though.
Life is too short to spend it in front of a computer
tronkel wrote:Haven't been able to get CUPS printing to work in Saluki
In the default CUPS 1.3.11 version, there was no access to the CUPS interface at localhost:631. The interface was visible but was inactive.
I've had the same problem but haven't reported it yet as I thought it might have been caused by something I'd added or tweaked in Saluki.....
CUPS does work OK on a new pristine install but then stops working for some reason.
I've loaded the Chrome 12 SFS - did wonder if that caused it but haven't had time to experiment - but now that there are 2 reports of the same problem....when the fault occurs its the same in both Midori and Chrome - the browser tries to access localhost:631 but just hangs with no response.
The problem manifested itself in both 016 and 017 at least....
Thanks
PeeBee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I did have google-chrome sfs which brake cups due to wrong permissions. Fixing the permissions and all was good. This was in dpup exprimo and I am not referring to Saluki Chrome sfs.
Just mentioning the possibility.
James C wrote:Guess I might as well report this problem. As was also happening in Exprimo and Wary, my installs of Saluki have no Wget and the inability to ping.Barry K discovered the solution here http://www.murga-linux.com/puppy/viewto ... 098#616098 so it should be in the next Woof commit.
Also, the PPM works but unable to download updated package lists.
tronkel wrote:I've been trying out Saluki 017 yesterday.
Here's the story, first the problems.
Frisbee has never worked for me in other Puppy variants. In the case of Saluki, neither Frisbee, Barry's Simple Network Manager nor Network Manager would work. I had to therefore configure the rtl8192cu WLAN set-up manually using wpa_supplicant + DHCP from the command line. Works OK now.
Second problem was the ati fglrx module. The official pet package for this didn't work and neither was it possible to build the module as supplied from the AMD website - using kernel sources for k3.2.8 and the devx. I therefore decided to have a go with the Saluki Custom builder and installed the k3.1.10 PAE kernel sfs-module from Slacko along with the kernel sources pet. This was successful and the ATI fglrx built first time. From further research, this 3.2.8 kernel needs a patch so that the ati fglrx module can be compiled.
Third problem was the XFCE4 sound mixer. This mixer has a problem co-existing with ALSA. XFCE mixer and ALSA toggle each other's digital mixer channel (lol!) - hence no microphone in Skype. The fix was to install retrovol and to configure the xfce mixer panel applet to point to retrovol instead of to xfce-mixer. This is done by right-clicking the volume icon and accessing the properties menu.
The video and wlan problems as described above could well be show-stoppers for a noobie, so it it's worth looking into them.
The end result was good though. Looks good with Compiz running. Guake also worked straight out of the box. Really liked the Custom Builder. So I'll be exploring other customisation options further. Seems to be plenty of great extra software stuff available too.
I'll be using this distro on a daily basis and will be looking out for any updates.
If you go into Wireless Diagnostics in Frisbee and Generate Diagnostic Data and post the results, I may be able to find your Frisbee problem.
I'm going to pull the ati package from the repo. I think it was compiled on a slightly older revision of the kernel. Maybe someone will post a new ati pet.
HiDeHo wrote:Hi i found this post. relating to sakluki and asking what i already have here. why is there only one forum for sakuki. click here
Having one thread really does make it hard to find the information for each build. sometimes a build can go back as far as 10 or more pages. this is why generally most other puppy os have made a new forum page for each build of there os, and use the puppy linux wikka for the main page for there os with all the new updates etc there.
I am only mentioning this again because i saw someone else pose the same question.
I cant wait for the final 1.0 release of saluki and it to become a full recognised puplet.
My view is that saluki is a more full featured os than other puppyes, in respect to using a bigger xfce desktop but still being small and compact. great job.
Given how frequently I do releases and how much traffic there can be on this thread, I'm not certain having posts scattered all over the place is going to help. Having one thread makes it easier for me to stay on top of things.
I'm not sure about being a "recognized" puplet. That is for Barry to decide. I think Barry's opinion is going to be that Saluki is a fork.
pemasu wrote:I did have google-chrome sfs which brake cups due to wrong permissions. Fixing the permissions and all was good. This was in dpup exprimo and I am not referring to Saluki Chrome sfs.
Just mentioning the possibility.
The root folder and its subfolders were screwed in that google-chrome I used. I changed ownerships and permissions back to as they should be in puppies.
I have repackaged the google-chrome.sfs so that the cups should not be so upset.
Give it a try and give feedback. I also fixed the missing menu icon...
About protecting cups files permissions and ownerships. Jpeps has created simple gui for it. It installs to the Filesystem in my dpup. I dont know if it will have menu entry in Saluki. http://www.murga-linux.com/puppy/viewtopic.php?t=68790
Well I finally got my full install to work correctly. Upgrading via the Univ Installer SEEMED to work, ish, bt Midori was hopelessly unstable, seg faulting all over the place, so I did a clean install from the CD iso.
Thanks so much for the wallpaper guys.
Been using Puppy exclusively since 4.1, but this is the first time I have ever tried a full install. All works very nicely.
The launcher on the left is a second panel. This only loads correctly at boot up about 50% of the time. The other 50% it displays as a blank grey bar and I have to re-start X. This has been the same for all versions of Saluki. Maybe my hardware is not quite fast enough.