system upgrade: kmod

[hcjlnx]

hi guys,

i have got a problem upgrading my system. new kmod requires moving the kernel modules from /lib to /usr/lib. i upgraded kmod ignored the new kernel linux-raspberrypi-3.1.9-29 and moved the whole modules directory to /usr/lib. after that i installed the kernel. i had to do this twice, because after the first run modules directory was again created under /lib.

now rebooting fails. i just get into the rescue system.

any ideas?
hcjl

[naicheben]

Is it like this: http://www.raspberrypi.org/phpBB3/viewt ... 97#p124397 ?

[naicheben]

Ah, it was an error and will be fixed today/tomorrow.
The solution was to make a symlink after updating and then update the modules:

Code: Select all

pacman -Syu
ln -s /lib/modules /usr/lib/modules
depmod -a

But you should remove the symlink before updating again tomorrow!

[hcjlnx]

ah, i did it the other way round. symlink first and then the upgrade.

just try it again;-)

[hcjlnx]

thx, that did the trick.

[hcjlnx]

i restored an image i made before update. now new packages are:
automake-1.12.2-1
bash-4.2.036-1
hwids-20120711-1
initscripts-2012.06.3-2.1
iputils-20101006-4
kmod-9-2
libsystemd-186-2
linux-headers-raspberrypi-3.1.9-30
linux-raspberrypi-3.1.9-30
pcre-8.31-1
pkg-config-0.27-1
procps-ng-3.3.3-3
raspberrypi-firmware-20120714-1
readline-6.2.003-2
syslog-ng-3.3.5-2
systemd-tools-186-2
usbutils-006-1
util-linux-2.21.2-5

just upgrading results in the same error i had before. first upgrading kmod, creating symlink, running depomod -a as well.
do i have to wait for kmod > kmod-9-2?

on my i686 and x86_64 machines kmod and glibc update went fine.

btw ma i the only one with this problem?

thx again & regards
hcjl

[naicheben]

I have removed the symlink before upgrading and all went well.

[hcjlnx]

I have removed the symlink before upgrading and all went well.

well, that's good for you;-)

but i now don't know what to do in which order. as i said i restored a backup image, which i created before kmod update.

do i have to
1. upgrade kmod
2. mv /lib/modules /usr/lib/modules
3. upgrade kernel and the rest?

obviously not, because i did it like this and now my system doesn't boot anymore. i just receive the rescue login.

would you please be so kind and assist me again?

thx & rgds

[naicheben]

To remove the symlink you have to

Code: Select all

rm /usr/lib/modules

The command "mv" moves the files from /lib/modules to /usr/lib/modules but you must not do that. I You can make the symlink like described before:

Code: Select all

ln -s /lib/modules /usr/lib/modules

and kmod will look into /usr/lib/modules witch is a redirection to /lib/modules and find the files there.

So as I understand you first have to set the symlink, upgrade kmod, remove the symlink and then update the system?

[pepedog]

There is now a newer kernel where modules are in /usr/lib/modules
Not sure if you have to remove symlink first, but pacman -Syu should be ok now.
Watch out for upcoming glibc update, /lib will become a symlink to /usr/lib

[hcjlnx]

So as I understand you first have to set the symlink, upgrade kmod, remove the symlink and then update the system?

proceeding like this ****ed it up as well.
maybe the problem is something else. i will start from scratch with reinstalling.
thx for your help.
rgds
hcjl

[hcjlnx]

the problem wasn't the kmod or kernel update.

it was this https://github.com/archlinuxarm/PKGBUILDs/issues/211

thx again
hcjl

[hcjlnx]

how can i mark this thread as solved?

[naicheben]

Good question. It looks like you can only edit the topic subject if nobody replied and only for a short periode.
But you can reply to this and change the subject to [SOLVED] this appears in the search results (at least).

[hcjlnx]

Problem solved. Please read thread.

[naicheben]

how can i mark this thread as solved?

You may have solved the problem upgrading kmod ... but not how to makr the thread subject as [SOLVED]
But ok, never mind.