Linux-Hardware Digest #562, Volume #14            Tue, 3 Apr 01 03:13:03 EDT

Contents:
  Is AMD 760 chipset now working? ([EMAIL PROTECTED])
  Re: Problem with second ethernet card ("Bastiaan Schaap")
  KT7 and Networking (Twix)
  VTech Helio PDA (Young4ert)
  Re: Problem with second ethernet card (Dean Thompson)
  Re: USB Hard Drive (Update) (John Hong)
  Re: External modem HELP!!! (Nader)
  Re: Question: Anyone got ide2 *and* ide3 working on Promise ata100? (Nader)
  Re: Problems with Toshiba's 4600 graphics card (Klamer Schutte)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED]
Subject: Is AMD 760 chipset now working?
Date: Tue, 03 Apr 2001 04:58:41 GMT

Any one have luck or info on the AMD 760 chipset mobo's with DDR
SDRAM?

------------------------------

From: "Bastiaan Schaap" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Problem with second ethernet card
Date: Tue, 3 Apr 2001 07:53:39 +0200

Thank you for the input guys!!  I've been insmod-ding, lsmod-ding,
ifconfig-ging all night.... I compiled a new kernel, with the ne2000 support
as a kernel module. I reconfigured /etc/modules.conf to only contain:
alias eth0 ne2k-pci
alias eth1 ne2k-pci,
whithout the option lines. It only recognizes my 'second' card (Realtek).
The first card (Winbond) get's recognized as a NON-VGA adapter for some
reason. I tried to load it with the ne module (NE1000), then it says: Device
busy... Offcourse I unloaded all other modules first ;-)
So when I reached the stage where I was standing in front of the window
holding the linux box above my head, I suddenly felt this sudden urge to put
in one of those nice old ISA network cards, and throwing the Winbond card
out of the window instead.... I must say it was a real relief when I heard
the Winbond cracking on the pavement below, hihi ;-)  Well, I configured the
ISA to be on IRQ 9 and io 240. Put in alias eth0 ne  and option eth0 ne
io=240 irq=9 in my modules.conf and it works like a charm..  I have two
ethernetcards working...  The problem now has shifted to the fact that I
configured my eth0 card to use DHCP (in rc.config). During boot-up I see
both cards being found, I see dhcp client starting for eth0, I see
networking starting for eth1, and I can login. If I check my routing table,
eth0 didn't get an ip.....  but this is another problem, and if I can't
manage to figure it out, I'll post a new thread.

Thanx for all your help!,

cheers,

--
Bastiaan Schaap
Desyde BV
[EMAIL PROTECTED]
Tel 06 - 51998277
Fax 035 - 5430547
http://www.desyde.nl
________________________________

God doesn't play dice. -- Albert Einstein




------------------------------

From: Twix <[EMAIL PROTECTED]>
Subject: KT7 and Networking
Date: Mon, 02 Apr 2001 22:52:41 -0700

I need some help with my network card.  I'm using a Linksys Fast 100
network card.  I have the KT7-RAID mb by abit with the VIA133 chipset.
Currently VIA133 chipsets don't support Linux and there are no
immeadiate plans to in the future.  Because of this, no bridge drivers
install and my network card although detected as a generic unknown
card goes unused, and I can't get Linux to do anything with it.  I'm
using Mandrake 8.0 now.  Does anyone know a fix for this?


------------------------------

From: Young4ert <[EMAIL PROTECTED]>
Subject: VTech Helio PDA
Date: Tue, 03 Apr 2001 05:36:31 GMT

Hi,

I just bought a VTech Helio PDA for ~$50 (after marked down and rebates) 
and am wondering if it is supported under Linux.  TIA.

------------------------------

From: Dean Thompson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Problem with second ethernet card
Date: Tue, 03 Apr 2001 16:03:25 +1000


Hi Bastiaan,

