Hot Diggety! Farrell Farahbod was rumored to have written:
> wow...quick reply :) i guess they werent lying when they said gentoo has
> terrific forums! wooho!

It's a pretty nifty crowd, indeed. :)
 
> well about possible nic/nat problems...i highly highly doubt it, becuase
> like i said, i run redhat9 linux on the same box...its a dual boot. and
> the live cd was able to easily use my nic, like i mentioned earlier. but

Ok. Based on that and the other information you pasted, I'd like to say
that it's likely a module issue of some sort, possibly. Not with loading
it, but with functioning, for some unknown reason?

> cat /etc/env.d/01hostname:
> 
> HOSTNAME="farrell"
> 
> (you said it should have a FQDN...but it doesnt...but if it was supposed
> to have a fqdn, why is the filename 01hostname? just curious...i like to
> learn :) )

With some OS installs (not just Gentoo, but many others on various
platforms), sometimes it isn't always clear to end users -- especially one
new to the OS/distribution -- that a FQDN is desirable. I'm no spring
chicken when it comes to UNIX (and UNIX-like clones for some of our
resident pedants ;) ) but that still bites me from time to time.

Further compounded by the fact that the various OS/distros don't usually be
picky about FQDN vs non-FQDN hostname because it doesn't assume anything
about the environment the machine is in. (DNS, no DNS, domain vs no domain,
or just plain don't care, etc)

As for numbering scheme with /etc/env.d, if it's anything like SysV init
scripts, it appears that the numbering is mostly to ensure the more
important basic stuff gets set or processed first.

For instance, with /etc/env.d, you see: 00basic, 01hostname -- number one
stuff to get set early on! Then you have 05gcc, 10mozilla, 10xfree, etc...
then later on, the less important stuff -- 70less, 90games, etc.
 
> lsmod:
> 
> Module                  Size  Used by    Not tainted
> usbcore                55488   1
> 8139too                14152   1
> mii                     2160   0  [8139too]

So it appears to have loaded ok. You've got an eth0 device as well.

But what bothers me is the ifconfig eth0 output.
 
> (hum...looks to me like petty few kernel modules...but then again i have
> practically nothing configured...sound, printing, etc..) also, you asked

That's fine. Modules offers the greatest flexibility and lessens the need
to reboot to enable/disable functionality. But since this is a new
installation, I'm sure you'll eventually get around to modulizing as many
stuff as you can... for now, what you have is fine.

> ifconfig eth0:
> eth0      Link encap:Ethernet  HWaddr 00:02:44:14:1B:72
>           inet addr:192.168.1.105  Bcast:192.168.1.255 Mask:255.255.255.0
>           inet6 addr: fe80::202:44ff:fe14:1b72/10 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0xf000

I was mostly concerned about 'UP BROADCAST RUNNING' being present
along with inet+bcast+netmask matching/making sense, and MAC address
being correctly displayed. Looks good on all counts.

Now, the fact is, there's _0_ packets or errors... that seriously
bothers me the most. Try pinging the default route IP again, and see
if you get anywhere.

Not going to be a cable issue (which usually lists some TX packets
and errors) because it works fine in a dual-booted RH setup.

Also, could try booting into RH, and do 'ifconfig eth0' and compare
to see if stuff (like the MTU, for instance) agrees.

Now, normally, 0'd counters for an ethernet device might mean that
the driver (module) is not working or didn't recognize the chipset,
even though it loaded.

Just because a module loaded, doesn't mean it will actually handle
a device. I'm baffled, if the exact same module worked ok on the
LiveCD. Hmm.

Might also try pasting the output of:

# dmesg | grep -i eth
 
> and about ipchains etc..i dont think so... i dont recall them loading at
> boot time, but it scrolls by soo fast i dont know if i'd really
> notice... but all i have installed on gentoo is what i had emerge
> install: sync, gnome, kudzu, but of course it satasfied any dependencies
> those had. how do i check to see if ipchains, etc is installed? im used
> to redhats rpm -qa ;(

That's ok... judging from eth0 info, doesn't appear to be an issue.

As for checking packages... you'd need to do this to emulate rpm -qa:

# emerge gentoolkit
# qpkg -I -v [search string]

(or just 'qpkg -I -v' to look through the whole list)

Although until you get eth0 working, probably don't have an easy way of
grabbing gentoolkit-0.1.30.tar.bz2 (or .gz) into /usr/portage/distfiles
for that emerge to work. :) (short of booting into RH, d/l'ing that file,
cp'ing over to the Gentoo partition, etc)

One workaround and a way to check without needing qpkg is:

# emerge -s ipchains

(-s = search only, doesn't install)

Will tell you [ Not Installed ] for the 'Latest version installed:'
if it isn't installed.

-Dan

--
[EMAIL PROTECTED] mailing list

Reply via email to