Linux-Setup Digest #692, Volume #20 Fri, 23 Feb 01 12:13:09 EST
Contents:
Re: Charger un module au demarrage de LINUX (Jean-Marie DELAPIERRE)
Re: Looking for modelines for ViewSonic A70 ("Gene Heskett")
Re: Installation appears to freeze!! Please help ("Wayne Howarth")
Re: how to run windows apps on linux (Roman Fietze)
What platforms are supported for the 1.2.2 SDK? ("Thomas Paine")
Re: how to run windows apps on linux (Rod Smith)
Re: Ximian upgrade on Debian/Stormix - Stuck at login (Leonard Stiles)
what do i do?? ("r")
Error when mounting SCSI ZIP Disk ("Jared R. Jones")
Re: Looking for modelines for ViewSonic A70 (Ross Jordan)
man -k ? ("Chris Coyle")
What do you folks 'make' of this: ipchains in kernel 2.2.7-14 RH7 (David Cecere)
HOW TO UNINSTALL APACHE ("airsupply")
Re: LILO problem ("Phil Windell")
----------------------------------------------------------------------------
From: Jean-Marie DELAPIERRE <[EMAIL PROTECTED]>
Crossposted-To: fr.comp.os.linux.configuration
Subject: Re: Charger un module au demarrage de LINUX
Date: 23 Feb 2001 14:00:36 GMT
syco a �crit :
> J'ai une carte SCSI Adaptec aha1540.
> LINUX ne reconnaissant pas cette carte en natif, Pour reconnaitre mes
> disques il faut charger le module aha1542 ( par modprobe aha1540
> aha1540=0x230 ).
>
> A la main �a marche.
> Comment faire pour que ce module soit charg� automatiquement AVANT le
> montage des file systems ?
> - j'ai jet� un oeil dans /etc/modules.conf mais je n'ai pas trouv� la
> logique
> - j'ai lu man sur modules, rc.d, insmod, init, .... je suis trop boeu
> peut-�tre, mais je n'ai pas trouv� d'explication claire sur ce que je veux
> faire.
>
> En SUSE 7.0
> Merci d'avance.
>
> --
> SYCO
> de Sycoweb
> ( BROCANTES DU NORD-EST http://www.chez.com/sycoweb/puces/index.htm )
> - Let me Alone but not Forever -
Bonjour,
Essaye d'ajouter dans /etc/modules.conf la ligne modprobe aha1540
aha1540=0x230
Cordialement.
Jean-Marie
------------------------------
Date: 23 Feb 2001 8:45:19 -0500
From: "Gene Heskett" <[EMAIL PROTECTED]>
Subject: Re: Looking for modelines for ViewSonic A70
Crossposted-To: comp.os.linux.x
Gene Heskett sends Greetings to Joe Mason;
JM> Hi,
JM> I'm running XFree86 4.0.2, with a ViewSonic A70 monitor and an NVidia
JM> TNT2.
JM> (Using the basic nv driver - gonna get this working before trying
JM> accelerated).
JM> I can't get X to display at 1280x1024 - 1024x768 is the highest I can do.
JM> I suspect I have to put an explicit modeline in the config file in order
JM> to get this resolution, but I'm not sure what values to use. I've lost
JM> the monitor manual, so I can't get detailed modelines for it
JM> (although I don't think the manual had all that much technical detail
JM> anyway).
JM> The only tech specs I could find are at
JM> http://www.red.it/pnp/monitor/a/a70.pdf (text version at
JM> http://www.google.com/search?q=cache:www.red.it/pnp/monitor/a/a70.pdf+Vie
JM> wSonic+A70+refresh+rate). The pertinent info is:
JM> * 1,280 x 1,024 maximum resolution
JM> Displays a maximum resolution of 1,280 x 1,024; 1,024 x 768 at 87Hz
JM> flicker-free refresh rate for easy viewing.
JM> 1,280 x 1,024 @ 166Hz
JM> 1,024 x 768 @ 187Hz
JM> 800 x 1,600 @ 110Hz
JM> 640 x 1,480 @ 135Hz
JM> <snip>
JM> Frequency Fh:30-70kHz, Fv:50-180Hz
JM> Anyway, I put these into the XF86Config file hoping it would fill in the
JM> correct modelines automagically:
JM> Section "Monitor"
JM> Identifier "ViewSonic A70"
JM> HorizSync 30-70
JM> VertRefresh 50-180
JM> EndSection
JM> Section "Screen"
JM> ...
JM> Subsection "Display"
JM> Depth 24
JM> Modes "1024x768" "1280x1024"
JM> EndSection
JM> At 1024x768 everything works fine, but at 1280x1024 the screen simply
JM> blanks out.
This is probably the monitors reaction to an Fh that is beyond its
capabilities. Take a read of the man pages, but I think its trying to
use too high a dot clock, which in turn give an overrange of Fh. Doing
1280x1024 at any refresh thats not too flickery is going to give an Fh
rate that pushed a 70khz monitor to the limits. I do that here, but
with about 20hz less Fv to keep the Fh within my NEC 5FG's comfortable
range.
JM> I noticed some interesting things in the startup log. In one block,
JM> which I'm not sure exactly how to interpret, the highest listed mode was
JM> 1152x870, so I tried that instead. Here's the output from that:
JM> (II) NV(0): I2C bus "DDC" initialized.
JM> (II) NV(0): I2C device "DDC:ddc2" registered.
JM> (II) NV(0): I2C device "DDC:ddc2" removed.
JM> (II) NV(0): I2C device "DDC:ddc2" registered.
JM> (II) NV(0): I2C device "DDC:ddc2" removed.
JM> (II) NV(0): DDC Monitor info: 0x84e7dd8
JM> (II) NV(0): Manufacturer: VSC Model: 5a43 Serial#: 8264
JM> (II) NV(0): Year: 1999 Week: 29
JM> (II) NV(0): EDID Version: 1.2
JM> (II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
JM> (II) NV(0): Signal levels configurable
JM> (II) NV(0): Sync: Separate CompositeSerration on. V.Sync Pulse req. if
JM> CompSync or SyncOnGreen
JM> (II) NV(0): Max H-Image Size [cm]: horiz.: 32 vert.: 24
JM> (II) NV(0): Gamma: 2.80
JM> (II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
JM> (II) NV(0): First detailed timing is preferred mode
JM> (II) NV(0): GTF timings supported
JM> (II) NV(0): redX: 0.652 redY: 0.321 greenX: 0.281 greenY: 0.616
JM> (II) NV(0): blueX: 0.141 blueY: 0.057 whiteX: 0.283 whiteY: 0.297
JM> (II) NV(0): Supported VESA Video Modes:
JM> (II) NV(0): 720x400@70Hz
JM> (II) NV(0): 720x400@88Hz
JM> (II) NV(0): 640x480@60Hz
JM> (II) NV(0): 640x480@67Hz
JM> (II) NV(0): 640x480@72Hz
JM> (II) NV(0): 640x480@75Hz
JM> (II) NV(0): 800x600@56Hz
JM> (II) NV(0): 800x600@60Hz
JM> (II) NV(0): 800x600@72Hz
JM> (II) NV(0): 800x600@75Hz
JM> (II) NV(0): 832x624@75Hz
JM> (II) NV(0): 1024x768@87Hz (interlaced)
JM> (II) NV(0): 1024x768@60Hz
JM> (II) NV(0): 1024x768@70Hz
JM> (II) NV(0): 1024x768@75Hz
JM> (II) NV(0): 1152x870@75Hz
JM> (II) NV(0): Manufacturer's mask: 0
JM> (II) NV(0): Supported Future Video Modes:
JM> (II) NV(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
JM> (II) NV(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
JM> (II) NV(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
JM> (II) NV(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
JM> (II) NV(0): #4: hsize: 1280 vsize 960 refresh: 60 vid: 16513
JM> (II) NV(0): #5: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
JM> (II) NV(0): Supported additional Video Mode:
JM> (II) NV(0): clock: 78.8 MHz Image Size: 310 x 232 mm
JM> (II) NV(0): h_active: 1024 h_sync: 1040 h_sync_end 1136 h_blank_end
JM> 1312 h_border: 0
JM> (II) NV(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 800
JM> v_border: 0
JM> (II) NV(0): Serial No: CZ92908264
JM> Notice 1152x870 is the highest listed "real" video mode: 1280x1024 is
JM> listed as "Future". Does this mean that the driver doesn't support it,
JM> even though the monitor does?
JM> It continues:
JM> (II) NV(0): Ranges: V min: 50 V max: 180 Hz, H min: 30 H max: 70 kHz,
JM> PixClock max 100 kHz
======================^ I hope this was an 'm'!
JM> (II) NV(0): Monitor name: A70
JM> (II) NV(0): end of DDC Monitor info
JM>
JM> (==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
JM> (II) NV(0): ViewSonic A70: Using hsync range of 30.00-70.00 kHz
JM> (II) NV(0): ViewSonic A70: Using vrefresh range of 50.00-180.00 Hz
JM> (II) NV(0): Clock range: 12.00 to 350.00 MHz
JM> (WW) NV(0): Default mode "1280x960" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1280x1024" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1280x1024" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1792x1344" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1792x1344" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1856x1392" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1856x1392" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1920x1440" deleted (hsync out of range)
JM> (WW) NV(0): Default mode "1920x1440" deleted (hsync out of range)
JM> (WW) NV(0): Mode "1152x870" deleted (no mode of this name)
Meaning there is not a modeline that matches this in the config file.
Note that the deletions are caused by the hsync being out of range,
most are probably well above 70khz.
JM> (--) NV(0): Virtual size is 1024x768 (pitch 1024)
JM> (**) NV(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
JM> (++) NV(0): DPI set to (100, 100)
JM> So it seems to me that the 1280x960 and 1280x1024 modes should be usable,
JM> but X's defaults have too high an hsync, and failing that, 1152x870
JM> should be usable except that X doesn't know about it. Either way I have
JM> to come up with a modeline, but I don't know how to convert
JM> "1280x1024@60Hz" into all the different values X is expecting. Can
JM> someone tell me how to do this (or provide an alternate explanation of
JM> the above logs)?
Yup, read the man pages and figure out which figure in each of the
modelines is the dot clock. As Fv is 85.0 hz, you have plenty of room
to slow the dot clock down without running into objectionable diplay
flicker. Go thru the modelines and reduce the dotclock to about 65/85ths
of its present value and try it again. Almost, if not all else, scales
up and down with the dot clock, and this should get the Fh into your
monitors useable range.
Cheers, Gene
--
Gene Heskett, CET, UHK |Amiga A2k Zeus040, Linux @ 500mhz
email gene underscore heskett at iolinc dot net
#Amiga based X10 home automation program EZHome, see at:#
<http://www.thirdwave.net/~jimlucia/amigahomeauto>
This messages reply content, but not any previously quoted material,
is � 2001 by Gene Heskett, all rights reserved.
--
------------------------------
From: "Wayne Howarth" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,linux.redhat
Subject: Re: Installation appears to freeze!! Please help
Date: Fri, 23 Feb 2001 14:50:33 -0000
Many thanks for the quick reply. HGowever, since posting earlier today I
have successfully installed the Red Hat 6.2 distribution. I am now trying to
decide whether to try the RH 7 distribution again or perform an upgrade from
6.2 to 7.0. Is this option possible? If so I guess I'll need to
download/obtain an upgrade CD?
Wayne.
"Nils O. Sel�sdal" <[EMAIL PROTECTED]> wrote in message
news:1lql6.4983$[EMAIL PROTECTED]...
>
> "Wayne Howarth" <[EMAIL PROTECTED]> wrote in message
> news:97580v$8eh$[EMAIL PROTECTED]...
> > Please help. I have been trying to install the Red Hat 7 distribution
for
> > most of the afternoon however I am finding that about 20% through the
> > installation the computer just hangs. The installation screen is still
> > visible and the mouse seems to respond by moving around the screen.
> try the text installation modus..
> also look in the terminals for output messages if you can, press CTRL+ALT
+
> F1 to F7
>
>
------------------------------
From: Roman Fietze <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.caldera,comp.os.linux.hardware
Subject: Re: how to run windows apps on linux
Date: 23 Feb 2001 14:07:22 +0100
Mohammed Khalid Ansari <[EMAIL PROTECTED]> writes:
> Can anybody tell me how do I run windows applications on Linux? Where do I
> get the required software or libraries?
vmWare
Win4Lin
WINE
dosemu (Win 3.11 only?)
native port :)
I do not have the URL's at hand, but they should be easy to find.
Roman
--
Roman Fietze (Mail Code 6) [EMAIL PROTECTED]
Heidelberg Digital Finishing GmbH, Germany DDF-T SWEC ESW
------------------------------
From: "Thomas Paine" <[EMAIL PROTECTED]>
Crossposted-To: comp.lang.java.machine,comp.lang.java.programmer
Subject: What platforms are supported for the 1.2.2 SDK?
Date: Fri, 23 Feb 2001 08:52:55 -0600
Reply-To: "Thomas Paine" <[EMAIL PROTECTED]>
Does the SDK support Linux running on a Sparc station? I see Linux/x86
or Solaris/Sparc, but no Linux/Sparc.
--
Thanks,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thomas Paine ([EMAIL PROTECTED])
University of Wisconsin - Eau Claire
Computing & Networking Services
Famous Last Words
"Did you hear thunder? Oh well hurry up and putt." (JD)
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Crossposted-To: alt.os.linux.caldera,comp.os.linux.hardware
Subject: Re: how to run windows apps on linux
Date: Fri, 23 Feb 2001 15:15:15 -0000
Reply-To: [EMAIL PROTECTED]
[Posted and mailed]
In article <[EMAIL PROTECTED]>,
Mohammed Khalid Ansari <[EMAIL PROTECTED]> writes:
>
> Can anybody tell me how do I run windows applications on Linux? Where do I
> get the required software or libraries?
I know of at least six ways to do this, and I'm sure there are or will
be more:
1) Use WINE. This is an open source re-implementation of the Windows
API running in Linux. It's still alpha quality, but it's getting to
the point where at least some "serious" Windows programs will run.
The homepage is http://www.winehq.com.
2) Use VMware. This is a program that emulates a complete x86 PC, so you
can install and run any version of Windows you like. It's something
of a CPU hog, though. Its Web site is http://www.vmware.com. This is
commercial software.
3) Use Win4Lin. This is in-between WINE and VMware; it's a partial x86
emulator that lets you run Windows 95 or 98, but not other version of
Windows, or any other OS. Read more at http://www.netraverse.com.
This is commercial software.
4) Run Win-OS/2 3.1 using DOSEMU. DOSEMU is a DOS emulator for Linux
(or more precisely, a limited x86 machine emulator in which DOS can
run). I've seen reports that Win-OS/2, the recompiled version of
Windows 3.1 that ships with some versions of IBM's OS/2, can run in
this environment. I've not tried it, though, and I don't have any
URLs for instructions offhand. This will run only 16-bit Windows
applications, or at best Win32s programs.
5) Use Willows TWIN. This is similar to WINE in principle, but I've
never used it, and I don't believe it's as popular. Its Web page is
http://www.willows.com.
6) Use WABI. This is a discontinued commercial product that allowed
Linux to run Windows 3.1, IIRC. Sun created it originally, but the
Linux version was licensed by Caldera.
I've used the first three options. Of those, Win4Lin is best if you
want to get the best speed and reliability out of several productivity
programs. VMware is best if you need certain OS features not supported
by WINE or Win4Lin, or if you need to run Windows NT, 2000, or Me
specifically. WINE may be good if the applications you want to run are
supported by it.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
Crossposted-To: linux.debian.user
Subject: Re: Ximian upgrade on Debian/Stormix - Stuck at login
From: Leonard Stiles <[EMAIL PROTECTED]>
Date: Fri, 23 Feb 2001 15:43:59 GMT
[EMAIL PROTECTED] (Lacky) writes:
> So I just finished a fresh install of Hail and figured I would get
> Helix/Ximian Gnome up-to-date. So, after consulting the Ximian web
> site (www.ximian.org) for instructions on how to update Debian based
> systems, I typed the following as su:
>
> lynx -source http://go-gnome.com/ | sh
I've heard about this and I find the suggestion that one should grab a
script from the web and execute it as root without even looking at
what it contains somewhat questionable.
> Everything seemed to work just fine until I tried to reboot. I am now
> stuck in an endless cycle of login screens. If I try to login as
> either root or my personal account, the screen goes blank for a second
> as if the monitor was turned off and then I am simply returned to the
> login page to do it all over again. I simply cannot get past the login
> page.
This is a shot in the dark, but my guess is that the `login screens'
you refer to are gdm's (the gnome replacement for xdm). Gdm can be,
and in your case probably is configured to use PAM (pluggable
authentication modules) for all authentication handling. I presume the
problem is that the program that installed gdm did not install a pam
configuration file for gdm. If this is the case then you will not be
able to use gdm to log in.
Log in from the console as root (press <ctrl-alt-f1> from the gdm
screen to get to the console) and check if the file /etc/pam.d/gdm
exists. If it does not, you will have to create it. If you have an
/etc/pam.d/xdm file you could probably get away with just copying
it. Otherwise, you will have to write your own (refer to the PAM
documentation). FYI, my /etc/pam.d/gdm looks like this:
======= /etc/pam.d/gdm follows
#%PAM-1.0
auth required pam_nologin.so
auth required pam_env.so
auth required pam_unix_auth.so
account required pam_unix_acct.so
password required pam_unix_passwd.so shadow
session required pam_unix_session.so
======= End
If you already have a /etc/pam.d/gdm file, it may be that it is
syntactically invalid or corrupted in some way, which you would have
to fix. When you are done you will probably have to restart gdm.
HTH
--
Leonard Stiles <[EMAIL PROTECTED]>
------------------------------
From: "r" <[EMAIL PROTECTED]>
Subject: what do i do??
Date: Fri, 23 Feb 2001 16:03:27 GMT
Just wondering if anyone can tell me of a way to allow a Macintosh machineb
to talk to a machine with linux Os. I would like the linux machine to act
as a file server. The mac's will be running os9. I would appreciate it if
someone could tell me what to do on the linux end of things. I.E software
version, and steps to make this happen.
Thanks in advance
Rob.
------------------------------
From: "Jared R. Jones" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help
Subject: Error when mounting SCSI ZIP Disk
Date: Fri, 23 Feb 2001 11:15:57 -0500
Hello,
I have several ZIP disks that I use with Win98. I have an IOMEGA
ZIP-100 SCSI drive on
RedHat 6.2, Kernel 2.4.1. I have a symbolic link /dev/zip which points
to /dev/sdc4.
I tried mounting as root both the link and the real device with types
msdos, and vfat. Here is what I tried:
mount -t auto /dev/zip /mnt/zip
mount: /dev/zip is not a valid block device
mount -t vfat /dev/zip /mnt/zip
mount: /dev/zip is not a valid block device
mount -t auto /dev/zip /mnt/sdc4
mount: /dev/zip is not a valid block device
mount -t vfat /dev/zip /mnt/sdc4
mount: /dev/zip is not a valid block device
Thanks for any help!
Jared
------------------------------
From: Ross Jordan <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.os.linux.help,uw.linux
Subject: Re: Looking for modelines for ViewSonic A70
Date: Fri, 23 Feb 2001 11:28:14 -0500
Take a look at the following HOWTO.
http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/
-Ross
On 23 Feb 2001, Joe Mason wrote:
> Hi,
>
> I'm running XFree86 4.0.2, with a ViewSonic A70 monitor and an NVidia TNT2.
> (Using the basic nv driver - gonna get this working before trying
> accelerated).
>
> I can't get X to display at 1280x1024 - 1024x768 is the highest I can do.
> I suspect I have to put an explicit modeline in the config file in
> order to get this resolution, but I'm not sure what values to use.
> I've lost the monitor manual, so I can't get detailed modelines for it
> (although I don't think the manual had all that much technical detail
> anyway).
>
> The only tech specs I could find are at
> http://www.red.it/pnp/monitor/a/a70.pdf (text version at
>
>http://www.google.com/search?q=cache:www.red.it/pnp/monitor/a/a70.pdf+ViewSonic+A70+refresh+rate).
> The pertinent info is:
>
> * 1,280 x 1,024 maximum resolution
> Displays a maximum resolution of 1,280 x 1,024; 1,024 x 768 at 87Hz
> flicker-free refresh rate for easy viewing.
> 1,280 x 1,024 @ 166Hz
> 1,024 x 768 @ 187Hz
> 800 x 1,600 @ 110Hz
> 640 x 1,480 @ 135Hz
>
> <snip>
>
> Frequency Fh:30-70kHz, Fv:50-180Hz
>
> Anyway, I put these into the XF86Config file hoping it would fill in the
> correct modelines automagically:
>
> Section "Monitor"
> Identifier "ViewSonic A70"
> HorizSync 30-70
> VertRefresh 50-180
> EndSection
>
> Section "Screen"
> ...
> Subsection "Display"
> Depth 24
> Modes "1024x768" "1280x1024"
> EndSection
>
> At 1024x768 everything works fine, but at 1280x1024 the screen simply blanks
> out.
>
> I noticed some interesting things in the startup log. In one block, which
> I'm not sure exactly how to interpret, the highest listed mode was 1152x870,
> so I tried that instead. Here's the output from that:
>
> (II) NV(0): I2C bus "DDC" initialized.
> (II) NV(0): I2C device "DDC:ddc2" registered.
> (II) NV(0): I2C device "DDC:ddc2" removed.
> (II) NV(0): I2C device "DDC:ddc2" registered.
> (II) NV(0): I2C device "DDC:ddc2" removed.
> (II) NV(0): DDC Monitor info: 0x84e7dd8
> (II) NV(0): Manufacturer: VSC Model: 5a43 Serial#: 8264
> (II) NV(0): Year: 1999 Week: 29
> (II) NV(0): EDID Version: 1.2
> (II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
> (II) NV(0): Signal levels configurable
> (II) NV(0): Sync: Separate CompositeSerration on. V.Sync Pulse req. if
> CompSync or SyncOnGreen
> (II) NV(0): Max H-Image Size [cm]: horiz.: 32 vert.: 24
> (II) NV(0): Gamma: 2.80
> (II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
> (II) NV(0): First detailed timing is preferred mode
> (II) NV(0): GTF timings supported
> (II) NV(0): redX: 0.652 redY: 0.321 greenX: 0.281 greenY: 0.616
> (II) NV(0): blueX: 0.141 blueY: 0.057 whiteX: 0.283 whiteY: 0.297
> (II) NV(0): Supported VESA Video Modes:
> (II) NV(0): 720x400@70Hz
> (II) NV(0): 720x400@88Hz
> (II) NV(0): 640x480@60Hz
> (II) NV(0): 640x480@67Hz
> (II) NV(0): 640x480@72Hz
> (II) NV(0): 640x480@75Hz
> (II) NV(0): 800x600@56Hz
> (II) NV(0): 800x600@60Hz
> (II) NV(0): 800x600@72Hz
> (II) NV(0): 800x600@75Hz
> (II) NV(0): 832x624@75Hz
> (II) NV(0): 1024x768@87Hz (interlaced)
> (II) NV(0): 1024x768@60Hz
> (II) NV(0): 1024x768@70Hz
> (II) NV(0): 1024x768@75Hz
> (II) NV(0): 1152x870@75Hz
> (II) NV(0): Manufacturer's mask: 0
> (II) NV(0): Supported Future Video Modes:
> (II) NV(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
> (II) NV(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
> (II) NV(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
> (II) NV(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
> (II) NV(0): #4: hsize: 1280 vsize 960 refresh: 60 vid: 16513
> (II) NV(0): #5: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
> (II) NV(0): Supported additional Video Mode:
> (II) NV(0): clock: 78.8 MHz Image Size: 310 x 232 mm
> (II) NV(0): h_active: 1024 h_sync: 1040 h_sync_end 1136 h_blank_end 1312
> h_border: 0
> (II) NV(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 800
> v_border: 0
> (II) NV(0): Serial No: CZ92908264
>
> Notice 1152x870 is the highest listed "real" video mode: 1280x1024 is listed
> as "Future". Does this mean that the driver doesn't support it, even though
> the monitor does?
>
> It continues:
>
> (II) NV(0): Ranges: V min: 50 V max: 180 Hz, H min: 30 H max: 70 kHz,
> PixClock max 100 kHz
> (II) NV(0): Monitor name: A70
> (II) NV(0): end of DDC Monitor info
>
> (==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
> (II) NV(0): ViewSonic A70: Using hsync range of 30.00-70.00 kHz
> (II) NV(0): ViewSonic A70: Using vrefresh range of 50.00-180.00 Hz
> (II) NV(0): Clock range: 12.00 to 350.00 MHz
> (WW) NV(0): Default mode "1280x960" deleted (hsync out of range)
> (WW) NV(0): Default mode "1280x1024" deleted (hsync out of range)
> (WW) NV(0): Default mode "1280x1024" deleted (hsync out of range)
> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) NV(0): Default mode "1600x1200" deleted (hsync out of range)
> (WW) NV(0): Default mode "1792x1344" deleted (hsync out of range)
> (WW) NV(0): Default mode "1792x1344" deleted (hsync out of range)
> (WW) NV(0): Default mode "1856x1392" deleted (hsync out of range)
> (WW) NV(0): Default mode "1856x1392" deleted (hsync out of range)
> (WW) NV(0): Default mode "1920x1440" deleted (hsync out of range)
> (WW) NV(0): Default mode "1920x1440" deleted (hsync out of range)
> (WW) NV(0): Mode "1152x870" deleted (no mode of this name)
> (--) NV(0): Virtual size is 1024x768 (pitch 1024)
> (**) NV(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
> (++) NV(0): DPI set to (100, 100)
>
> So it seems to me that the 1280x960 and 1280x1024 modes should be usable,
> but X's defaults have too high an hsync, and failing that, 1152x870 should
> be usable except that X doesn't know about it. Either way I have to come up
> with a modeline, but I don't know how to convert "1280x1024@60Hz" into all
> the different values X is expecting. Can someone tell me how to do this (or
> provide an alternate explanation of the above logs)?
>
> Thanks,
> Joe
>
>
------------------------------
From: "Chris Coyle" <[EMAIL PROTECTED]>
Subject: man -k ?
Date: Fri, 23 Feb 2001 11:53:29 -0500
Since I installed RH6.2 a few weeks ago,
I have never been able to get "man -k ..."
(or "apropos...") to do anything.
Did I miss some part of installation?
------------------------------
From: David Cecere <[EMAIL PROTECTED]>
Subject: What do you folks 'make' of this: ipchains in kernel 2.2.7-14 RH7
Date: Fri, 23 Feb 2001 11:11:54 -0500
Reply-To: [EMAIL PROTECTED]
Greetings,
RH tech support refused to address this as a post-install issue. I was
trying to recompile my kernel to support ipchains and this is what make
tells me:
make[3]: Entering directory `/usr/src/linux-2.2.17/net/ipv4' kgcc
-D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686
-DEXPORT_SYMTAB -c ip_masq.c ip_masq.c:578: `ip_masq_hash' undeclared here
(not in a function) ip_masq.c:578: initializer element for
`__ksymtab_ip_masq_hash.value' is not constant ip_masq.c:579:
`ip_masq_unhash' undeclared here (not in a function) ip_masq.c:579:
initializer element for `__ksymtab_ip_masq_unhash.value' is not constant
ip_masq.c:518: warning: `masq_port_lock' defined but not used make[3]: ***
[ip_masq.o] Error 1 make[3]: Leaving directory
`/usr/src/linux-2.2.17/net/ipv4' make[2]: *** [first_rule] Error 2 make[2]:
Leaving directory `/usr/src/linux-2.2.17/net/ipv4' make[1]: ***
[_subdir_ipv4] Error 2 make[1]: Leaving directory
`/usr/src/linux-2.2.17/net' make: *** [_dir_net] Error 2
_____________________________________________________________________________
"Thinking is, or ought to be, a coolness and a calmness; and our poor hearts
throb, and our poor brains beat too much for that."--Herman Melville
My r�sum� and etc.: http://4.34.161.50/
------------------------------
From: "airsupply" <[EMAIL PROTECTED]>
Subject: HOW TO UNINSTALL APACHE
Date: Fri, 23 Feb 2001 18:01:43 -0800
i would like to uninstall apache; can i do it ??
and how ??
apache was installed with apache.x.tar.gz
thanks
------------------------------
From: "Phil Windell" <[EMAIL PROTECTED]>
Subject: Re: LILO problem
Date: Fri, 23 Feb 2001 11:05:19 -0600
"Patrick Fisher" <[EMAIL PROTECTED]> wrote in message
news:9743ta$dg3$[EMAIL PROTECTED]...
>
> "Alim" <[EMAIL PROTECTED]> wrote in message
> news:971bbt$slb$[EMAIL PROTECTED]...
>
> > Now the only way I can get to boot windows is to change the boot device
in
> > the bios, which is not much good. Does anyone know how I can get either
> the
> > win2k bootloader to load LILO, or preferably LILO to boot the win2k
> > bootloader?
All you need is a little (free) utility called BootPart. I guess it's short
for boot partition. It sets up the NT boot loader to duel boot with Linux no
matter what partition or driver you installed it in. Nothing changes if your
using Win2k.
You install LILO to the "master block" of the partition it is on. At this
point neither OS needs to be aware of the other's existence. You copy the
BootPart.exe file to the NT boot partition (usually C:)
Using a command prompt window in NT run BootPart twice. First time it reads
all partitions and drives and numbers the various OSs that it finds begining
with 0. You then run it again with the number. For example, if your main
Linux partition is numberd as "2" by BootPart, then you would type:
"BootPart 2 bootsect.lnx Linux"
The "bootsect" file is created by BootSect and is the file NT's boot loader
needs to know how to switch to Linux's partition. The "Linux" is jst the
description that goes in the Boot.ini file. Make sure the bootsect.* file is
in the root and the boot.ini path to it is correct. It may work in other
locations, but I like to keep it in the root of C:
The normal zip file name for it is "bootpa22.zip". If you can't find it
anywhere, I can e-mail it to you.
--
Phillip Windell (MCP)
[EMAIL PROTECTED]
WAND TV
www.wandtv.com
------------------------------
** 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.setup.
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-Setup Digest
******************************
