Power on powerbook G4
Hi all, I have one question about the behaviour of the battery on my powerbook G4: When the battery is full, and the electricity cable is still plug-in, does this damage the battery ? I heard that when the battery full is, you have to unplug the cable and wait before plug-in, till the battery empty is. I wanted to know if I can leave the electricity cable plug-in with full battery, without damaging my battery ? Thanks for the help Guillaume -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrecord a bootable cd
Mauricio Hernandez Z. [EMAIL PROTECTED] writes: [snip] Block size=512, Number of Blocks=58605120 DeviceType=0x0, DeviceId=0x0 -- William Hmmm, so you mean you installed your system using that very ISO? Yes, exactly. One of my friends burnt that for me using nero in Windows XP. Now, i'm trying to burn one of my own in case meeting system panic problems ;-) Then, have you successfully burnt cds using cdrecord and kernel 2.6.x? Sure. The problem is burning a bootable cd. AFAIK, cdrecord emulates SCSI behaviour for kernel 2.4.x but 2.6 does not need/use it. Right, i use ide-cd, no need SCSI emulations any more. I can't tell you much about it because I have not burnt any cds with 2.6.x yet (I was going to but my oldworld powerbook has not turned on/booted for the last 5 days :( ) Secondly, as I am forced to use an x86 machine -so far-, I remember I had similar problems with cdrecord (using 2.4.x) and bootable cds. That happened to me when burning while running Knoppix cd, but as soon as I tried K3B, the ISO booted correctly. (still scratching my head trying to understand WHAT TF was the difference). Also, the funny thing is that when using those cdrecord-burnt-cd to boot anohter x86 machine, the cds booted just fine, BUT in the machine I am using. That is what I can tell you by now. Sorry if I am not helpful :) You've helped me a lot, thanks. ;) As for hda v/s hdc the only time I have had an hdc HardDisk was when I reordered the cables for Master and Slave. -- Mauricio Hernandez Z. www.tecnocimiento.cl -- William -- 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]
Disable startup jingle on PowerBook G4?
Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? Thanks, Pander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Disable startup jingle on PowerBook G4?
Pander wrote: Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? Thanks, Pander Hi, install the package powerpc-utils and add the following line to your /etc/init.d/halt and /etc/init.d/reboot: nvsetvol 0 When you shut down / reboot OS X with the sound turned on, the startup jingle is also turned on. by, Martin -- Powered by Debian GNU / Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Disable startup jingle on PowerBook G4?
On Thu, Jan 20, 2005 at 05:01:24PM +0100, Pander wrote: Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? You can use nvsetvol from powerpc-utils to turn down the volume (to 0 if you don't want to hear it at all) Sjoerd -- Yeah, but you're taking the universe out of context. -- 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]
Re: MSNBC_Auto_Response: Thank you for contacting TODAY with Katie Couric and Ma
Can you please tell me how to contact acupuncturist Bruce Mandelbaum who was recently on your show to talk about acupuncture as an alternative to cosmetic surgery? I am interested in getting more information. Thank you, Mary Hatt [EMAIL PROTECTED]
Re: Power on powerbook G4
On Thu, 20 Jan 2005 11:33:36 +0100 Guillaume Florey [EMAIL PROTECTED] wrote: Hi all, I have one question about the behaviour of the battery on my powerbook G4: When the battery is full, and the electricity cable is still plug-in, does this damage the battery ? I heard that when the battery full is, you have to unplug the cable and wait before plug-in, till the battery empty is. I wanted to know if I can leave the electricity cable plug-in with full battery, without damaging my battery ? The plugged in AC connector doesn't do any harm to your battery. The battery charge is kept at maximum level controlled by an internal charging electronic. Usually high temperatures decrease battery life time and mobile computers with high speed processors mostly generate a lot of heat. Due to this it is recommended to remove a 75% charged battery while working on AC power but I think this not an option for you. Fortunately the Apple powerbooks don't get as hot as intel counterparts. :-) Another interesting fact about Li-Ion batteries is that the maximum live time is not only a matter of time but of charge cycles. Current battery packs usually allow 500 charge cycles (more or less) before they get useless. Even if you use you laptop only one hour on battery until recharging or drain it completely empty, the stress for the battery is the same. So batteries should always be used until they are completly empty before recharging. Best Regards Matthias Grimm -- 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: 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: Contents of /boot and /etc/yaboot.conf
Chris == Chris Doherty [EMAIL PROTECTED] writes: Chris I didn't use the --initrd options (or the added-patches Chris options, either) to make-kpkg. I made the mistake of Chris assuming that the defaults would be sensible. I'm Well, most people I've run into think that not having the initrd built by default is sensible. There is (was? its been a while) a certain class of Linux users who immediately recompile the kernel so they build all that they need into the kernel and not have any modules. They say this is more efficient. Whatever. It is hard to keep everyone happy. I hope you've had better (good) luck since. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Floppy disks
I want install Debian on a PowerMac I recently acquired. Unfortunately, I have to make floppies apparently, but I can't seem to find any instructions on exactly how to go about making floppies. Could someone give me some advice here? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Contents of /boot and /etc/yaboot.conf
Shyamal Prasad wrote: Well, most people I've run into think that not having the initrd built by default is sensible. There is (was? its been a while) a certain class of Linux users who immediately recompile the kernel so they build all that they need into the kernel and not have any modules. They say this is more efficient. Whatever. It is hard to keep everyone happy. That's not quite what I meant: given that not building in initrd means that one *must* have the right filesystems compiled directly in, and what that filesystem is is going to depend on what one decided to format the boot partition with, *and* that not compiling in initrd is likely to give you an unbootable system, it seems sensible to me that initrd should be on by default, since this will always give you a bootable system. Then again, I subscribe to the first do no harm philosophy of IT - it seems more useful to me for the defaults on these tools to give you a bootable system without necessarily optimizing very well; the optimization can come later (and of course should be supported by the same tools). Chris -- As an adolescent I aspired to lasting fame, I craved factual certainty, and I thirsted for a meaningful vision of human life - so I became a scientist. This is like becoming an archbishop so you can meet girls. ~ M. Cartmill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
unsubscribe
Re: cdrecord a bootable cd
Mauricio Hernandez Z. [EMAIL PROTECTED] writes: William Xuuu ([EMAIL PROTECTED]) wrote: Hi, Anybody knows how to burn a bootable cd using cdrecord ? With a simple command `cdrecord dev=ATAPI:0,0,0 boot.iso' , i'm able to burn a cd with exact same data in boot.iso, but i can't boot from it. Any suggestions would be appreciated. -- William Maybe I may have not understood correctly your question but... AFAIK, there's nothing special about it, just need to make sure the ISO is in fact bootable. If so, 1) get the device $ cdrecord --scanbus 2) burn the iso (my case dev=0,1,0) $ cdrecord -v dev=0,1,0 fs=16m speed=4 the_file.iso That will work at least for kernel 2.4.x So, nothing special in recording a bootable cd. Hmm, then why can't i boot it ? the ISO is definitely bootable. I have `enablecdboot' in yaboot.conf, and select that while booting, it seems to try to boot from cd-rom, but falls back to the menu after a while. My linux kernel is 2.6.9. by the way, i installed the base system using this ISO: http://penguinppc.org/~eb/files/boot-new-powermac-xfs.iso which recognized hda as hdc, see this: # fdisk -l /dev/hdc /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple63 @ 1( 31.5k) Partition map /dev/hdc2 Apple_Bootstrap bootstrap 1600 @ 64 (800.0k) NewWorld bootblock /dev/hdc3 Apple_UNIX_SVR2 swap 260544 @ 1664 (127.2M) Linux swap /dev/hdc4 Apple_UNIX_SVR2 root 12311320 @ 262208 ( 5.9G) Linux native /dev/hdc5 Apple_HFS Apple_HFS_Untitled_6 14180272 @ 12573528 ( 6.8G) HFS /dev/hdc6 Apple_UNIX_SVR2 source 31851320 @ 26753800 ( 15.2G) Linux native Block size=512, Number of Blocks=58605120 DeviceType=0x0, DeviceId=0x0 -- William
Power on powerbook G4
Hi all, I have one question about the behaviour of the battery on my powerbook G4: When the battery is full, and the electricity cable is still plug-in, does this damage the battery ? I heard that when the battery full is, you have to unplug the cable and wait before plug-in, till the battery empty is. I wanted to know if I can leave the electricity cable plug-in with full battery, without damaging my battery ? Thanks for the help Guillaume
Re: mounting msdos flash cards
On 19/01/2005 at 13:48 -0800, Adam Done wrote: That worked perfectly. Now I noticed that depending on what is pluged in first and or at start up such as a firewire drive or the compact flash card, the first one probed gets sda. So in my fstab file I set things for sda or sde which is listed in dmesg but it changes. How can I set it so the proper dev file to match the fstab? Use udev -- Kiko Private mail is preferred encrypted: http://www.pirispons.net/pgpkey.html
Re: ibook2.2's thermal control dilemma
According to Benjamin Herrenschmidt, on Wed, 19 Jan 2005 11:47:12 +1100, On Sun, 2005-01-16 at 22:49 +0100, Luca Bigliardi - shammash wrote: Ben does not like this patch. He also has explained why but i didn't understood (the problem is my little tech skill :) ). If Cedric who wrote the former driver feels that the lmsensor one is good enough with appropriate threshold values etc... then he can fix it to properly probe on the iBook. I'm sorry to say that, but I have not performed a real good evaluation of the lmsensor one. As I said, they support a lot of thing, a lot of applets support them, and they seem to have a good architecture, so I cannot recommend my version as beeing better than theirs... Nevertheless, you are right, I will try to have a look to their code and see if there is something clean to do in order to have something working on ppc. -- Cedric
Re: Getting 7500 w/ G3 upgrade card to boot w/ quik
Le mar 2005-01-18 a 17:55:40 -0500, Sean Jewett [EMAIL PROTECTED] a dit: I have a 7500 with a G3 upgrade card (Sonnet Crescendo G3/PCI 250Mhz 512K cache) that I'm having trouble getting to boot w/ quik. I can run the boot / root disks just fine, but after installing quik and rebooting the system hangs. I've spent the better part of the day going through various troubleshooting tips, a fair bit of which came from the NetBSD stuff here: both an 8500 and a power tower pro with a g3/300 here. both booted with no problems. the MESH SCSI controller might be getting in the way hoever. i encountered that with another PT pro witha g3/400. you need the g3/mesh patch possibly: http://www.cpu.lu/~mlan/linux/dev/g3upgrade.html : Booting from the internal SCSI bus set your output-device to whatever your video device is, and set your input-device to kbd (use boot var. or system disk: http://simonraven.nuit.ca/macppc/files/) and see if OF keeps whining about resetting SCSI Bus... repeatedly. if it is, then you need the patch (info grabbed from first URI). and please use quik 2.1, it's got new stuff in it that should make it much more usable. sarge's is updated to that version as of a few days ago. CC me if you have problems, i don't always read the ML. ec/sr -- Software Patents are patently wrong: http://swpat.ffii.org/papiere/eubsa-swpat0202/ustr0309/index.en.html signature.asc Description: Digital signature
Re: cdrecord a bootable cd
Mauricio Hernandez Z. [EMAIL PROTECTED] writes: [snip] Block size=512, Number of Blocks=58605120 DeviceType=0x0, DeviceId=0x0 -- William Hmmm, so you mean you installed your system using that very ISO? Yes, exactly. One of my friends burnt that for me using nero in Windows XP. Now, i'm trying to burn one of my own in case meeting system panic problems ;-) Then, have you successfully burnt cds using cdrecord and kernel 2.6.x? Sure. The problem is burning a bootable cd. AFAIK, cdrecord emulates SCSI behaviour for kernel 2.4.x but 2.6 does not need/use it. Right, i use ide-cd, no need SCSI emulations any more. I can't tell you much about it because I have not burnt any cds with 2.6.x yet (I was going to but my oldworld powerbook has not turned on/booted for the last 5 days :( ) Secondly, as I am forced to use an x86 machine -so far-, I remember I had similar problems with cdrecord (using 2.4.x) and bootable cds. That happened to me when burning while running Knoppix cd, but as soon as I tried K3B, the ISO booted correctly. (still scratching my head trying to understand WHAT TF was the difference). Also, the funny thing is that when using those cdrecord-burnt-cd to boot anohter x86 machine, the cds booted just fine, BUT in the machine I am using. That is what I can tell you by now. Sorry if I am not helpful :) You've helped me a lot, thanks. ;) As for hda v/s hdc the only time I have had an hdc HardDisk was when I reordered the cables for Master and Slave. -- Mauricio Hernandez Z. www.tecnocimiento.cl -- William
OldWorld almost dead no booting?
I have a WallStreet OldWorld (1999, first term), 350 MHz, 4,5GB, 256 MB, dual boot MacOS9 and Debian 3.1, kernel 2.6.9 (Yaboot). After using it with no problems for about a year (for office stuff, MoinMoin access to friends, etc. I turned it on/off many times, but also left it on for a week sometimes) I turned it off last saturday morning and I have not been able to turn it on since then :( The symptoms: - Power button does nothing. - Key Combination, Power+Shift+Fn+Ctrl does reboot turn it on but the only thing I hear is the sound of fan and see the green/yellow light. Other than that... nothing else I can see. - If I do not use the Fn key, the result is exactly as indicated above. First I thought it may have something to do with the power supply (cables broken or something) but I used a different one and it was the same problem. ANY IDEAS, PLEASE Thanks. -- Mauricio Hernandez Z. www.tecnocimiento.cl [Este mail ha sido escrito bajo estandares simples de edicion para asi evitar problemas de compatibilidad de caracteres considerando los idiomas y softwares de las personas que lo podran recibir]
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
Disable startup jingle on PowerBook G4?
Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? Thanks, Pander
Re: Disable startup jingle on PowerBook G4?
Pander wrote: Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? Thanks, Pander Hi, install the package powerpc-utils and add the following line to your /etc/init.d/halt and /etc/init.d/reboot: nvsetvol 0 When you shut down / reboot OS X with the sound turned on, the startup jingle is also turned on. by, Martin -- Powered by Debian GNU / Linux
Re: Disable startup jingle on PowerBook G4?
On Thu, Jan 20, 2005 at 05:01:24PM +0100, Pander wrote: Hi all, Is it possible to disable the stpid Apple startup jingle on a PowerBook G4? Some setting in OpenFirmware? You can use nvsetvol from powerpc-utils to turn down the volume (to 0 if you don't want to hear it at all) Sjoerd -- Yeah, but you're taking the universe out of context.
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?
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: MSNBC_Auto_Response: Thank you for contacting TODAY with Katie Couric and Ma
Can you please tell me how to contact acupuncturist Bruce Mandelbaum who was recently on your show to talk about acupuncture as an alternative to cosmetic surgery? I am interested in getting more information. Thank you, Mary Hatt [EMAIL PROTECTED]
Re: Power on powerbook G4
On Thu, 20 Jan 2005 11:33:36 +0100 Guillaume Florey [EMAIL PROTECTED] wrote: Hi all, I have one question about the behaviour of the battery on my powerbook G4: When the battery is full, and the electricity cable is still plug-in, does this damage the battery ? I heard that when the battery full is, you have to unplug the cable and wait before plug-in, till the battery empty is. I wanted to know if I can leave the electricity cable plug-in with full battery, without damaging my battery ? The plugged in AC connector doesn't do any harm to your battery. The battery charge is kept at maximum level controlled by an internal charging electronic. Usually high temperatures decrease battery life time and mobile computers with high speed processors mostly generate a lot of heat. Due to this it is recommended to remove a 75% charged battery while working on AC power but I think this not an option for you. Fortunately the Apple powerbooks don't get as hot as intel counterparts. :-) Another interesting fact about Li-Ion batteries is that the maximum live time is not only a matter of time but of charge cycles. Current battery packs usually allow 500 charge cycles (more or less) before they get useless. Even if you use you laptop only one hour on battery until recharging or drain it completely empty, the stress for the battery is the same. So batteries should always be used until they are completly empty before recharging. Best Regards Matthias Grimm
Re: Power on powerbook G4
Guillaume Florey wrote: Hi all, I have one question about the behaviour of the battery on my powerbook G4: When the battery is full, and the electricity cable is still plug-in, does this damage the battery ? I heard that when the battery full is, you have to unplug the cable and wait before plug-in, till the battery empty is. I wanted to know if I can leave the electricity cable plug-in with full battery, without damaging my battery ? I'm not an expert on that mather, but it should'nt be a problem because the battery stop being recharged when it is full (it is managed directly by the battery firmware I believe). Many batteries can have problems if they don't have full charge/discharge cycles, but it is not a problems with lithium-ion batteries. If you always keep your battery full (because you keep it at home or at your work place) Apple recommand to do the equivalent of a full charge/discharge cycle once a month to keep the electron flowing periodically. But you don't have to discharge it all in one time (you can discharge it by 2/3 once and in few days by 1/3 and it still count as a full cycle for your battery). That is not true for lead based batteries and most others. There is batteries that will have shorther life if they don't have full charge/discharge cycles, but it is not your case. Simon Valiquette http://gulus.USherbrooke.ca http://www.gulus.org
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. [ ... ]
Congratulations!!!You're a winner
Delotto Netherlands Lottery, 41132 NL- 1007 DB, AMSTERDAM, THE NETHERLANDS, HQs. FROM: THE DESK OF THE PROMOTIONS MANAGER, INTERNATIONAL PROMOTIONS/PRIZE NOTIFICATION DEPARTMENT, REF: KP6821873DL BATCH: 28/2017/IPD ATTENTION: RE: AWARD NOTIFICATION: FINAL NOTICE. We are pleased to inform you of the announcement today, 20th of JANUARY 2005 winners of the Delotto Netherlands Lottery PROGRAMS held on 31ST of DECEMBER,2004. Your company/individual e-mail, attached to ticket number (025-1146-2003-750), with serial number (2113-22) drew the lucky numbers (13-15-22-37-39-43), and consequently won the lottery in the 3rd category. You are therefore been approved for a lump sum pay of USD 800,000.00 (Eight Hundred Thousand United States Dollars) in cash credited to file REF NO. KP6821873DL. This is from total prize of US$10,400,000.00 shared among the twenty two international winners in this category. All participants were selected through a computer ballot system drawn from 15 million names from Australia, New Zealand, America, Europe and North America and Africa as part of International Promotions Program, which is conducted annually. CONGRATULATIONS! Your fund is now deposited with a security company insured in your name. Due to the mix up of some numbers and names, we ask that you keep this notification strictly from public notice until your claim has been processed and your money remitted to your account. This is part of our security protocol to avoid double claiming or unscrupulous acts by beneficiaries of this program. We hope with a part of your prize, you will participate in our mid of the year high stakes US$1.3 billion International Lottery. To begin your claim, please contact your claim agent: Dr. Cole James /ym/[EMAIL PROTECTED], [EMAIL PROTECTED] For due processing and remittance of your prize to a designated account of your choice. Remember, all prize money must be claimed not later than 30th JANUARY, 2005. After this date, all funds will be returned as unclaimed. NOTE: In order to avoid unnecessary delays and complications, please remember to quote your reference and batch numbers in every one of your correspondences. Furthermore, should there be any change of your address, do inform us as soon as possible. Congratulations once again from all the staff of Delotto Netherlands Lottery. And thank you for being part of our promotions program. Sincerely,DR.WAALE KOLH, THE PROMOTIONS MANAGER, Delotto Netherlands Lottery. N.B. Any breach of confidentiality on the part of the winners will result to disqualification. DR.WAALE KOLH. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 1/17/2005
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?
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?
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: Contents of /boot and /etc/yaboot.conf
Chris == Chris Doherty [EMAIL PROTECTED] writes: Chris I didn't use the --initrd options (or the added-patches Chris options, either) to make-kpkg. I made the mistake of Chris assuming that the defaults would be sensible. I'm Well, most people I've run into think that not having the initrd built by default is sensible. There is (was? its been a while) a certain class of Linux users who immediately recompile the kernel so they build all that they need into the kernel and not have any modules. They say this is more efficient. Whatever. It is hard to keep everyone happy. I hope you've had better (good) luck since. Cheers! Shyamal
Floppy disks
I want install Debian on a PowerMac I recently acquired. Unfortunately, I have to make floppies apparently, but I can't seem to find any instructions on exactly how to go about making floppies. Could someone give me some advice here? Curtis
Re: Floppy disks
Curtis Vaughan wrote: I want install Debian on a PowerMac I recently acquired. Unfortunately, I have to make floppies apparently, but I can't seem to find any instructions on exactly how to go about making floppies. Could someone give me some advice here? Curtis If you use bootx the process is pretty simple http://www.debian.org/releases/stable/powerpc/ch-install-methods.en.html#s-files-oldworld the basic idea is 1. partition hard drive (use macos hd tool) and create macos partition and 2 unix parts 2. install macos 3. install bootx and ramdisk and kernel 4. select ramdisk and kernel from bootx control panel 5. boot linux 6. follow prompts in debian installer you probably should have a debian cd as well, unless you have a good internet connection. have a look at the installation howto as well http://www.nl.debian.org/releases/stable/powerpc/install.en.html cheers -- - David Howe http://www.qednet.biz -
[www.tuttinudi.it] Dea
Stasera mia sorella mi ha invitata a cena e preparo gli involtini primavera... Speriamo bene chè oggi non è giornata: ho fatto un colloquio di lavoro e vogliono assumermi :-(! Lavorare si deve, ma sul fatto che nobiliti... ho seri dubbi! Lo so, sono una ragazza assurda... Se hai delle belle immagini mandamele qui: [EMAIL PROTECTED] PER I FORUM, O CHATTARE CON NOI E GLI ALTRI ISCRITTI: www.tuttinudi.it Problemi tecnici: [EMAIL PROTECTED] L'iscrizione (come anche tutto il resto) è GRATIS, segnalala ai tuoi amici: per iscriversi basta inviare una mail, anche vuota, a: [EMAIL PROTECTED] Se vuoi regalare l'iscrizione ad un amico c'è il box sulla home page del sito. Per CANCELLARTI manda un messaggio anche vuoto a: [EMAIL PROTECTED] attachment: tn00033.jpg
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: Contents of /boot and /etc/yaboot.conf
Shyamal Prasad wrote: Well, most people I've run into think that not having the initrd built by default is sensible. There is (was? its been a while) a certain class of Linux users who immediately recompile the kernel so they build all that they need into the kernel and not have any modules. They say this is more efficient. Whatever. It is hard to keep everyone happy. That's not quite what I meant: given that not building in initrd means that one *must* have the right filesystems compiled directly in, and what that filesystem is is going to depend on what one decided to format the boot partition with, *and* that not compiling in initrd is likely to give you an unbootable system, it seems sensible to me that initrd should be on by default, since this will always give you a bootable system. Then again, I subscribe to the first do no harm philosophy of IT - it seems more useful to me for the defaults on these tools to give you a bootable system without necessarily optimizing very well; the optimization can come later (and of course should be supported by the same tools). Chris -- As an adolescent I aspired to lasting fame, I craved factual certainty, and I thirsted for a meaningful vision of human life - so I became a scientist. This is like becoming an archbishop so you can meet girls. ~ M. Cartmill
on kernel building, firewire support, my install HowTo
Hello everyone, I've used debian-ppc off and on for about two years now. This is the first I've never really participated in the debian community as most of my experimenting was from reading (and some irc). About the firewire support, RC2 has firewire enabled by default as my firewire burner is detected and works (It's a LiteOn repackaged as a Lacie). So there is no need to custom make a kernel for this reason. As for building kernels, it seems that every linux-pc head named tom, dick, and harry that I personally know has built a kernel. According to my experience and that of others I have read, it is not such an easy process on ppc. In retrospect I now know what probably made it fail, but what I found annoying is the sheer lack of qualitative (or quantitative) data on how to build specifically a working ppc 2.6 kernel (when I looked at least). Seems there is lots of info for 2.4, and most of that pc specific. When searching as to why my kernel failed, I've been told that it might have been because some things were created as modules that were supposed to be built into the kernel. The pc specific HowTos (that I've read) do not take into account ppc specifics that might break your kernel. You'd think they make the set up so as to not allow disabling choices such as these. In part they do, but this leaves a lot to be desired. My two cents is that try to use the RC2 stock kernel before you go out and try a custom one. And as for a method of install, I've installed not so intuitive OSes that like you to do things in blocks (such as a bsd I will not mention by name), and I always come back to a simple mac? way of doing things. Essentially I speak of the routine a certain redhat ppc suggests in their install manual (that I've aquisitioned). If you want a dual boot, it's the simplist and least terse. 1. boot from mac OS (X) install CD 2. goto the disk utility (under file?). 3. Once booted from CD, partition top leaving it as Free Space (the name used in OS X's disk utility (classic uses some other name for Free Space but it is reminiscent of Free Space) 4. partition making the bottom partition HFS(+) The Free space and MacOS must be this way else the partition scheme collapses 4.1 goto disk icon of the Free Space partition, highlight and select info button. Write down unix designation (such as disk0sX where is X equals is number. Jot this down). 5. quit disk utility and start the OS X installer. 5.1 Finish OS X install, put up firewall, update 6. then use the latest sarge installer and select manual install process. 7. find the Free Space (recall the the unix designation number (without the disk0s) as this should be the same as what gnu-linux calls it), highlight it -- enter- select automatically partition (I think I select select work desk [what ever gives a separate partition for user]). Then the installer will put you back into the manual partitioner utility. From here you can highlight partitions and hit 'enter' to change their default sizes. Easy as pie. At debian's manual partitioner: I sometimes simply do not bother to take down the disk0s number because I've made the partitions significantly different sizes so as it is easy to tell the difference. Also, if Panther partitioned, Free Space will show up (can't remember what Jaguar names it but is similar). From here you select to write partition scheme, once again it asks you to approve partitions that it will change. Somewhere at this point the sarge's RC1 used to notify me about not installing a bootloader (I don't think RC2 does this anymore). If so, just ignore it as it is installed latter on (or prompts you to latter on). The notifying of having installed no bootloader seemed to be a bug, an annoying one at that. This works for me on a new world by installing yaboot (and gives me a working kernel that supports my firewire burner). But I would think that if sarge is nearing maturity ... it would also intutively install an old world bootloader instead of yaboot within this routine. If the installer does not install the proper bootloader, you should still have the option of using apple's boot loader. As I recall (correct me if I am wrong anyone), macs with OF (of any version) offer the a graphical boot loader if you boot with the option key (yes not called the alt key:]) held down. This works for me when I've had bootloader problems from, other distro, installs that mess up yaboot. Then again I have version 3 of OF. Last thing I'll say for now, sarge RC2 with the default kernel and with KDE just flies. It's is so responsive that I have had a brand new G4 ibook collecting dust. Moral of the story, if you just want a working system try the defaults first. And if you're having trouble with terse install procedures try the above instructions (they'll work as long as the default supports your machine. Else you can perhaps adapt it). I did write them from memory, but they should be fine. Sorry about the length, but
