[arch-dev-public] udev-177
Hi guys, udev-177 is now in [testing], and a few words of caution are in order. Firstly, don't be alarmed by the warnings mkinitcpio will spit out when using udev-177, these are harmless and will go away in the next mkinitcpio release (which will move to core together with udev-177). A lot changed in this release, in particular * the build system was changed around and the standard install locations were changed. I did my best to change everything back, as we are not ready to move /bin to /usr/bin yet. * blkid and modprobe are no longer used, instead their respective libraries are used in internal tools. Both of these things might have caused some bugs, so please let me know if you notice anything. * as have been mentioned previously devtmpfs is now a hard requirement. This release depends on kmod, which is currently under heavy development. udev will therefore stay in testing until Dave decides that kmod is ready for core. Cheers, Tom
On Jan 12, 2012 3:52 PM, "Tom Gundersen" <teg@jklm.no> wrote:
Hi guys,
udev-177 is now in [testing], and a few words of caution are in order.
Firstly, don't be alarmed by the warnings mkinitcpio will spit out when using udev-177, these are harmless and will go away in the next mkinitcpio release (which will move to core together with udev-177).
A lot changed in this release, in particular
* the build system was changed around and the standard install locations were changed. I did my best to change everything back, as we are not ready to move /bin to /usr/bin yet.
* blkid and modprobe are no longer used, instead their respective libraries are used in internal tools.
Both of these things might have caused some bugs, so please let me know if you notice anything.
* as have been mentioned previously devtmpfs is now a hard requirement.
This release depends on kmod, which is currently under heavy development. udev will therefore stay in testing until Dave decides that kmod is ready for core.
Cheers,
Tom
Just to clarify, the errors from mkinitcpio are in regard to "missing" firmware rules and helpers in udev. Udev now handles firmware as a built-in function and no longer depends on external files. Other errors can happily be reported. Dave
On 12 January 2012 21:52, Tom Gundersen <teg@jklm.no> wrote:
Hi guys,
udev-177 is now in [testing], and a few words of caution are in order.
Firstly, don't be alarmed by the warnings mkinitcpio will spit out when using udev-177, these are harmless and will go away in the next mkinitcpio release (which will move to core together with udev-177).
A lot changed in this release, in particular
* the build system was changed around and the standard install locations were changed. I did my best to change everything back, as we are not ready to move /bin to /usr/bin yet.
* blkid and modprobe are no longer used, instead their respective libraries are used in internal tools.
Both of these things might have caused some bugs, so please let me know if you notice anything.
* as have been mentioned previously devtmpfs is now a hard requirement.
This release depends on kmod, which is currently under heavy development. udev will therefore stay in testing until Dave decides that kmod is ready for core.
I had to downgrade udev,kmod,mkinitcpio to make my laptop (wifi was broken and applications didn't start) working again. This error has gone after the downgrade: http://dpaste.com/687105/ I'm using systemd 38. -- Andrea
Hi Andrea, On Fri, Jan 13, 2012 at 11:52 AM, Andrea Scarpino <andrea@archlinux.org> wrote:
I had to downgrade udev,kmod,mkinitcpio
Any change we could narrow this down a bit? If you upgrade again kmod+mkinitcpio (possibly ignoring the versioned deps), do you still get the bug? I assume udev is the culprit, so would be nice to get a confirmation.
wifi was broken and applications didn't start
When you say that wifi was broken, do you mean at the kerne/modules level, or at the NM level? I.e. is it possible to get the wifi working using commandline tools, or even nm-cli as root? Any more details / logs about the applications not starting? E.g. which applications are not starting?
This error has gone after the downgrade: http://dpaste.com/687105/
Hm, so the NM related ones are surely caused by CK failing to start. No idea why CK is failing though (I have tested CK+sd+[testing] and it works fine for me). Does 'systemctl status console-kit-daemon.service' give you any more info?
I'm using systemd 38.
This should be unrelated, but do you have '-session optional pam_systemd.so' at the bottom of /etc/pam.d/kde* ? This is needed to get device ACL's to work, so would be nice if we could include it in the standard file (like is done for at least ssh and login). Cheers, Tom
On 13 January 2012 12:39, Tom Gundersen <teg@jklm.no> wrote:
Any change we could narrow this down a bit? If you upgrade again kmod+mkinitcpio (possibly ignoring the versioned deps), do you still get the bug? I assume udev is the culprit, so would be nice to get a confirmation.
I updated kmod,mkinitcpio,systemd (except udev then) and everything's fine.
When you say that wifi was broken, do you mean at the kerne/modules level, or at the NM level? I.e. is it possible to get the wifi working using commandline tools, or even nm-cli as root? I was broken at kernel level, I just found this (this is the output using udev 177):
[ 10.732916] Loading firmware rtlwifi/rtl8192sefw.bin [ 71.520133] rtl8192se:rtl92s_init_sw_vars():<0-0> Failed to request firmware! [ 71.520141] rtlwifi:rtl_pci_probe():<0-0> Can't init_sw_vars.
Any more details / logs about the applications not starting? E.g. which applications are not starting? Forgot that.
This error has gone after the downgrade: http://dpaste.com/687105/
Hm, so the NM related ones are surely caused by CK failing to start. No idea why CK is failing though (I have tested CK+sd+[testing] and it works fine for me). Does 'systemctl status console-kit-daemon.service' give you any more info? As I said, everything's ok without udev 177 now. The console-kit-daemon too.
This should be unrelated, but do you have
'-session optional pam_systemd.so'
at the bottom of /etc/pam.d/kde* ? This is needed to get device ACL's to work, so would be nice if we could include it in the standard file (like is done for at least ssh and login). Uh. I didn't know. If you say I should add it, I'll.
-- Andrea
On Fri, Jan 13, 2012 at 1:40 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
[ 10.732916] Loading firmware rtlwifi/rtl8192sefw.bin [ 71.520133] rtl8192se:rtl92s_init_sw_vars():<0-0> Failed to request firmware! [ 71.520141] rtlwifi:rtl_pci_probe():<0-0> Can't init_sw_vars.
Thanks, I'll look into it.
'-session optional pam_systemd.so'
Uh. I didn't know. If you say I should add it, I'll.
Please do. -t
On 01/13/2012 12:52 PM, Andrea Scarpino wrote:
On 12 January 2012 21:52, Tom Gundersen <teg@jklm.no> wrote:
Hi guys,
udev-177 is now in [testing], and a few words of caution are in order.
Firstly, don't be alarmed by the warnings mkinitcpio will spit out when using udev-177, these are harmless and will go away in the next mkinitcpio release (which will move to core together with udev-177).
A lot changed in this release, in particular
* the build system was changed around and the standard install locations were changed. I did my best to change everything back, as we are not ready to move /bin to /usr/bin yet.
* blkid and modprobe are no longer used, instead their respective libraries are used in internal tools.
Both of these things might have caused some bugs, so please let me know if you notice anything.
* as have been mentioned previously devtmpfs is now a hard requirement.
This release depends on kmod, which is currently under heavy development. udev will therefore stay in testing until Dave decides that kmod is ready for core.
I had to downgrade udev,kmod,mkinitcpio to make my laptop (wifi was broken and applications didn't start) working again.
This error has gone after the downgrade: http://dpaste.com/687105/
works fine for me.
I'm using systemd 38.
i blame this one. -- Ionuț
participants (4)
-
Andrea Scarpino
-
Dave Reisner
-
Ionut Biru
-
Tom Gundersen