All of lore.kernel.org
 help / color / mirror / Atom feed
* Fwd: gma500: display displaced vertically by a few lines
       [not found] <CAOpc7mFCpg7bfkxVdK+aRaa5RVnvQYfbL3EHaXfgc-3ZpsCBeQ@mail.gmail.com>
@ 2013-05-13 10:03 ` Holger Schurig
  2013-05-13 10:40   ` Dave Airlie
  0 siblings, 1 reply; 12+ messages in thread
From: Holger Schurig @ 2013-05-13 10:03 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 7922 bytes --]

Hi List,

I've an device with an Intel GMA/Poulsbo chip, PCI ID 8080:8101.

Under (self-compiled) Linux 3.2.31 I've used psb_gfx, now with 3.8.10 I'm
using gma500_gfx.


But now the display under X11 (xserver-xorg-video-fbdev from Debian,
1:0.4.2-4+b2) shows the image moved some lines up on the newer kernel. I'd
guess that the first 4 to 6 lines are missing. I've run both kernels with
drm.debug=0x04, but haven't found something that looked suspicious. Or,
well, maybe not. The output of drm_mode_debug_printmodeline is a bit
different, 0x0 vs. 0xa.

/var/log/Xorg.0.log doesn't contain anything differiing at all that is
related to video output.

And hints on how I could pursue this issue?




3.2.31, "dmesg | grep drm":

Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda1 ro quiet
init=/bin/systemd video=LVDS-1:800x600 drm.debug=0x04
[drm] Initialized drm 1.1.0 20060810
[drm:drm_mode_debug_printmodeline], Modeline 0:"800x600" 0 39790 800 824
896 1056 600 601 603 628 0x8 0x0
[drm] SGX core id = 0x01130000
[drm] SGX core rev major = 0x01, minor = 0x02
[drm] SGX core rev maintenance = 0x01, designer = 0x00
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] No driver support for vblank timestamp query.
[drm:drm_fb_helper_parse_command_line], cmdline mode for connector LVDS-1
800x600@60Hz
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1]
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] probed
modes :
[drm:drm_mode_debug_printmodeline], Modeline 20:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_mode_debug_printmodeline], Modeline 28:"800x600" 72 50000 800 856
976 1040 600 637 643 666 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 27:"800x600" 75 49500 800 816
896 1056 600 601 604 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 21:"800x600" 60 40000 800 840
968 1056 600 601 605 628 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 22:"800x600" 56 36000 800 824
896 1024 600 601 603 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 24:"640x480" 73 31500 640 664
704 832 480 489 491 520 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 23:"640x480" 75 31500 640 656
720 840 480 481 484 500 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 25:"640x480" 60 25200 640 656
752 800 480 490 492 525 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 26:"720x400" 70 28320 720 738
846 900 400 412 414 449 0x40 0x6
[drm:drm_setup_crtcs],
[drm:drm_enable_connectors], connector 7 enabled? yes
[drm:drm_target_preferred], looking for cmdline mode on connector 7
[drm:drm_target_preferred], found mode 800x600
[drm:drm_setup_crtcs], picking CRTCs for 2048x2048 config
[drm:drm_setup_crtcs], desired mode 800x600 set on crtc 4
[drm:drm_crtc_helper_set_config],
[drm:drm_crtc_helper_set_config], [CRTC:3] [NOFB]
[drm:drm_crtc_helper_set_config],
[drm:drm_crtc_helper_set_config], [CRTC:4] [FB:11] #connectors=1 (x y) (0 0)
[drm:drm_crtc_helper_set_config], crtc has no fb, full mode set
[drm:drm_crtc_helper_set_config], modes are different, full mode set
[drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0
0x0
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_config], encoder changed, full mode switch
[drm:drm_crtc_helper_set_config], crtc changed, full mode switch
[drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] to [CRTC:4]
[drm:drm_crtc_helper_set_config], attempting to set mode from userspace
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_mode], [CRTC:4]
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_mode], [ENCODER:8:LVDS-8] set [MODE:10:800x600]
[drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
[drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] set DPMS on
drm: registered panic notifier
[drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0


3.8.10, "dmesg | grep drm":

Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda1 ro quiet
init=/bin/systemd video=LVDS-1:800x600 drm.debug=0x04
[drm] Initialized drm 1.1.0 20060810
[drm:psb_intel_init_bios], Using VBT from OpRegion: $VBT POULSBO        d
[drm:drm_mode_debug_printmodeline], Modeline 0:"800x600" 0 39790 800 824
896 1056 600 601 603 628 0x8 0xa
[drm:parse_sdvo_device_mapping], No SDVO device info is found in VBT
[drm:parse_edp], EDP timing in vbt t1_t3 32810 t8 162 t9 34014 t10 0
t11_t12 6144
[drm:parse_edp], VBT reports EDP: Lane_count 1, Lane_rate 6, Bpp 18
[drm:parse_edp], VBT reports EDP: VSwing  0, Preemph 0
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] No driver support for vblank timestamp query.
[drm:psb_intel_sdvo_read_byte], i2c transfer returned -6
[drm:psb_intel_sdvo_init], No SDVO device found on SDVOB
[drm:drm_fb_helper_parse_command_line], cmdline mode for connector LVDS-1
800x600@60Hz
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1]
[drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm
LVDSBLC_B
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] probed
modes :
[drm:drm_mode_debug_printmodeline], Modeline 20:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_mode_debug_printmodeline], Modeline 18:"800x600" 72 50000 800 856
976 1040 600 637 643 666 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 17:"800x600" 75 49500 800 816
896 1056 600 601 604 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 11:"800x600" 60 40000 800 840
968 1056 600 601 605 628 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 12:"800x600" 56 36000 800 824
896 1024 600 601 603 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 14:"640x480" 73 31500 640 664
704 832 480 489 491 520 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 13:"640x480" 75 31500 640 656
720 840 480 481 484 500 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 15:"640x480" 60 25200 640 656
752 800 480 490 492 525 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 16:"720x400" 70 28320 720 738
846 900 400 412 414 449 0x40 0x6
[drm:drm_setup_crtcs],
[drm:drm_enable_connectors], connector 7 enabled? yes
[drm:drm_target_preferred], looking for cmdline mode on connector 7
[drm:drm_target_preferred], found mode 800x600
[drm:drm_setup_crtcs], picking CRTCs for 2048x2048 config
[drm:drm_setup_crtcs], desired mode 800x600 set on crtc 4
[drm:drm_crtc_helper_set_config],
[drm:drm_crtc_helper_set_config], [CRTC:3] [NOFB]
[drm:drm_crtc_helper_set_config],
[drm:drm_crtc_helper_set_config], [CRTC:4] [FB:21] #connectors=1 (x y) (0 0)
[drm:drm_crtc_helper_set_config], crtc has no fb, full mode set
[drm:drm_crtc_helper_set_config], modes are different, full mode set
[drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0
0x0
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_config], encoder changed, full mode switch
[drm:drm_crtc_helper_set_config], crtc changed, full mode switch
[drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] to [CRTC:4]
[drm:drm_crtc_helper_set_config], attempting to set mode from userspace
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_mode], [CRTC:4]
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824
896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_mode], [ENCODER:8:LVDS-8] set [MODE:10:800x600]
[drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
[drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] set DPMS on
[drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0

[-- Attachment #1.2: Type: text/html, Size: 9835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 10:03 ` Fwd: gma500: display displaced vertically by a few lines Holger Schurig
@ 2013-05-13 10:40   ` Dave Airlie
  2013-05-13 13:02     ` Holger Schurig
  0 siblings, 1 reply; 12+ messages in thread
From: Dave Airlie @ 2013-05-13 10:40 UTC (permalink / raw)
  To: Holger Schurig; +Cc: dri-devel

>
> /var/log/Xorg.0.log doesn't contain anything differiing at all that is
> related to video output.
>
> And hints on how I could pursue this issue?

Try installing xf86-video-modesetting driver or whatever your distro calls it.

Dave.

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 10:40   ` Dave Airlie
@ 2013-05-13 13:02     ` Holger Schurig
  2013-05-13 14:47       ` Patrik Jakobsson
  2013-05-24 14:51       ` Anisse Astier
  0 siblings, 2 replies; 12+ messages in thread
From: Holger Schurig @ 2013-05-13 13:02 UTC (permalink / raw)
  Cc: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 2118 bytes --]

Thanks Dave, for the fast answer.

I had a new attack of a "BWAAAH, since 5 years graphics drivers for X11 on
Linux are a mess" moment. Things don't work out of the box, and if you try
google-fu, then you get ton's of ancient, outdated or only halfways true
information. Grrr.

That's not downplaying your work or knowledge at all, Dave. It's just an
outburst of a feeling!


I installed xserver-xorg-video-modesettings (from Debian Wheezy) and also
updated xserver-core, -evdev, -vesa and -fbdev. The I started X11. Seems
that Debian doesn't yet contain the addition of the modesettings driver to
the auto-probed drivers, Xorg.0.log didn't contain a trace of modesettings.

So I added

Section "Device"
        Identifier "gma"
        Driver     "modesetting"
BusID    "pci:0:2:0
EndSection

But then I get

[  4309.430] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  4309.430] (--) using VT number 1

[  4309.463] (WW) Falling back to old probe method for modesetting
[  4309.464] (II) UnloadModule: "modesetting"
[  4309.464] (EE) Screen(s) found, but none have a usable configuration.
[  4309.464]
Fatal server error:
[  4309.464] no screens found

So, I tried to add a screen, while grumbling "Since when do I need a
'Screen' section in a modern xorg.conf again?":

Section "Screen"
        Identifier      "800x600"
        Device "Card0"
        DefaultDepth    24
EndSection

But X11 still says

[  4440.511] (EE) Screen(s) found, but none have a usable configuration.
[  4440.511]
Fatal server error:
[  4440.511] no screens found

And of course, it's silent about WHAT exactly would constitute a usable
configuration.

I tried 32 bits depth as well. I tried adding a subsection "Display". I
tried to stay calm ...  but no success so far!   :-)


