Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Fri, Jan 21, 2005 at 07:25:05AM -0800, Shyamal Prasad wrote: > > "Gabriel" == Gabriel Paubert <[EMAIL PROTECTED]> writes: > > Gabriel> Not surprising, since *power4* means that it is a 64 bit > Gabriel> kernel, i.e., for G5 aka PPC970. > > The Debian power4 kernels in sarge still run in 32 bit mode AFAIK. Indeed, I was not clear, sorry. What I meant is that, even if it runs in 32 bit mode, it uses features of 64 bit processors that are very different of what is available in 32 bit processors (the MMU comes to mind: different page tables, no BATs but large segments, etc...). Cheers, Gabriel
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
"Gabriel" == Gabriel Paubert <[EMAIL PROTECTED]> writes: Gabriel> Not surprising, since *power4* means that it is a 64 bit Gabriel> kernel, i.e., for G5 aka PPC970. The Debian power4 kernels in sarge still run in 32 bit mode AFAIK. Cheers! Shyamal
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Fri, Jan 21, 2005 at 07:25:05AM -0800, Shyamal Prasad wrote: > > "Gabriel" == Gabriel Paubert <[EMAIL PROTECTED]> writes: > > Gabriel> Not surprising, since *power4* means that it is a 64 bit > Gabriel> kernel, i.e., for G5 aka PPC970. > > The Debian power4 kernels in sarge still run in 32 bit mode AFAIK. Indeed, I was not clear, sorry. What I meant is that, even if it runs in 32 bit mode, it uses features of 64 bit processors that are very different of what is available in 32 bit processors (the MMU comes to mind: different page tables, no BATs but large segments, etc...). Cheers, Gabriel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
"Gabriel" == Gabriel Paubert <[EMAIL PROTECTED]> writes: Gabriel> Not surprising, since *power4* means that it is a 64 bit Gabriel> kernel, i.e., for G5 aka PPC970. The Debian power4 kernels in sarge still run in 32 bit mode AFAIK. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 08:27:23PM +0100, Wolfgang Pfeiffer wrote: > On Thu, Jan 20, 2005 at 07:11:16PM +0100, Wolfgang Pfeiffer wrote: > > [ ... ] > > > > But I just installed a new kernel: > > kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) > > > > When trying to boot 2.4.27 I get this (I think that's still the Open > > Firmware stage where this happens - and I could not copy the following: I > > had to type the following ... hoping I didn't make any typos): > > > > returning 0x0140 from pro_init > > > > Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 > > > > I ignored the "quik" questions during the 2.4.27 install, i.e. I typed > > "no" when it asked whether to install some boot (?) parameters to > > /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my > > bootstrap partition ... > > Done. I uninstalled quik, installed another kernel: > kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the > previous kernel-image-2.4.27-power4-pmac probably was simply the wrong > kernel for the Powerbook G4 ... Not surprising, since *power4* means that it is a 64 bit kernel, i.e., for G5 aka PPC970. Gabriel
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 08:27:23PM +0100, Wolfgang Pfeiffer wrote: > On Thu, Jan 20, 2005 at 07:11:16PM +0100, Wolfgang Pfeiffer wrote: > > [ ... ] > > > > But I just installed a new kernel: > > kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) > > > > When trying to boot 2.4.27 I get this (I think that's still the Open > > Firmware stage where this happens - and I could not copy the following: I > > had to type the following ... hoping I didn't make any typos): > > > > returning 0x0140 from pro_init > > > > Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 > > > > I ignored the "quik" questions during the 2.4.27 install, i.e. I typed > > "no" when it asked whether to install some boot (?) parameters to > > /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my > > bootstrap partition ... > > Done. I uninstalled quik, installed another kernel: > kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the > previous kernel-image-2.4.27-power4-pmac probably was simply the wrong > kernel for the Powerbook G4 ... Not surprising, since *power4* means that it is a 64 bit kernel, i.e., for G5 aka PPC970. Gabriel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On 20-Jan-2005 Wolfgang Pfeiffer wrote:
> Done. I uninstalled quik, installed another kernel:
> kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the
>
> Whatever: At least I have now a hopefully firewire enabled Linux
> kernel here ...
You should be able to load the modules
ohci1394
sbp2
On my TiBook IV with kernel 2.4.24 I've to use a script called
'rescan-scsi-bus.sh' as mentioned at http://www.linux1394.org/sbp2.php.
After rescanning the scsi bus You should see the partitions in
/proc/partitions and have access to Your firewire disk.
I attached the version of rescan-scsi-bus.sh which works fine for me.
Friendly,
Thomas P.
#!/bin/bash
# Skript to rescan SCSI bus, using the
# scsi add-single-device mechanism
# (w) 98/03/19 Kurt Garloff <[EMAIL PROTECTED]> (c) GNU GPL
# Return hosts. /proc/scsi/HOSTADAPTER/? must exist
findhosts ()
{
hosts=
for name in /proc/scsi/*/?; do
name=${name#/proc/scsi/}
if test ! $name = scsi
then hosts="$hosts ${name#*/}"
echo "Host adapter ${name#*/} (${name%/*}) found."
fi
done
}
# Test if SCSI device $host $channen $id $lun exists
# Outputs description from /proc/scsi/scsi, returns new
testexist ()
{
grepstr="scsi$host Channel: 0$channel Id: 0*$id Lun: 0$lun"
new=`cat /proc/scsi/scsi|grep -e"$grepstr"`
if test ! -z "$new"
then cat /proc/scsi/scsi|grep -e"$grepstr"
cat /proc/scsi/scsi|grep -A2 -e"$grepstr"|tail -2|pr -o4 -l1
fi
}
# Perform search (scan $host)
dosearch ()
{
for channel in $channelsearch; do
for id in $idsearch; do
for lun in $lunsearch; do
new=
devnr="$host $channel $id $lun"
echo "Scanning for device $devnr ..."
printf "OLD: "
testexist
if test ! -z "$remove" -a ! -z "$new"
then echo "scsi remove-single-device $devnr" >/proc/scsi/scsi
echo "scsi add-single-device $devnr" >/proc/scsi/scsi
printf "\r\x1b[A\x1b[A\x1b[AOLD: "
testexist
if test -z "$new"; then printf "\rDEL: \r\n\n\n\n"; let rmvd+=1; fi
fi
if test -z "$new"
then printf "\rNEW: "
echo "scsi add-single-device $devnr" >/proc/scsi/scsi
testexist
if test -z "$new"; then printf "\r\x1b[A"; else let found+=1; fi
fi
done
done
done
}
# main
if test @$1 = @--help -o @$1 = @-h
then
echo "Usage: rescan-scsi-bus.sh [-l] [-w] [-c] [host [host ...]]"
echo " -l activates scanning for LUNs 0 .. 7 [default: 0]"
echo " -w enables scanning for device IDs 0 .. 15 [def.: 0 .. 7]"
echo " -r enables removing of devices[default: disabled]"
echo " -c enables scanning of channels 0 1 [default: 0]"
echo " If hosts are given, only these are scanned [default: all]"
exit 0
fi
# defaults
lunsearch="0"
idsearch="0 1 2 3 4 5 6 7"
channelsearch="0"
remove=""
# Scan options
opt="$1"
while test ! -z "$opt" -a -z "${opt##-*}"; do
opt=${opt#-}
case "$opt" in
l) lunsearch="0 1 2 3 4 5 6 7" ;;
w) idsearch="0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15" ;;
c) channelsearch="0 1" ;;
r) remove=1 ;;
*) echo "Unknown option -$opt !" ;;
esac
shift
opt="$1"
done
# Hosts given ?
if test @$1 = @; then findhosts; else hosts=$*; fi
declare -i found=0
declare -i rmvd=0
for host in $hosts; do dosearch; done
echo "$found new device(s) found. "
echo "$rmvd device(s) removed. "
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On 20-Jan-2005 Wolfgang Pfeiffer wrote:
> Done. I uninstalled quik, installed another kernel:
> kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the
>
> Whatever: At least I have now a hopefully firewire enabled Linux
> kernel here ...
You should be able to load the modules
ohci1394
sbp2
On my TiBook IV with kernel 2.4.24 I've to use a script called
'rescan-scsi-bus.sh' as mentioned at http://www.linux1394.org/sbp2.php.
After rescanning the scsi bus You should see the partitions in
/proc/partitions and have access to Your firewire disk.
I attached the version of rescan-scsi-bus.sh which works fine for me.
Friendly,
Thomas P.
#!/bin/bash
# Skript to rescan SCSI bus, using the
# scsi add-single-device mechanism
# (w) 98/03/19 Kurt Garloff <[EMAIL PROTECTED]> (c) GNU GPL
# Return hosts. /proc/scsi/HOSTADAPTER/? must exist
findhosts ()
{
hosts=
for name in /proc/scsi/*/?; do
name=${name#/proc/scsi/}
if test ! $name = scsi
then hosts="$hosts ${name#*/}"
echo "Host adapter ${name#*/} (${name%/*}) found."
fi
done
}
# Test if SCSI device $host $channen $id $lun exists
# Outputs description from /proc/scsi/scsi, returns new
testexist ()
{
grepstr="scsi$host Channel: 0$channel Id: 0*$id Lun: 0$lun"
new=`cat /proc/scsi/scsi|grep -e"$grepstr"`
if test ! -z "$new"
then cat /proc/scsi/scsi|grep -e"$grepstr"
cat /proc/scsi/scsi|grep -A2 -e"$grepstr"|tail -2|pr -o4 -l1
fi
}
# Perform search (scan $host)
dosearch ()
{
for channel in $channelsearch; do
for id in $idsearch; do
for lun in $lunsearch; do
new=
devnr="$host $channel $id $lun"
echo "Scanning for device $devnr ..."
printf "OLD: "
testexist
if test ! -z "$remove" -a ! -z "$new"
then echo "scsi remove-single-device $devnr" >/proc/scsi/scsi
echo "scsi add-single-device $devnr" >/proc/scsi/scsi
printf "\r\x1b[A\x1b[A\x1b[AOLD: "
testexist
if test -z "$new"; then printf "\rDEL: \r\n\n\n\n"; let rmvd+=1; fi
fi
if test -z "$new"
then printf "\rNEW: "
echo "scsi add-single-device $devnr" >/proc/scsi/scsi
testexist
if test -z "$new"; then printf "\r\x1b[A"; else let found+=1; fi
fi
done
done
done
}
# main
if test @$1 = @--help -o @$1 = @-h
then
echo "Usage: rescan-scsi-bus.sh [-l] [-w] [-c] [host [host ...]]"
echo " -l activates scanning for LUNs 0 .. 7 [default: 0]"
echo " -w enables scanning for device IDs 0 .. 15 [def.: 0 .. 7]"
echo " -r enables removing of devices[default: disabled]"
echo " -c enables scanning of channels 0 1 [default: 0]"
echo " If hosts are given, only these are scanned [default: all]"
exit 0
fi
# defaults
lunsearch="0"
idsearch="0 1 2 3 4 5 6 7"
channelsearch="0"
remove=""
# Scan options
opt="$1"
while test ! -z "$opt" -a -z "${opt##-*}"; do
opt=${opt#-}
case "$opt" in
l) lunsearch="0 1 2 3 4 5 6 7" ;;
w) idsearch="0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15" ;;
c) channelsearch="0 1" ;;
r) remove=1 ;;
*) echo "Unknown option -$opt !" ;;
esac
shift
opt="$1"
done
# Hosts given ?
if test @$1 = @; then findhosts; else hosts=$*; fi
declare -i found=0
declare -i rmvd=0
for host in $hosts; do dosearch; done
echo "$found new device(s) found. "
echo "$rmvd device(s) removed. "
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
"Wolfgang" == Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes: Wolfgang> The details: The hard disk broke on a PowerBook G4 Wolfgang> (TitaniumIV). The repair service already installed a new Wolfgang> disk to this machine. I need access to the old disk: The Wolfgang> repair service will give me the chance to access the Wolfgang> data on the old disk via a firewire connection from the Wolfgang> Titanium to the broken disk. This will happen tomorrow Wolfgang> noon. I have used recent d-i builds (Sarge RC2 and later, kernel 2.6.8) to boot a G4 laptop and it has detected an external firewire drive succesfully. The external drive in question was a newer G5 tower in target disk mode ;-) Might be worth a try: boot from CD, go to virtual terminal, mount two disks, and copy? Cheers! Shyamal
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 08:27:23PM +0100, Wolfgang Pfeiffer wrote: > > Done. I uninstalled quik, installed another kernel: > kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the ^ Typo ... :) .. should read: kernel-image-2.4.27-powerpc-pmac. Sorry Wolfgang > previous kernel-image-2.4.27-power4-pmac probably was simply the wrong > kernel for the Powerbook G4 ... >
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 07:11:16PM +0100, Wolfgang Pfeiffer wrote: [ ... ] > > But I just installed a new kernel: > kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) > > When trying to boot 2.4.27 I get this (I think that's still the Open > Firmware stage where this happens - and I could not copy the following: I > had to type the following ... hoping I didn't make any typos): > > returning 0x0140 from pro_init > > Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 > > I ignored the "quik" questions during the 2.4.27 install, i.e. I typed > "no" when it asked whether to install some boot (?) parameters to > /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my > bootstrap partition ... Done. I uninstalled quik, installed another kernel: kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the previous kernel-image-2.4.27-power4-pmac probably was simply the wrong kernel for the Powerbook G4 ... But this new kernel won't be staying here for long: The LED for hard disk activity seems to be disabled ... :( Whatever: At least I have now a hopefully firewire enabled Linux kernel here ... Let's see tomorrow ... Best Regards, and Thanks again Wolfgang
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
"Wolfgang" == Wolfgang Pfeiffer <[EMAIL PROTECTED]> writes: Wolfgang> The details: The hard disk broke on a PowerBook G4 Wolfgang> (TitaniumIV). The repair service already installed a new Wolfgang> disk to this machine. I need access to the old disk: The Wolfgang> repair service will give me the chance to access the Wolfgang> data on the old disk via a firewire connection from the Wolfgang> Titanium to the broken disk. This will happen tomorrow Wolfgang> noon. I have used recent d-i builds (Sarge RC2 and later, kernel 2.6.8) to boot a G4 laptop and it has detected an external firewire drive succesfully. The external drive in question was a newer G5 tower in target disk mode ;-) Might be worth a try: boot from CD, go to virtual terminal, mount two disks, and copy? Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Hi. Thanks a lot to all those responding so far ... On Thu, Jan 20, 2005 at 10:26:05AM -0600, vinai wrote: > Wolfgang, > > In the interests of time, I would recommend your trying the ext2 VFS > extension for Mac OS X, which can be found at: > > http://sourceforge.net/projects/ext2fsx/ > > I've been using a powerbook drive in a firewire case on my Pismo PB > for the better part of the last 2 years. This software is a kernel > extension, and allows you to access ext2 volumes from within Mac OS > X. I think it also works for ext3, but it ignores the journal. I have only Linux installed on this Titanium :) ... I'm still not quite sure whether it makes sense to 1: install OSX and 2: install the ext2 extension for OSX ... above all because it's not clear whether this extension will render OSX capable of reading the ext3 filesystem on my old disk ... > [ ... ] But I just installed a new kernel: kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) When trying to boot 2.4.27 I get this (I think that's still the Open Firmware stage where this happens - and I could not copy the following: I had to type the following ... hoping I didn't make any typos): -- returning 0x0140 from pro_init Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 - I ignored the "quik" questions during the 2.4.27 install, i.e. I typed "no" when it asked whether to install some boot (?) parameters to /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my bootstrap partition ... And what is this "quik" stuff: Do I need it for 2.4.27: I'd like to get rid of quik, and remove it from the system ... Will it be a problem? And yes: I changed yaboot.conf for the new kernel: --- boot=/dev/hda2 device=hd: partition=4 root=/dev/hda4 timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot default=Linux enablecdboot image=/vmlinux label=Linux read-only image=/vmlinux.old label=Linux2.4.18 read-only - ran 'ybin -v': nothing I have no idea what's going on: I can still boot my old 2.4.18 kernel. 2.4.27 broken? Anyone? TIA Wolfgang > > On Thu, 20 Jan 2005, Wolfgang Pfeiffer wrote: > > > Hi All > > > > Sorry for asking here instead of browsing Google: But I have not even 24 > > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > > configs, that are lost forever if I don't find some way to access them in > > the next few hours on the old disk. I can't keep the old disk, as > > Apple, as it seems, wants it back after I got a new one via the > > warranty I still have with an "Apple Care Protection Plan" ... > > > > The details: > > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > > already installed a new disk to this machine. I need access to the old > > disk: The repair service will give me the chance to access the data on > > the old disk via a firewire connection from the Titanium to the broken > > disk. This will happen tomorrow noon. [ ... ]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 08:27:23PM +0100, Wolfgang Pfeiffer wrote: > > Done. I uninstalled quik, installed another kernel: > kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the ^ Typo ... :) .. should read: kernel-image-2.4.27-powerpc-pmac. Sorry Wolfgang > previous kernel-image-2.4.27-power4-pmac probably was simply the wrong > kernel for the Powerbook G4 ... > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
On Thu, Jan 20, 2005 at 07:11:16PM +0100, Wolfgang Pfeiffer wrote: [ ... ] > > But I just installed a new kernel: > kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) > > When trying to boot 2.4.27 I get this (I think that's still the Open > Firmware stage where this happens - and I could not copy the following: I > had to type the following ... hoping I didn't make any typos): > > returning 0x0140 from pro_init > > Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 > > I ignored the "quik" questions during the 2.4.27 install, i.e. I typed > "no" when it asked whether to install some boot (?) parameters to > /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my > bootstrap partition ... Done. I uninstalled quik, installed another kernel: kernel-iamge-2.4.27-powerpc-pmac. And the latter booted fine. the previous kernel-image-2.4.27-power4-pmac probably was simply the wrong kernel for the Powerbook G4 ... But this new kernel won't be staying here for long: The LED for hard disk activity seems to be disabled ... :( Whatever: At least I have now a hopefully firewire enabled Linux kernel here ... Let's see tomorrow ... Best Regards, and Thanks again Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
If (the proposed solution by vinai does not work or) you insist on using linux to get your data you could download the gnoppix (ubuntu) beta live image and start from there. is possible that you will have the harddisk's icon on the desktop, so you won't have to worry about /dev/whatever :) I used this http://source.rfc822.org/pub/local/gnoppix/gnoppix/beta/hoary_0.9.3b3-powerpc.iso to boot from, on a PowerBook G4 and worked fine. Also there is: http://source.rfc822.org/pub/local/gnoppix/gnoppix/beta/hoary_0.9.3b2-powerpc.iso but I guess the newer the better. PS: I haven't tried firewire transfer on linux (neither on gnoppix or debian) so I can't say it works, but I guess, since the debian-installer team added download support through firewire devices (as ethernet), it works fine. Good luck, EddyP On Thu, 20 Jan 2005 16:54:19 +0100, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote: > Hi All > > Sorry for asking here instead of browsing Google: But I have not even 24 > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > configs, that are lost forever if I don't find some way to access them in > the next few hours on the old disk. I can't keep the old disk, as > Apple, as it seems, wants it back after I got a new one via the > warranty I still have with an "Apple Care Protection Plan" ... > > The details: > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > already installed a new disk to this machine. I need access to the old > disk: The repair service will give me the chance to access the data on > the old disk via a firewire connection from the Titanium to the broken > disk. This will happen tomorrow noon. > > Current software on the Titanium: > > A very rudimentary Debian/testing system is installed: Just enough > packages to get the machine booting from the new hard disk, with some > additional stuff like curl, lynx etc.. The kernel version on this > system is a 2.4.18-newpmac. > > My idea now was to either boot the Titanium from the Debian/3.0 r1 install > CD, to start the first few installer steps and then to copy the data > from the old, broken via firewire connected disk to the new disk > inside the Titanium. Or, alternatively, simply boot the Debian system > from the new disk and try to connect it to the old, via firewire > connected disk outside the PowerBook. > > The problem: I do not know, whether the Debian 3.0 r1 installer > system - that is, the 2.4.18 kernel - will *see* the old, via firewire to > the Titanium connected disk. > > And I also don't know anything about firewire technology until now; I > just had a look to the 2.4.18 config on the Titanium /boot dir, and I > see several instances of "CONFIG_IEEE1394*" modules. This actually > means this kernel is ready for firewire connections? Positive? > > Excerpt from the current 2.4.18 config: > -- > CONFIG_IEEE1394=m > CONFIG_IEEE1394_PCILYNX=m > CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m > CONFIG_IEEE1394_SBP2=m > CONFIG_IEEE1394_RAWIO=m > -- > > I consider installing a newer 2.6 (2.4?) kernel for the fresher > firewire drivers: > > Does anyone know where to get a readily installable, pre-compiled > ppc kernel that does not boot via initrd: I don't want this initrd stuff > on my machine, if possible: It is complicating things unnecessarily, > AFAICT .. > > And last question - important because I need to find a way to mount > the old disk outside: > How does the kernel call a hard disk that is connected via firewire: > /dev/hd[?] ... Or something else? > > Best Regards > > And thanks in anticipation > > Wolfgang > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Regards, EddyP
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Wolfgang, In the interests of time, I would recommend your trying the ext2 VFS extension for Mac OS X, which can be found at: http://sourceforge.net/projects/ext2fsx/ I've been using a powerbook drive in a firewire case on my Pismo PB for the better part of the last 2 years. This software is a kernel extension, and allows you to access ext2 volumes from within Mac OS X. I think it also works for ext3, but it ignores the journal. The only problems I've had with this software is from trying to work with files on the ext2 volumes from the Finder - that does (or did) not work. However, working with a command line from Terminal.app, or from an xterm in X11 should be just fine. And at least this way, you don't have to worry about Firewire support. >From what I recall, firewire support started working stably (for me at least) at ~ 2.4.16 to 2.4.18, so the Debian installer might be at that edge of support. If your disk is in another format, like xfs or jfs or reiser, this won't work ... Good luck ! cheers vinai On Thu, 20 Jan 2005, Wolfgang Pfeiffer wrote: > Hi All > > Sorry for asking here instead of browsing Google: But I have not even 24 > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > configs, that are lost forever if I don't find some way to access them in > the next few hours on the old disk. I can't keep the old disk, as > Apple, as it seems, wants it back after I got a new one via the > warranty I still have with an "Apple Care Protection Plan" ... > > The details: > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > already installed a new disk to this machine. I need access to the old > disk: The repair service will give me the chance to access the data on > the old disk via a firewire connection from the Titanium to the broken > disk. This will happen tomorrow noon. > > Current software on the Titanium: > > A very rudimentary Debian/testing system is installed: Just enough > packages to get the machine booting from the new hard disk, with some > additional stuff like curl, lynx etc.. The kernel version on this > system is a 2.4.18-newpmac. > > My idea now was to either boot the Titanium from the Debian/3.0 r1 install > CD, to start the first few installer steps and then to copy the data > from the old, broken via firewire connected disk to the new disk > inside the Titanium. Or, alternatively, simply boot the Debian system > from the new disk and try to connect it to the old, via firewire > connected disk outside the PowerBook. > > The problem: I do not know, whether the Debian 3.0 r1 installer > system - that is, the 2.4.18 kernel - will *see* the old, via firewire to > the Titanium connected disk. > > And I also don't know anything about firewire technology until now; I > just had a look to the 2.4.18 config on the Titanium /boot dir, and I > see several instances of "CONFIG_IEEE1394*" modules. This actually > means this kernel is ready for firewire connections? Positive? > > Excerpt from the current 2.4.18 config: > -- > CONFIG_IEEE1394=m > CONFIG_IEEE1394_PCILYNX=m > CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m > CONFIG_IEEE1394_SBP2=m > CONFIG_IEEE1394_RAWIO=m > -- > > I consider installing a newer 2.6 (2.4?) kernel for the fresher > firewire drivers: > > Does anyone know where to get a readily installable, pre-compiled > ppc kernel that does not boot via initrd: I don't want this initrd stuff > on my machine, if possible: It is complicating things unnecessarily, > AFAICT .. > > And last question - important because I need to find a way to mount > the old disk outside: > How does the kernel call a hard disk that is connected via firewire: > /dev/hd[?] ... Or something else? > > Best Regards > > And thanks in anticipation > > Wolfgang > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Hi. Thanks a lot to all those responding so far ... On Thu, Jan 20, 2005 at 10:26:05AM -0600, vinai wrote: > Wolfgang, > > In the interests of time, I would recommend your trying the ext2 VFS > extension for Mac OS X, which can be found at: > > http://sourceforge.net/projects/ext2fsx/ > > I've been using a powerbook drive in a firewire case on my Pismo PB > for the better part of the last 2 years. This software is a kernel > extension, and allows you to access ext2 volumes from within Mac OS > X. I think it also works for ext3, but it ignores the journal. I have only Linux installed on this Titanium :) ... I'm still not quite sure whether it makes sense to 1: install OSX and 2: install the ext2 extension for OSX ... above all because it's not clear whether this extension will render OSX capable of reading the ext3 filesystem on my old disk ... > [ ... ] But I just installed a new kernel: kernel-image-2.4.27-power4-pmac (correct for Titanium IV ? ... ) When trying to boot 2.4.27 I get this (I think that's still the Open Firmware stage where this happens - and I could not copy the following: I had to type the following ... hoping I didn't make any typos): -- returning 0x0140 from pro_init Invalid memory access at [unreadable]SRR0: 0054 [unread]SRR1: 5400 - I ignored the "quik" questions during the 2.4.27 install, i.e. I typed "no" when it asked whether to install some boot (?) parameters to /dev/hda4: hda4 is my root partition, and I wanted it to use hda2, my bootstrap partition ... And what is this "quik" stuff: Do I need it for 2.4.27: I'd like to get rid of quik, and remove it from the system ... Will it be a problem? And yes: I changed yaboot.conf for the new kernel: --- boot=/dev/hda2 device=hd: partition=4 root=/dev/hda4 timeout=30 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot default=Linux enablecdboot image=/vmlinux label=Linux read-only image=/vmlinux.old label=Linux2.4.18 read-only - ran 'ybin -v': nothing I have no idea what's going on: I can still boot my old 2.4.18 kernel. 2.4.27 broken? Anyone? TIA Wolfgang > > On Thu, 20 Jan 2005, Wolfgang Pfeiffer wrote: > > > Hi All > > > > Sorry for asking here instead of browsing Google: But I have not even 24 > > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > > configs, that are lost forever if I don't find some way to access them in > > the next few hours on the old disk. I can't keep the old disk, as > > Apple, as it seems, wants it back after I got a new one via the > > warranty I still have with an "Apple Care Protection Plan" ... > > > > The details: > > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > > already installed a new disk to this machine. I need access to the old > > disk: The repair service will give me the chance to access the data on > > the old disk via a firewire connection from the Titanium to the broken > > disk. This will happen tomorrow noon. [ ... ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Hi All Sorry for asking here instead of browsing Google: But I have not even 24 hours to rescue some configs from a broken hard disk. Data, i.e. Linux configs, that are lost forever if I don't find some way to access them in the next few hours on the old disk. I can't keep the old disk, as Apple, as it seems, wants it back after I got a new one via the warranty I still have with an "Apple Care Protection Plan" ... The details: The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service already installed a new disk to this machine. I need access to the old disk: The repair service will give me the chance to access the data on the old disk via a firewire connection from the Titanium to the broken disk. This will happen tomorrow noon. Current software on the Titanium: A very rudimentary Debian/testing system is installed: Just enough packages to get the machine booting from the new hard disk, with some additional stuff like curl, lynx etc.. The kernel version on this system is a 2.4.18-newpmac. My idea now was to either boot the Titanium from the Debian/3.0 r1 install CD, to start the first few installer steps and then to copy the data from the old, broken via firewire connected disk to the new disk inside the Titanium. Or, alternatively, simply boot the Debian system from the new disk and try to connect it to the old, via firewire connected disk outside the PowerBook. The problem: I do not know, whether the Debian 3.0 r1 installer system - that is, the 2.4.18 kernel - will *see* the old, via firewire to the Titanium connected disk. And I also don't know anything about firewire technology until now; I just had a look to the 2.4.18 config on the Titanium /boot dir, and I see several instances of "CONFIG_IEEE1394*" modules. This actually means this kernel is ready for firewire connections? Positive? Excerpt from the current 2.4.18 config: -- CONFIG_IEEE1394=m CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m CONFIG_IEEE1394_RAWIO=m -- I consider installing a newer 2.6 (2.4?) kernel for the fresher firewire drivers: Does anyone know where to get a readily installable, pre-compiled ppc kernel that does not boot via initrd: I don't want this initrd stuff on my machine, if possible: It is complicating things unnecessarily, AFAICT .. And last question - important because I need to find a way to mount the old disk outside: How does the kernel call a hard disk that is connected via firewire: /dev/hd[?] ... Or something else? Best Regards And thanks in anticipation Wolfgang
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
If (the proposed solution by vinai does not work or) you insist on using linux to get your data you could download the gnoppix (ubuntu) beta live image and start from there. is possible that you will have the harddisk's icon on the desktop, so you won't have to worry about /dev/whatever :) I used this http://source.rfc822.org/pub/local/gnoppix/gnoppix/beta/hoary_0.9.3b3-powerpc.iso to boot from, on a PowerBook G4 and worked fine. Also there is: http://source.rfc822.org/pub/local/gnoppix/gnoppix/beta/hoary_0.9.3b2-powerpc.iso but I guess the newer the better. PS: I haven't tried firewire transfer on linux (neither on gnoppix or debian) so I can't say it works, but I guess, since the debian-installer team added download support through firewire devices (as ethernet), it works fine. Good luck, EddyP On Thu, 20 Jan 2005 16:54:19 +0100, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote: > Hi All > > Sorry for asking here instead of browsing Google: But I have not even 24 > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > configs, that are lost forever if I don't find some way to access them in > the next few hours on the old disk. I can't keep the old disk, as > Apple, as it seems, wants it back after I got a new one via the > warranty I still have with an "Apple Care Protection Plan" ... > > The details: > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > already installed a new disk to this machine. I need access to the old > disk: The repair service will give me the chance to access the data on > the old disk via a firewire connection from the Titanium to the broken > disk. This will happen tomorrow noon. > > Current software on the Titanium: > > A very rudimentary Debian/testing system is installed: Just enough > packages to get the machine booting from the new hard disk, with some > additional stuff like curl, lynx etc.. The kernel version on this > system is a 2.4.18-newpmac. > > My idea now was to either boot the Titanium from the Debian/3.0 r1 install > CD, to start the first few installer steps and then to copy the data > from the old, broken via firewire connected disk to the new disk > inside the Titanium. Or, alternatively, simply boot the Debian system > from the new disk and try to connect it to the old, via firewire > connected disk outside the PowerBook. > > The problem: I do not know, whether the Debian 3.0 r1 installer > system - that is, the 2.4.18 kernel - will *see* the old, via firewire to > the Titanium connected disk. > > And I also don't know anything about firewire technology until now; I > just had a look to the 2.4.18 config on the Titanium /boot dir, and I > see several instances of "CONFIG_IEEE1394*" modules. This actually > means this kernel is ready for firewire connections? Positive? > > Excerpt from the current 2.4.18 config: > -- > CONFIG_IEEE1394=m > CONFIG_IEEE1394_PCILYNX=m > CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m > CONFIG_IEEE1394_SBP2=m > CONFIG_IEEE1394_RAWIO=m > -- > > I consider installing a newer 2.6 (2.4?) kernel for the fresher > firewire drivers: > > Does anyone know where to get a readily installable, pre-compiled > ppc kernel that does not boot via initrd: I don't want this initrd stuff > on my machine, if possible: It is complicating things unnecessarily, > AFAICT .. > > And last question - important because I need to find a way to mount > the old disk outside: > How does the kernel call a hard disk that is connected via firewire: > /dev/hd[?] ... Or something else? > > Best Regards > > And thanks in anticipation > > Wolfgang > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Regards, EddyP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Wolfgang, In the interests of time, I would recommend your trying the ext2 VFS extension for Mac OS X, which can be found at: http://sourceforge.net/projects/ext2fsx/ I've been using a powerbook drive in a firewire case on my Pismo PB for the better part of the last 2 years. This software is a kernel extension, and allows you to access ext2 volumes from within Mac OS X. I think it also works for ext3, but it ignores the journal. The only problems I've had with this software is from trying to work with files on the ext2 volumes from the Finder - that does (or did) not work. However, working with a command line from Terminal.app, or from an xterm in X11 should be just fine. And at least this way, you don't have to worry about Firewire support. >From what I recall, firewire support started working stably (for me at least) at ~ 2.4.16 to 2.4.18, so the Debian installer might be at that edge of support. If your disk is in another format, like xfs or jfs or reiser, this won't work ... Good luck ! cheers vinai On Thu, 20 Jan 2005, Wolfgang Pfeiffer wrote: > Hi All > > Sorry for asking here instead of browsing Google: But I have not even 24 > hours to rescue some configs from a broken hard disk. Data, i.e. Linux > configs, that are lost forever if I don't find some way to access them in > the next few hours on the old disk. I can't keep the old disk, as > Apple, as it seems, wants it back after I got a new one via the > warranty I still have with an "Apple Care Protection Plan" ... > > The details: > The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service > already installed a new disk to this machine. I need access to the old > disk: The repair service will give me the chance to access the data on > the old disk via a firewire connection from the Titanium to the broken > disk. This will happen tomorrow noon. > > Current software on the Titanium: > > A very rudimentary Debian/testing system is installed: Just enough > packages to get the machine booting from the new hard disk, with some > additional stuff like curl, lynx etc.. The kernel version on this > system is a 2.4.18-newpmac. > > My idea now was to either boot the Titanium from the Debian/3.0 r1 install > CD, to start the first few installer steps and then to copy the data > from the old, broken via firewire connected disk to the new disk > inside the Titanium. Or, alternatively, simply boot the Debian system > from the new disk and try to connect it to the old, via firewire > connected disk outside the PowerBook. > > The problem: I do not know, whether the Debian 3.0 r1 installer > system - that is, the 2.4.18 kernel - will *see* the old, via firewire to > the Titanium connected disk. > > And I also don't know anything about firewire technology until now; I > just had a look to the 2.4.18 config on the Titanium /boot dir, and I > see several instances of "CONFIG_IEEE1394*" modules. This actually > means this kernel is ready for firewire connections? Positive? > > Excerpt from the current 2.4.18 config: > -- > CONFIG_IEEE1394=m > CONFIG_IEEE1394_PCILYNX=m > CONFIG_IEEE1394_OHCI1394=m > CONFIG_IEEE1394_VIDEO1394=m > CONFIG_IEEE1394_SBP2=m > CONFIG_IEEE1394_RAWIO=m > -- > > I consider installing a newer 2.6 (2.4?) kernel for the fresher > firewire drivers: > > Does anyone know where to get a readily installable, pre-compiled > ppc kernel that does not boot via initrd: I don't want this initrd stuff > on my machine, if possible: It is complicating things unnecessarily, > AFAICT .. > > And last question - important because I need to find a way to mount > the old disk outside: > How does the kernel call a hard disk that is connected via firewire: > /dev/hd[?] ... Or something else? > > Best Regards > > And thanks in anticipation > > Wolfgang > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PPC Firewire support on 2.4.18-newpmac/Debian-3.0 r1 install CD?
Hi All Sorry for asking here instead of browsing Google: But I have not even 24 hours to rescue some configs from a broken hard disk. Data, i.e. Linux configs, that are lost forever if I don't find some way to access them in the next few hours on the old disk. I can't keep the old disk, as Apple, as it seems, wants it back after I got a new one via the warranty I still have with an "Apple Care Protection Plan" ... The details: The hard disk broke on a PowerBook G4 (TitaniumIV). The repair service already installed a new disk to this machine. I need access to the old disk: The repair service will give me the chance to access the data on the old disk via a firewire connection from the Titanium to the broken disk. This will happen tomorrow noon. Current software on the Titanium: A very rudimentary Debian/testing system is installed: Just enough packages to get the machine booting from the new hard disk, with some additional stuff like curl, lynx etc.. The kernel version on this system is a 2.4.18-newpmac. My idea now was to either boot the Titanium from the Debian/3.0 r1 install CD, to start the first few installer steps and then to copy the data from the old, broken via firewire connected disk to the new disk inside the Titanium. Or, alternatively, simply boot the Debian system from the new disk and try to connect it to the old, via firewire connected disk outside the PowerBook. The problem: I do not know, whether the Debian 3.0 r1 installer system - that is, the 2.4.18 kernel - will *see* the old, via firewire to the Titanium connected disk. And I also don't know anything about firewire technology until now; I just had a look to the 2.4.18 config on the Titanium /boot dir, and I see several instances of "CONFIG_IEEE1394*" modules. This actually means this kernel is ready for firewire connections? Positive? Excerpt from the current 2.4.18 config: -- CONFIG_IEEE1394=m CONFIG_IEEE1394_PCILYNX=m CONFIG_IEEE1394_OHCI1394=m CONFIG_IEEE1394_VIDEO1394=m CONFIG_IEEE1394_SBP2=m CONFIG_IEEE1394_RAWIO=m -- I consider installing a newer 2.6 (2.4?) kernel for the fresher firewire drivers: Does anyone know where to get a readily installable, pre-compiled ppc kernel that does not boot via initrd: I don't want this initrd stuff on my machine, if possible: It is complicating things unnecessarily, AFAICT .. And last question - important because I need to find a way to mount the old disk outside: How does the kernel call a hard disk that is connected via firewire: /dev/hd[?] ... Or something else? Best Regards And thanks in anticipation Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
