Xenialpup64 CE 7.5 / 25 Nov 2017

A home for all kinds of Puppy related projects
Message
Author
belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#421 Post by belham2 »

mavrothal wrote:
666philb wrote:i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.
As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.

Boy, I really don't understand this comment and/or reply.

So Micko releases Slacko 6.9.9.9, and officially calls it 'Slacko 700' in the thread title, then has left it like that for several months now. Phil had his "Xenialpups" marked as "7.0.8.#" for the same amount of time, returns & releases "7.0.8.6" which was much arppeciated. Then phil makes a comment that soon he should be able to go to 7.0.9, and Marvothal writes the above comment?


Can I ask why 7.0.9 is such a problem? Is it the fact it is only 3 numbers in length? Because we all are pretty used to seeing the "7" in front of everything when it comes to releases from both Micko and Phil. And the reference to Peebee? What is that?? His releases are like 17.##.## on the zesty/artful side, and same goes for the LxPupSc side.

Again, it begs the question, why did Phil's comment about going to a "7.0.9" elicit such a response? By reasoning and rationale alone in that comment to Phil, then no one (especially Micko) should ever have written a "7", let alone a "700" (like beside Slacko), correct?

User avatar
Moat
Posts: 955
Joined: Tue 16 Jul 2013, 06:04
Location: Mid-mitten

#422 Post by Moat »

Yeah, I didn't quite get that one either.

7.1.0 FTW! :)

Or maybe 8.0.0... :shock:

Bob

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#423 Post by perdido »

belham2 wrote:
mavrothal wrote:
666philb wrote:i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.
As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.

Boy, I really don't understand this comment and/or reply.

So Micko releases Slacko 6.9.9.9, and officially calls it 'Slacko 700' in the thread title, then has left it like that for several months now. Phil had his "Xenialpups" marked as "7.0.8.#" for the same amount of time, returns & releases "7.0.8.6" which was much arppeciated. Then phil makes a comment that soon he should be able to go to 7.0.9, and Marvothal writes the above comment?


Can I ask why 7.0.9 is such a problem? Is it the fact it is only 3 numbers in length? Because we all are pretty used to seeing the "7" in front of everything when it comes to releases from both Micko and Phil. And the reference to Peebee? What is that?? His releases are like 17.##.## on the zesty/artful side, and same goes for the LxPupSc side.

Again, it begs the question, why did Phil's comment about going to a "7.0.9" elicit such a response? By reasoning and rationale alone in that comment to Phil, then no one (especially Micko) should ever have written a "7", let alone a "700" (like beside Slacko), correct?


All of the 7.x versions so far are in beta.
No official 7.x versions yet.

I believe the reference about 7.0.9 is solely a problem with semantics.

.

.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#424 Post by bigpup »

666philb wrote:
bigpup wrote:Xenialpup64 7.0.8.6
Frugal
Save folder.

I can live with this and have been for some time.
Just wonder why it is required in Xenialpup.

Video card Nvidia GeForce GTX 970.

Initial first boot, have to use nouveau.modeset=0 to get to visible desktop.
hi bigpup,

i've no idea why this is required with xenialpup64. do you need to use the same option with xenialpup32 bit as well? if so can you try the 32bit xenialpup with artfuls kernel. just copy the vmlinux & zdrv.sfs over renaming the zdrv.sfs
Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.
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 :shock:
YaPI(any iso installer)

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

wifi failed to connect using b43 module on laptop HP2530p

#425 Post by charlie6 »

Hi 666philb, :)
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions).
Other recent Puppies (TahPup, Zesty, Artful, whatever 32 or 64 bits) connect to wifi network OOTB.
I even tried to compile the wl kernel module for the previous xenialpup64-7.0.8.5 version without getting wifi !
Here are some reports from Frisbee network tool to help for an eventual fix.

