On Fri, Mar 30, 2007 at 18:16:30 -0700, John Lee wrote:
> Thanks for your help, Florian.
>
> Actually the system dropped me to the ash because it cannot mount
> root. I tried it for quite a while before I used the old
> initrd.img-2.6.18-4-686.bak and I'm pretty sure all the modules are
> still t
Thanks for your help, Florian.
Actually the system dropped me to the ash because it cannot mount
root. I tried it for quite a while before I used the old
initrd.img-2.6.18-4-686.bak and I'm pretty sure all the modules are
still there (I did modprobe sd_mod). The linux-image is not updated
this ti
On Fri, Mar 30, 2007 at 14:13:12 -0400, Greg Folkert wrote:
> On Fri, 2007-03-30 at 20:05 +0200, Florian Kulzer wrote:
> > My guess is that some sound(-related) module from the old initrd does
> > not work properly with the new kernel. I would not spend time trying to
> > get sound to work until yo
On Fri, 2007-03-30 at 20:05 +0200, Florian Kulzer wrote:
> My guess is that some sound(-related) module from the old initrd does
> not work properly with the new kernel. I would not spend time trying to
> get sound to work until you can create a working initrd for your current
> kernel. It seems th
On Fri, Mar 30, 2007 at 02:28:20 +0800, John Lee wrote:
> first of all I cannot boot after update. traced and find out some
> strange problems:
>
> 1. sd_mod won't load. my system is running on SATA so mdadm will fail
> to assemble my (/home) md0. also the system will not be able to mount
> (/r
5 matches
Mail list logo
