From owner-freebsd-alpha Mon Aug 7 10: 7:38 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 3619137BC88 for ; Mon, 7 Aug 2000 10:07:33 -0700 (PDT) (envelope-from craig-burgess@home.net) Received: from home.net ([24.0.178.21]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000807170730.JGJW8825.femail2.sdc1.sfba.home.com@home.net> for ; Mon, 7 Aug 2000 10:07:30 -0700 Message-ID: <398EED47.BA82D659@home.net> Date: Mon, 07 Aug 2000 10:09:27 -0700 From: Craig Burgess X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-alpha mailing list Subject: Problems & Discoveries (5-current) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A couple of weeks ago I thought I broke the installation, but it ended up only very bent. Starting with 5-current from April I did cvsup for new source and discovered the new scheme and syntax for devices. Unfortunately for me, I didn't notice the new kernel line 'hints' and the kernel built without it would panic at boot for no system clock. Now, in retrospect I can see that it would have been a whole lot easier to copy GENERIC and adjust the copy, but I already had a functional kernel configuration file, I thought. Since I hadn't discovered that I needed to add one brief line to the kernel config file I tried to cvsup src for 4 which only made matters worse, so back to 5 and then I discovered that the kernel would build and boot when configuration file properly referenced the 'hints' file. Unfortunately the resulting mess would boot, but things were badly bent; e.g., the machine would hang at 'synching disks...' at any kind of graceful shutdown or restart of the system. There were other anomalies, too, which isn't suprising. I decided that the best thing to do was get rid of the whole mess and start over. I made two discoveries about building the boot floppies: a "quick format" (DOS) of a diskette which previously contained a boot image appears to work, but the result of using fdimage to write to the diskette does not result in a useable diskette. I also discovered that a very HOT floppy drive does not write a good image in any case ... The 5-current boot images appear to absolutely require ad0 or they do not work -- panic when the device is not found. I was able to get the 4.1-release images to work and the system is back performing most of the things it did before but with much more grace. One of these days I may try to cvsup -current but now I know that the syntax of the kernel configuration will be different. ===================== EB164 Digital AlphaPC 164 500 MHz, 500MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=2 extensions=0x1 OSF PAL rev: 0x1000800020117 real memory = 265904128 (259672K bytes) avail memory = 252829696 (246904K bytes) Preloaded elf kernel "kernel" at 0xfffffc000064c000. md0: Malloc disk cia0: ALCOR/ALCOR2, pass 3 cia0: extended capabilities: 21 pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x10180-0x101bf irq 2 at device 5.0 on pci0 xl0: interrupting at CIA irq 2 xl0: Ethernet address: 00:60:08:19:48:35 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: <3D Labs model 0009 graphics accelerator> at 6.0 irq 0 xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0x10100-0x1017f mem 0x830a0100-0x830a017f irq 1 at device 7.0 on pci0 xl1: interrupting at CIA irq 1 xl1: Ethernet address: 00:10:4b:9c:da:ee miibus1: on xl1 xlphy0: <3Com internal media interface> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 8.0 on pci0 isa0: on isab0 ncr0: port 0x10000-0x100ff mem 0x830a0000-0x830a00ff irq 3 at device 9.0 on pci0 ncr0: interrupting at CIA irq 3 ncr0: driver is using old-style compatability shims atapci0: port 0x101c0-0x101cf irq 5 at device 11.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 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,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at ISA irq 12 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3bf irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Polled port plip0: cannot reserve interrupt, failed. ppc0: interrupting at ISA irq 7 Timecounter "alpha" frequency 499998180 Hz IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled ata0-slave: identify retries exceeded ad0: 2441MB [4960/16/63] at ata0-master using WDMA2 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ncr0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) -------------- craig -- ... mind like a steel trap: things wander in and get mangled ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message