linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: pmac netdevice driver probing bugs
Date: Tue, 6 Feb 2001 12:14:15 +0100	[thread overview]
Message-ID: <20010206121414.A7877@suse.de> (raw)


Hi,

the current device probing code for mace,bmac and gmac returns always 0
and the module can be loaded even if the required hardware is not
present.

cherry:~ # modprobe pcnet32
/lib/modules/2.4.1-olaf/kernel/drivers/net/pcnet32.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.1-olaf/kernel/drivers/net/pcnet32.o: insmod
/lib/modules/2.4.1-olaf/kernel/drivers/net/pcnet32.o failed
/lib/modules/2.4.1-olaf/kernel/drivers/net/pcnet32.o: insmod pcnet32
failed
cherry:~ #  modprobe bmac
cherry:~ # lsmod
Module                  Size  Used by
bmac                   12512   0  (unused)
nfsd                   75888   4  (autoclean)
autofs4                11920   4  (autoclean)
ipv6                  151488  -1  (autoclean)
gmac                   15248   1  (autoclean)



Can we change that behaviour?
de4x5 and pcnet32 return -EIO as example and the module is not loaded.



Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-02-06 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 11:14 Olaf Hering [this message]
2001-02-14  2:24 ` pmac netdevice driver probing bugs Olaf Hering

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=20010206121414.A7877@suse.de \
    --to=olh@suse.de \
    --cc=linuxppc-dev@lists.linuxppc.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).