On Sun, Mar 18, 2007 at 09:04:11PM -0400, Greg Folkert wrote:
> On Sun, 2007-03-18 at 13:11 -0400, Rick Pasotto wrote:
> >
> > /boot was full! (too many previous kernels still lying around).
> > Evidently apt-get only wrote *part* of the initrd file because the file
> > system filled up but I saw
On Sun, 2007-03-18 at 13:11 -0400, Rick Pasotto wrote:
> On Sun, Mar 18, 2007 at 06:38:13PM +0200, Vasil Benov wrote:
> > Hi,
> >
> > I have experienced the same problem. If you have a SATA harddrive
> > you should specify root=/dev/sda1(or whatever device number and partition
> > you boot from)
>
On Sun, Mar 18, 2007 at 06:38:13PM +0200, Vasil Benov wrote:
> Hi,
>
> I have experienced the same problem. If you have a SATA harddrive
> you should specify root=/dev/sda1(or whatever device number and partition
> you boot from)
>
> On kenrel update the installer overwrites the values for (root=
Hi,
I have experienced the same problem. If you have a SATA harddrive
you should specify root=/dev/sda1(or whatever device number and partition
you boot from)
On kenrel update the installer overwrites the values for (root=) nad
puts there /dev/hd...
Hope this helps
Regards, Vasil
On 3/18/
I upgraded my system today (etch) and when I rebooted this new kernel
complained about running out of compressed data and that I needed to
specify a correct root= parameter. Booting with kernel 2.6.17-4-k7 still
works fine and it uses the same root= parameter. My hard drive is SATA.
Is this a know
5 matches
Mail list logo