NetBSD/Amiga

[strim]

Originally Posted by gibs

Where are the pkgsrc ? so I can download them and put in the CF.

http://www.pkgsrc.org/ (there's a link to source distribution tarball, extract it to /usr/pkgsrc )

But if you don't have working network connection, then you'll also need source tarballs for dillo and all dependencies on your CF (put them into /usr/pkgsrc/distfiles ). Usually they are downloaded automatically by build scripts, but since you have no network, you'll have to download them manually. Be sure to read the pkgsrc user's guide.

Is Dillo working fine ?

Last time I tried it was working just fine, but that was around 1,5 year ago. It should still work.

[gibs]

Strim,
I have now a Xircom Credit card PS-CE2-10, 2.10 Manufacturer 0x0105 Product 0x10b

When I insert it, it's not disabled but it's not configured.
Not configured means the driver isn't built in the kernel ?

I thought it was a NE2000 compatible, it is reported as it.

[strim]

Originally Posted by gibs

Strim,
I have now a Xircom Credit card PS-CE2-10, 2.10 Manufacturer 0x0105 Product 0x10b

When I insert it, it's not disabled but it's not configured.

As far as I know, this card is support by the xi driver. However...

Not configured means the driver isn't built in the kernel ?

Exactly, you'd need to build your own kernel with xi enabled. It's quite easy. However... I am afraid that xi driver might not work properly on amiga. At least not until we fix the PCMCIA driver .

I thought it was a NE2000 compatible, it is reported as it.

Who does report it as it? Personally, I doubt it is compatible, since it needs a separate driver.

[gibs]

Here on a FreeBSD site : http://www.freebsd.org/fr/releases/4.2R/notes.html

[strim]

Originally Posted by gibs

Here on a FreeBSD site : http://www.freebsd.org/fr/releases/4.2R/notes.html

It's not stated very clearly, but you can see that "NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards" and "Xircom CreditCard adapters(16bit) and workalikes" are separate points. FreeBSD has different drivers for them too.

[ahhyes]

Originally Posted by strim

Exactly, you'd need to build your own kernel with xi enabled. It's quite easy. However... I am afraid that xi driver might not work properly on amiga. At least not until we fix the PCMCIA driver .

I dread to think how long a kernel build would take on an amiga and even an amiga equipped with an 060 (cook a lamb roast and come back later?)

Does "kldload" not work on NetBSD (eg: kldload xi)? I use this on FreeBSD when I dont want to have to recompile the kernel. You can have the kldload persistent across reboots by adding the relevant directives to /boot/loader.conf

Though it's been a long time since I played with NetBSD so this might not apply.

[strim]

Originally Posted by ahhyes

I dread to think how long a kernel build would take on an amiga and even an amiga equipped with an 060 (cook a lamb roast and come back later?)

You can cross-build on almost any POSIX-like system (Linux, FreeBSD, Solaris, etc.). It works great, I do it all the time. It's possible to cross-build not only kernel but whole OS. Building a new kernel is as easy as grabbing the source, then:

./build.sh -m amiga tools
./build.sh -m amiga kernel=GENERIC

And if you want to build everything specify "release" instead of kernel parameter. This process is explained in the documentation.

Does "kldload" not work on NetBSD (eg: kldload xi)?

No, we have something similar on other platforms, but on m68k only statically compiled kernels are supported (no modules).

[gibs]

Hi strim,

I have received the Surecom, it is recognised now

I have a problem: I can't ping from the Amiga the computers in my network or the gateway. But, I can ping from OSX the Amiga.

route show
default 192.168.1.1 UG

ifconfig ne0
inet 192.168.1.68 netmask 0xFFFFFF00 broadcast 192.168.1.255

I have also added the 2 DNS of my provider in /etc/resolv.conf

what is missing ?

Thanks

[strim]

Hmm, it should just work.

If you can ping your Amiga from OS X, then it means that communication works both way (after all, ping is sending icmp echo and waiting for reply from the other machine).

If you have DHCP server on your network then just put into your rc.conf:

rc_configured=YES # if missing or set to NO
ifconfig_ne0="dhcp"

