linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: linux-ppc <linuxppc-dev@ozlabs.org>
Cc: debian-powerpc@lists.debian.org
Subject: Re: Long boot delay with agpgart
Date: Sun, 9 Mar 2008 21:58:24 +0100	[thread overview]
Message-ID: <20080309205824.GA3373@localhost> (raw)
In-Reply-To: <20080305163320.GA3961@localhost>

On Wed, Mar 05 2008, at 17:33 +0100, Wolfgang Pfeiffer wrote:

> The boot process began being stuck the moment some agpgart init
> routine started:
> 
> Excerpt from kern.log that moment:
> 
> [    6.882357] usbcore: registered new device driver usb
> [   36.732011] uninorth_agp: gave up waiting for init of module agpgart.
> [   36.733009] uninorth_agp: Unknown symbol agp_bridge
> [   66.734008] uninorth_agp: gave up waiting for init of module agpgart.
> [   66.735011] uninorth_agp: Unknown symbol agp_find_bridge
> [   96.736009] uninorth_agp: gave up waiting for init of module agpgart.
> [   96.737010] uninorth_agp: Unknown symbol agp_device_command
> 

With Debian package modutils not being installed I still had in
/etc/modutils/local and in /etc/modules.conf:

pre-install radeon /sbin/modprobe "-k" "agpgart"
pre-install agpgart /sbin/modprobe "-k" "uninorth_agp"

I don't know whether these lines can be confusing for the boot
routines, or whether they're read at all by the system on boot
time. Anyway: 

I removed modules.conf, and commented out everything in
/etc/modutils/local

A first reboot after the change didn't break anything, as it seems
... 

Sorry if it was only noise ...

Best Regards
Wolfgang

-- 
http://heelsbroke.blogspot.com/
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on

      reply	other threads:[~2008-03-09 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 16:33 Long boot delay with agpgart Wolfgang Pfeiffer
2008-03-09 20:58 ` Wolfgang Pfeiffer [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=20080309205824.GA3373@localhost \
    --to=roto@gmx.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).