Re: -CURRENT boot problems: loader, kernel

2001-11-15 Thread Falco Krepel

Yes, Robert wrote:

Looks like it was a delayed affect of the awk change; recovering via
/boot/loader.old and rebuilding and installing src/sys seemed to get
things under control.

This solve the problem.

-- 
Falco KrepelPhone:  +49-(0)30-3463-7276
Fraunhofer FOKUSFax:+49-(0)30-3463-8276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.fhg.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: pxeboot doesn't work anymore

2001-07-17 Thread Falco Krepel

I use FreeBSD 5.0.

Falco Krepel wrote:
 
 I use the 3COM 3C905c TX-M with bootrom (PXE v2.20, MBA v4.30). Some
 time after 2001-05-14 the pxeboot is not working anymore.
 
 I have the following behavior:
 
 1. The client gets his IP address and bootfile with DHCP.
 2. TFTP starts with downloading the pxeboot and after approximatly 1
 kbyte it stops and on the entire display, colored and flashing
 characters appear.
 
 I have no idea where the problem could be, because the pxeboot changes
 are only minor changes. Maybe somebody could help me.
 
 Thanx,
 
 Falco

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



new rc.diskless{1,2} files

2001-03-30 Thread Falco Krepel

I have implemented good ideas from Mike Smith in my
rc.diskless{1,2} files and make some other changes:

1. Now I use the kernel flag vm.nswapdev to determine if swap is
available.

2. To determine if DEVFS are used I check the kernel flag
vfs.devfs.generation as it done within the /etc/rc file.

3. I write chk_err and mkmd functions also in rc.diskless2 because
the rc.diskless2 file is executed in the rc file: sh rc.diskless2
When you change this call to . rc.diskless2 than the mkmd function
from rc.diskless2 could replace the mkmd function in rc.diskless1. The
chk_err function in rc.diskless2 could be deleted.

The following knobs must be added in the rc.conf:

diskless_var_size=32m
diskless_tmp_enable=NO
diskless_tmp_size=32m
diskless_dev_size=2m

I am attaching the files here for those interested. Any comments are
welcome.

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

# Copyright (c) 1999  Matt Dillion
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
# $FreeBSD: src/etc/rc.diskless1,v 1.6 2000/10/08 19:18:24 obrien Exp $
#

#
# /etc/rc.diskless1 - general BOOTP startup
#
# BOOTP has mounted / for us.  Assume a read-only mount.  We must then
# - figure out our IP by querying the interface
# - fill /conf/etc (writable) with files from /etc, and then update
#   per-machine files from /conf/*/ where * is the IP of the host,
#   the IP of the subnet, default, or nothing.
# - mount /conf/etc over /etc so we can see the new files.
#
# WARNING: i thing you should not change /etc/rc or strange things could
# happen.
#
# The operator is in charge of setting /conf/*/etc/* things as appropriate.
# Typically rc.conf and fstab need to be changed, but possibly
# also other files such as inetd.conf etc.

# chkerr:
#
# Routine to check for error
#
#   checks error code and drops into shell on failure.
#   if shell exits, terminates script as well as /etc/rc.
#
chkerr() {
case $1 in
0)
;;
*)
echo $2 failed: dropping into /bin/sh
/bin/sh
# RESUME
;;
esac
}

# mkmd:
#
# Builds an md(4) disk of the size in $1
# Labels and newfs' it.
# Mounts it on the destination in $2
# Returns the name of the created md device in md_device
# Returns the name of the device containing the filesystem in md_filesystem
mkmd() {
md_device=`mdconfig -a -t malloc -s $1`
chkerr $? configuring md device
disklabel -rw $md_device auto
chkerr $? labelling md device
md_filesystem=/dev/$md_devicec
newfs $md_filesystem 21 /dev/null
chkerr $? making md device filesystem
mount $md_filesystem $2
chkerr $? mounting md filesystem on $2
}

# DEBUGGING
#
# set -v

# Figure out our interface and IP.
#
bootp_ifc=
bootp_ipa=
bootp_ipbca=
iflist=`ifconfig -l`
for i in ${iflist} ; do
set `ifconfig ${i}`
while [ $# -ge 1 ] ; do
if [ ${bootp_ifc} =  -a $1 = inet ] ; then
bootp_ifc=${i} ; bootp_ipa=${2} ; shift
fi
if [ ${bootp_ipbca} =  -a $1 = broadcast ] ; then
bootp_ipbca=$2; shift
fi
shift
done
if [ ${bootp_ifc} !=  ] ; then
break
fi
done
echo Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipbca}
 
# Files in /etc are copied to /conf/etc which is writable. Then
# per-machine configs from /conf/ip.address/etc are copied onto this
# directory. First choice is using the client's IP, then the client's
# broadcast address

Re: use md device in /etc/rc.diskless{1,2}

2001-03-26 Thread Falco Krepel

I sent a patch request:

http://www.freebsd.org/cgi/query-pr.cgi?pr=25730

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: use md device in /etc/rc.diskless{1,2}

