Linux-Hardware Digest #752, Volume #14 Thu, 10 May 01 09:13:03 EDT
Contents:
Re: CD Writer for Linux (ram2500)
Re: where are the modem settings held? ("stevek")
Re: parallel port programming for linux? ("The Snowman")
Re: Tape drive installation problem (Joshua Baker-LePain)
Re: Fire GL 4000 (KegBot)
Re: smart card readers (serial probably) ("Adam Short")
Re: IBM Thinkpad 600E power switch change.. ("The Snowman")
----------------------------------------------------------------------------
From: ram2500 <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: CD Writer for Linux
Date: Thu, 10 May 2001 11:10:59 GMT
Charles Stevenson wrote:
> Where do you go to find CD-RWs that will work with Linux? ( Intel
> Pentium II, 233 MHz, Redhat Linux 6.2. , Purpose: system backup &
> recovery, soley. )
>
> The local CompUSA & internet searches show reveal several reasonable
> Windows-compatible choices, but none that I've seen claim that they will
> will work with Linux.
my smart & freindly works with rh 7.1
------------------------------
From: "stevek" <skortjohnatmetrolinkdotnet>
Subject: Re: where are the modem settings held?
Date: Thu, 10 May 2001 07:28:44 -0400
problem solved....I put the modem in a windows box and it does not work
there either...I bought another and everything gets detected and works fine.
=====
"stevek" <skortjohnatmetrolinkdotnet> wrote in message
news:9d65o7$[EMAIL PROTECTED]...
> I have an internal pci usrobotics modem. It had been working ok since
> putting the pc together (about 3 weeks) and then stopped working
yesterday.
> I am using redhat 7.1. I have tried physically removing and reinstalling
> the modem. Each time linux notes the correct modem and asks if I want to
> remove configuration settings or set up the modem, depending on whether I
am
> putting or taking. When I try redetecting or setting up the modem, I get
> "no modem found" messages. I do not think I did anything to confuse the
> matter, and had no problems during initial linux installation. I thought
if
> I found all of the relevant configuration files and commented out setting
> for the modem, I could then try to redetect/configure from fresh. Can
> anyone point me to the locations that might hold modem settings?
>
> thanks,
> steve
>
>
------------------------------
From: "The Snowman" <[EMAIL PROTECTED]>
Subject: Re: parallel port programming for linux?
Date: Thu, 10 May 2001 12:15:00 GMT
Many thanks to those who responded. The suggested extra board wouldn't be
much good I'm afraid, as it sounds like it would require an ISA slot, of
which I have none free. I do however have a parallel port, and no printer,
so that's more or less the route I'll still be taking.
Andreas: thanks, I think I've got an idea how to go about accessing the
port, or at least what to look for info on.
Regards,
Snowman
------------------------------
From: Joshua Baker-LePain <[EMAIL PROTECTED]>
Subject: Re: Tape drive installation problem
Date: 10 May 2001 12:31:33 GMT
Nick Long <[EMAIL PROTECTED]> wrote:
> Yes, it is a SCSI drive.
> Here is the output from /sbin/lsmod:
> Module Size Used by
> e100 37468 1 (autoclean)
> ncr53c8xx 51424 6
Well, then the scsi tape module is not being loaded. Try
'/sbin/modprobe st'. Although it is strange, b/c RH6.2 has always
loaded it for me. If it works, you may want to put that command at
the end of /etc/rc.d/rc.local.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
------------------------------
From: [EMAIL PROTECTED] (KegBot)
Subject: Re: Fire GL 4000
Reply-To: [EMAIL PROTECTED]
Date: Thu, 10 May 2001 12:34:09 GMT
The VESA driver? Well I never thought of that. I'll give it a shot.
Thanks!
On 10 May 2001 00:44:10 -0400, Michael Meissner <[EMAIL PROTECTED]> wrote:
>[EMAIL PROTECTED] (KegBot) writes:
>
>> Does anyone make an X server for the Diamond Fire GL4000 card, commercial
>> or otherwise? I tried searching the web and even looked at XIG's page.
>> Couldn't find anything relevant. I'd like to use this card if possible!
>
>Have you tried the VESA driver in XFree86 4.x? The VESA driver allowed me to
>bring up X on an unsupported Radeon VE (normal Radeon's are supported, but the
>VE is too new for current support) for example. Here is the XF86Config-4 file
>I used when I used the Radeon VE:
>
># File generated by xf86config, hacked by [EMAIL PROTECTED]
>
># Copyright (c) 1999 by The XFree86 Project, Inc.
>#
># Permission is hereby granted, free of charge, to any person obtaining a
># copy of this software and associated documentation files (the "Software"),
># to deal in the Software without restriction, including without limitation
># the rights to use, copy, modify, merge, publish, distribute, sublicense,
># and/or sell copies of the Software, and to permit persons to whom the
># Software is furnished to do so, subject to the following conditions:
>#
># The above copyright notice and this permission notice shall be included in
># all copies or substantial portions of the Software.
>#
># THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
># IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
># FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
># THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
># WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
># OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
># SOFTWARE.
>#
># Except as contained in this notice, the name of the XFree86 Project shall
># not be used in advertising or otherwise to promote the sale, use or other
># dealings in this Software without prior written authorization from the
># XFree86 Project.
>#
>
># **********************************************************************
># Refer to the XF86Config(4/5) man page for details about the format of
># this file.
># **********************************************************************
>
># **********************************************************************
># Module section -- this section is used to specify
># which dynamically loadable modules to load.
># **********************************************************************
>#
>Section "Module"
>
># This loads the DBE extension module.
>
> Load "dbe" # Double buffer extension
>
># This loads the miscellaneous extensions module, and disables
># initialisation of the XFree86-DGA extension within that module.
> SubSection "extmod"
> Option "omit xfree86-dga" # don't initialise the DGA extension
> EndSubSection
>
># This loads the Type1 and FreeType font modules
> Load "type1"
> Load "freetype"
>
># This loads the GLX module
># Load "glx"
>
>EndSection
>
># **********************************************************************
># 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 (which are concatenated together),
># as well as specifying multiple comma-separated entries in one FontPath
># command (or a combination of both methods)
>#
># If you don't have a floating point coprocessor and emacs, Mosaic or other
># programs take long to start up, try moving the Type1 and Speedo directory
># to the end of this list (or comment them out).
>#
>
># By default, Red Hat 6.0 and later now use a font server independent of
># the X server to render fonts.
>
> FontPath "unix/:7100"
>
># FontPath "/usr/X11R6/lib/X11/fonts/local/"
># FontPath "/usr/X11R6/lib/X11/fonts/misc/"
># FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
># FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
># FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
># FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
># FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
># FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
>
># The module search path. The default path is shown here.
>
># ModulePath "/usr/X11R6/lib/modules"
>
>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
>
># Option "NoTrapSignals"
>
># Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
># This allows clients to receive this key event.
>
># Option "DontZap"
>
># Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
># sequences. This allows clients to receive these key events.
>
># Option "Dont Zoom"
>
># Uncomment this to disable tuning with the xvidtune client. With
># it the client can still run and fetch card and monitor attributes,
># but it will not be allowed to change them. If it tries it will
># receive a protocol error.
>
># Option "DisableVidModeExtension"
>
># Uncomment this to enable the use of a non-local xvidtune client.
>
># Option "AllowNonLocalXvidtune"
>
># Uncomment this to disable dynamically modifying the input device
># (mouse and keyboard) settings.
>
># Option "DisableModInDev"
>
># Uncomment this to enable the use of a non-local client to
># change the keyboard or mouse settings (currently only xset).
>
># Option "AllowNonLocalModInDev"
>
>EndSection
>
># **********************************************************************
># Input devices
># **********************************************************************
>
># **********************************************************************
># Core keyboard's InputDevice section
># **********************************************************************
>
>Section "InputDevice"
>
> Identifier "Keyboard1"
> Driver "Keyboard"
># For most OSs the protocol can be omitted (it defaults to "Standard").
># When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
># uncomment the following line.
>
># Option "Protocol" "Xqueue"
>
> Option "AutoRepeat" "500 30"
>
># Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
># Option "Xleds" "1 2 3"
>
># Option "LeftAlt" "Meta"
># Option "RightAlt" "ModeShift"
>
># 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:
># Option "XkbModel" "pc102"
>#
># If you have a US Microsoft Natural keyboard, you can use:
># Option "XkbModel" "microsoft"
>#
># Then to change the language, change the Layout setting.
># For example, a german layout can be obtained with:
># Option "XkbLayout" "de"
>#
># or:
># Option "XkbLayout" "de"
># Option "XkbVariant" "nodeadkeys"
>#
># If you'd like to switch the positions of your capslock and
># control keys, use:
># Option "XkbOptions" "ctrl:swapcaps"
>
># These are the default XKB settings for XFree86
># Option "XkbRules" "xfree86"
># Option "XkbModel" "pc101"
># Option "XkbLayout" "us"
># Option "XkbVariant" ""
># Option "XkbOptions" ""
>
># Option "XkbDisable"
>
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc101"
> Option "XkbLayout" "us"
>
>EndSection
>
>
># **********************************************************************
># Core Pointer's InputDevice section
># **********************************************************************
>
>Section "InputDevice"
>
># Identifier and driver
>
> Identifier "Mouse1"
> Driver "mouse"
>
> Option "Protocol" "PS/2"
> Option "Device" "/dev/psaux"
>
># Option "Protocol" "IMPS/2"
># Option "Device" "/dev/mouse"
># Option "ZAxisMapping" "4 5"
>
># When using XQUEUE, comment out the above two lines, and uncomment
># the following line.
>
># Option "Protocol" "Xqueue"
>
># Baudrate and SampleRate are only for some Logitech mice. In
># almost every case these lines should be omitted.
>
># Option "BaudRate" "9600"
># Option "SampleRate" "150"
>
># Emulate3Buttons is an option for 2-button Microsoft mice
># Emulate3Timeout is the timeout in milliseconds (default is 50ms)
>
># Option "Emulate3Buttons"
># Option "Emulate3Timeout" "50"
>
># ChordMiddle is an option for some 3-button Logitech mice
>
># Option "ChordMiddle"
>
>EndSection
>
>
># **********************************************************************
># Monitor section
># **********************************************************************
>
># Any number of monitor sections may be present
>
>Section "Monitor"
>
> Identifier "ViewSonic VP181"
> VendorName "ViewSonic"
> ModelName "VP181"
>
># 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 - 95
>
># 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 - 75
>
>EndSection
>
>
># **********************************************************************
># Graphics device section
># **********************************************************************
>
># Any number of graphics device sections may be present
>
>Section "Device"
> Identifier "Standard Vesa"
> VendorName "ATI"
> BoardName "Radeon VE"
> Driver "vesa"
>
># BusID "PCI:1:0:0"
># Screen 1
># Chipset "chipset"
># Ramdac "ramdac-type"
># DacSpeed speed-8 speed-16 speed-24 speed-32
># Clocks clock...
># ClockChip "clockchip-type"
># VideoRam 32768
># BiosBase baseaddress
># MemBase baseaddress
># IOBase baseaddress
># ChipID id
># ChipRev rev
># TextClockFreq freq
># Option "ShadowFB" "true"
>
>EndSection
>
>
># **********************************************************************
># Screen sections
># **********************************************************************
>
># Any number of screen sections may be present. Each describes
># the configuration of a single screen. A single specific screen section
># may be specified from the X server command line with the "-screen"
># option.
>Section "Screen"
> Identifier "Screen vga"
> Device "Standard Vesa"
> Monitor "ViewSonic VP181"
> DefaultDepth 24
>
> Subsection "Display"
> Depth 8
> Modes "1280x1024"
> EndSubsection
>
> Subsection "Display"
> Depth 16
> Modes "1280x1024"
> EndSubsection
>
> Subsection "Display"
> Depth 24
> Modes "1280x1024"
> EndSubsection
>
> Subsection "Display"
> Depth 32
> Modes "1280x1024
> EndSubsection
>EndSection
>
># **********************************************************************
># ServerLayout sections.
># **********************************************************************
>
># Any number of ServerLayout sections may be present. Each describes
># the way multiple screens are organised. A specific ServerLayout
># section may be specified from the X server command line with the
># "-layout" option. In the absence of this, the first section is used.
># When now ServerLayout section is present, the first Screen section
># is used alone.
>
>Section "ServerLayout"
>
># The Identifier line must be present
> Identifier "Simple Layout"
>
># Each Screen line specifies a Screen section name, and optionally
># the relative position of other screens. The four names after
># primary screen name are the screens to the top, bottom, left and right
># of the primary screen. In this example, screen 2 is located to the
># right of screen 1.
>
> Screen "Screen vga"
>
># Each InputDevice line specifies an InputDevice section name and
># optionally some options to specify the way the device is to be
># used. Those options include "CorePointer", "CoreKeyboard" and
># "SendCoreEvents".
>
> InputDevice "Mouse1" "CorePointer"
> InputDevice "Keyboard1" "CoreKeyboard"
>
>EndSection
>
>
>--
>Michael Meissner, Red Hat, Inc. (GCC group)
>PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
>Work: [EMAIL PROTECTED] phone: +1 978-486-9304
>Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: "Adam Short" <[EMAIL PROTECTED]>
Subject: Re: smart card readers (serial probably)
Date: Thu, 10 May 2001 13:44:13 +0100
> > Anyone know anything about these things?
>
> See http://www.linuxnet.com
>
Thanks, that looks perfect!
--
'Attempted murder'? Now honestly what is that? Do they give out a Nobel
prize for 'Attempted Chemistry'? - Sideshow Bob
------------------------------
From: "The Snowman" <[EMAIL PROTECTED]>
Subject: Re: IBM Thinkpad 600E power switch change..
Date: Thu, 10 May 2001 13:02:33 GMT
AFAIK laptop screens don't burn in, so if there isn't a problem with power
consumption, why not just set it not to blank the screen and set up a screen
saver that does something graphical (something moving on screen would
probably give fair warning that the machine is already up and running.)
"Walter Francis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I'm having a problem with my wife not thinking about the laptop being on
> and turning it off when the screen has blanked, thinking she's actually
> turning it on.
>
> Using tpctl, I can set the power switch to turn the machine off, or to
> go into hibernation. Is there a way to set it to do anything different,
> such as safely reboot the computer? (ie: run a given command)
>
> I'm setting it to hibernate until I come up with a better solution..
> Unfortunately, occationally I have to really power down the machine with
> the power switch.. :(
>
> --
> Walter Francis
> http://theblackmoor.net Powered by Red Hat Linux 7.0
------------------------------
** 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
******************************
