x11
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
x11 [2018/08/06 20:16] – wiki_admin | x11 [2022/04/15 12:48] (current) – added note on system.twmrc wiki_admin | ||
---|---|---|---|
Line 5: | Line 5: | ||
The default install of Amiga UNIX, even with the capabilities of ECS, allows only a black and white X display without additional hardware, whether that hardware is a NIC providing for use of X over the network or a graphics card such as the ridiculously hard to find A2410 " | The default install of Amiga UNIX, even with the capabilities of ECS, allows only a black and white X display without additional hardware, whether that hardware is a NIC providing for use of X over the network or a graphics card such as the ridiculously hard to find A2410 " | ||
- | ===== Amiga A2410 " | + | ==== Amiga A2410 " |
This board is supported by Amix, during install reply ' | This board is supported by Amix, during install reply ' | ||
- | Then use olinit | + | Following commands are from the "UNIX System V Release 4 Amiga Version 2.0 Addendum" |
+ | |||
+ | For 1024x768 mode: **olinit | ||
+ | |||
+ | For 800x600 mode: **olinit -- -tiga -tm 3** | ||
+ | |||
+ | The A2410 is also emulated by WinUAE. | ||
==== What else is there? ==== | ==== What else is there? ==== | ||
- | With the use of drivers from the **Gateway UNIX CD**, certain other graphics cards are supported which may be easier to find (see the hardware page or the readme in the archive for a complete list). Among them is the Picasso II/ | + | With the use of drivers from the [[http:// |
+ | |||
+ | |||
+ | Some history ([[http:// | ||
+ | |||
+ | Klaus currently works at Village Tronic, at was, is and will be responsible for the hardware design of the graphic boards | ||
+ | " | ||
+ | |||
+ | |||
+ | Since long his hobby was AMIX. Having an A2000 with a GVP Series II SCSI adaptor, he wrote support for this adaptor for AMIX. | ||
+ | |||
+ | |||
+ | Also, he wrote about a dozen of very sophisticated X Servers for several graphic boards. Having intented to release this stuff for years, he finally found a place to distribute it on the Gateway! Vol. 2. | ||
+ | // | ||
This has only been tested with a Picasso II+ board using a fully patched 2.1p2a installation. Other supported boards should use the same or very similar procedure. | This has only been tested with a Picasso II+ board using a fully patched 2.1p2a installation. Other supported boards should use the same or very similar procedure. | ||
Line 30: | Line 49: | ||
3. Run olinit and xinit to make sure they are set up on your machine and working. You should be able to bring up the hideous black and white display. Do this also for other user accounts that you wish to be able to use X later (or copy the config files into that user's home directory later). | 3. Run olinit and xinit to make sure they are set up on your machine and working. You should be able to bring up the hideous black and white display. Do this also for other user accounts that you wish to be able to use X later (or copy the config files into that user's home directory later). | ||
- | 4. Download the SVGA Drivers, uncompress them using bzcat AMIX.tar.bz2 | tar -xf - and gunzip the file X11R5_bin.tar.gz using gzip -d X11R5_bin.tar.gz to end up with a file named X11R5_bin.tar. Write this file to an empty tape on your A3070, don't forget to retension/ | + | 4. Download the [[http:// |
5. Copy the file install.svga from the drivers archive to the AMIX machine (put it in your home directory or /tmp) and run it: sh install.svga You can use an MS-DOS formatted 720k floppy to copy the file. On AMIX insert the disk and execute the command mcopy A: | 5. Copy the file install.svga from the drivers archive to the AMIX machine (put it in your home directory or /tmp) and run it: sh install.svga You can use an MS-DOS formatted 720k floppy to copy the file. On AMIX insert the disk and execute the command mcopy A: | ||
Line 36: | Line 55: | ||
6. This should have left 3 files in /var/tmp. These will be deleted later so copy them to /home or somewhere else if you want to save them. The only file you will need at this point is named installR5. This needs a quick edit with vi to comment out (or delete) the command on the 5th line that reads mt fsf. The tar command will not find the file on your tape if you do not do this. The modified file should look like this: | 6. This should have left 3 files in /var/tmp. These will be deleted later so copy them to /home or somewhere else if you want to save them. The only file you will need at this point is named installR5. This needs a quick edit with vi to comment out (or delete) the command on the 5th line that reads mt fsf. The tar command will not find the file on your tape if you do not do this. The modified file should look like this: | ||
+ | < | ||
#!/sbin/sh | #!/sbin/sh | ||
Line 68: | Line 88: | ||
echo "Edit XsvgaConfig in your home directory for approriate ViewMode! | echo "Edit XsvgaConfig in your home directory for approriate ViewMode! | ||
Make sure / | Make sure / | ||
+ | </ | ||
7. Run the modified installR5 script with the command sh installR5. This will copy the files from the 30 meg .tar file that you put on the tape to your hard drive. It will take some time. The binaries will go in a new directory named / | 7. Run the modified installR5 script with the command sh installR5. This will copy the files from the 30 meg .tar file that you put on the tape to your hard drive. It will take some time. The binaries will go in a new directory named / | ||
Line 73: | Line 94: | ||
8. cd /etc and back up your profile (cp profile profile.bak) and use vi to modify the path statements to include / | 8. cd /etc and back up your profile (cp profile profile.bak) and use vi to modify the path statements to include / | ||
+ | < | ||
PATH=/ | PATH=/ | ||
/ | / | ||
+ | </ | ||
9. Change to the directory named /usr/sys and run the command make. This will compile a new kernel with the changes needed to run the linked-in " | 9. Change to the directory named /usr/sys and run the command make. This will compile a new kernel with the changes needed to run the linked-in " | ||
Line 82: | Line 105: | ||
11. Type xinit and hope for the best! If it worked, congratulations! Grab a well deserved cup of coffee and start playing around with some of the binaries in the / | 11. Type xinit and hope for the best! If it worked, congratulations! Grab a well deserved cup of coffee and start playing around with some of the binaries in the / | ||
- | Check out Jeff's screen shots on amiga.org to see what it looks like. You will find them here and here. | + | <del>Check out Jeff's screen shots on amiga.org to see what it looks like. You will find them here and here.</ |
Note from Jeff: A couple of last minute thoughts. The keymap seems to be screwed up now, but only in " | Note from Jeff: A couple of last minute thoughts. The keymap seems to be screwed up now, but only in " | ||
Line 90: | Line 113: | ||
====== X11R5 and OpenLook ====== | ====== X11R5 and OpenLook ====== | ||
- | With thanks to mackbw | + | OpenLook is a graphical user interface |
- | Upgrading to X11R5 with the method described above seems to break OpenLook. It will complain about a missing font d12lucida.snf and won't start. This can be fixed by manually telling where the fonts directory is. | + | <figure label> |
+ | {{: | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | Thanks to **mackbw** for describing the fix in [[http:// | ||
+ | |||
+ | Upgrading to X11R5 with the method described above seems to break OpenLook: it will complain about a missing font d12lucida.snf and won't start. This can be fixed by manually telling where the fonts directory is. | ||
Make sure all the user accounts have path statement correctly set (step 8 above) and that the XsvgaConfig is in every user's home directory. | Make sure all the user accounts have path statement correctly set (step 8 above) and that the XsvgaConfig is in every user's home directory. | ||
- | To change the desktop manager from tvtwm to OpenLook, change your profile' | + | To change the desktop manager from tvtwm to OpenLook, change your profile' |
- | - comment out or delete | + | - comment out or delete |
- | - add "xset fp+ / | + | - add **xset fp+ / |
- | - add olwsm | + | - add **olwsm** |
+ | |||
+ | Now xinit will bring up the OpenLook desktop. Go to Workspace / Properties / Color and select a color combination. For the color selection window to fit the screen, you'll need a resolution of at least 1024x768. Or use the shortcut key A to Apply the selection. | ||
+ | |||
+ | <figure label> | ||
+ | {{: | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | |||
+ | ---- | ||
- | Now xinit will bring up the OpenLook desktop. Go to Workspace / Properties / Color and select a color combination. For the color selection window to fit the screen, you'll need a resolution of at least 1024x768 (or use the shortcut key A to Apply the selection). | + | To-do: |
- | OpenLook Color Selection screen with "Factory" | + | * system.twmrc is in / |
- | {{: | + |
x11.1533579403.txt.gz · Last modified: 2021/09/19 17:59 (external edit)