Hi, I found that the gnome-shell extension can not show the status of laptop cell charging. So I reinstalled the laptop-mode-tools, and changed the wired interface name from "eth0" to "enp0s31f6" in the file /etc/laptop-mode/conf.d/ethernet.conf as advice from Ritesh.
Then, I reboot several times, it seems running OK. I will try more times. > -----原始邮件----- > 发件人: "Ritesh Raj Sarraf" <r...@debian.org> > 发送时间: 2020-02-27 01:56:04 (星期四) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: 925...@bugs.debian.org > 主题: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name > maybe changed when reboot > > Control: serverity -1 important > > > I am lowering the severity as this is common reflection of problems > elsewhere disguising as a problem with laptop-mode-tools. > > > Couple of things to mention: > > * If you know of the persistent name for your interface, can you > populate that into the /etc/laptop-mode/conf.d/ethernet.conf and see if > that helps > > * From the logs that you've shared on the bug report, I'm lost. That > log is huge. laptop-mode-tools will apply power savings to ethernet > device. On boot, this happens quite early on. And probably that is > causing the problem. But I'd still like to see what holds the device so > long that NetworkManager fails to rename it. Does disabling the > `ethernet` module in laptop-mode-tools solve your problem ? If so, as a > workaround you can start with disabling it. And then try to investigate > what may be causing the device to remain busy for so long. > > * There's a valid bug report #925944, where a side-effect of enabling > power savings on the ethernet device results in NetworkManager not > considering the device. I am not sure how that should be solved because > how other tools (like NetworkManager, avahi etc) behave is beyond the > scope. But, if the integration of these tools do not work proper, > disabling one of the tools (like laptop-mode-tools) or a particular > hardware power savings (like ethernet module), could be a viable > option. > > > Coming up with an ideal default is challenging and I struggle to find a > balance. We do have /etc/laptop-mode/conf.d/board-specific/ . It is > documented in the manpage. > > > For the case of #925944, I think we should remove eth0 from the default > list. Because most devices these days have a unique persistent name and > it is best left to the user to find out the name and populate it in the > configuration file. That is what my upload today, 1.73.1-2 does. > > > On Wed, 2020-02-26 at 23:32 +0800, wg...@china.com wrote: > > OK, thank you very much! I will wait for all things are fine again! > > Thank you again! > > > > > > > > > -----原始邮件----- > > > 发件人: "Michael Biebl" <bi...@debian.org> > > > 发送时间: 2020-02-26 23:09:22 (星期三) > > > 收件人: wg...@china.com, 952...@bugs.debian.org, > > > laptop-mode-to...@packages.debian.org > > > 抄送: > > > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe > > > changed when reboot > > > > > > Control: reassign -1 laptop-mode-tools > > > Control: retitle -1 lmt breaks network interface renaming > > > Control: severity -1 serious > > > > > > Am 26.02.20 um 16:01 schrieb wg...@china.com: > > > > As your recommendation, I removed the laptop-mode-tools, it seems > > > > that wired interface' name is correct for several boot. But if > > > > there is no laptop-mode-tools, how I using its function for > > > > saving power to laptop? > > > > > > Don't use laptop-mode-tools. The kernel does it sufficiently well > > > on > > > it's own these days. I'm not actually sure what business > > > laptop-mode-tools has with your network interfaces. > > > > > > I'm going to reassign this bug report to laptop-mode-tools and > > > bumping > > > the severity to RC. > > > > > > Michael > > > > > > > > > > > > > -- > Ritesh Raj Sarraf | http://people.debian.org/~rrs > Debian - The Universal Operating System
