Re: [SLE] Help please with a few problems in 8.1.
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 11 November 2002 01:56, JR wrote:
**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
REPLY: Hi JR, from the Above mention information your problem for Konqueror not working is a DNS issue, you see Web browsers usually do a DNS lookup before going to look for a page when you type the URL. Maybe the DNS servers provided by your ISP are not working properly, try the following command: #nslookup you will get a prompt = ">" At the prompt type:
207.139.84.34 You should get something like:
34.84.139.207.in-addr.arpa name = netsystemsinfo.com. 34.84.139.207.in-addr.arpa name = dns1.netsystemsinfo.com. if you do not get this type of reply modify your resolv.conf file: comment out everything and add the following line:
#search tampabay.rr.com #nameserver 65.32.1.80 #nameserver 65.32.2.136 nameserver 207.139.84.34
Save the file, and now do again nslookup command but this time we try something we are all familiar with: #nslookup
www.netscape.com Server: 10.1.0.4 Address: 10.1.0.4#53
www.netscape.com canonical name = netscape.com. Name: netscape.com Address: 64.12.180.22 Name: netscape.com Address: 64.12.151.211 Name: netscape.com Address: 64.12.151.215 Name: netscape.com Address: 64.12.180.19 You should see something like this. If you do the open Konqueror try to browse it should work. The solution then is to ask you provider for DNS servers that resolv properly for your address.
2) My RAID drives only have Windows insalled on them and lots of data.
my /var/log/boot.msg information is attached as a .txt file and zipped to save download time.
3) more info about my scsi linux:/home/jamruh # ls /proc/scsi . .. aic7xxx ide-scsi scsi sg
linux:/home/jamruh # cat /proc/scsi/scsi Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: OnStream Model: DI-30 Rev: 1.08 Type: Sequential-Access ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: PIONEER Model: DVD-RW DVR-103 Rev: 1.55 Type: CD-ROM ANSI SCSI revision: 02
linux:/home/jamruh # lspci -vv | grep SCSI 00:0c.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
REPLY: For your disks, can you send me a printout of the /etc/fstab file Thanks Vic - -------------------------------------------------------------------------------------------------- NetSystems Info Inc. 164 rue Ideal St-Eustache, Quebec J7P !R3, CANADA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9z8I93GpaTL3AppcRAkFeAJ99Qy7pbIaQToWqxYlfEx8+oikWHQCgwpQK F1QFYVwkz42pvtPxK/WrV1U= =rIKW -----END PGP SIGNATURE-----
Here is the information that I received from nslookup and from the fstab. ***nslookup info nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing.
207.139.84.34 ;; connection timed out; no servers could be reached 207.139.84.34 Server: 65.32.1.80 Address: 65.32.1.80#53
Non-authoritative answer: 34.84.139.207.in-addr.arpa name = netsystemsinfo.com. Authoritative answers can be found from: 84.139.207.in-addr.arpa nameserver = ns.InterLink.NET. 84.139.207.in-addr.arpa nameserver = ns.RezoNet.NET. ns.RezoNet.NET internet address = 198.168.54.8
www.netscape.com ;; connection timed out; no servers could be reached
----------------------------------------- ***fstab info /dev/hda4 / ext3 defaults 1 1 /dev/hda1 /boot ext3 defaults 1 2 /dev/hda3 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrecorder1 /media/cdrecorder1 auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/hda5 /windows/c vfat defaults 0 0 /dev/hda6 /windows/d vfat defaults 0 0 /dev/hdc1 /windows/e vfat defaults 0 0 /dev/hdc5 /windows/f vfat defaults 0 0 /dev/hda7 /home2 ext3 defaults 1 2 Than you, James Ruhsam *********** REPLY SEPARATOR *********** On 11/11/2002 at 9:44 AM Victor Mendez wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 11 November 2002 01:56, JR wrote:
**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
REPLY: Hi JR, from the Above mention information your problem for Konqueror not working is a DNS issue, you see Web browsers usually do a DNS lookup before going to look for a page when you type the URL. Maybe the DNS servers provided by your ISP are not working properly, try the following command: #nslookup you will get a prompt = ">" At the prompt type:
207.139.84.34 You should get something like:
34.84.139.207.in-addr.arpa name = netsystemsinfo.com. 34.84.139.207.in-addr.arpa name = dns1.netsystemsinfo.com.
if you do not get this type of reply modify your resolv.conf file: comment out everything and add the following line:
#search tampabay.rr.com #nameserver 65.32.1.80 #nameserver 65.32.2.136 nameserver 207.139.84.34
Save the file, and now do again nslookup command but this time we try something we are all familiar with: #nslookup
www.netscape.com Server: 10.1.0.4 Address: 10.1.0.4#53
www.netscape.com canonical name = netscape.com. Name: netscape.com Address: 64.12.180.22 Name: netscape.com Address: 64.12.151.211 Name: netscape.com Address: 64.12.151.215 Name: netscape.com Address: 64.12.180.19
You should see something like this. If you do the open Konqueror try to browse it should work. The solution then is to ask you provider for DNS servers that resolv properly for your address.
2) My RAID drives only have Windows insalled on them and lots of data.
my /var/log/boot.msg information is attached as a .txt file and zipped to save download time.
3) more info about my scsi linux:/home/jamruh # ls /proc/scsi . .. aic7xxx ide-scsi scsi sg
linux:/home/jamruh # cat /proc/scsi/scsi Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: OnStream Model: DI-30 Rev: 1.08 Type: Sequential-Access ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: PIONEER Model: DVD-RW DVR-103 Rev: 1.55 Type: CD-ROM ANSI SCSI revision: 02
linux:/home/jamruh # lspci -vv | grep SCSI 00:0c.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
REPLY: For your disks, can you send me a printout of the /etc/fstab file
Thanks
Vic - ---------------------------------------------------------------------------
NetSystems Info Inc. 164 rue Ideal St-Eustache, Quebec J7P !R3, CANADA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE9z8I93GpaTL3AppcRAkFeAJ99Qy7pbIaQToWqxYlfEx8+oikWHQCgwpQK F1QFYVwkz42pvtPxK/WrV1U= =rIKW -----END PGP SIGNATURE-----
-- 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
Here is the information that I received from nslookup and from the fstab.
***nslookup info nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing.
207.139.84.34
;; connection timed out; no servers could be reached
207.139.84.34
Server: 65.32.1.80 Address: 65.32.1.80#53
Non-authoritative answer: 34.84.139.207.in-addr.arpa name = netsystemsinfo.com.
Authoritative answers can be found from: 84.139.207.in-addr.arpa nameserver = ns.InterLink.NET. 84.139.207.in-addr.arpa nameserver = ns.RezoNet.NET. ns.RezoNet.NET internet address = 198.168.54.8
www.netscape.com
;; connection timed out; no servers could be reached REPLY: JR I think I was not clear: Do the following command: #nslookup
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 11 November 2002 13:01, JR wrote: then type: server 207.139.84.34 then type: www.netscape.com send me the output... - --------------------------------------------------------------------------------------------------------
-
***fstab info /dev/hda4 / ext3 defaults 1 1 /dev/hda1 /boot ext3 defaults 1 2 /dev/hda3 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrecorder1 /media/cdrecorder1 auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 REPLY Vi /etc/fstab file system and then comment the following line:
/dev/hda5 /windows/c vfat defaults 0 0 /dev/hda6 /windows/d vfat defaults 0 0 /dev/hdc1 /windows/e vfat defaults 0 0 /dev/hdc5 /windows/f vfat defaults 0 0
They should look like : # /dev/hda5 /windows/c vfat defaults 00 #/dev/hda6 /windows/d vfat defaults 00 #/dev/hdc1 /windows/e vfat defaults 00 #/dev/hdc5 /windows/f vfat defaults 00 Now when the system will boot it will not try to mount this filesystems.. Regards - -------------------------------------------------------------------------------------------------- NetSystems Info Inc. 164 rue Ideal St-Eustache, Quebec J7P !R3, CANADA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9z/Ug3GpaTL3AppcRAmxrAJoC+GQXxOV3MoaE4vh4IQTDnVJDCwCfQuUc iemGwPl5e4C37dkvCKoI3MM= =TgvR -----END PGP SIGNATURE-----
Here is the information that you requested. # nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing.
server 207.139.84.34 Default server: 207.139.84.34 Address: 207.139.84.34#53 www.netscape.com ;; connection timed out; no servers could be reached
------------ As for the partitions that you asked me to remark out. I have no problem with those partitions. The partitions that I am having problems with do not show up in fstab. They are my hde, hdf, hdg, hdh drives. The networking problem I never had before doing the fresh install of 8.1. When using 8.0 there was no problem at all, since everything was setup correctly during the install. Would you have any idea as to why it would be such a problem now? And here I thought that a fresh install of 8.1 would be the safest way to go. :-( Oh well. At least I am learning. :-) Thank you for all of the assistance. James Ruhsam *********** REPLY SEPARATOR *********** On 11/11/2002 at 1:21 PM Victor Mendez wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Here is the information that I received from nslookup and from the fstab.
***nslookup info nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing.
207.139.84.34
;; connection timed out; no servers could be reached
207.139.84.34
Server: 65.32.1.80 Address: 65.32.1.80#53
Non-authoritative answer: 34.84.139.207.in-addr.arpa name = netsystemsinfo.com.
Authoritative answers can be found from: 84.139.207.in-addr.arpa nameserver = ns.InterLink.NET. 84.139.207.in-addr.arpa nameserver = ns.RezoNet.NET. ns.RezoNet.NET internet address = 198.168.54.8
www.netscape.com
;; connection timed out; no servers could be reached REPLY: JR I think I was not clear: Do the following command: #nslookup
On Monday 11 November 2002 13:01, JR wrote: then type: server 207.139.84.34 then type: www.netscape.com send me the output...
- ---------------------------------------------------------------------------
-
***fstab info /dev/hda4 / ext3 defaults 1 1 /dev/hda1 /boot ext3 defaults 1 2 /dev/hda3 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbdevfs /proc/bus/usb usbdevfs noauto 0 0 /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrecorder1 /media/cdrecorder1 auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 REPLY Vi /etc/fstab file system and then comment the following line:
/dev/hda5 /windows/c vfat defaults 0 0 /dev/hda6 /windows/d vfat defaults 0 0 /dev/hdc1 /windows/e vfat defaults 0 0 /dev/hdc5 /windows/f vfat defaults 0 0
They should look like : # /dev/hda5 /windows/c vfat defaults 00 #/dev/hda6 /windows/d vfat defaults 00 #/dev/hdc1 /windows/e vfat defaults 00 #/dev/hdc5 /windows/f vfat defaults 00
Now when the system will boot it will not try to mount this filesystems..
Regards - ---------------------------------------------------------------------------
NetSystems Info Inc. 164 rue Ideal St-Eustache, Quebec J7P !R3, CANADA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE9z/Ug3GpaTL3AppcRAmxrAJoC+GQXxOV3MoaE4vh4IQTDnVJDCwCfQuUc iemGwPl5e4C37dkvCKoI3MM= =TgvR -----END PGP SIGNATURE-----
-- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 12 November 2002 13:55, JR wrote:
Here is the information that you requested.
# nslookup Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing.
server 207.139.84.34
Default server: 207.139.84.34 Address: 207.139.84.34#53
www.netscape.com
;; connection timed out; no servers could be reached
------------
As for the partitions that you asked me to remark out. I have no problem with those partitions. The partitions that I am having problems with do not show up in fstab. They are my hde, hdf, hdg, hdh drives.
The networking problem I never had before doing the fresh install of 8.1. When using 8.0 there was no problem at all, since everything was setup correctly during the install. Would you have any idea as to why it would be such a problem now? And here I thought that a fresh install of 8.1 would be the safest way to go. :-( Oh well. At least I am learning.
:-)
Thank you for all of the assistance. James Ruhsam REPLY: I just received a verison of SuSE Professional 8.1, I will have one of my guy's install it on a test machine, and then verify the Installation.
We do not use any Unix/linux machines to talk directrly to the Internet we use hardware firewalls in between, but we have a Cable modeml ink to test I will make shure that the Kinternet is set and tested. and then I will provide you with my results. Another thing do you have a firewall installed on the Linux box??? if yes what is the configuration. It is not normal that DNS reply's are not accepted, either you have firewall that is blocking DNS or your IP stack is completly buggy which I doubt. I'm in CANADA and it is 15:40 EST an today I have a few meetings with customers I should have and answer for you tomorrow morning regarding the Kinternet, about your disk I will look again at the info you send me and I will reply tomorrow. Thanks Victor - -------------------------------------------------------------------------------------------------- NetSystems Info Inc. 164 rue Ideal St-Eustache, Quebec J7P !R3, CANADA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE90Wgr3GpaTL3AppcRAmYUAJ4otE70JLD9w9FNZLth69THev5DMwCdEMNT Fs0EoZp3gvrI02q+z7tZa6A= =gqb2 -----END PGP SIGNATURE-----
participants (2)
-
JR
-
Victor Mendez