Linux-Hardware Digest #77, Volume #9 Thu, 31 Dec 98 23:13:27 EST
Contents:
help : UPS script problem.......... ("randymale")
Re: need to take action on the Winmodem problem (Byron A Jeff)
Symbios Sym20402 (Keith Berger)
Re: Decent Soundcard for Linux (mike dombrowski)
Which dirvers for Riva TNT & SB128? ("gradste")
Re: Redhat Linux 5.1 and 3com 3c509b-TPO card troubleshooting (T1)
Re: linux wannabe! (Andy Jefferson)
Re: Travan TR2 Floppy tape backup troubles (Frank)
Re: parport/ppa problem with 2.2.0pre1 (Jens Kristian S�gaard)
Re: Best Dual Pentium motherboard, and other hardware (Raymond Lillard)
Re: need to take action on the Winmodem problem (Byron A Jeff)
My Modem doesn�t work ("Philipp Winkler")
video in XWindows -- Help!
Re: Primary Slave HD & FDISK (Andries Brouwer)
Re: More than 8 GByte with IBM-DTTA-351010 (Andries Brouwer)
Is the NS 16550AN Uart Supported? (Nathan Zalman)
----------------------------------------------------------------------------
From: "randymale" <[EMAIL PROTECTED]>
Subject: help : UPS script problem..........
Date: Thu, 31 Dec 1998 17:55:38 -0000
Help!
I'm having a problem to run a script used to install Power Alert Plus
from Tripplite.
I'm Running Redhat Linux Version 5.1 kernel version 2.0.34.
The version of Power Alert Plus is supposed to be compatible with RHL
Version 5.x and according to the full script it probes for different forms
of UNIX as well as Linux.
The software comes with an installation script titled pap_inst. Seems
straightforward to me until I run this under sh and get lines upon lines of
: command not found. Perhaps I am doing something wrong? I've checked it
(#file pap_inst) and get the response :Bourne shell script text. Have also
tried csh with the same errors. I'm inclosing part of the script up to line
121 where it shuts down at with the error :syntax error near unexpected
token '{. Any help I can get on this would be appreciated. I thought I was
going along well with setting up my hardware until this. Oh I also think the
CDROM_DIR variable needs to be changed, but I find the description of this
variable and the documentation limited.
script below to line 121:
#!/bin/sh
#
# Installation script for PowerAlert Plus (UNIX)
#
# @(#)pap_inst 1.13 10/05/98
#
CDROM_DIR=`pwd` # save the dir where the stuff comes from
TMP_DIR="/tmp"
SHUTDOWN_INI="shutdown.ini"
SERVER_INI="server.ini"
PAPLUS_RSD=pap_rsd # remote shutdown monitor executable name
PAPLUS_SERVER=pap_upsd # server executable name
# some utility variables to make things easier to read
NO="no"
YES="yes"
INVALID_RESPONSE="InVaLiD_ReSpOnSe"
PAPLUS_CMD=pap
# try to determine wether we need to use "-n" or "\c" to suppress a newline
DASH_N=`echo -n`
if [ "$DASH_N" = "-n" ]
then
NO_NEWLINE_PARAM="" # -n not supported
NO_NEWLINE_TERM="\\c"
else
NO_NEWLINE_PARAM="-n" # -n supported
NO_NEWLINE_TERM=""
fi
# setup the initial values of our control variables
DONE=$NO
AUTO_START_FLAG=$YES
DEFAULT_AUTO_START_FLAG=$YES
DEFAULT_UPS_IS_LOCAL=$YES
DEFAULT_UPS_SPEED="2400"
DEFAULT_UPS_MANUFACTURER="TrippLite"
DEFAULT_UPS_TYPE="Intelligent"
DEFAULT_UPS_NOM_VOLTAGE="120"
DRIVER_FILE_SUFFIX=".drv"
DEFAULT_UPS_SERVER="No server specified"
# UPS "brands"
MANUFACTURER_TRIPPLITE="TrippLite"
TRIPPLITE_SMART_DRIVER_FILE=tripp1
TRIPPLITE_DUMB_DRIVER_FILE=tripp2
MANUFACTURER_APC="APC"
APC_SMART_DRIVER_FILE=apc1
DEFAULT_DRIVER_FILE=$TRIPPLITE_SMART_DRIVER_FILE
# set the defaults since we'll config one way or the other (local or remote)
UPS_COMM_PORT=$DEFAULT_UPS_COMM_PORT
UPS_SPEED=$DEFAULT_UPS_SPEED
UPS_MANUFACTURER=$DEFAULT_UPS_MANUFACTURER
UPS_TYPE=$DEFAULT_UPS_TYPE
UPS_NOM_VOLTAGE=$DEFAULT_UPS_NOM_VOLTAGE
DRIVER_FILE=$DEFAULT_DRIVER_FILE
UPS_SERVER=""
# UPS "types"
UPS_TYPE_SMART="Intelligent"
UPS_TYPE_DUMB="Contact Closure"
# init files and directories
RC0_DIR=
RC2_DIR=
RC3_DIR=
RC4_DIR=
RC5_DIR=
INIT_D_DIR=
RC0_K_FILE=
RC2_S_FILE=
RC2_K_FILE=
RC3_S_FILE=
RC3_K_FILE=
RC4_S_FILE=
RC4_K_FILE=
RC5_S_FILE=
RC5_K_FILE=
########################################################################
# center a line of text on the screen
centerLine() {
^ this is line 121
thanks in advance,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Byron A Jeff)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: need to take action on the Winmodem problem
Date: 31 Dec 1998 21:43:25 -0500
In article <76ca96$[EMAIL PROTECTED]>,
Michael David Jones <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] (Chris Lee) writes:
->In article <[EMAIL PROTECTED]>,
->[EMAIL PROTECTED] says...
->>On 29 Dec 1998 00:42:57 -0600, Steve Mading <[EMAIL PROTECTED]>
->wrote:
->>>mlw ([EMAIL PROTECTED]) wrote:
->>>I avoid the problem by refusing all internal modems and only getting
->>>externals. If there's no physical connection to the motherboard other
->>>than through a standard rs232 port, then I'm guaranteed that there's no
->>>way in hell it can offload some of its responsibility to the CPU no matter
->>>what it says on the box in the store. Granted it costs about $10-15 more
->>>than an equivilent internal modem, but then you get Dasblinkelights on the
->>>modem. You can never have too many blinkenlights.
->>No. Forcing users to have another power plug on their desk and more
->>cables to cope with sucks pretty severely, even if Dasblinkelights
->>are extremely useful for troubleshooting.
->It's the internal modems that suck dude. Try using/swaping that PC internal
->modem with another computer. What's that? It doesn't work with an Mac or an
->Amiga system? Looks like you have to buy another modem,dude....
-
-This is where the Linux crowd needs to get a good stiff double shot of
-the real world. People buy winmodems. They buy them because they're
-cheap, and because they're good enough for most people's needs. If you
-want those people to consider Linux, you need to make it work with the
-hardware they have. It's really funny, you know. I'm a Unix-head from
-way back, and my first exposure to Linux was from people raving about
-how it would run on just about any old cheap, crufty hunk of silicon.
-Now, suddenly, winmodems aren't good enough for the Linux crowd. Well,
-fellas, I can only say: fish or cut bait.
Mike,
I don't think you've read the rest of this thread. The Linux sprit you speak
of is alive and well. Consider however what a Winmodem is: a specialized
sound card that requires software to operate properly. Software that
unfortunately is based on information that is not publicly available so that
it can be duplicated under Linux.
It isn't that Linux developers don't want to support WinModems, it's that they
cannot because the information that's required to program them isn't available.
Now this leads to the repercussions. There are instances (such as the parallel
ZIP drive) where the need was urgent enough and the interface clean enough
(one can monitor the writes to a parallel port) that a driver could be
reversed engineers. However today's modems use ultra-sophisticated DSP
algorithms to shove as much bandwidth as possible through an ordinary phone
line. Developers are walking blind without either the interface to the modem
or the algorithms required to make it go.
The other repercussion is the fact that Winmodems are not unique, at least
not yet. Both external modems, and internal non-WinModems work fine under
Linux. So with such a steep hill to climb, coupled with such an easy path
around, the motivation to support WinModems is lacking.
I can almost gurantee that if a WinModem manufacturer said "here are the specs
to program our modems" that a Linux driver would soon follow. But I don't
see that statement forthcoming.
BAJ
------------------------------
From: Keith Berger <[EMAIL PROTECTED]>
Subject: Symbios Sym20402
Date: 1 Jan 1999 03:22:41 GMT
Does anyone know where I can find a linux driver for the Symbios SYM20402 ISA
PnP SCSI Adapter. Please email to [EMAIL PROTECTED]
Thanks
Keith
------------------------------
From: [EMAIL PROTECTED] (mike dombrowski)
Subject: Re: Decent Soundcard for Linux
Date: Fri, 01 Jan 1999 03:23:42 GMT
On Thu, 31 Dec 1998 21:35:23 -0500, Martin Robinson
<[EMAIL PROTECTED]> wrote:
>I am wondering what sound ards work well under Linux. I originally
>planned to go with the Sound Blaster AWE64, but have seen some posts
>about problems with Sound Blaster 16 & AWEs with Redhat 5.2. I don't
>really want to use isapnp tools, but will if it is necessary. I don't
>need anything really fancy, just for maybe CD audio, midi(if possible),
>and mp3s. One thing is that I would like it to be compatible enough with
>Sound Blasters that I could use it for DOS(gasp) game that needs
>something SB. I also want something under $100. Any suggestions
>appreciated.
>
>
Ya me too. Does the esoniq AudioPCI work? It's cheap ($28) pci and is
pretty decent as far as sound quality.
Thanks
Mike Dombrowski
------------------------------
From: "gradste" <[EMAIL PROTECTED]>
Subject: Which dirvers for Riva TNT & SB128?
Date: Thu, 31 Dec 1998 23:43:00 GMT
I am brand-new to Linux and want to get the latest drivers for my hardware
before loading the OS. A few questions from you experienced ones:
Can I download files via Windows NT and them be able to read tem from a
floppy and load via Linux 5.1?
There are a huge number of files available at xfree 3.3.3 ftp site for
Linux. How do I know which are the right ones?
Does Linux support SoundBlasterPCI128?
Yes, I know these all sound like idiot questions. As long as you can supply
answers, you can think of me as anything you want. Thanks in advance.
------------------------------
From: [EMAIL PROTECTED] (T1)
Crossposted-To: comp.os.linux.setup,comp.os.linux.install
Subject: Re: Redhat Linux 5.1 and 3com 3c509b-TPO card troubleshooting
Date: Thu, 31 Dec 1998 23:44:55 GMT
I tried that but Linux is still not able to recognize the card. I'm
still getting that "delaying" error message. Maybe I was not doing it
right. Could you kinda help out with this dos setup utility so that I
could see where I am going wrong? I would kindly appreciate it. Thank
you.
On Thu, 31 Dec 1998 23:19:26 GMT, Prasanth Kumar <[EMAIL PROTECTED]>
wrote:
>Try disabling the PnP capability on the card using the dos setup
>utility you can get from 3com (on disk or via ftp server) This
>worked great for my card.
>
>T1 wrote:
>>
>> Hi. I am currently using Redhat Linux 5.1 and am using a 3com
>> 3c509b-TPO card. It worked well in my older PC under all operating
>> systems but when I transferred it to my new PC, it worked well under
>> Windows98 but not under RH Linux 5.1. I tried to get it to the correct
>> I/O and correct IRQ but no luck so far. Does anyone know how to get
>> this ethernet card working once again under RH Linux 5.1?
------------------------------
Date: Thu, 31 Dec 1998 16:21:00 +0000
From: Andy Jefferson <[EMAIL PROTECTED]>
Subject: Re: linux wannabe!
James Barley wrote:
>
> As a newcomer to linux, I've a couple of questions that have I'm sure been
> asked before, but here goes...
>
> Two things I can't get to work, and I miss dearly are my scsi flatbed
> scanner, (AGFA Snapscan) and my printer (Epson Color 600).
> I can get some basic ascii text to print but no color or any of the many
> features the printer is capable of.
>
> Any suggestions on what I can do, or where I can look for help, would be
> helpfull...
As far as the scanner, look at SANE (http://www.mostang.com/sane/)
though I'm not sure if your scanner is supported.
For the printer, get ghostscript 5.10, which supports the Epson range of
printers. RedHat 5+ comes with a version (3.*) of ghostscript, but you
need to upgrade to 5.10 to get Epson support.
HTH
--
Andy Jefferson
------------------------------
From: Frank <[EMAIL PROTECTED]>
Subject: Re: Travan TR2 Floppy tape backup troubles
Date: Thu, 31 Dec 1998 16:27:01 -0600
Paul Nevin wrote:
> Hi there,
>
> I was just wondering if anyone could help me with a floppy tape backup
> unit. The device is a Travan TR2 1.6Gb tape drive running off the
> floppy disc controler.
>
> I have recompiled my kernel to install the ftape (4.x something) drivers
> but the device is failing to mount under /dev/qft0.
>
> Is there something wrong with the included settings recommended in the
> ftape FAQ? It seems odd that the similar tape drive as mine has an irq
> of 65.. is this done on purpose to ensure people look up the correct
> settings?
>
> I have a Pentium II system running linux kernel 2.0.36 and have compiled
> the ftape drivers into modules. My conf.modules looks as follows
>
> alias char-major-27 zftape
> options ftape ft_fdc_driver=ftape-internal,none,none,none
> options ftape-internal ft_fdc_base=0x4711 ft_fdc_irq=6 ft_fdc_dma=13
> pre-install ftape-internal /usr/local/bin/swapout 15
>
> I have changed the IRQ to 6, as I believe this is correct. However I am
> not sure of the other settings for ft_fdc_base and ft_fdc_dma. If there
> is something in here that is obviously wrong please let me know.
>
> Thanks in advance.
hey paul,
i'm having similar troubles... if you find out how to identify the base and
dma, PLS let me know!
------------------------------
From: [EMAIL PROTECTED] (Jens Kristian S�gaard)
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.system
Subject: Re: parport/ppa problem with 2.2.0pre1
Date: 01 Jan 1999 00:43:02 +0100
Griffin Caprio <[EMAIL PROTECTED]> writes:
> I can't even get my printer to work under 2.2.0pre1. It works fine in
> 2.0.36, but not in the newer kernels. I tried to switch from lp1 to lp0
> and it still doesn't work. Any tips?
Try putting something like this in your /etc/conf.modules:
alias parport_lowlevel parport_pc
options lp parport=0
I've set the option to lp back to 0, as I suppose you only have only
parallel port ( and thats the one the printer is connected to ). I'm
not sure if it's needed -- but anyways...
I ofcourse assume you have a normal PC parallelport.
--
Jens Kristian S�gaard,
[EMAIL PROTECTED]
------------------------------
Date: Thu, 31 Dec 1998 15:54:08 -0800
From: Raymond Lillard <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Best Dual Pentium motherboard, and other hardware
Alex,
Alex Parfenov wrote:
>
> Thank you Paul for answering my posting,
> I have a question regarding your reply:
> How(and why) do you configure 2 network interfaces for the same ( I am
> assuming) network?
>
> Paul Nevin wrote:
> > I just built a Dual Pentium II 450MHz system using the following parts.
> >
> > Asus P2B-DS motherboard - Dual Processor and F+W Ultra SCSI II on board
> > 2x 3Com 3c900 Server Ethernet controllers
> > 512Mb Seimens RAM
> > 2x 450MHz Intel Pentium II Processors
> > 2x 9.6Gb F+W Ultra SCSI II Quantum Hard disks
> > 20/40Gb Sony DAT backup unit SCSI II
> > 8Mb Diamond Glint Pro - 3Dlabs Permedia II AGP graphics card
> >
> > This system was my choice for the ultimate Linux server in preference to
> > clustering single processor NT boxes to do a similar job. I have never
> > had any problems with the ASUS motherboards and can recommend them to any
> > server application. The Asus motherboard here is dual processor capable
> > and has the Adaptec scsi controller built in to the board, saving hassle
> > no doubt.
I too have outstanding experience with ASUS motherboards. Over the last
4 years, I have configured about a dozen systems with ASUS and had only
one fail (after a tech dropped a screw-driver in it) during that time.
About half of these systems ran Linux, the other were dual boot with
Windoze. I am a s/w engr with no financial connection to ASUS or Adaptec.
Obviously, I can't answer for certain, but a good guess for the two
ethernet cards is that he is using it as a server or a firewall or both.
My current workstation is a very similar to the above except for the
dual processors and second ethernet card.
Regards,
Ray
------------------------------
From: [EMAIL PROTECTED] (Byron A Jeff)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: need to take action on the Winmodem problem
Date: 31 Dec 1998 21:32:13 -0500
In article <76fubj$m44$[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
-
->
-> : 1. As someone who has been working with both Windows (mostly NT 4.0) and
-> : Linux for the last few years nothing amazes me more than the general Linux
-> : communities reaction to WinModems. The attitude seems to be "They have the
-> : word Win in there name therefore they are evil. . . ". It is the exact
-type
-> : of thinking they blast from the Microsoft camp for. The Windows people say
-> : "if it's not made for Windows it doesn't matter because only these freaks
-who
-> : use Linux want it". Now it seems the Linux people ae starting to say "if it
-> : is made for Windows users it doesn't matter because its made for those money
-> : hungry, monolopistic, M$ people". Very interesting how times have changed.
->
-> You are dead wrong. While it's true that linux doesn't work with
-> winmodems, you are dead wrong as to the reasons why. The information
-> needed to write a winmodem driver is unavailable to linux programmers.
-
-
-I am dead wrong? I think you need think about what you are saying - because
-you are pretty much proving my point. If, and I agree with you, it would be
-almost impossible to write a seperate Linux WinModem driver for each brand of
-WinModems, then this becomes a business issue. Why? Because once you
-discover that a technical solution is either not possible or not worth the
-"cost" it becomes a business issue. This is my BIG concern with the Linux
-"attitude". Steve, since I don't know you, I will assume you may be the best
-programmer in the world and you may know 100 x's as much about Linux and
-modems as I do, but - if as you say - it's not really possible to write
-seperate WinModems drivers for Linux then you need to take a non-technical
-approach. IMHO that would be lobbying the 3Com's of the world to support
-Linux by either writting drivers for their OWN WinModems or getting them to
-distrubute modems that are "Linux Approved". Either would be possible, but
-both takes time = money on 3Com's part. Technical people do not make these
-descisions - Business people do.
3Com does distribute "Linux Approved" modems, both internal and all external
ones.
3Com from a business perspective have to rationale to support Linux. You've
pointed out that time = money. The Linux market is so insignificant compared
to the real market, it's a loss to support Linux.
We as Linux users and developers understand that. That's why we don't ask for
companies to write/maintain Linux drivers for their hardware. It becomes a
serious development/support issue for such companies.
All we ask for is the ability to write and maintain the drivers ourselves. A
small added development or support costs to the company, but an increase in
their hardware sales, at the slight expense of now telling Linux people that
call their user support Linux that while they do not in fact support Linux,
that the driver and a bunch of information is available at such and such
website.
-
-
-> It doesn't *matter* whether or not linux people want to write windmodem
-> drivers - the specs are hidden and they *can't*.
-
-This is where you REALLY prove my point. We (the Linux community) can't
-write WinModems drivers for EVERY WinModem but 3Com *CAN* write Linux
-WinModem drivers for THEIR WinModems - they *HAVE* the specs. Again, you
-have to convince the business people at 3Com to do this - not the
-programmers.
We have to write WinModem drivers for every modem (or as many as we can get
the specifications for) because 3com nor anyone else is going to write them
precisely because it makes no business sense to do so.
-
-
-> As to the "winmodems suck" angle - the reason for saying so is 100%
-> technical, and not because of the word "win" in it. Putting the
-> modem's signal processing stuff into the OS's hands is a big waste.
->
-> However, even so, I do think that a part of the "winmodems suck"
-> attitude probably is sour grapes. After all, linux supports a lot
-> of other really inferior hardware out of necessity because it is
-> common and cheap, like IDE as opposed to SCSI. I am 100% confident
-> that *if* the information were available, someone *would* write a
-> linux winmodem driver and it would find its way into the main
-> distributions.
->
-> But unless the info is there, it remains a moot point.
-> --
-> Steve Mading: [EMAIL PROTECTED] http://www.execpc.com/~madings
-
-
-I agree WinModems suck - but not if you have a 400 mHz, PII with 96MB RAM and
-are running WIN95/98, then they work just fine. It all depends on your frame
-of reference. You can kick and scream about WinModems all you want but
-unless companies see a real reason (read that as money or consumer attitude)
-to stop producing them they will continue to flood the market. This is why I
-say - contact Sales and Marketing people at the big modem companies. Someone
-on another thread suggested returning a computer if it contains a WinModem
-AND *explaining* that you want a "real" modem AND *why* you want it.
That's a good start. But it'll be a small trickle against the flood. Remember
that most Windows users have no reason to return their Winmodems, because they
have drivers and the modems work for them. Explain to me the business sense
in supporting 3-5 percent of the sales base when the other 95-98 percent are
perfectly happy and buying.
The only way Linux will get a foothold is if some extremely large buyer calls
and says "We're running Linux now and we'll use your WinModems if drivers
are available". Unfortunately it's unlikely.
-Companies will listen, they just respond better to concrete and well thought
-out agruments - not to insults and whinning (this is a general comment - not
-meant to point you out as a whinner, I believe you have a valid point here, I
-just disagree with it).
While companies do respond to well thought out arguments, they have absolutely
no incentive to support Linux. When Linux occupies 25-30 percent of PC
marketshare, then there will be enough of a voice to convince companies to
include Linux support. Until then, the best we can do is ask the companies to
give us enough information to support the hardware with the argument that it'll
represent a marginal increase in sales at minimal expenditure.
It's a tough world for us out there. But rather than whining, or dreaming the
impossible dream, let's work on what we really can do, build market share
for Linux, and ask companies to allow us to support their hardware.
BAJ
------------------------------
From: "Philipp Winkler" <[EMAIL PROTECTED]>
Subject: My Modem doesn�t work
Date: Fri, 1 Jan 1999 00:05:06 +0100
Recently I installed Redhat Linux 5.2 on my Machine.
It really works fine. I only have one problem:
I cannot use my Modem!
I have an external "US Robotics Sportster Message Plus" Modem
If I use Minicom it is not able to find it.
I tried to use setserial to configure it, but it doesn�t work.
Com 1 is used a mouse and Com 2 by the modem.
I used the following settings: (these settings work with Win98)
setserial /dev/cua1 uart 16550A port 0x2F8 irq 3 spd_vhi
I also used modemtool and linuxconf but it still doesn`t work.
The modem doesn�t anything!
Does anybody know how to solve the problem ?
Thanks
Philipp Winkler
------------------------------
From: <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.help,comp.os.linux.questions
Subject: video in XWindows -- Help!
Date: Fri, 01 Jan 1999 00:52:24 GMT
I installed Linux and everything went okay. I'm using LILO to dual boot to
Win98 and that works fine too. I'm having trouble with XWindows though. I
can't seem to configure the video card correctly. After playing with
configyrations using xf86config, i got something. The resolution is huge, a
small menu takes up the entire screen. Also the mouse doesn't work. I have
a Microsoft mouse with the roller in the middle. I tried Microsoft
compatible and generic PS/2, neither worked but one let me use the arrow
keys to control the cursor. Anyway, the video problem. This is what I get
when XWindows simply won't load.
(--) SVGA:PCI: Unknown vendor (0x8086) Unknown chipset (0x7800) rev 33,
Memory@0-e6000000, 0xe5000000
(--)SVGA:chipset:generic
(--)SVGA:videoram:64k
(--)SVGA-clocks:25.18
(**)SVGA:32bpp not supported for this chipset
*** A configured device found, but display modes could not be resolved.***
Fatal server error:
no screens found
Also something about errno111 and errno3.
I'm not sure how to answer the monitor questions it asks me. I there a way
to find out that stuff in Win98? I just make my best guess.
My video card is an AGP Starfighter w 8mb of video RAM. This is on a
PII-300 w/ 64mb ram, 6gig HD cut down the middle for Linux and Win98. Also,
I can't run Xconfigurator. It's just not there. Tell me if you need more
information. Thanks for any help!
-Travis, [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Andries Brouwer)
Subject: Re: Primary Slave HD & FDISK
Date: Fri, 1 Jan 1999 00:38:39 GMT
[EMAIL PROTECTED] (Ki-Won Lee) writes:
: I've successfully installed a 2nd HD on my box and my BIOS recognizes it
: fully. It's a Quantum Fireball EX 6.4G. This is the unit on which I'd
: like to dedicate Linux on.
: The problem I'm having is that when I run Linux fdisk, it tells me that it
: only has 784 cylinders instead of 1023. I installed RH 5.0 anyway to see
: what happens and the install went without a hitch, but when I do a "df -h"
: on it, it tells me the followng:
: /dev/hd1 100M (this is my "/")
: /dev/hd2 5.5G (this is my "/usr")
: /dev/hd3 61M (this is my "/home")
: and I have about a 100M of swap space accoring to my top. (Please excuse
: me if the output of df doesn't look exact, I'm going by memory here)
: As you can see, it's only recognizing about 5.8G at most of my HD instead
: of 6.4G. The LBA is enabled for this HD as well in my BIOS and like I
: said, it's fully recognized by it. According to fdisk, I got this info:
: 255 heads, 63 sectors, 784 cylinders Units = cylinders of 16065 * 512
: bytes.
Well, if I multiply 63*255*784*512 = 6448619520 I find all
of your 6.4 GB so there is no problem - you lost nothing.
(But beware of the fact that some programs make a GB equal to
1024*1024*1024 bytes, other programs use 1000*1024*1024 bytes,
other programs again use 1000*1000*1024 bytes, and some programs
follow the SI standard which tells us that G is the prefix for 10^9.
Thus, when unsure, compute in bytes rather than in larger or smaller
kilo-, mega- or gigabytes.)
------------------------------
From: [EMAIL PROTECTED] (Andries Brouwer)
Subject: Re: More than 8 GByte with IBM-DTTA-351010
Date: Fri, 1 Jan 1999 00:45:55 GMT
Stefan Dreyer <[EMAIL PROTECTED]> writes:
: i have put an IBM-DTTA-351010 with 10 GByte into an older Computer with
: an Gigabyte HX-Motherboard (GA-586HX). The problem is, that i can only
: use 8 GByte an not 9.671. With
: fdisk i can only use 8Gbyte, 1027 cylinder. Can i use kernelparameter to
: get the whole disk?. I am using S.u.S.E. 5.3 and kernel 2.0.36.
: thanks in advance
: Stefan
: Boot-Message:
: <4>ide: i82371 PIIX (Triton) on PCI bus 0 function 57
: <4> ide0: BM-DMA at 0xf000-0xf007
: <4> ide1: BM-DMA at 0xf008-0xf00f
: <4>hda: IBM-DTTA-351010, 9671MB w/466kB Cache, CHS=1027/255/63, DMA
: fdisk v2.8
You need the following kernel patch (to 2.0.36):
=========================================================================
--- ide.c~ Tue Nov 17 17:30:57 1998
+++ ide.c Fri Jan 1 01:50:25 1999
@@ -2579,13 +2579,11 @@
}
/* calculate drive capacity, and select LBA if possible */
- (void) current_capacity (drive);
+ capacity = current_capacity (drive);
- /* Correct the number of cyls if the bios value is too small */
- if (drive->sect == drive->bios_sect && drive->head == drive->bios_head) {
- if (drive->cyl > drive->bios_cyl)
- drive->bios_cyl = drive->cyl;
- }
+ /* Set the cylinder count - the BIOS reported value may be too small */
+ if (drive->bios_sect && drive->bios_head)
+ drive->bios_cyl = capacity / (drive->bios_sect * drive->bios_head);
if (!strncmp(id->model, "BMI ", 4) &&
strstr(id->model, " ENHANCED IDE ") &&
@@ -2593,7 +2591,7 @@
drive->no_geom = 1;
printk ("%s: %.40s, %ldMB w/%dkB Cache, CHS=%d/%d/%d",
- drive->name, id->model, current_capacity(drive)/2048L, id->buf_size/2,
+ drive->name, id->model, capacity/2048L, id->buf_size/2,
drive->bios_cyl, drive->bios_head, drive->bios_sect);
drive->mult_count = 0;
=========================================================================
------------------------------
From: [EMAIL PROTECTED] (Nathan Zalman)
Crossposted-To: redhat.linux.config
Subject: Is the NS 16550AN Uart Supported?
Date: Thu, 31 Dec 1998 02:57:08 GMT
Hi folks, I've got the modem configuration blues.
Which isn't really so bad, because I've got RedHat
Linux 5.2 up and running very smoothly and with
little fuss.
Question: setserial does not list the 16550AN uart
among those it supports. I've tried using 16550A
instead, no success.
The modem: a Viking V.90 56k flex modem, external,
on /dev/cua1, with the default address & irq.
Can anyone help? I'd sure be grateful.
Hey, you know, it's nice to be playing with a real
operating system again!
Thanks,
Nathan Zalman
The Boxwood Studio
------------------------------
** 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
******************************
