Re: Configuring X on Intel 82845 gl board
Forgive me if[sic] this is irrelevant nonsense (I know precious
little about this stuff; I've only been scrutinizing the ouput
you have provided), but ...
On Wed, May 18, 2005 at 07:20:29PM -0000, shatam bhattacharya wrote:
[...]
> 2) I still cant apt-get update (the same problem i.e. (1.0.0.0) hang persists.)
> I suspect the route output will give you a clue ---
>
> ginie:/home/shatam# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
> Just to rebrief I am using a DSL router (192.168.1.1) and an ethernet card whose ifconfig shows ---
> ginie:/home/shatam# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:08:A1:32:E1:7E
> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3252 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3406 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:2884677 (2.7 MiB) TX bytes:580437 (566.8 KiB)
> Interrupt:18 Base address:0xac00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:388 errors:0 dropped:0 overruns:0 frame:0
> TX packets:388 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:19848 (19.3 KiB) TX bytes:19848 (19.3 KiB)
>
... if I remember rightly, you recently posted your dmesg output
which showed your single ethernet card being recognized twice - as
eth0 (associated with the via Rhine driver) and eth1 (associated
with the 8139too driver). Since 8139too seems to be the correct
driver, but ifconfig shows eth0, could the problems stem from your
having the wrong driver from the card?
As I said, pure surmise; I have no idea how these things work :-{
Cheers,
David
--
David Jardine
"Running Debian GNU/Linux and
loving every minute of it." -L. von Sacher-M.(1835-1895)
Reply to: