On Fri, Sep 08, 2006 at 03:32:25PM +0200, Sven Luther wrote: > On Fri, Sep 08, 2006 at 03:20:58PM +0200, Hans Ekbrand wrote: > > Hi! > > Hi, please make sure you CC debian-kernel too on issues like this.
Bug #366620 is against linux-image-2.6.16-2-powerpc, my post was a follow up to [EMAIL PROTECTED] CC:ed to debian-powerpc. > > The official debian kernels for powerpc stopped working for me with > > 2.6.16 (2.6.15 works fine). The 2.6.16 ones fail to mount root fs at > > boot, which I have reported in bug #366620 > > > > I compiled my own 2.6.16 with a minimal change in .config, and that > > was it, 2.6.16 now boots on my oldworld mac. > > > > The needed change in config was the following: (diff against > > ./boot/config-2.6.16-2-powerpc in the package > > linux-image-2.6.16-2-powerpc_2.6.16-18_powerpc.deb) > > > > 4c4 > > < # Sat Aug 19 00:42:57 2006 > > --- > > > # Fri Sep 8 09:14:38 2006 > > 772c772 > > < CONFIG_BLK_DEV_IDEDISK=m > > --- > > > CONFIG_BLK_DEV_IDEDISK=y > > 2317c2317 > > < CONFIG_EXT2_FS=m > > --- > > > CONFIG_EXT2_FS=y > > 2328c2328 > > < CONFIG_FS_MBCACHE=m > > --- > > > CONFIG_FS_MBCACHE=y > > > > I think this shows that there is some problem with loading the proper > > modules for ide and ext2 from the initrd. As stated in the bugreport > > of #366620 I have tried both yaird and the other initrd creator. [...] > > Will you consider appling this patch to the config? While it is not > > the right solution in the long term, it would make oldworld macs run > > with official debian kernels again (at least the ones with > > IDE-drives). > > No, please get the ramdisk creator packages to get fixed for this one, if it > is that the issue. I don't know what to belive anymore, I have tested both mkinitramfs and yaird (their previous and current versions). I have inspected the initrds that they produce and the module for ide, "ide-disk" is included. > Also, can you please try the 2.6.18-rc6 packages from : > > http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/ > > and see if your problem persists there. Yes the problem persists. But 2.6.18-rc6 gives a clearer error message at boot. Here is the output at boot on 2.6.18-rc6 (failing) ide0: no intrs for device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED], using 13 ide0: Found Apple OHare ATA controller, bus ID 0, irq 13 [...] hda: QUANTUM FIREBALL_TM1700A, ATA DISK drive hda: Enabling Multiword DMA 2 ide0: Disabled unable to get IRQ 13. ide0: failed to initialize IDE interface [...] VFS: Cannot open root device "hda5" or unknown-block(0,0) * Here is the output of a successful boot (with 2.6.16) * ide0: no intrs for device /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED], using 13 ide0: Found Apple OHare ATA controller, bus ID 0, irq 13 Probing IDE interface ide0... [...] hda: QUANTUM FIREBALL_TM1700A, ATA DISK drive hda: Enabling MultiWord DMA 2 ide0 at 0xc2016000-0xc2016007,0xc2016160 on irq 13 hda: max request size: 128KiB hda: 3335472 sectors (1707 MB) w/76KiB Cache, CHS=3309/16/63, DMA hda: [mac] hda1 hda2 hda3 hda4 hda5 hda6 hda7 * Here is the output of yaird, looks OK * # yaird --verbose --output=/boot/myyaird.img 2.6.18-rc6-powerpc yaird: goal: template, prologue (/etc/yaird/Default.cfg:52) yaird: action: prologue, {} yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56) yaird: goal: input, -- (/etc/yaird/Default.cfg:73) yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103) yaird: goal: module, evdev (/etc/yaird/Default.cfg:104) yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/drivers/input/evdev.ko {optionList=-- } yaird: goal: resume, -- (/etc/yaird/Default.cfg:143) yaird: goal: mountdir, / (/etc/yaird/Default.cfg:157) yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/drivers/ide/ide-disk.ko {optionList=-- } yaird: hardware: completed pci0000:00/0000:00:10.0/0.f3000000:ohare/0.00020000:ATA/ide0/0.0 yaird: action: mkbdev, /dev/hda {sysname=hda } yaird: action: mkbdev, /dev/hda5 {sysname=hda/hda5 } yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/fs/mbcache.ko {optionList=-- } yaird: action: insmod, /lib/modules/2.6.18-rc6-powerpc/kernel/fs/ext2/ext2.ko {optionList=-- } yaird: action: mount, /mnt {device=/dev/hda5 fsType=ext2 isRoot=1 options=-o 'errors=remount-ro' } yaird: goal: template, postlude (/etc/yaird/Default.cfg:170) yaird: action: postlude, {} # -- Hans Ekbrand (http://sociologi.cjb.net) <[EMAIL PROTECTED]> A. Because it breaks the logical sequence of discussion Q. Why is top posting bad?
signature.asc
Description: Digital signature