Bug#341559: yaird: fails to create initrd
Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): subprocess post-installation script returned error exit status 2 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages yaird depends on: ii cpio 2.6-3 GNU cpio -- a program to manage ar ii dash 0.5.2-7 The Debian Almquist Shell ii libc62.3.5-4 GNU C Library: Shared libraries an ii libhtml-template-perl2.7-1 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.7-4 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote: Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Hi Hans, ... Do you happen to know exactly which driver is needed for this device ? Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Could you send us a : find /sys/devices/pci:00/:00:10.0/0.f300:ohare output, so we know this ? I suppose this is just that yaird doesn't know about the intermediary nodes between the actual block driver and the hardware it knows of, so will be rather easy to fix. Erik, Jonas, what about a i know what i do option, which would allow to ignore this kind of in-between nodes, provided that the final block driver is known ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote: Package: yaird Version: 0.0.11-12 Severity: important This is a Old-world IDE-based Macintosh Performa 5400, running unstable on a 2.6.8-12 kernel. Hi Hans, ... Do you happen to know exactly which driver is needed for this device ? Do you mean which module to drive this IDE harddisk? Unpacking linux-image-2.6-powerpc (from .../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ... Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Could you send us a : find /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00016000:via-cuda/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0006:nvram/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3 /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00015000:swim3/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00014000:awacs/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013000:ch-b/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/devspec /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/power/state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/0.00013020:ch-a/detach_state /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.00013000:escc/devspec
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare yaird error: unrecognised device: /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA Failed to create initrd image. dpkg: error processing linux-image-2.6.14-2-powerpc (--configure): -- Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED] Q. What is that strange attachment in this mail? A. My digital signature, see www.gnupg.org for info on how you could use it to ensure that this mail is from me and has not been altered on the way to you. signature.asc Description: Digital signature
Bug#341559: yaird: fails to create initrd
clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd (you might need to comment that as soon as you want to test yaird). Other suitable ramdisk generating tools : /usr/sbin/mkinitramfs. so it's installed ;) -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 12:37:23PM +0100, Hans Ekbrand wrote:
Package: yaird
Version: 0.0.11-12
Severity: important
This is a Old-world IDE-based Macintosh Performa 5400, running unstable
on a 2.6.8-12 kernel.
Hi Hans, ...
Do you happen to know exactly which driver is needed for this device ?
Do you mean which module to drive this IDE harddisk?
Unpacking linux-image-2.6-powerpc (from
.../linux-image-2.6-powerpc_2.6.14-4_powerpc.deb) ...
Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ...
Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
yaird error: unrecognised device:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
yaird error: unrecognised device:
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
Could you send us a :
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of the
two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. -- 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
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
Could you send us a :
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
OK, I will try that but does not have enough time for the moment.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
use it to ensure that this mail is from me and has not been
altered on the way to you.
signature.asc
Description: Digital signature
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:16:04PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. -- maks ps one last time cc 341559, sorry for the noise jonas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjw3Gn7DbMsAkQLgRAqnIAJ9krhuSG/SsQGqIcPXKdJ45NHye1wCffZ55 Y8zhxM+Tu5VAbLDtnfXTekM= =87uc -END PGP SIGNATURE-
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:27:35PM +0100, Maximilian Attems wrote: On Thu, Dec 01, 2005 at 03:16:04PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 02:08:14PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:41:01PM +0100, Maximilian Attems wrote: clone 341559 -1 reassign -1 initramfs-tools stop On Thu, Dec 01, 2005 at 01:33:10PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:51:48PM +0100, maximilian attems wrote: just saw your bugreport could you try latest initramfs-tools from unstable too? would be cool to get it tested, and report probable boot error (or success)? Exactly the same error: # dpkg --configure -a Setting up linux-image-2.6.14-2-powerpc (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. well you are still using yaird. OK. I thought installing initramfs-tools would suffice, I didn't know that it was an alternativ to yaird, nor that it would not be used by default. please try temporarly adding to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd OK. Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! Huh ? You don't want people to test initramfs-tools in MODULES=dep mode ? svenl stop givine bad advices to users. Huh again ? #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Who cares, his stuff worked in initramfs-tools with MODULES=most, but was it tested in MODULES=dep ? Friendly, Sven Luther -- maks ps one last time cc 341559, sorry for the noise jonas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail. Aucun virus connu a ce jour par nos services n'a ete detecte. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? defaults are set out of *dam-good-reasons*. :) if you wana play around with them do it on your dev machine. if svenl is serious about his little pet option than he would have followed up to his bug report long since 5th november. it's none of the business of this bug reporter. it seems like that very nice old world mac had np booting an full featured initramfs and reporter wanted to get his machine up quickly. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 16:37:30 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: Why not? Is that option somehow unsupported? defaults are set out of *dam-good-reasons*. :) Thanks for the clarification! - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjyIqn7DbMsAkQLgRAqz4AJ9++7Z44MEN02bPaCZ8jv+YvZhhHwCgk2Dj BjVns+DrgbevigESZiJnEMs= =R+Un -END PGP SIGNATURE-
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 04:37:30PM +0100, Maximilian Attems wrote: On Thu, Dec 01, 2005 at 03:50:46PM +0100, Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Dec 2005 15:27:35 +0100 Maximilian Attems [EMAIL PROTECTED] wrote: Now it worked! the initrd was created and the boot successful. Can you try the same thing also using MODULES=dep (or whatever that option is called) in /etc/mkinitramfs/mkinitramfs.conf please ? no please dont!! svenl stop givine bad advices to users. #341559 is an yaird bug, the initramfs one was cloned as #341567 and is fixede. Why not? Is that option somehow unsupported? We have here a chance to test initramfs-tools on a tricky machine - and Sven suggests to then extend the test to not only the default setting but also the more compact one. It is no secret that Sven and I is fond of yaird, but this is no competition: Do you prefer discovering possible bugs closer to release? defaults are set out of *dam-good-reasons*. :) if you wana play around with them do it on your dev machine. if svenl is serious about his little pet option than he would have followed up to his bug report long since 5th november. it's none of the business of this bug reporter. Ok, since we go this way, i notice that you didn't even bother to post a single post to said bug report, and that when i used my time to test initramfs-tools on the pegasos, you ended up being uncivile to me (again) on irc, so really, i am a bit sick of your behavior. it seems like that very nice old world mac had np booting an full featured initramfs and reporter wanted to get his machine up quickly. So, what does it cost asking that he goes the full way and tries out MODULES=dep, or are you afraid it will be broken, and will need to coerce someone else to fix the bug for you ? Like you not even bothering to look at how to build klibc with l-k-h as it should, and me having to do it for you ? Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
[...]
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Attached is a patch that made it match the two problematic lines:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
With the patch applied, the initrd was successfully created, and the
kernel booted without any problems.
--
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
78a79,81
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Another Apple bus; harmless
}
81a85,87
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA$!) {
# Apple IDE bus; harmless
}
signature.asc
Description: Digital signature
Bug#341559: yaird: fails to create initrd
tags 341559 + patch
thanks
On Thu, Dec 01, 2005 at 11:25:34PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote:
On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote:
On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote:
[...]
find /sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA/ide0/0.0/block
This is probably similar to the problem we had :
/sys/devices/pci0001:10/0001:10:17.0/0.8000:mac-io/0.0002:ata-3/ide1
so instead of ignoring 0.8000:mac-io and 0.0002:ata-3, you need to
ignore 0.f300:ohare and 0.0002:ATA.
So, in /usr/lib/yaird/perl/Hardware.pm, at line 81, you need to copy one of
the two
above lines :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:mac-io$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ata-\d+$!) {
# Apple IDE bus; harmless
}
for your case, maybe something like :
if ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ohare$!) {
# Apple bus; harmless
}
elsif ($abspath =~ m!/[a-f\d]+\.[a-f\d]+:ATA\d+$!) {
# Apple IDE bus; harmless
}
but i am no perl expert, and may have gotten the exact magic wrong.
Attached is a patch that made it match the two problematic lines:
/sys/devices/pci:00/:00:10.0/0.f300:ohare
/sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA
With the patch applied, the initrd was successfully created, and the
kernel booted without any problems.
Hehe, thanks, i guess a diff -u is prefered, but i am sure Erik and Jonas will
be able to adapt.
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341559: yaird: fails to create initrd
On Thu, Dec 01, 2005 at 11:25:34PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 01:52:34PM +0100, Sven Luther wrote: On Thu, Dec 01, 2005 at 01:10:39PM +0100, Hans Ekbrand wrote: On Thu, Dec 01, 2005 at 12:54:34PM +0100, Sven Luther wrote: Attached is a patch that made it match the two problematic lines: /sys/devices/pci:00/:00:10.0/0.f300:ohare /sys/devices/pci:00/:00:10.0/0.f300:ohare/0.0002:ATA With the patch applied, the initrd was successfully created, and the kernel booted without any problems. Thanks, applied to development repository, revno 14. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
