Posts by Altoid

Altoid · Hardware & System Configuration

Hello:

hevidevi wrote:

... maybe in your closebook.sh script you should not declare the PATH=/bin:/sbin ...

I put it in just in case the system path has some issue.
Belt and suspenders thing.

But that would not seem to be the problem because the script is found and the executables in it are run properly.

What is not being found is the script that calls closebook.sh unless I run it as ./shutdown.

I just realised that the /root folder is not in the system PATH variable:

root@OpenWrt:~# $PATH
-ash: /usr/sbin:/usr/bin:/sbin:/bin: not found
root@OpenWrt:~#

This one:

root@OpenWrt:~# ls
shutdown
root@OpenWrt:~#

Which you can see here:

root@OpenWrt:/# ls
bin         dev         lib         mnt         proc        # root #        srv         tmp         var
boot        etc         lost+found  overlay     rom         sbin        sys         usr         www
root@OpenWrt:/#

No idea as to how to follow up.
Surely it is not a good idea to have the root folder in the path.

Thanks for your input.

Best,

A.

Altoid · Hardware & System Configuration

Hello:

Still playing around with my new My Book Live thingy, trying to set up a solution to the lack of a shutdown command in this PowerPC 44x processor.
This is the OpenWRT installed on the unit:

~# uname -a
Linux_book 5.4.179 #0 Wed Feb 16 20:29:10 2022 ppc GNU/Linux
~#

I wrote a script to shut down the board gracefully:

root@OpenWrt:/usr/bin# cat closebook.sh
#!/bin/sh
# script to stop drive and shut down MBL
# gives ~15s from blue led <on> to unplug unit
PATH=/bin:/sbin

sync && wait && hdparm -Y /dev/sda && wait && halt
root@OpenWrt:/usr/bin#

The script is executable:

root@OpenWrt:~# ls -l /usr/bin/closebook.sh
-rwxr-xr-x    1 root     root           166 Apr 17 08:40 /usr/bin/closebook.sh
root@OpenWrt:~#

Once the front LED goes from green to blue, you have to physically disconnect power to the board within ~15s, otherwise a watchdog will sense the new situation and proceed to reboot the board.

For the time being, I call the /usr/bin/closebook.sh from ~/ with another script:

root@OpenWrt:~# cat shutdown 
#!/bin/sh
sh -c '/usr/bin/closebook.sh'
root@OpenWrt:~#

The script is executable:

root@OpenWrt:~# ls -l shutdown
-rwxr--r--    1 root     root            40 Apr 17 10:07 shutdown
root@OpenWrt:~#

It works as intended and have not had an instance where the plug was pulled late or where the watchdog reboot caused any issues.
Unsurprisingly, not shutting down in this manner will always cause dmesg to print this:

[    0.907630] EXT4-fs (sda2): warning: mounting unchecked fs, running e2fsck is recommended
[    5.802598] EXT4-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

The main problem is that while /dev/sda1 but can be unmounted to run e2fsck, /dev/sda2 holds the rootfs and cannot be unmounted:

root@OpenWrt:~# blkid
--- snip ---
/dev/sda2: LABEL="rootfs" UUID="ff313567-e9f1-5a5d-9895-3ba130b4a864" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="228c756a-02"
--- snip ---
root@OpenWrt:~#

But I digress ...

The thing is that to run the script I have to do it with ./, otherwise it is not found:

root@OpenWrt:~# shutdown
-ash: shutdown: not found
root@OpenWrt:~#

This even though I am running it as root and it is located in what would be home directory:

root@OpenWrt:~# ls
shutdown
root@OpenWrt:~#

The system's $PATH:

root@OpenWrt:~# $PATH
-ash: /usr/sbin:/usr/bin:/sbin:/bin: not found
root@OpenWrt:~#

I'm sure it is a $PATH issue ...

What am I doing wrong?

Thanks in advance,

A.

Altoid · Hardware & System Configuration

Hello:

hevidevi wrote:

... that system would have to enable some sort of admin ...
... possible to build busybox ash, bash with certain flags to enable ...

Could be.
But the idea is to avoid building anything with/for OpenWRT as it would complicate eventual sysupgrades.

I found this:
https://forum.sailfishos.org/t/busybox- … sh/6808/11

