Xenialpup CE 7.5 / 25 Nov 2017

[Bird Dog]

@artsown

Thanks for the reply art but I couldn't figure out how to bookmark as cups.

@bigpup

Thanks for the reply bigpup,.I was in the applications chooser but looking for cups. The HTML viewer was set to autodetct so I changed it to palemoon and it works great. Thank you and Art for your help.

Thanks
Bird Dog

[jimcraven]

rerwin asked me to post a request for the ath9k driver in XenialPup 7.5 (32-bit).

You can read about my problem "Unable to get wireless to work on eeePC 1005HA, Puppy 7.5" at

http://www.murga-linux.com/puppy/viewtopic.php?p=976524

I'd be happy to test a new version with the ath9k driver on my Asus eeePC 1005HA with an Atheros Atheros AR9285 Wireless Network Adapter (PCI).

Thanks,
Jim Craven

[jimcraven]

As a follow up to my previous post regarding ath9k drivers, 666philb provided the solution. See the original post at
http://www.murga-linux.com/puppy/viewtopic.php?p=976787

[666philb]

Xenial 7.5 worked well on my IBM thinkcentre desktop

One small fault I noticed .....

I set up a samba server with Samba Simple managment
and by default the share folder is /mnt/home. (see image)

This doesn't exist by default so I had to create it.
___________________________________________

thanks don570,

i've re-uploaded the samba .pets so it'll be fixed in future builds

[666philb]

Xenialpup 7.5 fresh frugal install with fresh new save.

I am going to report this again, because I have seen several others reporting on this same problem.
Trying to use the Nvidia drivers in Quickpet.

I downloaded and installed the 380 driver.
It is suppose to be the one that supports my hardware. (340 will also)

After reboot driver is not working.

I noticed in startup there is no Nvidia file.
I copied one from another Puppy and rebooted.
(this may be a file Getnvidia makes)

On this boot up I got this error.
See image.

Update:
The next bootup after a complete shutdown.
Booted to screen with warning about x server was not shutdown cleanly.
Ran xorgwizard.
Selected the modeset driver and correct resolution.
Xwin
Booted to a working desktop and it was now using the Nvidia driver correctly, with everything working as it should.
What the @$&!*

That Nvidia file I put in startup could be what caused this to now work.

hi bigpup,

i've made some changes to the nvidia driver .pets. can you test these for me
32bit http://distro.ibiblio.org/puppylinux/pe ... 5-i386.pet
64bit http://distro.ibiblio.org/puppylinux/pe ... x86_64.pet

[666philb]

I'm reporting this here because Xenialpup-7.5 is the most prominent pup affected but this bug also affects 64-bit XenialPup64-7.5 and Slacko-6.9.9.9 both 32 & 64bit. (Does not affect Dpup-Stretch from @radky as that is using an older version of Gnumeric from Precise).

The way to see the bug is to open Gnumeric spreadsheet and put some data into a column. Select the cells containing the data then goto "Search & Replace" in the "Edit" menu.

Search for an item of data and replace by something different - choose Scope=Range. (see attached)

Click "Apply" and Gnumeric instantly crashes with an error like:
(gnumeric:19877): GLib-ERROR **: gmem.c:328: overflow allocating 4294967295*8 bytes
Trace/breakpoint trap

The bug is caused by goffice rather than Gnumeric, and can be cured by reverting the version of goffice to the Wheezy version (for 32-bit systems ***):
http://distro.ibiblio.org/puppylinux/pe ... 0.8.17.pet

32-bit Versions which exhibit the bug include:
http://distro.ibiblio.org/puppylinux/pe ... 7-i686.pet

http://distro.ibiblio.org/puppylinux/pe ... 6_s700.pet

[added-10-dec]
64-bit with bug:
http://distro.ibiblio.org/puppylinux/pe ... pril64.pet

*** Unfortunately, an equivalent fix for XenialPup64 has not been found.

thanks peebee,

using ubuntu's goffice fixes it, .... bugfix coming!

[don570]

I reported to BarryK about problems with the probedisk command

http://murga-linux.com/puppy/viewtopic. ... 680#976680

Xenialpup was one of the distros I had problems with.
____________________________________________________

[bigpup]

hi bigpup,

i've made some changes to the nvidia driver .pets. can you test these for me
32bit http://distro.ibiblio.org/puppylinux/pe ... 5-i386.pet
64bit http://distro.ibiblio.org/puppylinux/pe ... x86_64.pet

So far I tried the 64 bit one for Xenialpup64 7.5.
No help.
It still does not bootup using the driver correctly.

I noticed the driver pets that seem to work have this file nvidia loaded into the startup directory.
This pet did not have this file or did not put it into startup.
File attached.
Remove the tar from name to see the actual nvidia file.

Update:
I put this nvidia file in startup and rebooted.
Got to a desktop with the correct resolution, but the mouse was frozen up.
So that file helped, but not 100% good.

Update, update:
Tried the one for Xenialpup 7.5 (32bit)
The same problems as above.
So, this one did not work.

[charlie6]

Hi Phil,

on this 7.5 version, gnumerics preview reports in terminal:

Code: Select all

root# gnumeric
/usr/bin/evince: line 13: exec: epdfview: not found

as qpdfview is the onboard pdfviewer, just made the following symlink to fix it !

Code: Select all

ln -s /usr/bin/qpdfview /usr/bin/epdfview

(to mention:
1) on previous versions, it happened that gnumeric asked for evince-previewer; now it claims for epdfview ; now it is evince that claims for epdfview instead of evince-previewer;
2) this xenialpup-7.5 runs like a charm ! )

HTH and have a nice day whatever the weather today !
charlie

[proebler]

A curious experience with a xenialpup-7.5 frugal install to USB flash with Grub4Dos boot loader.
I created a small savefile to preserve the localization and some Rox filer options.
I did this on an HP 6930p laptop, then used the USB on an HP-8200 desktop.
It boots on the desktop, using the savefile, but both keyboard and mouse are inactive.
All I can do is to use power off in order to shut down.

I rebooted with pfix=ram, no problem, keyboard and mouse are working ok.
So I then created a new 2nd small savefile, again with settings for localization and Rox options.
With this second savefile I can now boot both on the desktop and on the laptop.

The initial 1st savefile appears to contain machine specific information which makes it unsuitable for the desktop.
I don't think that I have experienced such a thing with a Puppy before.
What is going on?

[bigpup]

What format is the partition the save is on?

[proebler]

What format is the partition the save is on?

the partition is FAT32

[don570]

I created a small savefile

The name of the save file is important if it is stored on a FAT32 partition
because FAT32 doesn't allow certain symbols like ":"

Avoid these...

" * ? . , ; : / \ | + = < > [ ] signs

___________________________________________________

[proebler]

I have now used the USB on two more machines; I booted with pfix=ram and then crated savefiles in the same manner as described in my previous post.
The machines are a HP P4 desktop and a HP 8460p laptop (i5).

Now I have 4 very similar savefiles to use.
Two were created on (different) laptops, the other two were created on (different) desktops.
All 4 savefiles were created from the same system xenialpup-7.5 , run from the same frugal install on the one USB and saved to the same FAT32 partition on that USB.

On the two laptops all 4 savefiles work together with the base system.

On the two desktops the two savefiles created on desktops work together with the base system.

On the two desktops the two savfiles created on laptops will lead to a booted system with no input possible from either keyboard or wired (USB) mouse.
That the savefile does get loaded is evident from the desktop appearance and also from the way the (forced) shutdown takes place when the power button is pressed.
Meaning, that the option whether to save or not to save is presented (having set the system up in that way).
It is interesting to note, that at that point the keyboard does become active, i.e. allowing me to use arrow and Enter keys.

The kernel line I use is pmedia=atahd pfix=fsck psubdir=/some_subdir

No disallowed characters are used in the name of the savefile(s).

[mikeslr]

I'm surprised that bigpup hasn't responded yet. Perhaps he was exaggerating when he told me he never sleeps. At any rate, he --or someone else-- may be able to provide a better understanding of what may have caused your 'curious experience'.

Edited: wrote laptop a couple time meaning to write USB-key.

Xenialpup's system resides on your USB-Key. The SaveFiles you create on a laptop don't work when you try to use them on a desktop.

According to your last post, "The kernel line I use is pmedia=atahd pfix=fsck psubdir=/some_subdir ".

If I take this at face value, that's the kernel line you have on your USB-Key used for your laptop. I have to wonder how you created them. If you installed grub4dos to your usb-key and ran it to create a menu.lst on that key, it would have created a kernel line like the following:

pmedia=usbflash pfix=fsck psubdir=/some_subdir ## emphasis supplied.

With pmedia=atahd as the boot argument on a USB-Key, I would have expected that the effect would have been either to prevent booting or to ignore that improper argument when booting from the USB-Key. But, perhaps it did more, somehow enabling you to boot while instructing Xenialpup that you have a peculiar system. That peculiarity may have been incorporated into the Savefile. When you later try to boot using the SaveFile lacking that peculiarity, the curious effect you noticed may be the result.

Just guessing.

Try creating a SaveFile from your Laptop after booting into it with the kernel argument

