VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: Is there a work around for the intel gfx problem ?  (Read 1414 times)

marduk

  • Member
  • *
  • Posts: 6
Is there a work around for the intel gfx problem ?
« on: April 21, 2010, 10:17:36 am »



linux + my crapy laptop = vesa

If i try to load the intel drivers x wont start

it just blinks a cupple of times and x fails to boot

so im stuck with vesa drives like many intel chipset users

im aware this bug is plaguing the linux community

if anyone has a link to a fix or work around

or has any ideas any help would be appreciated

                                                                                     
Logged

retired1af

  • Packager
  • Vectorian
  • ****
  • Posts: 1300
Re: Is there a work around for the intel gfx problem ?
« Reply #1 on: April 21, 2010, 10:20:11 am »

More information would be helpful. Notebook specifications especially. Processor, RAM, video chipset, version of VL you're using, etc. ;)
Logged
ASUS K73 Intel i3 Dual Core 2.3GHz

marduk

  • Member
  • *
  • Posts: 6
Re: Is there a work around for the intel gfx problem ?
« Reply #2 on: April 21, 2010, 10:50:10 am »

compact presario cq60

GMA X4500 intel gfx

2 gigs of ram

on vector 6

Genuine Intel(R) CPU             585  @ 2.16GHz
Family, model, stepping      : 6, 15, 13 (Pentium III/Pentium III Xeon/Celeron)


Logged

retired1af

  • Packager
  • Vectorian
  • ****
  • Posts: 1300
Re: Is there a work around for the intel gfx problem ?
« Reply #3 on: April 21, 2010, 12:02:12 pm »

VL 6 has some issues with the GMA 4500. Joe found a work around described in this thread...

http://forum.vectorlinux.com/index.php?topic=10633.msg68411
Logged
ASUS K73 Intel i3 Dual Core 2.3GHz

marduk

  • Member
  • *
  • Posts: 6
Re: Is there a work around for the intel gfx problem ?
« Reply #4 on: April 21, 2010, 12:31:49 pm »

Thanks ill give it a try tonight
Logged

marduk

  • Member
  • *
  • Posts: 6
Re: Is there a work around for the intel gfx problem ?
« Reply #5 on: April 21, 2010, 01:08:56 pm »

it worked  ;D
now i just need to get this worked out

glxinfo
name of display: :0.0
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".


glxgears
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual

Logged

roarde

  • Vectorian
  • ****
  • Posts: 589
  • move the needle
Re: Is there a work around for the intel gfx problem ?
« Reply #6 on: April 21, 2010, 04:10:23 pm »

You've probably already made sure the GLX extension is requested in xorg.conf.  There's some reason it's not loading, then. I'm on chrome9/openchrome and solved a similar (not identical, sorry) problem by looking at /var/log/Xorg.0.log and walking it down. Grep helps, but it's hard to tell what to search for. You may have to read or at least scan the whole file.

The author's long-winded, and not much plot, but bring a pot of coffee and hunker down; the ending's usually worth the read. :P
Logged
Robert
VL Light RC 1.9

marduk

  • Member
  • *
  • Posts: 6
Re: Is there a work around for the intel gfx problem ?
« Reply #7 on: April 21, 2010, 08:06:14 pm »

O.O


(WW) VESA(0): Bad V_BIOS checksum



(WW) VESA(0): Failed to set up write-combining range (0x83f00000,0xf0000)
(WW) VESA(0): Failed to set up write-combining range (0x83e00000,0x1f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83c00000,0x3f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83800000,0x7f0000)
(WW) VESA(0): Failed to set up write-combining range (0x83000000,0xff0000)
(WW) VESA(0): Failed to set up write-combining range (0x82000000,0x1ff0000)
(WW) VESA(0): Failed to set up write-combining range (0x80000000,0x3ff0000)



(WW) VESA(0): Option "DRI" is not used
(WW) VESA(0): Option "UseEdidFreqs" is not used

(WW) Option "XkbModel" requires an string value

(WW) Option "XkbVariant" requires an string value


And the rabbit hole gets deeper
Logged