On 12/11/24 16:14, Andrew M.A. Cater wrote:
On Wed, Dec 11, 2024 at 01:17:37AM -0500, gene heskett wrote:
installation is broken. Given the complexity of your haystack, I expect
finding and fixing the needle(s) would be time prohibitive.
It is indeed, David. The package managers apt and synaptic cannot find
anything wrong, and I should be on record as reporting that opening any
local file takes a minimum of 30 seconds to pop up the requester, during
which time the system is also locked. I've installed some stuff folks have
suggested to no avail so I gave up wasting everybody's time and just put up
with it. memtest86 has toured the 32gigs several times but doesn't find
anything. Frustrating but apparently it hasn't bothered anyone else. It
would very helpful if something stuck up a hand or did the gotta pee dance
but in 2 years nothing has. Maybe its something leftover from ripping out
orca and brltty that I tried to stop by a fresh install around 30 times.
The installer put them in even when I said no.
Gene,
You make life difficult for yourself (and, coincidentally, for the rest of us
who try to follow what you've done :) )
TL; DR
Which is nigh impossible, Andy, one of the reasons I quit harping on it,
I finally realized that to most of you, I am the ultimate power user,
making this machine do things that many don't understand. I don't often
think inside that famous box. I read virtually every msg posted here,
hoping to glean a clue to something I can check from someone else with a
similar problem. First, I don't own a wired mouse except the serial
interfaced one on my now dead from nearly 40 yo caps trs-80 color
computer 3. So hooking that up would probably trigger the install of
orca and brltty despite specifically skipping by that question from the
installer.. IDK, haven't tried it. Won't do this below either, because
putting it back together would be the equ of pulling a new mobo out of
the box and building it all up from scratch again. Those 2 slots, rumor
has it only 1 will work, but which one? No one can tell me. They are
buried UNDER several other cards, including 2 more multiport sata-II
cards holding now out of service raid10's. This mobo is filled up. A
radio would be nice, 3d printers come with them now, but where would I
put it? Video is mobo.
I'll probably do that when trixie is out, a year or so down the log if
I'm still here then. By building a new machine. Maybe by then wifi will
be secure, it is sure not now when a neighbor with a hell fone can use
60GB of my bandwidth a month w/o leaving a log. That was not found
until i had a new printer do a band scan and it showed up in my ipv4
address block. I run a dhcpd with its hands well tied. It only reply's
to known MAC addresses. I run a level 3 time server just to service the
rest of my machines but ntpsec does that regardless. Can't be stopped
w/o megabytes of iptables entry's.
You've got an NVME drive that's unused, I think, that you could put onto your
motherboard. Bring your system to the minimum you can - disconnect the other
drives for the meantime. Install Debian to that drive - standard, stable Debian.
Gradually reinstate the other drives and potentially copy data across once
you have a simple stable Debian 12.
The 30 installs you did resulted in a whole stream of annoyed emails: that was
almost entirely because you had a USB serial device. Simplify, simplify,
simplify.
If all else fails, get hold of a secondhand machine that you can use to
troubleshoot problems like this rather than your main machine.
All best, as ever,
Andy Cater
(amaca...@debian.org)
When I destabilize a system, my preferred solution is a backup,
re-image, and restore cycle. To make this solution possible, I have
invested myself in disaster preparedness. And, I must continue
investing effort on a regular basis to keep it viable.
When all I had was data backups, my best option was backup, wipe, fresh
install, and restore.
Things were truly scary before I had decent data backups.
If you rebuild the computer as a hypervisor host (using the NVMe PCIe
SSD) and a storage server (using the various SATA SSD's), you can do all
the experimentation you want inside virtual machines. If a VM blows up,
the base system keeps running and so do the other VM's. This removes
your current problem of "all of your eggs in one basket". Also, a good
hypervisor makes it easy to snapshot and revert VM's. This facilitates
disaster preparedness and disaster recovery for the VM's. You would
still need data backups; use the HDD's.
David
.
Thanks Andy, take care.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
