Debian Bug report logs - #343048
linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Martin Stolle <mstoll@sus.mcgill.ca>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Date: Sun, 11 Dec 2005 23:50:33 -0500

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system



After the last update (-4 => -5), the system fails to boot.  There are
several error messages:  waiting for /sys/block.../hda to come up.  It
seems like the IDE module is loaded, but no drives whatsoever are found.
When booting with an alternate kernel, some ACPI stuff happens when the
ide driver gets started - maybe something with ACPI is wrong with the
latest version?

Martin


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.14-rc3-mst
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
ii  libc6-i686                    2.3.5-8.1  GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
* linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:
* linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true

Message #10 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Aapo Rista <aapo.bugs.debian@rista.net>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 08:07:21 +0200

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048


After upgrading linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14-5,
IBM Thinkpad X40 fails to boot. Last lines before the end of
initializing process are here:

---------------8<-------------8<-------------------
Uniform Multi-Platform E-IDE driver Revision 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 1 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 2 seconds for /sys/block/hda/dev to show up
[...]
Device /sys/block/hda/dev seems to be down
Debugging opportunity, type ^D to continue
/bin/dash: can't access tty: job control turned off
# <prompt here>
---------------8<-------------8<-------------------

Older kernel 2.6.11 boots fine.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=C, LC_CTYPE=fi_FI@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:
* linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true

Message #15 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Aapo Rista <aapo.bugs.debian@rista.net>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 07:20:03 +0100

On Mon, Dec 12, 2005 at 08:07:21AM +0200, Aapo Rista wrote:
> Package: linux-image-2.6.14-2-686
> Version: 2.6.14-5
> Followup-For: Bug #343048
> 
> 
> After upgrading linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14-5,
> IBM Thinkpad X40 fails to boot. Last lines before the end of
> initializing process are here:

To help pin down the cause, could you post the output of:

	uname -a
	dpkg -l yaird
	yaird -v -o crap.img 2.6.14-4-686
	yaird -v -o crap.img 2.6.14-5-686

(assuming these are the last kernel that boots and the first that works)

Thanks,
Erik

Message #20 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Håkan Lindqvist <lindqvist@netstar.se>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 09:33:04 +0100

I have the exact same problem, on a homebrew system with Intel ATA
controller.

linux-image-2.6.14-2-686 2.6.14-4 worked fine, 2.6.14-5 doesn't boot.


(It goes like this:)

...
Freeing unused kernel memory: 180k freed
mice: PS/2 mouse device common for all mice
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 1 seconds for /sys/block/hda/dev to show up
input: AT Translated Set 2 keyboard on ia0060/serio0
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 2 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 4 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 8 seconds for /sys/block/hda/dev to show up
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 16 seconds for /sys/block/hda/dev to show up
Device /sys/block/hda/dev seems to be down.
Debugging opportunity, type ^D to continue.
/bin/dash: can't access tty; job control turned off

If I press ^D, the same thing starts over, this time about hda2...



ii  yaird          0.0.12-1       Yet Another mkInitRD
ii  linux-image-2. 2.6.14-5       Linux kernel 2.6.14 image on



