Date: Mon, 5 Jun 95 07:34 CDT From: gordon@sneaky.lonestar.org (Gordon Burditt) To: bugs@FreeBSD.org Subject: Comments on 2.0.5-ALPHA boot floppy - Jun 4 Message-ID: <m0sIbMo-000E0iC@hammy.lonestar.org>
next in thread | raw e-mail | index | archive | help
I just tried out the latest 2.0.5 ALPHA boot disk, and things don't seem to be working completely. And I didn't even TRY to do an install yet. System: 486DX/33, 8 meg, IDE and SCSI disk, with DOS and FreeBSD 1.1.5.1 partitions on each. More hardware details at end. The boot disk: FreeBSD 2.0.5-ALPHA, Jun 4. This may be ambiguous, and thanks to ftpmail latency, I don't know the exact time but it was sometime in the afternoon (Central Daylight Time). cksum: 499586753 1228800 floppies/boot.flp When I boot up, there are half a dozen lines of messages on the first screen just before it turns blue. I can't read much more than "etc/sysinstall" in repeated tries. The second screen shows that the system really DOES NOT LIKE my 1.1.5.1 disklabels and complains that several are "not entirely within the slice". Does this mean there is no chance for 1.1.5.1 and 2.0.5 to co-exist due to incompatible disklabel format, even if they leave each other's partitions alone? Actually, I'd eventually switch over entirely, but this makes trying it out rather final. The system finds network devices 'cuaa0' and 'cuaa1' which the -c option doesn't list. Are these PPP/SLIP pseudo-devices? When I exit, I get a complaint that it cannot open /etc/sysconfig. This happens even if I just read documentation and exit. Is this normal? I am not attempting to actually do an install yet; I do not have direct net access, and alternatives are several weeks of ftpmail getting the distribution, then install by tape, or wait for the CDROM, which might be faster, and probably costs less than the tape to hold it all. The main objectives right now are to see if 2.0.5 is worth upgrading from 1.1.5.1, read the documentation, figure out a good partition setup, and play around with specifying a configuration without actually committing. The (M)edia menu item refuses to let me select a tape drive as the device to load the distribution from unless there is a tape in the SCSI tape drive (see attachment at end for hardware details) just after the kernel finishes identifying all the devices. Otherwise, I get a message st0(aha0:1:0) NOT READY csi 40,0,0,0 on the second screen, and then it doesn't think I have a tape device and won't let me select one. I think it is at least worth mentioning this in the documentation if it's not fixed. I like the -c option on boot, but maybe for 2.1 whether or not to save the changes permanently ought to be a settable option along with the changes. This makes one-shot test configurations a little less hazardous as you won't forget something you need to undo, but not all changes are one-shot. Is the configuration saved in /kernel, or in what you booted from (if different)? Gordon L. Burditt sneaky.lonestar.org!gordon My system configuration, using FreeBSD 1.1.5.1. (The ridiculous bunch of configurations for network cards is used to figure out what the hardware jumpers do on cheap used cards that came with no documentation. Change jumper, boot, see what's detected.) The most relevant parts of this are probably the CPU and memory, SCSI controller, IDE & SCSI disks and SCSI tape drive. FreeBSD 1.1.5.1(RELEASE) (HAMMYNET) #0: Mon Jun 5 04:21:18 CDT 1995 gordon@hammy.lonestar.org:/usr/src/sys/compile/HAMMYNET CPU: i486DX (486-class CPU) real memory = 8257536 (2016 pages) avail memory = 7233536 (1766 pages) using 150 buffers containing 1228800 bytes of memory Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16450 sio2 at 0x3e8-0x3ef irq 12 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 15 on isa sio3: type 16550A lpt0 at 0x378-0x37f on isa lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff tan0 at 0x108-0x109 irq 10 maddr 0xfe0000 msize 65536 on isa tan1 not probed due to irq conflict with sio3 at 15 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: [0: fd0: 1.44MB 3.5in] [1: fd1: 1.2MB 5.25in] wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): <MAXTOR LXT-535A> wd0: 504MB (1032192 total sec), 1024 cyl, 16 head, 63 sec, bytes/sec 512 wdc1 not probed due to irq conflict with sio3 at 15 aha0: reading board settings, dma=5 int=11 (bus speed defaulted) aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle aha0 targ 0 lun 0: type 0(direct) fixed SCSI2 aha0 targ 0 lun 0: <SEAGATE ST41601N 3000> sd0: 1307MB (2676846 total sec), 2099 cyl, 17 head, 75 sec, bytes/sec 512 aha0 targ 1 lun 0: type 1(sequential) removable SCSI1 aha0 targ 1 lun 0: <WANGTEK 51000 SCSI REV73J > st0: density code 0xf, 512-byte blocks, write-enabled aha0 targ 2 lun 0: type 5(readonly) removable SCSI2 aha0 targ 2 lun 0: <SONY CD-ROM CDU-541 2.6a> cd0: cd present.[208702 x 2048 byte records] ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:40:c7:21:b7:f0, type NE2000 (16 bit) bpf: ed0 attached ed1 at 0x340-0x35f irq 5 on isa ed1: address 00:40:c7:21:c8:65, type NE2000 (16 bit) bpf: ed1 attached ed2 not probed due to irq conflict with ed0 at 9 ed3 not probed due to irq conflict with ed0 at 9 ed4 not probed due to irq conflict with ed0 at 9 ed5 not probed due to irq conflict with ed0 at 9 ed6 not probed due to irq conflict with ed0 at 9 ed6 not probed due to I/O address conflict with ed1 at 0x340 ie0 not found at 0x360 is0 not probed due to irq conflict with tan0 at 10 el0 not probed due to I/O address conflict with ed0 at 0x300 el0 not probed due to irq conflict with ed0 at 9 el1 not probed due to I/O address conflict with ed1 at 0x340 el1 not probed due to irq conflict with ed1 at 5 npx0 on motherboard bpf: lo0 attached bpf: ppp0 attached bpf: sl0 attached bpf: sl1 attached
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0sIbMo-000E0iC>