tahrpup64 6.0.5 CE

[Sailor Enceladus]

I had no wireless (b43) so I made an fdrv with it's firmware from tahr32.

Nice to see a lot of updated programs like Palemoon 27.0.3.

Gparted shows all 3 partitions as one so I can't change their sizes but pmount shows them ok.

[prehistoric]

Now running tahrpup64 6.0.5.3, without proprietary Nvidia driver. Looks very good so far.

Created my own problem when I removed the previous save file. Even editing the kernel line to add pfix=ram without remembering to tell it psubdir=tahrpup produced a search for files in non-existent USB storage. This is what comes of doing a manual installation from the iso image without telling it all the details.

This is the relevant section of my latest GRUB multiboot menu.lst

Code: Select all

# Linux bootable partition config begins
  title Tahrpup 6.0.5 test (on /dev/sda2)
  root (hd0,1)
  kernel /tahrpup/vmlinuz psubdir=tahrpup
  initrd /tahrpup/initrd.gz
# Linux bootable partition config ends

It now picks up the save folder created in that first boot w/o problems.
Good thing it did not try to search everywhere, there is no telling what it might find. I have six different Linux installations.

[Snail]

I downloaded the ISO only. MD5sum OK.

I am using a Lenovo Thinkpad T400 Laptop, with no HDD, running from USB2 flash stick.

I created a /Tahr64-6053/ directory and copied my existing tahr64save FOLDER to it.

I copied initrd, vmlinuz, puppy_tahr64_6.0.5.3.sfs, the zdrv and tahr.png from the mounted 64-6053 ISO to /Tahr64-6053/. I placed a dummy text file, 64-6053 in /Tahr64-6053/tahr64save/, so I could check that the right save folder was being used.

I added the stanza for 6053 to menu.lst and re-booted into 64-6053. I got the message that the savefile was from Tahr64-605 and hit ENTER to accept the upgrade. The boot then proceeded without further intervention, or obvious error messages.

Unfortunately, on 3 subsequent re-boots, i keep being asked to hit ENTER to upgrade the save folder. On each boot,I have checked that the correct save folder is actually being used.

WIFI connects automatically.

On the desktop, the file icon is the default script icon, not the usual custom icon.
Pre-upgrade, I had two icons on the desktop linking to a couple of scripts I have written. These have vanished, although My-Applications/bin/ is still OK.

[Snail]

I decided to reboot 64-6053 to test sound. The boot froze after the message "booting kernel". I had to hard power-off. This has never happened to me before with this set-up.

I tried booting again and it worked, although i still have to hit ENTER to upgrade.

Sound works by the way.

[Snail]

Booted as above. WIFi connected using SNS no problem. Posting from it now. Sound works but very faint with the default settings. The desktop "file" icon is good.

[artsown]

Getflash still doesn't work. The getflash-1.6.pet is no longer useful because
of recent changes by Adobe. Unfortunatley, some videos out there still
require flash player.

I grabbed libflashplayer.so from Fatdog and copied it to
/usr/lib/mozilla/plugins It is version 11.2.202.644 which may hold me for
awhile. If I'm lucky, it will hold me until no videos require flash player

Art

[prehistoric]

Getflash still doesn't work. The getflash-1.6.pet is no longer useful because
of recent changes by Adobe. Unfortunatley, some videos out there still
require flash player.

I grabbed libflashplayer.so from Fatdog and copied it to
/usr/lib/mozilla/plugins It is version 11.2.202.644 which may hold me for
awhile. If I'm lucky, it will hold me until no videos require flash player

Art

Unfortunately, Adobe has already replaced flash player 11.2.202.644 with 24.0.0.186 which broke the Fatdog update flash script. Earlier versions have a serious vulnerability.

[artsown]

@prehistoric
Yes, it's best to install the latest vulnerabilities from Adobe I suppose
One becomes cynical after many years of updating vulnerabilities.

I'm curious to know if you hardened (spotified?) your browsers somehow
on tahr64?

Art

[prehistoric]

@artsown

Yes, I generally do run browsers as spot, but at the moment I don't remember which installation I was using on Tahrpup64 when I updated with getflash 1.6.

I would recommend using 24.0.0.186 until something better comes along because there were many vulnerabilities in earlier versions. I did have trouble with flash on one installation, indicating that someone was exploiting a vulnerability, but running as spot protected the rest of the system.

[Snail]

Testing with a save folder made by 6053.

I don't need to hit return to upgrade every boot, as happens when I try to use an "updated" 605 save folder.

Palemoon is now version 27.0.3. The problem of GoogleMaps restricting me to Lite mode has now been fixed.

In three different installations of Tahr64-605 and now this 6053 installation, the TahrPup welcome page seems to be riveted onto the starting tab. No amount of editing preferences seems to be able to change it. The only thing that did allow me to open Pale Moon to a blank page was when I ran the update and that had other, less desirable, consequences. As there is as yet no more up to date version than the one in the ISO, I can't check the updater at present.

[Snail]

In 6053, clicking on the button for the PPM Introduction that is in the Install Applications panel simply takes you to the Tahrpup64 jumping-off page. This is not all that helpful. Would it be better to go to the Howto for the PPM?

file:///usr/local/petget/help.htm

I would also like to suggest that the paragraph and link to Tahrpup's internal documentation should be at the very top of the Tahrpup64 jumping-off page, instead of right at the bottom, as it is at present. The current top link takes you to a very detailed but dated puppy website. The internal docs seem a lot better to me.

[torgo]

Sorry for the somewhat off-topic question, but seeing this I had to jump at the opportunity to ask...

The motherboard is an ASUS M2NPV-VM with integrated graphics most closely resembling early Quadros and sometimes designated as type 6150. Hardware-info describes this as NV4E.

Prehistoric - have you been able to get the component TV-out working in any version of Puppy? Or any version of Linux, for that matter?

I have three of these motherboards, and I'm wondering what it would take to get them to feed video through the component-out in Puppy, be it Precise or Tahr or Xenial or whatever. I haven't had any luck with it so far in Ubuntu.

[Pelo]

lazpaint is an application for both 32 and 64 bits, but i fail to launch it on tahrpup64, whatever the version.
I rarely use 64 bits Puppy. Because applications are not fun, old
Could somebody make a pet or SFS for Lazpaint 64 bits ?
"Image editor, like PaintBrush or Paint.Net, written in Lazarus (Free Pascal)."
"LazPaint
LazPaint Yes I appreciate any help. I am developping under Windows, however I apply adjustements so that it works well on Linux as well." Puppy Linux 32 bits (Slacko, Racy, and OBprecise ok) had no trouble with last version, and previous too.

[James186282]

A belated Merry Christmas to you all.

I'm having problems with USB 3 on my machine. I "think" the driver I'm supposed to see for this is the xhci driver? It doesn't seem to appear if I look for it with lsmod. There is a pet floating around that worked the first time I installed it but after that I get solid (good) messages about it finding the hardware but then

xhci_hcd 0000:01:00.0: Timeout while waiting for setup address command
xhci_hcd 0000:01:00.0: Stopped the command ring failed, maybe the host is dead
xhci_hcd 0000:01:00.0: Abort command ring failed
xhci_hcd 0000:01:00.0: HC died; cleaning up
xhci_hcd 0000:01:00.0: Timeout while waiting for setup address command
xhci_hcd 0000:01:00.0: Abort the command ring, but the xHCI is dead.
usb 4-4: device not accepting address 2, error -108

Not sure if this is connected but directly after the hardware is found I get this warning
fusbh200_hcd: FUSBH200 Host Controller (EHCI) Driver
Warning! fusbh200_hcd should always be loaded before uhci_hcd and ohci_hcd, not after

I tried the hardware info program and it sees
USB Controller VIA tech inc VL80x xHCI USB 3.0 Controller (rev 03) (prog-if30 [XHCI])

[jlst]

I notice that in this new version the "openssl version" is still 'OpenSSL 1.0.1f 6 Jan 2014' (same as the previous Tahr64 pup). Isn't this several versions ago of the latest openssl??? Do you happen to have the latest, updated version of openssl complied for Tahrpup64 (it's sort of important nowadays given the attack vectors by hackers)? Maybe so that we can download the latest as a pet and easily install it? Or do each of us--gulp--have to download the 'devx' files and then attempt to compile the latest openssl version for ourselves??

Again, mucho thanks for the latest Tahr64 pup!


P.S. [Edit] Wait, I remember Peebee explaining to me awhile back the crazy scheme ubuntu uses when updating something. Even when they update it, they still leave the same number. So maybe the openssl 1.0.1f is the latest??? Dang, wish I understood this stuff better. Now I know why Peebee said it is so much easier to grasp in Slacko---and it is!!! Slacko (like debian & the dogs), makes it flippin' simple to understand if you have the latest version of something, especially something important like openssl. If anyone knows the answer about this 1.0.1f version in the latest tahrpup64, would appreciate any feedback

