All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Steven Barnhart <sbarn03@softhome.net>
Cc: linux-kernel@vger.kernel.org, linux-kernel-mm@vger.kernel.org
Subject: Re: 2.5.54-mm3
Date: Sat, 04 Jan 2003 14:46:37 -0800	[thread overview]
Message-ID: <3E17644D.59E3F205@digeo.com> (raw)
In-Reply-To: 002401c2b441$4e03eff0$18df9641@steven

Steven Barnhart wrote:
> 
> > autofsv4 has been working fine across the 2.5 series.  You'll need to
> > send a (much) better report.
> 
> I don't really know what the problem is..everything seems to be working
> right except when it goes to mount the system from ro mode to rw mode.
> Therefore well everything goes down hill after that. I looked through the
> /var/log/messages and all those files but nothing specific to the problem.
> If I disable fsck and append rw mode kernel boots fine. One minor note, boot
> also fails during Mounting other filesystems and gives the typical mount
> error about bad superblock, or to many mounted filesystems. My .config was
> attached before(?) and that's all I have..anything paticular you are looking
> for?

Your .config was not attached.

There is a devfs mounting problem in 2.5.54.  If you're using devfs
you may find that
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.54/2.5.54-mm3/broken-out/devfs-mount-fix.patch
will help

> > You could try statically linking it, yes.  More details are needed,
> > such as a description of what hardware you have and what driver you're
> > using.
> 
> I have a i810 Intel graphics card/motherboard, intel celeron 1.06 GHz
> processor, and agp 3 enabled, could that be the problem? I have enabled the
> intel i810 driver in the graphics area as you can see in the .config. The
> intel driver seems to be enabled fine as in the Xfree/GDM log it says
> something about Intel. Only error is it can't find device /dev/agpgart even
> though it *is* there. Any more info you would need?

The device node exists in /dev.  It sounds like no kernel driver
has registered itself against tht node's major/minor.   Make really
sure that you have compiled the appropriate driver for your hardware;
things may have changed.  All else fails, send lspci and dmesg output
to this list and/or davej@codemonkey.org.uk

  reply	other threads:[~2003-01-04 22:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04  9:00 2.5.54-mm3 Andrew Morton
2003-01-04  9:00 ` 2.5.54-mm3 Andrew Morton
2003-01-04 15:47 ` 2.5.54-mm3 Steven Barnhart
2003-01-04 15:47   ` 2.5.54-mm3 Steven Barnhart
2003-01-04 21:18   ` 2.5.54-mm3 Andrew Morton
2003-01-04 21:18     ` 2.5.54-mm3 Andrew Morton
2003-01-04 22:31     ` 2.5.54-mm3 Steven Barnhart
2003-01-04 22:46       ` Andrew Morton [this message]
2003-01-04 23:41         ` 2.5.54-mm3 Steven Barnhart
2003-01-05 18:04 ` 2.5.54-mm3 uaca
2003-01-05 20:38   ` 2.5.54-mm3 Andrew Morton
2003-01-05 21:17     ` 2.5.54-mm3 uaca
  -- strict thread matches above, loose matches on Subject: below --
2003-01-05  2:20 2.5.54-mm3 Steven Barnhart
2003-01-05 14:35 2.5.54-mm3 Michael Abshoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E17644D.59E3F205@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel-mm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbarn03@softhome.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.