Kernel panic - need help quick - Page 2

onebuck · 01-10-2008, 12:37 PM

Hi,

Quote:

Originally Posted by Alien_Hominid

His ISP might not have given him DNS address because maybe router acts as a DNS resolver.

Possible but not probable here in the U.S. Most ISP don't hide the DNS. You can use whois to find the nameserver for a domain. Even with a router/modem as a resolver there is no reason to not being able to get the IP of the DNS from a ISP.

Rollo69 · 01-10-2008, 08:17 PM

Quote:

Originally Posted by onebuck

Code:

~#ifconfig -a
~#route -n

Please post it.

Hope I do this correctly so here it goes:

Code:

route -n  
Destination  Gateway       Genmask      Flags Metric Ref  Use  Iface
192.168.0.0  0.0.0.0      255.255.255.0  U     0      0    0    eth0
127.0.0.0    0.0.0.0      255.0.0.0      U     0      0    0     lo
0.0.0.0      192.168.0.1  0.0.0.0        UG    1      0    0    eth0

I only wrote some of the ifconfig but is what I wrote:

Code:

ifconfig 
      inet addr 192.168.0.104 Bcast 192.168.0.255 Mask 255.255.255.0
       UP BROADCAST MULTICAST MTU:1500 Metric:1
       Interrupt:19

My slak box went down last night and I can't boot or I would give you the entire ifconfig -a that you asked for. Since it went down I tried the memtest cd but was unable to complete it from what I could tell. I thought I had some extra RAM sticks but unfortunately wrong type/kind.

I did however access the router and it showed a DNS address.

Code:

DNS  24.158.63.28

Google only shows this IP in malware/trojan type sites or forums.

Quote:

onebuck Today 12:37 PM

You can use whois to find the nameserver for a domain. Even with a router/modem as a resolver there is no reason to not being able to get the IP of the DNS from a ISP.

How can I use whois to find the nameserver?? I can't explain the reasoning of this cable company (the only cable internet supplier in my area) not giving me the DNS because I asked for it when they came out and hooked up my internet and cable.

Thanks for your help and is RAM my only culprit for my problem??

edit: Did I use the quotes and codes correctly in this post Onebuck

onebuck · 01-11-2008, 08:57 AM

Hi,

Quote:

Originally Posted by Rollo69

edit: Did I use the quotes and codes correctly in this post Onebuck

Yes! A lot easier for the person reading your post(s)

Quote:

Originally Posted by Rollo69

I did however access the router and it showed a DNS address.

Code:

DNS  24.158.63.28

Quote:

Originally Posted by Rollo69

How can I use whois to find the nameserver?? I can't explain the reasoning of this cable company (the only cable internet supplier in my area) not giving me the DNS because I asked for it when they came out and hooked up my internet and cable.

No one can! Most just use secondary support personnel and these people just move the equipment an are told not to provide information other than what is on the work orders. How I found the info;

Code:

~# ping -c1 24.158.63.28
PING 24.158.63.28 (24.158.63.28) 56(84) bytes of data.
64 bytes from 24.158.63.28: icmp_seq=1 ttl=240 time=75.6 ms

--- 24.158.63.28 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 75.639/75.639/75.639/0.000 ms

~# whois 24.158.63.28
Charter Communications CHARTER-NET-2BLK (NET-24-158-0-0-1)
                                  24.158.0.0 - 24.158.255.255
Charter Communications HKRY-NC-24-158-32 (NET-24-158-32-0-1)
                                  24.158.32.0 - 24.158.63.255

# ARIN WHOIS database, last updated 2008-01-10 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

~# whois CHARTER-NET-2BLK

OrgName:    Charter Communications
OrgID:      CC04
Address:    12405 Powerscourt Dr.
City:       St. Louis
StateProv:  MO
PostalCode: 63131
Country:    US

NetRange:   24.158.0.0 - 24.158.255.255
CIDR:       24.158.0.0/16
NetName:    CHARTER-NET-2BLK
NetHandle:  NET-24-158-0-0-1
Parent:     NET-24-0-0-0-0
NetType:    Direct Allocation
NameServer: NS1.CHARTER.COM
NameServer: NS2.CHARTER.COM
NameServer: NS3.CHARTER.COM
NameServer: NS4.CHARTER.COM
Comment:    ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
Comment:    "For NETWORK ABUSE issues, please email abuse@charter.net"
RegDate:    2001-03-06
Updated:    2004-04-14

RTechHandle: IPADD1-ARIN
RTechName:   IPAddressing
RTechPhone:  +1-314-288-3889
RTechEmail:  ipaddressing@chartercom.com

OrgAbuseHandle: ABUSE19-ARIN
OrgAbuseName:   Abuse
OrgAbusePhone:  +1-314-288-3111
OrgAbuseEmail:  abuse@charter.net

OrgTechHandle: IPADD1-ARIN
OrgTechName:   IPAddressing
OrgTechPhone:  +1-314-288-3889
OrgTechEmail:  ipaddressing@chartercom.com

