Linux-Hardware Digest #260, Volume #9            Sun, 24 Jan 99 10:16:31 EST

Contents:
  Re: PCI support people alive ?! (Tabman)
  Re: Ultra ATA/UDMA drives+controllers don't work? (Roger Atkinson)
  Re: SCSI - Is it worth it? (Roger Atkinson)
  Re: Adaptec AHA-1505 question - i/o address (Roger Atkinson)
  idt winchip? (Jason Wagner)
  Recycling older hdwr (Robert Wenzlaff)
  Re: SCSI Parity Errors ("Mark Vandersteen")
  Soundblaster: Error Opening /Dev/Audio ("PG@Root")
  Re: Modem compatability (Rob Thompson)
  Lightnux, the slim Linux ("Pascal Ferrari")
  Re: HP Jet Direct (Harry McGregor)
  Re: Beware buying from House of Computers (Harry McGregor)
  Re: Fireport SCSI and redhat 5.2 (Harry McGregor)
  Re: Ultra ATA/UDMA drives+controllers don't work? (Tim Moore)
  Re: partitioning woes (Tim Moore)
  CyberVision C52 monitor and X (Douglas J Hagen)
  Re: Cirrus 5424 @ 16bpp? (The Blackest Heart in Christendom)
  Re: RH 5.2 on a 486 Compaq, worth the time? (Dave Pooser)
  Re: Want Linux bogomips numbers for Intel PII-450 ([EMAIL PROTECTED])
  Re: Manual Switch boxes, Any hope? (Ed Blackman)

----------------------------------------------------------------------------

From: Tabman <[EMAIL PROTECTED]>
Subject: Re: PCI support people alive ?!
Date: Sat, 23 Jan 1999 23:00:19 -0500 (EST)
Reply-To: [EMAIL PROTECTED]


On 24-Jan-99 Peter T. Breuer wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> 
>:     I would just like to know if they received my message or not.  Some of
>: the devices I reported still aren't supported in the pre9 kernel, and I
>: would like to know if the lack of support is because they're unaware of
>: these devices or because they're just really busy and haven't had time to
>: add the support.
> 
> What do you mean?


        I meant recognized, as in "When I boot, I get these 'unknown PCI
device' warning messages.". Looking in pci.h, I don't see any '#define' for
them.


> Are you by any chance complaining about some messages?


        NO ! What I'm saying is that I sent a report to the PCI support people
( [EMAIL PROTECTED] )-- as per the instructions in pci.h -- but
never received a response. I would like to know if my message got through or
not. So, I posted here to see if the Linux PCI support group has disbanded,
moved, or whatever else.


>  Ignore them - or
> patch them away.  I regularly update my pci lists (haven't in a while,
> though ...).


        <Sigh> Read my original post. As of yesterday, the latest kernel
release available at kernel.org is 2.2.0pre9, which does not have '#define's for
all the unknown devices I reported.


> Why would any sane person be worried about it?


        Perhaps because they're not aware of all the possible consequences
which may result. And I don't have the time to go through the 
kernel source to see what the possible implications are.


> Do you think it implies that the kernel doesn't know how to treat the
> card?


        ...or it may not be treating it optimally.


>  Think! Look at /proc/pci.


        Hey Einstein, I already did that. It only gives you a memory address
and latency (aside from the usual bus, device, vendor id, and possibly Gnt.,
depending on the device.) Does it tell you how the kernel is going to treat it
? No. Does it tell you whether it's going to treat it like it does a similar
device which is not unknown ? No.

        Anyways, like I said, the purpose of my post was to see if the Linux
PCI support group still exists and whether or not I should have received a
reply to the report I submitted or not.
        

        It was not an invitation for flamers to waste bandwidth.



'later...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| "If you make people think they are
Tabman           You may answer in |  thinking, they will love you; if you
           english, french, german |  make them think, they will hate you."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                 - Don Marquis


------------------------------

From: Roger Atkinson <[EMAIL PROTECTED]>
Subject: Re: Ultra ATA/UDMA drives+controllers don't work?
Date: Sat, 23 Jan 1999 21:56:04 -0800

Mark Vandersteen wrote:
> 
> There is a section on using the Promise in the UDMA mini HOWTO check it out
> before making a decision
> 
> TURBO1010 wrote in message <78b12i$dfa$[EMAIL PROTECTED]>...
> An onboard UDMA should work fine, which come with most boards.  Just don't
> make the mistake of getting a Promise UDMA Controller, it's recognized, but
> can't be used after reboot.
>     José Ureña wrote in message <[EMAIL PROTECTED]>...
>     The UDMA drives will still work as EIDE or IDE
>     I have notice that UDMA compatibility is tested by the kernel at
> startup.
>     and I read somewhere that if the Controller+Disk is not one of the known
> good combinations, then UDMA is dissabled
> 
>     it  is done to protect the disk + data
> 
>     [EMAIL PROTECTED] wrote:
> 
>         Sorry if this question has been beaten to death previously, I have
> been
>         searching on the newsgroups and on the RedHat site for a definite
> answer, to
>         no avail. I am about to buy a PentiumII machine for RedHat
> distribution 5.2,
>         but reading the RedHat hardware compatibility list, it says that
> "the Promise
>         series of "Ultra-ATA" controllers (and *other* Ultra ATA, Ultra DMA
> or ATA 33
>         controllers) appear to be incompatible with RH Linux." There is
> another doc
>         that I read, the Ultra-DMA Howto, that doesn't directly answer my
> question
>         either.
>         My problem is that almost all of the possible machines I could buy
> have the
>         Ultra ATA/UDMA drives and controllers on them. Ultra ATA has become
> the
>         defacto standard (sorry, SCSI is slightly out of my price range) for
> cheap
>         desktop machines. Does this mean that RHLinux 5.2 will not work with
> *any*
>         machine that has a Ultra ATA/UDMA drive and controller? Is this a
> problem in
>         the kernel? (which I guess means that any distribution of Linux
> would have
>         the same incompatibility, or is it only RH?)Or does this only apply
> to add-in
>         PCI-bus controllers, and not to the hard drive controllers that are
>         integrated into the motherbd? If I have a machine with an integrated
> Ultra
>         ATA controller, than will it run with Linux but only in the slower
> EIDE mode?
>         Is there something special I'll have to do during the install? I
> must not be
>         the first person to ask this because the Ultra ATA drives are so
> ubiquitous.
>         Obviously, I don't wanna buy a new machine only to find out that I
> can't
>         install and run Linux on it.
> 
>         much thanks from a newbie,
>         Scott Serata
>         [EMAIL PROTECTED]
> 
>         -----------== Posted via Deja News, The Discussion Network
> ==----------
>         http://www.dejanews.com/       Search, Read, Discuss, or Start Your
> Own

Hi All,  I'm currently using an SiiG CN2449 Ultra ATA (UDMA) card in my
P166 and it works great with the Seagate ST34321A (4GB) drive. I am
running Red Hat 5.2 and upgraded to Kernel 2.0.36-3. I currently boot
with a boot floppy in accordance with the UDMA Mini HowTo and I have to
use the ide= parameter to get it boot from /dev/hdg1 but thats only
until I get the Lilo Patches for the device type. I have two 2GB IDE
drives and the Seagate UDMA drive on this controller and all works fine
under Linux and Windoze.

Just thought you might like to know,
-- 
Roger Atkinson  Unix Sys Admin  (Solaris, IRIX, HP-UX, DUX)
Work: [EMAIL PROTECTED]   Linux newbie and thinkin it's great !
Home: [EMAIL PROTECTED]

------------------------------

From: Roger Atkinson <[EMAIL PROTECTED]>
Subject: Re: SCSI - Is it worth it?
Date: Sat, 23 Jan 1999 22:05:06 -0800