BTW, I upgraded to kernel 3.9.2 for this.


2013/5/13 Dave Airlie <airlied@gmail.com>

> >
> > /var/log/Xorg.0.log doesn't contain anything differiing at all that is
> > related to video output.
> >
> > And hints on how I could pursue this issue?
>
> Try installing xf86-video-modesetting driver or whatever your distro calls
> it.
>
> Dave.
>

[-- Attachment #1.2: Type: text/html, Size: 3516 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 13:02     ` Holger Schurig
@ 2013-05-13 14:47       ` Patrik Jakobsson
  2013-05-13 15:10         ` Holger Schurig
  2013-05-24 14:51       ` Anisse Astier
  1 sibling, 1 reply; 12+ messages in thread
From: Patrik Jakobsson @ 2013-05-13 14:47 UTC (permalink / raw)
  To: Holger Schurig; +Cc: dri-devel

On Mon, May 13, 2013 at 3:02 PM, Holger Schurig <holgerschurig@gmail.com> wrote:
> I installed xserver-xorg-video-modesettings (from Debian Wheezy) and also
> updated xserver-core, -evdev, -vesa and -fbdev. The I started X11. Seems
> that Debian doesn't yet contain the addition of the modesettings driver to
> the auto-probed drivers, Xorg.0.log didn't contain a trace of modesettings.
>
> So I added
>
> Section "Device"
>         Identifier "gma"
>         Driver     "modesetting"
> BusID    "pci:0:2:0
> EndSection
>
> But then I get
>
> [  4309.430] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [  4309.430] (--) using VT number 1
>
> [  4309.463] (WW) Falling back to old probe method for modesetting
> [  4309.464] (II) UnloadModule: "modesetting"
> [  4309.464] (EE) Screen(s) found, but none have a usable configuration.
> [  4309.464]
> Fatal server error:
> [  4309.464] no screens found
>
> So, I tried to add a screen, while grumbling "Since when do I need a
> 'Screen' section in a modern xorg.conf again?":
>
> Section "Screen"
>         Identifier      "800x600"
>         Device "Card0"
>         DefaultDepth    24
> EndSection
>
> But X11 still says
>
> [  4440.511] (EE) Screen(s) found, but none have a usable configuration.
> [  4440.511]
> Fatal server error:
> [  4440.511] no screens found
>
> And of course, it's silent about WHAT exactly would constitute a usable
> configuration.
>
> I tried 32 bits depth as well. I tried adding a subsection "Display". I
> tried to stay calm ...  but no success so far!   :-)
>
>
> BTW, I upgraded to kernel 3.9.2 for this.

Hi

Valid device id's for poulsbo are 8086:8108 and 8086:8109 so 8080:8101 is
something else.

You should be fine with just:

Section "Device"
	Identifier	"gma"
	Driver		"modesetting"
EndSection

So there is something else going on. Can we get a full dmesg on 3.9.2 with
drm.debug=0xf

Thanks
Patrik

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 14:47       ` Patrik Jakobsson
@ 2013-05-13 15:10         ` Holger Schurig
  2013-05-14 10:36           ` Holger Schurig
  0 siblings, 1 reply; 12+ messages in thread
From: Holger Schurig @ 2013-05-13 15:10 UTC (permalink / raw)
  To: Patrik Jakobsson; +Cc: dri-devel

[-- Attachment #1: Type: text/plain, Size: 2655 bytes --]

Oops, I did mistype. I have an 8086:8108:

# lspci --n  | head -n 2
00:00.0 Host bridge [0600]: Intel Corporation System Controller Hub
(SCH Poulsbo) [8086:8100] (rev 07)
00:02.0 VGA compatible controller [0300]: Intel Corporation System
Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07)

Somehow I think that this is a kernel regression, because for Kernel
3.2.31 I've used xorg-server-video-fbdev and psb_gfx, and there it
worked correctly.

Unfortunately my kernel has around 32 quilt patches added (e.g.
aufs3), so it's not easy for me to do a bi-section.

2013/5/13 Patrik Jakobsson <patrik.r.jakobsson@gmail.com>:
> On Mon, May 13, 2013 at 3:02 PM, Holger Schurig <holgerschurig@gmail.com> wrote:
>> I installed xserver-xorg-video-modesettings (from Debian Wheezy) and also
>> updated xserver-core, -evdev, -vesa and -fbdev. The I started X11. Seems
>> that Debian doesn't yet contain the addition of the modesettings driver to
>> the auto-probed drivers, Xorg.0.log didn't contain a trace of modesettings.
>>
>> So I added
>>
>> Section "Device"
>>         Identifier "gma"
>>         Driver     "modesetting"
>> BusID    "pci:0:2:0
>> EndSection
>>
>> But then I get
>>
>> [  4309.430] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
>> [  4309.430] (--) using VT number 1
>>
>> [  4309.463] (WW) Falling back to old probe method for modesetting
>> [  4309.464] (II) UnloadModule: "modesetting"
>> [  4309.464] (EE) Screen(s) found, but none have a usable configuration.
>> [  4309.464]
>> Fatal server error:
>> [  4309.464] no screens found
>>
>> So, I tried to add a screen, while grumbling "Since when do I need a
>> 'Screen' section in a modern xorg.conf again?":
>>
>> Section "Screen"
>>         Identifier      "800x600"
>>         Device "Card0"
>>         DefaultDepth    24
>> EndSection
>>
>> But X11 still says
>>
>> [  4440.511] (EE) Screen(s) found, but none have a usable configuration.
>> [  4440.511]
>> Fatal server error:
>> [  4440.511] no screens found
>>
>> And of course, it's silent about WHAT exactly would constitute a usable
>> configuration.
>>
>> I tried 32 bits depth as well. I tried adding a subsection "Display". I
>> tried to stay calm ...  but no success so far!   :-)
>>
>>
>> BTW, I upgraded to kernel 3.9.2 for this.
>
> Hi
>
> Valid device id's for poulsbo are 8086:8108 and 8086:8109 so 8080:8101 is
> something else.
>
> You should be fine with just:
>
> Section "Device"
>         Identifier      "gma"
>         Driver          "modesetting"
> EndSection
>
> So there is something else going on. Can we get a full dmesg on 3.9.2 with
> drm.debug=0xf
>
> Thanks
> Patrik

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 32464 bytes --]

