Re: [SLE] Card Hell (Was network hell)
At 01:29 PM 5/2/2002 +0100, you wrote:
Well if it really is a virgin install, why not do the reinstall he suggests. You've already lost 2 hours on the phone, why not risk 20 minutes and see if it works better this time with the card out. Unless the install was particularly hard first time round, I don't think his idea is all that mad.
Actually I agree, but since I'm trying to learn about Linux this seems a very Windoweez way of going about it. Something don't work? Reinstall the entire operating system! But I take your point. Of more concern was my distinct impression that the suse tech, while a VERY nice guy, seemed a bit lost. For example, not once did he ask me for the output of ifconfig. For example. It is: 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: 54 errors:0 dropped:0 overruns:0 frame:0 TX Packets: 54 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX Bytes: 3784 TX Bytes: 3784
The other respondents could help you more than I can with the rest, I think. Hope the problem is solving itself by now,
Not at all. Thanks in advance, everyone.
A couple of things bothered me about Nick's posts. First, the necessity of rebooting the system. In Linux and Unix systems there are very few reasons why a system needs to be rebooted. Possibly the card services thing may have assigned the installed NIC on eth1 and the PC card onto eth0. In that case, I might suggest a reboot. But, changing most networking information generally requires simply a quick reconfiguration. YaST normally handles this. Certainly, if you want to run a new kernel, you need to reboot. But even if you want to change a driver, simply unload the module (if it is loaded), and load the new module. Even if X is screwing up, if you can get to a virtual terminal (ctl-alt-f[1-6]). Log in as root and telinit 3 (to shut off X until you can fix the problem). There are some other reasons. I have seen X grab the mouse and keyboard in such a manner that the only thing you can do is power off. The other is reinstall. If you really messed up the installation, then that might be a solution, but with most modern Linux distros, you can easily remove and add packages. With YaST, it is relatively simple to change your network configuration. We hold our monthly LUG meetings at MIT where we have a static IP. After I boot my laptop, I simply reconfigure the network with the static IP assigned to that classroom. (BTW: I've spent many hours in network hell as well as various code management systems hell :-) On 2 May 2002 at 15:13, Nick Selby wrote:
Actually I agree, but since I'm trying to learn about Linux this seems a very Windoweez way of going about it. Something don't work? Reinstall the entire operating system! But I take your point. Of more concern was my distinct impression that the suse tech, while a VERY nice guy, seemed a bit lost. For example, not once did he ask me for the output of ifconfig. For example.
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
At 09:31 AM 5/2/2002 -0400, you wrote:
A couple of things bothered me about Nick's posts. First, the necessity of rebooting the system. In Linux and Unix systems there are very few reasons why a system needs to be rebooted. Possibly the card services thing may have assigned the installed NIC on eth1 and the PC card onto eth0. In that case, I might suggest a reboot. But, changing most networking information generally requires simply a quick reconfiguration.
That was my suspicion, and the main reason I am hesitant to make the clean reinstall: I just made a clean install on a spanking new hard drive; the thing SEES my ethernet card; there should be no reason it cannot be configured. Except I don't know how. Or even where to start.
YaST normally handles this. Certainly, if you want to run a new kernel, you need to reboot. But even if you want to change a driver, simply unload the module (if it is loaded), and load the new module. Even if X is screwing up, if you can get to a virtual terminal (ctl-alt-f[1-6]). Log in as root and telinit 3 (to shut off X until you can fix the problem). There are some other reasons. I have seen X grab the mouse and keyboard in such a manner that the only thing you can do is power off.
The other is reinstall. If you really messed up the installation, then that might be a solution, but with most modern Linux distros, you can easily remove and add packages.
With YaST, it is relatively simple to change your network configuration. We hold our monthly LUG meetings at MIT where we have a static IP. After I boot my laptop, I simply reconfigure the network with the static IP assigned to that classroom.
(BTW: I've spent many hours in network hell as well as various code management systems hell :-)
On 2 May 2002 at 15:13, Nick Selby wrote:
Actually I agree, but since I'm trying to learn about Linux this seems a very Windoweez way of going about it. Something don't work? Reinstall the entire operating system! But I take your point. Of more concern was my distinct impression that the suse tech, while a VERY nice guy, seemed a bit lost. For example, not once did he ask me for the output of ifconfig. For example.
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
it sees your ethernet card? does that mean it loads the module for it? do the following /sbin/lscpi | grep Ethernet what is the output? do /sbin/lsmod what is the output do /sbin/ifconfig what is the output paste the output of each of those into an email and either i or someone else will have you working in a few minutes. On Thursday 02 May 2002 08:49 am, Nick Selby wrote:
At 09:31 AM 5/2/2002 -0400, you wrote:
A couple of things bothered me about Nick's posts. First, the necessity of rebooting the system. In Linux and Unix systems there are very few reasons why a system needs to be rebooted. Possibly the card services thing may have assigned the installed NIC on eth1 and the PC card onto eth0. In that case, I might suggest a reboot. But, changing most networking information generally requires simply a quick reconfiguration.
That was my suspicion, and the main reason I am hesitant to make the clean reinstall: I just made a clean install on a spanking new hard drive; the thing SEES my ethernet card; there should be no reason it cannot be configured.
Except I don't know how. Or even where to start.
YaST normally handles this. Certainly, if you want to run a new kernel, you need to reboot. But even if you want to change a driver, simply unload the module (if it is loaded), and load the new module. Even if X is screwing up, if you can get to a virtual terminal (ctl-alt-f[1-6]). Log in as root and telinit 3 (to shut off X until you can fix the problem). There are some other reasons. I have seen X grab the mouse and keyboard in such a manner that the only thing you can do is power off.
The other is reinstall. If you really messed up the installation, then that might be a solution, but with most modern Linux distros, you can easily remove and add packages.
With YaST, it is relatively simple to change your network configuration. We hold our monthly LUG meetings at MIT where we have a static IP. After I boot my laptop, I simply reconfigure the network with the static IP assigned to that classroom.
(BTW: I've spent many hours in network hell as well as various code management systems hell :-)
On 2 May 2002 at 15:13, Nick Selby wrote:
Actually I agree, but since I'm trying to learn about Linux this seems a very Windoweez way of going about it. Something don't work? Reinstall the entire operating system! But I take your point. Of more concern was my distinct impression that the suse tech, while a VERY nice guy, seemed a
bit
lost. For example, not once did he ask me for the output of ifconfig. For example.
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Compaq Computer Corp. 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Chad Whitten Network/Systems Administrator neXband Communications cwhitten@nexband.com
At 09:11 AM 5/2/2002 -0500, you wrote:
it sees your ethernet card? does that mean it loads the module for it? do the following /sbin/lscpi | grep Ethernet
...
paste the output of each of those into an email and either i or someone else will have you working in a few minutes.
Thanks for this. As soon as I get the new hard drive RE-installed (this is so much fun!) I'll do those and send it. Your message warms my heart!!!! Nick
WOW!! I restarted I went into YAST2 I re-entered what I thought should be the right IP addresses I got to the internet. The machine can see the network, and get out! Small problems remaining: 1) When the Notebook reboots, i see something like this eth0 (DHCP) . . . . .No IP yet, waiting I can ping the gateway but not the windows machine (192.168.10.1) on the network. When I go to a shell console, I see the following: nick@(none):~> This seems to tell me that I haven't set the domain or the "search" properly, is that right? Which brings me to 2) My windows machine on the same network - which also has internet access through the same gateway - cannot ping the new notebook. Which would be okay, except the windows machne has the /home/nick directory of the notebook mapped. And cannot access it. Can anyone tell me what I need to tell you to have you help me straighten these last pieces of the puzzle out? Thanks! NIck At 04:22 PM 5/2/2002 +0200, you wrote:
At 09:11 AM 5/2/2002 -0500, you wrote:
it sees your ethernet card? does that mean it loads the module for it? do the following /sbin/lscpi | grep Ethernet
...
paste the output of each of those into an email and either i or someone else will have you working in a few minutes.
Thanks for this. As soon as I get the new hard drive RE-installed (this is so much fun!) I'll do those and send it. Your message warms my heart!!!!
Nick
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
participants (3)
-
Chad Whitten -
Jerry Feldman -
Nick Selby