You are not logged in.

#1 2004-03-13 05:49:30

cmhood
Member
From: Portland, Oregon
Registered: 2004-01-06
Posts: 15

Upgrading from 2.6.3 to 2.6.4 loses path to modules

I tried to upgrade the kernel to the current version (2.6.4-1) and after reboot the system is still looking for modules in the /lib/modules/2.6.3 directory which no longer exists.

The "depmod" command returns with "WARNING: Couldn't open directory /lib/modules/2.6.3: No such file or directory  FATAL: Could not open /lib/modules/2.6.3/modules.dep.temp for writing: No such file or directory"

What is the magic command to point the system into the right place?

Offline

#2 2004-03-13 06:27:11

Xentac
Forum Fellow
From: Victoria, BC
Registered: 2003-01-17
Posts: 1,797
Website

Re: Upgrading from 2.6.3 to 2.6.4 loses path to modules

You didn't run lilo after your upgrade.


I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal

Offline

#3 2004-03-13 14:58:26

cmhood
Member
From: Portland, Oregon
Registered: 2004-01-06
Posts: 15

Re: Upgrading from 2.6.3 to 2.6.4 loses path to modules

That seamed to do it!

Thanks

Offline

#4 2004-03-13 19:43:03

wdemoss
Member
From: WV - USA
Registered: 2004-01-18
Posts: 222

Re: Upgrading from 2.6.3 to 2.6.4 loses path to modules

This seems to happen alot! Is there any way that a post_install on the kernel pkg could detect whether lilo is being used and run this? Just a thought.

-wd


Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?

Offline

#5 2004-03-14 02:50:33

sarah31
Member
From: Middle of Canada
Registered: 2002-08-20
Posts: 2,975
Website

Re: Upgrading from 2.6.3 to 2.6.4 loses path to modules

i don't think so but using a .install file to echo in a warning after install it woulod cut down on this error a wee bit.

a script may not be able to account for unusual lilo setups


AKA uknowme

I am not your friend

Offline

Board footer

Powered by FluxBB