From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: dri and agpgart not working in udev >075 and linux-2.6.15
Date: Fri, 17 Mar 2006 17:49:28 +0000 [thread overview]
Message-ID: <20060317174928.GA3172@kroah.com> (raw)
In-Reply-To: <20060317170117.GA14973@dyne.org>
On Fri, Mar 17, 2006 at 06:01:17PM +0100, jaromil wrote:
>
> re all,
>
> this issue was reported already in january
> http://sourceforge.net/mailarchive/message.php?msg_id\x14545517
> (please note that in my mail i had a typo: i was using 2.6.15 kernel)
>
> and apparently fixed:
> http://sourceforge.net/mailarchive/message.php?msg_id\x14546267
>
> i'm now testing udev-087 with linux-2.6.15.6 and sysfsutils-2.0
> and still there are no /dev/agpgart and /dev/dri/* created.
Did you see where that patch went into 2.6.16-rc, not 2.6.15, that's why
you are having this issue. Please upgrade your kernel and it will be
fixed.
> test is run on a sane environment and the devices are correctly created
> when using udev < 075.
Just stick with this version until you upgrade your kernel, if you do
not want to do that.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-03-17 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 17:01 dri and agpgart not working in udev >075 and linux-2.6.15 jaromil
2006-03-17 17:49 ` Greg KH [this message]
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=20060317174928.GA3172@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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.