Installation

[Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem \ <fstype> eg. ufs:/dev/da0s1a ? List valid disk boot devices <empty line> Abort manual input mountroot>]

hi,friends:

My computer for m0n0 is:128m sdram,128m kingstone cf card,Intel82559*2,motherboard is PCChips M787CL,which has VIA Samuel2 1Giga Pro in it.

I had writen 1.22.img in cf card,but when I power the machine for a while,it display below:

Manual root filesystem specification:
      <fstype>:<device>  Mount <device> using filesystem \
<fstype>
                           eg. ufs:/dev/da0s1a
      ?                  List valid disk boot devices
      <empty line>       Abort manual input

    mountroot>

It seems that there's something wrong that FreeBSD can not run.so the m0n0 can not be initial configuration !

Need helps!Thanks!

Yesterday I  had tryed m0n01.3b2 for the same hardware,but still could not run successfully!

Systems  showed below:

ad0:FAILURE-SETFEATURES SET TRANSFER MODE status=51<READY,DSC,ERROR>error=4<ABORTED>

I really don't know why!

hi,friends:

My computer for m0n0 is:128m sdram,128m kingstone cf card,Intel82559*2,motherboard is PCChips M787CL,which has VIA Samuel2 1Giga Pro in it.

I had writen 1.22.img in cf card,but when I power the machine for a while,it display below:

Manual root filesystem specification:
      <fstype>:<device>  Mount <device> using filesystem \
<fstype>
                           eg. ufs:/dev/da0s1a
      ?                  List valid disk boot devices
      <empty line>       Abort manual input

    mountroot>

It seems that there's something wrong that FreeBSD can not run.so the m0n0 can not be initial configuration !

Need helps!Thanks!

i got the same error after burning cd the CD version and booting from it.
please help!

Not sure what that's about, but for starters I would suggest making sure that you are using the right image, which would be the generic pc image for the cf card and the cd image for the cd boot. While you're at it you should probably get the latest stable version (1.231 atm) and check the md5sum on your downloaded image before burning.

Let us know if you still have problems after trying the above.

db

For your information. I used the CD image and tried the versions 1.231, 1.23, 1.22, 1.21, 1.2 and 1.11. All give the same error.

I am using version 1.0 for some years now, so you cans see i am not really a new user and only this version seems to work.

For your information i am using and old machine. It is a HP deskpro Pentium 166Mhz with 3 3com 3c900b nics. It has 64Mb of memory.

When i boot from another machine, a IBM Pentium III, using the newer versions i do not get the error. It seems the problem is hardware related.

For your information. I used the CD image and tried the versions 1.231, 1.23, 1.22, 1.21, 1.2 and 1.11. All give the same error.

I am using version 1.0 for some years now, so you cans see i am not really a new user and only this version seems to work.

For your information i am using and old machine. It is a HP deskpro Pentium 166Mhz with 3 3com 3c900b nics. It has 64Mb of memory.

When i boot from another machine, a IBM Pentium III, using the newer versions i do not get the error. It seems the problem is hardware related.

The same to you!When i boot from another machine, a 845PE mainboard, using the newer versions i do not get the error.

Does m0n0 do nou support VIA CPU?But VIA C3 1Giga is base on x86.

I have used VIA C3 CPU's in several different hardware platforms in the past with no issues. You do need to set the access mode on the CF to CHS on some of those platforms.

As for the one system that works with 1.0 and nothing newer, newer versions are based on newer FreeBSD releases, it's possible there are regressions in drivers or elsewhere that can cause problems. Given that the FreeBSD release used in 1.2 is end of life and no longer supported, those are issues that won't be resolved. You may want to try the 1.3 beta.

I have used VIA C3 CPU's in several different hardware platforms in the past with no issues. You do need to set the access mode on the CF to CHS on some of those platforms.

As for the one system that works with 1.0 and nothing newer, newer versions are based on newer FreeBSD releases, it's possible there are regressions in drivers or elsewhere that can cause problems. Given that the FreeBSD release used in 1.2 is end of life and no longer supported, those are issues that won't be resolved. You may want to try the 1.3 beta.

No matter what access mode on the CF I setted,there's still the same problem.Even the CHS mode.

And the newest version I can download is 1.231,which is still based on freebsd 4.x.And how can I get the 1.3 beta?

Thanks a lot!

http://m0n0.ch/wall/beta-1.3.php

http://m0n0.ch/wall/beta-1.3.php

Thank you! I will try as soon as possible.

[ad0:FAILURE-SETFEATURES SET TRANSFER MODE status=51<READY,DSC,ERROR>error=4<ABORTED>]

hi,friends!

I had tested m0n01.3b2 for the same hardware,but still could not run successfully!

Systems  showed below:

ad0:FAILURE-SETFEATURES SET TRANSFER MODE status=51<READY,DSC,ERROR>error=4<ABORTED>

It seems that I have to give up m0n0? I don't want! So anyone who can help me!