Michael Meissner wrote:
> 
> Nik Anderson <[EMAIL PROTECTED]> writes:
> 
> > Often you can find the same drive with either an ide or scsi interface.  The
> > difference in price between the scsi drives reflect the more complicated
> > logic that must be on a scsi drive.  I would say, though, that you shouldn't
> > see any difference in reliablilty in an investigation based on interface
> > alone.
> 
> People are always saying that `often' you can find the same drive with either
> interface.  I tend to think its rarer than `often' would suggest, at least in
> the last few years.  Off the top of my head, there is the Quantum Fireball and
> the Seagate Medalist Pro.  The fireball scsi version has been repeatily slammed
> for having bad scsi support in the review sites.  I believe the price
> difference is not the logic per se, but more that disk mfgrs know they can get
> a higher profit for scsi disks (though less volume).

I use both types of drives at work and at home and have been satisfied
with both UDMA drives and SCSI drives. One thing to remember in any
drive type is that when you start to get over 4GB they draw more power
and therefore run a bit hotter. Any drive will die early if you don't
cool it properly.

As far as is it worth it - Well, at home if you still have IRQ's and
Slots left you might not want to spend the extra money. OTOH, if you
have lots of toys, having a SCSI card allows you to put from 7 to 15
devices on a single controller and only use the one IRQ. This can come
in real handy on a PC. At work, I wouldn't use anything but SCSI for all
my Production Machines and High Availability machines.  I have some
500MB SCSI disks that are over 10 yrs old and still work just fine.

Hope this helps,
-- 
Roger Atkinson  Unix Sys Admin  (Solaris, IRIX, HP-UX, DUX)
Work: [EMAIL PROTECTED]   Linux newbie and thinkin it's great !
Home: [EMAIL PROTECTED]

------------------------------

From: Roger Atkinson <[EMAIL PROTECTED]>
Subject: Re: Adaptec AHA-1505 question - i/o address
Date: Sat, 23 Jan 1999 22:11:25 -0800

Peter Polman wrote:
> 
> > I'm trying to get my RH5.2 to recognize my Adaptec AHA-1505 scsi host
> > adapter.
> > I know that it is aha152x compatible, but I don't know what parameters to
> > pass it when I do /sbin/modprobe   or   when I use Kernel Configurator.
> > My system is dual boot with NT, NT has the following settings for it
> >
> > i/o = 340-35f
> > IRQ=11
> > scsi ID = 7
> >
> > so I tried  /sbin/modprobe aha152x aha152x=340-35f,11,7,1
> >
> 
> The proper format would be aha152x=0x340,11,7,1
> 
> > Am I putting in the wrong value for i/o address?
> > How do I find the exact i/o address?

I was never able to get my Iomega SCSI Card (Adaptec 1505 chip) to probe
under Linux unless it was IOport 330 or 334. I also found this to be
true with the AHA1520B and the AHA1542CF that I am now using. I tried
the above config info in an append statement in my lilo.conf and it
never found the card. When I set the IOport to 334 (330 was a conflict
for me) everything worked just fine, has been for months.

BTW I am currently running RH5.2 Kernel 2.0.36-3 but my install and
setup detect probelms occured with both RH5.1 and RH5.2. Setting the
IOport to one of the older suggested port numbers in the SCSI HowTo
worked magic for me.

Hope this helps,

-- 
Roger Atkinson  Unix Sys Admin  (Solaris, IRIX, HP-UX, DUX)
Work: [EMAIL PROTECTED]   Linux newbie and thinkin it's great !
Home: [EMAIL PROTECTED]

------------------------------

From: Jason Wagner <[EMAIL PROTECTED]>
Subject: idt winchip?
Date: 24 Jan 1999 06:30:53 GMT

i was wondering, in general, what linux thinks of the idt winchip?  are
there any compatability issues?

thanks.

jason

-- 
__________________________________________________________________________
Jason Wagner                            Applications Systems Analyst, BOFH
[EMAIL PROTECTED]                  The University of Arizona
12821209                                Sierra Vista

The opinions expressed here are strictly my own, and in no way reflect the
opinions of The University of Arizona.

------------------------------

From: Robert Wenzlaff <[EMAIL PROTECTED]>
Subject: Recycling older hdwr
Date: Sat, 23 Jan 1999 21:22:25 -0500

