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