From: Olaf Hering <olh@suse.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: netboot on CHRP B50
Date: Sat, 12 Aug 2000 00:16:20 +0200 [thread overview]
Message-ID: <20000812001620.A21670@suse.de> (raw)
Hi,
while trying netboot with our machines we found a bug either in the
kernel or in the pcnet32 network driver.
If we boot with "boot net" from the OF prompt everything works fine.
Booting the same kernel with "boot net console=ttyS0[,9600]" kills the
network driver, in this case pcnet32.
There are 2 cards in the machine, only the first card was found. The
interface was up, but not network traffic. The TX line of ifconfig
contains errors but no transmitted packages.
The dmesg output contains no infos that something is wrong with the
card, no errors.
This is the normal output:
pcnet32.c: PCI bios is present, checking for devices...
PCI Master Bit has not been set. Setting...
Found PCnet/PCI at 0xbff400, irq 22.
eth0: PCnet/FAST 79C971 at 0xbff400, 00 04 ac 97 35 56
tx_start_pt(0x0400): 64 bytes, BCR18(6821):BurstWrEn NoUFlow
SRAMSIZE=0x7f00, SRAM_BND=0x4000, assigned IRQ 22.
pcnet32.c:v1.25kf 26.9.1999 tsbogend@alpha.franken.de
PCI Master Bit has not been set. Setting...
Found PCnet/PCI at 0xbff800, irq 18.
eth1: PCnet/FAST 79C971 at 0xbff800, 00 04 ac de 53 bf
tx_start_pt(0x0400): 64 bytes, BCR18(6821):BurstWrEn NoUFlow
SRAMSIZE=0x7f00, SRAM_BND=0x4000, assigned IRQ 18.
pcnet32.c:v1.25kf 26.9.1999 tsbogend@alpha.franken.de
This is the output with a boot arg:
pcnet32.c: PCI bios is present, checking for devices...
PCI Master Bit has not been set. Setting...
Found PCnet/PCI at 0xbff400, irq 22.
PCI Master Bit has not been set. Setting...
Found PCnet/PCI at 0xbff800, irq 18.
eth0: PCnet/FAST 79C971 at 0xbff800, 00 04 ac de 53 bf
tx_start_pt(0x0400): 64 bytes, BCR18(6821):BurstWrEn NoUFlow
SRAMSIZE=0x7f00, SRAM_BND=0x4000, assigned IRQ 18.
pcnet32.c:v1.25kf 26.9.1999 tsbogend@alpha.franken.de
Hmm, that means that the eth0 is still active and the older eth1 becomes
eth0 now.
Looks like we have to shutdown the card first. I wonder why it works
without a bootarg.
Any hints?
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:[~2000-08-11 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000812001620.A21670@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).