From: "Steven Barnhart" <sbarn03@softhome.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.54-mm3
Date: Sat, 04 Jan 2003 18:41:19 -0500 [thread overview]
Message-ID: <pan.2003.01.04.23.41.14.859710@softhome.net> (raw)
In-Reply-To: 3E17644D.59E3F205@digeo.com
On Sat, 04 Jan 2003 14:46:37 +0000, Andrew Morton wrote:
> 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
.config is now attached and no, I am not using devfs.
> 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
I also attached the dmesg output from 2.5.54. Hope that helps. Sometime
tonight/tomorrow I will reboot 2.5 and attempt to get the lspci output for
the list.
Steven
next prev parent reply other threads:[~2003-01-04 23:33 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 ` 2.5.54-mm3 Andrew Morton
2003-01-04 23:41 ` Steven Barnhart [this message]
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=pan.2003.01.04.23.41.14.859710@softhome.net \
--to=sbarn03@softhome.net \
--cc=linux-kernel@vger.kernel.org \
/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.