2001-03-26 Thread Falco Krepel

I have sent a patch request:

http://www.freebsd.org/cgi/query-pr.cgi?pr=25730

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: use md device in /etc/rc.diskless{1,2}

2001-03-26 Thread Falco Krepel

This is a fine solution. I hope it's OK when I add this to my patch
request.

But I have two remarks.

1. For example you could use the diskless boot procedure for smart
clients with a small disk used as swap space. So I think it is better to
use swap instead of malloc for var,dev, and tmp. This could be done with
a variable (e.g. diskless_swap_enable). What do think about it?

2. Building a dev dir is obsolete when you use DEVFS. So you should
distinguish between these two  situations. I don't know if you could use
one of the "vfs.devfs.*" variables to determine the usage of DEVFS.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ahc driver: aic7892 no longer supported

2001-03-22 Thread Falco Krepel

"Justin T. Gibbs" wrote:

In aic7xxx_pci.c:ahc_pci_config() the call to ahc_pci_map_int(ahc) is
failing.  bus_alloc_resource() appears to need more time than I have
right now so that will have to wait till tonight :-)  It does look like
a more fundamental problem below the scsi driver is involved.

I have the same problem: the call to ahc_pci_map_int(ahc) is failing.

The following function call returns NULL in ahc_pci.c:

208 ahc-platform_data-irq =
209 bus_alloc_resource(ahc-dev_softc, SYS_RES_IRQ, zero,
2100, ~0, 1, RF_ACTIVE | RF_SHAREABLE);

This function is in pci.c:

1192 static struct resource *
1193 pci_alloc_resource(device_t dev, device_t child, int type, int
*rid,
1194u_long start, u_long end, u_long count, u_int
flags)  
1195 {
1196 struct pci_devinfo *dinfo = device_get_ivars(child);
1197 struct resource_list *rl = dinfo-resources;
1198 pcicfgregs *cfg = dinfo-cfg;
1199
1200 /*
1201  * Perform lazy resource allocation
1202  *
1203  * XXX add support here for SYS_RES_IOPORT and
SYS_RES_MEMORY
1204  */
1205 if (device_get_parent(child) == dev) {
1206  /*
1207  * If device doesn't have an interrupt routed, and
is deserving of
1208  * an interrupt, try to assign it one.
1209  */

...

1219 }
1220
1221 return resource_list_alloc(rl, dev, child, type, rid,
1222start, end, count, flags);
1223 }

The device must have an interrupt routed due to the deleted code
fragment were not executed. So I think this must be a problem within the
the pci resource allocation procedure. Put I don't know how this works.
So it is difficult for me to find the error.

Maybe you have an idea, where the problem is. I try to find out at which
day this error occur to find out which changes were made.

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ahc driver: aic7892 no longer supported (conflict with ATA)

2001-03-22 Thread Falco Krepel

I think I found the problem. The problem occur since 03/14/2001. The
following files could be infvolved:

P dev/ata/ata-all.c
P dev/ata/ata-all.h
P dev/ata/ata-disk.c
P dev/ata/ata-disk.h
P dev/ata/atapi-all.c
P dev/ata/atapi-all.h
P dev/ata/atapi-cd.c
P dev/ata/atapi-cd.h
P dev/ata/atapi-fd.c
P dev/ata/atapi-fd.h
P dev/ata/atapi-tape.c
P dev/ata/atapi-tape.h

It should be somthing in ata-all.c. Because since 03/14 the ata1 probe
doesn't fail and uses irq 15 same as the ahc. But this shouldn't be a
problem. I am right?

= boot failed (since 03/14/2001)

atapci0: VIA 82C686 ATA100 controller port 0xd000-0xd00f at device 7.1
on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000
ata0: mask=03 status0=50 status1=00
ata0-master: ATAPI probe 14 eb
ata0-slave: ATAPI probe 14 eb
ata0: mask=03 status0=10 status1=00
ata0: devices=0c
ata0: at 0x1f0 irq 14 on atapci0
ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008
ata1: at 0x170 irq 15 on atapci0
pci0: bridge, PCI-unknown at 7.4 (no driver attached)
ahc0: Adaptec 29160 Ultra160 SCSI adapter port 0xdc00-0xdcff mem
0xdf00-0xdf000fff irq 15 at device 9.0 on pci0
ahc0: Platform free
device_probe_and_attach: ahc0 attach returned 12

= boot working (03/13/2001 and before)

atapci0: VIA 82C686 ATA100 controller port 0xd000-0xd00f at device 7.1
on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd000
ata0: mask=03 status0=50 status1=00
ata0: mask=03 ostat0=50 ostat2=00
ata0-master: ATAPI probe a=14 b=eb
ata0-slave: ATAPI probe a=14 b=eb
ata0: mask=03 status0=10 status1=00
ata0: devices=0c
ata0: at 0x1f0 irq 14 on atapci0
ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd008
ata1: mask=00 status0=ff status1=ff
ata1: probe allocation failed
pci0: bridge, PCI-unknown at 7.4 (no driver attached)
ahc0: Adaptec 29160 Ultra160 SCSI adapter port 0xdc00-0xdcff mem
0xdf00-0xdf000fff irq 15 at device 9.0 on pci0
ahc0: Reading SEEPROM...done.
ahc0: BIOS eeprom is present
ahc0: Secondary High byte termination Enabled
ahc0: Secondary Low byte termination Enabled
ahc0: Primary Low Byte termination Enabled
ahc0: Primary High Byte termination Enabled
ahc0: Downloading Sequencer Program... 424 instructions downloaded
aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs

-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ahc driver: aic7892 no longer supported

2001-03-20 Thread Falco Krepel

Dear Justin,

Since the update around the middle of feb of the ahc driver the aic7892
chip is no longer supported correctly. The same card with aic7870 is
working as usual. So I think that this is the problem. The snapshot
(2001/02/10) of the current version is OK.

I get the following boot messages:

### boot after update:

ahc0: Adaptec 29160 Ultra160 SCSI adapter port 0xdc00-0xdcff mem
0xdf00-0xdf000fff irq 15 at device 9.0 on pci0
ahc0: Platform free
device_probe_and_attach: ahc0 attach returned 12

.
.
.

acd0: CDROM ...
Mounting root from ufs:/dev/da0s1a
setroot byname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6


### boot before update:

ahc0: Adaptec 29160 Ultra160 SCSI adapter port 0xdc00-0xdcff mem
0xdf00-0xdf000fff irq 15 at device 9.0 on pci0
aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs

Do you have any idea?


-- 
Falco KrepelPhone:  +49-(0)30 - 34 63 - 7 276
GMD-FOKUS   Fax:+49-(0)30 - 34 63 - 8 276
Kaiserin-Augusta-Allee 31   e-mail: [EMAIL PROTECTED]
10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ahc driver: aic7892 no longer supported

2001-03-20 Thread Falco Krepel

### 29160 BIOS v.2.57.2

### pciconf

aries# pciconf -l
hostb0@pci0:0:0:class=0x06 card=0x chip=0x03051106
rev=0x02 hdr=0x00
pcib1@pci0:1:0: class=0x060400 card=0x0080 chip=0x83051106 rev=0x00
hdr=0x01
isab0@pci0:7:0: class=0x060100 card=0x1106 chip=0x06861106 rev=0x40
hdr=0x00
atapci0@pci0:7:1:   class=0x01018a card=0x05711106 chip=0x05711106
rev=0x06 hdr=0x00
none0@pci0:7:4: class=0x068000 card=0x30571106 chip=0x30571106 rev=0x40
hdr=0x00
ahc0@pci0:9:0:  class=0x01 card=0xe2a09005 chip=0x00809005 rev=0x02
hdr=0x00
xl0@pci0:11:0:  class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x74
hdr=0x00
xl1@pci0:13:0:  class=0x02 card=0x100010b7 chip=0x920010b7 rev=0x74
hdr=0x00
none1@pci1:0:0: class=0x03 card=0x40151043 chip=0x011010de rev=0xa1
hdr=0x00
aries# 

### cvs status

File: ahc_eisa.cStatus: Up-to-date

   Working revision:1.21
   Repository revision: 1.21   
/usr/ncvs/src/sys/dev/aic7xxx/ahc_eisa.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: ahc_pci.c Status: Up-to-date

   Working revision:1.41
   Repository revision: 1.41   
/usr/ncvs/src/sys/dev/aic7xxx/ahc_pci.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7770.c Status: Up-to-date

   Working revision:1.4
   Repository revision: 1.4
/usr/ncvs/src/sys/dev/aic7xxx/aic7770.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

=
==
File: aic7xxx.c Status: Up-to-date

   Working revision:1.71
   Repository revision: 1.71   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx.h Status: Up-to-date
 
   Working revision:1.37
   Repository revision: 1.37   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx.h,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx.reg   Status: Up-to-date

   Working revision:1.35
   Repository revision: 1.35   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx.reg,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx.seq   Status: Up-to-date

   Working revision:1.113
   Repository revision: 1.113  
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx.seq,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_93cx6.c   Status: Up-to-date

   Working revision:1.13
   Repository revision: 1.13   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_93cx6.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_93cx6.h   Status: Up-to-date

   Working revision:1.9
   Repository revision: 1.9
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_93cx6.h,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_freebsd.c Status: Up-to-date

   Working revision:1.23
   Repository revision: 1.23   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_freebsd.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_freebsd.h Status: Up-to-date

   Working revision:1.8
   Repository revision: 1.8
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_freebsd.h,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_inline.h  Status: Up-to-date

   Working revision:1.14
   Repository revision: 1.14   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_inline.h,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)

===
File: aic7xxx_pci.c Status: Up-to-date

   Working revision:1.13
   Repository revision: 1.13   
/usr/ncvs/src/sys/dev/aic7xxx/aic7xxx_pci.c,v
   Sticky Tag:  (none)
   Sticky Date: 2001.03.18.23.00.00
   Sticky Options:  (none)