Post has attachment
Just wanted to say hello to the group.

I used Amithlon for a years but my last functioning machine died a few years ago so I moved to MorphOS.

Not seen this reccomended anywhere so I thought I'd mention it. Works wonders and gives a noticable speed increase.

http://aminet.net/package/misc/emu/RaMithlon.lha

I was in contact with the author a few years back with regard to him releasing the code but he wasn't sure where it was stored if anywhere sadly.

Just received a new motherboard for Amithlon testing from a friend.
It's an MSI X58M with a 1st Gen i7 CPU. His testing has USB and NIC support (based on the RTL8111 driver for Kernel4) and we're looking into getting the onboard audio working similar to how we got the onboard NIC. It only has 1 PCI slot so that could be Video or Audio at this point. Video could be covered with a PCI Matrox G550 card. I'm waiting on RAM to arrive to start testing.

Post has attachment
Okay, doing some linux investigating we've found a 2.4 kernel module for the RTL8111 series cards common on motherboards (10/100/1000 nic).

I have a new module file for the following network cards (mostly motherboard), it doesn't build with the kernel so had to be manipulated a little to get it to 'make' for kernel4.

Download it here for your Amithlon system.
http://amithlon.snkbitten.com/files/kernels/Kernel4/rtl8111nic.lha

Extract the files to ram: then copy the r1000.o file to your devs: pcidrivers/net/ folder and copy the other three files to your S: directory.

It will overwrite your pci_modules, vendors.txt and vendors_pci.txt files in S: so you may want to back those up. The new ones were updated and should give more useful info as well when doing a pcilist command (much less "unknown device")

RTL8111B/RTL8168B/RTL8111/RTL8168
RTL8111C/RTL8111CP/RTL8111D(L)
RTL8168C/RTL8111DP/RTL8111E
RTL8168E/RTL8111F/RTL8411
RTL8111G/RTL8111GUS/RTL8411B(N)
RTL8118AS

It's based off version 1.07, no changes to the driver just massaged the make file.

http://www.realtek.com.tw/Downloads/downloadsView.aspx?Conn=4&DownTypeID=3&Langid=1&Level=5&PFid=5&PNid=13&SortByDesc=1
I can remove the Intel Pro 1000 Nic from my system now and use the motherboard built-in controller..

Some basic testing last night between unpatched, Amithlon's fastcopy (extras/testprogs on Amithlon CD) and RaMithlon to see which increased memory copy functions. In my case, remaining unpatched provided the best performance. The additional overhead of process switching from 68k to x86 the other two use to boost speed actually created delays on my system. Granted I have a fast CPU with lots of cache which appears to allow the 68k+JIT implementation run faster than process switching to x86 and executing and then switching back to 68k.

These type apps/patches can improve performance, but in my case they decreased performance. Always test on your own machine as what helps one system may do nothing or hurt another.

Some basic experimenting with the kickstart in Amithlon. I started with the Amithlon Rom (loaded all it's modules in to remus) then replaced the ones with versions from the BoingBag2 extracted modules . I then replaced the math libs with hsmathlibs and layers.library with version 45.27.

I removed workbench.library, battclock.resource and scsi.device for room. Amithlon booted just fine and I haven't noticed any issues currently. I'll continue to monitor.

Changed my setpatch line to
SetPatch NOROMUPDATE NONSD >NIL:
in startup and commented out my LoadModule line.

battclock.resource is injected by Amithlon so not needed. scsi.device is not needed because Amithlon uses amithlon.device. workbench.library I use an updated version in libs.

Replaced modules:
exec_45.20 (A1200-A500)
bootmenu_447(A500)
console.device_44.8
filesystem.resource_45.10
filesystem_45.13
ram-handler_44.24_NoBss
shell_45.7
mathffp.library (HSML)
mathieeesingbas.library (HSML)
layer.library 45.27

Removed modules:
battclock.resource_39.3
scsi.device_40.5(A600-A1200)
workbench.library_40.5

Any suggestions of what else to replace/upgrade. We are limited to 512KB ROM image so keep that in mind.

Post has attachment
New kernel compiling guide. This is based of Ubuntu 5.10, and old linux distro but newer than the Centos distro my original guide used. Now go build your own kernel customized to your Amithlon machine (within the 2.4.37.9 limits).

Suggestion, set up the Virtualbox/Ubuntu environment and compile the kernel without making changes. Test it to see if your kernel works. You can then start making changes.

I'll start working on a basic outline of what you can change and how you can make the kernel specific to your hardware to eliminate the need to load modules after booting with the pciinsmod command. Remember that this is still kernel4 and the hardware it supported is still only what is available.

Post has attachment

It's been a quiet new year so far, I've been playing with Lightwave 2018 and unfortunately spending less time with Amithlon. I need to start using Amiga's Lightwave 3d 5.x again, though it's getting more and more difficult bouncing between the old (Amiga) and new (PC) versions :)

