NetNews Offline 2

home *** CD-ROM | disk | FTP | other *** search

/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / unix / amiga / 179 < prev next >

Wrap

Internet Message Format | 1996-08-06 | 44.0 KB

Path: informatik.uni-kl.de!jmayer From: jmayer@informatik.uni-kl.de (Joerg Mayer) Newsgroups: comp.os.linux.m68k,comp.os.linux.development.system,comp.unix.amiga,maus.os.linux68k,comp.os.linux.answers,comp.answers,news.answers Subject: Linux/68k-FAQ v1.10 Followup-To: poster Date: 19 Jan 1996 17:09:47 GMT Organization: University of Kaiserslautern, Germany Approved: *.answers moderation team <news-answers-request@mit.edu>, Matt Welsh <linux-answers@news.ornl.gov> Distribution: world Message-ID: <4doj8r$f41@irz1.informatik.uni-kl.de> NNTP-Posting-Host: osiris.informatik.uni-kl.de Keywords: Linux, 68K, port, Amiga, Atari, Macintosh, VME, FAQ Last-modified: 96-01-19 Maintained-By: Joerg Mayer <jmayer@informatik.uni-kl.de> Posting-Frequency: bi-weekly Archive-name: linux/m68k-faq URL: http://pfah.informatik.uni-kl.de:8000/pers/jmayer/linux68k-faq Frequently Asked Questions on Linux/m68k A Linux port to Motorola's 680x0 processors Version of this FAQ : 1.10 Version of Linux/m68k : 0.9.13 (old) and 1.2.13pl5 (current) Version of Linux : 1.2.13 (stable) and 1.3pl58 (experimental) Version of Amiboot : 2.2 (not for 0.9.13) Version of ataboot : 1.5 (not for 0.9.13) i) Introduction =============== This is an updated version of the Linux/m68k FAQ. Since it probably contains errors (typographical and logical), outdated and missing infos, I ask that you send feedback and corrections to me. This document is not intended to describe what Unix is or how to administrate it. To find out more about that read the standard Linux manuals. Thanks to everyone who sent me feedback (additions, corrections) for version 1.9! I spent most of the time that I can dedicate to this faq to just inte- grate the feedback into this new version. ii) Newsflash ============= - A new newsgroup, comp.os.linux.m68k, has been created. User level questions should be directed there instead of the mailinglist if possible. - 1.2.13pl4 has been released (Roman.Hodek@informatik.uni-erlangen.de) (Yes, I know it's been a long time since the last release of this FAQ :-( - 1.2.13pl5 has been released (Roman.Hodek@informatik.uni-erlangen.de) - ftp.uni-erlangen.de/pub/Linux/LOCAL/680x0 is the new master site for Linux/m68k. tsx-11 mirrors this site now. - A new version of the Linux/m68k install guide (mostly Amiga) has been released (Frank.Neumann@arbi.informatik.uni-oldenburg.de) http://www.informatik.uni-oldenburg.de/~amigo/inst.html, ftp.informatik.uni-oldenburg.de:/pub/amiga/linux/local/docs/ InstGuide_v2.0a.txt.gz (available as .ps and .html files too) - Don't use libc 4.7.2. It won't work with binaries compiled with earlier versions of libc and vice versa! If you've got libc 4.7.2 replace it with an earlier version (4.6.27). iii) Contents ============= i Introduction ii Newsflash iii Contents iv Versions 1. About Linux and Linux/m68k 2. Requirements to run Linux/m68k 2.1 Processor 2.2 RAM 2.3 Harddisk 2.4 Software 3. Similarities and differences of Amiga and Atari Linux/m68k 3.1 Similarities 3.2 Differences 4. The current status of Linux/m68k 4.1 General 4.2 Amiga 4.3 Atari 4.4 Mac 4.5 VME 4.6 PC 5. Hints on installing Linux/m68k 6. Sources for information/sources/binaries 6.1 Documentation 6.2 Newsgroups 6.3 Mailinglists 6.4 WWW-sites 6.5 Ftp-sites 6.6 Modem 6.7 Distributions 6.8 IRC (Internet Relay Chat) 7. Activities 7.1 Coordinator 7.2 Bug reports/Known bugs 7.2.1 TT-FPU bug 7.2.2 Amiga with GVP 16 bit RAM 7.3 Under construction/To do 8. Common problems 8.1 I can't find the manpage for XXX 8.2 Is there an X-server for the Amiga? 8.3 How can I access my SCSI tape drive? 8.4 Where did all my Amiga's chipmem go? 8.5 Do I really need an FPU? 8.6 How do I access Linux partitions from AmigaDOS? 8.7 I can't boot from harddisk although the root partition seems to be fine!? 8.8 When I try to start X11, I get 'cannot open /dev/mouse' 8.9 My SCSI bus locks up when I want to use my DAT drive 8.10 I cannot delete files with rm as root 8.11 My SCSI bus locks up when the kernel probes for devices 8.12 I displayed a binary file, and now my console is totally screwed up 8.13 Can I use both ELF and a.out libraries/binaries in my system? 8.14 After installing a patch, the new files are in the current directory 8.15 I can't mount MSDOS diskettes on my Amiga 8.16 Less behaves weird when I press a key 8.17 What are the current major/minor device numbers for /dev/xxx? 8.18 How can I tell an a.out binary from an ELF one? 9. Famous last words iv) Versions ============ At the present time, two kernel trees exist: 0.9.x and 1.2.13plx. To make switching between these versions a bit more interesting, they use a different bitorder in the ext2fs code (ext2 is the primarily used filesystem). In order to to be able to use a 0.9 ext2fs under 1.2, the 1.2 version of the filesystem check program has to be run and vice versa. Please note that starting with version 1.2.13pl4 the bitorder has been changed to yabo (yet another bit order). So you must run the current version of the ext2fs tools with the current kernel! Also there are two versions of executables. The old a.out format (which is being phased out) and the new ELF format. The problem is that a.out executables don't work with ELF dynamic libraries and vice versa. To make things a bit more ugly, for some packets (e.g. X11R6) the version numbers of ELF and a.out libraries are the same. This makes it a bit more complicated to use dynamically linked a.out and ELF binaries of X-window clients in the same installation tree (see section 8.13). Finally, these are the different versions of the ataboot, amiboot and amiga-lilo programs: 0.9.13 can be started via amiboot-1.12a, ataboot-0.7 and amiga-lilo-0.4a. 1.2.13pl3 can be compiled in two formats: a.out and ELF. The a.out version can be started by the same programs as 0.9.13. If your kernel is ELF compiled you must use amiboot-2.1, ataboot-1.2 and amiga-lilo-0.5 or later. These programs will boot a.out kernels, too. 1. About Linux and Linux/m68k ============================= Linux is a freely available operating system for PCs - to be more precise, it is one of many flavours of Unix. Linux is being developed on the net by several thousand people, first and foremost by Linus Torvalds, and being tested/used by many many more. The fun and success of Linux inspired Hamish Macdonald 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 09pl3 (this reads version 09 patchlevel 3). Linux/m68k can be regarded as beta. This means that code that hasn't been ported/written recently works well most of the time. After having released v1.2pl3 Hamish handed the coordination over to Roman. Here's the story about the beginning in Hamish's words: "I decided to port Linux to my Amiga for a variety of reasons. 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 others 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 68k (was a version about 0.06 or so), but learned that is 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' head.S so it ran on his Falcon (until the first console output :-). 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 MausNet, 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 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 '94, a German Atari magazine published an article about Linux/68k. By this Martin heard that there were some more Atari-Linux hackers and joined us." 2. Requirements to run Linux/m68k ================================= 2.1 Processor ------------- You need a Motorola 680x0 processor *with PMMU*. There is *no way* to run it without one. This reduces the list of possible processors to 68020+68851, 68030, 68040, 68LC040, 68060. Currently only the 68020+68851, 68030 and 68040 are supported. Starting with 1.2.13pl5 68060 support has been added, but it isn't working yet. At this stage you will also need a 68881 or 68882 FPU if you don't have a 68040. In theory an FPU would not be strictly necessary as it can be emulated with the normal processor, however nobody has written the code to do so - which means that in practice an FPU *is* necessary. 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/40 (not! A4000/30 which has a 68EC030 processor) and A2500/30. There has been a report that the last A4000/40s produced by Commodore shipped with an 040LC. In that case it won't work either; you need a FPU. The following Ataris (or clones) have the "right" processor built-in: Atari Falcon (FPU is not standard but needed!), Atari TT, Medusa, Eagle (not yet supported). Note: 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 7.2.1). Any processor upgrade card with a 68040 or 68030+68881/2 (like PAK/3) is able to run Linux. Note2: 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). 2.2 RAM ------- Note 1: On the Amiga the size of FastRAM is relevant, i.e. the ChipRAM is only used internally for graphics, sound and floppy data; it is not used by normal programs. Note 2: If you have an Amiga with 16-bit expansion RAM on a GVP card, see "Known bugs". It is possible 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). 2.3 Harddisk ------------ If you want to do more than just boot Linux/m68k you will need 80 - oo (infinity) MB of space on your hard disk and a supported hard disk controller. Add another 20 MB for X. 2.4 Software ------------ Amiga: In order to run amiboot you need AmigaDOS 2.0 or higher (expansion.lib- rary V36+) and at least version 39 of ixemul.library. Amiga: amiboot works with SetPatch and RsrvMem (part of Emplant) running. It doesn't work with VMM running. 3. Similarities and differences between Amiga and Atari Linux/m68k ================================================================== 3.1 Similarities ---------------- All code that depends only on the processor (i.e. paging, systemcalls, parts of the interrupt handling and of c(o)urse 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 the Amiga and the Atari may use the same kernel image (in fact the vmlinux from tsx-11 runs on both machines). 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 or Atari - as long as no machine specific devices are used (see below). 3.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. 4. The current status of Linux/m68k =================================== 4.1 General ----------- What has been done? The kernel (this means all the processor/mmu/fpu specific stuff) has been ported. V1.2 is based on Linux/i386 1.2 patchlevel 13, its Makefile structure has been adopted from the 1.3.x Linux/i386 kernel tree. Several hardware independent drivers have been ported: Ramdisk, mem, pty, tty, vt, (c)slip, ppp, net/inet, general SCSI stuff. Also the following filesystems have been done: minix, ext2, msdos, proc, isofs, affs, nfs (affs = Amiga Fast File System, read only). An X-server exists that uses the frame buffer device. Frame buffer devices exist for both Amiga and Atari in the kernel. 4.2 Amiga --------- Supported built-in hardware: A3000-SCSI, A4000-IDE, A1200-IDE, serial port, parallel port, mouse, keyboard, graphics emulates an ASCII-terminal (resolution varies with your chipset/ setup), timer, floppy disk drive (DD/HD, Amiga and PC formatted disks), beep (no real sound support), RTC of A2000/A3000/A4000. Supported cards: Several SCSI cards are supported. These are the A2091, A590 and GVP Series II. The Ariadne, Hydra and A2065 ethernet cards are supported. Also the 16c552 double-UART of the GVP IO-Extender is supported. To find out whether additional hardware is supported, look at the Linux/m68k source (config.in provides a list of supported hardware). Note: There are problems with GVP 16 bit RAM cards (see "Known bugs"). 4.3 Atari --------- SCSI, ACSI, Falcon IDE, all builtin serial ports, keyboard, Atari mouse, parallel printer port, RTC clock, floppy disk (DD/HD/ED), native Atari graphics (ST/TT/Falcon/Medusa), beep (all) and sound (Falcon/TT) are supported. The ET4000 card used in the Medusa is partially supported (you can't change the resolution). Note: Linux' Minix FS is compatible to the Minix V2 FS used with MiNT. Supported cards: The following RAM cards for the Falcon are supported: FX-card and Magnum. The Lance based ethernet cards (RieblCard, PAM's VME boards) are supported too. Screen extenders(?) like Screenblaster, Onscreen, etc. work too. The Atari Laserprinter is supported too. 4.4 Mac ------- There was talk about a Mac port but it seems to have died. There is a port of NetBSD for the Mac. 4.5 VME ------- Two ports to different VME bus machines have been started (see 7.3.4), one of them is already self hosting. 4.6 PC ------ Since PCs don't have Motorolas inside (except on soundcards and other plug-ins), this section should read "What parts of Linux/m68k are available for but not part of Linux/i386?" - Amiga Fast File System (read only) tsx-11:/pub/linux/patches/amigaffs.tar.Z Please note that most disk controllers for PC, Atari and Mac are not able to read Amiga formatted disks (this is a hardware limitation). 5. Hints on installing Linux/m68k ================================= Please note that there is a much better installation doc available. It's the 'Linux/m68k installation guide' written by Frank Neumann and Ingo Wilken. A more complete list of installation guides can be found in the documentation section. If you want to find out whether Linux/m68k runs on your system the hints given here may be sufficient. If you want to work with your Linux/m68k system you should get the Installation guide. The address is given below. The hints given here are for 1.2.13pl5 and later! 0. a) Get the installation guide mentioned above. b) Ignore steps 1-9 and follow your new guide. 1. Get a working kernel, *all* announce files and the bootstrap program for your machine (different kernel versions may require different bootstrap versions), the root and usr-filesystems and the newfilesys (this is a ramdisk that contains everything you will need to set up a working harddisk environment). Sources for these programs: See below. You will also need gunzip (from the gzip package) for your native OS in order to unpack the following .gz files: amiboot/ataboot, filesys-for-pl4 and vmlinux. Note: If gunzip succeeds your files are OK. If you want to test the integrity of the files you downloaded without decompressing them you can do 'gzip -t <filename.gz>'. 2. Bootstrap the kernel and filesys-for-pl4 as described in the ANNOUNCE file for that kernel. Many of the bootstrap flags available are documented in older announce files only. Note for Amiga users: You have to install ixemul.library in libs: in order to run versions of amiboot prior to 2.0. If you have any problems booting linux you may try to run this session without executing the startup-sequence. This will prevent any manipulation of the MMU as is done by the CPU, SetCPU, Enforcer and VMM commands. 3. Create a partition on your harddisk and install an ext2fs filesystem on it. 4. Create another partition as swapspace. 5. Unpack the root and usr filesystem onto the disk (these are still a.out, sigh). 5a. Install your ramdisk image to harddisk! It contains new versions of the filesystem utilities and newer libraries (the latter may not be true anymore). 6. Check that the utmp and wtmp files exist in the right places and that there are links from the old locations to the new ones as decribed in ELF/README (I told you to read a somewhat more verbose installation guide). 7. Reboot 8. Bootstrap your kernel, this time from the harddisk instead of ramdisk. 9. Get and read the Installation-HOWTO for Linux. Start reading from section 4 "Installing the Software". Warning: This is for the PC so you may have to do things differently at some points. Installation guide: ftp://ftp.informatik.uni-oldenburg.de /pub/amiga/linux/local/docs/InstGuide_v2.0a.txt.gz These are the filenames relative to 680x0/ ANNOUNCE-1.XXXXXX (and 0.x!) v1.2/filesys-for-pl4.gz filesys/root.tar.gz filesys/usr.tar.gz ELF/README ELF/gcc-2.7.2.bin.tar.gz ELF/binutils-2.6.bin.tar.gz ELF/ld.so-1.7.12.tar.gz ELF/libc-5.0.9.tar.gz v1.2/vmlinux-1.2.13pl5.gz v1.2/amiboot-2.2.gz (Amiga only) v1.2/ataboot-1.5.gz (Atari only) v1.2/linux-1.2.13pl5.tar.gz (the kernel source tree) ../docs/HOWTO/Installation-HOWTO (only at servers not dedicated to 680x0) The root.tar.gz file contains no gcc, emacs or tcsh. If you are a tcsh or emacs addict you will want to get these packages from bin/ too. The filesystems naturally contain *no kernel sources*, so you will have to get these too. 6. Sources for information/sources/binaries =========================================== 6.1 Documentation ----------------- This FAQ is available on ftp://ftp.uni-erlangen.de/pub/Linux/LOCAL/680x0/FAQ, rtfm.mit.edu://pub/usenet-by-hierarchy/comp/os/linux/answers/linux/m68k-faq and http://pfah.informatik.uni-kl.de:8000/pers/jmayer/linux68k-faq. An installation guide 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. The ANNOUNCE files are also valuable documentation. Further documents can be found in the directories ftp://tsx-11.mit.edu/pub/ linux/docs/ and ftp://sunsite.unc.edu/pub/Linux/docs. These documents were 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 ftp://rtfm.mit.edu/pub/usenet/comp.sys.m68k/ comp.sys.m68k_Frequently_Asked_Questions_(FAQ) and mirrors. Last but not least: Look into the Documentation directory of the kernel tree if you are using a current 1.2.13 kernel. 6.2 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.kernel: 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 as well as new kernel releases. 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. The following internet site is known to serve this group: news.uni-stuttgart.de (read only) The Newsgroup is also available in FidoNet (LINUX-68K.GER). comp.unix.amiga: This group is for discussions on AMIX, NetBSD and Linux/m68k on the Amiga. As most articles on Linux/m68k are not Amiga specific, the name is somewhat of a misnomer. de.comp.sys.amiga.unix: Similar to comp.unix.amiga but in German language. 6.3 Mailinglists ---------------- I am aware of two mailinglists for Linux/m68k. The first is being phased out because of technical reasons (overloaded). To leave the first, send mail to majordomo@vger.rutgers.edu with no subject and body 'unsubscribe linux-680x0'. An archive for this list can be found via Helmut Neukirchen's WWW page. Another mailinglist originally intended for Linux on Ataris where many "general" things are discussed as well is named linux-m68k. It is now a full blown Linux/m68k mailing list. As there is a newsgroup for Linux/m68k topics on this list should be restricted to developement issues if possible. To subscribe, send mail to majordomo@phil.uni-sb.de, any subject, with body 'subscribe linux-m68k'. Note: linux-m68k was formerly known as atarix. Note2: All mails sent to linux-680x0 will be mirrored in linux-m68k. Note3: Using linux-680x0 is stronly discouraged. 6.4 WWW-sites ------------- Helmut Neukirchen's Linux/m68k WWW page: http://www-users.informatik.rwth-aachen.de/~hn/linux68k.html Chris Lawrence' Linux/m68k WWW page: http://www.rose-hulman.edu/~lawrenc/linux/index.html Mirrors of tsx-11 via WWW: http://src.doc.ic.ac.uk/packages/Linux/tsx-11-mirror/680x0/ 6.5 Ftp-sites ------------- THE Linux/m68k server: ftp://ftp.uni-erlangen.de/pub/Linux/LOCAL/680x0/ THE two Linux servers (sources for you to port to/compile on Linux/m68k): ftp://tsx-11.mit.edu/pub/linux/sources/ ftp://sunsite.unc.edu/pub/Linux/system/ Mirrors (please use the one nearest to you, most of these mirrors are updated daily): ftp://tsx-11.mit.edu/pub/linux/680x0/ ftp://ftp.tu-clausthal.de/pub/systems/Linux/680x0/ ftp://ftp.informatik.tu-muenchen.de/pub/comp/os/linux/680x0/ ftp://ftp.informatik.uni-oldenburg.de/pub/linux/680x0/ ftp://ftp.twi.tudelft.nl/pub/Linux/680x0/ ftp://ftp.germany.eu.net/pub/os/Linux/Mirror.SunSITE/ ftp://ftp.fu-berlin.de/pub/atari/linux/ ftp://src.doc.ic.ac.uk/computing/operating-systems/Linux/tsx-11-mirror/680x0/ ftp://ftp.spc.uchicago.edu/pub/linux/680x0 ftp://ftp.nvg.unit.no/pub/linux/680x0 ftp://ftp.phil.uni-sb.de/pub/atari/linux/tsx-11.mirror Linux on Amiga: ftp://ftp.informatik.uni-oldenburg.de/pub/amiga/linux/local/ Linux on Atari (all new patches for Ataris): ftp://ftp.phil.uni-sb.de:/pub/atari/linux/ [Please tell me if your favourite mirror is not on this list.] The kernel source for Linux/m68k can be found in 680x0/v0.9/ and 680x0/v1.2/, a lot of binaries in 680x0/bin/. A few more tools reside in 680x0/tools/. The following addresses are known to offer ftp-mail: ftpmail@info2.rus.uni-stuttgart.de ftpmail@ftp.inf.tu-dresden.de ftpmail@informatik.uni-oldenburg.de To get more info on ftpmail send a mail with subject help to one of the addresses mentioned above. 6.6 Modem --------- If you have a modem, you can get Linux/m68k from the following addresses: 6.6.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) 6.7 Distributions ----------------- There are no distributions available via ftp at the moment. ALD (= Autoren Linux68K Distribution) for Atari is available from Whiteline. 6.8 IRC (Internet Relay Chat) ----------------------------- I'm trying to establish an IRC channel for Linux/m68k: #Linux68k Just do a "/join #Linux68k" and look out for others. If nobody's there, there are two possible reasons for this: You are the first to join this channel (actually, the first one to join a channel creates this channel) or (due to overload) the worldwide IRC net split into several nets and everyone else is in another net (these nets merge automagically the moment the overload goes away). There already is a well established #Linux. 7. Activities ============= 7.1 Coordinator --------------- Linux/m68k releases are built and released by Roman Hodek (Roman.Hodek@ informatik.uni-erlangen.de). As Roman does not have an Amiga, that part is maintained by Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be). 'Built' means that you can write a patch against the current version/ 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 Roman has no way to test Amiga specific patches and Geert can't test Atari specific things. Note: If you patch processor specific code (e.g. 68030 vs. 68040 MMU or FPU) make sure that you document the dependencies. 7.2 Bug reports/Known bugs -------------------------- Send bugreports to the author of the code or to Geert (Amiga) or to Roman (Atari). A probably better approach is to post it to the linux-680x0 channel 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. 7.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 te 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 | ___________________________________________________________| | | ___| 7.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: Get some real 32 bit RAM. The 16 bit RAM may still be used as a ramdisk. 7.3 Under construction/To do ---------------------------- I would like a list of projects planned/started, similar to the Linux Project-FAQ. If you send me infos, I will put them in this section. 7.3.1 General ------------- Affs: Write code, other DOS types and special root block handling is missing (dorchain@cscip.uni-sb.de). Documentation: A Linux/m68k update of the khg (Kernel hackers guide) needs to be written (especially the mmu specific stuff). Infos on the machine abstraction would be nice too. FPU-emulation A NetBSD version exists an can be found at ftp://puma.bevd.blacksburg.va.us/pub/incoming/fpe.110395.tar.gz A new multi frame buffer device (Martin Schaller) 7.3.2 Amiga ----------- Drivers for Arcnet cards are in alpha/beta (Frank.Neumann@arbi.informatik.uni-oldenburg.de) A new frame buffer device with color support (Geert.Uytterhoeven@cs.kuleuven.ac.be) A frame buffer device for the Cybervision graphics card is in alpha/beta (apel@physik.uni-kl.de and t_ebelin@informatik.uni-kl.de) The following drivers were asked about but nobody has reported interest in writing them (yet): - Concept/code for the use of chip ram and the blitter from user space. - A2024 support missing - Audio drivers - Support for Emplant serial and scsi - Support for the A4091 scsi card 7.3.3 Atari ----------- Ethernetcards (internal PAM cards) (rnhodek@informatik.uni-erlangen.de) Low level code of the new multi frame buffer device (Martin Schaller). AtariLaserPrinter is in alpha (rnhodek@informatik.uni-erlangen.de) 7.3.4 VME --------- A port to the MVME147 board has been started (engel@numerik.fb6.uni-siegen.de, nils@vespa.unix-ag.uni-siegen.de) A port to the MVME166 is in an advanced state (selfhosting) (srh@gpt.co.uk) See the vme/ directory on the Linux/m68k ftp-sites. 8. Common problems ================== 8.1 I can't find the manpage for XXX ------------------------------------ There is a *wealth* of Linux documentation out there for the original PC Linux which almost always applies to Linux/68k. Check out the documentation at your favourite Linux ftp site. 8.2 Is there an X-server for the Amiga? --------------------------------------- Yes, there is one: It's in the same package as the one for the Atari. It can be found at.../680x0/X11R6/X-binaries.tar.gz. The frame buffer device you need is already integrated into the 0.9pl5+ kernel. Make sure that /usr/X11R6/bin/X is a link to /usr/X11R6/bin/XF86_Axxxx. 8.3 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. 8.4 Where did all my Amiga's chipmem 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 (floppy, framebuffer, sound). 8.5 Do I really need an FPU? ---------------------------- Most software doesn't use the FPU, but you still need one, because the stan- dard program startup code contains at least one FPU instruction. There are two ways to avoid this problem: 1) write a FPU emulation and put it into the kernel (as is done with the i387 code) or 2) change the crt0.o module of gcc and recompile *all* programs you have. 8.6 How do I access Linux partitions from AmigaDOS? --------------------------------------------------- There is an ext2 filesystem for AmigaDOS (http://titan.cs.bonn.edu/~fasten). It allows you to read/write ext2 partitions. Not all write operations are currently (version 0.3) supported. Btw: Do read the "Known bugs section". Other ways to transfer files from Linux to AmigaDOS are to use an msdos partition, an Amiga/PC formatted floppy with msdos file system (this requires a mountlist entry on AmigaDOS side), the use of a partition with minix file system and the minix file handler on AmigaDOS side (the driver is somewhat unstable) or by accessing the floppy / any (empty!) partition directly via GNU tar. 8.7 I can't boot from harddisk although the root partition seems to be fine!? ----------------------------------------------------------------------------- If you have used the new-filesys RAM filesystem to boot, created filesystems on harddisk partitions and try to boot from one of these harddisk partitions, you might see an error like: No such file or directory while trying to open /dev/hda5 The filesystem superblock is corrupt. Try running e2fsck ... This does _NOT_ mean that your files are corrupt - instead, the /dev directory on your harddisk is missing some special files for accessing certain partitions. Check the following: Start the kernel with the RAM filesystem, mount the root partition under /mnt and check all partition nodes under /mnt/dev (sd<xy> for SCSI partitions and hd<xy> for IDE partitions). If you discover that your root/usr/whatever partition is not among them, you will have to create the special file(s) by using the 'mknod' command. Unfortunately this command is not in the new-filesys, so you will have to use the one from the root filesystem, like this: '/mnt/bin/mknod <parameters>'. For example, if your root partition is supposed to be on /dev/hda5, you should go to /mnt/dev (NOT /dev!) and issue the command '/mnt/bin/mknod hda5 b 3 5'. In this case, the '3' is the major device number for IDE harddisk devices - replace it with a '8' for SCSI harddisk devices. The minor device number (the last value) is the partition number on that harddisk, starting with 1 (NOT 0!) for the first partition. Once we have new root filesystem images or a real installation program, this should not be a problem anymore, but until then you will have to live with it. 8.8 When I try to start X11, I get 'cannot open /dev/mouse' ----------------------------------------------------------- Some installations automatically start the 'selection' demon when the system comes up. 'selection' allows you to use Cut&Paste on virtual consoles. However, this program uses the mouse driver (/dev/mouse or alike) to access the mouse, and X11 also requires the driver. The current mouse driver, however, can only be used by one program at a time. For this reason, you will have to kill the selection process before you can start X. The simplest way to do this is to issue the command 'selection -k' (selection will then look for an already running process of itself and remove it). This line could be quite handy if you put it into your $HOME/.xinitrc. 8.9 My SCSI bus locks up when I want to use my DAT drive -------------------------------------------------------- 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 harddisk in your Amiga, the bus will lock up very early (under AmigaDOS, 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 "harddisks"). 8.10 I cannot delete files with rm as root ------------------------------------------ If you have installed the root and usr filesystems from tsx.mit.edu (pub/linux/680x0/filesys) and get a message like the following whenever you try to delete files as root: "rm: dont use rm" you might find it interesting to look into the file '.bashrc' in root's home directory. In the last line, it reads: "alias rm='echo dont use rm'" which is probably not what everyone wants. Remove that line and re-login as root to get rid of this (or, for the current shell, just type "unalias rm"). 8.11 My SCSI bus locks up when the kernel probes for devices ------------------------------------------------------------ This can have two reasons: a) Some SCSI devices dislike being inquired by the host adapter to negotiate for synchronous transfers. To inhibit that behaviour for selected devices, the amiboot program has an option "wd33c93=<xxx>". This option of course only makes sense on SCSI host adapters with the WD33C93 chip, like the A3000 built-in SCSI, the A2091 or the GVP Series II. I am not sure if this also works on other host adapters using the same chip. An example: If you have a CD-ROM on SCSI address 4, the command line option to amiboot would be 'wd33c93=16' (the number is calculated from 2^SCSI_ADDRESS - or, in our example, 2^4 = 16 (SCSI addresses start with 0). You can disable sync negotiation on more than one device by adding up the values for each device. A longer explanation of this subject is contained in the ANNOUNCE-0.9pl1.gz announcement file (on tsx.mit.edu under /pub/linux/680x0). b) Other 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 behaviour 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. Although not related, it seems as if you can also bypass this problem with the "wd33c93=" amiboot option mentioned in the previous item. 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. [Can someone mail instructions how to do this on the Atari, please?] 8.12 I displayed a binary file, and now my console is totally screwed up ------------------------------------------------------------------------ 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, for instance to 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. 8.13 Can I use both ELF and a.out libraries/binaries in my system? ------------------------------------------------------------------ No problem. If you moved to ELF according to Andreas Schwab's hints (tsx.mit.edu:/pub/linux/680x0/ELF/README), you already have such 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 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 binaries some of which require ELF libraries while others 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). Note: Concerning a.out libraries, a couple of people had problems with the last libc that was created (4.7.2). So it is recommended to stay with 4.6.27 which most people were using. 8.14 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). 8.15 I can't mount MSDOS 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. 8.16 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?) 8.17 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-2.2.tar.gz. A list of the major/minor device numbers can also be found in the 1.3 kernel tree as Documentation/devices.txt. 8.18 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. 9. Famous last words ==================== I want to thank everyone who contributed to this FAQ. There are many people who did so by writing mails/news answering questions or by asking those questions. Sections 8.7 - 8.13 were provided by Frank Neumann. You may freely distribute this FAQ without any legally binding restrictions except that it must remain in whole and unmodified. I would however be grateful if you drop me a note if you include this file on a disk or cdrom (especially, if you send me a copy ;-) Amiga, Atari, Commodore, Motorola, MSDOS, Unix and maybe a few more words I used in this text are trademarks. So what? -- J"org Mayer Student und Sysop an der Universit"at Kaiserslautern http : http://pfah.informatik.uni-kl.de:8000/pers/jmayer.html e-mail : jmayer@informatik.uni-kl.de // PGPid: 0xFB2461E1 For my address ask me, use finger or take a look at my www page.