Re: problems after upgrade
"s. keeling" <keeling@spots.ab.ca> wrote: Fred J. :
Please, don't post HTML. Plain ASCII text, thanks.
> I am running debian/testing with kernel 2.6.15
> In my /etc/sources.list I have basically 2 lines,
> Deb http://http.us.debian.org/debian/ testing main contrib non-free
> Deb http://secure-testing.debian.net/debian-secure-testing/ \
> testing/security-updates main contrib non-free
>
> The box has been working very well for the last 8 months and has
> gone through many $apt-get update upgrades. This morning I ran
> $sudo apt-get update and upgrade.
>
> First thing I noticed, I lost the ability to browse and to apt-get;
> in the browser I get connection has timed out.
> in the
apt-get I get 0%[Connecting to http.us.debian.org
> (1.0.0.0)] and nothing happend.
> I checked and both my /etc/network/interfaces and /etc/hosts are
> the same before and after the upgrade.
What does "/sbin/ifconfig" say? What's in /etc/resolv.conf? What
does "ping -c 1 lists.debian.org" say? If that doesn't work, what
does "ping -c 1 70.103.162.30" say?
*******************************************************************************************
debian:/home/fred# /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:5A:6D:B3:3D
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:5aff:fe6d:b33d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
MTU:1500 Metric:1
RX packets:4974 errors:0 dropped:0 overruns:0 frame:0
TX packets:4712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4158047 (3.9 MiB) TX bytes:765061 (747.1 KiB)
Interrupt:10 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:02:E3:20:EC:E6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::202:e3ff:fe20:ece6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
MTU:1500 Metric:1
RX packets:4640 errors:0 dropped:0 overruns:0 frame:0
TX packets:4847 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:766401 (748.4 KiB) TX bytes:4134105 (3.9 MiB)
Interrupt:11 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436
Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1072 (1.0 KiB) TX bytes:1072 (1.0 KiB)
debian:/home/fred# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
debian:/home/fred# ping -c 1 lists.debian.org
PING lists.debian.org (70.103.162.30) 56(84) bytes of data.
64 bytes from lists.debian.org (70.103.162.30): icmp_seq=1 ttl=42 time=221 ms
--- lists.debian.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time
0ms
rtt min/avg/max/mdev = 221.107/221.107/221.107/0.000 ms
debian:/home/fred# ping -c 1 lists.debian.org 70.103.162.30
PING 70.103.162.30 (70.103.162.30) 56(84) bytes of data.
64 bytes from 70.103.162.30: icmp_seq=1 ttl=42 time=220 ms
--- 70.103.162.30 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 220.132/220.132/220.132/0.000 ms
debian:/home/fred#
Script done on Thu 24 Aug 2006 14:43:55 EST
*****************************************************************************************
...
> I tried to fix it by rebooting the debian box, and noticed a line
> during rebooting saying "iPV6 over iPV4 tunelling device"
> failed
Do you use iPV6? I suspect this just means that, like most people,
you don't use it so trying to find it won't work. No biggie.
I don't know if I am using
it or not, how do I find out?
***************** the rest of the problems below is fixed by a new mouse **********
> Second thing I noticed is when I click on items on the screen to
> do something �icewm� it takes few seconds to respond.
> Never was like this before.
Hmmm ...
How low will we go? Check out Yahoo! Messenger?s low PC-to-Phone call rates.
Reply to: