WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [intel igp] using 915resolution or xorg  (Read 9204 times)

Offline will19

  • Newbie
  • *
  • Posts: 3
[intel igp] using 915resolution or xorg
« on: April 22, 2010, 07:53:37 PM »
Hi!, My Toshiba Portege M750  Laptop boots to a blank screen with the tiny core live cd.
I have an Intel GMA 4500MHD card and 1280x800 resolution. 

"Xvesa -listmodes" lists:
Interrupt pointer doesn't point at ROM
Interrupt pointer doesn't point at ROM
0x0006:  640x200x1  (monochrome) Planar (1 planes)
0x000D:  320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E:  640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010:  640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011:  640x480x1 (monochrome) Planar (1 planes)
0x0012:  640x480x4 Planar (4 planes)
0x0013:  320x200x8 PseudoColor

"sudo 915resolution 50 1280 800" lists
sudo: 915resolution: command not found

how can i get the 915 extension working, and what command do i use to edit the xsession script,
if these are my solutions at all anyway?
Also, I'm planning on installing tinycore on my hard drive once I can boot the livecd. how will i need to configure my install to get my card working?
Thanks, i'm lovin' tinycore on my other system, help would be greatly appreciated.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: [intel igp] using 915resolution or xorg
« Reply #1 on: April 22, 2010, 08:06:41 PM »
The '915resolution' command is in the '915resolution.tcz' extension.

Without a working X server you won't be able to run the 'appbroser' GUI. I'd therefore suggest to use tce-load -wi 915resolution.tcz to install the extension from the command line. This obviously depends on having a working network connection.

Offline will19

  • Newbie
  • *
  • Posts: 3
Re: [intel igp] using 915resolution or xorg
« Reply #2 on: April 22, 2010, 08:42:30 PM »
wow, thanks quick response

the download worked, however 915resolution does not seem to work for me as it outputs:

Intel chipset detected. However,
915resolution was unable to determine the chipset type
chipset id: 2a408086

it looks like  some guys over at puppy linux patched the 915 extension for 2a40806 / gma 4500
http://www.murga-linux.com/puppy/viewtopic.php?t=32462
but i guess that doesn't help me

any alternatives, suggestions?

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: [intel igp] using 915resolution or xorg
« Reply #3 on: April 22, 2010, 11:29:12 PM »
Have you tried Xorg? (enter the following to install: tce-load -wi Xorg-7.4.tcz)

Edit: OTOH, I don't see a reason why you should not be able to download the patched source from the Puppy forum and compile it yourself (using tce-load -wi compiletc.tcz to get the required tools for that). This way you could find out if the patched version really works for your system, and we might get our extension updated depending on your findings. (Sing out if you need further directions re. the compilation)
« Last Edit: April 23, 2010, 12:40:20 AM by maro »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10993
Re: [intel igp] using 915resolution or xorg
« Reply #4 on: April 23, 2010, 03:29:37 AM »
Have you checked the bios? There's often an option "AGP aperture" "Reserved graphics ram" or similar. Should be more than 4mb to get some proper resolutions in vesa / 915resolution.
The only barriers that can stop you are the ones you create yourself.

Offline will19

  • Newbie
  • *
  • Posts: 3
Re: [intel igp] using 915resolution or xorg
« Reply #5 on: April 23, 2010, 02:02:38 PM »
xorg worked, 915 didn't

 i  was able to compile the patched 915 resolution
and ran sudo  915resolution 50 1280 800

it appeared successful as it output

Chipset :GM45
BIOS :type 1
mode tableoffset: $C0000  + $268
Mode Table Entries: 36

Patch mode 50 to resolution 1280x800 complete

I then edited and saved .xsession, replacing 1024x768x32 on line 1 with 1280x800x32.
Then i typed startx, and there was  a blank screen  again.  Also, i couldn't find the BIOS settings you mentioned curaga while browsing my BIOS.

suggestions? 

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10993
Re: [intel igp] using 915resolution or xorg
« Reply #6 on: April 24, 2010, 05:25:53 AM »
Just use xorg? :)

Your -listmodes output looks like the bios has only set something like 512kb for graphics, which is not enough for any higher resolutions than those listed.

If there's no bios option, xorg is the only part that can allocate more. 915resolution only adds the resolution itself, can't change how much graphics ram there is.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14641
Re: [intel igp] using 915resolution or xorg
« Reply #7 on: April 26, 2010, 04:12:18 PM »
I had a similar problem with a toshiba m100 and the only way I could fix things was with xorg...

Offline bgpbupii

  • Newbie
  • *
  • Posts: 4
Re: [intel igp] using 915resolution or xorg
« Reply #8 on: June 29, 2010, 07:47:42 PM »
I have the same problem too with my u200 but i could not fix it with xorg. When I simply boot, it ends up a black screen with an X in the middle and everithing hangs up. After I installed Xorg from repostory, then I just tryed it with startx. The results was a blank screen then I get back the command line. Without any modification Xvesa -listmodes lists the following:

VBE version 3.0 (Intel(r) 8294GM Chipset Family Graphics Accelerated VGA BIOS)
DAC is fixed, controller is VGA compatible, RAMDAC causes snow
Total memory: 7872 kilobytes
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x250x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor
0x0163: 1280x800x8 PseudoColor
0x0164: 1280x800x16 TrueColor [5:6:5:0]
0x0165: 1280x800x24 TrueColor [8:8:8:8]
0x0105: 1024x768x8 PseudoColor
0x0117: 1024x768x16 TrueColor [5:6:5:0]
0x0118: 1024x768x24 TrueColor [8:8:8:8]
0x0112: 640x480x24 TrueColor [8:8:8:8]
0x0114: 800x600x16 TrueColor [5:6:5:0]
0x0115: 800x600x24 TrueColor [8:8:8:8]
0x0101: 640x480x8 PseudoColor
0x0103: 800x600x8 PseudoColor
0x0111: 640x480x16 TrueColor [5:6:5:0]


It seems the problem is not the amount of allocated video memory, nor video modes...

any suggestions?

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14641
Re: [intel igp] using 915resolution or xorg
« Reply #9 on: June 29, 2010, 11:29:57 PM »
Did you try to google "xorg.conf" and the name of your graphics chip?

This will usually turn something up that you can copy to /etc/X11 and get Xorg going

Offline bgpbupii

  • Newbie
  • *
  • Posts: 4
Re: [intel igp] using 915resolution or xorg
« Reply #10 on: June 30, 2010, 08:14:15 AM »
Hi, thanks for the rapid answer! So in my previous post I mistyped my chiset. It's 82945GM, so its a 945GM. I tryed googling thoroughly on theme but can't find any relevant solution, but many people had problems with 945GM on ubuntu forums too. BTW I am quite new in Linux, so I'm not shure that I always understand every explanations. ???

Last time I generated an xorg.conf file then I tested it. The problem was the same - black screen then consol again, but this time it generated a log file, wich contains errors that I can't overcome.
My generated xorg.conf.new file:

Section "ServerLayout"
   Identifier     "X.org Configured"
   Screen      0  "Screen0" 0 0
   InputDevice    "Mouse0" "CorePointer"
   InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
   ModulePath   "/usr/local/lib/X11/modules"
   FontPath     "/usr/local/lib/X11/fonts/misc/"
   FontPath     "/usr/local/lib/X11/fonts/TTF/"
   FontPath     "/usr/local/lib/X11/fonts/OTF"
   FontPath     "/usr/local/lib/X11/fonts/Type1/"
   FontPath     "/usr/local/lib/X11/fonts/100dpi/"
   FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
   Load  "glx"
   Load  "extmod"
   Load  "dri"
   Load  "dbe"
EndSection