I'd like to start looking at other motherboard/cpu combinations again for an even faster Amithlon system....maybe finally try an older i7 motherboard/cpu setup. Too bad those still haven't dropped in to the "cheap" price category.

Hope everyone is having a great start to 2018....lets see those Amithlon desktops and list of your favorite utilities/apps!!

Doing some more reading/researching and I found some nice information on the init string to launch Amithlon and setting certain settings in the typically done in the 'startup-sequence' in AmigaOS.

First off, the init string ...

init=/linuxrc
Don't change this one, it is needed for Amithlon to start

console_level=0
Set this to 4 (instead of 0), and the boing ball will no longer bounce, but rather sit in the top left corner, and you will get kernel and emulator messages during startup. Do this if things fail to start!

root=/dev/ram0
Leave this as it is. Amithlon needs it like this (kernel 4 uses ram1 instead)

ramdisk_size=12010
Leave this as it is for 'bigird.gz' or use 2310 if using 'smallird.gz'

leavepages=7400
Don''t reduce this number. You might want to increase it to give Amithlon more memory for disk caching (only read-caching, no write caching, so it's safe!).
Each page stands for 4k; If you increase the number by 1024, you are adding 4MB of disk cache (but take 4MB away from the Amiga). Reducing the number below the values given will result in weird and hard to track hangs!

vga=769
Only used if you are using the VESA driver for graphics support. In that case, this decides the one (and only) mode you will have available. See the following table for the meaning of the numbers. **Installing amithlonupdate131 will give you screenmode choices in AmigaOS for additional VESA modes.

Resolution 640x480 800x600 1024x768 1280x1024
8bit 769 771 773 775
16bit 785 788 791 794
24bit 786 789 792 795

So an 8bit 800x600 screenmode would be vga=771

If you are using the setconfig options in your startup sequence (e.g. to set cachesize, or monitor frequencies), you can also put those onto the kernel command line. The advantage is that those options are available before AmigaOS starts up, and will thus not require a reboot to come into effect. To set, for example, the cachesize to 16384kB from the kernel command line, simply add the option "cachesize=16384" after the "leavepages=xxxx" entry. A word of warning, though --- the various boot loaders all have limits on how long the kernel command line can be; So if it looks like your settings didn't make it into Amithlon, check with "dumpconfig"... They might just have been truncated.

My init string for loadlin.exe is named tsmall and contains the following:

nvitel.gz init=/linuxrc console_level=0 root=/dev/ram1 initrd=smallird.gz ramdisk_size=2310 leavepages=7800 cachesize=65536 vesa_defaults=0 hsyncmin=24 hsyncmax=82 vsyncmin=48 vsyncmax=76 clockmax=300 asynchronous_io=1

So my autoexec.bat file reads
"loadlin @tsmall"

**nvitel.gz is my kernel, your init would be whatever kernel you are using, most likely kernel4 or kern310.
The rest set all the init options and then the setconfig settings that were previously in my s:startup-sequence file. Since I can comment those out now, on boot the setconfig reboot if changed no longer forces a reboot. Running dumpconfig confirmed all my settings were still present (after a complete power cycle and restart).

Not huge news but nice to always eliminate any additional reboots on boot when possible.

It would be interesting to find out what would be the fastest PC that can be built to run Amithlon. Naturally with the constraints of maximum RAM size that Amithlon can handle as well as the smallest DIMM size that is available. I'm thinking perhaps an I7 on a socket 1156 or socket 1366 board with 1GB or possibly 2GB DDR3. I imagine graphics would have to be a PCI 5200 (I hear this is the fastest card with hardware acceleration?).
Naturally it may not be possible to do all the initial setup on this PC and may need an older PC to initially set it up and do all the kernel updates and patches and then move the HDD over to the fast machine.
Im currently building another Amithlon box based on Gigabyte EG41MF board with a Q6600 Quad Core CPU. To my surprise it can boot the Amithlon CD and also allows me to install it and run it on a SATA HDD without having first done any kernel updates. The only constraint I have is that it only has 2 PCI slots so Im using those for video and sound and getting an Intel Pro 1000 card as per Toms advice for the PCI-E slot. I will then multiboot this PC for other Amiga projects. Thoughts?
Wait while more posts are being loaded