Linux-Hardware Digest #9, Volume #10 Mon, 12 Apr 99 22:13:44 EDT
Contents:
Re: ISDN / BT Speedway Problem (HiSax/Fritz) (Simon Griffiths)
Re: Modem : which is the best? (Andrew Comech)
Re: 3com / US robotics 56K (Andrew Comech)
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?) ("Charles R.
Lyttle")
Re: S3 Trio 3d Video card ("Jakub Chmielewski")
easy-to-configure soundcard (Arun Muthukumaran)
Problem with disk partitioning. HELP!!! (Gopal Cheruku)
Re: 56K FAXMODEM (Allen)
Re: Netgear ISA EA201c NIC (Allen)
2 Problems: I have a HP8100 CDR and Im very inexperenced linux user. Help! (Carlos
Espino)
Re: All the current OSes are idiotic (was Re: Is Windows for idiots?) (Johan
Kullstam)
Re: Compiling for x86 CPUs (Was: ... seperate "i686" tree for Redhat (wizard)
Re: X terminal? ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: Simon Griffiths <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: ISDN / BT Speedway Problem (HiSax/Fritz)
Date: Tue, 13 Apr 1999 00:49:37 +0100
Simon Griffiths wrote:
>
> Heeeeeelp.....
>
> I've currently got a 2.2.5 kernel with modular support for IDSN/HiSax
> (Fritz)
> and a BT Speedway PCI card. All looks fine....
>
> but I get :
>
> Apr 10 14:10:24 localhost kernel: HiSax: Card AVM A1 not installed !
> Apr 10 14:10:24 localhost kernel: ISDN-subsystem unloaded
>
> everytime I try to load the HiSax module with...
>
> modprobe -v hisax io=0x6400 irq=9 protocol=2 type=5 id=Fritz
>
OK, I've had a chance to look further into this, and I come to the
following conclusions....
1. The card I have - a BT speedway internal - is a Fritz/PCI version.
2. There are 3 Fritz types in the ISDN4Linux Hisax driver module: Fritz,
Fritz!PnP, Fritz!PCI
3. The internal BT Speedway needs the Fritz!PCI
4. Each type of card requires a different type argument in the insmod
call. I should have been using:
modprobe -v hisax protocol=2 type=27
But....
5. the Fritz!PCI & Fritz!PnP drivers are included in 2.0.36, but not in
2.2.x
6. the Fritz!PCI driver included in the latest version of ISDN4Linux
won't compile in 2.2.n
(at least I can't get it to!)
7. 2.2.x is great - there's so much good stuff in here I don't want to
regress
Conclusion - I'll just have to manage with my 33.6 modem until some
wonderful person can tell
me how to get the Fritz!PCI driver compiled in 2.2.n !
or...
the Fritz!PCI driver gets rolled into the 2.2 kernel distribution.
Any takers ?
Also, I think the BT Speedway card is being pushed pretty strongly with
the new
BT Highway products and is selling pretty well, - there may be lots pf
people out there
with the same problem as me !
Simon.
------------------------------
From: [EMAIL PROTECTED] (Andrew Comech)
Subject: Re: Modem : which is the best?
Reply-To: [EMAIL PROTECTED]
Date: 12 Apr 1999 19:36:59 -0500
On Mon, 12 Apr 1999 20:23:38 GMT, David Ripton wrote:
>In article <[EMAIL PROTECTED]>,
>Andrew Comech <[EMAIL PROTECTED]> wrote:
>>On Thu, 8 Apr 1999 14:47:41 -0700, Peter MacKay wrote:
>>>In the past several months I have heard so many complaints about various
>>>modems. None of these complaints are directed at external modems (at least
>>>as far as I can remember).
>>>
>>>Here's my advise. BUY AN EXTERNAL ONE
>>>I use an external US Robotics 33.4 (A little old ) and I have never had a
>>>problem
>>
>>I have never had a problem with my _internal_ modem.
>>I wonder: what's the reason to spend extra $20 or something?
>
>1. Status lights
If you need them all the time, it is a bad modem.
Those lights might be reassuring... but this is basically it.
>2. Power switch
Most of the time it's not that an external modem _has_ the power
switch; it _has to have_ the power switch. And an extra power outlet.
>3. Hardware portability
>4. Easier installation
What I like is that external modems could be plugged [back and forth]
on-the-fly (please do not tell anybody that this is how I changed
_internal_ modems; this is risky business indeed, although I was lucky).
Other than that, don't you think it is _faster_ to pull out an
internal card than to wind and pack all those extra cords?
>5. Much smaller chance of getting a Winmodem by mistake
Well, there is still a chance of getting a) a USB modem;
b) an RPI modem; c) a broken modem. Although b) and c) are probably
obsolete, you have to "grep -iv 'usb'".
It is _easy_ not to make mistakes with internal ones: never buy
models not mentioned at http://www.o2.net/~gromitkc/winmodem.html
as `OK' for Linux.
* * *
Actually, Peter, I ran out of flames and would like to drop the
discussion... My point is not the external-internal fight, but the
affordability of Linux-compatible modems: a person who spends below
$50 on a modem does not sacrifice the performance.
She is not getting a bonus power switch, though.
Cheese,
Andrew
--
Looking for a Linux-compatible V.90 modem? See
http://www.math.sunysb.edu/~comech/tools/CheapBox.html#modem
Expect to pay below $50.
------------------------------
From: [EMAIL PROTECTED] (Andrew Comech)
Crossposted-To: comp.os.linux.help,comp.os.linux.misc
Subject: Re: 3com / US robotics 56K
Reply-To: [EMAIL PROTECTED]
Date: 12 Apr 1999 18:55:28 -0500
On 12 Apr 1999 15:06:57 -0400, Mark Nielsen wrote:
>>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.
Hi MArk,
Egenric is certainly a nice brand ;-), but AOpen's FM56-ITU/2 for
around $40 [plus shipping] seems to be a better deal. Wanna give a price
break for Linux freaks? Please write me if YES; I'd add you to my list.
Who knows; maybe you'd sell more.
Cheese,
Andrew
--
Looking for a Linux-compatible V.90 modem? See
http://www.math.sunysb.edu/~comech/tools/CheapBox.html#modem
Expect to pay below $50.
------------------------------
From: "Charles R. Lyttle" <[EMAIL PROTECTED]>
Crossposted-To:
comp.lang.java.advocacy,comp.os.linux.advocacy,comp.os.ms-windows.advocacy
Subject: Re: All the current OSes are idiotic (was Re: Is Windows for idiots?)
Date: Mon, 12 Apr 1999 23:51:04 GMT
Chris Welch wrote:
>
> In comp.os.ms-windows.advocacy westprog <[EMAIL PROTECTED]> wrote:
> > In article <[EMAIL PROTECTED]>,
>
> > This is the reason for case-sensitive operating systems, file systems and
> > programming languages. Nobody really wants a system that can't recognise
> > "MyFileName" as the same as "MyFilename", but it saved a few cycles back in
> > the valve age.
>
> Nobody as in a whole lot of people? That irks me most about Dos. "bob" and
> "Bob" are the same thing. My question is why _wouldn't_ you want it? It
> doesn't hurt anything. If you want "MyFileName" then type that.
> --
> -
> http://www.olemiss.edu/~cmwelch1
>
> Great spirits have always encountered violent opposition from
> mediocre minds - Albert Einstein
The reason for using case sensitivity in an OS is that the ASCII
character has 256 distinct characters and 't' is not the same character
as 'T'. It is not good for the OS to decide that when I typed
MyFirstProgram.java that Myfirs~1.jav is a better name.
The worst thing about windows is that if I enter a file name bob.java,
explorer automatically changes that to Bob.jav. If I have files named
Bob.java.save1, bob.java.save3, BOB.java.save2, I get Bob~1.sav,
Bob~2.sav, Bob~3.sav and I have to go to extra trouble to find out which
is which. I recently ran into a situation where I had to download three
directory structures from different Unix based systems onto a windows95
machine. One was named projects, one Projects and the third PROJECTS.
They contained lots of files with similar names. That job took less than
10minutes on my Linux machine. I only had to change one of the compiler
paths in the make files. On the windows system it took 3 days because I
had to change all the make files to recognize new directory names. Put
files into new directory structures. Well, there were some things that
better programming practices would have helped, but you get the idea.
--
Russ Lyttle, PE
<http://www.flash.net/~lyttlec>
Thank you Melissa!
Not Powered by ActiveX
------------------------------
From: "Jakub Chmielewski" <[EMAIL PROTECTED]>
Subject: Re: S3 Trio 3d Video card
Date: Mon, 12 Apr 1999 23:46:38 +0200
Leo Cambilargiu napisa�(a) w wiadomo�ci: ...
>The XWindows system which comes with RH5.0 doesn't support this video
>card.
>Does anyowe know were I can find a version which does?
>
>A Celery PII on VIA chipsets with a S3 Trio 3d w/ 4 mg vram <==
No free X-server is currently available. See www.xfree86.org for details.
There is a trialware www.scitechsoft.com (scitechsoft display driver beta
version) for linux XFree.
www.xig.com also sell their driver.
See ya!
Jakub Chmielewski
------------------------------
From: Arun Muthukumaran <[EMAIL PROTECTED]>
Subject: easy-to-configure soundcard
Date: Mon, 12 Apr 1999 12:27:37 -0500
Hello,
Could anyone please suggest an easy-to-install,
not-so-expensive-yet-good sound card.... I know I'm asking for too much!
Any help would be appreciated.
Thanks,
Arun.
------------------------------
From: Gopal Cheruku <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Problem with disk partitioning. HELP!!!
Date: Mon, 12 Apr 1999 14:39:29 -0500
Hi:
I ran fdisk from RedHat 5.1 during installation of linux. When I enter
into fdisk it gave me a warning saying the number of cylinders on my
disk is set to 8912 which is greater than 1024. I ignored the error and
partitioned my disk and tried to install linux. When installation comes
to a point of loading LILO it gives an error and doesn't go any further.
I dos-formatted the whole 4 Gig hard drive. It still gives me the same
error. Please, could somebody tell me what could be wrong and how to
correct it?
Thanks
Gopal
------------------------------
From: [EMAIL PROTECTED] (Allen)
Subject: Re: 56K FAXMODEM
Date: 13 Apr 1999 01:00:33 GMT
HuH??? Tell us more!! Inquiring minds want to know... What was the model
number of the modem, and ALL the gory details?
On Mon, 12 Apr 1999 01:43:41 -0500, David Tate <[EMAIL PROTECTED]> wrote:
>I have recently installed a USR 56k PCI with success. I had to run
>pnpdump >isapnp.conf. Then edit it to set up the same irq that windows
>uses (irq 10). Then I copied it to /etc. I also made sure that modem
>was linked to /dev/ttys1.
>
> I hope this helps for PCI.
>
> David A Tate <[EMAIL PROTECTED]>
>
...snip...
Allen
(email addy; user ID portion has a numeral one in place of word
onespoiler, and of course, delete the bogus secondary domain of nospam.)
PC/hardware Guru, and Linux Newbie
------------------------------
From: [EMAIL PROTECTED] (Allen)
Crossposted-To: comp.os.linux.networking
Subject: Re: Netgear ISA EA201c NIC
Date: 13 Apr 1999 01:00:32 GMT
On 11 Apr 1999 21:12:18 -0700, [EMAIL PROTECTED] (J. P.) wrote:
...snip...
>Unfortunatelly I can't test it for a while because after putting in the
>NIC, I could not boot up my PC. Something must have been damaged during
>the operation. I'll have to figure out what.
It still won't boot after taking out the NIC? I guess at that point,
best thing to do is to dump the CMOS memory, and remove all cards or drive
connectors except video card, and start re-booting from there, adding parts one
at a time, 'till you find out which one won't allow you to continue.
Allen
(email addy; user ID portion has a numeral one in place of word
onespoiler, and of course, delete the bogus secondary domain of nospam.)
PC/hardware Guru, and Linux Newbie
------------------------------
From: Carlos Espino <[EMAIL PROTECTED]>
Subject: 2 Problems: I have a HP8100 CDR and Im very inexperenced linux user. Help!
Date: 12 Apr 1999 23:32:24 GMT
Thanks for your attention...
Please tell me how to make work my 8100 CDR unit in linux 2.2.36, and what
software do you suggest me to use...
My cdr actually its working..like cdrom, but i want to make it burn!!!
Please help me in a simple way to configure it..(Because im barely new
with linux)
Thanks 4 all...
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
Crossposted-To:
comp.lang.java.advocacy,comp.os.linux.advocacy,comp.os.ms-windows.advocacy
Subject: Re: All the current OSes are idiotic (was Re: Is Windows for idiots?)
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 12 Apr 1999 20:31:09 -0400
[EMAIL PROTECTED] (Jason V. Robertson~) writes:
> Case preservation = good. Case sensitivity - in the filesystem - =
> bad.
not necessarily.
> It's easy to make arguments for the former, hard to make them against the
> later. 99% of the time, if you type 'MyFilename' you mean (if it already
> exists) 'MyFileName'.
if capital letters cause you difficulty, *do* *not* *use* *them*.
what is so wrong with `myfilename'? it saves a pressing of the shift
key. i'd rather have *enforced* lower case than the case preservation
without sensitivity.
> You prevent more errors by coding to that 99%. It's pretty hard to
> think of legitimate cases for case sensitivity in the filesystem
> other than "Unix does it, so I need it."
filesystem case sensitivity has never caused me much lossage. at
least with upper and lower case, the letters are distinct.
weirdnesses like control characters in a filename, however, should be
banned by international treaty. ;-)
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
------------------------------
From: wizard <[EMAIL PROTECTED]>
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
Date: Mon, 12 Apr 1999 21:31:03 -0400
Reply-To: [EMAIL PROTECTED]
Urs Thuermann 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 these
> instructions exist only on the i686, right?
>
> What target should I specify to the glibc configure script? I guess
> i486-pc-linu-gnu does't what I want, right?
>
> However, then some i686 optimized routines are not used, although
> AFAICT based on my little x86 knowledge, these seem to run on other
> CPUs as well. For example
> glibc-2.1/sysdeps/unix/sysv/linux/i386/i686/sysdep.h.
>
> Maybe some pretty solution would be to have the i686-specific code in
> the lib and have an exception handler on the i486 that emulates the
> missing instructions, i.e. similar to the kernel's i387 emulation.
> Does something like this exist and how much performance loss would
> this cause compared to regular i486 code?
>
> And what about the kernel? The 2.0.36 config help files state that
> a kernel compiled for i486, pentium, or pentium pro will run on every
> cpu except i386. But in 2.2.5 this has changed and it is stated that
> code compiled for one CPU will not neccessarily run on a previous
> CPU. Is this due to compiler options or because of different inline
> assembly routines? I've looked at the make output and even if PPro
> is selected, the compiler is called with -m486, but -D586 is changed
> to -D686, so I assume some #ifdef selects between different inline
> assembly code, that will possibly not run on all ix86 CPUs.
>
> But what sense does the -m486 make, if the code does not necessarily
> run on an i486 anyway?
>
> OK, many questions and assumption in this posting. Can someone sched
> some light on all this and answer/correct/acknowledge.
>
> urs
>
> P.S. I have removed the linux.redhat.misc group from the Newsgroups
> line.
Did you rebuild all of your applications to work with Glibc. If you
made a major version change this could very well be the isssue. The
latest release of glib may not be compatiable with your installed
applications. This could mean that these application may need a
rebuild. In any even look seriously at upgrading the rest of you
system, if your will to use a bleeding edge compiler and library this
little upgrade should be a minor concern.
Thanks
Dave
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.x
Subject: Re: X terminal?
Date: Tue, 13 Apr 1999 01:37:35 GMT
Igel makes X Terminals w/a Linux based OS http://www.igelusa.com/
Neoware makes them, too http://www.neoware.com/ (I think Neoware was HDS)
Of course NCD http://www.ncd.com (they bought Tektronix's terminal division)
Wyse's high end winterminal has an x server http://www.wyse.com/
IBM and HP also make them (look for network computers)
The traffic issue stems from the fact that many X terminals did boot entirely
off the network. So, a terminal might download a 15MB (approx size of my HP
terminal's OS) OS file from the boot server. With a few of those on a taxed
10BT ethernet and the network might seem taxed, BUT ONLY when the things
first boot up. Now, many terminals can/do have their OSs loaded into a
flashdisk on the machine, eliminating that problem.
-J. Burrell
In article <[EMAIL PROTECTED]>,
Michael Meissner <[EMAIL PROTECTED]> wrote:
> "E. Robert Tisdale" <[EMAIL PROTECTED]> writes:
>
> > Chris Evich wrote:
> >
> > > What company makes them? Can I find them on the net anywhere?
>
> NCD is/was a maker of X terminals. There were a few others that have slipped
> my mind.
>
> > You don't want to buy a new Xterminal.
> > A Linux workstation is much cheaper.
> >
> > Most systems administrators won't let you put an old Xterminal
> > on the local area network because they soak up bandwidth.
>
> In general I would imagine that an X terminal will soak up as much bandwidth
as
> a Linux workstation acting as an X terminal. Traffic is traffic.
>
> --
> Michael Meissner, Cygnus Solutions
> PO Box 98, Ayer Massachusetts, USA 01432-0098
> [EMAIL PROTECTED]
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
** 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
******************************
