New Kernel - Newly compiled MOL - old problems

Quentin Mason mol-general@lists.maconlinux.org
Wed, 2 Oct 2002 16:31:19 -0400 (EDT)


Hi,

> HFS  images/moldisk.i MOL                <read-only>     0 MB
> ------> /dev/sdb3 is linux-mounted with write privileges.
> HFS  /dev/sdb3        ATM HD-1 SYSTEM    <read-only>  2047 MB BOOT
> ------> /dev/sdb4 is linux-mounted with write privileges.
> HFS  /dev/sdb4        ATM HD-2 DATA-A    <read-only>  2047 MB
> HFS  /dev/sdb5        ATM HD-4 SOFT      <read-only>  2047 MB
> HFS  /dev/sdb6        ATM HD-3 DATA-B    <read-only>  2047 MB
> ------> /dev/sdb7 is linux-mounted with write privileges.
> HFS+ /dev/sdb7        ATM HD-5 WIN95     <read-only>   490 MB
> ------> /dev/sdd4 is linux-mounted with write privileges.
> HFS  /dev/sdd4        LINUX XFER         <read-only>    95 MB
> ----> (disk_open) Opening /dev/fd0: No such device or address
> ----> (disk_open) Opening /dev/cdrom: No medium found
> 
> Loading 'System Folder:Mac OS ROM' from /dev/sdb3

> 1.  Even when I define hfs volumes as -rw, the Mac window shows a padlock
> and I get "Volume Protected" messages when I try to save things.

This may be simple;  you cannot have write access to a drive in both Linux
and MacOS.  Umount your HFS drives in linux before using them in MOL.  
MOL is clever and stops you from trashing all your data which is what
would result from simultaneous Linux+MOL writes to the disk.

MacOS often does not appreciate being booted from read-only partitions -- 
it likes to record the date + time of boot, mess with preferences etc.

> 2.  Under MacOs, a parade of small icons for all of my extensions being
> loaded parade across the MacOs Banner page.  When booting under mol a
> few large icons parade and not all of my stuff gets loaded.     A
> strange symptom:  When I was experimenting with different mouse
> settings, some of them resulted in the small icon parade and some the
> large.  Unfortunately, although I have an adb mouse, only "mouse ps2"
> works resulting in large icons and not all my stuff loading.

> MODE:  640* 480, depth 8,15   { 0.0 } Hz
> MODE:  800* 600, depth 8,15,32   { 72.1, 74.9 } Hz
> MODE: 1024* 768, depth 8,15   { 0.0 } Hz
> MODE: 1152* 864, depth 8,15   { 0.0 } Hz
> MODE: 1280*1024, depth 8,15   { 0.0 } Hz
> MODE: 1600*1200, depth 8,15   { 0.0 } Hz

> Starting in video mode 800*600, depth 32, 72.1 Hz  [offs:0, rb:3200]

It is fairly clear from the log that it is trying to run at 800x600 -- 
this is most likely why the icons are so much larger.  I would recommend 
choosing a better option with molvconfig.

Not all extensions CAN run in MOL -- eg the powerlogix extension for my
upgraded processor crashes MOL, + anything to do with modems, serial stuff
or accelerated graphics is unlikely to load as MOL does not "have"  this
hardware.  If you are lucky they just come up with a red X through them...
This is what "Extension Manager" and "Location Manager" are for.

You may have an adb mouse but that does not mean that linux sees it as 
adb.  EG Mandrake uses "USB mice" on ALL machines (USB input layer).  Have 
a look at what /dev/mouse and /dev/input/mouse? point to... and what line 
is in your /etc/X11/XF86Config-4 file for the mouse location and even what 
configuration gpm is using (ps auxwww | grep gpm).  PS/2 is a protocol 
that many mice use.

I think that both of these problems are clearly indicated in the log, but 
perhaps you have found some more complicated and buggy behaviour.

Q.