# ARIN WHOIS database, last updated 2008-01-10 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
~#

I first ping the IP to make sure that it is valid.
I then whois the IP. You then can use the 'whois domain name' to get the information.

Code:

   Domain Name: CHARTER.COM
   Registrar: NETWORK SOLUTIONS, LLC.
   Whois Server: whois.networksolutions.com
   Referral URL: http://www.networksolutions.com
   Name Server: NS1.CHARTER.COM
   Name Server: NS2.CHARTER.COM
   Name Server: NS3.CHARTER.COM
   Name Server: NS4.CHARTER.COM
   Status: clientTransferProhibited
   Updated Date: 16-oct-2006
   Creation Date: 30-jul-1994
   Expiration Date: 29-jul-2011

Quote:

Originally Posted by Rollo69

<snip>

My slak box went down last night and I can't boot or I would give you the entire ifconfig -a that you asked for. Since it went down I tried the memtest cd but was unable to complete it from what I could tell. I thought I had some extra RAM sticks but unfortunately wrong type/kind.

Google only shows this IP in malware/trojan type sites or forums.

Thanks for your help and is RAM my only culprit for my problem??

When you boot the memtest86, do you start the test? If not just swap the sticks, rotate them. Meaning that you move position 0 to 1 and 1 to 0. That is if you only have two slots. If three then the order would involve that number of positions. I like to clean the edge(s) when at this level.

You should first use good ground techniques, either with a grounding wrist strip or at least placing yourself at the the same potential level as the system by maintaining contact with the equipment.

I would shut the power off to the system. Clean the card edge for the memory using strips of new 20# paper wet with alcohol. Swipe in one direction with folded wet paper for the edge, a new piece for each swipe. You can use a credit card to clean the connector if that is needed by folding the paper over the end of the credit card. But first you should use dry air to blow the connector out. In the USA it can be purchased at most computer/office supply houses, even Walmart has it. Then replace the card without touching the card edge. BTW, don't use a eraser to clean/buffer the card edge. You are doing more harm then good.

If you do have a ram problem then Yes replacement will be the solution.

Your Welcome!

Rollo69 · 01-11-2008, 11:48 PM

Quote:

Originally Posted by onebuck

When you boot the memtest86, do you start the test? If not just swap the sticks, rotate them. Meaning that you move position 0 to 1 and 1 to 0. That is if you only have two slots. If three then the order would involve that number of positions. I like to clean the edge(s) when at this level.

Memtest does start a boot up and doesn't complete test. It does state a lot of errors.

Quote:

Originally Posted by onebuck

You should first use good ground techniques, either with a grounding wrist strip or at least placing yourself at the the same potential level as the system by maintaining contact with the equipment.

I would shut the power off to the system. Clean the card edge for the memory using strips of new 20# paper wet with alcohol. Swipe in one direction with folded wet paper for the edge, a new piece for each swipe. You can use a credit card to clean the connector if that is needed by folding the paper over the end of the credit card. But first you should use dry air to blow the connector out. In the USA it can be purchased at most computer/office supply houses, even Walmart has it. Then replace the card without touching the card edge. BTW, don't use a eraser to clean/buffer the card edge. You are doing more harm then good.

If you do have a ram problem then Yes replacement will be the solution.

I built this system using an older mobo (AOpen) w/ intel celeron 1.8 cpu. I do only have to slots for ram. I tried cleaning the ram with dry q-tip (no alcohol, don't have any here) and switching positions yesterday. I also reset CMOS. When I powered back up and start boot process but system started beeping so powered down and switched back to original positions. It does start boot process, lilo loads, but want load up completely. I used the chassis of the tower to ground myself. I don't have a wrist strap to ground myself. I learned that in computer repair classes. I wasn't aware of using 20# paper w/ alcohol. I knew about the eraser. I think we used cotton and alcohol , if memory serves me well. I will have to try cleaning the connector(s) on mobo to see if that may be culprit, otherwise ram shopping I will have to do.

Thanks again and will let you know the out come.

onebuck · 01-12-2008, 08:55 AM

Hi,

If you use cotton/swabs lint can be left on the connector. You can purchase special cotton swaps that are made for electronics work that are tight wraps but these should be used one per wipe. Another type has a sponge wrap over the cotton. Rather expensive.

The rag content of 20# paper is sufficient to clean the connector when wet. That is why you wipe in one direction and use the paper once per wipe. I cut the paper in one inch wide strips with the paper folded in half length wise twice then cut at folds. You could use isopropyl but I prefer a good methyl alcohol.

Be sure to use dry air to clean out the MB connector before attempting to wipe it with paper and a credit card.

As for the problem with the swap of memory positions. Try with one stick at a time to see if you can identify a problem stick. What were the errors and address for the memtest86? This would indicate the problem address area. You could have a MB issue.

BTW, did you try the BIOS defaults to see if the timing for the memory has been modified. Be sure to write the timing settings down before reset.