tahrpup 6.0.5 CE

[mories]

su spot is working for me in both PAE and noPAE, do you get the same if you boot live?

In live CD (pfix=ram) "su spot" working properly.
I have delimited the problem was in one of my customizations, using "unsquashfs -d / -f some.sfs" seems affects the properties of some directory (although I see I have permissions similar to the situation in live cd).
Thank you for your attention and sorry for any inconvenience.

[bigpup]

Hi y'all, graphics are failing (fails with distorted out of scale overlapping double image of text; doesn't reach gui) when trying to boot tahrpup on a Compaq Presario F700 (F767CL) laptop w/ an onboard nvidia card (NVIDIA GeForce 7000M). Happens with both default and vesa.

Try this:
At Puppy boot screen hit F2 key
Use boot option puppy pfix=nox
This should boot to a prompt.
Type xorgwizard
In xorgwizard choose the modeset driver.
Select a resolution you know should work.
Finishing xorgwizard
At the prompt type xwin

What happens?

[bigpup]

I got Wine working in Tahrpup 6.0 CE

Basically do what is stated here.
http://murga-linux.com/puppy/viewtopic. ... 510#794510
For the Wine version get the latest pet.
One of the links is bad, but you can get everything from here:
http://version2013.yolasite.com/page1.php#mpg123

After installing everything go to menu->Utility->Wine config

Make sure to select drivers tab and choose autodetect to setup all the drive locations.

Go to Wine web sit to learn about and how to use.
https://www.winehq.org/

[kevjonesin]

Try this:
At Puppy boot screen hit F2 key
Use boot option puppy pfix=nox
This should boot to a prompt.
Type xorgwizard
In xorgwizard choose the modeset driver.
Select a resolution you know should work.
Finishing xorgwizard
At the prompt type xwin

What happens?

After entering

Code: Select all

puppy pfix=nox

at boot things went to the same out of scale double-vision view of the terminal prompts on the laptop's native (1280x800) screen but I happened to have an external LCD monitor attached as well and it came up with a legible mirrored view. Was able to run 'xorgwizard' and follow prompts and got to GUI mirrored cleanly on both native and external at 1024x768 . But tty1–tty3 CLI (via <ctrl>+<alt>+<Fx>) still came up doubled and out of scale on the native screen.

Separate issue, default save menu at shutdown presumes boot USB stick partition only and won't let me choose another (hdd) partition for creating a pupsave file. [I'd previously installed tahrpup frugal to a netbook partition via 'Universal installer' along with grub4dos after encountering the same lack of save choices.] Is this a known bug? Are there other workarounds?

[bigpup]

Was able to run 'xorgwizard' and follow prompts and got to GUI mirrored cleanly on both native and external at 1024x768

1024X768 is probably the closest resolution this driver can give you.

Try this while you are in a working GUI. I assume that is a working desktop.

Run Quickpet->Drivers tab
Click on Nvidia web site
Find out what driver they recommend for your hardware.
Download and install that driver
Change to using that driver

When booting from a USB flash drive the save process presumes you want to save to the flash drive so that everything is on that drive.
The idea is you take it from computer to computer and everything will be on that flash drive.
Also, it makes no changes to the computer you run it on.
Most flash drives will have free space to put the save file/directory, so why not use it.
Also, when running from a USB flash drive the save process works to limit the number of writes to the drive.
You can still save any data to the hard drive. It will just not be in the save file/directory.

If you really want to have Puppy on the hard drive. It is better to do a frugal or full install, to the hard drive, and run it from there. There are things being done to take advantage of what that setup provides, that a flash drive install can not.

[mikeslr]

Hi 666philb & All,

I'm running tahrpup 6.0 nonpae and find it to be the Pup I most frequently boot into. It boots fast and seems to start my apps faster than others. Great job, 666philb.

