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]>; <misc@openbsd.org> 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: <misc@openbsd.org> 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
