pacman -Syu : error glibc : /lib is already there...

[mupi]

The

Code: Select all

/lib

directory is meant to go missing - it's the root of the problem. That's the reason why we need to be calling commands with their full path.

pepedog: The instructions on alarm have changed. Everything was fine with the ones given yesterday, but now the text is barely visible.

[pepedog]

pepedog: The instructions on alarm have changed. Everything was fine with the ones given yesterday, but now the text is barely visible.

I see that, was a problem for my old eyes

[jakebpg]

Thank you very,very much pepedog, your link and instructions worked beautifully!

My RPI is now running and up to date. I'm now creating an RPI.img file on my laptop using the dd command on my archlinux laptop. This way if I brick my system a simple dd will bring my pi back to life.

Next up installation of xfce4 and all of its goodies.

Thanks again, you're a genus, thought I was going to have to wait for the next iteration of the arch release before being able to use this mini PC. I have many things I want to try with this thing starting off with the gpio pins.

[jakebpg]

pepedog, hate to say this but now more problems after the updates. Installed sudo and configured it and rebooted the system with reboot kernel panic and hit kdb with a long list of kernel errors. Yes this was after dd the sd card to an image file which should not have affected the sd card at all. I've searched the internet to no avail and everyone that has had this error is dead in the water. here's a breif on this first line kernel null pointer 00000000.

No fix for this that I can find. The really strange thing is that some times it will boot maybe 1 out of 10 times and its fine, I guess the trick is NOT to reboot these things when you actually get them running. I did get Xwindows installed after booting multiple times only to find that NO keyboard or mouse input is possible which put me right back to where I was originally upon receiving the rpi and bricking it multiple times in an attempt to get the keyboard and mouse working.
I'm going to plug this little bugger into my UPS and never reboot it again if I can get the damn thing to boot again!

But your fix to get past the glibc error worked great!

DO you know if there will be an announcement when the new image is released?

Thanks for your help.

Jake

[pepedog]

The image is probably on the download server, but I don't know link, download page is changed by Liz.
I got the nod that hard float repo on line, so that will be available soon.

Sorry to hear you troubled. Too late to give advice but it doesn't hurt running sync before umount, halt, or reboot.

Edit: someone found the link
http://downloads.raspberrypi.org/images ... 012-09-16/

[antiloquax]

Thanks pepedog. I've set up my filesystem using the rootfs you supplied and it's fine.
I hadn't realised a new Arch sd card image was available!
mark

[attos]

Hello all,

Yesterday I had trouble upgrading my systems running Arch Linux Arm and I just want to share my experience and how I fixed it.

I run Arch Linux Arm on a Sheeva plug, a Pogoplug and a Raspbery Pi and the solution worked for all of them.

I first tried to upgrade the packages on the RPi with pacman -Syu and got a conflict with glibc.

Code: Select all

error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded

Searching for the fix I found that the lib directory becomes a symlink according to the following page:
https://www.archlinux.org/news/the-lib- ... a-symlink/

The solution according to https://wiki.archlinux.org/index.php/De ... iki:usrlib is to:

Code: Select all

pacman -Syu --ignore glibc
pacman -Su

I tried it several times with no success. There is a warning on the previuos page not to use the --force switch. This is because forcing glibc to upgrade removes the /lib directory contents making the system unusable and requiring to boot from a boot CD and using the console, which are not avail on my systems.

Digging a bit further I found a way on how to upgrade glibc and is as follows:

Open two ssh connections to the RPi logging in as root.

On the first one install busybox (pacman -S busybox). Busybox is a group of self-contained commands that do not depend on glibc.

Once busybox is installed issue the following commands:

Code: Select all

busybox sh
cd /

On the second connection you will force glibc to upgrade:

Code: Select all

pacman --force -S glibc

After doing this your /lib directory should be empty or non existent and anything you try to execute will return with an error.

Go back to the first connection (the one running busybox) and issue the following commands:

Code: Select all

rm -rf lib
ln -s usr/lib /lib

(please use usr/lib and not /usr/lib)
At this moment the second connection should work again and your system will be updated.

I hope this helps, but I'm not responsible of any damages.

[Kjue]

Thanks man! I was starting a new with the armel image and had this specific problem when trying to update stuff. This helped a lot!