My Amithlon System

For grins, here’s my Amithlon system, from power on to running AmigaOS (video) and a picture of my Workbench and SysInfo v4 speed test.

My Amithlon’s Workbench
My Amithlon running SysInfo v4

System configuration:

Gigabyte Gigabyte GA-P35-DS3L motherboard

Intel Core2Duo @ 4.00 Ghz

(2) 512 MB ram modules (1 GB total)

256 MB nVidia 5200 PCI graphics card

32 MB Matrox G550 PCIe graphics card

Catweasel MKIV PCI card

Soundblaster Live 5.1 PCI

Realtek 8169 10/100/1000 Network card (PCI)

Intel Pro-1000 10/100/1000 Desktop Network card (PCIe)

8x DVD-RW(-/+) Slot loading drive

20 GB SATA dos boot drive (freedos)

256 GB SATA AmigaOS drive

Multi-card USB reader

Catweasel Mk4 PCI

Picking up a Catweasel Mk4 PCI card, hoping this will work well with Amithlon allowing me to read/write Amiga formatted floppies. The device allows reading/writing Amiga DD/HD, PC DD/HD and Mac formatted disk with a standard PC floppy drive.

The fun part…I’m out of PCI slots. So I need to see if my PCI-e to PCI adapter for my motherboard works or perhaps try a PCI-e network card in place of the PCI one I’m using.

This will be interesting….

And….

The Catweasel is installed! Multidisk.device copied to devs: and I created two mountlist, one for Amiga DD disk and one for Amiga HD disk. Double clicked the DD one and then inserted an Amiga DD disk and its icon popped up on my Workbench. Double clicked it and it opened the contents of the disk. I removed the floppy and the disk icon went away……only to be replaced by that familiar Amiga disk drive clicking.

Any noclick tools work with multidisk.device? – Yes, the Multidisk prefs program from the Catweasel 2 software.  No click enabled….. no clicking.  Bonus, the Catweasel 2 software also included a patch for CrossDOSFileSystem that makes it work with multidisk.device and supports disk changes (no diskchange ph0: or ph1:).

Kernel compiling, what’s really needed?

If you’ve followed my guide for compiling a kernel and have spent any amount of time looking at the .config file…..I’m curious if anyone has experimented with what’s really needed or not?  I launched VirtualBox the other day, booted my Centos setup for compiling the Amithlon kernel and dumped one out and tested on my actual system.  I made very few changes, mostly removing all the modules [m] options since I don’t use any modules.  I’m more curious if some of the modules are expected to be loaded (depending on hardware) that I could be missing that would be better off compiled in to the kernel ([*] instead of [m]).  Honestly the only things I remember ever using modules for were network drivers, audio drivers and/or network drivers.  A lot of character/keyboard/serial selections are designated at modules in Milan’s .config file.

After booting and testing the first one I went back to Centos and stripped out all the IDE drivers, just leaving generic and Intel (my motherboard uses an Intel SouthBridge and NorthBridge) IDE, enabling SATA support and adding the drivers for a possible SCSI card (I have) if I feel like giving it a try.  My kernel wasn’t much smaller than the one I compiled and have been using.   I’d like to strip out more unneeded tags or drivers.

I have to admit, I was trying to make a more generic kernel while being specific at the same time…one I can use in VirtualBox as well as on my hardware system.  Adding NIC and Sound drivers for options VB presents and such.  I could strip those out to be leaner I suppose.

Anyone else compiling their own Amithlon kernel and discovering what can be left out and what is absolutely required?

Slight update to my Amithlon system

I’ve been using a slim DVD drive that fits in a 5.25″ bracket that holds the slim drive and a 3.5″ device in my A4000T and really liked the look.  I thought about adding one to my Amithlon but didn’t know what I’d put in the 3.5″ area (it can remain empty or contain a device you don’t need access if you leave the 3.5″ cover attached (it’s a break off piece)).  I use a CF Card reader in my A4000T in that spot.  I also have a 3.5″ USB multi-card reader in my A4000T so I figured adding one of these would be beneficial to my Amithlon setup as well.    I actually replaced the tray-loading slim drive in my A4000T with a slot-loading one so I decided to do the same here.  Slot-loading slim DVD-RW, 3.5″ Multi-card USB reader, both in a 5.25″ bracket, replaced the 5.25″ DVD-RW drive that had been there.  I had an open USB header on the motherboard so connected the multi-card reader to it, attached the IDE cable to the slim to IDE adapter that was attached to the drive and booted up.  I had to add the additional ports in Poseidon (AmithlonUSB.device 4 and 5) and all was good.

I had installed BB3&4 package earlier and felt everything was good until I tried to launch Shapeshifter….which caused and immediate “emulator crash…” reboot of Amithlon.  It’s either something being loaded as a module to replace the kickstart modules or something in the ‘Amiga OS ROM update” file that the  BB3&4 skips.  I also didn’t see any advantage BB3&4 was adding to my system so I wiped it once more and started the install again from a blank HD.  This time I installed with the intent of getting a good base setup that I can restore if needed.   So, I installed Amithlon’s OS 3.9 (which includes BB1), AOSXLUpdate1, BB2, AmithlonUpdate131, MUI 3.8, Poseidon/Arakattack, Picasso96 2.1e, Roadshow and icon.library and layers.library + loadmodule.  With this all functioning I copied the contents to another partition I created named Backups:   I’ll hide this with the Workbench prefs program which only hides the device to Workbench, you still have access from the shell.   If something goes crazy from either me experimenting with software patches or libraries, etc…I can easily wipe and copy my “backup” back to the SYS: volume in seconds.

So, new slot loading DVD-RW drive with a Multi-card USB reader, all functioning with a backup made to quickly and easily setup again if I screw things up.

*Shapeshifter now has a real Macintosh feel, you drag the disc icon over the trash and it pops the disc out instead of opening the disc tray.  A small bonus with the slot-load drive 🙂

i686be-amithlon-ahiusr Audio working

Finally, i686be-amithlon-ahiusr.lha installed and functioning. I just wanted to get it working vs. the m68k-amigaos-ahiusr.lha version.   More of a challenge I guess since I kept hearing it was much more difficult to do than the 68k version.

Bernie stated there really isn’t much of a difference, the i686 will be ever so slightly faster, but use it for bragging rights or something    Faster because you are running x86 native code vs. m68k emulated code.

You need run_elf in your user-startup to let it interpret the x86 binary.

run <>NIL: run_elf GUARD PATCH

I’ll add the note to my guides and include run_elf 1.8c.tar.gz file.

You’ll need both run_elf and run_elf86 copied to C: or C:amithlonc/

After numerous attempts, finally finding the right components to make it work feels good.

Amithlon system reinstall

This weekend I formatted my system volume and installed Amithlon again.  Leaving all my other partitions alone provided access quickly to most of my installed software, just needed to spend time setting up my Workbench and patching/updating.  I also had a copy of my Sys: partition on my DATA: volume in a folder so I could easily pull patch files, libraries, review my startup-sequence, etc… as I was setting up my new install.

This time I skipped doing any Genesis install and I went straight for RoadShow for the TCP/IP stack.  Everything is mostly working, I have a few software packages to install but before I continue I may do another fresh install.  I want to get Amithlon installed, all the proper updates/patches (AOSXL_update1, Boing Bag2, AmithlonUpdate131) installed, USB and networking configured and Picasso96 installed and configured, then make a full backup of this configuration.  Experimental patches and software installs come later as this way I can have a full configured base system (AmigaOS and hardware) to restore if something happens and I can re-evaluate what additional patches and/or software to install from that base.

Roadshow TCP/IP stack

I use Roadshow on my A4000T and enjoy the DHCP aspect (even though I reserve IP’s for my systems so they always have the same one), I enjoyed the “in the background” aspect it offered in that it launched at boot (during the user-startup) and was just there, doing it’s thing…providing TCP/IP to my system.   On my Amithlon system I had been using Genesis, and while nice, it doesn’t offer DHCP, it doesn’t really run in the background and it hasn’t been updated, or continues to be updated, like Roadshow.

I had configured Genesis to not show it’s GUI on launch and added the startup commands to my S:user-startup file to make it appear seamless like Roadshow, however if I ever attempted to change a screenmode, it would not allow me to do so until I had launched the Genesis GUI and exited out of it.   A minor inconvenience but still an inconvenience.

I had attempted to configure Roadshow on my Amithlon system previously and had a single issue that prevented me from using it……my machine would lock/freeze on boot….basically when trying to run the script s:network-startup that is added to your s:user-startup file.  I’m not positive what my issue was but I believe I have found what it was during my latest attempt.   The Amithon Installation Guide Pt. 2  is being updated and already contains the following information:

 

Networking (Roadshow)

You could instead use Roadshow if you have purchased this.  Installation is done via an Installer but configuration changes are made editing text files that Roadshow uses.  These will need to be edited after installing to reflect your network card, network addresses, name servers, hosts and routes.

Install Roadshow using the installer, once installation is complete, browse to your DEVS:Storage/NetInterfaces folder and make a copy of the RTL8139 text file and name it AmithlonNET, then copy it to DEVS:NetInterfaces/ .   Edit this file to use the device driver of your Amithlon system, most likely the same as used for Genesis, the amithlon1_net.device.  I had issues with it obtaining an IP address via dhcp so I commented out the line for dhcp and uncommented the lines for address and subnet and modified those for my network.  You may also want to change these two lines:

#iprequests=32

#writerequests=32

to

iprequests=64

writerequests=64

As it will improve the performance of the network interface (faster transfers)

Next you’ll edit the ‘name_resoltuion’ file under DEVS:Internet changing the line:

#nameserver 192.168.0.1

Removing the “#” to uncomment it and modifying the address to match that of your router which is typically the name server you use.  You can add additional name servers by uncommenting the other lines and modifying those if you also point to Google’ DNS servers, etc..

In the same folder (DEVS:Internet) edit the file ‘routes’ and change the line:

#default localhost to remove the “#” and change “localhost” to your router’s IP address (again this is a typical configuration).

If you have any devices you communicate with on your local LAN, it would be a good idea to add those to the ‘hosts’ file.  Ad the bottom of the file, just add your devices IP and what you call them.  I have a NAS box for storage so I add it’s IP address, press tab and then add the name MyNAS.   This allows me to reference MyNAS instead of the IP when using SMBFS or FTP, etc..

Reboot and your Amithlon should start up with networking enabled and running.  I will look into the DHCP issue I was having and see if it can be easily resolved.  I use DHCP (with an IP reservation on my A4000T so I expect it should work just as well on my Amithlon system.

When using DHCP you should only edit the AmithlonNET file to uncomment the ‘iprequest’ and ‘writerequest’ and bump them to 64 and edit the ‘name-resolution’ file to add your router’s IP address as the nameserver.   If you have local devices you want to reference by name, editing the ‘hosts’ file is still needed.

Make sure to also update to the latest version, Roadshow v1.13.