Re: [Fwd: Re: firewire issue]

Fabio <[email protected]>
Newsgroups gmane.os.freebsd.devel.firewire
Message-ID <[email protected]>
Le 26 oct. 2009 à 22:46, Andreas Tobler a écrit :

> Fabio,
>
> Fabio wrote:
>
>> Thank you both for your quick answer. I'll see what I can do with   
>> Andreas' diff. Right now, I'm still fighting with sysinstall  
>> (trying  to get the proper partition map) so it may take a while.
>
> Are you trying to install FreeBSD on an external firewire disk? Or  
> do you have a firewire device attached to you imac G3 and want to  
> install to an internal disk?
> If the first is true, I'm sorry, I feel it won't work since early  
> Apple Firewire chips are broken in several ways.
> If the second is true, please try to detach any firewire devices  
> from your G3 before booting.

No FW device is attached at all.

> The firewire code from 8.0/CURRENT goes into an infinite loop with  
> this crappy chip.

Well for now I'm booting from an USB 1.0 HD, but my ultimate goal is  
to boot from the FW. I'm not ready to give up right now ^^

> If both are not true, if you can, try to use the pdisk from OS-X to  
> format your partition you want fbsd installed on.

That's what I did. In fact, this is my partition map:

#:                type               name            length    
base      ( size )
1: Apple_partition_map       Apple         63 @ 1
2:     Apple_Bootstrap     freebsd_boot      4000 @ 64        (  2.0M)
3:           Apple_HFS       Extra        156297424 @ 4064      ( 74.5G)

But I keep getting an "Operation not permitted" with sysinstall. I  
even tried fdisk. And I used the "dd" command to copy the boot1.hfs  
file.
I'll see if I can find an answer in the freebsd-ppc list archive.

Fabio

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.