FW: [SLE] Urgent! Need help!
-----Original Message----- From: Greg Wallace [mailto:jgregw@acsalaska.net] Sent: Thursday, August 19, 2004 4:47 PM To: suse-linux-e@suse.com Subject: FW: [SLE] Urgent! Need help!
On Thursday, August 19, 2004 @ 12:06 AM Richard wrote
On Wednesday 18 August 2004 06:23 pm, Greg Wallace wrote:
1) Start boot 2) Show the Windows startup screen 3) flash the BIOS 4) Restart 5) go through 1-4 again (though sometimes it doesn't restart but simply shows the Windows startup screen again immediately after the previous flash.
How much memory do you have in that machine?? If you're running win98 and
have over 1gig ram, that can cause the problem! Win 98 will choke big time
when you get to much ram. Happened to me with 1.3 Gigs. reducing to less
than 1 G stopped the constant reboot.
Drove me nuts! RA
Forget everything I said about this. I was not doing the recovery in the proper manner (I'd never done one). I ended going back to square one and trying again and this time I deciphered the ASR recovery process correctly and it worked perfectly (and quickly).
Greg Wallace
Well, Stanley, you've really done it this time! I just went in to re->format my USB drive and instead of deleting the NTFS partition, I deleted both that and the EISA header! I now have a disk with absolutely nothing on it! Will I have to take this drive into someone to get a new disk header put on it or can I add an EISA header to it from my Windows machine?
Yours truly, Greg Wallace
What an idiot I am! I moved my backup to this EFG80 device via ftp. All I have to do is connect to it and ftp my backup back down to my Linux machine! Actually, I'd have already done it already, but I can't get back on my network. I'm REALLY back to square one! I went into YAST and started inetd, but that wasn't enough. I still can't get back on my network. I did a plain vanilla install, so do I need to get some additional packages installed before I can get this up and going? I tried simply doing -- Ping 192.168.1.77 (the ip address of my Linksys EFG80 where my backup is) It came back with "Network is unreachable". What do I need to do to get basic networking going again. My machines all connect via a Linksys 4 port Router. Thanks, Greg Wallace
On Thursday 19 August 2004 6:39 pm, Greg Wallace wrote:
What an idiot I am! I moved my backup to this EFG80 device via ftp. All I have to do is connect to it and ftp my backup back down to my Linux machine! Actually, I'd have already done it already, but I can't get back on my network. I'm REALLY back to square one! I went into YAST and started inetd, but that wasn't enough. I still can't get back on my network. I did a plain vanilla install, so do I need to get some additional packages installed before I can get this up and going? I tried simply doing --
Ping 192.168.1.77 (the ip address of my Linksys EFG80 where my backup is)
It came back with "Network is unreachable". What do I need to do to get basic networking going again. My machines all connect via a Linksys 4 port Router.
Check the settings of your network card. Rich
Thanks, Greg Wallace
-- C. Richard Matson
On Thursday 19 August 2004 @ 6:15 PM, C. Richard Matson wrote:
On Thursday 19 August 2004 6:39 pm, Greg Wallace wrote:
What an idiot I am! I moved my backup to this EFG80 device via ftp. All I have to do is connect to it and ftp my backup back down to my Linux machine! Actually, I'd have already done it already, but I can't get back on my network. I'm REALLY back to square one! I went into YAST and started inetd, but that wasn't enough. I still can't get back on my network. I did a plain vanilla install, so do I need to get some additional packages installed before I can get this up and going? I tried simply doing --
Ping 192.168.1.77 (the ip address of my Linksys EFG80 where my backup is)
It came back with "Network is unreachable". What do I need to do to get basic networking going again. My machines all connect via a Linksys 4 port Router.
Check the settings of your network card. Rich
Thanks, Greg Wallace
-- C. Richard Matson
I go through a router. I can't even get to the router! And I mean I can't even "Ping" it! I have taken the following steps in YAST. 1) Made sure intetd was up and running 2) Gone to Network Advanced and a) Gone under Host name and DNS and *) Entered my machine name and the Domain Name I'm using in my router. *) Checked "Update name servers and search list via DHCP" b) Gone to Routing and checked "Enable IP forwarding" No luck. I still can't ping my router. I never had this problem before, and I installed from the exact same disk. I did simply take all of the default packages, but I know you don't have to install a special package just to have internet support! This is so aggravating because as soon as I can get on the network and can grab my backup and get my system back. Grrrr! Something sort of amusing about this though -- The default "wallpaper" for Root shows a round back bomb with a burning fuse and a big triangle with an exclamation mark in it. The desktop itself is bright red!! I think Linux is playing games with me!! Greg Wallace
The Friday 2004-08-20 at 01:47 -0800, Greg Wallace wrote:
I go through a router. I can't even get to the router! And I mean I can't even "Ping" it! I have taken the following steps in YAST.
Ping it by IP number, not name. Give exact error, not "it doesn't work".
1) Made sure intetd was up and running 2) Gone to Network Advanced and a) Gone under Host name and DNS and *) Entered my machine name and the Domain Name I'm using in my router. *) Checked "Update name servers and search list via DHCP" b) Gone to Routing and checked "Enable IP forwarding"
No luck. I still can't ping my router. I never had this problem before,
If dhcp doesn't work, your card will not get an IP number, and you will not be able to connect. Give it a fixed IP number, if possible. Then run "ifconfig" to check.
Grrrr! Something sort of amusing about this though -- The default "wallpaper" for Root shows a round back bomb with a burning fuse and a big triangle with an exclamation mark in it. The desktop itself is bright red!! I think Linux is playing games with me!!
That's absolutely correct. You should not work as root, so the red wallpaper just reminds you that you really should not be there. -- Cheers, Carlos Robinson
* Greg Wallace
Grrrr! Something sort of amusing about this though -- The default "wallpaper" for Root shows a round back bomb with a burning fuse and a big triangle with an exclamation mark in it. The desktop itself is bright red!! I think Linux is playing games with me!!
open an xterm window and type: whoami this is the reason for the bright red and the bomb -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 20 August 2004 16:47, Greg Wallace wrote:
On Thursday 19 August 2004 @ 6:15 PM, C. Richard Matson wrote:
On Thursday 19 August 2004 6:39 pm, Greg Wallace wrote:
What an idiot I am! I moved my backup to this EFG80 device via ftp. All I have to do is connect to it and ftp my backup back down to my Linux machine! Actually, I'd have already done it already, but I can't get back on my network. I'm REALLY back to square one! I went into YAST and started inetd, but that wasn't enough. I still can't get back on my network. I did a plain vanilla install, so do I need to get some additional packages installed before I can get this up and going? I tried simply doing --
Ping 192.168.1.77 (the ip address of my Linksys EFG80 where my backup is)
It came back with "Network is unreachable". What do I need to do to get basic networking going again. My machines all connect via a Linksys 4
port
Router.
Check the settings of your network card. Rich
Thanks, Greg Wallace
-- C. Richard Matson
I go through a router. I can't even get to the router! And I mean I can't even "Ping" it! I have taken the following steps in YAST.
1) Made sure intetd was up and running 2) Gone to Network Advanced and a) Gone under Host name and DNS and *) Entered my machine name and the Domain Name I'm using in my router. *) Checked "Update name servers and search list via DHCP" b) Gone to Routing and checked "Enable IP forwarding"
As Rich already said: Check the settings of your network card! Can you ping yourself? What is the IP address you get for your network card? Ping to that address. Working? If not, then again: Check the settings of your network card! if it works, then the next question is: Is it on the same network as your device with IP 192.168.1.77 ?
No luck. I still can't ping my router. I never had this problem before, and I installed from the exact same disk. I did simply take all of the default packages, but I know you don't have to install a special package just to have internet support! This is so aggravating because as soon as I can get on the network and can grab my backup and get my system back. Grrrr! Something sort of amusing about this though -- The default "wallpaper" for Root shows a round back bomb with a burning fuse and a big triangle with an exclamation mark in it. The desktop itself is bright red!! I think Linux is playing games with me!!
Open your favorite text editor and write 1000 times: "There is *no* good reason to log into KDE as root. *That* is why I see a red wallpaper with nice bombs if I do so."
Greg Wallace
participants (5)
-
C. Richard Matson -
Carlos E. R. -
Greg Wallace -
Matt T. -
Patrick Shanahan