BionicDog (updated: 2018-06-04)
I've since found that Publii works if download Publii.AppImage instead of the deb. If root user, need to run it with --no-sandbox option. Still don't know the issue with deb version and save2flash; maybe some Bionic library gets overwritten???
wiak
wiak
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Yes, would be interesting to know what causes the issue, but no hurry, the Appimage version works fine, and personally I'm now using Hugo instead since really nice and has lots of docs/tutorial. Actually, it's my partner that needs the functionality, which is why I looked at Publii since more GUI drag and drop type of app, and Jekyll too technical, but Hugo learning curve isn't so steep for basic use anyway.fredx181 wrote:Hi wiak, thanks, I'll try to investigate the issue you mentioned within the next days, atm I'm in a flow of doing other things.
Fred
wiak
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Hi wiak, I found the cause.
Indeed has to do with save2flash, well, actually with the snapmergepuppy script (called by save2flash) which skips copying the contents of any "trash" folder.
/opt/Publii contains a trash subfolder which is needed for Publii to run and cannot find it after reboot with save2flash.
I added upgraded package "porteusbootscript" (0.0.6) to repo, which contains fixed snapmergepuppy, installing that + re-installing Publii and it should be ok.
Fred
Indeed has to do with save2flash, well, actually with the snapmergepuppy script (called by save2flash) which skips copying the contents of any "trash" folder.
/opt/Publii contains a trash subfolder which is needed for Publii to run and cannot find it after reboot with save2flash.
I added upgraded package "porteusbootscript" (0.0.6) to repo, which contains fixed snapmergepuppy, installing that + re-installing Publii and it should be ok.
Fred
- chesterpeng
- Posts: 18
- Joined: Tue 17 Sep 2019, 03:03
- Location: bc.ca
unable to upgrade kernel
Hi there,
I am running BionicDog64_2018-06-04-firmware_all, frugal installed to sda1.
Recently, I am trying to upgrade the kernel through Menu->system->upgrade-kernel, the script seems to run successfully. see attached screen shot.
After rebooting, I find the system is still running old kernel.
and the two .bak files which are supposed to be created by the script do not exist under /casper.
I guess something must be messed up in my system, anyone knows how to clean it up?
Thanks.
I am running BionicDog64_2018-06-04-firmware_all, frugal installed to sda1.
Recently, I am trying to upgrade the kernel through Menu->system->upgrade-kernel, the script seems to run successfully. see attached screen shot.
After rebooting, I find the system is still running old kernel.
Code: Select all
root@bionicdog64:~# uname -a
Linux bionicdog64 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@bionicdog64:~#
I guess something must be messed up in my system, anyone knows how to clean it up?
Thanks.
- Attachments
-
- 2020-04-14-01.png
- (106.75 KiB) Downloaded 72 times
Hi chesterpeng,
I have no idea what went wrong for you, just tested upgrade-kernel and went fine, booting with 4.15.0-96 now.
What you can try is removing kernel 4.15.0-96 with apt :
And then try running upgrade kernel again, take a close look at the process if you see any error messages (specially at the end when initrd is generated) (it looks like that earlier for you the new kernel got installed well but only the files in casper are not created)
Fred
I have no idea what went wrong for you, just tested upgrade-kernel and went fine, booting with 4.15.0-96 now.
What you can try is removing kernel 4.15.0-96 with apt :
Code: Select all
apt purge linux-image-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic
Fred
Fred might have more specific information, but this may get you pointed in the right direction.dcung wrote:Wifi issue - anyone can help please?
http://murga-linux.com/puppy/viewtopic. ... 41#1055641
https://help.ubuntu.com/community/WifiD ... er/bcm43xx
- chesterpeng
- Posts: 18
- Joined: Tue 17 Sep 2019, 03:03
- Location: bc.ca
Hi Fredfredx181 wrote: What you can try is removing kernel 4.15.0-96 with apt :And then try running upgrade kernel again...Code: Select all
apt purge linux-image-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic
After removing the 3 modules and rerunning upgrade-kernel, I got some errors. It seems that initrd is not generated because of the cp errors.
Chester
- Attachments
-
- after removing 3 kernel 4.15.0-96 modules.jpg
- (201.5 KiB) Downloaded 64 times
Hi chesterpeng, it looks like something is wrong with /usr/sbin/update-initramfs (I see on your screenshot "permission denied") resulting that /boot/initrd.img-4.15.0-96-generic doesn't exist and cannot be copied.
Have a look if update-initramfs is executable
(it should read like above: -rwxr-xr-x)
If not executable you can try to reinstall initramfs-tools :
and check again if /usr/sbin/update-initramfs is executable
Once that is fixed you need to remove kernel 4.15.0-96 (like you did earlier) and run upgrade-kernel again.
But maybe the best is to start fresh with save-file/folder, something must have gone wrong (that resulted in the "permission denied" of update-initramfs, also could have affected other vital system software)
Fred
Have a look if update-initramfs is executable
Code: Select all
root@live64:~# ls -l /usr/sbin/update-initramfs
-rwxr-xr-x 1 root root 8235 Oct 7 2019 /usr/sbin/update-initramfs
If not executable you can try to reinstall initramfs-tools :
Code: Select all
apt install --reinstall initramfs-tools
Once that is fixed you need to remove kernel 4.15.0-96 (like you did earlier) and run upgrade-kernel again.
But maybe the best is to start fresh with save-file/folder, something must have gone wrong (that resulted in the "permission denied" of update-initramfs, also could have affected other vital system software)
Fred
- chesterpeng
- Posts: 18
- Joined: Tue 17 Sep 2019, 03:03
- Location: bc.ca
Hi Fred,
You are right. The executable property of my /usr/sbin/update-initramfs file got somehow lost and become -rw-r--r--. After modifying the permission to -rwxr-xr-x and running upgrade-kernel again, Linux kernel is upgraded to 4.15.0-96 successfully.
Thank you for the help.
Cheers!
Chester
You are right. The executable property of my /usr/sbin/update-initramfs file got somehow lost and become -rw-r--r--. After modifying the permission to -rwxr-xr-x and running upgrade-kernel again, Linux kernel is upgraded to 4.15.0-96 successfully.
Code: Select all
root@bionicdog64:~# uname -a
Linux bionicdog64 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Cheers!
Chester
Thanks for the link dancytron.dancytron wrote: Fred might have more specific information, but this may get you pointed in the right direction.
https://help.ubuntu.com/community/WifiD ... er/bcm43xx
It's a little out of my depth, but after few trials and errors, I think I managed to use STA driver. Will see if wifi is more stable now.
Code: Select all
****BEFORE****
root@live64:~# lspci -vvnn | grep -A 9 Network
0c:00.0 Network controller [0280]: Broadcom Limited BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
Subsystem: Dell Wireless 1500 Draft 802.11n WLAN Mini-card [1028:000a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
Region 2: Memory at f0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
root@live64:~#
****AFTER****
root@live64:~# lspci -vvnn | grep -A 9 Network
0c:00.0 Network controller [0280]: Broadcom Limited BCM4321 802.11a/b/g/n [14e4:4328] (rev 03)
Subsystem: Dell Wireless 1500 Draft 802.11n WLAN Mini-card [1028:000a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K]
Region 2: Memory at f0000000 (64-bit, prefetchable) [size=1M]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Kernel driver in use: wl
Kernel modules: ssb, wl
root@live64:~#
Thanks for reporting back.dcung wrote:FYI - Update.dcung wrote: Will see if wifi is more stable now.
Have been video streaming (live TV, Netflix, etc) since using wl driver. Wifi has not dropped once since.
In my case, it (STA/wl driver) seems to be more reliable than b43 driver.
I have updated all my D630 to use wl driver now.
Updated version of "quick-remaster" v1.2.1 in custom repo, see more info here (about different method used):
http://murga-linux.com/puppy/viewtopic. ... 59#1057459
@backi, the mksquashfs from Bionic doesn't have compression option zstd, so not much new in fact (except the different method used (more safe) and no forced reboot)
Fred
http://murga-linux.com/puppy/viewtopic. ... 59#1057459
@backi, the mksquashfs from Bionic doesn't have compression option zstd, so not much new in fact (except the different method used (more safe) and no forced reboot)
Fred