Linux-Hardware Digest #464, Volume #12 Sun, 12 Mar 00 19:13:04 EST
Contents:
Install locks up (Ken)
Re: How to add new hardware in Linux? (Matti Juhani Kurkela)
Re: Ultra66 RH6.1 installs, but LILO hangs (John Noble)
Re: COM1 or COM2 for the ext. modem; whats optimal? ("Roger Hamlett")
Re: UDMA66 HPT366 linux driver (Bryan)
Re: ATA66 and Linux (Hal Burgiss)
Re: Ultra66 RH6.1 installs, but LILO hangs (Alan Burns)
Re: D-Link DFE-550TX Ethernet card...supported??? (Kris)
Re: Real audio, /dev/mixer (Martin Booth)
Re: VIA vs Intel chipsets - which is better? (Bill Moseley)
BE6-II mobo no > 64MB ("Felonius Monk")
Re: ATA66 and Linux (A transfinite number of monkeys)
3com nic problem (Jim Colgan)
Re: BE6-II mobo no > 64MB (Dances With Crows)
Re: Zoom modem configuration (Jim Jerzycke)
Re: need help with pcmcia scsi. ("Robert M. Stockmann")
----------------------------------------------------------------------------
From: Ken <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.redhat,comp.os.linux.setup
Subject: Install locks up
Date: Sun, 12 Mar 2000 20:18:37 GMT
All,
I am trying to install Redhat 6.0 on a computer with a Tyan Titan Turbo
S1572 motherboard.
>From either the floppy or the CD, i lock up right after i get past
the SCSI detection.
I have stripped the ocmputer down to only a video card (Diamond V330),
and still no luck.
Any ideas ?
Ken
------------------------------
From: Matti Juhani Kurkela <[EMAIL PROTECTED]>
Subject: Re: How to add new hardware in Linux?
Date: 12 Mar 2000 22:40:02 +0200
Per Inge Oestmoen <[EMAIL PROTECTED]> writes:
> As a newcomer to Linux, there is a question that seems less obvious than
> it should be:
>
> When one buys a Linux distribution, often you have hardware which is not
> supported by the material found in the present package. That is cool; I
> know that the support is under way.
>
> However, there the problem arises: In the absence of a Windows-style
> driver model, how is support for new hardware in Linux added?
Basically, there are two possibilities.
If the new hardware uses some standard interface which is already
supported (and its data-transfer requirements are not too great)
the support may come in the form of an utility program,
which is installed just like any other program.
(That is: if the program comes e.g. as a RPM package, you use your
favorite package management tool to install it. If there's only the
source of the program available, the installation usually goes
more or less like this:
less README
less INSTALL
./configure
make
make install
...and then maybe edit a configuration file or two according to the
instructions in the README and/or other included documents.
Done!)
Otherwise, the support will be included in the Linux kernel (or as a
separate kernel module). This will often require you to compile
yourself a new kernel. (For more information, see e.g. the appropriate
HOWTO document and/or the documentation of your distribution.)
Compiling a kernel is not too difficult nor at all dangerous per se.
The amount of configurable options at the start of kernel compilation
might seem daunting, but the configuration system has a very
informative help system. It even contains hints like "Most people will
say N here" or "Answer Y unless you *know* you don't need this".
However, when you install your new kernel be sure to ensure that you
have a fallback option of some sort if your new kernel turns out to be
non-functional.
The complete kernel source package is about 16 MB in size, so it might
be a pain to download. There is a way around this, though: you can
download a patch to upgrade your existing kernel source to a next
newer version. These patches are orders of magnitude smaller than the
complete kernel source: however you'll need to apply one patch for
every step of increment in the version number, and the patches *must*
be applied in order. (A failure in patching is not immediately fatal:
at worst it means that you must obtain a "clean" kernel source package
before you can compile a new kernel.)
> A case in point is my own SCSI card, scanner and graphics card.
> Then the question arises: How do we a) find and b) install the necessary
> additions that will allow the use of new hardware? Understandably, some
> form for upgrade must happen, but how is this accomplished? I take for
> granted that one does not have to buy/download a new distribution after
> each time a new piece of hardware is added, but what exactly are the
> procedures for adding it?
SCSI card:
The support for SCSI cards is certainly a part of the kernel.
The Linux kernel archive (http://www.kernel.org/) has the current
kernels and http://www.kernelnotes.org/ documents the changes between
kernel versions. Both have some documentation about compiling and
installing a new kernel.
Scanner:
The Linux scanner support is being developed by the SANE project.
See their homepage ( http://www.mostang.com/sane/ ) for more information.
Graphics card:
Usually the Linux graphics hardware support is provided by the X
server. The majority of Linux users seem to use XFree86, although
there are some some alternatives (some of them proprietary).
See http://www.xfree86.org/ for updates and more information.
(By the way, the major update Xfree86 4.0 has just been released.
Only source packages seem to be available for Linux as yet, though:
I'd wait for the Linux binaries rather than recompile the entire X
sub-system from sources.)
--
[EMAIL PROTECTED] <URL: http://www.hut.fi/u/mkurkela/ >
The universe runs through the complex interweaving of energy, matter,
and enlightened self interest.
------------------------------
From: John Noble <[EMAIL PROTECTED]>
Subject: Re: Ultra66 RH6.1 installs, but LILO hangs
Date: Sun, 12 Mar 2000 21:30:03 GMT
First off, Thanks to all for the input. I got lucky and managed to figure
it out. My 2 Ultra66 drives map to /dev/hde and /dev/hdg. The MBR where
LILO lives is on /dev/hde and Linux is on /dev/hdg. Because Linux is on
/dev/hdg and not /dev/hdf, I needed to map /dev/hdg to the second drive.
All I needed was:
disk=/dev/hdg
bios=0x81
in my lilo.conf.
Here's my current working version:
boot=/dev/hde
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
disk=/dev/hdg
bios=0x81
image=/boot/vmlinuz-2.2.12-20
label=linux
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/hdg9
append="ide2=0x18b8,0x18ac ide3=0x18b0,0x18a8"
other=/dev/hde1
label=win
Now, on to the next problem :)
-John
John Noble wrote:
>
>
> So I've made some progress with my Promise Ultra66 and RedHat 6.1.
> I'm able to get the install done with the ide2=addr,adrr ide3=addr,addr
> trick, but
> then I run into trouble with LILO. When I try to boot off the first
> Ultra66 drive, LILO hangs at "LI".
>
> I've got 2 Ultra66 drives on this system. The first with Win98 and the
> other specifically for Linux. I put all my partitions on the second
> drive (/boot, /, all of it) and then install LILO on the MBR of the
> Win98 drive. I've added the ide2=addr,addr ide3=addr,addr to the append
> of the lilo.conf, but to no avail. I have not installed and new
> kernels/patches for Ultra66 support. I figure I shouldn't have to just
> to get LILO to boot the system right?
> I'm pretty sure /boot is under the 1024 cylinder limit, but it's on a
> different drive than where LILO is installed (LILO is on the MBR of the
> win98 drive, /boot is on the other drive) should this matter?
> I took the lilo.conf that the RH 6.1 installer created and tired adding
> "linear" and "bios=0x80" to the global section, but that did not help.
> If this is a disk geometry problem, how can I tell if it is and any
> ideas how I would solve it?
>
> Should I use another loader (maybe ChooseOs)?
>
> Any clues here to any of this?
>
> Thanks
> pulling out my hair
> -John
>
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "Roger Hamlett" <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.periphs.mainboard.asus,comp.sys.ibm.pc.hardware.chips,comp.sys.ibm.pc.misc
Subject: Re: COM1 or COM2 for the ext. modem; whats optimal?
Date: Sun, 12 Mar 2000 17:50:17 -0000
Keith R. Williams wrote in message ...
>On Sun, 12 Mar 2000 12:34:33, "Wayne Monteath"
><[EMAIL PROTECTED]> wrote:
>
>> COM2 uses IRQ3.
>> COM1 uses IRQ4
>>
>> IRQ3 gets serviced (has a higher priority) before IRQ4.
>
>This is backwards (which is why COM1 is on IRQ4 by default), but
>it doesn't matter in any case.
I agree it doesn't really matter, but the priority order given is
correct. The order on a PC is:-
0 1 2 8 9 10 11 12 13 14 15 3 4 5 6 7
Com2, was assumed in the original PC, to be a higher data rate channel
than Com1.
Best Wishes
------------------------------
From: Bryan <Bryan@[EMAIL PROTECTED]>
Subject: Re: UDMA66 HPT366 linux driver
Date: Sun, 12 Mar 2000 22:13:29 GMT
kernel source mirror (ftp.kernel.org), under 'people' and 'hedrick'.
ide*patch files.
Damon Tsang <[EMAIL PROTECTED]> wrote:
: Do anyone know where to find Highpoint HPT366 UDMA66 linux driver.
: -- Damon
--
Bryan, http://Grateful.Net (ANTISPAM: email is my name at my web's domain)
(c) 2000. Publishing and/or relaying of this material on all forums other than
USENET implies agreeing to a consultancy fee of US$150 per posting. You must
obtain a written permit before you publish. Violators are subject to civil
prosecution for Copyright Infringement as applicable. Publication by C|NET
and Microsoft Networks expressly prohibited.
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Crossposted-To: alt.os.linux,linux.redhat.install
Subject: Re: ATA66 and Linux
Reply-To: [EMAIL PROTECTED]
Date: Sun, 12 Mar 2000 22:29:25 GMT
On Sun, 12 Mar 2000 19:45:14 GMT, news-server.optonline.net
<[EMAIL PROTECTED]> wrote:
>I have a dell 700mhz system with an ata66 controller card, and I am
>trying to install redhat linux 6.1. When I get to the part where I
>select what kind of installation I will perform, it says that it cannot
>find any media to install to, and then leaves me hanging. What is an
>ata66 controller card and how do I get it to work with linux (I am very
>comfortable with computers in general, but only so-so with linux).
The RH6.1 installer will not recognize UDMA66 drives on UDMA66
controllers. Your options are using a distro that does. Someone has said
that the most recent SuSE does. Or connect the drive to a std UDMA33
controller, install, then get the kernel patches that do support UDMA66
and go from there.
--
Hal B
[EMAIL PROTECTED]
--
------------------------------
From: Alan Burns <aburns@!SPAMTRAP.ebicom.net>
Subject: Re: Ultra66 RH6.1 installs, but LILO hangs
Date: Sun, 12 Mar 2000 16:15:36 -0600
In article <[EMAIL PROTECTED]>, John Noble <[EMAIL PROTECTED]> wrote:
>
> So I've made some progress with my Promise Ultra66 and RedHat 6.1.
> I'm able to get the install done with the ide2=addr,adrr ide3=addr,addr
> trick, but
> then I run into trouble with LILO. When I try to boot off the first
> Ultra66 drive, LILO hangs at "LI".
I had the same problem a few weeks ago with my new 27GB Maxtor, and
I absolutely pulled my hair out trying to get the friggin thing to work. I read
all the HOWTOs and other docs, and I never could get it to work right
on the install. I don't know if this is an option for you, but here's what I
had to do:
I have a plain old EIDE controller and a SCSI adapter on my motherboard,
and my UDMA controller is an off-board type. I had to yank the Promise
controller out and hook the drive up to the EIDE onboard to do the install.
The system BIOS couldn't recognize the drive and reported it as 540 MB,
so I disabled hard drive detection but left the chipset enabled. Linux
will still see the full capacity when it loads the IDE drivers. (Linux is
so COOL :-)
After the installation was finished, I put the UDMA back in, connected the
drive to it, and disabled the onboard chipset in the BIOS. (This will mess
you up if you leave it on because the drive on the UDMA will be reported
as hde instead of hda and you'll get a kernel panic.) On the first boot, pass
your ide paramaters to LILO, and everything should work, albeit without
Ultra66 support.
You can then compile one of the 2.3.x series kernels with Ultra66 support
enabled. I'm using 2.3.46 right now with no problems, and hdparm -t reports
about 13 MB/s on the drive. Once I got everything working, I went to the
LILO HOWTO and learned how to boot 2.3.46 from a floppy to avoid having
to pass the ide paramaters next time I have to do an install.
It's a kludge, I know, but at least it works. Hope this helps.
------------------------------
From: Kris <[EMAIL PROTECTED]>
Subject: Re: D-Link DFE-550TX Ethernet card...supported???
Date: Sun, 12 Mar 2000 22:52:12 +0000
Tony R. Bennett writes:
> I checked the HOWTO and it does not list this card as being
> supported... But I see that there are quite a few 'clone'
> NIC's... is this one???
>
> I 'came' with my Toshiba M500 Server... I could just buy another
> NIC but not if it isn't necessary.
That card uses the via-rhine driver; so yes, it's fully supported. (I
use it myself and very nice it is too).
Adios,
Kris
--
Kris | [EMAIL PROTECTED]
PGP/GPG: DH/DSS/1024 0x34941A9F
F438 005B 9700 E14E 0B8F D3D7 C98E CF45 3494 1A9F
------------------------------
From: Martin Booth <[EMAIL PROTECTED]>
Crossposted-To: [EMAIL PROTECTED]
Subject: Re: Real audio, /dev/mixer
Date: Sun, 12 Mar 2000 23:03:05 +0000
> Find the URL of the RA file, then use wget to fetch it...I've used this
> method before now, with some success. Similarly works for midi files,
> mods, wavs, and anything else that gets thrown on a web page.
>
> Chris...
I tried that:
wget pnm://ravi.***.de/.../42.ra
and:
--22:55:23-- ftp://pnm:21/%2Fravi.****de/.../42.ra
=> `42.ra'
Connecting to pnm:21...
pnm: Host not found
Where *** is the various parts of the address.
How was the exact terminology which you used? It didn't seem to work for me.
Thanks for the help,
Martin Booth.
P.S. In case of E-mail remove the nospam.
------------------------------
From: Bill Moseley <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.ibm.pc.hardware.chips,comp.sys.ibm.pc.hardware.systems
Subject: Re: VIA vs Intel chipsets - which is better?
Reply-To: [EMAIL PROTECTED]
Date: Sun, 12 Mar 2000 23:03:56 GMT
"Ron Reaugh" <[EMAIL PROTECTED]> wrote:
>
>Paul Tiseo wrote in message ...
>>In article <C8wx4.404$[EMAIL PROTECTED]>,
>>[EMAIL PROTECTED] says...
>>> Gee Ron, I use VIA based MoBo's & have no IDE problems - what am I
>doing wrong? Same with my
>>> customers.... who buy more VIA based MoBo's then Intel?
>>>
>>> Now you can quote post (actually you didn't even do that - you just
>told us where we MIGHT find
>>> some data) all day long... most will be from users have caused their own
>problems. Can you post your
>>> own personal data - like Dean & I can??
>>
>> Whatever you do, John, DON'T GET SUCKERED IN BY RON!!! He lives in
>>*.hardware.storage and he and a few others engage in lengthy, pointless,
>>name-calling threads in SCSI vs. IDE wars. The participants are all
>>very, very stubborn and probably enjoy causing this sort of pointless
>>mischief. It's endless. Plenty of references to "blindness" and
>>"stalking" from both sides, ad nauseum. Sickening, really. All over HDs,
>>for pete's sake...
>>
>> I left that group because of it. Half of the time, Ron is baited
>>and he easily and quickly takes the bait and starts flinging insults.
>>The other half, he's wrong and bullheadedly refuses to acknowledge it.
>
>
>Typical of the kind who has nothing to contribute of technical value to the
>NG. Your type always deals in personalities and not the facts. Why bother
>even posting.
>
Pot. Kettle. Idiot...
I have seen more actual technical info come from posts from newbies on
alt.flame than from "Ron Reaugh".
Biil Palmjob, meet Ron.
<Plonk!>
--
****** Bill Moseley (William E.) [EMAIL PROTECTED] ******
#include <std_disclaimer.h>
"The problem is not that the world is full of fools, it's that lightning
isn't being distributed correctly." -- Mark Twain
------------------------------
From: "Felonius Monk" <[EMAIL PROTECTED]>
Subject: BE6-II mobo no > 64MB
Date: Sun, 12 Mar 2000 23:05:58 GMT
Okay, so I have this Abit BE6-II that won't read any more than 64 megs of
Ram in Linux. It turns out that it's because they banished a call in the
BIOS to make the board ACPI compliant or something, but Linux (at least
2.2.14) relies on that call to accurately detect the right amount of RAM.
There isn't an update for the board, but I was told that I had a couple of
choices:
1) Manually tell the kernel how much RAM I have in the system
2) 2.3 kernels seem to be detecting the right amount of Ram on these boards
My questions:
1) How would I go about telling the kernel how much RAM it should be reading
manually?
2)How stable are the prerelease 2.3 kernels?
Obviously, since I asked the first question, I'm far from a kernel hacker,
but I'd like to get my system reading the right amount of memory....
TIA!
------------------------------
From: [EMAIL PROTECTED] (A transfinite number of monkeys)
Crossposted-To: alt.os.linux,linux.redhat.install
Subject: Re: ATA66 and Linux
Date: Sun, 12 Mar 2000 23:13:58 GMT
On Sun, 12 Mar 2000 22:29:25 GMT, Hal Burgiss <[EMAIL PROTECTED]> wrote:
: >I have a dell 700mhz system with an ata66 controller card, and I am
:
: The RH6.1 installer will not recognize UDMA66 drives on UDMA66
: controllers. Your options are using a distro that does. Someone has said
: that the most recent SuSE does. Or connect the drive to a std UDMA33
: controller, install, then get the kernel patches that do support UDMA66
: and go from there.
You can most times pass parameters to the kernel to do the install, then
rebuild the kernel using the IDE patches to support UDMA66 i/f's...
Mandrake 7.0 detects many UDMA66 controllers and offers support for them..
--
Jason Costomiris <><
Technologist, cryptogeek, human.
jcostom {at} jasons {dot} org | http://www.jasons.org/
------------------------------
From: [EMAIL PROTECTED] (Jim Colgan)
Subject: 3com nic problem
Date: Sun, 12 Mar 2000 23:23:21 GMT
I have a scom 3c920 (3c920c-TX compatible) network card integrated on
a Dell Optiplex machine. I am using Redhat 6.0.
I'm having some trouble getting the card recognised. When I specified
the card in the Lan settings part of the linux installation it failed
to recognise it. I thought then it would be a simple matter of
installing the driver, but then came further problems.
After finding the linux driver on the 3com support site and copying
the tar file onto the machine it doesn't seem to think it is a valid
archive. I tried obtaining a driver from some other site with no luck
and the 3com ftp site had only windows drivers.
Would anyone have this driver perhaps or be able to help me install it
in some other way?
Any hekp would be appreciated.
-Jim
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: BE6-II mobo no > 64MB
Date: 12 Mar 2000 18:56:04 EST
Reply-To: [EMAIL PROTECTED]
On Sun, 12 Mar 2000 23:05:58 GMT, Felonius Monk
<<qpVy4.4221$[EMAIL PROTECTED]>> shouted forth into the ether:
>There isn't an update for the board, but I was told that I had a couple of
>choices:
>1) Manually tell the kernel how much RAM I have in the system
>2) 2.3 kernels seem to be detecting the right amount of Ram on these boards
As for 1, it's in the FAQ. At the LILO prompt, enter "linux mem=128M" or
however much RAM you actually have. Add the line
append "mem=128M"
to the global section of /etc/lilo.conf (before the first "image=" line,
that is) and re-run lilo to make this automatic at every boot.
The most recent 2.3 kernels seem to be working pretty well, except when
they go haywire and hang the SCSI bus or something. Unless you have a
compelling reason for going to 2.3, I wouldn't try it. The memory
detection isn't a compelling reason IMHO.
(Compelling reasons for me would be: I have some hardware 2.3 supports
but 2.2 doesn't, I wish to try out all the nifty new features like devfs,
I want to do my part by testing stuff and sending bug reports, or I'm just
curious and want to play with the latest shiny new toys...)
--
Matt G / Dances With Crows \###| Programmers are playwrights
There is no Darkness in Eternity \##| Computers are lousy actors
But only Light too dim for us to see \#| Lusers are vicious drama critics
(Unless, of course, you're working with NT)\| BOFHen burn down theatres.
------------------------------
From: Jim Jerzycke <[EMAIL PROTECTED]>
Subject: Re: Zoom modem configuration
Date: Mon, 13 Mar 2000 08:02:16 +0000
What model number is it, and do you have the PnP jumper disabled? I've
had extremely good luck using Zoom internal modems, but I always pull
the jumper to disable PnP, and set the other jumpers to force it to a
known com port / irq setting.
Regards, Jim
------------------------------
From: "Robert M. Stockmann" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable
Subject: Re: need help with pcmcia scsi.
Date: Mon, 13 Mar 2000 01:05:12 +0100
Sirron Davis wrote:
>
> I just got a Panasonic KXL-RW10A CD-R/RW for my laptop (with Mandrake
> 7.0 and kernel 2.2.15). This includes a Panasonic pcmcia scsi card.
> However, I have serious problems whenever the card is inserted. I need
> any tips and suggestions you have for configuring my system to work with
> this card.
Please be informed that the latest 2.2 kernel is stil 2.2.14.
If mandrake claims they have kernel 2.2.15, they are lying. I think
the marketing hype has also hit the Linux arena.
So what you do is download linux-2.2.14.tar.gz from ftp.kernel.org
and also the latest pcmcia stuff from sourceforge.org :
ftp://sourceforge.org/pcmcia/pcmcia-cs-3.1.12.tar.gz
On http://pcmcia.sourceforge.org/ftp/SUPPORTED.CARDS you can read that
some of those Panasonic scsi pcmcia cards are supported. they use the
[qlogic_cs driver] .
So boot your laptop with only the networkcard , install kernel and
pcmcia
tar-balls compile them , and if that ain't working come back here.
Please stop nagging about kernel 2.2.15 not working. It don't exsist
at the time of this writing.
Robert
--
++---------------------++---------------------------------++
|| R.M. Stockmann || InfoMagic Nederland VOF ||
|| [EMAIL PROTECTED] || Unix administration & support ||
++---------------------++---------------------------------++
Linux: A copylefted Unix-like operating system for several platforms :
http://perso.wanadoo.es/xose/linux/linux_ports.html
------------------------------
** 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
******************************