last edited: added dmesg output on ArtFulPup 32bits for a working WiFi
dmesg output about b43:
...
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 ]
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
e1000e: eth0 NIC Link is Down
ip_tables: (C) 2000-2006 Netfilter Core Team
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Read] Request device [02:00.0] fault addr fffe9000 [fault reason 06] PTE Read access is not set
b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Controller restarted
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
Thanks for any advice!
Charlie
dmesg output for workig WiFi on ArtFulPup on the VERY SAME PC
...
ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
Console: switching to colour frame buffer device 160x50
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
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 ]
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
udevd[8046]: Process '/sbin/crda' failed with exit code 254.
udevd[8162]: Process '/sbin/crda' failed with exit code 254.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
udevd[8407]: Process '/sbin/crda' failed with exit code 254.
udevd[8673]: Process '/sbin/crda' failed with exit code 254.
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authenticated
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated
udevd[8718]: Process '/sbin/crda' failed with exit code 254.
udevd[9384]: Process '/sbin/crda' failed with exit code 254.
wlan0: deauthenticated from 20:0c:c8:16:e0:7c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
udevd[9388]: Process '/sbin/crda' failed with exit code 254.
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: authenticated
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated
udevd[9396]: Process '/sbin/crda' failed with exit code 254.
udevd[9451]: Process '/sbin/crda' failed with exit code 254.
udevd[9502]: Process '/sbin/crda' failed with exit code 254.
wlan0: deauthenticating from 20:0c:c8:16:e0:7c by local choice (Reason: 3=DEAUTH_LEAVING)
udevd[9523]: Process '/sbin/crda' failed with exit code 254.
udevd[9544]: Process '/sbin/crda' failed with exit code 254.
e1000e: enp0s25 NIC Link is Down
b43-phy0: Radio hardware status changed to DISABLED
b43-phy0: Radio hardware status changed to ENABLED
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authentication with 20:0c:c8:16:e0:7c timed out
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authentication with 20:0c:c8:16:e0:7c timed out
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authenticated
b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated
Attachments
Netw_set_failed.png
(135.23 KiB) Downloaded 836 times
pdiag-20171031.tar.gz
(182.85 KiB) Downloaded 144 times
Netw_set_wpa-status.png
(130.18 KiB) Downloaded 871 times
Net_set_wpa_Supp_Log.png
(137.7 KiB) Downloaded 808 times

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#426 Post by 666philb »

bigpup wrote: Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.
hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder
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

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

Re: wifi failed to connect using b43 module on laptop HP2530p

#427 Post by 666philb »

charlie6 wrote:Hi 666philb, :)
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions).
Other recent Puppies (TahPup, Zesty, Artful, whatever 32 or 64 bits) connect to wifi network OOTB.
I even tried to compile the wl kernel module for the previous xenialpup64-7.0.8.5 version without getting wifi !
hi charlie6,

can you try the suggestion pointed to in this link https://bbs.archlinux.org/viewtopic.php?id=230381
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

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

[SOLVED] wifi failed to connect using b43 module on HP2530p

#428 Post by charlie6 »

666philb wrote:
charlie6 wrote:Hi 666philb, :)
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions
...
hi charlie6,
can you try the suggestion pointed to in this link https://bbs.archlinux.org/viewtopic.php?id=230381
Hi 666philb :D !
tons of thanks for you quick reply ! :P
it works now !
Have added «intel_iommu=off» to the GRUBs kernel parameters as suggested in the above link; aftrwds reboot (frugal install) and it connects to WiFi straight on after inserting WPA code!

Here is my grub code:

Code: Select all

title Puppy Linux XENIALPUP64_7.0.8.6 frugal in sda4 dir xen64
  root (hd0,3)
  kernel /xen64/vmlinuz psubdir=xen64 pmedia=atahd pfix=fsck intel_iommu=off
  initrd /xen64/initrd.gz
as reported in the above links by forum moderator V1del:
About linux-4.13.3-1-x86_64 kernel: One new option enabled in the 4.13 kernel by default is iommu, have you tried the mentioned kernel parameter to turn that off again?
Best regards
Charlie

last edited:
For Xenialpup64-7.0.8.5-uefi: /lib/firmware/b43 is missing:
It also fixes the same issue on Xenialpup64-7.0.8.5-uefi provided the /lib/firmware/b43 has previuosly been installed, and the PC rebooted: firmware copied from Xenialpup64-7.0.8.6