Initializing cgroup subsys cpu
Linux version 3.9.2 (linux@me) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 13 16:59:08 CEST 2013
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
Disabled fast string operations
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000003f66ffff] usable
BIOS-e820: [mem 0x000000003f670000-0x000000003f67ffff] reserved
BIOS-e820: [mem 0x000000003f680000-0x000000003f68dfff] ACPI data
BIOS-e820: [mem 0x000000003f68e000-0x000000003f6c7fff] ACPI NVS
BIOS-e820: [mem 0x000000003f6c8000-0x000000003f7fffff] reserved
BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
NX (Execute Disable) protection: active
DMI not present or invalid.
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
e820: last_pfn = 0x3f670 max_arch_pfn = 0x1000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CFFFF write-protect
  D0000-DFFFF uncachable
  E0000-EFFFF write-through
  F0000-FFFFF write-protect
MTRR variable ranges enabled:
  0 base 000000000 mask 0C0000000 write-back
  1 base 03F700000 mask 0FFF00000 uncachable
  2 base 03F800000 mask 0FF800000 uncachable
  3 disabled
  4 disabled
  5 disabled
  6 disabled
  7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
original variable MTRRs
reg 0, base: 0GB, range: 1GB, type WB
reg 1, base: 1015MB, range: 1MB, type UC
reg 2, base: 1016MB, range: 8MB, type UC
total RAM covered: 1015M
Found optimal setting for mtrr clean up
 gran_size: 64K 	chunk_size: 16M 	num_reg: 3  	lose cover RAM: 0G
New variable MTRRs
reg 0, base: 0GB, range: 1GB, type WB
reg 1, base: 1015MB, range: 1MB, type UC
reg 2, base: 1016MB, range: 8MB, type UC
found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780]
initial memory mapped: [mem 0x00000000-0x019fffff]
Base memory trampoline at [c009b000] 9b000 size 16384
init_memory_mapping: [mem 0x00000000-0x000fffff]
 [mem 0x00000000-0x000fffff] page 4k
init_memory_mapping: [mem 0x37800000-0x379fffff]
 [mem 0x37800000-0x379fffff] page 2M
init_memory_mapping: [mem 0x34000000-0x377fffff]
 [mem 0x34000000-0x377fffff] page 2M
init_memory_mapping: [mem 0x00100000-0x33ffffff]
 [mem 0x00100000-0x001fffff] page 4k
 [mem 0x00200000-0x33ffffff] page 2M
init_memory_mapping: [mem 0x37a00000-0x37bfdfff]
 [mem 0x37a00000-0x37bfdfff] page 4k
BRK [0x01500000, 0x01500fff] PGTABLE
ACPI: RSDP 000f85f0 00024 (v02 ACPIAM)
ACPI: XSDT 3f680100 00064 (v01   MEIN Terminal 20090917 MSFT 00000097)
ACPI: FACP 3f680290 000F4 (v04 091709 FACP1631 20090917 MSFT 00000097)
ACPI: DSDT 3f6805c0 05E50 (v02  QMENR QMENR114 00000114 INTL 20051117)
ACPI: FACS 3f68e000 00040
ACPI: APIC 3f680390 00068 (v02 091709 APIC1631 20090917 MSFT 00000097)
ACPI: MCFG 3f680400 0003C (v01 091709 OEMMCFG  20090917 MSFT 00000097)
ACPI: SLIC 3f680440 00176 (v01   MEIN Terminal 20090917 MSFT 00000097)
ACPI: OEMB 3f68e040 0013C (v01 091709 OEMB1631 20090917 MSFT 00000097)
ACPI: HPET 3f686410 00038 (v01 091709 OEMHPET  20090917 MSFT 00000097)
ACPI: GSCI 3f68e180 02024 (v01 091709 GMCHSCI  20090917 MSFT 00000097)
ACPI: SSDT 3f690b70 004F0 (v01  PmRef    CpuPm 00003000 INTL 20051117)
ACPI: Local APIC address 0xfee00000
122MB HIGHMEM available.
891MB LOWMEM available.
  mapped low ram: 0 - 37bfe000
  low ram: 0 - 37bfe000