Section "InputDevice"
   Identifier  "Keyboard0"
   Driver      "kbd"
EndSection

Section "InputDevice"
   Identifier  "Mouse0"
   Driver      "mouse"
   Option       "Protocol" "auto"
   Option       "Device" "/dev/input/mice"
   Option       "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
   Identifier   "Monitor0"
   VendorName   "Monitor Vendor"
   ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"               # [<bool>]
        #Option     "SWcursor"              # [<bool>]
        #Option     "ColorKey"              # <i>
        #Option     "CacheLines"            # <i>
        #Option     "Dac6Bit"               # [<bool>]
        #Option     "DRI"                   # [<bool>]
        #Option     "NoDDC"                 # [<bool>]
        #Option     "ShowCache"             # [<bool>]
        #Option     "XvMCSurfaces"          # <i>
        #Option     "PageFlip"              # [<bool>]
   Identifier  "Card0"
   Driver      "intel"
   VendorName  "Unknown Vendor"
   BoardName   "Unknown Board"
   BusID       "PCI:0:2:0"
EndSection

Section "Screen"
   Identifier "Screen0"
   Device     "Card0"
   Monitor    "Monitor0"
   SubSection "Display"
      Viewport   0 0
      Depth     1
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     4
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     8
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     15
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     16
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     24
   EndSubSection
EndSection


And the Xorg.0.log, with bunch of errors (its quite long, sorry ::)) :




_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/box:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29.1-tinycore i686
Current Operating System: Linux box 2.6.29.1-tinycore #1337 SMP Fri Apr 10 19:12:39 EEST 2009 i686
Build Date: 25 April 2009  08:42:34PM
 
   Before reporting problems, check www.tinycorelinux.com
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 30 13:38:29 2010
(EE) Unable to locate/open config file: "-/home/tc/xorg.conf.new"
(II) Loader magic: 0x7abc
(II) Module ABI versions:
   X.Org ANSI C Emulation: 0.4
   X.Org Video Driver: 5.0
   X.Org XInput driver : 4.0
   X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 2

(--) PCI:*(0@0:2:0) unknown vendor (0x8086) unknown chipset (0x27a2) rev 3, Mem @ 0xffd80000/524288, 0xe0000000/268435456, 0xffd40000/262144, I/O @ 0x0000cff8/8
(--) PCI: (0@0:2:1) unknown vendor (0x8086) unknown chipset (0x27a6) rev 3, Mem @ 0x54000000/524288
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
   Section "Device"
      Identifier   "Builtin Default intel Device 0"
      Driver   "intel"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default intel Screen 0"
      Device   "Builtin Default intel Device 0"
   EndSection
   Section "Device"
      Identifier   "Builtin Default i810 Device 0"
      Driver   "i810"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default i810 Screen 0"
      Device   "Builtin Default i810 Device 0"
   EndSection
   Section "Device"
      Identifier   "Builtin Default vesa Device 0"
      Driver   "vesa"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default vesa Screen 0"
      Device   "Builtin Default vesa Device 0"
   EndSection
   Section "Device"
      Identifier   "Builtin Default fbdev Device 0"
      Driver   "fbdev"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default fbdev Screen 0"
      Device   "Builtin Default fbdev Device 0"
   EndSection
   Section "ServerLayout"
      Identifier   "Builtin Default Layout"
      Screen   "Builtin Default intel Screen 0"
      Screen   "Builtin Default i810 Screen 0"
      Screen   "Builtin Default vesa Screen 0"
      Screen   "Builtin Default fbdev Screen 0"
   EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
   Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default i810 Device 0"
(==) No monitor specified for screen "Builtin Default i810 Screen 0".
   Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
   Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
   Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
   Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
   Entry deleted from font path.
(==) FontPath set to:
   /usr/local/lib/X11/fonts/misc/,
   /usr/local/lib/X11/fonts/TTF/,
   /usr/local/lib/X11/fonts/Type1/,
   /usr/local/lib/X11/fonts/75dpi/,
   built-ins
