Michael Fothergill wrote: > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. Note that it will log errors with EE at the front. This is where the errors start: > [ 15.104] (II) [KMS] drm report modesetting isn't supported. > [ 15.104] (EE) open /dev/dri/card0: No such file or directory > [ 15.104] (WW) Falling back to old probe method for modesetting > [ 15.104] (EE) open /dev/dri/card0: No such file or directory > [ 15.104] (II) Loading sub module "fbdevhw" > [ 15.104] (II) LoadModule: "fbdevhw" > [ 15.105] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 15.105] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 15.105] compiled for 1.17.1, module version = 0.0.2 > [ 15.105] ABI class: X.Org Video Driver, version 19.0 > [ 15.105] (EE) open /dev/fb0: No such file or directory > [ 15.105] (WW) Falling back to old probe method for fbdev > [ 15.105] (II) Loading sub module "fbdevhw" > [ 15.105] (II) LoadModule: "fbdevhw" > [ 15.105] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so > [ 15.105] (II) Module fbdevhw: vendor="X.Org Foundation" > [ 15.105] compiled for 1.17.1, module version = 0.0.2 > [ 15.105] ABI class: X.Org Video Driver, version 19.0 > [ 15.105] (EE) open /dev/fb0: No such file or directory > [ 15.105] (EE) Screen 0 deleted because of no matching config section. > [ 15.105] (II) UnloadModule: "radeon" > [ 15.105] (EE) Screen 0 deleted because of no matching config section. > [ 15.105] (II) UnloadModule: "modesetting" > [ 15.105] (EE) Screen 0 deleted because of no matching config section. > [ 15.105] (II) UnloadModule: "fbdev" > [ 15.105] (II) UnloadSubModule: "fbdevhw" > [ 15.105] (II) Loading sub module "vbe" > [ 15.105] (II) LoadModule: "vbe" > [ 15.105] (II) Loading /usr/lib/xorg/modules/libvbe.so > [ 15.105] (II) Module vbe: vendor="X.Org Foundation" > [ 15.105] compiled for 1.17.1, module version = 1.1.0 > [ 15.105] ABI class: X.Org Video Driver, version 19.0 > [ 15.105] (II) Loading sub module "int10" > [ 15.105] (II) LoadModule: "int10" > [ 15.105] (II) Loading /usr/lib/xorg/modules/libint10.so > [ 15.105] (II) Module int10: vendor="X.Org Foundation" > [ 15.105] compiled for 1.17.1, module version = 1.0.0 > [ 15.105] ABI class: X.Org Video Driver, version 19.0 > [ 15.105] (II) VESA(0): initializing int10 > [ 15.105] (EE) VESA(0): Cannot read int vect > [ 15.105] (II) UnloadModule: "vesa" > [ 15.105] (II) UnloadSubModule: "int10" > [ 15.105] (II) Unloading int10 > [ 15.105] (II) UnloadSubModule: "vbe" > [ 15.105] (II) Unloading vbe > [ 15.105] (EE) Screen(s) found, but none have a usable configuration. "Screen(s) found, but none have a usable configuration." I have many times seen and dreaded that message. I can't decode the above into the root cause of the problem. Hopefully someone else will be able to do so. Does anyone else on this list have any hints here? I fear the problem is the newer Linux KMS and DRM interfaces which obsoleted a lot of hardware. I have been hit by that problem myself. Whereas older kernels worked perfectly supporting the hardware newer kernels have dropped support and broken my systems. I suggest booting one of the previous kernels and seeing if that helps. If not then try the newest kernel available, possibly a backports kernel. If not then I suggest trying to boot with the kernel command line option "nomodeset" and see if it improves things. Plus any better hints that others might supply. Bob
Attachment:
signature.asc
Description: Digital signature