Re: Kernel 2.6: bootup errors not logged?

2004-02-01 Thread Kristian Niemi
After the first time I installed the new kernel, it seemed like the changes I made in /etc/modules didn't matter at all. Nor did modconf remove the old modules, i.e. the `fatals' bootup reported. After the second time I installed the (new) kernel, changes I made in /etc/modules *did* matter. So

Re: Kernel 2.6: bootup errors not logged?

2004-01-29 Thread Stef
Kristian Niemi mentioned : => They're not in /var/log/boot. => I don't believe it's "unresolved symbol" that is printed on the screen, => but not sure either. You know what I mean :) The message isn't the same in 2.6 kernel => Pretty sure the errors have something to do with modules from previ

Re: Kernel 2.6: bootup errors not logged?

2004-01-28 Thread Kristian Niemi
I know what I'm looking for, because I see them (the messages) flash by at bootup. It looks like it's trying to load (old) modules, producing FATAL something. Not sure, because they just whizz by; no time to read them properly, nor even to catch a glimpse of them all. They're not in /var/log/bo

Re: Kernel 2.6: bootup errors not logged?

2004-01-28 Thread Stef
Kristian Niemi mentioned : => At bootup I see a number or error-messages flash by, but they dissappear => too fast for me to read them. I've tried to find them in dmesg & various => files in /var/log/, but so far I haven't had any luck. I see the place You can't read the error-messages, but you

Kernel 2.6: bootup errors not logged?

2004-01-28 Thread Kristian Niemi
Hi, I'm trying to switch over to kernel 2.6; it's up and running now. No real problems. But there's a for me mainly `cosmetic' problem (since everything works). At bootup I see a number or error-messages flash by, but they dissappear too fast for me to read them. I've tried to find them in dme