similar to: hang after switcheroo'd...

On 13 October 2012 15:12, Daniel J Blueman <daniel at quora.org> wrote: > On my Macbook Retina, when switching to the integrated GPU, we see a > ioread32 issued to the discrete GPU, which hangs as it is in D3 [1] > (drm.debug is set to 14 here). > > Full kernel 3.6.2 boot logs with drm.debug=5 are at: > http://quora.org/2012/mbp-i915-panel.txt > > What additional

After analyzing verbose nouveau & drm dmesg, I have found seemingly no more useful details pertaining to having no TV-1 device. The TV-1 device might be getting lost within DRM, by setting the TV-1 (SVIDEO, Composite) device into DPMS mode or Full Power Down mode, and the ch7006 datasheet does say in this mode, all but the i2c circuits are disabled! Looking at

Hi, As summary says I cannot compile latest origin/for-airlied against kernel 2.6.34 on openSUSE. My archive: git archive origin/for-airlied drivers/gpu/ include/drm/ --prefix=drm-all/ | bzip2 >../drm-nouveau.tar.bz2 (So all necessary things should be in it ...) If you need further information: https://build.opensuse.org/package/show?package=drm-nouveau&project=home%3Ajobermayr (I think

On 01/26/2016 03:58 PM, Ilia Mirkin wrote: > On Tue, Jan 26, 2016 at 5:54 PM, don fisher <hdf3 at comcast.net> wrote: >> On 01/26/2016 03:24 PM, Ilia Mirkin wrote: >>> >>> sleep 1 && xset dpms force off >> >> Could you confirm exactly how to add the drm.debug=0x1e option. Is it >> another parameter on the kernel command line? > > Yep

Tom Lanyon <tom at netspot.com.au> wrote: > On 06/12/2007, at 8:20 AM, James A. Peltier wrote: >> > Tom Lanyon wrote: >> >>> >> Hi all, >>> >> Trying to install 5.0 or 5.1 (i386 or x86_64) on a new system from >>> >> an install DVD. As soon as the installer launches anaconda, the >>> >> screen shuts off

Hi all, I have an odd problem, for which I couldn't find any suggestions on google. A CentOS 5.7x64 gives me a blank screen on bootup, both to the 17" LCD monitor connected to the VGA port, and to the KVMOVIP device built-into the server, I can see the GRUB boot loader, and everything booting up, upto the point where it says "Waiting for driver initialization.", then it goes

Hi: I am having problems with isolinux.cfg I am receiving several error messages. 'Missing parameter in config file' and 'Unknown keyword in config file'. Here is a copy of my Isolinux.cfg maybe sombody can help me figure it out: default ks prompt 1 timeout 60 display custom.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 custom.msg

https://bugs.freedesktop.org/show_bug.cgi?id=31961 Summary: [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:6] Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=27828 Summary: Changing mode repeatedly locks up card Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi, all: I can't make my HP DL380 G2 servers to boot off local disk by using "default local" line in my PXE boot menu. For fully automated server setups, I have configured all my DL380 servers to always do PXE boot. By manipulating the default boot option in boot menu, I can control a server whether to install a new OS via kickstart or just boot off local disk. This scheme works

Hi. I have a problem with current kernel 2.6.35 and nouveau module compiled from git (today).From xorg.0.log I got information that no output was found.And here is some nasty kernel logs: ... Aug 2 21:53:02 zilog kernel: Linux agpgart interface v0.103 Aug 2 21:53:02 zilog kernel: [drm] Initialized drm 1.1.0 20060810 Aug 2 21:53:02 zilog kernel: nouveau 0000:01:00.0: PCI INT A -> GSI 16

greetings, We are a couple of new CentOS users here. We have previous experience with RH and FC installations. Now we'd like to move up in the world to CentOS. We successfully installed the 3-CD set of CentOS-3 on a laptop this weekend. When the script instructed us to remove the installation media and reboot, we did that and then the system hung after text was displayed showing the stopping

https://bugs.freedesktop.org/show_bug.cgi?id=70511 Priority: medium Bug ID: 70511 Assignee: nouveau at lists.freedesktop.org Summary: nouveau_bo_name_get segmentation fault while running root tutorials/gl/glbox.C QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

I am attempting to install Gentoo on my cdless machine using the thumbdrive as a boot device. The motherboard is an Intel D815EEA, and is the latest firmware revision (at least on the BIOS). I believe I have done everything right, but it tells me I have unknown keywords in my syslinux.cfg and corrupt kernel images. The steps I have followed are thus: 1) Starting with a 4GB flash device,

Not needed, already tracked by drm_crtc_state->active. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_drv.h | 1 - drivers/gpu/drm/virtio/virtgpu_display.c | 4 ---- drivers/gpu/drm/virtio/virtgpu_plane.c | 2 +- 3 files changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_drv.h

Return early for the no framebuffer (or disabled output) case. Results in a simpler code flow for the remaining cases. No functional change. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_plane.c | 62 ++++++++++++++------------ 1 file changed, 33 insertions(+), 29 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c

Return early for the no framebuffer (or disabled output) case. Results in a simpler code flow for the remaining cases. No functional change. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_plane.c | 62 ++++++++++++++------------ 1 file changed, 33 insertions(+), 29 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

Hello, I've started seeing the following warning in 3.11-rc2. [In the interest of full disclosure, I do have a patch applied that tries to implement drm_planes, which I might have done completely incorrectly, but looking around it doesn't seem related. I'm definitely not invoking any of the planes functionality right now. See http://paste.debian.net/hidden/cf8b3a2, plus a call to the

I took another pass at trying to install this, and failed again with video issues. I have Fedora 5 and a nvidia MX-440 video card (To the uninitiated that's the sort they give away in breakfast cereal boxes - quite old 4x agp w/64MB) This time, I ran as windows 2000, ran under winedbg to slow things slightly. So I uninstalled fedora's highly cooked current video drivers, installed a debug