ALARM on Samsung ARM Chromebook

[WarheadsSE]

There are a few, including the keymaps/symbl set from chrubuntu.

google: samsung arm chromebook keyboard linux

[simonbp]

$this->bbcode_second_pass_quote('JudgeGregg', '
')EDIT 2: It works !
Just followed the guidelines on
https://wiki.archlinux.org/index.php/WPA_Supplicant
and I'm back online.

[WarheadsSE]

I am actually not seeing this bug, per se, in that it drops connection. I have laggy spots that don't make sense, but I have those in ChromeOS and in ALARM. I have our kernel from the repo installed, and it behaves rather identically.

[EMKLI]

I tried to solve the glibc/filesystem problem, but i'm kinda stuck in a deadlock...

So far, i've tried the following:

- updating all packages possible with ignoring glibc and filesystem.

When i want to try to update filesystem pacman tells me:
$this->bbcode_second_pass_code('', '
/bin exists in filesystem
/sbin exists in filesystem
/usr/sbin exists in filesystem
')

So i moved everything which was in it to /usr/bin and deleted the folders. Everything still worked, even without the symlinks to /usr/bin.

When i want to update filesystem now, pacman tells me:
$this->bbcode_second_pass_code('', '
/lib exists in filesystem
')

But lib is already just a symlink to /usr/lib...

I've tried lots of things to bypass it. Deleting /lib wasn't a good idea, because then, nothing worked anymore. Forcing the filesystem to install even with /lib worked, but when i tried to install glibc afterwards, thi installation succeeds but i get the following error message:

$this->bbcode_second_pass_code('', '
/usr/bin/pacman: no such file or directory
')

And this is for every executable in there.


Any ideas?

Greetings,
Markus

[WarheadsSE]

So the steps in the news article did nothing for you?

[EMKLI]

$this->bbcode_second_pass_quote('WarheadsSE', 'S')o the steps in the news article did nothing for you?

[WarheadsSE]

http://bit.ly/14wVJEL

[EMKLI]

Thank you, i guess i got it. Since this is a fresh installation, there aren't any aur packages. But i indeed ignored the wpa supplicant and libnl. When i did this all the first time, i forgot to ignore them and this was the only time it worked for me... Well, lets hope that i can connect to the wifi afterwards... I guess this wpa bug is still alive?

[simonbp]

$this->bbcode_second_pass_quote('WarheadsSE', 'I') am actually not seeing this bug, per se, in that it drops connection. I have laggy spots that don't make sense, but I have those in ChromeOS and in ALARM. I have our kernel from the repo installed, and it behaves rather identically.

[WarheadsSE]

No, I have no issues connecting to my home WPA2 802.11n 2.4GHz network. Netcfg, passphrase, and all.

The lag for me is present on every connection I have tired, in ChromeOS or ALARM.