Filed as bug 497137.
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I had similar worries about race conditions, but this code path is supposed
to be happening so rarely, that the race conditions would probably be even
rarer.
That being said, that does seem like a cleaner solution. File a different
bug and we'll track it there. It's just going to need some good
> --- debian/gdm.upstart2009-12-11 05:36:55 +
> +++ debian/gdm.upstart2009-12-14 20:12:34 +
> @@ -9,7 +9,9 @@
> start on (filesystem
>and (graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1
> or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPL
This bug was fixed in the package xorg - 1:7.5~3ubuntu3
---
xorg (1:7.5~3ubuntu3) lucid; urgency=low
* debian/x11-common.failsafe-x.upstart: (LP: #453365)
- Start on the build-failed signal that DKMS may emit
during a failed build for nvidia or fglrx.
-- Mario Limonciello
** Package changed: openafs (Ubuntu) => xorg (Ubuntu)
** Changed in: xorg (Ubuntu)
Status: New => In Progress
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs
This bug was fixed in the package gdm - 2.29.1-0ubuntu6
---
gdm (2.29.1-0ubuntu6) lucid; urgency=low
* debian/gdm.upstart (LP: #453365)
- Start on built-successful signal for fglrx or nvidia modules.
- If dkms is available on the system, use it to check the status
of f
Anders:
In case it's not clear, here's the final upstart task that I settled upon:
http://linux.dell.com/git/?p=dkms.git;a=blob;f=dkms_autoinstaller.upstart;h=27fc487923f1f77d0e075b3570f76e718746b9bb;hb=HEAD
It should start immediately upon startup on all systems. I've got some
extra integration
This bug was fixed in the package dkms - 2.1.1.0-0ubuntu1
---
dkms (2.1.1.0-0ubuntu1) lucid; urgency=low
[ Mario Limonciello ]
* New upstream version
* dkms_autoinstall: Minor logic cleanups from submitted patches.
* dkms_autoinstall: Run under dash since dkms.conf isn't sourc
> If the effort is just to get any packages in main by Lucid, I don't see why
> it's not achievable.
Fixing all of main isn’t good enough for many users (openafs is itself
in universe). Whether it’s acceptable to break universe is up to the
Ubuntu TB, but there’s absolutely no point in breaking *
On Thu, Dec 10, 2009 at 01:07, Anders Kaseorg wrote:
> > Now, if you chain that with the openafs upstart job waiting for DKMS to
> > be done and apache/mysql/$favorite_server_service waiting for network
> > file systems to be ready and you've got a very logical ordering to your
> > boot process.
> Now, if you chain that with the openafs upstart job waiting for DKMS to
> be done and apache/mysql/$favorite_server_service waiting for network
> file systems to be ready and you've got a very logical ordering to your
> boot process.
Yes yes, I understand that. And I want very much to live in t
On 12/09/2009 02:54 PM, Anders Kaseorg wrote:
> Even if it is desirable to convert openafs-client to upstart right now,
> forcing dkms to load after rc would force openafs-client to load after
> rc. This will be a problem for other services that depend on openafs,
> such as apache2 installations w
Even if it is desirable to convert openafs-client to upstart right now,
forcing dkms to load after rc would force openafs-client to load after
rc. This will be a problem for other services that depend on openafs,
such as apache2 installations with docroot in /afs.
dkms provides kernel modules, an
** Changed in: dkms (Ubuntu)
Importance: Undecided => Medium
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
It's very early in the cycle, so this is the time that these types of
things should be switched over and ironed out. I'm going to adjust the
DKMS task back to Fix Committed. If you've got some other feedback
about how this upstart script should look before I upload it, feel free
to leave it here,
And it will (bug 483506), but I worry that there may be other
initscripts with the same problem. In any event, should we really force
all of these transitions to happen at exactly the same time?
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You
** Also affects: openafs (Ubuntu)
Importance: Undecided
Status: New
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Anders:
Then openafs-client should be converted to an upstart script that depends on
DKMS having finished running
On Tue, Dec 8, 2009 at 15:33, Anders Kaseorg wrote:
> You added “or stopping rc RUNLEVEL=[2345]” rather than “or starting rc
> RUNLEVEL=[2345]”. This will break openafs-modules-dkm
You added “or stopping rc RUNLEVEL=[2345]” rather than “or starting rc
RUNLEVEL=[2345]”. This will break openafs-modules-dkms because
/etc/init.d/openafs-client (which requires the kernel module to have
already been built) is started from rc.
** Changed in: dkms (Ubuntu)
Status: Fix Commit
I've committed a solution to this upstream:
http://linux.dell.com/git/?p=dkms.git;a=commit;h=3692368c51692003a56d5c4a174f7d712aace71e
I tested it on both desktop and server installations, the script still
runs in both scenarios.
** Changed in: gdm (Ubuntu)
Status: New => Won't Fix
** Chan
> +start on (starting gdm
> + or starting kdm
> + or starting xdm
> + or starting oem-config
> + or starting ubiquity)
I’m not completely familiar with how upstart jobs work, but won’t that
make dkms_autoinstaller never start on a server that needs it for
openaf
Well, here are all the logs created in /var/log during a reboot with
--verbose after ‘dkms remove -m nvidia -v 185.18.36 -k $(uname -r)’. As
you can see, gdm started too early to find the nvidia module that dkms
was still in the process of compiling. The nvidia driver could be
loaded fine manuall
Can anyone else confirm this is indeed happening? Sounds like it could
cause a lot of bad breakage if so.
Anders, any additional data you could provide (log files, error
messages, etc.) could help move this issue faster towards becoming
actionable.
--
dkms should start before gdm if needed for
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
24 matches
Mail list logo