Re: OpenBSD 4.1 install issue?? [RESOLVED]
Hi, On Mon, 21.05.2007 at 18:00:30 +0200, Toni Mueller <[EMAIL PROTECTED]> wrote: > Is this problem worth opening a bug on the OpenBSD web site? after reading the great advice of Rob Waite, the answer is obviously NO. Sorry for the noise. Best, --Toni++
Re: OpenBSD 4.1 install issue??
Hi,
On Mon, 30.04.2007 at 21:04:37 -0400, Rob Waite <[EMAIL PROTECTED]> wrote:
> booting cd0a:4.1/i386/bsd.rd: blah blah
> entry point at blah blah
>
> avm_page_physload: unable to load physical memory segment. 5 segments
> allocated, ignoring blah blah
> increase VM_PHYSSEG_MAX
I experience the same problem. The machine in question runs fine with
OpenBSD 4.0, but does not even boot from CD, or with any of the 4.1
kernels I tried. The cued session below shows the dmesg for 4.0, and
what goes wrong with 4.1.
Script started on Mon May 21 11:21:09 2007
$ ttu
cu -l ttyS0
Connected.
>> OpenBSD/i386 BOOT 2.10
booting hd0a:/bsd: \
5515872|
+867984 [52+274160/
+255770-
]=0x6980a4
entry point at 0x200120
[ using 530356 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org
OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
RTC BIOS diagnostic error 4
cpu0: Intel(R) Xeon(R) CPU 5120 @ 1.86GHz ("GenuineIntel" 686-class) 1.87 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,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16
cpu0: unknown Core FSB_FREQ value 0 (0xc1c8149e)
cpu0: EST: unknown system bus clock
real mem = 2141421568 (2091232K)
avail mem = 1945268224 (1899676K)
using 4256 buffers containing 107175936 bytes (104664K) of memory
RTC BIOS diagnostic error 4
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 08/18/06, SMBIOS rev. 2.5 @
0x7fa42000 (56 entries)
bios0: MAXDATA PLATINUM 2200 IR M6
pcibios at bios0 function 0x1a not configured
bios0: ROM list: 0xc/0x9000 0xc9000/0x5200 0xce800/0x1000 0xcf800/0x1000
ipmi0 at mainbus0: version 2.0 interface KCS iobase 0xca2/2 spacing 1
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x25d8 rev 0xb1
ppb0 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x25f7 rev 0xb1
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci2 at ppb1 bus 2
ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01
pci4 at ppb3 bus 4
ppb4 at pci2 dev 2 function 0 vendor "Intel", unknown product 0x3518 rev 0x01
pci5 at ppb4 bus 5
em0 at pci5 dev 0 function 0 "Intel PRO/1000 PT (80003ES2)" rev 0x01: irq 5,
address 00:04:23:d6:10:e2
em1 at pci5 dev 0 function 1 "Intel PRO/1000 PT (80003ES2)" rev 0x01: irq 11,
address 00:04:23:d6:10:e3
ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01
pci6 at ppb5 bus 6
ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0xb1
pci7 at ppb6 bus 7
ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE" rev 0xb1
pci8 at ppb7 bus 8
ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0xb1
pci9 at ppb8 bus 9
ppb9 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0xb1
pci10 at ppb9 bus 10
ppb10 at pci10 dev 0 function 0 "Intel IOP333 PCIE-PCIX" rev 0x00
pci11 at ppb10 bus 11
mfi0 at pci11 dev 14 function 0 "Symbios Logic MegaRAID SAS 1064R" rev 0x00:
irq 5
mfi0: logical drives 1, version 5.0.1-0041, 128MB RAM
scsibus0 at mfi0: 1 targets
sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed
sd0: 139236MB, 139236 cyl, 64 head, 32 sec, 512 bytes/sec, 285155328 sec total
ppb11 at pci10 dev 0 function 2 "Intel IOP333 PCIE-PCIX" rev 0x00
pci12 at ppb11 bus 12
ppb12 at pci0 dev 7 function 0 "Intel 5000 PCIE" rev 0xb1
pci13 at ppb12 bus 13
vendor "Intel", unknown product 0x1a38 (class system subclass miscellaneous,
rev 0xb1) at pci0 dev 8 function 0 not configured
pchb1 at pci0 dev 16 function 0 "Intel 5000 Error Reporting" rev 0xb1
pchb2 at pci0 dev 16 function 1 "Intel 5000 Error Reporting" rev 0xb1
pchb3 at pci0 dev 16 function 2 "Intel 5000 Error Reporting" rev 0xb1
pchb4 at pci0 dev 17 function 0 "Intel 5000 Reserved" rev 0xb1
pchb5 at pci0 dev 19 function 0 "Intel 5000 Reserved" rev 0xb1
pchb6 at pci0 dev 21 function 0 "Intel 5000 FBD" rev 0xb1
pchb7 at pci0 dev 22 function 0 "Intel 5000 FBD" rev 0xb1
uhci0 at pci0 dev 29 function 0 "Intel 6321ESB USB" rev 0x09: 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
uhci1 at pci0 dev 29 function 1 "Intel 6321ESB USB" rev 0x09: irq 5
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 6321ESB USB" rev 0x09: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 "Intel 6321ESB USB" rev 0x09: irq 5
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel U
Re: OpenBSD 4.1 install issue??
Rob , raising VM_PHYSSEG_MAX to 16 did the trick. I'm running stable 4.1 now. Thanks a lot for the sound advice ! Regards, Marcos Laufer - Original Message - From: "Rob Waite" <[EMAIL PROTECTED]> To: Sent: Saturday, May 12, 2007 1:04 PM Subject: Re: OpenBSD 4.1 install issue?? Oh yeah... I also noticed that others were trying the snapshot. I do not think you should run it at all. I only used it to see if the change to vmparam.h was likely to be the culprit. If you are getting the "uvm_page_physload: ... increase VM_PHYSSEG_MAX" error (and you wont see it easily... it flies by after about 2/10ths of a second) it is definately the change to vmparam.h For a truly clean install (that is if you are not a pro and want to be certain things are up to stable plus this patch) get the -stable (or the cd release if you don't mind the errata patches missing) and make the change to vmparam.h and build a release. This way you get safe code... a safe build ... and you will have cds that can be used to install this on these machines without having to go through all of this again. The reason I only used my built bsd kernel and the cd41.iso was because I wanted to make sure etc.tar.gz was clean. I actually did the whole build on 4.0 so I didn't want to use it's version of etc.tar.gz. I also suppose if you took a look at the makefiles.. you could build the cd41.iso much more quickly instead of going through the whole release.. but as I said... if you don't have the time to look through and make sure you are doing something safe (or dont know if you are)... you might as well just do the whole release and be sure its clean.
Re: OpenBSD 4.1 install issue??
Oh yeah... I also noticed that others were trying the snapshot. I do not think you should run it at all. I only used it to see if the change to vmparam.h was likely to be the culprit. If you are getting the "uvm_page_physload: ... increase VM_PHYSSEG_MAX" error (and you wont see it easily... it flies by after about 2/10ths of a second) it is definately the change to vmparam.h For a truly clean install (that is if you are not a pro and want to be certain things are up to stable plus this patch) get the -stable (or the cd release if you don't mind the errata patches missing) and make the change to vmparam.h and build a release. This way you get safe code... a safe build ... and you will have cds that can be used to install this on these machines without having to go through all of this again. The reason I only used my built bsd kernel and the cd41.iso was because I wanted to make sure etc.tar.gz was clean. I actually did the whole build on 4.0 so I didn't want to use it's version of etc.tar.gz. I also suppose if you took a look at the makefiles.. you could build the cd41.iso much more quickly instead of going through the whole release.. but as I said... if you don't have the time to look through and make sure you are doing something safe (or dont know if you are)... you might as well just do the whole release and be sure its clean.
Re: OpenBSD 4.1 install issue??
Yeah... sorry you are also having the problem.. if you have an evening to start from scratch... I think you could fix it though. I am not sure about this moving back from current to stable. This is what I did (and it could have been more efficient) 1) Downloaded the source trees (src.tar.gz sys.tar.gz) 2) Updated to -stable from CVS 3) Changed the offending code FROM: #define VM_PHYSSEG_MAX5 TO: #define VM_PHYSSEG_MAX16 IN: /usr/src/sys/arch/i386/include/vmparam.h 3) Built a release (this requires that you build the kernel, the userland and then do the actual release) 4) I took the cd41.iso and burnt it to disk. I then burned the other release files to a second disk. 5) I started my install from the cd41.iso cd and it was fine. When it asked for my files... I went ahead and used the ftp for all but the kernel. I then used my cd to install the kernel (bsd) 6) Everything has been working fine I don't see why you wouldnt be able to go from current back to stable. Couldn't you delete your whole source tree... follow steps 1 and 2 above... then make a new release and reinstall. It sounds like you would want to do that because you wouldnt feel very certain of your production server in the state it is in now (at least it sounded that way) To do the build... please read: http://www.openbsd.org/faq/faq5.html#Bld From 5.3 through 5.4. I had never done it before and I stupidly skimmed the reading and it didn't work. So don't take shortcuts and read it unless you have done it before. If you run into problems read: http://www.openbsd.org/cgi-bin/man.cgi?query=release&sektion=8 It is the authoritative set of instructions for this. There is a chance that you don't have to change the code... but when I did this... the change was not applied to -stable For a history of this change see: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/i386/include/vmparam.h It is revision 1.37 and if you click the link that says "colored" you can see a nice pretty diff of the change. Well.. I hope this was of help.. if you are having trouble with making the release.. feel free to email me directly about this. [EMAIL PROTECTED] Good luck - Original Message - From: "Marcos Laufer" <[EMAIL PROTECTED]> To: "Ben Calvert" <[EMAIL PROTECTED]>; Sent: Friday, May 11, 2007 8:27 AM Subject: Re: OpenBSD 4.1 install issue?? Looks like i'm miximng kernel and userspace versions because i did get the -release cd and installed it, but it didn' recognize my hardware , it wouldn't boot: http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg So i found this thread wich says i should install the latest snapshot . What i didn't consider is that it was not possible to move to -stable from -current. I did tried to move to -stable (compiled kernel and booted) and it crashed like in those images up there, the same does when booting with -release cd , so i had to keep with -current kernel (and -current userland of course) I just wish OpenBSD 4.1 -release (too late for -release) or -stable could boot on my hardware, i can't fix that myself , i don't know how to backport the changes i need - Original Message - From: "Ben Calvert" <[EMAIL PROTECTED]> To: "Marcos Laufer" <[EMAIL PROTECTED]> Sent: Friday, May 11, 2007 12:33 AM Subject: Re: OpenBSD 4.1 install issue?? On May 10, 2007, at 7:25 PM, Marcos Laufer wrote: I upgraded to stable , rebooted with the new kernel, and i was stuck with this uvm_page_physload problem again. It looks like moving to stable from this snapshot is not possible . I had to go back to the snapshot kernel . 1. you can't upgrade down ( current > stable ) 2. ths is not linux - from the above it sounds like you were mixing different kernel and userspace versions.. you can't do that either ( as you seem to have found out ) Will it be possible to move to stable from this point? possible? maybe. supported? no. I really wouldn't like to have a production server running -current so then you need to get the -release cd, and upgrade to -stable from there. Has anyone sorted this out? Marcos
Re: OpenBSD 4.1 install issue??
Looks like i'm miximng kernel and userspace versions because i did get the -release cd and installed it, but it didn' recognize my hardware , it wouldn't boot: http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg So i found this thread wich says i should install the latest snapshot . What i didn't consider is that it was not possible to move to -stable from -current. I did tried to move to -stable (compiled kernel and booted) and it crashed like in those images up there, the same does when booting with -release cd , so i had to keep with -current kernel (and -current userland of course) I just wish OpenBSD 4.1 -release (too late for -release) or -stable could boot on my hardware, i can't fix that myself , i don't know how to backport the changes i need - Original Message - From: "Ben Calvert" <[EMAIL PROTECTED]> To: "Marcos Laufer" <[EMAIL PROTECTED]> Sent: Friday, May 11, 2007 12:33 AM Subject: Re: OpenBSD 4.1 install issue?? On May 10, 2007, at 7:25 PM, Marcos Laufer wrote: > I upgraded to stable , rebooted with the new kernel, and i > was stuck with this uvm_page_physload problem again. > It looks like moving to stable from this snapshot is not possible . > I had to go back to the snapshot kernel . 1. you can't upgrade down ( current > stable ) 2. ths is not linux - from the above it sounds like you were mixing different kernel and userspace versions.. you can't do that either ( as you seem to have found out ) > > Will it be possible to move to stable from this point? possible? maybe. supported? no. > I really > wouldn't like to have a production server running -current so then you need to get the -release cd, and upgrade to -stable from there. > > Has anyone sorted this out? > > Marcos
Re: OpenBSD 4.1 install issue??
On Thu, May 10, 2007 at 11:25:39PM -0300, Marcos Laufer wrote: > I upgraded to stable , rebooted with the new kernel, and i > was stuck with this uvm_page_physload problem again. > It looks like moving to stable from this snapshot is not possible . > I had to go back to the snapshot kernel . > > Will it be possible to move to stable from this point? I really > wouldn't like to have a production server running -current You can go to -stable when 4.2 is tagged, and not before. Of course, if you know what you are doing, you could try to backport the change you need to -stable... Joachim -- PotD: x11/xfce4/xfce4-clipman - clipboard history plugin for the xfce4 panel
Re: OpenBSD 4.1 install issue??
I upgraded to stable , rebooted with the new kernel, and i was stuck with this uvm_page_physload problem again. It looks like moving to stable from this snapshot is not possible . I had to go back to the snapshot kernel . Will it be possible to move to stable from this point? I really wouldn't like to have a production server running -current Has anyone sorted this out? Marcos - Original Message - From: "Marcos Laufer" <[EMAIL PROTECTED]> To: "Rob Waite" <[EMAIL PROTECTED]>; Sent: Wednesday, May 09, 2007 2:30 PM Subject: Re: OpenBSD 4.1 install issue?? I had the same problem installing OpenBSD 4.1 on an Intel D945GCcr motherboard and the snapshot worked just fine! But i noticed that it is not possible to install gd package due to lack of libfontconfig.3.0 on xbase41.tgz of the snapshot. But the libfontconfig.3.0 is on the xbase41.tgz of the release. So i installed the xbase41.tgz of the release over the snapshot installation, and i could install gd smoothly. Now i just have to move on to stable and i'm ready to go! Thanks ! Marcos Laufer - Original Message - From: "Rob Waite" <[EMAIL PROTECTED]> To: Sent: Wednesday, May 02, 2007 9:52 AM Subject: Re: OpenBSD 4.1 install issue?? Yep.. the snapshot worked... I did not get a chance to try 3.9... I spent all last night making a new release... I was pretty sure that I only needed cd41.iso and the kernel but I went ahead and did the whole thing anyway. So now it is up and running and everything seems fine. Thanks for your help! Rob - Original Message - From: "Tom Cosgrove" <[EMAIL PROTECTED]> To: "Rob Waite" <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2007 11:58 AM Subject: Re: OpenBSD 4.1 install issue?? > Rob > > Can you try a snapshot? VM_PHYSSEG_MAX was upped from 5 to 16 at > the end of March; this should help. (This change was too late for > 4.1 though.) > > I was also serious in asking you to try 3.9: I think you will find > that this does not work either. In other words, 4.0 is the only > recent release that will have worked for you - there were changes > in 4.0 which were reverted (undone) for 4.1 because they did not > work for everyone. However, they did include a higher value for > VM_PHYSSEG_MAX. > > Thanks > > Tom > >>>> Rob Waite 1-May-07 14:43 >>> >> >> Yeah I am sorry about the first hand written dmesg with the >> "blah blah" in it. Below are two links to images of my screen.. some >> intermediate messages were lost because they scrolled by too fast. >> >> To recap... it works on i386 4.0 (the clock_battery message shows >> up there too) it works on amd64 4.1 (clock_message also) and the >> screenshots for i386 4.1 are below. There is a message in the >> secondScreen image where fxp0 has a fault. If I disable the intel >> ethernet (it is onboard the motherboard) I get an error at about the >> same place about the USB having a fault. If I disable the USB... >> another item has a fault and so on (sorry.. I don't remember the >> item... if someone thinks that is an important clue I will try again >> and let you know). >> >> It seems like the initial avm_page_physload is a big part of this >> issue. It seems so strange how the other releases will work. >> >> Okay... so here are the links to the screenshots and the dmesg for >> amd64 was in an earlier post. Thanks again everyone. >> >> http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg >> >> http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg
Re: OpenBSD 4.1 install issue??
I had the same problem installing OpenBSD 4.1 on an Intel D945GCcr motherboard and the snapshot worked just fine! But i noticed that it is not possible to install gd package due to lack of libfontconfig.3.0 on xbase41.tgz of the snapshot. But the libfontconfig.3.0 is on the xbase41.tgz of the release. So i installed the xbase41.tgz of the release over the snapshot installation, and i could install gd smoothly. Now i just have to move on to stable and i'm ready to go! Thanks ! Marcos Laufer - Original Message - From: "Rob Waite" <[EMAIL PROTECTED]> To: Sent: Wednesday, May 02, 2007 9:52 AM Subject: Re: OpenBSD 4.1 install issue?? Yep.. the snapshot worked... I did not get a chance to try 3.9... I spent all last night making a new release... I was pretty sure that I only needed cd41.iso and the kernel but I went ahead and did the whole thing anyway. So now it is up and running and everything seems fine. Thanks for your help! Rob - Original Message - From: "Tom Cosgrove" <[EMAIL PROTECTED]> To: "Rob Waite" <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2007 11:58 AM Subject: Re: OpenBSD 4.1 install issue?? > Rob > > Can you try a snapshot? VM_PHYSSEG_MAX was upped from 5 to 16 at > the end of March; this should help. (This change was too late for > 4.1 though.) > > I was also serious in asking you to try 3.9: I think you will find > that this does not work either. In other words, 4.0 is the only > recent release that will have worked for you - there were changes > in 4.0 which were reverted (undone) for 4.1 because they did not > work for everyone. However, they did include a higher value for > VM_PHYSSEG_MAX. > > Thanks > > Tom > >>>> Rob Waite 1-May-07 14:43 >>> >> >> Yeah I am sorry about the first hand written dmesg with the >> "blah blah" in it. Below are two links to images of my screen.. some >> intermediate messages were lost because they scrolled by too fast. >> >> To recap... it works on i386 4.0 (the clock_battery message shows >> up there too) it works on amd64 4.1 (clock_message also) and the >> screenshots for i386 4.1 are below. There is a message in the >> secondScreen image where fxp0 has a fault. If I disable the intel >> ethernet (it is onboard the motherboard) I get an error at about the >> same place about the USB having a fault. If I disable the USB... >> another item has a fault and so on (sorry.. I don't remember the >> item... if someone thinks that is an important clue I will try again >> and let you know). >> >> It seems like the initial avm_page_physload is a big part of this >> issue. It seems so strange how the other releases will work. >> >> Okay... so here are the links to the screenshots and the dmesg for >> amd64 was in an earlier post. Thanks again everyone. >> >> http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg >> >> http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg
Re: OpenBSD 4.1 install issue??
Yep.. the snapshot worked... I did not get a chance to try 3.9... I spent all last night making a new release... I was pretty sure that I only needed cd41.iso and the kernel but I went ahead and did the whole thing anyway. So now it is up and running and everything seems fine. Thanks for your help! Rob - Original Message - From: "Tom Cosgrove" <[EMAIL PROTECTED]> To: "Rob Waite" <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2007 11:58 AM Subject: Re: OpenBSD 4.1 install issue?? Rob Can you try a snapshot? VM_PHYSSEG_MAX was upped from 5 to 16 at the end of March; this should help. (This change was too late for 4.1 though.) I was also serious in asking you to try 3.9: I think you will find that this does not work either. In other words, 4.0 is the only recent release that will have worked for you - there were changes in 4.0 which were reverted (undone) for 4.1 because they did not work for everyone. However, they did include a higher value for VM_PHYSSEG_MAX. Thanks Tom Rob Waite 1-May-07 14:43 >>> Yeah I am sorry about the first hand written dmesg with the "blah blah" in it. Below are two links to images of my screen.. some intermediate messages were lost because they scrolled by too fast. To recap... it works on i386 4.0 (the clock_battery message shows up there too) it works on amd64 4.1 (clock_message also) and the screenshots for i386 4.1 are below. There is a message in the secondScreen image where fxp0 has a fault. If I disable the intel ethernet (it is onboard the motherboard) I get an error at about the same place about the USB having a fault. If I disable the USB... another item has a fault and so on (sorry.. I don't remember the item... if someone thinks that is an important clue I will try again and let you know). It seems like the initial avm_page_physload is a big part of this issue. It seems so strange how the other releases will work. Okay... so here are the links to the screenshots and the dmesg for amd64 was in an earlier post. Thanks again everyone. http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg
Re: OpenBSD 4.1 install issue??
Yeah I am sorry about the first hand written dmesg with the "blah blah" in it. Below are two links to images of my screen.. some intermediate messages were lost because they scrolled by too fast. To recap... it works on i386 4.0 (the clock_battery message shows up there too) it works on amd64 4.1 (clock_message also) and the screenshots for i386 4.1 are below. There is a message in the secondScreen image where fxp0 has a fault. If I disable the intel ethernet (it is onboard the motherboard) I get an error at about the same place about the USB having a fault. If I disable the USB... another item has a fault and so on (sorry.. I don't remember the item... if someone thinks that is an important clue I will try again and let you know). It seems like the initial avm_page_physload is a big part of this issue. It seems so strange how the other releases will work. Okay... so here are the links to the screenshots and the dmesg for amd64 was in an earlier post. Thanks again everyone. http://i175.photobucket.com/albums/w132/winstonwaite/firstScreen.jpg http://i175.photobucket.com/albums/w132/winstonwaite/secondScreen.jpg - Original Message - From: "Tom Cosgrove" <[EMAIL PROTECTED]> To: "Rob Waite" <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2007 4:11 AM Subject: Re: OpenBSD 4.1 install issue?? Rob Waite 1-May-07 06:22 >>> One thing I neglected to include in my hand written dmesg was that amd64 seems to use CDBOOT 1.08 and i386 uses CDBOOT 1.06, unless my video capture made the 6 look like an 8. Maybe this is by design. Anyway.. I will stop flooding this board with my messages. Sorry ; ) Rob If you can't capture the 4.1 stuff except with a video camera, could you at least post links to the images :) That way we don't have to guess the "blah blah" and "basically" stuff. Could you also try 3.9 i386 and see if it has the same problems as 4.1, or if it works like 4.0 (this is a serious request). Thanks Tom
Re: OpenBSD 4.1 install issue??
One thing I neglected to include in my hand written dmesg was that amd64 seems to use CDBOOT 1.08 and i386 uses CDBOOT 1.06, unless my video capture made the 6 look like an 8. Maybe this is by design. Anyway.. I will stop flooding this board with my messages. Sorry ; )
Re: OpenBSD 4.1 install issue??
Another interesting thing... I installed the amd64 version of 4.1 and it
works without a hitch. I also noticed a line that says:
RTC BIOS diagnostic error 80
It does seem to boot okay and everything seemed stable. I have installed win
xp on this machine for a week and no problems at all. I went out and bought
a new cmos battery but the message still shows.
The info on the screen for i386 and the dmesg for amd64 are below. The info
for i386 is off of a video frame so I may be off by a letter or two but I am
pretty sure it is accurate. Thanks ahead for any time anyone puts to looking
at this.
Info on screen from booting on i386 cd:
booting cd0a:/4.1/i386/bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288
entry point at 0x200120
avm_page_physload: unable to load physical memory segment 5 segments
allocated, ignoring 0x3f5dc -> 0x3f67f increase VM_PHYSSEG_MAX
avm_page_physload: unable to load physical memory segment 5 segments
allocated, ignoring 0x3f6e9 -> 0x3f6ed increase VM_PHYSSEG_MAX
(copyright info)
OpenBSD 4.1 (RAMDISK_CD) #240: (date)
[EMAIL PROTECTED]:/usr /src/sys/arch/i386/compile/RAMDISK_CD
RTC BIOS diagnostic error 80
cpu0: Intel(R) Core(TM)2 CPU 6600 @ 2.40Ghz ("GenuineIntel" 686-class)
Then it jumps to the next screen and maybe stuff scrolls by but I couldnt
catch it on my camera... as I said.. I didnt know how to save the output or
scroll back up when it told me to halt
bios0: ROM list: 0x/0xad00!
acpi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GP" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ppb0 at pci0 dev 20 function 0 "Intel 82801GB PCIE" rev 0x01
pci1 at ppb0 bus 1
ppb1 at pci0 dev 20 function 0 "Intel 82801GB PCIE" rev 0x01
pci2 at ppb1 bus 2
ppb2 at pci0 dev 20 function 0 "Intel 82801GB PCIE" rev 0x01
pci3 at ppb2 bus 3
ppb3 at pci0 dev 30 function 0 "Intel 82801GB AGP" rev 0xe1
pci4 at ppb3 bus 4
fxp0 at pci4 dev 0 function 0 "Intel PRO/100 VM" rev
0x01uvm_fault(0xd0691160, 0x3f000, 0, 1) -> e
fatal page fault (6) in supervisor mode
trap type 6 code 0 eip d02b0a10 cs 0 eflags 10202 cr2 3f707 cpi 0
panic: trap type 6, code=0, pc=d02b0a10
The operating system has halted.
Please press any key to reboot.
Here is my dmesg from AMD64:
OpenBSD 4.1 (RAMDISK_CD) #1054: Sat Mar 10 19:32:06 MST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 1062072320 (1037180K)
avail mem = 899346432 (878268K)
using 22937 buffers containing 106414080 bytes (103920K) of memory
RTC BIOS diagnostic error 80
mainbus0 (root)
acpi at mainbus0 not configured
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz, 2395.57 MHz
cpu0:
FPU,VME,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,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu0: 4MB 64b/line 16-way L2 cache
pci0 at mainbus0 bus 0: configuration mode 1
pchb0 at pci0 dev 0 function 0 "Intel 82945GP" rev 0x02
vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01
pci3 at ppb2 bus 3
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: irq 9
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
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: irq 11
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: irq 9
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
ppb3 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0xe1
pci4 at ppb3 bus 4
fxp0 at pci4 dev 8 function 0 "Intel PRO/100 VM" rev 0x01, i82562: irq 9,
address 00:16:76:ce:b8:4a
ukphy0 at fxp0 phy 1: Generic IEEE 802.3u media interface, rev. 0: OUI
0x00aa00, model 0x0031
"Intel 82801GB LPC" rev 0x01 at pci0 dev 31 function 0 not configured
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x01: DMA, channel
0 configured to compatibil
Re: OpenBSD 4.1 install issue??
On 4/30/07, Rob Waite <[EMAIL PROTECTED]> wrote: This is a new computer so I was worried that the hardware was not supported. I popped in my OBSD 4.0 boot disk and it started up no problem.. so my question is this: Do the FTP sites put out some sort of incomplete boot iso before the official release? Or are these iso's I see the actual ones and my current hardware really doesnt like 4.1 vs. 4.0 if it's there, it's the only 4.1 there is. can you post a complete dmesg for 4.0 and as many exact details for 4.1 as possible?
OpenBSD 4.1 install issue??
Hello.. I know that OpenBSD is released officially on May 1st. I noticed however that it is available on the FTP's (all of this just happened in the last 30 minutes). I made the boot cd and then tried to install but it seems to be very unhappy. After it mentions the ramdrive... some text flashes for like 2/10ths of a second... then I get a screen that says the main bus was not loaded and then it basically says to reboot. This is a new computer so I was worried that the hardware was not supported. I popped in my OBSD 4.0 boot disk and it started up no problem.. so my question is this: Do the FTP sites put out some sort of incomplete boot iso before the official release? Or are these iso's I see the actual ones and my current hardware really doesnt like 4.1 vs. 4.0 Thanks!
OpenBSD 4.1 install issue??
I couldnt figure out how to get my dmesg when it wouldnt even boot so I took a picture... it says the following (basically): booting cd0a:4.1/i386/bsd.rd: blah blah entry point at blah blah avm_page_physload: unable to load physical memory segment. 5 segments allocated, ignoring blah blah increase VM_PHYSSEG_MAX avm_page_physload: unable to load physical memory segment. 5 segments allocated, ignoring blah blah increase VM_PHYSSEG_MAX Copyright about the regents OpenBSD 4.1 (RAMDISK.CB) #248 blah blah RTC BIOS diagnostic error 80 and then things dont load.. I get more messages and I could transcribe them if someone needs them to help. I would accept that my hardware has a problem except I just ran memtest86 for two days and prime95 for two days. I also can boot the 4.0 disk no problem everytime. Does anyone know what these messages mean for me? I saw some people mention them in past forum posts but it didn't really seem to mention a fix or goal to look for. Thanks and sorry if the dmesg is not clean.. it wouldnt boot at all so I had to take a digital picture to see what it said.
