Groups | Search | Server Info | Login | Register

Groups > comp.os.minix > #2579

Re: Lost Post..

Show all headers | View raw

Wilhelm Greiner <wilhelm.greiner@web.de> writes:

> If you read it, please can you repost it? :) - I lost it without tried
> your solution.

You can ask your newsreader to show old articles. How to do that depends
on the newsreader. Looks like they were from Oct. 2025. They don't
disappear; they are still on the news server. It was probably one of
these:



From: Peter 'Shaggy' Haywood <phaywood@alphalink.com.au>
Subject: Re: Minix2 Network config?
Newsgroups: comp.os.minix
Date: Sun, 12 Oct 2025 10:44:58 +1100 (13 weeks, 1 day, 17 hours ago)
Organization: A noiseless patient Spider

  Sorry for taking so long to get back to you! I've been busy with other
things.

Groovy hepcat Wilhelm Greiner was jivin' in comp.os.minix on Fri, 3 Oct
2025 05:27 am. It's a cool scene! Dig it.

> Find it how to set it statically, but for documentation
> reasons i reinstalled the system and now i have a problem,

  You didn't need to reinstall the whole system, just install the man
pages.

> it panic()s at boot with:
> panic at mnx_eth.c, 44

  First of all, I should point out that I'm not a minix expert by any
means.
  I don't know why you're getting this problem. I've never seen this
before. Perhaps a reinstallation error.
  If there's anyone lurking here who's more knowlegable and has some
insight into Wilhelm's problem, please chime in.

> Below are all Files, dont know how to repair that.
> Also a new install ends in the same situation.
> 
> Have also tried to recompile "inet" - but binary is
> completely the same, no changes.
> 
> Thanks for all Idead, Wilhelm
> 
> /etc/inet.conf:
> eth0 WDETH 0 { default; };
> 
> /etc/rc.net (same without it (dhcp)):
> ifconfig -h 192.168.0.19 -n 255.255.255.0 -m 1400
> add_route -g 192.168.0.1 -m 25

  The add_route command doesn't have a -m option. I tried this
configuration on my system to see what would happen, and add_route
fails with an error message (but not the one you're getting), and
pr_routes yields no routes.
  The man page says:

*********************************************************************
ADD_ROUTE(8)              Minix Programmer's Manual              
ADD_ROUTE(8)


NAME
     add_route - configure IP routing.

SYNOPSIS
     add_route -g gateway [-d destination [-n netmask ]] [-i ip device]

DESCRIPTION
     Add_route is used for manual entry of routes in the IP routing
table.

OPTIONS

     -g   gateway specifies the gateway IP address to use.

     -d   destination specifies the destination(s) reached via this
gateway.

     -n   netmask specifies a netmask when the destination is a net.

     -i   ip device specifies the ip device.

SEE ALSO
     irdp(8), pr_routes(8).

AUTHOR
     Add_route.c was created August 7, 1991 by  Philip  Homburg.  This 
manual
     page by A. S. Woodhull, last revised 13.02.96.
*********************************************************************

  You can specify a destination in CIDR notation with the -d option, or
in separate destination and netmask format with the -d and -n options,
although it will default to 0.0.0.0/0 if not specified. 

add_route -g 192.168.0.19 -d 0.0.0.0/0

> daemonize nonamed
> #daemonize talkd
> daemonize tcpd shell in.rshd
> daemonize tcpd login in.rlogind
> daemonize tcpd telnet in.telnetd
> #daemonize tcpd ftp in.ftpd

  Do you have a /etc/hosts file? If you have a DNS server on your
network, put an entry for it in this file:

192.168.1.1 %nameserver

Otherwise just put in an entry for each node on the network:

192.168.1.1 foo.local
192.168.1.2 bar.local
192.168.1.3 baz.local

> Boot Vars - "T" is the one to try net:
> 
> Boot parameters editor.
> c0d0p1s0>set
> rootdev = c0d0p1s0
> ramimagedev = c0d0p1s0
> ramsize = 512
> processor = (?)
> bus = (?)
> video = (?)
> chrome = (?)
> memory = (?)
> c0 = (?)
> image = (minix)
> leader() echo \cMinix boot monitor \v\n\nPress ESC to enter the
> monitor main() menu
> trailer() echo \c
> d(d,Dos) {boot c0d0p0}
> m(m,Minix) {boot}
> T(T,Minix Test) {net_on;boot}
> net_on() {servers=inet;DPETH=300:10;image=/minix/minix}
> rescue() {image=/minix/2.0.4}
> R(R,Rescue Minix) {rescue;boot}

  I'm not sure whether this makes any difference, but you seem to have
three different kernel image specifications; the default (image =
(minix)), the one specified in net_on (image=/minix/minix) and the one
specified in rescue (image=/minix/2.0.4). If pressing m at the boot
menu works you might remove the image specification for net_on and use
the default image. Otherwise you might change it to image=/minix/2.0.4,
if pressing T works.
  Here's what I have:

rootdev = c0d0p0s0
ramimagedev = c0d0p0s0
ramsize = (0)
processor = (286)
bus = (at)
video = (vga)
chrome = (color)
memory = (800:92290,100000:300000)
c0 = (at)
image = (minix)
leader() echo \cMinix boot monitor \v\n\nPress ESC to enter the monitor
main() menu
main {trap 5000 boot:c0d0p1}
trailer() echo \c
dos(d,MS-DOS 6.20) boot c0d0p1
minix(m,minix 2.0.4) boot
DPETH0 = 300:5
servers = inet




  I've been thinking about your problem, and I'm not sure, but I may
have found the cause. There seems to be an error in your setup that I
didn't spot before. Here's what I have in my boot params:

DPETH0 = 300:5

And here's what you have in yours:

DPETH = 300:5

The difference is that you have not specified the network card number.
There must be a number; 0 for the first card, 1 for the second, 2 for
the third, etc.


-- 
PGP Key ID: 781C A3E2 C6ED 70A6 B356  7AF5 B510 542E D460 5CAE
       "The Internet should always be the Wild West!"

Back to comp.os.minix | Previous — Previous in thread | Find similar

Thread

Lost Post.. Wilhelm Greiner <wilhelm.greiner@web.de> - 2026-01-10 18:22 +0100
  Re: Lost Post.. jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-12 12:09 -0500

csiph-web