Linux-Hardware Digest #93, Volume #10 Sat, 24 Apr 99 05:13:28 EDT
Contents:
Re: SCSI CD-ROM problem (David Corn)
Re: Partioning a drive with ez-bios (Bradley M Keryan)
5687-02 setup here (allen kurt savegnago)
Pacbell ADSL ("Ting")
Modem recognized by minicom but not chat or dip ("Mark Story")
Can't access printer, help! (Oliver Klimek)
Re: kernel 2.2.6: ATAPI Zip Drive still a problem (cdog)
HOWTO Awe64, Ditto Max and 3COM/USR 56k internal ("nicholas butler")
Re: ESS ES1938 PCI Audiodrive (Bradley M Keryan)
Re: ESS Maestro (Bradley M Keryan)
Re: 2.2.5 Kernel is dead (Bradley M Keryan)
Re: Red Hat 5.2 Question (Bradley M Keryan)
Re: Problems with 3Com 3c509b network i/f. ("Steven Koutstaal")
S3Trio3D XFree86 ("Steven Koutstaal")
----------------------------------------------------------------------------
From: David Corn <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,linux.redhat.misc
Subject: Re: SCSI CD-ROM problem
Date: Fri, 23 Apr 1999 23:14:25 +0000
Thanks for your help! I ran dmesg, saw that my 2nd (unused/unmount)
CDROM drive was hdd, changed fstab a bit, and now I have 2 CDROM drives
under Linux.
Thanks for the help!
DC
diahedrial wrote:
>
> Try "ls -l /dev/cdrom" I think you will find that it is pointing to the
> wrong device, like /dev/hdc rather than /dev/sr0. Type "dmesg" and see
> what device the cdrom is (/dev/sr0 maybe). If /dev/cdrom doesn't point
> to that, delete it, "rm -f /dev/cdrom" and create a new link to the
> correct device, "ln -s /dev/sr0 /dev/cdrom" (if sr0 is the right device
> for your cdrom). Now try "mount /dev/cdrom" and it should work. Hope
> this helps,
> -diahedrial
>
> [EMAIL PROTECTED] wrote:
> >
> > Hello all,
> >
> > after installing RedHat 5.2 from an IDE CD-ROM, I decided to replace the
> > drive with a Pioneer DR-766 SCSI CD-ROM. The problem is that I cannot mount
> > it. The 'mount /dev/cdrom' command gives a message saying '/dev/cdrom is not
> > recognized as a block device' and it fails. '/dev/cdrom' is the name in the
> > file system setup. The SCSI card is an Adaptec AHA-2940AU, and during boot,
> > both the card and the CD-ROM drive seem to be recognized properly.
> > Termination is also okay as far as I can tell. I know that the CD-ROM and
> > also SCSI in general have to be supported in the kernel. After reading the
> > kernel howto, I decided to re-run the configuration to make sure they are
> > enabled. Unfortunately, the 'make config' command does not work, it's not
> > located in the /usr/src/linux directory as the howto says it should be.
> >
> > Can someone give me advice what should I do to make the drive to work?
> >
> > Thanks,
> >
> > Tamas.
> >
> > -----------== Posted via Deja News, The Discussion Network ==----------
> > http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Bradley M Keryan <[EMAIL PROTECTED]>
Subject: Re: Partioning a drive with ez-bios
Date: Sat, 24 Apr 1999 00:03:59 -0400
On Fri, 23 Apr 1999, Allan Manning wrote:
> I have a 10Gb hd, but my system bios won't recognize over 8.4 Gb, so I
> have a program called ez-bios controlling the drive so that I can use
> all 10 gigs. But when I run the Linux fdisk, it doesn't recognize the
> partion, and tells me there are no available sectors to create linux
> partions, also it reports that my hd has 1027 cylinders, too many above
> 1024, please help, as I don't want to have to buy a motherboard that
> will support >8.4 Gb hdds.
> I have also flashed my bios with no luck.
Sounds like you're using the 2.0.x kernel; 2.2.x has better IDE geometry
detection (it detects my 9.1GB Seagate ST39140A correctly). So one fix is
to upgrade your kernel.
The other fix is to specify the correct geometry (cylinders, heads,
sectors). You can do this by entering "expert mode" in fdisk and changing
the geometry there. Once it's in the partition table, the kernel will
accept it as being true. Just be careful to get it right (check your HD
manual).
Either way, the partition your kernel is on (either / or /boot) has to be
within the first 1024 cylinders so the BIOS routines can read it. A tiny
(10-20MB) /boot partition will do fine.
Ditch EZ-bios, you don't need it for Linux and it's getting in the way. If
all your DOS drives (if any) are in the first 1024 cylinders and your
/boot is in the first 1024 cylinders, you should be fine.
Brad
------------------------------
Subject: 5687-02 setup here
From: [EMAIL PROTECTED] (allen kurt savegnago)
Date: Sat, 24 Apr 1999 04:52:09 GMT
Here is the helpfile to get the 3Com 5687-02 Plug and Pray modem running
in Linux. It has helped 12 other folks to get it working.
Subj: 5687-02 modem setup here
Hi,
Here is a help file I wrote to get the 3Com 5687-02 modem to work under
Linux. I had four requests from folks and composed this file. They all
have the 5687-02 (Plug-and-Pray) modem working under Linux as I do.
I received the modem as a gift on Christmas and spent the day getting it
working. I posted notice of this and received four requests as to
how I got it to work. I am now posting this publicly so if one does a
dejanews or other search, they will get a hit and be on their way to get the
modem working under Linux. Read the file carefully and print it out to
refer to. There is a line (VERIFLYD N) that is not placed appropriately in the
pnpdump file. The printout will show where to put it. Here is the file:
Subject: Re: U.S. Robotics 5687-02 Faxmodem
Sorry for the delay. I was upgrading a FIC-503+ board over the weekend
with an AMD 400Mhz cpu and 262Mb of ram. I got into a bind and that is the
reason for the delay. The GIMP program runs much faster now when
processing images though I am not very good at it yet.
My old Winblows 950a version was very glitchy and I couldn't get reliable
boot ups without GPF's. When I could get into it though, it was very fast.
I had to purloin a copy of Winblows 98 from the office and dang, that thing
is bloated. Slowed down my system a bit but at least it boots reliably.
Now getting to your modem problem. The thing to remember is I use Slackware.
I started out with it 4 years ago and just got used to it. I've tried the
other major versions of Linux but always gravitated back to the simple
Slack distribution in spite of its' drawbacks.
One thing I find very disconcerting is that some folks have been trying to
set the convention of the com ports to ttyS"X" instead of cua"X". I ran into
trouble with trying to set up ppp-2.3.5 as it would only recognize a
ttyS"X" port and Slack is STILL using cua"X". If this is a problem with you,
I can send more details as it entails modifying the setup script and is
actually pretty easy to do. My problem was finding the right file.
What follows is my pnpdump file. It is an abridged file as I have dropped
out the pnp sound card. My el cheapo sound card is pnp but allows one
to jumper it if they so desire. I jumpered mine and it works fine but
pnpdump still detects it and prints out the options the card can use.
I uncommented the lines as you can see below so the modem uses com2 and
interrupt 3. I guess one can experiment with these settings and assign
a card to wherever the "preset" options allow them to. Anyhow, enough
of my b.s. and here is the file:
(INSERTED FILE)
# $Id: pnpdump.c,v 1.15 1998/05/25 17:22:16 fox Exp $
# This is free software, see the sources for details.
# This software has NO WARRANTY, use at your OWN RISK
#
# For details of this file format, see isapnp.conf(5)
#
# For latest information on isapnp and pnpdump see:
# http://www.roestock.demon.co.uk/isapnptools/
#
# Compiler flags: -DREALTIME -DNEEDSETSCHEDULER
#
# Trying port address 0203
# Board 1 has serial identifier e5 ff ff ff ff 70 00 8c 0e
# Board 2 has serial identifier a5 fc d9 b9 a6 31 30 72 56
# (DEBUG)
(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERIFYLD N)
# Card 2: (serial identifier a5 fc d9 b9 a6 31 30 72 56)
# Vendor Id USR3031, Serial Number 4242127270, checksum 0xA5.
# Version 1.0, Vendor version 0.0
# ANSI string -->U.S. Robotics 56K FAX INT<--
#
# Logical device id USR3031
# Device supports vendor reserved register @ 0x38
# Device supports vendor reserved register @ 0x39
# Device supports vendor reserved register @ 0x3d
# Device supports vendor reserved register @ 0x3e
#
# 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 USR3031/4242127270 (LD 2
# Multiple choice time, choose one only !
# Start dependent functions: priority preferred
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x02f8
# Maximum IO base address 0x02f8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
(IO 0 (BASE 0x02f8))
# IRQ 3, 5, 7, 10, 11, 12 or 15.
# High true, edge sensitive interrupt (by default)
(INT 0 (IRQ 3 (MODE +E)))
# Start dependent functions: priority acceptable
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x03f8
# Maximum IO base address 0x03f8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
# (IO 0 (BASE 0x03f8))
# IRQ 2, 3, 4, 5, 7, 10, 11, 12 or 15.
# High true, edge sensitive interrupt (by default)
# (INT 0 (IRQ 4 (MODE +E)))
# Start dependent functions: priority acceptable
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x03e8
# Maximum IO base address 0x03e8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
# (IO 0 (BASE 0x03e8))
# IRQ 2, 3, 4, 5, 7, 10, 11, 12 or 15.
# High true, edge sensitive interrupt (by default)
# (INT 0 (IRQ 2 (MODE +E)))
# Start dependent functions: priority acceptable
# Logical device decodes 16 bit IO address lines
# Minimum IO base address 0x02e8
# Maximum IO base address 0x02e8
# IO base alignment 8 bytes
# Number of IO addresses required: 8
# (IO 0 (BASE 0x02e8))
# IRQ 2, 3, 4, 5, 7, 10, 11, 12 or 15.
# High true, edge sensitive interrupt (by default)
# (INT 0 (IRQ 2 (MODE +E)))
# End dependent functions
(ACT Y)))
# End tag... Checksum 0x00 (OK)
# Returns all cards to the "Wait for Key" state
(WAITFORKEY)
(END OF INSERTED FILE)
Got all that? If you noticed the (VERIFYLD N) line. Make sure your file
says that. I also removed the "#" to uncomment the 0x02f8 line and
the IRQ3 (MODE +E) lines. It will be easier to see if you print this out
to hardcopy. Now I think the lines below what I have uncommented would
set a modem up to com 1 interrupt 4 though I haven't tried it in my system.
You can experiment but you have to uncomment the appropriate lines and
if you have the wrong line uncommented or too many of them untagged, it
won't work.
The next step is how does one get this thing to work? Well, the above
file is known as the isapnp.conf file and one has to put it into the
/etc directory. If you boot your machine, log in and type isapnp, it should
initialize the modem.
I like the thing to initialize automatically so I discovered by blind
chance that if I add the line "isapnp /isapnp.conf" to the last line in the
rc.S file that resides in the etc/rc.d directory, the modem will be
appropriately initialized on boot-up. I can't remember if such a file
exsists in Redhat but I think you can experiment with this.
Let me suggest that you print out my file above and your own "pnpdump"
file. Go to the modem section and compare my file with what is presented.
Uncomment out the appropriate lines, make sure your file reads similarly
to what I have written (you may have to change the com port) and see if
it works. Let me know how things turn out!
Best regards,
Kurt Savegnago
[EMAIL PROTECTED]
* 1st 2.00 #6533 * "Windws is ine for bckgroun comunicaions" - Bll Gats, 192
--
------------------------------
From: "Ting" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc
Subject: Pacbell ADSL
Date: Fri, 23 Apr 1999 21:53:08 -0700
I signed up with Pacbell's $49/mon ADSL service. They will provide
Kingston KNE40T NIC. Does anybody know whether this card
works with Linux? If it does, what kind of options should I compile
into kernel (NE2000 support, etc)? I am using RedHat 5.2.
Thanks in advance.
-Ting
------------------------------
From: "Mark Story" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc
Subject: Modem recognized by minicom but not chat or dip
Date: Fri, 23 Apr 1999 22:34:05 -0700
I have been trying to setup ppp but am having problems getting either chat
or dip to recognize the modem. The modem is a Supra 288i and works fine
with minicom. Any ideas on how to troubleshoot this problem?
------------------------------
From: [EMAIL PROTECTED] (Oliver Klimek)
Subject: Can't access printer, help!
Date: 24 Apr 1999 05:34:48 GMT
I have just installed Suse Linux (Kernel 2.2.5) and I cannot access my
printer at all (Epson Stylus Photo). When I do a simple cat file >
/dev/lp0 I get the message "operation not supported by device". lsmod
shows that lp and parport are loaded in the kernel. I suspect that I also
nee parport_pc, but when I try to modprobe parport_pc I get an error
"device busy".
Please tell me how I can get the printer to work
Oliver Klimek [EMAIL PROTECTED]
------------------------------
From: cdog <[EMAIL PROTECTED]>
Subject: Re: kernel 2.2.6: ATAPI Zip Drive still a problem
Date: Fri, 23 Apr 1999 21:54:21 -0500
Reply-To: [EMAIL PROTECTED]
So what the problem? Drives are rated in a raw size and actual size. And since a
kB is 1024 bytes the byte
-kB sizes jive.
[EMAIL PROTECTED] wrote:
> I have compiled the new ATAPI (floppy) support into my new 2.2.6 kernel.
> Unfortunately, after showing the device, etc., there are two error messages in
> /var/log/messages (and thus obviously also when I use fdisk):
>
> hdb: 98288kB, 196576 blocks, 512 sector size
> hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
>
> The drive reports both 100663296 and 100646912 bytes as its capacity. (I
> tried the IOMEGA instruction to disable BIOS support, but the problem
> remains.)
>
> Guessing from these error messages, IOMEGA may have been sloppy in its
> firmware, reporting inconsistent numbers depending on how it is queried. Is
> this guess correct?
>
> Even if it is IOMEGA's fault, can the kernel driver be made smart enough to
> handle this problem, e.g., by suppressing the incorrect size?
>
> /ivo welch
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
Reply-To: "nicholas butler" <[EMAIL PROTECTED]>
From: "nicholas butler" <[EMAIL PROTECTED]>
Subject: HOWTO Awe64, Ditto Max and 3COM/USR 56k internal
Date: Sat, 24 Apr 1999 09:32:52 +0100
I have made a first attempt at constructing a HOW to on the subject of
getting AWE64, DITTO Max and 56kInternal modems to work. Its a First draft,
probably quite embarrassing really, but I have pulled from my notes the
issues which arose when installing these devices and I hope you all find it
useful.
http://www.ashaman.force9.co.uk/nik/linux/pnpexample.html
------------------------------
From: Bradley M Keryan <[EMAIL PROTECTED]>
Subject: Re: ESS ES1938 PCI Audiodrive
Date: Sat, 24 Apr 1999 00:14:43 -0400
On Fri, 23 Apr 1999, George Del Monte wrote:
> Has anyone discovered how to set up this relatively new on-board sound
> interface also known as, I think, the Solo-1? I'm unwilling to pay
> $30.00 for a driver in the OSS package.
>
I don't have one (anymore) but it's on the ALSA driver supported soundcard
list.
http://www.alsa-project.org/
Brad
------------------------------
From: Bradley M Keryan <[EMAIL PROTECTED]>
Subject: Re: ESS Maestro
Date: Sat, 24 Apr 1999 00:20:35 -0400
On Fri, 23 Apr 1999 [EMAIL PROTECTED] wrote:
> Has anybody gotten Red Hat 5.2 to work with the ESS Maestro sound board. I
> have tried many different settings and it always says it is busy. Any
> suggestions?
>
The status of ESS Maestro support is at
http://roadrunner.swansea.uk.linux.org/oss.shtml
with a hint as to how to get it to possibly work even though it's not
really supported yet.
Brad
------------------------------
From: Bradley M Keryan <[EMAIL PROTECTED]>
Subject: Re: 2.2.5 Kernel is dead
Date: Sat, 24 Apr 1999 00:32:59 -0400
On Fri, 23 Apr 1999 [EMAIL PROTECTED] wrote:
> The kernel seems frozen after the message "OK, booting the kernel", but I can
> see in the syslog of the server that it is requesting the dhcp server and
> mounting the networked file system. That's means that the kernel is working,
> but that there is no display. However, I've checked the CONFIG_VT and
> CONFIG_VT_CONSOLE, but that is'nt enough....
>
You didn't turn off CONFIG_VGA_CONSOLE, did you? You need it.
Mmm, spam.
Brad
------------------------------
From: Bradley M Keryan <[EMAIL PROTECTED]>
Subject: Re: Red Hat 5.2 Question
Date: Sat, 24 Apr 1999 00:28:05 -0400
On Fri, 23 Apr 1999, Sal Capaci wrote:
> I was at the Red Hat support page and it said if the hardware wasn't listed,
> it wasn't supported. I didn't see my video card, and the DVD drive said it
> wouldn't work with Linux. I'm new to Linux, so what is an XServer? Do you need
> it? and is there any way to get it to work with my new system? thank you for
> any answers.
Link to the Banshee video driver beta:
http://glide.xxedgexx.com/3DfxRPMS_vb_glibc.html
General newbie questions (what is an Xserver etc):
chapter 1.4.3 of this document: http://metalab.unc.edu/mdw/LDP/gs/gs.html
or go to a bookstore and pick up a book on Linux like _Running_Linux_ by
Matt Welsh.
Also, I've used a Hitachi GD-2000 DVD drive under Linux and it worked just
like a normal CD-ROM, unless yours is "special" there should be no problem
(except the lack of DVD-movie support).
Brad
------------------------------
From: "Steven Koutstaal" <[EMAIL PROTECTED]>
Subject: Re: Problems with 3Com 3c509b network i/f.
Date: Sat, 24 Apr 1999 09:35:28 +0200
for turning off the PnP, go to the 3Com site, and download the support
disks, boot your pc to dos mode, disable PnP, set the IRQ & IO to a
(predetermined) available value and you should be fine.
Also in exerimenting with kernels it is quite useful to compile the support
first as a module, not right in there so you can fiddle around with the
start options. I find with the 3C509b that it needs an io=(value) while
starting.
success!
Steven Koutstaal
Andy Buckley wrote in message <[EMAIL PROTECTED]>...
>We're having a few problems getting a 3Com 3c509b network card to work
>under linux - there are no errors upon booting but the IRQ and base
>adress aren't the same as windows 95 seems to recognise. When booting is
>complete however there are no networking facilities (ping, telnet etc)
>are working. We've tried various kernels from 2.0.34 to 2.2.6 with no
>luck. Does anyone have any ideas as to what we're doing wrong.
>
>Cheers,
>
>Andy and Phil.
>
------------------------------
From: "Steven Koutstaal" <[EMAIL PROTECTED]>
Subject: S3Trio3D XFree86
Date: Sat, 24 Apr 1999 09:28:35 +0200
Does anyone know of a server for my (yes, it's in an IBM) S3Trio3D. Yhe
current software I've got says I should be satisfied with a VGA16 server.
Steven Koutstaal
[EMAIL PROTECTED]
or
[EMAIL PROTECTED]
------------------------------
** 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
******************************
