Re: Problem with the lid closing event
Igor Korot wrote: Larry, -Original Message- From: Igor Korot [EMAIL PROTECTED] Sent: Jan 28, 2007 8:14 PM To: Larry Finger [EMAIL PROTECTED] Cc: Michael Buesch [EMAIL PROTECTED], Bcm43xx-dev@lists.berlios.de Subject: Re: Problem with the lid closing event Larry, -Original Message- From: Larry Finger [EMAIL PROTECTED] Sent: Jan 28, 2007 6:17 PM To: Igor Korot [EMAIL PROTECTED] Cc: Michael Buesch [EMAIL PROTECTED], Bcm43xx-dev@lists.berlios.de Subject: Re: Problem with the lid closing event Igor Korot wrote: Hi, Larry, I did a quick test and, indeed, the value calculation is the same in both cases. Sorry about the confusion. However, I found another problem. I am running Gentoo with 2.6.18 kernel with the LED activation and interrupt enabled patches. After running ifconfig eth1 up, the card is up, the WiFi LED is on, and everything works as expected. However, when I close and re-open the lid of my laptop, I lost the ability to restore it. I am not running the suspend software, I have a 'vbetool' installed on top of GNOME. Since evrything was working, I was able to capture the dmesg output, which is attached. I didn't see anything in the log that indicates an error. Is this dmesg output from before or after the lid closing? I don't see either the suspend or resume debug messages from bcm43xx. This dmesg is after the lid has been open. The WiFi LED was still on. However, the screen was not restored. There is a report of bcm43xx not resuming correctly after suspend to disk. Unfortunately, my graphics system crashes when I try to suspend and I have to do a power off. That prevents me from testing the suspend or resume code. It might be the same issue, or the different one. You can try to install the vbetool on you laptop, and check if it won't crash. Then we can check for the bcm43xx driver behavior This is the software I installed: http://www.srcf.ucam.org/~mjg59/vbetool/ It won't even compile here. Perhaps it is because I have an x86_64 system. I don't have time to debug that program. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
Hendrik Sattler wrote: Am Dienstag 30 Januar 2007 16:22 schrieb Larry Finger: This is the software I installed: http://www.srcf.ucam.org/~mjg59/vbetool/ It won't even compile here. Perhaps it is because I have an x86_64 system. I don't have time to debug that program. You can use the debian package or its source: http://packages.debian.org/testing/utils/vbetool They have an amd64 package thus it should compile just fine. VBETOOLS is useless on x86_64, the package is only for i386 to i686 32bit machines, so your suggestion is useless in this case. Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
Am Dienstag 30 Januar 2007 19:59 schrieb Jory A. Pratt: Hendrik Sattler wrote: Am Dienstag 30 Januar 2007 16:22 schrieb Larry Finger: This is the software I installed: http://www.srcf.ucam.org/~mjg59/vbetool/ It won't even compile here. Perhaps it is because I have an x86_64 system. I don't have time to debug that program. You can use the debian package or its source: http://packages.debian.org/testing/utils/vbetool They have an amd64 package thus it should compile just fine. VBETOOLS is useless on x86_64, the package is only for i386 to i686 32bit machines, so your suggestion is useless in this case. Don't tell me, I only have i386, tell the debian maintainer. He obviously sees some usage, there. HS ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
On Tue, 30 Jan 2007, Jory A. Pratt wrote: They have an amd64 package thus it should compile just fine. VBETOOLS is useless on x86_64, the package is only for i386 to i686 32bit machines, so your suggestion is useless in this case. Funny that, it seems to work quite fine here on my system. $ file /usr/sbin/vbetool /usr/sbin/vbetool: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.0, dynamically linked (uses shared libs), stripped I end up needing it to get my backlight to turn back on when opening my laptop, I've got an ACPI script calling /usr/sbin/vbetool dpms on So -Aaron ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
Larry, -Original Message- From: Igor Korot [EMAIL PROTECTED] Sent: Jan 28, 2007 8:14 PM To: Larry Finger [EMAIL PROTECTED] Cc: Michael Buesch [EMAIL PROTECTED], Bcm43xx-dev@lists.berlios.de Subject: Re: Problem with the lid closing event Larry, -Original Message- From: Larry Finger [EMAIL PROTECTED] Sent: Jan 28, 2007 6:17 PM To: Igor Korot [EMAIL PROTECTED] Cc: Michael Buesch [EMAIL PROTECTED], Bcm43xx-dev@lists.berlios.de Subject: Re: Problem with the lid closing event Igor Korot wrote: Hi, Larry, I did a quick test and, indeed, the value calculation is the same in both cases. Sorry about the confusion. However, I found another problem. I am running Gentoo with 2.6.18 kernel with the LED activation and interrupt enabled patches. After running ifconfig eth1 up, the card is up, the WiFi LED is on, and everything works as expected. However, when I close and re-open the lid of my laptop, I lost the ability to restore it. I am not running the suspend software, I have a 'vbetool' installed on top of GNOME. Since evrything was working, I was able to capture the dmesg output, which is attached. I didn't see anything in the log that indicates an error. Is this dmesg output from before or after the lid closing? I don't see either the suspend or resume debug messages from bcm43xx. This dmesg is after the lid has been open. The WiFi LED was still on. However, the screen was not restored. There is a report of bcm43xx not resuming correctly after suspend to disk. Unfortunately, my graphics system crashes when I try to suspend and I have to do a power off. That prevents me from testing the suspend or resume code. It might be the same issue, or the different one. You can try to install the vbetool on you laptop, and check if it won't crash. Then we can check for the bcm43xx driver behavior This is the software I installed: http://www.srcf.ucam.org/~mjg59/vbetool/ Maybe it will run fine on you video. Also, I tried to turn the card on, then off, and then close/open the lid. It didn't work as well. Which means that any card activity stops this software from restoring the screen. Thank you. Larry Thank you. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
Larry, -Original Message- From: Larry Finger [EMAIL PROTECTED] Sent: Jan 28, 2007 6:17 PM To: Igor Korot [EMAIL PROTECTED] Cc: Michael Buesch [EMAIL PROTECTED], Bcm43xx-dev@lists.berlios.de Subject: Re: Problem with the lid closing event Igor Korot wrote: Hi, Larry, I did a quick test and, indeed, the value calculation is the same in both cases. Sorry about the confusion. However, I found another problem. I am running Gentoo with 2.6.18 kernel with the LED activation and interrupt enabled patches. After running ifconfig eth1 up, the card is up, the WiFi LED is on, and everything works as expected. However, when I close and re-open the lid of my laptop, I lost the ability to restore it. I am not running the suspend software, I have a 'vbetool' installed on top of GNOME. Since evrything was working, I was able to capture the dmesg output, which is attached. I didn't see anything in the log that indicates an error. Is this dmesg output from before or after the lid closing? I don't see either the suspend or resume debug messages from bcm43xx. This dmesg is after the lid has been open. The WiFi LED was still on. However, the screen was not restored. There is a report of bcm43xx not resuming correctly after suspend to disk. Unfortunately, my graphics system crashes when I try to suspend and I have to do a power off. That prevents me from testing the suspend or resume code. It might be the same issue, or the different one. You can try to install the vbetool on you laptop, and check if it won't crash. Then we can check for the bcm43xx driver behavior Larry Thank you. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
