Subject: Re: cannot start mol
From: Bhagwati P Gupta (bpgupta@its.caltech.edu)
Date: Tue May 16 2000 - 04:44:26 MDT
Francois Felix Ingrand wrote:
>
> I would appreciate a fb.modes file and a molrc file for a config running on
> a PB FW.
You can generate fb.modes file by doing -
fbset > /etc/fb.modes
Afterwords, edit this file -
"name" will be whatever your screen resolution is, such as "1024x768-100"
I have attached my molrc file ( I donot use console video to run mol for various
reasons....mainly it used to create problem with my X). I have been successfully
running mol in 800x600 window. You might want to modify the file for your needs,
especially ram (mine is set at 96MB). Also, turn off virtual memory in Mac.
Good luck.
Bhagwati
#-*-makefile-*-################################################
#
# Mac-on-Linux configuration file (molrc)
#
# MOL looks for this resource file in the following places
#
# $MOLRC (if started as root)
# /etc/molrc-hostname
# /etc/molrc
#
# All paths are relative to the 'lib' folder, normally
# /usr/lib/mol/ or /usr/local/lib/mol/
#
###############################################################
####################################
# ROM support
####################################
# If newworld_boot is set to yes, then MOL boots from a file-ROM
# (also called "newworld" ROM). The file-ROM image is simply a copy of the
# file "MacOS ROM" and can be copied from the System Folder (MacOS 8.6 or later).
# The ROM file might be missing on non-G3 machines if MacOS was installed
# with the "minimal installation" option checked (you can use free application
# 'tome viewer' to extract the file from the MacOS installer).
#
# IMPORTANT: Currently it is necessary to strip the first 0x4000 bytes
# from the newworld image. This is done with the command
# 'strip_nwrom org_romimage destimage'.
#
# Newworld booting currently does not work on 601-based machines (but
# the built-in ROM should work for these machines)
#
newworld_boot: yes
newworld_rom: rom/rom.nw # path to the stripped ROM-image
# To boot from a Boot-ROM (not a newworld_boot), set newworld_boot
# above to 'no'. The following *only* applies to Boot-ROMs.
#
# You should in general use a ROM-image and an oftree description
# file from the same machine, or from a closely related machine.
# If no ofree image is available (or if it doesn't work),
# try all the files in the oftrees directory /usr/lib/mol/oftrees.
#
# If the lines below are commented, then the ROM/oftree of the
# machine running the software will be used (see doc/mol/Status
# for more information)
#
# Also, remember to set 'processor' below to 4.
#
# Note: Do NOT use the "strip_nwrom" command on non-newworld images!
#
rom_image: rom/rom.8500
oftree: oftrees/oftree.8500
####################################
# Emulation parameters
####################################
#
# 1=601, 2=602, 3=603, 4=604, 8=750 (G3)
#
# NOTE [Boot-ROMs only]: 603 machines should specify 8 (or 4). Also
# some boot-ROMs might not run in G3 mode (if so, run in 604 mode instead).
# You should **ALMOST ALWAYS** specify 8 for 'processor'. If this is
# not done, the DOZE function will not work (a System 8.6 feature, causing
# MOL to sleep when MacOS is inactive).
processor: 8 # Should almost *ALWAYS* be 8 <------------
ram_size: 96 # you might want to increase this
####################################
# HFS volumes
####################################
#
# blkdev: device flags
#
# Device can for instance be /dev/hda, /dev/hda6 or /dev/sda4.
# The following flags are supported:
#
# -rw/-ro read-write / read-only [default]
# -force use this flag to mount non-HFS partitions
# -cd CD (in principal the same as -ro)
blkdev: /dev/hda9 -rw
#blkdev: /dev/hdc1 -rw
#blkdev: /dev/sda -ro
#blkdev: /dev/sdb -ro
#blkdev: /dev/cdrom -cd
# Note 1: You probably want to change the entries above to something
# like 'blkdev /dev/hda6 -rw'. Use pdisk/disklabel to find out
# what partition numbers your HFS volumes have. If you do not
# change this, then the volume might end up locked (even if
# it is not mounted by linux).
#
# Note 2: Which volume MacOS tries to boot from is dependent
# upon the order of the blkdev lines above.
#
# ** IMPORTANT **
# Please make sure that important data are backed up before
# enabling read-write permissions. Disk corruption in conjunction with
# MOL has been reported by in total two users.
####################################
# Mouse
####################################
#
# One of the following mouse settings should probably be used:
#
# device protocol
# -------------------------
# /dev/usbmouse, usb
# /dev/adbmouse, adb
# - console
mouse_device: /dev/adbmouse
mouse_protocol: adb # usb (ps2), adb, console
mouse_dpi: 100 # higher == slower mouse
use_x_cursor: yes # use X cursor as mouse cursor
####################################
# Ethernet
####################################
disable_osi_enet: no
enet_interface: eth0
#######################################
# Video configuration
#######################################
# Startup resolution and depth (used as a hint only)
resolution: 800/600/116.3 # width/height[/Hz]
depth: 32 #
# The fb.modes file contains a description of the full-screen
# video modes the monitor supports. Do 'man fbset' and
# 'man fb.modes' for more info. A sample fb.modes file is
# included in the /usr/doc/mol/extra/ directory.
#
# The /etc/fb.modes file might need some configuration.
# At least, incompatible modes should be removed
# (or MOL might try to use an incompatible video mode)
#
vmode_database: /etc/fb.modes
# X-display to be used ($DISPLAY is used if commented)
#xdisplay: remote.host.address:0.0
start_on_console: no # switch to console initially
autoswitch_console: no # allow automatic switch to console
enable_console_video: no # 'no' to disable full-screen (console) video
enable_xvideo: yes #
use_backing_store: no # Set to 'yes' only if the X-server is remote.
#vt: 8 # VT-number to use for full-screen video
####################################
# Keyboard
####################################
#
# Almost all Apple keyboards have an unique ID, and it affects how MacOS
# deals with key map tables and such. Ideally, we'd want to get this info
# from /dev/adb, but for now please specify.
#
# Hint: *Usually* the ID is printed during Linux/PPC's bootup.
# .....
# adb devices: [2]: 2 22 [3]: 3 1
# ^ ^
# | +- The second number ("22" here) is the keyboard ID.
# This "2" indicates that it's an ADB keyboard.
#
# Sample IDs:
# ID #
# ----
# 1 Apple Standard Keyboard
# 2 Apple Extended Keyboard
# 22 JIS Apple Keyboard II
# 200 JIS USB Keyboard
#
keyboard_id: 12
####################################
# Console video gamma
####################################
#
# Gamma correction for the display. "gamma" takes one floating number
# between 0.1 and 10.0 or three floating numbers specifying each R, G, and B
# value separately. A larger value gives a brighter display. No correction
# is made when the value is 1.0.
# Please note that the xvideo mode is not affected by this setting.
gamma: 1.0 # one value for all RGB
#gamma: 1.0 1.0 1.0 # R G B separately
####################################
# Misc
####################################
logfile: /tmp/mol-logfile # only used in debugger mode
This archive was generated by hypermail 2a24 : Tue May 16 2000 - 11:47:36 MDT