[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FireWire Hard Disk

Thanks a lot, I got step further now...

Now I have a rather ignorant question:

How do I format my firewire-harddisk so that i can mount it in linux?

I formated it in OsX as DOS-Type.

Under linux pmac-fdisk produces the following output:

titan:/mnt# pmac-fdisk /dev/sda
The number of cylinders for this disk is set to 3648.
This is larger than 1024, and may cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software form other OSs
  (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sda: 255 heads, 63 sectors, 3648 cylinders
Units = cylinders of 16065 * 512 bytes

  Device Boot   Begin    Start      End   Blocks   Id  System

Command (m for help):

What does that mean? There is no partition recognized, am I correct?

How did you guys out there with working fw-drives format/partition your disks?


Nicolas Lopez wrote:

On Thu, Jul 18, 2002 at 01:06:51AM +0200, jonas bandi wrote:

I try to use my firewire-harddisk with my 2nd gen tiBook.

I compiled the latest benh kernel as suggested in earlier posts.

dmesg produces now the following output:


Is that good? What is missing?

That's all good.
What can I do now ? I expected something like "Attached scsi disk sda at scsi1, channel 0, id 0, lun 0", that would tell me what to mount ...

 The 1394 stacks in newer BenH kernels are less energetic about reporting
things to the scsi layer than they used to be.  This is mostly a good thing,
it just requires either a properly configured hotplug daemon or sending
notifications to the scsi layer manually. I manually alert the scsi layer to changes with the rescan-scsi-bus.sh
script which just forces an excessive reprobe. Search either this lists's
archives or google for the script. Then just run it after pluging in your
device and run it again with the -r switch after unpluging the device. Don't
forget to unmount before removing the devices.

 Also, last I checked there was no support for PowerBook sleep mode(or any)
and very bad things tend to happen if you put the laptop to sleep while the
1394 modules are loaded. I usually get droped into the kernel debugger at
the first activity on the bus after a sleep. Seeing about properly handling
sleep is on my todo list. I looked at the code last night and might try
breaking my kernel tonight.

 - Nick Lopez
We still need to do something about quik, ritual goat sacrifice is
somewhat tricky to implement in C...
  - Ethan Benson on debian-boot 5-30-01

To UNSUBSCRIBE, email to debian-powerpc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: