I tried to get the NVIDIA video driver for Wary. I down loaded the latest version (190.36.15) for Linux. I found one needs to have the devxx.sfs for it. It needs several binary utilities. I thought it was going to work, but, it needs the kernel source to built the driver. Oh well, I need to think about this and do some research. I reached the limit of my knowledge.

OK, I found the sfs file with the kernel sources. The process went a bit farther, but still failed. This is the error message from the log:

Quote:

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

I did also find that you need to do the building from the command line. The Xserver can not be running. Any help or suggestions will be appreciated. I am definitely "out of my league" with this one. Thank you in advance for any help.

My nvidia seems to work in Vesa but not in xorg set up. Video get choppy and jerky instead of having glitches which I prefer to choppy and jerky which makes me seasick looking at them.

Could there be somebody deciding they prefer the choppy and jerky over glitches and that we will get stuck with that preference for all future???

Me really worried that this is decided way high up in linux foundation something?

Could anyone give a hint if the choppy and jerkyness is an error that crept in or a deliberate design feature that somebody decided is better than glitches.

Glitches
1. A minor malfunction, mishap, or technical problem; a snag: a computer glitch; a navigational glitch; a glitch in the negotiations.
2. A false or spurious electronic signal caused by a brief, unwanted surge of electric power.
a glitch looks like a super fast narrow line that appear randomly horisontally on the screen

while a choppy or jerky is the whole movement of a person goes from one position to another in a delayed smoothed out jerking move as if they have some spastic problem moving or are playing Robots.

we are at least three members of this forum having this problem. it only happens with Quirky and Dpup and Upup and one more.

What in Linux land is going on?_________________I use Google Search on Puppy Forum
not an ideal solution though

All the formatting buttons on the toolbar work but not the menu. I was trying to change the difference between two dates into plain numbers (of days) but couldn't in gnumeric. Had to use Planmaker instead.

BTW, Barry, Great fix on Abiword and the .docx files. Have installed the .pet and am using it at work.

No my error is different. The NVIDIA installer is complaining about the Kbuild directory for the kernel with me. If I got your error message, I would press the No button to see if it would continue and what happens. Your message is complaining about the use of GCC, which should not be fatal. Thank you for the URL. I will have to look at it.

I tried the instructions of the above URL and got the same error message. This happens every so often. Time, to re-think the approach._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love MuchLast edited by JustGreg on Sun 18 Apr 2010, 18:47; edited 2 times in total

Earlier I found that modprobe and lsmod were missing, but it was very late, the fix was trivial (copy them in from another Puppy), didn't take notes, so not sure if that was on wary or some other new woofbuild.

___q018 update100416/18___
Oh %#&@
Had to hardoff in q013 while testing jwm2-489-w1 dotpet/extract (an exit to prompt gave a nonresponsive cursorblink topleft, no kybd response, nada) .. on getting to a prompt (somewhere in the xorg after the initial dialogue, I think) gave the reboot cmd and it offered usual choices .. somewhere in there it did a fs3 check and wiped out the quirkysave-eighteen.3fs savefile (yes, again ) as well as quirky_devx_010.sfs (hunh ) .. it seems the checksystem may bite you on a hardoff even if you make what seems like reasonable choices.

So perhaps until the checksystem is completely understood..
a) always make backups of savefiles on an external partition
b) after a hardoff, boot a pre-q010 quirky and try to guess at how to fix things before trying to use a quirky with a checksystem - optionally, make backup(s) of possibly corrupt savefile(s) since they may be better than nothing
c) use multisession liveCD

100418
For the third time a savefile for q018 (this one's a 2fs - noticed in other pups that a 3fs savefile may not be clickmountable.. there are a few occasions when it's easier for me to do 'fixes' outside of a running pup and possibly why this is the third savefile ).

Outside of that personal observation, I like q018. Xorg seems to be a bit easier to deal with (not saying much, compared to w019 ) and offers a few tweaks for my particular twin-ati so that's one.

Another is that conky (1.7.11) works in q018 with only a minor libset (xcb-something) added - this may be due to the older pixman (0.16.2), rather than w019's more up-to-date one. Jwm is better icon-trans-wise with the 489 binary from the w dotpet.