I've recently picked up a rather  large lot of (mostly) 486 annd 386
motherboards and I'm looking for suitable applications for them.

Would a 386DX40 make a good router?

Would bumping up the 486DX40's Memory and I/O speed make it a suitable
Server for a  small (How Small?) network?  What are the recomended specs
for Firewalls, Web Servers, backup servers?

I would probably configure a small disk on a second IDE  channel for
swap (If you haven't tried it, it helps ALOT).  Maybe use extra space on
that as a backup disk.

My personal machine is a 486 MB with an AMD-K5-133 Upgrade chip, 20Mb
RAM.  It runs X (using KDE, yet!) pretty well.  Judging from my  system
performance I think Linux responds very well to Mem upgrades.

Just looking for some advice.

Bob Wenzlaff



------------------------------

From: "Mark Vandersteen" <[EMAIL PROTECTED]>
Subject: Re: SCSI Parity Errors
Date: Sun, 24 Jan 1999 17:08:12 +1030

I had a similar problem with a adaptec 1542b, and a seagate 540 mg HD.
I had errors like this for a while (parity errors) before I lost the entire
HD. It wouldn't boot the computer at all coundn't format or anything from
floppy etc. After thinking the HD was stuffed, (I couldn't get any low level
formatting stuff to check it myself for the 1542b). I give it to my brother
to play with , all he did was low level format with a AHA-2940U and he's
been using it ever since, with out problems.

Maybe you could backup the data on the disk low level reformat it with the
aha utilities and try again ??

Mark Vandersteen [EMAIL PROTECTED]
Powered by Linux !  Obsessed with women !
The thoughts here are not necessariy mine !

Nicholas Barry wrote in message ...
>Hello everyone,
>
>I have a curious question.  I currently run an Adaptec AHA-2940U SCSI card
>with 5 devices hanging off of it.  I just recently upgraded from a Future
>Domain TMC-3260.  I've never seen this problem before, but now that I've
got
>the new card, I'm seeing it every 10-30 minutes.  The issue is the
following:
>
>I get Data Parity Errors in my syslog with the exact output like this:
>
>(scsi0:-1:-1:-1) Data Parity Error during PCI address or PCI writephase.
>(scsi0:-1:-1:-1) Received a PCI Target Abort
>(scsi0:-1:-1:-1) Data Parity Error during PCI address or PCI writephase.
>(scsi0:-1:-1:-1) Received a PCI Target Abort
>
>
>Has anybody here seen this before?  If so, any clues as to which device may
>be causing it?  That is, does a resource exist where I can track down this
>problem?  The reason I'm really pissed off is because I've managed to ruin
>9 blank CD-R disks in the past week and I have a feeling it's the error
above.
>While writing CDs I get write failures with differing reasons and my
>guess is that it's due to the parity errors seen above.  I'm in
>the process of replacing my 4+ year old 2x CD-ROM drive to work
>better with my 2x6 CD-R drive, but if that's not the problem (what's
>giving the parity errors) then I've got little clue other
>than to completely disassemble my system and go through drive at a time
>until I find the culprit.  I'd prefer to shorten this process.
>
>Anyway, if anybody has any clue, I'm all ears.  Thanks!
>
>To reply to me, see my address in the .sig.
>
>
>
>
>
>
>
>nick
>--
>n i p  at  i s o l a t i o n  dot  n e t
>"Giving money and power to government is like giving whiskey and car
>keys to teenage boys."                                -P.J. O'Rourke



------------------------------

Date: Sun, 24 Jan 1999 06:30:53 +0000
From: "PG@Root" <[EMAIL PROTECTED]>
Subject: Soundblaster: Error Opening /Dev/Audio

Using RH 5.2.
Sounblaster Awe 32 (not PnP)

When I installed Red Hat, I could have sworn the install routine
detected the sound card. I get no sound however using KDE (or any other
method for that matter). So, I've run SNDConfig, and when it tries to
play I sound I recieve the message "Error Opening /Dev/Audio". This
makes me think I don't need to recomplie the Kernel (as suggested in the
Sound-HOWTO), as if it were already being "held open". Is there a simple
solution to this (still fairly new to Linux...)?