pmedia=usbflash pfix=fsck psubdir=/some_subdir

and see if that SaveFile is usable on your Desktops.

Alternatively, don't include your customizations of rox in the SaveFiles you create on your laptops and see if such SaveFile is usable on your Desktops.

mikesLr

[bigpup]

My guess!

Installed on a USB flash drive.

A normal kernel line for Tahrpup installed as a frugal install in a directory named:
tahr606uefi

All the Tahrpup files are in this directory, including the save.

Code: Select all

kernel /tahr606uefi/vmlinuz   psubdir=tahr606uefi pmedia=usbflash pfix=fsck

Notice the order of the options!

The saves you made on the laptop could have some, specific to the laptop, hardware setup in the save.
It could have settings for the touchpad.
These would be very specific settings.
Desktops do not have touchpads.
But this save could be looking for one and think that is all it should have to find.

The desktop save is going to also have hardware settings, but they are going to be more general in nature. Not so specific.
Desktops are not that different in the general hardware setup.
(this is a keyboard, this is the mouse. that is about it)
It looks for things like touchpads, because nothing is telling it not too.

Why the desktop save will work in everything could be because it is setup, with general settings, that work on a lot of different hardware.

Note:
Usually using a save from one computer to another.
The hardware setup is the troublesome thing.

[proebler]

mikesir's

The SaveFiles you create on a laptop don't work when you try to use them on a desktop

and
bigpup's guess

The saves you made on the laptop could have some, specific to the laptop, hardware setup in the save.
It could have settings for the touchpad.
These would be very specific settings.
Desktops do not have touchpads.
But this save could be looking for one and think that is all it should have to find.

are likely to be correct.
I have placed the files for a frugal slacko-6.9.6.4 into a separate directory on the same USB.
Then went on to run and create savefiles for that slacko on the P4 and on one of the laptops.
The result is the same as with xenialpup-7.5, i.e. no keyboard and no mouse available on the desktop machines, when the savefile created on the laptop is used.

I should have posted this probably in House Training > Users instead of here on the Xenialpup CE 7.5 topic. My apology.

Also, I made a mistake when I wrote that I use pmedia=atahd in the kernel line of the Grub4Dos menu.lst.
I am actually using pmedia=ataflash. My usage of this comes from forcing Pupmode 13 with frugal HD installs.
With a USB flashdrive, both pmedia=ataflash and pmedia=usbflash seem to work.
Following mikesir's suggestion I have created savefile(s) after booting with
pmedia=usbflash pfix=ram psubdir=/some_subdir
it made no difference.

I may do one more thing, when I have some time, change from Grub4Dos to simply Grub.

Thanks to all for your help.
proebler

[redandwhitestripes]

In xenial pup 32 I can't mount my xfs partition. Xenial pup 64 is OK for me, but my drives on my 64 bit desktop don't include xfs. From searching and scanning this thread, I see there are other hitches related to drive-mounting but the discussion is a little too abstract for moi

I'll stick with Tahr until that hitch is solved. Xenial looks great, though!

[rufwoof]

SneekyLinux Xenial pup video https://youtu.be/N2K1NVLFFZw

[mavrothal]

In xenial pup 32 I can't mount my xfs partition. Xenial pup 64 is OK for me, but my drives on my 64 bit desktop don't include xfs. From searching and scanning this thread, I see there are other hitches related to drive-mounting but the discussion is a little too abstract for moi

This has nothing to do with drive mounting "problems"
Xenial kernels are not configured to include the xfs module.
Maybe try another kernel till a new one is provided for Xenial

Edit
...or you can make the module and insert it as such:
Make sure you load devx and kernel_source SFSs
then in the terminal type (copy/paste)

Code: Select all

cd /lib/modules/$(uname -r)/build/
zcat /proc/config.gz > .config
make oldconfig
geany .config

In geany find the line with
"# CONFIG_XFS_FS is not set"
and change it to
"CONFIG_XFS_FS=m"
savefile and close.
Back in interminal type

Code: Select all

make prepare #Accept the defaults in all the questions
make modules_prepare
make SUBDIRS=scripts/mod
make SUBDIRS=fs/xfs modules
mkdir -p /lib/modules/$(uname -r)/kernel/fs/xfs
cp -a --remove-destination fs/xfs/xfs.ko /lib/modules/$(uname -r)/kernel/fs/xfs/
depmod -a
modprobe xfs

You can add the last line in your /etc/rc.d/rc.local to be loaded in every boot so xfs will work
You will also need to install xfsprogs with PPM

Edit 2
...or just isntall the attached pet (and xfsprogs from PPM)