Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 17 Oct 2017, 00:14
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Xenialpup64 7.0.8.4
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 16 of 26 [381 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16, 17, 18, ..., 24, 25, 26 Next
Author Message
artsown

Joined: 12 Sep 2012
Posts: 232

PostPosted: Mon 17 Apr 2017, 08:33    Post subject:  

Why was this thread moved to Puppy Derivatives?

Art
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1163
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 18 Apr 2017, 02:45    Post subject:  

Hi Phil, thanks for your reply !

Quote:

...
b43 was requested earlier in the xenialpups thread and is probably blocking your wireless driver.

try blacklisting it in ...menu>>system>>bootmanager


I did it but no success Sad
I indeed already had "blacklisted" b43 by editing /etc/rc.d/MODULESCONFIG and copying wl.ko to /lib/modules/4.9.15/kernel/drivers/net/wireless
as forum member ozsouth does (see http://murga-linux.com/puppy/viewtopic.php?p=921110#921110)
So, b43 is not longer listed in lsmod report nor in the bootmanagers modules list.

Charlie
Back to top
View user's profile Send private message 
riedzig

Joined: 01 Oct 2015
Posts: 25

PostPosted: Tue 18 Apr 2017, 03:06    Post subject:  

Hi bigpup,
I checked everything, moved it all under /mnt/home and got the same error
Quote:
ERROR: Unable to load the kernel module.


ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find
suggestions on fixing installation problems in the README available
on the Linux driver download page at www.nvidia.com.

nvidia: loading out-of-tree module taints kernel.
nvidia: module license 'NVIDIA' taints kernel.
nvidia: module verification failed: signature and/or required key missing - tainting kernel
NVRM: DRM init failed
See also 'nvidia-installer.log'
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9372
Location: Charleston S.C. USA

PostPosted: Tue 18 Apr 2017, 05:59    Post subject:  

What is the specific Nvidia hardware?

Yes, the SFS packages and the Nvidia run package all need to be in /mnt/home.

You do have the devx and kernel sfs packages loaded by using menu->Setup->SFS-load-on-the-fly?

I would double check and make sure you got the correct Nvidia driver run package and it was a good download.
You are getting the Nvidia driver package directly from Nvidia web site driver download?

Same for the other sfs packages.

I have seen those same errors and it turned out I had a bad or wrong package. Nvidia run or SFS.

This is a computer with at least 1GB of memory?
That could be an issue.

_________________
I have found, in trying to help people, that 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 Shocked

Last edited by bigpup on Tue 18 Apr 2017, 06:20; edited 1 time in total
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9372
Location: Charleston S.C. USA

PostPosted: Tue 18 Apr 2017, 06:15    Post subject:  

artsown wrote:
Why was this thread moved to Puppy Derivatives?

Art

Someone spammed the forum.
Flash had to do a lot of topic fixing.
He probably moved it by mistake.

I sent him a PM about this.

_________________
I have found, in trying to help people, that 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 Shocked
Back to top
View user's profile Send private message 
radky

Joined: 02 May 2010
Posts: 720

PostPosted: Tue 18 Apr 2017, 15:42    Post subject:  

666philb wrote:
radky wrote:
Testing xenialpup64 7.0.8.5:

Running as root, the three standard dbus processes are running (image 1).

However, when palemoon is launched as spot it seems the $DBUS_SESSION_BUS_ADDRESS is not recognized in the spot environment and a session-bus file is not created. For comparison, see a normal session-bus file below for tahrpup64 (image 2).

Although palemoon launches as spot for me in xenialpup64-7.0.8.5, I see the following pop-up error message: No D-BUS daemon running (image 3).

Note: I see this error in xenialpup64 but not in tahrpup64-6.0.6.

Thanks


hi radky,

tahrpup64's dbus seems to work http://distro.ibiblio.org/puppylinux/pet_packages-tahr64/dbus-tahr-x86_64.pet

i wonder if this will cause problems elsewhere

Re: dbus as spot in xenialpup64 7.0.8.5:

Hi phil,

I installed your dbus-tahr-x86_64.pet to xenialpup64 7.0.8.5 and it works fine in initial testing.

The spot session-bus file is created correctly and the three standard dbus processes are running (image-1).

Palemoon launches as spot with no errors. Smile

Thanks
image-1.png
 Description   
 Filesize   15 KB
 Viewed   819 Time(s)

image-1.png


_________________
PupMates
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1163
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Wed 19 Apr 2017, 03:01    Post subject:  

Hi Phil,

Quote:
...
b43 was requested earlier in the xenialpups thread and is probably blocking your wireless driver.

try blacklisting it in ...menu>>system>>bootmanager


further to the previous post, here is what dmesg reports when wireless module b43 is loaded:
Quote:
...
Console: switching to colour frame buffer device 160x50
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
ssb: Found chip with id 0x4312, rev 0x01 and package 0x00
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
gpiochip_find_base: found new base at 496
gpio gpiochip0: (ssb_chipco_gpio): added GPIO chardev (254:0)
gpiochip_setup_dev: registered GPIOs 496 to 511 on device: gpiochip0 (ssb_chipco_gpio)
ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0
Broadcom 43xx driver loaded [ Features: PNLS ]
b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2
b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2
b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2
b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
e1000e: eth0 NIC Link is Down
....

For info, b43 wireless connection went well on xenialpup64-7.0.7 on this PC.

best regards, Charlie
Back to top
View user's profile Send private message 
Hesse James


Joined: 08 Feb 2010
Posts: 62

PostPosted: Wed 19 Apr 2017, 09:07    Post subject: ldlinux.c32 error  

Hello
I have also observed this failure on several computers, mainly on old ones. The Xenial32 is also affected by this.
As a counter-measure I have removed for my own purpose the uefi-capability of the ISO and than Xenial runs even on my old Athlon XP (bought in 2002).
Christian
Back to top
View user's profile Send private message 
Hesse James


Joined: 08 Feb 2010
Posts: 62

PostPosted: Wed 19 Apr 2017, 09:08    Post subject:  

I meant the ldlinux.c32 error.
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1163
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Wed 19 Apr 2017, 13:22    Post subject: Re: ldlinux.c32 error  

Hi Christian,
Hesse James wrote:
Hello
I have also observed this failure on several computers, mainly on old ones. The Xenial32 is also affected by this.
As a counter-measure I have removed for my own purpose the uefi-capability of the ISO and than Xenial runs even on my old Athlon XP (bought in 2002).
Christian

...Hmmm...interesting!....and would you mind being a bit more explicit about the «counter-measure»...? Wink
Thanks by advance !
Best regards
Charlie
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1163
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Thu 20 Apr 2017, 00:37    Post subject:  

Hi again Phil,
[quote="666philb"]
charlie6 wrote:
...
b43 was requested earlier in the xenialpups thread and is probably blocking your wireless driver.

try blacklisting it in ...menu>>system>>bootmanager


as dmesg reported
Quote:
...
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found


an googling about the reported error, have found this post:
http://www.linuxquestions.org/questions/linux-hardware-18/wifi-not-working-after-debian-upgrade-4175562548/

The above error complains about /lib/firmware/b43/ stuffs missing.
I then followed the b43 firmwares installation instructions (install b43-fwcutter-amd64.deb , etc,etc,...), rebooted, and the wlan0 went up Smile !
...but no wifi connection yet: log tells about a timeout error ...???

I believe I had rather get a try on a new xenialpup64-7.8.0.5 installation !

HTH, Charlie
Back to top
View user's profile Send private message 
Hesse James


Joined: 08 Feb 2010
Posts: 62

PostPosted: Thu 20 Apr 2017, 16:17    Post subject:  

Hello
I did it in this way:
I downloaded the latest Slacko64 or Slacko-ISO without uefi support (in my case slacko64-6.3.0.iso), opened it in any Puppy Linux with IsoMaster and removed initrd.gz, puppy_slacko64_6.3.0.sfs, vmlinuz and zdrv_slacko64_6.3.0.sfs. Then I added the corresponding files from the Xenial64-ISO (initrd.gz, puppy_xenialpup64_7.0.8.5.sfs, zdrv_xenialpup64_7.0.8.5.sfs). Finally, you could replace the logo.16 by the unzipped attachment. Afterwards save the ISO using a different name.
Hope that helps. Same procedure with Xenial32.
Best regards.
Christian
logo.16.zip
Description 
zip

 Download 
Filename  logo.16.zip 
Filesize  37.4 KB 
Downloaded  27 Time(s) 
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1163
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Fri 21 Apr 2017, 00:40    Post subject: b43 problem on hp2530p elitebook  

Hi Phil,
b43 story continues... Wink
[quote="charlie6"]Hi again Phil,
666philb wrote:
charlie6 wrote:
...
b43 was requested earlier in the xenialpups thread and is probably blocking your wireless driver.

try blacklisting it in ...menu>>system>>bootmanager


as dmesg reported
Quote:
...
b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found


an googling about the reported error, have found this post:
http://www.linuxquestions.org/questions/linux-hardware-18/wifi-not-working-after-debian-upgrade-4175562548/

The above error complains about /lib/firmware/b43/ stuffs missing.
I then followed the b43 firmwares installation instructions (install ...
I believe I had rather get a try on a new xenialpup64-7.8.0.5 installation !


Done a new trial on a fresh frugal install with addition of the b43 firmware:
here is what /var/log/messages reports about b43:
Quote:
...
Apr 21 05:13:28 puppypc27121 user.err kernel: b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
Apr 21 05:13:28 puppypc27121 user.info kernel: b43-phy0: Controller RESET (DMA error) ...
Apr 21 05:13:28 puppypc27121 user.info kernel: b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
Apr 21 05:13:30 puppypc27121 user.warn kernel: b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
Apr 21 05:13:30 puppypc27121 user.info kernel: b43-phy0: Controller restarted
Apr 21 05:13:32 puppypc27121 daemon.err dhcpcd[11211]: control_open: Connection refused
Apr 21 05:13:32 puppypc27121 daemon.info dhcpcd[11211]: version 6.6.2 starting
...
Apr 21 05:13:40 puppypc27121 daemon.info dhcpcd[11214]: wlan0: waiting for carrier


and about b43 DMA error, I found this interesting forum members tempestous's post (thanks to him!):
http://murga-linux.com/puppy/viewtopic.php?p=448464&sid=f46bb6f10dcfcf1af119029d93616ab6#448464
Quote:
...

2a. DMA failure. You will see this -
Quote:
user.err kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, ...
user.err kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
user.err kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.

In this case you need the PIO-enabled version of the b43 driver, which I have provided at the bottom of this post; b43-PIO-mode-k2.6.33.2.pet
After installing this dotpet, unload/reload the b43 driver, or reboot.
Run the "dmesg" command again and you will hopefully see this - "b43-phy1 debug: Wireless interface started".
Go ahead and run the Network Wizard.


One might need «...the PIO-enabled version of the b43 driver» How can one get it?

HTH, Charlie
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9372
Location: Charleston S.C. USA

PostPosted: Sat 22 Apr 2017, 07:46    Post subject:  

666philb,

Did you get the bugfix feature working correctly?

Get corrected the issues with installing stuff and Quickpet that were not setup for Xenialpup64?

Remember this:
http://www.murga-linux.com/puppy/viewtopic.php?p=949894#949894

_________________
I have found, in trying to help people, that 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 Shocked
Back to top
View user's profile Send private message 
riedzig

Joined: 01 Oct 2015
Posts: 25

PostPosted: Sun 23 Apr 2017, 02:16    Post subject:  

Hi, bigpup

After numerous attempts with getnvidia it seems that a nvidia 64-bit 304 driver for the Puppies with highest kernels is currently not available
On
http://www.murga-linux.com/puppy/viewtopic.php?t=72405&start=105
there are some patched .run files, not working on xenialpup64 7.0.8.5, though. On 7.0.7 it makes a crippled driver (5 MB) which obviously doesn't work properly.

However, on Slacko64 everything went OK.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 16 of 26 [381 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16, 17, 18, ..., 24, 25, 26 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0817s ][ Queries: 14 (0.0102s) ][ GZIP on ]