What was your last good kernel?

[hard candy]

After messing with a Gentoo installation the last 2 weeks and trying out kernels from 2.4.26 to 2.6.9-gentoo-r6. Then trying out some newer kernels on Slackware.
AND having all kinds of problems with NVIDIA-6996 on the newer kernels, AND trying out udev on old and new kernels, AND compiling a Gentoo installation and after it finished Stage 3, then realizing my clock was off by 4 hours which led to all kinds of "clock skewed" error messages and starting over, AND sticking to WINXP for the past 24 hours because I was sick and tired of looking at a console, I started thinking, "What was the last good kernel that just compiled and booted and everything ran right from the start?"
It was 2.6.4 from sources, or 2.4.26 from the Slackware 10 cd. Oh, for those simpler times.
So I'd have to say the 2.6.4 kernel was the last kernel I enjoyed. As a matter of fact, I'm going to download it and compile it tonight.
This Gentoo installation business can get too complicated since "emerge" is a six letter word meaning "if you use me too liberally, I'll make life a b***h for you!", so I learned my lesson and will make my new media center PC from Slackware. Nothing against Gentoo, it's my lack of self control when I type "emerge" I have to watch out for, is there an Emerge 12-step program anywhere?
Well, back to Slack and the golden days when kernels were kernels and men were men. Back to the 2.6.4.

[Daedrus]

I am using 2.6.7 on Slackware current. I compiled it without any problems. I had to move back to 2.6.7 from 2.6.9 because there were issues with k3b and 2.6.9. I haven't seen any issues with 2.6.7 that I have run into.

[Parcival]

Gentoo development-sources 2.6.7

[mrBen]

I'm using a custom 2.6.7 on a Debian unstable box.

I avoided 2.6.8 because of the k3b problems. I'm looking to upgrade to 2.6.9 soonish.

[Enlighted One]

2.4.27

[Icarus]

Wow, nvidia-6996 drivers? Talk about cutting edge, we can only download the 6629

I've been using 2.6.8.1 for quite a while on Gentoo and have been quite happy with it (except for those times I realize I forgot a setting and need to recompile )

Oh, you're using udev...talk to bwkaz

[JavaPunk]

gentoo-dev-sources-2.6.7-r14

[je_fro]

gentoo-*-sources are buggy p's of s.
development-sources (2.6.9) works just fine here, once I figured out my SATA drive is now sda.

[leonpmu]

Currently, I don;t have the time, energy, and I am too laxy to recompile because I have nothing better to do, so I just download the latest updates from SuSE using You, and I am currently running 2.6.7-111....

[JohnT]

What was your last good kernel?

H-m-m-m...Sanders ......I think???

[hard candy]

H-m-m-m...Sanders ......I think???

I heard he kicked the bucket (didn't say if it was original or crispy).

[Parcival]

Originally posted by mrBen
I avoided 2.6.8 because of the k3b problems. I'm looking to upgrade to 2.6.9 soonish.

If you wanna avoid K3B problems, you may skip 2.6.9 as well, too.

[Icarus]

Originally posted by Parcival
If you wanna avoid K3B problems, you may skip 2.6.9 as well, too.

Yup, the changes made in 2.6.8 are the new standard of how sudo is handled

K3B wasn't broken, by the way, its ALL apps that have relied on using sudo for users to run certain processes as root. So the app still works just fine, you just need to be root to do it now.
This has been made a cdrecord problem as it was documented and mentioned in the kernel plans, but the cdrecord guy/people didn't want to be bothered with it and so they blame the kernel people.

So long story short, it's going to be broken untill the cdrecord people fix their broken app

[gehidore]

2.6.7 or 2.6.9 (vanilla kernels on gentoo) I refuse to use those *gentoo* filth kernels.
but along with my update to 2.6.9 I did an emerge auvD world (updating everything from the original packages from the date that the 2004.1cd was released) and have found that something is making my mouse lag coupled with a 20-50FPS loss in game. (so I'm not sure if it is the kernel or something(s) other than 2.6.9 yet)

[hard candy]

From Kernel trap:
http://kerneltrap.org/node/view/3644

"CD burning with 2.6.8/2.6.9 kernel - workaround
Unrated comment posted by Anonymous on Thursday, November 25, 2004 - 08:15

These kernels don't allow users to burn CDs even if cdrecord etc. are suid root. It makes no difference if you're using ide-scsi or ide-cdrom. You can work around this by using sudo. Add users and
relevant commands to /etc/sudoers using `visudo'
(see sudo and sudoers manpages).
eg. in /etc/sudoers:

username ALL=NOPASSWD:/usr/bin/cdrecord,/usr/bin/cdrdao

then in your .bashrc add these aliases:

alias cdrecord='sudo cdrecord'
alias cdrdao='sudo cdrdao'

This allows you to use cdrecord and cdrdao as a user without typing
`sudo' every time or being asked for a password. You'll have to do
the same with cdda2wav and cdparanoia if you use those too.
BTW I found that most of the CD burning programs apart from cdrecord
still don't recognise /dev/hdx so you still have to use ide-scsi and
the scsi device names.



Now I can burn CDs as a user but my sudoers and .bashrc
files are getting pretty large. Anyone know when these broken kernels are going to get fixed?



[ reply to this comment ]


New cdrecord version works with 2.6.9
Unrated comment posted by Anonymous on Thursday, November 25, 2004 - 12:07
I just tried cdrecord 2.0+a38-1 from Debian Unstable and it works with the 2.6.9 kernel. If set suid root, users can now burn CDs without sudo."


(So like the Postman said, "Stuff's getting better all the time".)