HTH, Charlie
Last edited by charlie6 on Mon 13 Nov 2017, 08:14, edited 1 time in total.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#429 Post by bigpup »

666philb wrote:
bigpup wrote: Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.
hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder
Artfulpup is 32bit.
Is it's fdrv going to work in a 64bit Xenialpup?
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 :shock:
YaPI(any iso installer)

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#430 Post by 666philb »

bigpup wrote:
666philb wrote:
bigpup wrote: Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.
hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder
Artfulpup is 32bit.
Is it's fdrv going to work in a 64bit Xenialpup?
i believe so, as i don't think the firmware is dependent on the operating systems architecture. (could be wrong though :) )
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

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#431 Post by 666philb »

mavrothal wrote:
666philb wrote:i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.
As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.
ok.... i'll ask and see what they reckon . i actually don't mind what it is.
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

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

Re: Xenial Pup 64

#432 Post by 666philb »

Duprate wrote:
BUG:
For the proper functioning of the audio in Firefox, it is necessary that the libs in usr/lib/apulse/, are located in usr/lib/ e I solved the problem by copying and pasting it in the right place.
hi Duprate,

the problem with this solution is with apps that check to see if there is a working pulse audio, and then not finding it use the alsa interace instead. those apps will then always use the pulseaudio interface provided by apulse.
and whilst they work there's less control over them in puppys native mixer.

so i reckon i'll be sticking with the apulse libs in /usr/lib/apulse and using 'apulse firefox' to run firefox
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

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#433 Post by mavrothal »

666philb wrote: i actually don't mind what it is.
Can't find the post now that BK archived his blogs, but the story goes that Distowatch does not want to go back and forth with numbers, (you should not have puppy-xenial7.1 and then puppy-slacko 7.0) and not like to "announce" point releases.
(They do announce development/beta releases with any version, and maybe puppy builders should take advantage of it).
== [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] ==

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#434 Post by bigpup »

SOMEBODY JUST POST SOME NEW INFO ABOUT PUPPY ON DISTROWATCH. :!: :!: :!: :!: :!: :!:
WHATEVER IT IS :!: :!: :!:

The last Puppy version talked about is Slacko 6.3 and that was in 2015 :shock: :roll: :!:
Tahrpup is talking about Tahrpup 6.0. Nothing about Tahrpup 6.0.5 or 6.0.6 and any of the 64bit versions of Tahrpup.

Do not say why do you not do it?

Distrowatch would like the, developer of a Puppy version, to give the info to post.
I agree. The developer knows the Puppy version and what it is all about. Someone else, may think they know it, but there may be other features they know nothing about.
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 :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#435 Post by bigpup »

the story goes that Distowatch does not want to go back and forth with numbers, (you should not have puppy-xenial7.1 and then puppy-slacko 7.0) and not like to "announce" point releases.
Seems Ubuntu can do it :shock:
2017-10-19: Distribution Release: Ubuntu 17.10
• 2017-09-29: Development Release: Ubuntu 17.10 Beta 2
• 2017-08-03: Distribution Release: Ubuntu 16.04.3
• 2017-04-13: Distribution Release: Ubuntu 17.04
• 2017-03-23: Development Release: Ubuntu 17.04 Beta 2
• 2017-02-17: Distribution Release: Ubuntu 16.04.2
• 2016-10-13: Distribution Release: Ubuntu 16.10
• 2016-09-28: Development Release: Ubuntu 16.10 Beta 2
• 2016-08-05: Distribution Release: Ubuntu 14.04.5
• 2016-07-21: Distribution Release: Ubuntu 16.04.1
• 2016-04-21: Distribution Release: Ubuntu 16.04
• 2016-03-25: Development Release: Ubuntu 16.04 Beta 2
Seems if you are talking about two or more completely different named Puppy versions. The version number should go along with the development of that specific Puppy.
They may all be considered version 7 in the Puppy series, which is now controlled by WOOF-CE.
But where in that named version of Puppy may be completely different from one named version to another.

DistroWatch needs to understand that there is more than one version of Puppy. Several different ones are developed at the same time based on different core programs, features, and files.
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 :shock:
YaPI(any iso installer)

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#436 Post by mavrothal »

