Re: X: set resolution in Squeeze on a Macbook
On 2011-01-21 03:37 +0100, Richard Lawrence wrote: Sven Joachim svenj...@gmx.de writes: On 2011-01-20 18:39 +0100, Richard Lawrence wrote: Thanks for any advice you can offer. I feel pretty clueless about X-related stuff. 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? $ lsmod | grep i915 i915 54 0 drm_kms_helper 18309 1 i915 drm 112088 2 i915,drm_kms_helper i2c_algo_bit3497 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. 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? You should have a file /etc/modprobe.d/i915-kms.conf with content options i915 modeset=1, is it there? Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ipxi8yz0@turtle.gmx.de
Re: X: set resolution in Squeeze on a Macbook
Liam O'Toole liam.p.oto...@gmail.com writes: I have the same graphics card (down to the revision number) as the OP, and find that it works in squeeze both with and without KMS. The comsole appearance and behaviour is different, of course. ¹ http://wiki.debian.org/KernelModesetting That page mentions some known bugs for the card, but a consistently reliable workaround doesn't seem to be available. Fortunately I haven't encountered those bugs as yet. OK, now I'm *really* confused. Last night, I started experiencing problems with the touchpad: the mouse cursor wasn't really responding anymore; X seemed to be interpreting all movements as scroll events, and I couldn't move the cursor in any direction except sporadically. So rather than hibernating, as I usually do, I shut the machine down. This morning, my first boot attempt resulted in a blank screen. That is, I wasn't even getting a console. (X does not start at boot.) So I tried booting with acpi=off, as I have seen a number of sources that say this helps X-related problems on the Macbook go away. The result was: no change in mouse; no change in the graphics resolution; but really slow keyboard interaction (at the console and in X). To fix the mouse, I tried unloading and then reloading the appletouch module, which actually did help a bit, but didn't bring the mouse back to its normal functionality. Rebooted again (without acpi=off). Now I'm in X at native resolution, for the first time since installing Squeeze. Mouse works beautifully. /var/log/Xorg.0.log shows that I am at last using the intel driver. The only line before the driver initialization that I can see is different from previous attempts is: (WW) Falling back to old probe method for vesa ...So should I just hope it lasts? :) Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739omxlrv@berkeley.edu
Re: X: set resolution in Squeeze on a Macbook
Sven Joachim svenj...@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 54 0 drm_kms_helper 18309 1 i915 drm 112088 2 i915,drm_kms_helper i2c_algo_bit3497 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 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [6.513358] i915 :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: 0x0010, masking [7.950092] fb0: inteldrmfb frame buffer device [7.950103] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 2232.604944] i915 :00:02.0: PCI INT A disabled [ 2233.212105] i915 :00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 2233.212114] i915 :00:02.0: restoring config space at offset 0x7 (was 0x0, writing 0x5040) [ 2233.212118] i915 :00:02.0: restoring config space at offset 0x6 (was 0x8, writing 0x4008) [ 2233.212122] i915 :00:02.0: restoring config space at offset 0x5 (was 0x1, writing 0x20e1) [ 2233.304919] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 2233.304925] i915 :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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y66ew5qj@berkeley.edu
Re: X: set resolution in Squeeze on a Macbook
On 2011-01-21 17:29 +0100, Richard Lawrence wrote: So I tried booting with acpi=off, as I have seen a number of sources that say this helps X-related problems on the Macbook go away. The result was: no change in mouse; no change in the graphics resolution; but really slow keyboard interaction (at the console and in X). To fix the mouse, I tried unloading and then reloading the appletouch module, which actually did help a bit, but didn't bring the mouse back to its normal functionality. With acpi=off, many things will not work well (or at all). Indeed this option breaks the i915 kernel module on my laptop. Rebooted again (without acpi=off). Now I'm in X at native resolution, for the first time since installing Squeeze. Mouse works beautifully. /var/log/Xorg.0.log shows that I am at last using the intel driver. The only line before the driver initialization that I can see is different from previous attempts is: (WW) Falling back to old probe method for vesa ...So should I just hope it lasts? :) There is an error message from your other post [drm:i915_handle_error] *ERROR* EIR stuck: 0x0010, masking which I think is not fatal, but you could try a newer kernel (e.g. 2.6.37 from experimental) and see if runs more stable than the Squeeze kernel on your system. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874o9288l9@turtle.gmx.de
Re: X: set resolution in Squeeze on a Macbook
Sven Joachim svenj...@gmx.de writes: There is an error message from your other post [drm:i915_handle_error] *ERROR* EIR stuck: 0x0010, masking which I think is not fatal, but you could try a newer kernel (e.g. 2.6.37 from experimental) and see if runs more stable than the Squeeze kernel on your system. Very good; I'll try that if I continue to have problems. Thanks, everyone, for your help. Best, Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87lj2ew3wo@berkeley.edu
Re: X: set resolution in Squeeze on a Macbook
On 2011-01-19, Richard Lawrence richard.lawre...@berkeley.edu wrote: Thanks for your help, Liam! Liam O'Toole liam.p.oto...@gmail.com writes: The background: this Macbook has an Intel graphics card. lspci says it is a Mobile 945GM/GMS, 943/940GM Express Integrated Graphics Controller. Is the package xserver-xorg-video-intel installed? If it is, it should configure the resolution automatically. Yes, it is installed. Good. However, I suspect that there is deeper trouble afoot than simply a missing resolution in my X configuration. When I start X, there is a brief moment of onscreen garbage (randomly colored bars, etc.) before the screen goes blank and stumpwm starts (in a lower resolution). This leads me to believe that something in the auto-detection is failing and X is falling back to some default settings. Unfortunately, I don't see anything in /var/log/Xorg.0.log that would indicate this (is there another log I should check?). Check the log for occurences of intel. That will tell you whether the correct driver is used. It looks to me like it is being used, but I'm not sure...what's all this about VESA? $ grep -i /var/log/Xorg.0.log (--) PCI:*(0:0:2:0) 8086:27a2:8086:7270 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5038/524288, 0x4000/268435456, 0x5040/262144, I/O @ 0x20e0/8 (--) PCI: (0:0:2:1) 8086:27a6:8086:7270 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5030/524288 (==) Matched intel as autoconfigured driver 0 (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor=X.Org Foundation (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller Oh dear. For some reason the intel driver bombs and vesa is used by X instead. Are there any clues following the line intel: Driver for Intel Integrated Graphics Chipsets: i810,? [...] -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnijftq1.4ac.liam.p.otoole@dipsy.tubbynet
Re: X: set resolution in Squeeze on a Macbook
Hi Liam and all, $ grep -i /var/log/Xorg.0.log (Woops: for posterity's sake, that should be grep -i intel ...) (--) PCI:*(0:0:2:0) 8086:27a2:8086:7270 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5038/524288, 0x4000/268435456, 0x5040/262144, I/O @ 0x20e0/8 (--) PCI: (0:0:2:1) 8086:27a6:8086:7270 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5030/524288 (==) Matched intel as autoconfigured driver 0 (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor=X.Org Foundation (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller Oh dear. For some reason the intel driver bombs and vesa is used by X instead. Are there any clues following the line intel: Driver for Intel Integrated Graphics Chipsets: i810,? Not too much. Here's what I've got: [snip] (==) Matched intel as autoconfigured driver 0 (==) Matched vesa as autoconfigured driver 1 (==) Matched fbdev as autoconfigured driver 2 (==) Assigned the driver to the xf86ConfigLayout (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.13.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: vesa (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so (II) Module vesa: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.3.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: fbdev (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so (II) Module fbdev: vendor=X.Org Foundation compiled for 1.7.6.901, module version = 0.4.2 ABI class: X.Org Video Driver, version 6.0 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge (II) VESA: driver for VESA chipsets: vesa (II) FBDEV: driver for framebuffer: fbdev (II) Primary Device is: PCI 00@00:02:0 (WW) Falling back to old probe method for fbdev (II) Loading sub module fbdevhw (II) LoadModule: fbdevhw (II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so (II) Module fbdevhw: vendor=X.Org Foundation compiled for 1.7.7, module version = 0.0.2 ABI class: X.Org Video Driver, version 6.0 (EE) open /dev/fb0: No such file or directory (II) Loading sub module vbe (II) LoadModule: vbe (II) Loading /usr/lib/xorg/modules/libvbe.so (II) Module vbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Video Driver, version 6.0 (II) Loading sub module int10 (II) LoadModule: int10 (II) Loading /usr/lib/xorg/modules/libint10.so (II) Module int10: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Video Driver, version 6.0 [/snip] At that point, the VESA driver starts to initialize. The only warnings/errors in there seem to be related to fbdev. Here they are for the whole file: $ grep -E '\(EE|WW\)' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. (WW) `fonts.dir' not found (or not valid) in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. (WW) Falling back to old probe method for fbdev (EE) open /dev/fb0: No such file or directory (WW) VESA(0): Unable to estimate virtual size (WW) VESA(0): No valid modes left. Trying less strict filter... (WW) VESA(0): Unable to estimate virtual size (WW) VESA(0): No valid modes left. Trying aggressive sync range... (WW) VESA(0): Unable to estimate virtual size (EE) appletouch Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device appletouch (WW) Apple Computer Apple Internal Keyboard / Trackpad: unable to handle keycode 464 Thanks for any advice you can offer. I feel pretty clueless about X-related stuff. Best, Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
Re: X: set resolution in Squeeze on a Macbook
On 2011-01-20 18:39 +0100, Richard Lawrence wrote: Thanks for any advice you can offer. I feel pretty clueless about X-related stuff. 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 ? Sven ¹ http://wiki.debian.org/KernelModesetting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762tjxwut@turtle.gmx.de
Re: X: set resolution in Squeeze on a Macbook
Richard Lawrence schreef: Hi all, I've just installed Squeeze on a Macbook (2,1) and I'm wondering how I can get X to display at the native 1280x800 resolution. I've searched the Web and Debian list archives, but nothing seems to turn up quite the information I need. I'm not sure exactly how to do this. I read that Xorg -config can dump X's auto-detected configuration, which I could then tweak, but I am not sure exactly what command I would use to do this (Xorg -config alone yields Required argument to -config not specified). ... snip as far as i know the command is *not* Xorg conf but you have to do as root *Xorg -configure* please try this out. k. regards, steef -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d388470.6020...@home.nl
Re: X: set resolution in Squeeze on a Macbook
On 2011-01-20, Sven Joachim svenj...@gmx.de wrote: On 2011-01-20 18:39 +0100, Richard Lawrence wrote: Thanks for any advice you can offer. I feel pretty clueless about X-related stuff. 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 ? I have the same graphics card (down to the revision number) as the OP, and find that it works in squeeze both with and without KMS. The comsole appearance and behaviour is different, of course. ¹ http://wiki.debian.org/KernelModesetting That page mentions some known bugs for the card, but a consistently reliable workaround doesn't seem to be available. Fortunately I haven't encountered those bugs as yet. -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnijh6hf.4ac.liam.p.otoole@dipsy.tubbynet
Re: X: set resolution in Squeeze on a Macbook
Hi Sven, Thanks for chiming in! Sven Joachim svenj...@gmx.de writes: On 2011-01-20 18:39 +0100, Richard Lawrence wrote: Thanks for any advice you can offer. I feel pretty clueless about X-related stuff. 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. $ lsmod | grep i915 i915 54 0 drm_kms_helper 18309 1 i915 drm 112088 2 i915,drm_kms_helper i2c_algo_bit3497 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 it looks like I am using KMS (right?). Thanks, Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mxmvc77t@berkeley.edu
X: set resolution in Squeeze on a Macbook
Hi all, I've just installed Squeeze on a Macbook (2,1) and I'm wondering how I can get X to display at the native 1280x800 resolution. I've searched the Web and Debian list archives, but nothing seems to turn up quite the information I need. I am using stumpwm, and not a desktop environment that would provide me with a GUI for setting the resolution. Thus, my question *may* boil down to: 1) how can I set the resolution from the command line? But there are a few things I don't understand. The background: this Macbook has an Intel graphics card. lspci says it is a Mobile 945GM/GMS, 943/940GM Express Integrated Graphics Controller. In the past, running X on this machine at the native resolution has required the 915resolution package. But sources on the Web tell me that is no longer necessary in Squeeze, because there is better support in the kernel for this graphics chipset, and indeed the 915resolution package no longer even seems to exist. Curious to me also is the fact that xorg.conf no longer exists. Again, sources on the Web tell me that this is because X now auto-configures itself, so a static configuration file is not necessary (though it will be used if provided). So this brings me to my puzzle. Normally, I would look to set the available resolutions in xorg.conf. But since there is no xorg.conf, I'm not sure where to go. I can see at least one option: 2) provide an xorg.conf that will set the native resolution. I'm not sure exactly how to do this. I read that Xorg -config can dump X's auto-detected configuration, which I could then tweak, but I am not sure exactly what command I would use to do this (Xorg -config alone yields Required argument to -config not specified). However, I suspect that there is deeper trouble afoot than simply a missing resolution in my X configuration. When I start X, there is a brief moment of onscreen garbage (randomly colored bars, etc.) before the screen goes blank and stumpwm starts (in a lower resolution). This leads me to believe that something in the auto-detection is failing and X is falling back to some default settings. Unfortunately, I don't see anything in /var/log/Xorg.0.log that would indicate this (is there another log I should check?). Any advice as to how to proceed here would be greatly appreciated! If anyone has a working configuration of X, with native resolution, on a Macbook with an Intel card, in Squeeze, I'd be happy to hear about it. Thanks! Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3nsg6ag@berkeley.edu
Re: X: set resolution in Squeeze on a Macbook
On 2011-01-19, Richard Lawrence richard.lawre...@berkeley.edu wrote: Hi all, I've just installed Squeeze on a Macbook (2,1) and I'm wondering how I can get X to display at the native 1280x800 resolution. I've searched the Web and Debian list archives, but nothing seems to turn up quite the information I need. I am using stumpwm, and not a desktop environment that would provide me with a GUI for setting the resolution. Thus, my question *may* boil down to: 1) how can I set the resolution from the command line? But there are a few things I don't understand. The background: this Macbook has an Intel graphics card. lspci says it is a Mobile 945GM/GMS, 943/940GM Express Integrated Graphics Controller. Is the package xserver-xorg-video-intel installed? If it is, it should configure the resolution automatically. In the past, running X on this machine at the native resolution has required the 915resolution package. But sources on the Web tell me that is no longer necessary in Squeeze, because there is better support in the kernel for this graphics chipset, and indeed the 915resolution package no longer even seems to exist. Correct. The 915resolution is obsolete. Curious to me also is the fact that xorg.conf no longer exists. Again, sources on the Web tell me that this is because X now auto-configures itself, so a static configuration file is not necessary (though it will be used if provided). Correct again. The file is no longer necessary in most cases ans is not created by default. So this brings me to my puzzle. Normally, I would look to set the available resolutions in xorg.conf. But since there is no xorg.conf, I'm not sure where to go. I can see at least one option: 2) provide an xorg.conf that will set the native resolution. I'm not sure exactly how to do this. I read that Xorg -config can dump X's auto-detected configuration, which I could then tweak, but I am not sure exactly what command I would use to do this (Xorg -config alone yields Required argument to -config not specified). Not sure about that issue, but hopefully it won't matter :-) However, I suspect that there is deeper trouble afoot than simply a missing resolution in my X configuration. When I start X, there is a brief moment of onscreen garbage (randomly colored bars, etc.) before the screen goes blank and stumpwm starts (in a lower resolution). This leads me to believe that something in the auto-detection is failing and X is falling back to some default settings. Unfortunately, I don't see anything in /var/log/Xorg.0.log that would indicate this (is there another log I should check?). Check the log for occurences of intel. That will tell you whether the correct driver is used. Any advice as to how to proceed here would be greatly appreciated! If anyone has a working configuration of X, with native resolution, on a Macbook with an Intel card, in Squeeze, I'd be happy to hear about it. I have used Intel cards on various machines, although not a Macbook. In all cases X found the native resolution without a hitch. Thanks! Richard Good luck. Liam -- Liam O'Toole Cork, Ireland -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnijebsb.4ac.liam.p.otoole@dipsy.tubbynet
Re: X: set resolution in Squeeze on a Macbook
Thanks for your help, Liam! Liam O'Toole liam.p.oto...@gmail.com writes: The background: this Macbook has an Intel graphics card. lspci says it is a Mobile 945GM/GMS, 943/940GM Express Integrated Graphics Controller. Is the package xserver-xorg-video-intel installed? If it is, it should configure the resolution automatically. Yes, it is installed. However, I suspect that there is deeper trouble afoot than simply a missing resolution in my X configuration. When I start X, there is a brief moment of onscreen garbage (randomly colored bars, etc.) before the screen goes blank and stumpwm starts (in a lower resolution). This leads me to believe that something in the auto-detection is failing and X is falling back to some default settings. Unfortunately, I don't see anything in /var/log/Xorg.0.log that would indicate this (is there another log I should check?). Check the log for occurences of intel. That will tell you whether the correct driver is used. It looks to me like it is being used, but I'm not sure...what's all this about VESA? $ grep -i /var/log/Xorg.0.log (--) PCI:*(0:0:2:0) 8086:27a2:8086:7270 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5038/524288, 0x4000/268435456, 0x5040/262144, I/O @ 0x20e0/8 (--) PCI: (0:0:2:1) 8086:27a6:8086:7270 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0x5030/524288 (==) Matched intel as autoconfigured driver 0 (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor=X.Org Foundation (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller (II) VESA(0): VESA VBE OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation (II) VESA(0): VESA VBE OEM Product: Intel(r) 82945GM Chipset Family Graphics Controller Also, shortly after my original post, I learned about xrandr. This confirms my suspicion that the correct mode is not being detected: $ xrandr --prop xrandr: Failed to get size of gamma for output default Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 61.0* 800x60061.0 (Note the lack of a 1280x800 resolution.) Any ideas? Am I mistaken in believing that X is loading the correct driver? How can I clue X in to the native resolution? Thanks! Richard -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874o94eksj@berkeley.edu