With 2.6.14-5:
#  yaird -v -o crap.img 2.6.14-2-686
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: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.k
o {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {
optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.
ko {optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko
{optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/fs/exportfs/exportfs.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/xfs/xfs.ko
{optionLis
t=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=xfs isRoot=1
options=-- }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}



After downgrading the linux-* packages to 2.6.14-4:
# yaird -v -o crap2.img 2.6.14-2-686
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: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko
{optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko
{optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko
{optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/fs/exportfs/exportfs.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/xfs/xfs.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=xfs isRoot=1
options=-- }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

Message #25 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Didrik Pinte <dpinte@itae.be>

To: 343048@bugs.debian.org

Subject: same problem here on my thinkpad R50

Date: Mon, 12 Dec 2005 09:38:34 +0100

[Message part 1 (text/plain, inline)]

upgrading from 2.6.14-2-686 4 to 5 breaks the system. Luckily, i had
kept an "old" 2.6.12 kernel ;-)

Here are the information you ask for more details :

ii  linux-image-2.6.14-2-686    2.6.14-5       Linux kernel 2.6.14 ...
ii  yaird                       0.0.12-1       Yet Another mkInitRD


geru-itea:/boot# yaird -v -o crap.img 2.6.14-2-686
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: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko
{optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko
{optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko
{optionList=-- }
yaird: action:
insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko
{optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=ext3 isRoot=1
options=-o 'errors=remount-ro,user_xattr' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}


Didrik

[signature.asc (application/pgp-signature, inline)]

Message #30 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Håkan Lindqvist <lindqvist@netstar.se>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 09:45:52 +0100

As the output looked the same I felt I had to check if the newly
installed 2.6.14-4 worked, and it didn't!

So, I dug out an old yaird version...

ii  yaird          0.0.11-12      Yet Another mkInitRD


Now it works (2.6.14-5)!

So, this appears to be either a yaird bug or a linux-image <-> yaird
interaction bug.


/Håkan

Message #35 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Ricardo Ferreira <debian-bugs@pasquinade.cjb.net>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 10:26:16 +0000

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048


I have the same problem. At first I thought it might be the way yaird was
generating the ram disk, so I tried using initramfs-tools instead. This did
not work (the error was about the same stated in other words in the boot
process). When I "dpkg -i" to the version that was previously working fine
(kernel version 2.6.14-4) I was surprised to find it had now the exact same
error. This probably means that it is not the kernel package's fault, but
something about the way the initrd is generated (although it is giving the
same problem with yaird and initramfs-tools). 

I repeat: The previously working fine kernel package
linux-image-2.6.14-2-686_2.6.14-4 is _not_ working now either after I rolled
back to it using "dpkg -i".

On boot the system does give me a console when hitting the error so it lets
me manually load the modules. "modprobe ide-generic" and "modprobe ide-disk"
allows the system to boot just fine.

Hope it helps.
Ricardo

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  initramfs-tools [linux-initra 0.42       tools for generating an initramfs
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
* linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
* linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:

Message #40 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Sumit Madan <s.madan@billiton.de>

To: 343048@bugs.debian.org

Subject: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 12:32:51 +0100

Hello Ricardo,

> On boot the system does give me a console when hitting the error so it lets
> me manually load the modules. "modprobe ide-generic" and "modprobe ide-disk"
> allows the system to boot just fine.

how do u have modprobed the modules?

after the errors i get /bin/dash where no modprobe exists and dont know
how to mount my root partition.

In /bin/dash there is no "ls". Then i have created a new directory
"root". The command "mount -t ext3 /dev/hda2 /root" doesnt work, it says
"filesystem type not found".

"/sbin/modprobe" doesnt work too because /bin/dash doesnt find modprobe.

Can u please explain how you modprobed the modules?

Thanks,
Sumit

Message #45 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Maximilian Attems <maks@sternwelten.at>

To: Ricardo Ferreira <debian-bugs@pasquinade.cjb.net>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 12:53:31 +0100

On Mon, Dec 12, 2005 at 10:26:16AM +0000, Ricardo Ferreira wrote:
> I have the same problem. At first I thought it might be the way yaird was
> generating the ram disk, so I tried using initramfs-tools instead. This did
> not work (the error was about the same stated in other words in the boot
> process). When I "dpkg -i" to the version that was previously working fine
> (kernel version 2.6.14-4) I was surprised to find it had now the exact same
> error. This probably means that it is not the kernel package's fault, but
> something about the way the initrd is generated (although it is giving the
> same problem with yaird and initramfs-tools). 
> 
> I repeat: The previously working fine kernel package
> linux-image-2.6.14-2-686_2.6.14-4 is _not_ working now either after I rolled
> back to it using "dpkg -i".
> 
> On boot the system does give me a console when hitting the error so it lets
> me manually load the modules. "modprobe ide-generic" and "modprobe ide-disk"
> allows the system to boot just fine.

the debian kernel package has an patch that prevents udev from properly
loading ide-generic.
that patch is on the way to be removed.

the ide-disk case needs to be looked into.
anyway as short time workaround add
-- /etc/mkinitramfs/modules
ide-generic
ide-disk
--

and dpkg-reconfigure your linux-image.

regards

--
maks

Message #50 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Ricardo Ferreira <ricardo@isr.ist.utl.pt>

To: Maximilian Attems <maks@sternwelten.at>

Cc: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 12:24:09 +0000

On Monday 12 December 2005 11:53, Maximilian Attems wrote:
> the debian kernel package has an patch that prevents udev from properly
> loading ide-generic.
> that patch is on the way to be removed.
>
> the ide-disk case needs to be looked into.
> anyway as short time workaround add
> -- /etc/mkinitramfs/modules
> ide-generic
> ide-disk
> --
>
> and dpkg-reconfigure your linux-image.
>
> regards
>
> --
> maks

Yup, that works, at least with initramfs-tools, will try going back to yaird 
later. Any comments on using one instead of the other?

Just to answer Sumit's question: if you install initramfs-tools (instead of 
yaird) and recreate the initial ram disk (with a "dpkg-reconfigure 
linux-image-2.6.14-2-686" for example) you'll have a busybox executable in 
the image (which includes modprobe). Much more usefull than what yaird 
provides. I'm not up to speed on the differences between the two initrd 
tools, this is just what I got out-of-the-box with apt-get install. 

Thanks for the quick response. 
Ricardo

Message #55 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Henrik Enberg <enberg@gmail.com>

To: 343048@bugs.debian.org

Subject: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 13:55:06 +0100

[Message part 1 (text/plain, inline)]

> Just to answer Sumit's question: if you install initramfs-tools (instead of
> yaird) and recreate the initial ram disk (with a "dpkg-reconfigure
> linux-image-2.6.14-2-686" for example) you'll have a busybox executable in
> the image (which includes modprobe). Much more usefull than what yaird
> provides. I'm not up to speed on the differences between the two initrd
> tools, this is just what I got out-of-the-box with apt-get install.

And if you don't have a bootable kernel on the system?  Are you SOL?

I used to have initramfs-tools on my box, anyone knows how I ended
up with this newfangled yaird?

[Message part 2 (text/html, inline)]

Message #60 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Sumit Madan <s.madan@billiton.de>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 14:12:38 +0100

Hello,

> Yup, that works, at least with initramfs-tools, will try going back to yaird 
> later. Any comments on using one instead of the other?
> 
> Just to answer Sumit's question: if you install initramfs-tools (instead of 
> yaird) and recreate the initial ram disk (with a "dpkg-reconfigure 
> linux-image-2.6.14-2-686" for example) you'll have a busybox executable in 
> the image (which includes modprobe). Much more usefull than what yaird 
> provides. I'm not up to speed on the differences between the two initrd 
> tools, this is just what I got out-of-the-box with apt-get install. 
> 
> Thanks for the quick response. 
> Ricardo

That was it.

Steps i done:
- boot with knoppix
- mount the root partition: mount /mnt/hda1
- mount the dev in the root partition: mount -o remount,dev /mnt/hda1
- chroot /mnt/hda1
- changed to /bin/bash
- mount /proc
- apt-get install initramfs-tools
- apt-get --purge remove yaird
- echo ide-generic >> /etc/mkinitramfs/modules
- echo ide-disk >> /etc/mkinitramfs/modules
- dpkg-reconfigure linux-image-2.6.14-2.686
- run lilo

Now i can boot with the kernel.

Thanks for the solutions.

Regards,
Sumit

Message #65 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Maximilian Attems <maks@sternwelten.at>

To: Ricardo Ferreira <ricardo@isr.ist.utl.pt>

Cc: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 16:31:34 +0100

On Mon, Dec 12, 2005 at 12:24:09PM +0000, Ricardo Ferreira wrote:
> 
> Yup, that works, at least with initramfs-tools, will try going back to yaird 
> later. Any comments on using one instead of the other?

they are very different.
initramfs-tools uses udev, bb and klibc and wants max hardware support
yaird like to reimplement work in perl and tries to produce minimal

for the use case of copying around your root,
pulling out your harddisc from one pc to another initramfs-tools
is your friend. the drivers need to generate uevents for udev loading.

yaird will boot your exotic archs easier, because no need to port klibc,
but you need working perl and modules outside of perl-base.
the minimal image has also advantages on broken bootloader size
assumptions. 

initramfs-tools is used by ubuntu's breezy release and
will feature dapper. the ease of hooks make it very extensible.

yaird has a pretty impressive doc section, anyway there is also a
wiki page documenting both:
-> http://wiki.debian.org/InitrdReplacementOptions

yaird is set as default for 2.6.14 to get good test coverage.
when reading this, take into account that i'm current initramfs-tools
maintainer and thus my preference is clear. :)

enjoy

-- 
maks

Message #70 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Michael Setzer <michael.setzer@celeborn.de>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Mon, 12 Dec 2005 17:09:26 +0100

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048

Hi,

after being knocked down with the same problem which left my system in
an unbootable state I wondered if it wasn't possible to bring the system
back to life without removing yaird. This is what I simply did:

- boot system with KNOPPIX
- mount the root partition
- remount the /dev into the root partition
- chroot into your root partition
- mount /proc
- mount /sys
- edit /etc/yaird/Default.cfg and add
	MODULE ide-generic
	MODULE ide-disk
  right after the "MODULE evdev" line
- dpkg-reconfigure linux-image-2.6.14-2-686
- umount /sys
- umount /proc
- leave chroot'ed partition and umount it

And right after a reboot your system is usable again. :)

Regards, Michael


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
* linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:

Message #75 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: Maximilian Attems <maks@sternwelten.at>, 343048@bugs.debian.org, Ricardo Ferreira <ricardo@isr.ist.utl.pt>

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: modules ide-generic and ide-disk not loading

Date: Mon, 12 Dec 2005 17:44:55 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 12 Dec 2005 16:31:34 +0100
Maximilian Attems <maks@sternwelten.at> wrote:

> On Mon, Dec 12, 2005 at 12:24:09PM +0000, Ricardo Ferreira wrote:
> > 
> > Yup, that works, at least with initramfs-tools, will try going back
> > to yaird later. Any comments on using one instead of the other?
> 
> they are very different.
> initramfs-tools uses udev, bb and klibc and wants max hardware support
> yaird like to reimplement work in perl and tries to produce minimal

The most interesting feature of yaird for me (being the yaird
maintainer) is not perl or minimal images, but that it tries hard to
spot problems in the image building proces and fails _before_ rebooting
in such cases.

Sadly, this current bugreport shows a situation not handled that way.


> for the use case of copying around your root,
> pulling out your harddisc from one pc to another initramfs-tools
> is your friend. the drivers need to generate uevents for udev loading.

My comparable scenario for yaird would then be a remote-managed server
that you cannot afford (distance, downtime or both) to not reboot with
a newer kernel on _same_ hardware setup.

When you switch hardware around, you are physically close the the box
and can (with a fallback kernel and a capable bootloader like GRUB)
roll back to the earlier working kernel+ramdisk.

> anyway there is also a wiki page documenting both:
> -> http://wiki.debian.org/InitrdReplacementOptions

Indeed. Let's both include our different arguments from this thread
into that page and point to that instead of repeating ourselves here :-)


 - 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)

iD8DBQFDnakHn7DbMsAkQLgRAhnLAJ99RC02BWfvczdy4pKm9u6fQeHYeACfdYFX
bM65b6LvVF2eL9gfHuULF+A=
=k16q
-----END PGP SIGNATURE-----

Message #80 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: Michael Setzer <michael.setzer@celeborn.de>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Mon, 12 Dec 2005 17:49:13 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 12 Dec 2005 17:09:26 +0100
Michael Setzer <michael.setzer@celeborn.de> wrote:

> after being knocked down with the same problem which left my system in
> an unbootable state I wondered if it wasn't possible to bring the
> system back to life without removing yaird. This is what I simply did:
> 
> - boot system with KNOPPIX
> - mount the root partition
> - remount the /dev into the root partition
> - chroot into your root partition
> - mount /proc
> - mount /sys
> - edit /etc/yaird/Default.cfg and add
> 	MODULE ide-generic
> 	MODULE ide-disk
>   right after the "MODULE evdev" line
> - dpkg-reconfigure linux-image-2.6.14-2-686
> - umount /sys
> - umount /proc
> - leave chroot'ed partition and umount it
> 
> And right after a reboot your system is usable again. :)

Thanks!

For the first half involving KNOPPIX one could also use GRUB (or
similarly capable bootloaders) and make sure to always keep an older
kernel version installed to use in case of upgrade problems like this.


Still, it is indeed a bug that should be fixed!


 - 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)

iD8DBQFDnaoJn7DbMsAkQLgRAtfHAJ9Qbw/5jU8CwtCYsaoAEW2dchGLVACfYF/h
2z1Bt25H/DvT64NyX179dAk=
=YV0L
-----END PGP SIGNATURE-----

Message #85 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Aapo Rista <aapo.bugs.debian@rista.net>

To: Erik van Konijnenburg <ekonijn@xs4all.nl>

Cc: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 20:47:30 +0200 (EET)

On Mon, 12 Dec 2005, Erik van Konijnenburg wrote:
> On Mon, Dec 12, 2005 at 08:07:21AM +0200, Aapo Rista wrote:
> > Package: linux-image-2.6.14-2-686
> > Version: 2.6.14-5
> > Followup-For: Bug #343048 
> > 
> > After upgrading linux-image-2.6.14-2-686 from 2.6.14-4 to 2.6.14-5,
> > IBM Thinkpad X40 fails to boot. Last lines before the end of
> > initializing process are here:

Kernel image 2.6.14-1-686 boots fine.
 
> To help pin down the cause, could you post the output of:
> 
> 	uname -a

Linux snadi 2.6.14-1-686 #1 Tue Nov 1 15:51:43 JST 2005 i686 GNU/Linux

> 	dpkg -l yaird

ii  yaird                 0.0.12-1              Yet Another mkInitRD

> 	yaird -v -o crap.img 2.6.14-4-686
> 	yaird -v -o crap.img 2.6.14-5-686
> (assuming these are the last kernel that boots and the first that works)

Those print nothing else than errors, but 
"yaird -v -o crap.img 2.6.14-1-686" prints: (boots fine)
---------------8<-----------------8<-------------------------------
yaird: goal: template, prologue (/etc/yaird/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/etc/yaird/Default.cfg:56)
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/video/console/bitblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/video/console/font.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/video/console/tileblit.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/video/console/fbcon.ko {optionList=-- }
yaird: goal: input, -- (/etc/yaird/Default.cfg:73) yaird: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}
---------------8<-----------------8<-------------------------------


