Firewire help, please...

[Derick Centeno]

Hi Dylan:
Don't worry ...arrogance is something all humans have.  This is  
probably why we are all learning to deal with one another, other  
species and our technological and other creations!  Anyway before I go  
way off-topic I recommend that you review this old link regarding  
creating custom kernels:

http://www.yellowdoglinux.com/support/solutions/ydl_general/ 
kernels.shtml

What is useful there are the details as regards to what steps come at  
what point.  The procedures discussed probably will remain forever as  
long as Linux itself exists.  You may already know it very well, still  
a lot of mistakes due to impatience can be avoided just by sticking to  
established practices and procedures.  Given what you already have gone  
through and the difficulties you've experienced you may want to  
consider using the make menuconfig format and become versed with  
accessing the various help and explanations embedded in various screens  
throughout the module selection process which provide explanations to  
nearly every possible selection allowing you to decide (then and there)  
whether you actually need that module.

It has been my experience that as the kernels become more advanced, the  
explanations actually become clearer and more concise.  This may be my  
own interpretation as I have taken the time to exhaust nearly every  
variant explanation file or discussion possible for nearly every option  
in building a new kernel.  You may discover, if you are patient enough,  
that some modules are deprecated and unnecessary where other new ones  
are still experimental and untried.  As it has become clear you could  
be running YDL or intend to, run it from a Powerbook, the modules you  
choose will affect how the kernel behaves.

However, the plain vanilla kernel provided and built by others (such as  
the stock YDL 4.0 kernel) may be the way for you to go as already it is  
successful on many machines and the modern kernels are very much more  
astute in loading the appropriate modules for the machines they find  
themselves to be running upon.  This could save you from the angst of  
the decisions you are considering until you make the time to comprehend  
more of which modules do what, why and how.

IP tunneling has been or is used as a particular form of file transfer  
within or while using SSH.  References exist discussing this and other  
things of passing interest or headaches (depending on one's view) in  
such works sold at such places as www.fatbrain.com ...Yes, you too can  
educate yourself to the level of heightened chronic cyberconcious  
madness!  So...take your time to swallow, breath and do yoga  
interspersed with the other techie stuff you may need to reference and  
utilize.  No human should ever sound like R2D2 ...so when enough is  
enough remember to take a break and come back later.  Hey fella... it's  
Spring.  Ya know... SPRING!  Remember to go to a local beach!

The work, these and related projects will all still be around.   
However, Life is moving on and living is far way MORE important.

However you arrange your breaks or time off this stuff... you may  
discover a sharper perspective and/or really unique insight.  Doing the  
reference reading and testing, and drawing correct lessons or  
observations from it can only happen when one is clear.  It has been  
said that Newton was in an Apple Orchard when musing upon gravity.   
Einstein dreamed his concepts of relativity.  So as silly and  
non-linear as it sounds maybe a straight line is NOT the shortest way  
to a goal!

Best wishes...

On Apr 4, 2005, at 7:23 AM, Dylan wrote:

>  Rescanned the scsi bus with the script to no avail.  It still did not  
> find the drive.  I went through the kernel and found that firewire was  
> disabled (along with a lot of other items I think I need...).  I  
> reconfigured the Kernel and re-compiled.  I have run into trouble when  
> it comes time to use 'make modules'.  I came up with an error when it  
> tried to compile the floppy driver.  Since I have a PowerBook Titanium  
> with no floppy, I just disabled the floppy and re-compiled.  I thought  
> I had it licked this time, but I was soon punished for my arrogance.   
> This time the error is coming up (still during the compilation of  
> modules...) with a driver for 'cipe.o'.  I looked it up and found out  
> it has something to do with IP Tunneling.  I went back through the  
> config and I am having trouble finding what is enabled in networking  
> that controls this.  I know the obvious is to disable, or compile as a  
> module, IP Tunneling, but I did not touch networking when I  
> re-compiled for Firewire.  My worry is that if I disable it, am I  
> going to shut down something I need (I use my laptop at work (the  
> powers that be are too cheap to provide laptops for the IT department,  
> even though we look after a network that spans both England, Scotland,  
> Northern Ireland and Ireland...greed and economics, gotta love  
> it...)...).  It works when you install YDL 3.0.1, why doesn't it  
> compile properly now.
>
>  I am going to upgrade the Kernel and try to reconfigure it from  
> scratch.  Maybe I will get lucky.  If not, I think that I am going to  
> have to take your second bit of advice and upgrade to YDL 4.0 (Last  
> ditch solution though, the delivery costs twice as much as the  
> software (Ooohhhhh more economics and greed, does the love never  
> end...).
>
>  In the mean time, do you have any suggestions?  Can you recommend a  
> good Kernel?  Last time I used YDL, the Benq(???) Kernels were the  
> ones to download.  Is this still true???
>
>  Thanks again for your previous help and any help you might be able to  
> further provide,
>
>  Dylan