You are not logged in.
Hello:
Looks like it doesn't have a partition table ...
Can you mount it manually?
Hmm ...
Not the last time I tried.
Let's see now.
Plugged it into the erader and the reader into the socket.
dmesg says:
[ 347.180602] usb 5-5: new high-speed USB device number 5 using ehci-pci
[ 347.337732] usb 5-5: New USB device found, idVendor=14cd, idProduct=125a, bcdDevice= 2.00
[ 347.337737] usb 5-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 347.337740] usb 5-5: Product: Mass Storage Device
[ 347.337742] usb 5-5: Manufacturer: Generic
[ 347.337745] usb 5-5: SerialNumber: 812520090519
[ 347.338023] usb-storage 5-5:1.0: USB Mass Storage device detected
[ 347.338187] scsi host7: usb-storage 5-5:1.0
[ 348.369261] scsi 7:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 348.369596] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 348.371680] sd 7:0:0:0: [sdc] 3842048 512-byte logical blocks: (1.97 GB/1.83 GiB)
[ 348.372368] sd 7:0:0:0: [sdc] Write Protect is off
[ 348.372372] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 348.372994] sd 7:0:0:0: [sdc] No Caching mode page found
[ 348.372999] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 348.434000] sd 7:0:0:0: [sdc] Attached SCSI removable disk
~$ But, as before, it is not seen in the file manager.
~$ sudo mount /dev/sdc /mnt
[sudo] password for groucho:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error.
~$ Hmmm ...
Rather ambiguous.
ie: this, that or any other. 8^D
groucho@devuan:~$ sudo findmnt /mnt
groucho@devuan:~$ The SD card is healthy as far as the camera it is used on concerns: I can se the contents and write to the card.
I think the FS is FAT16.
Thanks for your input.
Best,
A.
Hello:
For the longest while I have had this problem in a sort of on/off way.
ie: does not happen all the time, but always happens when I need to see the SD's contents.
eg:
I plug in the SD card into the reader and the reader into one of the my box's USB sockets.
I then open the file manager PCManFM 1.3.1 but the SD card has not been mounted.
So I check dmesg:
~$ sudo dmesg
--- snip ---
[ 3029.553100] usb 5-5: new high-speed USB device number 4 using ehci-pci
[ 3029.710237] usb 5-5: New USB device found, idVendor=14cd, idProduct=125a, bcdDevice= 2.00
[ 3029.710241] usb 5-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 3029.710244] usb 5-5: Product: Mass Storage Device
[ 3029.710246] usb 5-5: Manufacturer: Generic
[ 3029.710249] usb 5-5: SerialNumber: 812520090519
[ 3029.739442] usb-storage 5-5:1.0: USB Mass Storage device detected
[ 3029.739977] scsi host8: usb-storage 5-5:1.0
[ 3029.740084] usbcore: registered new interface driver usb-storage
[ 3029.743230] usbcore: registered new interface driver uas
[ 3030.765763] scsi 8:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
[ 3030.766106] sd 8:0:0:0: Attached scsi generic sg6 type 0
[ 3030.767372] sd 8:0:0:0: [sdg] 3842048 512-byte logical blocks: (1.97 GB/1.83 GiB) <---- here it is
[ 3030.768873] sd 8:0:0:0: [sdg] Write Protect is off
[ 3030.768878] sd 8:0:0:0: [sdg] Mode Sense: 03 00 00 00
[ 3030.769496] sd 8:0:0:0: [sdg] No Caching mode page found
[ 3030.769501] sd 8:0:0:0: [sdg] Assuming drive cache: write through
[ 3030.822495] sd 8:0:0:0: [sdg] Attached SCSI removable disk
~$ Sure enough, there it is: sdg
Then I check with lsblk:
groucho@devuan:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
`-sda1 8:1 0 465.8G 0 part /run/timeshift/backup
sdb 8:16 0 111.8G 0 disk
|-sdb1 8:17 0 28.9G 0 part /
|-sdb2 8:18 0 1K 0 part
|-sdb3 8:19 0 4.1G 0 part [SWAP]
|-sdb5 8:21 0 750M 0 part /var/log
`-sdb6 8:22 0 78.1G 0 part /home
sdc 8:32 0 279.4G 0 disk
`-sdc1 8:33 0 279.4G 0 part
sdd 8:48 0 279.4G 0 disk
`-sdd1 8:49 0 279.4G 0 part /media/storage
sde 8:64 0 68.4G 0 disk
|-sde1 8:65 0 18.6G 0 part
|-sde2 8:66 0 1K 0 part
|-sde3 8:67 0 7.5G 0 part
|-sde5 8:69 0 1.9G 0 part
`-sde6 8:70 0 40.4G 0 part
sdf 8:80 0 279.4G 0 disk
`-sdf1 8:81 0 279.4G 0 part
sdg 8:96 1 1.9G 0 disk <--- no mount point
groucho@devuan:~$ Sure enough, there it is: sdg but it is not mounted.
usbView 2.0 sees it:
Mass Storage Device
Manufacturer: Generic
Serial Number: 812520090519
Speed: 480Mb/s (high)
Bus: 5
Address: 4
USB Version: 2.00
The disks application sees it but states unknown content.
gparted sees it but says unallocated.
And if I put it back in my Minolta Dimage X31, it mounts the SD card and shows me the content and writes new files to it with no problems whatsoever.
Unfortunately, I have not been able to reproduce this problem, so I am at a loss as to how to fix it.
Any ideas?
Thanks in advance.
Best,
A.
Hello:
... was hoping another process (the old pihole?) was holding on to that port.
... can't connect, because the service is not running.
Exactly ...
Would you mind trying this ...
Of course:
root@chimaera:~# cat /etc/pihole/setupVars.conf
WEBPASSWORD=688cee6d6cc168f344644ff376482d3cd6894b5d294962dd41a514887f8972b2
BLOCKING_ENABLED=true
DNSSEC=false
REV_SERVER=false
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=127.0.0.1#5335
PIHOLE_DNS_2=
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSMASQ_LISTENING=local
root@chimaera:~# root@chimaera:~# service pihole-FTL start
Not running
FTL started!
root@chimaera:~#root@chimaera:~# service pihole-FTL status
[ ] pihole-FTL is not running
root@chimaera:~# It was doing this before.
... check /var/log/pihole/FTL.log for other clues.
These are the last six lines in the log:
[2022-08-20 22:04:12.618 1362M] Successfully accessed setupVars.conf
[2022-08-20 22:04:12.620 1362M] listening on 0.0.0.0 port 53
[2022-08-20 22:04:12.641 1362M] listening on :: port 53
[2022-08-20 22:04:12.655 1366M] PID of FTL process: 1366
[2022-08-20 22:04:12.657 1366M] Listening on port 4711 for incoming IPv4 telnet connections
[2022-08-20 22:04:12.668 1366M] Error opening IPv6 telnet socket: Address family not supported by protocol (97) <------ the only error... a section "Pi-hole diagnosis" ...
It has always read *No issues found*.
... nuke it (including configs) and re-install.
Yes.
Not too fond of that but as I was in a hurry, I did it.
Brings bad memories of Win95/98 ... 8^°
So ...
Been there, done that.
Full nuke, clean install.
No dice, same story.
I am convinced that the problem lies with port 4711 not being accessible to Pi-Hole.
---> BREAKING NEWS <----
Check this:
https://discourse.pi-hole.net/t/ftl-v5- … e/57181/17
Caveat:
The web site does not work with Pale Moon, to them it is an unsupported browser. 8^|
We found the reason why it's failing when no IPv6 is available. We'll prepare a fix for this.
root@chimaera:~# pihole checkout ftl fix/no_telnet_is_okay
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Branch fix/no_telnet_is_okay exists
[i] Switching to branch: "fix/no_telnet_is_okay" from "master"
[✓] Downloading and Installing FTL
[✓] Restarting pihole-FTL service...
[✓] Enabling pihole-FTL service to start on reboot...
root@chimaera:~# That fixed it, seems you were on the right track. 8^)
Fortunately they move fast.
Once again, thank you very much for your efforts.
Best,
A.
Hello:
Sorry for the delay ...
... can you open the pihole web admin page?
Yes, no problem with that.
Up at the top left I have this data:
Status
DNS service not running
Load: 0 0 0
Memory usage: 3.1 %
Once I log in, the four screens (green, blue, ochre and red) have no information, just 'NaN'.
If I go to the 'Settings' page, I get the error message I mentioned in previously at the top:
Error
There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
The system tab reads:
FTL Information
The FTL service is offline!
re: /etc/pihole/setupVars.conf
... same as mine, except for PIHOLE_DNS_1=127.0.0.1#5335
This might be valid ...
It is.
I have Pi-Hole runninng as a recursive DNS server in a Chimaera headless VM inside my box.
So I use my own DNS server.
--- note start --->
If you want to check on how it is done, check this video: https://www.youtube.com/watch?v=FnFtWsZ8IP0
There are also a couple of web pages: here: https://opensourcelibs.com/lib/pihole-unbound and here: https://medium.com/nerd-for-tech/recurs … a766d4f703
<--- note end ---
My pihole goes out to other DNS servers ...
Mine goes to 192.168.1.3 which is the IP of the Chimaera VM.
This setup was working perfectly well until the last upgrade to Pi-hole v5.11.4 FTL v5.16.2 Web Interface v5.13. 8^°
Maybe it was a combination of that and some Devuan update?
Did we have a Devuan update involving access to port 4711? No idea ...
what happens when you run these ...
I think I tried this one the other day.
[root@devuan ~]# ss -tnlp | grep 4711
[root@devuan ~]# Nothing.
Same as if I try to telnet to the VM from my box:
[root@devuan ~]# telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
[root@devuan ~]# root@devuan:/etc/pihole# ss -tnlp | grep 4711
No ...
Can't do that.
Pi-hole is not installed up in my box, it is installed in the VM.
So it would be this:
root@chimaera:/etc/pihole# ss -tnlp | grep 4711
root@chimaera:/etc/pihole# Again, nothing.
root@chimaera:/etc/pihole# telnet 127.0.0.1 4711
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused <----- this is it. But why?
root@chimaera:/etc/pihole# Thank you very much for your efforts.
Much appreciated.
Best,
A.
Hello:
What is the output of:
service lighttpd status
Here it is:
root@chimaera:~# service lighttpd status
lighttpd is running.
root@chimaera:~# FYI, my (very-old) FTL.php contains this:
function connectFTL($address, $port=4711) { if($address == "127.0.0.1") { // Read port $portfile = file_get_contents("/var/run/pihole-FTL.port"); if(is_numeric($portfile)) $port = intval($portfile); } // Open Internet socket connection $socket = @fsockopen($address, $port, $errno, $errstr, 1.0); return $socket; }
I think that whatever is going on has been caused by some change in the Pi-Hole configuration.
... next place to look would be /etc/pihole/setupVars.conf... check if anything looks off in there.
Here it is:
root@chimaera:~# cat /etc/pihole/setupVars.conf
WEBPASSWORD=688cee6d6cc168f344644ff376482d3cd6894b5d294962dd41a514887f8972b2
BLOCKING_ENABLED=true
DNSSEC=false
REV_SERVER=false
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=127.0.0.1#5335
PIHOLE_DNS_2=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
DNS_FQDN_REQUIRED=true
DNS_BOGUS_PRIV=true
DNSMASQ_LISTENING=local
root@chimaera:~# At first sight it 'looks' OK.
Not that I'd have much idea ... 8^/
... don't forget the log files: /var/log/pihole/FTL.log and /var/log/pihole/pihole.log
These are the last two lines in /var/log/pihole/FTL.log:
[2022-08-19 18:05:28.675 1140M] Listening on port 4711 for incoming IPv4 telnet connections
[2022-08-19 18:05:28.696 1140M] Error opening IPv6 telnet socket: Address family not supported by protocol (97)As you can see, port 4711 is mentioned.
Surely related to this line in the debugging info:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
/var/log/pihole/pihole.log is empty.
If fsockopen gets refused trying to connect to 127.0.0.1:4711, then there is a permissions problem with port 4711.
How do I troubleshoot that, specifically?
eg:
I cannot reach port 4711 on the VM from my box:
user@devuan:~$ telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
user@devuan:~$ [root@devuan ~]# telnet 192.168.1.3 4711
Trying 192.168.1.3...
telnet: Unable to connect to remote host: Connection refused
[root@devuan ~]# ^^^ This ^^^ means that it is closed to outside access.
pihole-FTL uses port 67 ( DHCP ) IPv4 UDP
pihole-FTL uses port 547 ( DHCPv6 ) IPv6 UDP
lighttpd uses port 80 ( HTTP ) TCP
pihole-FTL 4711 TCP
But if pi-hole needs to use it for whatever, it should be able to.
ie: part of the installation (?) to make that happen.
FTL is our API engine and uses port 4711 on the localhost interface. This port should not be accessible from any other interface.
See https://docs.pi-hole.net/main/prerequisites/
Thanks for your input.
Best,
A.
Hello:
Hello:
It would seem like I am the only one ... 8^°
Said I because a search for 'pi-hole' or 'pihole' got me where it is mentioned but they were all mine. 8^°
Devuan is not a supported OS for Pi-Hole (but Debian is) so it's hard to figure things out when something goes wrong.
In any case, I have narrowed down the cause of a problem I am having.
After the last update, the DNS server is not starting and it looks like a permissions issue:
There was a problem applying your settings.
Debugging information:PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
Here is what is happens after I get this:
I opne a terminal on the VM where Pi-Hole is running and start pihole-FTL.
As it was stopped, it says so and then starts it:
root@chimaera:~# service pihole-FTL restart
Not running
FTL started!
root@chimaera:~#I then immediately query the pihole-FTL status to check if this is so ...
root@chimaera:~# service pihole-FTL status
[ ] pihole-FTL is not running
root@chimaera:~# ... but no.
As you can see it reports as 'not running'.
Here are lines 28 to 47 from the FTL.php script mentioned in the debug output:
...
28 }
29
30 function connectFTL($address, $port) {
31 if ($address == DEFAULT_FTL_IP) {
32 $config = piholeFTLConfig();
33 // Read port
34 $portfileName = isset($config['PORTFILE']) ? $config['PORTFILE'] : DEFAULT_FTL_PORTFILE;
35 if ($portfileName != '') {
36 $portfileContents = file_get_contents($portfileName);
37 if (is_numeric($portfileContents)) {
38 $port = intval($portfileContents);
39 }
40 }
41 }
42
43 // Open Internet socket connection <-------
44 $socket = @fsockopen($address, $port, $errno, $errstr, 1.0); <------
45
46 return $socket;
47 }
...How can I troubleshoot / find the cause of this problem?
ie: unable to connect to 127.0.0.1:4711 (Connection refused)
Thanks in advance.
Best,
A.
Hello:
Has anyone here at Dev1 installed/run Pi-Hole?
It would seem like I am the only one ... 8^°
Thanks in advance.
Best,
A.
Hello AP:
... they recommend the 32-bit builds by Steve Pusser.
... don't know if the latest Pale Moon will work better ...
I only had Fixefox installed due to the lack of a 32-bit PM.
I don't really like FF but could not find anything else at the time.
Fortunately, I've solved the issue with the ADSL.
Some DH at the telco did a remote firmware upgrade (the usual), changing my customer ID/PW for the service and setting up a hard wired admin PW.
All this without informing me or anyone else, not even the techs who came to see what was going on.
So I'll put the PM 32-bit thing on the back burner for the moment, I now have a severe problem with with my Pi-Hole configuration.
Thank you very much for the heads-up and the link to the 32-bit PM. 8^D
Best,
A.
Hello:
rbit wrote:Have you run apt update recently?
^ This.
I mentioned that earlier in my previous post:
... but I run updates regularly, atb least once every fortnight.
Check the pinning with
apt policy firefox-esr
Here it is:
~$ apt policy firefox-esr
firefox-esr:
Installed: 78.15.0esr-1~deb10u1
Candidate: 78.15.0esr-1~deb10u1
Version table:
*** 78.15.0esr-1~deb10u1 500
500 http://deb.devuan.org/merged beowulf-security/main i386 Packages
100 /var/lib/dpkg/status
78.14.0esr-1~deb10u1 500
500 http://deb.devuan.org/merged beowulf/main i386 Packages
~$ And /apt/preferences.d is empty.
Thank you both for your input.
Best,
A.
Hello:
Well that's not right.
But I get this.
~$ sudo apt install firefox-esr/beowulf-security
Reading package lists... Done
Building dependency tree
Reading state information... Done
firefox-esr is already the newest version (78.15.0esr-1~deb10u1).
Selected version '78.15.0esr-1~deb10u1' (Devuan-Security:3.0.0/oldstable-security [i386]) for 'firefox-esr'
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
~$ I have not used Firefox on this rig for two or three years, but I run updates regularly, atb least once every fortnight.
I must be doing something wrong ... 8^º
This is the sources.list file:
# Linux Beowulf 3.0 - i386
# 20220325 - cleaned up sources list
deb http://deb.devuan.org/merged beowulf main non-free contrib
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
deb http://deb.devuan.org/merged beowulf-updates main contrib non-free
deb http://deb.devuan.org/merged beowulf-backports main contrib non-free
groucho@eee-dev3:~$ Thanks for your input.
Best,
A.
Hello:
Thanks for the prompt reply. 8^)
I have Firefox-esr from the repos on my 32bit Devuan Live install ...
Is it the same version I have installed?
ie: 78.15.0esr
Thanks for your input.
Best,
A.
Hello:
Background
My ISP has been screwing around with the cabling and as a result of whatever they are up to I am (for maybe 72 hrs.?) without web access.
As a result (firmware update?) I have lost access to the ADSL modem's admin -> advanced options settings where I direct it to a Chimaera VM running a PiHole/Unbound recursive DNS in my main box.
The local telco is on a holy war to rip out all the copper lines and get everyone and their dog on fibre manu military and what is happening is part of the pressure on the clients to go along.
Fibre is something I do not want or need as if/when power goes down, there is nowhere to call as the fibre modem goes dead without power.
And without power, there's nothing to charge your phone's battery with after a day or so.
Till this problem gets solved, I am using a slow WiFi on my Asus 1000HE, enabled for me by a neighbour two doors down.
Should the admin lock-out turn out to be permanent, I'll post a question to solve the modem problem on another thread.
Request
For now I need the forum's collective to give me a hand and suggest a viable 32-bit browser for my 1000HE.
The installed browser (have not used it since before the pandemic) is Firefox 78.15.0esr, not the best choice at present.
As we know, Pale Moon stopped the 32-bit versions back in 2020.
The 1000HE is running Devuan 32-bit on a back ported kernel, just like my main box.
~$ uname -a
Linux eee-dev3 5.10.0-0.bpo.15-686-pae #1 SMP Debian 5.10.120-1~bpo10+1 (2022-06-13) i686 GNU/Linux
~$ Thanks in advance.
Best,
A.
Hello:
Yes, the problem is almost certainly network interface name.
Hmm ...
Nothing in the release notes about that? 8^°
... sometimes it's better to just start fresh.
Granted.
It is much easier, particularly if you have limited Linux experience.
But ...
Check this out:
https://www.theregister.com/2022/07/25/ … _upgraded/
And tell me if anyone can pull that one off with any of the MS OSs .
Best,
O.
Hello:
Please select one of the following ...
I'm not ignoring your post ... But it does not seem to be a popular destination, so to speak.
But I agree: that particular topic has already been thrashed to death.
Resurrected and then thrashed to death.
Again.
Fortunately and for the time being Devuan is doing quite alright with what the devs and maintainers have on their respective plates, kudos to them.
I say for the time being because in the present situation, nothing is a given.
Keeping Devuan Linux working in spite of the systemd onslaught on the Linux ecosystem takes a lot of work.
That said ...
In my opinion, there's no "Init System" discussion needed.
Besides, it would probably attract the usual pro-systemd crowd.
Not needed either, at least here at Devuan.
What is needed is help in testing and bug reporting when those things arise.
Best,
A.
Hello:
Good to know someone took over at X.Org.
Kudos to Kanapickas! 8^)
---
This release fixes 2 recently reported security vulnerabilities in xkb, several
regressions since 1.20.x and a number of miscellaneous bugs.
Błażej Szczygieł (1):
present: Check for NULL to prevent crash
Jeremy Huddleston Sequoia (23):
rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined)
X11Application: Ensure TIS operations are done on the main thread
os/connection: Improve abstraction for launchd secure sockets
xquartz: Create a separate category for organizing user preferences
xquartz pbproxy: Adopt NSUserDefaults+XQuartzDefaults for preferences
xquartz: Fold spaces related preferences into NSUserDefaults+XQuartzDefaults
XQuartz: Ensure scroll events are delivered to a single window (not both X11 and AppKit)
meson: Bump requirement to meson-0.50.0
xquartz: Update Sparkle configuration to use SUPublicEDKey
xquartz: Update copyright for 2022
meson: Provide options to set CFBundleVersion and CFBundleVersionString in XQuartz
Revert "meson: Bump requirement to meson-0.50.0"
xquartz: Update autotools-based builds of XQuartz to account for recent changes
print_edid: Fix a format string error
xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK
tests: Fix build failure from missing micmap.c
meson: Support building Xnest and Xorg on darwin
XQuartz: Build the bundle trampoline when using meson
XQuartz: Add TCC reason keys to Info.plist
xquartz: Use correct defines when building to support Sparkle updates
xquartz: Fix a possible crash when editing the Application menu due to mutaing immutable arrays
XQuartz: Improve type safety for X11Controller's application menu editor
xquartz: Add missing files to distribution tarball
Olivier Fourdan (1):
render: Fix build with gcc 12
Peter Hutterer (3):
xkb: switch to array index loops to moving pointers
xkb: swap XkbSetDeviceInfo and XkbSetDeviceInfoCheck
xkb: add request length validation for XkbSetGeometry
Povilas Kanapickas (5):
Revert "os: Try to discover the current seat with the XDG_SEAT var first"
dix: Correctly save replayed event into GrabInfoRec
dix: Don't send touch end to clients that do async grab without touches
xfree86: Fix event data alignment in inputtest driver
xserver 21.1.4
Samuel Thibault (1):
xkb: fix XkbSetMap when changing a keysym without changing a keytype
git tag: xorg-server-21.1.4
https://xorg.freedesktop.org/archive/in … 1.4.tar.gz
SHA256: cbd5a1f75881e8a341823e51e489281aee0912c7023b4eed170b26b18f617e36 xorg-server-21.1.4.tar.gz
SHA512: 6e15d5c7f2a63f72688d3b04c3493271f419a69ce4b0c412a14293c40463733e050beb594689f27e5048b2356ce8f5b84aae96dad4a422054b36393d2f3d1847 xorg-server-21.1.4.tar.gz
PGP: https://xorg.freedesktop.org/archive/in … tar.gz.sig
https://xorg.freedesktop.org/archive/in … 1.4.tar.xz
SHA256: 5cc4be8ee47edb58d4a90e603a59d56b40291ad38371b0bd2471fc3cbee1c587 xorg-server-21.1.4.tar.xz
SHA512: eb5b8520d02908f72719e6ecfbf7a9bf139acb65ccae04d1db4223a8a2384cd3a94bd5afef10cce327b751b800cc2b79bfaa5ae35c95c3a217f775168082e68f xorg-server-21.1.4.tar.xz
PGP: https://xorg.freedesktop.org/archive/in … tar.xz.sig
---
Best,
O.
Hello:
Good to know someone took over at X.Org.
Kudos to Kanapickas! 8^)
Just received this in my mbox:
---
X.Org Security Advisory: July 12, 2022
Multiple input validation failures in X server extensions
=========================================================
All theses issues can lead to local privileges elevation on systems
where the X server is running privileged and remote code execution for
ssh X forwarding sessions.
* CVE-2022-2319/ZDI-CAN-16062: X.Org Server ProcXkbSetGeometry Out-Of-Bounds
Access
The handler for the ProcXkbSetGeometry request of the Xkb extension does
not properly validate the request length leading to out of bounds memory
write.
* CVE-2022-2320/ZDI-CAN-16070: X.Org Server ProcXkbSetDeviceInfo Out-Of-Bounds
Access
The handler for the ProcXkbSetDeviceInfo request of the Xkb extension
does not properly validate the request length leading to out of bounds
memory write.
Patches
-------
Patches for this issues have been committed to the xorg server git
repository. xorg-server 21.1.4 will be released shortly and will
include these patches.
commit 6907b6ea2b4ce949cb07271f5b678d5966d9df42
xkb: add request length validation for XkbSetGeometry
No validation of the various fields on that report were done, so a
malicious client could send a short request that claims it had N
sections, or rows, or keys, and the server would process the request
for N sections, running out of bounds of the actual request data.
Fix this by adding size checks to ensure our data is valid.
Fixes ZDI-CAN 16062, CVE-2022-2319.
This vulnerability was discovered by:
Jan-Niklas Sohn working with Trend Micro Zero Day Initiative
commit dd8caf39e9e15d8f302e54045dd08d8ebf1025dc
xkb: swap XkbSetDeviceInfo and XkbSetDeviceInfoCheck
XKB often uses a FooCheck and Foo function pair, the former is
supposed to check all values in the request and error out on
BadLength, BadValue, etc. The latter is then called once we're
confident the values are good (they may still fail on an individual
device, but that's a different topic).
In the case of XkbSetDeviceInfo, those functions were incorrectly
named, with XkbSetDeviceInfo ending up as the checker function and
XkbSetDeviceInfoCheck as the setter function. As a result, the setter
function was called before the checker function, accessing request
data and modifying device state before we ensured that the data is
valid.
In particular, the setter function relied on values being already
byte-swapped. This in turn could lead to potential OOB memory access.
Fix this by correctly naming the functions and moving the length checks
over to the checker function. These were added in 87c64fc5b0 to the
wrong function, probably due to the incorrect naming.
Fixes ZDI-CAN 16070, CVE-2022-2320.
This vulnerability was discovered by:
Jan-Niklas Sohn working with Trend Micro Zero Day Initiative
Introduced in c06e27b2f6fd9f7b9f827623a48876a225264132
Backporting of the security fixes also needs this commit:
f1070c01d616c5f21f939d5ebc533738779451ac.
Thanks
======
The vulnerabilities have been discovered by Jan-Niklas Sohn working with
Trend Micro Zero Day Initiative and fixed by Peter Hutterer.
--
Povilas Kanapickas
-----
Best,
O.
Hello:
For whatever it may be worth, on my main box I run Devuan Beowulf on a backported kernel:
user@devuan:~$ uname -a
Linux devuan 5.10.0-0.bpo.12-amd64 #1 SMP Debian 5.10.103-1~bpo10+1 (2022-03-08) x86_64 GNU/Linux
user@devuan:~$ And I have VirtualBox 6.1.34 running a headless Chimaera VM running PiHole 5.90 and a recursive DNS server:
user@devuan:~$ vboxmanage --version
6.1.34r150636
user@devuan:~$ user@chimaera:~$ uname -a
Linux chimaera 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
user@chimaera:~$ So my guess is that 5.10 is not a problem.
I guess it may be an issue with the kernel you are using and VM support for that kernel. (?)
Best,
A.
Hello:
Celebrate the light as it begins to turn to darkness . . .
Indeed ...
For me, yesterday was the shortest day of the year and last night was the longest one. 8^/
The good thing is that, from today onwards, days will be gradually getting <i>longer/i>.
It seems to me that few people reflect on the fact that we know that light is what it is because of the existence of darkness.
Works the other way around, obviously.
In any case, it's all about the balance of the cosmos.
Best,
A.
Hello:
... means that even if you currently have a working system, at some point something will upgrade ...
+1
Exactly the case with my Nvidia 340XX legacy cards with (up to now) no chimaera drivers.
The same thing happened with my Matrox cards a few years ago.
So ...
Then it was no more Matrox, ever.
And as of this year, it is no more Nvidia, ever.
If and when I need to get new cards, they will be AMD.
... cannot fix stupidity. Learn your lesson, sigh & walk away.
Quite so.
Best,
A.
Hello:
Found this early today.
---
Symbiote Linux malware spotted, and infections are 'very hard to detect'
'Performing live forensics on an infected machine may not turn anything up' warn researchers
---
https://forums.theregister.com/forum/al … x_malware/
Anyone know about this?
Best,
A.
Hello:
I've been following this thread as I have a parallel Devuan Beowulf setup on another drive which I keep up to date.
It is a practise bed for when I finally leave Xfce behind and go to a 100% Openbox setup.
I'd like to recover the best part of my old #! Waldorf installation.
there's also rofi, dmenu replacement ...
Seems that this app (just from reading about it) suffers from what I have seen in many other applications: feature creep.
Why can't things go back to the tried and true do one thing and do it well and just not complicate things?
I like how obmenu works and not getting it in chimaera is yet another reason to keep using beowulf with a backported kernel.
slim and wicd my other ones.
Of course, YMMV.
Best,
A.
Hello:
Saw this early today:
Original killer PC spreadsheet Lotus 1-2-3 now runs on Linux natively
As Google guru who ported it points out, the operating system did not exist when 1-2-3 came out in 1983
See:
https://www.theregister.com/2022/05/25/ … x_appears/
And:
https://lock.cmpxchg8b.com/linux123.html
I used it everyday many years ago at work, till DOS got killed and W3.10 was installed on the few available PCs.
Maybe it is finally gettings it's dues? 8^D!
A.
Hello:
... a post by a Ubuntu specialist, enigma9o7 on how to compile an
nvidia-legacy-304xx driver straight from Nvidia for Ubuntu 18.04.
Thank you. 8^)
... description for version 340.107 states that the driver does
work for xorg-xserver-1.20.
At the moment my box runs beowulf on a backported kernel ...
~$ uname -a
Linux devuan 5.10.0-0.bpo.12-amd64 #1 SMP Debian 5.10.103-1~bpo10+1 (2022-03-08) x86_64 GNU/Linux
~$ ... and xorg-xserver-1.20:
~$ cat /var/log/Xorg.0.log
[ 33.934]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 33.935] Build Operating System: Linux 5.10.0-10-amd64 x86_64 Debian
[ 33.935] Current Operating System: Linux devuan 5.10.0-0.bpo.12-amd64 #1 SMP Debian 5.10.103-1~bpo10+1 (2022-03-08) x86_64
--- snip ---Maybe the issue is just with 5.4 kernels.
ie: 5.4 included.
... driver does not work on kernels newer than 5.4.
I don't think I'm up to using anything other than the official Devuan kernels.
... before invoking the Nvidia installer, for the XFCE desktop, disable the compositor.
Yes.
The XFCE compositor is a PITA, screws up many things.
Has been a problem for quite a while but the devs/maintainers have taken no steps to fix it.
The old let's wait for the new release song and dance while putting the blame on something else.
So I'm slowly but steadily heading towards Openbox as the XFCE 4.16 and it's path to 5.x does not look too bright.
See:
https://forum.xfce.org/viewtopic.php?pid=56141#p56141
https://forum.xfce.org/viewtopic.php?pid=56143#p56143
https://forum.xfce.org/viewtopic.php?pid=56144#p56144
Thank you very much for taking the time to write this up.
I'll just stay with the backported beowulf kernel for the time being.
*************
Edit:
Given that the proposed solution involves downgrading the kernel (ie: to a pre 5.4 kernel) it would seem that it is not a suitable one.
At least, not a suitable answer to the OP's question: install nvidia-legacy-340xx drivers on Devuan chimaera.
This thread has had 2K views, so it's evidently of some interest to many.
ie: not a unique/one off setting.
From where I am seeing it, it should not be marked as solved.
But it's the admins say that counts.
*************
Maybe the Ubuntu people will get the chaps at Debian to do something about this Nvidia problem.
Maybe not, we'll see.
But I'm not giving up my video cards again.
Best,
A.
Hello:
@deepforest:
... it's not clear whether you've found a satisfactory solution or not.
Yes, same here.
Thanks to HevyDevy* I managed to set up the legacy 340xx drivers on beowulf and posted the terminal printout of the process.
It works with beowulf but I don't know if it will work with chimaera.
See: https://dev1galaxy.org/viewtopic.php?pid=24694#p24694
Did it work for you?
Did you have to do anything differently?
* it seems that there is a HevyDevy and a hevidevi ...
One and the same maybe?
@Len E.
... have an idea on how to do the installation ...
... won't burden you with the details ...
Please do share your solution with the forum.
Not a burden, many of us are in the same leaky Nvidia boat so all data is useful
I for one am not expecting much from nouveau and won't touch wayland.
Nvidia has recently released some source code but they did not include the source files to the 340XX blob.
Those cards are not manufactured any more so I can't see the reason for not releasing the source.
But Nvidia is Nvidia ... 8^|
I refuse to ditch a pair of perfectly working and quite suitable FX-580 Quadro cards for the lack of decent Linux drivers.
I already went through that a few years ago with a pair of Matrox G450s so if needed I'll just stay on beowulf.
A step-by-step terminal printout of the installation process like the one I posted would be of great help.
Thanks in advance.
Best,
A.
Hello:
... possibly the MemAvailable measure has lost ...
I had the exact same thought when I first saw the printout.
But no, it is correct.
The thing is that the /proc/meminfo list prints like this ...
root@OpenWrt:~# cat /proc/meminfo
MemTotal: 251868 kB
MemFree: 222268 kB
MemAvailable: 208408 kB
--- snip ---... which makes sense as they are usually progressively declining values.
ie: as I understand it (?) total will always be higher than free which will be equal to or higher than available due to buffers, cached, etc. This when swap is not part of the equation as it adds to the available memory.
I think the confusion arises because I put them the wrong way around.
ie: instead of how they are originally listed.
Now it looks like it makes sense:
~$ ssh user@192.168.1.3
--- snip ---
uptime: 32 min
ui: inactive
daemon: running
mem free: 222312 kB
mem available: 208392 kB
sda1 free/used: 3.6M 53%
sda3 free/used: 362.6G 58%
hd temp: 36°C
~# Thank you for pointing that out.
Best,
A.