kernel upgrade---->urpmi problem
 

hi there

recently after i installed mandrake , urpmi was working well not untill today
whenver i try to install a package using urpmi, it asks for a cCD and on inserting that disk it ejects that and keeps on asking for the correct disc,which i am using.
i found out that this serror is not there in the generic kernel that came in the distro
i get this errior in the kernel that i have compiled myself
now how does a diffent kernel affect the urpmi
i am new to urpmi since i have been working on other distros previosly

any suggestions???

regards

See this thread: http://www.linuxquestions.org/questi...97#post1346097

the above post does not seem to solve my query since
as i mentioned earlier that urpmi is working fine with the kernel i got with mandrake
it is not working with my kernel that i compiled in mandrake using my settings

regards

Actually it does answer your question.... You just need to read between the lines a bit.



URPMI is trying to obtain a file from the CD.

It is unable to verify that the CD which is inserted is the one it thinks it needs.



This infers one of two things with your compiled kernel.

a) Your existing URPMI database is either corrupt OR does not include the inserted disk...

Or the more likely

b) With your recompiled kernel, Linux and hence URPMI is having difficulty reading files off the CD-ROM, which in turn is causing it to ask for the disk over and over.

Since you have no problems with the Mandrake kernel, I'd put money on the latter.

hi there

i do no think there is problem in reading the cds because
after i could no get urpmi working on this newer kernel i booted the older one and urpmi is workling fine there
also i am able to copy the package manualy from the CD and install them using urpmi in the newer compiled kernel

regards

What you just said proves what I posted is correct.


For whatever reason (switches, etc.) your COMPLIED kernel is not reading the CD's properly.

You just proved that yourself.

Once the files are copied they work via your hard drive but still do not work via the CD... or rather URPMI does not recognize the disk.

It's the same disk, so you KNOW that this can't be the problem, and the only variable is your compiled kernel.

thats is what i have not been able to figure out
how can it happen that my kernel is not reading my CDs
infact it is able to mount the same CD and copynthe respective rpm packages from there

regards

Probably some change you made is caused the kernel to not register the disk properly or causes it to misread the disk headers or track information.

You should first install the kernel-source rpm's

e.g.

urpmi kernel-source

Then WITHOUT changing anything, nor running make mrproper (something you really never want to do with Mandrake anyway...) nor make (x)menu, etc... just ...

make bzImage modules

And make sure it completes.

The resulting kernel should be no different than your installed one and should work the same way.

Test it by installing it and it's modules, and mkinitrd image.

Then once you verified that everything is ok, go to work on any changes.

BTW: Why do you need to modify the kernel?

Usually there is no reason to as every possible option is enabled, or at worst available on one of the alternate kernels on the repositories.

hi there

i am sure that the kerne compilation process is OK , i have compiled my kernel for oer a 100 times
and i get better performnce with my customized kernel,far better that i get from this generic kernel which comes with these distros

thanks for ur concern!!
meanwhile i look out for the required headers!!

regards

The performance differences should be imperceptable.

At worst, use the kernel-source as I've indicated and change the processor to reflect what you have then recompile.

This should leave you with an optimzed kernel, but everything set up as Mandrake requires.

Also remember that if you haven't already done so, edit /etc/sysconfig/harddisk and uncomment the indicated lines for a dramatic performance boost.

Finally make sure that towards the top of /etc/lilo.conf you have the word COMPACT

then re-run lilo.

thanx for the info!!

i am trying all this out

regards