You are not logged in.
Hi
With the current systemd update my wlan0 interface was renamed to wlp3s0, wich i dont like much. Is this by any chance the new standard?
What bothers me more is that my mouse stopped working with this update and that i'm not able to shutdown and boot properly. I had to type "startx" to get my desktop started. SLIM did not start on it's own.
Anyone else with the same problems?
Regards,
Dove
Offline
With the current systemd update my wlan0 interface was renamed to wlp3s0, wich i dont like much. Is this by any chance the new standard?
This was already the standard but as far as I know on previous upgrades there was a mechanism in place to keep the old naming until the user takes action to use the new one. On the latest upgrade i got the following message:
:: Network device naming is now controlled by udev's net_setup_link
builtin. Refer to the NETWORK LINK CONFIGURATION section of the
udev manpage for a full description.
:: No changes have been made to your network naming configuration.
Interfaces should continue to maintain the same names.
I was already using the new scheme, though. What message did you get on update? The postinstall action should have told you what changes were made.
I cannot say anything regarding the other problems, sorry.
Offline
Is this by any chance the new standard?
New? Not extremely.
https://wiki.archlinux.org/index.php/Be … connection
Last edited by cjazz (2014-03-05 13:44:54)
Offline
Regarding networking, udev rule has been renamed. Upgrade of systemd took care of this in my case and renamed my mask rule (most straight-forward way to get "old" naming scheme).
:: Renaming 80-net-name-slot.rules to 80-net-setup-link.rules in order
to preserve existing network naming behavior.
‘etc/udev/rules.d/80-net-name-slot.rules’ -> ‘etc/udev/rules.d/80-net-setup-link.rules’
After recent update of my system I had following problems:
late boot console printk got reset to 15
I boot to console and the GPM failed on some "psmouse" / "mousedev" problems (visible in dmesg and systemd journal)
initcpio shutdown sequence got stuck in weird way
I've tried to add "psmouse" module to initcpio and all above issues went away.
Maybe it has something to do with https://www.archlinux.org/news/linux-31 … w-modular/, though I didn't investigate any further.
inactive, migrated to new user account: <mkoskar> (https://bbs.archlinux.org/profile.php?id=83604)
Offline
Maybe it's https://www.archlinux.org/news/linux-31 … w-modular/ ?
Too late ...
Last edited by karol (2014-03-05 14:09:20)
Offline
Well. I read the news and checked my output. It did not seem to be necessary to take action:
[dove@ArchBox ~]$ dmesg -t | grep '^i8042'
i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
Which is very different from:
$ dmesg -t | grep '^i8042'
i8042: PNP: No PS/2 controller found. Probing ports directly.
I don't see the necessity for the new interface names... but it is not a big problem. I can always rename my configurations.
Hadn't had any time to look into this properly. Maybe on the weekend.
Thanks
Offline