I’ve been a Windows user for a long time now. I know it quite well, and so have decided to venture into Linux territory. From alot of distro’s that i’ve tried, OpenSUSE speaks to me the most.
Anyway, considering that i’m a noob at Linux (especially in regards to syntax/command lines) i’m trying my best.
So, i’ve installed OpenSUSE 11 (with latest KDE --is it 3.5 or 4.0…I forgot…). The interface is pleasent and relatively easy to figure out.
So, i’ve configured my network card (IP address, Subnet Mask, Default Gateway and DNS addresses)…everything is set up fine, and I should be able to browse the internet (via my DSL modem) and browse my home network (will need to configure Samba).
The only issue is that the system registers my ethernet controller as (Not Connected).
For the sake of eliminating possible problems, i’d disabled the firewall.
I don’t know why it’s not working, and I have no idea how to proceed from here. At least if I can get the internet working in OpenSUSE, then I can manage and learn how to use it more from there…but booting back into Windows and then booting back to OpenSUSE is cumbersome.
Let’s have a look at a few diagnostics. Open a console and enter su to get root’s powers. Then enter these four commands and copy/paste the dialogue back here in a reply:
cat /etc/resolv.conf
ifconfig
iwconfig
route
Also, how did you add the configuration? From the command line or in Yast?
That might get the ball rolling.
I’ll give the advice a go. After I post this, i’ll boot into OpenSUSE and check what’s up.
As for the network configurations, I did not configure via command line; it was via Yast (via the KDE GUI).
…usually i’m quite literate with computers; especially Windows…but Linux is pretty new to me…so I feel a little silly/unprepared. But, i’m hoping to get good at this too.
The dialogue you get says that prima facie you should be connected (and hold and below you are!)
Regarding “why the error”, I’ve got three candidates:
1: Check in Yast –> System Services –> Runlevels –> expert (might have to wait there for up to 2 mins for a Suse 11.0 bug to clear) –> check the network is set to start at runlevels 2 3 and 5 (but I don’t think that’s the problem).
2: It was a Rainy Day In Georgia (but I don’t like that answer either)
3: It was … hmmmmm… (I like this one the best).
Hello! I am also a new user to suse as well as linux. I got tired of windows and think it’s about time I started learning a real OS! Please go slow as I know little to nothing about linux. I’ll do the best I can.
As for my problem, I have a similar one. I did those commands and I got the following:
linux-pkzu:/home/rich # cat /etc/resolv.conf
domain site
linux-pkzu:/home/rich # iwconfig
lo no wireless extensions.
>
> Hello! I am also a new user to suse as well as linux. I got tired of
> windows and think it’s about time I started learning a real OS! Please
> go slow as I know little to nothing about linux. I’ll do the best I
> can.
>
> As for my problem, I have a similar one. I did those commands and I got
> the following:
>
> linux-pkzu:/home/rich # cat /etc/resolv.conf
> domain site
>
> linux-pkzu:/home/rich # iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> linux-pkzu:/home/rich # ifconfig
> lo 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:240 errors:0 dropped:0 overruns:0 frame:0
> TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:16496 (16.1 Kb) TX bytes:16496 (16.1 Kb)
>
> linux-pkzu:/home/rich # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> loopback * 255.0.0.0 U 0 0 0
> lo
>
> Is that of any help? I want to setup my wireless card. From there, I
> can start to remotely install packages and really get into suse 11.
>
> Thanks
>
>
You REALLY should start a new thread for your problems, since you won’t
likely get the attention you deserve by piggybacking onto someone else’s
problem.
Based on what you’ve posted though… you don’t even HAVE a wireless network
adapter installed in the system.