BRK [0x01501000, 0x01501fff] PGTABLE
Zone ranges:
  DMA      [mem 0x00001000-0x00ffffff]
  Normal   [mem 0x01000000-0x37bfdfff]
  HighMem  [mem 0x37bfe000-0x3f66ffff]
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x00001000-0x0009efff]
  node   0: [mem 0x00100000-0x3f66ffff]
On node 0 totalpages: 259598
free_area_init_node: node 0, pgdat c140a440, node_mem_map f740e020
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3998 pages, LIFO batch:0
  Normal zone: 1752 pages used for memmap
  Normal zone: 224254 pages, LIFO batch:31
  HighMem zone: 245 pages used for memmap
  HighMem zone: 31346 pages, LIFO batch:7
Using APIC driver default
ACPI: PM-Timer IO Port: 0x908
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
smpboot: Allowing 1 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 40
e820: [mem 0x3f800000-0xfedfffff] available for PCI devices
setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 13 pages/cpu @f73fb000 s30400 r0 d22848 u53248
pcpu-alloc: s30400 r0 d22848 u53248 alloc=13*4096
pcpu-alloc: [0] 0 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 257814
Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda1 ro quiet init=/bin/systemd drm.debug=0xf
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
__ex_table already sorted, skipping sort
Initializing CPU#0
Initializing HighMem for node 0 (00037bfe:0003f670)
Memory: 1024192k/1038784k available (2900k kernel code, 14200k reserved, 1272k data, 396k init, 125384k highmem)
virtual kernel memory layout:
    fixmap  : 0xfff67000 - 0xfffff000   ( 608 kB)
    pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
    vmalloc : 0xf83fe000 - 0xffbfe000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf7bfe000   ( 891 MB)
      .init : 0xc1414000 - 0xc1477000   ( 396 kB)
      .data : 0xc12d508c - 0xc14131c0   (1272 kB)
      .text : 0xc1000000 - 0xc12d508c   (2900 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
	RCU dyntick-idle grace-period acceleration is enabled.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
NR_IRQS:2304 nr_irqs:256 16
CPU 0 irqstacks, hard=f6c08000 soft=f6c0a000
Console: colour VGA+ 80x25
console [tty0] enabled
hpet clockevent registered
tsc: Fast TSC calibration using PIT
tsc: Detected 1097.251 MHz processor
Calibrating delay loop (skipped), value calculated using timer frequency.. 2194.50 BogoMIPS (lpj=4389004)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Disabled fast string operations
mce: CPU supports 5 MCE banks
CPU0: Thermal monitoring enabled (TM1)
Last level iTLB entries: 4KB 32, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 64, 2MB 0, 4MB 8
tlb_flushall_shift: 6
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20130117
ACPI: All ACPI Tables successfully acquired
Enabling APIC mode:  Flat.  Using 1 I/O APICs
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
smpboot: CPU0: Intel(R) Atom(TM) CPU Z510   @ 1.10GHz (fam: 06, model: 1c, stepping: 02)
Performance Events: PEBS fmt0+, LBR disabled due to erratumAtom events, Intel PMU driver.
... version:                3
... bit width:              40
... generic registers:      2
... value mask:             000000ffffffffff
... max period:             000000007fffffff
... fixed-purpose events:   3
... event mask:             0000000700000003
Brought up 1 CPUs
smpboot: Total of 1 processors activated (2194.50 BogoMIPS)
devtmpfs: initialized
NET: Registered protocol family 16
ACPI: bus type PCI registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: not using MMCONFIG
PCI : PCI BIOS area is rw and x. Use pci=nobios if you want it NX.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=2
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: Added _OSI(Module Device)
ACPI: Added _OSI(Processor Device)
ACPI: Added _OSI(3.0 _SCP Extensions)
ACPI: Added _OSI(Processor Aggregator Device)
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI BIOS Bug: Warning: Incorrect checksum in table [OEMB] - 0x03, should be 0x53 (20130117/tbutils-324)
ACPI: SSDT 3f690280 001FA (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT   (null) 001FA (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)
ACPI: SSDT 3f690510 0065D (v01  PmRef  Cpu0Cst 00003001 INTL 20051117)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT   (null) 0065D (v01  PmRef  Cpu0Cst 00003001 INTL 20051117)
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
PCI: Using MMCONFIG for extended config space
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
ACPI: Power Resource [FAN1] (on)
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [bus 00-ff]
pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
pci_bus 0000:00: root bus resource [mem 0x3f800000-0xdfffffff]
pci_bus 0000:00: root bus resource [mem 0xf0000000-0xffffffff]
pci 0000:00:00.0: [8086:8100] type 00 class 0x060000
pci 0000:00:02.0: [8086:8108] type 00 class 0x030000
pci 0000:00:02.0: reg 10: [mem 0xfe980000-0xfe9fffff]
pci 0000:00:02.0: reg 14: [io  0xd880-0xd887]
pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff]
pci 0000:00:02.0: reg 1c: [mem 0xfe940000-0xfe97ffff]
pci 0000:00:1b.0: [8086:811b] type 00 class 0x040300
pci 0000:00:1b.0: reg 10: [mem 0xfe938000-0xfe93bfff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot
pci 0000:00:1c.0: [8086:8110] type 01 class 0x060400
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: [8086:8112] type 01 class 0x060400
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.0: [8086:8114] type 00 class 0x0c0300
pci 0000:00:1d.0: reg 20: [io  0xd480-0xd49f]
pci 0000:00:1d.1: [8086:8115] type 00 class 0x0c0300
pci 0000:00:1d.1: reg 20: [io  0xd080-0xd09f]
pci 0000:00:1d.2: [8086:8116] type 00 class 0x0c0300
pci 0000:00:1d.2: reg 20: [io  0xc880-0xc89f]
pci 0000:00:1d.7: [8086:8117] type 00 class 0x0c0320
pci 0000:00:1d.7: reg 10: [mem 0xfe937c00-0xfe937fff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1f.0: [8086:8119] type 00 class 0x060100
pci 0000:00:1f.1: [8086:811a] type 00 class 0x010180
pci 0000:00:1f.1: reg 20: [io  0xffa0-0xffaf]
pci 0000:01:00.0: [168c:002a] type 00 class 0x028000
pci 0000:01:00.0: reg 10: [mem 0xfeaf0000-0xfeafffff 64bit]
pci 0000:01:00.0: supports D1
pci 0000:01:00.0: PME# supported from D0 D1 D3hot
pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device.  You can enable it with 'pcie_aspm=force'
pci 0000:00:1c.0: PCI bridge to [bus 01]
pci 0000:00:1c.0:   bridge window [mem 0xfea00000-0xfeafffff]
pci 0000:02:00.0: [10ec:8168] type 00 class 0x020000
pci 0000:02:00.0: reg 10: [io  0xef00-0xefff]
pci 0000:02:00.0: reg 18: [mem 0xfebff000-0xfebfffff 64bit]
pci 0000:02:00.0: reg 20: [mem 0xcfff0000-0xcfffffff 64bit pref]
pci 0000:02:00.0: reg 30: [mem 0xfebc0000-0xfebdffff pref]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:1c.1: PCI bridge to [bus 02]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xfeb00000-0xfebfffff]
pci 0000:00:1c.1:   bridge window [mem 0xcff00000-0xcfffffff pref]
pci_bus 0000:00: on NUMA node 0
acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08)
ACPI: PCI Interrupt Link [LNKA] (IRQs *10)
ACPI: PCI Interrupt Link [LNKB] (IRQs *11)
ACPI: Invalid _PRS IRQ 0
ACPI: PCI Interrupt Link [LNKC] (IRQs) *0, disabled.
ACPI: Invalid _PRS IRQ 0
ACPI: PCI Interrupt Link [LNKD] (IRQs) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs *5)
ACPI: PCI Interrupt Link [LNKF] (IRQs *15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 15) *6
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Enabled 3 GPEs in block 00 to 1F
acpi root: \_SB_.PCI0 notify handler is installed
Found 1 acpi root devices
vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
vgaarb: bridge control possible 0000:00:02.0
SCSI subsystem initialized
libata version 3.00 loaded.
ACPI: bus type USB registered
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Initialized.
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
e820: reserve RAM buffer [mem 0x3f670000-0x3fffffff]
HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Switching to clocksource hpet
pnp: PnP ACPI init
ACPI: bus type PNP registered
system 00:00: [mem 0x40000000-0x7fffffff] has been reserved
system 00:00: [mem 0x3f800000-0x3fffffff] has been reserved
system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:02: Plug and Play ACPI device, IDs PNP0800 (active)
pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
system 00:04: [io  0x04d0-0x04d1] has been reserved
system 00:04: [io  0x0900-0x09f3] has been reserved
system 00:04: [io  0x0400-0x043f] has been reserved
system 00:04: [io  0x0480-0x04bf] has been reserved
system 00:04: [mem 0xf0000000-0xf0003fff] has been reserved
system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
pnp 00:06: Plug and Play ACPI device, IDs INT0800 (active)
system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:08: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:08: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:09: [io  0x0a00-0x0a7f] has been reserved
system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:0b: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:0c: Plug and Play ACPI device, IDs PNP0400 (active)
system 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0e: [mem 0xe0000000-0xefffffff] has been reserved
system 00:0e: Plug and Play ACPI device, IDs PNP0c02 (active)
system 00:0f: [mem 0x00000000-0x0009ffff] could not be reserved
system 00:0f: [mem 0x000c0000-0x000cffff] could not be reserved
system 00:0f: [mem 0x000e0000-0x000fffff] could not be reserved
system 00:0f: [mem 0x00100000-0x3f7fffff] could not be reserved
system 00:0f: Plug and Play ACPI device, IDs PNP0c01 (active)
pnp: PnP ACPI: found 16 devices
ACPI: bus type PNP unregistered
pci 0000:00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 01] add_size 1000
pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff pref] to [bus 01] add_size 200000
pci 0000:00:1c.0: res[9]=[mem 0x00100000-0x000fffff pref] get_res_add_size add_size 200000
pci 0000:00:1c.0: res[7]=[io  0x1000-0x0fff] get_res_add_size add_size 1000
pci 0000:00:1c.0: BAR 9: assigned [mem 0x80000000-0x801fffff pref]
pci 0000:00:1c.0: BAR 7: assigned [io  0x1000-0x1fff]
pci 0000:00:1c.0: PCI bridge to [bus 01]
pci 0000:00:1c.0:   bridge window [io  0x1000-0x1fff]
pci 0000:00:1c.0:   bridge window [mem 0xfea00000-0xfeafffff]
pci 0000:00:1c.0:   bridge window [mem 0x80000000-0x801fffff pref]
pci 0000:00:1c.1: PCI bridge to [bus 02]
pci 0000:00:1c.1:   bridge window [io  0xe000-0xefff]
pci 0000:00:1c.1:   bridge window [mem 0xfeb00000-0xfebfffff]
pci 0000:00:1c.1:   bridge window [mem 0xcff00000-0xcfffffff pref]
pci 0000:00:1c.0: enabling device (0106 -> 0107)
pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
pci_bus 0000:00: resource 8 [mem 0x3f800000-0xdfffffff]
pci_bus 0000:00: resource 9 [mem 0xf0000000-0xffffffff]
pci_bus 0000:01: resource 0 [io  0x1000-0x1fff]
pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
pci_bus 0000:01: resource 2 [mem 0x80000000-0x801fffff pref]
pci_bus 0000:02: resource 0 [io  0xe000-0xefff]
pci_bus 0000:02: resource 1 [mem 0xfeb00000-0xfebfffff]
pci_bus 0000:02: resource 2 [mem 0xcff00000-0xcfffffff pref]
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
pci 0000:00:02.0: Boot video device
PCI: CLS 32 bytes, default 64
bounce pool size: 64 pages
aufs 3.9-20130506
msgmni has been set to 1755
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered (default)
intel_idle: MWAIT substates: 0x3020220
intel_idle: v0.4 model 0x1C
intel_idle: lapic_timer_reliable_states 0x2
tsc: Marking TSC unstable due to TSC halts in idle states deeper than C2
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
ACPI: Sleep Button [SLPB]
ACPI: Requesting acpi_cpufreq
thermal LNXTHERM:00: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (55 C)
Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Linux agpgart interface v0.103
loop: module loaded
pata_sch 0000:00:1f.1: version 0.2
pata_sch 0000:00:1f.1: setting latency timer to 64
scsi0 : pata_sch
scsi1 : pata_sch
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:02:00.0: irq 40 for MSI/MSI-X
r8169 0000:02:00.0 eth0: RTL8168c/8111c at 0xf8414000, 00:13:95:08:e4:20, XID 1c2000c0 IRQ 40
r8169 0000:02:00.0 eth0: jumbo features [frames: 6128 bytes, tx checksumming: ko]
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-pci 0000:00:1d.7: setting latency timer to 64
ehci-pci 0000:00:1d.7: EHCI Host Controller
ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci-pci 0000:00:1d.7: debug port 1
ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
ehci-pci 0000:00:1d.7: irq 23, io mem 0xfe937c00
ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 3.9.2 ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 20, io base 0x0000d480
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: UHCI Host Controller
usb usb2: Manufacturer: Linux 3.9.2 uhci_hcd
usb usb2: SerialNumber: 0000:00:1d.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 21, io base 0x0000d080
usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: UHCI Host Controller
usb usb3: Manufacturer: Linux 3.9.2 uhci_hcd
usb usb3: SerialNumber: 0000:00:1d.1
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 22, io base 0x0000c880
usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: UHCI Host Controller
usb usb4: Manufacturer: Linux 3.9.2 uhci_hcd
usb usb4: SerialNumber: 0000:00:1d.2
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i8042: PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: PC Speaker as /devices/platform/pcspkr/input/input2
rtc_cmos 00:01: RTC can wake from S4
rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Netfilter messages via NETLINK v0.30.
TCP: westwood registered
NET: Registered protocol family 17
Using IPI Shortcut mode
ALSA device list:
  No soundcards found.
