Linux-Hardware Digest #8, Volume #10 Mon, 12 Apr 99 20:13:36 EDT
Contents:
Re: 3com / US robotics 56K (Mark Nielsen)
Re: Compiling for x86 CPUs (Was: ... seperate "i686" tree for Redhat ...) (StatiK)
Re: With dual-processor system, is SCSI a must or is Ultra-DMA enough? (Johan
Kullstam)
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?)
([EMAIL PROTECTED])
Re: Scanning temp. freezes system w/ ISA scsi card (Bill)
Linux on an Austin notebook? (Craig McCluskey)
New user: Vidio server Intel 740 (Roger Doulis)
Re: ES 1371 on Intel 440BX motherboard (Harry McGregor)
Re: 2.2.x/2.2.5 kernel no like ATAPI CDR(W) or Acer 8x CD (Brian Walker)
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?) ("Rob Eamon")
From: [EMAIL PROTECTED] (Mark Nielsen)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Re: 3com / US robotics 56K
Date: 12 Apr 1999 15:06:57 -0400
>The problem is that I can't find any of these being sold anywhere. The
>closest model number I can find is 1787, and I can't find any technical
>details that tell if this one would probably be compatible, too. I'm curious
>if anyone else out there has had any success with this model.
>
>Also, if you know of another 56K modem that works well with linux, I wouldn't
>mind hearing about that, either.
Well, I try not to plug my company when responding to questions, but...
I sell a $50 egenric modem Internal ISA that you can jumper.
I also sell USR internal for $84.
An external one for less than $100.
If you use an external one, just attach it to one of your serial ports.
MArk
--
Mark Nielsen"Where 98 has no meaning."
www.tcu-inc.com [EMAIL PROTECTED]
The Computer Underground, Inc. 614-485-0506
computers, programming, networking, Perl, PHP, SQL, HTMl, Linux, Unix
--
From: [EMAIL PROTECTED] (StatiK)
Crossposted-To:
comp.os.linux.misc,alt.linux,alt.os.linux,comp.os.linux.development.system
Subject: Re: Compiling for x86 CPUs (Was: ... seperate "i686" tree for Redhat ...)
Reply-To: [EMAIL PROTECTED]
Date: Mon, 12 Apr 1999 22:02:32 GMT
Buy another Pro / P][ and get rid of the dx2!!
StatiK
On 12 Apr 1999 14:28:40 +0200, Urs Thuermann
<[EMAIL PROTECTED]> wrote:
>Johan Kullstam <[EMAIL PROTECTED]> writes:
>
>> -mcpu=i686 makes the compiler schedule for a i686 core. it uses only
>> the i386 instruction set.
>>
>> -march=i686 enables usage of i686 instructions like cmov (which did
>> not exist on i[345]86. it also implies cpu=i686.
>>
>> if you compile with -mcpu=i686, then yes, it would work with any of
>> intels 32bit x86 cpus. however, by using -march=i686 you will
>> introduce new op-codes which are not implemented on previous
>> processors.
>>
>> based by my own experience with compiling various things with egcs
>> on a pentiumpro, it is not very important for performance no matter
>> what the cpu or arch settings are so long as you avoid pentium.
>
>
>Could someone give some more details about this whole story, please?
>I seem to have problems with this issue since a few days.
>
>I have a Pentium II running in my server machine (which has only a
>Herkules Video card and an Atari ST attached to the serial port) and a
>i486dx2 in my diskless client running Linux and X11.
>
>Both machines run the same 2.0.36 kernel image, the diskless machine
>has its own /tftpboot dir on the server and shares the /usr with the
>server (it mounts /usr read-only, though).
>
>I run egcs-1.1.2 and gcc-2.7.2.3 which have both configured themselves
>as a i686-pc-linux-gnu native compiler. What kind of code will these
>produce if called without any -m... option? How should I invoke egcs
>and gcc-2.7.2.3 to compile with maximum performance on i686 but with
>the constraint that the code should also be executable on i486?
>
>
>
>The problem I am observing is this: With egcs configured as described
>above I compiled the glibc-2.1. When I copy /lib/lib*2.1.so and the
>other glibc-2.1 files to the diskless' /tftpboot directory, the
>diskless i486 won't boot anymore. The statically linked /sbin/init
>seems ok, but (at least) the agetty's die immediately with an SIGILL
>(illegal instruction). So I assume, glibc-2.1 is compiled in a way by
>egcs so that it only runs on i686. This may, however, also be caused
>by glibc itself. glibc-2.1 configured itself as i686-pc-linux-gnu
>also, and obviously has code for this case, which is i686-specific,
>e.g. in glibc-2.1/sysdeps/libm-i387/i686/s_fdim.S there are
>fcomi/fucomi instructions. I think I read in this thread that th