Linux-Hardware Digest #762, Volume #13 Fri, 20 Oct 00 20:13:07 EDT
Contents:
ZIP Drive time-out (Geir Bjune)
Re: brother 1240 (Ross Vandegrift)
Keyboard modes (Ross Vandegrift)
Re: SV: modem.... (Dark Dog)
Re: Hardware for Mail Server (Michael Erskine)
Rockwell USB Modem driver (Olly Smith)
Zip Drive (Francisco Caamano)
Re: Adding SCSI to IDE System Linux 6.2 (Mark Post)
Re: How to detect sensors using gameport? (Bloody Viking)
Redhat 7 + ide patches = trouble ?? (Ton)
Re: Redhat 7 + ide patches = trouble ?? (Hal Burgiss)
Re: cd writer? (Gary Sandine)
Re: Modem driver (James Richard Tyrer)
Re: ESS 1869 Drivers (Josh Rovero)
Re: Configuring modems for usage in Linux (James Richard Tyrer)
Re: PIII vs Athlon (Robert MacGregor)
Re: Redhat 7 + ide patches = trouble ?? (Ton)
----------------------------------------------------------------------------
From: Geir Bjune <[EMAIL PROTECTED]>
Crossposted-To: wsu.linux
Subject: ZIP Drive time-out
Date: 20 Oct 2000 13:53:03 -0700
My SCSI ZIP (100 MB) keeps timing out when I am accessing it from Linux. I
have tried with both 2.2.* and 2.4.0-test10, but the same problem always
comes up.
The device timeouts, the SCSI (aic7xxx, AHA-2940U) bus resets and this keeps
on happening for a longtime.
In Windows (95/98/NT/2000), the device works all the time, with no
timeouts occuring.
Is this related to failure of the hardware or is there some configuration of
the device that needs to change ? Other devices connected to the same
controller work nicely...
Geir
------------------------------
From: Ross Vandegrift <[EMAIL PROTECTED]>
Subject: Re: brother 1240
Date: Fri, 20 Oct 2000 16:57:13 -0400
Reply-To: [EMAIL PROTECTED]
HEy,
I just bought this printer, and I must say,m it rocks. I'm coming
from a super-crappy printer (bubble-jet... yuck), so maybe I'm just being
spoiled now. Nice looking output, PCL compatability, 2M of memory, and
12ppm adds up to a great deal for only ~280 dollars.
Ross Vandegrift
On Wed, 18 Oct 2000, pete wrote:
> Hi all,
>
> Thinking of buying a Brother 1240 laser printer. I see there's a linux
> driver so I'm not too worried about getting it to work, but in a few online
> reviews I've read some user comments trash the printer's print quality.
> Does anyone have any comments about that in this newsgroup?
>
> Thanks,
>
> peter
>
>
------------------------------
From: Ross Vandegrift <[EMAIL PROTECTED]>
Subject: Keyboard modes
Date: Fri, 20 Oct 2000 17:07:05 -0400
Reply-To: [EMAIL PROTECTED]
Hi everyone,
I have been having problems with servers, and I think I've traced
it to hardware problems with our keyboards. Specifically, we have
cheap-ass switches and I think they're screwing up the kernel when we
switch them. I'm curious to test this theory out - but I have yet to
figure out a way to change the keyboard mode without using Magic SysRq key
(some servers aren't local and that makes it quite difficult). First of
all, am I correct in thinking that the kernel boots up and accessesd the
keyboard in RAW mode? Second, what other modes are there (I've heard of
XLATE, at least) and what are the differences betwween them. Finally, how
can I configure the kernel to use the various modes?
Thanks,
Ross Vandegrift
[EMAIL PROTECTED]
Seitz Techical Products Inc
------------------------------
From: Dark Dog <[EMAIL PROTECTED]>
Subject: Re: SV: modem....
Date: Fri, 20 Oct 2000 23:24:50 +0200
On Thu, 28 Sep 2000, Marre wrote:
>well....
>it is an external modem.....
>
>Marre
>
>
>Marre <[EMAIL PROTECTED]> skrev i
>diskussionsgruppsmeddelandet:EcDA5.14324$[EMAIL PROTECTED]
>> Hi!
>>
>> Iīve got problems with my modem. PPP dialer canīt get connected to my
>modem.
>> My modem is a usr sportster message plus updated with v90. When I run the
>> internet setup wizard, it canīt find my modem.
>> This is with Red Hat 6.2......
>>
>> any suggestions??
>>
>> Marre
>>
Create /etc/rc.d/rc.serial and put the following stuff in it (assuming the
modem is connected to COM1):
#!/bin/sh
setserial /dev/ttyS0 irq 4 autoconfig
setserial /dev/ttyS0 spd_vhi
setserial /dev/ttyS0
stty -echo < /dev/ttyS0
Activate the settings by running source /etc/rc.d/rc.serial
Use Red Hat's Control Panel to make a link from /dev/modem to ttyS0.
Hope this helps.
Jon-Ivar
------------------------------
From: Michael Erskine <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Hardware for Mail Server
Date: Fri, 20 Oct 2000 18:14:08 -0400
" =A4j=A9=FA" wrote:
> =
> Hi,
> =
> I'd like to get some suggestion for the hardware of my Email Server.
> =
> My company have staffs around 50 - 70, and I dunno what is the min
> hardware requirement for this. The mail server will host mail for 5 vir=
tual
> domain and around 1300+ mails per day.
> =
> The first plan is to use a single 733Mhz w/256MB ECC SDRAM, 18GB Ultra=
3
> SCSI Drive. Will it be over power ?? What's your suggestions ?
> =
> ThanX....
This is tongue in cheek and not intended to offend...
Good Lord... Steve and his constant shilling for qmail... And people ta=
lking
about killing mosquitos with freakin' howitzers! :)
Running RH 5.2 on an old P-120 with 128 Megs of ram and a 4 gig drive up =
till
recently. Processing 15,000 mail messages per day for 2000 users on 200
dialups. Sendmail but that doesn't matter except that it does have a bit=
more
overhead than qmail.
Oh, yeah, the box was a primary DNS server for half a dozen domains as we=
ll.
Every once in a while, she did slow down a bit -- not so as any user woul=
d
notice
but you could feel it on the console a tad.
Yeah, the system you describe is enough to serve about 50000 web visiters=
per
day,
especially if you just give it another 256M....
Hell, that is enough machine to run a news server, a web server and mail =
for
the
organization you describe. Just make sure she doesn't get into swap.
Does anybody even know what a Vax MIP is anymore?
-m-
--
Nothing astonishes men so much as common sense and plain dealing.
------------------------------
Subject: Rockwell USB Modem driver
From: [EMAIL PROTECTED] (Olly Smith)
Date: Fri, 20 Oct 2000 22:27:50 GMT
Hey all.
Basically, I'm looking for a challenge, and since I have a Rockwell (eek!)
USB modem that AFAIK has no support from existing drivers, I wanna have
a go at writing a driver for it. It's got a full chipset on it, so I'm
not gonna be playing around with yukky winmodem stuff, just trying to
communicate with the on-bard USB controller.
What I need to know is..
o is anybody already trying this?
o does anybody have any info on the Rockwell chipset/USB controller
(AFAIK Rockwell are charging big-bucks for this info).
Thanks,
Olly
------------------------------
From: Francisco Caamano <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Zip Drive
Date: Fri, 20 Oct 2000 18:55:46 -0400
I can mount the Zip 100, but I can't eject the zip disk from drive, I'm
using Red Hat 6.1, I'm just testing it and trying to learn ... thanks
for helping me..
------------------------------
From: [EMAIL PROTECTED] (Mark Post)
Subject: Re: Adding SCSI to IDE System Linux 6.2
Date: Fri, 20 Oct 2000 23:04:48 GMT
On Thu, 19 Oct 2000 22:25:28 GMT, [EMAIL PROTECTED] wrote:
>Got a question for those who have gone this path
>before.
>I just added an Adaptec 2940UW card to my linux
>box that was previously installed on a 20GB IDE
>drive. I've added 4 SCSI Ultra Wide hard drives
>to the system. I only want to use the SCSI drives
>as additional data drives and do NOT want to move
>the install to the SCSI drives.
>Upon the initial boot(after adding the card and
>drives) the autoconfigure detected the card and a
>screen came up and loaded the aic7xxx driver for
>the card(which is the correct driver). So far so
>good.
>The problem is that I can't FDISK the drives.
>fdisk /dev/sda returns "Unable to open /dev/sda".
Do you have support for SCSI disks compiled into your kernel?
What do you get when you do:
'cat /proc/devices'
'cat /proc/partitions'
'cat /proc/scsi/scsi'
Try doing a 'modprobe sd_mod' and see what happens.
Do you have /dev/sd? defined?
>I tried sda, sda1, sdb etc... Nothing...
>So I then decide to see if the install can see the
>drives. I boot from CD and start an install and
>ALL of the drives are listed. I went ahead and
>partitioned and formatted them and completed a
>minimal install with no problem.
This really sounds like your kernel doesn't have support for SCSI disks in
it, even though it has support for the aic7xxx card. You might try copying
the kernel that is on your bootable CD to where you keep your kernels on
your disk drive, update LILO to point to it, and reboot with it.
>I'm back to booting to the IDE now and it's the
>same old story, the fdisk utility will not see the
>drives. I checked the kernel to see if the SCSI
>module was loaded and it is.
You will also need a sd_mod module for the SCSI disks.
Mark Post
Postmodern Consulting
Information Technology and Systems Management Consulting
To send me email, replace 'nospam' with 'home'.
------------------------------
From: [EMAIL PROTECTED] (Bloody Viking)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: How to detect sensors using gameport?
Date: 20 Oct 2000 23:16:45 GMT
[EMAIL PROTECTED] wrote:
: do a
: man -k joystick
: to learn how to program the joystick port. Viewing the source code from some
: games would also be a good idea. mame, the multiple arcade machine emulator,
: has joystick code you could study.
It's possible to use a second parallel port to output to 8 different things
too, though I don't know how to do it. (darn) It might be as easy as simply
putting a character into the /dev/lpt* file of choice. You can have 3 parallel
fittings, with the printer on one (with daemon) and the other two for your
Disco Machine from Hell(tm).
As far as viewing source code, for beginners it can be a tough challenge. I
remember downloading the Replay.com remailer source, and despite being a lousy
C programmer, I was still able to do some hacking on it to make a custom
remailer. It's a challenge, but if you have the time, far from impossible.
If I ever make my own site with domain, I'll gladly add an anon remailer such
as "[EMAIL PROTECTED]" or remailer@ whatever. One time I wanted to make
an anon.penet.fi clone. I would have taken the Replay code and hacked the shit
out of it.
--
FOOD FOR THOUGHT: 100 calories are used up in the course of a mile run.
The USDA guidelines for dietary fibre is equal to one ounce of sawdust.
The liver makes the vast majority of the cholesterol in your bloodstream.
------------------------------
From: Ton <[EMAIL PROTECTED]>
Subject: Redhat 7 + ide patches = trouble ??
Date: Sat, 21 Oct 2000 01:17:24 +0200
Hi,
Could anyone tell me if and why it is absolutely necessary to download
the fresh source tree from kernel.org, instead of using the default that
comes with RedHat 7, to make the (Hedrick's) ide patches work without
modifications of the source, and to make compilable kernels, not getting
rejects or error #2's?
It has cost me weeks now to get RH7 and the default kernel to work
properly, just to make it recognize the hard disk properly. I only
succeeded by doing this with 2.4.0-test9 by using a fresh tree, but
using RH's sources and patching it is nothing but trouble. Beginning to
get very mad at RH...
Thanks,
Ton
--
ICQ 3923462
'So if you want my address, it's number one at the end of the bar..'
(Fish)
"Windows as a rule does not crash for no reason. There is always a
reason, but finding it may take a little time."
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Subject: Re: Redhat 7 + ide patches = trouble ??
Reply-To: Hal Burgiss <[EMAIL PROTECTED]>
Date: Fri, 20 Oct 2000 23:30:33 GMT
On Sat, 21 Oct 2000 01:17:24 +0200, Ton <[EMAIL PROTECTED]> wrote:
>Hi,
>
>Could anyone tell me if and why it is absolutely necessary to download
>the fresh source tree from kernel.org, instead of using the default that
>comes with RedHat 7, to make the (Hedrick's) ide patches work without
>modifications of the source, and to make compilable kernels, not getting
>rejects or error #2's?
Redhat's kernels already have a lot of patches applied would be my
guess.
--
Hal B
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
------------------------------
From: Gary Sandine <[EMAIL PROTECTED]>
Subject: Re: cd writer?
Crossposted-To: comp.os.linux.setup
Date: Fri, 20 Oct 2000 23:36:22 GMT
In comp.os.linux.hardware Dr Aldo Medina <[EMAIL PROTECTED]> wrote:
> I have a similar problem, not being able to get Linux recognize my
> Creative 8433e CDRW. However it seems from the post previous to yours
> (not available at my server) that I must disable ATAPI cdrom in my
> kernel. However, how can I then get Linux to recognize my other ATAPI
> IDE CDROM? or should I program both as SCSI-emulated?. TIA
You should read CD-writing HOWTO - especially section 2.1 where it
details *exactly* how to make ide-cd ignore your CDRW, yet it can
still drive your CDR, DVD, or whatever. The easiest way is via some
insertions in your module configuration file (/etc/modules.conf or
whatever) - does not require a kernel recompile.
http://www.lanm-pc.com (Cheap Linux boxes)
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: Modem driver
Date: Fri, 20 Oct 2000 23:52:30 GMT
This is a multi-part message in MIME format.
==============347BF8BD49F690D6AA4A213E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sonny wrote:
> I just installed Corel Linux on an old Pentium 100 machine. I actually know
> next to nothing about Linux, but I'm eager to learn. The problem is, I'm
> not sure about how it detects and installs hardware. Right now, my biggest
> concern is my modem. It's a Diamond SupraMax 56i PCI. It didn't install
> itself. Can I get a driver for it someplace? Will it just be an
> executable?
>
The modem data base at:
http://www.o2.net/~gromitkc/20001005a.html
indicates that this is a Rockwell chip set HCF. That is, it is a WINMODEM!
Consult the above link for further info.
>
> There's also an old ISA network card and an ISA sound card (Yamaha OPL
> YM719B-S) that don't work.
Your ISA network card might work if it is a standard brand. I have no
experience with network cards.
Sound cards require Kernel support. Your card appears to be supported by
module: opl3sa2. If this module is built into your Kernel, you install it by
making the proper entries in the file: "/etc/modules.conf". If it is not in
your Kernel, you will need to build a Kernel.
See attached.
JRT
==============347BF8BD49F690D6AA4A213E
Content-Type: text/plain; charset=us-ascii;
name="OPL3-SA2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="OPL3-SA2"
Documentation for the OPL3-SA2, SA3, and SAx driver (opl3sa2.o)
===============================================================
Scott Murray, [EMAIL PROTECTED]
January 5, 1999
NOTE: All trade-marked terms mentioned below are properties of their
respective owners.
This driver is for PnP soundcards based on the following Yamaha audio
controller chipsets:
YMF711 aka OPL3-SA2
YMF715 aka OPL3-SA3
YMF719 aka OPL3-SAx (?)
I'm a little fuzzy on what exactly is classified a SAx, as I've seen
the label used to refer to the whole 7xx family and as a specific
identifier for the 719 on my no-name soundcard. To make matters
worse, there seem to be several revisions of the 715 chipset.
Anyways, all of these chipsets implement the following devices:
OPL3 FM synthesizer
Soundblaster Pro
Microsoft/Windows Sound System
MPU401 MIDI interface
Note that this driver uses the MSS device, and to my knowledge these
chipsets enforce an either/or situation with the Soundblaster Pro
device and the MSS device. Since the MSS device has better
capabilities, I have implemented the driver to use it.
Being PnP cards, some configuration is required. There are two ways
of doing this. The most common is to use the isapnptools package to
initialize the card, and use the kernel module form of the sound
subsystem and sound drivers. Alternatively, some BIOS's allow manual
configuration of installed PnP devices in a BIOS menu, which should
allow using the non-modular sound drivers, i.e. built into the kernel.
I personally use isapnp and modules, and do not have access to a PnP
BIOS machine to test. If you have such a beast, try building both the
MSS driver and this driver into the kernel (appropriately configured,
of course). I have received reports of this working, so it should be
possible for most people with PnP BIOS. If it does not work for you,
then email me if you are willing to experiment in an effort to make it
work.
************************************************************************
* I have now had two such machines, and I have fixed this to work
* properly when built into the kernel. The Toshiba Libretto series, or
* at least models 70CT and 110CT which I have owned, use a Yamaha
* OPL3-SAx (OPL3-SA3 according to documentation) sound chip, IRQ 5,
* IO addresses 220/530/388/330/370 and DMA 1,0 (_not_ 0,1). All these
* configuration settings can be gathered by booting another OS which
* recognizes the card already.
*
* I have made things 'just work' for the non-modular case on such
* machines when configured properly.
*
* David Luyer <[EMAIL PROTECTED]>
************************************************************************
If you are using isapnp, follow the directions in its documentation to
produce a configuration file. Here is the relevant excerpt I use for
my SAx card from my isapnp.conf:
(CONFIGURE YMH0800/-1 (LD 0
# Instead of (IO 0 (BASE 0x0220)), disable SB:
(IO 0 (BASE 0x0000))
(IO 1 (BASE 0x0530))
(IO 2 (BASE 0x0388))
(IO 3 (BASE 0x0330))
(IO 4 (BASE 0x0370))
(INT 0 (IRQ 7 (MODE +E)))
(DMA 0 (CHANNEL 0))
(DMA 1 (CHANNEL 3))
Here, note that:
Port Acceptable Range Purpose
---- ---------------- -------
IO 0 0x0220 - 0x0280 SB base address, I set to 0 just to be safe.
IO 1 0x0530 - 0x0F48 MSS base address
IO 2 0x0388 - 0x03F8 OPL3 base address
IO 3 0x0300 - 0x0334 MPU base address
IO 4 0x0100 - 0x0FFE card's own base address for its control I/O ports
The IRQ and DMA values can be any that considered acceptable for a
MSS. Assuming you've got isapnp all happy, then you should be able to
do something like the following (which matches up with the isapnp
configuration above):
insmod mpu401
insmod ad1848
insmod opl3sa2 io=0x370 mss_io=0x530 mpu_io=0x330 irq=7 dma=0 dma2=3
insmod opl3 io=0x388
Remember that the opl3sa2 module's io argument is for it's own control
port, which handles the card's master mixer for volume (on all cards),
and bass and treble (on SA3 and SAx cards).
If all goes well and you see no error messages, you should be able to
start using the sound capabilities of your system. If you get an
error message while trying to insert the opl3sa2 module, then make
sure that the values of the various arguments match what you specified
in your isapnp configuration file, and that there is no conflict with
another device for an I/O port or interrupt. Checking the contents of
/proc/ioports and /proc/interrupts can be useful to see if you're
butting heads with another device.
If you still cannot get the module to load, look at the contents of
your system log file, usually /var/log/messages. If you see the
message "Unknown Yamaha audio controller version", then you have a
different chipset than I've encountered so far. Look for a line in
the log file that says "opl3sa2.c: chipset version = <some number>".
If you want me to add support for your card, send me the number from
this line and any information you have on the make and chipset of your
sound card, and I should be able to work up a permanent fix.
If you do not see the chipset version message, and none of the other
messages present in the system log are helpful, email me some details
and I'll try my best to help.
Lastly, if you're using modules and want to set up automatic module
loading with kmod, the kernel module loader, here is the section I
currently use in my conf.modules file:
# Sound
alias char-major-14 opl3sa2
pre-install opl3sa2 modprobe "-k" "ad1848"
post-install opl3sa2 modprobe "-k" "opl3"
options opl3sa2 io=0x370 mss_io=0x530 mpu_io=0x330 irq=7 dma=0 dma2=3
options opl3 io=0x388
That's all it currently takes to get an OPL3-SAx card working on my
system. Once again, if you have any other problems, email me at the
address listed above.
Scott
==============347BF8BD49F690D6AA4A213E==
------------------------------
From: Josh Rovero <[EMAIL PROTECTED]>
Subject: Re: ESS 1869 Drivers
Date: Fri, 20 Oct 2000 23:54:15 GMT
> > [EMAIL PROTECTED] wrote:
> > ls /> Hey I hope someone can help me. I have a ESS 1869 sound card
> > and i need linux drivers for it, (yes i have checked the
> > manufacturers web site).
A RH 6.2 or 7.0 system should recognize this without too
many problems. I had to change the IRQ from 5 to 7 for
mine to work, since I had other hardware on IRQ 5.
Just run (as root) isapnp, then sndconfig. Edit
the /etc/isapnp.conf file if necessary.
My isapnp.conf:
# $Id: pnpdump_main.c,v 1.23 2000/04/19 22:49:44 fox Exp $
# Release isapnptools-1.22
#
# This is free software, see the sources for details.
# This software has NO WARRANTY, use at your OWN RISK
#
# For details of the output file format, see isapnp.conf(5)
#
# For latest information and FAQ on isapnp and pnpdump see:
# http://www.roestock.demon.co.uk/isapnptools/
#
# Compiler flags: -DREALTIME -DNEEDSETSCHEDULER -DABORT_ONRESERR
#
# Trying port address 0273
# Board 1 has serial identifier be ff ff ff ff 69 18 73 16
# (DEBUG)
(READPORT 0x0273)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
# Card 1: (serial identifier be ff ff ff ff 69 18 73 16)
# Vendor Id ESS1869, No Serial Number (-1), checksum 0xBE.
# Version 1.0, Vendor version 1.0
# ANSI string -->ESS ES1869 Plug and Play AudioDrive<--
#
# Logical device id ESS0006
# Device supports vendor reserved register @ 0x39
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3d
# Device supports vendor reserved register @ 0x3f
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be
changed if required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE ESS1869/-1 (LD 0
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0800
# Maximum IO base address 0x0ff8
# IO base alignment 8 byte# Number of IO addresses
required: 8
# (IO 0 (SIZE 8) (BASE 0x0800))
(NAME "ESS1869/-1[0]{ESS ES1869 Plug and Play AudioDrive}")
(ACT Y)
))
#
# Logical device id ESS1869
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3b
# Device supports vendor reserved register @ 0x3e
# Device supports vendor reserved register @ 0x3f
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be
changed if required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE ESS1869/-1 (LD 1
# Multiple choice time, choose one only !
# Start dependent functions: priority preferred
# Start dependent functions: priority preferred
# First DMA channel 1.
# 8 bit DMA only
# Logical device is not a bus master
# DMA may execute in count by byte mode
# DMA may not execute in count by word mode
# DMA channel speed in compatible mode
(DMA 0 (CHANNEL 1))
# Next DMA channel 0 or 3.
# 8 bit DMA only
# Logical device is not a bus master
# DMA may execute in count by byte mode
# DMA may not execute in count by word mode
# DMA channel speed in compatible mode
(DMA 1 (CHANNEL 0))
# IRQ 5.
# High true, edge sensitive interrupt (by default)
(INT 0 (IRQ 7 (MODE +E)))
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0220
# Maximum IO base address 0x0220
# IO base alignment 1 bytes
# *** Bad resource data: Base alignment 0 - changed to 1
# Number of IO addresses required: 16
(IO 0 (BASE 0x220))
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0388
# Maximum IO base address 0x0388
# IO base alignment 1 bytes
# *** Bad resource data: Base alignment 0 - changed to 1
# Number of IO addresses required: 4
(IO 1 (SIZE 4) (BASE 0x0388))
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x0330
# Maximum IO base address 0x0330
# IO base alignment 1 bytes
# *** Bad resource data: Base alignment 0 - changed to 1
# Number of IO addresses required: 2
(IO 2 (BASE 0x330))
# End dependent functions
(NAME "ESS1869/-1[1]{ESS ES1869 Plug and Play AudioDrive}")
(ACT Y)
))
(WAITFORKEY)
--
P. Josh Rovero KK1D Oceanographer & Meteorologist
[EMAIL PROTECTED] http://members.home.net/provero
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: Configuring modems for usage in Linux
Date: Sat, 21 Oct 2000 00:00:12 GMT
apple wrote:
> Hi Guys,
>
> It would be very appreciated if you could tell me if there is any solution
> for configuring my modem for RedHat Linux 6.2.
>
> My motherboard is a PC-100 with a built-in video card which is shared with
> my RAM.
> There is also a built-in crystal sound card attached with my MotherBoard.
> My MotherBoard also has a built-in HSP Modem.
>
> I have tried almost everything in configuring my HSP 56kb/s modem in
> RedHat Linux 6.2 but in vain. I tried using minicom but it just does not
> detect my modem.
For general reference:
The way to find PCI modems is:
lspci -v | less
>
>
> Since I have both Linux and Windows 98 installed in computer, my HSP Modem
> is configured in the COM4 in Windows or in /dev/ttyS3 in Linux.
For general reference:
If your modem is not at the standard address for ttyS3, you need to tell the
driver where it is. This is usually the case with PCI modems.
>
>
> I would really appreciate it if I could get some help for configuring my
> modem to run in Linux since I use Linux nearly all the time. I just have
> have to use Windows just to get connected to the Internet.
>
> Thanks and awaiting your relpy soon
>
> From,
>
> Apple
>
> --
> Posted via CNET Help.com
> http://www.help.com/
But none of this will help since those letters: HSP indicate that it is a
WINMODEM:
http://www.o2.net/~gromitkc/20001005a.html
JRT
------------------------------
From: Robert MacGregor <[EMAIL PROTECTED]>
Crossposted-To: comp.graphics.api.opengl,comp.graphics.packages.3dstudio
Subject: Re: PIII vs Athlon
Date: Fri, 20 Oct 2000 17:02:40 -0700
Out of the murky depths of comp.graphics.packages.3dstudio, the terrible
Edward Lee arose and bellowed forth:
> Michael Thornberg wrote:
>
> > What is important however is standard and that is Intel. Simply because it
> > is their invention.
> > Amd is just cloning them and there ARE issues with the amd processors that
> > WILL cause
> > problems if working professionally with them. This mainly being not
> > following the intel standard
> > fully. Of course this is because Intel does not give all it's secrets away
> > but since most software
> > today relies and is built upon Intel for that very reason the fact will
> > remain.
> >
>
> This may be true for windows, but not for Linux. The Intel only stuffs are
> simply non-existance or carefully #ifdef away. That's why i am using Linux, i
> don't want to be restricted to Intel only CPU.
>
> >
> > Now end this tiring subject ok?
> >
>
> Absolutely, with Linux, we don't care much about the brand of CPU.
Even with Linux a crappy CPU and/or chipset can cause your system to be
an unstable piece of junk.
------------------------------
From: Ton <[EMAIL PROTECTED]>
Subject: Re: Redhat 7 + ide patches = trouble ??
Date: Sat, 21 Oct 2000 01:57:11 +0200
Of course I was talking about applying the right patches, not the ones that
are already included :-)
Ton
Hal Burgiss wrote:
> On Sat, 21 Oct 2000 01:17:24 +0200, Ton <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >Could anyone tell me if and why it is absolutely necessary to download
> >the fresh source tree from kernel.org, instead of using the default that
> >comes with RedHat 7, to make the (Hedrick's) ide patches work without
> >modifications of the source, and to make compilable kernels, not getting
> >rejects or error #2's?
>
> Redhat's kernels already have a lot of patches applied would be my
> guess.
>
> --
> Hal B
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> --
--
ICQ 3923462
'So if you want my address, it's number one at the end of the bar..' (Fish)
"Windows as a rule does not crash for no reason. There is always a
reason, but finding it may take a little time."
------------------------------
** 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
******************************