And "yaird -v -o crap.img 2.6.14-2-686" prints: (does not boot)
---------------8<-----------------8<-------------------------------
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: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- 
}
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda2 {sysname=hda/hda2 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda2 fsType=ext3 isRoot=1 options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}
---------------8<-----------------8<-------------------------------

-- 
Aapo Rista

Message #90 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Aapo Rista <aapo.bugs.debian@rista.net>, 343048@bugs.debian.org, Cesare Leonardi <celeonar@tiscali.it>

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Mon, 12 Dec 2005 22:44:17 +0100

On Mon, Dec 12, 2005 at 08:47:30PM +0200, Aapo Rista wrote:
> On Mon, 12 Dec 2005, Erik van Konijnenburg wrote:
> > To help pin down the cause, could you post the output of:

> > 	yaird -v -o crap.img 2.6.14-4-686
> > 	yaird -v -o crap.img 2.6.14-5-686
> > (assuming these are the last kernel that boots and the first that works)

> yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
> yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
> yaird: action: insmod, /lib/modules/2.6.14-1-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
> yaird: hardware: completed pci0000:00/0000:00:1f.1/ide0/0.0

Hi Aapo, Cesare,

Thanks for your feedback.  There's a patch at the following location:

http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/

This should add ide-generic if you have piix controller without the need
to add it explicitly in the /etc/yaird/Default.cfg file.

Could you give it a try and let me know if it actually works?

Thanks,
Erik

Message #95 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Curt Howland <howland@priss.com>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: IDE failure boot message

Date: Mon, 12 Dec 2005 17:28:50 -0500

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048


I took a picture of the failure message that was not included in the
message opening this bug report:

Right after mice: and input: messages,

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33 MHz system bus speed for PIO modes; overri[out of
picture, normal message Curt-]
/bin/cat: /sys/block/hda/dev: No such file or directory
Waiting 2 seconds for /sys/block/hda/dev to show up

Above message repeats with doubling of seconds until 16 is reached, then
the system prints "Debug Opportunity ^D to continue" which seems to
be just a raw bash session.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:

Message #100 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)

Date: Mon, 12 Dec 2005 21:18:01 -0200

Erik van Konijnenburg wrote on Dec, 12:

[...]

> Thanks for your feedback.  There's a patch at the following location:
> 
> http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> 
> This should add ide-generic if you have piix controller without the need
> to add it explicitly in the /etc/yaird/Default.cfg file.
> 
> Could you give it a try and let me know if it actually works?

Apologies for the more than basic question: how do I apply the patch ?

Thanks for the patience,
Paulo

Message #105 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Arthur Marsh <arthur.marsh@internode.on.net>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: fails to boot

Date: Tue, 13 Dec 2005 10:54:34 +1030

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048


Same thing happens here. I also had problems trying to install loop-aes 
at the same time as upgrading from 2.6.14-4 to 2.6.14-5. The 
installation went ahead if I upgraded the kernel in aptitude first then 
the loop-aes stuff.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
ii  libc6-i686                    2.3.5-8.1  GNU C Library: Shared libraries [i

Message #110 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Aapo Rista <aapo.bugs.debian@rista.net>

To: Erik van Konijnenburg <ekonijn@xs4all.nl>

Cc: 343048@bugs.debian.org, Cesare Leonardi <celeonar@tiscali.it>

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Tue, 13 Dec 2005 06:32:08 +0200 (EET)

On Mon, 12 Dec 2005, Erik van Konijnenburg wrote:
> Thanks for your feedback.  There's a patch at the following location:
> 
> http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> 
> This should add ide-generic if you have piix controller without the need
> to add it explicitly in the /etc/yaird/Default.cfg file.
> 
> Could you give it a try and let me know if it actually works?

I already downgraded my yaird to version 0.0.11-12 which works fine.
If I have any time in the evening, I'll try the patch, if still necessary.

-- 
Aapo Rista

Message #115 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)

Date: Tue, 13 Dec 2005 07:23:41 +0100

On Mon, Dec 12, 2005 at 09:18:01PM -0200, Paulo Marcel Coelho Aragao wrote:
> Erik van Konijnenburg wrote on Dec, 12:
> > http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> > Could you give it a try and let me know if it actually works?
> 
> Apologies for the more than basic question: how do I apply the patch ?

None needed, my description was rather cryptic ...
Step by step:

**	Decide if you want to go ahead with this test.
	Only try this if you know how to recover from a non-booting kernel
	(& if I'm correct you've just done that)

**	Save the attached patch.

**	Make backup:
	$ cp /usr/lib/yaird/perl/Hardware.pm just-in-case.pm

**	Apply patch:
	$ sudo patch /usr/lib/yaird/perl/Hardware.pm < /dat/tmp/Hardware.pm.patch
	patching file /usr/lib/yaird/perl/Hardware.pm
	Hunk #1 succeeded at 216 (offset -18 lines).
	$ 

	(the offset is a normal warning in this case)

**	Comment out any work-arounds (MODULE ide-generic) you may have made
	in /etc/yaird/Default.cfg

	This is an important bit: you would not want to report success with
	the patch if actually your edit in Default.cfg is what makes the system boot.

**	Use the patched version to make a new initrd.img.
	A quick way to do this is 

	$ sudo apt-get install linux-image-2.6.14-2-686-smp

	but only if you don't actually have an SMP system.  This should
	leave your normal single-cpu kernel in place and install an smp
	kernel, with new initrd.img, next to it.

**	reboot into new kernel; report success; undo if you don't like the
	effect.


Regards,
Erik

Message #120 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (applying the patch)

Date: Tue, 13 Dec 2005 07:28:28 +0100

[Message part 1 (text/plain, inline)]

On Tue, Dec 13, 2005 at 07:23:41AM +0100, Erik van Konijnenburg wrote:
> **	Save the attached patch.

Oops, patch attached for real now.

[Hardware.pm.patch (text/plain, attachment)]

Message #125 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Thomas Maier <Thomas.Maier@uni-kassel.de>

To: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 09:44:22 +0100

Hi,

I also added

        MODULE          ide-generic
        MODULE          ide-disk

to /etc/yaird/Default.cfg and the kernel booted again.  Unfortunately,
DMA was disabled and I got several fat warnings about this while
booting.  Adding 

        MODULE          ide-core
        MODULE          piix
        MODULE          ide-generic
        MODULE          ide-disk

instead seems to solve the problem for me.  I had only little idea what
I had to do but saw 

ICH3M: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:pio

in dmesg and just tried loading modules until I saw that output.  It
seems piix was the critical one.  As it depends on ide-core and insmod
is used, I cowardly inserted ide-core before that one.  No idea whether
that was clever or stupid.  Also no idea why yaird fails to load piix
itself.  Everything worked fine until I upgraded

linux-image-2.6.14-2-686 (2.6.14-4) to 2.6.14-5
yaird (0.0.11-12) to 0.0.12-1

yesterday.

HTH, Thomas.

Message #130 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Sumit Madan <s.madan@billiton.de>

To: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Tue, 13 Dec 2005 10:41:09 +0100

[Message part 1 (text/plain, inline)]

Hello,

i cannot activate DMA. Its a bit slow here.

These modules are loaded:
##
lsmod |egrep "piix|generic|ide"
piix                   10436  0 [permanent]
generic                 4356  0 [permanent]
ide_disk               18784  7
ide_generic             1216  0 [permanent]
ide_core              131740  4 piix,generic,ide_disk,ide_generic
##

##
cat /etc/mkinitramfs/modules
ide-generic
ide-disk
##

##
hdparm /dev/hda

/dev/hda:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)
##

Any ideas?

-- 
Mit freundlichem Gruß

Sumit Madan - billiton internet services GmbH
Software-Entwicklung + Technik

direct phone: 0271/30386-32  direct mail: s.madan@billiton.de
Weitere Informationen finden Sie unter http://www.billiton.de

[signature.asc (application/pgp-signature, attachment)]

Message #135 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Michael Setzer <michael.setzer@celeborn.de>

To: Sumit Madan <s.madan@billiton.de>

Cc: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Tue, 13 Dec 2005 11:33:56 +0100

> hdparm /dev/hda
>
> /dev/hda:
>  setting using_dma to 1 (on)
>  HDIO_SET_DMA failed: Operation not permitted
>  using_dma    =  0 (off)
> ##
>
> Any ideas?

Saw that already yesterday. Seems to be an issue with the 
linux-image-2-6-14-2-686 (2.6.14-5).

Regards, Michael

Message #140 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: Thomas Maier <Thomas.Maier@uni-kassel.de>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 11:52:43 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 13 Dec 2005 09:44:22 +0100
Thomas Maier <Thomas.Maier@uni-kassel.de> wrote:

> It seems piix was the critical one.

Yes - that's why piix is mentioned in the title of this thread...

Sorry it wasn't clear to you and you had to play detective yourself to
get to same conclusion.


 - 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)

iD8DBQFDnqf7n7DbMsAkQLgRApyDAKCQvQb7B+FTqECoTNMj29fVA1nmvACeNEOd
1CosAIUmAPGOCocae5Ed4cA=
=TXoC
-----END PGP SIGNATURE-----

Message #145 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Thomas Maier <Thomas.Maier@uni-kassel.de>

To: Sumit Madan <s.madan@billiton.de>, Michael Setzer <michael.setzer@celeborn.de>

Cc: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Tue, 13 Dec 2005 12:01:47 +0100

> 
> > These modules are loaded:
> > ##
> > lsmod |egrep "piix|generic|ide"
> > piix                   10436  0 [permanent]
> > generic                 4356  0 [permanent]
> > ide_disk               18784  7
> > ide_generic             1216  0 [permanent]
> > ide_core              131740  4 piix,generic,ide_disk,ide_generic
> > ##
> > [...]
> > hdparm /dev/hda
> >
> > /dev/hda:
> >  setting using_dma to 1 (on)
> >  HDIO_SET_DMA failed: Operation not permitted
> >  using_dma    =  0 (off)
> > ##
> >
> > Any ideas?
> 
> Saw that already yesterday. Seems to be an issue with the 
> linux-image-2-6-14-2-686 (2.6.14-5).

I got that error, too.  For me, adding the piix module helped (see
above).  Even with linux-image-2-6-14-2-686 (2.6.14-5) which I have
booted right now.  But strangely, Sumit has it loaded.  Might it be that
"piix" has to be loaded earlier?  Maybe before "generic"?

Regards, Thomas

Message #150 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Stephen Gran <sgran@debian.org>

To: Sumit Madan <s.madan@billiton.de>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Tue, 13 Dec 2005 11:23:02 +0000

[Message part 1 (text/plain, inline)]

This one time, at band camp, Sumit Madan said:
> Hello,
> 
> i cannot activate DMA. Its a bit slow here.

ide-generic was loaded before piix, making your ide bus a bit sluggish.
Put piix above ide-generic in the modules file, rebuild your initrd, and
reboot.

Hope that helps,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

[signature.asc (application/pgp-signature, inline)]

Message #155 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Thomas Maier <Thomas.Maier@uni-kassel.de>

To: Jonas Smedegaard <dr@jones.dk>

Cc: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 12:27:09 +0100

Am Dienstag, den 13.12.2005, 11:52 +0100 schrieb Jonas Smedegaard:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tue, 13 Dec 2005 09:44:22 +0100
> Thomas Maier <Thomas.Maier@uni-kassel.de> wrote:
> 
> > It seems piix was the critical one.
> 
> Yes - that's why piix is mentioned in the title of this thread...

Yes, I added it to the title after finding out :).  Michael Setzer
wrote, that adding 
  MODULE ide-generic
  MODULE ide-disk
to /etc/yaird/Default.cfg makes it work.  I could boot with that, but
DMA was disabled.  I found out that manually adding piix reenables DMA
for me, so I meant "yes it works, no need to install initramfs-tools,
but piix is not loaded and that disables my DMA".

> Sorry it wasn't clear to you and you had to play detective yourself to
> get to same conclusion.

No need to excuse (but appreciated of course).  Any idea though why piix
is not loaded?  The patch from Erik seems to care for ide-generic only
(and assumes that piix is loaded I guess).

Thomas

Message #160 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Sven Luther <sven.luther@wanadoo.fr>

To: Thomas Maier <Thomas.Maier@uni-kassel.de>, 343048@bugs.debian.org

Cc: Jonas Smedegaard <dr@jones.dk>

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 12:36:58 +0100

On Tue, Dec 13, 2005 at 12:27:09PM +0100, Thomas Maier wrote:
> Am Dienstag, den 13.12.2005, 11:52 +0100 schrieb Jonas Smedegaard:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Tue, 13 Dec 2005 09:44:22 +0100
> > Thomas Maier <Thomas.Maier@uni-kassel.de> wrote:
> > 
> > > It seems piix was the critical one.
> > 
> > Yes - that's why piix is mentioned in the title of this thread...
> 
> Yes, I added it to the title after finding out :).  Michael Setzer
> wrote, that adding 
>   MODULE ide-generic
>   MODULE ide-disk
> to /etc/yaird/Default.cfg makes it work.  I could boot with that, but
> DMA was disabled.  I found out that manually adding piix reenables DMA
> for me, so I meant "yes it works, no need to install initramfs-tools,
> but piix is not loaded and that disables my DMA".

What about addign only piix, and not the others ? Will this work ? 

Friendly,

Sven Luther

Message #165 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Thomas Maier <Thomas.Maier@uni-kassel.de>

To: Sven Luther <sven.luther@wanadoo.fr>

Cc: 343048@bugs.debian.org, Jonas Smedegaard <dr@jones.dk>

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 12:53:20 +0100

Am Dienstag, den 13.12.2005, 12:36 +0100 schrieb Sven Luther:
> On Tue, Dec 13, 2005 at 12:27:09PM +0100, Thomas Maier wrote:
> > Am Dienstag, den 13.12.2005, 11:52 +0100 schrieb Jonas Smedegaard:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > On Tue, 13 Dec 2005 09:44:22 +0100
> > > Thomas Maier <Thomas.Maier@uni-kassel.de> wrote:
> > > 
> > > > It seems piix was the critical one.
> > > 
> > > Yes - that's why piix is mentioned in the title of this thread...
> > 
> > Yes, I added it to the title after finding out :).  Michael Setzer
> > wrote, that adding 
> >   MODULE ide-generic
> >   MODULE ide-disk
> > to /etc/yaird/Default.cfg makes it work.  I could boot with that, but
> > DMA was disabled.  I found out that manually adding piix reenables DMA
> > for me, so I meant "yes it works, no need to install initramfs-tools,
> > but piix is not loaded and that disables my DMA".
> 
> What about addign only piix, and not the others ? Will this work ? 

Unfortunately I do not have time to reboot and test that right now but
yaird output looks promising, thanks for the hint Sven:

