Subject: Linux-Development Digest #522 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Sun, 6 Mar 94 06:13:05 EST Linux-Development Digest #522, Volume #1 Sun, 6 Mar 94 06:13:05 EST Contents: TIOCLBIS and TIOCLBIC Ultrastor SCSI driver is confused by ultrastor ESDI card (chris ulrich) Re: Help! GCC errors (Rob Janssen) Re: eth0: transmit timed out in PL15h (Clint Olsen) Re: ISDN card comments wanted (Jim Campbell) Re: Where's ioperm() and in/outb()? (Jorge Nunes) Re: Specialix driver (Stephen Harris) Re: Help! GCC errors [STUPID IDIOTS ON COMP.OS.LINUX.* GROUPS] (John Henders) Re: AMD 486DX problem (with Linux?) (Michael Bongartz) Re: Amiga FileSystem, Anyone? (David Holland) Re: eth0: transmit timed out in PL15h (Chris Hafey) Ping, eth0, WD8023, 99pl15, crashes (Dhaliwal Bikram Singh) Re: Ping, eth0, WD8023, 99pl15, crashe: SOLUTION!! (Dhaliwal Bikram Singh) ---------------------------------------------------------------------------- From: freedman@athena.mit.edu () Subject: TIOCLBIS and TIOCLBIC Date: 5 Mar 1994 21:15:36 GMT I'm in the process of porting PCLU to Linux. I've gotten most of it to compile but now I'm stuck with a few undeclared constants. TIOCLBIS and TIOCLBIC are the most troublesome. On an Ultrics system, these constants are defined in /usr/include/sys/ioctl.h. I also noticed the constants TIOCGETC and TIOCSETC in this header file. On my Linux system TIOCGETC and TIOCSETC are defined in /usr/include/bsd/sgtty.h. I'm not sure what TIOCLBIS and TIOCLBIC are used for, but here are the comments from the ultrix includ file. #define TIOCLBIS _IOW('t', 127, int) /* Bis local mode bits */ #define TIOCLBIC _IOW('t', 126, int) /* Bic local mode bits */ This is one of the lines of code that uses TIOCLBIS. ioctl(ch->wr.num, TIOCLBIS, LLITOUT) The only other constant that is undefined is F_OK. This constant is defined to be 0 in the Ultrix file.h header and is used to tell if a file exists. This is the line of code where it is used. acc = access(fname.str->data, F_OK); Thanks for any advise on this project. -Aaron Freedman- freedman@athena.mit.edu ------------------------------ From: insom@galaxy.ucr.edu (chris ulrich) Subject: Ultrastor SCSI driver is confused by ultrastor ESDI card Date: 5 Mar 1994 04:43:01 -0800 I recently installed an ultrastor 22f in my computer. This is an eisa esdi controller card. The ultrastor SCSI driver detects this card and thinks it is a SCSI card, and crashes the machine. This happened with the slackware boot disk. If anyone is interested in more infomation about this bug, contact me. chris insom@ac.ucr.edu Ecstatic peace insom@ucrvms Savage conquest ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: Help! GCC errors Date: Sat, 5 Mar 1994 22:56:15 GMT Reply-To: pe1chl@rabo.nl In dgardner@netcom.com (Dave Gardner) writes: >Dean Junk (us292121@bulldog.mmm.com) wrote: >: Take this as you wish ... piss off! I can't beleive the attitude of some >: of the people on this newsgroup. >Dean, you're not alone. >I started using Linux about a year ago with SLS, before I and many others >knew just how broken it was. Many of us had lots of problems and asked >lots of questions, most answered much the same way as you got here. >Rather than politely either answer the question, or point out where the >answer might be found, many Linux 'experts' chose to instead wield their >often questionable wit to insult. And nobody, expert or newbie, likes to >be insulted; it has nothing to do with the thickness of the skin. You must have missed that this newsgroup is about "Ongoing work on the Linux operating system", not about asking questions. That largely explains the attitude towards people asking questions anyway, especially when they are so clearly answered in the read.me file that came with the package that they are asking about... Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: olsenc@maxwell.ee.washington.edu (Clint Olsen) Subject: Re: eth0: transmit timed out in PL15h Date: 5 Mar 1994 21:08:29 GMT In article <2l58o0$mv7@senator-bedfellow.mit.edu>, Erik Nygren wrote: >I've been getting messages like: > >Mar 3 11:16:50 foundation kernel: eth0: transmit timed out, tx_status 00 status > 2000. > >ever since pl14 when I first installed my 3Com 3c509. The problem still >exists in pl15h and in pl15i with the 3c509 patch. I did a survey >of other people on campus and determined that 5 out of 6 people >with 3c509's running Linux encountered this problem. Generally, it >only appears while transmitting large amounts of data (ie serving ftp). > >No data gets lost and it is able to recover, but it does slow down >transmissions quite a but as the card recovers. > >I've talked to Donald Becker who thinks that it may be a problem with the card or >the network since that error appears under NetBSD as well with the 3c509. > >Anyone else encounter this, know what might be causing it, or know a way >around it? I was warned by my boss about this. Apparently, the 3c509 has a tiny buffer on the card, as opposed to something infinitely more useable (2k ?), and you will get all kinds of problems with overruns in the buffer. It makes sense that you have problems with big transfers. This was his experience using this card with packet drivers in D*S. I bought a 3c503 card instead. I heard it has a more adequate buffer. Please discuss. -Clint -- Clint Olsen University of Washington Electrical Engineering olsenc@maxwell.ee.washington.edu ------------------------------ From: jimc@fietop.Raleigh.NC.US (Jim Campbell) Subject: Re: ISDN card comments wanted Date: Sat, 5 Mar 94 10:53:25 -0500 In archie@cory.EECS.Berkeley.EDU (Archie Cobbs) writes: >A company I've worked for is interested in the possibility >of developing an ISDN card for the PC... IBM is currently marketing an ISDN card for PCs (both ISA-bus and MCA). It is named the Waverunner. You might have the company check this out before investing development money into another one. As memory serves, the Waverunners retail somewhere in the $500 range. E-mail me if you would like more info. -- Jim Campbell (919) 848-9298 ------------------------------ From: jfn@pc-visao-4.inesc (Jorge Nunes) Subject: Re: Where's ioperm() and in/outb()? Date: Sat, 5 Mar 1994 10:30:09 GMT I dont't know if ioperm() is really a library function but as for inb() and outb() they are defined as inline functions. You will have to compile with the -O switch, otherwise you will get the unresolved symbols you mentioned. I have been using these functions successfuly to interact with some special hardware on my machine. Dont't forget to include (I'm using Slackware 1.1), where they are declared, and to run your binary as root. Hope this helps. Jorge Nunes -- =========================================================== Jorge Filipe Franco Nunes E-mail: jfn@vision.inesc.pt ------------------------------ From: sweh.womble@spuddy.UUCP (Stephen Harris) Crossposted-To: gnu.misc.discuss Subject: Re: Specialix driver Date: Sat, 05 Mar 94 12:28:00 GMT [ slightly off topic, sorry ] In article <2l5u1p$vcj@zealot.uucp> kmedcalf@zealot.uucp writes: >The problem is the number of numbnuts that do not even know the meaning of >the word DERIVED even though they seem to spout off about it for megabyte >after megabvyte of useless interpretation that would be made much simpler if >they could merely understand the Kings' English! Hee hee. Since when have legal definitions of words necessarily agreed with English definitions? And in the case of a word that has multiple definitions, does the legal wording cover all definitions, or merely the definition that applies in context? This is why some legal papers can spend most of the time defining words and limits of the definitions! Whole legal cases have been argued over the definition of a word. And to make things harder, the English definitions can change over time (eg "Gay"). I'm sure that if someone took the GPL and scrutinized it according to strict English definitions, they would get a conclusion that is not the correct one understood in law. -- Stephen Harris sweh.womble@spuddy.uucp ...!uknet!axion!spuddy!sweh.womble * Meow! Call Spuddy the Cat for Usenet access in the UK. Call 0203 364436 * ------------------------------ From: jhenders@jonh.wimsey.com (John Henders) Subject: Re: Help! GCC errors [STUPID IDIOTS ON COMP.OS.LINUX.* GROUPS] Date: Sat, 5 Mar 1994 20:58:57 GMT crfisher@nyx10.cs.du.edu (I am being repressed.) writes: Crossposting to Newsgroups: comp.os.linux.development,alt.pud,alt.stupidity Thanks for doing your part to keep to the charter of the linux development group. >In article <2kvr8o$4iv@senator-bedfellow.mit.edu>, >Mitchum DSouza wrote: >>Dean Junk: >> Do one of the following: >> >>1) Read the library release notes TO THE LETTER - EVERY SINGLE SENTENCE. >>2) Read the GCC-FAQ before asking GCC related queries. >> > Although it may seem that every newsgroup in the c.o.l.* > series actually have the word flame in them, they do not. I am so > sick of the petty replies and responses I see here all the time. > If you can not help someone then do not bother to even reply. So it helps people to encourage them to post to the wrong group, does it? what about the people who are trying to use the group for the reason it was created? Don't they count, in your worldview? If you think Mitchum didn't answer the question because he didn't know the answer, you're as clueless as you appear. If you prefer people quitely suffer the clueless postings here to the wrong groups, perhaps you also favour all the people who have a clue retreating to mailing lists where they don't have to put up with this idiocy. > You > do no one any good when you do. All you do is waste resources > and show that you don't even know hot to flame properly. And we can take your post as a good exaple of this? -- John Henders - Wimsey Information Services GAT/MU/AE d- -p+(--) c++++ l++ u++ t- m--- e* s-/+ n-(?) h++ f+ g+ w+++ y* ------------------------------ From: micha@mubo.saar.de (Michael Bongartz) Subject: Re: AMD 486DX problem (with Linux?) Date: Sat, 5 Mar 1994 20:46:44 GMT On 05 Mar 1994 05:42:38 GMT in comp.os.linux.development, Gregory McKesey (mckesey@imaphics.prior.com) wrote: : I have found an annoying problem with the AMD 486DX chip and : Linux that is leading me to believe that there may be a compatibility : problem with this chips math functions. One reported symptom is : that ghostscript dies during initialization. While trying to track : down the problem I booted my kernel with the no387 option (using Lilo). : To my surprise ghostscript worked in this configuration. : I decided to investigate further, and found a problem with : single precesion (ie float) multiplys. The following is a sample : program that illustrates the problem. I couldn't resist testing this on my AMD 486 DX2/66 system: micha@moko|~/tmp>cc -o float float.c micha@moko|~/tmp>float 1.312500 * 7.999900 =10.499868 1.312500 * 7.999900 =10.499869 Test succeeded! It seems that this bug doesn't exist on all AMD chips. Micha -- A bad ad can ruin your whole day! EMail: micha@mubo.saar.de /\/\ University: bongartz@cs.uni-sb.de Voice: 0681/556-54 / \ Fax + Modem (ZyX 19k2): +49 681 556-34 SnailMail: Michael Bongartz, Hohe Wacht 18, 66119 Saarbruecken, Germany ------------------------------ Subject: Re: Amiga FileSystem, Anyone? From: dholland@husc7.harvard.edu (David Holland) Date: 5 Mar 94 23:25:31 rob@pe1chl.ampr.org's message of Thu, 3 Mar 1994 09:15:13 GMT said: > > [stuff about Amiga floppies] > > Is this comment backed by technical knowledge and/or experience with > other products? Some. It's hardware, so everything I say must be qualified with a disclaimer. (I did say "should"...) However, I would guess from the complete lack of existing software (including specialized DOS programs to tweak the hardware like exist for Mac floppies) that there's at least one big problem I don't know about. :-) The strange stuff the trackdisk.device does should be possible with PC hardware, unless that hardware is even less capable than I thought. If the Amiga does something else, like write more tracks than the average PC drive can access, I don't know about it. > Hey, come on! Now *that*'s complete nonsense! You never saw an > MS-DOS machine read a CD-ROM or access a network file system? Yes, I have. It's amazing that it can be done at all, however poorly... :-) -- - David A. Holland | Nobody ever went broke underestimating dholland@husc.harvard.edu | the intelligence of the American public. ------------------------------ From: chafey@ecst.csuchico.edu (Chris Hafey) Subject: Re: eth0: transmit timed out in PL15h Date: 6 Mar 1994 05:33:26 GMT In article <2lascd$7uc@news.u.washington.edu>, Clint Olsen wrote: >In article <2l58o0$mv7@senator-bedfellow.mit.edu>, >Erik Nygren wrote: >>I've been getting messages like: >> >>Mar 3 11:16:50 foundation kernel: eth0: transmit timed out, tx_status 00 status >> 2000. >> >>ever since pl14 when I first installed my 3Com 3c509. The problem still >>exists in pl15h and in pl15i with the 3c509 patch. I did a survey >>of other people on campus and determined that 5 out of 6 people >>with 3c509's running Linux encountered this problem. Generally, it >>only appears while transmitting large amounts of data (ie serving ftp). >> >>No data gets lost and it is able to recover, but it does slow down >>transmissions quite a but as the card recovers. >> >>I've talked to Donald Becker who thinks that it may be a problem with the card or >>the network since that error appears under NetBSD as well with the 3c509. >> >>Anyone else encounter this, know what might be causing it, or know a way >>around it? > We have been running our linux boxes mainly on 3c509's. We encounter the problem you talk about quite frequently. Our linux File Server gives out these messages because of the high traffic it receives. We also have a linux box set up to run a MUD, and it regularly has 50-60 mud users on it (yes its a popular one, Highlands I think). It also complains about transmit time out errors. I did some debugging/testing on the card and I didn't find a problem with Donald's driver. I also talked with 3com and they said that it isn't the cards fault, its the driver. I haven't tried out the 15i release yet, but the 3c509 is not suitable for high traffic lans. We had a linux box on our busiest subnet here and it choked. >I was warned by my boss about this. Apparently, the 3c509 has a tiny >buffer on the card, as opposed to something infinitely more useable (2k ?), and >you will get all kinds of problems with overruns in the buffer. It makes sense >that you have problems with big transfers. True, you will always get this message if you try to ftp to a local machine. It is especially bad between two linux boxes both with 3c509's in them. I end up getting about 50K per second between two linux boxes because the cards seem to get really confused talking to each other. My guess is that it is a hardware problem. Chris -- =============================================================================== Chris Hafey * True programming is rebooting the machine chafey@ecst.csuchico.edu * after each crash until it works. ------------------------------ From: a336dhal@cdf.toronto.edu (Dhaliwal Bikram Singh) Subject: Ping, eth0, WD8023, 99pl15, crashes Date: Sun, 6 Mar 1994 07:40:26 GMT I am having some major problems getting my little mini-network setup. I have two identical WD80x3 cards (10baseT), and I have hard wired the settings in the kernal: IO addr=0x300 IRQ = 9 Memory = 0xCC00 ping -c1 suedehead.org gives: ping suedehead (197.100.1.22): 56 data packets eth0: bogus packet, status=0x0,nxpg=0x10,size=68 I get this no matter what but only on one machine, the other seems fine. I think this card is a 16K card, since the DOS config for it lets me set it at that (it is used, don't have any manuals). I have two computers, identical except one has 8 megs , the other 4 megs. The 4 meg machine crashes regularily if I try to ping it from the 8 meg machine, however the 8 meg machine never crashes regardless of what I do. In fact I can make the 4 meg machine crash by trying to rlogin or ping from the 8 meg machine. Both are running the same kernel. here is my hosts file: /etc# cat hosts # /etc/hosts: List of hostnames and IP addresses 127.0.0.1 localhost 197.100.1.21 bigmouth.org bigmouth 197.100.1.22 suedehead.org suedehead here is my rc.inet1 for the 8 meg machine: (partial) IPADDR="197.100.1.22" # Your IP address NETMASK="255.255.255.0" # Your netmask NETWORK="197.100.1.0" # Your network address BROADCAST="" # Your broadcast address (blank if none) GATEWAY="" # Your gateway address and for the 4 meg machine: IPADDR="197.100.1.21" # Your IP address NETMASK="255.255.255.0" # Your netmask NETWORK="197.100.1.0" # Your network address BROADCAST="" # Your broadcast address (blank if none) GATEWAY="" # Your gateway address and my /etc/networks file: loopback 127.0.0.0 localnet 197.100.1.0 Please help, this is really disturbing behaviour. Is the smaller machine crashing because of memory? -- -a336dhal@cdf.toronto.edu -bikram dhaliwal ------------------------------ From: a336dhal@cdf.toronto.edu (Dhaliwal Bikram Singh) Subject: Re: Ping, eth0, WD8023, 99pl15, crashe: SOLUTION!! Date: Sun, 6 Mar 1994 09:25:59 GMT In article <1994Mar6.074026.16826@cdf.toronto.edu> a336dhal@cdf.toronto.edu (Dhaliwal Bikram Singh) writes: >I am having some major problems getting my little mini-network >setup. I have two identical WD80x3 cards (10baseT), and I have >hard wired the settings in the kernal: >IO addr=0x300 >IRQ = 9 >Memory = 0xCC00 > I eventually figured out that the problems that I was having was hard-ware related. I went to the dianostic part of the CMOS setup for the card, the card failed 4 of 5 memory tests, so I put the cards memory from the low of 0xCC00 to 0xDD00. And now all of a sudden everything works great. >ping -c1 suedehead.org gives: >ping suedehead (197.100.1.22): 56 data packets >eth0: bogus packet, status=0x0,nxpg=0x10,size=68 > >I get this no matter what but only on one machine, the >other seems fine. > >I think this card is a 16K card, since the DOS config for it lets >me set it at that (it is used, don't have any manuals). > >I have two computers, identical except one has 8 megs , the other 4 megs. >The 4 meg machine crashes regularily if I try to ping it from the >8 meg machine, however the 8 meg machine never crashes regardless >of what I do. > >In fact I can make the 4 meg machine crash by trying to rlogin or >ping from the 8 meg machine. Both are running the same kernel. > >here is my hosts file: > >/etc# cat hosts ># /etc/hosts: List of hostnames and IP addresses >127.0.0.1 localhost >197.100.1.21 bigmouth.org bigmouth >197.100.1.22 suedehead.org suedehead > >here is my rc.inet1 for the 8 meg machine: (partial) > >IPADDR="197.100.1.22" # Your IP address >NETMASK="255.255.255.0" # Your netmask >NETWORK="197.100.1.0" # Your network address >BROADCAST="" # Your broadcast address (blank if none) >GATEWAY="" # Your gateway address > >and for the 4 meg machine: > >IPADDR="197.100.1.21" # Your IP address >NETMASK="255.255.255.0" # Your netmask >NETWORK="197.100.1.0" # Your network address >BROADCAST="" # Your broadcast address (blank if none) >GATEWAY="" # Your gateway address > >and my /etc/networks file: > >loopback 127.0.0.0 >localnet 197.100.1.0 > > >Please help, this is really disturbing behaviour. Is the smaller >machine crashing because of memory? > >-- >-a336dhal@cdf.toronto.edu >-bikram dhaliwal -- -a336dhal@cdf.toronto.edu -bikram dhaliwal ------------------------------ ** 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: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development) via: Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Development Digest ******************************