> Thank you for the input guys!!  I've been insmod-ding, lsmod-ding,
> ifconfig-ging all night.... I compiled a new kernel, with the ne2000 
> support as a kernel module. I reconfigured /etc/modules.conf to only 
> contain:
> alias eth0 ne2k-pci
> alias eth1 ne2k-pci,
> whithout the option lines. It only recognizes my 'second' card (Realtek).
> The first card (Winbond) get's recognized as a NON-VGA adapter for some
> reason. I tried to load it with the ne module (NE1000), then it says: 
> Device busy... Offcourse I unloaded all other modules first ;-)

>From memory I think you have to download a special network driver from Donald
Beckers site (I can't remember exactally the URL, but it is posted in this
newsgroup somewhere) which supports the WinBond network adapter.

[...]
> The problem now has shifted to the fact that I configured my eth0 card to 
> use DHCP (in rc.config). During boot-up I see both cards being found, I see 
> dhcp client starting for eth0, I see networking starting for eth1, and I 
> can login. If I check my routing table, eth0 didn't get an ip.....  but 
> this is another problem, and if I can't manage to figure it out, I'll post 
> a new thread.

Yep, check to make sure that you have a DHCP server which is listening to you
and that it is running.  If you run into any problems you might like to take a
quick look through the DHCP-HOWTO document located at http://www.linuxdoc.org,
which outlines some of the "gotcha's" that can exist when setting up DHCP
servers and trying to get IP addresses from them.

Good luck.

See ya

Dean Thompson

--
+____________________________+____________________________________________+
| Dean Thompson              | E-mail  - [EMAIL PROTECTED] |
| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

------------------------------

From: [EMAIL PROTECTED] (John Hong)
Subject: Re: USB Hard Drive (Update)
Date: Tue, 3 Apr 2001 05:29:25 +0000 (UTC)

[EMAIL PROTECTED] (Kenneth Crudup) writes:

>In article <99dlvl$m8m$[EMAIL PROTECTED]>,
>[EMAIL PROTECTED] (John Hong) says:

>>      So far, no luck with SuSE 7.1 with the newest 2.4.2 kernel.

>FWIW, I've been using a USB Zip drive for months with the 2.4.X series of
>kernels. Have you loaded usb-storage.o ?

        Yep, also the ide-scsi.o and sg.o, no luck yet.  I'm sure they'll
get it working one way or another.  Just a matter of time.



------------------------------

From: Nader <[EMAIL PROTECTED]>
Subject: Re: External modem HELP!!!
Date: Mon, 02 Apr 2001 23:14:13 -0700

What kernel version are you using?

What /dev/ttyS device are you using?  /dev/modem?

Check out http://linux.nf/stepbystep.htm, Modems section.


Zak wrote:

> Hi,
> i had many difficulties on configuring my internal modem so i finally
> bought an external modem(CNET Ambiant , 56k/V90, serial). I tried it on
> windows and it works fine on com4 irq3 (with driver on floppy).
> I understood before that linux supports all external modems, but using
> the kppp i couldnt make it work, when i query the modem it gives a
> message saying 'couldnt get a response from the modem. I could see the
> RS and TR light go on when i press the query modem but no result...i
> couldnt find much help in the how to in linux.org and many other sites
> that only talk about internal modems and stating that external modems
> have no problems...im using mandrake 7.2, and kppp 2.0...please help!!!
> or refer me to any good site on internet...Thank.


------------------------------

From: Nader <[EMAIL PROTECTED]>
Subject: Re: Question: Anyone got ide2 *and* ide3 working on Promise ata100?
Date: Mon, 02 Apr 2001 23:18:00 -0700

You may want to try kernel 2.4.2.  There have been many improvements to the ide
code since 2.2.x.

It's not too much effort and you can always go back to your current kernel (as
long as you save it).

jazbo wrote:

> Nader wrote:
>
> > What kernel version are you using?
> >
> > If the kernel doesn't support HPT366, then you'll have to
> > pass ide parameters to the kernel during installation.  See this web site
> > for more info and details on how to determine the parameters and how to
> > pass them: http://linux.nf/stepbystep.htm - select the ULTRA-66 Step by
> > Step
> > guide.  After you get your system running and stable, you can put the
> > parameters in LILO so you don't have to type them each time you boot.
> > Alternatively, you can upgrade to the 2.4.2 kernel which can be
> > configured to support HPT366 directly.
>
> Actually I was hoping that someone could confirm that they have *seen* both
> channels in use under Linux.
>


