Hi,
Some questions back:
1) Which program do you use to connect to the internet? Kinternet, wvdial, Kppp? If the one you uses does not work properly, have you tried one of
Here is some more information from my system.
1) **from /var/log/messages
Nov 10 20:41:11 linux kernel: NETDEV WATCHDOG: eth0: transmit timed out
Nov 10 20:41:11 linux kernel: eth0: transmit timed out, tx_status 00 status
e601.
Nov 10 20:41:11 linux kernel: diagnostics: net 0cc6 media 88c0 dma
0000003a.
Nov 10 20:41:11 linux kernel: eth0: Interrupt posted but not delivered --
IRQ blocked by another device?
Nov 10 20:41:11 linux kernel: Flags; bus-master 1, dirty 80(0) current
80(0)
Nov 10 20:41:11 linux kernel: Transmit list 00000000 vs. c2907200.
Nov 10 20:41:11 linux kernel: 0: @c2907200 length 8000002a status
0001002a
Nov 10 20:41:11 linux kernel: 1: @c2907240 length 800000bf status
000100bf
Nov 10 20:41:11 linux kernel: 2: @c2907280 length 800000bf status
000100bf
Nov 10 20:41:11 linux kernel: 3: @c29072c0 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 4: @c2907300 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 5: @c2907340 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 6: @c2907380 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 7: @c29073c0 length 80000042 status
00010042
Nov 10 20:41:11 linux kernel: 8: @c2907400 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 9: @c2907440 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 10: @c2907480 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 11: @c29074c0 length 80000036 status
00010036
Nov 10 20:41:11 linux kernel: 12: @c2907500 length 8000004a status
0001004a
Nov 10 20:41:11 linux kernel: 13: @c2907540 length 8000004a status
0001004a
Nov 10 20:41:11 linux kernel: 14: @c2907580 length 8000004b status
8001004b
Nov 10 20:41:11 linux kernel: 15: @c29075c0 length 8000002a status
8001002a
Nov 10 20:41:11 linux kernel: eth0: Resetting the Tx ring pointer.
**from ifstatus eth0
dhcpcd running
eth0 is up
**from ping 207.139.84.34
PING 207.139.84.34 (207.139.84.34) from 192.168.1.200 : 56(84) bytes of
data.
64 bytes from 207.139.84.34: icmp_seq=1 ttl=234 time=19668 ms
64 bytes from 207.139.84.34: icmp_seq=2 ttl=234 time=18650 ms
< snip >
19 packets transmitted (because I stopped the ping manually), 16 received,
15% loss, time 50668ms
rtt min/avg/max/mdev = 12650.079/21536.866/30430.063/5852.770 ms, pipe 9
**from ping dns1.netsysteminfo.com
ping: unknown host dns1.netsysteminfo.com
**from cat /etc/resolv.conf
search tampabay.rr.com
nameserver 65.32.1.80
nameserver 65.32.2.136
2: eth0:
other? Can you send an error log from the connection program you use?
2) Check /var/log/messages and /var/log/boot.msg for any error messages that can be related to the checking of the disks. Send these to the list.
3) Check the same files as in 2 for error messages. Do you get any output of 'cat /proc/scsi/scsi' of 'ls /proc/scsi'. Also try 'lspci -vv | grep SCSI' as root.
Regards,
Jostein
On Sunday 10 November 2002 21:20, JR wrote:
Hello.
Getting right to the point I installed SuSE 8.1 to fresh partitions and since then I have been having some problems. I am hopeing that someone might be able to help me with the problems below.
1) My main problem is that I am having problems accessing the internet. My eth0 card is seen and seems to be seeing my provider, at least it gets the information, but I am unable to get Konquer to view any websites. It either times out, most of the time, or its connection fails. I have done what I know about and have had no luck fixing it myself. DHCP seemes to be fine ifstatus eth0 shows that it is connected to my provider, as far as I can tell. I am using RoadRunner cable as my provider.
2) I have 2 RAID 0 drives, Highpoint HTP370, that I built under WinDOS that are causing problems, and I can not access them. The problem occures during the booting of Linux. I keep getting lost interrupts, among other errors, for the 4 drives and it has caused my boot up to be over 9 minutes. Is there a way I can disable the checking of these drives, get Linux to recognize the partitions, or stop the error messages from taking Sooooo much time? Also when I access the partitioning part of Yast2 it takes several minutes before I see the partitions.
3) The last error that I know of now is that my SCSI card is not allowed to connect during boot, or has problems, and therefore it is not accessable. It was accessable in all of the other versions of SuSE Linux I have used, from 6.2 and it is still good since it is available in WinDOS.
Thank you in advance. James Ruhsam jruhsam@gmx.net
-------------------------------------------------------
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com