This is a frugal install which has worked without a problem for a couple of weeks. Recently, however, when I plug in a USB-Key, although it will both automatically mount it and initiate rox to show the files and folders, after I close that window clicking the desktop drive icon only brings up pmount. It doesn't initiate rox.
This may not be a tahr problem. I may have played with the settings. But if I did I can't figure out how to undo whatever I did.
Any suggestions?

mikesLr

[gyro]

clicking the desktop drive icon only brings up pmount. It doesn't initiate rox.

I've seen this problem before.
My workaround is to delete the corresponding rox-app in "/root/.pup_event" and reboot.
I can't remember if it was in tahr, and I think it was for a hard drive partition.
Unfortunately, whenever I've seen this I've never been in the mood to try to debug the problem, just do the workaround and get on with things.

gyro

[Gyle]

A workaround I tested recently is to disconnect all the USB devices and connect only those concerned with the boot sequence directly on the machine and NOT via a hub.
For me it seems it is a problem of bad management of Interrupt Requests (IRQ n#...).
On my config a USB CDRom device fueling successfully the live tahrpup 6.0 CE is iconified on the desktop and the clicking brings up pMount but the cdrom is not visible in the pMount app so it is not recognised by pMount and rox cannot be launched.
Same problem with a live USB drive. Same workaround. It seems that the order or the number of the IRQ's is not well managed at the boot by pMount, depending on may be a pecular hardware or a bad timing with IRQ's.
Now, on my laptop, keyboard and mouse are plugged in a hub, and the live USB CDRom device or the live USB hard drive and other USB devices are plugged in the laptop's USB ports. All works fine.
But, if the pMount app shows the CDRom as sr1 and initiating Rox, it does not show the other USB devices like sdb1, sdb2.
although clicking these USB devices iconified on the desktop initiates Rox.
The partitions on the HD are OK.

I saw already this issue in a recent pup distro, I don't remember, and the live CD was fired via a USB CDRom device, not the laptop's CDRom.
At the end of the session the choice of the device where to write the pupsave was only sr1, identified as the laptop's CDRom device, although there was no CD in. The USB CDRom fueling the live CD was not recognised as sr2.

[mikeslr]

Hi 666philb, gyro & All,

Thanks gyro for the work-around. And thanks Gyle for joining the discussion.
I've also had it happen before; I think running tahrpup, but perhaps not.
Actually I had pretty much decided to see how the pae kernel would do on the computer, so switching over was my "work-around". But I've bookmarked gyro's instructions should the problem show up again.
Since the problem wasn't just "me" and Gyle has pointed out it is of a more general nature, I hope that 666phib or the guys at github have the opportunity to seek a fix.
Puppies should do what is expected of them.

mikesLr

[gjuhasz]

clicking the desktop drive icon only brings up pmount. It doesn't initiate rox.

Please find below a workaround tested in (the Tahr-based beta version of) Puli. Commenting out Line 226 in /usr/local/bin/drive_all script helps:

• # =false always start Pmount.
  if [ "$AUTOTARGET" = "false" ];then
  if [ "`pidof gtkdialog_pmount`" != "" ];then #if pmount running, kill it.
  killall gtkdialog_pmount 2>/dev/null
  sleep 0.1
  fi
  # exec pmount $DRV_CATEGORY
  fi

However, note that this is a temporary fix. The root of the problem seems to be buried deeper. So, don't hesitate to find a better solution.

The drive_all script is buggy anyway (consequently, AppRun scripts of drive icons are bad, too). For example, even if a running gtkdialog_pmount is expected to be killed in the above code segment, it keeps running. In contrast, the same code segment kills gtkdialog_pmount if typed in a terminal window.


Have fun!

regards,

gjuhasz

[mariojrmatos]

I am trying to increase Puppy's save file but so far I've been unsuccessful.

I've tried the Puppy Resize method, forcing it through the terminal and writing the desire size on the resize .txt file itself but Puppy just doesn't apply the changes.

I'm using 6.0 tahrpup CE (frugal install to a USB stick).


Am I doing something wrong or is this a bug?

[torgo]

will new palemoon versions come through quickpet?

If you go to the Pale Moon web site and download the PaleMoon For Linux version and unzip it (anywhere - it doesn't have to be in your save file), what you get is a .sh file.

Click on that and choose to update Pale Moon. It will then pull in the latest version and update for you.

If anyone is wondering, Pale Moon has hit version 25.1.0, so it's probably worth it to do the update.



CAUTION: on at least one machine (I think two - just not sure if they were different ones or the same one twice), I found that updating Pale Moon or adding any other browser before installing Flash led to all kinds of problems when I tried to add Flash later.

If I load Flash first and THEN install or update the browsers, everything is fine. But if I load Flash after updating/installing, it causes all the browsers to crash. The browsers then work fine after I uninstall Flash. But reload Flash - any version - and they crash again.

I have absolutely no idea what the reason is for that. I might try investigate further this weekend, but first I have a whole lot of other items to check into.

[torgo]

I have tried Tahr 6.0 on two motherboards (different manufacturers) that have ATI Radeon 3000 graphics on the board.

I have been using Precise 5.7.1 on those same systems, selecting the "radeon" driver in XorgWizard (instead of "ati"), and everything is fantastic.

But in Tahr, XorgWizard doesn't even show "radeon" as an option. The only non-generic driver that shows up is the "ati" one.

That one has major problems in XorgWizard in Tahr - it gives you the "click OK if you can read this" screen, but after you click OK, it freezes up. You have to reboot and choose to fall back to a previous xorg.conf file to salvage your save file, (That doesn't happen with the ati driver in XorgWizard in Precise.)

Tahr does load the ati driver as the default (just don't run xorgwizard), but the performance is not as good as with the radeon driver in Precise.

I have also noticed that NVidea chipsets only list "nouveau" in the Tahr version of XorgWizard, where the Precise version also lists "nv" as an option. The only generic option listed in Tahr's XorgWizard is "modesetting", with "vesa" missing.

Anyone else using on-board Radeon 3000 graphics? Does anyone know if all this might be happening because of different Linux kernels, or changes in XOrgWizard? Or is it a Tahr thing?

[gcmartin]

As @Torgo shares earlier, Flash's positioning in installation is key to error free use of all subsequent browsers.

Since Flash is SO ubiquitous, why do we insist on making users add this. Why not include and offer a Menu option to remove for those experienced users who would not want it. The RAM cost is miniscule, at best.

Just an idea for development's consideration as it reduces development suipport research while at same time increasing overall benefit to the many..

[jlst]

I have also noticed that NVidea chipsets only list "nouveau" in the Tahr version of XorgWizard, where the Precise version also lists "nv" as an option. The only generic option listed in Tahr's XorgWizard is "modesetting", with "vesa" missing.

Anyone else using on-board Radeon 3000 graphics? Does anyone know if all this might be happening because of different Linux kernels, or changes in XOrgWizard? Or is it a Tahr thing?

I have an answer to this.

1) depending on your machine, you may have to wait at least 20 seconds and then CTRL+ALT+BACK
2) then run xorgwizard

That's how the savage driver detection happens here, you have to wait patiently.


---

The 'nv' driver was compiled in Precise Puppy I think, it wasn't part of Xorg anymore.. at least in Ubuntu.

It still can be used if you compile it, but I guess you can use the precise version and you add the IgnoreABI option to the xorg.conf file, ServerFlags Section

Section "ServerFlags"
Option "IgnoreABI" "true"

---

Xorgwizard is not really that important anymore.

I think Xorg is wise enough to load the correct driver. How do I know that?

Because I tested 4 graphic cards (besides integrated graphics), using a modified xorg.conf. Xorg did not fail to detect and load the correct driver for each one of them (even in the first boot).

Xorg works perfectly in Precise Puppy. it changed after that. So Precise Puppy must be kept alive.

This is my current xorg.conf-auto-pc (/etc/X11)

Code: Select all

#barry Kauler 2011
#pre-constructed xorg.conf, for use by /usr/sbin/xorgwizard-automatic
#110627 working on mageia1 build, this needs fixing.
#111029 Terryphi reported 1cm screen displacement, changed vert freq range from 56-76 to 59-76.
#120329 more placemarkers for xorgwizard-automatic script.
#121013 change depth from 16 to 24. note, some arm boards need 16.

#--- changes for precise puppy 5.7.1 ---
# Remove /etc/X11/xorg.conf from main SFS and
# Replace /etc/X11/xorg.conf-auto-pc with this file
#
#jlst: xorg fails to start automatically in integrated graphics (2003-2005) 
# 		and VERY old graphic cards (1997-1999)... the ones I tested
#  removing these settings fixes the issues:
#	HorizSync    35-81 -> #HorizSync	35-81
#	VertRefresh  59-76 -> #VertRefresh	59-76
#jlst: xorg does not obey this setting
#		Modes       "1024x768x16"
#	Must remove 'x16'
#		Modes 		"1024x768"
#jlst: Depth 24 does not always work properly, 
#		I think it's better to change it to 16 for the retro flavour
#----

#### Tweaks and more tweaks for tahrpup/ubuntu trusty to gain some speed ####



# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
#	Load "synaptics" #loadsynaptics

# This loads the DBE extension module.
	
    Load    "dbe"  	# Double buffer extension
#	Load 	"xaa"
    

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
#    Load        "freetype"

# This loads xtrap extension, used by xrandr
#    Load       "xtrap"

# This loads the GLX module (if present). xorg 7.4/5, need explicit disable to disable... change "Disable" to "Load" if reqd...
#    Disable       "glx" #LOADGLX

# This loads dri module (if present). 7.4 loads it by default, have to disable... change "Disable" to "Load" if reqd...
#    Disable       "dri" #LOADDRI

EndSection

# **********************************************************************
# Files section.  This allows default font paths to be set
# **********************************************************************

Section "Files"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

    #FontPath   "/usr/share/fonts/X11/misc/"
    #FontPath   "/usr/share/fonts/liberation/"
    FontPath   "/usr/share/X11/fonts/misc/"
    FontPath   "/usr/share/X11/fonts/Type1/"
    FontPath   "/usr/share/X11/fonts/TTF/"
    FontPath   "/usr/share/X11/fonts/default"

EndSection

Section "Extensions"
#	Option "Generic Events" "Disable"
#	Option "Composite" 		"Disable"
#	Option "DAMAGE" 		"Disable"
#	Option "DOUBLE-BUFFER" 	"Disable"
#	Option "DPMS" 			"Disable"
#	Option "GLX" 			"Disable"
#	Option "MIT-SCREEN-SAVER" "Disable"
#	Option "MIT-SHM" 		"Disable"
#	Option "RANDR" 			"Disable"
#	Option "RENDER" 		"Disable"
#	Option "SECURITY" 		"Disable"
#	Option "X-Resource" 	"Disable"
#	Option "XFree86-DGA" 	"Disable"
#	Option "XFree86-DRI" 	"Disable"
#	Option "XFree86-VidModeExtension" "Disable"
#	Option "XFIXES" 		"Disable"
#	Option "XINERAMA" 		"Disable"
#	Option "SELinux" 		"Disable"
#	Option "XTEST" 			"Disable"
#	Option "XVideo" 		"Disable"
EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

	Option "IgnoreABI" "true"
#	Option "DRI2"	   "true"
	
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

    Option "RandR" "on"

# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...

    Option "AutoAddDevices" "false"

# For no-Hal, kirk also suggests this...

#    Option "AllowMouseOpenFail" "true"

# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...

    Option "DontZap" "false"

EndSection


Section "ServerLayout"
#	InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option      "XkbRules" "xorg"
	Option      "XkbModel" "pc102" #xkbmodel0
	Option      "XkbLayout" "us,es" #xkeymap-0
	#Option      "XkbVariant" "" #xkbvariant0
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2" #mouse0protocol
	Option	    "Device" "/dev/mouse"
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
	#HorizSync    35-81
	#VertRefresh  59-76
	#UseModes     "Modes0" #monitor0usemodes
	Option      "PreferredMode" "1024x768" #monitor0prefmode
	EndSection
	
Section "Modes"
	Identifier "Modes0"
	#modes0modeline0
EndSection

#110627 remove...
##server can find BusID automatically, comment out...
Section "Device"
	Identifier  "Card0"
#	Option "AccelMethod" "xaa"
#	Option "NoAccel" "true"
#   Option     "ShadowFB"		"false"    	# [<bool>] savage
#	Option     "DisableXVMC"	"true"     	# [<bool>] savage
    Option     "DisableTile"	"true"     	# [<bool>] savage
#	Option     "DisableCOB"		"true"     	# [<bool>] savage
#	Driver      "vesa" #card0driver
#	VendorName  "Unknown Vendor"
#	BoardName   "Unknown Board"
#	BusID       "PCI:0:2:0" #card0busid
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth 16
	#Option         "metamodes" "1280x800_60 +0+0" #METAMODES_0
	Subsection "Display"
		Depth       16
		Modes       "1024x768" #screen0modes
	EndSubsection
EndSection

[torgo]

That actually touches on the workaround that I found for my particular machines - I booted from the Precise cd and made a fresh save file after using the Precise xorgwizard to configure the video with the radeon driver.

Then I copied that xorg.conf file into my Tahr setup.

[torgo]

*** EDIT *** still testing this - had to hard power off when xorgwizard failed, which might have corrupted something on the ssd partition that is causing the failure.

Issue: on some ASUS motherboards, the system is not allowing me to create a save file/folder, claiming that no partitions were found and automatically rebooting without saving.

[666philb]

I am trying to increase Puppy's save file but so far I've been unsuccessful.

I've tried the Puppy Resize method, forcing it through the terminal and writing the desire size on the resize .txt file itself but Puppy just doesn't apply the changes.

I'm using 6.0 tahrpup CE (frugal install to a USB stick).


Am I doing something wrong or is this a bug?

menu>>>utility>>resize personal storage

note that if you are using a save folder this is not needed

[gyro]

clicking the desktop drive icon only brings up pmount. It doesn't initiate rox.

I've just seen this problem again, and even though it wasn't tahr, I did a little investigating this time. And the result might provide a simpler work around, and might point to where the problem actually resides.

In this case the arguments contained in the icon were wrong. They were "drive vfat" when they should have been "drive ext4". Once I edited the arguments in the icon, it worked perfectly. So, maybe the problem is with the code that creates the icons, rather than 'drive_all' itself.

Next time you have this problem, try checking the icon arguments. Right click on the icon and select "Edit Item", it's the second field.

gyro

[mariojrmatos]

menu>>>utility>>resize personal storage

note that if you are using a save folder this is not needed

Thank you, 666philb

However, I already did it using the "resize personal storage" tool. That's what I meant when I said "I've tried the Puppy Resize method". Sorry.

I am not using a save folder, though. I have the regular pupsave created after the installation onto the USB stick.
The content of my pupsave consists only of installed programs (original packages and installed by me) and software preferences (namely Puppy's). The remaining files, including SFS files, are stored outside the save file (/mnt/home/FOLDER)
I have about 1.9 GB free on my personal storage space/savefile but I still need to install a couple of programs, and, of course, leave some free space for cache and other regular tasks that usually need some wiggle room on the storage front.

Do you have other suggestions to bypass/solve this barrier?