[vox-tech] monitor troubles

[Peter Jay Salzman]

ok. getting closer.


at some point, you're going to have to use google.  i need to get work
done and can't do anymore leg work tonight.


i went back to google, and did a search on:

   "i810 Not using mode "1024x768" (no mode of this name)"




A. i found a rather nice description of why you might be having this
   problem.  i have to admit, i didn't know this before:

   http://www.mail-archive.com/xfree86@xfree86.org/msg14541.html


B. you may want to try the modline suggested in this post:

   http://lists.suse.com/archive/suse-laptop/2003-Sep/0160.html

   if your monitor supports "1400x1050"  however, i don't think this
   will work, given what i found in A above.

C. this restates A:

   http://www.spinics.net/lists/xf-xpert/msg06361.html

D. this thread might be relevent:

   http://www.fedoraforum.org/forum/showthread/t-99.html

E. you can register your soul to hell to get this answer (i doubt
   they'll have anything of worth; the best documentation is free):

   http://www.experts-exchange.com/Operating_Systems/X_Windows/Q_20909629.html

F. or just go directly to the devil himself:

   http://www.xfree86.org/~dawes/intelfb.html




in addition:

   * try commenting out dri and glx in the module section of xf86config.
   * what version of X are you running?
   * in screen section of xf86config, set DefaultDepth to 16.  you might
     get a nice mode.
   * i've seen references to this chipset using 8MB vram, not 64.
     unless you're very sure i'm wrong, use 8MB.
   * try the vesa driver, as mark suggested.
   * did you know there's an i810 HOWTO at www.tldp.org?
   * use fbdev.  see (F) above.


three last pieces of advice before i really need to get back to work.

1. we're talking about a chipset here.  companies lease this technology
   from intel and play around with it (or hire intel to play around with
   it).  this means your chipset may not be the same as the "same"
   chipset on another machine.  it would help to google for the make and
   model of your computer along with the chipset name and the word
   "linux".  if you had a video card, it wouldn't make a bit of
   difference.  because this is a chipset, your computer's manufacturer
   and model might help.

2. heed the advice about "recent X versions", "vesa driver" and "fbdev".

3. you can always buy a super-duper cheap video card.  the voodoo 3 is
   STILL a relevent card.  you can play quake3/unreal tournament on it
   (not doom3 or ut2003 though) and it's only a measely 12 bucks.  yes,
   that's right fellow gamers.  12 bucks.  i don't care to admit what i
   paid for mine.  ;-)  this will make your problem go completely away,
   and you'll get some great hardware acceleration to boot.

now i need to get back to work.

hope you get it working.
pete


On Wed 21 Apr 04,  2:27 PM, Jennifer Stickel <jrstickel@ucdavis.edu> said:
> I did build it as a module into the kernel and modprobe -a agpgart gives
> 
> WARNING: Module agpgart already in kernel
> 
> I also tried modprobe intel-agp
> 
> This one eliminates the error message and by specifying the amount of 
> video RAM in XF86config I don't get any error messages in the 
> XF86config.0.log file.  But I do get these lines
> 
> (II) I810(0): Not using mode "1024x768" (no mode of this name)
> (II) I810(0): Increasing the scanline pitch to allow tiling mode (640 -> 
> 1024).
> (--) I810(0): Virtual size is 640x480 (pitch 1024)
> (**) I810(0):  Built-in mode "640x480"
> (II) I810(0): Attempting to use 73Hz refresh for mode "640x480" (41)
> (--) I810(0): Display dimensions: (300, 220) mm
> (--) I810(0): DPI set to (54, 55)
> 
> Jennifer
> 
> Peter Jay Salzman wrote:
> 
> >On Wed 21 Apr 04,  1:42 PM, Jennifer Stickel <jrstickel@ucdavis.edu> said:
> > 
> >
> >>It looks like this might be my problem.  I checked and there is 64MB of 
> >>video RAM for this card, but this is what I am getting in my 
> >>XF86config.0.log file
> >>
> >><big snip>
> >>
> >>(II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA 
> >>BIOS
> >>(II) I810(0): VESA VBE OEM Software Rev: 1.0
> >>(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
> >>(II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller
> >>(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
> >>(II) I810(0): Integrated Graphics Chipset: Intel(R) 865G
> >>(--) I810(0): Chipset: "865G"
> >>(--) I810(0): Linear framebuffer at 0xE8000000
> >>(--) I810(0): IO registers at addr 0xFEB80000
> >>(II) I810(0): detected 892 kB stolen memory.
> >>(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
> >>(WW) I810(0): /dev/agpgart is either not available, or no memory is 
> >>available
> >>for allocation.  Using pre-allocated memory only.
> >>(WW) I810(0): VideoRAM reduced to 892 kByte (limited to available sysmem)
> >>(--) I810(0): Pre-allocated VideoRAM: 892 kByte
> >>(--) I810(0): VideoRAM: 892 kByte
> >>   
> >>
> >
> >try this:
> >
> >  modprobe -a agpgart
> >
> >if that doesn't work,
> >
> >  cd /usr/src/linux/linux-version
> >  make menuconfig
> >  build agpgart as a module (simplest)
> >  make dep
> >  make modules
> >  make modules_install
> >  depmod -a
> >
> >  modprobe -a agpgart
> >
> >or, if you know how to build a kernel, i'd build it right into the
> >kernel.
> >
> >
> >before you follow this advice, do this:
> >
> >  dmesg | grep -i agpgart
> >
> >and see if agpgart is trying to register itself but is failing for some
> >reason.  if you don't see any mention, then definitely try the above.
> >
> >pete

-- 
Make everything as simple as possible, but no simpler.  -- Albert Einstein
GPG Instructions: http://www.dirac.org/linux/gpg
GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D