HDTenEightyP/NetNews huggingface dataset:
Subject: Intel 400 modem working in Linux?
Distribution: world
Organization: Demon Internet Services
Reply-To: pm2@aries.demon.co.uk, pm2@doc.ic.ac.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Thu, 28 Jan 1993 19:18:16 +0000

Hi,

Has anyone been able to get the Intel Satisfaxtion 400 modem (the internal
one) working in Linux?  I know it's not supposed to work because of the need
to load the DOS device driver first to initialise the modem.  I am asking
because I found out that once the driver is loaded in DOS, you can actually
reboot (warm instead of cold) your machine and use the modem in DOS without
loading the driver again (I have tested this many times).  So I assume maybe
the driver stays resident in the modem during the warm reboot.  However, I've
not been successful to do this in Linux (i.e. booting DOS to load the driver
and then warm boot to load Linux).  My 400 is configured as com2.  After Linux
boots, it doesn't seem to recognize the presence of com2 at all.  Has anyone
got a way round this?  I'd love to use my modem under Linux instead of DOS.

Thanks.

Paul.

-- 
Paul Ma                                Email : pm2@doc.ic.ac.uk
Department of Computing                        pm2@aries.demon.co.uk
Imperial College                               70262.3352@compuserve.com
University of London		       
United Kingdom                         Voice : +44-81-2082677
Newsgroups: comp.os.linux
From: skip@junior (Geoff Rothfuss)
Subject: Re: problem with SLS 0.99, 'ps' and 'w' cmds complain 'bad offset 0xXXXXX'
X-Newsreader: Tin 1.1 PL3
Distribution: comp
Date: 21 Jan 93 14:33:21 CST


    Try typing  'ps -U' or 'ps -U /usr/src/linux/tools/system' .
 
   This will rebuild psdatabase.


                                                      SKIP...
Newsgroups: comp.os.linux
From: agc@weasel.demon.co.uk (Alan Charlton)
Subject: Re: Groff won't do PostScript!  Sob!
Organization: home
Apparently-To: mail2news@news.demon.co.uk
Date: Tue, 26 Jan 1993 19:41:19 +0000

In article <1993Jan26.084403.10094@newshub.ariel.yorku.ca> cs911461@ariel.yorku.ca (CHRISTIAN D. ARMOUR) writes:

   $ groff -Tps -man lc.1 > lc.ps

   Here's what it says:

   gtroff: can't open `DESC'
   gtroff: fatal error: sorry, I can't continue

I had this problem.  It appears that the groff which came with the
0.98.5 SLS (like wot I have) is - errr.... broken.  As a stop-gap
measure I did a work-around as follows:

	groff -Tdvi file > file.dvi

then;

	dvips file.dvi -o file.ps

...which worked a treat on the elm 2.4.20 documentation.  However, I
then grabbed the sources for groff-1.06 from prep.ai.mit.edu and made
it (and boy, does that c++ object code take up a lot of disk space!).
I tried the `-Tps' thing again, and this time it worked.  Strangely
enough, though, I found that the fonts generated by dvips are *vastly*
superior in terms of readability and style than the ones generated by
the groff Postscript driver.

Moral:  don't bother with `groff -Tps' - use `groff -Tdvi'and `dvips'
	instead!

Hope this helps,

Alan
--
|  Alan Charlton            |  `Time is an illusion -   |
|  agc@weasel.demon.co.uk   |   lunchtime, doubly so.'  |
|  agc@cix.compulink.co.uk  |  - Douglas Adams          |
From: feoh@hal.gnu.ai.mit.edu (Chris Patti)
Newsgroups: comp.os.linux
Subject: Re: Linux on Amiga?
Date: 27 Jan 93 18:45:11 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.ai.mit.edu

This question continues to pop up every now and again.

There was *TALK* of an amiga port, and that's all.

Linux is inexorably intertwined with the Intel 80x86 chipset.. porting it
to motorola chips would be EXCEEDINGLY difficult at best...

For amiga owners, why not check out AmigaMach, which actually *exists* :)
or try Minix..

