Re: Improper shutdown, now Kernel panic.

2019-09-14 Thread murph nj
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin wrote: > > Symbolic links missing on / (/bin->/usr/bin and such). > /bin/bash missing or corrupted. > /lib64/ libraries missing or corrupted. > systemd itself missing, pivot root attempts to run systemd and that > may be what is failing, but you don't r

Re: ssh

2019-09-14 Thread Ed Greshko
On 9/15/19 1:19 AM, Patrick Dupre wrote: > Here is the bizarre thing: > from a gnome-shell > telnet 192.168.1.12 22 > Trying 192.168.1.12... > Connected to 192.168.1.12. > Escape character is '^]'. > SSH-2.0-OpenSSH_8.0 > > Invalid SSH identification string. > Connection closed by foreign host. Th

Re: ssh

2019-09-14 Thread Patrick Dupre
Here is the bizarre thing: from a gnome-shell telnet 192.168.1.12 22 Trying 192.168.1.12... Connected to 192.168.1.12. Escape character is '^]'. SSH-2.0-OpenSSH_8.0 Invalid SSH identification string. Connection closed by foreign host. ssh 192.168.1.12 22 time out But from a terminal (ttx) the ss

Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 11:41 PM, Richard wrote: > Actually, it looks like you did a telnet to the (default) telnet port > (23): > > > telnet 192.168.1.12 > > rather than the ssh port (22), as Ed suggested: Thanks!  Good Catch. I only looked at the end result.  Gotta get out of the habit of expecting someo

Re: ssh

2019-09-14 Thread Richard
> Date: Saturday, September 14, 2019 22:13:11 +0800 > From: Ed Greshko >>> On 9/14/19 9:34 PM, Patrick Dupre wrote: > >>> From the remote system, what do you get when you try to "telnet" >>> to port 22? >>> >> telnet 192.168.1.12 >> Trying 192.168.1.12... >> telnet: connect to address 192.168

Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 10:13 PM, Ed Greshko wrote: > On 9/14/19 9:59 PM, Patrick Dupre wrote: >>> On 9/14/19 9:34 PM, Patrick Dupre wrote: Hello, ssh does not respond (time out, the machine is OK). Hence, I restarted it and systemctl status sshd ● sshd.service - OpenSSH serv

Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 9:59 PM, Patrick Dupre wrote: >> On 9/14/19 9:34 PM, Patrick Dupre wrote: >>> Hello, >>> >>> ssh does not respond (time out, the machine is OK). Hence, I restarted it >>> and >>> >>> systemctl status sshd >>> ● sshd.service - OpenSSH server daemon >>>Loaded: loaded (/usr/lib/systemd

Re: ssh

2019-09-14 Thread Patrick Dupre
> On 9/14/19 9:34 PM, Patrick Dupre wrote: > > Hello, > > > > ssh does not respond (time out, the machine is OK). Hence, I restarted it > > and > > > > systemctl status sshd > > ● sshd.service - OpenSSH server daemon > >Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor > >

Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 9:34 PM, Patrick Dupre wrote: > Hello, > > ssh does not respond (time out, the machine is OK). Hence, I restarted it and > > systemctl status sshd > ● sshd.service - OpenSSH server daemon >Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor > preset> >Active: a

ssh

2019-09-14 Thread Patrick Dupre
Hello, ssh does not respond (time out, the machine is OK). Hence, I restarted it and systemctl status sshd ● sshd.service - OpenSSH server daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset> Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ag

kernel error: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.

2019-09-14 Thread Cătălin George Feștilă
I got this error on cockpit and I want to fix it: 13:13 [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. kernel The content of this error is: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. PRIORITY3 SYSLOG_F