You are not logged in.
- Topics: Active | Unanswered
#1176 Re: Devuan Derivatives » Support for DevuanDog! » 2021-06-02 17:05:47
Hello:
BusterDog is still available and active?
Hmm ...
No idea.
Not my dog.
Sadly, I haven't had a dog since I was 16.
What is your link to download your Live iso?
I don't have a Live iso, hence I have no link to anything you can download.
Since July 2020 there is no activity on your forum.
Makes sense ...
I don't have a forum.
Never had one.
I don't understand how a nice system like DevuanDog has been discontinued.
Hmm ...
Ask the author?
Or carefully read what he posted here --> https://oldforum.puppylinux.com/viewtop … c#p1040932
ie:
Reason is that I've found a self-supporting way, which I prefer, to avoid systemd, BusterDog is based on Debian Buster with a few alterations to make possible running without systemd.
Sorry ...
It's quite all right.
Every one has a bad day at some time or another.
I have one every week.
Usually on tuesdays, occasionally fridays.
... in what flavor of Devuan do you have software updated to date with firefox which is about version 89?
Sorry to dissapoint you.
I don't have any flavours of Devuan.
Just the plain Devuan Beowulf I got here.
But my all time favourite ice cream flavour is bitter chocolate with dark chocolate chips mixed in.
Yes, redundancy is a real thing for me.
Cheers, 8^P
A.
#1177 Re: Devuan Derivatives » Support for DevuanDog! » 2021-06-02 12:36:12
Hello:
Why did devuandog stay in 2019? ...
It was discontinued/terminated.
See: https://oldforum.puppylinux.com/viewtop … 2#p1040932
Reason is that I've found a self-supporting way, which I prefer, to avoid systemd, BusterDog is based on Debian Buster with a few alterations to make possible running without systemd.
A.
#1178 Re: Other Issues » Tape drives » 2021-05-23 21:11:33
Hello:
that might be it
sadly ftape and zftape are not in the kernel anymore
Indeed ...
The problem was that this hardware (my opinion) was not really something solid like all the SCSI tape drives out there at the time.
The advantage was that it was much less expensive to get a QIC/Travan etc. and run it from a parallel port or IDE adaptor card.
But for most, not the real thing.
In my day, I had a QIC and a Travan under Windows but found them to be slow and unreliable.
Here's a link to old Ubuntu releases:
http://old-releases.ubuntu.com/releases/
Try Ubuntu 5.10 (Breezy Badger) or Ubuntu 6.06.2 LTS (Dapper Drake), both have 64bit DVD Live editions:
http://old-releases.ubuntu.com/releases … -amd64.iso
http://old-releases.ubuntu.com/releases … -amd64.iso
... any practical usecase for that tape drive ...
Quite so.
With relatively inexpensive fast HDDs to make a multiple Tb NAS with very little investment, tape ends up being cumbersome.
And no, I will not store anything in any cloud.
A cloud is just water vapour: one moment it's there, the next it's gone.
I had my last DAT DD2 drive sitting atop my box for the longest while and finally decided to move it out of the way last week.
A beautiful Sun Microsystems external box hosting a Seagate Scorpion 8000 which saw very little use.
Maybe the box, PS and SCSI board will be of use for something.
... still curious what might be sitting on that tape
Ahh ...
So that's it. 8^D !
... put it back into that old 486 where i ripped it out ...
You'll still need the application used to make the tape or download it raw and pick out the bits.
Once you find out what you can do by booting the Ubuntu DVD, you may want to make a VM see if you can access it from there.
Much better than trying anything with the 486.
Cheers,
A.
#1179 Re: Other Issues » Tape drives » 2021-05-22 17:16:32
Hello:
It seems that what is needed is to load the proper driver modules.
ie: modprobe zftape -> depends ftape
This will load zftape and ftape, creating all needed devices under /dev, so there's no MAKEDEV to run.
But this was when you could actually find ftape and zftape for your kernel.
zftape and ftape went awol quite a few years ago, so they were taken out of the kernel from 2.x something on.
I have read in one post that maybe some old Ubuntu may have it, so booting that from a CD may be a solution.
https://retrocomputing.stackexchange.co … with-ftape
Check out these posts:
http://thewunders.org/SxS/storage/ftape.html
https://tldp.org/HOWTO/Ftape-HOWTO-6.html#ss6.1
https://github.com/Godzil/ftape
https://dmitrybrant.com/2020/11/01/how- … -qic-tapes
Good luck ... 8^)
Best,
A.
#1180 Re: Installation » Kernel upgrade: apparmor and tomoyo » 2021-05-17 18:30:18
Hello:
Everything not needed to run a system should remain optional ...
... don't foist these things onto ordinary desktop users ...
Evidently that's not the vision of those who are in a position to run the Debian show and decide the hows, why's and whens.
... a good working distro to do my daily tasks ..
I'm glad to see we're more than one.
But I'm afraid the dice have already been rolled.
And the result was not in our favour.
Hence the very existence of Devuan.
Best,
A.
#1181 Re: Installation » Kernel upgrade: apparmor and tomoyo » 2021-05-17 15:51:26
Hello:
... this sort of config should be opt in even at the kernel level.
Exactly my point.
If and when I want/need to install a Mandatory Access Control scheme for my rig's security, I'll just apt install the required modules and configure.
Makes no sense to call it a security feature ...
I could not care less about what it is called.
It is being made part of the kernel just because some DH decided it should be.
Why? On the basis of what?
Next thing you know you'll have to set it up/configure if you want the kernel to work.
eg: no apparmor/tomoyo/SELinux? No WAN/LAN.
This has all the colourings of one of Poettering's diktats.
Like this other one:
https://dev1galaxy.org/viewtopic.php?id=4136
Bad, bad, bad ...
A.
#1182 Re: Installation » Kernel upgrade: apparmor and tomoyo » 2021-05-16 22:46:29
Hello:
I think not:
https://wiki.archlinux.org/title/TOMOYO_Linux#
You were quite right, I stand corrected.
In spite of what wiki.archlinux says, adding security=none disables tomoyo as there are no entries for it in dmesg, kern.log or syslog.
Edit: security=none not only disables tomoyo, it also makes apparmor=0 unneccesary. 8^D
Thanks for the heads up. 8^)
Best,
A.
#1183 Re: Installation » Kernel upgrade: apparmor and tomoyo » 2021-05-16 22:30:18
Hello:
... Way Too Many.
Indeed ...
tomoyo-tools ...
... why that is enabled in debian's standard linux-image is unkown to me ...
Hmm ...
Maybe it's yet another one of Poettering's brillant ideas?
Apparently adding security=none to the boot command should disable this one.
I was wondering about that.
A bit for disabling apparmor but none for disabling tomoyo?
I think not:
https://wiki.archlinux.org/title/TOMOYO_Linux#
TOMOYO Linux 2.x is the Linux mainline kernel branch of development. In June 2009, TOMOYO was merged into the Linux kernel version 2.6.30 and it uses standard Linux Security Module (LSM) hooks. However, the LSM hooks must be extended further in order to port the full MAC functionality of TOMOYO Linux into the Linux kernel. Thus, it does not yet provide equal functionality with the 1.x branch of development. This chart compares the differences between each branch.
Disabling
For kernels 5.1 and above remove tomoyo from the lsm= kernel parameter or remove lsm= entirely. <- | x |
For kernels 3.2 to 5.0 change the kernel parameter security=tomoyo to security=none.
I'll try it out and report.
-------> I_don't_like_this. 8^|
If and when I want/need to install a Mandatory Access Control scheme for my rig's security, I'll just apt install the required modules and configure.
Why do I have to have the kernel looking to run something that is not there?
Thanks for your input.
Best,
A.
#1184 Installation » Kernel upgrade: apparmor and tomoyo » 2021-05-16 19:29:46
- Altoid
- Replies: 8
Hello:
My 4.19 Devuan Beowulf, unlike ascii which had it disabled by default, set up apparmor as if I had actually asked for it.
I let it stay on and after reading around a bit, decided that it was not worth keeping around.
So I uninstalled it and added apparmor=0 to my kernel command line so it would not be asking for it.
Fast forward to my upgrading the installation to the 5.10 kernel:
groucho@devuan:~$ 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:~$ The 5.10 kernel also recommends apparmor:
groucho@devuan:~$ aptitude why apparmor
i linux-image-5.10.0-0.bpo.3-amd64 Recommends apparmor
groucho@devuan:~$ So it does as the upgrade from ascii to Beowulf did and installs apparmor.
Now ...
Seeing that my kernel command line had the apparmor=0 bit, you'd think that it would leave it alone and skip installing apparmor.
After all, it left the rest of the command line stanzas as they were.
But no ...
Not only did it install apparmor but it also removed the apparmor=0 bit from the kernel command line.
No big deal: I just uninstalled it and returned the kernel command line to what I had set it.
Then while looking for clues as to what goes on in my system when I get a bad shutdown, I found this in dmesg:
In dmesg ie: at boot
[ 21.906451] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.Also at shutdown:
In kern.log and syslog:
May 16 13:57:16 devuan kernel: [14429.313238] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.I had to look it up as I had no idea as to what tomoyo was, let alone of its existence.
What is all this about?
Is it just me or am I seeing far too many (unrequired) Mandatory Access Control instances in the Linux kernel?
Cheers,
A.
#1185 Re: Other Issues » Tape drives » 2021-05-15 15:49:31
Hello.
... iomega tape 250 drive along with this 3gb ditto tape ...
Nice find. 8^)
... how do i get it to work?
The key to this may be here:
Technical aspects
Ditto internal drives were connected through the floppy drive channel and used MFM encoding to store data (the same method as on older floppy drives). An ISA accelerator card called the Ditto Dash, providing higher speed than a stock floppy controller, was also available.
--- snip ---
Check that the USB Floppy adapter is correctly inserted.
It should (?) have a key (like the IDE cables did) or some indication in the adapter's manual/instruction sheet.
See:
https://en.wikipedia.org/wiki/Ditto_(drive)
https://www.manualslib.com/products/Iom … 35190.html <---- | x |
https://johnvidler.co.uk/linux-journal/LJ/022/1215.html
http://pong.tamu.edu/~baum/linux/LDP/HO … TO-28.html
Edit:
https://tldp.org/HOWTO/pdf/ZIP-Drive.pdf
Best,
A.
#1186 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-13 19:56:13
Hello:
... and report back.
Done.
groucho@devuan:~$ 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:~$ groucho@devuan:~$ apt policy nvidia-legacy-340xx-kernel-dkms
nvidia-legacy-340xx-kernel-dkms:
Installed: 340.108-10~bpo10+1
Candidate: 340.108-10~bpo10+1
Version table:
*** 340.108-10~bpo10+1 100
100 http://deb.devuan.org/merged beowulf-backports/non-free amd64 Packages
100 /var/lib/dpkg/status
340.108-3~deb10u1 500
500 http://deb.devuan.org/merged beowulf/non-free amd64 Packages
groucho@devuan:~$ Q: what does *** after Version table: mean?
With respect to e1000e-3.8.7, I guess now it's time to wait and see if there's another bad_shutdown or bad_boot and if they leave any trace
Maybe the additons to /etc/default/acpi-support have some effect?
---
Edit:
Last night I realised that the e1000e driver module now put in use by the 5.10 kernel upgrade was most probably the current one ie: e1000e-3.8.7.
But I had not applied the five patches, so that's done now.
---
Thanks for your input.
Best,
A.
#1187 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-13 17:17:36
Hello:
Did you try nvidia drivers from backports / non-free?
Yes.
I do have that in my /etc/apt/sources.list.
Must be a question of package priorities.
Will have to specifically install that: apt install nvidia-legacy-340xx-kernel-dkms/stable-backports
I'll get it done and report back.
Thanks for your input.
Best,
A.
#1188 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-13 00:03:58
Hello:
I'll apply patch 1005 and report back with whatever results I get.
Right, here we go.
groucho@devuan:/usr/src/e1000e-3.8.7$ sudo patch -p0 -i /usr/src/e1000e-patch/1005-e1000e_387_pm_freeze_sane_detach.patch
patching file src/netdev.c
groucho@devuan:/usr/src/e1000e-3.8.7$groucho@devuan:/usr/src/e1000e-3.8.7/src$ sudo make
make[1]: Entering directory '/usr/src/linux-headers-4.19.0-16-common'
make[2]: Entering directory '/usr/src/linux-headers-4.19.0-16-amd64'
CC [M] /usr/src/e1000e-3.8.7/src/netdev.o
/usr/src/e1000e-3.8.7/src/netdev.c: In function 'e1000e_pm_freeze':
/usr/src/e1000e-3.8.7/src/netdev.c:7401:3: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
int count = E1000_CHECK_RESET_COUNT;
^~~
LD [M] /usr/src/e1000e-3.8.7/src/e1000e.o
Building modules, stage 2.
MODPOST 1 modules
CC /usr/src/e1000e-3.8.7/src/e1000e.mod.o
LD [M] /usr/src/e1000e-3.8.7/src/e1000e.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.19.0-16-amd64'
make[1]: Leaving directory '/usr/src/linux-headers-4.19.0-16-common'
groucho@devuan:/usr/src/e1000e-3.8.7/src$groucho@devuan:/usr/src/e1000e-3.8.7/src$ sudo modinfo /usr/src/e1000e-3.8.7/src/e1000e.ko
filename: /usr/src/e1000e-3.8.7/src/e1000e.ko
version: 3.8.7-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 7C3F06437067F7EF077432C
alias: pci:v00008086d00001A1Dsv*sd*bc*sc*i*
--- snip ---
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends:
retpoline: Y
name: e1000e
vermagic: 4.19.0-16-amd64 SMP mod_unload modversions
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
parm: TxIntDelay:Transmit Interrupt Delay (array of int)
parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
parm: RxIntDelay:Receive Interrupt Delay (array of int)
parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
parm: IntMode:Interrupt Mode (array of int)
parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
parm: EEE:Enable/disable on parts that support the feature (array of int)
parm: Node:[ROUTING] Node to allocate memory on, default -1 (array of int)
parm: debug:Debug level (0=none,...,16=all) (int)
groucho@devuan:/usr/src/e1000e-3.8.7/src$dmesg at boot
groucho@devuan:~$ sudo dmesg | grep -i "e1000e\|00:19"
[ 1.079755] pci 0000:00:19.0: [8086:10bd] type 00 class 0x020000
[ 1.079770] pci 0000:00:19.0: reg 0x10: [mem 0xf5fc0000-0xf5fdffff]
[ 1.079776] pci 0000:00:19.0: reg 0x14: [mem 0xf5ffe000-0xf5ffefff]
[ 1.079783] pci 0000:00:19.0: reg 0x18: [io 0xac00-0xac1f]
[ 1.079830] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 2.147352] e1000e: loading out-of-tree module taints kernel.
[ 2.215009] e1000e: module verification failed: signature and/or required key missing - tainting kernel
[ 2.316026] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[ 2.333730] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[ 2.357402] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2.368687] e1000e 0000:00:19.0: PHY Smart Power Down Disabled
[ 2.390290] e1000e 0000:00:19.0: EEE Support was initialized to be enabled
[ 2.412085] e1000e 0000:00:19.0: EEE Support has been reset to be disabled
[ 2.897162] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:14:4f:4a:a2:81
[ 2.897164] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 2.897182] e1000e 0000:00:19.0 eth0: MAC: 7, PHY: 6, PBA No: FFFFFF-0FF
[ 27.302085] e1000e 0000:00:19.0 eth0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 27.314226] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
groucho@devuan:~$dmesg for rmmod -v e1000e
groucho@devuan:~$ sudo dmesg
--- snip ---
[10140.513586] e1000e: PCI REMOVE PTP
[10140.513590] e1000e: PCI REMOVE TIMER
[10140.513593] e1000e: PCI REMOVE CANCEL WORK SYNC
[10140.513595] e1000e: PCI REMOVE HW TIMESTAMP
[10140.513617] e1000e: NETDEV CLOSE ENTERED
[10140.513619] e1000e: NETDEV CLOSE WAIT DONE
[10140.513620] e1000e: NETDEV CLOSE DEV IS PRESENT
[10140.741067] e1000e: NETDEV CLOSE DEV IS DOWN
[10140.741081] e1000e: NETDEV CLOSE FREE IRQ
[10140.741086] e1000e 0000:00:19.0 eth0: NIC Link is Down
[10140.741087] e1000e: NETDEV CLOSE LINK DOWN MSG
[10140.741089] e1000e: NETDEV CLOSE NAPI DISABLED
[10140.741099] e1000e: NETDEV CLOSE FREE TX RES
[10140.741121] e1000e: NETDEV CLOSE FREE RX RES
[10140.741123] e1000e: NETDEV CLOSE VLAN DONE
[10140.741125] e1000e: NETDEV CLOSE HW CTRL RELEASED
[10140.741128] e1000e: NETDEV CLOSE DONE
[10140.756902] e1000e: PCI REMOVE UNREGISTER NETDEV
[10140.756908] e1000e: PCI REMOVE WAKE NO RESUME
[10140.756911] e1000e: PCI REMOVE RELEASE HW CONTROL
[10140.756951] e1000e: PCI REMOVE INT AND TX RX RING
[10140.756968] e1000e: PCI REMOVE SELECTED REGIONS
[10140.772962] e1000e: PCI REMOVE FREE NETDEV
[10140.772965] e1000e: PCI REMOVE DISABLE ERR REPORTING
[10140.773065] e1000e: PCI REMOVE DISABLE DEVICE
--- snip ---
groucho@devuan:~$dmesg for modprobe -v e1000e
groucho@devuan:~$ sudo dmesg
--- snip ---
[10200.634814] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[10200.634819] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[10200.635004] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[10200.635007] e1000e 0000:00:19.0: PHY Smart Power Down Disabled
[10200.635008] e1000e 0000:00:19.0: EEE Support was initialized to be enabled
[10200.635010] e1000e 0000:00:19.0: EEE Support has been reset to be disabled
[10200.949099] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:14:4f:4a:a2:81
[10200.949104] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[10200.949129] e1000e 0000:00:19.0 eth0: MAC: 7, PHY: 6, PBA No: FFFFFF-0FF
[10202.829745] e1000e 0000:00:19.0 eth0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[10202.829854] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
groucho@devuan:~$Seems everything is where/how it should be?
Thanks in advance,
A.
#1189 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-12 21:42:17
Hello:
... here it shuts down properly...
Any idea why it would not shut down properly in my box?
How can I troubleshoot that?
Right.
Thanks. 8^)
... if your system entered sleep and e1000e called the pm_freeze function things could be corrupted, indeed.
Which ones?
... next shutdown and start may go boom?!
Nah ! 8^D
... WoL, too tricky ...
... disable WoL command early in boot process ...
That's what I am already doing, remember?
First at /etc/rc.local ...
groucho@devuan:~$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
# to set all /proc/acpi/wakeup entries to 'disabled'
# no wakeup from S4 for anything
# does not survire reboot that's why it is here
# see https://dev1galaxy.org/viewtopic.php?pid=29113#p29113
/usr/local/bin/acpi_wakeups.sh
# to disable wol via ethtool at boot
# does not survire reboot that's why it is here
/sbin/ethtool -s eth0 wol d
groucho@devuan:~$ ... and just in case some #%&?¡ whatever decides differently, with my shutdown script:
groucho@devuan:~$ cat /usr/bin/shutdown.sh
#!/bin/sh
# added to shutdown directly - no shutdown helper
# options added to troubleshoot nic related bad shutdown
PATH=/sbin:/bin:/usr/sbin:/usr/bin:
# 2
# sync
# disable onboard eth wol
# shutdown system directly
sync && sudo ethtool -s eth0 wol d && sudo shutdown -h nowI've come across a couple of pages related to PM and /etc/default/acpi-support.
As acpi-support seesm to have been deprecated long ago, I had to look around for oldish pages or get systemd only hits.
I added the links to the file so as to remember where it all came from:
groucho@devuan:~$ cat /etc/default/acpi-support
# comment the next line to disable ACPI suspend to RAM
# ACPI_SLEEP=true
ACPI_SLEEP=false
# comment the next line to disable suspend to disk
# ACPI_HIBERNATE=true
ACPI_HIBERNATE=true
# added 20210511
# see https://forums.linuxmint.com/viewtopic.php?t=43068
# https://askubuntu.com/questions/47311/how-do-i-disable-my-system-from-going-to-sleep
SUSPEND_METHODS="none"
groucho@devuan:~$ With respect to the >5.5 kernel upgrade:
I installed 5.10 but there are no drivers for my Nvidia cards.
It seems that the nvidia-340xx-legacy driver used by my perfectly working Nvidia Quadro FX 580 cards has fallen out of favour with the powers that be.
And from what I have read, caused a lot of noise.
I think Manjaro and Ubuntu have put out patches, I expect Debian/Devuan will follow suit. (?)
So I'll have to wait.
I'm not going to give up my 580's or use nouveau, unless it improves.
They still have a few years left in them.
I'll apply patch 1005 and report back with whatever results I get.
Thank you very much for your help.
Best,
A.
#1190 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-11 11:21:10
Hello:
You got that PCI REMOVE prints once out of dmesg?
Yes.
I posted them at your request.
But I got them only after a rmmod e1000e and modprobe -v e1000e cycle:
groucho@devuan:~$ sudo dmesg
--- snip ---
[ 1.805846] e1000e: loading out-of-tree module taints kernel.
[ 1.808975] ACPI: Power Button [PWRB]
[ 1.851745] e1000e: module verification failed: signature and/or required key missing - tainting kernel
[ 1.851839] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 1.873915] ACPI: Power Button [PWRF]
[ 1.894607] SCSI subsystem initialized
[ 1.906926] ACPI: bus type USB registered
[ 1.917645] usbcore: registered new interface driver usbfs
[ 1.934103] Fusion MPT base driver 3.04.20
[ 1.944731] Copyright (c) 1999-2008 LSI Corporation
[ 1.945571] usbcore: registered new interface driver hub
[ 1.966487] usbcore: registered new device driver usb
[ 1.979636] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI
[ 1.990206] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[ 2.002032] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 2.013157] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 2.021243] e1000e 0000:00:19.0: PHY Smart Power Down Disabled
[ 2.039474] e1000e 0000:00:19.0: EEE Support was initialized to be enabled
[ 2.050107] e1000e 0000:00:19.0: EEE Support has been reset to be disabled
--- snip ----
[ 431.874537] e1000e: PCI REMOVE PTP <-- here is rmmod e1000e
[ 431.874542] e1000e: PCI REMOVE TIMER
[ 431.874546] e1000e: PCI REMOVE CANCEL WORK SYNC
[ 431.874547] e1000e: PCI REMOVE HW TIMESTAMP
[ 431.874572] e1000e: NETDEV CLOSE ENTERED
[ 431.874573] e1000e: NETDEV CLOSE WAIT DONE
[ 431.874575] e1000e: NETDEV CLOSE DEV IS PRESENT
[ 432.104194] e1000e: NETDEV CLOSE DEV IS DOWN
[ 432.104210] e1000e: NETDEV CLOSE FREE IRQ
[ 432.104215] e1000e 0000:00:19.0 eth0: NIC Link is Down
[ 432.104217] e1000e: NETDEV CLOSE LINK DOWN MSG
[ 432.104218] e1000e: NETDEV CLOSE NAPI DISABLED
[ 432.104228] e1000e: NETDEV CLOSE FREE TX RES
[ 432.104251] e1000e: NETDEV CLOSE FREE RX RES
[ 432.104252] e1000e: NETDEV CLOSE VLAN DONE
[ 432.104254] e1000e: NETDEV CLOSE HW CTRL RELEASED
[ 432.104257] e1000e: NETDEV CLOSE DONE
[ 432.120067] e1000e: PCI REMOVE UNREGISTER NETDEV
[ 432.120072] e1000e: PCI REMOVE WAKE NO RESUME
[ 432.120075] e1000e: PCI REMOVE RELEASE HW CONTROL
[ 432.120110] e1000e: PCI REMOVE INT AND TX RX RING
[ 432.120123] e1000e: PCI REMOVE SELECTED REGIONS
[ 432.140044] e1000e: PCI REMOVE FREE NETDEV
[ 432.140048] e1000e: PCI REMOVE DISABLE ERR REPORTING
[ 432.140164] e1000e: PCI REMOVE DISABLE DEVICE
-----------------------------------------------------------------------------------------------------------------------------------
[ 443.741628] e1000e: Intel(R) PRO/1000 Network Driver - 3.8.7-NAPI <--- here is modprobe -v e1000e
[ 443.741632] e1000e: Copyright(c) 1999 - 2020 Intel Corporation.
[ 443.741822] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 443.741824] e1000e 0000:00:19.0: PHY Smart Power Down Disabled
[ 443.741826] e1000e 0000:00:19.0: EEE Support was initialized to be enabled
[ 443.741827] e1000e 0000:00:19.0: EEE Support has been reset to be disabled
[ 444.060221] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:14:4f:4a:a2:81
[ 444.060227] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 444.060251] e1000e 0000:00:19.0 eth0: MAC: 7, PHY: 6, PBA No: FFFFFF-0FF
[ 446.780888] e1000e 0000:00:19.0 eth0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 446.780997] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 447.562186] e1000e: NETDEV CLOSE ENTERED
[ 447.562190] e1000e: NETDEV CLOSE WAIT DONE
[ 447.562192] e1000e: NETDEV CLOSE DEV IS PRESENT
[ 447.792198] e1000e: NETDEV CLOSE DEV IS DOWN
[ 447.792211] e1000e: NETDEV CLOSE FREE IRQ
[ 447.792216] e1000e 0000:00:19.0 eth0: NIC Link is Down
[ 447.792218] e1000e: NETDEV CLOSE LINK DOWN MSG
[ 447.792219] e1000e: NETDEV CLOSE NAPI DISABLED
[ 447.792227] e1000e: NETDEV CLOSE FREE TX RES
[ 447.792251] e1000e: NETDEV CLOSE FREE RX RES
[ 447.792252] e1000e: NETDEV CLOSE VLAN DONE
[ 447.792254] e1000e: NETDEV CLOSE HW CTRL RELEASED
[ 447.792257] e1000e: NETDEV CLOSE DONE
[ 448.311058] e1000e: NETDEV CLOSE ENTERED
[ 448.311062] e1000e: NETDEV CLOSE WAIT DONE
[ 448.311064] e1000e: NETDEV CLOSE DEV IS PRESENT
[ 448.532200] e1000e: NETDEV CLOSE DEV IS DOWN
[ 448.532213] e1000e: NETDEV CLOSE FREE IRQ
[ 448.532218] e1000e 0000:00:19.0 eth0: NIC Link is Down
[ 448.532220] e1000e: NETDEV CLOSE LINK DOWN MSG
[ 448.532221] e1000e: NETDEV CLOSE NAPI DISABLED
[ 448.532230] e1000e: NETDEV CLOSE FREE TX RES
[ 448.532254] e1000e: NETDEV CLOSE FREE RX RES
[ 448.532255] e1000e: NETDEV CLOSE VLAN DONE
[ 448.532257] e1000e: NETDEV CLOSE HW CTRL RELEASED
[ 448.532260] e1000e: NETDEV CLOSE DONE
[ 450.408891] e1000e 0000:00:19.0 eth0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 450.409000] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
groucho@devuan:~$ I have found no other record of e1000e activity on a bad_sutdown.
A normal shutdown would not enter S3?
Though, I am out with that.
I don't know.
There's the issue of not being able to disable sleep state in the BIOS.
And that being set to S3.
The thing would be to avoid the system from picking it up and overriding what the BIOS says.
ie: the proper way to do things
I patch WOL and PM FREEZE detach thingie and that's it from me.
Sorry to hear that, but I understand.
You've done more than enough already. 8^)
And no one else has made any suggestions.
Maybe not patch WoL as that seems to be taken care of vie ethtool and boot and shutdown.
BTW: you have this in your system?
# Make it possible to not shut down network interfaces,
# needed to use wake-on-lan
netdown="-i"
if [ "$NETDOWN" = "no" ]; then
netdown=""
fi
log_action_msg "Will now halt"
read -p "Press enter to halt ($netdown $poweroff $hddown)" reply <--- this line added
halt -d -f $netdown $poweroff $hddown
}Does it shut down properly?
Thanks for your input.
Best,
A.
#1191 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 21:54:42
Hello:
... and the dmesg output shows what for the freeze?
Screen was frozen, needed a hard shudown.
dmesg0 does not show anything strange.
I could reproduce the whole thing but how to get what dmesg recorded, if anything at all?
Thanks in advance,
A.
#1192 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 21:45:03
Hello:
... you got no pm tooling, I wonder who enters S3.
That's what I think is the question here.
I think the answer is in the U24's BIOS.
Remember that I have not been able to disable ME "Firmware Power Control" and "Host Sleep States" in BIOS.
It is set to S3, I can set it back to S0 but I cannot disable it.
Only one visible for now is /sbin/halt with its unsetted NETDOWN.
If not that, it must be the kernel on its own, then?!
Hmm ...
Why would that be?
Anyone here knows about sleep state handling?
No one else has pitched in ...
But you have gathered quite a following.
Thanks for your input.
A.
#1193 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 21:36:05
Hello:
There's some alteration in the posting order ...
... you want to put NETDOWN=no into /etc/default/halt to disable WoL handling of /sbin/halt.
Right.
groucho@devuan:~$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
NETDOWN=no
groucho@devuan:~$ Quite strange parameter to what it is doing in the end.
I'll take your word for it.
Don't have a clue as to what is strange here ...
Though, you still want to disable WoL via ethtool. The more disabling, the better.
That is supposed to be the tool to use.
When the HW or the driver does not undo it behind your back.
We can get a patch to forcefully disable WoL by module parameter. I already spotted the flag in code, which activates WoL.
We can, hypothetically for now, reset that in src/param.c ...
Thanks for sharing.
But it's you doing the patching. 8^)
... even with that hypothetical patch, We want to disable WoL from /sbin/halt.
Right.
Would be like disabling it in the BIOS, which for whatever reason cannot be done without screwing up everything.
I discovered an old Sun Microsystems thread.
Had to find a catched copy.
Seems that this was a hard cookie from the very start of the Sun Ultra 24's market debut:
https://webcache.googleusercontent.com/ … clnk&gl=us
Best,
A.
#1194 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 21:23:33
Hello:
I'll edit that into /etc/init.d/halt and see how it behaves.
If I understand correctly, it will shut down on Enter.
Never got that far ...
Here's the part that I edited:
# Make it possible to not shut down network interfaces,
# needed to use wake-on-lan
netdown="-i"
if [ "$NETDOWN" = "no" ]; then
netdown=""
fi
log_action_msg "Will now halt"
read -p "Press enter to halt ($netdown $poweroff $hddown)" reply <--- just this line
halt -d -f $netdown $poweroff $hddown
}On shutdown, the box froze at this point:
Good sign is that there were no fans blowing.
Only way out was a hard shutdown.
REISUB did not work or maybe it was that I could not type and hold Alt+SysRq at the same time?
This happens whether I shut down with my script or with sudo shutdown -h now from a terminal.
Thanks in advance.
A.
#1195 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 20:16:57
Hello:
Note:
Somehow this whole post got lost.
I recovered it but the posting order may have been altered.
Sorry ...
For disabling CONFIG_PM, you have to build your own kernel.
Hmm ...
Not on my list.
... seems to be any pm tooling installed.
How is it that it is done in systemd distributions?
There's no pre-systemd / Linux Devuan equivalent to sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target?
I was reading here: https://answers.launchpad.net/acpi-supp … tion/36260
Since my system had no /etc/default/acpi-support file, I added one:
groucho@devuan:~$ cat /etc/default/acpi-support
# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=false
# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=false
groucho@devuan:~$ Don't know if it does anything at all.
... remind you not to use a 4.x kernel and neither kernel version < 5.5.
I do have your suggestion on my desk.
Not forgotten, just postponed. 8^)
Unless we see some NIC hang ...
... mostly out of thoughts.
Well ...
Your efforts did unearth a lot of e1000e fun which could be put to good use by the module's maintainers.
If nothing else, the quality of the code will be been significantly improved by your work.
No one can thumb their nose at that.
Now, what could happen?
1. another bad shutdown.
It's been ~10 days since I started using the last version of the e1000e module ie: three patches + a std. shutdown.
The third patch was then edited further to accomodate various debug scenarios, but I understand that it was basically the same as v2.
Up to that point I had been without a bad_shutdown for at least a week.
I think that the bad_shutdown I had is linked to the bad_boot.
And the bad boot may (?) have been linked to not setting WoL to disabled on shutdown.
Like I mentioned previously, my shutdown script now sets WoL to disabled on shutdown but does not remove the e1000e module.
But there's that S3 that is bothering me and I'd like to know how to get rid of.
2. another bad_boot followed by a bad_shutdown.
My money is on getting rid of S3 to prevent that.
Maybe setting WoL to disabled serves the same purpose?
3. none of the above.
If in 30/45 days' time we are still at 3. then it could mean that something you have edited/changed with your patches to the e1000e module has had effect. 8^D!
But for now, we have to wait and see.
... check /etc/init.d/halt for hddown= and netdown=, which you can disable by respective configuration settings from /etc/default/halt.
Let's see:
groucho@devuan:~$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
groucho@devuan:~$ groucho@devuan:~$ cat /etc/init.d/halt
#! /bin/sh
### BEGIN INIT INFO
# Provides: halt
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop: 0
# Short-Description: Execute the halt command.
# Description:
### END INIT INFO
NETDOWN=yes
PATH=/sbin:/usr/sbin:/bin:/usr/bin
[ -f /etc/default/halt ] && . /etc/default/halt
. /lib/lsb/init-functions
do_stop () {
if [ "$INIT_HALT" = "" ]
then
case "$HALT" in
[Pp]*)
INIT_HALT=POWEROFF
;;
[Hh]*)
INIT_HALT=HALT
;;
*)
INIT_HALT=POWEROFF
;;
esac
fi
# See if we need to cut the power.
if [ "$INIT_HALT" = "POWEROFF" ] && [ -x /etc/init.d/ups-monitor ]
then
/etc/init.d/ups-monitor poweroff
fi
# Don't shut down drives if we're using RAID.
hddown="-h"
if grep -qs '^md.*active' /proc/mdstat
then
hddown=""
fi
# If INIT_HALT=HALT don't poweroff.
poweroff="-p"
if [ "$INIT_HALT" = "HALT" ]
then
poweroff=""
fi
# Make it possible to not shut down network interfaces, <-------- | x |
# needed to use wake-on-lan <-------- | x |
netdown="-i"
if [ "$NETDOWN" = "no" ]; then
netdown=""
fi
log_action_msg "Will now halt"
halt -d -f $netdown $poweroff $hddown
}
case "$1" in
start|status)
# No-op
;;
restart|reload|force-reload)
echo "Error: argument '$1' not supported" >&2
exit 3
;;
stop)
do_stop
;;
*)
echo "Usage: $0 start|stop" >&2
exit 3
;;
esac
:
groucho@devuan:~$ In my box, netdown and hdown are set.
You may set that configuration parameters, so that they are disabled.
I put
read -p "Press enter to halt ($netdown $poweroff $hddown)" reply
before
halt -d -f $netdown $poweroff $hddown
to see what is set.
Right.
I'll edit that into /etc/init.d/halt and see how it behaves.
If I understand correctly, it will shut down on Enter.
Thanks for your input.
Best,
A.
#1196 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-10 14:39:34
Hello:
... check kernel commandline parameter pcie_port_pm=off.
... disabling sleep states for your pci express slots and NIC.
I think I used something pci=ish without results.
Have to see my notes.
... also the parameter apm ...
... some suspend software installed in /etc/pm, /etc/apm or /etc/acpi and check for such in /etc/default.
I don't have pm-utils installed, removed it some time ago.
groucho@devuan:~$ apt list | grep -i installed | grep -i pm-utils
--- snip ---
groucho@devuan:~$Notwithstanding, I do have these:
groucho@devuan:~$ ls -R /etc/apm/
/etc/apm/:
event.d
/etc/apm/event.d:
20hdparm
groucho@devuan:~$ This for spinning down HDDs if not on AC.
Always on AC but I presume it works as intended.
groucho@devuan:~$ ls -R /etc/acpi/
/etc/acpi/:
events powerbtn-acpi-support.sh
/etc/acpi/events:
powerbtn-acpi-support
groucho@devuan:~$ This to initiate shutdown when the power button is pressed.
I disabled this in /etc/default/acpid because I inadvertently touched the recessed power button more than a few times. 8^/
Also because I'd rather shutdown via terminal or script.
groucho@devuan:~$ ls -R /etc/default/
/etc/default/:
acpid cacerts dbus grub.d hwclock locale~ ntpdate rsyslog su useradd
anacron console-setup devpts grub.ucf-dist intel-microcode networking rcS saned su~ wicd
autofs cpufrequtils exim4 halt keyboard networking.dpkg-dist rcS.dpkg-dist saned.dpkg-dist sysstat
avahi-daemon crda gdomap haveged keyboard~ nfs-common rkhunter saned~ timeshift.json
bsdmainutils cron grub hddtemp locale nss rsync smartmontools tmpfs
/etc/default/grub.d:
init-select.cfg
groucho@devuan:~$ ls -R /etc/default/groucho@devuan:~$ cat /etc/default/acpid
# Options to pass to acpid
#
# OPTIONS are appended to the acpid command-line
# enabled 20181108 to log events to syslog
OPTIONS="-l"
# Linux kernel modules to load before starting acpid
#
# MODULES is a space separated list of modules to load, or "all" to load all
# acpi drivers, or commented out to load no module
#MODULES="battery ac processor button fan thermal video"
#MODULES="all"
groucho@devuan:~$ I added OPTIONS="-l" back in 2018 to see if I could get anything written to a(ny) log.
Thanks for your input.
Best,
A.
#1197 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-09 22:21:02
Hello:
... the /sys/power stuff belongs to Kernel CONFIG_PM I guess.
Feel free to disable that.
Hmm ...
Sure.
Q: how do I go about that.
ie: the opposite of # echo mem > /sys/power/state, effectively removing mem?
Cannot find anything specific about that for non-systemd distributions.
My idea is that if I remove anything S3 related from the system, it may (?) keep whatever system state is set in BIOS from activating.
... also try shutdown -h -P to halt and power off.
Just as you point out:
groucho@devuan:~$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
groucho@devuan:~$ ... if you got to the frozen "reboot: Power down", press Alt + SysRq (Print Screen key) + o for shutdown
Hmm ...
I'm not sure that I did try it but without the expected result.
I'll remember for next time but I think (?) the kb was totally unresponsive.
See: http://blog.kember.net/articles/reisub- … x-restart/
Thanks for the heads up.
Best,
A.
#1198 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-09 16:21:05
Hello:
... does not sound like an NIC (driver) issue.
... if boot already goes noisy.
I agree.
I have always wondered if the bad_boot and the bad_shutdown problems were indpendent of each other or if they shared more than the fans at full blast symptom.
Out of fear of some part of the filesystem getting borked, I had never allowed the boot sequence to go on, aborting it and getting a clean boot afterwards.
It will reboot after a time-out unless you explicitly allow the boot sequence to continue.
This time, not aborting the sequence revealed a bad_shutdown right after a bad_boot.
Then, going back to the Sun Microsystems *.pdf on the matter and seeing the diagnostic put forth (S0, S3, etc.) again made my doubts resurface.
ie:
"If you power on the workstation before the system enters the S3 ... "
Q: why would the system be entering S3 or any other save S5 in the first place?
This probably has to do with my not being able to disable ME "Firmware Power Control" and "Host Sleep States" in BIOS.
It is true that I pressed the power button immediately after power off and blank screen.
But I have not been able to reproduce it.
Like I mentioned, I have edited to shutdown script to set WoL to disabled as before, just not removing the e1000e module.
With respect to system states, dmesg states:
groucho@devuan:~$ sudo dmesg | grep S0
[ 0.729378] ACPI: (supports S0 S1 S3 S4 S5)
groucho@devuan:~$ I'm only interested in S0 and S5 but ...
groucho@devuan:/sys/power$ cat /sys/power/state
freeze standby mem disk
groucho@devuan:/sys/power$ I have seen how, if needed, freeze, standby, mem and disk can be added to /sys/power/state to enable power states S0, S1, S3 and S4 respectively.
eg: # echo mem > /sys/power/state
And have found how to disable power states in systemd distributions.
eg: sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
But I have not found out how to do that in Devuan.
I am guessing that not having those values (specifically S3) could help finding out what is going on.
How to do the opposite of # echo mem > /sys/power/state ?
Thanks in advance.
A.
#1199 Re: Installation » Linux e1000e module removal and e1000e EEE timer - Part II » 2021-05-09 01:02:04
Hello:
Update
All shutdowns normal up to now. 050520201@21:03 GMT
That has not changed.
But I did get a bad boot which then resulted in a bad shutdown.
A bad boot is when on starting up the system, both CPU and case fans start to run at 100% and the BIOS stops with a "CPU Fan error" notice.
It asks if you want to continue or press ESC or an Fx to abort, can't recall.
Sorry, no video or grab as I was obviously not ready for it.
This has not happened in a while and although the fans running at 100% is what this bad boot has in common with the bad shutdown, I have always thought they were for different causes.
Sun Microsystems had at one time diagnosed (but evidently not bothered to fix) this problem in a Sun Product Notes *.pdf for this WS (2009) where it says it can happen and why:
CPU Fan Error Might Occur After Power On
If you power on the workstation before the system enters the S3 sleep
state, a CPU fan error might occur.
It also provided a workaround which consists in accessing the Management Engine (ME) BIOS Setup utility to change the power policies.
You have to set ME "Firmware Power Control" to ON and "Host Sleep States" to ON in S0, S3.
I changed "Host Sleep States" from S1, S3 to S0, S3 but every so often the CPU Fan error came around again.
[rant]
But why would I want this?
It is basically allowing Intel ME to start up you workstation remotely.
[/rant]
So I tried to set ME "Firmware Power Control" or "Host Sleep States" to OFF, effectively disabling sleep of any type in my box.
Because ...
WTHF does a server/workstation need a damn S state different than S5 for?
As a result all havok broke loose: on reboot with the box frozen at the start of the BIOS sequence, both CPU and case fans at 100%.
I was scared shitless that my new WS was done for.
Only way out was a hard shutdown, a CMOS clear and a ME BIOS reflash.
I believe that this is closely related to the fact that it is not possible to disable the on-board GbE LAN in the BIOS. (it is greyed out)
That and the Intel e1000 driver is *always* enabling WoL no matter what settings you give it.
Which is why I had WoL set to OFF both at boot and at shutdown via a shutdown script.
In any case, "Host Sleep States" is evidently set to ON and S1, (not S0) and S3.
I insisted with my attempt once again before starting the first part of this thread, with the same results.
Not as scared and more confident around the hardware than the first time I tried it, but in a sweat till I saw a working boot screen come up.
But I digress ...
Instead of aborting the boot sequence I continued to boot into Devuan, which went on without any other problem than the fans blowing continuously at 100%.
I got a copy of dmesg checked that everything was working properly and proceeded to shut down as I am usually doing these days. ie: plain shutdown -h now, no script.
The result was another bad shutdown, like the ones I usually get.
Here's the shutdown screen:
No different than what I am getting these days with a normal shutdown.
ie: contains no debug data.
I will edit the shutdown script to disable WoL as I had been doing to see if there's any change in this behaviour.
Thanks in advance,
A.
#1200 Re: Desktop and Multimedia » Thunar crashes on "Drag and Drop" » 2021-05-07 15:16:17
Hello:
... dependencies are mostly from sid/ceres rather than experimental.
... that .deb cannot be installed in a beowulf system without breaking it.
Enough for me not to consider attempting it.
... could try backporting it ...
... not worth the bother.
I agree.
Thanks for your input.
A.
Board footer
