Re: X: set resolution in Squeeze on a Macbook
Sven Joachim <svenjoac@gmx.de> writes:
>>> The Intel driver in Squeeze requires Kernel Modesetting (KMS)¹, if X
>>> uses the Vesa driver instead that means KMS is not active, for whatever
>>> reason. What are the contents of /proc/fb (if any) and the output of
>>> "/sbin/lsmod | grep i915" ?
>>
>> /proc/fb exists, but is empty.
>
> Just to make sure: you did "cat /proc/fb" and got no output, rather than
> "ls /proc/fb" and seeing a file with size 0, right?
Right.
>> $ lsmod | grep i915
>> i915 222254 0
>> drm_kms_helper 18309 1 i915
>> drm 112088 2 i915,drm_kms_helper
>> i2c_algo_bit 3497 1 i915
>> i2c_core 12696 5 i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit
>> button 3598 1 i915
>> video 14605 1 i915
>
> So i915 is loaded, but does apparently not work.
I see.
>> So it looks like I am using KMS (right?).
>
> No, you're not, otherwise the vesa driver would refuse to load. What
> does "dmesg | grep -E '(drm|i915)'" print?
$ dmesg | grep -E '(drm|i915)'
[ 6.317650] [drm] Initialized drm 1.1.0 20060810
[ 6.513284] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6.513358] i915 0000:00:02.0: setting latency timer to 64
[ 6.520225] [drm] set up 15M of stolen space
[ 6.951910] [drm] initialized overlay support
[ 6.952284] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
[ 7.950092] fb0: inteldrmfb frame buffer device
[ 7.950103] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 2232.604944] i915 0000:00:02.0: PCI INT A disabled
[ 2233.212105] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[ 2233.212114] i915 0000:00:02.0: restoring config space at offset 0x7 (was 0x0, writing 0x50400000)
[ 2233.212118] i915 0000:00:02.0: restoring config space at offset 0x6 (was 0x8, writing 0x40000008)
[ 2233.212122] i915 0000:00:02.0: restoring config space at offset 0x5 (was 0x1, writing 0x20e1)
[ 2233.304919] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2233.304925] i915 0000:00:02.0: setting latency timer to 64
(Note, however, that I grabbed this output after booting this morning
and successfully getting the intel driver and native resolution...see my
other post a short while ago in this thread.)
> You should have a file /etc/modprobe.d/i915-kms.conf with content
> "options i915 modeset=1", is it there?
Yes, indeed it is.
Thanks for your help, Sven.
Richard
Reply to: