From what I can tell, Asus has come out with three different generations of the EeePC -- the 701, 900, & 1000 series. The
misc@ archives indicates some traffic from about a year ago of a number of people successfully installing onto the 1000H:
http://marc.info/?l=openbsd-misc&w=2...eepc+1000h&q=b
Only you will be able to answer whether you have the same model.
Quote:
Originally Posted by sutures
Installation seems to go well, until I halt the system and reboot. System sits with a scrolling screen of death flashing by too fast to read. Something about Inodes and time there is a "fix YES" at the end of some of the lines.
|
From your description
(& from searching the archives where you were attempting to install FreeBSD...), it sounds like you are trying to set up a dual-boot system with the existing Xandros installation trying to preserve it if you are unsuccessful in installing one of the *BSD's.
If this is a correct assumption, it is unclear from your message how and/or if you resized the MBR partition in which Xandros resides such that space would be freed for another operating system, so let me review the basics:
- The Intel architecture first executes instructions defined in the BIOS to initialize all known hardware components. At its end, the BIOS checks to see if the MBR signature value of 0xAA55 is defined at the end of the first 512 bytes of the hard drive's first sector. If this value is found, it assumed that the drive is properly initialized, so execution is then handed off to the first of the sector also known as the Master Boot Record. Normally, the instructions poke about the table found at the end of the MBR to ensure that only one partition (of four possible...) is defined as active. If this is true, then continues the process attempting to boot whatever operating system exists in what is defined as active.
- When OpenBSD was installed, if you did not set its fdisk(8) (MBR) partition as active, what you may be describing is Xandros attempting to boot again.
- If you did not resize the amount of space Xandros occupies (because by default Asus will have configured Xandros to take up all hard drive space available...), the inode mess described may be accounted for by the fact that OpenBSD was installed on top of part of Xandros.
- If the Xandros installation was using any of the other three MBR partitions for what you call "system recovery" could have been seen in the fdisk(8) output at the beginning of installing OpenBSD.
Whether your Xandros installation can be recovered now is unclear from the information presented.
It is also unknown from your message as to what version of OpenBSD was being installed.
From your earlier messages, it appears that you are new to the *BSD's & perhaps to their installations which requires knowledge of the MBR & partitioning up front. Attempting to configure a dual-boot as a first exercise is also a bit ambitious.
If you have been using some type of system recovery disk provided by Asus, I suspect that it simply reinstalls Xandros to take up whatever space is available on the SSD. If you want to continue delving into a dual-boot configuration, you will need to determine whether this can be resized. Undoubtedly, this will require Linux tools. GParted is a common choice.
If I have characterized your situation correctly, & you have been able to restore Xandros through some CD, my suggestion is to install OpenBSD by itself. Forget about dual-booting for now. Gain the experience of a simple installation before tackling something more complicated.