2.5.70

vt · Posted: Tue May 27, 2003 8:28 pm Post subject:

yes, it is a good kernel.

but if you experience oopses, or modules do no load, add

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

Thanks Lovechild,
I should have checked bugs.gentoo myself :oops:

I'm rebuilding glibc from a chrooted environment now -> fixes the problem as well.

Lovechild · Posted: Tue May 27, 2003 8:37 pm Post subject:

damn, nvidia-kernel dislikes mm1

vt · Posted: Tue May 27, 2003 9:09 pm Post subject:

best fix: radeon
secondbest: www.minion.de

darktux · Posted: Tue May 27, 2003 9:13 pm Post subject:

It works fine with me Lovechild.

which version of the nvidia-kernel package are you using? I had one new today, along with 2.5.70-mm1, which probably fixed things.
_________________
Lego my ego, and I'll lego your knowledge

www.tuxslare.org - My reborn website

Lovechild · Posted: Tue May 27, 2003 9:22 pm Post subject:

darktux · Posted: Tue May 27, 2003 10:03 pm Post subject:

You're welcome :wink:

_________________
Lego my ego, and I'll lego your knowledge

www.tuxslare.org - My reborn website

sindre · Guru Joined: 01 Nov 2002 Posts: 315 Location: Norway

Whoa! I just changed from cfq to as, now the kernel panics are gone. Seeing that as might be better anyway I'll just stick with that. Anyone else care to test if elevator=cfq gives them kernel panics in 2.5.70-mm1?

Lovechild · Posted: Tue May 27, 2003 10:25 pm Post subject:

lurid · Guru Joined: 12 Mar 2003 Posts: 595 Location: Florida

The first time I tried to re-emerge nvidia-kernel after booting 2.5.70-mm1 the kernel died while emerge was running ldconfig (ie. it built the nividia-module, but portage died afterwards) which caused some heafty damage. Nothing booting the Gentoo cd couldn't fix though. Trying it a second time the kernel died while in the middle of compiling it.

This doesn't seem to be an nvidia problem to me, it seems to be a kernel problem. Running ldconfig or compiling shouldn't cause it to die. For the record I was using the CFQ elevator and used the same .config file from 2.5.69-mm3. I'll try switching to AS and see if I can get through the emerge.

EDIT:

Ok, turning off the CFQ elevator seems to do the trick. Everything is working well.. not to sure about anything being "snappier" because everything was pretty fast to begin with (was using 2.5.69-mm3 and got used to it). I see the annoying "sound skips while browsing the web" thing is still around. :roll:

Are we ever going to get this fixed? I know we're still in dev-mode but Linus is talking like hes ready to release this kernel really soon. This bug can't go unfixed. I'd guess that 90% of computer users spend 90% of their time on the computer bowsing the web and listening to music.

IntergalacticWalrus · Posted: Wed May 28, 2003 1:08 am Post subject:

Damn, I just read through this topic and now I feel like trying 2.4.70-mm1 too...

However I'd like to know: you guys talk a lot about some elevator setting, but where exactly do you set it? Where do I put this "elevator=XXX"?

idl · Posted: Wed May 28, 2003 1:12 am Post subject:

dolbz · Posted: Wed May 28, 2003 1:20 am Post subject:

so what exactly is this elevator? anyone link me to somewhere or a quick explanation?

Thanks
Dolbz

cyfred · Retired Dev Joined: 23 Aug 2002 Posts: 596

Well ive been using mm1 for 12hours quite happily except for two little things regarding my mice. (its a laptop machine with a ps2 touch pad and a usb external mouse)

1) On boot up if I have mousedev compiled statically the system tries to load it as a module. This fails, so I compiled mousedev as a module. But now I can only use the ps2 mouse if I have the usb mouse plugged in. mousedev is in modules.autoload.d/kernel-2.5 and does get loaded... It seems there is some "mice" controller that just doesnt activate the ps2 mouse until something is loaded during inserting the usb mouse (wether during boot or when running).

2) Touch pad clicking doesnt work. As in i cant just tap the touch pad and have that recognised as a cllick. Thats no big deal but it is annoying... as im used to it now...

Other than that im quite happy

Well actually there was one other thing. On boot up I recieved

idl · Posted: Wed May 28, 2003 1:41 am Post subject:

ebrostig · Posted: Wed May 28, 2003 2:02 am Post subject:

idl · Posted: Wed May 28, 2003 2:06 am Post subject:

lurid · Guru Joined: 12 Mar 2003 Posts: 595 Location: Florida

Yeah, it locked me up hard twice too. I had the CFQ elevator enabled with 2.5.69-mm3 and I just changed the grub.conf entry to reflect the new kernel, not thinking twice about the elevator setting. I discovered this thread, switched it to AS and its running quite well now.

jimlynch11 · Posted: Wed May 28, 2003 2:18 am Post subject:

whats all this "as" talk?

rvalles · Tux's lil' helper Joined: 19 Feb 2003 Posts: 121

ebrostig · Posted: Wed May 28, 2003 2:33 am Post subject:

sindre · Guru Joined: 01 Nov 2002 Posts: 315 Location: Norway

Something that's been bugging me for a while: What is Huge TLB Page support? It's an option in the 2.5.x Processor type and features section. Enable or disable? Also there's this new /sys directory. What's it's purpose? Seems to me as an ordered mix between /dev and /proc.

ebrostig · Posted: Wed May 28, 2003 3:02 am Post subject:

IntergalacticWalrus · Posted: Wed May 28, 2003 4:14 am Post subject:

Just tried 2.5.70-mm1. A few problems occured:

- I get a kernel panic when I load my NIC drivers (e100).
- My ALSA drivers won't get loaded by the alsasound boot script. They seem fine if I load them manually with modprobe, though.

Basically problems with modules only (yes, I do have module-init-tools installed). And why did they change so much about modules anyway? The .ko extension, the new tools, god knows what else... ugh. When 2.6 will be out, migrating from 2.4 won't be too smooth cause a lot of things will be broken, that's for sure.