How can I go back to my old kernel? (Getting segfaults)

NegaBenji · Tux's lil' helper Joined: 08 Jun 2004 Posts: 90

I tried out the 2.6.9-r1 kernel the other day, since it's supposed to be stable with the eciadsl modem driver - problem was the modem itself wasn't being recognized, so I want to stick with 2.6.5 until I have time to mess around getting it to work. There's just one problem - I booted back into my 2.6.5 kernel and I'm having issues.

I set it up for framebuffer support back in the day, but it never actually worked (couldn't find any images) - until now. The screen corrupts a bit, but switching to another terminal and back fixes it up. But I seem to be getting some dmesg output leaking onto the screen. And when I look at dmesg, I get this:

bin-doph · Guru Joined: 23 May 2003 Posts: 302

Hi,

why don't u try this. Boot with a standard live-cd. mount your drives and chroot into your system. Then remove bootsplash from any runlevels (I use gensplash, so my service name is "splash", I guess there's something similar with bootsplash). Your modules should be ok, unless you recompiled them. Since your using different kernel-versions they should be located in the approprioate directory under /lib/modules. Leave the chroot, unmount your drives and reboot.

hth
-fe
_________________
perl -e '$_=q;4a75737420616e6f74686572205065726c204861636b65720as;;for(s;s;s;s;s;s;s;s;s;s;s;s){s;(..)s?;qq qprint chr 0x$1 and \161 ssq;excess;}'

NegaBenji · Tux's lil' helper Joined: 08 Jun 2004 Posts: 90

Thanks, I'll give that a go tomorrow. I'm not sure it's entirely down to the bootsplash though, that floating point exception I was getting in KDE/Xfce4 terminal windows seemed like a bad omen. I also saw some mention of 'badness' when the computer was shutting down?

I did recompile my modules, as in running 'make && make modules' when I compiled the kernel. Doesn't that build specific 2.6.9 modules though, in their own separate folder which is accessed depending on the running kernel revision? (I forget the exact path...) If recompiling them *is* causing this problem, do I just run 'make modules' from the 2.6.5 source directory to fix it all up again?

JohnDoe · Posted: Sun Jan 09, 2005 9:41 pm Post subject:

I know this is not what's under discussion here, but when I tried to make a new gateway machine I compiled a 2.6 kernel. (The older one still has a 2.4 and I've been very happy with it.)

I initially tried a hardened kernel but it still goes on the 2.6.7 version which is unstable with the driver. Then I moved to a 2.6.9-gentoo-r13 and it didn't work. It gave a "ERROR eciadsl-synch: failed to create shared semaphore" error.

Then I compiled a 2.6.9 kernel ('emerge =development-sources-2.6.9' since it already goes on the version 2.6.10) and it worked.

Don't know what the problem really is but it comes with the gentoo sources.