You are not logged in.
Pages: 1
2.6.10 has been released today! Shhhh keep it quiet Merry Christmas for all who celebrate it.
Offline
CHANGELOG lines 44576-44578:
Linux 2.6.10
Merry Christmas everyone. Ho ho ho!
The impossible missions are the only ones which succeed.
Offline
dubbed the "Woozy Numbat" release?
um...
...
...
*scratches head*
I think I may have had too much "holiday nog" to get that one...
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Yes, I don't know what I did with it. I had to laugh. First, it wouldn't boot, hung at uncompressing kernel, which usually means that I put in the wrong processor--booted back with the old kernel, turned out I'd somehow changed it from generic i386. Then, recompiled, got some error in the netfilter section. Played around with that and somehow had no network cards listed. I don't know what I did, but i did laugh. And no, it wasn't too much Christmas cheer, I was sober, though my wife was telling me to hurry as we had to go out.
So, got back just redownloaded and started from scratch.
Hopefully, it'll compile this time.
(In case it's not clear, I'm not blaming the kernel folks, this had to be me. Of course, I remember once quickly tabbing through make config to add a printer and managing somehow to remove hard drive support which made for an interesting boot.)
Still wonder how the heck I managed to remove all network cards from the config file. That one took talent.
(edited a few minutes later)
Should have added that of course, the second time around, everything worked without problem.
Sigh, now for FreeBSD CURRENT which died in the midst of buildworld last night.
Offline
lol..you probably accidentally disabled ALL networking support.
:twisted:
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Believe me, I laughed too. I could swear that I only removed a few things in netfilter, and I'd think if I disabled ALL networking support, I wouldn't even have had the generic stuff available, but at any rate, it was funny, though irritating.
All kidding aside--when I was new to buliding kernels, I never made stupid careless mistakes--I'd make some goofs from ignorance, but when new and nervous, one is very careful. It's only after yuo're experienced that you can REALLY mess things up. Half the time, it's because you <snicker>know what you're doing, so do it with only half your attention on it.
Ah well, all's well that ends well and all that.
Offline
Any issues with the new kernel? :-D
:?
Offline
None that I've run into. I haven't done any real stress testing, but the usual stuff works normally. (As I said, in case it wasn't clear, I have no idea what happened the first time, but am sure it was due to carelessness on my part--when I redownloaded and started the compilation from scratch, everything was fine and dandy and went completely smoothly.)
Offline
Current 3.14.6 Ati drivers won't work with kernel 2.6.10, unknown symbol error.
--
JSkier
Offline
Current 3.14.6 Ati drivers won't work with kernel 2.6.10, unknown symbol error.
Did you recompile the Kernel module?
Offline
Of course, thats where the unknown symbol error came from, while running make script in the /lib/modules/fglrx direcrtory.
JSkier
--
JSkier
Offline
Pages: 1