I am using 2.5.75 and am guessing that 2.6.0-test1 should be about the same. The sysfs doesn't hurt 2.4 kernels and is not actually needed. I am mounting it through automount, and even without it I only needed it for the cpufreq access. The sysfs gives access to the kernel data structures for userspace. The usbfs does matter if you also use usb file system on 2.4 since the name has been changed from usbdevfs. There is back support for the old name but I don't belive that forward support ;) For me acpi works quite well with acpid and acpi. It does matter whether you used the acpi patch for 2.4 kernels since the location of the files with the patched kernels and 2.6 under the proc file system is different then with the unpatched 2.4 kernels. AFAIK /sys has nothing to do with acpi since it appears under /proc and not /sys. Alsa actually worked quite well with the old configuration in place although I haven't managed to get alsaconf to work, it doesn't seem to recognise the sound card. Could be because alsaconf is ver 0.90 and alsa under 2.5.75 is 0.95, if anyone has any ideas? You could try to run a 2.4 kernel with the alsa modules, configure the card and then switch back to 2.6. A crude work around but it is a workaround.
On Tue, 2003-07-22 at 07:31, arief_mulya wrote: > Dear Marino, > > > Nice HOWTO. > > I like to know, if the change to fstab (sysfs and usbfs) will affect how > 2.4* kernel works? Have you tried that? > > About ALSA, it's perfectly working the last time I try them. But it > seems we need some change in the alsa init scripts. For me, the solution > was just compiled alsa into the kernel. > > Now ACPI. I think it work. But acpid and acpi package doesn't recognize > the existance, but I haven't try with /sys enabled yet. And another > thing, I got hang on resume with ACPI. > > I'm going to try (again) to install 2.6.0-test1 on my IBM T30 tonight. > > > > Best Regards. > -- > arief_mulya <[EMAIL PROTECTED]> > Damai Itu Indah > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