As for an Amiga linux port.. Don't hold your breath.. I waited awhile and then
gave up and bought a 486 to run Linux on :)
From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
Newsgroups: comp.os.linux
Subject: Re: Why not splitting this group?
Date: 27 Jan 1993 14:00:22 -0600
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

unrzf0@cip.rrze.uni-erlangen.de (Carl Scheuermann) writes:

>Hi,

>I know, there has been a lot of talking about splitting this group.
>But I can't understand, why it isn't possible to find a solution to this
>problem. There are so many questions on how to install the XServer. So
>why not creating a group comp.os.linux.X11. Or, for the people working
>with TCP/IP, making a group comp.os.linux.TCP?
>Please don't kill me if I say something that has been said a lot of times.
>But the current state of this group isn't bearable any more - and it WILL 
>get worse.

>Bye the way,
>can someone tell me the difference of all the different S3 chip versions?
>All the different chips I know of is 911, 928 and 801. Are there more of them?
>(why does the latter one don't have such a cute Porsche modell number?)

>thanx 4 your answers,

>Carl

The group was attempted to be split about 2 months ago, and failed. Thus
according to policy, no new discussions for splitting should be brought
up for 6 months. (Around May then from what I remember).

As a general rule, from what I have seen splitting groups does nothing
to help traffic. As a matter of fact, it tends to increase as things
get cross-posted. Overall the flood of articles does seem to be slowing a
little lately.

James
Newsgroups: comp.os.linux
From: ggerard@alex (Greg Gerard)
Subject: SLS: will it be going to pl4 soon?
Followup-To: ggerard@tusol.cs.trinity.edu
Organization: Trinity University, San Antonio TX, USA
Date: Fri, 22 Jan 1993 04:45:06 GMT

with the new release of .99pl4, will SLS be updated in the next few days?

thanks,
greg
ggerard@tusol.cs.trinity.edu
Newsgroups: comp.os.linux
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Trouble getting DOS emulator to work
Summary: Can't get to first base
Organization: Computer Science, University of Melbourne, Australia
Date: Tue, 26 Jan 1993 14:56:31 GMT

I have tried the DOS emulator for linux 0.97 pl5 or better
(I am running 0.99.1, and got dosemu in a recent SLS release).
Unfortunately it doesn't seem to get very far. Here is what happens, after
following the instructions in the README.

$ dos > errs
		(floppy disk drive is accessed for a couple of seconds,
		screen clears, then prompt returns)
$ cat errs	
EMULATE
ISBLK
dev : 200
DISK /dev/fd0 removeable
ISBLK
dev : 201
DISK /dev/fd1 removeable
FLOPPY /dev/fd0 h=2, s=9, t=40
general protection
 cs    eip     ss    esp      flags    ds   es   fs   gs 
   0:00000000    0:00000000 00000000    0    0    0    0
  eax      ebx      ecx      edx      edi      esi      ebp
00000000 00000000 00000000 00000000 00000000 00000000 00000000 
 e8 5b 02 00 00 b8 2d 00 00 00
booted

Does anyone have any clues as to what might be going wrong?

P.S. mail to the author lautner@informatik.uni-wuerzburg.de bounced.

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
Newsgroups: comp.os.linux
From: cummings@hammer.prime.com (Kevin Cummings)
Subject: Re: Changing video modes after boot time
Organization: Prime Computer, Inc.
Date: Fri, 22 Jan 1993 18:33:41 GMT

In article <13875@tranter>, tranter@Software.Mitel.COM (Jeff Tranter) writes:
> On bootup the Linux kernel can prompt for video mode selection, but is
> there any way to change it afterwords without rebooting? Different
> users may want different video modes, or perhaps I want to run emacs
> in 132x43 mode but the shell in 80 columns.

The prompt at boot time occurs while the machine is still running in
REAL mode and the video BIOS is still available.  The resulting choice
is made with an INT 10 BIOS call (or more than one if necessary).

After LINUX is up and running (in protected mode), all mode changing
has to be done by programming the video hardware directly, and different
boards have different programming requirements.  Sure, you could write
some programs to work on YOUR video board, but there is no guarrentee
that it will work on some other brand video board.

How best to run emacs in 132x43 and your shell as 80x50?  Use X-Windows!
After you have the resolutions you want, you can pick the font that
looks best for you!  Sorry, but if you're unable to configure
X on your system, then I have no good alternative for you.

=================================================================
Kevin J. Cummings                       ComputerVision Services
20 Briarwood Road                       500 Old Connecticut Path
Framingham, Mass.                       Framingham, Mass.
					
Home:  cummings@kjc386.framingham.ma.us	Work:  cummings@primerd.Prime.COM

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
Newsgroups: comp.os.linux
From: tjrc1@cus.cam.ac.uk (T.J.R. Cutts)
Subject: Re: S3 801 (Actix GraphicsEngine32)
Organization: U of Cambridge, England
Date: Sun, 24 Jan 1993 15:13:30 GMT

In article <74250@cup.portal.com>, sseto@cup.portal.com (Shinichiro S Seto) writes:
|> Hello!
|> 
|> I just wnat to know if XS3 supports Orchid Fahrenheit VA 801.
|> If it does, which version of the server?
|> I've been struggling to get it work and am getting to suspect
|> that XS3 DOES support it. I know you guys are tired of this
|> kind of question. But, this is a very serious matter for me,
|> because I've already sold my good old ET4000 board.

Yep.  Version 0.3.1 for 801 chips.  Earlier versions have some bugs, apparently. 
I have a 911 chip and both 0.2b and 0.3.1 work fine.

Tim.
Newsgroups: comp.os.linux
From: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Subject: Re: Bernoulli/SyQuest
Organization: Naval Research Laboratory
Date: Wed, 27 Jan 1993 16:18:18 GMT

In article <1993Jan27.011248.8864@colorado.edu> drew@romeo.cs.colorado.edu (Drew Eckhardt) writes:
>>(2) although the Syquest is a
>>"mountable" hard disk, the partition table on the cartridge is only
>>read once during boot up, so you are out of luck if you want to umount
>>and mount a different cartridge while the system is up and running.
>
>Nope, you can change cartridges.  Sending a BLKRRPART ioctl to the disk will 
>reread the partition table.  

	It is actually better than that.  The kernel should detect a disk
change and automatically reread the partition tables when you try and remount
the disk.  It should also flush all of the buffers and so forth, so you should
be able to change disks without any trouble.  I would like to know if this is
not the case for anyone.  I know of at least one person who indicated that
the automatic re-read of the partition table was working correctly.

-Eric

-- 
A host is a host from coast to coast.....eric@tantalus.nrl.navy.mil
& no one will talk to a host that's close..........................
Unless the host (that isn't close).................................
is busy, hung or dead................................Eric Youngdale
Newsgroups: comp.os.linux
From: fox@cs.nyu.edu (David Fox)
Subject: Re: SLS won't install a3 and up; still seeking help for this.
Organization: Courant Institute of Mathematical Sciences
Date: Tue, 26 Jan 1993 18:08:24 GMT

I got this behavior once when I asked it to prompt me for each package.
From: jimc@hal.gnu.ai.mit.edu (James Carpenter)
Newsgroups: comp.os.linux
Subject: ST-01 and Quantum
Date: 28 Jan 1993 01:27:39 GMT
Organization: Massachusetts Institute of Technology
NNTP-Posting-Host: hal.ai.mit.edu

I almost have everything working with my ST-01 and my Quantum. I finally got
the computer to operate with the host adapter and finally got linux to
partion it and make a file system on it. Now I'm getting, every now and
then, a "SCSI host 0 timed out - aborting command" message. Then the machine
hangs.

The board is set at C800 and IRQ 5. These are not conflicting with any other
hardware in place.

I'm almost there folks! I've ironed out a number of problems and hopefully 
someone out there can get me over this last hill! Thanks for any help.

-- 

	Jim Carpenter
	Carpenter@Eisner.DECUS.Org
	jimc@gnu.ai.mit.edu
Newsgroups: comp.os.linux
From: wirzeniu@klaava.Helsinki.FI (Lars Wirzenius)
Subject: Re: Motif for Linux ?
Organization: University of Helsinki
Date: Fri, 22 Jan 1993 15:12:29 GMT

nan@matt.ksu.ksu.edu (Nan Zou) writes:
>Having the Motif widget set would definitely be a big plus,

While I too think that the diverse user interfaces of X programs is a
bad thing, I don't think Motif has much of a future for Linux until it
becomes free distributable in source form.  One of the reasons behind
the success of Linux, GNU software, and X (to name a few examples) is
that the source is readily and freely available and distributable.
Having to rely on other people to get binaries that work with new
compilers and libraries is a bad idea.

--
Lars.Wirzenius@helsinki.fi  (finger wirzeniu@klaava.helsinki.fi)
   MS-DOS, you can't live with it, you can live without it.


Newsgroups: comp.os.linux
From: markus@mwhh.hanse.de (Markus Witt)
Subject: Re: SLS: how do we know we've caught up ?
Organization: Nothin' is organized here.
Date: Thu, 21 Jan 93 21:01:49 GMT

vince@victrola.sea.wa.us (Vince Skahan) writes:

[how to keep up with Linux and SLS improvements or better how to
 know if all is the newest stuff]

I second that and I think one possible solution would be to put a
file called SLS.930120 or something like that into the archives
containing a list of all files being part of SLS distribution of
*THAT* day with a checksum for each file, so that one could write
a program/script to check the integrity of the distribution.

Don't get me wrong, I don't talk about checking *after* but before
installing.

Also sysinstall could check during installation if the package being
installed is ok with a list only for that package.

As I think longer about it, I think there should be a list for each
package, not for the whole distribution.
After all, there are distributions so that you don't need to install
all of it.


Markus
-- 
Arthur prodded the mattress nervously and then sat on it himself: in fact
he had very little to be nervous about, because all mattresses grown in the
swamps of Sqornshellous Zeta are very thoroughly killed and dried before
being put to service. Very few have ever come to life again.
                                   -- The Hitch Hiker's Guide to the Galaxy
From: Ekkehard.Burkon@f129.n246.z2.fidonet.org (Ekkehard Burkon)
Newsgroups: comp.os.linux
Subject: Re: Internal compiler error while building kernel
Date: Mon, 18 Jan 1993 13:17:00 -0800

Hallo Hakkarainen!

Am 14 Jan 93 10:33 schrieb Hakkarainen Kimmo an All:

K> I have also Maxtor 7213at drive and have often got that fatal signal
11
K> when compiling. The compiling can be successfully completed if the
machine
K> is rebooted. I just read that article yesterday and decided to check
K> whether, my version is the old one. It was PCBA 65. Is it too old ?

I have the same problem here. But I have a Conner 30204. And the problem
occured only with gcc 2.3.3 with the old version I had no trouble at
all.

Anybody an idea???

cu

       Ekkehard

Internet: burkon@dvsatr.edv.agrar.tu-muenchen.de

 * Origin: Come on, make my day! (2:246/129)

Newsgroups: comp.os.linux
From: richmond@sml.cs.psu.edu (Matt Richmond)
Subject: defrag problems
Organization: Surely you jest
Date: Tue, 26 Jan 1993 04:22:17 GMT

 Hi fellow Linuxers.  I know that the newextfs is out and also
xiafs, but since these filesystems are relatively untried, I've
decided to stick with extfs.  Thing is, I can't get defrag to
work now.  I'm running 99.4 on a 486/33 with IDE and 16megs RAM.
defrag compiles fine, both with and without -static, but when
I try to run it, I get a core dump.  Has anyone else had this
problem?  I'm really at a loss as to what could be wrong seeing
how it compiles cleanly.  Oh, it core dumps with/out -static.
Any help would be greatly appreciated.  Thanks..

--Matt Richmond
Newsgroups: comp.os.linux
From: awitt@euler.fernuni-hagen.de (Andreas Wittkemper)
Subject: TMC885 + ST1096N, no scsi drive found
Organization: FernUniversitaet Hagen
X-Newsreader: TIN [version 1.1 PL8]
Date: Thu, 28 Jan 1993 14:22:59 GMT

I have a problem with my Future Domain SCSI Adapter (TMC885).
As i tried to install Linux from the SLS package, the SCSI Drive
wasn't recoignized. (ST 1096N) .The Adapter was clearly recoignized.
Only the drive wasn't found and so fdisk could't work :-(

Andreas

--
+--------------------+-------------------------------------------------+
| Andreas Wittkemper | FernUniversitaet Hagen, Theor. Inf. II,         |
| Ostenbergstr 109   | Postfach 940, 5800 Hagen                        |
| 4600 Dortmund 50   | Fax: +49 2331 987 313                           |
| Tel: 0231/753018   | Tel: +49 2331 987 2186                          |
+--------------------+-------------------------------------------------+
| EMail : Andreas.Wittkemper@fernuni-hagen.de , Merkur@hot.zer.de      |
+----------------------------------------------------------------------+

Newsgroups: comp.os.linux
From: Mario Guerra <MGUERRA%UCRVM2.BITNET@mitvma.mit.edu>
Subject: Some considerations when making a new Linux kernel
Reply-To: MGUERRA%UCRVM2.BITNET@mitvma.mit.edu
Organization: The Internet
Date: Sat, 23 Jan 1993 11:11:58 GMT

One should be careful of checking some parameters in the general Makefile:

- Check the root filesystem. The default is /dev/hdb1.
- Check the VGA MODE. I have a normal VGA card and the first time Linux
  asked for a SVGA mode....
- Check the RAMDISK line. If you want a RAM disk, uncomment the line.
- Check the KEYBOEARD you want to use.

+----------------------------+
| MARIO GUERRA               |
| MGUERRA@UCRVM2.BITNET      |
| UNIVERSIDAD DE COSTA RICA  |
+----------------------------+
|   VOICE: +506-24-88-29     |
|          +506-25-92-92     |
|   FAX:   +506-53-60-75     |
+----------------------------+
From: kankkune@klaava.Helsinki.FI (Risto Kankkunen)
Newsgroups: comp.os.linux
Subject: Re: Dumb question: new executable format?
Date: 21 Jan 93 21:33:26 GMT
Organization: University of Helsinki, Department of Computer Science

>Either we could adopt BSD-style executables with a 4K header and lots
>of wasted space, or we could do as someone suggested on comp.os.linux
>(sorry can't remember your name, but for the record it was not my
>idea) and put the header in the first page of the text segment,
>supposedly including a header version number and a pointer (or even
>better, a jump instruction) to the beginning of the actual code.

I don't understand why you need a pointer or a jump, but anyway...

I think sun uses a 32 byte header, which is directly followed by the
code. The header gets (and stays) loaded with the first page (and is
part of it) and the program entry point is defined to be 32 (I think).

There is already support for this in the GNU utils, so adapting
something like this to Linux wouldn't be difficult. Reserving a distinct
magic number for this would keep things unambiguous.
-- 
                  dos, windows, nt... are you a victim of the MS disease?
From: bitbangr@moosevax.cojones.com (Anthony W. Hursh)
Newsgroups: comp.os.linux
Subject: Re: SLS not booting??
Date: Tue, 26 Jan 93 16:41:50 AST
Organization: Mooseware Productions, Anchorage, Alaska

wolf@sol.cs.uni-sb.de (Wolfgang Huwig) writes:

> In article <C1BxG3.FnG@iat.holonet.net> emelton@iat.holonet.net (Edwin Melton
> 
> >   When I boot the system from the floppy, I get the screen as follows:
> >

        <screen dump deleted>'

> I got similar messages when booting a kernel written with dd.

> Maybe it's a physical problem with your disk (weak sectors or some
> such).

This may well be the case. When I was first installing the bootdisk/rootdisk
combo some time ago, the first bootdisk I made *refused* to boot, giving
similar messages to what you and Edwin got. I tried remaking the disk a
couple of times. No joy. When I tried using a different disk, though, it
worked fine. The first "bad" disk works fine with (gak) MS-DOS (no bad
sectors reported when formatted, e.g.), but will not boot Linux at all.
It's my guess that something in the boot code is much pickier than Messy
when it comes to marginal disks. Timing, perhaps? Or maybe the boot code
doesn't retry "bad" sectors enough times? I know that Messy will retry
a sector numerous times before giving up and popping up that horrible
"Abort, Retry, Fail?" message.


--
I was born in a Hostess Cupcake factory before the sexual revolution!
Internet: bitbangr@moosevax.cojones.com 
WWIVnet:bitbangr#moosevax.cojones.com@500 or: 1@500
UUCP: ..!uunet!coldbox!moosevax!bitbangr
From: marc@r-node.pci.on.ca (Marc G Fournier)
Subject: Re: v.32 Modem and uugetty...
Organization: R-node Public Access Unix - 1 416 249 5366
Date: Tue, 26 Jan 1993 16:48:11 GMT

In article <1993Jan19.181908.11534@wefunk.rent.com> ludwig@wefunk.rent.com writes:
>
>	Ok, this is getty crazy.  First off, I've got my system
>configured so that I can poll other systems.  I connect fine at
>anywhere from 1200 to 38400 baud.  Now, I'd like to set up the
>uugetty.
>
>	So, I set up uugetty, and it seems to work fine.  When I call
>my Linux box, the lock files get created and all, and everything is
>cool.  My problem is, I can't get my modem to pick up and work
>right...
>
>	So, is there anyone who is successfully using a v.32 modem
>(I'm sure there are) that would be kind enough to send me a copy of
>their gettytab, their /etc/default/uugetty.ttys1, and their
>/etc/inittab? (BTW - using gettyps204...)
>

here is my uugetty.ttyS11 file...it runs for a Worldblazer with uugetty
locked at 38400:
#####################################################################
#  This is a high speed modem line
ISSUE=/etc/issue
HANGUP=NO
TIMEOUT=70
#  NOTE:  be sure to have trailing \r\n on the INIT sequence
#	  in fact, all the \r\n's appear to be necessary !
INIT="" A\pA\pA\pAT\r OK\r\n-ATZ\r-OK\r\n ATZ\r OK\r\n
WAITFOR=RING

#DELAY=2

#  The modem's speed is locked, so we don't autobaud

CONNECT="" ATA\r CONNECT
#####################################################################


On the modem, I have Echo off (E0) and Result Codes on (Q0).

My inittab file entry is:
##############################################
t4:6:respawn:/bin/uugetty.new ttyS11 38400
##############################################

	where uugetty.new is from the gettyps_204 package.

And, finally, my gettydefs is:
##################################################################################
38400# B38400 CS8 # B38400 SANE CRTSCTS -ISTRIP -CLOCAL HUPCL ECHO #login: #38400
##################################################################################

Now, while looking at this, it is substantially smaller then I've seen entries
in other gettydefs files...is there something that I may want to add to this?
Or is it fine as it is?

Hope this helps...

marc
-- 
Marc G. Fournier      | R-node Public Access Unix running Linux 0.99p4
Etobicoke, Ontario    | 416-249-5366   24hrs 7 days/week   network email
voice: 249-4230       | shell accounts       1600+ newsgroups       FREE
marc@r-node.pci.on.ca | Telebit WorldBlazer/SupraModem2400/Cardinal 2400
From: s_titz@ira.uka.de (Olaf Titz)
Newsgroups: comp.os.linux
Subject: How does chown() work, rsp. does it work at all?
Date: 27 Jan 1993 16:36:31 GMT
Organization: Fachschaft math/inf, Uni Karlsruhe, FRG
NNTP-Posting-Host: irau30.ira.uka.de
Summary: at1.1 pukes at my box only :-(
Keywords: chown()

I have a strange problem. I tried to install at1.1 and it gives me as
non-root the message "cant give away file". The manpage says that the
chown() function may be used (BSDish) only by root. I have asked
Thomas and he said that 
- chown() works for non-root SysV-style, and 
- at runs perfectly at his box and he knows of others.
Any clues? I'm running the 99.2 kernel on a minix-fs.

Olaf


-- 
| Olaf Titz - comp.sc.student  |   o     | uknf@dkauni2.bitnet | old address |
| univ. of karlsruhe - germany |  _>\ _  | s_titz@ira.uka.de   | is still    |
| +49-721-60439                | (_)<(_) | praetorius@irc      | valid       |
  "My heart is human - my blood is boiling - my brain IBM" - Mr. Roboto