From: "Craig D. Lansing" <clansing@charter.net>
To: "'Grant Grundler'" <grundler@parisc-linux.org>,
"'Matthew Wilcox'" <matthew@wil.cx>
Cc: parisc-linux@lists.parisc-linux.org
Subject: RE: [parisc-linux] J2240 - Almost there....
Date: Wed, 4 Jan 2006 23:08:03 -0500 [thread overview]
Message-ID: <000601c611ad$a02a50e0$3401a8c0@POGO> (raw)
In-Reply-To: <20060104181854.GE20079@colo.lackof.org>
I forgot about the built-in LAN port. I moved the cable to that one and all
was working from HP-UX, so I restarted the Debian install from CD... it sure
works much better now!!!! The installer doesn't ask for the network info
anymore (i.e. got an IP address from DHCP and did not ask for DNS info,
gateway, etc.), automagically selected eth1 (I guess that implies that eth1
is the built-in and eth0 is the card), and no longer whines about not being
able to reach security.debian.org.
The installer has been busily installing packages for at least 3 hours.
1. Blew up / hung once on:
Setting up libatk1.0-0 (1.8.0-4) ...
module ipv6 relocation of symbol ipv6_chk_addr is out of range (0x3ff3fffd
in 17 bits).
2. Power cycled, booted
I get the "module ipv6..." errors when portmap, PostgreSQL, and Apache2
daemons start.
3. Restarted install via "apt-get -f install". This is my first attempt at
Debian, so I am not APT literate. This is just what I was prompted to do
when I tried to install one package.
Installer is still chugging.
This appears to be a good sign.
-----Original Message-----
From: parisc-linux-bounces@lists.parisc-linux.org
[mailto:parisc-linux-bounces@lists.parisc-linux.org] On Behalf Of Grant
Grundler
Sent: Wednesday, January 04, 2006 1:19 PM
To: Matthew Wilcox
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] J2240 - Almost there....
On Wed, Jan 04, 2006 at 10:49:43AM -0700, Matthew Wilcox wrote:
...
> > 0000:00:03.0 is tulip in slot 3.
> > 0000:01:14.0 is tulip built-in. (my guess)
>
> I disagree. The 'Cujo' on GSC bus 8 is actually a Dino. As I said
> in my earlier mail, I've now fixed this.
I couldn't tell if the names were wrong offhand - needed ioscan output
(got it) and compare. Thanks for fixing this.
> So I think eth0 (00:03.0) is actually the built-in one.
I think I got this right despite PCI controller names.
Workstations typically hardwired the PCI slot to use the same device
number (e.g. 3) as what is silk screened on the back of the machine.
Built-in devices were typically given numbers much greater than the
highest slot number.
Servers never did this just because that scheme doesn't work multi-cell
systems with > 32 PCI slots (e.g. superdome) or multiple IO bays with
identical silk screened slot numbers.
thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-01-05 4:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 15:51 [parisc-linux] J2240 - Almost there Craig D. Lansing
2005-12-30 20:09 ` Kyle McMartin
2005-12-31 3:16 ` Craig D. Lansing
2005-12-31 3:30 ` Kyle McMartin
2005-12-31 16:21 ` Craig D. Lansing
2005-12-31 18:08 ` Grant Grundler
2006-01-01 4:21 ` Craig D. Lansing
2006-01-01 6:32 ` Grant Grundler
2006-01-01 14:15 ` Thibaut VARENE
2006-01-03 1:19 ` Craig D. Lansing
2006-01-03 2:01 ` Matthew Wilcox
2006-01-04 17:43 ` Grant Grundler
2006-01-04 17:49 ` Matthew Wilcox
2006-01-04 18:18 ` Grant Grundler
2006-01-05 4:08 ` Craig D. Lansing [this message]
2006-01-03 2:01 ` Craig D. Lansing
2005-12-31 14:43 ` [parisc-linux] " Max Grabert
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 2:43 [parisc-linux] J2240 - Almost There Craig D. Lansing (root)
2001-11-12 6:03 ` Jurriaan on Alpha
2001-11-13 0:07 ` Craig D. Lansing
2001-11-13 0:04 ` Matthew Wilcox
2001-11-13 0:11 ` John David Anglin
2001-11-13 7:40 ` Grant Grundler
2001-11-13 9:03 ` nick
2001-11-12 10:49 ` Albert Strasheim
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='000601c611ad$a02a50e0$3401a8c0@POGO' \
--to=clansing@charter.net \
--cc=grundler@parisc-linux.org \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.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