I noticed that in ubuntu and debian.. apps require a specific version of a lib... and because they're compiling newer libs without recompiling the apps that depend on them... they keep the same name and stuff..

[radky]

removed - wrong thread

[James C]

Quick manual frugal test install of Tahr64 6.0.5.3.All good so far.

Code: Select all

root# inxi -Fxx
System:    Host: puppypc14195 Kernel: 3.14.79 x86_64 (64 bit, gcc: 4.8.4) 
           Desktop: JWM 2.3.6 dm: N/A Distro: tahrpup64 6.0.5.3
Machine:   Mobo: ASUSTeK model: M5A97 LE R2.0 version: Rev 1.xx serial: 150545593600028
           Bios: American Megatrends version: 2601 date: 03/24/2015
CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 42144.7 
           Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz 5: 1400.00 MHz 6: 3500.00 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 chip-ID: 10de:0a65 
           X.org: 1.15.1 drivers: nouveau (unloaded: vesa) tty size: 68x23 Advanced Data: N/A for root 
Audio:     Card-1: NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3 
           Card-2: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) 
           driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383 
           Sound: Advanced Linux Sound Architecture ver: k3.14.79
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller 
           driver: r8169 ver: 2.3LK-NAPI port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 1c:87:2c:5a:bb:e2
Drives:    HDD Total Size: 1120.2GB (-)
           1: id: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB serial: N/A 
           2: id: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB serial: N/A 
Partition: ID: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap 
RAID:      System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4 
           No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
           Unused Devices: none
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 128 Uptime: 13 min Memory: 313.9/15931.2MB Runlevel: 5 Gcc sys: N/A 
           Client: Shell (bash 4.3.42 running in urxvt) inxi: 1.9.17 

Code: Select all

root# free
             total         used         free       shared      buffers
Mem:      16313540      1062376     15251164            0        97588
-/+ buffers:             964788     15348752
Swap:      8396796            0      8396796
root# 

[LateAdopter]

I notice that in this new version the "openssl version" is still 'OpenSSL 1.0.1f 6 Jan 2014' (same as the previous Tahr64 pup). Isn't this several versions ago of the latest openssl??? Do you happen to have the latest, updated version of openssl complied for Tahrpup64

You can install the latest version from the ubuntu Trusty repo or download the package and then click on it in rox filer to install it.

The last update was 23 sept 2016
http://packages.ubuntu.com/trusty/openssl

WARNING: Ubuntu packages have not been tested on Tahrpup64. Occasionally I try one and it breaks Puppy. So make a test copy of Puppy and try it on that first. Usually they work properly because they are compiled for the exact versions in Trusty Tahr

[peppyy]

Hi All, Remember me? lol been using Puppy for years but the 64 bit has me a little befuddled.tahrpup64 6.0.5CE Fully updated and full hd install.

System HP Desktop A2512p Dual core/ intel/ intel graphics/ 4gb memory/ full install/ and the fastest times I have ever seen reported by hardinfo!

I built it to replace my better half's really old "XP" computer. and I only have a couple things to still workout.

#1 When right clicking a photo and setting it as desktop wallpaper it creates a new directory called x/x/x original. if you then set the desktop background from that folder it is called x/x/x Original Original and so on. Is this something I can change with rox or jwm or pinboard or other?

I downloaded Nathan's Wallpaper setter and it works well on 64 however it does not always show previews and it is tough for her to find the files she used to use without that.

#2 Is there a 64 bit image viewer available that allows her to print from the menu? I didn't want her to have to open Gimp every time and find the file she wants to print before printing a photo or Mandela etc. I have added the 32 bit libs but I can't seem to get any 32 bit apps to work. I noticed in the report that a lot were not installed. I think it was 400+ skipped files.
Edit: 400+ not 4000+
I will save my other questions for later, just wanting to keep the better half happy!

BTW, Great job on this version!

Perhaps I should start an up-to-date search engine?

[mikeslr]

If you've built applications by using debs available from Ubuntu repositories, you are probably familiar with Lazy Puppy's PaDS pet to combine debs into an SFS. My experience was that it didn't work under 64-bit Puppies.

I may have solved that problem: http://www.murga-linux.com/puppy/viewto ... 515#938515

mikesLr