All FreeMiNT builds again available and more!

[TheNameOfTheGame]

Well I put the MINT-36C.PRG as the last program in my AUTO folder and copied the MINT folder over to the C-boot drive.

It starts to load MiNT, but hangs at the MFP serial driver...here is a screenshot. What should I do to get it to boot? This is on a Hades060.

hades_mint.png

[frank.lukas]

Is it possible that that the network are not working well with the 000 package. I can not make the Network working with the 36C and the USB ASX0 or with a Netusbee enec.xif ...

[mikro]

Do I just move these to my hard drive and boot? I notice in the AUTO folder is "mint-36c.prg". But in the "mint/1-19-36c/" folder there is a "mint060.prg". Does the AUTO folder program call the other file?

Yes and yes. :)

Not sure about NVDI situation on Hades but I guess it wont hurt to have it present in AUTO (before mint-36c.prg). Let us know how it went!

EDIT: Oh, you already did. Well, as the first step, try to disable all modules and then enable them one by one. I'm not sure when was the last time somebody tried the latest kernel on a Hades, so it's possible something is not working. It is enough just to rename *.XDD to *.XDX, *.XFS to *.XFX and *.XIF to *.XIX. In both c:\mint\1-19-36c and c:\mint\1-19-36c\hades.

[mikro]

Is it possible that that the network are not working well with the 000 package. I can not make the Network working with the 36C and the USB ASX0 or with a Netusbee enec.xif ...

Everything is possible. :) Did it work before? (i.e. did you just replace your c:\mint\1-19-cur without any configuration change?)

If so, try to attach some logs / photos.

[dhedberg]

Thanks mikro! Perhaps it's time for me to finally have a go at mint now when I have a TT with plenty of TT-RAM.

[frank.lukas]

Is it possible that that the network are not working well with the 000 package. I can not make the Network working with the 36C and the USB ASX0 or with a Netusbee enec.xif ...

Everything is possible. :) Did it work before? (i.e. did you just replace your c:\mint\1-19-cur without any configuration change?)
If so, try to attach some logs / photos.

The asix.xif works not with my Mega STE before in 2018 with the Lightning VME. At the time I test with a Lightning ST at a Atari Mega ST not MSTE and it do not work. Also it works not with a Netusbee enec.xif for test.

When I start in a shell ping one line is coming up and than nothing happens anymore.

ping.gif

mint.cnf ...

Code: Select all

# USB

exec u:/c/mint/1-19-36c/usb/loader.prg

# Network

exec u:/c/mint/1-19-36c/sysroot/bin/ifconfig.ttp en0 addr 192.168.2.14 netmask 255.255.255.0 up
exec u:/c/mint/1-19-36c/sysroot/bin/route.ttp add default en0 gw 192.168.2.1 metric 1

# The "exec" command is used to launch programs. Note that programs
# so launched are started before GEM is, so they must be TOS/TTP
# programs.

# Start Draconis to MiNT-Net gateway

#exec u:/c/mint/mgw.prg
#echo

# Start Gluestik

#exec u:/c/mint/gluestik.prg
#echo

# NFS Mount

exec u:/c/mint/1-9-36c/sysroot/bin/nfsmount.ttp -v -o rw,rsize=1024,wsize=1024,retrans=10 192.168.2.118:/Users/frank/Downloads/Atari /nfs/MacPro



[mikro]

The asix.xif works not with my Mega STE before in 2018 with the Lightning VME.

Hmm, so it did work with a kernel from 2018? Do you know which build exactly? If so, it looks like some USB regression, something which David (Galvez here on AF) will be certainly happy to hear about. :) If you can provide more details about the working build/setup, it's a good idea to report it here: https://github.com/freemint/freemint/issues

[Kroll]

@TheNameOfTheGame, @mikro:
Yes exactly, on my Hades I had to rename MFP.XDD to MFP.XDX

[TheNameOfTheGame]

@TheNameOfTheGame, @mikro:
Yes exactly, on my Hades I had to rename MFP.XDD to MFP.XDX

