You are not logged in.
Assuming the system where the mate components are missing is the one that had the HDD crash:
Check the config files in your home dir. And compare them with the systems that are OK. That sounds the most likely cause if the OS is identical.
Thanks, that gives us something to go on.
There are a *lot* of models of laptop you might have and a lot of models of TV you might be trying to connect to. So telling us what you have makes it a lot easier to offer useful advice.
Let us know if you get it working or find it won't work. That would help someone else in a similar situation.
chris2be8 wrote:You would probably have got a better response if you had started by saying what make and model of laptop you have and what make and model of TV you would like to connect it to. And putting the above link in your first post would have been more helpful (or just saying what make and model it is).
As it is no one could offer any specific help since they could only guess what you were trying to connect.
It seemed rather clear to me, then again perception is everything.
And it seemed as clear as mud to me. You still havn't answered my questions:
What make and model of laptop do you have?
What make and model of TV would you like to connect it to?
Without that information we can't offer any specific advice.
You would probably have got a better response if you had started by saying what make and model of laptop you have and what make and model of TV you would like to connect it to. And putting the above link in your first post would have been more helpful (or just saying what make and model it is).
As it is no one could offer any specific help since they could only guess what you were trying to connect.
Do you have a GUI installed? If so what one? I assume tty1 is the normal text only display.
Exactly what happens when you try to log on to tty7 with a long password? It sounds as if it *might* be the GUI only allows you to enter 20 (or so) characters for the password (the programmers probably assumed no one would want to use a 24 char password). Does trying to log on produce a failed login reported in syslog or by lastb? If not the GUI might not be allowing you to try to log on.
Do you have another system? If so can you log on to the systems with problems via ssh (preferably before causing it to hang)? That should give you a way to enter commands (I've had to do this).
Just to confirm, does Ctrl-Alt-F1---7 work whan the system is not hung?
ctrl-alt-f1 (press all 3 keys at once) should get you to a text screen (there are 6 of them, ctrl-alt-f1 to ctrl-alt-f6). ctrl-alt-f7 should get you back to the GUI (try this out *before* you get another hang). If that works you should be able to log on and try commands like killall firefox and killall thunderbird.
If you can't free the GUI you could use sudo shutdown -r now as a slightly gentler way to force a reboot.
China (and other countries) will also be developing LLM and other AI systems. So any moratorium only lets China etc get a head start.
I can't think of a good option. But allowing Microsoft and Google to carry on as they wish is probably the least bad.
System FUBAR (video ATI RadeOn 4225 failed, no display. )
How badly failed is it?
Does the system show any sign of life when you try to boot it?
Does the display work if you try to boot off a live disk/USB stick? If not it might be a hardware fault.
Have you got another computer on the same network? If so does the faulty system respond to ping? Or come up far enough to SSH onto it?
Does ctrl-alt-f1 get you to a text screen?
If you re-installed the system then your username might have had it's numeric UID changed (it's the 3rd field in /etc/passwd). That would mean that everything in it's home dir would be owned by the old UID, not it's new UID. The sudo chown -R user:user /home/user command would have fixed it. And destroyed most of the evidence.
I've hit this problem before when switching distributions.
If your problem is that the system runs slowly then start by trying to fix that *without* disabling FDE.
A few questions to start with:
What sort of system is it? (Desktop or Laptop, make model, etc?)
What CPU has it got?
How much memory has it?
What is it's display? (Could you add a GPU if it hasn't got one?)
What is running on it? (OS, desktop env, etc?)
Is it using swap space very often? (If yes then adding memory might speed it up a lot.)
Try running top and vmstat to see if they say anything interesting.
Hopefully answering that lot will point you towards a fix.
Try searching everywhere outside /home that your user account could write to. (Ignore symlinks though, only permissions on what they point to matter.) Personal data could leak into any of them.
At least check /tmp/ and /var/tmp/ (you would probably need to make them separate encrypted partitions).
I assume both screens will be powered on before the boot. But how are they connected (are there two motherboard sockets or is one on a GPU)? And what sort of PC is it?
There *should* be a BIOS option to say which screen to use. But that probably only applies to the BIOS output.
You could try booting the system with one screen powered off and see what happens. Then try the other. (It probably won't help but costs nothing to experiment.)
One day i had complaints from every https site i tried to visit. The reason was:the hardware decided that current time is january 2002.
That sounds like the battery for the real time clock is going flat. And might cause it to forget changes you made to the BIOS settings (or just randomly change settings). Replacing the battery would be a good start, then check all the BIOS settings.
The first thing I'd try is to repeat round 1, cp sums.txt sums_1.txt, repeat round 2 and diff sums_1.txt sums.txt to see if they differ.
It will cause problems for scripts that call which. Unless stderr is sent somewhere harmless such as /dev/null it will either put out the message to the terminal (annoying, but probably the script will still work) or get mixed up with the output the script will try to parse (and probably make the script fail).
https://wiki.debian.org/NewInBookworm says:
Shell script writers are advised to use command -v instead.
But I won't be holding my breath waiting for *every* script calling which to be updated.
which is actually a shell script, so if this proves too annoying you could just update it on your system to comment out the message. And try to remember this if you write a script for someone else that uses which.
Don't blindly assume everyone on the left is virtuous. That would place you in grave danger if you encounter a psychopathic murderer who claims to be on the left to give people a false sense of security. And a con artist doing the same thing could give you a painful lesson.
In any case trying to fit all political views onto one dimension is far to simplistic. The extreme left and extreme right are almost identical in what they actually do, the centre are much further from them than they are from each other. Remember that Nazi is short for National Socialist.
Try running a port scan (eg nmap) from another system on the same network. That should tell you what ports are open.
If you don't have a port scanner sudo traceroute -T -p 80 realupnow.com would test access to port 80, Then you could repeat for other ports, eg 443 (https) and 22 (sshd). That should tell what ports are blocked.
Edit: we cross posted.
You may need to allow *inbound* access to port 80 (and port 443 if you want to use https). Knowing what point of view inbound and outbound refer to can be confusing.
Having a quick look from outside:
$ host www.realupnow.com
www.realupnow.com has address 66.172.90.106
$ ping www.realupnow.com
PING www.realupnow.com (66.172.90.106) 56(84) bytes of data.
64 bytes from 66.172.90.106: icmp_seq=1 ttl=47 time=110 ms
64 bytes from 66.172.90.106: icmp_seq=2 ttl=47 time=109 ms
$ sudo traceroute -T www.realupnow.com
traceroute to www.realupnow.com (66.172.90.106), 30 hops max, 60 byte packets
<snip>
13 168.182.127.17 (168.182.127.17) 114.734 ms 118.489 ms 116.881 ms
14 168.182.127.1 (168.182.127.1) 110.179 ms 110.515 ms 113.517 ms
15 168.182.127.98 (168.182.127.98) 118.143 ms 116.080 ms 117.728 ms
16 66.172.90.106 (66.172.90.106) 115.229 ms 109.814 ms 111.151 ms
17 66.172.90.106 (66.172.90.106) 3117.564 ms !H 3111.648 ms !H 3109.469 ms !H
But I can't tell what 66.172.90.106 is. Could that be your router's external IP address? Or the server's external IP address?
NB. traceroute -T uses a SYN packet as it's probe, to port 80 by default.
To get kernel driver info you need to use lspci -knn (pipe it into less to keep screen output searchable). See the man page for lspci.
Searching for recently changed files in /etc and your home directory might tell you what did it. It's more likely to be in /etc but might be in some subdirectory. Try the find command (read it's man page first if it's new to you).
The latest issue of Linux Magazine (called Linux Pro in some countries) has an article on Lynis, a tool to help harden Linux systems. I've not had time to read the article, but it's probably worth looking at (just put Lynis into your favourite serach engine and you should find it).
HTH
root@devuan1:/home/david1# modprobe e1000e bash: modprobe: command not found root@devuan1:/home/david1#
That makes me suspect you switched to root with su so didn't get your PATH updated. Try su - and see if modprobe works then.
If it still doesn't post output from:
echo $PATH
whereis modprobe
Please post output from:
uname -a
lspci -v -s nn (replace nn with the address of the nic).
Also check in /var/log/messages and /var/log/syslog for messages relating to the nic.
And are you sure the device the nic is connected to is OK? And the cable connecting it? With troubleshooting the most annoying problem is when the component you never thought to check is the faulty one.
Can you set ublock to *pretend* to allow ads, but not actually show them on your screen? It's an option I would like to have if I need to use a site that blocks access to people who are using ad blockers. The idea is that ads get downloaded but not shown, so the advertisers can't tell they are paying for nothing.