On Sat, Aug 28, 2004 at 04:27:58PM +0200, Sven Luther wrote: > On Sat, Aug 28, 2004 at 04:08:06PM +0200, Martin Geier wrote: > > On Mon, Aug 23, 2004 at 11:32:30PM +0200, Sven Luther wrote: > > > On Mon, Aug 23, 2004 at 10:25:46PM +0200, Martin Geier wrote: > > > > On Mon, Aug 23, 2004 at 12:35:12PM +0200, Sven Luther wrote: > > > > > On Sun, Aug 22, 2004 at 09:13:32PM +0200, Martin Geier wrote: > > [snip] > > > > Are the debian-installer-floppies using kernel 2.6? Shall I try out > > > There is both the powerpc-small/floppy ones, which are based on 2.4, and > > > the > > > powerpc/floppy which are based on 2.6. > > So it seems that only the 2.4-based are running... > notice that powerpc-small/floppy has been moved to powerpc/floppy-2.4 Yeah, my assumption was right ;)
I tried: ./2004-08-28/powerpc/floppy-2.4/boot.img: red-crossed tux ./2004-08-28/powerpc/floppy-2.4/ofonlyboot.img: red-crossed tux I really don't understand that, because last time I tried the 2.4-based floppies they didn't show this behaviour. ./2004-08-28/powerpc/floppy/boot.img: red-crossed tux > > > > 2.6 on woody (mh, i would have to upgrade a lot of things...). Then I > > > > could verify if the fbdev works... > > > That would be great. > > Could you please send me the .config of the powerpc-small/floppy-kernel? > > Then I'll build an "equal" kernel and look what happens. > It is the one in the powerpc-small debian package, just get it from it. > (/boot/config-2.4.25-powerpc-small after install). Hm, I wasn't able to install the complete kernel-image: # You are attempting to install an initrd kernel image (version 2.4.25-powerpc-small) # but you do not seem to have a mkinitrd command in the path. This will # break the installation. I am aborting now. In any case, quik (the oldworld bootloader) seems not to support initrds :( So I unpacked the .deb to get the .config and changed the following from module to static: -mesh and 53c94 scsi driver -ext3 driver to be able to boot without initrd. Then I installed the kernel-source-2.4.25_2.4.25-3_all from sarge, cp'ed the modified .config, recompiled and rebooted. And guess: The screen turns off as like as when using the older debian-installer floppies! The systems comes up normally, I can ssh into it (after blindly(sp?) loading the ethernet-module ;) dmesg: mac kernel: Symbols match kernel version 2.4.25. mac kernel: atyfb: mach64GX (ATI888GX00) [0x00d7 rev 0x03] 2M VRAM, 14.31818 MHz XTAL, 135 MHz PLL, 50 Mhz MCLK, 50 Mhz XCLK mac kernel: atyfb: monitor sense=0, mode 20 mac kernel: Console: switching to colour frame buffer device 80x30 mac kernel: fb0: ATY Mach64 frame buffer device on PCI When adding "video=ofonly" to the kernel commandline, it works: mac kernel: Using unsupported 640x480 ATY,mach64 at 81000000, depth=8, pitch=640 mac kernel: Console: switching to colour frame buffer device 80x30 mac kernel: fb0: Open Firmware frame buffer device on /[EMAIL PROTECTED]/ATY,[EMAIL PROTECTED] When using the kernel-image from woody, it looks identical (and works too!) mac kernel: Symbols match kernel version 2.4.18. mac kernel: Using unsupported 640x480 ATY,mach64 at 81000000, depth=8, pitch=640 mac kernel: Console: switching to colour frame buffer device 80x30 mac kernel: fb0: Open Firmware frame buffer device on /[EMAIL PROTECTED]/ATY,[EMAIL PROTECTED] So the question is: Why is this not working when using the ofonlyboot-images? [snip] > > Another idea: Is it possible to start the new debian installer from a > > running > > woody-system? > No. Would be too easy ;) Greetings, Martin -- /ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ\ | PGP-Key 0x43D23ABE available via www.de.pgp.net, see header for fpr | \___________________________________________________________________/
