Page 21 of 42
Posted: Sun 18 Nov 2018, 13:37
by peebee
Attached is an ndiswrapper pet - it
requires a kernel change to 3.16.45:
https://sourceforge.net/projects/lxpup/ ... 2/download
Posted: Tue 20 Nov 2018, 19:44
by B.K. Johnson
A couple of questions peebee.
Let's assume that I am changing the kernel in upupcc,
My only prior experience with changing a kernel was the new vmlinuz and zdrv of the new kernel would simply replace the old. That is not the case here.
Exactly what should I do with
- vmlinuz-3.16.45-puppy4g
kernel-modules.sfs-3.16.45-puppy4g
produced when huge-3.16.45-puppy4g.tar.bz2 is uncompressed?
Should I just rename them to vmlinuz and zdrv_upupcc_18.10.sfs
reboot, run Grub4Dos then run the ndiswrapper pet?
TIA for your guidance.
Posted: Tue 20 Nov 2018, 20:11
by peebee
B.K. Johnson wrote:Exactly what should I do with
- vmlinuz-3.16.45-puppy4g
kernel-modules.sfs-3.16.45-puppy4g
produced when huge-3.16.45-puppy4g.tar.bz2 is uncompressed?
Should I just rename them to vmlinuz and zdrv_upupcc_18.10.sfs
Yes
reboot, run Grub4Dos then run the ndiswrapper pet?
Yes - but no need for grub4dos - just reboot
Posted: Tue 20 Nov 2018, 20:38
by rockedge
swap kernel made easy ...tested and works great in peebee's Bionic series...
http://www.murga-linux.com/puppy/viewtopic.php?t=101144
script download
http://www.murga-linux.com/puppy/viewto ... h&id=90829
the script might already be on board so worth a check
Posted: Fri 23 Nov 2018, 15:07
by B.K. Johnson
@peebee
A short advisory:
The latest ndiswrapper offering works but there are some strange outputs I want to investigate and identify whether they are ndiswrapper related or upupcc..
Posted: Fri 23 Nov 2018, 18:11
by B.K. Johnson
The attached screenshot is
copied from this post
http://murga-linux.com/puppy/viewtopic. ... 56#1008778
by chrisbear in the upupcc thread and to which I added marked-ups in red. The items underlined or red-circled are similar to what I see when I use Net Wizard. Note that my system does have a wireless PCI card but it is not being used.
lspci rightfully does not recognize it. Yet, a wireless PCI is what is identified at the NetWizard output, which is similar to that in the screenshot and which I can't identify. Chris can confirm whether his driver is properly named and his interface is an USB or PCI.
I have also plugged in, an USB wireless adapter which lsbusb recognizes. Furthermore, there is no doubt that it is the USB that is connected for on removing the adapter from the port, I lose the connection.
It may be that this is neither a upupbb nor ndiswrapper related issue, but I am posting here for continuity. Subsequent postings may well be made in the upupcc thread.
Posted: Fri 23 Nov 2018, 19:16
by Brown Mouse
And I still don't understand !
These latest Puppys contain no less than 5 sfs files...adrv sfs..fdrv sfs..ydrv sfs..zdrv sfs and upupbb sfs.
Do they all need changing??
Posted: Fri 23 Nov 2018, 19:25
by peebee
Brown Mouse wrote:And I still don't understand !
These latest Puppys contain no less than 5 sfs files...adrv sfs..fdrv sfs..ydrv sfs..zdrv sfs and upupbb sfs.
Do they all need changing??
There is a README in the iso to explain....
The kernel comes in 2 files - zdrv and vmlinuz
My kernels have firmware in the fdrv (other people's kernels include firmware in the zdrv - you can normally tell by the size if so).
The fdrv is kernel (and architecture) agnostic and can be used with many kernels and doesn't have to be changed.
So if you're changing to another of my kernels all you have to change is the vmlinuz and zdrv.
Posted: Fri 23 Nov 2018, 19:28
by Brown Mouse
peebee wrote:Brown Mouse wrote:And I still don't understand !
These latest Puppys contain no less than 5 sfs files...adrv sfs..fdrv sfs..ydrv sfs..zdrv sfs and upupbb sfs.
Do they all need changing??
There is a README in the iso to explain....
The kernel comes in 2 files - zdrv and vmlinuz
My kernels have firmware in the fdrv (other people's kernels include firmware in the zdrv - you can normally tell by the size if so).
The fdrv is kernel (and architecture) agnostic and can be used with many kernels and doesn't have to be changed.
So if you're changing to another of my kernels all you have to change is the vmlinuz and zdrv.
Thank you peebee.
Posted: Fri 23 Nov 2018, 19:39
by Terry H
B.K. Johnson wrote:The attached screenshot is
copied from this post
http://murga-linux.com/puppy/viewtopic. ... 56#1008778
by chrisbear in the upupcc thread and to which I added marked-ups in red. The items underlined or red-circled are similar to what I see when I use Net Wizard. Note that my system does have a wireless PCI card but it is not being used.
lspci rightfully does not recognize it. Yet, a wireless PCI is what is identified at the NetWizard output, which is similar to that in the screenshot and which I can't identify. Chris can confirm whether his driver is properly named and his interface is an USB or PCI.
I have also plugged in, an USB wireless adapter which lsbusb recognizes. Furthermore, there is no doubt that it is the USB that is connected for on removing the adapter from the port, I lose the connection.
It may be that this is neither a upupbb nor ndiswrapper related issue, but I am posting here for continuity. Subsequent postings may well be made in the upupcc thread.
I haven't read any previous posts regarding this issue, so apologies if this may have been already covered. I don't have this wifi card, but was looking through the upbb fdrv.sfs and noticed there is an rtlwifi folder, which contains what may be firmware for your card. I would have thought that it should be identified and loaded directly.
Do you have the fdrv loaded?
Firmware is not included if the fdrv is not loaded.
Edit: Does dmesg identify anything regarding the driver?
dmesg|grep wifi OR dmesg|grep r8188 OR similar?
Posted: Sat 24 Nov 2018, 15:02
by peebee
Posted: Tue 27 Nov 2018, 14:30
by B.K. Johnson
@Terry H
First, apologies for not responding before. I had to be switching berween upupcc without my regular tool-set and tahr with them. Full complement not yet installed, but enough to spend more time in upupcc.
You wrote:
...I don't have this wifi card, but was looking through the upbb fdrv.sfs and noticed there is an rtlwifi folder, which contains what may be firmware for your card. I would have thought that it should be identified and loaded directly.
Just in case you missed it Terry, that screenie is for chrisbeard's card.
A screenshot of my card is attached to this post. As can be seen, it shows Wireless PCI when it should be USB. Following your lead, I looked in upupcc's fdrv but did not find enx204e... Feel free to check it out.
Do you have the fdrv loaded?
Yes!
Does dmesg identify anything regarding the driver?
dmesg|grep wifi OR dmesg|grep r8188
Code: Select all
# dmesg|grep wifi
# dmesg|grep enx204e
ndiswrapper: interface renamed to 'enx204e7fee1f18'
#
So, it is ndiswrapper that names the driver.
@peebee
Over to you.
Posted: Tue 27 Nov 2018, 15:18
by perdido
Peazip 6.6.1 precompiled works great in upup bionic beaver.
It handles the latest compression methods available from rar and 7zip
and many others & complements what UExtract does not handle.
I am using the PeaZip for Linux x86 6.6.1 GTK2 version available at top of this page
http://www.peazip.org/peazip-linux-x86.html
No extra dependencies needed for GTK2 version.
I used this one --->
https://osdn.net/dl/peazip/peazip_6.6.1 ... 2_i386.deb
Additional plugins available for ace, rar,arc, etc, available at this page.
The addaitional plugin for rar is not really needed but available.
Info & plugins available on this page.
http://www.peazip.org/peazip-add-ons.html
Sources are available at this link if you want to compile your own,
--->
https://osdn.net/projects/peazip/downlo ... 1.src.zip/
to compile you will need to track down the missing dependencies though.
.
Posted: Tue 27 Nov 2018, 17:36
by peebee
B.K. Johnson wrote:So, it is ndiswrapper that names the driver.
If you don't like the new interface naming
see post #2
Posted: Tue 27 Nov 2018, 19:45
by B.K. Johnson
Thanks for the link peebee. Got it, but could you explain for this ignoramus the source of this new naming? Is it from the firmware name? Just curius.
TIA
Posted: Tue 27 Nov 2018, 19:51
by peebee
B.K. Johnson wrote:Thanks for the link peebee. Got it, but could you explain for this ignoramus the source of this new naming? Is it from the firmware name? Just curius.
TIA
Debian - Ubuntu thing:
https://wiki.debian.org/NetworkConfigur ... face_Names
Posted: Sat 08 Dec 2018, 10:53
by peebee
Posted: Sat 08 Dec 2018, 16:52
by rockedge
I use a boot parameter to use predictable interface names with : net.ifnames=0
more info here ->
https://askubuntu.com/questions/628217/ ... te-kernels
Grub4Dos menu.lst entry ->
Code: Select all
title BionicZM-C 18.05+20 (sda4/BionicZM-C)
find --set-root uuid () acc8a5ba-3340-43e8-9d4c-b09ef6b299d1
kernel /BionicZM-C/vmlinuz pdrv=acc8a5ba-3340-43e8-9d4c-b09ef6b299d1 psubdir=/BionicZM-C pmedia=atahd pfix=fsck net.ifnames=0
initrd /BionicZM-C/initrd.gz
Posted: Sat 08 Dec 2018, 18:01
by Marv
Smooth update from 20 to 21 on the Fujitsu S761 i5 laptop. I continue to use the 32b 4.9.134 kernel from upupcc with no problems here.
Code: Select all
# uname -a
Linux puppypc20747 4.9.134-lxpup-32-pae #1 SMP Fri Oct 19 10:37:59 +08 2018 i686 i686 i686 GNU/Linux
Thanks,
Posted: Sun 09 Dec 2018, 07:52
by tallboy
I have been playing with saves to a multisession CD, and I am very satisfied with the UPupBB. You've done a great job, peebee.
With a support time spanning the next ten years, I think it will be my main Puppy for a long time. But, I have a problem. The initial .iso burnt to the CD was a upupbb-18.05+1.iso, and I have added 4 sessions to the CD. I don't use a savefile. Is it possible to update a live multisession CD-R to the latest edition, using the delta updates and reverse_updates, and keep the multisession saves? The saved session directories are dated, and they cannot just be moved into a new .iso.
Any suggestions?
Edit:
peebee suggested I make a new thread to raise this question, so any futher development may not be mentioned here, unless I actually remember to update you guys and gals!
New thread here:
http://murga-linux.com/puppy/viewtopic. ... 87#1012687 I would suggest that those of you wanting to remaster, or modify a live UPupBB in any other way than by updates, read the posts there.