| 04:19.43 | *** join/#debianppc apt_ (i=ibot@rikers.org) |
| 04:19.43 | *** topic/#debianppc is The Debian GNU/Linux PowerPC Port: http://www.debian.org/ports/powerpc/ | Debian CDs are not bootable on OldWorld PowerMacs |
| 04:36.29 | *** join/#debianppc tilmann_ (n=tilmann@p5B2F442F.dip.t-dialin.net) |
| 04:39.12 | *** join/#debianppc kelsoo (n=ok@bb-87-82-13-52.ukonline.co.uk) |
| 04:51.15 | *** join/#debianppc apt (i=ibot@rikers.org) |
| 04:51.15 | *** topic/#debianppc is The Debian GNU/Linux PowerPC Port: http://www.debian.org/ports/powerpc/ | Debian CDs are not bootable on OldWorld PowerMacs |
| 06:46.30 | *** join/#debianppc vaidy (n=sv@122.248.161.59) |
| 07:07.42 | *** join/#debianppc Muhammad (n=Karmic@unaffiliated/eng1n33r) |
| 08:01.55 | *** join/#debianppc lumis (n=jon@cpc1-leic7-0-0-cust236.lei3.cable.ntl.com) |
| 08:49.14 | *** join/#debianppc psychicist_ (n=psychici@j0175.upc-j.chello.nl) |
| 09:20.36 | *** join/#debianppc pahartik (i=pahartik@zazu.pahartik.iki.fi) |
| 10:11.50 | *** join/#debianppc ssam (n=ssam@87.127.117.246) |
| 12:09.24 | *** join/#debianppc Bryanstein (i=bryan@free.psybnc.and.eggdrop.at.shellium.org) |
| 14:42.13 | *** join/#debianppc vaidy (n=sv@59.96.205.236) |
| 15:01.44 | *** join/#debianppc vaidy (n=sv@59.96.205.236) |
| 15:43.24 | *** join/#debianppc _Trinity_ (n=Chascon@pc-72-103-160-190.cm.vtr.net) |
| 16:42.18 | *** join/#debianppc DelTree (n=deplagne@213.246.51.70) [NETSPLIT VICTIM] |
| 16:42.18 | *** join/#debianppc Bor_Ed (n=ari@65.13.147.133) [NETSPLIT VICTIM] |
| 17:01.20 | *** join/#debianppc peterrooney (n=peter@96.54.162.41) |
| 19:46.25 | *** join/#debianppc ssam (n=ssam@87.127.117.246) |
| 21:58.55 | *** join/#debianppc Jeah (n=eric@c-69-247-233-37.hsd1.fl.comcast.net) |
| 22:02.48 | Jeah | Can anyone help me with BootX? I'm trying to use it to boot the Lenny installer on an Old World PowerBook, but all I get is a "Welcome to Linux, kernel 2.6.26-2-powerpc" message and nothing happens after that. |
| 22:03.25 | Jeah | I've read several tutorials online, but no one seems to mention that kind of problem. |
| 22:21.57 | pahartik | Jeah: Did you also point it to ramdisk image? |
| 22:23.44 | Jeah | pahartik: Yes. The problems I can come up with regarding the ramdisk are that I'm using initrd.gz whereas BootX documentation says it should be ramdisk.image.gz or something and that maybe the specified ramdisk size is wrong. But lots of the tutorials say that the initrd.gz works as the ramdisk, and I've tried specifying larger ramdisk sizes... |
| 22:25.22 | Jeah | pahartik: The funny thing is that several of the tutorials don't say anything about changing the ramdisk size even though I believe it's necessary for any recent installers. The default is 8 megs. |
| 22:26.32 | pahartik | Jeah: You could also try to add "video=ofonly" to parameters... And try older kernel and ramdisk images... |
| 22:30.18 | Jeah | pahartik: I'll try the "video=ofonly" in a sec here. I was actually able to get BootX to work with the Woody kernel and ramdisk (that one's actually a ramdisk.image.gz) but the upgrade path was too long and bumpy for my technical abilities. |
| 22:31.03 | Jeah | pahartik: And I figured since I found pages of people saying Lenny worked for them that it wouldn't be a problem. Well, not an insurmountable one, anyway... |
| 22:37.57 | Jeah | pahartik: No luck with the "video=ofonly". BootX has a "No video driver" option that is supposed to be equivalent, and I tried that too, with no improvement. |
| 22:39.05 | pahartik | Jeah: I do not have problems with recent Linux kernels, but my OldWorld systems are running Debian Etch, because of incompatibility between "PowerPC 604e" and recent "libc6" |
| 22:39.59 | pahartik | Jeah: (I always build my own kernel packages with system-specific configurations) |
| 22:40.31 | simonrvn | Jeah: the 'ramdisk' size should exactly 16384 kB |
| 22:41.08 | simonrvn | that number should be specified in kB and powers of 2 |
| 22:41.26 | Jeah | pahartik: My CPU is supposed to be a PowerPC 603e. Would that be a problem for me with the standard kernel? |
| 22:42.15 | pahartik | Jeah: It should work... |
| 22:42.47 | Jeah | simonrvn: Ok, I'll give that a shot real quick. I think for some reason it's not saving my selection for ramdisk size, either... I'll have to look into that. I specify a different size, hit save preferences, and boot. It doesn't work, then next time the size is back down to 8192 (the default). |
| 22:42.54 | pahartik | Jeah: What kind of hardware do you try to run it on? |
| 22:43.12 | simonrvn | yeh it's doesn't save the number at all. |
| 22:43.23 | simonrvn | thinks bug |
| 22:44.05 | Jeah | simonrvn: I've tried 32768 as per the note on this tutorial: http://knol.google.com/k/bootx-and-debian-ppc-on-old-world-macintosh-architecture |
| 22:44.19 | Jeah | simonrvn: I'll try yours, though. |
| 22:44.43 | Jeah | pahartik: powerbook 3400 |
| 22:44.45 | simonrvn | hm ok. not really needed to be that big, but helps sometimes if it's a large initrd. |
| 22:45.32 | Jeah | simonrvn: I'm trying to use the initrd.gz copied from the debian-503-powerpc-netinst.iso CD. |
| 22:45.44 | simonrvn | why? |
| 22:45.53 | simonrvn | boot the installer? |
| 22:47.47 | pahartik | Jeah: Frame buffer on old PowerBook is probably challenging device to support |
| 22:48.43 | Jeah | simonrvn: Yeah, to start the installation. No luck with 16384, unfortunately... |
| 22:50.01 | Jeah | pahartik: Weird that it was supported in Woody, though. Would that have been dropped? |
| 22:51.16 | pahartik | Jeah: Build custom kernel package from latest "linux-source" package provided by Debian, configured to have necessary drivers built-in and not as modules... |
| 22:53.12 | pahartik | Jeah: Maybe there has been no similar device to test recent default Linux kernels on |
| 22:54.33 | Jeah | pahartik: Embarrassing confession: I've never compiled a kernel before. |
| 22:55.20 | Jeah | pahartik: That might be past my meager Linux knowledge. |
| 22:56.41 | Jeah | pahartik: Would the symptom be right? Not doing anything at all after the welcome message? |
| 22:59.02 | pahartik | Jeah: If you do not want to build kernels, use latest Debian release that seems to work on it... |
| 23:01.48 | Jeah | pahartik: Hm, ok, that's probably the way to go... I just like staying current if possible. I guess if it's not possible then that's that. |
| 23:02.47 | Jeah | pahartik: I just hope I don't have to go all the way back to woody or something else that's not even getting patches anymore. |
| 23:03.59 | Jeah | pahartik: If I do decide to give custom kernel compilation a go, how will I know which drivers I'll actually need? |
| 23:04.51 | Jeah | pahartik: And can I compile the kernel on a different architecture or does it actually have to be compiled on a PPC? |
| 23:06.02 | peterrooney | Jeah: You can do that, it's called cross-compiling |
| 23:06.04 | pahartik | Jeah: Check out which drivers are being used on kernel that you have managed to boot... Then enable those and test... |
| 23:06.41 | Jeah | peterrooney: Thanks. I'll look that up. |
| 23:07.10 | Jeah | pahartik: Ok. Thanks. |
| 23:07.32 | pahartik | Jeah: With new system, I usually configure and build kernel at least few times before I get results I am satisfied with |
| 23:08.26 | Jeah | pahartik: Ah, fun. :) Wait, did I accidentally go to #gentooppc? :-D |
| 23:09.12 | Jeah | pahartik: Just kidding, I'm sure it'll be good to know this stuff sooner or later. Always plenty of learning experiences to be had with Linux! |
| 23:10.51 | pahartik | Jeah: Well, I do not build everything, just kernel and some userland packages... Those that I want to optimize or use different configuration or version |
| 23:11.38 | pahartik | Jeah: But it is great fun to configure and build kernel packages on various architectures |
| 23:13.53 | Jeah | pahartik: Cool. Well, thanks for all the help! |
| 23:14.14 | pahartik | Jeah: You are welcome |
| 23:19.40 | Jeah | pahartik: Shoot, one more volley of questions. If I compile a custom kernel, can I use it for the installation, too? If so, would I need to make a custom ramdisk as well, or could I use the standard one? |
| 23:20.53 | Jeah | pahartik: Or is a kernel for installation different somehow? |
| 23:23.43 | pahartik | Jeah: I do not know about recent installers, but if kernel has necessary parts built in, it should be enough for installer |
| 23:24.31 | Jeah | pahartik: Necessary parts meaning necessary drivers for the system? |
| 23:27.27 | pahartik | Jeah: Yes... Speaking of it, I should try to build custom kernel for current installer and see how it works... |
| 23:28.18 | Jeah | pahartik: Do you have a similar system? |
| 23:32.47 | pahartik | Jeah: Not really... I have PowerMacintosh 7300/200 (probably closest to it of my OldWorld systems) |
| 23:35.05 | Jeah | pahartik: Oh, were you offering to compile one for *me* to try? |
| 23:35.48 | Jeah | pahartik: Or do you think that your system would be close enough that if it works for yours it should be possible for mine, too? |
| 23:44.16 | pahartik | Jeah: Oh, I could try to compile Linux kernel for PowerMacintosh 3400... |
| 23:46.15 | Jeah | pahartik: If that's not what you were thinking, I don't want to make you do that. |
| 23:47.58 | Jeah | pahartik: Let me try booting some older installer kernels real quick and see if I can get it to go with something more recent than Woody. |
| 23:48.22 | pahartik | Jeah: At least I thought I could try to configure custom kernel for provided installer ramdisk, just to see what it requires nowadays |
| 23:49.09 | pahartik | Jeah: That sounds like easy and efficient test |
| 23:49.45 | Jeah | pahartik: True. |