Classic Pup 2.14X -- Updated 2 series

[JonT]

Installed xvesa pet ... same result as James C. If I select the Xvesa wizard from the menu I get dumped straight to a prompt, no resolution setting gui. i810 is my usual driver, as does James C, as I have the 82845 video chipset. Here's /tmp/xerrs.log

Code: Select all

Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list!
killall: HotPup.sh: no process killed



cups: restarted scheduler.
3444: old priority 0, new priority 19
/root/Startup-Metacity-apps/gatotray: Can't get scaling frequencies: No such file or directory
Window manager warning: Lost connection to the display ':0';
most likely the X server was shut down or you killed/destroyed
the window manager.
/usr/X11R7/bin/xinit:  connection to X server lost.

[ttuuxxx]

The way I did it guys was I exited X to command prompt via the shutdown menu than ran xorgwizard and when it gave me a choice of Xorg or Xvesa, I select Xvesa.
I could be a difference in video cards/monitors also.
I'll try something else tomorrow
ttuuxxx

[James C]

The way I did it guys was I exited X to command prompt via the shutdown menu than ran xorgwizard and when it gave me a choice of Xorg or Xvesa, I select Xvesa.
I could be a difference in video cards/monitors also.
I'll try something else tomorrow
ttuuxxx

Further update on xvesa.........

Top 8 live pfix=ram on my main Linux box with an old Nvidia card. Xvesa works and I even got to see the pretty gui resolution selector. This is with the original iso....no added pet included.
My preferred 1440x900 is not included but I do have a workable desktop.

So, xvesa is working with this Nvidia card but doesn't like Intel graphics.

[James C]

More stuff.....

-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1035MB (155MB used)
Operating System : Puppy Linux 0.21
User Name : root (root)
Date/Time : Fri 01 Jul 2011 11:01:57 AM PUP
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : (null)
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235


sh-3.00# free
total used free shared buffers
Mem: 1035712 387024 648688 0 48084
Swap: 1228932 0 1228932
Total: 2264644 387024 1877620
sh-3.00#

[Aitch]

perhaps xdpyinfo might help?

see http://www.murga-linux.com/puppy/viewto ... 238#336238

Aitch

[RetroTechGuy]

Code: Select all

Usage init
init is the mother of all processes 

and then it stalls.

The kernel line should contain:

Code: Select all

root=/dev/ram0

this wasn't deprecated until puppy version 3 (maybe 2.17), I think.

Also the filemnt command is missing and sfs files cannot be mounted by clicking in rox.

See this post!


And, ttuuxxx, Classic pup 214X sounds like a good and spot-on name for this puppy.

hth /
MHHP

Booting an old machine from CD works fine, but installing the "newgrub.txt" script into my menu.lst does not boot, still giving this error (also had it with Top7). Applying this patch works, but this script should probably be fixed.

