Kent West wrote:
Debian User Leonard Chatagnier wrote:
The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
on going to the 2.6.6-2-686 kernel and will eventually, probably
soon. Kent
finally fixed lilo for me so that sarge boots now if you haven't
already read it.
You
On Fri, 24 Jun 2005 22:15:31 -0500, Debian User Leonard Chatagnier
<[EMAIL PROTECTED]> wrote:
>I'm still trying to get a stable system for the last six months that
>I've been using Debian ... Out of 3 or 4 sarge installs, only the last
>one via testing worked out of the box and booted normally. T
Debian User Leonard Chatagnier wrote:
> The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
> on going to the 2.6.6-2-686 kernel and will eventually, probably
> soon. Kent
> finally fixed lilo for me so that sarge boots now if you haven't
> already read it.
> You can, if you
Marty wrote:
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline
the process).
Like any other package: "apt-get remove " or use aptitude,
dselect, etc.
I don't use the packaged kernels so I don't know but if it tries to
re-install
LILO
On Fri, Jun 24, 2005 at 01:35:23PM +0100, Clive Menzies wrote:
> On (24/06/05 23:29), Chris Bannister wrote:
> > On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
> >
> > >Now I'm worried. Note: I don't have a reiserfs file system, only an
> > >ext3 fs since day one on
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline the
process).
Like any other package: "apt-get remove " or use aptitude, dselect,
etc.
I don't use the packaged kernels so I don't know but if it tries to re-install
LILO, I would postpone
Marty wrote:
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you
boot
using LinuxOLD. It boots normally as it did since first installed.
I do see that
Output module failed to load as was the case on my old sarge. If
your refering
to
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Sorry again. After I emailed my response, I realized I for got to run
lilo. So ran it and got this error:
ChatagnierL-Home:/home/lchata# lilo
Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
ChatagnierL-Home:/home/
Debian User Leonard Chatagnier wrote:
> Sorry again. After I emailed my response, I realized I for got to run
> lilo. So ran it and got this error:
> ChatagnierL-Home:/home/lchata# lilo
> Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
> ChatagnierL-Home:/home/lchata#
>
> So
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you boot
using LinuxOLD. It boots normally as it did since first installed. I do see
that
Output module failed to load as was the case on my old sarge. If your refering
to my notes about n
Marty wrote:
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
(
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent West wrote:
The line should be:
initrd=/initrd.img
I put the / in front of initrd.img and rebooted with kernel panic
again giving
these same boot messages:
VFS: Cannot open root device "301" or 03:01
Please app
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've tried
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
(Lacking an enab
Debian User Leonard Chatagnier wrote:
> Kent West wrote:
>
>> The line should be:
>> initrd=/initrd.img
>
> I put the / in front of initrd.img and rebooted with kernel panic
> again giving
> these same boot messages:
>
> VFS: Cannot open root device "301" or 03:01
> Please append a correct "
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've tried
Debian User Leonard Chatagnier wrote:
> Kent,
> Sorry about my mixup. Found the original reply in drafts; never sent.
> This is new reply that is more current. My reply is bolow:
>
> Leonard Chatagnier wrote:
>
>> Kent West wrote:
>>
>>> Sarge's boot is hosed, but you've tried to boot off the Wo
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice "301" or 30:01
Please append a correct "root=" boot option
Kernel panic: VFS unable to mount root fs on
Debian User Leonard Chatagnier wrote:
> -Doesn't look like Kent is going to reply
> to my last post:
I missed seeing any such post. Nor do I find one in the archives:
http://lists.debian.org/debian-user/2005/06/thrd8.html
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On (24/06/05 23:29), Chris Bannister wrote:
> On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
>
> >Now I'm worried. Note: I don't have a reiserfs file system, only an
> >ext3 fs since day one on all partitions.
> >
> >If anyone can help me to get the system boota
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
>Now I'm worried. Note: I don't have a reiserfs file system, only an
>ext3 fs since day one on all partitions.
>
>If anyone can help me to get the system bootable again, I think I can
>correct the lilo.conf prob
--- Kent West <[EMAIL PROTECTED]> wrote:
Leonard Chatagnier wrote:
> VFS: Cannot open rootdevice "301" or 30:01
> Please append a correct "root=" boot option
> Kernel panic: VFS unable to mount root fs on 30:01
> Ok, not worried at this time as I have my woody
CD's and can do a
> rescbf24 to
--- Kent West <[EMAIL PROTECTED]> wrote:
> Leonard Chatagnier wrote:
>
> > VFS: Cannot open rootdevice "301" or 30:01
> > Please append a correct "root=" boot option
> > Kernel panic: VFS unable to mount root fs on 30:01
> > Ok, not worried at this time as I have my woody
> CD's and can do a
>
Leonard Chatagnier wrote:
> VFS: Cannot open rootdevice "301" or 30:01
> Please append a correct "root=" boot option
> Kernel panic: VFS unable to mount root fs on 30:01
> Ok, not worried at this time as I have my woody CD's and can do a
> rescbf24 to mount woody still installed and correct the li
So frustrating, just fixed KDE Knotify problem and Debian only stayed fixed
until installed a dist-upgrade.
Stayed fixed less than a day. Ok, the problem is related to lilo.conf
for an initrd.img. I followed the dist-upgrade messages closely and
thought I did it as described, but apparently
25 matches
Mail list logo
