Dmitry wrote:
Hello!

I decided to try new development kernel. :) And i have some questions already.

First.

I had a linux-2.5.63.tar.bz2 on my HDD, so i thought that it would be less time for me if I just patch it rather then downloading full version. So i downloaded three patches (up to 2.5.66) and done the upgrade. Patch process went with no error or warning at all for all three patch files. :).
After that i tarred and bzipped resulting directory tree, and put linux-2.5.66.tar.bz2 file into /usr/portage/distfiles directory. And now sad things - emerge told me that md5 sum isn't correct :(. Then i found, that i didn't include top level directory (i.e. linux-2.5.66/) in tar file. I've done so, but... ooops... the same error :(. And even size of files were different.


Well, i compiled it without emerging :). And everything compiled FINE! Just wondering why md5sums don't match.

MD5 sums will tell you with whether the files match with a very high sensitivity to any change. Odds are that there are mild differences between your patched tree and the official kernel.org tarball for the kernel. Also, even if the patch was perfect, and you had EXACTLY the same tree as you'd get from the official tarball, you will still need to use the exact same parameters for bzip. Again, any difference, and the MD5 won't match.


I believe portage tells you what to do to correct the MD5, but that will be overwritten the next time you rsync. If you want it to not complain, you'll just have to get the real thing.


Anyway i have anoter questions:
- Kernel booted OK, but alsa doesn't found my SBLive card (support for it was compiled in for sure). It says:


ALSA device list:
        No sound cards found.

Why it might be? :( With 2.4.20 all works OK.

Not sure here, I'd check the alsa groups for complaints about 2.5 series kernels.


- Most irritating - at each boot (i booted 2 times with new kernel) my system clock ADVANCED to a DAY and couple of HOURS FORWARD!!! So now is April 6. :)

Sounds like a timezone problem or GMT RTC problem. Check into /etc/localtime:
ls -l /etc/localtime
lrwxrwxrwx 1 root root 30 2002-09-19 14:38 /etc/localtime -> /usr/share/zoneinfo/US/Central


Also look at what you have for your kernel config under General, there is an option there for "RTC stores time in GMT"

- Couldn't get any modules loaded:
depmod: QM_MODULES  nod defined.

Check /etc/modules.*


It seems that module-init-tools should help, but what if i'll boot my old 2.4.20 kernel? Will modprobe stuff work? As i understand, module-init-tools replace that programs with newer versions for 2.5.xx kernels. Am I wrong?

Newer modutils are generally backwards compatible.


Since you mentioned it, is there any particular reason you are running unstable kernels? I've tended to avoid anything but release candidates/stable for machines I care about (heck, I only recently started compiling my kernel with gcc 3.x!). If you are just looking to play, it would be far safer to do so in UML or a virtualizer such as VMWare or bochs. Sure you won't get a feel for speed improvements, but you aren't risking your data on unstable I/O developments. Just a friendly suggestion... <remembers the umount sync fiasco... and that was on "stable" kernels!>

-Dave

--
Public key available at pgp.mit.edu keyID:36F46FD0


-- [EMAIL PROTECTED] mailing list



Reply via email to