Re: Problems booting 4.2 CD on two older machines.
On 29/10/2007, at 5:24 PM, Craig Findlay wrote: As other have already said, it seems to only be a problem with quite old PC's. At least mine is. (see dmesg below) Cheers, Craig OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 234 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX 4.2 official CD works for me on Dell Optiplex ~500Mhz - I'll get exact details and dmesg tomorrow if of interest to anyone. Also installed on newer Compaq Celeron laptop - again, no CD / installation issues. With the 4.1 release, the CD set I bought personally was fine, but the CD set for work failed to read CD 1 (so I just used the personal set to install at work.) I did not investigate further - just assumed dud CD.
Re: Problems booting 4.2 CD on two older machines.
Hi, On 29/10/2007, Nick Holland [EMAIL PROTECTED] wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? The bios tries to boot, but does not find the CD bootable and falls back on the hard disk. And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). No. Not on 2 machines I tried on the other day, but it does boot on my main deskto pand laptop (2 completely different, more modern machines). Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) Unsure, havent tried. For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? Yes If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? I have tried multiple cd drives. Does a CD made from install42.iso boot? unsure. Does a CD made from cd42.iso boot? unsure Does a CD made from cdemu42.iso boot? unsure - I have no CDR's to try this out... If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick. Yes, perhaps it is something obscure in manufacturing. Could be a change of the brand of media for example, or something strange. Not a lot we can do about it. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
On Sun, 28 Oct 2007 22:48:20 -0400, Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. Well, I read Theo's message and I know we can't ask for any changes to the issue CDs. Shit happens. I just get my terrier genes showing a bit because it's a challenge. Don't like being locked out of solutions and knowing what is needed to prevent repetition. So I have done a bit of detective work and maybe it will get shot down or else it will pop up one of those cartoon lightbulbs for somebody who will then improve my education by informing me about the rest of the story. Here is what I know so far about the differences in the CDs that boot or don't on older machines: All the CDs that boot have a copy of the cdbr content before 64MB from the start of the CD whereas the 4.2 release has it located at 76,398,592 bytes in. I have used (in addition to 4.2 Official build 375) snapshots for kernel build 372, 373, 374 and 461. 372, 373 and 374 all have the cdbr code at 60,293,120 bytes and 461 has it at 60,854,272 and all of those boot. Here is what I don't know (about this issue, not LTUAE!): Is 67,108,864 a possible barrier for old BIOSes ? Do we have any way to predetermine where that code will be located on the CD? Am I chasing a red herring? I'd like to keep a bunch of low(er) powered servers going for a while and I as I said earlier I can do it without a bootable CD even tho' those boxes (except one) don't have a floppy drive either. My concern is more for some young guys with only one old dumpster surprise and no previous experience with OpenBSD, trying to give it a try using a buddy's CD. Apart from my mad curiosity, of course! Rod/ (Please reply to the list even if it's Theo or Nick telling me to let go of it.) -- Write a wise saying and your name will live on forever. - Anonymous
Re: Problems booting 4.2 CD on two older machines.
Hi, Great work on the detailed inspection. On 29/10/2007, RW [EMAIL PROTECTED] wrote: Is 67,108,864 a possible barrier for old BIOSes ? But weren't peoples old machines booting home made 4.2 cd's just fine? My concern is more for some young guys with only one old dumpster surprise and no previous experience with OpenBSD, trying to give it a try using a buddy's CD. Dumpster surprise... yes.. A couple of us use OpenBSD for workstation/university stuff. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
Hi, On 28/10/2007, RW [EMAIL PROTECTED] wrote: So maybe that narrows it a bit if we can find out what relevant factor changed between those and release. I guess it would be around here somplace: http://www.openbsd.org/cgi-bin/cvsweb/src/distrib/ I had a quick look in the i386 folder but dont see any obvious relevant changes. Do newer snapshots work on this hardware? -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
Barry Miller wrote: On Sat, Oct 27, 2007 at 05:51:25PM -0700, kim wrote: When the CD that I burned booted up, I got a message at boot: /etc/boot.conf too large But that came from cdboot, right? I don't think the rest of us in this thread are getting that far. The error message came as I was successfully booting with the new burned CD.
Re: Problems booting 4.2 CD on two older machines.
On Sun, 28 Oct 2007 11:51:37 +, Edd Barrett wrote: Hi, On 28/10/2007, RW [EMAIL PROTECTED] wrote: So maybe that narrows it a bit if we can find out what relevant factor changed between those and release. I guess it would be around here somplace: http://www.openbsd.org/cgi-bin/cvsweb/src/distrib/ I had a quick look in the i386 folder but dont see any obvious relevant changes. Do newer snapshots work on this hardware? Well, install42.iso from Oct 26 does. Don't know about others, sorry, Rod (please don't CC me. I'm on the list and the reply-to is a limited use, burn when spam arrives facility 8-) ) whereas the list mail always get through due to classy filtering. In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod.
Re: Problems booting 4.2 CD on two older machines.
This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? Does a CD made from install42.iso boot? Does a CD made from cd42.iso boot? Does a CD made from cdemu42.iso boot? If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick.
Re: Problems booting 4.2 CD on two older machines.
I am seeing the same issue: On my OBSD machine: Using disk 1 on the openBSD 4.1 distro, it boots like a champ. Using disk 1 on the OpenBSD 4.2 distro, it skips the cd and goes on to the next step. By Skip, my guess is that it doesnt find an appropriate bootblock on the cd to boot from, and then goes to the next device in the boot order. I even went so far as to try different positions in the IDE chain for the cd drive (secondary/slave, primary/master, but no difference). I also tried disabling all other bootable devices in bios and leaving only the CD-rom as a viable boot device, and it still would not boot. My solution was to burn cd42.iso to a cd and boot off of that. That worked well for me. Motherboard: tyan trinity I845e bios rev:v1.10 As found here: http://www.tyan.com/archive/products/html/trinityi845e.html Answers to other questions: - The 4.2 cd does boot sucessfully on another machine. - I didnt move the CD-rom drive to another machine, but it seems ok, considering it boots 4.1. - cd42.iso does boot. - I did not see a emu or install iso on the 4.2 disk 1. (Find reveals only cd42.iso) Hope that helps --C p.s. I'll send my dmesg over as well. On Sun, 28 Oct 2007, Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? Does a CD made from install42.iso boot? Does a CD made from cd42.iso boot? Does a CD made from cdemu42.iso boot? If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick.
Re: Problems booting 4.2 CD on two older machines.
On Sun, 28 Oct 2007 22:48:20 -0400, Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? It says: Bootable CD does not exist ... and goes off to the HDD. And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). For me: No Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) I didn't make the copy but simply imaged the release CD to an iso file. Zero errors. For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? Yes. If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? I can't do that test. I have 4 identical no-go machines and only one other that I may not swap the drive out of plus 2 laptops that won't swap drives with the desktops. Besides I have the 4 identical boxes with MX36LE A-Open mobos that I posted dmesgs from yesterday. There are 2 with Diamond 52X CDR, one with a combo drive and the one that made me think I had a buggy DVD 2 layer/dvd-ram/+/-/cdr/rw/ latest and greatest. They all fail on the release CD or a copy of it. I don't believe it is drive related. BIOS maybe ? Whoops! I just remembered an old clunker around here where I am. 766 Celeron + combo drive. It won't boot release but does do the others. Does a CD made from install42.iso boot? Can't test that until Friday (Australian time) when it gets onto ftp. 8-) BUT install42.iso from Oct 26 snapshot does boot! As does install42.iso from Aug 24 (which had a build #374 kernel) Does a CD made from cd42.iso boot? Can't tell atm. Does a CD made from cdemu42.iso boot? Can't tell atm. I'm away from the necessary resources for a while. If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. It would look like a crook boot track except for all the boxes that it works on, including that one I was trying to get four copies onto ;-) Anything else I can assist with? It's my job to help wherever I can, is it not? I can get the OS onto any of those boxes without a CD but not everyone is as well placed. ttys, Rod/ From the land down under: Australia. Do we look umop apisdn from up over?
Re: Problems booting 4.2 CD on two older machines.
Apologies to the list for not having all my data ahead of time. After finding and burning install42.iso (from the 10/28 snapshot), I can say that it boots. (at least up to the (I)nstall, (U)pgrade or (S)hell? prompt. The cdemu42.iso (also from the 10/28 snapshot) works as well. --Colin On Sun, 28 Oct 2007, Colin Corbett wrote: I am seeing the same issue: On my OBSD machine: Using disk 1 on the openBSD 4.1 distro, it boots like a champ. Using disk 1 on the OpenBSD 4.2 distro, it skips the cd and goes on to the next step. By Skip, my guess is that it doesnt find an appropriate bootblock on the cd to boot from, and then goes to the next device in the boot order. I even went so far as to try different positions in the IDE chain for the cd drive (secondary/slave, primary/master, but no difference). I also tried disabling all other bootable devices in bios and leaving only the CD-rom as a viable boot device, and it still would not boot. My solution was to burn cd42.iso to a cd and boot off of that. That worked well for me. Motherboard: tyan trinity I845e bios rev:v1.10 As found here: http://www.tyan.com/archive/products/html/trinityi845e.html Answers to other questions: - The 4.2 cd does boot sucessfully on another machine. - I didnt move the CD-rom drive to another machine, but it seems ok, considering it boots 4.1. - cd42.iso does boot. - I did not see a emu or install iso on the 4.2 disk 1. (Find reveals only cd42.iso) Hope that helps --C p.s. I'll send my dmesg over as well. On Sun, 28 Oct 2007, Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). Does a copy of the official CD boot? (Is there any error reported when trying to make a copy?) For the people that say the official CD doesn't boot, do they have other machines they /can/ boot the official CD? If people are spotting some machines that do and some that don't, what happens if you move the CD drive from one that does boot to one that doesn't? Does the problem follow the machine or the drive? Does a CD made from install42.iso boot? Does a CD made from cd42.iso boot? Does a CD made from cdemu42.iso boot? If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick.
Re: Problems booting 4.2 CD on two older machines.
Nick Holland wrote: This thread is a bit bothersome for a lot of reasons. However, there is a lack of hard info so far. When you say it isn't booting the CD, what does this mean? Does it try but fail with some error? Does it not even stop at the CD on the way to attempting to boot the hard disk? Does not even stop at the CD. And let's see what the actual scope of the problem is: Does the official CD boot? (I think the point of this thread is for some people, no it doesn't). No, it doesn't. Mine is an official CD. If install42.iso or cd42.iso boot, don't be looking for code changes, sounds like we had a bum pressing of CDs or some other quirk in the way the master was made, as they all use the same boot process. Still needs to be identified and fixed for 4.3, but it wouldn't be a code problem. Nick. As other have already said, it seems to only be a problem with quite old PC's. At least mine is. (see dmesg below) Cheers, Craig OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 234 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX cpu0: F00F bug workaround installed real mem = 66678784 (65116K) avail mem = 52531200 (51300K) using 844 buffers containing 3457024 bytes (3376K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 12/23/97, BIOS32 rev. 0 @ 0xfb190 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xb658 pcibios0: PCI BIOS has 6 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 9 10 11 12 pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371AB PIIX4 ISA rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82439TX System rev 0x01 pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x01 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: QUANTUM FIREBALL SE3.2A wd0: 16-sector PIO, LBA, 3079MB, 6306048 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, CD-ROM CR-585, ZM50 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 0, DMA mode 1 uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x01: SMI iic0 at piixpm0 sis0 at pci0 dev 8 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:09:5b:be:0a:76 nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 vga1 at pci0 dev 9 function 0 S3 ViRGE DX/GX rev 0x01 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) sis1 at pci0 dev 10 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 12, address 00:09:5b:e0:c6:ff nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 fxp0 at pci0 dev 11 function 0 Intel 8255x rev 0x04, i82558: irq 11, address 00:a0:c9:8f:45:72 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask eb65 netmask ff65 ttymask ffe7 pctr: 586-class performance counters and user-level cycle counter enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: Problems booting 4.2 CD on two older machines.
As other have already said, it seems to only be a problem with quite old PC's. At least mine is. (see dmesg below) All of these problems have nothing to do with OpenBSD. The BIOS itself decides to not even give the CD a try. Two people have said that copying the CD to a CDR ... makes that CDR work. The first few blocks of the CD are basically identical to previous releases. It sounds like something physical, ie. at the plant, is involved. It works on almost all machines, except a few very old machines. I'll ask around about plant / physical issues, but I don't see how we're going to be able to do anthing about it this release. Oh well.
Re: Problems booting 4.2 CD on two older machines.
Theo de Raadt wrote: As other have already said, it seems to only be a problem with quite old PC's. At least mine is. (see dmesg below) All of these problems have nothing to do with OpenBSD. The BIOS itself decides to not even give the CD a try. Two people have said that copying the CD to a CDR ... makes that CDR work. The first few blocks of the CD are basically identical to previous releases. It sounds like something physical, ie. at the plant, is involved. It works on almost all machines, except a few very old machines. I'll ask around about plant / physical issues, but I don't see how we're going to be able to do anthing about it this release. the patient amongst us might be inclined to remove said machine's hard drive, install on a machine of the same architecture that actually boots the CD, re-install the now bootable drive and boot openbsd. as long as it stays openbsd there is no problem here :). cheers, jake Oh well.
Problems booting 4.2 CD on two older machines.
Hi, A couple of friends have been wanting to try out OpenBSD 4.2 on their machines, but the 4.2 disk will not boot whereas the 4.1 disk will. I know the 4.2 disk can be booted, because it works on my new hardware. One of the machines I have installed by installing 4.1 and using a bsd.rd to upgrade, but the other box has problems copying the sets onto disk (I have tried a new disk, cable and IDE channel). I'm not sure if this is a hardware fault, but I would like to boot the 4.2 cd anyway, in case it was a bug in 4.1. Has anyone else had problems booting the 4.2 CD? And is there a workaround? Thanks -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
On 27/10/2007, Edd Barrett [EMAIL PROTECTED] wrote: Hi, A couple of friends have been wanting to try out OpenBSD 4.2 on their machines, but the 4.2 disk will not boot whereas the 4.1 disk will. I should mention these are i386 boxes. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
On Sat, Oct 27, 2007 at 07:01:04PM +0100, Edd Barrett wrote: A couple of friends have been wanting to try out OpenBSD 4.2 on their machines, but the 4.2 disk will not boot whereas the 4.1 disk will. [...] Has anyone else had problems booting the 4.2 CD? And is there a workaround? I have the same problem. My 4 year old i386 test box doesn't see it as bootable (4.[01] CDs work fine). The CD seems ok - no problem pulling kernels, sets, and packages off it. It boots on my newer machines, and even on an ancient (ca. 1999) NetVista. I haven't had any other issues with the drive itself. dmesg after manual upgrade on the no-boot box: OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) CPU 1.70GHz (GenuineIntel 686-class) 1.70 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 259551232 (247MB) avail mem = 243310592 (232MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/14/03, BIOS32 rev. 0 @ 0xfb2f0, SMBIOS rev. 2.2 @ 0xf0800 (34 entries) bios0: vendor Phoenix Technologies, LTD version 6.00 PG date 06/14/2003 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdf84 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/192 (10 entries) pcibios0: PCI Exclusive IRQs: 5 9 10 11 pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xb000! 0xcc000/0x1800 0xce000/0x1800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845G/GL rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82845G/GL Video rev 0x03: aperture at 0xe000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x02: irq 5 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x02: irq 10 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x02: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x02: irq 9 usb0 at ehci0: USB revision 2.0 uhub0 at usb0: Intel EHCI root hub, rev 2.00/1.00, addr 1 ppb0 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x82 pci1 at ppb0 bus 1 fxp0 at pci1 dev 3 function 0 Intel 8255x rev 0x10, i82551: irq 11, address 00:e0:81:52:b5:a9 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci1 dev 6 function 0 Intel 8255x rev 0x10, i82551: irq 10, address 00:e0:81:52:b5:aa inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 ichpcib0 at pci0 dev 31 function 0 Intel 82801DB LPC rev 0x02: 24-bit timer at 3579545Hz pciide0 at pci0 dev 31 function 1 Intel 82801DB IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST380011A wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors wd1 at pciide0 channel 0 drive 1: SAMSUNG HD300LD wd1: 16-sector PIO, LBA48, 286168MB, 586072368 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, CD-224E, 1.9A SCSI0 5/cdrom removable cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x02: irq 5 iic0 at ichiic0 it8712 at iic0 addr 0x2d not configured iic0: addr 0x2d 00=11 01=10 02=00 03=07 04=00 05=00 06=00 07=00 08=00 09=00 0a=1f 0b=5b 0c=6a 0d=18 0f=13 13=70 14=00 15=00 16=00 17=00 18=6a 19=6a 1a=6a 1b=6a 1c=6a 1d=6a 1e=6a 1f=6a 20=6a 21=5d 22=cf 23=c1 24=b8 25=3b 26=47 27=b7 29=16 2a=30 2b=2e 2c=6a 2d=6a 2e=6a 2f=6a 48=2d 51=1c 52=7f 53=7f 54=7f 58=90 59=78 5a=fd 5b=12 5c=80 5d=00 5e=00 5f=00 60=7f 61=7f 62=7f 63=7f 64=7f 65=00 66=00 67=00 68=7f 69=7f 6a=7f 6b=7f 6c=7f 6d=00 6e=00 6f=00 70=7f 71=7f 72=7f 73=7f 74=00 75=00 76=00 77=00 80=11 81=10 82=00 83=00 84=00 85=00 86=00 87=00 88=00 89=00 8a=1f 8b=5b 8c=6a 8d=18 8f=13 93=70 94=00 95=00 96=00 97=00 98=6a 99=6a 9a=6a 9b=6a 9c=6a 9d=6a 9e=6a 9f=6a a0=6a a1=5d a2=cf a3=c1 a4=b7 a5=39 a6=49 a7=b7 a9=16 aa=30 ab=2e ac=6a ad=6a ae=6a af=6a c8=2d d1=1c d2=7f d3=7f d4=7f d8=90 d9=78 da=fd db=12 dc=80 dd=00 de=00 df=00 e0=7f e1=7f e2=7f e3=7f e4=7f e5=00 e6=00 e7=00 e8=7f e9=7f ea=7f eb=7f ec=7f ed=00 ee=00 ef=00 f0=7f f1=7f f2=7f f3=7f f4=00 f5=00 f6=00 f7=00: it8712 usb1 at uhci0: USB revision 1.0 uhub1 at usb1: Intel UHCI root hub, rev 1.00/1.00, addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2: Intel UHCI root hub, rev 1.00/1.00, addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3: Intel UHCI root hub, rev 1.00/1.00, addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0:
Re: Problems booting 4.2 CD on two older machines.
On Sat, 27 Oct 2007 19:30:27 -0400, Barry Miller wrote: On Sat, Oct 27, 2007 at 07:01:04PM +0100, Edd Barrett wrote: A couple of friends have been wanting to try out OpenBSD 4.2 on their machines, but the 4.2 disk will not boot whereas the 4.1 disk will. [...] Has anyone else had problems booting the 4.2 CD? And is there a workaround? I have the same problem. My 4 year old i386 test box doesn't see it as bootable (4.[01] CDs work fine). The CD seems ok - no problem pulling kernels, sets, and packages off it. It boots on my newer machines, and Another one (user but 4 identical PCs). The first (to exhibit the problem) machine I tried to upgrade to 4.2 had a CD drive that was dead some time ago but I only replaced it when I took it out of service to upgrade. When it failed to boot the 4.2 release CD I figured that a fancy DVD burner with all the bells whistles must have scared the old BIOS. I just planted a bsd.rd onto it across the network and upgraded using the CD which as the others have said mounts and reads perfectly. I cannot see any pertinent difference in 4.1cd boot dmesg and 4.2 installed dmesg but my eyes may have missed something so here is one of each: 4.2 installed. OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(TM) CPU 1300MHz (GenuineIntel 686-class) 1.31 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 259555328 (247MB) avail mem = 243314688 (232MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/27/02, BIOS32 rev. 0 @ 0xfb4b0, SMBIOS rev. 2.3 @ 0xf0800 (35 entries) bios0: vendor Phoenix Technologies, LTD version 6.00 PG date 02/27/2002 bios0: VIA Technologies, Inc. VT8601 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xde94 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde10/128 (6 entries) pcibios0: PCI Exclusive IRQs: 10 11 12 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xc000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8601 PCI rev 0x05 ppb0 at pci0 dev 1 function 0 VIA VT82C601 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Trident CyberBlade i1 rev 0x6a wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST340016A wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LITE-ON, DVDRW LH-20A1P, KL0N SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 12 uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x1a: irq 12 viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40: 24-bit timer at 3579545Hz rl0 at pci0 dev 17 function 0 Realtek 8139 rev 0x10: irq 11, address 00:01:80:20:88:ab rlphy0 at rl0 phy 0: RTL internal PHY isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb0 at uhci0: USB revision 1.0 uhub0 at usb0: VIA UHCI root hub, rev 1.00/1.00, addr 1 usb1 at uhci1: USB revision 1.0 uhub1 at usb1: VIA UHCI root hub, rev 1.00/1.00, addr 1 biomask f765 netmask ff65 ttymask ffe7 pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 root on wd0a swap on wd0b dump on wd0b 4.1 CD booted to shell: OpenBSD 4.1 (RAMDISK_CD) #248: Sat Mar 10 19:32:46 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Celeron(TM) CPU 1300MHz (GenuineIntel 686-class) 1.31 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,F XSR,SSE real mem = 259555328 (253472K) avail mem = 230711296 (225304K) using 3199 buffers containing 13103104 bytes (12796K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 02/27/02, BIOS32 rev. 0 @ 0xfb4b0, SMBIOS rev. 2.3 @ 0xf0800 (35 entries) bios0: VIA Technologies, Inc.
Re: Problems booting 4.2 CD on two older machines.
Same problem here on a 3 year old i386. I copied the iso file from the install CD ( /4.2/i386/cd42.iso ) and burned it to another CD. This booted fine, and then I copied all of the OpenBSD file sets from the install CD to complete the setup. When the CD that I burned booted up, I got a message at boot: /etc/boot.conf too large I will submit a bug report tomorrow. I have ordered another install CD from the supplier.
Re: Problems booting 4.2 CD on two older machines.
Edd Barrett wrote: On 27/10/2007, Edd Barrett [EMAIL PROTECTED] wrote: Hi, A couple of friends have been wanting to try out OpenBSD 4.2 on their machines, but the 4.2 disk will not boot whereas the 4.1 disk will. I should mention these are i386 boxes. Same problem on an old Pentium Box. I wanted to upgrade it from 4.0 to 4.2 4.0 to 4.1 went fine. 4.2 CD was not recognised as bootable. I left it for now as I had more pressing things to do, but if anyone has an explanation and/or workaround I will be interested. Cheers, Craig
Re: Problems booting 4.2 CD on two older machines.
On 28/10/2007, kim [EMAIL PROTECTED] wrote: Same problem here on a 3 year old i386. I copied the iso file from the install CD ( /4.2/i386/cd42.iso ) and burned it to another CD. This booted fine, and then I copied all of the OpenBSD file sets from the install CD to complete the setup. When the CD that I burned booted up, I got a message at boot: /etc/boot.conf too large I will submit a bug report tomorrow. I have ordered another install CD from the supplier. So I am not going insane. This is good I suppose. But why are these machines not booting the CD's properly? -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: Problems booting 4.2 CD on two older machines.
On Sat, Oct 27, 2007 at 07:01:04PM +0100, Edd Barrett wrote: Has anyone else had problems booting the 4.2 CD? Here's another can read the CD but not boot from it machine: OpenBSD 4.1 (GENERIC) #1435: Sat Mar 10 19:07:45 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 934 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE real mem = 1073311744 (1048156K) avail mem = 971960320 (949180K) using 4278 buffers containing 53788672 bytes (52528K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 08/29/01, BIOS32 rev. 0 @ 0xfb3b0, SMBIOS rev. 2.2 @ 0xf0800 (46 entries) bios0: VIA Technologies, Inc. VT82C694X apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdd94 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdcf0/160 (8 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xcc000/0x800 0xcd000/0x800 0xce000/0x800 0xcf000/0x800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT82C691 PCI rev 0xc4 ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mach64 GM rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: MAXTOR 6L060J3 wd0: 16-sector PIO, LBA, 57259MB, 117266688 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MITSUMI, CD-ROM FX4831T!A, R02G SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 7 function 3 VIA VT83C572 USB rev 0x1a: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40 xl0 at pci0 dev 8 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 11, address 00:04:75:ad:65:c7 exphy0 at xl0 phy 24: 3Com internal media interface xl1 at pci0 dev 10 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 5, address 00:04:75:ad:5d:ac exphy1 at xl1 phy 24: 3Com internal media interface xl2 at pci0 dev 11 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 10, address 00:04:75:80:bb:9e exphy2 at xl2 phy 24: 3Com internal media interface xl3 at pci0 dev 12 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 11, address 00:04:75:ad:5d:10 exphy3 at xl3 phy 24: 3Com internal media interface isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask eb5d netmask ef7d ttymask pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: Problems booting 4.2 CD on two older machines.
On Sun, 28 Oct 2007 01:48:54 +, Edd Barrett wrote: But why are these machines not booting the CD's properly? I was testing snapshots up to build #374. One of my no-boot on #375 (release) boxes was installed from either #373 or #374 (can't tell now) using snapshot .iso file So maybe that narrows it a bit if we can find out what relevant factor changed between those and release. I have a spare box that will let me provide testing assistance if required. Mind you, if the problem never gets fixed it is not the end of the world. When it comes to installs TIMTOWTDI prevails. I wish I'd had the time to do the snap that was #375 as my test box for snaps was one of the problem varietyand that's why we do snapshot testing, innit? Rod/ From the land down under: Australia. Do we look umop apisdn from up over?
Re: Problems booting 4.2 CD on two older machines.
On Sat, Oct 27, 2007 at 05:51:25PM -0700, kim wrote: When the CD that I burned booted up, I got a message at boot: /etc/boot.conf too large But that came from cdboot, right? I don't think the rest of us in this thread are getting that far.
