Bug#337974: i2o controller probe failed err -110

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Maximilian Attems-3
tags 337974 moreinfo
severity 337974 important
stop

please retry as already requested against latest 2.6.14 in unstable
or against 2.6.15-rcX from experimental


--
maks


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Maximilian Attems-3
hello bill,

please keep the bug report cc'ed! :)

On Mon, 02 Jan 2006, Bill Gatliff wrote:

> Maks:
>
> Still stuck on this one:
>
> mercury:~# apt-get install linux-image-2.6.14-2-k7
> Reading package lists... Done
> Building dependency tree... Done
> Suggested packages:
>  linux-doc-2.6.14 linux-source-2.6.14 lilo
> Recommended packages:
>  libc6-i686
> The following NEW packages will be installed:
>  linux-image-2.6.14-2-k7
> 0 upgraded, 1 newly installed, 0 to remove and 551 not upgraded.
> Need to get 17.5MB of archives.
> After unpacking 51.9MB of additional disk space will be used.
> Get:1 http://mirror.mcs.anl.gov unstable/main linux-image-2.6.14-2-k7
> 2.6.14-7 [17.5MB]
> Fetched 17.5MB in 1m58s (148kB/s)
> Preconfiguring packages ...
> Selecting previously deselected package linux-image-2.6.14-2-k7.
> (Reading database ... 206599 files and directories currently installed.)
> Unpacking linux-image-2.6.14-2-k7 (from
> .../linux-image-2.6.14-2-k7_2.6.14-7_i386.deb) ...
> Setting up linux-image-2.6.14-2-k7 (2.6.14-7) ...
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitrd.yaird to build the ramdisk.
> yaird error: Could not read output for /sbin/lvdisplay -c (fatal)
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.14-2-k7 (--configure):
> subprocess post-installation script returned error exit status 9
> Errors were encountered while processing:
> linux-image-2.6.14-2-k7
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> Don't know how to make lvdisplay happy.
>
> b.g.

use initramfs-tools this shouldn't fail:
apt-get install initramfs-tools

add to /etc/kernel-img.conf
ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd

good luck ;)

--
maks


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Bill Gatliff
Max:

maximilian attems wrote:

>
>
>use initramfs-tools this shouldn't fail:
>apt-get install initramfs-tools
>
>add to /etc/kernel-img.conf
>ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
>
>good luck ;)
>
>  
>


I patched up my /etc/lvm/lvm.config and now the kernel package installs
clean.  It won't successfully boot, however.  It hangs with:

...
Waiting for /sys/block/sdb/dev
...
/sys/block/sdb/dev seems to be down
...


The /dev/sdb device is where my root filesystem is at.  Not quite sure
why the kernel can't find it...

Any ideas?


b.g.

--
Bill Gatliff
[hidden email]



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Bill Gatliff
In reply to this post by Maximilian Attems-3
Max:

maximilian attems wrote:

>use initramfs-tools this shouldn't fail:
>apt-get install initramfs-tools
>
>add to /etc/kernel-img.conf
>ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
>
>good luck ;)
>
>  
>

One other thing.  When I try to --purge the package, I get this:

# dpkg --purge linux-image-2.6.14-2-k7
(Reading database ... 206960 files and directories currently installed.)
Removing linux-image-2.6.14-2-k7 ...
Searching for GRUB installation directory ... found: /boot/grub .
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
Unless you used the optional flag in lilo,
 you may need to re-run lilo
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
Unless you used the optional flag in lilo,
 you may need to re-run lilo
Purging configuration files for linux-image-2.6.14-2-k7 ...
Searching for GRUB installation directory ... found: /boot/grub .

... and it just hangs there.


b.g.

--
Bill Gatliff
[hidden email]



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Sven Luther
On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote:

