headers
Frank Thieme | 7 Jan 2010 01:28

Intel GMA 4500HD and X11 not working

Hi!

I already tried on the tech-x11 mailing list, but got no answer. Maybe I get 
an answer or an hint here...

I tried NetBSD current (because I need the iwn capabilities for 5100) on my 
Lenovo SL300.

First try was just normal start of netbsd. Kernel detects vga and loads 
i915drm. When I start X screen gets black and never comes back. All I can do 
is restart the notebook.

NetBSD 5.99.22 (GENERIC) #0: Sun Dec 13 00:52:10 UTC 2009
	builds <at> b8.netbsd.org:/home/builds/ab/HEAD/amd64/200912130000Z-
obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/GENERIC
total memory = 4061 MB
avail memory = 3920 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
LENOVO                         273852G (ThinkPad SL300)
mainbus0 (root)
cpu0 at mainbus0 apid 0: Intel 686-class, 1795MHz, id 0x6fd
cpu1 at mainbus0 apid 1: Intel 686-class, 1795MHz, id 0x6fd
ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 20, 24 pins
acpi0 at mainbus0: Intel ACPICA 20090730
acpi0: X/RSDT: OemId <LENOVO,TP-6A   ,00000590>, AslId <MSFT,00000097>
acpiecdt0 at acpi0: ACPI Embedded Controller via ECDT
acpi0: SCI interrupting at int 9
acpi0: fixed-feature power button present
timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
(Continue reading)

Permalink | Reply | 8 comments |
headers
matthew green | 8 Jan 2010 11:49
Picon
Favicon

re: Intel GMA 4500HD and X11 not working


   /netbsd: error: [drm:pid14130:i915_set_status_page] *ERROR* can not ioremap 
   virtual address for G33 hw status page

please set "sysctl -w hw.dri.debug=1" and try again.  it should report
more information about why i915_set_status_page() fails.

this might be pretty long..

.mrg.
Permalink | Reply | 5 comments |
headers
Frank Thieme | 8 Jan 2010 15:20

Re: Intel GMA 4500HD and X11 not working

Hi!

On a side note I tried UXA and got

(WW) intel(0): UXA not built in, falling back to EXA.

So  how do I get UXA?

On Friday 08 January 2010 11:49:36 matthew green wrote:
>    /netbsd: error: [drm:pid14130:i915_set_status_page] *ERROR* can not
>  ioremap virtual address for G33 hw status page
> 
> please set "sysctl -w hw.dri.debug=1" and try again.  it should report
> more information about why i915_set_status_page() fails.

you find the log here: http://pastebin.ca/1742751

Bye...Frank
Permalink | Reply | 4 comments |
headers
Matthias Pfaller | 10 Jan 2010 12:57
Picon

Re: Intel GMA 4500HD and X11 not working

matthew green wrote:
>    
>    On Friday 08 January 2010 11:49:36 matthew green wrote:
>    >    /netbsd: error: [drm:pid14130:i915_set_status_page] *ERROR* can not
>    >  ioremap virtual address for G33 hw status page
>    > 
>    > please set "sysctl -w hw.dri.debug=1" and try again.  it should report
>    > more information about why i915_set_status_page() fails.
>    
>    you find the log here: http://pastebin.ca/1742751
> 
> OK, i had a look through this.
> 
> it is failing in bus_space_map().  apparently it is returning EAGAIN:
> 
> Jan  8 14:11:47 stars /netbsd: [drm:pid26120:drm_netbsd_ioremap]
[drm:pid26120:drm_netbsd_ioremap] ioremap: flags 2
> Jan  8 14:11:47 stars /netbsd: [drm:pid26120:drm_netbsd_ioremap]
[drm:pid26120:drm_netbsd_ioremap] ioremap: failed to map (35)
> Jan  8 14:11:47 stars /netbsd: error: [drm:pid26120:i915_set_status_page] *ERROR* can not ioremap
virtual address for G33 hw status page
> Jan  8 14:11:47 stars /netbsd: [drm:pid26120:drm_ioctl] [drm:pid26120:drm_ioctl]     returning 12
> 
> i'm not sure what could cause this.  i'll see what i can find.

I think this is xsrc/42262. spz and I have the same or a similar 
problem. Without drm the xserver works just fine (for me).

Matthias
(Continue reading)

Permalink | Reply | 2 comments |
headers
Frank Thieme | 10 Jan 2010 13:53

Re: Intel GMA 4500HD and X11 not working

On Sunday 10 January 2010 12:57:21 Matthias Pfaller wrote:
> I think this is xsrc/42262. spz and I have the same or a similar
> problem. Without drm the xserver works just fine (for me).

Does this patch solve the problem? I will try it then...

Setting 'Option "DRI" "false"' in the device section solves the problem for 
starting an X server. 

Sadly KDE4 tries to figure that out themself and leaves a black screen. You 
have to disable Desktop effects by calling "systemsettings" from a running X11 
session. 

Interestingly I get some strange graphics artefacts whenever a notification 
occurs then...

