
  Linux/m68k Frequently Asked Questions
  Chris Lawrence, quango@themall.net
  Version 2.0.4, 24 January 1997

  This is the Frequently Asked Questions file for the port of the Linux
  operating system to Motorola 680x0-based systems.  This is version
  2.0.4 of this FAQ, which corresponds with Linux/m68k versions 2.0.28
  (stable) and 2.1.21 (developmental).
  ______________________________________________________________________

  Table of Contents:

  1.	Introduction

  1.1.	About this FAQ

  1.2.	Where to get the latest version of this FAQ

  1.2.1.  FAQ Numbering System

  1.2.2.  Linux/m68k Versions Covered

  2.	A Brief History of Linux and Linux/m68k

  2.1.	In Their Own Words

  3.	Requirements to run Linux/m68k

  3.1.	Processor

  3.2.	RAM

  3.3.	Hard Disk

  3.4.	Software

  4.	Similarities and differences between Amiga and Atari
  Linux/m68k

  4.1.	Similarities

  4.2.	Differences

  5.	The current status of Linux/m68k

  5.1.	General

  5.2.	Amiga

  5.3.	Atari

  5.4.	VME

  5.4.1.  Motorola MVME166 and MVME167 boards

  5.4.2.  Motorola MVME162 board

  5.4.3.  Motorola MVME147 board

  5.5.	Unsupported

  5.6.	Other processors

  6.	Installing Linux/m68k

  7.	Sources for information, sources and binaries

  7.1.	Installation Guides

  7.2.	Other Documents

  7.3.	Newsgroups

  7.4.	Mailing Lists

  7.5.	WWW sites

  7.6.	FTP sites

  7.7.	Modem

  7.7.1.  Germany

  7.8.	Distributions

  7.9.	IRC (Internet Relay Chat)

  8.	Activities

  8.1.	Coordinator

  8.2.	Bug reports/Known bugs

  8.2.1.  TT-FPU bug

  8.2.2.  Amiga with GVP 16-bit RAM

  8.2.3.  Zorro II DMA Bug on A3640 rev 3.0

  8.3.	Under construction/To do

  8.3.1.  General

  8.3.2.  Amiga

  8.3.3.  Atari

  8.3.4.  Other Systems

  8.3.4.1.	Apple Macintosh

  8.3.4.2.	Hewlett-Packard/Apollo Domain Workstations

  8.3.4.3.	Sun 3 Workstations

  8.3.4.4.	NeXT, HP 9000/300, etc.

  9.	Common problems

  9.1.	I can't find the man page for XXX

  9.2.	How can I access my SCSI tape drive?

  9.3.	Where did all my Amiga's chip memory go?

  9.4.	How do I access Linux partitions from AmigaOS?

  9.5.	My SCSI bus locks up when I want to use my DAT drive

  9.6.	My SCSI bus locks up when the kernel probes for devices

  9.7.	I displayed a binary file, and now my console is totally
  screwed up

  9.8.	Can I use both ELF and a.out libraries/binaries in my system?

  9.9.	After installing a patch, the new files are in the current
  directory

  9.10.	I can't mount MS-DOS diskettes on my Amiga

  9.11.	Less behaves weird when I press a key

  9.12.	What are the current major/minor device numbers for /dev/xxx?

  9.13.	How can I tell an a.out binary from an ELF one?

  9.14.	GCC complains that it can't find shared libs while linking

  9.15.	Linux recognizes my Amiga's XXX board, but it doesn't work

  9.16.	I can't use ttyS3 and ttyS4 simultaneously on my Atari

  9.17.	Amiboot dies when I start it with VMM running

  9.18.	How do I byte-swap an ext2 filesystem?

  9.19.	My kernel hangs at the login prompt

  9.20.	I just upgraded to 2.1.21 (or later) and modules don't work

  9.21.	Where can I get Linux/m68k on CD-ROM?

  9.22.	How do I patch my kernel?

  9.23.	How do I choose what video mode to use with Linux?

  9.24.	How can I get my Jaz drive to work with Linux (or another
  OS...)?

  10.	Famous last words

  10.1.	Copyright and License
  ______________________________________________________________________

  1.  Introduction

  This is an updated version of the Linux/m68k Frequently Asked
  Questions file (or FAQ). Since it probably contains errors
  (typographical and logical), outdated and missing information, and
  other significant problems, I ask that you send feedback and
  corrections to me.

  This document is not intended to describe what Linux or Unix is or how
  to administrate it. To find out more about that read the standard
  Linux books and manuals.  I particularly recommend Matt Welsh's "Linux
  Installation and Getting Started" published by the LDP and available
  in print from SSC <http://www.ssc.com/> (or its commercial
  counterpart, "Running Linux, Second Edition" available from O'Reilly
  and Associates <http://www.ora.com/>).

  For questions about Linux in general, I recommend that you read the
  Linux INFO-SHEET.  This document, along with many others about Linux,
  is available at the Linux Documentation Project's home page
  <http://sunsite.unc.edu/LDP/>.

  1.1.	About this FAQ

  This FAQ was originally maintained by Joerg Mayer
  <jmayer@informatik.uni-kl.de>.  It is now maintained by Chris Lawrence
  <quango@themall.net>.

  If you have a link to a previous version (1.x) of the FAQ, please
  change it to the new location as listed below.

  1.2.	Where to get the latest version of this FAQ

  This FAQ is posted every two weeks to the Usenet newsgroups
  comp.os.linux.m68k, comp.os.linux.answers, comp.unix.amiga, and
  maus.os.linux68k.  (Please let me know if an appropriate group has
  been left out.)

  The latest revision is available in HTML format, suitable for reading
  with a World Wide Web browser (such as Netscape, Lynx, Arena, etc.),
  at  <http://www.clark.net/pub/lawrencc/linux/faq/>.  It is also
  available in plain text format at all major Linux/m68k FTP sites.

  SGML source for this FAQ, as well as PostScript, DVI and LaTeX
  conversions, are available from the maintainer.

  1.2.1.  FAQ Numbering System

  From now on, the first two parts of the version number of this FAQ
  will follow the mainstream kernel version number (i.e. when 2.2 is
  released, the next FAQ will be version 2.2.0).  This has the side
  effect of skipping versions 2.1.x, 2.3.x, etc.  The third portion of
  the version number is incremented every time this FAQ is revised.

  1.2.2.  Linux/m68k Versions Covered

  This FAQ documents the 2.0 series of kernels.	If you are currently
  using a 1.2 series kernel, I recommend that you read the Linux/m68k
  2.0 announcement
  <http://www.clark.net/pub/lawrencc/linux/announce-2.html> (and all the
  documents it says to read) and then upgrade to a 2.0 kernel.	The 0.x
  and 1.2 series of kernels are pretty much obsolete.

  Most things said about 2.0 kernels apply also to the 2.1 development
  series, unless otherwise noted.  I strongly recommend against trying
  to use the 2.1 kernels until you are accustomed to using Linux.  On
  the other hand if you like kernel hacking, join the 2.1 party.

  The latest versions of the kernel and boot loaders:

  o  Linux/i386 kernel:

  o  Old stable: 1.0.9, 1.2.13

  o  Current stable: 2.0.28

  o  Experimental: 2.1.23

  o  "Official" Linux/m68k kernel:

  o  Old stable: 0.9.13 and 1.2.13pl10

  o  Current stable: 2.0.28

  o  Experimental: 2.1.21

  o  Amiboot (AmigaOS bootstrap): 5.2

  o  Ataboot (Atari bootstrap): ?

  o  Amiga LILO (low-level bootstrap): 2.1

  2.  A Brief History of Linux and Linux/m68k

  Linux is a freely available operating system for PCs: to be more
  precise, it is one of many flavors of Unix. Linux is being developed
  on the Internet by several thousand people, first and foremost by
  Linus Torvalds <torvalds@cs.helsinki.fi>, and is being tested and used
  by many more (the total is thought to be in the hundreds of thousands,
  perhaps millions).

  The fun and success of Linux inspired Hamish Macdonald
  <hamish@border.ocunix.on.ca> and Greg Harp to port it to another
  platform: the Amiga. The first version released to the general public
  was 005. While 008 was current, a few enthusiasts ported that version
  to the Atari and the two versions have been successfully merged with
  0.9pl3 (this reads version 0.9 patchlevel 3). Linux/m68k can be
  regarded as being of production quality. This means that almost
  everything works as intended without problems.

  After releasing 1.2.13pl3, Hamish handed the coordination over to
  Roman Hodek <rnhodek@informatik.uni-erlangen.de>.  Starting with
  Hamish's unfinished 1.3.20 port, Jes Degn Soerensen <jds@kom.auc.dk>
  started to work on integrating the m68k stuff into 1.3. With 1.3.94
  the majority of the m68k stuff was put into the official kernel tree.

  2.1.	In Their Own Words

  Here's the story about the beginning in Hamish's words:

       I decided to port Linux to my Amiga for a variety of rea-
       sons.  I have always had an interest in operating systems
       (my work is in embedded systems for telecommunications).
       After finishing my Master's thesis, I needed some project to
       keep me busy, and justify keeping my Amiga.  Linux was just
       getting popular at the time, and I thought it would be fun
       to port it to my Amiga.	So I did.  Greg Harp and a few oth-
       ers had been talking for a while about porting Linux to the
       Amiga.  They'd only got a little way into it when I got
       involved, bringing the work I'd already done myself....

  And here about the port to the Atari in Roman's words:

       I'm an old Atari user, but in some dark age of Atari, I also
       bought a PC... running only Linux, of course! Some time
       later, I noticed that there was a Linux for m68k (was a ver-
       sion about 0.06 or so), but learned that it was for Amiga
       only. Already at that time, I thought that it can't be that
       hard to port this to the Atari, but after some browsing in
  the sources, I gave up. I just didn't find a point where to
  start. But at least I subscribed to the MausNet newsgroup
  "LINUX68K". Several months later, in April '94, Bjoern
  Brauel posted an article there, that he has adapted Linux's
  head.S so it ran on his Falcon (until the first console out-
  put :-). I again was interested and asked Bjoern for the
  sources. In the next time, we two built some very basic
  driver, so we could at least see some output on the screen,
  and the kernel booted until the "unable to mount root".
  There was no HD driver yet... So I started to write a SCSI
  driver, and Bjoern went to IDE.

       At that time, we heard that there was another group working
       on an Atari port. The most important members of this group
       were Robert de Vries and Andreas Schwab. They've never
       announced that they're working or how far they are, so we
       didn't know about them. And we communicated over the Maus-
       Net, not the Internet, so they didn't notice us... So we
       finally had two versions of an Atari port at the same time.
       Fortunately, we've mostly worked on different parts, so the
       merged version 0.01pl3 made a big jump in respect to what
       drivers were available.

       The next story is about Martin Schaller: He also ported
       Linux to the Atari, starting directly from PC Linux, not
       from the Amiga version.	(He didn't have a modem at that
       time, so no Internet, not even MausNet...) For that he
       worked totally on his own, he came very far and did a great
       job. In fall 1994, a German Atari magazine published an
       article about Linux/m68k. By this Martin heard that there
       were some more Atari Linux hackers and joined us.

  3.  Requirements to run Linux/m68k

  3.1.	Processor

  You need a Motorola 680x0 processor with a programmable memory
  management unit (PMMU). There is no way to run it without one. This
  reduces the list of possible processors to 68020+68851, 68030, 68040,
  68LC040, 68060. All of these processors are supported as of
  1.2.13pl10. This list of processors excludes the 68000, 68010,
  68EC020, 68EC030, 68EC040.  Linux/m68k can never run on these
  processors as they lack a PMMU and an interface for an external one
  (this is true for all machines but some pretty old Suns :-).

  The following Amigas have the "right" processor built-in: A3000,
  A3000T, A4000/040 (not the A4000/030, which has a 68EC030 processor)
  and A2500. There has been a report that the last A4000/40s produced by
  Commodore were shipped with 68LC040's. In that case, you will need a
  kernel with FPU emulation compiled in.

  The following Ataris (or clones) have the "right" processor built-in:
  Atari Falcon, Atari Falcon with Afterburner 040, Atari TT, and Medusa.
  The standard Falcon does not have an FPU built in. In this case you
  will need a kernel with FPU emulation compiled in. Any processor
  upgrade card with a 68040 or 68030 (like PAK/3 with or without 68881
  or 68882) is able to run Linux.

  Notes:

  1. In some of the older TTs there is a bug in the PAL controlling the
     access to the FPU. This may cause a crash (see ``Known Bugs'').

  2. On the Amiga, there exists a program called "lawbreaker" (part of
     the Enforcer package). This program allows you to check whether you
     have a working PMMU or not (it needs to generate 5 hits in
     combination with enforcer where the last one is an alert).

  3. The FPU emulation does not yet support all transcendent functions
     and not all supported functions have full precision implemented.

  4. The standard 2.0.28 kernel which can be found via FTP will not work
     with FPU emulation (FPU emulation is not distributed in the main
     kernel due to copyright concerns).

  3.2.	RAM

  It is possible (but very difficult) to boot Linux/m68k with as little
  as 2 MB. Now you know that the kernel works on your system: that's it.
  If you want to work with it you should have at least 4 MB (8 MB with
  an X-server).

  Notes:

  o  On the Amiga only the size of your Fast RAM is relevant, i.e. the
     Chip RAM is only used internally for graphics, sound and floppy
     data; it is not used by normal programs.

  o  If you have an Amiga with 16-bit expansion RAM on a GVP card, see
     the ``16-bit RAM'' section.

  3.3.	Hard Disk

  If you want to do more than just boot Linux/m68k you will need 60 MB
  or more of free space on your hard disk and a supported hard disk
  controller.  Add another 20 MB to the base requirements for X.

  3.4.	Software

  Amiga: In order to run amiboot you need AmigaOS 2.0 or higher
  (expansion.library V36+).

  Amiga: amiboot works with SetPatch and RsrvMem (part of Emplant)
  running.  you can start amiboot with VMM running (see ``Known Bugs''
  for how to do this).

  4.  Similarities and differences between Amiga and Atari Linux/m68k

  4.1.	Similarities

  All code that depends only on the processor (i.e. paging, system
  calls, parts of the interrupt handling and of course those parts of
  Linux that were hand optimized by writing the code in assembler) has
  to be ported to Linux/m68k only once. This means that, with enough
  memory, the Amiga and the Atari may use the same kernel image.
  Another big bonus is that all user programs (= binaries) should work
  on any machine running Linux/m68k no matter whether the machine is an
  Amiga, Atari or VME system (or any future platform) as long as no
  machine-specific devices are used (see below).

  4.2.	Differences

  All code that depends on the hardware is machine dependent and with
  very few exceptions which are in the kernel (timer, a small part of
  interrupt handling, startup code) has been put into modules called
  device drivers.  Writing device drivers makes up most of the porting
  work.

  5.  The current status of Linux/m68k

  5.1.	General

  What has been done? The kernel (this means all the processor, MMU and
  FPU specific stuff) has been ported. Version 2.0 is based directly on
  Linux/i386 2.0.

  Several hardware-independent drivers have been ported: Ram disk,
  memory, pty, tty, vt, (C)SLIP, PPP, multi-disk (MD), networking, and
  general SCSI and IDE stuff.

  Also the following filesystems have been done: minix, ext2, msdos
  (including umsdos and Win95 VFAT), proc, isofs, affs, nfs, and ufs
  (affs = Amiga file system).  Both Amiga and MS-DOS partitions can be
  used.

  Starting with the 1.05 release of e2fsprogs, new filesystems are
  created using the common ext2 format (as used by Linux/i386).
  Filesystems compatible with kernel 1.2.13pl4 and later can be used in
  Linux/m68k 2.0, but before upgrading to 2.2 it will be necessary to
  byteswap your filesystem (see ``How To Byteswap Your Filesystems'') to
  put it into the common format.  The common format can be read from and
  written to by Linux on all processors, as well as the GNU Hurd.

  An X server exists that uses the frame buffer device. Frame buffer
  devices exist for both native Amiga and Atari graphics in the kernel.
  The list of supported hardware should be exhaustive, i.e. if it isn't
  in here or in ``Work In Progess'' it isn't supported at all.	If you
  find omissions, please report them.

  5.2.	Amiga

  Supported built-in hardware:

  A3000 SCSI, A4000 IDE, A1200 IDE, serial port, parallel port, mouse,
  keyboard, built-in graphics (OCS, ECS and AGA), timer, floppy disk
  drive (DD/HD, Amiga and PC formatted disks), sound, and real-time
  clock of A2000, A3000 and A4000.

  All RAM expansions are supported (but see notes on ``16 bit RAM
  expansions'').

  Supported SCSI cards: A2091, A590, GVP Series II (including HC+8,
  A4008), Phase5 Cyberstorm and Cyberstorm II SCSI options, Phase5
  Blizzard 1230IV/1260 SCSI options, Phase5 Blizzard 2060 68060+SCSI
  card and Phase5 Fastlane Z3 SCSI card.  If you have an A4000/040, see
  the section about the ``A3640 Zorro II Bug''.

  Supported Ethernet cards: Ariadne, Hydra, A2065

  Supported IO cards: BSC Alfa Data MultiFaceCard III, GVP IO-Extender.

  Supported graphics cards: Phase5 Cybervision64 (probably Cybervision64
  3D too).

  5.3.	Atari

  SCSI, ACSI, Falcon IDE, all built-in serial ports, keyboard, Atari
  mouse, parallel printer port, RTC clock, floppy disk (DD/HD/ED),
  built-in Atari graphics (ST/TT/Falcon/Medusa), beep (all) and sound
  (Falcon/TT) are supported. The ET4000 and the Mach64 cards used in the
  Medusa are partially supported (you can't change the resolution).

  Linux's Minix FS is compatible with the Minix V2 FS used with MiNT.

  Supported RAM cards: FX-card (Falcon), Magnum (Falcon)

  Supported Ethernet cards: RieblCard, PAM's VME boards (most Lance-
  based Ethernet cards should work)

  Screen extenders: Screenblaster, Onscreen work, others should work
  too.

  Other peripherals: Atari Laser Printer

  5.4.	VME

  5.4.1.  Motorola MVME166 and MVME167 boards

  (provided by Richard Hirst <srh@gpt.co.uk>)

  There are multiple VME boards out there on which Linux/m68k could run.
  There is currently one port for the Motorola MVME166 and MVME167
  boards.  These are complete systems on a card, so there's no need to
  support any external controller cards:

  o  68040 at 25 or 33MHz (at least)

  o  4 to 32MB DRAM (maybe more)

  o  CD2401 four channel serial controller

  o  NCR53C710 SCSI controller

  o  Parallel port (currently unsupported)

  o  Intel 82596CA Ethernet controller (under construction)

  o  VMEchip2 VME interface chip

  o  PCCchip2 local controller chip

  o  VSBchip2 (MVME166 only)

  o  MK48T08 BBRAM and TOD clock

  o  68230 PIT

  The source is based on 2.0.8 at present.  The system will happily loop
  building the kernel for hours on end with no problems (no '040 MMU bug
  here!)  It takes about 20 minutes to build a kernel.

  More information can be found at Richard's VMEbus port page
  <http://www.sleepie.demon.co.uk/mvme166.html>.

  5.4.2.  Motorola MVME162 board

  A port to the MVME162 board has been made by Vaughn Skinner
  <vaughn@solid.net>.  It is based on Richard Hirst's port.

  5.4.3.  Motorola MVME147 board

  A port to the MVME147 board has been started by Dave Frascone
  <chaos@mindspring.com>.  It is currently in alpha testing.

  5.5.	Unsupported

  There is currently no Linux/m68k port for several 680x0 based
  computers that would be able to run Linux. The reason for this is
  rather simple: Nobody has written it. The reasons for that are many:
  The people who already have most/all of the knowledge on the Linux
  side of the port are usually busy maintaining/improving one of the
  existing ports. Another quite common reason is that no or only
  insufficient documentation on the hardware of that platform exists.
  Sun 3s are an even more special case: Unlike all other machines
  mentioned here, they don't use Motorola MMUs (except the Sun 3/80,
  which has an 68030).

  Here is a (probably incomplete) list of the currently unsupported
  machines with 680x0 processor:

  HP Apollos, HP 9000/300 series, Macintoshes, Sun 3s, NeXTs and most
  VME bus machines.  See the ``Other Systems'' section of this FAQ for
  details on progress toward completing these ports.

  As far as I know, you can run NetBSD <http://www.netbsd.org/> on most
  Sun 3s and Macs with 680x0 processors (see the NetBSD FAQ).

  5.6.	Other processors

  Linux also runs on several other platforms in varying states of
  usability:

  o  Alpha (Linux/AXP):	<http://www.azstarnet.com/~axplinux/>

  o  PowerPC processors (Linux/PPC):  <http://www.linuxppc.org/>

  o  PowerMacs using OSF Mach microkernel:
     <http://www.mklinux.apple.com/>

  o  Sparc processors (SparcLinux):
     <http://www.geog.ubc.ca/sparclinux.html>

  o  I think I heard some rumors about an Intel version too ;-)

  This list is not exhaustive: More complete and more current versions
  of these infos can be found at the Linux Mailing List Archives
  <http://www.linux.ncm.com/>.

  6.  Installing Linux/m68k

  Get one of the ``installation guides'' available and follow the
  procedures.  You shouldn't have any problems, just bear in mind that
  many of them were written for 1.2 and some of the filenames have
  changed.

  When you're done, register yourself at the Linux/m68k Registration
  Site <http://www.cs.kuleuven.ac.be/~geert/Linux/m68k/>.

  7.  Sources for information, sources and binaries

  7.1.	Installation Guides

  An installation guide for the Amiga is available at
  <http://www.informatik.uni-oldenburg.de/~amigo/inst.html>. It is also
  available in various formats from  <ftp://ftp.informatik.uni-
  oldenburg.de/pub/amiga/linux/local/docs/>.  Although the guide was
  written for the Amiga, many things are also useful for Atari users.

  An Atari-specific install guide can be found at
  <http://www.gti.net/azog/linux68k.txt>; another one can be found at
  <http://zippy.spods.dcs.kcl.ac.uk/~tomlin/flinux.html>.

  7.2.	Other Documents

  Further documents can be found in at
  <ftp://tsx-11.mit.edu/pub/linux/docs/> and
  <http://sunsite.unc.edu/LDP/>. These documents were originally written
  for Linux/i386, but many are useful for Linux/m68k users too (e.g.
  HOWTOs on UUCP, PPP and the general Linux FAQ).

  A FAQ on Motorola chips (including the 680x0 microprocessors) is
  available at	<http://www.oise.on.ca/~rboys/m68kfaq.html>.

  Last but not least: Look into the Documentation directory of the
  kernel tree.

  7.3.	Newsgroups

     comp.os.linux.m68k
	The group comp.os.linux.m68k is intended to further interest in,
	and development of, the port of the Linux operating system to
	the 680x0 architecture. All discussion in the newsgroup should
	be in English.

     comp.os.linux.development.system
	This group is on Linux kernel development only. From time to
	time it contains messages dealing with the Linux/m68k kernel.

     comp.os.linux.announce
	This group announces new Linux-related products. Announcements
	for new versions of Linux/m68k may be found there.

     maus.os.linux68k
	This group deals with Linux/m68k only. The languages currently
	used are German and English.  This newsgroup is also available
	via FidoNet (LINUX-68K.GER).

     comp.unix.amiga
	This group is for discussions on Amiga Unix, NetBSD and
	Linux/m68k on the Amiga.

     de.comp.sys.amiga.unix
	Similar to comp.unix.amiga, but in German.

  7.4.	Mailing Lists

  I am aware of one mailing list for Linux/m68k, which is named linux-
  m68k.	As there is a newsgroup for Linux/m68k, topics on this list
  should be restricted to development issues if possible.

  (provided by Benjamin Lorenz <benni@phil.uni-sb.de>)

  You can subscribe to linux-m68k@phil.uni-sb.de by sending a mail to
  majordomo@phil.uni-sb.de, with a random subject and a single line in
  the mail body containing "subscribe linux-m68k". You may want to
  subscribe to linux-m68k-digest@phil.uni-sb.de instead: in this case,
  you will receive one mail per day containing all mails to the list
  from the last 24 hours. If you prefer to read mail in this way, please
  unsubscribe from linux-m68k to reduce net load!

  You can download archives from the digest mails! They are stored at
  <ftp://ftp.phil.uni-sb.de/pub/linux-m68k/mailinglist>.

  Another mailing list archive that supports searching can be found at
  <http://aire.ncl.ac.uk/Atari/Mailing-Lists/Linux-m68k-phil-
  List.index.html>.

  7.5.	WWW sites

  o  The Linux/m68k Home Pages:
     <http://www.clark.net/pub/lawrencc/linux/>

  o  Linux/m68k Registration Site:
     <http://www.cs.kuleuven.ac.be/~geert/Linux/m68k/>

  o  Helmut Neukirchen's Linux/m68k WWW page (no longer maintained):
     <http://www-users.informatik.rwth-aachen.de/~hn/linux68k.html>

  o  Dirk Wetter's Linux/m68k WWW page:	<http://bunsen.pci.uni-
     hannover.de/linux68k.html>

  7.6.	FTP sites

  o  The Linux/m68k server:  <ftp://ftp.uni-
     erlangen.de/pub/Linux/LOCAL/680x0/>.  Mirrors include (please use
     the one nearest to you, most of these mirrors are updated daily):

  o  <ftp://tsx-11.mit.edu/pub/linux/680x0/>

  o  <ftp://ftp.funet.fi/pub/Linux/BETA/680x0/>

  o  <ftp://ftp.tu-clausthal.de/pub/systems/Linux/680x0/>

  o  <ftp://ftp.informatik.tu-muenchen.de/pub/comp/os/linux/680x0/>

  o  <ftp://ftp.informatik.uni-oldenburg.de/pub/linux/680x0/>

  o  <ftp://ftp.twi.tudelft.nl/pub/Linux/680x0/>

  o  <ftp://ftp.germany.eu.net/pub/os/Linux/Mirror.SunSITE/>

  o  <ftp://ftp.fu-berlin.de/pub/atari/linux/>

  o  <ftp://src.doc.ic.ac.uk/computing/operating-
     systems/Linux/tsx-11-mirror/680x0/>

  o  <ftp://ftp.spc.uchicago.edu/pub/linux/680x0/>

  o  <ftp://ftp.nvg.unit.no/pub/linux/680x0/>

  o  <ftp://ftp.phil.uni-sb.de/pub/linux-m68k/mirror.erlangen/>

  o  <ftp://ftp.unina.it/pub/linux/linux68k/>

  o  <ftp://ftp.belnet.be/packages/Linux-680x0/>

  o  Please tell me if your favorite mirror is not on this list.

  o  The kernel source for Linux/m68k can be found in 680x0/v2.0/ and
     680x0/v2.1/, a lot of binaries in 680x0/bin/. A few more tools
     reside in 680x0/tools/.

  o  The two Linux servers (sources for you to port to/compile on
     Linux/m68k):

  o  <ftp://tsx-11.mit.edu/pub/linux/sources/>

  o  <ftp://sunsite.unc.edu/pub/Linux/system/>

  o  Linux on Amiga:  <ftp://ftp.informatik.uni-
     oldenburg.de/pub/amiga/linux/local/>

  o  Various stuff:  <ftp://ftp.phil.uni-sb.de/pub/linux-m68k/>

  o  FPU emulation is available from
     <ftp://ftp.nocrew.pp.se/pub/linux/>

  The following addresses are known to offer FTP via e-mail:

  o  ftpmail@info2.rus.uni-stuttgart.de <mailto:ftpmail@info2.rus.uni-
     stuttgart.de>

  o  ftpmail@ftp.inf.tu-dresden.de <mailto:ftpmail@ftp.inf.tu-
     dresden.de>

  o  ftpmail@informatik.uni-oldenburg.de <mailto:ftpmail@informatik.uni-
     oldenburg.de>

  To get more info on FTP-mail send a mail with subject "help" to one of
  the addresses mentioned above.

  7.7.	Modem

  If you have a modem, you can get Linux/m68k from the following
  addresses:

  7.7.1.  Germany

       System name: nasim
       Phone: +49 89 5469593, ZyX19200
       Login: Anon-uucp: nuucp - no password / ZModem: gast - no password
       Contents: full 680x0-tree of tsx-11 in /pub/linux-68k
       Get first: index file /pub/linux-68k/ls-lR.nasim.linux-68k.gz
       Other features: provides uucp access to 680X0 channel (read only) and
       the linux.act.* news-groups
       Admin: Frank Bartels <knarf@nasim.cube.net>

  7.8.	Distributions

  There are no distributions available via FTP at the moment.  ALD (=
  Autoren Linux68K Distribution) for Atari is available from Whiteline.

  7.9.	IRC (Internet Relay Chat)

  An IRC channel for Linux/m68k exists, called #Linux68k. Start irc and
  select one of the servers of LinuxNET, such as irc.blackdown.org. A
  list of servers can be found at
  <http://www.blackdown.org/LinuxNET/LinuxNET.html>. Just do a

       /join #Linux68k

  and look out for others. If nobody is there, there is a simple reason
  for this: you are the first to join this channel (actually, the first
  one to join a channel creates this channel). There already is a well
  established #Linux.

  Note: The attempt to establish a channel #Linux68k via the "regular"
  IRC servers more or less failed because of many, many net splits.
  LinuxNET is much more reliable.

  8.  Activities

  8.1.	Coordinator

  Linux/m68k releases are built and released by Jes Degn Soerensen.
  "Built" means that you can write a patch against the current version
  or patchlevel and send it to them or the mailing list and they will
  integrate it into one of the next releases. Make sure you state
  against which version the patch was made. Please note that Jes has no
  way to test Atari-specific patches.

  Note: If you patch processor-specific code (e.g. 68030 vs. 68040 MMU
  or FPU) make sure that you document the dependencies.

  8.2.	Bug reports/Known bugs

  Send bug reports to the author of the code or to Jes. Probably a
  better approach is to post it to the linux-m68k mailing list or to the
  appropriate newsgroup.  If there are bugs that will probably stay in
  the code for an extended period of time let me know so I may publish
  them here.

  8.2.1.  TT-FPU bug

  Problem:

  Linux reports *** COPROCESSOR PROTOCOL VIOLATION *** FORMAT=9 or
  something similar.

  Fix:

  Pull the 16L8 PAL's pin 11 free (this is the signal 'XBG') and solder
  it to +5V. This prevents the PAL from tri-stating AS and DS until
  XBGACK has gone low.

  To make your 32 MHz daughter-card work:

  1. Pull pin 11 of the 16L8 PAL out of the board

  2. Solder pin 11 of the IC to +5V (pin 20 of 16L8)

  ****This applies to the CA400771 32 MHz daughter board****
  **********Other boards should not have this bug***********
  _______________________________________________________________
  Atari 32 Meg Daughter Board / PGA				|
								|
				     ___________________	|
				     |		 |	|
				     |		 |	|
				     2 1 1 1 1 1 1 1 1 1	|
				     0 9 8 7 6 5 4 3 2 1	|
      . . . . . . . . . .	    . . . . . . . . . .	|
	 PAL 16R4-7PC			PAL 16L8-7PC		|
      . . . . . . . . . .	    . . . . . . . . . .	|
				     1 2 3 4 5 6 7 8 9 1	|
						       0	|
	CA400771						|
     ___________________________________________________________|
     |
     |
  ___|

  8.2.2.  Amiga with GVP 16-bit RAM

  Problem:

  When using a GVP card with 16 bit RAM on an Amiga with 68040
  Linux/m68k dies.

  Fix:

  Unfortunately, there is no known solution to that problem. So your
  best bet is to get some real 32 bit RAM. The 16-bit RAM may still be
  used as a ramdisk using the z2ram device, but you must disable it as
  normal RAM (-m option of amiboot).

  Quoting from the README for amiboot:

  If you have some non-AutoConfig memory you want to use under Linux, or if you
  want to disable some parts of your memory (e.g. Zorro II RAM on '040 based
  systems), you have to use a memory file and the --memfile option. This file
  contains information about the memory chunks you want to use under Linux. The
  format for the file is:

      chipramsize
      [0xfastchunkaddr fastchunksize]
      [0xfastchunkaddr fastchunksize]
      ...

  For example, if you don't want Linux to use your 2nd meg of chipram, you would
  create a file that looks contains only:

      1048576

  If you had 1M of chip ram, 2M of 16 bit FAST ram at address 0x200000 and 16M of
  32 bit FAST ram at address 0x80000000, and you didn't want Linux to use the
  slow 16 bit FAST ram, you'd create a file that looks like:

      1048576
      0x80000000 16777216

  The memory file can also be used to specify in which block of memory the kernel
  will be put. Normally Amiboot will put the kernel in the first block of Fast
  RAM it will find. If you use a memory file, it will put the kernel in the first
  block of fast RAM you specify.

  8.2.3.  Zorro II DMA Bug on A3640 rev 3.0

  Problem:

  You get strange system crashes and segmentation faults with a SCSI
  controller and an Amiga 3000 or 4000 with a Commodore A3640 revision
  3.0.

  Fix:

  The immediate fix is to make your SCSI controller stop using DMA.  Add
  the kernel parameter wd33c93=nodma:1 to the boot command you are
  using.

  A better solution is to replace the A3640 with a newer version of the
  card or a third-party card like the Phase5 Cyberstorm, Warp Engine,
  QuikPak 4060T, or Apollo 4060.

  8.3.	Under construction/To do

  I would like a list of projects planned/started, similar to the Linux
  Project-FAQ. If you send me info, I will put them in this section.

  Please note that a lot of these are rather old.  I have marked the
  ones that haven't had any recent activity with ?.

  8.3.1.  General

  o  Creation of a freely available Debian distribution for Linux/m68k.
     Send mail to debian-68k-request@lists.debian.org with the word
     "subscribe" in the message body. Mails should be sent to
     debian-68k@lists.debian.org. Please do not join the list if you are
     not willing/going/able to actually work on the packages. Testers
     are not yet needed (it's too early for that).

  o  ? Integration of VME stuff into main kernel tree.

  8.3.2.  Amiga

  o  Drivers for Arcnet cards are in alpha/beta: Frank Neumann
     <Frank.Neumann@informatik.uni-oldenburg.de>.

  o  ? Support for the Oktagon SCSI controller is planned:
     <kcozens@io.org> and <shermane@ct.picker.com>.

  o  A frame buffer device for the Spectrum, Piccolo, Picasso II and
     SD64 graphics cards is in the works: Frank Neumann
     <Frank.Neumann@informatik.uni-oldenburg.de>.

  o  Support for the A2410 and DMI Resolver graphics boards is planned:
     Topi Kanerva <topi@susanna.oulu.fi> and Jes Degn Soerensen
     <jds@kom.auc.dk>.

  o  Support for the Commodore A2232 7-port serial card is under
     development: Eric van Dijken <E.vanDijken@PTT-Telecom.nl>.

  o  Support for the Commodore A2024 monitor (a high resolution
     grayscale monitor): Frank Eibisch <ergocat@minet.uni-jena.de>.

  The following drivers were asked about but nobody has reported
  interest in writing them (yet):

  o  Concept and code for the use of chip ram and the blitter from user
     space.

  o  Support for Emplant serial and SCSI.

  o  Support for the Commodore/DKB A4091 SCSI card and the A4000T built-
     in SCSI controller (could be based on the NCR53C710 driver for the
     MVME166/167 boards?)

  o  BSC Alfa Data MultiFaceCard II support. Docs available from Joerg
     Dorchain <dorchain@mpi-sb.mpg.de>.

  o  Improved Cybervision support (on the fly mode changes, 16 bpp
     framebuffer support, etc.).

  o  Warp Engine SCSI controller support.

  o  Prodev Merlin graphics card.

  o  Commodore A2090 SCSI controller.

  o  Commodore A2286 Bridgeboard (also other models).

  o  Phase5 PowerPC/68060 cards. (Run Linux/PPC on one CPU and
     Linux/m68k on the other?)

  8.3.3.  Atari

  Currently none?

  8.3.4.  Other Systems

  8.3.4.1.  Apple Macintosh

  Rob Pelkey <rpelkey@bates.edu> is coordinating the Linux/Mac68k
  project, a fresh effort to port Linux/m68k to the Mac.  More
  information on this project is available at the Linux/Mac68k Home Page
  <http://www.bates.edu/~rpelkey/linux-mac68k/>.

  8.3.4.2.  Hewlett-Packard/Apollo Domain Workstations

  The first pre-alpha is now available at
  <ftp://www.ba.be/pub/apollo/>.  It apparently only runs from a
  ramdisk, but it does support the monochrome framebuffer and the
  keyboard.  Contact Peter De Schrijver <p2@linux.cc.kuleuven.ac.be> for
  more details.

  8.3.4.3.  Sun 3 Workstations

  Pekka Pietikaeinen <pp@netppl.fi> is the point of contact for this
  port.	A patch relative to 2.0.25 is available from him.

  8.3.4.4.  NeXT, HP 9000/300, etc.

  As far as I know, there is nobody working on ports to these systems at
  the present time, but there has been some interest from users.

  9.  Common problems

  A lot of these no longer apply to new users, but may be of interest to
  people who have been running Linux/m68k for a while.

  This is by no means an exhaustive list.  If you have any suggestions
  for entries, please send them to me.

  9.1.	I can't find the man page for XXX

  There is a *wealth* of Linux documentation out there for the original
  PC Linux which almost always applies to Linux/m68k. Check out the
  documentation at your favorite Linux FTP site.

  9.2.	How can I access my SCSI tape drive?

  Use /dev/st0. Be aware that your tape drive must be up and running at
  boot time so that Linux can recognize it and you can use it.

  9.3.	Where did all my Amiga's chip memory go?

  It's still there, but the kernel doesn't offer it to the user. It is
  used by drivers that use the custom chips (like floppy, framebuffer,
  and sound).

  9.4.	How do I access Linux partitions from AmigaOS?

  There is an ext2 filesystem for AmigaOS (available at
  <http://titan.cs.bonn.edu/~fasten/>).	It allows you to read/write
  ext2 partitions. Not all write operations are currently (version 0.3)
  supported. Important: Do read the "Known bugs" section.

  Other ways to transfer files from Linux to AmigaOS are to use an msdos
  partition, an Amiga/PC formatted floppy with msdos file system (this
  requires a Mountlist entry on AmigaOS side), use of a partition with
  minix file system and the minix file handler on AmigaOS side (the
  driver is somewhat unstable) or by accessing the floppy / any (empty!)
  partition directly via GNU tar.

  You can also read and write Amiga partitions from within Linux (using
  the affs filesystem).

  9.5.	My SCSI bus locks up when I want to use my DAT drive

  (provided by Frank Neumann)

  This problem seems to be related to certain A3000 Amigas: probably
  only those with BootROMs. It has been discovered that if you have a
  DAT drive connected whose SCSI address is smaller than the smallest
  SCSI address of a hard disk in your Amiga, the bus will lock up very
  early (under AmigaOS, while the SCSI bus is being scanned: you can
  notice this by seeing that the SCSI LED is constantly lit and nothing
  happens).  The solution is to use higher address for DAT drives (and
  maybe also for CD-ROMs) and the lower ones for direct-access media
  (read that as "hard disks").

  9.6.	My SCSI bus locks up when the kernel probes for devices

  (provided by Frank Neumann)

  Some devices dislike being polled on LUNs (logical units) other than
  0. What can happen here is that the SCSI bus just locks up because the
  device does not answer the inquiry. Quite a couple of drives have
  already been added to the blacklist of "bad" devices in the kernel,
  but there are probably more. If you discover this behavior on one of
  your SCSI devices, you might try adding it to the blacklist (in
  drivers/scsi/scsi.c) yourself or ask someone to do it for you if you
  are sure about it.

  If you think you're adventurous and want to fix the kernel for a
  specific SCSI device yourself, here is what you could do:

  Under AmigaOS, use the scsiutil command (on Aminet) and its -i option
  to send an Inquiry command to that particular device. Write down its
  vendor identification, product identification and Product revision
  level.  For instance, an Apple CD-300 CD-ROM drive might give (at the
  bottom) this output:

    Vendor identification: SONY
    Product identification: CD-ROM CDU-8003A
    Product revision level: 1.9a

  Now go into the kernel source tree and (under drivers/scsi/scsi.c) add
  your drive to the blacklist of drives that have problems (just search
  for "blacklist"). Recompile the kernel and try it out without the
  wd33c93= options you probably used so far.

  If it works, you might want to send your change as a GNU context diff
  to one of the Linux/m68k maintainers.

  9.7.	I displayed a binary file, and now my console is totally screwed
  up

  (provided by Frank Neumann)

  Once in a while, it may happen to you that you try to read a binary
  file. Text viewers like more will interpret the input they get as
  control characters, to for instance change to an alternate character
  set. This may result in a strange looking prompt, made up of special
  characters.  In such a case, you need to reset the terminal to its
  initial state.  There are several ways to do this, here's what I use:
  You have to type (blindly):

       echo "^V Esc c"

  Read this as: Control-V, Escape key, character c. The sequence
  "Escape-c" does just what we want: It resets the text attributes and
  character set, and also clears the screen. You have to mask the escape
  character with Control-V, otherwise the shell would directly try to
  use the "Escape" for its purposes. ^V ^O should do the same job.

  You can also avoid this problem by replacing more with less (less
  warns about binary files before displaying them).

  9.8.	Can I use both ELF and a.out libraries/binaries in my system?

  (provided by Frank Neumann)

  No problem.  If you moved to ELF according to Andreas Schwab's hints (
  <ftp://tsx-11.mit.edu/pub/linux/680x0/ELF/README>), you already have a
  mixed system. All old a.out shared libraries, stubs, static libraries
  and simple object files (*.so, *.sa, *.o, *.a) are now in /usr/m68k-
  linuxaout/lib, except for libc and libm which remain in /lib.	The ELF
  shared libraries are in the usual places (/lib, /usr/lib and maybe
  /usr/X11R6/lib and /usr/local/lib) and don't interfere with the a.out
  libraries.

  When starting a program which is either a.out or ELF, the
  corresponding link loader (ld.so and ld-linux.so respectively) will
  determine what shared libraries are required and load them on the fly.
  This of course works for both a.out and ELF binaries.	You only have
  to keep in mind that with a mixed system (using some binaries which
  require ELF libraries while others which require a.out libraries) both
  ELF and a.out libraries have to be kept in memory (in particular, but
  not limited to, libc and libm). This certainly costs valuable memory.
  So, the long-term solution will be a pure ELF installation (libraries
  and binaries).

  You can download the ELF versions of the programs via FTP, download
  sources and recompile, or "Debianize" your system (I really don't
  recommend the latter unless you really know what you are doing).

  If you install from Watchtower-2, you will have the a.out
  compatibility libraries but no a.out binaries.

  Note: Concerning a.out libraries, a couple of people had problems with
  the last libc that was created (4.7.2). So we recommend staying with
  4.6.27 which most people were using.

  9.9.	After installing a patch, the new files are in the current
  directory

  Do a man patch. Understand what the -p option does. In case the rest
  of the patches install ok, add a -p0 to your command options. I
  usually use patch -s -E -p0 < patchfile (s: only report errors, E:
  remove empty files).

  If you are in the linux directory, almost all kernel patches will
  apply with either -p1 (this covers all official Linux patches) or -p0.

  9.10.	I can't mount MS-DOS diskettes on my Amiga

  On the Amiga, the floppy minor numbers are 0-3 for drives 0-3 using
  Amiga formatted disk and 4-7 for drives 4-7 using MSDOS formatted
  disks (drive+4).  Please name them mfd0-mfd3. Just in case you don't
  know how to create the device files: Do a mknod /dev/mfd(0-3) b 2
  (4-7) and please read a book about Linux (even PC :-). Now you can do
  a "mount -t msdos /dev/mfd0 /mnt".  In case this still doesn't work:
  Do a "cat /proc/filesystems" and check whether the kernel was
  configured to support msdos filesystems.

  Alternatively you can use the mtools package. You can find a correctly
  configured and pre-compiled package on tsx-11 in the bin directory.

  9.11.	Less behaves weird when I press a key

  The older versions of the root-filesys have the wrong device numbers
  for /dev/tty. Delete it and do a MAKEDEV std (you do have a somewhat
  current /dev/MAKEDEV, don't you?)

  9.12.	What are the current major/minor device numbers for /dev/xxx?

  The address of the "official" version of MAKEDEV for Linux/i386 can be
  found at sunsite and mirrors in /pub/Linux/system/Admin/MAKEDEV-
  x.y.tar.gz.  A list of the major/minor device numbers can also be
  found in the kernel tree as Documentation/devices.txt.

  9.13.	How can I tell an a.out binary from an ELF one?

  Use the file command. It will either tell you 'mc68020 demand paged'
  if it is an a.out binary, and give a longer (self-explanatory)
  description if it is ELF.

  You can also use ldd.	If it says something about a "DLL jump", the
  binary is in a.out format; otherwise, it's in ELF.

  For statically linked binaries, ldd reports statically linked (ELF)
  for ELF binaries.  I have no idea what it says for a.out binaries,
  because I don't have anything statically linked a.out any more (matter
  of fact, I doubt I have any a.out binaries left at all).

  9.14.	GCC complains that it can't find shared libs while linking

  (provided by Geert Uytterhoeven)

  The current ld requires you to create links from *.so to *.so.6 for
  all libs, so you should have e.g. libX11.so -> libX11.so.6,
  libX11.so.6 -> libX11.so.6.0

  Recent versions of ldconfig seem to take care of this automatically.

  9.15.	Linux recognizes my Amiga's XXX board, but it doesn't work

  Linux/m68k can detect the Amiga's AutoConfig devices. That it is able
  to detect and correctly classify these devices does not mean that the
  kernel has an actual driver for that device. The list of supported
  hardware given earlier should be exhaustive, i.e. anything that is not
  listed is not supported. Note: turbo boards that appear as AutoConfig
  devices are almost always supported (except for the SCSI controller,
  if they house one).

  9.16.	I can't use ttyS3 and ttyS4 simultaneously on my Atari

  This is perfectly normal: ttyS3 and ttyS4 correspond to different
  physical external connectors on the Atari, but these connectors use
  the same internal hardware (Channel A of the SCC).

  9.17.	Amiboot dies when I start it with VMM running

  (provided by Martin Apel)

  What happens is that amiboot gets loaded into virtual memory and
  shoots itself out of accessible memory when disabling the MMU. But
  fortunately there's an easy way to solve this:

  Enter amiboot into the task list of VMM with code and data set to "No
  VM".	Then amiboot (version 3.0 or higher) should work correctly.

  9.18.	How do I byte-swap an ext2 filesystem?

  IMPORTANT: Make sure you are using e2fsprogs-1.06-swapfixed or later!
  The 1.05 and original 1.06 versions of e2fsprogs had serious bugs that
  can corrupt your disks while byte swapping.

  There are three reasons why you'd want to do this:

  1. You want to share some sort of mass storage medium (Jaz or Zip
     disks, hard disks, SyQuest media etc.) between Linux/i386 (or
     another Linux port) and Linux/m68k

  2. You want to use ``the ext2 filesystem for AmigaOS''

  3. You want to use Linux/m68k 2.1.21 or later

  For the purposes of this discussion, "big-endian" refers to the ext2
  filesystem format used by Linux/m68k 1.2.13pl4 and later and "little-
  endian" or "common" refers to the Linux/i386 ext2fs format.

  There are two steps.	First, you must run e2fsck -f on the partition
  to make sure it is completely error-free.  Then use e2fsck -s to do
  the byteswap to the common format.  Note that e2fsck -s will have no
  effect on a common format partition (so it's OK to use it if you're
  not sure).

  You can see whether or not a partition is in the common format by
  running dumpe2fs on it.  A warning message will be displayed if it is
  in the big-endian format.

  Linux/m68k 2.0.28 includes a warning about big-endian format
  filesystems.	Note that Linux/m68k 2.1.21 and later 2.1 series kernels
  can't mount the big-endian format (support for them has been removed).
  You will have to convert your filesystems before upgrading to 2.2,
  when it is released.	(However, it is possible to convert your
  filesystem while running 2.1.21 or later from a ramdisk.)

  9.19.	My kernel hangs at the login prompt

  It is possible that you have an IDE controller on your system without
  any IDE devices attached to it.  If you have been experiencing
  problems like this, you should upgrade to kernel 2.0.28.  If upgrading
  doesn't fix the problem, ask for help in the newsgroup.

  9.20.	I just upgraded to 2.1.21 (or later) and modules don't work

  You need release 970116 or later of modutils for 2.1.21.  Note that
  these modutils are incompatible with kernels from 2.1.0 to 2.1.17, so
  you'll need to keep a copy of modutils-2.1.13 if you plan on switching
  back and forth.  Modutils can be found at
  <ftp://ftp.redhat.com/pub/alphabits/>.

  Make sure you apply the patch in the modutils archive.  You will also
  need to apply Andreas Schwab's 2.1.21 patch, available on the mailing
  list.	Note that some of the patches do overlap.

  Modules in 2.1 series kernels also require running libc 5.4.17 or
  later (which in turn requires ld.so 1.8.5 or later).	Don't run
  anything called libc 6 (aka glibc) unless you're Andreas Schwab (or
  really like life on the bleeding edge).

  9.21.	Where can I get Linux/m68k on CD-ROM?

  (S.u.S.E. info provided by Christian Steigies)

  In the United States and Canada, a good source is the Infomagic Linux
  Developers' Resource CD-ROM set.  The current price is $27.50 US, and
  includes 6 CDs which include mirrors of sunsite.unc.edu and
  tsx-11.mit.edu.  The latter mirror is of interest, since the complete
  680x0 tree from ftp.uni-erlangen.de is included.  The latest edition
  is the December 1996 set, and is updated every 3 months.  More info
  can be found at Infomagic's web site <http://www.infomagic.com/>.

  Specialized System Consultants  <http://www.ssc.com/> shrinkwraps a
  copy of Matt Welsh's "Linux Installation and Getting Started" and the
  LDR CD-ROM set together; this combination package retails for $37.95
  US and is usually available at large "category-killer" bookstores
  (such as Borders, Bookstar, and Barnes and Noble).

  In Europe, S.u.S.E. distributes a 4 CD set called "SuSE Aktuell 4.4".
  The latest edition is also dated December 1996.  In addition to a
  direct mirror of erlangen's 680x0 tree, a mirror of ftp.phil.uni-
  sb.de's linux-m68k tree is included.	Each set is 45 DM, or you can
  get 6 for 209 DM in Germany and 259 DM in "Ausland" (which I'm
  guessing means "outside of Germany" my only foreign language is
  French, sorry). S.u.S.E.'s web site is at  <http://www.suse.de/>
  (German language only).

  If you have already started using the Debian packaging system,
  iConnect Corporation distributes CDs of master.debian.org which are
  updated daily and should include the unstable/binary-m68k tree.  1.3
  snapshot CD's are $25.00 US (plus $5.00 US shipping and handling
  inside the US and $10.00 US elsewhere).  Check out <http://www.i-
  connect.net/> for details.

  9.22.	How do I patch my kernel?

  Once you have a copy of the Linux/m68k kernel, you should rarely need
  to get a completely new tree.	Instead, you can patch the kernel to
  the next released version.

  For example, if you have the 2.0.25 kernel tree already, you need to
  get the file linux-2.0.28.diff.gz via FTP (don't get the file with the
  word "native" in it unless you have the same version kernel tree for
  Linux/i386).	Then use cd to get to the directory above your kernel
  tree (probably /usr/src), and make a copy using hard links to save
  some space:

       cp -rl linux-2.0.25 linux-2.0.28

  You may also want to change your symbolic link linux -> linux-2.0.25
  to point to the new tree:

       ln -sf linux-2.0.28 linux

  This way, your links in /usr/include don't have to be changed every
  time you upgrade your kernel (i.e. you can link /usr/include/linux ->
  /usr/src/linux/include/linux instead of using the kernel version
  number hard-coded).  Then, cd to linux-2.0.28 and type the following 2
  commands:

       rm -rf include/asm
       zcat (path of linux-2.0.28.diff.gz) | patch -p1 -s

  If all goes well, it will work for a minute or two and then return you
  to your shell's prompt.  Make sure the patch applied correctly by
  typing find . -name '*.rej'.	If no filenames are listed, everything
  worked perfectly.

  Now do a make clean to delete all the backup .orig files left by
  patch, and then do a normal make config, make dep and finally make.

  Once you've successfully made a copy of the new kernel, you can safely
  delete the previous version's tree using rm -r.

  Miniproject: Someone with a bit of spare time might want to adapt
  scripts/patch-kernel to understand Linux/m68k diffs.

  Please note that you will get rejected patches if you patch a kernel
  tree that you patched from the Linux/m68k mailing list (or from any
  other source).  The easiest way to avoid this is to make a "clean"
  (i.e. distribution) kernel tree and another tree which you apply the
  patches from the mailing list to.

  9.23.	How do I choose what video mode to use with Linux?

  This is done with the 'video' boot parameter.	For details on what
  resolutions are supported, you'll want to read
  Documentation/m68k/framebuffer.txt and Documentation/m68k/kernel-
  options.txt in the Linux/m68k kernel source tree (the former document
  only appeared in 2.0.28).

  You can also specify what font you want to use with the font option to
  'video'.

  For example, to boot into 640x480x4 mode on an Amiga with a 31 kHz or
  multiscan monitor, use video=vga.

  9.24.	How can I get my Jaz drive to work with Linux (or another
  OS...)?

  Recent models of the Jaz drive (with firmware version H.71 and later)
  are shipped in a so-called "write-verify" mode.  This mode causes
  problems for operating systems (like Linux) that can't run Iomega's
  proprietary drivers.

  I (Chris) have been in touch with Iomega tech support, and they
  provided me with the low-level commands that allegedly get the Jaz
  drive into the correct mode.	However, the commands they provided
  don't seem to work (probably (ab)user error, knowing my level of SCSI
  programming knowledge).

  In the meantime, the only thing to do is find a Mac or PC with a SCSI
  interface and use Iomega's Jaz Tools software to disable the write
  verify mode.	This can also be done with a registered copy of
  Shapeshifter on the Amiga.

  More information about the Jaz drive and Linux (including the Jaz
  mini-HOWTO) can be found at Bob Willmot's Jaz-Linux information page
  <http://www.cnct.com/~bwillmot/jaztool/>.

  10.  Famous last words

  I want to thank everyone who contributed to this FAQ. There are many
  people who did so by answering questions or by asking those questions.
  Some sections are marked "provided by"; this means that the text was
  originally written by that person but has been edited by Joerg or
  myself.

  o  Frank Neumann <Frank.Neumann@informatik.uni-oldenburg.de>

  o  Benjamin Lorenz <benni@phil.uni-sb.de>

  o  Richard Hirst <srh@gpt.co.uk>

  o  Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>

  o  Martin Apel <apel@tecmath.de>

  o  Christian Steigies <steigies@physik.uni-kiel.de>

  o  Last, but certainly not least, Joerg Mayer <jmayer@informatik.uni-
     kl.de>

  10.1.	Copyright and License

  This FAQ is (C) 1995-96 Joerg Mayer and (C) 1997 Chris Lawrence.

  You may freely redistribute this FAQ without any legally-binding
  restrictions except that it must remain intact and unmodified.  Please
  contact the current maintainer in order to ensure you are distributing
  the most recent version of the FAQ.

  Amiga, Atari, Commodore, Motorola, MS-DOS, Sun, Unix and maybe a few
  more words I used in this text are trademarks. So what?

