What are Source CDs for

[Arch and Cath]

Derick,

I believe at this point that I have a fundamental hardware incompatibility
problem.    pdisk lists 3 scsi devices; two of my Mac scsi hard drives and
my scsi ZIP.  It also lists the ATA drive containg my linux system and the
ATA cdrom.   No other drives.

Using insmod I have checked or loaded all of the drivers that seem to be
applicable.   

I have to think that the Keyspan USB/firewire card is not linux compatible.

Back to ebay and see what I can find.

Thanks for your help.

Arch

on 8/19/04 10:22 PM, Derick Centeno at aguilarojo@verizon.net wrote:

> Dear Arch:
> Did what I send to the list for your examination make sense to you?
> It takes a while to read the mount points which pdisk reports.
> Again pdisk is invoked from within the sbin directory and it can see all
> the drives currently connected and ON.  Of course, if the drive is off,
> it can't see it.
> 
> ./pdisk -l 
> the option following pdisk is an l (the letter l (el) not number 1.
> 
> you'll then get a listing of the drives on your system as I previously
> listed on mine and sent to the list.  Referring to what I sent in take a
> look and you'll see that the name I gave the firewire drive appears in
> quotes "Dharma V"; pdisk is telling us that Partition 5 of this drive is
> an Apple_HFS partition and IT IS.  This firewire drive is visible to the
> Mac OS.  HOwever pdisk is also saying that the location of this
> partition, note where it states horizontally Partition map etc.: on
> '/dev/sda, then all one has to do is count to where the name Dharma V
> appears and that is the mount point for that portion of the drive.  IN
> this example it is /dev/sda5
> 
> The rest is exactly as I presented it.
> 
> In other words use pdisk as I described and you'll find your firewire
> drive if it is on, connected properly and functioning.
> 
> Of course, the other thing which will help alot is what I mentioned
> earlier; when you created the partitions and named the firewire drive
> when you were within the Mac OS , did you give the drive a name you
> could easily spot distinguishing it from how the computer addresses or
> names anything else.  That is if you name your drive HD4532-RE or
> something like your eyes will pass right over it because they just get
> tired.  But if its named something unique that you would spot
> immediately, "Harriet" or something else anything which makes sense to
> you then when you are looking at the listing pdisk gives, you'll see
> that unique name no question about it.  The rest is really about row and
> column matching.  The name is at a certain row number and pdisk has
> listed the devices tree location.
> 
> Then to mount it on the desktop it is as I presented earlier.
> 
> You guessing what it may be is not a good use of your time.  Why guess??
> The method I showed you works...although it took me awhile to understand
> why and to read pdisk's messages; there's no short course other than
> this -- unfortunately.
> 
> Here's hoping that you get it straight eventually...
> Best wishes....
> 
> On Thu, 2004-08-19 at 20:13, Arch and Cath wrote:
>> on 8/19/04 7:54 PM, Derick Centeno at aguilarojo@verizon.net wrote:
>> 
>>> Arch...I tracked back to the branches discussing USB2 and Firewire;
>>> which from I can make out of the discussion is really about a particular
>>> card from a particular manufacturer which provides both USB2 AND
>>> Firewire ports on the same card.  I have a similar card sitting in my
>>> PCI slot and I have a Firewire drive connected which I mount and umount.
>>> 
>>> Perhaps the problem is more a matter of what you are expecting.  Linux
>>> should see firewire, usb and anything else; but it seeing it is very
>>> different from you mounting it onto your desktop so that you see it.
>>> 
>>> 
>>> Now I happen to know from experience that my firewire drive lives as
>>> /dev/sda5 but it is currently unmounted and unavailable to the Linux
>>> desktop (and to me) until I mount it.  But there is a subtle issue here;
>>> pdisk is NOT telling that it is a firewire drive by name;  it is telling
>>> me that a device is different from all other devices that Linux has put
>>> it on the sda chain!  It is up to me to know what the name of that drive
>>> is and what it means.  So name your drives in whatever ways jog your
>>> memory.  For me, I use Sanskrit nomenclature!
>> 
>> 
>> Therein lies my problem -- I don't know what my firewire drive lives as!  I
>> have pored over the lastlog file generated during boot to see what pseudo
>> SCSI drives there are.  I can only find the regulars.   I have built a mount
>> point directory and even tried guessing drive id's -- sdd would be the next
>> in line.  If I knew that it was /dev/sdd6, for instance, I would probably be
>> home free.  
>> 
>> Right now, I am going to boot again and once more review the lastlog to see
>> if I can find the /dev/ to mount.
>> 
>> Arch
>> 
>> _______________________________________________
>> yellowdog-newbie mailing list
>> yellowdog-newbie@lists.terrasoftsolutions.com
>> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
> 
> _______________________________________________
> yellowdog-newbie mailing list
> yellowdog-newbie@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie