Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!not-for-mail From: David Henshaw <dhenshaw@silas.cc.monash.edu.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Problem with 2.2.1 Install !!! Date: Sat, 14 Jun 1997 19:34:21 +1000 Organization: Monash University Lines: 83 Message-ID: <33A2659D.41C67EA6@silas.cc.monash.edu.au> NNTP-Posting-Host: ascendp-int-59.cc.monash.edu.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-NNTP-Posting-User: root X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.1-RELEASE i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42931 Gidday all, I recently received my new version of FreeBSD (2.2.1). I was running 2.1.5 without any problems whatsoever. Machine is a Pentium 150 with 16 Meg, and a 500M FreeBSD partition. Also installed is a SoundBlaster 16, and a 3Com 3c503 based board. I had my kernel configured properly for all devices and booting and working was no problem. XFree running as well. Firstly I decided to backup /etc /root and other directories I had managed to finally get settled. I then booted and ran the install.bat file on the first CD. Chose the UPGRADE option, read the warnings and decided to proceed. Well....that was problem one!!!... So I decided to wipe the existing installation and install 2.2.1 from scratch. All went smoothly, and I dutifully restarted the machine. And BANG.... Straight after the ed0 probe (which should probe the 3Com board) I received the following rather large (and awe inspiring/scary) message. Fatal trap 12 : page fault while in kernel mode fault virtual address = 0refc00000 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01cfa03 stack pointer = 0x10:0xefbffefc frame pointer = 0x10:0xefbffefc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, IOPL=0 current process = 0 () interrupt mask = net tty bio panic page fault Arrhh.....my initial reaction was that I had a faulty SIMM. But after much thought I figured that I'll try disabling the ed0 probe. So I rebooted and entered the kernel config mode and disabled all devices that definitely were not required (and YES...I mean only those not required!!). After doing so I exited the kernel config mode and found another problem. THE KERNEL FAILED TO START and the system hung. This would seem to be a problem with the kernel. After much frustration I decided to wipe the partition that the installation had been done on. I then proceeded to install 2.2.1 with the install.bat procedure. Disabled ed0 and all other unused/missing devices during the installation procedure and commited the changes. Ahh....success.... Restored all the previous versions of files that were required, and now have things up and running... It would seem that the structure of /etc and the files used during boot have changed. Still figuring these out. I'm going to put my 2 cents worth in form my experiences with this upgrade. Firstly, the structure of /etc and the files used during boot needs to be explained. That way people can safely know where to do the configuration of their systems and "where something that was somewhere else belongs". Secondly, during the next few releases, the upgrade option really needs to be polished. In my opinion, several things need doing. A) Some means of determining what packages/ports and distributions are installed on a system and updating these needs to be done. This should allow users to safely upgrade without needing to worry about reinstalling the latest (well almost :) ) releases of software. B) Automatic updating of configuration files based on the previous system. C) In general, a simpler method of upgrading to the latest release of what is definitely one of the best OS's available. Excuse my long winded spiel, and apart from my upgrade experience, I am nothing but overjoyed by, and proud to call myself a user of, FreeBSD! -- David Henshaw dhenshaw@silas.cc.monash.edu.au