> Max:
>
> maximilian attems wrote:
>
> >use initramfs-tools this shouldn't fail:
> >apt-get install initramfs-tools
> >
> >add to /etc/kernel-img.conf
> >ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
> >
> >good luck ;)
> >
> >
> >
>
> One other thing.  When I try to --purge the package, I get this:
>
> # dpkg --purge linux-image-2.6.14-2-k7
> (Reading database ... 206960 files and directories currently installed.)
> Removing linux-image-2.6.14-2-k7 ...
> Searching for GRUB installation directory ... found: /boot/grub .
> The link /vmlinuz is a damaged link
> Removing symbolic link vmlinuz
> Unless you used the optional flag in lilo,
> you may need to re-run lilo
> The link /initrd.img is a damaged link
> Removing symbolic link initrd.img
> Unless you used the optional flag in lilo,
> you may need to re-run lilo
> Purging configuration files for linux-image-2.6.14-2-k7 ...
> Searching for GRUB installation directory ... found: /boot/grub .
>
> ... and it just hangs there.

Known grub bug, try playing with /etc/kernel/postrm.d/grub or whatever script
is responsible for this.

The workaround fix is for grub-update to do output to stderr and not stdout, i
believe, being exclusively ppc, i have not much knowledge or interest in grub.

Friendly,

Sven Luther



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Sven Luther
In reply to this post by Bill Gatliff
On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote:

> Max:
>
> maximilian attems wrote:
>
> >use initramfs-tools this shouldn't fail:
> >apt-get install initramfs-tools
> >
> >add to /etc/kernel-img.conf
> >ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd
> >
> >good luck ;)
> >
> >
> >
>
> One other thing.  When I try to --purge the package, I get this:
>
> # dpkg --purge linux-image-2.6.14-2-k7
> (Reading database ... 206960 files and directories currently installed.)
> Removing linux-image-2.6.14-2-k7 ...
> Searching for GRUB installation directory ... found: /boot/grub .
> The link /vmlinuz is a damaged link
> Removing symbolic link vmlinuz
> Unless you used the optional flag in lilo,
> you may need to re-run lilo
> The link /initrd.img is a damaged link
> Removing symbolic link initrd.img
> Unless you used the optional flag in lilo,
> you may need to re-run lilo
> Purging configuration files for linux-image-2.6.14-2-k7 ...
> Searching for GRUB installation directory ... found: /boot/grub .
>
> ... and it just hangs there.

Oh, and BTW, this is :

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344767

Friendly,

Sven Luther



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Bill Gatliff
Sven:

Sven Luther wrote:

>On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote:
>  
>
>Oh, and BTW, this is :
>
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344767
>
>  
>

Thanks for all the great feedback!

I noticed the BTS for the aforementioned ends with:

tags 344739 patch
tags 344767 patch

Does that mean that the grub in unstable fixes the issue?


b.g.

--
Bill Gatliff
[hidden email]




--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Sven Luther
On Thu, Jan 05, 2006 at 09:37:44AM -0600, Bill Gatliff wrote:
> I noticed the BTS for the aforementioned ends with:
>
> tags 344739 patch
> tags 344767 patch
>
> Does that mean that the grub in unstable fixes the issue?

No, this means someone provided a patch, which the grub maintainers could or
not use to fix the problem in an upload to unstable.

You could apply those patches to the grub package and rebuild it otoo.

Friendly,

Sven Luther



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#337974: i2o controller probe failed err -110

Bill Gatliff
Sven:

Sven Luther wrote:

>On Thu, Jan 05, 2006 at 09:37:44AM -0600, Bill Gatliff wrote:
>  
>
>>I noticed the BTS for the aforementioned ends with:
>>
>>tags 344739 patch
>>tags 344767 patch
>>
>>Does that mean that the grub in unstable fixes the issue?
>>    
>>
>
>No, this means someone provided a patch, which the grub maintainers could or
>not use to fix the problem in an upload to unstable.
>
>You could apply those patches to the grub package and rebuild it otoo.
>  
>

Nothing makes my palms sweat faster than tinkering with grub...  :(


b.g.

--
Bill Gatliff
[hidden email]



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]