Patrick

------------------------------

Date: Sun, 24 Jan 1999 01:46:15 -0500
From: Rob Thompson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Modem compatability

Dear Carson,

  Use the command 'pnpdump' and direct the output to /etc/isapnp.conf.  Then
edit this config file, which involves selecting suitable choices for address and
IRQ.  See the README files in /usr/doc/isapnp for more help.

Rob Thompson

Carson Saunders wrote:

> I tried to use isapnp but it requires a config file.  Where do I get that?
> US Robotics doesnt make a driver/config file for Linux.  Any other thoughts?
>
> Thanks
> Carson
>
> >It may or may not work.  Dell sells both 3COM/USR modems and
> >winmodems.  If it is a winmodem it will not work!  If it is a modem.
> >Setserial can help configure it, if it is PnP (Plug and Pray), use isapnp.
> >--
> >           Dan Nguyen            | There is only one happiness in
> >        [EMAIL PROTECTED]         |   life, to love and be loved.
> >http://www.cse.msu.edu/~nguyend7 |                   -George Sand
> >


------------------------------

From: "Pascal Ferrari" <[EMAIL PROTECTED]>
Subject: Lightnux, the slim Linux
Date: 24 Jan 1999 07:36:04 GMT

Yesterday night I had a dream :

I was visiting one of my clients' office and was looking at the people
working there : 
- 8 secretaries typing mail as usual on their old x386 Win3.1 machine, 
- 2 accountants entering book items from their term emulator using my
remote char-based accounting application running on the Linux Server,
- 3 managers using their wonderful Pentium Pro box under Win98 one hour per
day for just playing Doom.

In my dream I was unplugging the x386 machines, leaving to the users their
monitor, keyboard and mouse and plugging these peripherals back on a small
and flat box I placed under their monitor. This box was just offering a
VGA, a keyboard, a mouse and a network connection plugs : no floppy drive,
no CD and even no hard drive.

This box contained its own OS stored in a simple PROM. This OS was a tiny
Linux Kernel with just the minimal functions for good networking : Web
browser, terminal emulation and GUI. When the users plugged on their new
machine, there was no OS loading delay and no noise. They immediatly got
their connection to the server. The accountants kept using my accounting
application without any change. The secretaries worked on a new word
processor, running on the remote Linux server, providing Word 6 compatible
documents. And the managers, between two Doom games, could open and read
these documents from their Office 98 word processor.

Not only I could sell these nice boxes at an interesting price, but my
client gave me for free all their x386 CPUs, thanking me for taking off
this obsolete stuff. And with this old material I could build new boxes by
using the inside components, and sell back these boxes in a new client
office.

When I woke up this morning I went on the Web and looked for this tiny OS.
Unfortunately for me, the idea was already taken by QNX. QNX's OS can be
stored entirely on one floppy (1.44 MB)! Unbelievable!...But it is a
commercial product with the well known serie of development licenses,
run-time licenses, paying options and so on...The final bill raises to
several thousands $. And you remain in the hands of a commercial structure
and its changing pricing options, most often going higher than lower.

So my idea is the following :

Linux is getting fat. The last Red Hat distribution is about 800 MB and
needs at least 32 MB RAM to run efficiently. This is acceptable for a
server machine where you need more functionalities and which has higher
architecture.

But for a workstation, it becomes too much. So, why not to write a very
light and packaged version of the current Linux, with only the minimal
functions for networking easily? This "Lightnux" should be no more than 4
MB if we want to store it on a simple PROM.

Do anybody have an experience in that way? Do you think we can obtain
efficient results quickly by using standard Linux components, or is it
necessary to develop specific functions?

Thank you for your answer.


Pascal Ferrari




------------------------------

From: [EMAIL PROTECTED] (Harry McGregor)
Subject: Re: HP Jet Direct
Date: Sun, 24 Jan 1999 07:33:57 GMT