Bye...Frank
Permalink | Reply | 0 comments |
headers
Jukka Salmi | 10 Jan 2010 20:13
Picon

Re: mga(4) dual-head setup broken after update

Tobias Nygren --> tech-x11 (2009-11-23 16:00:16 +0100):
> On Wed, 18 Nov 2009 00:10:34 +0100
> Jukka Salmi <j+nbsd <at> 2009.salmi.ch> wrote:
> 
> > updating a NetBSD/i386 5.0_STABLE system with native Xorg (X server
> > 1.4.2 -> 1.6.3, mga driver 1.4.8 -> 1.4.11) broke the dual-head setup
> > I'm using with my Matrox G450 video card:
> > 
> > $ startx
> > [...]
> > (WW) MGA(0): Direct rendering disabled
> > (==) RandR enabled
> > (EE) MGA(1): Unable to map BAR 0.  Invalid argument (22)
> > 
> > Fatal server error:
> > AddScreen/ScreenInit failed for driver 1
> > [...]
> > 
> > (The full [1]log is available, as is the [2]log from before the update.)
> > 
> > Any hints about how to fix this?  Single-head works fine, BTW.
> 
> Probably delete your configuration, start over with a clean one and use
> xrandr(1) to configure the dual-head setup from your ~/.xsession.
> 
> This means you lose the ability to use your monitors as separate
> screens. For some reason they broke this with 1.5 server, it's
> not just an MGA issue.

Thanks for the hint.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Moneygram | 18 Jan 2010 11:27
Favicon

Restore your online account

Dear MoneyGram member,

We are sorry to inform you that your MoneyGram Online Account has 
been suspended. A high number of failed login attempts have been 
recorded on your online account. As a security measure we had to 
temporarily suspend your account.

To restore your account we have attached a form to this email. 
Please download the form and follow the instructions on your 
screen.

We apologize for any inconvenience this may have caused.
Sincerely, the MoneyGram security team.

© 2005 - 2010 MoneyGram. All rights reserved.
Attachment (restore_your_account.html): application/octet-stream, 2939 bytes
Permalink | Reply | 0 comments |
headers
Moneygram | 18 Jan 2010 15:00
Favicon

Restore your online account

Dear MoneyGram member,

We are sorry to inform you that your MoneyGram Online Account has 
been suspended. A high number of failed login attempts have been 
recorded on your online account. As a security measure we had to 
temporarily suspend your account.

To restore your account we have attached a form to this email. 
Please download the form and follow the instructions on your 
screen.

We apologize for any inconvenience this may have caused.
Sincerely, the MoneyGram security team.

© 2005 - 2010 MoneyGram. All rights reserved.
Attachment (restore_your_account.html): application/octet-stream, 2939 bytes
Permalink | Reply | 0 comments |
headers
Brad du Plessis | 21 Jan 2010 10:50
Picon

xf86-video-intel query

Hi,

I'm trying to get X working with the xf86-video-intel driver on my new 
Intel mini-ITX motherboard (Intel D410PT) on netbsd-5. What I've done so 
far involves fiddling in sys/dev/pci to get the kernel to recognise the 
IGD. See dmesg below.

xf86-video-vesa 2.3.0 works no problem. I then tried intel 2.9.1 which 
doesn't officially support the Pineview device and X started up but all 
I got was a blank screen. I can see from the monitor's own menu that it 
had correctly set the resolution and remotely via a telnet session I 
could query and alter the resolution with xrandr. Couldn't do anything 
to cure the blackness though.

At this point I assumed the intel driver to be the problem so I updated 
to intel 2.10.0 and now X wouldn't start at all. I assume the critical 
error was the one about "No kernel modesetting driver detected."

Any pointers as to how I can get this working would be great.

Thanks,
  Brad

See dmesg and Xorg.0.log when running Intel 2.10.0:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009
     The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Piotr | 21 Jan 2010 11:26
Picon

Re: xf86-video-intel query

Brad du Plessis <bradd <at> cat.co.za> writes:

> 
> Hi,
> 
> I'm trying to get X working with the xf86-video-intel driver on my new 
> Intel mini-ITX motherboard (Intel D410PT) on netbsd-5. What I've done so 
> far involves fiddling in sys/dev/pci to get the kernel to recognise the 
> IGD. See dmesg below.
> 
> xf86-video-vesa 2.3.0 works no problem. I then tried intel 2.9.1 which 
> doesn't officially support the Pineview device and X started up but all 
> I got was a blank screen. I can see from the monitor's own menu that it 
> had correctly set the resolution and remotely via a telnet session I 
> could query and alter the resolution with xrandr. Couldn't do anything 
> to cure the blackness though.
> 
> At this point I assumed the intel driver to be the problem so I updated 
> to intel 2.10.0 and now X wouldn't start at all. I assume the critical 
> error was the one about "No kernel modesetting driver detected."
> 
> Any pointers as to how I can get this working would be great.
> 
> Thanks,
>   Brad
> 

> 

Hi Brad,
(Continue reading)

Permalink | Reply | 3 comments |

Gmane