From owner-freebsd-alpha Sun Apr 16 13:14:49 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 92DC137BA8B for ; Sun, 16 Apr 2000 13:14:41 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 4423 invoked by uid 0); 16 Apr 2000 20:14:39 -0000 Received: from vador.aoc.clarkson.edu (128.153.130.33) by mail.clarkson.edu with SMTP; 16 Apr 2000 20:14:39 -0000 Date: Sun, 16 Apr 2000 16:13:09 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@vador.aoc.clarkson.edu To: freebsd-alpha@freebsd.org Subject: modload/arla Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, this may be a dumb question, but I just installed arla from the ports collection and it relies on modload. Where is modload located? -Todd --------------------------------------------------- http://www.clarkson.edu/~cohentl "Sometimes crazy things happen in circuits." - Muku, 1999 "The answers to lifes problems aren't at the bottom of bottles, they're on TV" - Homer J. Simpson --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 17 1:19:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id BCC0337BAAA for ; Mon, 17 Apr 2000 01:19:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12h6kS-000DQM-0K; Mon, 17 Apr 2000 08:19:12 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA90463; Mon, 17 Apr 2000 09:26:50 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 Apr 2000 09:24:55 +0100 (BST) From: Doug Rabson To: Todd Cohen Cc: freebsd-alpha@freebsd.org Subject: Re: modload/arla In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 16 Apr 2000, Todd Cohen wrote: > Ok, this may be a dumb question, but I just installed arla from the ports > collection and it relies on modload. Where is modload located? There is no longer any such thing as modload. Since FreeBSD 3.0, we have used a different system for loading kernel modules called KLD. See kldload(8) for details. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Apr 17 3:57:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.toplink.net (mail.toplink.net [195.2.171.8]) by hub.freebsd.org (Postfix) with ESMTP id 2642A37B585 for ; Mon, 17 Apr 2000 03:57:19 -0700 (PDT) (envelope-from kschmidt@gdimbh.de) Received: from besuux01.bechtle.de (gdi-gw.customer.toplink.net [195.2.170.58]) by mail.toplink.net (8.9.3/8.9.3) with ESMTP id MAA14484 for ; Mon, 17 Apr 2000 12:57:13 +0200 (CEST) Received: from gdimbh.de ([10.31.1.101]) by besuux01.bechtle.de (8.9.3/8.9.3) with SMTP id MAA26211 for ; Mon, 17 Apr 2000 12:58:50 +0200 Message-Id: <200004171058.MAA26211@besuux01.bechtle.de> Date: Mon, 17 Apr 2000 12:50:46 +0200 From: Kai Schmidt Reply-To: Kai Schmidt To: freebsd-alpha@FreeBSD.ORG Subject: Weird things happening X-Mailer: Kai Schmidt's registered AK-Mail 3.0b [ger] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I tried to install FreeBSD Alpha 4.0 on a UDB Mulita, after I successfully installed several boxes I thought this might not be a big problem. I got the ISO image from the net and created the cd which installs fine on a PWS. When I use 4.0 floppies to boou the mulita the system falls over. I got the 3.4 disk from the net, the booting works without any problems. The CD seems to install fine. Than the install stops with an MAKEDEV error and all processes die with a core dump. I decided to go back to 3.1 which I installed succesfully on two other multias, the install works fine but when rebooting I end up in single user mode. Any hints? Oh by the way, where doc I enable the getty on a serial console, I forgot and can't find the mail! Even a search on my working multia shows nothing! Regards Kai-- Kai Schmidt GDI mbH http://www.gdimbh.de Robert-Bosch-Strasse 5 72172 Sulz am Neckar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 9:44:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 3A1FD37B9E1 for ; Tue, 18 Apr 2000 09:44:11 -0700 (PDT) (envelope-from matt@thebiz.net) Received: (qmail 946 invoked from network); 18 Apr 2000 12:44:09 -0400 Received: from mail1.thebiz.net (172.16.0.179) by mx1.thebiz.net with SMTP; 18 Apr 2000 12:44:09 -0400 Received: (qmail 7304 invoked by uid 0); 18 Apr 2000 12:44:09 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.thebiz.net with SMTP; 18 Apr 2000 12:44:09 -0400 Message-ID: <00c501bfa955$203546e0$1401eed8@mahatma> From: "Matthew Zahorik" To: Subject: HELP! Date: Tue, 18 Apr 2000 12:42:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a reliable kernel panic when copying a file. These are diskless servers. /etc is a MFS filesystem. /sandbox/etc is NFS mounted. [shell1]:DING~:~# cd /sandbox/etc [shell1]:12:00pm:/sandobx/etc# cp /etc/sshd_config . fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0x0 a1 = 0x1 a2 = 0xffffffffffffffff pc = 0x0 ra = 0x1 curproc = 0xfffffe0011456e00 pid = 338, comm = cp ddbprinttrap from 0x0 ddbprinttrap(0x0, 0x1, 0xffffffffffffffff, 0x2) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe0012afd3f0>\ db> trace Debugger() at Debugger+0x2c panic() at panic+0x100 trap() at trap+0x610 XentMM() at XentMM+0x20 (null) at 0x1 db> You can cat/more, ls -l, and otherwise manipulate the file. You can't copy it for the life of me. (I haven't tried mv'ing it) I tried different destinations, like cp /etc/sshd_config /tmp and that still crashes. This was a 4.0-RELEASE kernel. I CVS'd out the current kernel (cd /usr/src, cvs co sys) just a couple of moments ago and tried that - no change, so it's not a bug that has a fix recently committed. These machines were really close to hitting production with FreeBSD instead of Linux on them, but I can't have people rebooting the machines at will (: Any pointers would be appreciated so I can fix this quickly. There's no PC, or any other address that points to the bad code, so I really can't track it down. Something is getting a null pointer, and crashing. Since it's bringing down the machine, I assume it is in the kernel space. (I assume a null pointer access in user space can't bring the machine down) My gut tells me it's MFS related. I can't reproduce this on my Intel boxes - either the bug doesn't exist or the setup isn't identical. - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 10: 5:40 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id BDAAC37BA86 for ; Tue, 18 Apr 2000 10:05:35 -0700 (PDT) (envelope-from maz@albany.net) Received: (qmail 21784 invoked from network); 18 Apr 2000 13:05:32 -0400 Received: from mail1.thebiz.net (172.16.0.179) by mx1.thebiz.net with SMTP; 18 Apr 2000 13:05:32 -0400 Received: (qmail 14409 invoked by uid 0); 18 Apr 2000 13:05:32 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.albany.net with SMTP; 18 Apr 2000 13:05:32 -0400 Message-ID: <00ff01bfa958$1d7c3a00$1401eed8@mahatma> From: "Matthew Zahorik" To: References: <00c501bfa955$203546e0$1401eed8@mahatma> Subject: Re: HELP! Date: Tue, 18 Apr 2000 13:04:10 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A slight update. This works. [shell1]:12:55pm:/etc# mv sshd_config sshd_config2 [shell1]:12:55pm:/etc# cp sshd_config2 /tmp [shell1]:12:55pm:/etc# mv sshd_config2 sshd_config [shell1]:12:55pm:/etc# cp sshd_config /tmp [shell1]:12:56pm:/etc# _ Works fine. But, after the machine freshly reboots: [shell1]:12:58pm:/etc# cp sshd_config /tmp crashes instantly. Weird, strange, and unusual. sshd_config is copied in /etc/rc.local from /usr/local/etc/sshd_config with this bit of code: #!/bin/sh cp /usr/local/etc/sshd_config /etc/sshd_config ifconfig -a | grep inet | head -2 | awk '{printf("ListenAddress %s\n",$2);}' \ >>/etc/sshd_config cp /usr/local/etc/ssh_host_key /etc/ssh_host_key /usr/local/sbin/sshd -f /etc/sshd_config echo -n ' sshd' - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 ----- Original Message ----- From: "Matthew Zahorik" To: Sent: Tuesday, April 18, 2000 12:42 PM Subject: HELP! : I have a reliable kernel panic when copying a file. : : These are diskless servers. /etc is a MFS filesystem. /sandbox/etc is NFS : mounted. : : [shell1]:DING~:~# cd /sandbox/etc : [shell1]:12:00pm:/sandobx/etc# cp /etc/sshd_config . : : fatal kernel trap: : : trap entry = 0x2 (memory management fault) : a0 = 0x0 : a1 = 0x1 : a2 = 0xffffffffffffffff : pc = 0x0 : ra = 0x1 : curproc = 0xfffffe0011456e00 : pid = 338, comm = cp : : ddbprinttrap from 0x0 : ddbprinttrap(0x0, 0x1, 0xffffffffffffffff, 0x2) : panic: trap : panic : Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe0012afd3f0>\ : : db> trace : Debugger() at Debugger+0x2c : panic() at panic+0x100 : trap() at trap+0x610 : XentMM() at XentMM+0x20 : (null) at 0x1 : db> : : You can cat/more, ls -l, and otherwise manipulate the file. You can't copy : it for the life of me. (I haven't tried mv'ing it) : : I tried different destinations, like cp /etc/sshd_config /tmp and that : still crashes. : : This was a 4.0-RELEASE kernel. I CVS'd out the current kernel (cd /usr/src, : cvs co sys) just a couple of moments ago and tried that - no change, so it's : not a bug that has a fix recently committed. : : These machines were really close to hitting production with FreeBSD instead : of Linux on them, but I can't have people rebooting the machines at will (: : Any pointers would be appreciated so I can fix this quickly. : : There's no PC, or any other address that points to the bad code, so I really : can't track it down. Something is getting a null pointer, and crashing. : Since it's bringing down the machine, I assume it is in the kernel space. (I : assume a null pointer access in user space can't bring the machine down) My : gut tells me it's MFS related. : : I can't reproduce this on my Intel boxes - either the bug doesn't exist or : the setup isn't identical. : : - Matt : : -- : Matthew Zahorik Director of Systems and Networking - BiznessOnline.com : matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary : maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 : : : : To Unsubscribe: send mail to majordomo@FreeBSD.org : with "unsubscribe freebsd-alpha" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 11:18:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 71A3837B506 for ; Tue, 18 Apr 2000 11:18:21 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA17377; Tue, 18 Apr 2000 14:18:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA96402; Tue, 18 Apr 2000 14:18:18 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Apr 2000 14:18:17 -0400 (EDT) To: "Matthew Zahorik" Cc: Subject: Re: HELP! In-Reply-To: <00c501bfa955$203546e0$1401eed8@mahatma> References: <00c501bfa955$203546e0$1401eed8@mahatma> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14588.42187.126783.219096@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Zahorik writes: > I have a reliable kernel panic when copying a file. > > These are diskless servers. /etc is a MFS filesystem. /sandbox/etc is NFS > mounted. > > [shell1]:DING~:~# cd /sandbox/etc > [shell1]:12:00pm:/sandobx/etc# cp /etc/sshd_config . > > fatal kernel trap: > > trap entry = 0x2 (memory management fault) > a0 = 0x0 > a1 = 0x1 > a2 = 0xffffffffffffffff > pc = 0x0 > ra = 0x1 > curproc = 0xfffffe0011456e00 > pid = 338, comm = cp > > The values in the RA & PC are probably accurate & they could indicate that something followed a null function pointer. Maybe you could provide more details? Like kldstat output & perhaps the output from either mount or df? Is either NFS or MFS loaded as a module? Are you certain your modules match your kernel? If they or anything else is loaded as a module, can you try compiling everything (but osf/1) into your kernel statically? I think I've at least partially replicated your environment, and I cannot duplicate this crash: <2:11pm>vivaldi/gallatin:~>df -h . /tmp Filesystem Size Used Avail Capacity Mounted on locus:/cs/locus/home1 9.9G 4.9G 4.9G 50% /a/locus/cs/locus/home1 mfs:22 124M 4.3M 110M 4% /tmp <2:11pm>vivaldi/gallatin:~>uname -srm FreeBSD 4.0-RELEASE alpha <2:11pm>vivaldi/gallatin:~>sysctl hw.model hw.model: COMPAQ AlphaServer DS10 466 MHz <2:11pm>vivaldi/gallatin:~>cp /tmp/sshd_config . <2:11pm>vivaldi/gallatin:~>kldstat Id Refs Address Size Name 1 2 0xfffffc0000300000 314ae8 kernel 2 1 0xfffffe000204c000 22000 osf1.ko Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 11:28:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 2B07C37BB43 for ; Tue, 18 Apr 2000 11:28:09 -0700 (PDT) (envelope-from maz@albany.net) Received: (qmail 19844 invoked from network); 18 Apr 2000 14:28:05 -0400 Received: from mail1.thebiz.net (172.16.0.179) by mx1.thebiz.net with SMTP; 18 Apr 2000 14:28:05 -0400 Received: (qmail 9740 invoked by uid 0); 18 Apr 2000 14:28:05 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.albany.net with SMTP; 18 Apr 2000 14:28:05 -0400 Message-ID: <014501bfa963$a5609550$1401eed8@mahatma> From: "Matthew Zahorik" To: "Andrew Gallatin" Cc: References: <00c501bfa955$203546e0$1401eed8@mahatma> <14588.42187.126783.219096@grasshopper.cs.duke.edu> Subject: Re: HELP! Date: Tue, 18 Apr 2000 14:26:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : The values in the RA & PC are probably accurate & they could indicate : that something followed a null function pointer. I would assume it's a kernel function. I naively assume a long jump to a null pointer in user space would result in the crash of the user program (cp in this instance) but not a kernel panic. : Maybe you could provide more details? Like kldstat output & perhaps Sure! I can even provide you with a login to that box if you so desire. I'll disable the mount of swap and you can get crash dumps too. : module? Are you certain your modules match your kernel? If they or : anything else is loaded as a module, can you try compiling everything : (but osf/1) into your kernel statically? Everything is static. I was agressive with the removal of things from my kernel config, but I don't think I nuked anything something else was depending on. Removing things like FFS_ROOT may have very creepy side effects. It has been running fine up to this point. [shell1]:2:19pm:~% kldstat Id Refs Address Size Name 1 2 0xfffffc0000300000 2a6e70 kernel 2 1 0xfffffe00012c6000 14000 null.ko [shell1]:2:19pm:~% df -k Filesystem 1K-blocks Used Avail Capacity Mounted on 172.16.0.3:/export/alpha 8038348 1120623 6274658 15% / mfs:139 959 599 284 68% /conf/etc /conf/etc 959 599 284 68% /etc procfs 8 8 0 100% /proc mfs:162 31743 214 28990 1% /var /var/tmp 31743 214 28990 1% /tmp mfs:184 1511 53 1338 4% /dev 172.16.0.3:/export/shell 8038348 1120623 6274658 15% /sandbox nfs-web:/homedirs 100149168 19353284 80795884 19% /sandbox/home nfs-web:/webfiles 100149168 19353284 80795884 19% /sandbox/webfiles [shell1]:2:20pm:~% uname -a FreeBSD shell1.thebiz.net 4.0-RELEASE FreeBSD 4.0-RELEASE #8: Tue Apr 4 13:36:42 EDT 2000 root@web1.thebiz.net:/usr/src/sys/compile/DISKLESS-DS10 alpha [shell1]:2:20pm:~% sysctl hw.model hw.model: COMPAQ AlphaServer DS10 466 MHz [shell1]:2:20pm:~% more /sys/alpha/conf/DISKLESS-DS10 # # GENERIC -- Generic kernel configuration file for FreeBSD/alpha # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../i386/conf/LINT configuration file. # If you are in doubt as to the purpose or necessity of a line, check first # in LINT. Please note that this is the i386 LINT, but it still contains # valuable info for alpha too # # For hardware specific information check HARDWARE.TXT # # $FreeBSD: src/sys/alpha/conf/GENERIC,v 1.71 2000/02/27 07:35:36 green Exp $ machine alpha cpu EV5 ident DISKLESS-DS10 maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # Platforms supported options DEC_ST6600 # xp1000, dp264, ds20, ds10, family options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Memory Filesystem options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=2000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies # # Required for netboooting # options BOOTP options BOOTP_NFSROOT options BOOTP_NFSV3 options BOOTP_COMPAT options BOOTP_WIRED_TO=de1 # # Firewall support to forward sockets # # Standard busses device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata device atapicd # ATAPI CDROM drives # SCSI Controllers device isp # Qlogic family # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # syscons is the default console driver, resembling an SCO console device sc0 at isa? # real time clock device mcclock0 at isa? port 0x70 # Serial (COM) ports device sio0 at isa? port IO_COM1 irq 4 device sio1 at isa? port IO_COM2 irq 3 flags 0x50 # PCI Ethernet NICs device de # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter [shell1]:2:20pm:~% To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 11:59:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3AA6037B634 for ; Tue, 18 Apr 2000 11:59:45 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA18580; Tue, 18 Apr 2000 14:59:40 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA96451; Tue, 18 Apr 2000 14:59:40 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 18 Apr 2000 14:59:39 -0400 (EDT) To: "Matthew Zahorik" Cc: Subject: Re: HELP! In-Reply-To: <014501bfa963$a5609550$1401eed8@mahatma> References: <00c501bfa955$203546e0$1401eed8@mahatma> <14588.42187.126783.219096@grasshopper.cs.duke.edu> <014501bfa963$a5609550$1401eed8@mahatma> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14588.44846.499922.61041@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Zahorik writes: > [shell1]:2:19pm:~% kldstat > Id Refs Address Size Name > 1 2 0xfffffc0000300000 2a6e70 kernel > 2 1 0xfffffe00012c6000 14000 null.ko Hey, how did null.ko get loaded? Are you using nullfs? I'm not an FS person, but the mount_null() man page says: BUGS THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN <...> This is enough for me to suggest you get nullfs out of the picture before proceeding any further.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 12:28:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 2B27937BB1F for ; Tue, 18 Apr 2000 12:28:55 -0700 (PDT) (envelope-from maz@albany.net) Received: (qmail 2867 invoked from network); 18 Apr 2000 15:28:52 -0400 Received: from mail2.thebiz.net (172.16.0.129) by mx1.thebiz.net with SMTP; 18 Apr 2000 15:28:52 -0400 Received: (qmail 15702 invoked by uid 0); 18 Apr 2000 15:28:52 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.albany.net with SMTP; 18 Apr 2000 15:28:52 -0400 Message-ID: <01c801bfa96c$2309a520$1401eed8@mahatma> From: "Matthew Zahorik" To: "Andrew Gallatin" Cc: References: <00c501bfa955$203546e0$1401eed8@mahatma><14588.42187.126783.219096@grasshopper.cs.duke.edu><014501bfa963$a5609550$1401eed8@mahatma> <14588.44846.499922.61041@grasshopper.cs.duke.edu> Subject: Re: HELP! Date: Tue, 18 Apr 2000 15:27:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : > [shell1]:2:19pm:~% kldstat : > Id Refs Address Size Name : > 1 2 0xfffffc0000300000 2a6e70 kernel : > 2 1 0xfffffe00012c6000 14000 null.ko : : Hey, how did null.ko get loaded? Are you using nullfs? I'm not an FS : person, but the mount_null() man page says: Ugh. It's used by rc.diskless* [shell1]:3:14pm:/etc% fgrep null rc* rc: dlv=`/sbin/sysctl -n vfs.nfs.diskless_valid 2> /dev/null` rc:umount -a >/dev/null 2>&1 rc: (cd /var/run && cp /dev/null utmp && chmod 644 utmp;) rc.alpha: echo -n ' OSF/1'; osf1 > /dev/null 2>&1 rc.diskless1:# WARNING! null mounts cannot handle mmap, and since many programs rc.diskless1:mount_null /conf/etc /etc rc.diskless2: mount_null /var/tmp /tmp And wonders of wonders, in rc.diskless1: # # WARNING! null mounts cannot handle mmap, and since many programs # use mmap (such as 'cp'), we have to copy. # mount_mfs -s 2048 -T qp120at dummy /conf/etc cp -Rp /etc/* /conf/etc chkerr $? "MFS mount on /conf/etc" if [ -d /conf/${bootp_ipa} ] ; then cp -Rp /conf/${bootp_ipa}/etc/* /conf/etc elif [ -d /conf/${bootp_ipbca} ] ; then cp -Rp /conf/${bootp_ipbca}/etc/* /conf/etc else cp -Rp /conf/default/etc/* /conf/etc fi # Make the new directory available as /etc # mount_null /conf/etc /etc Ugh. How can I remount that without using null mounts? I lose the data if I unmount the MFS filesystem, don't I? I guess I'll have to do this in three steps. 1. Mount /conf/etc 2. Copy /etc/* and /conf/{ip}/etc/* into /conf/etc 3. Mount another MFS at /etc 4. cp /conf/etc to /etc 5. umount /conf/etc Anything wrong with that logic? It's only uses a couple of more megs at startup, and these are 576M machines. It's funny any cp's work at all, and it's even worse that this is the default scripts that come with the distro (: - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 13:20: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20]) by hub.freebsd.org (Postfix) with SMTP id 7640637B648 for ; Tue, 18 Apr 2000 13:20:00 -0700 (PDT) (envelope-from maz@albany.net) Received: (qmail 12699 invoked from network); 18 Apr 2000 16:19:58 -0400 Received: from mail2.thebiz.net (172.16.0.129) by mx1.thebiz.net with SMTP; 18 Apr 2000 16:19:58 -0400 Received: (qmail 30961 invoked by uid 0); 18 Apr 2000 16:19:58 -0400 Received: from unknown (HELO mahatma) (216.238.1.20) by mail.albany.net with SMTP; 18 Apr 2000 16:19:58 -0400 Message-ID: <02a201bfa973$45f4fd80$1401eed8@mahatma> From: "Matthew Zahorik" To: "Andrew Gallatin" Cc: Subject: Re: HELP! Date: Tue, 18 Apr 2000 16:18:34 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : 1. Mount /conf/etc : 2. Copy /etc/* and /conf/{ip}/etc/* into /conf/etc : 3. Mount another MFS at /etc : 4. cp /conf/etc to /etc : 5. umount /conf/etc This worked. Here are the diffs - I'll submit them in a bug report after I fix the /var mount_null too. Thanks for all the help! -- snip -- *** /conf/etc/rc.diskless1 Wed Mar 15 13:40:48 2000 --- rc.diskless1 Tue Apr 18 15:57:08 2000 *************** *** 86,92 **** # Make the new directory available as /etc # ! mount_null /conf/etc /etc # Tell /etc/rc to run the specified script after # it does its mounts but before it does anything --- 86,96 ---- # Make the new directory available as /etc # ! mount_mfs -s 2048 -T qp120at dummy /etc ! cp -Rp /conf/etc/* /etc ! chkerr $? "MFS mount on /etc" ! ! umount /conf/etc # Tell /etc/rc to run the specified script after # it does its mounts but before it does anything - Matt -- Matthew Zahorik Director of Systems and Networking - BiznessOnline.com matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 14:59:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sun.rhrk.uni-kl.de (sun.rhrk.uni-kl.de [131.246.137.50]) by hub.freebsd.org (Postfix) with SMTP id 2327C37B82F for ; Tue, 18 Apr 2000 14:59:19 -0700 (PDT) (envelope-from naddy@unix-ag.uni-kl.de) Received: from sushi.unix-ag.uni-kl.de ( root@sushi.unix-ag.uni-kl.de [131.246.89.13] ) by sun.rhrk.uni-kl.de id aa04425 for ; 18 Apr 2000 23:59 MESZ Received: from fettuccini.unix-ag.uni-kl.de (fettuccini.unix-ag.uni-kl.de [131.246.89.27]) by sushi.unix-ag.uni-kl.de (8.9.3/8.9.1) with ESMTP id XAA11152 for ; Tue, 18 Apr 2000 23:45:46 +0200 Received: (from naddy@localhost) by fettuccini.unix-ag.uni-kl.de (8.9.3/8.9.3) id XAA08358 for freebsd-alpha@freebsd.org; Tue, 18 Apr 2000 23:45:54 +0200 (CEST) (envelope-from naddy) Date: Tue, 18 Apr 2000 23:45:54 +0200 From: Christian Weisgerber To: freebsd-alpha@freebsd.org Subject: XFree86 support? Message-ID: <20000418234554.C7054@fettuccini.unix-ag.uni-kl.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What's the current state of XFree86 support on FreeBSD/alpha? We have an AXPpci33 here that we're currently trying to re-install. So far the chosen Linux distros have given us installation trouble. If none work out, I might be able to push for BSD. The main purpose of this box will be to serve as an X11 display. Does XFree86 work on FreeBSD/alpha with a Matrox Millennium card (XF86_SVGA)? -- Christian "naddy" Weisgerber naddy@unix-ag.uni-kl.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Apr 18 15: 7:14 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 419BD37BB8B for ; Tue, 18 Apr 2000 15:07:12 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000418220708.IKWI9461.relay02@chello.nl>; Wed, 19 Apr 2000 00:07:08 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id AAA02471; Wed, 19 Apr 2000 00:07:10 +0200 (CEST) (envelope-from wkb) Date: Wed, 19 Apr 2000 00:07:10 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: XFree86 support? Message-ID: <20000419000709.A2443@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000418234554.C7054@fettuccini.unix-ag.uni-kl.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000418234554.C7054@fettuccini.unix-ag.uni-kl.de>; from naddy@unix-ag.uni-kl.de on Tue, Apr 18, 2000 at 11:45:54PM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Apr 18, 2000 at 11:45:54PM +0200, Christian Weisgerber wrote: > What's the current state of XFree86 support on FreeBSD/alpha? > > We have an AXPpci33 here that we're currently trying to re-install. > So far the chosen Linux distros have given us installation trouble. > If none work out, I might be able to push for BSD. The main purpose > of this box will be to serve as an X11 display. Does XFree86 work > on FreeBSD/alpha with a Matrox Millennium card (XF86_SVGA)? According to the messages I saw go-by on freebsd-alpha (check the archives) a Millenium works just fine on FreeBSD/alpha. I've also been running S3-based cards successfully in one of my Alphas. W/ -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Apr 19 17:54:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 4EF2F37B7E2 for ; Wed, 19 Apr 2000 17:54:15 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id CAA06003 for freebsd-alpha@freebsd.org; Thu, 20 Apr 2000 02:54:06 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA48339 for freebsd-alpha@freebsd.org; Thu, 20 Apr 2000 01:17:32 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: XFree86 support? Date: 20 Apr 2000 01:17:31 +0200 Message-ID: <8dleqb$1f65$1@bigeye.rhein-neckar.de> References: <20000418234554.C7054@fettuccini.unix-ag.uni-kl.de> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber wrote: > We have an AXPpci33 here that we're currently trying to re-install. > So far the chosen Linux distros have given us installation trouble. > If none work out, I might be able to push for BSD. Well, we may end up re-installing some Linux distro after all (I'm outnumbered), but today we tried FreeBSD 4.0-RELEASE. Hint: Don't reuse an existing Linux disklabel. The installation will work fine, however, the bootstrap on the disk will crash leaving you with a system you can't boot. Redoing the install, this time deleting and recreating all partitions, fixed this. Apart from this, which isn't FreeBSD's fault I guess, the whole installation procedure went very smoothly. XFree86 seems to work, too. "X -indirect " will crash xdm, though. Has anybody seen this? I can provide the xdm configuration details. No, it's no basic xdm setup problem. We're using this configuration on a variety of Linux/BSD hosts. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 11: 7:51 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from quasar.uvt.ro (quasar.uvt.ro [193.226.13.67]) by hub.freebsd.org (Postfix) with ESMTP id B532437B86C for ; Thu, 20 Apr 2000 11:07:46 -0700 (PDT) (envelope-from ardelean@quasar.uvt.ro) Received: from localhost (ardelean@localhost) by quasar.uvt.ro (8.9.3/8.9.3) with SMTP id VAA10991 for ; Thu, 20 Apr 2000 21:07:40 +0300 (EEST) Date: Thu, 20 Apr 2000 21:07:40 +0300 (EEST) From: Gheorghe Ardelean To: freebsd-alpha@freebsd.org Subject: firmware updating problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have (at our Univ) a DEC3000 Model400 and I'd like to install FreeBSD on it. Just now I'm experincing problems with firmware upgrade. There is no floppy drive on if so I managed to upgrade via BOOTP from an PC running FreeBSD 3.4-RELEASE After issuing the boot ez0 command on the SRM console I receive the following message: Host server IP address is ... AUDIT_BSERVER_FOUND 84 FAIL >>> Looking with tcpdump on the boot server I see the following: 21:04:13.083134 arp who-has 0.0.0.0 (10:0:0:0:0:0) tell jad2.uvt.ro 21:04:21.520591 arp who-has 0.0.0.0 (10:0:0:0:0:0) tell jad2.uvt.ro 21:04:27.769809 arp who-has phys-ppp-gw.uvt.ro (f:0:0:0:0:0) tell jad2.uvt.ro 21:04:27.770060 arp reply phys-ppp-gw.uvt.ro is-at 0:0:c0:fe:b0:4a 21:04:27.771579 jad2.uvt.ro.60581 > phys-ppp-gw.uvt.ro.tftp: 24 tftp-#0 [tos 0x1] (ttl 30, id 2447, bad cksum c976!) (jad2.uvt.ro is the alpha machine and phys-ppp-gw is the PC acting like BOOTP/TFTPD server) Here is the /etc/bootptab file contents: jad2:ht=ethernet:ha=08002b38be3a:hd=/:td=/tftboot:bf=m400_v7_0.btp:\ :ds=193.226.14.33:dn=uvt.ro:gw=193.226.13.65:hn:\ :ip=193.226.13.100:sm=255.255.255.192:bs=auto: Could you please help? Sincerely yours, Gheorghe ARDELEAN West Univ. Of Timisoara Dept. of Theoretical and Computational Physics V. Parvan No.4, Ro-1900, Timisoara, ROMANIA Tel: +40-(0)56-194068 Ext. 203, 201, 108 | Fax: +40-(0)56-190333 Email: ardelean@quasar.uvt.ro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 11:19:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 46BB037BA91 for ; Thu, 20 Apr 2000 11:19:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA00765; Thu, 20 Apr 2000 14:19:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA04668; Thu, 20 Apr 2000 14:19:27 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Apr 2000 14:19:27 -0400 (EDT) To: Gheorghe Ardelean Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: firmware updating problems In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14591.18469.739521.636337@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gheorghe Ardelean writes: > > Hello, > > I have (at our Univ) a DEC3000 Model400 and I'd like to install > FreeBSD on it. > > Just now I'm experincing problems with firmware upgrade. > There is no floppy drive on if so I managed to upgrade via BOOTP > from an PC running FreeBSD 3.4-RELEASE Be VERY VERY careful. Upgrading past a certain revision of the firmware without upgrading the SROM chip will make a 3000/400 unusable. Unfortunately, its been years since I've dealt with machines this old, so I don't know the firmware revisions off the top of my head. A www search will probably turn up something in the osf1 managers mailing lists about this. Again, upgrading a 3000/400 to a modern firmware revisions (anything in the last 4-5 years or so) should be undertaken with extreeme caution. > 21:04:27.771579 jad2.uvt.ro.60581 > phys-ppp-gw.uvt.ro.tftp: 24 tftp-#0 > [tos 0x1] (ttl 30, id 2447, bad cksum c976!) Some revisions of the dec firmware generate bad checksums when netbooting via bootp. Mop might be an option.. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 11:26:52 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 55F8437B58E for ; Thu, 20 Apr 2000 11:26:12 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000420182608.DSSH18572.relay02@chello.nl>; Thu, 20 Apr 2000 20:26:08 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id UAA06611; Thu, 20 Apr 2000 20:26:09 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Apr 2000 20:26:09 +0200 From: Wilko Bulte To: Gheorghe Ardelean Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: firmware updating problems Message-ID: <20000420202609.A6499@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from ardelean@quasar.uvt.ro on Thu, Apr 20, 2000 at 09:07:40PM +0300 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 20, 2000 at 09:07:40PM +0300, Gheorghe Ardelean wrote: > I have (at our Univ) a DEC3000 Model400 and I'd like to install > FreeBSD on it. Beware that FreeBSD does not currently support the SCSI interface on DEC3000 series machines. It should be able to run diskless. See also the HARDWARE.TXT file for FreeBSD-4.0 and -current. > Looking with tcpdump on the boot server I see the following: > > 21:04:13.083134 arp who-has 0.0.0.0 (10:0:0:0:0:0) tell jad2.uvt.ro > 21:04:21.520591 arp who-has 0.0.0.0 (10:0:0:0:0:0) tell jad2.uvt.ro > 21:04:27.769809 arp who-has phys-ppp-gw.uvt.ro (f:0:0:0:0:0) tell > jad2.uvt.ro > 21:04:27.770060 arp reply phys-ppp-gw.uvt.ro is-at 0:0:c0:fe:b0:4a > 21:04:27.771579 jad2.uvt.ro.60581 > phys-ppp-gw.uvt.ro.tftp: 24 tftp-#0 > [tos 0x1] (ttl 30, id 2447, bad cksum c976!) > > (jad2.uvt.ro is the alpha machine and phys-ppp-gw is the PC acting like > BOOTP/TFTPD server) > > Here is the /etc/bootptab file contents: > > jad2:ht=ethernet:ha=08002b38be3a:hd=/:td=/tftboot:bf=m400_v7_0.btp:\ > :ds=193.226.14.33:dn=uvt.ro:gw=193.226.13.65:hn:\ > :ip=193.226.13.100:sm=255.255.255.192:bs=auto: What I've been using to boot FreeBSD on my DEC3000/40 is: sandpiper:\ :ht=ethernet:ha=08002B3C6145:\ :ip=192.168.200.19:sm=255.255.255.0:sa=192.168.200.22:\ :hd="/usr/sandpiper":bf=netboot:rp="192.168.200.22:/usr/sandpiper":vm=rfc1048: But I think there might be SRM firmware out there that just does not do the right thing to tftp. This might mean you need a CD to upgrade your firmware. W/ -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 11:59:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zorro.methos.net (ns2.aquik.net [216.54.55.3]) by hub.freebsd.org (Postfix) with SMTP id D370037B67E for ; Thu, 20 Apr 2000 11:59:10 -0700 (PDT) (envelope-from dmaple@methos.net) Received: (qmail 97509 invoked by uid 500); 20 Apr 2000 19:07:32 -0000 Received: from intra.acgva.net (HELO acgpdc) (216.54.63.4) by methos.net with SMTP; 20 Apr 2000 19:07:32 -0000 From: "David C. Maple" To: Subject: Problem booting from floppies Date: Thu, 20 Apr 2000 15:04:31 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am getting a recurring error when trying to run the install from the boot floppies. I have tried several disks, so I know they are good. I suspect that the floppy drive itself may be bad. The error I'm getting follows: *** Soft Error - Error #10 - FDC: Data overrun or underrun Diagnostic Name ID Device Pass Test Hard/Soft 20-APR-2020 boot 00000020 err_iob 0 0 0 22 14:55:24 *** End of Error *** This repeats several times then asks for the mfs disk. The same error repeats during the read of the mfs disk and then I get dumped back out at the prompt. Am I correct that it should begin the installation there or am I supposed to type something here to start the install? Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:10:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 6791337B98B for ; Thu, 20 Apr 2000 12:10:31 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000420191002.EPXP6157.relay01@chello.nl>; Thu, 20 Apr 2000 21:10:02 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA06957; Thu, 20 Apr 2000 21:09:54 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Apr 2000 21:09:54 +0200 From: Wilko Bulte To: "David C. Maple" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem booting from floppies Message-ID: <20000420210954.A6943@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmaple@methos.net on Thu, Apr 20, 2000 at 03:04:31PM -0400 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 20, 2000 at 03:04:31PM -0400, David C. Maple wrote: Is this a Multia machine? Sure looks like one... Multia SRM has problems booting floppies. Wilko > I am getting a recurring error when trying to run the install from the boot > floppies. I have tried several disks, so I know they are good. I suspect > that the floppy drive itself may be bad. The error I'm getting follows: > > *** Soft Error - Error #10 - FDC: Data overrun or underrun > > Diagnostic Name ID Device Pass Test Hard/Soft 20-APR-2020 > boot 00000020 err_iob 0 0 0 22 14:55:24 > > *** End of Error *** > > This repeats several times then asks for the mfs disk. The same error > repeats during the read of the mfs disk and then I get dumped back out at > the prompt. Am I correct that it should begin the installation there or am > I supposed to type something here to start the install? > > Thanks, > > Dave > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end quoted text--- -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:17:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zorro.methos.net (ns2.aquik.net [216.54.55.3]) by hub.freebsd.org (Postfix) with SMTP id E347737B88F for ; Thu, 20 Apr 2000 12:17:34 -0700 (PDT) (envelope-from dmaple@methos.net) Received: (qmail 97662 invoked by uid 500); 20 Apr 2000 19:26:11 -0000 Received: from intra.acgva.net (HELO acgpdc) (216.54.63.4) by methos.net with SMTP; 20 Apr 2000 19:26:11 -0000 From: "David C. Maple" To: Subject: RE: Problem booting from floppies Date: Thu, 20 Apr 2000 15:23:10 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000420210954.A6943@yedi.wbnet> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry, I should have included that. Yes it is a Multia. Any ideas what I can do? -----Original Message----- From: Wilko Bulte [mailto:wkb@chello.nl] Sent: Thursday, April 20, 2000 3:10 PM To: David C. Maple Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem booting from floppies On Thu, Apr 20, 2000 at 03:04:31PM -0400, David C. Maple wrote: Is this a Multia machine? Sure looks like one... Multia SRM has problems booting floppies. Wilko > I am getting a recurring error when trying to run the install from the boot > floppies. I have tried several disks, so I know they are good. I suspect > that the floppy drive itself may be bad. The error I'm getting follows: > > *** Soft Error - Error #10 - FDC: Data overrun or underrun > > Diagnostic Name ID Device Pass Test Hard/Soft 20-APR-2020 > boot 00000020 err_iob 0 0 0 22 14:55:24 > > *** End of Error *** > > This repeats several times then asks for the mfs disk. The same error > repeats during the read of the mfs disk and then I get dumped back out at > the prompt. Am I correct that it should begin the installation there or am > I supposed to type something here to start the install? > > Thanks, > > Dave > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end quoted text--- -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:22:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 009E737B9B6 for ; Thu, 20 Apr 2000 12:22:56 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000420192300.EVHY6157.relay01@chello.nl>; Thu, 20 Apr 2000 21:23:00 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA07178; Thu, 20 Apr 2000 21:22:53 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Apr 2000 21:22:53 +0200 From: Wilko Bulte To: "David C. Maple" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem booting from floppies Message-ID: <20000420212253.F6943@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000420210954.A6943@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmaple@methos.net on Thu, Apr 20, 2000 at 03:23:10PM -0400 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 20, 2000 at 03:23:10PM -0400, David C. Maple wrote: > Sorry, I should have included that. Yes it is a Multia. Any ideas what I > can do? Boot from CD... (really, this floppy booting thing is a pain in the b* problem ) -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:24:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zorro.methos.net (ns2.aquik.net [216.54.55.3]) by hub.freebsd.org (Postfix) with SMTP id CFB3737BE93 for ; Thu, 20 Apr 2000 12:24:37 -0700 (PDT) (envelope-from dmaple@methos.net) Received: (qmail 97701 invoked by uid 500); 20 Apr 2000 19:33:15 -0000 Received: from intra.acgva.net (HELO acgpdc) (216.54.63.4) by methos.net with SMTP; 20 Apr 2000 19:33:14 -0000 From: "David C. Maple" To: Subject: RE: Problem booting from floppies Date: Thu, 20 Apr 2000 15:30:14 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000420212253.F6943@yedi.wbnet> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, there lies another problem, I don't have a SCSI CDRom Drive. -----Original Message----- From: Wilko Bulte [mailto:wkb@chello.nl] Sent: Thursday, April 20, 2000 3:23 PM To: David C. Maple Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem booting from floppies On Thu, Apr 20, 2000 at 03:23:10PM -0400, David C. Maple wrote: > Sorry, I should have included that. Yes it is a Multia. Any ideas what I > can do? Boot from CD... (really, this floppy booting thing is a pain in the b* problem ) -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:41:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 03A9E37BDCE for ; Thu, 20 Apr 2000 12:41:13 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000420194105.ESRE18572.relay02@chello.nl>; Thu, 20 Apr 2000 21:41:05 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA07313; Thu, 20 Apr 2000 21:41:07 +0200 (CEST) (envelope-from wkb) Date: Thu, 20 Apr 2000 21:41:07 +0200 From: Wilko Bulte To: "David C. Maple" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Problem booting from floppies Message-ID: <20000420214107.A7265@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <20000420212253.F6943@yedi.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmaple@methos.net on Thu, Apr 20, 2000 at 03:30:14PM -0400 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 20, 2000 at 03:30:14PM -0400, David C. Maple wrote: > Well, there lies another problem, I don't have a SCSI CDRom Drive. Ouch.. I would have suggested trying a netboot of the NoName but that is not always guaranteed to work. And you would need an ethernet card that the NoName SRM understands. W/ > To: David C. Maple > Cc: freebsd-alpha@FreeBSD.ORG > Subject: Re: Problem booting from floppies > > > On Thu, Apr 20, 2000 at 03:23:10PM -0400, David C. Maple wrote: > > Sorry, I should have included that. Yes it is a Multia. Any ideas what I > > can do? > > Boot from CD... > > (really, this floppy booting thing is a pain in the b* problem ) > > -- > Wilko Bulte Powered by FreeBSD http://www.freebsd.org > http://www.tcja.nl > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message ---end quoted text--- -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:41:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2]) by hub.freebsd.org (Postfix) with ESMTP id CE0A737BE94 for ; Thu, 20 Apr 2000 12:41:22 -0700 (PDT) (envelope-from king@sstar.com) Received: from jking (jking.lgc.com [134.132.75.164]) by jking1.lgc.com (8.9.3/8.9.3) with SMTP id OAA64862; Thu, 20 Apr 2000 14:40:07 -0500 (CDT) (envelope-from king@sstar.com) Message-ID: <002901bfab00$47f9dbd0$a44b8486@jking> From: "Jim King" To: "David C. Maple" , References: Subject: Re: Problem booting from floppies Date: Thu, 20 Apr 2000 14:40:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you have a SCSI Zip drive handy it's possible to use that (I've done it). Getting a SCSI CD-ROM drive would probably be a good idea in the long run. Jim ----- Original Message ----- From: "David C. Maple" To: Sent: Thursday, April 20, 2000 2:30 PM Subject: RE: Problem booting from floppies > Well, there lies another problem, I don't have a SCSI CDRom Drive. > > -----Original Message----- > From: Wilko Bulte [mailto:wkb@chello.nl] > Sent: Thursday, April 20, 2000 3:23 PM > To: David C. Maple > Cc: freebsd-alpha@FreeBSD.ORG > Subject: Re: Problem booting from floppies > > > On Thu, Apr 20, 2000 at 03:23:10PM -0400, David C. Maple wrote: > > Sorry, I should have included that. Yes it is a Multia. Any ideas what I > > can do? > > Boot from CD... > > (really, this floppy booting thing is a pain in the b* problem ) > > -- > Wilko Bulte Powered by FreeBSD http://www.freebsd.org > http://www.tcja.nl > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 12:47:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zorro.methos.net (ns2.aquik.net [216.54.55.3]) by hub.freebsd.org (Postfix) with SMTP id 47A9637B99B for ; Thu, 20 Apr 2000 12:47:43 -0700 (PDT) (envelope-from dmaple@methos.net) Received: (qmail 3931 invoked by uid 500); 20 Apr 2000 19:56:20 -0000 Received: from intra.acgva.net (HELO acgpdc) (216.54.63.4) by methos.net with SMTP; 20 Apr 2000 19:56:20 -0000 From: "David C. Maple" To: Subject: RE: Problem booting from floppies for alpha install Date: Thu, 20 Apr 2000 15:53:19 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have 3.8-3 that is the lates one I found on the web. Dave -----Original Message----- From: Joe Royce [mailto:joe@team7.cba.ualr.edu] Sent: Thursday, April 20, 2000 3:35 PM To: David C. Maple Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problem booting from floppies for alpha install Soft errors are normal for a Multia ( at least for mine). Do you have the latest firmware? I couldn't get mine to boot until I upgraded to the latest firmware. -Joe On Thu, 20 Apr 2000, David C. Maple wrote: > Date: Thu, 20 Apr 2000 15:22:07 -0400 > From: David C. Maple > To: freebsd-questions@FreeBSD.ORG > Subject: Problem booting from floppies for alpha install > > This relates to the installation of FreeBSD on a Multia. > > I am getting a recurring error when trying to run the install from the boot > floppies. I have tried several disks, so I know they are good. I suspect > that the floppy drive itself may be bad. The error I'm getting follows: > > *** Soft Error - Error #10 - FDC: Data overrun or underrun > > Diagnostic Name ID Device Pass Test Hard/Soft 20-APR-2020 > boot 00000020 err_iob 0 0 0 22 14:55:24 > > *** End of Error *** > > This repeats several times then asks for the mfs disk. The same error > repeats during the read of the mfs disk and then I get dumped back out at > the prompt. Am I correct that it should begin the installation there or am > I supposed to type something here to start the install? > > Thanks, > > Dave > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 15:26:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 3A36137B78D for ; Thu, 20 Apr 2000 15:26:55 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 27389 invoked by uid 0); 20 Apr 2000 22:26:22 -0000 Received: from crux.clarkson.edu (128.153.4.132) by mail.clarkson.edu with SMTP; 20 Apr 2000 22:26:22 -0000 Date: Thu, 20 Apr 2000 18:26:21 -0400 (EDT) From: Todd Cohen To: freebsd-alpha@freebsd.org Subject: acroread4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I installed acroread4 via the ports collection and when I try to run it I get the following: bash-2.03$ acroread4 Illegal instruction Any ideas? Anyone know of an alternative to use for now? --------------------------------------------------- http://www.clarkson.edu/~cohentl "Sometimes crazy things happen in circuits." - Muku, 1999 "The answers to lifes problems aren't at the bottom of bottles, they're on TV" - Homer J. Simpson --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 15:51:34 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A322137B7F4 for ; Thu, 20 Apr 2000 15:51:26 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA09948; Thu, 20 Apr 2000 18:51:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA05195; Thu, 20 Apr 2000 18:51:17 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Apr 2000 18:51:17 -0400 (EDT) To: Todd Cohen Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: acroread4 In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14591.34159.42813.764442@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Todd Cohen writes: > I installed acroread4 via the ports collection and when I try to run it I > get the following: > > bash-2.03$ acroread4 > Illegal instruction > > Any ideas? Anyone know of an alternative to use for now? > You failed to give almost any information about your configuration. When you have a problem, please at least include the version of FreeBSD you are running and the platform you are running it on. I'm *guessing* you're running on a machine which does not support byte/word instructions (LCA, EV4, EV45, or EV5), am I right? According a wheezing old EV5 box running Tru64, acroread4 contains instructions for newer CPUs which it needs to emulate: % /usr/pkg/Acrobat4/bin/acroread inst emulated pid=11774 va=0x11fffeeb0 pc=0x120058df0 inst=0x37ef0090 I don't know what 0x37ef0090 is & don't have time to look it up, but given that it doesn't work on a 21164 and works on my Miata at home, I'm guessing that its a bwx instruction. Unfortunately, FreeBSD doesn't support instruction emulation, so you're SOL right now. Fortunately, I think that 3.x version of Acrobat will be OK (at least the same Tru64 box does not spit out any messages about emulated instructions). Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 16:13:42 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 07D0C37B650 for ; Thu, 20 Apr 2000 16:13:40 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 512 invoked by uid 0); 20 Apr 2000 23:13:38 -0000 Received: from crux.clarkson.edu (128.153.4.132) by mail.clarkson.edu with SMTP; 20 Apr 2000 23:13:38 -0000 Date: Thu, 20 Apr 2000 19:13:37 -0400 (EDT) From: Todd Cohen To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: acroread4 In-Reply-To: <14591.34159.42813.764442@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You're right, I'm sorry... Yeah, I have an older AlphaStation 200, I'll try acroread 3. Thanks for you help. -Todd On Thu, 20 Apr 2000, Andrew Gallatin wrote: > > Todd Cohen writes: > > I installed acroread4 via the ports collection and when I try to run it I > > get the following: > > > > bash-2.03$ acroread4 > > Illegal instruction > > > > Any ideas? Anyone know of an alternative to use for now? > > > > You failed to give almost any information about your configuration. > When you have a problem, please at least include the version of > FreeBSD you are running and the platform you are running it on. > > I'm *guessing* you're running on a machine which does not support > byte/word instructions (LCA, EV4, EV45, or EV5), am I right? > According a wheezing old EV5 box running Tru64, acroread4 contains > instructions for newer CPUs which it needs to emulate: > > % /usr/pkg/Acrobat4/bin/acroread > inst emulated pid=11774 va=0x11fffeeb0 pc=0x120058df0 inst=0x37ef0090 > > I don't know what 0x37ef0090 is & don't have time to look it up, but > given that it doesn't work on a 21164 and works on my Miata at home, > I'm guessing that its a bwx instruction. Unfortunately, FreeBSD > doesn't support instruction emulation, so you're SOL right now. > > Fortunately, I think that 3.x version of Acrobat will be OK (at least > the same Tru64 box does not spit out any messages about emulated > instructions). > > Cheers, > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > --------------------------------------------------- http://www.clarkson.edu/~cohentl "Sometimes crazy things happen in circuits." - Muku, 1999 "The answers to lifes problems aren't at the bottom of bottles, they're on TV" - Homer J. Simpson --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 17:17:30 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by hub.freebsd.org (Postfix) with ESMTP id D72EF37B5A0 for ; Thu, 20 Apr 2000 17:17:27 -0700 (PDT) (envelope-from nm@vt.edu) Received: from mail.vt.edu (gkar.cc.vt.edu [128.173.16.40]) by sable.cc.vt.edu (8.9.3/8.9.3) with ESMTP id UAA24582 for ; Thu, 20 Apr 2000 20:17:26 -0400 (EDT) Received: from dog ([198.82.106.223]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0FTC00383BH00D@gkar.cc.vt.edu> for freebsd-alpha@freebsd.org; Thu, 20 Apr 2000 20:17:25 -0400 (EDT) Date: Thu, 20 Apr 2000 20:16:32 -0400 From: nm Subject: scsi cable problems? X-Sender: nmanisca@mail.vt.edu (Unverified) To: freebsd-alpha@freebsd.org Message-id: <3.0.32.20000420201631.00cb6210@mail.vt.edu> MIME-version: 1.0 X-Mailer: Windows Eudora Pro Version 3.0 (32) Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just bought an 18GB uw scsi disk (hitachi). It has an SCA->68pin adapter on it... During boot up, the system hangs with these messages displayed: Waiting 15 seconds for SCSI devices to settle de0: enabling 10baseT port ahc0:A:5: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x50, ARG_1 == 0xff, SEQ_FLAGS == 0x0 What do you think this means? Bad termination? Bad cable? The cable and disk are brand new... There is another uw dev on this cable that works fine. What other information would be needed to diag this prob? Thanks, Nick Maniscalco nmanisca@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 18:31:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 1A2A437B522 for ; Thu, 20 Apr 2000 18:31:19 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id DAA08289 for freebsd-alpha@freebsd.org; Fri, 21 Apr 2000 03:31:17 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id AAA92140 for freebsd-alpha@freebsd.org; Fri, 21 Apr 2000 00:33:58 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: XFree86 support? Date: 21 Apr 2000 00:33:57 +0200 Message-ID: <8do0kl$2put$1@bigeye.rhein-neckar.de> References: <20000418234554.C7054@fettuccini.unix-ag.uni-kl.de> <8dleqb$1f65$1@bigeye.rhein-neckar.de> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christian Weisgerber wrote: > XFree86 seems to work, too. "X -indirect " will crash > xdm, though. In fact, any "X -query" to xdm on the alpha will cause it to dump core. Is anybody else seeing this? XFree86 3.3.6 from 4.0-RELEASE. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Apr 20 21:31: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 8173B37B543 for ; Thu, 20 Apr 2000 21:30:58 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id GAA24904 for freebsd-alpha@freebsd.org; Fri, 21 Apr 2000 06:30:56 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id EAA00622 for freebsd-alpha@freebsd.org; Fri, 21 Apr 2000 04:03:03 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: syscons colors Date: 21 Apr 2000 04:03:02 +0200 Message-ID: <8docsm$j0$1@bigeye.rhein-neckar.de> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I noticed during the install that the colors on alpha are different from those on i386. Instead of a blue background there was a red one, and in turn the red menu letters are blue. Well, my thought went, it's an alpha, maybe Jordan prefers a distinctive color scheme for that. Today I started up w3m and the colors there are wrong too, so this appears to be a general issue not limited to sysinstall. Is this some bizarre feature, a bug, ...? [AXPpci33, 4.0-RELEASE, Matrox Millennium] -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 2:47:37 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 7945237B67B for ; Fri, 21 Apr 2000 02:47:34 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000421094720.CCYZ22628.relay02@chello.nl>; Fri, 21 Apr 2000 11:47:20 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id LAA11584; Fri, 21 Apr 2000 11:47:23 +0200 (CEST) (envelope-from wkb) Date: Fri, 21 Apr 2000 11:47:23 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: syscons colors Message-ID: <20000421114722.E11432@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <8docsm$j0$1@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <8docsm$j0$1@bigeye.rhein-neckar.de>; from naddy@mips.rhein-neckar.de on Fri, Apr 21, 2000 at 04:03:02AM +0200 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 21, 2000 at 04:03:02AM +0200, Christian Weisgerber wrote: > I noticed during the install that the colors on alpha are different > from those on i386. Instead of a blue background there was a red > one, and in turn the red menu letters are blue. Well, my thought > went, it's an alpha, maybe Jordan prefers a distinctive color scheme > for that. Today I started up w3m and the colors there are wrong > too, so this appears to be a general issue not limited to sysinstall. > > Is this some bizarre feature, a bug, ...? > > [AXPpci33, 4.0-RELEASE, Matrox Millennium] I've also seen sysinstall use red on my Miata with S3 based VGA. At least you are not alone ;-) As I hardly use the graphics console on my Alphas I do not have much experience with applications using color. W/ -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 4:59:50 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 6EDB937B8FC for ; Fri, 21 Apr 2000 04:59:47 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12ic65-0002uj-0A; Fri, 21 Apr 2000 11:59:45 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id NAA92904; Fri, 21 Apr 2000 13:08:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 21 Apr 2000 13:05:18 +0100 (BST) From: Doug Rabson To: wc.bulte@chello.nl Cc: Christian Weisgerber , freebsd-alpha@freebsd.org Subject: Re: syscons colors In-Reply-To: <20000421114722.E11432@yedi.wbnet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Apr 2000, Wilko Bulte wrote: > On Fri, Apr 21, 2000 at 04:03:02AM +0200, Christian Weisgerber wrote: > > I noticed during the install that the colors on alpha are different > > from those on i386. Instead of a blue background there was a red > > one, and in turn the red menu letters are blue. Well, my thought > > went, it's an alpha, maybe Jordan prefers a distinctive color scheme > > for that. Today I started up w3m and the colors there are wrong > > too, so this appears to be a general issue not limited to sysinstall. > > > > Is this some bizarre feature, a bug, ...? > > > > [AXPpci33, 4.0-RELEASE, Matrox Millennium] > > I've also seen sysinstall use red on my Miata with S3 based VGA. At least > you are not alone ;-) As I hardly use the graphics console on my Alphas I > do not have much experience with applications using color. Its a known bug. For some reason, the text-mode vga palette is different on alpha. It would be possible to work around this in the console driver but noone has felt it important enough to do yet. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 6:29:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from gw.one.com.au (gw.one.com.au [203.18.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B66737B618 for ; Fri, 21 Apr 2000 06:29:30 -0700 (PDT) (envelope-from raymond@one.com.au) Received: from one.com.au (pmo.local [10.18.85.2]) by gw.one.com.au (8.9.2/8.9.2) with SMTP id XAA10937 for freebsd-alpha@FreeBSD.ORG; Fri, 21 Apr 2000 23:29:26 +1000 (EST) (envelope-from raymond@one.com.au) Date: Fri, 21 Apr 2000 23:29:26 +1000 (EST) From: User Raymond Message-Id: <200004211329.XAA10937@gw.one.com.au> Subject: floatingpoint control from c Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: freebsd-alpha@FreeBSD.ORG I have a language implementation for FreeBSD ( http://www.mumps.org/ ) that I'm trying to port to the alpha and have a floating point problem. I need to trap floating point arithmetic errors. On x86, I used the in-line functions and definitions in the file /usr/include/floatingpoint.h. This doesn't exist on the alpha. Does anyone have any hints as to a platform independant method of checking for floating point errors? Ray Newman Message sent at 11:28 PM on 21 Apr 2000 by PUP::RAYMOND. Id: 19233. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 12:36:22 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 32E3037B6A6; Fri, 21 Apr 2000 12:36:21 -0700 (PDT) (envelope-from wilko@FreeBSD.org) Received: (from wilko@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA30224; Fri, 21 Apr 2000 12:36:20 -0700 (PDT) (envelope-from wilko@FreeBSD.org) Date: Fri, 21 Apr 2000 12:36:20 -0700 (PDT) From: Message-Id: <200004211936.MAA30224@freefall.freebsd.org> To: eric@hotrail.com, wilko@FreeBSD.org, freebsd-alpha@FreeBSD.org Subject: Re: alpha/12821: slib.aq for the 3.2-RELEASE alpha distribution is broken Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: slib.aq for the 3.2-RELEASE alpha distribution is broken State-Changed-From-To: open->closed State-Changed-By: wilko State-Changed-When: Fri Apr 21 12:34:06 PDT 2000 State-Changed-Why: with 3.2 gone altogether from ftp.FreeBSD.org this PR no longer has much use: ftp> pwd 257 "/.0/FreeBSD/releases/alpha" is current directory. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for 'file list'. total 6 drwxr-xr-x 2 2035 207 512 Oct 29 06:48 3.3-STABLE drwxr-xr-x 14 2035 207 512 Jan 1 02:11 3.4-RELEASE lrwxrwxrwx 1 root 207 10 Feb 27 00:37 3.4-STABLE -> 3.3-STABLE drwxr-xr-x 2 2035 207 512 Oct 29 06:48 4.0-CURRENT drwxr-xr-x 14 2035 207 512 Mar 20 22:57 4.0-RELEASE drwxr-xr-x 2 2035 207 512 Mar 24 18:25 ISO-IMAGES 226 Transfer complete. ftp> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 12:50: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A782037B556 for ; Fri, 21 Apr 2000 12:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA31716; Fri, 21 Apr 2000 12:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Fri, 21 Apr 2000 12:50:02 -0700 (PDT) Message-Id: <200004211950.MAA31716@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Wilko Bulte Subject: Re: alpha/13912: unaligned access Problem seems to be affecting compiling and sa Reply-To: Wilko Bulte Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/13912; it has been noted by GNATS. From: Wilko Bulte To: freebsd-gnats-submit@FreeBSD.org, serendip@sabrecross.com Cc: Subject: Re: alpha/13912: unaligned access Problem seems to be affecting compiling and sa Date: Fri, 21 Apr 2000 21:42:46 +0200 problem also occurs in 4.0R To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 17:29: 2 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 2802B37BE7A for ; Fri, 21 Apr 2000 17:28:59 -0700 (PDT) (envelope-from rickm@sabrecross.com) Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by excalibar.sabrecross.com (8.9.3/8.9.3) with ESMTP id RAA06490 for ; Fri, 21 Apr 2000 17:28:09 -0700 (PDT) Date: Fri, 21 Apr 2000 17:28:09 -0700 (PDT) From: Rick McGee To: freebsd-alpha@FreeBSD.ORG Subject: Password file coverting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an Alpha 500a running freebsd 3.4, running lcrypt not des encryption. We are purchasing an ISP that is running BSDI 4.0 intel. Initial tests indicate the password file will not transport easy. Check the file length and the BSDi file appears to be doing 16 characters. Anyone got any ideas on how to convert this file? 10K users to manually load will be a big problem. I'd sure appreciate it. All my attempts have sure failed. Thanks Rick rickm@sabrecross.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 18:58:29 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 31C7237BED2 for ; Fri, 21 Apr 2000 18:58:27 -0700 (PDT) (envelope-from rickm@sabrecross.com) Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by excalibar.sabrecross.com (8.9.3/8.9.3) with ESMTP id SAA06825 for ; Fri, 21 Apr 2000 18:57:46 -0700 (PDT) Date: Fri, 21 Apr 2000 18:57:46 -0700 (PDT) From: Rick McGee To: freebsd-alpha@FreeBSD.ORG Subject: Re: Password file converting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Answer is, don't use MD5. I assume if I repoint the libs to des things will be ok.. Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 20:58:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id F12DD37B98D for ; Fri, 21 Apr 2000 20:58:09 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.1/8.10.1) with ESMTP id e3M3w8U11372 for ; Fri, 21 Apr 2000 22:58:08 -0500 (CDT) Date: Fri, 21 Apr 2000 22:58:08 -0500 (CDT) From: Steve Price To: freebsd-alpha@freebsd.org Subject: porting Java to the alpha Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have a wild hair to spend some time (but no promises as to how much) porting JDK2 to the alpha. A couple of questions come to mind immediately after doing some work on the i386 port. 1) What are the contents of sigjmp_buf._sjb[*]? Any pointers to some good Alpha assembly language docs would be great as I'd really like to understand the contents of src/lib/libc/alpha/gen/{,sig}setjmp.S. 2) Is there any state that I need to worry about maintaining when switching contexts that {,sig}setjmp and {,sig}longjmp don't already do for me? I know the Alpha doesn't have FP registers, but for instance on the i386 you have to (re)store the FPU mask when switching contexts. Anything like this on the Alpha that I should be aware of? TIA. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Apr 21 21:37:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 0055B37B95F for ; Fri, 21 Apr 2000 21:37:55 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.1/8.10.1) with ESMTP id e3M4brN03505 for ; Fri, 21 Apr 2000 23:37:53 -0500 (CDT) Date: Fri, 21 Apr 2000 23:37:53 -0500 (CDT) From: Steve Price To: freebsd-alpha@FreeBSD.ORG Subject: Re: porting Java to the alpha In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Apr 2000, I wrote: # 2) Is there any state that I need to worry about maintaining # when switching contexts that {,sig}setjmp and {,sig}longjmp # don't already do for me? I know the Alpha doesn't have # FP registers, but for instance on the i386 you have to # (re)store the FPU mask when switching contexts. Anything like ^^^^^^^^ I meant to say FPU registers here. The FPU mask is already handled correctly on the i386 as it is saved in the sigjmp_buf but all of you knew that already. :-) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Apr 22 2:19:25 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 1779D37B516 for ; Sat, 22 Apr 2000 02:19:23 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12iw4N-000FIC-0U; Sat, 22 Apr 2000 10:19:19 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA63336; Sat, 22 Apr 2000 10:28:07 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 22 Apr 2000 10:24:50 +0100 (BST) From: Doug Rabson To: Steve Price Cc: freebsd-alpha@freebsd.org Subject: Re: porting Java to the alpha In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 21 Apr 2000, Steve Price wrote: > Hi all, > > I have a wild hair to spend some time (but no promises as > to how much) porting JDK2 to the alpha. A couple of questions > come to mind immediately after doing some work on the i386 > port. > > 1) What are the contents of sigjmp_buf._sjb[*]? Any pointers > to some good Alpha assembly language docs would be great > as I'd really like to understand the contents of > src/lib/libc/alpha/gen/{,sig}setjmp.S. > 2) Is there any state that I need to worry about maintaining > when switching contexts that {,sig}setjmp and {,sig}longjmp > don't already do for me? I know the Alpha doesn't have > FP registers, but for instance on the i386 you have to > (re)store the FPU mask when switching contexts. Anything like > this on the Alpha that I should be aware of? > > TIA. The jmp_buf formats should be the same as struct sigcontext. Note that this *does* include FPU registers and FP control register but that for efficiency, setjmp only saves registers which are preserved over function calls. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Apr 22 10:19:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id C288A37B9AA for ; Sat, 22 Apr 2000 10:19:42 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000422171928.MHWQ22628.relay02@chello.nl> for ; Sat, 22 Apr 2000 19:19:28 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA08976 for freebsd-alpha@freebsd.org; Sat, 22 Apr 2000 19:19:31 +0200 (CEST) (envelope-from wkb) Date: Sat, 22 Apr 2000 19:19:31 +0200 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: trying to get DE203 (ISA) to work on Alpha Message-ID: <20000422191930.A8945@yedi.wbnet> Reply-To: wc.bulte@chello.nl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Question: are ISA ethernet cards supposed to work on FreeBSD/alpha (4.0R)? I have a DEC DE203 ISA card that I want to get to run on my Aspen Alpine (EB64+) but I'm not having a whole lot of success. The kernel has been built with: # DE203 device le0 at isa? port 0x300 irq 5 iomem 0xd0000 But nothing shows in the probe messages during boot: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Fri Apr 7 10:48:12 CEST 2000 root@alpine.wbnet:/usr/src/sys/compile/ALPINE EB64+ Alpha 21064A Evaluation Board 274 MHz, 274MHz 8192 byte page size, 1 processor. CPU: EV45 (21064A) major=6 minor=2 OSF PAL rev: 0x100070002012d real memory = 31473664 (30736K bytes) Physical memory chunk(s): 0x0012c000 - 0x002fbfff, 1900544 bytes (232 pages) 0x005e2000 - 0x01f0dfff, 26394624 bytes (3222 pages) avail memory = 27123712 (26488K bytes) Preloaded elf kernel "kernel" at 0xfffffc00005e0000. found-> vendor=0x1000, dev=0x0001, revid=0x01 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=7 map[10]: type 1, range 32, base 00010000, size 8 map[14]: type 1, range 32, base 81010000, size 8 found-> vendor=0x5333, dev=0x8811, revid=0x54 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=1 map[10]: type 1, range 32, base 84000000, size 26 found-> vendor=0x8086, dev=0x0484, revid=0x03 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 pci0: on pcib0 ncr0: port 0x10000-0x100ff mem 0x81010000-0x810100ff irq 7 at device 5.0 on pci0 BIOS values: SCNTL3:00 DMODE:00 DCNTL:01 CTEST3:00 CTEST4:00 CTEST5:00 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver ncr0: interrupting at APECS irq 7 ncr0: driver is using old-style compatability shims pci0: (vendor=0x5333, dev=0x8811) at 7.0 irq 1 isab0: at device 8.0 on pci0 Bus Modes: Resource Lock, Mouse function enabled Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Configuration RAM: 0C00h,0800h-08FFh Port 92: enabled isa0: on isab0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd0: irq 1 on atkbdc0 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbd0: atkbd0, generic (0), config:0x0, flags:0x1f0000, port:0x60-0x6f atkbd0: interrupting at ISA irq 1 psm0: current command byte:0061 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xb8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 04 02 14 01 05 03 07 38 3c 3a 3e 39 3d 3b 3f 04 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) mcclock0: at port 0x70-0x71 on isa0 Calibrating clock(s) ... PCC clock: 275008104 Hz (firmware 274725274 Hz) sio0: irq maps: 0x41 0x50 0x40 0x40 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A, console sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o isa_probe_children: probing PnP devices Timecounter "alpha" frequency 275008104 Hz bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached Waiting 5 seconds for SCSI devices to settle ncr0: restart (scsi reset). ACTUAL values:SCNTL3:03 DMODE:c8 DCNTL:01 CTEST3:00 CTEST4:08 CTEST5:00 (probe4:ncr0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ncr0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:ncr0:0:4:0): Invalid field in CDB sks:c8,1 Creating DISK da0 Creating DISK cd0 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 122608527398 pass0: 10.000MB/s transfers (10.000MHz, offset 8) pass1 at ncr0 bus 0 target 4 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 4.237MB/s transfers (4.237MHz, offset 8) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 122608527398 da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1222MB (2503872 512 byte sectors: 255H 63S/T 155C) Mounting root from ufs:/dev/da0a (cd0:ncr0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ncr0:0:4:0): NOT READY asc:3a,0 (cd0:ncr0:0:4:0): Medium not present cd0 at ncr0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da0: invalid primary partition table: no magic Related question: is SRM's isacfg used at all with FreeBSD? Wilko (who until now always used PCI cards on his alpha machines..) -- Wilko Bulte Powered by FreeBSD http://www.freebsd.org http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Apr 22 20:29:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B8D7F37B631 for ; Sat, 22 Apr 2000 20:29:11 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.1/8.10.1) with ESMTP id e3N3TAX30684 for ; Sat, 22 Apr 2000 22:29:10 -0500 (CDT) Date: Sat, 22 Apr 2000 22:29:10 -0500 (CDT) From: Steve Price To: freebsd-alpha@freebsd.org Subject: need help porting JDK2 to alpha Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1866096048-956460550=:16038" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1866096048-956460550=:16038 Content-Type: TEXT/PLAIN; charset=US-ASCII Evening UberHackers, I'm working on porting JDK2 to FreeBSD/Alpha. I've run into two stumbling blocks that are well beyond my skills as a programmer to overcome. The first one should be relatively easy for someone that knows their way around the Alpha architecture so I'll include the details in this message. The other one requires a bit of assembly language programming skills. If you are interested in that, contact me off-list and I'll fill you in on the details. In the JDK there is a method, initContext, for initializing the state of a context switch. I've attached the code that we use on the i386, and my first cut at the alpha code. Any and all suggestions/patches are most welcome. :) Thanks. -steve --0-1866096048-956460550=:16038 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="context.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: context.c Content-Disposition: attachment; filename="context.c" I2lmZGVmIF9fRnJlZUJTRF9fDQojaWYgZGVmaW5lZChpMzg2KQ0Kdm9pZA0K aW5pdENvbnRleHQobGpfdWNvbnRleHRfdCAqdWMsIGdzdGFja190ICpzdGFj aywgdW5zaWduZWQgaW50IHBjLA0KICAgICAgICAgdm9pZCAoKmRlYXRoX2Z1 bmMpKHZvaWQpLCB1bnNpZ25lZCBpbnQgYXJnKQ0Kew0KICAgIHVuc2lnbmVk IGNoYXIgKnNwLCAqbGltaXQ7DQogICAgaW50ICpwOw0KICAgIGNoYXIgKmZk YXRhOw0KDQogICAgbGltaXQgPSAodW5zaWduZWQgY2hhciAqKXN0YWNrLT5i YXNlIC0gc3RhY2stPnNpemU7DQogICAgc3AgPSAodW5zaWduZWQgY2hhciAq KSBzdGFjay0+YmFzZTsNCiAgICBzcCAtPSBzaXplb2Yoc3lzX3RocmVhZF90 ICopOw0KICAgIC8qIEZvcmNlIHNwIHRvIGJlIGRvdWJsZSBhbGlnbmVkISAq Lw0KICAgIHNwID0gKHVuc2lnbmVkIGNoYXIgKikoKHVuc2lnbmVkIGxvbmcp KHNwKSAmIDB4ZmZmZmZmZjgpOw0KICAgIC8qIGZvciB4ODYgdGhlIGFyZ3Mg dG8gZGVhdGhfZnVuYyBhcmUgcGFzc2VkIG9uIHRoZSBzdGFjayAqLw0KICAg IHAgPSAoaW50ICopc3A7DQogICAgKi0tcCA9IChpbnQpYXJnOwkvKiBhcmcg MiAqLw0KICAgICotLXAgPSAoaW50KXBjOwkvKiBhcmcgMSAqLw0KICAgICot LXAgPSAoaW50KTA7CS8qIHJldHVybiBQQyAqLw0KICAgICotLXAgPSAoaW50 KTA7CS8qIF9fRnJlZUJTRF9fICovDQoNCiAgICBtZW1zZXQodWMsIDAsIHNp emVvZihsal91Y29udGV4dF90KSk7DQogICAgZmRhdGEgPSAoY2hhciAqKXVj LT5mbG9hdGJ1ZjsNCiAgICBfX2FzbV9fKCJmc2F2ZSAlMCI6OiJtIiAoKmZk YXRhKSk7DQogICAgX19hc21fXygiZndhaXQiKTsNCg0KICAgIHVjLT5qbXBi dWYtPl9zamJbM10gPSAoaW50KShjaGFyICopcDsNCiAgICB1Yy0+am1wYnVm LT5fc2piWzJdID0gKGludCkoY2hhciAqKXA7DQogICAgdWMtPmptcGJ1Zi0+ X3NqYlswXSA9IChpbnQpZGVhdGhfZnVuYzsNCiAgICB1Yy0+am1wYnVmLT5f c2piW0ZCU0RfRlBVX01BU0tdID0gMHgxMjdmOwkJLyogRlBVIG1hc2sgKi8N Cn0NCiNlbGlmIGRlZmluZWQoYWxwaGEpDQp2b2lkDQppbml0Q29udGV4dChs al91Y29udGV4dF90ICp1YywgZ3N0YWNrX3QgKnN0YWNrLCB1bnNpZ25lZCBp bnQgcGMsDQogICAgICAgICB2b2lkICgqZGVhdGhfZnVuYykodm9pZCksIHVu c2lnbmVkIGludCBhcmcpDQp7DQogICAgdW5zaWduZWQgY2hhciAqc3A7DQoN CiAgICBtZW1zZXQodWMsIDAsIHNpemVvZihsal91Y29udGV4dF90KSk7DQoN CiAgICBzcCA9ICh1bnNpZ25lZCBjaGFyICopc3RhY2stPmJhc2U7DQogICAg c3AgLT0gc2l6ZW9mKHN5c190aHJlYWRfdCAqKTsNCiAgICAvKiBGb3JjZSBz cCB0byBiZSBkb3VibGUgYWxpZ25lZCEgKi8NCiAgICBzcCA9ICh1bnNpZ25l ZCBjaGFyICopKCh1bnNpZ25lZCBsb25nKShzcCkgJiB+N0wpOw0KDQogICAg LyoNCiAgICAgKiBYWFggSU1QTEVNRU5UIE1FISEhDQogICAgICoNCiAgICAg KiBXZSBzdGlsbCBuZWVkIHRvIGRldGVybWluZSB3aGVyZSBpbiB0aGUgc2ln am1wX2J1ZiBzdHJ1Y3R1cmUgdG8gc3R1ZmYNCiAgICAgKiBkZWF0aF9mdW5j LCBwYywgYW5kIGFyZyB0byBtYWtlIHRoaXMgYWN0dWFsbHkgd29yay4NCiAg ICAgKi8NCiAgICB1Yy0+am1wYnVmLT5fc2piW0ZCU0RfU1RBQ0tfUE9JTlRF Ul0gPSAobG9uZylzcDsNCn0NCiNlbHNlDQojZXJyb3IgYXJjaGl0ZWN0dXJl IHVuc3VwcG9ydGVkDQojZW5kaWYNCg== --0-1866096048-956460550=:16038-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message