Do you know if the 4000TN comes with postscript by default?  or is it
an option.  I am looking at getting one for a Linux based computer lab
(elementary school), that I just finished building.

                Harry

------------------------------

From: [EMAIL PROTECTED] (Harry McGregor)
Crossposted-To: 
comp.os.terminals,comp.misc,comp.os.ms-windows.win95.misc,comp.os.nt.misc,comp.os.ms-windows.misc,comp.os.linux.misc,comp.os.ms-windows.nt.setup.hardware
Subject: Re: Beware buying from House of Computers
Date: Sun, 24 Jan 1999 07:31:30 GMT

I have dealt with house of computer before (though no RMAs).  I love
their products (IBM hds are great, so are DigiView monitors).  Most
mail order places I have dealt with charge for s/h to them on RMAs so
do manufactuers (i.e. Iomega (sucks), CTX, etc).  $50 for a 17" is
rather close, sending a CTX 17" back to CTX cost me $35 twice, and
that was normal parcel post, book mail (they sent it back without it
being fully fixed!!!).


                        Harry

------------------------------

From: [EMAIL PROTECTED] (Harry McGregor)
Subject: Re: Fireport SCSI and redhat 5.2
Date: Sun, 24 Jan 1999 07:36:16 GMT

I don't know much about red hat (I use slackware), but I am using a
fireport 40 under slackware as my bood devices (it uses the symbios
logic chipset, I think its the 875).

                        Harry

------------------------------

Date: Sun, 24 Jan 1999 00:14:49 -0800
From: Tim Moore <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,linux.redhat.misc
Subject: Re: Ultra ATA/UDMA drives+controllers don't work?

[EMAIL PROTECTED] wrote:
> 
> no avail. I am about to buy a PentiumII machine for RedHat distribution 5.2,
> but reading the RedHat hardware compatibility list, it says that "the Promise
> series of "Ultra-ATA" controllers (and *other* Ultra ATA, Ultra DMA or ATA 33
> controllers) appear to be incompatible with RH Linux." There is another doc

