From: Igor Zubkov <igor.zubkov@gmail.com> To: ALT Linux Sisyphus discussions <sisyphus@lists.altlinux.org> Subject: [sisyphus] Сломался dhcp в GNOME3 / NetworkManager Date: Sun, 22 Sep 2013 14:10:25 +0300 Message-ID: <CAJXf7QOEEaV5DTT6w8SUt5OpEiDFKtfgf2u=4iwxQJcbCNe7zQ@mail.gmail.com> (raw) Hi, Вот это обновление привело к отваливанию WiFi через NetworkManager в GNOME3: $ rpm -q --lastchange dhcpcd * Пт сен 20 2013 Mikhail Efremov <sem@altlinux.org> 1:6.1.0-alt1 - Disable 'persistent' option by default. - Don't package 70-vendor-encap hook. - Updated to 6.1.0. $ Выгладит это всё примерно так: 1. Загружаем машину, входим в гном и сеть не поднимается вот так: $ ip ad sh 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 60:eb:69:99:8d:82 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:26:c7:82:51:5e brd ff:ff:ff:ff:ff:ff inet6 fe80::226:c7ff:fe82:515e/64 scope link valid_lft forever preferred_lft forever $ Здесь должна быть двух часовая пауза во время которой я пытался понять и починить. Единственно что я не делал, это откатить пакет dhcpcd т.к. официальный архив с Сизифом помер. 2. Интересно. Я запускаю руками от рута dhcpcd: # dhcpcd dhcpcd[4828]: version 6.1.0 starting dhcpcd[4940]: wlan0: starting wpa_supplicant dhcpcd[4943]: wlan0: failed to start wpa_supplicant dhcpcd[4944]: wlan0: Successfully initialized wpa_supplicant Line 1049: unknown EAP method 'FAST' You may need to add support for this EAP method during wpa_supplicant build time configuration. See README for more information. Line 1049: failed to parse eap 'FAST'. Line 1055: failed to parse network block. Line 1060: unknown EAP method 'FAST' You may need to add support for this EAP method during wpa_supplicant build time configuration. See README for more information. Line 1060: failed to parse eap 'FAST'. Line 1066: failed to parse network block. Failed to read or parse configuration '/etc/wpa_supplicant.conf'. dhcpcd[4828]: eth0: waiting for carrier dhcpcd[4828]: wlan0: rebinding lease of 192.168.1.66 dhcpcd[4828]: wlan0: leased 192.168.1.66 for 86400 seconds dhcpcd[4828]: wlan0: adding host route to 192.168.1.66 via 127.0.0.1 dhcpcd[4828]: wlan0: adding route to 192.168.1.0/24 dhcpcd[4828]: wlan0: adding default route via 192.168.1.1 dhcpcd[4828]: forked to background, child pid 5113 # 3. И всё заработало: $ ip ad sh 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 60:eb:69:99:8d:82 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:26:c7:82:51:5e brd ff:ff:ff:ff:ff:ff inet 192.168.1.66/24 brd 192.168.1.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::226:c7ff:fe82:515e/64 scope link valid_lft forever preferred_lft forever $ И так приходится делать каждую загрузку. -- Igor Zubkov http://hi.im/ice
next reply other threads:[~2013-09-22 11:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-22 11:10 Igor Zubkov [this message] 2013-09-23 11:17 ` Mikhail Efremov 2013-09-23 22:10 ` Mikhail Efremov 2013-09-24 8:13 ` Michael Shigorin 2013-09-24 16:26 ` Mikhail Efremov 2013-09-24 17:07 ` Michael Shigorin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAJXf7QOEEaV5DTT6w8SUt5OpEiDFKtfgf2u=4iwxQJcbCNe7zQ@mail.gmail.com' \ --to=igor.zubkov@gmail.com \ --cc=sisyphus@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \ sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru public-inbox-index sisyphus Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.sisyphus AGPL code for this site: git clone https://public-inbox.org/public-inbox.git