systemd stoped my wifi

[pjaneck]

Hello everybody,

yesterday my wifi stopped working on my samsung arm chromebook. It did some research https://lists.fedoraproject.org/pipermail/arm/2013-June/006116.html about the dmesg error and found out that the kernel should use the kernelspace to load firmware drivers now (I know this mail is from 2013 but it still makes sense to me.). The maintainers of systemd therefore disabled this feature. Since I'm running the chromeOS kernel which doesn't support this feature, I depend on systemd loading the firmware from userspace. Maybe this will be patched in the future...
Long story short. I cleared my pkg cache before my last update and cannot downgrade systemd. Is it possible to get the previous version of systemd from some "depricated" repository or can someone send the package (systemd-216-3) to me?

Thanks in advance,
Peter

[pepedog]

http://rollback.archlinuxarm.org

[pjaneck]

Thanks,

that is exactly what I was looking for.

Regards,
Peter

[Nyutag]

Same issue here, solved by downgrading systemd.

So why can't we, alarm user, can't have systemd with :

$this->bbcode_second_pass_code('', 'configure --with-firmware-path=/usr/lib/firmware')

?

I'm actually trying with the systemd-git in AUR without success...

[WarheadsSE]

If we can relevant recent proof that this applies, we'll certainly consider it. But what I am seeing does not lineup to recent versions. I will see about building a package with that, and if that has any effect when I have a spare moment (sadly too rare)

[pjaneck]

I tried the new systemd package 217-7. The issue still exists.

[Veyrdite]

Not only did the update stop my wifi firmware from loading, it stopped my usb ports from working. Awesome bananas!

Time to setup a boot drive I'm glad my exams are over.

EDIT: I should point out that I really appreciate the work done on ALARM for my platform. Please keep it up, regardless of how much we complain

[Veyrdite]

Anyone with similar troubles: 216-3 is good

[doragasu1]

I upgraded today (didn't power up my Chromebook for 2~3 months) and found this problem with systemd 218-1.

[WombleGoneBad]

Guys, thanks for this thread, I had exactly the same issue and this thread saved me a lot of time.

Just thought i'd clarify for anyone reading this - it is UDEV changes that caused the issue (which is now part of the monstrous systemd package). ( I don't use systemd, udev is the only thing i use from this package.)

I wish someone reliable would fork udev away from the systemd people... i know gentoo started something a couple of years back.. I wonder if anything came of that....