Ok, thanks...and what is the implication of that? Does it cause some loss of functionality?

[TheNameOfTheGame]

Ok, renamed MFP.XDD to MFP.XDX and the system boots up to teradesk. However, when I selected the teradesk "about" dialog the system had a total lockup. See associated picture.

teradesk_lockup.png

[frank.lukas]

The Network do also not work with a 2018 000 kernel. It is not a USB thing because I test it also with a netusbee and it do not work ...

[mikro]

Ok, renamed MFP.XDD to MFP.XDX and the system boots up to teradesk. However, when I selected the teradesk "about" dialog the system had a total lockup. See associated picture.

Nice. :-)

Is this with NVDI installed? If yes, try to disable other (non-essential) AUTO programs/ACCs. Also, when you see the FreeMiNT boot message, press shift and try to disable memory protection (not nice but if it works, it will give us a hint).

About MFP.XDD: actually, you can read the current state in https://github.com/freemint/freemint/bl ... /ports.txt -- unknown. ;) I erroneously assumed that serial ports in Hades are Atari compatible but they are not: http://www.medusacomputer.com/thes-hades.html. I have disabled it for Hades builds for now. In practice, you wont see the serial ports in u:/dev.

If you have any technical information about the ports (where they are mapped and what circuit they are using), maybe we can do something about it (for the Milan there is a special UART version).

[mikro]

The Network do also not work with a 2018 000 kernel. It is not a USB thing because I test it also with a netusbee and it do not work ...

Can you find any kernel (even as old as 1.18: https://github.com/freemint/freemint/releases) which works for you? I can't test the build on any ST machine right now.

[Galvez]

The Network do also not work with a 2018 000 kernel. It is not a USB thing because I test it also with a netusbee and it do not work ...

Can you find any kernel (even as old as 1.18: https://github.com/freemint/freemint/releases) which works for you? I can't test the build on any ST machine right now.

We hit the same issue the last year with the ROM-port Ethernet adapter, this confirms that the problem was not in the driver but in the 000 kernel.

viewtopic.php?f=15&t=33189&p=343103#p343508

[frank.lukas]

I will hope it can be fixed !

For such a long time it are not working with the 000 package

The Network do also not work with a 2018 000 kernel. It is not a USB thing because I test it also with a netusbee and it do not work ...

Can you find any kernel (even as old as 1.18: https://github.com/freemint/freemint/releases) which works for you? I can't test the build on any ST machine right now.

The 1-18 package has no inet.xdd and the whole cpu typ folders 000, 030 and so on are all empty ...

[TheNameOfTheGame]

Ok, renamed MFP.XDD to MFP.XDX and the system boots up to teradesk. However, when I selected the teradesk "about" dialog the system had a total lockup. See associated picture.

Nice.

Is this with NVDI installed? If yes, try to disable other (non-essential) AUTO programs/ACCs. Also, when you see the FreeMiNT boot message, press shift and try to disable memory protection (not nice but if it works, it will give us a hint).

About MFP.XDD: actually, you can read the current state in https://github.com/freemint/freemint/bl ... /ports.txt -- unknown. I erroneously assumed that serial ports in Hades are Atari compatible but they are not: http://www.medusacomputer.com/thes-hades.html. I have disabled it for Hades builds for now. In practice, you wont see the serial ports in u:/dev.

If you have any technical information about the ports (where they are mapped and what circuit they are using), maybe we can do something about it (for the Milan there is a special UART version).

Yes, Nova-VDI is installed with NVDI for GDOS support. I will back out some of the AUTO folder programs/ACCs as you suggest.

As for the Hades MFP, there is some technical information in the DOKUE101.TXT file in the memory map section:

Code: Select all

FFFFFA00 - FFFFFA3F  rw   STMFP like with the ST and TT:
                            IO0: Printer Busy
                            IO1: DCD Modem 1
                            IO2: CTS Modem 1
                            IO3: Interrupt ISA 1
                            IO4: Interrupt ACIAs
                            IO5: Interrupt IDE
                            IO6: RI Modem 1
                            IO7: Interrupt ISA 2
FFFFFA80 - FFFFFABF  rw   TTMFP like with the TT:
                            IO0: Interrupt PCI 1
                            IO1: Interrupt PCI 2
                            IO2: Interrupt PCI 3
                            IO3: RI Modem 2
                            IO4: Floppy Interrupt
                            IO5: Interrupt PCI 4
                            IO6: Clock Interrupt
                            IO7: SCSI Interrupt

[frank.lukas]

3 ping packs going out and than it stop

ping2.gif

I had the network in 2/2016 working with a Atari Mega ST but I have not longer the files ...

-> https://forum.atari-home.de/index.php/t ... #msg203880

[mikro]

The 1-18 package has no inet.xdd and the whole cpu typ folders 000, 030 and so on are all empty ...

Maybe you didn't look into 'drivers' folder? All modules are compiled for 68000 so don't worry about CPU builds. 1.18.0 was released in 2013, so if you had a working setup in 2/2016, there is a good chance this will work. And it will give us something to start with.

Ah, I see what you mean: you downloaded a 1.18 branch build, not 1.18.0 release from the link I have provided. So please try that instead. :)

[mikro]

As for the Hades MFP, there is some technical information in the DOKUE101.TXT file in the memory map section:

Code: Select all

FFFFFA00 - FFFFFA3F  rw   STMFP like with the ST and TT:
                            IO0: Printer Busy
                            IO1: DCD Modem 1
                            IO2: CTS Modem 1
                            IO3: Interrupt ISA 1
                            IO4: Interrupt ACIAs
                            IO5: Interrupt IDE
                            IO6: RI Modem 1
                            IO7: Interrupt ISA 2
FFFFFA80 - FFFFFABF  rw   TTMFP like with the TT:
                            IO0: Interrupt PCI 1
                            IO1: Interrupt PCI 2
                            IO2: Interrupt PCI 3
                            IO3: RI Modem 2
                            IO4: Floppy Interrupt
                            IO5: Interrupt PCI 4
                            IO6: Clock Interrupt
                            IO7: SCSI Interrupt

This is perhaps why I thought it has Atari compatible serial ports - it has the MFP, all right but most likely not connected to the serial ports which are wired differently (UART?).

[frank.lukas]

The 1-18 package has no inet.xdd and the whole cpu typ folders 000, 030 and so on are all empty ...

Ah, I see what you mean: you downloaded a 1.18 branch build, not 1.18.0 release from the link I have provided. So please try that instead. :)

1-18-cur do not work because xaaes is not running.

AESSYS fatal error
ILLEGAL INSTRUCTION





I give up !

[mikro]

Frank: can you at least try that networking? You can try ping without xaaes... (just specify INIT=/c/path/to/bash in mint.cnf). The 68000 build has been long without any attention so it's no surprising it's not working 100%. But without users willing to test things nothing is going to improve.

Btw, the 1.18x snapshot should be complete, this whole time it was using a broken script and nobody has noticed. So you see, it's not very well tested nor used.

[frank.lukas]

mint.cnf = INIT=u:/bin/bash

ping do not work. One line and than nothing with 1-18-0 and 36c ...

[mikro]

Well, in that case networking is really screwed. If you had it working in 02/2016, that must have been some of the daily builds from freemint.org. Maybe I can make you a custom 68000 build from around that era if you would be so kind to test it.

You may also want to try 1.17.0 (https://github.com/freemint/freemint/re ... int-1_17_0) and 1.16.1b (https://github.com/freemint/freemint/re ... eta-1_16_1).

[frank.lukas]

I use always all the trunk stuff with the helmut kernel in 2/2016 because of the TOSFS in the helmut kernel.

[frank.lukas]

I check it cross with the 1-19-36C on a Atari Mega STE and the Network works fine with ASIX.XIF and a Lightning USB VME Interface. The kernel is hanging when SCC.XDD are loading otherwise it is working fine.