Linux-Hardware Digest #371, Volume #14 Mon, 19 Feb 01 16:13:13 EST
Contents:
Re: Orinoco wavelan, ISA-PCMCIA adapter on linux ("D Knisely")
Re: Orinoco wavelan, ISA-PCMCIA adapter on linux ("D Knisely")
Re: Replicate/Clone RH6.2 Linux (Scott Nolde)
Modem found, but doesn't initialize (Clemson Tiger)
Re: Anyone using a Matrox G450 with 2 Monitors? (James Davis)
ttyS0 vs cua0??? (bgeer)
Re: replacing startx with startx -- +xinerama ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: "D Knisely" <[EMAIL PROTECTED]>
Subject: Re: Orinoco wavelan, ISA-PCMCIA adapter on linux
Date: Mon, 19 Feb 2001 14:17:07 -0600
I have set up Lucent Orinoco drivers on a couple of laptops and (recently)
using an ISA adapter under Linux. You need to get the "memory include"
ranges correct for your system (the default settings in
/etc/pcmcia/config.opts were not correct and did not work). Otherwise,
setting up the Orinoco drivers (which you can download from www.wavelan.com)
is simply a matter of obtaining the latest pcmcia distribution, overlaying
the Orinoco driver, building, and installing per the instructions from
Orinoco.
By the way, there are MANY compatibility problems with PCI to PCMCIA
adapters, and I would not recommend you try them unless you have no other
option. They only work with very recent system boards and BIOSs. Stick
with ISA to PCMCIA adapters.
I have not tried two Orinoco cards in the same system. I suspect not. At a
minimum, you will need two separate ISA to PCMCIA adapters, even if your
adapter supports more than one PCMCIA card, since the Wavelan card has a
thick external antenna housing. I do not know if the Linux driver supports
more than one device. There is at least one problem - there is no way to
configure independent settings (port_type, network_name, etc.) in
/etc/pcmcia/config.opts independently for more than one Wavelan card.
Perhaps the easiest thing to do would be to configure two PCs, each with a
Wavelan card and an ethernet card. Connect the two ethernets together with
a loopback cable, and set up the boxes to route Wavelan -> ethernet ->
Wavelan. Simple and cheap.
I found a very nice ISA to PCMCIA adapter on ebay recently for a very good
price.
Good luck.
D. Knisely
"Hans-Christian Prytz" <[EMAIL PROTECTED]> wrote in message
news:96orkj$bei$[EMAIL PROTECTED]...
> Hi, I just got my radiolink ingernet connection installed, and I was
> wondering if anyone has had experiences with the Lucent Orinoco pcmcia
card,
> and the matching ISA adapter under Linux.
>
> I have read some posts (on Deja/Google, what's the real name now anyhow?)
> from people saying they have gotten it to work, and I've heard something
> about an oss driver. How does this compare to Lucent's driver?
>
> Secondly, has anyone tried to use two of these cards in one machine? I
want
> to have a internal wireless LAN in addition to the WAN link going out. Any
> experience with this anyone?
>
> Hoping for a good response,
>
> Hans-Christian
>
> --
> Hans-Christian Prytz
> [EMAIL PROTECTED]
>
>
>
------------------------------
From: "D Knisely" <[EMAIL PROTECTED]>
Subject: Re: Orinoco wavelan, ISA-PCMCIA adapter on linux
Date: Mon, 19 Feb 2001 14:20:15 -0600
Also forgot this - "oss" is a set of drivers for sound devices (Open Sound
System?). I don't think this has anything to do with Wavelan/Orinoco.
D. Knisely
"Hans-Christian Prytz" <[EMAIL PROTECTED]> wrote in message
news:96orkj$bei$[EMAIL PROTECTED]...
> Hi, I just got my radiolink ingernet connection installed, and I was
> wondering if anyone has had experiences with the Lucent Orinoco pcmcia
card,
> and the matching ISA adapter under Linux.
>
> I have read some posts (on Deja/Google, what's the real name now anyhow?)
> from people saying they have gotten it to work, and I've heard something
> about an oss driver. How does this compare to Lucent's driver?
>
> Secondly, has anyone tried to use two of these cards in one machine? I
want
> to have a internal wireless LAN in addition to the WAN link going out. Any
> experience with this anyone?
>
> Hoping for a good response,
>
> Hans-Christian
>
> --
> Hans-Christian Prytz
> [EMAIL PROTECTED]
>
>
>
------------------------------
From: Scott Nolde <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.misc,comp.os.linux.help,comp.os.linux.networking,comp.os.linux.setup
Subject: Re: Replicate/Clone RH6.2 Linux
Date: Mon, 19 Feb 2001 20:12:20 GMT
Wow, all that crossposting. Anyway, this is how I'd do it:
1. Make boot disk of system.
2. Collect partition info (fdisk -l /dev/hda) and save on extra
floppy. Print it, too.
3. Shutdown system and install new hard drive (as /dev/hdb perhaps).
Reboot into runlevel 1 since it's the fastest.
4. fdisk /dev/hdb in similar fashion of /dev/hda. mkfs.ext2
/dev/hdbx. mkswap too.
5. mount partitions of /dev/hdb into /mnt/whatever
6. cp -avf / /bin /sbin, etc... to /mnt/whatever (you are copying files
to their respective directories on the new drive. Don't copy the /proc
directory.)
7. To test, move /dev/hdb into /dev/hda position and reboot. You may
have to use the boot floppy and /sbin/lilo the new drive.
You could do the above, or use tomsrtbt to
dd if=/dev/hda of=/dev/hdb (assuming identical hard drive geometry.
I haven't tested the second method, but the first works well.
- Scott
Steven Conway wrote:
>
> I have painstakingly set up old OS/2 Warp (urgh) workstation with
> RedHat 6.2.
>
> 1) I have correctly configured all of the devices by downloading
> patches, recompiling, etc.
>
> 2) Updated and changed the kernel.
>
> 3) Updated the numerous packages with the latest patches (up2date)
> RPMS & .tar.gz).
>
> 4) Installed, and tested numerous other third party software packages.
>
> 5) tested, tweeked and finally have the computer working exactly how I
> want it to.
>
> I now need to replicate/clone this workstation to 25 IDENTICAL
> workstations that are all connected over a Private internal network.
>
> I was told to look at RedHats Kickstart but I am not sure if this
> approach is the best way to do this as it assumes you are installing
> off of a CD and not off of an existing system. Am I correct in this
> assumption? Can I even do what I am trying to do.
>
> Steven Conway
--
Never do Windows again with | Scott M. Nolde
Linux! No streaks, haze or | [EMAIL PROTECTED]
glaze! |
3:01pm up 1 day, 14:17, 1 user, load average: 1.00, 1.00, 1.00
------------------------------
From: Clemson Tiger <[EMAIL PROTECTED]>
Subject: Modem found, but doesn't initialize
Date: Mon, 19 Feb 2001 20:30:04 -0000
I am trying to configure and dial my ISP with a Motorola Voice 56K modem,
which I know to work -- at least with MS Windows. Linux recognized the
modem during installation and I can find the modem in hardware
configuration, using "X".
When I try to setup and configure the modem, using "kppd" in "X", the
modem is found; however, when I try to dial, the dial-up box starts and
says the "modem is ready" and "initializing". The process stops at the
initializing phase.
When I check the "kppd" setup in "X" and click on the modem tab and click
on commands there are commands listed for intialize, "ATZ". When I query
the modem, there is nothing listed for AT1 through AT7. Is this the
problem and what do I do?
I'm an experienced MS Windows user who is trying to kick the Windows
habit. Other than the modem, the installation was fairly straight
forward. Of course, I have not tried to read or burn a CD or use my
floppy, zip and jaz drives.
Thanks for the help.
Clemson Tiger
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (James Davis)
Subject: Re: Anyone using a Matrox G450 with 2 Monitors?
Date: 19 Feb 2001 21:40:13 +0100
I am currently running a matrox g450 with 2 monitors under slackware 7.0.
I have had to upgrade the xserver a couple of times. I am currently
using XFree86 4.0.2 with the newest module from matrox.
Works nice. :)
--
Posted from root@[192.147.172.16]
via Mailgate.ORG Server - http://www.Mailgate.ORG
------------------------------
From: [EMAIL PROTECTED] (bgeer)
Subject: ttyS0 vs cua0???
Date: 19 Feb 2001 14:00:26 -0700
When I use /dev/ttyS0 for my external modem, I usually manage to get
it "constipated" while tinkering with creating new ppp connections.
Like, the open call fails, just hangs, no error return, no nada?
When I use cua0, it works every time.
So why am I not supposed to use cua0? Is using ttyS0, which can
apparently get stuffed up to the point of unresponsiveness, an
improvement?
Inquiring mind wants to know...:-)
Much obliged for any info...Bob
--
<> Robert Geer & Donna Tomky | |||| |||| <>
<> [EMAIL PROTECTED] | == == Suddenly, == == <>
<> [EMAIL PROTECTED] | == == We feel enchanted! == == <>
<> Albuquerque, NM USA | |||| |||| <>
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux.redhat,comp.os.linux.admin,comp.os.linux.misc,comp.os.linux.setup
Subject: Re: replacing startx with startx -- +xinerama
Date: Tue, 20 Feb 2001 07:02:34 +1000
I have this itchy feeling that you want to do a bit of research on
gdm, (gnome display manager AFAIK). This is the thing that you first see
with the choice of window managers. The man pages are broken on my
system, so I dont know where to point you. It may also be a case of
having to poke around in your /etc/X11/xinit/ directory, there are a
couple of scripts in there that are run when you startx.
Sorry for the complete vagueness
J
-=<************************************>=-
The list of specs for my
PC is longer than my willy.
jaredATcelab21DOTpcDOTelecDOTuqDOTeduDOTau
On Mon, 19 Feb 2001, Chris Nelson wrote:
> Hello: This weekend I finally got a working config file for using 2
> monitors on a g400 max.
>
> My problem however is that right now my etc/inittab file has me going to
> only run level 3. if I change this value to 5, the systems takes me to a
> graphical logon..but with only one monitor. My guess is that the system
> is still strying to run startx as opposed to startx -- +xinerama. Where
> do I need to make a change so this can be automoated? Any advice is
> appreciated...
>
> P.S. Any idea how I can have the system default to KDE as opposed to
> gnome? Thought I would throw this in as well
>
> Chris
> Enclosed ar emy XF86Config filke and my /etc/inittab files
>
> *********MY inittab file*************
> #
> # inittab This file describes how the INIT process should set up
> # the system in a certain run-level.
> #
> # Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]>
> # Modified for RHS Linux by Marc Ewing and Donnie Barnes
> #
>
> # Default runlevel. The runlevels used by RHS are:
> # 0 - halt (Do NOT set initdefault to this)
> # 1 - Single user mode
> # 2 - Multiuser, without NFS (The same as 3, if you do not have
> networking)
> # 3 - Full multiuser mode
> # 4 - unused
> # 5 - X11
> # 6 - reboot (Do NOT set initdefault to this)
> #
> id:3:initdefault:
>
> # System initialization.
> si::sysinit:/etc/rc.d/rc.sysinit
>
> l0:0:wait:/etc/rc.d/rc 0
> l1:1:wait:/etc/rc.d/rc 1
> l2:2:wait:/etc/rc.d/rc 2
> l3:3:wait:/etc/rc.d/rc 3
> l4:4:wait:/etc/rc.d/rc 4
> l5:5:wait:/etc/rc.d/rc 5
> l6:6:wait:/etc/rc.d/rc 6
>
> # Things to run in every runlevel.
> ud::once:/sbin/update
>
> # Trap CTRL-ALT-DELETE
> ca::ctrlaltdel:/sbin/shutdown -t3 -r now
>
> # When our UPS tells us power has failed, assume we have a few minutes
> # of power left. Schedule a shutdown for 2 minutes from now.
> # This does, of course, assume you have powerd installed and your
> # UPS connected and working correctly.
> pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
>
> # If power was restored before the shutdown kicked in, cancel it.
> pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
>
>
> # Run gettys in standard runlevels
> 1:2345:respawn:/sbin/mingetty tty1
> 2:2345:respawn:/sbin/mingetty tty2
> 3:2345:respawn:/sbin/mingetty tty3
> 4:2345:respawn:/sbin/mingetty tty4
> 5:2345:respawn:/sbin/mingetty tty5
> 6:2345:respawn:/sbin/mingetty tty6
>
> # Run xdm in runlevel 5
> # xdm is now a separate service
> x:5:respawn:/etc/X11/prefdm -nodaemon
>
>
> **********My XF86Config File*****************
> # File generated by xf86config.
>
> #
>
> 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
>
> Section "Files"
>
> RgbPath
> "/usr/X11R6/lib/X11/rgb"
>
>
> 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/"
>
> EndSection
>
> # **********************************************************************
> # Server flags section
> # **********************************************************************
>
> Section "ServerFlags"
>
> 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"
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc101"
> Option "XkbLayout" "us"
> Option "XkbCompat" ""
>
> EndSection
>
>
> # **********************************************************************
> # Core Pointer's InputDevice section
> # **********************************************************************
>
> Section "InputDevice"
>
> # Identifier and driver
>
> Identifier
> "Mouse1"
> Driver
> "mouse"
> Option "Protocol" "PS/2"
> Option "Device" "/dev/mouse"
>
> EndSection
>
> # **********************************************************************
> # Monitor section
> # **********************************************************************
>
> # Any number of monitor sections may be present
>
> Section "Monitor"
>
> Identifier "817-1"
> HorizSync 30-130
> VertRefresh 50-180
>
> EndSection
>
> Section "Monitor"
>
> Identifier "815"
> HorizSync 30-130
> VertRefresh 50-180
>
> EndSection
>
> # **********************************************************************
> # Graphics device section
> # **********************************************************************
>
> # Any number of graphics device sections may be present
>
> # Standard VGA Device:
>
> Section "Device"
> Identifier
> "Standard VGA"
> VendorName
> "Unknown"
> BoardName
> "Unknown"
>
> # The chipset line is optional in most cases. It can be used to override
> # the driver's chipset detection, and should not normally be specified.
>
> # Chipset "generic"
>
> # The Driver line must be present. When using run-time loadable driver
> # modules, this line instructs the server to load the specified driver
> # module. Even when not using loadable driver modules, this line
> # indicates which driver should interpret the information in this section.
>
> Driver "vga"
> # The BusID line is used to specify which of possibly multiple devices
> # this section is intended for. When this line isn't present, a device
> # section can only match up with the primary video device. For PCI
> # devices a line like the following could be used. This line should not
> # normally be included unless there is more than one video device
> # intalled.
>
> # BusID "PCI:0:10:0"
>
> # VideoRam 256
>
> # Clocks 25.2 28.3
>
> EndSection
>
> # Device configured by xf86config:
>
> Section "Device"
> Identifier "maxxx"
> Driver "mga"
> # unsupported card
> #VideoRam 32777
> VideoRam 32768
> # Insert Clocks lines here if appropriate
> EndSection
>
> Section "Device"
> Identifier "G400_1"
> Driver "mga"
> BusID
> "PCI:1:0:0"
> Screen
> 0
> EndSection
>
> Section "Device"
> Identifier "G400_2"
> Driver "mga"
> BusID
> "PCI:1:0:0"
> Screen
> 1
> 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 15"
> Device "maxxx"
> Monitor "817-1"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> Subsection "Display"
> Depth 16
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> Subsection "Display"
> Depth 24
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> EndSection
>
> Section "Screen"
> Identifier "Screen 1"
> Device "G400_1"
> Monitor "817-1"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 16
> Modes "1280x1024
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 24
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
> EndSection
>
> Section "Screen"
> Identifier "Screen 2"
> Device "G400_2"
> Monitor "815"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 16
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 24
> Modes "1280x1024"
> ViewPort 0 0
> 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 1"
> Screen "Screen 1" LeftOf "Screen 2" Screen "Screen 2"
>
>
> # 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
>
>
>
------------------------------
** 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
******************************