Minor personal issue with a slapped-in jwm (either q018 or w019) and plogout. Plogout works fine in other wms (uncommented restartwm's final 3 lines to ease a button-switch without having to 'kick' it with ctrl+alt+bs), but in jwm the murgaLua window doesn't show? Put in a wmexit on tray and jwm's rootmenu so no biggie. Just puzzled why window doesn't show - if ctrl+alt+bs always dropped out of X to prompt.. yah, fussing with console(s) can be surprising occasionally for me (and why I generally leave kybd specializations on 'default' unless there's a real good reason not to).

___w019___
100416-17 w019 liveCDmulti
The dialogues on xorg need work - it took some few hardoffs and lucky guesses to get to x (plus disregarding bad or 'odd' info as reported in the final dialogues) but it did actually get the correct bus-card-display up (instead of the switched-off-in-BIOS set).

About time tabview got fixed in pmount.

Smooth gradations look nice .. in 24bit.

1st savedir (kind of a relief to get back to multisession after losing q018's savefile - yah, backup), some oddness with conky (not sure what, it may be newer version of pixman or xorg build) not displaying. Openbox still good, runs well without roxpin or fbpanel (eventmanager all unticked).

100418
It kind of grows on me (even with no conky), not that hard to get pfbpanel to liking. It (fbpanel) is a bit strange in wmx7, window decor is slightly different 'rules' there (for instance, retrovol has a 'window' even without a panel or tray up). The new display for freememapplet_tray is nice and simple, no squinting at numbers for a quick glance of a 'ballpark' of what you got to work with.

w019 does seem a bit quicker to load some apps (or it might be difference in liveCDmulti as opposed to the 'on-stick' of q018 - usb jacks on the tower are older-generation so transfer is a bit not quite what it could be).

100420 - conky alternative(s) for w019
It may just be me, but having some sysinfo clearly visible as a pseudo-transparent backwindow is a thing I've liked about torsmo/conky since meanpup (then there came the pwidget-system in p42x ).

a) use a console/htop - probably the most efficient
b) gkrellm - I'm not real familiar with gkrellm, but ttuuxxx's fairly recent gkrellm-2.3.2 dotpet works nicely in w019 and has lots of features and decent local docs ( "man gkrellm" does the usual attempt to connect to an online page rather than bring up the local dot1 - no biggie, gk's info tabs are decent and I can wade thru the dot1 if necessary for those little extras).

Do racing aerobatic planes have quirky or wary tails? Last edited by `f00 on Wed 21 Apr 2010, 10:58; edited 1 time in total

I tried Quirky 018 with the NVidia official driver. Same problem and same error. I noticed that Quirky Pets listed this driver:
xf86-video-nv-2.1.16-q1.pet

Is this the correct driver for Quirky 018 and the NVidia hardware. There are others, but, they have 7.3 in the name, which is the version of xorg that Wary 019 uses. I have tried xf86-video-nv-2.1.16-q1.pet, but the xserver refuses to start.. It seems no matter what I try, the only thing that will work is xorg Vesa driver.

The Vesa driver would be fine, if it supported the resolution of 1366 by 768. I am tried to edit xorg.conf to see if I can get the 1366 by 768 by setting the screen section resolution to 1366 by 768. It did not work.

Any thoughts, suggestions or help would be appreciated. Thank you in advance._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

Good morning JustGreg
NV and Nouveau-drivers are both open source more-or-less reengineered drivers for Nvidia Hardware (no VDPAU acceleration which is important for me). Tested both of them on diverse Puplets but I wasn't successful at all. ->Risky

Again Closed Source driver: As I wrote previously a continuation after my first error message depends on the used Puplet
1.) UPUP, DPUP: possible but crash after switching to 24bits
2.) Lucid and Quirky: no continuation possible (haven't tested Lucid-8 so far)

Concerning your installation attempts: did you reboot after SFS activation of the devx-development system ? I think I have seen your error message before... when I once forgot to reboot the machine.

There is a alternative description of the installation process
http://www.murga-linux.com/puppy/viewtopic.php?t=47049
I found it recently. It was written by Iguleder who also released some early Woof based Puplets.
http://www.murga-linux.com/puppy/viewtopic.php?t=53769
Could you please give it a try in combination with the NVIDIA installer? This worked for me but wasn't a real alternative to Lucid or Quirky.
Good luck.

hi all, i am new here and wanted to try wary-019 on my gecko edubook. I have upgraded my bios in order to get rid of the apm bug, and did a standard installation of wary on a 2gb sd card. here are the difficulties i am facing:

1. wary boots and brings me to the xorgwizard utility; if i am choosing another language than us, i get a blank screen and i am unable to get back to a prompt (either with ctrl+alt+F1 or F2, or with ctrl+alt+backspace); i have to reboot the gecko by pressing the on/off button;

2. booting wary and choosing the default (given) settings in xorgwizard, it brings me to the next screen where i have to choose either xorg or xvesa; but whatever i choose, i always get a blank screen (fortunately, i can get back to the xorgwizard utility with ctrl+alt+F1); even if i am choosing a non standard resolution for my edubook (say, 800x600), i get this blank screen an nothing happens.

puppy 431 and 432 works fine on the edubook (although with limitations underlined by Barry in his blog). thanks for support and help.

Thanks, Hesse James, for the information. I have looked at the web sites. The NVidia driver is a hot topic with other distributions. It is not that easy to install.

Yes, I do reboot after installing the devx and kernel source sfs files. Still get the problem. I will try to do it exactly following the Igulender how to.

Thank you for confirming that NV and Nouveau drivers are for the Nvidia video hardware. I have noticed that my Nvidia Ion LE hardware is not detected properly. Xorgwizard does not associate either with my video hardware.

I have several things to try and will post the results._________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

I have checked Quirky using the system interface tool. The PCI portion does identify the video process as NVIDIA with a device number 0x087E. Quirky also uses the xorg.conf.NVIDIAF19 file to set up xorg.conf. The NVIDIAF19 file forces the use of the VESA driver.

I found by placing nv_driver.so and nouveau_driver.so in the /usr/X11R7/lib/xorg/modules/drivers-alternate directory, one could use them by the tweak tool of xorgwizard. I found that the nv driver just failed and would not start. The nouveau driver just crashed the system, the video shutdown. I had to turn off the power and use another puppy system to go back to the original xorg.conf.
In looking at the /usr/lib/X11R7/lib/xorg/modules/drivers directory did not have a type la file for the nouveau driver. The pet did not install one either. The type la file is a library linking configuration file (I think). I think the lack of it is why the nouveau driver failed so badly.

I download the nVidia old version (190.53) driver that does work with Puppy 4.3.1. When I try to install it, the installer reported that it found the kernel sources, but could not determine what version of the kernel was being used. I tried a option (--kernel-name='kernel name') that I thought might work. It did not. It appears there needs to be file or environmental variable that has the kernel version information missing.

Any ideas on what to try next?_________________Enjoy life, Just Greg
Live Well, Laugh Often, Love Much

I burned Quirky to a DVD-RW using Burniso2cd, booted it, configured this and that, shut down saving to the DVD. Everything worked fine when I rebooted and all my settings had been retained.

A few boots later I needed to convert an audio book into mp3 so I could listen to it on my mp3 player. I installed Pcdripper from the Puppy 4 repository of the Puppy package manager. Everything seemed to go well, and there were no missing libraries reported. But, when I clicked on Pcdripper in the Multimedia menu, It started, but only as far as asking if I wanted to rip another disk.

I entered pcdripper in urxvt and got the error message shown, plus the window asking if I want to rip another disk.

Pcdripper has had this problem all along, but in Puppy 4.3.1 it would usually get past that question if I clicked Yes enough times. Another thing wrong with Pcdripper is that it doesn't retain my settings. Could they be related?

I really like Pcdripper. It allows me to number the files it rips in such a way that it is easy to combine many CDs into one directory with the mp3 files numbered so that they play in the correct sequence. No other CD ripper I've tried does that. However, Pcdripper has some flaws. Most are just mistakes in the design of the GUI which I suppose could be easily rectified by someone who knows what he's doing. I tinkered with it a bit, to no avail. However there is this one serious bug I'm reporting here. It's really a bug in Pcdripper, but it didn't prevent me using the program until Quirky.

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