From: Khoa Nguyen <khoan@rsn.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] BigSur on the LAN
Date: Wed, 30 Aug 2000 19:45:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205419@msgid-missing> (raw)
Hello,
I've been monitoring this list for a few days now and everyone seems to
have the IA64 box on the lan. To date, we have not been able to put our
bigsur on the lan. I've tried RedHat, and Turbo linux distribution to
no avail. If you know of any step that I might have missed, please let
me know. We'd like to put our box on the lan for every one to play with.
Here is what I've tried so far:
1. Installed Turbo linux (one version older than the lastest).
Configured network params.
Successfully pinged itself, but couldn't ping any other IP
eth0 listed as eepro100: IRQ 10, base addr 0x1000
Periodically got: "eth0: Transmit timed out: status f088
0c00 at 28/56 command 0001a000"
2. Installed latest RedHat.
Configured network params.
Successfully pinged itself, but couldn't ping any other IP
eth0 listed as eepro100: IRQ 10, base addr 0x1000
Periodically got: "eth0: Transmit timed out: status f088
0c00 at 28/56 command 0001a000"
3. Used RedHat latest as a base and rebuild the kernel with
module support.
Compiled eepro100 as modules
Copied System.map and vmlinux and rename them appropriately
to /boot and /boot/efi respectively.
Tried 'modprobe eepro100' and got these errors:
"..../eepro100.o: unresolved symbol pci_unmap_single"
"..../eepro100.o: unresolved symbol pci_map_single"
"..../eepro100.o: unresolved symbol pci_dma_sync_single"
I thought that the built-in ethernet card is bad. So, we bought a PCI
Intel Pro/100+. After installing it, the box continually reboots.
Here is the system config:
SDV Pre-Qual
A-3 stepping processor
1G RAM.
Any help is greatly appreciated.
Thanks,
Khoa.
reply other threads:[~2000-08-30 19:45 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=marc-linux-ia64-105590678205419@msgid-missing \
--to=khoan@rsn.hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox