Nick Nauwelaerts <nickwanadoo.be> writes:

> This is expected. 3.0 install media are hardwired for etc30.tgz,
> comp30.tgz etcetera. Even if you point it to the 3.1 directory on the
> FTP servers this is still no-go.
>
> Here's a usefull hint:
>
> * Download 3.1's bsd.rd
> * copy it to /
> * reboot
> * at the boot> prompt, type bsd.rd to boot the ramdisk

Thanks Nick, good to know. I managed to figure out I needed to edit
`install.sub' and change the version. Once that was done I could
proceed with no further trouble. At least not with the install.

But bad things happen to my network after the install is done and a
reboot occurs. The network data looks good to me but I'm not sure
what to look for. It appears I have a configured ethernet devcie
(xl0) a gateway and a correct /etc/resolv.conf

I first tried a redoing the install since it is fairly fast and easy.
And took that opertunity to download bsd.rd after the second install
and before rebooting the new installation. So I have it on board but
haven't used for anything yet.

Maybe some driver is not present or something but I'd think that
would show problems with ifconfig output,

It seems like the same settings that worked fine for a network
install now fail on reboot. Any network activity like trying a ping
prodoces `watchdog timeout' messages. But no working connection.
I'm thinking its kernel related since that is what is changed from
teh initial install media.

I've include a fair bit of data below but did make an effort to trim
out unnecessay stuff. Various bits of data are seperated by
delimiters (-- )

Included is output of:
  uname -a
  ifconfig -a
  route -n show
  netstat -nr
  arp -n -a
=====
contents of files:
  mygate
  myname
  hostname.xl0
  resolv.conf
  networks
  hosts
=============

uname -a
OpenBSD huey.local.lan 3.1 GENERIC#59 i386

-- 
cat hostname.xl0
inet 192.168.1.10 0xffffff00 NONE media autoselect
-- 
cat mygate
192.168.1.1
-- 
cat myname:
huey.local.lan
-- 
cat /etc/hosts:
127.0.0.1 localhost
192.168.1.10 huey.local.lan. huey
-- 
cat networks:
#	$OpenBSD: networks,v 1.5 1997/09/15 09:54:52 deraadt Exp $
#
# Internet networks (from nic.ddn.mil)
# 1) The multicast network
BASE-ADDRESS.MCAST.NET	224
loopback		127	loop
# Your subnets follow...
192.168.1.0
-- 
route -n show:
Routing tables
Internet:
Destination      Gateway            Flags 
default          192.168.1.1        UG     
127.0.0.0        127.0.0.1          UG     
127.0.0.1        127.0.0.1          UH     
192.168.1.0      link#1             U      
192.168.1.1      0:a0:cc:59:6b:fc   UH     
192.168.1.10     127.0.0.1          UGH    
224.0.0.0        127.0.0.1          U      
[...] snipped ipv6 stuff.
-- 
ifconfig -a:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
	inet6 ::1 prefixlen 128
	inet 127.0.0.1 netmask 0xff000000 
lo1: flags=8008<LOOPBACK,MULTICAST> mtu 33224
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	media: Ethernet autoselect (100baseTX)
	status: active
	inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
	inet6 fe80::201:2ff:feed:568a%xl0 prefixlen 64 scopeid 0x1
[...] skipped list of other interfaces
-- 
arp -n -a:
? (192.168.1.1) at 00:a0:cc:59:6b:fc
-- 
netstat -nr:
Routing tables
Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            192.168.1.1        UGS         0       12   1500   xl0
127/8              127.0.0.1          UGRS        0        0  33224   lo0
127.0.0.1          127.0.0.1          UH          3       24  33224   lo0
192.168.1/24       link#1             UC          0        0   1500   xl0
192.168.1.1        0:a0:cc:59:6b:fc   UHL         1        0   1500   xl0
192.168.1.10       127.0.0.1          UGHS        0        0  33224   lo0
224/4              127.0.0.1          URS         0        0  33224   lo0
[...] snipped ipv6 output

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]