| 1 |
On Thursday 22 April 2010 17:47:23 Grant wrote: |
| 2 |
> >>> Could this be the problem? |
| 3 |
> >>> |
| 4 |
> >>> # grep ^\(EE /var/log/Xorg.0.log |
| 5 |
> >>> (EE) Failed to load module "vesa" (module does not exist, 0) |
| 6 |
> >>> (EE) Failed to load module "fbdev" (module does not exist, 0) |
| 7 |
> >>> (EE) intel(0): [drm] Failed to open DRM device for : No such file or |
| 8 |
> >>> directory |
| 9 |
> >>> (EE) intel(0): Failed to become DRM master. |
| 10 |
> >>> (EE) intel(0): Failed to initialize kernel memory manager |
| 11 |
> >> |
| 12 |
> >> The first two errors are fine; Xorg defaults to trying vesa and fbdev as |
| 13 |
> >> display drivers and you just don't have them. |
| 14 |
> >> |
| 15 |
> >> The last three are your problem. The intel video driver is unable to |
| 16 |
> >> properly access the DRM subsystem, which will definitely cause X to slow |
| 17 |
> >> to a crawl. |
| 18 |
> >> |
| 19 |
> >> The most likely cause of your errors is that the intel AGP driver (i810 |
| 20 |
> >> or i915, depending on your hardware) isn't getting loaded. If that's |
| 21 |
> >> the case, you should see an error such as: |
| 22 |
> >> |
| 23 |
> >> [drm] failed to load kernel module "i915" |
| 24 |
> >> |
| 25 |
> >> in Xorg.0.log just before the ones from intel. If the modules are being |
| 26 |
> >> loaded, you'll likely see some other errors around that same area. The |
| 27 |
> >> aren't tagged with (EE), unfortunately; try: |
| 28 |
> >> |
| 29 |
> >> # grep -5 'Failed to open DRM' Xorg.0.log |
| 30 |
> >> |
| 31 |
> >> You can also check your dmesg output to see if the devices are being |
| 32 |
> >> initialized properly: |
| 33 |
> >> |
| 34 |
> >> platypus log # dmesg | grep agp |
| 35 |
> >> Linux agpgart interface v0.103 |
| 36 |
> >> agpgart-intel 0000:00:00.0: Intel 965GM Chipset |
| 37 |
> >> agpgart-intel 0000:00:00.0: detected 7676K stolen memory |
| 38 |
> >> agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000 |
| 39 |
> >> |
| 40 |
> >> platypus log # dmesg | grep drm |
| 41 |
> >> [drm] Initialized drm 1.1.0 20060810 |
| 42 |
> >> [drm] set up 7M of stolen space |
| 43 |
> >> [drm] initialized overlay support |
| 44 |
> >> fb0: inteldrmfb frame buffer device |
| 45 |
> >> [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 |
| 46 |
> >> |
| 47 |
> >> If everything's working, you should have the following devices that the |
| 48 |
> >> Xorg driver needs: |
| 49 |
> >> |
| 50 |
> >> platypus log # ls -l /dev/dri |
| 51 |
> >> total 0 |
| 52 |
> >> crw-rw---- 1 root video 226, 0 Apr 20 13:11 card0 |
| 53 |
> >> crw-rw---- 1 root video 226, 64 Apr 20 13:11 controlD64 |
| 54 |
> > |
| 55 |
> > Ah, thank you so much. I needed to enable CONFIG_DRM_I915 in the kernel. |
| 56 |
> > |
| 57 |
> > - Grant |
| 58 |
> |
| 59 |
> Strangely, now my laptop's brightness adjustment doesn't work via the |
| 60 |
> keyboard shortcuts. Any ideas on that? |
| 61 |
|
| 62 |
No idea other than to suggest that you take a look in |
| 63 |
/usr/share/hal/fdi/policy/10osvendor/* for any files that you could modify |
| 64 |
after you copy them to /etc/hal/fdi/policy/ - but I wouldn't know how. |
| 65 |
-- |
| 66 |
Regards, |
| 67 |
Mick |
Archives