After upgrading to sys-apps/hal-0.5.13-r2 and sys-fs/udev-146-r1 my ethernet card is completely ignored by networkmanager and I cannot use it. If I go back to hal-0.5.12_rc1-r8 then everything is fine again except that I have to install dev-libs/libvolume_id because otherwise hal fails to compile (BTW what package is supposed to provide libvolume_id now that it is not shipped with udev???). Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > (BTW what > package is supposed to provide libvolume_id now that it is not shipped with > udev???). > None, apps are supposed to be ported to libblkid, just as hal was.
(In reply to comment #1) > (In reply to comment #0) > > (BTW what > > package is supposed to provide libvolume_id now that it is not shipped with > > udev???). > > > None, apps are supposed to be ported to libblkid, just as hal was. > What about those of us who have to use <sys-apps/hal-0.5.13 because >=hal-0.5.13 does not work for us?
(In reply to comment #2) > What about those of us who have to use <sys-apps/hal-0.5.13 because > >=hal-0.5.13 does not work for us? > They should report their problem with details, so somebody could figure out if that's a problem with hal or that user's setup. For a start, see what's printed about your card by 'hal-device' both when it works and when it does not.
I installed networkmanager-0.7.1_p20090824 and now everything works fine even with hal-0.5.13-r2. As for the libvolume_id issue, I still think that there must be a solution for <sys-apps/hal-0.5.13 as long as these versions of hal are still in the tree.
Best I could find without your help is this commit: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NETWORKMANAGER_0_7&id=d185695d80b248354dd7a95fd896daa5c45085e5 On one hand, this may be a stable request for that version of NetworkManager, on the other, it may simply get a NEEDINFO.
(In reply to comment #5) > Best I could find without your help is this commit: > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NETWORKMANAGER_0_7&id=d185695d80b248354dd7a95fd896daa5c45085e5 This is it. This is the commit that fixes the issue. When nm_get_device_driver_name is called, it is called on the parent devices of the NIC. But in my case this device does not have an "info.linux.driver" and as a result nm_get_device_driver_name returns NULL. But this device has "info.subsystem = 'ssb'" and if you go one more level up in the hierarchy, to the grandparent, then this one has "info.linux.driver = 'b44'" so nm_get_device_driver_name will succeed. I think there are many people that use the b44 driver and will be affected by this bug. I propose to stabilize networkmanager-0.7.1_p20090824.
BTW, Rafał thanks for your help!
The latest version of sys-apps/hal broke my networkmanager when it went stable. Networkmanager couldn't see any wireless networks. I have a b43 chip: 0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) net-misc/networkmanager-0.7.1_p20090824 solves the issue for me. net-misc/networkmanager-0.7.1_p20090824 should be stabilized in my opinion.
sys-apps/hal was removed from tree wrt #313389, closing as OBSOLETE
