Re: Sieć nie wstaje

[Google]

   journalctl -r, jest tego za duzo
   -- Logs begin at Tue 2019-10-01 10:05:49 UTC, end at Wed 2019-10-02
   13:01:20 UTC. --
   Oct 02 13:01:20 eosek systemd-networkd[354]: eth0: Configured
   Oct 02 13:01:08 eosek systemd-networkd[354]: eth0: Gained IPv6LL
   Oct 02 13:01:07 eosek kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link
   becomes ready
   Oct 02 13:01:07 eosek kernel: e1000e: eth0 NIC Link is Up 1000 Mbps
   Full Duplex, Flow Control: Rx/Tx
   Oct 02 13:01:07 eosek systemd-networkd[354]: eth0: Gained carrier
   ....
   Oct 02 12:58:07 eosek kernel: e1000e 0000:0a:00.0 eth0: MAC: 2, PHY: 2,
   PBA No: FFFFFF-0FF
   Oct 02 12:58:07 eosek kernel: e1000e 0000:0a:00.0 eth0: Intel(R)
   PRO/1000 Network Connection
   Oct 02 12:58:07 eosek kernel: e1000e 0000:0a:00.0 eth0: (PCI
   Express:2.5GT/s:Width x1) 00:1c:c0:9c:db:de
   Oct 02 12:58:07 eosek kernel: i801_smbus 0000:00:1f.3: SMBus using PCI
   interrupt
   Oct 02 12:58:07 eosek kernel: kvm: disabled by bios
   Oct 02 12:58:07 eosek kernel: e1000e 0000:0a:00.0: Interrupt Throttling
   Rate (ints/sec) set to dynamic conservative mode
   Oct 02 12:58:07 eosek kernel: e1000e: Copyright(c) 1999 - 2015 Intel
   Corporation.
   Oct 02 12:58:07 eosek kernel: e1000e: Intel(R) PRO/1000 Network Driver
   - 3.2.6-k
   Oct 02 12:58:07 eosek kernel: i5k_amb i5k_amb.0:
   hwmon_device_register() is deprecated. Please convert the driver to use
   hwmon_device_register_with_info().
   Oct 02 12:58:07 eosek kernel: intel_rng: Firmware space is locked
   read-only. If you can't or
                                 intel_rng: don't want to disable this in
   firmware setup, and if
                                 intel_rng: you are certain that your
   system has a functional
                                 intel_rng: RNG, try using the
   'no_fwh_detect' option.





   > On sroda, 2 pazdziernika 2019 12:58:09 CEST Google wrote:
   >>    Dane wpisane. Dalej nie mam sieci.
   > A podnies interfejs i ustaw IP# recznie :
   > ip link set eth0 up
   > ip a add 192.168.2.78/24  dev eth0
   > Bedzie cos innego dla:
   > ip a
   > albo cos podejrzanego w journalu
   > journalctl -r
   > ?
   --
   Pozdrowienia,
    Google