Xenialpup64 CE 7.5 / 25 Nov 2017
Xenialpup64 CE 7.5
I installed to a 64gb flash drive for use on my HP desktop:
root# inxi -bw
System: Host: puppypc22238 Kernel: 4.9.65-x86_64 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: xenialpup64 7.5
Machine: Device: desktop System: HP product: 260-p029 serial: CNV6240BWP
Mobo: HP model: 81B4 v: 01 serial: PFPSK0BWJ301LW UEFI [Legacy]: AMI v: F.04 date: 05/10/2016
CPU: Dual core Intel Core i3-6100T (-HT-MCP-) speed/max: 800/3101 MHz
Graphics: Card: Intel Sky Lake Integrated Graphics
Display Server: X.org 1.18.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 150x23 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
Drives: HDD Total Size: 1064.7GB (0.5% used)
Weather: Conditions: 30 F (-1 C) - Mostly Cloudy Time: November 26, 11:14 AM EST
Info: Processes: 207 Uptime: 2 min Memory: 182.4/3878.8MB Client: Shell (bash) inxi: 2.3.8
root#
Installed applications with PPM.
I edited the menu.lst file:
kernel /xenialpup64-75/vmlinuz intel_pstate=disable psubdir=xenialpup64-75 pmedia=usbflash pfix=fsck
Changed kernels.
Thanks.
root# inxi -bw
System: Host: puppypc22238 Kernel: 4.9.65-x86_64 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: xenialpup64 7.5
Machine: Device: desktop System: HP product: 260-p029 serial: CNV6240BWP
Mobo: HP model: 81B4 v: 01 serial: PFPSK0BWJ301LW UEFI [Legacy]: AMI v: F.04 date: 05/10/2016
CPU: Dual core Intel Core i3-6100T (-HT-MCP-) speed/max: 800/3101 MHz
Graphics: Card: Intel Sky Lake Integrated Graphics
Display Server: X.org 1.18.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 150x23 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
Drives: HDD Total Size: 1064.7GB (0.5% used)
Weather: Conditions: 30 F (-1 C) - Mostly Cloudy Time: November 26, 11:14 AM EST
Info: Processes: 207 Uptime: 2 min Memory: 182.4/3878.8MB Client: Shell (bash) inxi: 2.3.8
root#
Installed applications with PPM.
I edited the menu.lst file:
kernel /xenialpup64-75/vmlinuz intel_pstate=disable psubdir=xenialpup64-75 pmedia=usbflash pfix=fsck
Changed kernels.
Thanks.
- Attachments
-
- screenshot.jpg
- (50.38 KiB) Downloaded 1370 times
congratulations
Congratulations Phil with the release of the final Xenialpup!
And thank you for the hard work. The result is very nice.
I don't have automatic wifi connection at startup. I try to set this up with sns. To solve this, I link rc.network in Startup. Another possibility would be to make a hotkey for rc.network in jwm, which gives me the choice of connecting or not.
And thank you for the hard work. The result is very nice.
I don't have automatic wifi connection at startup. I try to set this up with sns. To solve this, I link rc.network in Startup. Another possibility would be to make a hotkey for rc.network in jwm, which gives me the choice of connecting or not.
- Hesse James
- Posts: 106
- Joined: Mon 08 Feb 2010, 18:41
Xenialpup64 CE7.5 Nvidia driver
Hello
Concerning Nvidia-drivers for 7.5: I had compiled version 304.137 and 340.104 for Xenial64 7.0.8.6 (no patch necessary !!!) and thought to use them also in Xenial64 7.5. Despite the same Kernel number they don't work for me. I had to compile newer ones with Xenial64 7.5. That made it.
They contain only the 64bit libs, therefor the smaller size compared to the Pet packages.
If anybody want's to try them out, visit Shinobars Nvidia page:
http://www.murga-linux.com/puppy/viewto ... &start=140
Good luck.
Ah, one thing: Dougal's network wizard is back. Thank you.
Christian
Concerning Nvidia-drivers for 7.5: I had compiled version 304.137 and 340.104 for Xenial64 7.0.8.6 (no patch necessary !!!) and thought to use them also in Xenial64 7.5. Despite the same Kernel number they don't work for me. I had to compile newer ones with Xenial64 7.5. That made it.
They contain only the 64bit libs, therefor the smaller size compared to the Pet packages.
If anybody want's to try them out, visit Shinobars Nvidia page:
http://www.murga-linux.com/puppy/viewto ... &start=140
Good luck.
Ah, one thing: Dougal's network wizard is back. Thank you.
Christian
Xenialpup64 CE 7.5
I used UEFI Installer - Flash Drives to install to a 32gb SDHC card for
use on my Macmini.
root# inxi -bw
System: Host: puppypc17879 Kernel: 4.9.65-x86_64 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: xenialpup64 7.5
Machine: Device: laptop System: Apple product: Macmini6 1 v: 1.0 serial: C07JV98EDWYL
Mobo: Apple model: Mac-031AEE4D24BFF0B1 v: Macmini6 1 serial: C072496085YF1HCAG
UEFI: Apple v: MM61.88Z.0106.B03.1211161202 date: 11/16/2012
CPU: Dual core Intel Core i5-3210M (-HT-MCP-) speed/max: 1200/2501 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.4 driver: intel tty size: 188x30 Advanced Data: N/A for root
Network: Card-1: Broadcom NetXtreme BCM57766 Gigabit Ethernet PCIe driver: tg3
Card-2: Broadcom BCM4331 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 532.2GB (0.9% used)
Weather: Conditions: 36 F (2 C) - Overcast Time: November 26, 6:35 PM EST
Info: Processes: 206 Uptime: 2 min Memory: 188.2/16019.5MB Client: Shell (bash) inxi: 2.3.8
root#
I installed the usual applications and changed kernels.
I'm really enjoying the UEFI installer that allows running xenialpup64 on
my Imac and Macmini computers.
Thanks very much for this xenialpup64 final version.
use on my Macmini.
root# inxi -bw
System: Host: puppypc17879 Kernel: 4.9.65-x86_64 x86_64 (64 bit) Desktop: JWM 2.3.7 Distro: xenialpup64 7.5
Machine: Device: laptop System: Apple product: Macmini6 1 v: 1.0 serial: C07JV98EDWYL
Mobo: Apple model: Mac-031AEE4D24BFF0B1 v: Macmini6 1 serial: C072496085YF1HCAG
UEFI: Apple v: MM61.88Z.0106.B03.1211161202 date: 11/16/2012
CPU: Dual core Intel Core i5-3210M (-HT-MCP-) speed/max: 1200/2501 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.org 1.18.4 driver: intel tty size: 188x30 Advanced Data: N/A for root
Network: Card-1: Broadcom NetXtreme BCM57766 Gigabit Ethernet PCIe driver: tg3
Card-2: Broadcom BCM4331 802.11a/b/g/n driver: bcma-pci-bridge
Drives: HDD Total Size: 532.2GB (0.9% used)
Weather: Conditions: 36 F (2 C) - Overcast Time: November 26, 6:35 PM EST
Info: Processes: 206 Uptime: 2 min Memory: 188.2/16019.5MB Client: Shell (bash) inxi: 2.3.8
root#
I installed the usual applications and changed kernels.
I'm really enjoying the UEFI installer that allows running xenialpup64 on
my Imac and Macmini computers.
Thanks very much for this xenialpup64 final version.
- Attachments
-
- screenshot.jpg
- (78.96 KiB) Downloaded 1305 times
Just a suggestion for Quickpet.
Wine is listed for download.
To really get the full use of Wine.
Suggest to offer the wine_extras-v2.1.pet.
This provides menu entries for all the Wine support programs.
https://version2013.yolasite.com/page1.php#wine_menu
Wine is listed for download.
To really get the full use of Wine.
Suggest to offer the wine_extras-v2.1.pet.
This provides menu entries for all the Wine support programs.
https://version2013.yolasite.com/page1.php#wine_menu
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
hi bigpup,bigpup wrote:Xenialpup64 7.5
Frugal + save folder.
Did several downloads and installs to make sure was not bad download and install.
Tried this with both of the Quickpet Nvidia drivers.
Same results.
Tried to install the Nvidia drivers offered in Quickpet.
After the download, install, and reboot.
Pup-Sysinfo reports the Nvidia driver is being used.
Something is wrong.
glxgears will not run
nvidia x server settings will not run.
Get this error.
See image attached.
Trying to run nvidia-xconfig just totally breaks it.
Running xorgwizard
Selecting nvidia and correct settings.
Has no affect on solving the problems.
that's odd as the 380 driver from quickpet works for me.
have a look at /var/log/messages see if that sheds any light ... here's mine with a working driver
Nov 27 15:01:17 puppypc29681 user.warn kernel: nvidia: loading out-of-tree module taints kernel.
Nov 27 15:01:17 puppypc29681 user.warn kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 27 15:01:17 puppypc29681 user.warn kernel: Disabling lock debugging due to kernel taint
Nov 27 15:01:17 puppypc29681 user.notice kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Nov 27 15:01:17 puppypc29681 user.info kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 243
Nov 27 15:01:17 puppypc29681 user.info kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Nov 27 15:01:17 puppypc29681 user.warn kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 384.98 Thu Oct 26 15:16:01 PDT 2017 (using threaded interrupts)
Nov 27 15:01:17 puppypc29681 user.info kernel: [drm] Initialized
Nov 27 15:01:17 puppypc29681 user.info kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 384.98 Thu Oct 26 14:41:13 PDT 2017
Nov 27 15:01:17 puppypc29681 user.info kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Nov 27 15:01:17 puppypc29681 user.info kernel: nvidia-modeset: Allocated GPU:0 (GPU-fe88fbd9-5a3b-a28e-28fd-66538fa25ce3) @ PCI:0000:01:00.0
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
that's the cpu temp icon .... obviously doesn't support a virtual cpu you can disable it by moving /root/Startup/pmcputemp1 to the /disabled folders243a wrote:I just did a fresh install on a virtualbox on windows 8,1. A window pops up with the following error mesage:
"pmcputemp-0.63
unfortunately does not work on your system
(c) Michael Amadio
2015
GPLv2
"
I'm not sure if it has anything to do with xenialpup or not.
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Re: Xenialpup64 CE 7.5
hi Billtoo,Billtoo wrote:
The up-arrow isn't a problem because the 8 on the numeric keypad works like the up-arrow normally works and the up-arrow is great for taking screenshots
up arrow works fine here ... maybe it just happens with some keyboard layouts.
do you know if anyone's posted a fix for it anywhere?
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Re: Xenialpup64 CE 7.5
Hi Phil,666philb wrote:hi Billtoo,Billtoo wrote:
The up-arrow isn't a problem because the 8 on the numeric keypad works like the up-arrow normally works and the up-arrow is great for taking screenshots
up arrow works fine here ... maybe it just happens with some keyboard layouts.
do you know if anyone's posted a fix for it anywhere?
It happens on my mac uefi to flash drive installs, both use the aluminum mac keyboard.
Not a big deal, just have remember to use the 8 on the numeric keypad instead.
Thanks.
Re: Xenialpup64 CE 7.5
How could it get into Distrowatch?mavrothal wrote:Congratulations!!!666philb wrote:Xenialpup64 CE 7.5
built with woofCE testing
You would want to formally announce that in http://blog.puppylinux.com/
add a patch to update http://puppylinux.com/index.html#download to point to them
and alert BK to also put it in his blog.
Re: congratulations
hi foxpup,foxpup wrote:Congratulations Phil with the release of the final Xenialpup!
And thank you for the hard work. The result is very nice.
I don't have automatic wifi connection at startup. I try to set this up with sns. To solve this, I link rc.network in Startup. Another possibility would be to make a hotkey for rc.network in jwm, which gives me the choice of connecting or not.
yes there seems to be a problem with sns & frisbee failing to automatically connect,. network wizard is working fine though.
i've pm'd rerwin and asked him to take a look.
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Re: congratulations
666philb wrote:hi foxpup,foxpup wrote:Congratulations Phil with the release of the final Xenialpup!
And thank you for the hard work. The result is very nice.
I don't have automatic wifi connection at startup. I try to set this up with sns. To solve this, I link rc.network in Startup. Another possibility would be to make a hotkey for rc.network in jwm, which gives me the choice of connecting or not.
yes there seems to be a problem with sns & frisbee failing to automatically connect,. network wizard is working fine though.
i've pm'd rerwin and asked him to take a look.
Hi Phil,
I was just wondering, why isn't the whole process/idea behind 'Network Configuration' in Puppies solidified behind one network connection manager? For example, could not just 'Network Wizard' be made default, and permanently remove SNS and Frisbee. I've had horrible problems in the past (across Xenials, Slackos and others) where network profiles wouldn't be properly saved, and thus wouldn't start up, or SNS would conflict with Network Wizard, etc, etc.
I understand the puppy universe loves choice, but in this aspect, why everything has strayed from the K.I.S.S. principle seems to cause more headaches that necessary.
Just my $0.02
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
Re: congratulations
@belham2: I think getting rid of SNS would be the opposite of K.I.S.S. because it's the "Simple" choice (the name even says so ).
Re: congratulations
@sailor, lol, that's fine by me. I was just choosing one for an example, not advocating a choice. Figures I choose the one that someone jumps all over me about even though I actually do advocate itSailor Enceladus wrote:@belham2: I think getting rid of SNS would be the opposite of K.I.S.S. because it's the "Simple" choice (the name even says so ).
http://www.murga-linux.com/puppy/viewto ... 3cb8ef2f81
Saved file exists but not recognized
I installed xenial 64 puppy 7.5 today, tested in 3 computers. Everything is fine in 2 of them, wonderful version. However, in one PC, the saved file is made without problems, but after reboot, the system begins as if no saved file was present, and it is in the HDD.
The PC have 2 partitions, one for Windows 10 and one for ext4. I have tested with the Windows partition and with the ext4 partition, the same problem in both.
Previously, I worked with Precise puppy without issues to report.
Do you have an idea of what is happening? How can I solve this?
Thanks
The PC have 2 partitions, one for Windows 10 and one for ext4. I have tested with the Windows partition and with the ext4 partition, the same problem in both.
Previously, I worked with Precise puppy without issues to report.
Do you have an idea of what is happening? How can I solve this?
Thanks
Re: Saved file exists but not recognized
Providing some relevant info trigger ideas!morochos wrote:Do you have an idea of what is happening?
You can try the full report from pup-sysinfo though I think that the bootloader (grub4dos/grub2/LICK/other) options, the output of 'cut /proc/cmdline (just to be sure) and the /initrd/tmp/bootinit.log should give some idea.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
Re: congratulations
I think the reason for this variety of managers is the same difference between Windows users and Puppy users: -belham2 wrote:I was just wondering, why isn't the whole process/idea behind 'Network Configuration' in Puppies solidified behind one network connection manager?
Windows automatically finds connectable access points, asks you for password info, then FOREVER AFTERWARDS spends time "connecting, repairing connection, healing connection, restoring connection, troubleshooting connection" etc etc etc.
Puppy lets you bypass all that foofaa and set up your connection protocol however you want it.
The problem is when Puppy users get caught in the middle - they don't really understand how the connection with the router works (so they can't force their puppy to do the basics) and they don't really want to surrender their power to the operating system (as windows users do) so they install (or use) multiple managers in the belief that "more is better".
I think the answer is to identify "how to set up a connection" and separate it from "how to restore a connection that has problems".
Unfortunately the second of these problems varies from router brand to router brand.
Router manufacturers work closely with Windows but don't understand Puppy (or other small Linux variants) - so each puppy user ends up with a slightly different experience depending on their router.
I spent years unable to use SNS (had to use network wizard) until one day I was forced to swap my router and suddenly network wizard was less reliable and I have been forced to use SNS ever since.
I think we just need to ensure users understand that "making a connection" and "restoring a broken connection" are two different processes.
Last edited by greengeek on Wed 29 Nov 2017, 14:01, edited 1 time in total.
Re: congratulations
Just as an illustration: I have the same problem in the quirky/easy/pyro builds from Barry and there even my "rc.network in Startup" does not work, I have to redo the construction of the wlan0 profile every time anew.belham2 wrote: I was just wondering, why isn't the whole process/idea behind 'Network Configuration' in Puppies solidified behind one network connection manager? For example, could not just 'Network Wizard' be made default, and permanently remove SNS and Frisbee. I've had horrible problems in the past (across Xenials, Slackos and others) where network profiles wouldn't be properly saved, and thus wouldn't start up, or SNS would conflict with Network Wizard, etc, etc.
Well, it's almost puppy and it is not horrible