Not really a big deal.
When I finally get this NAS figured out and running as I want, I won't be needing access all the time like I'm having to do now.
I'll mark this thread solved.

Thanks for your input.

A.

Altoid · Off-topic

Hello:

golinux wrote:

Why would anyone want systemd in the first place?

Indeed ...
+1 8^D

systemd is the absolute opposite of basic Linux philosophy.
ie: Write programs that do one thing and do it well.

A.

Altoid · Hardware & System Configuration

Hello:

hevidevi wrote:

try these in your .bashrc if you do not already have them.
export HISTSIZE=10000
export HISTFILESIZE=10000
export HISTCONTROL=ignorespace:ignoredups

Hmm ...
I don't have a user set up on this system.
Maybe that's the reason? Have not had time to set up sudo either yet.

Edit:

I keep forgetting that this is a small footprint OS for embedded systems, a very different type of Linux.
That means that I should look in the right place and not bug my fellow Dev1 members.

OpenWRT does not use bash but ash.

From: https://forum.openwrt.org/t/enable-bash-history/70815

Ash (mainly the dash fork) is also fairly popular in embedded Linux systems. dash version 0.3.8-5 was incorporated into BusyBox 3, the catch-all executable often employed in this area, and is used in distributions like DSLinux, Alpine Linux 1, Tiny Core Linux and Linux-based router firmware such as OpenWrt, Tomato and DD-WRT.

and

ash is provided by busybox, which provides all basic shell & Linux default app features in OpenWrt.
You can enable the history feature in busybox and recompile a personal version of it for yourself, so that you can have ash that remembers history.

ash is part of the firmware image and while I can install the bash package, it will not survive a system upgrade.

There seems to be a work-around, I'll have to investigate further.

Thanks a lot for your input.

Best,

A.

Altoid · Hardware & System Configuration

Hello:

Playing around with SSH and my new My Book Live thingy, i have found a few things I'm used to do not work as expected.

This is the OpenWRT installed on the unit:

~# uname -a
Linux_book 5.4.179 #0 Wed Feb 16 20:29:10 2022 ppc GNU/Linux
~#

dmesg shows this:

One of those things is the bash history I use a lot.
It is an important part of my slow-ish training to eventually master the use of the terminal as much as possible.
eg: the history does not survive a reboot of the system.

How can I fix this?

Thanks in advance,

A.

Altoid · Hardware & System Configuration

Hello:

Altoid wrote:

... example of 2020's firmware for this system ...
... OpenWRT
... if anyone here has done anything on these WD thinguies.

Seems I'm the only one here scavenging on old hardware. 8^D

I'll mark this thread as solved.

I have managed to successfully install OpenWRT 21.02.2 to the WD-MBL and it is working, albeit with an expected issue: it seems that the APM821xx processor does not have a way to poweroff or even halt.

So while I'm installing a couple of missing utils I see if I can find a suitable work around, maybe with a script and a switch for when it needs to be moved or taken off-line for a few days.

Best,

A.

Altoid · Hardware & System Configuration

Hello:

garyk wrote:

You may find this helpful.

Thanks but I finally managed to successfully reset the unit late tonight.
After that it got assigned a proper IP by the router and I can access it via ssh and the UI via a browser.

After checking it out, I see it runs on an old linux kernel:

~# uname -a
Linux MyBookLive 2.6.32.11-svn70860 #1 Thu May 17 13:32:51 PDT 2012 ppc GNU/Linux
~#

I have to look into something newer without all the media suff the original FW has as I want to use it as a backup drive.
eg: Twonky, iTunes, etc.

But there's does not seem to be much available for PowerPC/ppc32 these days as Debian dropped support when Debian 8 came out.

The only example of 2020's firmware for this system that I have come across is OpenWRT which also has regular updates.
Also found someone who says he's been running Gentoo for about 10 years on his various units but he has now switched them all to OpenWRT.

I wonder if anyone here has done anything on these WD thinguies.

Thanks for your input.

Best,

O.

Altoid · Hardware & System Configuration

Hello:

Yewsterday I came across a practically new 1Tb MyBook Live for a bit under US$30 (!) and as I am needing a better backup routine, I went for it.
My only worry was that the 1Tb SATA drive would have some dings but even if it did, the hardware in the box was worth it.

The thing runs on an APM82181@800 MHz CPU, 256MB + 512Kb flash.
It has a SATA bay and Gigabit Ethernet LAN but no USB port.

