Saluki

Message

dalderton · #1781 Post by **dalderton** » Tue 13 Mar 2012, 07:34

I have tried a couple of times to install Saluki with no success .My box is a bit ordinary but I have never before had problems with any Pup I tried . I have Racy and 3HD on partitions on this hard disc with no problems.
Saluki does not find the screen resolution which is 1440*900 no matter what.
I am not particularly concerned as 3HD has been the best I have tried up to date. Incidentally I always Full install to the Hard Disc as I have never been able to see the point of Frugal installs. This is in no way a criticism of Saluki , I just thought that someone may be interested.
Regards Dennis.

smokey01 · #1782 Post by **smokey01** » Tue 13 Mar 2012, 07:59

Dennis have you tried CTRL+Alt+Backspace to get to the prompt.
Then type xorgwizard [enter] then probe or select your preferred screen resolution.
Once selected type xwin [enter]

Does it now work?

I had a similar problem with another monitor. Although it said it couldn't do 1280x1024, if I did the above it worked.

Good luck.

James C · #1783 Post by **James C** » Tue 13 Mar 2012, 08:15

dalderton wrote:I have tried a couple of times to install Saluki with no success .My box is a bit ordinary but I have never before had problems with any Pup I tried . I have Racy and 3HD on partitions on this hard disc with no problems.
Saluki does not find the screen resolution which is 1440*900 no matter what.
I am not particularly concerned as 3HD has been the best I have tried up to date. Incidentally I always Full install to the Hard Disc as I have never been able to see the point of Frugal installs. This is in no way a criticism of Saluki , I just thought that someone may be interested.
Regards Dennis.

My Nvidia boxes all boot straight to a black screen too. You can find my posts scattered back through the thread.

Also use 1440x900 as well.I've always ended up getting the correct resolution after using xorgwizard.

smokey01's way should work or if booting from the cd hit F2 to enter boot codes, enter "puppy pfix=nox" (without the quotes) which will get you to the prompt where you can run xorgwizard as detailed above.

Sage · #1784 Post by **Sage** » Tue 13 Mar 2012, 08:36

What smokey & James say both work. They are a restatement of what Jemimah said in response my several enquiries. Furthermore, J. wanted to say that she has no control over what Xorg chooses. Well, that may be so, but none of the other (current) derivatives, with or without nV or monitor complications, with or without booting direct to Quickset, end up with this feature. The question remains, what aspect of which Xorg version is causing the problem. Can Xorg be forced into selecting a lower resolution? Didn't BK confront something similar a while back? Now that a ground swell of reports are confirming my reports of aeons ago (well, several weeks) maybe one of the gurus around might look into how it could be circumvented? It may not be exciting, but it's exactly the sort of issue to deter the timid neophyte.

Sage · #1785 Post by **Sage** » Tue 13 Mar 2012, 09:21

SiS video driver is in the 'choose' list but doesn't work.

dalderton · #1786 Post by **dalderton** » Tue 13 Mar 2012, 09:46

I have been through the xorgwizard route but it still would not give me the required resolution. Once previously when I tried Saluki it would boot to the screen but It would not respond to the mouse clicks so I gave up on it . Then last week when I tried it igot the aforementioned problem with resolution.
All very strange but I guess thats why we continue to try these things.
Regards Dennis.

Sage · #1787 Post by **Sage** » Tue 13 Mar 2012, 10:50

xorgwizard route ... would not give me the required resolution

Generally, it's necessary to choose the native resolution for your monitor, then select a lower resolution to display. If you start with 800x600 display that is almost ubiquitous, then, depending on monitor/eyesight/proximity it may be possible to set 1024x768. Folks displaying to their (large) TV screens often choose too high a display requiring viewers to unpack their opera glasses...

antiloquax · #1788 Post by **antiloquax** » Tue 13 Mar 2012, 10:56

Here's my .pet for pygame in Python2.7.
You'll need the Saluki Python2.7, python-tk, tk, tcl, and all the SDL bits.
Pygame for Python2.7.2

mavrothal · #1789 Post by **mavrothal** » Tue 13 Mar 2012, 11:37

Since the early Racy builds I had issues with the 7.6 xserver.
It may has to do with the way was build (as a replacement for the 7.3 xserver of Wary).
It may worth recompiling for Saluki or use the one from Luci (certain components I tried work fine). I believe the Racy/Saluki version is build from the Ubuntu 10.04 sources anyway.

jemimah · #1790 Post by **jemimah** » Tue 13 Mar 2012, 12:45

dalderton wrote:I have been through the xorgwizard route but it still would not give me the required resolution. Once previously when I tried Saluki it would boot to the screen but It would not respond to the mouse clicks so I gave up on it . Then last week when I tried it igot the aforementioned problem with resolution.
All very strange but I guess thats why we continue to try these things.
Regards Dennis.

This sounds more like a case of a missing zdrive.

ICPUG · #1791 Post by **ICPUG** » Tue 13 Mar 2012, 14:03

Sage

You make a good point about the appearance of blank screen with some hardware. It is very offputting to the average user. There were two aspects to worry about - dealing with kernel mode setting and the introduction of the automatic X-Org trying to dispense with user defined parameters.

A lot of time was spent when Lucid was developed in solving these problems because boot to desktop was a requirement of this puppy.

