ACPI: -dp2 vs. -release
I installed the DP2 release of current on my Toshiba laptop when it was released and acpi worked very well. When the powercable was disconected the profile changed to economic _and_ the screen was dimmed a little bit to save power. But with every other iso release or cvsup from head since, acpi doesn't dim the screen anymore when running on batteries? what has changed or what can I do to make this work again(besides reverting back t -dp2)? /Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI: -dp2 vs. -release
On Thu, Feb 20, 2003 at 04:49:56PM +0100, Morten Rodal wrote: I have the same feature on my Dell laptop. The screen's brightness (or dim if you want) will go down when the computer is running on batteries. yes this happens with a 5.0-DP2 kernel. BUT not with a never kernel. It is however possible to change this back to normal with the Fn key (you probably have something similiar on your Toshiba) so that the brightness back to normal. Dell laptops remember this, so the next time I run the computer on batteries it will restore the brightness to the level I had last time I used it on batteries. The Fn-keys for turning the brightness up/down doesn't work with 5.0 on my laptop. I do not think this has anything to do with ACPI implimentation in FreeBSD. Since the brightness was turned down because the machine was put into economy-mode and the powermanagment is handled by the ACPI subsystem, I would believe that has. So the real question is: Can you configure the economy-profile to start doing it again? /peter -- If you hold a Unix shell to your ear, do you hear the C? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sound problems
On Tue, Nov 26, 2002 at 11:32:07PM +0100, Jan Srzednicki wrote: I have -CURRENT from Saturday on my box. I have SB 128PCI on my board, the module detects it without problems and seems to work fine. But the problem is that the sound is not clear; there happen to be some itchy noises from time to time, when I push up the system load. I wonder whether enlarging the sound buffer woul help, yet hw.snd.pcm0.buffersize is read-only, even setting it in /boot/loader.conf does not help. Under -STABLE those ithes never happened, so I don't think it's a hw issue. I have the same problem. It sounds like the soundbuffer runs empty somehow and needs to fill up before continueing. This results in something that sounds like a really small sample(1ms) looping for 1second or so. If this makes sense? :o) FreeBSD 5.0-CURRENT and a trident onboard soundcard which uses the snd_t4dwave.ko module. snip pcm0: Acer Labs M5451 port 0xed00-0xedff mem 0xf7efe000-0xf7efefff irq 11 at device 6.0 on pci0 /snip /peter -- (scheme (makes 'my (brain (hurt '() To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