After resetting it, when I hooked it up to the router it reported the proper MAC address with a 169.254.7.194 IP address.
Not the expected 192.168.1.1 or thereabouts.

As I was not able to get into the UI via browser, ssh or in any way get into the system and as I still had to check the drive before going forward, I decided to disassemble the case to remove the drive and hook it up to my main box with the idea of modifying a configuration file to set up another IP.

disks and gparted reported nothing nasty and gsmartcontrol gave it a clean bill of health.
No grown defects.

This is the drive's data and layout:

Model: WDC WD10EURX-63FH1Y0 (01.01A01)
Size: 1.0 TB (1,000,204,886,016 bytes)
Partitioning: GUID Partition Table
Serial: WD-WMC1U7235566

freespace   | swap partition 3 | partition 1       | partition 2       | partition 4: primary
16Mb        | 513Mb            | 2.0Gb             | 2.0Gb             | 996Gb
unallocated | basic data       | linux raid        | linux raid        | filesystem
                               | linux raid member | linux raid member | ext4

Unfortunately, I cannot mount the primary partition and get this error:

Error mounting /dev/sda4 at /media/groucho/7599bee0-ee74-4354-9c41-dbc05d70b49d: wrong fs type, bad option, bad superblock on /dev/sda4, missing codepage or helper program, or other error

When I try lsblk to see what's there I get this:

