chance227 wrote:i did find a diagram years ago with jumper settings for that card, and i was able to sort it out then i will try to get a pic of my card settings so that you can compare them together.
Yes, that would be helpful - my Riebl card works fine with both NetBSD/atari and Linux/m68k - but ASV just doesn't seem to like it, and I have no idea why that is.
chance227 wrote:Thanks for having a go at Marks Image and getting it sorted, good to hear some of you younger lads getting in Atari ASV
Oh well, for me, all of this comes a bit late... I had been searching for an ASV installation for well over a decade, but when those images finally showed up here in 2006, my general retro-foo had already been weakened a lot, most of the old machines hadn't been turned on for a long time, and screeching old SCSI disks distinctly get on my nerves. So I switch on the TT every couple of weeks to poke at things for an hour or two, to see if maybe this time something falls over in the right place...
...which, according to the Linux atarilance driver, are the addresses used in a MegaSTe. Of course, my card is configured with what everyone sais are the jumper settings for the TT.
Can't get routing to work atm (there is a default route in the table, but I still can't reach any system outside the local network)... Now to bootstrap a more recent gcc (I think maybe something in the line of 2.7.2 might work...)
[edit] I don't remember if the kernel got reconfigured automatically after I changed the edt_data - file... If it doesn't, boot with an -r on the kernel command line from the boot loader...
# ./configure --prefix=/usr/local --program-suffix=-2.7.2.3 --disable-nls --build=m68k-atari-sysv4
Using `./config/m68k/m68k.c' to output insns.
Using `./config/m68k/m68k.md' as machine description file.
Using `./config/m68k/atari.h' as target machine macro file.
Using `./config/m68k/xm-atari.h' as host machine macro file.
Merged t-svr4.
Merged c++ fragment(s).
Created `./Makefile'.
Merged t-svr4.
Created `cp/Makefile'.
Links are now set up to build a native compiler for m68k-atari-sysv4.
(I'll have a look at newer gcc's someday, but I seem to remember that 2.7.2.3 was the last one that could be built without lots of fiddling around on m68k-sun3-sunos4...)
By the way, asv_mark actually seems to be the more recent version. (No, didn't boot it yet, just had another look at some of the strings in the image files...)
C is all closed on mine. B is close/open/close. I have my card configured for AUI (A to top), and use an AUI/TP transciever. Contrary to the NetBSD FAQ, that one needs D in the top position, because otherwise the transciever isn't powered.
I didn't fully walk through the network configuration, but it seems the init scripts want an entry with the configured hostname and an associated IP address in /etc/hosts, and an appropriate entry in /etc/networks if you don't want classfull addressing.
gcc compilation bombed out with an internal compiler error in stage 1, so it seems that one needs another intermediate step.
How do I use the Image file on a Mac or PC or maybe even my Falcon running Mint? I have a PC running Windows 7 and a Mac running the latest version of 10. Any help would be great! Thanks!
wbyte wrote:The easiest way is to attach 50pin scsi controller to your pc and boot some live linux dist. Then just write the image using dd.
Sadly, no SCSI on the PC side anywhere. Amiga, Atari, Mac and even my C64! Could this be installed on a CF card, I'm using a CF adaptor in my TT. I can image the card on my old PC laptop with a CF adaptor.
tenox wrote:So I've dumped ASV image to a CF card attached via Acard. Normally works with TOS and NetBSD, but I get this:
asv.jpg
This is for both Richard and Mark and on 4 different CF cards.
Has anyone successfully booted this from Acard+CF?
Never tried this myself.
If it doesn't work, it seems as if your Acard does not implement the SCSI read capacity command correctly (or at least in a compatible manner).
If I remember correctly, early SCSI standards defined a fixed CDB (command descriptor block) length (6 bytes?) while newer standards extended this to variable sizes to be able to cope with extended LBA lengths. May be the ACARD insists on the latter?
wbyte wrote:The easiest way is to attach 50pin scsi controller to your pc and boot some live linux dist. Then just write the image using dd.
Sadly, no SCSI on the PC side anywhere. Amiga, Atari, Mac and even my C64! Could this be installed on a CF card, I'm using a CF adaptor in my TT. I can image the card on my old PC laptop with a CF adaptor.
wbyte wrote:The easiest way is to attach 50pin scsi controller to your pc and boot some live linux dist. Then just write the image using dd.
Sadly, no SCSI on the PC side anywhere.
I was using NetBSD/atari to dd the file to another disk (sending the image over network via netcat - so that needs a network card supported by NetBSD).
After some time I just built a PC with a SCSI card from spare parts to write the images, as it's way faster than pushing bits through the bloody Riebl thing...
Last edited by alexb on Sun Nov 24, 2013 11:48 am, edited 1 time in total.
tenox wrote:Also tried with Artmix CF AztecMonster. But that never works.
Are there any other SCSI to IDE bridges / adapters?
For SD cards on an Atari, there's the Gigafile, which works very well as ACSI device (SCSI mode seems somewhat experimental from what I heard).
At least according to the ASV documentation, it should be able to boot from an ACSI device too, but I never tried that (also never seen your error message)...
alexb wrote:
At least according to the ASV documentation, it should be able to boot from an ACSI device too, but I never tried that (also never seen your error message)...
To my knowledge, ASV never had proper ACSI support (although it _might_ be possible to have the root sector on an ACSI disk since the boot code uses DMAread() to get at it).
mfro wrote:To my knowledge, ASV never had proper ACSI support (although it _might_ be possible to have the root sector on an ACSI disk since the boot code uses DMAread() to get at it).
Sorry - I thought I had seen that in the release notes somewhere, but upon checking the documentation, it actually sais:
Note that ACSI hard disk drives are not supported by Atari System V.
I'm currently rounding up a number of different SCSI to ATA adapters and will try with different ones and report.
There also may be an issue with CF cards being reported as removable devices. While this may not matter to TOS it may to ASV. I have purchased couple of industrial CF cards that do report as non-removable media. We shall see.
Can't get routing to work atm (there is a default route in the table, but I still can't reach any system outside the local network)... Now to bootstrap a more recent gcc (I think maybe something in the line of 2.7.2 might work...)
[edit] I don't remember if the kernel got reconfigured automatically after I changed the edt_data - file... If it doesn't, boot with an -r on the kernel command line from the boot loader...
Do you know who is maintaining this? Jumper D (J7) is reversed, at least on my card
(I think maybe something in the line of 2.7.2 might work...)