Then do

/etc/rc.d/network restart

All settings will be updated automatically. Alternatively you can just try to use configure the interface from command line.

dhclient ne0

Static configuration (without DHCP) is a bit more complicated:

Set gateway in /etc/rc.conf :

rc_configured=YES
defaultroute="192.168.0.1"

Put interface configuration in /etc/ifconfig.ne0 :

inet 192.168.0.68 netmask 255.255.255.0 up

Put your DNSes into /etc/resolv.conf :

nameserver 192.168.0.1

Then restart network:

/etc/rc.d/network restart

Also... take a look at your dmesg, sometimes ne0 does not get detected due to infamous A1200 PCMCIA card reset bug. Solution is to remove the card and insert it again.

If you are sure that the network setting are OK, then double check configuration on other machines (like firewalls, etc.). Also, what error does ping give when trying to reach other machines?

Now I'm away from my amigas and can't check above examples, but you should get the picture .

[gibs]

I set the network config in dhcp, now it's working.
Therefore I don't know why it wasn't in manual...it was a routing issue.

Well now I can't add the repository

The documentation say:
export PKG_PATH="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD-<RELEASE-NUMBER>/<PORT>/All"
export PKG_PATH

But I get:
"export command not found"

[ahhyes]

Export only works as a command if your shell is bash. If it is csh, then use setenv. Example: setenv CFLAGS "-O3 -ffast-math"

You can use echo $SHELL to find out what your current shell is.

[strim]

Originally Posted by gibs

I set the network config in dhcp, now it's working.
Therefore I don't know why it wasn't in manual...it was a routing issue.

It's documented in rc.conf man page. But it's true that it should be added to the NetBSD guide.

Well now I can't add the repository

The documentation say:
export PKG_PATH="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD-<RELEASE-NUMBER>/<PORT>/All"
export PKG_PATH

But I get:
"export command not found"

The export command must exist since it's an internal bourne shell command, but as ahhyes suggested, you might have csh configured as your shell. You may want to change it to /bin/sh with chsh command if it's set to something else. Also, /bin/bash is not installed by default, but that's unrelated to this problem (just use /bin/sh ).

Proper way to use the export command is:

VARIABLE_NAME=value
export VARIABLE_NAME

