Linux-Hardware Digest #777, Volume #10 Fri, 16 Jul 99 08:13:25 EDT
Contents:
Re: X on Compaq Laptop (Quinn Coldiron)
has no current->timeout structure in kernel 2.2.X? ("robert_c")
Re: has no current->timeout structure in kernel 2.2.X? ("Moors, ing. E.W.J.")
Re: Newbie to two monitors&video cards.....looking for suggestions (Jason L Michael)
linux driver for AMD's pcNet-FAST III chip? ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: Quinn Coldiron <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,linux.redhat.install
Subject: Re: X on Compaq Laptop
Date: Thu, 15 Jul 1999 07:46:01 -0500
Reply-To: [EMAIL PROTECTED]
smith wrote:
>
> I am trying to get x to work correctly on a Compaq Armada 1750 laptop. It
> has an ATI Rage PRO LT chipset. The display seems to work fine, but it is
> appears in the left of the screen, and doesnt display the right end. I have
> tried the SVGA and Mach64 servers with the same result, and have tried
> various monitor settings.
>
> If anyone knows how its done drop me a line at
> [EMAIL PROTECTED]
I've got an Armada 7400 and I'm using the SVGA server. I have found it
runs best at 1024x768. anything lower gets really jagged.
Here's my XF86Config:
# File generated by XConfigurator.
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 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
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 500 5
# 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(pc101)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc101"
XkbLayout "us"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "ps/2"
Device "/dev/mouse"
# Protocol "Microsoft"
# Device "/dev/cua0"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Protocol "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice
# BaudRate 9600
# SampleRate 150
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
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 Multisync"
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 30-120
# 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-120
# 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
# 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
Modeline "1280x1024" 110 1280 1328 1512 1712 1024 1025 1028 1054
# 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
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "Generic VGA"
VendorName "Unknown"
BoardName "Unknown"
Chipset "generic"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by Xconfigurator:
Section "Device"
Identifier "Millennium II"
VendorName "Unknown"
BoardName "Unknown"
VideoRam 8192
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
# Use Device "Generic VGA" for Standard VGA 320x200x256
#Device "Generic VGA"
Device "Millennium II"
Monitor "Generic Multisync"
Subsection "Display"
Depth 16
# It will run in 24, but WordPerfect and the
# RealMedia 5.0 player don't work well
# Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
#
# This setting is from my desktop machine that uses this file also
#
# The accelerated servers (S3, Mach32, Mach8, 8514, P9000, AGX, W32,
Mach64
# I128, and S3V)
Section "Screen"
Driver "accel"
Device "Millennium II"
Monitor "Generic Multisync"
Subsection "Display"
Depth 32
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
------------------------------
From: "robert_c" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development.system
Subject: has no current->timeout structure in kernel 2.2.X?
Date: 16 Jul 1999 09:47:20 GMT
Hi:
I have a problem in porting code from kernel 2.0.X to 2.2.X.
In 2.0.X, I need a blocking function to do time deleayed and it was
implemented like following .
(Delay 3 second)
...
...
int delay_second = 3;
unsigned long total_jiffies = jiffies + delay_second *HZ;
...
current->timeout = total_jiffies; //<-- has no current->timeout data
structure in kernel 2.2.X?
current->state = TASK_INTERRUPTIBLE;
schedule();
current->timeout = 0; // (reset the timeout) the error like above, <-- has
no current->timeout data structure in kernel 2.2.X?
...
...
...
But, while I compile in kernel 2.2.X, it always says (structure *current has
no member named "timeout")
My question is that the 2.2.X kernel has some other API (or data
structure, like global variable) to do something like above? If yes, how to
do that?
------------------------------
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development.system
From: "Moors, ing. E.W.J." <[EMAIL PROTECTED]>
Subject: Re: has no current->timeout structure in kernel 2.2.X?
Date: Fri, 16 Jul 1999 10:26:21 GMT
robert_c wrote:
>
> Hi:
> I have a problem in porting code from kernel 2.0.X to 2.2.X.
> In 2.0.X, I need a blocking function to do time deleayed and it was
> implemented like following .
>
> (Delay 3 second)
> ...
> ...
> int delay_second = 3;
> unsigned long total_jiffies = jiffies + delay_second *HZ;
> ...
>
> current->timeout = total_jiffies; //<-- has no current->timeout data
> structure in kernel 2.2.X?
> current->state = TASK_INTERRUPTIBLE;
> schedule();
> current->timeout = 0; // (reset the timeout) the error like above, <-- has
> no current->timeout data structure in kernel 2.2.X?
> ...
> ...
> ...
>
> But, while I compile in kernel 2.2.X, it always says (structure *current has
> no member named "timeout")
>
> My question is that the 2.2.X kernel has some other API (or data
> structure, like global variable) to do something like above? If yes, how to
> do that?
I ran in to the same problem as you did, the new calls are
current->state = TASK_INTERRUPTIBLE;
schedule_timeout(JIFFIES);
Eric
------------------------------
From: Jason L Michael <[EMAIL PROTECTED]>
Subject: Re: Newbie to two monitors&video cards.....looking for suggestions
Date: Fri, 16 Jul 1999 10:31:04 GMT
w8tn4g0d0t wrote:
> Hi all. I've been using linux for a while now(apparently not long
> enough), and recently for my 95 partition added a voodoo 3 2000 PCI
> card. The voodoo works aok in win95, though I want to continue to use
> my ATI Mach64 video card under linux, as it's already setup and
> using/configured for x. The problem I've run in to is this: with
> primary monitor plugged in to the Voodoo3 card's connector, and my
> secondary monitor is plugged in to the Mach64 by way of the
> mamaboard's video.(ati chip is on-board) What I get in linux (suse) is
> this: Linux is using/reckognizing the
> Voodoo3 card, which is fine, but I guess I'm interested in the what
> for me is a challenge of getting suse to use the "other" card, the
> Mach64 card. My question is: how do I configure suse to use the Mach64
> card and monitor, not the Voodoo3?
> I'm here today posting to admit that I'm a little confused about what
> I need to do in order to have suse continue using the Mach64 card. I
> would imagine it it's a simple conf file with the appropriatte /dev
> link, but maybe not...?
> Can anyone point me in the direction of some documentation I should be
> reading?
> (I looked over the HOW-TO and Mini-How-To's and can't find a
> two-monitor-two-video-card how-to....I'm conducting searches at suse,
> the hardware and support database, and the linux hardware database,
> and am looking over the LDP, and have been unable to find any
> documentation. Anybody have any links to share?
>
> Thanks very much in advance.
> Jonathan
>
Jonathan,
My little brother's name is Jonathan. Nice to know you.
You set the primary video card in the BIOS (unfortunately). I don't think
there's a way to get around this. What I would do is set up the voodoo
card as the primary (under BIOS), and see if you can set up the onboard ATI
card as the secondary card (i.e. not primary). This should be OK with
Win98, and Linux might use the BIOS settings and use the ATI card. Also,
Linux might look at cards in a particular order, stopping at the first
acceptable card it finds (like the BeOS does), so you might need to move
the voodoo card around to get it so be seen after the ATI card.
Good luck, and tell me how it goes. I'll be moving to [EMAIL PROTECTED]
as soon as they start accepting new customers again (it's free POP3
e-mail).
JLM
P.S.: If all else fails, you might need to _disable_ the ATI card (again,
in the BIOS) and get a cheap replacement. Mach64 cards sell for under
$50 where I live.
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED]
Subject: linux driver for AMD's pcNet-FAST III chip?
Date: Fri, 16 Jul 1999 10:40:46 GMT
Hi,
I'm looking for a linux-driver for boards with AMD's new pcNet-FAST III
ethernet-controllers, which provide a 100/10Base-T port.
The exact names of the chips are AM79C973 or AM79C975 resp.
Does anyone know, if such a driver exists and where to find?
thanks
Martin
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
** 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 (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
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
******************************