------------------------------

From: Klamer Schutte <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.x
Subject: Re: Problems with Toshiba's 4600 graphics card
Date: Tue, 03 Apr 2001 08:22:27 +0200

This is a multi-part message in MIME format.
==============258B4C0FD28124C8B29842A4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

(message resent -- somehow it didn't come out)

Steve Rockefeller wrote:

> Sorry, not much help here other than to say install of Mandrake 7.2 went
> fine.  X works fine in 1024X768 16 or 24 bit mode (I think 24 bit, I'm only
> using 16.) 

This information did help me! Thanks! 
After struggling with RH 6.2 I downloaded mandrake 7.2 after reading this
advice.
It started with a graphical install... 
And the network worked at once (RH 6.2 did not automatically work.)

Install-time X configuration, as offered in the expert install, did not work.
To have X working afterwards it seems necessary to specify at LILO time 
what kind of video resolution you want to use with X, as the FBdev X
driver is used (I use XFree86 3.3.6). For that I have attached to this message
my /etc/lilo.conf and my /etc/X11/XF86Config file. The magic number 791 in 
lilo.conf is the decimal representation from 0x317; 0x317 comes from
/usr/src/linux/Documentation/fb/vesafb.txt. This results in 1024x768
with 24 bits. Respons is a bit slow, so we still have to wait for an accelerated
driver.

For another distribution this probably will mean: make sure you have a kernel
with vesafb support (possibly by recompiling your kernel) and getting the 
XF86_FBDev X server. (probably XFree86-FBDev-3.3.6-20.i386.rpm for RH 6.2)

> However, whenever I compile a new kernel (2.4.2) and add that in
> lilo even when saving my old modules etc... X gets broken :(  Yes I'm
> somewhat of a newbie but recompiled my kernel on a desktop with a g400 video
> card and X did not get broken there so..?.?

I guess here that in you new kernel you did not include the fbdev devices 
corresponding to CyberBlade XP device (my guess: you need the vesa device.)

> "Luis Miguel N Tavora" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> >
> >   I've tried to install Red Hat 7.0 on a brand new laptop Toshiba 4600
> > (PIII 700MHz)
> > but got some problems with the graphics card. The system doesn't
> > recognize the
> > Trident CyberBlade XP (22) card and so X doesn't work....

oh yes, all I said is relative to my brand new Toshiba Satellite Pro 4600 PIII
800.

Klamer
-- 
Klamer Schutte, E-mail: [EMAIL PROTECTED]
Electro-Optical Systems, TNO Physics and Electronics Laboratory
Tel: +31-70-3740469 -- Fax: +31-70-3740654 -- Mobile: +31-6-51316671
-- 
Klamer Schutte, E-mail: [EMAIL PROTECTED]
Electro-Optical Systems, TNO Physics and Electronics Laboratory
Tel: +31-70-3740469 -- Fax: +31-70-3740654 -- Mobile: +31-6-51316671
==============258B4C0FD28124C8B29842A4
Content-Type: text/plain; charset=us-ascii;
 name="lilo.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="lilo.conf"

boot=/dev/fd0
vga=791
default=linux
lba32
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz-2.2.17-21mdk
        label=linux
        root=/dev/hda5
        append="vga=791"
        read-only

==============258B4C0FD28124C8B29842A4
Content-Type: text/plain; charset=us-ascii;
 name="XF86Config"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="XF86Config"


# File generated by XFdrake.

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

Section "Files"

    RgbPath     "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Mandrake 6.0 and later now use a font server independent of
# the X server to render fonts.

    FontPath   "unix/:-1"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

    # Uncomment this to cause a core dump at the spot where a signal is
    # received.  This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    #NoTrapSignals

    # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    #DontZap

    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
    # sequences.  This allows clients to receive these key events.
    #DontZoom

    # This  allows  the  server  to start up even if the
    # mouse device can't be opened/initialised.
    AllowMouseOpenFail

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Keyboard section
# **********************************************************************

Section "Keyboard"

    Protocol    "Standard"

    # when using XQUEUE, comment out the above line, and uncomment the
    # following line
    #Protocol   "Xqueue"

    AutoRepeat  250 30

    # Let the server do the NumLock processing.  This should only be
    # required when using pre-R6 clients
    #ServerNumLock

    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    #Xleds      "1 2 3"

    #To set the LeftAlt to Meta, RightAlt key to ModeShift,
    #RightCtl key to Compose, and ScrollLock key to ModeLock:

    LeftAlt        Meta
    RightAlt       Meta
    ScrollLock     Compose
    RightCtl       Control

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    XkbDisable

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    XkbModel    "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#    XkbModel    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    XkbLayout   "de"
# or:
#    XkbLayout   "de"
#    XkbVariant  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    XkbOptions  "ctrl:swapcaps"

# These are the default XKB settings for XFree86
#    XkbRules    "xfree86"
#    XkbModel    "pc101"
#    XkbLayout   "us"
#    XkbVariant  ""
#    XkbOptions  ""

    XkbKeycodes     "xfree86"
    XkbTypes        "default"
    XkbCompat       "default"
    XkbSymbols      "us(pc105)"
    XkbGeometry     "pc"
    XkbRules        "xfree86"
    XkbModel        "pc105"
    XkbLayout       "us"

EndSection

# **********************************************************************
# Pointer section
# **********************************************************************

Section "Pointer"
    Protocol    "IMPS/2"
    Device      "/dev/psaux"
    ZAxisMapping 4 5
#    Emulate3Buttons
#    Emulate3Timeout    50

# ChordMiddle is an option for some 3-button Logitech mice

#    ChordMiddle

EndSection



# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"
    Identifier "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    VendorName "Unknown"
    ModelName  "Unknown"


# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
    HorizSync  31.5-57.0


# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
    VertRefresh 50-90


# Modes can be specified in two formats.  A compact one-line format, or
# a multi-line format.

# These two are equivalent

#    ModeLine "1024x768i" 45 1024 1048 1208 1264 768 776 784 817 Interlace

#    Mode "1024x768i"
#        DotClock       45
#        HTimings       1024 1048 1208 1264
#        VTimings       768 776 784 817
#        Flags          "Interlace"
#    EndMode
# 640x480, 75.0Hz; hfreq=37.500000, vfreq=75.000000
ModeLine "640x480"       31.50  640  656  720  840  480  481  484  500 -hsync -vsync
# 720x400, 70.0Hz
# 800x600, 72.0Hz; hfreq=48.077000, vfreq=72.188004
ModeLine "800x600"       50.00  800  856  976 1040  600  637  643  666 +hsync +vsync
# 1024x768, 87.0iHz

# This is a set of standard mode timings. Modes that are out of monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.

# 640x400 @ 70 Hz, 31.5 kHz hsync
Modeline "640x400"     25.175 640  664  760  800   400  409  411  450
# 640x480 @ 60 Hz, 31.5 kHz hsync
Modeline "640x480"     25.175 640  664  760  800   480  491  493  525
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600"     36     800  824  896 1024   600  601  603  625
# 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync
Modeline "1024x768"    44.9  1024 1048 1208 1264   768  776  784  817 Interlace

# 640x400 @ 85 Hz, 37.86 kHz hsync
Modeline "640x400"     31.5   640  672 736   832   400  401  404  445 -HSync +VSync
# 640x480 @ 72 Hz, 36.5 kHz hsync
Modeline "640x480"     31.5   640  680  720  864   480  488  491  521
# 640x480 @ 75 Hz, 37.50 kHz hsync
ModeLine  "640x480"    31.5   640  656  720  840   480  481  484  500 -HSync -VSync
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600"     40     800  840  968 1056   600  601  605  628 +hsync +vsync

# 640x480 @ 85 Hz, 43.27 kHz hsync
Modeline "640x480"     36     640  696  752  832   480  481  484  509 -HSync -VSync
# 1152x864 @ 89 Hz interlaced, 44 kHz hsync
ModeLine "1152x864"    65    1152 1168 1384 1480   864  865  875  985 Interlace

# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600"     50     800  856  976 1040   600  637  643  666 +hsync +vsync
# 1024x768 @ 60 Hz, 48.4 kHz hsync
Modeline "1024x768"    65    1024 1032 1176 1344   768  771  777  806 -hsync -vsync

# 640x480 @ 100 Hz, 53.01 kHz hsync
Modeline "640x480"     45.8   640  672  768  864   480  488  494  530 -HSync -VSync
# 1152x864 @ 60 Hz, 53.5 kHz hsync
Modeline  "1152x864"   89.9  1152 1216 1472 1680   864  868  876  892 -HSync -VSync
# 800x600 @ 85 Hz, 55.84 kHz hsync
Modeline  "800x600"    60.75  800  864  928 1088   600  616  621  657 -HSync -VSync

# 1024x768 @ 70 Hz, 56.5 kHz hsync
Modeline "1024x768"    75    1024 1048 1184 1328   768  771  777  806 -hsync -vsync
# 1280x1024 @ 87 Hz interlaced, 51 kHz hsync
Modeline "1280x1024"   80    1280 1296 1512 1568  1024 1025 1037 1165 Interlace

# 800x600 @ 100 Hz, 64.02 kHz hsync
Modeline  "800x600"    69.65  800  864  928 1088   600  604  610  640 -HSync -VSync
# 1024x768 @ 76 Hz, 62.5 kHz hsync
Modeline "1024x768"    85    1024 1032 1152 1360   768  784  787  823
# 1152x864 @ 70 Hz, 62.4 kHz hsync
Modeline  "1152x864"   92    1152 1208 1368 1474   864  865  875  895
# 1280x1024 @ 61 Hz, 64.2 kHz hsync
Modeline "1280x1024"  110    1280 1328 1512 1712  1024 1025 1028 1054

# 1024x768 @ 85 Hz, 70.24 kHz hsync
Modeline "1024x768"   98.9  1024 1056 1216 1408   768 782 788 822 -HSync -VSync
# 1152x864 @ 78 Hz, 70.8 kHz hsync
Modeline "1152x864"   110   1152 1240 1324 1552   864  864  876  908

# 1280x1024 @ 70 Hz, 74.59 kHz hsync
Modeline "1280x1024"  126.5 1280 1312 1472 1696  1024 1032 1040 1068 -HSync -VSync
# 1600x1200 @ 60Hz, 75.00 kHz hsync
Modeline "1600x1200"  162   1600 1664 1856 2160  1200 1201 1204 1250 +HSync +VSync
# 1152x864 @ 84 Hz, 76.0 kHz hsync
Modeline "1152x864"   135    1152 1464 1592 1776   864  864  876  908

# 1280x1024 @ 74 Hz, 78.85 kHz hsync
Modeline "1280x1024"  135    1280 1312 1456 1712  1024 1027 1030 1064

# 1024x768 @ 100Hz, 80.21 kHz hsync
Modeline "1024x768"   115.5  1024 1056 1248 1440  768  771  781  802 -HSync -VSync
# 1280x1024 @ 76 Hz, 81.13 kHz hsync
Modeline "1280x1024"  135    1280 1312 1416 1664  1024 1027 1030 1064

# 1600x1200 @ 70 Hz, 87.50 kHz hsync
Modeline "1600x1200"  189    1600 1664 1856 2160  1200 1201 1204 1250 -HSync -VSync
# 1152x864 @ 100 Hz, 89.62 kHz hsync
Modeline "1152x864"   137.65 1152 1184 1312 1536   864  866  885  902 -HSync -VSync
# 1280x1024 @ 85 Hz, 91.15 kHz hsync
Modeline "1280x1024"  157.5  1280 1344 1504 1728  1024 1025 1028 1072 +HSync +VSync
# 1600x1200 @ 75 Hz, 93.75 kHz hsync
Modeline "1600x1200"  202.5  1600 1664 1856 2160  1200 1201 1204 1250 +HSync +VSync
# 1600x1200 @ 85 Hz, 105.77 kHz hsync
Modeline "1600x1200"  220    1600 1616 1808 2080  1200 1204 1207 1244 +HSync +VSync
# 1280x1024 @ 100 Hz, 107.16 kHz hsync
Modeline "1280x1024"  181.75 1280 1312 1440 1696  1024 1031 1046 1072 -HSync -VSync

# 1800x1440 @ 64Hz, 96.15 kHz hsync
ModeLine "1800X1440"  230    1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# 1800x1440 @ 70Hz, 104.52 kHz hsync
ModeLine "1800X1440"  250    1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync

# 512x384 @ 78 Hz, 31.50 kHz hsync
Modeline "512x384"    20.160 512  528  592  640   384  385  388  404 -HSync -VSync
# 512x384 @ 85 Hz, 34.38 kHz hsync
Modeline "512x384"    22     512  528  592  640   384  385  388  404 -HSync -VSync

# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.

# 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio
Modeline "320x200"     12.588 320  336  384  400   200  204  205  225 Doublescan
# 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio
Modeline "320x240"     12.588 320  336  384  400   240  245  246  262 Doublescan
# 320x240 @ 72 Hz, 36.5 kHz hsync
Modeline "320x240"     15.750 320  336  384  400   240  244  246  262 Doublescan
# 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio
ModeLine "400x300"     18     400  416  448  512   300  301  302  312 Doublescan
# 400x300 @ 60 Hz, 37.8 kHz hsync
Modeline "400x300"     20     400  416  480  528   300  301  303  314 Doublescan
# 400x300 @ 72 Hz, 48.0 kHz hsync
Modeline "400x300"     25     400  424  488  520   300  319  322  333 Doublescan
# 480x300 @ 56 Hz, 35.2 kHz hsync, 8:5 aspect ratio
ModeLine "480x300"     21.656 480  496  536  616   300  301  302  312 Doublescan
# 480x300 @ 60 Hz, 37.8 kHz hsync
Modeline "480x300"     23.890 480  496  576  632   300  301  303  314 Doublescan
# 480x300 @ 63 Hz, 39.6 kHz hsync
Modeline "480x300"     25     480  496  576  632   300  301  303  314 Doublescan
# 480x300 @ 72 Hz, 48.0 kHz hsync
Modeline "480x300"     29.952 480  504  584  624   300  319  322  333 Doublescan


EndSection



# **********************************************************************
# Graphics device section
# **********************************************************************

Section "Device"
    Identifier "Generic VGA"
    Chipset   "generic"
EndSection

Section "Device"
    Identifier  ""
    VendorName  "Unknown"
    BoardName   "Unknown"
#    VideoRam    16384
    # Clock lines


    # Uncomment following option if you see a big white block        
    # instead of the cursor!                                          
    #    Option      "sw_cursor"

    Option      "power_saver"
EndSection



# **********************************************************************
# Screen sections
# **********************************************************************


# The Colour SVGA server

Section "Screen"
    Driver "svga"
    Device      "Generic VGA"
    Monitor     "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    Subsection "Display"
        Depth       8
        Modes       "320x200"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
    Driver "vga16"
    Device      "Generic VGA"
    Monitor     "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    Subsection "Display"
        Modes       "640x480" "800x600"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
    Driver "vga2"
    Device      "Generic VGA"
    Monitor     "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    Subsection "Display"
        Modes       "640x480" "800x600"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
    Driver "accel"
    Device      ""
    Monitor     "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    DefaultColorDepth 16
    Subsection "Display"
        Depth       8
        Modes       "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       15
        Modes       "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

Section "Screen"
    Driver "fbdev"
    Device      ""
    Monitor     "Generic|High Frequency SVGA, 1024x768 at 70 Hz"
    DefaultColorDepth 16
    Subsection "Display"
        Depth       8
        Modes       "default"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       15
        Modes       "default"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "default"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "default"
        ViewPort    0 0
    EndSubsection
EndSection

==============258B4C0FD28124C8B29842A4==


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list by posting to comp.os.linux.hardware.

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Hardware Digest
******************************

Reply via email to