# yaird -v -o /tmp/crap.img 2.6.14-2-686
yaird: goal: template, prologue (/usr/lib/yaird/conf/Default.cfg:52)
yaird: action: prologue,  {}
yaird: goal: module, fbcon (/usr/lib/yaird/conf/Default.cfg:56)
yaird: goal: input, -- (/usr/lib/yaird/conf/Default.cfg:73)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mouse/psmouse.ko {optionList=-- }
yaird: hardware: completed platform/i8042/serio1
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/usb/core/usbcore.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/usb/host/uhci-hcd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/usb/input/usbkbd.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/usb/input/usbhid.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/usb/input/yealink.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.1
yaird: goal: module, mousedev (/usr/lib/yaird/conf/Default.cfg:103)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko {optionList=-- }
yaird: goal: module, evdev (/usr/lib/yaird/conf/Default.cfg:104)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: module, piix (/usr/lib/yaird/conf/Default.cfg:107)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/piix.ko {optionList=-- }
yaird: goal: mountdir, / (/usr/lib/yaird/conf/Default.cfg:149)
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/pci/generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-generic.ko {optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko {optionList=-- }
yaird: hardware: completed pci0000:00/0000:00:1f.1/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.14-2-686/kernel/fs/reiserfs/reiserfs.ko {optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda5 fsType=reiserfs isRoot=1 options=-- }
yaird: goal: template, postlude (/usr/lib/yaird/conf/Default.cfg:162)
yaird: action: postlude,  {}

Message #170 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Michael Setzer <michael.setzer@celeborn.de>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools (but piix not loaded)

Date: Tue, 13 Dec 2005 13:56:10 +0100

> > > Yes, I added it to the title after finding out :).  Michael Setzer
> > > wrote, that adding
> > >   MODULE ide-generic
> > >   MODULE ide-disk
> > > to /etc/yaird/Default.cfg makes it work.  I could boot with that, but
> > > DMA was disabled.  I found out that manually adding piix reenables DMA
> > > for me, so I meant "yes it works, no need to install initramfs-tools,
> > > but piix is not loaded and that disables my DMA".
> >
> > What about addign only piix, and not the others ? Will this work ?
>
> Unfortunately I do not have time to reboot and test that right now but
> yaird output looks promising, thanks for the hint Sven:

Now I gave it another try and added

	MODULE piix
	MODULE ide-generic
	MODULE ide-disk

to the /etc/yaird/Default.cfg. After reconfiguring the 
linux-image-2.6.14-2-686 and rebooting I have DMA reenabled.

Using only "MODULE piix" in the /etc/yaird/Default.cfg results in an 
unbootable system. Too bad that this machine is not accessible to me right 
now, so my testing time is over for now. :)

Regards, Michael

Message #175 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (patch results)

Date: Tue, 13 Dec 2005 11:57:09 -0200

Erik van Konijnenburg wrote on Dec, 13:

[...]

> > > http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> > > Could you give it a try and let me know if it actually works?

[...]

> **	Decide if you want to go ahead with this test.
> 	Only try this if you know how to recover from a non-booting kernel
> 	(& if I'm correct you've just done that)

It's mine and everybody else's interest to have this solved.

> **	Save the attached patch.

Had already downloaded it from the URL you gave.

> **	Make backup:
> 	$ cp /usr/lib/yaird/perl/Hardware.pm just-in-case.pm

> **	Apply patch:
> 	$ sudo patch /usr/lib/yaird/perl/Hardware.pm < /dat/tmp/Hardware.pm.patch
> 	patching file /usr/lib/yaird/perl/Hardware.pm
> 	Hunk #1 succeeded at 216 (offset -18 lines).
> 	$ 
> 
> 	(the offset is a normal warning in this case)

> **	Comment out any work-arounds (MODULE ide-generic) you may have made
> 	in /etc/yaird/Default.cfg
> 	This is an important bit: you would not want to report success with
> 	the patch if actually your edit in Default.cfg is what makes the system boot.

> **	Use the patched version to make a new initrd.img.
> 	A quick way to do this is $ sudo apt-get install 
> 	linux-image-2.6.14-2-686-smp
> 	but only if you don't actually have an SMP system.  This should
> 	leave your normal single-cpu kernel in place and install an smp
> 	kernel, with new initrd.img, next to it.

It would take a while to download, so I did:

sudo yaird -v -o /boot/initrd.img-2.6.14-2-686.patched | tee yaird.log

and edited grub initrd at boot time.

> **	reboot into new kernel; report success; undo if you don't like the
> 	effect.

Bingo ! Flawless boot: all IDE devices recognized.

Thanks a lot for the speedy patch !

Paulo

Message #180 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (patch results, amended)

Date: Tue, 13 Dec 2005 12:48:41 -0200

Paulo Marcel Coelho Aragao wrote on Dec, 13:

[...]

> > > > http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> > > > Could you give it a try and let me know if it actually works?

[...]

> Bingo ! Flawless boot: all IDE devices recognized.

In haste, I didn't notice: DMA is turned off for all IDE devices.

I followed the workaround suggested in another thread: explicitly include pixx 
in Default.cfg.

Paulo

Message #185 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Sumit Madan <s.madan@billiton.de>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: no need to install initramfs-tools

Date: Tue, 13 Dec 2005 17:30:48 +0100

[Message part 1 (text/plain, inline)]

Stephen Gran wrote:

>This one time, at band camp, Sumit Madan said:
>  
>
>>Hello,
>>
>>i cannot activate DMA. Its a bit slow here.
>>    
>>
>
>ide-generic was loaded before piix, making your ide bus a bit sluggish.
>Put piix above ide-generic in the modules file, rebuild your initrd, and
>reboot.
>
>Hope that helps,
>  
>
Thanks.. Now i have DMA too.

I have another question. When a new kernel-image comes out, should i
have to edit the /etc/mkinitramfs/modules and remove all modules from
the file.
I can imagine that there will be no problems when the file has module
entries. But whats the best way?

Regards,
Sumit

[signature.asc (application/pgp-signature, attachment)]

Message #190 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Max Franco <maxter@email.it>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-686: same proble, kernel fails to load ide drive.. in my case the drive is under /sys/block/hdb/dev

Date: Tue, 13 Dec 2005 17:44:06 +0100

Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Followup-For: Bug #343048

same problem reported in the first report for this bug.. i only submit
my data hoping this may be useful for the manteiner...

many thanks

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-686 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.14-2-686/preinst/already-running-this-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-686/postinst/create-kimage-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/initrd-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/bootloader-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/old-system-map-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/failed-to-move-modules-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/depmod-error-initrd-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/old-dir-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/elilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/would-invalidate-boot-loader-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/overwriting-modules-2.6.14-2-686: true
  linux-image-2.6.14-2-686/preinst/abort-install-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-686/preinst/lilo-initrd-2.6.14-2-686: true
  linux-image-2.6.14-2-686/prerm/removing-running-kernel-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/depmod-error-2.6.14-2-686: false
  linux-image-2.6.14-2-686/postinst/bootloader-test-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/postinst/old-initrd-link-2.6.14-2-686: true
  linux-image-2.6.14-2-686/postinst/bootloader-error-2.6.14-2-686:
  linux-image-2.6.14-2-686/preinst/abort-overwrite-2.6.14-2-686:

Message #195 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Scott James Williamson <scott@sjwilliamson.ca>

To: 343048@bugs.debian.org

Subject: linux-image-2.6.14-2-k7: same proble, kernel fails to load ide drive.. in my case the drive is under /sys/block/hdb/dev