(==) ModulePath set to "/usr/local/lib/X11/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
   Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
   Using the default keyboard configuration.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
   
  • -1   0   0xffffffff - 0xffffffff (0x1) MX
  • [1] -1   0   0x000f0000 - 0x000fffff (0x10000) MX

   [2] -1   0   0x000c0000 - 0x000effff (0x30000) MX
   [3] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX
   [4] -1   0   0x0000ffff - 0x0000ffff (0x1) IX
   [5] -1   0   0x00000000 - 0x00000000 (0x1) IX
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/X11/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/X11/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "intel"
(II) Loading /usr/local/lib/X11/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 2.7.0
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/local/lib/X11/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 2.2.0
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(II) Loading /usr/local/lib/X11/modules/drivers//fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 0.4.0
   ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/X11/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.4.0
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "kbd"
(II) Loading /usr/local/lib/X11/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.3.2
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 4.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
   i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
   E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
   965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
   Mobile IntelĀ® GM45 Express Chipset,
   Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
   
  • -1   0   0xffffffff - 0xffffffff (0x1) MX
  • [1] -1   0   0x000f0000 - 0x000fffff (0x10000) MX

   [2] -1   0   0x000c0000 - 0x000effff (0x30000) MX
   [3] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX
   [4] -1   0   0x0000ffff - 0x0000ffff (0x1) IX
   [5] -1   0   0x00000000 - 0x00000000 (0x1) IX
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/local/lib/X11/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 0.0.2
   ABI class: X.Org Video Driver, version 5.0
(EE) open /dev/fb0: No such device
(II) resource ranges after probing:
   
  • -1   0   0xffffffff - 0xffffffff (0x1) MX
  • [1] -1   0   0x000f0000 - 0x000fffff (0x10000) MX

   [2] -1   0   0x000c0000 - 0x000effff (0x30000) MX
   [3] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX
   [4] 0   0   0x000a0000 - 0x000affff (0x10000) MS
   [5] 0   0   0x000b0000 - 0x000b7fff (0x8000) MS
   [6] 0   0   0x000b8000 - 0x000bffff (0x8000) MS
   [7] -1   0   0x0000ffff - 0x0000ffff (0x1) IX
   [8] -1   0   0x00000000 - 0x00000000 (0x1) IX
   [9] 0   0   0x000003b0 - 0x000003bb (0xc) IS
   [10] 0   0   0x000003c0 - 0x000003df (0x20) IS
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/local/lib/X11/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 0.1.0
   ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) intel(0): Creating default Display subsection in Screen section
   "Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM
(--) intel(0): Chipset: "945GM"
(--) intel(0): Linear framebuffer at 0xE0000000
(--) intel(0): IO registers at addr 0xFFD80000
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(==) intel(0): Using EXA for acceleration
(II) intel(0): 2 display pipes available.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA has no monitor section
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "SEC", prod id 16961
(II) intel(0): Resizable framebuffer: not available (1 3)
(II) intel(0): EDID vendor "SEC", prod id 16961
(II) intel(0): Output VGA disconnected
(II) intel(0): Output LVDS connected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS using initial mode 1280x800
(II) intel(0): detected 256 kB GTT.
(II) intel(0): detected 7932 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(==) intel(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/local/lib/X11/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 1.0.0
   ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/local/lib/X11/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
   compiled for 1.6.1, module version = 2.4.0
   ABI class: X.Org Video Driver, version 5.0
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(II) UnloadModule: "vesa"
(II) Unloading /usr/local/lib/X11/modules/drivers//vesa_drv.so
(II) UnloadModule: "fbdev"
(II) Unloading /usr/local/lib/X11/modules/drivers//fbdev_drv.so
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/local/lib/X11/modules/linux//libfbdevhw.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
   
  • -1   0   0xffffffff - 0xffffffff (0x1) MX
  • [1] -1   0   0x000f0000 - 0x000fffff (0x10000) MX

   [2] -1   0   0x000c0000 - 0x000effff (0x30000) MX
   [3] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX
   [4] 0   0   0x000a0000 - 0x000affff (0x10000) MS(OprD)
   [5] 0   0   0x000b0000 - 0x000b7fff (0x8000) MS(OprD)
   [6] 0   0   0x000b8000 - 0x000bffff (0x8000) MS(OprD)
   [7] -1   0   0x0000ffff - 0x0000ffff (0x1) IX
   [8] -1   0   0x00000000 - 0x00000000 (0x1) IX
   [9] 0   0   0x000003b0 - 0x000003bb (0xc) IS(OprU)
   [10] 0   0   0x000003c0 - 0x000003df (0x20) IS(OprU)
(EE) GARTInit: Unable to open /dev/agpgart (No such device)
(EE) intel(0): /dev/agpgart is either not available, or no memory is available
for allocation.  Please enable agpgart
.(WW) intel(0): VideoRam reduced to 7928 KB (page aligned - was 7931 KB)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "i915"
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 7928 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(EE) intel(0): AGP GART support is either not available or cannot be used.
   Make sure your kernel has agpgart support or has
   the agpgart module loaded.
(II) intel(0): Tiled allocation failed.
(WW) intel(0): Couldn't allocate tiled memory, fb compression disabled
(II) intel(0): Attempting memory allocation with untiled buffers.
(EE) intel(0): AGP GART support is either not available or cannot be used.
   Make sure your kernel has agpgart support or has
   the agpgart module loaded.
(II) intel(0): Untiled allocation failed.
(EE) intel(0): Couldn't allocate video memory

Fatal server error:
AddScreen/ScreenInit failed for driver 0


Please consult the TinyCore Linux support
    at www.tinycorelinux.com
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14641
Re: [intel igp] using 915resolution or xorg
« Reply #11 on: June 30, 2010, 08:39:23 AM »
My laptop has an i945 - xorg.conf for tc attached

Note that you will need to remove the touchpad sections and so on and this needs the i915 driver to be loaded.

I'm only using Xorg-7.5 and tc-3 now and the required drivers all load on their own - if I remember correctly, with Xorg-7.4 and tc-2, you need to manually load one or more of i915 and agpgart

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10993
Re: [intel igp] using 915resolution or xorg
« Reply #12 on: June 30, 2010, 08:42:11 AM »
Do you have the graphics- extension loaded?
The only barriers that can stop you are the ones you create yourself.

Offline bgpbupii

  • Newbie
  • *
  • Posts: 4
Re: [intel igp] using 915resolution or xorg
« Reply #13 on: June 30, 2010, 11:36:57 AM »
Hi,
I tried the following:

  • 0. Insert LiveCd, press F2, input: tinycore text
  • 1. Download 915resolution.tcz
  • 2. Set Mode 50 1280x800 32
  • 3. Download graphics-2.6.29.1-tinycore.tcz (I tried it under TC 3 too with graphics-2.6.33.3-tinycore.tcz and resolution changed 1280x800 inmediately in commandline just after download)
  • 4. Load agpgart kernelmodul with sudo modprobe agpgart
  • 5. Load i915 kernelmodul with sudo modprobe i915
  • 6. Generating xorg.conf.new (attached)
  • 7. Editing xorg.conf.new (attached)
  • 8. Testing with sudo Xorg -config /home/tc/xorg.conf.new.edited
  • 9. Black blank screen either TC2 or TC3. Must press hard reset...:-[

Am I doing someting wrong?
 
« Last Edit: June 30, 2010, 11:41:23 AM by bgpbupii »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14641
Re: [intel igp] using 915resolution or xorg
« Reply #14 on: June 30, 2010, 11:50:43 AM »
If you're going to use 915resolution, you only need Xvesa - what happens after your step 2 above if you enter "startx"

If you'd like to use Xorg, you don't need 915resolution