Towards the end of last week I asked if anyone understood why, with
the win4lin kernel, I lost access to my CD-writer since it was (as I
understood) just a patch of the Mandrake kernel).  The response was
that this kernel was compiled without SCSI support.  I found that odd,
expressed the thought that it seemed like a silly thing to do given
that it was a kernel being distributed by Traverse in support of their
product on a large variety of equipment.  Nevertheless, I could think
of no better explanation.

I was wrong...there is a very simple solution to this problem that I
came to after a LONG circuitous route in trying to get it to work by
kernel rebuilds.

First, I found that SCSI support is the default, suggesting that
someone at Traverse would have to actively disable this function. 
That seemed REAL unlikely.  Nevertheless, I did several kernel
rebuilds with different options selected in an attempt to give me
access to my drive.  NOTHING worked but my compiler is still warm from
all the work it's done in the past 24h :-)

In a fit of true thinking on my part (at 1AM) I thought "Maybe this
isn't it" and sat staring at the /etc directory, wondering what else
it could be.  Then it dawned on me...the problem is with the lilo.conf
setup.  The Traverse setup script modifies lilo.conf and sets up the
bootable win4lin kernel.  Of course it does this in simple fashion and
therein lies the rub, though it's a simple rub.  

This is what Traverse adds:

image = /boot/win4lin
        label = win4lin
        root = /dev/hda6
        
This is the standard lilo setup and is exactly as it should be.  BUT,
since I'm doing the 'fake the system into thinking it's talking to a
SCSI device when it talks to an IDE CD-writer' I need to add

        append = " hdc=ide-scsi"

With that simple addition (no kernel builds necessary) all is well
with the Win4lin kernel.  Sure wish I could say that I learned a bunch
about kernel building during this saga but I didn't.  All I learned
was that I can be pretty dumb at times and that sometimes answers can
be simple things.

Cheers --- Larry
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
http://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to