Date: Tue, 13 Dec 2005 13:44:34 -0500

FYI:

if you use a nvidia nforce 2 based motherboard, to get DMA on your
drives, add the following "MODULE amd74xx" after evdev and before
ide-generic to the /etc/yaird/Default.cfg file:

   MODULE          evdev

   MODULE          amd74xx

   MODULE          ide-generic
   MODULE          ide-disk

then run the command "dpkg-reconfig linux-image-2.6.14-2-k7"

-- 
Scott James Williamson <scott@sjwilliamson.ca>

Message #200 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Mathieu Laurent <mathieu.laurent@messenjer.be>

To: 343048@bugs.debian.org

Subject: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Date: Tue, 13 Dec 2005 19:51:56 +0100

I had the same problem, I try this patch and it works

http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/

> **    Use the patched version to make a new initrd.img.
>     A quick way to do this is $ sudo apt-get install
>     linux-image-2.6.14-2-686-smp
>     but only if you don't actually have an SMP system.  This should
>     leave your normal single-cpu kernel in place and install an smp
>     kernel, with new initrd.img, next to it.

apt-get install --reinstall linux-image-2.6.14-2-686-smp

Regards

Mathieu

Message #205 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (patch results, amended)

Date: Tue, 13 Dec 2005 19:56:23 +0100

On Tue, Dec 13, 2005 at 12:48:41PM -0200, Paulo Marcel Coelho Aragao wrote:
> Paulo Marcel Coelho Aragao wrote on Dec, 13:
> > > > > http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> > > > > Could you give it a try and let me know if it actually works?
> > Bingo ! Flawless boot: all IDE devices recognized.
> 
> In haste, I didn't notice: DMA is turned off for all IDE devices.
> 
> I followed the workaround suggested in another thread: explicitly include pixx 
> in Default.cfg.

That's odd.  The patch is designed to load piix before ide-generic,
so that you get working DMA.

Perhaps in your test you did not remove 'MODULE ide-generic' from your
/etc/yaird/Default.cfg, so that it gets loaded too early?

If that's not the case, could you post your config files plus
the output of yaird -d, so that I can debug further?

Thanks,
Erik

Message #210 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Erik van Konijnenburg <ekonijn@xs4all.nl>

To: Scott James Williamson <scott@sjwilliamson.ca>, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-k7: same proble, kernel fails to load ide drive.. in my case the drive is under /sys/block/hdb/dev

Date: Tue, 13 Dec 2005 20:52:20 +0100

On Tue, Dec 13, 2005 at 01:44:34PM -0500, Scott James Williamson wrote:
> FYI:
> 
> if you use a nvidia nforce 2 based motherboard, to get DMA on your
> drives, add the following "MODULE amd74xx" after evdev and before
> ide-generic to the /etc/yaird/Default.cfg file:
> 
>    MODULE          evdev
> 
>    MODULE          amd74xx
> 
>    MODULE          ide-generic
>    MODULE          ide-disk

Thanks, this is new information.

There have been piix users that report non-boot and no DMA with
the latest yaird version, but you are the first to report this
for an amd74xx motherboard.

Just to avoid misunderstandings: did you add the ide-generic
to repair a non-booting system, or just by way of prevention?

If the amd74xx also fails to boot without ide-generic, I'll need
to prepare a modified yaird patch.

Regards,
Erik

Message #215 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Paulo Marcel Coelho Aragao <pmcaragao-ag@yahoo.com>

To: debian-kernel@lists.debian.org, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize (SOLVED)

Date: Tue, 13 Dec 2005 18:21:42 -0200

Erik van Konijnenburg wrote on Dec, 13:

[...]

> > > > > > http://arch.debian.org/arch/yaird/ekonijn@xs4all.nl--debian/yaird/yaird--devo/yaird--devo--0.1/patch-131/
> > > > > > Could you give it a try and let me know if it actually works?
> > > Bingo ! Flawless boot: all IDE devices recognized.
> > 
> > In haste, I didn't notice: DMA is turned off for all IDE devices.

[...]

> That's odd.  The patch is designed to load piix before ide-generic,
> so that you get working DMA.

> Perhaps in your test you did not remove 'MODULE ide-generic' from your
> /etc/yaird/Default.cfg, so that it gets loaded too early?

My sincerest apologies: DMA is indeed enabled. I just don't know what I did 
wrong in my previous attempt. I recreated now the initrd image with the 
default config file and the IDE devices are recognized and DMA is enabled for 
all of them.

[...]

Thanks again for the speedy patch !
Paulo

Message #220 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Cesare Leonardi <celeonar@tiscali.it>

To: Erik van Konijnenburg <ekonijn@xs4all.nl>, aapo.bugs.debian@rista.net, 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: ide fails to initialize, additional information

Date: Tue, 13 Dec 2005 22:20:44 +0100

Thanks to the clear Erik's step by step guide, i've applayed his patch 
and here is my results.

Erik van Konijnenburg wrote:
> On Tue, Dec 13, 2005 at 12:52:34AM +0100, Cesare Leonardi wrote:
> Step by step:
[...]
> **	Comment out any work-arounds (MODULE ide-generic) you may have made
> 	in /etc/yaird/Default.cfg
> 
> 	This is an important bit: you would not want to report success with
> 	the patch if actually your edit in Default.cfg is what makes the system boot.
> 

Never touched /etc/yaird/Default.cfg.

> 
> **	reboot into new kernel; report success; undo if you don't like the
> 	effect.

Your patch seems to have resolved the problem: now i'm writing with the 
smp kernel (i like your trick of using smp kernel for testing purposes) 
and dmesg report no errors regarding disk/filesystem.
Since i have read other posts regarding problem with DMA (that seems 
caused by some hand-made configuration), i have also tested that in my 
system it is regularly enabled:
# hdparm -d /dev/hda
/dev/hda:
 using_dma    =  1 (on)
#

Thank you very much Erik.

Cesare.

Message #225 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Curt Howland <Howland@priss.com>

To: 343048@bugs.debian.org

Subject: Additional information

Date: Wed, 14 Dec 2005 11:04:18 -0500

Suggest merge with #343042, it seems this is happening to lots of 
people.

I attempted the fix mentioned in #343042, adding MODULE ide-generic 
and MODULE ide-disk to /etc/haird/Default.cfg, and running yaird -v 
-o /boot/initrd.img-2.6.14-2-686 2.6.14-2-686, but the same error 
occured. I have not yet downgraded yaird.

Curt-

-- 
September 11th, 2001
The proudest day for gun control and central 
planning advocates in American history

Message #230 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Max Vozeler <max@decl.org>

To: 343048@bugs.debian.org

Subject: Re: Bug#343048: linux-image-2.6.14-2-686: fails to boot

Date: Thu, 15 Dec 2005 14:49:13 +0100

