Slashdot Mirror
Linux Development Kernel 2.5.18 Released
the_real_tigga writes: "Well, the day is almost over, and still today's release of version 2.5.18 of the Linux development kernel tree has not yet hit Slashdot.
It is out, the official site is of course kernel.org, but be sure to check your local mirrors (usually www.country.kernel.org).
Here is the long Changelog,
major changes include suspend-to-RAM, more IDE and VFS fixes, and kbuild.
Linux Weekly has the news too, and a summary of the changes."
Folks,
buffer_head is now in its own header file, so in suspend.c, for example, you will need to include
< linux/buffer_head.h >.
Also, to get HFS (Apple filesystem) to compile, you have to include < linux/pagemap.h >
Best of luck...
w o r l d w i d e w e b e r
If anyone has the Yamaha YMF744B sound chip, then you should apply this little patch to get this card to work with the OSS system:
diff -Nru linux-2.5.12/sound/oss/Config.in linux-2.5.12-hq1/sound/oss/Config.in
--- linux-2.5.12/sound/oss/Config.in Tue Apr 30 20:09:00 2002
+++ linux-2.5.12-hq1/sound/oss/Config.in Wed May 1 12:50:03 2002
@@ -103,6 +103,9 @@
dep_tristate ' VIA 82C686 Audio Codec' CONFIG_SOUND_VIA82CXXX $CONFIG_PCI
dep_mbool ' VIA 82C686 MIDI' CONFIG_MIDI_VIA82CXXX $CONFIG_SOUND_VIA82CXXX
+dep_tristate ' Yamaha YMF7xx PCI audio' CONFIG_SOUND_YMFPCI $CONFIG_PCI
+dep_mbool ' Yamaha PCI legacy ports support' CONFIG_SOUND_YMFPCI_LEGACY $CON
FIG_SOUND_YMFPCI
+
dep_tristate ' OSS sound modules' CONFIG_SOUND_OSS $CONFIG_SOUND
if [ "$CONFIG_SOUND_OSS" = "y" -o "$CONFIG_SOUND_OSS" = "m" ]; then
@@ -164,8 +167,6 @@
dep_tristate ' Yamaha FM synthesizer (YM3812/OPL-3) support' CONFIG_SOUND
_YM3812 $CONFIG_SOUND_OSS
dep_tristate ' Yamaha OPL3-SA1 audio controller' CONFIG_SOUND_OPL3SA1 $CO
NFIG_SOUND_OSS
dep_tristate ' Yamaha OPL3-SA2 and SA3 based PnP cards' CONFIG_SOUND_OPL3
SA2 $CONFIG_SOUND_OSS
- dep_tristate ' Yamaha YMF7xx PCI audio (native mode)' CONFIG_SOUND_YMFPCI
$CONFIG_SOUND_OSS $CONFIG_PCI
- dep_mbool ' Yamaha PCI legacy ports support' CONFIG_SOUND_YMFPCI_LEGACY
$CONFIG_SOUND_YMFPCI
dep_tristate ' 6850 UART support' CONFIG_SOUND_UART6850 $CONFIG_SOUND_OSS
dep_tristate ' Gallant Audio Cards (SC-6000 and SC-6600 based)' CONFIG_SO
UND_AEDSP16 $CONFIG_SOUND_OSS
w o r l d w i d e w e b e r
They lied, this is actually suspend-to-disk, or swap, to be specific. The difference between this and the apm suspend, is that the apm suspend counts on the bios to do most of the work, while this addition (formerly called software-suspend) does it all in software, without any bios help. So, the computer doesn't still need to be on, and the bios can be from 1890 and it will still work.
http://students.washington.edu/djwatson
For those who don't have time to follow every kernel release, there's a page someone put together to follow all the big changes going into the 2.5 developement series here
No, it's not digital rights management.
It's Direct Rendering Module for 3D acceleration.
This is actually explained pretty well on the project's page which is here
The advantage of supend-to-RAM (generally, no idea if this applicable here) is that most of the components can be turned off. Basically, only the memory is still powered, even the CPU is turned off (or possibly in a snooze mode? not sure).
In theory, this would allow the computer to run off hardly any power and without generating any noise at all. At the same time the system would be back virtually instantly (as opposed to ~30 seconds for suspend-to-disk).
In practice, the CPU fan is left active, as is the PSU fan, so you don't gain a whole lot compared to just letting the computer run with the monitor turned off.
Switch back to Slashdot's D1 system.
It's both. The patch supports both suspend to
RAM and suspend to disk. It will work on a Mac.
It will be less buggy than APM and ACPI.
Do we really need /. to let us know when a kernel is released?
Of course, if you don't want to hear about linux, you can always exclude it from your topic list in your preferences.
Michael
There is no cryptographic solution to the problem where the intended receiver and the attacker are the same entity.
in the linux-2.5.18 directory at your bash prompt type:
.; echo wq) | ed kernel/suspend.c
(echo 44i; echo "#include <linux/buffer_head.h>"; echo
then recompile.
You're right about Suspend-to-RAM turning off most of the components, it also turns off the PSU and CPU fans, and you can't tell the difference between a computer on STR and one switched off, except for a tiny LED on the motherboard (at least on my mobo).
What you described is called "S1", it's suspend mode with the PSU and CPU fan running (but harddisks and graphics card turned off), which leaves the computer loud but dead.
Copied and pasted from a Google search result, the suspend "codes" are: Full-on (SO), Stop Grant (S1), Suspend to RAM (S3), Suspend to Disk (S4), and Soft-off (S5).
With STR, 5v run off the PSU to keep the RAM recharged. This is the same 5v that run for features like Wake-On-[LAN,Modem,Keyboard].
So I guess the kernel has suspend support now. That's cool, I use STR on Windows 2000 all the time, it would be cool to have it on Linux, but somehow I don't feel like using a dev-kernel.
What time is it/will be over there? Check with my iPhone app!
On a related note 2.2.21 is out (for those who refuse/can't upgrade)
Is this some sort of scheme to fool people into installing development kernels to make themselves feel 'cool'??
It's a scheme to get half a million more people to test the new code to see if they can break it.
Intelligent Life on Earth
So I guess the kernel has suspend support now. That's cool, I use STR on Windows 2000 all the time, it would be cool to have it on Linux, but somehow I don't feel like using a dev-kernel.
I've been using suspend-to-ram on Linux for years. That's just basic apm, you tell the bios to do it and it does it. What's been added is suspend-to-disk without help from the bios. The problem with the bios suspend-to-disk is, it relies on a magic partition that Microsoft knows the details of (presumably by way of a driver provided by the OEM) but we don't. So we just do an end run around the whole thing, and so much for yet another sneaky attempt to make Windows appear more capable than Linux.
Life's a bitch but somebody's gotta do it.
"The problem with the bios suspend-to-disk is, it relies on a magic partition that Microsoft knows the details of (presumably by way of a driver provided by the OEM) but we don't. So we just do an end run around the whole thing, and so much for yet another sneaky attempt to make Windows appear more capable than Linux."
That is a BS statement on a modern desktop box and on a laptop nine times out of ten. Take a look at how MS handles the so called magic partition on XP. Surprise it's just a file in the root of the XP boot drive. No hidden partitions.
On a laptop, it's up to the OEM to determine what they use. Many do use the hidden partition method. All of those are documented, it's just that about ten percent are non standard. That's where you get cases of "This laptop cannot run FreeBSD with power managment features enabled" because it uses the BSD boot disk partition type and gets messed up if there are other BSD partitions.
So what we really have here is a bunch of people working hard to introduce meaningful changes to Linux that will benefit users, and people like you posting BS about how MS and OEM are hampering their efforts. Gimme a break.