Barry, who likes to do things his way, then created an alternative way of dealing with the automatic X-Org.

The trouble with the Puppy development model is that every other developer has to get the knowledge somehow and knowledge transfer between developers is not great. Initially, Mick01 failed to get Slacko to boot to desktop and just gave up trying for a while. I think it has improved a bit since. It seems Jemimah has decided not to fight the automatic X-Org problem.

elroy · #1792 Post by **elroy** » Tue 13 Mar 2012, 15:01

What kind of hardware (monitor, etc.) are you running Saluki on. The reason I ask is that if you look at Saluki’s mission statement, from post #1 of the Saluki forum (The suggested target hardware is computers less than 5 years old), this doesn't seem to be an issue. If you're using Saluki on hardware older than the suggested target base, then you're kind of on your own as far as support goes. I myself am using a cheap laptop that's two years old that I purchased from Walmart. I haven't experienced any of these issues. As a matter of fact, I haven't experienced any issues on my cheap-o AMD laptop. I could be wrong, and if I am, please forgive me for my ignorance, but for the most part these complaints haven't been an issue on newer hardware to date.

Tman · #1793 Post by **Tman** » Tue 13 Mar 2012, 15:19

jemimah wrote:
Tman wrote:Heres a rudimentary pet of Uzbl web browser...
I've uploaded this to the repo.

I don't think uzbl is ready for general use, as I haven't figured out how to get the key bindings working, so you can surf, but the keyboard functions don't seem to be working (not very useful atm)..I'm taking a look at /root/.config/uzbl/config , trying to figure it out.

EDIT: okay, the website says it needs xclip installed for keybindings to work, but something is still wrong...

Okay, I figured it out...the first lines in uzbl-event-manager and uzbl-tabbed needed to be changed from "env python2" to
"env python". I don't know why that is, becuase python2 is installed in Saluki, but it works now.

Jemimah, please remove the old Uzbl pet from the repo. The keyboard functions work with this one out of the box...
I may make a new pet with a custom uzbl homepage, for easier use in the future.

Sage · #1794 Post by **Sage** » Tue 13 Mar 2012, 16:48

It seems Jemimah has decided not to fight the automatic X-Org problem.

!!!

I could be wrong...

- fraid so, you'd need to have been following this plot for a long time. Should've read ICPUG immediately preceding for a potted history. And then there's the eyesight/viewer positioning/nV v. ATI/etc. Age doesn't figure prominently, except, of course, everyone knows the 'old ones' are the best...

James C · #1795 Post by **James C** » Tue 13 Mar 2012, 16:58

I'm just relieved to know that these old boxes that I built in 2010 , not elcheapo either, are not new enough to boot to a desktop in Saluki. Knew I shouldn't have chosen to build with something as uncommon as Nvidia graphics either.

jemimah · #1796 Post by **jemimah** » Tue 13 Mar 2012, 17:08

Tman wrote:
jemimah wrote:
Tman wrote:Heres a rudimentary pet of Uzbl web browser...
I've uploaded this to the repo.
I don't think uzbl is ready for general use, as I haven't figured out how to get the key bindings working, so you can surf, but the keyboard functions don't seem to be working (not very useful atm)..I'm taking a look at /root/.config/uzbl/config , trying to figure it out.

EDIT: okay, the website says it needs xclip installed for keybindings to work, but something is still wrong...

Okay, I figured it out...the first lines in uzbl-event-manager and uzbl-tabbed needed to be changed from "env python2" to
"env python". I don't know why that is, becuase python2 is installed in Saluki, but it works now.

Jemimah, please remove the old Uzbl pet from the repo. The keyboard functions work with this one out of the box...
I may make a new pet with a custom uzbl homepage, for easier use in the future.

Ok, I will take care of this tonight.

Tman · #1797 Post by **Tman** » Tue 13 Mar 2012, 17:13

Tman wrote: EDIT: okay, the website says it needs xclip installed for keybindings to work, but something is still wrong...

the python-2.7 pet in the repo has "python xclip"

antiloquax · #1798 Post by **antiloquax** » Tue 13 Mar 2012, 17:46

James C wrote:I'm just relieved to know that these old boxes that I built in 2010 , not elcheapo either, are not new enough to boot to a desktop in Saluki. Knew I shouldn't have chosen to build with something as uncommon as Nvidia graphics either.

Sarcasm

It's not the age, I'd guess. Saluki works fine on my old Toshiba laptop. It's to do with Nvidia in some way. When I boot my desktop machine with Saluki, it "chooses" a resolution my monitor doesn't support. Helpfully, my monitor still displays the desktop while flashing up an "out of range" warning (it's an old 1024x768 screen). So then I exit to prompt and do the xorgwizard thing. It's all part of the fun, I'd say!

jemimah · #1799 Post by **jemimah** » Tue 13 Mar 2012, 17:51

I could blacklist the nouveau driver and let the nv driver handle nvidia. I don't know if this would cause more harm than good though.

I've never owned any nvidia hardware myself so (helpful) feedback and patches are welcome!

Sage · #1800 Post by **Sage** » Tue 13 Mar 2012, 18:01

I could blacklist the nouveau driver

Bells are ringing. The old memory box aint perfect but that sounds very much like a strategy that was used previously, maybe some years ago when it first raised it's ugly. One person who would know is BK, of course.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Saluki