bigpup wrote:Distrowatch would like the, developer of a Puppy version, to give the info to post.
I'm not sure about that either.
Originally DW was monitoring BK's blog. Later Barry should inform them about new versions (as he does for quirky now days). I'm not sure if it is still BK that does that, Mick or nobody, but I doubt is "any developer"
For sure should be "officially" announced somewhere beyond this forum, to point DW at.
As we know from this forum and Ally's archive, there are thousands of puppies and likely millions of Linux spins. DW tends to report on serious, consistent, openly reproducible, long term efforts.

BTW, Ubuntu's updates of their long term releases although numbered as point releases, are established and scheduled in the release from the beginning. They are major updates.
== [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] ==

artsown
Posts: 403
Joined: Wed 12 Sep 2012, 18:35

#437 Post by artsown »

Phil, please restore the option to select SNS instead of Frisbee. Frisbee
takes "forever" to make my wireless connection at startup. SNS is far
superior in this respect. The lack of choice is a step backward IMO.

Art, the grumpy old coot.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#438 Post by bigpup »

I'm not sure if it is still BK that does that, Mick or nobody, but I doubt is "any developer"
BK is no longer contributing to Puppy and has nothing to do with it.
01micko is suppose to be the person that took over as the Puppy master.
Seems to have little interest in Puppy for some months.

As for developers submitting information to DistroWatch.
DistroWatch seems to think they should.

Read the DistrWatch terms for submission of a new Linux version.
https://distrowatch.com/dwres.php?resource=submit
Once you've created a Linux distribution and would like to have it listed on DistroWatch, you should e-mail us to tell us about your project. Please provide the following four pieces of information in your e-mail:

The name of the project or distribution.
The URL of the project's website.
A brief description of the distribution, such as its goal(s) and what other distribution it uses as its base, if applicable.
A link to the distribution's installmedia media (ISO file).
This is really what DistroWatch wants you to do.
for those developers who absolutely and desperately want to have their distribution listed on DistroWatch today. All you need to do is to buy an advertising banner and your distro will be listed straight away.
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 :shock:
YaPI(any iso installer)

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#439 Post by Sailor Enceladus »

artsown wrote:Phil, please restore the option to select SNS instead of Frisbee. Frisbee
takes "forever" to make my wireless connection at startup. SNS is far
superior in this respect. The lack of choice is a step backward IMO.

Art, the grumpy old coot.
I noticed this in 32-bit version 7.0.8.6 too. I used Frisbee as it was the only choice and it works as good as SNS for me so far, but it was strange not to see the one I normally used since Slacko 5.6. I thought maybe this was because 666philb was using an old woof-CE before this change, but that is for including frisbee and netwiz I think, so mystery still remains on how this happened. :)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#440 Post by bigpup »

bigpup wrote:
666philb wrote:
bigpup wrote:Xenialpup64 7.0.8.6
Frugal
Save folder.

I can live with this and have been for some time.
Just wonder why it is required in Xenialpup.

Video card Nvidia GeForce GTX 970.

Initial first boot, have to use nouveau.modeset=0 to get to visible desktop.
hi bigpup,

i've no idea why this is required with xenialpup64. do you need to use the same option with xenialpup32 bit as well? if so can you try the 32bit xenialpup with artfuls kernel. just copy the vmlinux & zdrv.sfs over renaming the zdrv.sfs
Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.
I have been doing some research.
If I am understanding this correctly this is being caused by the kernel compile setup for the use of frame buffer and KMS.
Basically if they are compiled to be active or not active in the kernel.
The nouveau driver module, that is in the kernel, is also something that can have an affect on this.
You may want to disable KMS for various reasons, such as getting a blank screen. That is my problem.
Nvidia graphics card you need to add nouveau.modeset=0
Here is some info on KMS
https://nouveau.freedesktop.org/wiki/KernelModeSetting/

Still trying to figure out what is the difference between a kernel that does not have a problem and one that does.
But it does involve KMS and the nouveau driver kernel module.
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 :shock:
YaPI(any iso installer)

Post Reply