Date: Thu, 5 Aug 2010 16:23:41 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-hackers@freebsd.org Cc: Oleg Sharoyko <osharoiko@gmail.com> Subject: Re: PCI config space is not restored upon resume (macbook pro) Message-ID: <201008051623.53328.jkim@FreeBSD.org> In-Reply-To: <AANLkTimZxusSpj6BqKAYO_6YPCWVLW2hv_33K7C1rOus@mail.gmail.com> References: <AANLkTikMFhG1QLDf4raf%2BrxOKhobjoA-dRbUew2-8KeF@mail.gmail.com> <201008051145.53737.jhb@freebsd.org> <AANLkTimZxusSpj6BqKAYO_6YPCWVLW2hv_33K7C1rOus@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 05 August 2010 02:41 pm, Oleg Sharoyko wrote: > On 5 August 2010 19:45, John Baldwin <jhb@freebsd.org> wrote: > >> I'm afraid things are not that simple. I have tried without > >> success acpi_video.ko, > >> dmps.ko, sysctl hw.acpi.reset_video and sysutils/vbetool. And > >> what worries me, X server cannon start on resumed system. From > >> Xorg.log: (EE) NV(0): Failed to determine the amount of > >> available video memory It looks like videcard just ignores any > >> requests. > > > > Are you using the nvidia-driver or the "nv" driver from X? > > Have tried both. Error above is from "nv", and "nvidia" told that > it couldn't copy video bios and paniced. I have also tried "vesa" > which gave rather strange records in Xorg.0.log (see [1] for > complete log (63Mb)). Here some interesting lines: > > (--) PCI:*(0:1:0:0) 10de:0407:106b:00a0 nVidia Corporation G84 > [GeForce 8600M GT] rev 161, Mem @ 0x92000000/16777216, > 0x80000000/268435456, 0x90000000/33554432, I/O @ 0x00005000/128, > BIOS @ 0x????????/65536 > (==) VESA(0): Write-combining range (0xa0000,0x20000) was already > clear (==) VESA(0): Write-combining range (0xc0000,0x40000) was > already clear (II) VESA(0): Primary V_BIOS segment is: 0xc000 > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > (II) VESA(0): VESA BIOS detected > (II) VESA(0): VESA VBE Version 165.165 > (II) VESA(0): VESA VBE Total Mem: 2713920 kB > (II) VESA(0): VESA VBE OEM: <A5><A5><A5><A5> > (II) VESA(0): VESA VBE OEM Software Rev: 165.165 > (II) VESA(0): VESA VBE OEM Vendor: <A5><A5><A5><A5> > (II) VESA(0): VESA VBE OEM Product: <A5><A5><A5><A5> > (II) VESA(0): VESA VBE OEM Product Rev: <A5><A5><A5><A5> > (EE) VESA(0): Driver can't support depth 24 > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > > The last line repeats 983070 times. Strings with <A5> were very > long, I truncated them for readability. This is odd. > > 1. > http://www.oleg-sharoyko.net/files/freebsd/pci_config.201008/Xorg.v >esa.log Basically, it means the video ROM is not accessible or failed to POST. FYI, Mac's don't have "BIOS" any more. It is just emulated via "Boot Camp". Thus, my guess is the BIOS emulation is not being restored and/or video ROM is not shadowed properly. Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008051623.53328.jkim>