[ANNOUNCE] xf86-video-intel 2.7.0

Sun Apr 26 09:30:30 PDT 2009

Florian Mickler schrieb:
> On Sun, 26 Apr 2009 14:32:09 +0200
> Klaus Dittrich <kladit at arcor.de> wrote:
>
>   
>> Jin, Gordon schrieb:
>>     
>>> Klaus Dittrich wrote on Friday, April 24, 2009 2:50 AM:
>>>   
>>>       
>>>> After installing this driver a switch to a vt-terminal (ctrl-alt F2
>>>> for example) does not work.
>>>> No vt-termial / login was available any more nor a return
>>>> (ctrl-alt F7) to a graphical desktop.
>>>> I had to use ssh from of another machine to recover of this
>>>> situation. The last driver not showing this behavior is
>>>> xf86-video-intel-2.6.99.902, any later (newer) version
>>>> failed.
>>>> After installing xf86-video-intel-2.6.99.902 and restarting X
>>>> switching to vt-termials
>>>> works without rebooting.
>>>> Xserver was xorg-server-1.6.1, kernel 2.6.30-rc3 64bit.
>>>>     
>>>>         
>>> Are you using EXA or UXA? Could you check log to make sure DRI
>>> enabled?
>>>
>>> Gordon
>>>       
>> DRI was enabled, no accelaration choosen by xorg.conf, swrast got
>> called.
>>
>> Meanwhile I got xf86-video-intel-2.7.0 and kernel 2.6.30-rc3 to work
>> as expected
>> regarding graphics, switching to a vt still works only half.
>>
>> ctrl-alt-F2 changes the background color of some parts of the screen
>> but the graphical contents stayed, I could not see a black screen and
>> a login prompt.
>> But I was able to login blind and to recover to the graphics screen
>> by ctrl-alt-F7.
>>
>> Another point: I use startx and later on stopping X by ctrl-alt-bs 
>> results in a monitor
>> signaling me that there is no video-signal and no video-signal
>> reappeared when I tried switching to a vt. So without the second
>> machine and a running sshd
>> I would have been forced to reebot.
>>
>>
>> xorg.conf
>>
>> Section "Device"
>>
>>     Identifier  
>> "Intel-4-Series-Chipset-Integrated-Graphics-Controller-rev03"
>>
>>     Driver      "intel"
>>     BusID       "PCI:0:2:0"
>>
>>     Option      "DRI"           "true"
>>     Option       "Tiling"        "No"
>>
>>     Option      "AccelMethod"      "UXA"
>>
>> EndSection
>>
>> UXA, DRI2 works, glxinfo showed about 1500 fps, no tearing when
>> moving windows with content,
>> all very fast for my feeling.
>>
>>
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is 8, (OK)
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is 8, (OK)
>> drmOpenByBusid: Searching for BusID pci:0000:00:02.0
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is 8, (OK)
>> drmOpenByBusid: drmOpenMinor returns 8
>> drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
>> (II) [drm] DRM interface version 1.3
>> (II) [drm] DRM open master succeeded.
>> (II) intel(0): Output VGA1 using monitor section LG
>> (II) intel(0): Output DVI1 has no monitor section
>> (II) intel(0): Output DVI2 has no monitor section
>> (II) intel(0): Output VGA1 connected
>> (II) intel(0): Output DVI1 disconnected
>> (II) intel(0): Output DVI2 connected
>> (II) intel(0): Using user preference for initial modes
>> (II) intel(0): Output VGA1 using initial mode 1280x1024
>> (II) intel(0): Output DVI2 using initial mode 1280x1024
>> (==) intel(0): video overlay key set to 0x101fe        
>>
>> Only one monitor is connected via a dvi-cable.
>> The log shows two, is that correct or may it be the vt appears at a
>> not connected display?
>>
>>
>> (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  
>> 1024 1025 1028 1066 +hsync +vsync (64
>> .0 kHz)
>> (II) AIGLX: Suspending AIGLX clients for VT switch
>> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
>> directory) (II) No APM support in BIOS or kernel
>> (II) AIGLX: Resuming AIGLX clients after VT switch
>> (II) intel(0): Fixed memory allocation layout:
>> (II) intel(0): 0x00000000-0xffffffffffffffff: DRI memory manager (0
>> kB) (II) intel(0): 0x00000000:            end of aperture
>> (II) intel(0): BO memory allocation layout:
>> (II) intel(0): 0x00000000:            start of memory manager
>> (II) intel(0): 0x02530000-0x02a2ffff: front buffer (5120 kB)
>> (II) intel(0): 0x02520000-0x02529fff: HW cursors (40 kB)
>> (II) intel(0): 0x00000000:            end of memory manager
>> (II) Mouse0: ps2EnableDataReporting: succeeded
>>
>>
>>     
> Assuming you are using kernel-mode-setting:
> Do you have CONFIG_FB=y in your kernel .config?
> Without FB-Console, there is nothing to switch to, as
> kernel-mode-setting dosn't use text-mode anymore .
>
> Sincerely,
> Flo
>   
Good point, I did not know that. FB was on. Looking at the config variables
I detected I had had set FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.

After switching it off I could switch from graphical desktop to a VT,
I could switch between VT's but now not back to the graphics desktop by 
ctrl-alt-F7.
Black screen.

The only graphics device available is the G45 chip.

Here my settings regarding FB.

CONFIG_FB=y
CONFIG_FB_DDC=m
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_VESA=y
CONFIG_FB_INTEL=m
CONFIG_FB_INTEL_DEBUG=y
CONFIG_FB_INTEL_I2C=y

-- 
Klaus