~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk 
|-sda1   8:1    0   1.9G  0 part 
|-sda2   8:2    0   1.9G  0 part 
|-sda3   8:3    0   489M  0 part 
`-sda4   8:4    0 927.2G  0 part 
--- snip ---
~$

When I try parted to see what's there I get this:

~$ parted -l
[sudo] password for groucho: 
Model: ATA WDC WD10EURX-63F (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name     Flags
 3      15.7MB  528MB   513MB                primary  msftdata
 1      528MB   2576MB  2048MB  ext3         primary  raid
 2      2576MB  4624MB  2048MB  ext3         primary  raid
 4      4624MB  1000GB  996GB   ext4         primary  msftdata
--- snip ---
~$

What confounds me is the gpt partition table, this is a 1TB drive and other configurations only go to 3Tb.
And the msftdata flag.

I have no Windows installation to do anything with.

There is the also possibility of using WRT instead of the WD software.
I'm sure it won't have the problems thousands of users had last year.

Any ideas?

Thanks in advance.

Best,

A.

Altoid · Hardware & System Configuration

Hello:

Marjorie wrote:

... installed a new version of zlib1g:amd64 (1:1.2.11.dfsg-2+deb11u1) from Chimaera-security this morning.

Thanks for the update on this.

Last night I updated my netbook and main box running Beowulf backported and saw the upgrade come in.

The following packages will be upgraded:
  rsyslog zlib1g zlib1g:i386 zlib1g-dev

Seems all is well and right on time as usual with Linux Devuan. 8^D

Best,

A.

Altoid · Hardware & System Configuration

Hello:

Marjorie wrote:

... fixed in Debian for Bookworm and Sid ...
... Stretch, Buster and Bullseye have yet to be fixed.
... expect it will be fixed shortly ...
... stable and older remain vulnerable ...

Thanks for the information.
I guess we can wait a bit more, it's been out there forever. ;^)

Best,

A.

Altoid · Hardware & System Configuration

Hello:

This article came up yesterday at ElReg:

Zlib crash-an-app bug finally squashed, 17 years later.
https://www.theregister.com/2022/03/30/ … /?td=rt-4a

It is about a long standing bug in the zlib data-compression library.
Having been reported in 2018, it was never looked at or fixed.
Until now.

https://www.openwall.com/lists/oss-secu … 22/03/24/1

Jessica Lyons Hardcastle @The Register wrote:

A patch is available on Github, and security analysts recommend updating to Zlib version 1.2.12. Linux distros Ubuntu and Alpine, to name two, have also implemented the fix in their latest releases.

Don't know how problematic this can be for the everyday Devuan user.
It has been out there forever ...

Best,

A.

Altoid · Installation

Hello:

myself wrote:

... seems the problem is with the wrong version of the dkms package.

I was able to fix it all by doing a manual installation:

apt -t beowulf-backports install nvidia-legacy-340xx-driver --no-install-recommends

Now ...

~$ apt list | grep installed | grep legacy-340xx
--- snip ---
libegl1-nvidia-legacy-340xx/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
libgl1-nvidia-legacy-340xx-glx/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
libgles1-nvidia-legacy-340xx/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
libgles2-nvidia-legacy-340xx/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
libnvidia-legacy-340xx-cfg1/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
libnvidia-legacy-340xx-eglcore/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
libnvidia-legacy-340xx-glcore/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
libnvidia-legacy-340xx-ml1/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-alternative/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver-bin/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver-libs/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
nvidia-legacy-340xx-kernel-dkms/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-kernel-support/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-legacy-340xx-vdpau-driver/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
nvidia-settings-legacy-340xx/oldstable,now 340.108-1~deb10u1 amd64 [installed]
xserver-xorg-video-nvidia-legacy-340xx/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed,automatic]
~$

I think (?) what was happening is related to what rolfie points out here:

https://dev1galaxy.org/viewtopic.php?pid=35311#p35311

In any case, now it works.

Best,

A.

Altoid · Installation

Hello:

After my success with updating the backported kernel in my main Beowulf box, I decided to do the same with my parallel Beowulf installation.
It lives on a separate drive in the same box, albeit with a spartan Openbox desktop which is operational but unfinished.

As I was going through the update, I noticed that it was going to Linux devuan 5.10.0-0.bpo.12-amd64 which when I did the same in my main box had not yet been signed.

On reboot, just like with my main box, I was not able to get X started so followed the steps I took here to get things fixed:

https://dev1galaxy.org/viewtopic.php?id=4948

Basically install what was missing via ...

# apt -t beowulf-backports install linux-image-amd64
and
# apt -t beowulf-backports install linux-headers-amd64

But no, no cigar.

There seems to be some sort of dependency problem somewhere.
Here is what I could fish out of /var/log/apt/term.log:

Log started: 2022-03-22  17:32:49
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-3~deb10u1) ...
Removing old nvidia-legacy-340xx-340.108 DKMS files...

------------------------------
Deleting module version: 340.108
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 5.10.0-0.bpo.12-amd64
Building initial module for 5.10.0-0.bpo.12-amd64

Error! Bad return status for module build on kernel: 5.10.0-0.bpo.12-amd64 (x86_64)      <---------------------------------------                    

Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for more information.
error processing package nvidia-legacy-340xx-kernel-dkms (--configure):
installed nvidia-legacy-340xx-kernel-dkms package post-installation script subprocess returned error exit status 10
dependency problems prevent configuration of nvidia-legacy-340xx-driver:

nvidia-legacy-340xx-driver depends on nvidia-legacy-340xx-kernel-dkms (= 340.108-3~deb10u1) | nvidia-legacy-340xx-kernel-340.108; however:
  Package nvidia-legacy-340xx-kernel-dkms is not configured yet.
  Package nvidia-legacy-340xx-kernel-340.108 is not installed.
  Package nvidia-legacy-340xx-kernel-dkms which provides nvidia-legacy-340xx-kernel-340.108 is not configured yet.

error processing package nvidia-legacy-340xx-driver (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-legacy-340xx-kernel-dkms
 nvidia-legacy-340xx-driver
Log ended: 2022-03-22  17:33:20

I did not encounter any problems when I later updated my main box from Linux devuan 5.10.0-0.bpo.11-amd64 to the now signed Linux devuan 5.10.0-0.bpo.12-amd64.

I then went looking to see what may be amiss:

uname -a gave the same printout and cat /etc/apt/sources.list shows the same in both installations:

~$ cat /etc/apt/sources.list
## package repositories

# Changed - 20210218 - upgrade to Beowulf

# beowulf stable
deb http://deb.devuan.org/merged/ beowulf main contrib non-free 
deb http://deb.devuan.org/merged/ beowulf-security main contrib non-free 
deb http://deb.devuan.org/merged/ beowulf-updates main contrib non-free 

# needed x virtualbox backport - enable to update package
deb http://deb.devuan.org/merged/ beowulf-backports main contrib non-free 

# virtual box repository x installation
deb https://download.virtualbox.org/virtualbox/debian/ buster contrib non-free 
~$

Then I looked for anomalies in the installed 340xx packages and found that the lists were not the same:

My main box has 17 packages:

libegl1-nvidia-legacy-340xx/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
libgl1-nvidia-legacy-340xx-glx/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
	
        libgles1-nvidia-legacy-340xx/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]    <---- missing
	libgles2-nvidia-legacy-340xx/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]    <---- missing
	libnvidia-legacy-340xx-cfg1/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]     <---- missing

libnvidia-legacy-340xx-eglcore/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
libnvidia-legacy-340xx-glcore/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
libnvidia-legacy-340xx-ml1/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
nvidia-legacy-340xx-alternative/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver-bin/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver-libs/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
nvidia-legacy-340xx-driver/oldstable,now 340.108-3~deb10u1 amd64 [installed]

	nvidia-legacy-340xx-kernel-dkms/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]    <---- bad version

nvidia-legacy-340xx-kernel-support/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]
nvidia-legacy-340xx-vdpau-driver/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]

	nvidia-settings-legacy-340xx/oldstable,now 340.108-1~deb10u1 amd64 [installed,automatic]    <---- missing

xserver-xorg-video-nvidia-legacy-340xx/oldstable,now 340.108-3~deb10u1 amd64 [installed,automatic]

But the parallel installation has only 13 packages and the wrong version for the package that is not able to complete its job: nvidia-legacy-340xx-kernel-dkms/oldstable-backports.

ie:
The working installation has nvidia-legacy-340xx-kernel-dkms /oldstable-backports,now 340.108-10~bpo10+1 amd64
The non-working installation has nvidia-legacy-340xx-kernel-dkms /oldstable-backports,now 340.108-3 ~deb10u1 amd64

340.108-10~bpo10+1 is the backported driver
340.108-3 ~deb10u1 does not seem to be.

Any idea as to why this is so?
Can't figure out what is wrong or how it got like this.

I tried manually installing the missing packaged but it seems the problems is with the wrong version of the dkms package.

Thanks in advance.

Best,

A.

Altoid · Installation

Hello:

rolfie wrote:

... why I don't use NVidea at all.

The pair of cards were at a really great price.
Impossible to pass up or resist, for that matter.

rolfie wrote:

... run a setup for your drivers that builds the modules.
... need the headers for the new kernel ...
... need them for building the VBox kernel modules.

Yes.
I saw from the terminal that the VM that runs pihole was not up and the printout when atempting to run /sbin/vboxconfig put me up to speed.
Much more verbose in that respect than the nvidia drivers. 8^/

rolfie wrote:

... a manual process.

Sure.
Like installing a backported kernel.

rolfie wrote:

Try that:

# apt -t beowulf-backports install linux-headers-amd64

Done.
Booted into my SLiM log-it as always.

groucho@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.11-amd64 #1 SMP Debian 5.10.92-1~bpo10+1 (2022-02-03) x86_64 GNU/Linux
groucho@devuan:~$

Apparently everything runs as it should.
There may be a problem with the wicd daemon not starting right away, I'll have to look into that.

Thanks a lot for your input.

Best,

A.

Altoid · Installation

Hello:

rolfie wrote:

Run the previously posted command, that will do the job.

Done.
But the system does not find the nvidia driver module so I cannot get a desktop.
Just command line.

X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[    63.984] Build Operating System: Linux 5.10.0-10-amd64 x86_64 Debian
[    63.985] Current Operating System: Linux devuan 5.10.0-0.bpo.11-amd64 #1 SMP Debian 5.10.92-1~bpo10+1 (2022-02-03) x86_64
--- snip ---
[    64.025] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    64.025] (EE) NVIDIA:     system's kernel log for additional error messages and
[    64.025] (EE) NVIDIA:     consult the NVIDIA README for details.

Makes sense that it cannot find it.
ie: whereas there are 340xx modules in /lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms ...

~$ locate 340xx
--- snip ---
/lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms/nvidia-legacy-340xx-uvm.ko
/lib/modules/5.10.0-0.bpo.3-amd64/updates/dkms/nvidia-legacy-340xx.ko
--- snip ---

... there is no /updates or /updates/dkms directory in /lib/modules/5.10.0-0.bpo.11-amd64

~$ ls /lib/modules/5.10.0-0.bpo.11-amd64
kernel         modules.alias.bin  modules.builtin.bin      modules.dep      modules.devname  modules.softdep  modules.symbols.bin
modules.alias  modules.builtin    modules.builtin.modinfo  modules.dep.bin  modules.order    modules.symbols
~$

I did find this one via apt list but it is the one I have installed:

~$ apt list | grep nvidia-legacy-340xx | grep dkms
--- snip ---
nvidia-legacy-340xx-kernel-dkms/oldstable-backports,now 340.108-10~bpo10+1 amd64 [installed]
--- snip ---
~$

System's working with the previous version so it's not a serious problem.
But I don't get what has happened.

Thanks in advance.

Best,

A.

Altoid · Installation

Hello:

rolfie wrote:

Besides the backports kernel you may also install the backports metapackage.

I see ...
Sort of.

rolfie wrote:

... you will lose the updates of the main kernel packages ...
... get the updates from backports.

rolfie wrote:

I am using backports headers and images only, my Chimaera is running now with 5.16.

It would seem, if I understand correctly, that you have with your Chimaera) installation what I want to have with my Beowulf installation.

ie: Beowulf with a an up-to-date 5.10 backported kernel
Eventually, a couple of (or all, don't know yet) backported applications.

Not Chimaera because of the reasons posted previously.

How can I get this done?

Thanks in advance.

Best,

A.

Altoid · Installation

Hello:

GlennW wrote:

... use the bpo kernel.
... search for upgrades for it, linux-image...
... grab the kernel headers packages too.

I see.

apt says this:

groucho@devuan:~$ apt list | grep linux-image-5.10.0-0.bpo | grep -i amd64/oldstable 
--- snip ---
linux-image-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$

and this:

groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64/oldstable 
--- snip ---
linux-headers-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-cloud-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-rt-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$

This is what I have installed:

~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64 | grep installed
--- snip ---
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
~$

~$ apt list | grep linux-image-5.10.0-0.bpo | grep -i amd64 | grep installed
--- snip ---
linux-image-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
~$

So ...

I just do apt install linux-headers-5.10.0-0.bpo.12-amd64?
I'm assuming the matching linux-image gets dragged along although it seems it is unsigned:

~$ apt list | grep linux-image-5.10.0-0.bpo.12-amd64
--- snip ---
linux-image-5.10.0-0.bpo.12-amd64-dbg/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-image-5.10.0-0.bpo.12-amd64-unsigned/oldstable-backports 5.10.103-1~bpo10+1 amd64    <-------------
~$

Thanks in advance.

Best,

A.

Altoid · Installation

Hello:

alphalpha wrote:

why not use the standard kernel?

First there's the issue of the nvidia-legacy-340xx drivers and then the demise of python 2.7.18.
There are a couple of applications that will not work in chimaera, which is why I use the backported kernel.

Thanks for your input.

Best,

A.

Altoid · Installation

Hello:

fsmithred wrote:

... no metapackage for backports kernels ...

I'll take your word for it.
No idea what that does. 8^/

fsmithred wrote:

... only updates you would get would be if the kernel version didn't change.

I found out about this by chance while skimming through the synaptic lists, which I do every so often.
Otherwise I have become used to apt for updating and installing.

Maybe it is because the backported kernel was installed locally?

groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep installed
--- snip ---
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]
linux-headers-5.10.0-0.bpo.3-common/now 5.10.13-1~bpo10+1 all [installed,local]
groucho@devuan:~$

groucho@devuan:~$ apt list | grep linux-headers-5.10.0-0.bpo | grep -i amd64
--- snip ---
linux-headers-5.10.0-0.bpo.11-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-cloud-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.11-rt-amd64/oldstable-backports 5.10.92-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-cloud-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.12-rt-amd64/oldstable-backports 5.10.103-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.3-amd64/now 5.10.13-1~bpo10+1 amd64 [installed,local]     <--------------------
linux-headers-5.10.0-0.bpo.9-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-cloud-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
linux-headers-5.10.0-0.bpo.9-rt-amd64/oldstable-backports 5.10.70-1~bpo10+1 amd64
groucho@devuan:~$

Thanks in advance.

Best,

A.

Altoid · Installation

Hello:

My Devuan Beowulf runs on a backported kernel:

~$ uname -a
Linux devuan 5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) x86_64 GNU/Linux
groucho@devuan:~$

When I installed it I assumed it would be updated as it evolved, but I have just noted that it has not.
And that the latest version is 5.10.0-0.bpo.12-amd64.

I think I may omitted something when I installed it?
Some priority setting perhaps?

Please advise, don't want to screw up something.

Thanks in advance,

A.

Altoid · Hardware & System Configuration

Hello:

pcalvert wrote:

... LibreOffice installed and a search for "log4j" found nothing.

I got rid of it by purging libreoffice-nlpsolver and libreoffice-report-builder.

pcalvert wrote:

... don't allow software to install recommended packages ...

I followed fsmithred's advice and set up a system wide block for any and all recommends:
https://dev1galaxy.org/viewtopic.php?pid=35176#p35176

pcalvert wrote:

... installed LibreOffice Writer ...

I use Writer, Calc and Draw quite often.
But none of the crap that subreptitiously also comes with the stock installation.

By weeding out a lot of recommends, my java load has been somewhat reduced:

~$ apt list | grep installed | grep -i java
ca-certificates-java/oldstable,oldstable,now 20190405 all [installed,automatic]
java-common/oldstable,oldstable,now 0.71 all [installed,automatic]
javascript-common/oldstable,oldstable,now 11 all [installed,automatic]
libatk-wrapper-java-jni/oldstable,now 0.33.3-22+deb10u1 amd64 [installed,automatic]
libatk-wrapper-java/oldstable,oldstable,now 0.33.3-22+deb10u1 all [installed,automatic]
libel-api-java/oldstable,oldstable,now 3.0.0-2+deb10u1 all [installed,automatic]
libjavascriptcoregtk-4.0-18/oldstable-security,now 2.34.6-1~deb10u1 amd64 [installed,automatic]
libjsp-api-java/oldstable,oldstable,now 2.3.4-2+deb10u1 all [installed,automatic]
libreoffice-java-common/oldstable,oldstable,now 1:6.1.5-3+deb10u7 all [installed]
libservlet-api-java/oldstable,oldstable,now 4.0.1-2 all [installed,automatic]
libservlet3.1-java/oldstable,oldstable,now 1:4.0.1-2 all [installed]
libwebsocket-api-java/oldstable,oldstable,now 1.1-1+deb10u1 all [installed,automatic]
groucho@devuan:~$

Most (not all) due to LO.
To be quite honest, I'd rather use Lotus 123 than Calc or Excel and a standalone Word 6.0 instead of Writer.

I recently installed Lotus Smart Suite 9.8.2 on a XPSP3 VM.
I was then reminded of how the installer provided you with the means of choosing exactly what parts of the Suite you wanted to install.
Cannot understand how Linux, so much choice oriented, did not take up on that basic idea.

---------------------------------------------------------------------------------------------------------------------
I think Linux packagers should look back and take note of that important feature.
---------------------------------------------------------------------------------------------------------------------

pcalvert wrote:

... long preferred to use AbiWord and Gnumeric instead.

I keep/maintain few essential spreadsheets that have been growing/evolving over the last 20 years.
Originally in *.xls format, I keep them that way and run the risk of using LO to maintain them instead of using Excel in a VM.
Had a few unpleasant glitches at the start but they have been fixed.

Hopefully these spreadsheets will not be needed in a year's time.
Then I will see about ditching Calc/Writer to try gnumeric and AbiWord.

Thank you for your input.

Best,

A.

Altoid · Installation

Hello:

rbit wrote:

An alternate option for this particular case ...

Hmm ...
No thanks.

I'd prefer that any and all recommends be something I get to consider installing to then decide and not something that is installed because some Debian packager though it was a good idea.

That is how the Linux bloat we have today started ...

I think that a system-wide block on recommends is a great idea.
Of course, YMMV.

Thank you for your input.

Best,

A.

Altoid · Installation

Hello:

deepforest wrote:

Thanks ...

You're welcome.

deepforest wrote:

... try and report here ...

Please do.
A step by step description and a printout of the terminal as the job progresses would be ideal.

eg: like I did here: https://dev1galaxy.org/viewtopic.php?pid=24694#p24694

deepforest wrote:

Arch AUR community patched this drivers for new kernels ...

Please post the link.
Maybe the Devuan team may be able to do something with that. (?)

Best,

A.

Altoid · Installation

Hello:

deepforest wrote:

thanks for help!

You're welcome.

deepforest wrote:

... is it worth trying to install nvidia-legacy-340xx ...

The 340XX drivers were not dropped by Debian / Devuan.
It was Nvidia that dropped support for graphic cards working only with the 340XX driver.

The 340XX drivers are propiertary/closed source and Debian cannot supply a 340XX package because Nvidia will not update them for newer kernels.

True to their A1-asshole mentality, they will not release the code for the hardware to be used in newer kernels.
That said, it seems that it may be possible to run them on Debian Bullseye/Devuan Chimaera:

https://forums.debian.net/viewtopic.php … 73#p742573

I have not attempted to do it, no idea if it works without problems.

See here: https://forums.debian.net/viewtopic.php … 77#p745277
It is a patched proprietary driver "nvidia-legacy-340xx-driver_340.108-11" from "Debian Sid" repository.

If you try and succeed, please let us know how you did it and what results you got.

And yes, Nouevau does not seem to be up to scratch.

A few years ago (when XP was mothballed) and decided my definitive move to Linux, I was met with the fact that there were no drivers for my excellent Matrox G550 PCI cards as there were no available drivers for Linux, another proprietary fuck-up.

Between a rock and a hard place, I decided to invest in a whole new setup which is the one I have been using since, with a few HW upgrades.
A Sun Ultra 24 WS running 2xNVidia FX580 for three 19" monitors using the NVidia 340XX proprietary drivers, works perfect and do not need anything more.

If I can upgrade to Devuan Chimaera using these cards, fine.
And if Chimarea is the last kernel I can use with them, I'll probably stay there using a backported kernel for as long as I can.

Of course, YMMV.

Best,

A.

The officially official Devuan Forum!

#976 Re: Hardware & System Configuration » [SOLVED] Script $PATH question » 2022-04-17 16:56:08

#977 Hardware & System Configuration » [SOLVED] Script $PATH question » 2022-04-17 14:17:58

#978 Re: Hardware & System Configuration » [SOLVED] Bash history configuration » 2022-04-15 22:44:59

#979 Re: Off-topic » Why don't we just fork systemd and remove unneccessary bloat? » 2022-04-15 22:32:39

#980 Re: Hardware & System Configuration » [SOLVED] Bash history configuration » 2022-04-14 14:32:57

#981 Hardware & System Configuration » [SOLVED] Bash history configuration » 2022-04-14 14:07:55

#982 Re: Hardware & System Configuration » [SOLVED] WD MyBook Live with Devuan » 2022-04-14 13:58:08

#983 Re: Hardware & System Configuration » [SOLVED] WD MyBook Live with Devuan » 2022-04-13 07:01:32

#984 Hardware & System Configuration » [SOLVED] WD MyBook Live with Devuan » 2022-04-12 21:29:36

#985 Re: Hardware & System Configuration » [SOLVED] Zlib crash-an-app bug - does it affect us? » 2022-04-02 10:46:40

#986 Re: Hardware & System Configuration » [SOLVED] Zlib crash-an-app bug - does it affect us? » 2022-03-31 22:59:01

#987 Hardware & System Configuration » [SOLVED] Zlib crash-an-app bug - does it affect us? » 2022-03-31 21:12:35

#988 Re: Installation » [SOLVED] More Nvidia 340xx woes .... » 2022-03-22 23:05:56

#989 Installation » [SOLVED] More Nvidia 340xx woes .... » 2022-03-22 21:17:38

#990 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 18:39:15

#991 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 16:25:21

#992 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 11:54:02

#993 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 01:13:47

#994 Re: Installation » [SOLVED] Backported kernel update » 2022-03-19 22:24:22

#995 Re: Installation » [SOLVED] Backported kernel update » 2022-03-19 22:17:34

#996 Installation » [SOLVED] Backported kernel update » 2022-03-19 21:01:13

#997 Re: Hardware & System Configuration » Important - log4j exploit alarm affecting Linux » 2022-03-19 11:56:15

#998 Re: Installation » apparmor foisted on, by default? » 2022-03-18 21:13:28

#999 Re: Installation » [SOLVED] any chances to install nvidia-legacy-340xx on Devuan chimaera? » 2022-03-18 17:56:12

#1000 Re: Installation » [SOLVED] any chances to install nvidia-legacy-340xx on Devuan chimaera? » 2022-03-18 13:56:19

Board footer