The list is wrong [i'll send them an email].  Promise Ultra/33 controllers
are supported native in 5.2 (2.0.36) and in previous versions with boot
time parameters.  Here's my lilo.conf mods from a 2.0.34 kernel.  IDE 2 & 3
are the Promise:

append="\
        mem=128M \
        ide2=0xd000,0xb806,10 \
        ide3=0xb400,0xb006,10 \
        lp=0x278,7 \
        ppa=0x378,0,6 \
"
I ran IBM Deskstar 6.4GB drives with it and got about 8.5MB/s throughput. 
Not a bad deal getting 4 more EIDE drives for about $60.

Complete details in /usr/doc/HOWTO/mini/Ultra-DMA

-- 
[Replies: remove the dot(s)]

"Everything is permitted.  Nothing is forbidden."
                                   WS Burroughs.

------------------------------

Date: Sat, 23 Jan 1999 23:48:20 -0800
From: Tim Moore <[EMAIL PROTECTED]>
Subject: Re: partitioning woes

That was great.  I felt better just reading it.  Thanks.
-- 
[Replies: remove the dot(s)]

"Everything is permitted.  Nothing is forbidden."
                                   WS Burroughs.

------------------------------

From: Douglas J Hagen <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.x,comp.os.linux.misc,alt.os.linux
Subject: CyberVision C52 monitor and X
Date: Sat, 23 Jan 1999 13:24:18 -0500

Hello...

I'm a newbie at Linux and have a problem with my monitor and X-windows.
I have Linux installed fine on my computer, but at startx, I cannot get
my display configured at all!  I know that it has to do with the
modelines, but that's where my knowledge ends.

If anyone out there has a CyberVision monitor or is a modelines guru,
PLEASE reply via email to me!  Any help is GREATLY appreciated!

--
Doug Hagen
[EMAIL PROTECTED]



------------------------------

From: [EMAIL PROTECTED] (The Blackest Heart in Christendom)
Crossposted-To: comp.os.linux.setup,comp.os.linux.x,nf.comp.linux
Subject: Re: Cirrus 5424 @ 16bpp?
Date: Sat, 23 Jan 1999 23:35:44 GMT

On Thu, 21 Jan 1999 15:36:34 GMT, [EMAIL PROTECTED] threw their
Scrabble tiles in the air and got:


>The reason you can't get the higher colour depth is because the 8bpp mode
>uses a stock interface to the card and 16+bpp uses a hardware specific
>interface.  This driver will only access the card in this manner if the video
>buffer has been overlaid into the CPU address space - which you can't do
>because you've already got RAM there:)

>I've been working on a driver for the CLGD5434 for about a year.  I have a
>486/33 with 64MB ram and I hit the same problem as you.  My solution was to
>start working on a repacement driver.  It should be ready sometime towards the
>summer if you're not in a big hurry:)

Weird. I have a card with a Cirrus 5434 chipset (STB 5430, came with
my Gateway P4D-66) and I have the weirdest glitch. Runs fine under
8bpp on any resolution up to 1024x768. Runs 24 bpp at 640x480. For the
life of me, I can't find a mix for my XF86Config that will work at 16
bpp. Keep in mind my systems a 486DX2/66, with the video card on a PCI
bus with 1MB archaic memory (they say I can't buy more of that type
new), so it should be able to handle it. I didn't do anything beyond
hack dotclocks to get this to work.

-TBHiX-


------------------------------

From: [EMAIL PROTECTED] (Dave Pooser)
Crossposted-To: comp.os.linux.setup
Subject: Re: RH 5.2 on a 486 Compaq, worth the time?
Date: Sat, 23 Jan 1999 22:37:37 -0600

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (M. Buchenrieder) wrote:
 
> The ProLinea series should work, but you'll perhaps need to play some
> tricks to get around the proprietary Compaq BIOS settings. Be aware
> that getting additional add-on cards to work in a Compaq can be a really
> tough project. 

Is this toughness specific to Linux? I've got a 4/33 with a Phillips
CD-ROM and controller card (F206/F260). DOS recognizes it fine, but Linux
refuses to. I'd assumed it wasn't any kind of BIOS difficulty because it
worked with DOS... Is Linux more finicky?

-- 
Bubba Dave Pooser
If you can't figure out my email address,
I don't care what you have to say.

------------------------------

Date: Sat, 23 Jan 1999 09:54:57 -0800
From: [EMAIL PROTECTED]
Crossposted-To: comp.sys.intel,comp.os.linux.advocacy,comp.arch,alt.os.linux
Subject: Re: Want Linux bogomips numbers for Intel PII-450



Simon Kinahan wrote:
> 
> [EMAIL PROTECTED] wrote:
> > Note that AMD CPUs give higher-than-MHz BogoMIPS
> > numbers, but generally run other code slower.
> > This has to do, I claim, with the fact that the
> > K6 microarchitecture runs a two-instruction decrement/
> > branch loop faster than the P6 microarchitecture.
> 
> If you were right, you might have a point, but you aren't, so you don't. My AMD
> K6-2 300 (and every equivalent machine I have seen) gives just under 300
> bogomips. AMD chips have superior integer performance to Intel ones under some
> circumstances, but generally poorer floating point.

Sorry, you are the one who is wrong.

------------------------------

From: [EMAIL PROTECTED] (Ed Blackman)
Crossposted-To: alt.os.linux
Subject: Re: Manual Switch boxes, Any hope?
Date: Sat, 23 Jan 1999 11:49:29 -0500
Reply-To: [EMAIL PROTECTED]

In article <780rgo$mr4$[EMAIL PROTECTED]>,
       BL <[EMAIL PROTECTED]> wrote:
>the active boxes are THE way to go.  they retime and repeat the video signal
>AND keep the keybd/mouse alive.
>
>even at 1600x1200 (really!) the switchbox is 99.9% transparent.  pretty good,
>I think!
>
>get one - it works.

Do you have any recomendations for a good but inexpensive active
switchbox?

Ed

------------------------------


** 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
******************************

Reply via email to