2012/8/6 Zack Breckenridge :
> At this point, after having simply read through the sources and done
> some research, it looks like remote debugging might not be necessary,
> or even very useful, in this case after all (though it would be nice
> to have for future debugging endeavors so I will look
At this point, after having simply read through the sources and done
some research, it looks like remote debugging might not be necessary,
or even very useful, in this case after all (though it would be nice
to have for future debugging endeavors so I will look into your
suggestions, thank you).
S
2012/8/5 matt :
> On 08/03/12 23:39, 乔楚 wrote:
>>
>> 2012/8/3 Zack Breckenridge :
>>>
>>> First of all, let me note that the Kernel config file I posted was for
>>> 10.0-CURRENT (a few weeks back now though).
>>>
>>> I've been looking into it, but still haven't developed a patch yet. I
>>> have ver
On 08/03/12 23:39, 乔楚 wrote:
2012/8/3 Zack Breckenridge :
First of all, let me note that the Kernel config file I posted was for
10.0-CURRENT (a few weeks back now though).
I've been looking into it, but still haven't developed a patch yet. I
have verified that the screen blanking issue, on my
2012/8/3 Zack Breckenridge :
> First of all, let me note that the Kernel config file I posted was for
> 10.0-CURRENT (a few weeks back now though).
>
> I've been looking into it, but still haven't developed a patch yet. I
> have verified that the screen blanking issue, on my hardware, occurs
> some
First of all, let me note that the Kernel config file I posted was for
10.0-CURRENT (a few weeks back now though).
I've been looking into it, but still haven't developed a patch yet. I
have verified that the screen blanking issue, on my hardware, occurs
somewhere in the vm86 mode emulation code (w
2012-07-23 05:45, Zack Breckenridge wrote:
>Attached is the kernel configuration file I used to build my kernel without
>VESA.
>
>I went through the same process as you: setting suspend bounce, etc., and
>looking at the dmesg output. Again, I also looked at the witness output
>from my Intel driver
Oops, there was an error with the attachment. Here's a second try.
- Zack
On Sun, Jul 22, 2012 at 2:45 PM, Zack Breckenridge wrote:
> Attached is the kernel configuration file I used to build my kernel
> without VESA.
>
> I went through the same process as you: setting suspend bounce, etc., and
Attached is the kernel configuration file I used to build my kernel without
VESA.
I went through the same process as you: setting suspend bounce, etc., and
looking at the dmesg output. Again, I also looked at the witness output
from my Intel driver when resuming X -- and I noticed that it simply w
2012/7/20 Zack Breckenridge :
> If you look at the line:
>
>
>> Jul 20 16:07:00 x201i kernel: vga0: calling BIOS POST
>
> in your dmesg output, and then grep through the source, you'll find this is
> actually being printed
> from "src/sys/dev/fb/vesa.c" .
>
> I had a similar problem. After syncing
If you look at the line:
> Jul 20 16:07:00 x201i kernel: vga0: calling BIOS POST
in your dmesg output, and then grep through the source, you'll find this is
actually being printed
from "src/sys/dev/fb/vesa.c" .
I had a similar problem. After syncing with FreeBSD 10-CURRENT and
compiling a kerne
>On Sat, Jul 7, 2012 at 10:40 AM, Brandon Gooch
> wrote:
>> On Wed, Jul 4, 2012 at 4:23 PM, mbsd wrote:
>>> On Tue, 2012-07-03 at 14:11 +0800, 乔楚/HonestQiao wrote:
>> [SNIP]
In All the test, the screen is light and black, system is hangup, nothing
can be done.
The only thing c
On Sat, Jul 7, 2012 at 10:40 AM, Brandon Gooch
wrote:
> On Wed, Jul 4, 2012 at 4:23 PM, mbsd wrote:
>> On Tue, 2012-07-03 at 14:11 +0800, 乔楚/HonestQiao wrote:
> [SNIP]
>>>
>>> In All the test, the screen is light and black, system is hangup, nothing
>>> can be done.
>>> The only thing can be don
>On Wed, Jul 4, 2012 at 4:23 PM, mbsd wrote:
>> On Tue, 2012-07-03 at 14:11 +0800, 乔楚/HonestQiao wrote:
>[SNIP]
>>>
>>> In All the test, the screen is light and black, system is hangup, nothing
>>> can be done.
>>> The only thing can be done, is push power button, to force it shutdown.
>>
>> Whic
On Wed, Jul 4, 2012 at 4:23 PM, mbsd wrote:
> On Tue, 2012-07-03 at 14:11 +0800, 乔楚/HonestQiao wrote:
[SNIP]
>>
>> In All the test, the screen is light and black, system is hangup, nothing
>> can be done.
>> The only thing can be done, is push power button, to force it shutdown.
>
> Which graphic
On Tue, 2012-07-03 at 14:11 +0800, 乔楚/HonestQiao wrote:
> >On 07/02/12 02:29, 乔楚/HonestQiao wrote:
> >> Follow by step in
> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
> >> #sysctl debug.bootverbose=1
> >> #sysctl debug.acpi.suspend_bounce=1
> >> #acpiconf -s 3
Am 03.07.2012 08:11, schrieb 乔楚/HonestQiao:
> #kldstat
> kernel zfs.ko opensolaris.ko acpi_ibm.ko
> #cat /root/set.sh
> #!/bin/csh
> sysclt -w sysctl debug.bootverbose=1
> sysclt -w sysctl debug.acpi.suspend_bounce=1
>
>
> sysclt -w hw.acpi.reset_video="$argv[1]"
> sysclt -w hw.pci.do_power_resume
>On 07/02/12 02:29, 乔楚/HonestQiao wrote:
>> Follow by step in
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
>> #sysctl debug.bootverbose=1
>> #sysctl debug.acpi.suspend_bounce=1
>> #acpiconf -s 3(or push Fn+F3)
>>
>> After a moment, the display is light and black
On 07/02/12 02:29, 乔楚/HonestQiao wrote:
Follow by step in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
#sysctl debug.bootverbose=1
#sysctl debug.acpi.suspend_bounce=1
#acpiconf -s 3(or push Fn+F3)
After a moment, the display is light and black, LED Sleep is ligh
Follow by step in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
#sysctl debug.bootverbose=1
#sysctl debug.acpi.suspend_bounce=1
#acpiconf -s 3(or push Fn+F3)
After a moment, the display is light and black, LED Sleep is light.
But it cant be resume. No button can do
20 matches
Mail list logo
