My Radeon card comes back from resume, but the backlight doesn't (it
stays off). Think this patch might help with that? I was gonna start a
separate thread to ask for help debugging my backlight issue...
Thanks,
Anthony
On 09/03/15 16:06, Adrian Chadd wrote:
> oioo, would you please put that ra
On 04/09/2015 01:18, Jung-uk Kim wrote:
> AFAICT, the whole suspend/resume code looks incomplete and very messy.
> In fact, I'll be very surprised if it ever worked. :-(
It does seem to work for me with the patch and other people report that the code
works for them even without the patch.
--
An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/03/2015 18:30, David Wolfskill wrote:
> [Much trimming, both of older content and recipient addresses --
> dhw]
>
> On Thu, Sep 03, 2015 at 06:18:52PM -0400, Jung-uk Kim wrote:
>> ... AFAICT, the whole suspend/resume code looks incomplete and
On 04/09/2015 01:29, Anthony Jenkins wrote:
> My Radeon card comes back from resume, but the backlight doesn't (it
> stays off). Think this patch might help with that?
Likely not, but who knows.
> I was gonna start a
> separate thread to ask for help debugging my backlight issue...
--
Andriy
[Much trimming, both of older content and recipient addresses -- dhw]
On Thu, Sep 03, 2015 at 06:18:52PM -0400, Jung-uk Kim wrote:
> ...
> AFAICT, the whole suspend/resume code looks incomplete and very messy.
> In fact, I'll be very surprised if it ever worked. :-(
>
> Jung-uk Kim
> ...
While
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/03/2015 13:50, Andriy Gapon wrote:
> On 31/08/2015 11:53, Adrian Chadd wrote:
>> Try disabling hardware one at a time. Ie, unload usb; unload
>> wifi; leave kms loaded for mostly obvious reasons.
>
> Adrian, Garrett,
>
> thank you very much f
oioo, would you please put that radeon patch into a review?
I have an older machine with a radeon card in it that doesn't yet
suspend/resume; I can now test it out!
-a
On 3 September 2015 at 10:50, Andriy Gapon wrote:
> On 31/08/2015 11:53, Adrian Chadd wrote:
>> Try disabling hardware one at
On 31/08/2015 11:53, Adrian Chadd wrote:
> Try disabling hardware one at a time. Ie, unload usb; unload wifi;
> leave kms loaded for mostly obvious reasons.
Adrian, Garrett,
thank you very much for your tips.
Turned out that it was radeonkms that was causing the problem :-)
BTW, here is another
hi,
Try disabling hardware one at a time. Ie, unload usb; unload wifi;
leave kms loaded for mostly obvious reasons.
I hit a few of these which turned out to be an issue in the suspend
path of a driver - and once I found it was the USB hardware but the
BIOS itself that was hanging - FreeBSD put US
> On Aug 30, 2015, at 23:13, Andriy Gapon wrote:
>
>
> I would appreciate any pointers at how to debug an ACPI suspend problem that
> I have.
>
> What I have so far. The system hangs when I try to suspend it and it gets
> reset
> by a watchdog. Setting debug.acpi.suspend_bounce=1 does not
I would appreciate any pointers at how to debug an ACPI suspend problem that I
have.
What I have so far. The system hangs when I try to suspend it and it gets reset
by a watchdog. Setting debug.acpi.suspend_bounce=1 does not make any
difference, so the hang happens before the final sleep code
11 matches
Mail list logo