ata1.00: ATA-7: SFCA4096H1BR4TO-I-MS-226-STD, 20100806, max UDMA/133
ata1.00: 7793856 sectors, multi 0: LBA 
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access     ATA      SFCA4096H1BR4TO- 2010 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 7793856 512-byte logical blocks: (3.99 GB/3.71 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda1): recovery required on readonly filesystem
EXT3-fs (sda1): write access will be enabled during recovery
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
devtmpfs: mounted
Freeing unused kernel memory: 396k freed
Write protecting the kernel text: 2904k
Write protecting the kernel read-only data: 1016k
NX-protecting the kernel data: 3240k
systemd[1]: systemd 189 running in system mode. (-PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT -LIBCRYPTSETUP -GCRYPT -ACL +XZ; debian)
systemd[1]: [/lib/systemd/system/scannerd.service:3] Unknown lvalue 'Requist' in section 'Unit'. Ignoring.
systemd-udevd[44]: starting version 189
systemd-journald[45]: Fixed max_use=50.0M max_size=6.2M min_size=64.0K keep_free=25.0M
systemd-journald[45]: Reserving 11384 entries in hash table.
systemd-journald[45]: Vacuuming...
systemd-journald[45]: Flushing /dev/kmsg...
usb 2-2: new low-speed USB device number 2 using uhci_hcd
EXT3-fs (sda1): using internal journal
usb 2-2: New USB device found, idVendor=413c, idProduct=2107
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: Dell USB Entry Keyboard
usb 2-2: Manufacturer: DELL
input: DELL Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input3
hid-generic 0003:413C:2107.0001: input: USB HID v1.10 Keyboard [DELL Dell USB Entry Keyboard] on usb-0000:00:1d.0-2/input0
usb 4-2: new full-speed USB device number 2 using uhci_hcd
usb 4-2: New USB device found, idVendor=1a02, idProduct=bad6
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-2: Product: Environment Controller
input: Environment Controller as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/input/input4
hid-generic 0003:1A02:BAD6.0002: input: USB HID v1.11 Keyboard [Environment Controller] on usb-0000:00:1d.2-2/input0
systemd-journald[45]: systemd-journald running as pid 45
systemd-journald[45]: Received SIGUSR1
[drm] Initialized drm 1.1.0 20060810
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
[drm:drm_pci_init], 
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[drm:drm_get_pci_dev], 
[drm:drm_get_minor], 
[drm:drm_get_minor], new minor assigned 64
[drm:drm_get_minor], 
[drm:drm_get_minor], new minor assigned 0
gma500 0000:00:02.0: setting latency timer to 64
[drm:psb_intel_opregion_setup], OpRegion detected at 0x3f68e1a4
[drm:psb_intel_opregion_setup], Public ACPI methods supported
[drm:psb_intel_opregion_setup], ASLE supported
[drm:psb_intel_init_bios], Using VBT from OpRegion: $VBT POULSBO        d
[drm:drm_mode_debug_printmodeline], Modeline 0:"800x600" 0 39790 800 824 896 1056 600 601 603 628 0x8 0xa
[drm:parse_sdvo_device_mapping], No SDVO device info is found in VBT
[drm:parse_edp], EDP timing in vbt t1_t3 32810 t8 162 t9 34014 t10 0 t11_t12 6144
[drm:parse_edp], VBT reports EDP: Lane_count 1, Lane_rate 6, Bpp 18
[drm:parse_edp], VBT reports EDP: VSwing  0, Preemph 0
[Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
acpi device:03: registered as cooling_device1
acpi device:04: registered as cooling_device2
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] No driver support for vblank timestamp query.
[drm:drm_irq_install], irq=16
[drm:drm_sysfs_connector_add], adding "LVDS-1" to sysfs
[drm:drm_sysfs_hotplug_event], generating hotplug event
[drm:psb_intel_sdvo_read_byte], i2c transfer returned -6
[drm:psb_intel_sdvo_init], No SDVO device found on SDVOB
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1]
[drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter intel drm LVDSBLC_B
[drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] probed modes :
[drm:drm_mode_debug_printmodeline], Modeline 20:"800x600" 60 39790 800 824 896 1056 600 601 603 628 0x48 0xa
[drm:drm_mode_debug_printmodeline], Modeline 18:"800x600" 72 50000 800 856 976 1040 600 637 643 666 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 17:"800x600" 75 49500 800 816 896 1056 600 601 604 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 11:"800x600" 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 12:"800x600" 56 36000 800 824 896 1024 600 601 603 625 0x40 0x5
[drm:drm_mode_debug_printmodeline], Modeline 14:"640x480" 73 31500 640 664 704 832 480 489 491 520 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 13:"640x480" 75 31500 640 656 720 840 480 481 484 500 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 15:"640x480" 60 25200 640 656 752 800 480 490 492 525 0x40 0xa
[drm:drm_mode_debug_printmodeline], Modeline 16:"720x400" 70 28320 720 738 846 900 400 412 414 449 0x40 0x6
[drm:drm_setup_crtcs], 
[drm:drm_enable_connectors], connector 7 enabled? yes
[drm:drm_target_preferred], looking for cmdline mode on connector 7
[drm:drm_target_preferred], looking for preferred mode on connector 7
[drm:drm_target_preferred], found mode 800x600
[drm:drm_setup_crtcs], picking CRTCs for 2048x2048 config
[drm:drm_setup_crtcs], desired mode 800x600 set on crtc 4
[drm:drm_framebuffer_reference], FB ID: 21
fbcon: psbfb (fb0) is primary device
[drm:drm_crtc_helper_set_config], 
[drm:drm_crtc_helper_set_config], [CRTC:3] [NOFB]
[drm:drm_crtc_helper_set_config], 
[drm:drm_crtc_helper_set_config], [CRTC:4] [FB:21] #connectors=1 (x y) (0 0)
[drm:drm_crtc_helper_set_config], crtc has no fb, full mode set
[drm:drm_crtc_helper_set_config], modes are different, full mode set
[drm:drm_mode_debug_printmodeline], Modeline 0:"" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824 896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_config], encoder changed, full mode switch
[drm:drm_crtc_helper_set_config], crtc changed, full mode switch
[drm:drm_crtc_helper_set_config], [CONNECTOR:7:LVDS-1] to [CRTC:4]
[drm:drm_crtc_helper_set_config], attempting to set mode from userspace
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824 896 1056 600 601 603 628 0x48 0xa
ath: EEPROM regdomain: 0x37
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: AW
ath: Regpair used: 0x37
[drm:drm_crtc_helper_set_mode], [CRTC:4]
[drm:drm_mode_debug_printmodeline], Modeline 10:"800x600" 60 39790 800 824 896 1056 600 601 603 628 0x48 0xa
[drm:drm_crtc_helper_set_mode], [ENCODER:8:LVDS-8] set [MODE:10:800x600]
[drm:drm_calc_timestamping_constants], crtc 4: hwmode: htotal 1056, vtotal 628, vdisplay 600
[drm:drm_calc_timestamping_constants], crtc 4: clock 39790 kHz framedur 16666700 linedur 26539, pixeldur 25
[drm:drm_crtc_helper_set_config], Setting connector DPMS state to on
[drm:drm_crtc_helper_set_config], 	[CONNECTOR:7:LVDS-1] set DPMS on
[drm:drm_framebuffer_reference], FB ID: 21
r8169 0000:02:00.0 eth0: link down
r8169 0000:02:00.0 eth0: link down
Console: switching to colour frame buffer device 100x37
gma500 0000:00:02.0: fb0: psbfb frame buffer device
gma500 0000:00:02.0: registered panic notifier
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
[drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
cdc_acm 4-2:1.1: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[drm:asle_set_backlight], asle set backlight 800000ff
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
[drm:asle_set_backlight], asle set backlight 800000ff
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
cfg80211: Calling CRDA for country: AW
cfg80211: Regulatory domain changed to country: AW
cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211:   (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xf8560000, irq=16
[drm:asle_set_backlight], asle set backlight 800000ff
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
[drm:asle_set_backlight], asle set backlight 800000ff
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
r8169 0000:02:00.0 eth0: link up
wlan0: authenticate with 74:31:70:4b:92:2e
wlan0: send auth to 74:31:70:4b:92:2e (try 1/3)
wlan0: authenticated
wlan0: associate with 74:31:70:4b:92:2e (try 1/3)
wlan0: RX AssocResp from 74:31:70:4b:92:2e (capab=0x411 status=0 aid=2)
wlan0: associated

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 15:10         ` Holger Schurig
@ 2013-05-14 10:36           ` Holger Schurig
  2013-05-14 12:13             ` Holger Schurig
  0 siblings, 1 reply; 12+ messages in thread
From: Holger Schurig @ 2013-05-14 10:36 UTC (permalink / raw)
  To: Patrik Jakobsson; +Cc: dri-devel

Okay, I've can now circle the problem out. What did I do:

* I used vanilla-3.9.2 kernel, but brougth drivers/gpu/drm/gma500 to
the state of Linus' git tree commit id
0cdbee3e811b1bbb347c61814c8570658f2ab15c. This was shortly after
gma500 moved out of staging
* then I did "git format-patch
0cdbee3e811b1bbb347c61814c8570658f2ab15c..master
drivers/gpu/drm/gma500/"
* I then took the following patches to get this antique gma500 driver
compile against kernel 3.9.2 with it's updated DRM:
** psb/0001-drm-gma500-fix-compile-error.patch
** psb/0002-drm-move-the-fb-bpp-depth-helper-into-the-core.patch
** psb/0020-drm-Replace-pitch-with-pitches-in-drm_framebuffer.patch
** psb/0095-gma500-remove-the-second-argument-of-k-un-map_atomic.patch
** psb/0151-drm-Make-the-.mode_fixup-operations-mode-argument-a-.patch
(modified)
** psb/0152-drm-kill-reclaim_buffers-callback.patch
** psb/0175-mm-kill-vma-flag-VM_RESERVED-and-mm-reserved_vm-coun.patch
** psb/0178-drm-gma500-drm_connector_property-drm_object_propert.patch
(modified)

Now this franken-gma500_gfx driver runs perfectly with
xserver-xorg-video-fbdev and doesn't have the displaced vertical
screen issue.

Now I can roll in other patches until I find the culprit.

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-14 10:36           ` Holger Schurig
@ 2013-05-14 12:13             ` Holger Schurig
  2013-05-14 12:50               ` Patrik Jakobsson
  0 siblings, 1 reply; 12+ messages in thread
From: Holger Schurig @ 2013-05-14 12:13 UTC (permalink / raw)
  To: Patrik Jakobsson; +Cc: dri-devel

Okay, I found the patch that produces my regression:

----------------------------------------------------------------------------
>From bc794829141f28e14fe7d0e07e35870bd9aee78c Mon Sep 17 00:00:00 2001
From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Date: Mon, 21 May 2012 15:27:30 +0100
Subject: [PATCH 143/209] gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.
----------------------------------------------------------------------------

When I modify the patch that psb_chip_ops.cursor_needs_phys doesn't
get initialized to 1, then the display doesn't get displaced.

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-14 12:13             ` Holger Schurig
@ 2013-05-14 12:50               ` Patrik Jakobsson
  2013-05-14 13:07                 ` Holger Schurig
  0 siblings, 1 reply; 12+ messages in thread
From: Patrik Jakobsson @ 2013-05-14 12:50 UTC (permalink / raw)
  To: Holger Schurig; +Cc: dri-devel

On Tue, May 14, 2013 at 2:13 PM, Holger Schurig <holgerschurig@gmail.com> wrote:
> Okay, I found the patch that produces my regression:
>
> ----------------------------------------------------------------------------
> From bc794829141f28e14fe7d0e07e35870bd9aee78c Mon Sep 17 00:00:00 2001
> From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
> Date: Mon, 21 May 2012 15:27:30 +0100
> Subject: [PATCH 143/209] gma500: handle poulsbo cursor restriction
>
> Poulsbo needs a physical address in the cursor base register. We allocate a
> stolen memory buffer and copy the cursor image provided by userspace into it.
> When/If we get our own userspace driver we can map this stolen memory directly.
> The patch also adds a mark in chip ops so we can identify devices that has this
> requirement.
> ----------------------------------------------------------------------------
>
> When I modify the patch that psb_chip_ops.cursor_needs_phys doesn't
> get initialized to 1, then the display doesn't get displaced.

Hmm, I would have guessed on the gtt rolling code, but this makes sense.

If we need phys cursor, we allocate a cursor bo in stolen memory and this
happens before the framebuffer is allocated, thus moving the framebuffer 4
pages. Since the gtt rolling code tries to put a pitch of 1 page so it can
perform it's trick we loose 4 lines at the top. The actual problem is in
psbfb_vm_fault() where we assume the framebuffer to be at the start of stolen
memory. The following patch should fix your problem, though I recommend you use
the modesetting driver because you get a hardware accelerated cursor.

Thanks
Patrik

>From 1d68e97f39cb70862f7b02bb430e64dfa07fd08d Mon Sep 17 00:00:00 2001
From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Date: Tue, 14 May 2013 14:37:10 +0200
Subject: [PATCH] drm/gma500: Add fb gtt offset to fb base

Old code assumed framebuffer starts at base of stolen memory. Since the
addition of hardware cursors, this might not be true anymore so add the
gtt offset to the calculation.

Reported-by: Holger Schurig <holgerschurig@gmail.com>
Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
---
 drivers/gpu/drm/gma500/framebuffer.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/gma500/framebuffer.c
b/drivers/gpu/drm/gma500/framebuffer.c
index 1534e22..8b1b6d9 100644
--- a/drivers/gpu/drm/gma500/framebuffer.c
+++ b/drivers/gpu/drm/gma500/framebuffer.c
@@ -121,8 +121,8 @@ static int psbfb_vm_fault(struct vm_area_struct
*vma, struct vm_fault *vmf)
 	unsigned long address;
 	int ret;
 	unsigned long pfn;
-	/* FIXME: assumes fb at stolen base which may not be true */
-	unsigned long phys_addr = (unsigned long)dev_priv->stolen_base;
+	unsigned long phys_addr = (unsigned long)dev_priv->stolen_base +
+				  psbfb->gtt->offset;

 	page_num = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
 	address = (unsigned long)vmf->virtual_address - (vmf->pgoff << PAGE_SHIFT);
-- 
1.8.1.2

^ permalink raw reply related	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-14 12:50               ` Patrik Jakobsson
@ 2013-05-14 13:07                 ` Holger Schurig
  2013-05-14 13:19                   ` Patrik Jakobsson
  0 siblings, 1 reply; 12+ messages in thread
From: Holger Schurig @ 2013-05-14 13:07 UTC (permalink / raw)
  To: Patrik Jakobsson; +Cc: dri-devel

Patrick, have a

Tested-by: Holger Schurig <holgerschurig@gmail.com>

for this.




As for your suggestion:

> though I recommend you use the modesetting driver because you get
> a hardware accelerated cursor.

The current Debian Wheezy xserver-xorg doesn't autoload the
modesettings X11 driver. And I haven't found out how to manually load
that driver ...   also, there is about zilch documentation on that
driver available, also the error messages in the Xorg.0.log don't help
in any way. So, all in all this is too much hassle.

So I'll wait until support for that comes in up Debian SID a.k.a.
Unstable. I actually don't care about an "accelerated cursor" at all.
I don't perceive the mouse cursor (or the text cursor in rxvt-unicode)
to be "slow", so there's not much reason (for me!) in accellerating it
in the first place.

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-14 13:07                 ` Holger Schurig
@ 2013-05-14 13:19                   ` Patrik Jakobsson
  0 siblings, 0 replies; 12+ messages in thread
From: Patrik Jakobsson @ 2013-05-14 13:19 UTC (permalink / raw)
  To: Holger Schurig; +Cc: dri-devel

On Tue, May 14, 2013 at 3:07 PM, Holger Schurig <holgerschurig@gmail.com> wrote:
> Patrick, have a
>
> Tested-by: Holger Schurig <holgerschurig@gmail.com>
>
> for this.

I'll add that.

> As for your suggestion:
>
>> though I recommend you use the modesetting driver because you get
>> a hardware accelerated cursor.
>
> The current Debian Wheezy xserver-xorg doesn't autoload the
> modesettings X11 driver. And I haven't found out how to manually load
> that driver ...   also, there is about zilch documentation on that
> driver available, also the error messages in the Xorg.0.log don't help
> in any way. So, all in all this is too much hassle.

That still confuses me, but let's hope it automagically goes away some day.

> So I'll wait until support for that comes in up Debian SID a.k.a.
> Unstable. I actually don't care about an "accelerated cursor" at all.
> I don't perceive the mouse cursor (or the text cursor in rxvt-unicode)
> to be "slow", so there's not much reason (for me!) in accellerating it
> in the first place.

Sure, you'll only see a difference if you're running a compositing window
manager or your system is under heavy load.

-Patrik

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-13 13:02     ` Holger Schurig
  2013-05-13 14:47       ` Patrik Jakobsson
@ 2013-05-24 14:51       ` Anisse Astier
  2013-05-24 15:01         ` Holger Schurig
  1 sibling, 1 reply; 12+ messages in thread
From: Anisse Astier @ 2013-05-24 14:51 UTC (permalink / raw)
  To: Holger Schurig; +Cc: dri-devel

On Mon, 13 May 2013 15:02:46 +0200, Holger Schurig <holgerschurig@gmail.com> wrote :

> Thanks Dave, for the fast answer.
> 
> I had a new attack of a "BWAAAH, since 5 years graphics drivers for X11 on
> Linux are a mess" moment. Things don't work out of the box, and if you try
> google-fu, then you get ton's of ancient, outdated or only halfways true
> information. Grrr.
> 
> That's not downplaying your work or knowledge at all, Dave. It's just an
> outburst of a feeling!
> 
> 
> I installed xserver-xorg-video-modesettings (from Debian Wheezy) and also

The wheezy driver is too old, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683526

So no wonder it doesn't work. You can try applying the patches manually
or just compiling a more recent version of xf86-video-modesetting. Make
yourself known on this debian bug if it fixes it for you.

Regards,

Anisse

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: gma500: display displaced vertically by a few lines
  2013-05-24 14:51       ` Anisse Astier
@ 2013-05-24 15:01         ` Holger Schurig
  0 siblings, 0 replies; 12+ messages in thread
From: Holger Schurig @ 2013-05-24 15:01 UTC (permalink / raw)
  To: Anisse Astier; +Cc: dri-devel

Thanks, Anisse, but Dave's answer was wrong anyway. Using a different
user-space-driver wouldn't have magically fixed the bug in the kernel
KMS driver part.

Eventually something newer will pop up in Debian SID and/or Debian
Backports. I'll then pick it. As the performance of the device doesn't
bother me, I see no need. The more I stay at what Debian provides, the
less I have to maintain by myself :-)

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2013-05-24 15:01 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAOpc7mFCpg7bfkxVdK+aRaa5RVnvQYfbL3EHaXfgc-3ZpsCBeQ@mail.gmail.com>
2013-05-13 10:03 ` Fwd: gma500: display displaced vertically by a few lines Holger Schurig
2013-05-13 10:40   ` Dave Airlie
2013-05-13 13:02     ` Holger Schurig
2013-05-13 14:47       ` Patrik Jakobsson
2013-05-13 15:10         ` Holger Schurig
2013-05-14 10:36           ` Holger Schurig
2013-05-14 12:13             ` Holger Schurig
2013-05-14 12:50               ` Patrik Jakobsson
2013-05-14 13:07                 ` Holger Schurig
2013-05-14 13:19                   ` Patrik Jakobsson
2013-05-24 14:51       ` Anisse Astier
2013-05-24 15:01         ` Holger Schurig

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.