You are not logged in.
Hello:
After seeing Élisabeth's plight to recover from a damaged laptop keyboard problem, I started thinking about the different ways you could get out of a problem like that one.
I long ago made it a point of always having at least one spare kb at hand and in case that fails, BIOS enabled RS232 and on-board USB ports.
But as Murphy is always lurking, I set out to see if eg: I could make do with my Palm T|X on the ADSL router via WiFi.
I would have preferred to use a cable to RJ45 port solution but I don't know of any PalmOS TCP/IP applications or adaptors and the Palm T|X only has a USB port.
Easier said that done.
I was quite surprised to see that ssh applications for PalmOS5 are practically non-existent: I only found three and one of them (Top Gun ssh) was just for older models like the Palm Pilot Professional.
The other two are TUssh and pssh, I finally settled on this last one.
Tl;dr:
After many hours of fiddling/browsing and some great help from a chap at comp.security.ssh, I managed to ssh into the Devuan ascii VBox VM I have running PiHole for my Devuan Beowulf installation.
If anyone is interested, you can see most if not all the gory details here: https://groups.google.com/g/comp.securi … u0VvfEQudc
Of course, I am quite aware that ssh'ing into a system using deprecated protocols obviously implies security issues, but in this specific case I think I have attenuated them with three four things:
1. Access to the ADSL router via WiFi is MAC filtered. ie: it will only allow *this* specific Palm T|X handheld to log in.
2. A (relatively) complex WPA/WPA2 PSK Mixed PW such as this one is used: 4N@8974+6231, obviously with room to improve.
Unfortunately, the good people at Palm saw it fit to make the last Personal security upgrade only to WEP/WPA-PSK with a pre-shared key which made it useless outside the realm of home routers.
Enterprise security got EAP-TLS, EAP-TTLS, PAP, CHAP, MSCHAP, MSCHAPv2, EAP-GTC (password), EAP-MD5-Challenge, EAP-MSCHAPv2, EAP-PEAP (v0 and v1), MSCHAPv2, GTC (password), MD5-Challenge, LEAP and Dynamic WEP (WEP encryption with 802.1x based authentication).
3. For the time being, WiFi is enabled on a per-case basis till I can think up a more complex PW.
4. The destination machine's default port for ssh has been changed from 22 to one above 1024 / below 5000.
Best,
A.
Hello:
OpenSSH is a project from the OpenBSD folks ...
I'll have a look.
Don't have much idea wrt SSH.
All I know is how to log-in to the machines connected to my router.
No need for much else.
Thanks for your input.
Best,
A.
Hello:
I'm trying to solve an SSH problem but I don't know if Dev1 is the place for that.
The problem is related to a Palm OS5.4.1 application (Tungsten T|X) that can only deal with DES-EDE3-CBC ciphers.
This means that I need to generate a key that this application con handle.
There's really no security problem involved as the link is via WiFi through an ADSL router with a WPA/WPA2 PSK mixed password and a MAC filter.
Plus WiFi is only enabled on a per-case basis.
I cannot find a SSH user's mail list.
Any ideas?
Thanks in advance,
A.
Hello:
... no Apple or Windows in this house.
8^)
... got into single user mode.
Glad you are making progress.
Best,
A.
Hello:
... on my mobile phone.
I see.
Don't have one of those so it did not ocurr to me.
I use an old Blackberry 9320. 8^ )
And it's a pain in the back.
Yes.
I can relate to that.
Is it an android device?
Best,
A.
Hello:
How about ssh from another machine?
That's my only machine.
I'm sorry, maybe I've missed something.
Couldn't you try to ssh from the machine you are writing from now?
I am obviously assuming that it is not your laptop and that whatever machine you are using to post has an available ethernet port you can access.
Best,
A.
Hello:
Yes!!!
It lives! 8^D
.. look at the logs and see if anything is amiss ...
No problems detected in the guest machine logs, Pihole or Unbound.
For completeness' sake:
I run an autostarted VBbox Devuan Beowulf guest running Pihole/Unbound.
Although it starts up properly, for some reason it does not shutdown gracefully.
The result is that I get error messages when I shut down the host:
groucho@devuan:/var/log$ cat messages | grep -i error
--- snip ---
Nov 19 22:38:23 localhost kernel: [21254.843754] traps: VBoxSVC[2451] trap int3 ip:7fa545efcddc sp:7ffe92195e50 error:0 in VBoxXPCOMIPCC.so[7fa545ef8000+f000]
--- snip ---
groucho@devuan:/var/log$See https://dev1galaxy.org/viewtopic.php?id=4684
Fixing this script (VBox) issue made everything right.
Now the host shuts down after the guest shuts down properly, it's health is preserved and there are no more localhost kernel errors.
Thanks to all that pitched in. 8^)
Best,
A.
Hello:
... won't comment on VirtualBox ...
=^ )
... an entire terminal emulator to run a script ...
The only way I found to run this set of commands and see the printout roll out 'live' without much hassle.
Maybe could have sent the output to a file.
Perhaps just run a shell instead ....
Yes!!!
It lives! 8^D
sh -c 'vboxmanage controlvm "madmax ascii" poweroff && wait && sudo /usr/bin/shutdown.sh' as the command in the launcher works great.
Quite fast, maybe because the terminal is not involved now (?).
I have to look at the logs and see if anything is amiss VBox wise, but at first sight it seems to work as intended.
... recommend using /etc/rc6.d/ to execute scripts on shutdown.
I'll have a look at that further on.
Thank you very much for your input.
Much appreciated.
Best,
A.
Hello:
... working directly and not in a script, my first guess would be path ...
I thought of that at first so I checked the script and the launcher command line.
On one hand both xfce4-terminal and vboxmanage are located in /usr/bin/.
Also, as the vm does get shut down, I concluded that it was not related.
Nevertheelss, I just checked to see:
xfce4-terminal -x /usr/bin/vboxmanage controlvm "madmax ascii" poweroff && wait && sudo /usr/bin/shutdown.sh
... does not work either.
Thanks for your input.
Best,
A.
Hello:
... try it out and report ...
No, no change in how running the command from the launcher behaves.
But thanks a lot for the heads up on wait. 8^D
Using it instead of sleep, which has to be used with an arbitrary time lapse (which may or may not be always right) makes for a faster resolution of the command.
Thanks for your input.
Best,
A.
Hello:
... instead of using sleep use the wait command.
Hmm ...
"... wait is a command that waits for the given jobs to complete ..."
Think that may be it?
I'll try it out and report back here.
But if it the command works from an open terminal ...
vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh
... shouldn't it also work in the launcher command line?
xfce4-terminal -x vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh
My guess is that there's something in the syntax I'm using, just cannot find out what it is.
Thanks for your input.
Best,
A.
Hello:
... received an update to grub ...
... os-prober would no longer run.
... people with dual-boot or multi-boot computers will no longer be able to...update-grub...in order to get their other systems to show in the grub menu.
Any idea as to what led to that?
Is it some systemd related thing?
That will probably break the grub-customizer application.
C'mon devs, you can do better than that!
Indeed ...
+100
... open and edit the following file...
/etc/default/grub
...and add the following line...GRUB_DISABLE_OS_PROBER=falseSave and close the file, then open a terminal and run an...
update-grub
Thank you very much for the heads-up.
Best,
A.
Hello:
I shut down my Devuan Beowulf system with a script called from a launcher which I set up within the panel of my Xfce desktop:
This is the script:
#!/bin/sh
# added to shutdown directly - no shutdown helper
PATH=/sbin:/bin:/usr/sbin:/usr/bin:
#
sync && sudo ethtool -s eth0 wol d && sudo rmmod -s -v e1000e && sudo shutdown -h nowThis is the launcher command line:
xfce4-terminal -x sudo /usr/bin/shutdown.shThis has been working perfectly well for the longest time.
Some time ago I set up Pihole in an autostarted Vbox virtual machine but although it seems to start up properly it does not shutdown gracefully.
ie: sudo shutdown -h now takes effect before the virtual machine has completely shut down.
The idea is to send the virtual machine the shutdown command, wait 5s and then execute the shutdown script.
Simple if not elegant.
As VBox gives members of the vboxusers group permission to start and shutdown a virtual machine, I cannot add the shutdown command to the shutdown script called from the launcher because this script needs sudo. ie: root privileges and the vms belong to vmusers and not to root.
So I add the virtual machine shutdown script + a 5s sleep to the launcher command line.
But it does not work with the launcher.
vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && sudo /usr/bin/shutdown.sh works properly if I execute it from a terminal.
But not when I run it from the launcher:
xfce4-terminal -x vboxmanage controlvm "madmax ascii" poweroff && sleep 5s && /usr/bin/shutdown.sh
It only shuts down the virtual machine, the rest of the command does not have effect.
Cannot figure out what I'm doing wrong.
Any ideas?
Thanks in advance.
A.
Hello:
I don't have hibernation enabled in my Devuan Beowulf installation.
Why do I have this in my dmsg printout?
~$ sudo dmesg
--- snip ---
[ 0.039017] PM: hibernation: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.039019] PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.039020] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e1fff]
[ 0.039021] PM: hibernation: Registered nosave memory: [mem 0x000e2000-0x000fffff]
[ 0.039023] PM: hibernation: Registered nosave memory: [mem 0xbfe40000-0xbfe4dfff]
[ 0.039024] PM: hibernation: Registered nosave memory: [mem 0xbfe4e000-0xbfecffff]
[ 0.039026] PM: hibernation: Registered nosave memory: [mem 0xbfed0000-0xbfeddfff]
[ 0.039027] PM: hibernation: Registered nosave memory: [mem 0xbfede000-0xbfeebfff]
[ 0.039028] PM: hibernation: Registered nosave memory: [mem 0xbfeec000-0xbfffffff]
[ 0.039029] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xdfffffff]
[ 0.039031] PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
[ 0.039032] PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfedfffff]
[ 0.039033] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.039034] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xffafffff]
[ 0.039036] PM: hibernation: Registered nosave memory: [mem 0xffb00000-0xffffffff]
--- snip ---
~$
As far as I know, I have disabled any and all power management.
Thanks in advance,
A.
Hello:
Thanks
You're welcome.
I can/could 'iasl -c' a new DSDT ...
Yes.
Provided you were able enough and found your way around the obscure maze of DSDT stanzas.
Now, if the kernel you are using was compiled with ACPI_TABLE_UPGRADE=y you can still load an alternate DSDT table using the acpi_override method.
Here's the list of links I have kept, some may be dead by now.
There are one or two that have the recipe to load an alternate DSDT via acpi_override in one of these groups.
I used it and was able to load a new table successfully.
Override: <---- here
https://delta-xi.net/#056
https://wiki.archlinux.org/index.php/DSDT
https://cgc.com.kw/tag/dsdt-override/
Patches:
https://github.com/RehabMan/Laptop-DSDT … estart.txt
https://github.com/RehabMan/Intel-NUC-D … DT-PTS.dsl
https://www.tonymacx86.com/threads/shut … dt.229418/
GRUB:
https://github.com/tsgates/arch-wiki-ma … ki/DSDT.md
Then there's all these, some of which may have been worthwhile, but I can't recall which:
https://github.com/hirschmann/nbfc/wiki … k%27s-DSDT
https://cannibalcandy.wordpress.com/201 … acpi-woes/
https://sit1way.wordpress.com/2013/04/1 … uggy-dsdt/
http://blog.michael.kuron-germany.de/20 … compiling/
https://lists.gnu.org/archive/html/bug- … 00008.html
https://github.com/torvalds/linux/blob/ … pi/osi.txt
https://patchwork.kernel.org/patch/2831128/
https://www.kernel.org/doc/Documentatio … erride.txt
https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO/kconfig.html
https://01.org/linux-acpi/documentation/overriding-dsdt
https://www.insanelymac.com/forum/topic … dt-editor/
http://wiki.osx86project.org/wiki/index.php/DSDT
http://acpi.sourceforge.net/dsdt/
https://gaugusch.at/kernel.shtml
https://init-6.bitbucket.io/content/201 … r-central/
https://gist.github.com/rschmukler/1101770
Unfortunately DSDT editing is the almost exclusive realm of Mac boxes/laptop owners who want to run Linux on them.
This means that most if not all the information to be found is for that hardware, albeit with quite a bit of overlapping with Wintel stuff.
A fortunate thing because help is not available (or offered) to non-Mac people.
Long story short: I was eventually able to fix most of the BIOS errors/warnings detected with the MS based tools I found on line and came up with a new DSDT.
Much to my chagrin and after a great many hours hard work, the new DSDT did not solve the problems the crap BIOS my Sun Ultra 24 has.
Save getting rid of most of the errors/warnings (not all), did nothing else for me, at least nothing noticeable.
Which meant that the Linux kernel was doing its workaround properly. 8^)
But I had to do it all over again when the kernel got upgraded and after I forgot to do it for a second time, I decided it was not worth the hassle.
It did not solve my Ultra 24 issues so that was it.
HTH.
Best,
A.
Hello:
... an old piece from Intel atoms time.
D945GCLF2D ...
All these warning are like/similar to the ones I get in dmesg when booting my Sun Ultra 24 WS:
groucho@devuan:~$ sudo dmesg | grep -i "acpi bios"
[ 0.018306] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20200925/tbfadt-569)
[ 1.272873] ACPI BIOS Error (bug): Could not resolve symbol [\_SB._OSC.SUPP], AE_NOT_FOUND (20200925/psargs-330)groucho@devuan:~$ sudo dmesg | grep -i "acpi error"
[ 1.272882] ACPI Error: Aborting method \_SB._OSC due to previous error (AE_NOT_FOUND) (20200925/psparse-531)
groucho@devuan:~$ I run Devuan Beowulf on my Asus EEE 1000HE which has an Atom 280 processor and also get a number of ACPI warnings but it works properly.
Or so it seems. 8^/
groucho@eee-dev3:~$ sudo dmesg | grep -i "acpi warning"
[ 14.086823] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000087F (\PMIO) (20180810/utaddress-213)
[ 14.157275] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000800-0x000000000000087F (\_SB.PCI0.SBRG.PMS0) (20180810/utaddress-213)
[ 14.226890] ACPI Warning: SystemIO range 0x00000000000004B0-0x00000000000004BF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.GPBX) (20180810/utaddress-213)
[ 14.290513] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.GPBX) (20180810/utaddress-213)
groucho@eee-dev3:~$ I understand that these ACPI errors/warnings are caused by badly written BIOSes.
ie: The result of a blatant lack of adherence to ACPI standards by BIOS writers, OEMs and their permanent bowing to the very lax ACPI compliance by Microsoft.
Many years ago this was labelled the "Wintel" way of doing things and the main reason most motherboards support MS OSs (from XP home to Vista) but not Linux.
From what I have read, the Linux kernel is supposed to be able to 'work around' these problems but this does not happen on all motherboards/BIOSes.
And as time passes by, a lot of this hardware, which would work properly with a correctly written BIOS, ends up falling by the wayside.
You may want to try booting a plain/basic Beowulf Devuan net install installation from a USB sick with ACPI disabled in the kernel command line ie; ACPI=off and see what (if any) errors/warnings you get from that via the install logs and dmesg.
Maybe your server can do well enough without ACPI?
Sorry but that's all I can come up with.
Best,
A.
Hello:
... Devuan on both Pi4b and Pi400, in aarch64 mode.
... WIFI interface is named WLAN0 on the Pi4b ...
... named WLAN1 on the Pi400 ...
Any clues?
Can't imagine why.
But check this and see if there's something there: https://wiki.debian.org/NetworkInterfaceNames
eg: the /etc/udev/rules.d/70-persistent-net.rules file in each one of the installations and compare them.
Best,
A.
Hello:
I have been following this thread because I have never used serial input and was interested to see how it worked.
... other thing that is very odd is that I can enter in text at the log in prompt from the same SATA SSD drive
when a graphics card and keyboard is installed using the original install inittab that was saved before I modified it ...
So ...
What is the difference between the original install inittab and the modified one which then did not work?
And then, what is the difference between that original one and the one in the updated Devuan Chimaera?
Looking at the eventual differences between them will give us a way to diagnose the problem.
Thanks in advance,
A.
Hello:
Do smartctl -h to get a complete usage summary.
You may want to read the summary again. <----
Look for the -T modifier to see what it does ...
~$ sudo smartctl -h
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.3-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
Usage: smartctl [options] device
--- snip ---
===== SMARTCTL RUN-TIME BEHAVIOR OPTIONS =====
--- snip ---
-T TYPE, --tolerance=TYPE (ATA)
Tolerance: normal, conservative, permissive, verypermissive
--- snip ---
~$... and use it as required by the application so it can continue:
--- snip --- Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
External drives running through USB are sometimes tricky, some brands more than others.
Previous (limited) experience has shown me that this is many times due to problematic access to the USB controller chip inside the external drive's case.
While you can use other ie: -d modifiers, I expect that using -T will allow the application to decide the device's type and act accordingly.
For example, a run on an old 40Gb (!) USB drive I have:
groucho@devuan:~$ sudo smartctl -i -a -T verypermissive /dev/sdg1
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.3-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: SAMSUNG
Product: MP0402H
Revision: 0811
User Capacity: 40,060,403,712 bytes [40.0 GB]
Logical block size: 512 bytes
Device type: disk
Local Time is: Wed Nov 24 09:33:25 2021 -03
SMART support is: Unavailable - device lacks SMART capability.
=== START OF READ SMART DATA SECTION ===
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Error Counter logging not supported
Device does not support Self Test logging
~$ Running this ...
~$ sudo smartctl -i -a -T verypermissive /dev/sdx... should get you some results.
Best,
A.
Hello:
... why I got that error message ...
Could be a temp glitch in the script, caused by [ whatever could be ].
Periodically, I'll run updates and they don't complete.
I've experienced it in my boxes a couple of times.
I just retried and that would be it.
This is Linux, not MS. ;^ )
As long as the glitches are not a constant ...
Thanks to all, especially ...
You're welcome but it's nothing special.
Just trying to give back a bit of the much I have received here at Dev1.
Best,
A.
Hello:
... strongly recommend a SMART test on that device.
+1
See https://linoxide.com/how-to-test-ssd-hd … -in-linux/
or
Do smartctl -h to get a complete usage summary.
You don't want a drive with issues if you are using it for backups.
Best,
A.
Hello:
ron@ron:~$ sudo apt update && sudo apt upgrade --- snip --- 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
You're good to go. 8^D
Best,
A.
Hello:
Did all three ...
Doing as suggested by MiyoLinux included the next step I would have suggested to check the state your system was in:
$ sudo apt update && sudo apt upgradeAs you can see, the terminal printout when reinstalling linux-image-amd64 reads:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.You may want to try it and see if it comes up clean ie:
~$ sudo apt update && sudo apt upgrade
--- snip ---
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. # <- this
~$ If it does, we're done.
Unless you have any other issues, I think now you're good to go. 8^D
That said, in my opinion it is not by any means necessary to run a system on the latest kernel/bleeding edge.
Unless you have the latest hardware or are testing new things.
But then Debian most probably won't have native drivers ready and you will have to depend on the OEMs for that.
Until systemd and wayland reared their heads, it was all about stability and previsibility.
ie: the tried and true way of doing things in Debian.
Things have changed quite a bit, which is why we're here now.
Best,
A.
Hello:
sudo apt-get install --fix-broken returned ...
Right ...
apt says those packages are no longer required.
Now you do this:
sudo apt autoremove && sudo apt install -f The first part (before &&) will remove the packages no longer required and the second part will look for and try to fix any missing dependencies you may have in the system.
Let's see what you get from that.
Best,
A.
Hello:
No, not yet. I am reluctant ...
I went ahead and tried installing the latest avaiable from their repository.
groucho@devuan:~$ vboxmanage --version
6.1.28r147628
groucho@devuan:~$ After all the vm only runs Pie-hole and Unbound.
The line in dmesg for the guest is still there:
groucho@dev-pihole:~$ sudo dmesg | grep -i error
--- snip ---
[ 16.458606] 00:00:00.178288 vminfo Error: Unable to connect to system D-Bus (1/3): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
--- snip ---
groucho@dev-pihole:~$ I now get the kernel traps for vboxsvc and vboxheadless but can see no problem/effects.
That said, it seems that a newer version for Buster/Beowulf has been released after we last wrote:
https://download.virtualbox.org/virtual … _amd64.deb
I'll try it and see if things improve.
Thanks for your input.
Best,
A.