Also, is there a way to disable loading the .sfs to RAM? pfix=nocopy apparently has no effect, so it uses 157 MB RAM (on the machine I'm playing with, I have 512MB, but I would like to lighten the load, so it will run better when I put it on a really old machine, with low RAM).

[JonT]

About the Xvesa question: Sorry I didn't report that I had also tried exiting to a prompt, xorgwizard, Xvesa - still no Xvesa wizard.

Just to be clear, I'm not an experienced bash debugger, so the following may be off track but hope it helps with this issue. I'm only doing this to help out - like James C, I'm happier with Xorg and i810 but it's hard for ttuuxxx to fix a problem that doesn't exist on his computer. Sorry for the long post, just trying to be clear.
Lines 18-24 of /usr/sbin/Xvesawizard read

Code: Select all

# get list of modes available (note that I use this **unquoted** for the dialog)
## check if we've got a Intel card:
if grep -F 'oem:' /tmp/ddcprobe.txt | grep -F -q 'Intel' ;then 
  # intel card, have to manually give the options for high resolutions
  # get screen resolutions
  MONCHOICES="`grep -F 'timing:' /tmp/ddcprobe.txt | grep -E -v 'Apple|8514A|Mac II|\(XGA2\)' | grep -E ' 640x480@| 800x600@| 1024x768@| 1280x600@| 1280x768@| 1280x800@| 1280x1024@| 1360x768@| 1400x1050@| 1440x900@| 1600x1200@| 1680x1050@| 1792x1344@| 1856x1392@| 1920x1080@| 1920x1200@| 1920x1440@' | cut -f2 -d' ' | cut -d'@' -f1 | sort --field-separator=x --numeric-sort -u | tr '\n' ' '`"

The contents of my /tmp/ddcprobe.txt are

Code: Select all

vbe: VESA 3.0 detected.
oem: Intel(r)845G/845GL/845GE/845GV Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Intel(r)845G/845GL/845GE/845GV Graphics Controller Hardware Version 0.0
memory: 8000kb
mode: 1280x1024x256
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 1024x768x256
mode: 1024x768x64k
mode: 1024x768x16m
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x256
mode: 800x600x256
mode: 640x480x64k
edid: 
edidfail

There is no "timing:" string in that file so the variable MONCHOICES is empty. It looks to me as this ends up with the variable ALLCHOICES in line 47 (if I haven't messed up the original file) of Xvesawizard to be empty and the wizard exits.

As a test, I added MONCHOICES="1024x768@" just after line 24. All runs were with a fresh boot with pfix=ram. No luck till I added the recently posted PET (from Xorg) back to prompt, xorgwizard, Xvesa with a tiny but useable screen. Then I ran Xvesawizard from the command line, got a different gui from the one posted (blue background, older syle), tried the Menu > Setup > Setup Wizards > Xvesa Video Wizard which dumped me back to a prompt. I typed "xwin" and successfully got a 1024x768 screen. Never did see the gui posted (I have but not in top8).

So, this doesn't seem to be all the problem, it should affect only Intel graphics and maybe not all of those. Of course it may be that the problem is dccprobe.txt file is not filled out properly or something else altogether.

[MinHundHettePerro]

Booting an old machine from CD works fine, but installing the "newgrub.txt" script into my menu.lst does not boot, still giving this error (also had it with Top7). Applying this patch works, but this script should probably be fixed.

Also, is there a way to disable loading the .sfs to RAM? pfix=nocopy apparently has no effect, so it uses 157 MB RAM (on the machine I'm playing with, I have 512MB, but I would like to lighten the load, so it will run better when I put it on a really old machine, with low RAM).

Hello !
Just quickly glancing through /usr/sbin/puppyinstaller, it looks like adding root=/dev/ram0 at line 1287

kernel ${xNEWPSUBDIR}/vmlinuz root=/dev/ram0 pmedia=${FINALPMEDIA}${OPTIONPSUBDIR}

could solve the issue for frugal installs to internal hd:s, using GRUB.
Didn't really think about whether installs using sys/extlinux also need to be likewise modified ....

Didn't try it, though, perhaps someone would be willing to guinea-pig this..............

Cheers / MHHP

[SouthPaws]

Nice update on the poll... (I voted for my available choice this time.)

If your up for another choice... (you know, for those finicky voters)

You might consider adding the following...

one of the above

[JonT]

Addition to my post a couple above about Xvesa trouble:

Looking at the sample output of ddcprobe at http://www.cyberciti.biz/faq/howto-use- ... e-command/, it is the same as mine up to the failure of edid. Apparently failure of edid is key.

I downloaded 214X top 5 and got the same results as with top 8.

dccprobe failed identically for me in the latest Wary, though Xvesa works properly because Wary uses a different /usr/sbin/video-wizard than 214X does (video-wizard is used more often than the older /usr/sbin/Xvesawizard I first looked at but has similar code).

With luck it is only a problem with those of us happy with xorg. Maybe using a grep based on "mode:" instead of "timing:" would fix it

[nubc]

Argh, where's mhWaveEdit? Gots to have it.

[ttuuxxx]

Argh, where's mhWaveEdit? Gots to have it.

Here's the latest
ttuuxxx

[Colonel Panic]

Downloaded Top8 and am using it at home; I like the fact that it uses XFce by default now. Classic Pup is consistently one of the best Pups out there IMO

Cheers,

CP .

[ttuuxxx]

I Compiled the latest Fotoxx and made a special large version.
It contains fotoxx-11.07, exiv2-0.21.1, Image-ExifTool-8.60, ufraw-0.18
Enjoy
ttuuxxx
http://www.smokey01.com/ttuuxxx/2.14X/S ... 7-i386.pet <--3.9MB pet

[nubc]

I installed mhWaveEdit from PPM, but after restarting X server there is no menu entry. When I click Launch Mixer from the Record gui, nothing happens.
Ttuuxxx, I know this is your puppy, but would you mind putting pfind in the repo.

[ttuuxxx]

I installed mhWaveEdit from PPM, but after restarting X server there is no menu entry. When I click Launch Mixer from the Record gui, nothing happens.
Ttuuxxx, I know this is your puppy, but would you mind putting pfind in the repo.

mhWaveEdit just install the pet and click mhWaveEdit then click My Menu/Refresh Menus Then look in My Menu/Mulyimedia /CD/DVD Ripping/tools/ mhWaveEdit
And as pfind goes, It was way replaced with a better finder called Search Monkey,located in Menu/Filesystems /File Managers.
ttuuxxx

[ttuuxxx]

Here's the latest mtpaint I changed most of the gui icons
ttuuxxx

[sheldonisaac]

Hi, all. Some snipping.

Here's the latest sylpheed-3 beta version
ttuuxxx

I just re-did Puppy on this computer, with 214X-TOP8

Installed this Sylpheed pet.

When it starts up, it says there's a newer version, and do I want to update.

I've been saying no, because I don't know whether versions not specifically made for 214X will work.

Can someone please advise me on that?

Thanks a lot,

Sheldon

[ttuuxxx]

Here's the latest version of yad which is a offshoot of zenity which is a dialog program. Just open a terminal and type yad.
If you want to try a yad app then there is a a pupsave tool located at http://www.murga-linux.com/puppy/viewto ... 487#540487
and just make sure you drive is mounted where you want the new pupsave to be created first before running it.
ttuuxxx

[ttuuxxx]

Hi, all. Some snipping.

Here's the latest sylpheed-3 beta version
ttuuxxx

I just re-did Puppy on this computer, with 214X-TOP8

Installed this Sylpheed pet.

When it starts up, it says there's a newer version, and do I want to update.

I've been saying no, because I don't know whether versions not specifically made for 214X will work.

Can someone please advise me on that?

Thanks a lot,

Sheldon

Pet below for the latest version
ttuuxxx