On Tue, Dec 13, 2005 at 10:54:34AM +1030, Arthur Marsh wrote:
> Package: linux-image-2.6.14-2-686
> Version: 2.6.14-5
> Followup-For: Bug #343048
> 
> Same thing happens here. I also had problems trying to install
> loop-aes at the same time as upgrading from 2.6.14-4 to 2.6.14-5. The
> installation went ahead if I upgraded the kernel in aptitude first
> then the loop-aes stuff.

Regarding the loop-aes problem Arthur described: We worked together
to find out what the problem was and it turned out to have been a
transient error because of a previous failure to configure linux-image,
so not directly relevant for this bug.

cheers,
Max

Message #235 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Michael Setzer <michael.setzer@celeborn.de>

To: Debian Bug Tracking System <343048@bugs.debian.org>

Subject: linux-image-2.6.14-2-k7: happens on 2.6.14-2-k7 too

Date: Thu, 15 Dec 2005 21:24:46 +0100

Package: linux-image-2.6.14-2-k7
Version: 2.6.14-5
Followup-For: Bug #343048

Hi,

just to add some more (maybe helpful) information:

I just upgraded the kernel on my AMD machine and had the same problems.
Adding the modules amd74xx, ide-generic and ide-disk to the
/etc/yaird/Default.cfg and rebuilding the kernel fixed the problem. My
machine is now bootable again (I'm writing this additional information
with it right now ;).

Regards,

Michael


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-k7
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-k7 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-k7 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.14-2-k7/preinst/elilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/lilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/abort-overwrite-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/bootloader-error-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/overwriting-modules-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/old-system-map-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/depmod-error-initrd-2.6.14-2-k7: false
  linux-image-2.6.14-2-k7/prerm/removing-running-kernel-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/initrd-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-k7/postinst/depmod-error-2.6.14-2-k7: false
  linux-image-2.6.14-2-k7/preinst/failed-to-move-modules-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/old-dir-initrd-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/old-initrd-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/abort-install-2.6.14-2-k7:
* linux-image-2.6.14-2-k7/preinst/already-running-this-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/bootloader-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/bootloader-test-error-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/kimage-is-a-directory:
  linux-image-2.6.14-2-k7/prerm/would-invalidate-boot-loader-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/create-kimage-link-2.6.14-2-k7: true

Message #240 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Dominique Dumont <domi.dumont@free.fr>

To: 343048@bugs.debian.org, ekonijn@xs4all.nl

Subject: Re: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Date: Sat, 17 Dec 2005 11:16:30 +0100

Erik van Konijnenburg <ekonijn@xs4all.nl> writes:
> 
> Just to avoid misunderstandings: did you add the ide-generic
> to repair a non-booting system, or just by way of prevention?
> 
> If the amd74xx also fails to boot without ide-generic, I'll need
> to prepare a modified yaird patch.

Here's what I've tried with my nforce2 board (a7xn8x deluxe) with
/etc/yaird/Default.cfg and linux-image-2.6.14-2-k7 v 2.6.14-5:

ide-generic + ide_disk             -> boot, no DMA
ide-generic + ide_disk + amd74xx   -> boot, no DMA

amd74xx +  ide-generic + ide_disk  -> boot,    DMA :-)
amd74xx +                ide_disk  -> boot failure

HTH

Message #245 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Echo Nolan <hellish@comcast.net>

To: 343048@bugs.debian.org

Subject: yaird patch allowed booting but not DMA

Date: Sun, 18 Dec 2005 21:05:39 -0800

Hello all,
I've patched yaird, which gets me to booting, but no DMA.
/etc/yaird/Default.cfg is as installed.
chef-brian:/home/hellish# hdparm -d1 /dev/hda

/dev/hda:
 setting using_dma to 1 (on)
  HDIO_SET_DMA failed: Operation not permitted
   using_dma    =  0 (off)
This is the output of yaird -v:
chef-brian:/home/hellish# yaird -v --output=crap.img
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: hardware: completed platform/i8042/serio1
yaird: goal: module, mousedev (/etc/yaird/Default.cfg:103)
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/input/mousedev.ko
{optionList=-- }
yaird: goal: module, evdev (/etc/yaird/Default.cfg:104)
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/input/evdev.ko {optionList=-- }
yaird: goal: mountdir, / (/etc/yaird/Default.cfg:143)
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-core.ko {optionList=--
}
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-generic.ko
{optionList=-- }
yaird: action: insmod,
/lib/modules/2.6.14-2-686/kernel/drivers/ide/ide-disk.ko {optionList=--
}
yaird: hardware: completed ide0/0.0
yaird: action: mkbdev, /dev/hda {sysname=hda }
yaird: action: mkbdev, /dev/hda3 {sysname=hda/hda3 }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/mbcache.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/jbd/jbd.ko
{optionList=-- }
yaird: action: insmod, /lib/modules/2.6.14-2-686/kernel/fs/ext3/ext3.ko
{optionList=-- }
yaird: action: mount, /mnt {device=/dev/hda3 fsType=ext3 isRoot=1
options=-o 'errors=remount-ro' }
yaird: goal: template, postlude (/etc/yaird/Default.cfg:156)
yaird: action: postlude,  {}

TIA,
Echo Nolan

Message #250 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Claudio Saavedra <claudio@codemonkey.cl>

To: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Date: Thu, 22 Dec 2005 11:54:39 +0100

Hi,

Updated today to linux-image-2.6.14-2-686 2.6.14-6 and it booted without
problems. DMA working and everything aparently back to normality.

Claudio

-- 
Claudio Saavedra <claudio@codemonkey.cl>

Message #255 received at 343048@bugs.debian.org (full text, mbox, reply):

From: Michael Setzer <michael.setzer@celeborn.de>

To: 343048@bugs.debian.org

Subject: Re: linux-image-2.6.14-2-686: ide fails to initialize, fails to boot

Date: Tue, 27 Dec 2005 10:36:21 +0100

> Updated today to linux-image-2.6.14-2-686 2.6.14-6 and it booted without
> problems. DMA working and everything aparently back to normality.

Same over here. Upgrading the Kernel without a modified /etc/yaird/Default.cfg 
leads to a properly running system.

Even after the latest yaird update (0.0.12-2) and another "dpkg-reconfigure 
linux-image-2.6.14-2-686" everything runs fine.

Thanks a lot!

Regards, Michael

Message #260 received at 343048-done@bugs.debian.org (full text, mbox, reply):

From: Jonas Smedegaard <dr@jones.dk>

To: 343048-done@bugs.debian.org

Subject: Bug fixed with the upload of 0.0.12-2

Date: Wed, 28 Dec 2005 13:43:54 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Version: 0.0.12-2

As subject says, this bug was fixed with the upload of 0.0.12-2

 - 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)

iD8DBQFDsoiKn7DbMsAkQLgRAje0AJ9UyfgKE8pVO/EPfT6zDY70g0bRzACfRbU7
FwCcKgy9fcxZQJb+uIUYoZE=
=HZh1
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.