(don't do export twice)

By the way, you must use full path in PKG_PATH, variables such as release number and port are to be filled by user in this example, like:

ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amiga/5.1/All/

Notice that path has changed a bit since release of 5.1. This is explained in a README file that lies in an old directory structure . Documentation should probably be updated again...

Also, you'll notice that not so many packages are prebuilt for m68k. That's why it's good to install pkgsrc and build packages on your machine. I've explained this in some previous post .

[ahhyes]

Originally Posted by strim

Hmm, it should just work.

Hi Strim,

I am giving NetBSD a go on my 1200 (Equipped with an 060 (Blizzard 1260, 128MB RAM)).

I think I have gotten the partitioning right. However when I boot from the swap partition (after having written the miniroot.fs), It just bombs with error 2 at the netbsd bootstrap loader. Any ideas? I gather one needs to gunzip the miniroot image, as it was compressed (miniroot.fs.gz). I did this before writing the image

[strim]

Originally Posted by ahhyes

Hi Strim,

I am giving NetBSD a go on my 1200 (Equipped with an 060 (Blizzard 1260, 128MB RAM)).

I think I have gotten the partitioning right. However when I boot from the swap partition (after having written the miniroot.fs), It just bombs with error 2 at the netbsd bootstrap loader. Any ideas? I gather one needs to gunzip the miniroot image, as it was compressed (miniroot.fs.gz). I did this before writing the image

Yes, miniroot should be decompressed.

Error 2 is ENOENT (No such file or directory).

Are you really sure your partitioning setup is right? Double check with HDToolBox if:
- swap partition ID is 0x4e425301
- custom boot code is ON
- reserved blocks on start and end are set to 0
- number of custom boot blocks is to 16
- automount is set to ON

You might have to run xstreamtodev again after correcting it!

The swap partition must be within first 4GB of a disk for bootblocks to work. If it's not, you can try to boot the installation with loadbsd (should be somewhere on installation ISO).

Besides, NetBSD 5 is old. Grab the newest NetBSD 6 beta from this server.

[ahhyes]

Originally Posted by strim

Yes, miniroot should be decompressed.

Error 2 is ENOENT (No such file or directory).

Are you really sure your partitioning setup is right? Double check with HDToolBox if:
- swap partition ID is 0x4e425301
- custom boot code is ON
- reserved blocks on start and end are set to 0
- number of custom boot blocks is to 16
- automount is set to ON

You might have to run xstreamtodev again after correcting it!

The swap partition must be within first 4GB of a disk for bootblocks to work. If it's not, you can try to boot the installation with loadbsd (should be somewhere on installation ISO).

Besides, NetBSD 5 is old. Grab the newest NetBSD 6 beta from this server.

Same issue with 6. Photos of the partitioning included. Where have i gone wrong!

http://ahhyes.net/IMAG0029.jpg
http://ahhyes.net/IMAG0030.jpg

[strim]

Originally Posted by ahhyes

Same issue with 6. Photos of the partitioning included. Where have i gone wrong!

http://ahhyes.net/IMAG0029.jpg
http://ahhyes.net/IMAG0030.jpg

Hmm no idea, it looks good .

How did you use xstreamtodev to transfer miniroot? It should be something like

xstreamtodev --input=miniroot.fs --rdb-name=CDH1

Anyway, do an experiment. Get loadbsd-2.16 and GENERIC kernel image (ungzip it) from distribution. Put them into same directory on AmigaOS. Try to load the kernel with:

loadbsd kernelfile

You might want to use -A parameter to force VGA compatible video mode. Just running loadbsd without any parameters will print possible options.

See if it will boot. Pass wd0b (your swap) as root device to run installer.

[ahhyes]

Originally Posted by strim

Hmm no idea, it looks good .

How did you use xstreamtodev to transfer miniroot? It should be something like

xstreamtodev --input=miniroot.fs --rdb-name=CDH1

Anyway, do an experiment. Get loadbsd-2.16 and GENERIC kernel image (ungzip it) from distribution. Put them into same directory on AmigaOS. Try to load the kernel with:

loadbsd kernelfile

You might want to use -A parameter to force VGA compatible video mode. Just running loadbsd without any parameters will print possible options.

See if it will boot. Pass wd0b (your swap) as root device to run installer.

I used the same arguments to xstreamtodev as you quoted

I'm wondering whether the type of disk drive I am using could be an issue? It's not a real IDE drive:

http://amigakit.leamancomputing.com/...roducts_id=883

Though the Amiga HD Tools had no trouble seeing it..

I'll try the stuff you suggested tomorrow I have the unit at work

[strim]

Originally Posted by ahhyes

I used the same arguments to xstreamtodev as you quoted

I'm wondering whether the type of disk drive I am using could be an issue? It's not a real IDE drive:

http://amigakit.leamancomputing.com/...roducts_id=883

Though the Amiga HD Tools had no trouble seeing it..

I don't think it's a problem. I have the same adapter type in my A600 and it works with the NetBSD.

[ahhyes]

Originally Posted by strim

I don't think it's a problem. I have the same adapter type in my A600 and it works with the NetBSD.

Could it be an issue that xstreamtodev has not written ALL of the minirootfs contents?? I notice the utility goves no indication whether it was successful or not, even with the --verbose option. It wrote for probably about 10 seconds and then just stopped and went back to the amiga cli prompt. I can only assume it worked ok.

I am just wondering what exactly the loader cant find?

[ahhyes]

Originally Posted by ahhyes

Could it be an issue that xstreamtodev has not written ALL of the minirootfs contents?? I notice the utility goves no indication whether it was successful or not, even with the --verbose option. It wrote for probably about 10 seconds and then just stopped and went back to the amiga cli prompt. I can only assume it worked ok.

I am just wondering what exactly the loader cant find?

Could it be any jumper setting on my Blizzard 1260 causing an issue? There is a mapROM jumper setting that supposedly maps ROM to fastram. I wonder if this could be messing anything up?