-
This is minor now that I’ve found a fix for it, 11.1 would install fine, but when it would load up all I would get is a black screen (the monitor would stay on). Although from reading it seems it’s a problem with the X11 drivers. I solved it by, during the install, choosing to set up the graphics related choices myself (however this is not possible with the LiveCD unless I boot it up as failsafe). I have an Nvidia 8800GTX.
-
No sound. I can’t get sound at all with my M-Audo Delta 1010LT. Suse detects the card but I can’t get sound output.
-
Worst of all, no internet. I have no idea what to do. I can’t get 11.1 to detect my internet connection. Whenever I try to go to any website, I immediately get a website could not be found error.
audio
SDB:AudioTroubleshooting - openSUSE
In suse open a terminal and type su then your root password
now type
lspci -v
paste it all here
I would gladly do that if I could get video.
Right now I’m hanging out in Vista.
try this:
Pause the boot by moving the down arrow, then back up to the default boot. But now press backspace, it should delete any text where you can see VGA=.
Remove all text and now type just the number:
3
and hit enter
at the login type your user name and then password
now type:
su
then the root password
now type this:
sax2 -r -m 0=vesa
reboot and see if either default boot or failsafe get you in
if you end up a cli login - login and then try
startx
Got the video working. In terms of importance though, I would say getting an internet connection working is of more importance than audio. Any tips?
Got the video working. In terms of importance though, I would say getting an internet connection working is of more importance than audio. Any tips?
We have no information to help us to help you. If you have a wired Ethernet card, this tutorial should help:
HowTo Configure a network card in Suse/openSUSE 10, 11 for LAN and Internet Access.
But if it’s not a wired card or if it’s a wireless problem then we’ll need to know what your internet connection/setup is, what you’ve tried and what happened when you tried it.
I have an Intel D975XBX2 motherboard and I’m using the Ethernet port on it, which goes to an external DSL modem (Motorola 2210) running on AT&T’s 3MBPS DSL service.
I honestly don’t know what to try. 
That modem has a DHCP server built into the modem. You connect the ethernet cable between the ethernet ports on the computer and the modem and reboot the machine. Then open a terminal window and type/enter these three commands:
1:
su
to become root user then
2:
ifconfig
to see if you got an IP address.
3:
cat /etc/resolv.conf
to see how far the auto configuration got.
Copy the dialogue from 2 and 3 back here.
chris@beryllium:~> su
Password:
beryllium:/home/chris # ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:D1:21:DF:E7
inet addr:192.168.1.64 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::219:d1ff:fe21:dfe7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:259 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17490 (17.0 Kb) TX bytes:5577 (5.4 Kb)
Memory:e3100000-e3120000
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:96 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6464 (6.3 Kb) TX bytes:6464 (6.3 Kb)
beryllium:/home/chris # cat /etc/resolv.conf
/etc/resolv.conf file autogenerated by netconfig!
Before you change this file manually, consider to define the
static DNS configuration using the following variables in the
/etc/sysconfig/network/config file:
NETCONFIG_DNS_STATIC_SEARCHLIST
NETCONFIG_DNS_STATIC_SERVERS
NETCONFIG_DNS_FORWARDER
or disable DNS configuration updates via netconfig by setting:
NETCONFIG_DNS_POLICY=’’
See also the netconfig(8) manual page and other documentation.
Note: Manual change of this file disables netconfig too, but
may get lost when this file contains comments or empty lines
only, the netconfig settings are same with settings in this
file and in case of a “netconfig update -f” call.
Please remove (at least) this line when you modify the file!
nameserver 192.168.1.254
beryllium:/home/chris #
Your network card is working in Linux because it’s receiving an IP address (192.168.1.64) from the DHCP server in the modem.
I think now that you should configure the Name Servers. By this I mean you tell openSUSE networking the IP addresses of the computers provided by your ISP where Internet names (like www,google.com) are resolved to IP addresses (like Google’s IP [in Oz] is 74.125.19.103). That’s the final link.
So go to Yast → Network Devices → Network Settings → Hostname/DNS and fill in your ISP’s IP addresses in the slots “Name Server1” and “Name Server2”.
In essence you’re shooting for “Dynamic IP Setup II - Manually set Gateway & Name Resolution” as described in this tutorial: HowTo Configure a network card in Suse/openSUSE 10, 11 for LAN and Internet Access.
I call it “DHCP on steroids” and you follow these screenshots: Pics 1, 2, 5, 6, 7 and 8.
You get the IP addresses of your ISP’s Name Resolvers from their website. The gateway looks like 192.168.1.254 but you can double check that in windows: boot windows and GoTo Start → Run → cmd. A command window opens. Enter this: ipconfig/all. Check the gateway and use it in Linux. There’s a screenshot on this link.
I think that once using DHCP the chances that you should configure the DNS servers yourself are pretty small. But anyway… Have you configured any SuSEfirewall? If yes, just stop it and then see if you can point your browser to any url you would like.
Hate to sound thick but you kind of lost me… For one my ISP doesn’t supply me with just two IPs… it’s dynamic, every day it’s a completely different IP address. That would be impossible.
Hopefully these help:
http://img18.imageshack.us/img18/2284/dsff.jpg
http://img516.imageshack.us/img516/6861/fdgf.jpg
http://img516.imageshack.us/img516/2807/gftg.jpg
Ugh… I should go to bed, it’s getting late. :FIM:
On Fri February 20 2009 10:46 pm, TV-VCR wrote:
>
> swerdna;1947188 Wrote:
>> So go to Yast → Network Devices → Network Settings → Hostname/DNS
>> and fill in your ISP’s IP addresses in the slots “Name Server1” and
>> “Name Server2”.
> Hate to sound thick but you kind of lost me… For one my ISP doesn’t
> supply me with just two IPs… it’s dynamic, every day it’s a completely
> different IP address. That would be impossible.
>
> Hopefully these help:
> http://img18.imageshack.us/img18/2284/dsff.jpg
> http://img516.imageshack.us/img516/6861/fdgf.jpg
> http://img516.imageshack.us/img516/2807/gftg.jpg
>
> Ugh… I should go to bed, it’s getting late. :FIM:
>
>
TV-VCR;
Even if the IP assigned to you by your ISP changes, the address of their DNS
server(s) remains the same. Your ISP or IT department should be able to
provide you with the IPs of their DNS server(s).
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
With eth0 I never have to do anything - It just works from default DHCP, all I ever do is take out IPv6. For you being dynamic IP you have to use DHCP. I personally have a static IP but still use DHCP.
My Laptop is Networkmanager Controlled - so everything is done from there. And it works perfectly.
Of course whatever device that connects via your router will likely need to have it MAC added in the allowed devices (if that setup exists in your router). And depending on the router - you may configure a fixed LAN IP for each device.
The first pic:
Name Servers (1 and 2) have nothing to do with your IP address nor with the dynamic IP address assigned by your ISP to your DSL modem. Name Servers are the repositories of the addresses of all the web sites on the entire internet. If you can’t contact your name servers, you can’t see anything on the internet. Mostly that’s taken care of automatically – but in some rare cases, and perhaps yours is one, you have to tell your computer what are the IP addresses of the Name Servers. Your ISP proclaims those IP addresses on their web site. Once you have entered the IP addresses on Pic 1, you will know if Name Servers were the problem, or if it is something else. So find them out and put them in.
The second pic:
Looks good – provided you checked for the same Ip address in a windows machine, perhttp://forums.opensuse.org/newreply.php?do=newreply&p=1947368haps your brother’s, using the method I described earlier in post #10 with the screenshot linked in.
The third pic: take the ckeckmark out of “enable ipv6”.
Hope you slept well.
I’m with swerdna on the solution to this one, but there are a couple of ways that you can make this work. But, given a bit of confusing iformation earlier in the thread, I’m going to try to be crystal clear (bet I don’t succeed 
).
When people refer to their ISP giving them an IP or a dynamic IP, the IP that they are referring to is the external facing IP given to their modem/router. It is not the IP of a box internal to their network, and in the usual circumstance, couldn’t be. Normally, you use unroutable addresses on your internal network (eg 192.168.this.that) and your ISP neither knows nor cares about that.
Using DHCP, your modem router gives out these internal IPs. You don’t have to use DHCP, of course, but, for the lazy (and, err, me), DHCP can make things easier. If you are using mdns/Avahi/Bonjour (essentially, the same thing) you can get more than that out of it, and you can even get it to ‘automagically’ set up to know the IP of the modem/router and know that it will resolve names-to-IPs. (In this set up, your modem/router knows where to go to get names resolved and caches (remembers) recently used look-ups.
Alternatively, if your m/r won’t (or you don’t know how to configure it) do name look ups, you can configure your linux box to contact your ISP directly. In this case the Linux box has to know your ISP’s nameserver IP/IPs and for every look up it sends out a ‘get me the corresponding IP’ direct to your ISP.
Normally, the ISP will do a lot of the config of your m/r (either via DHCP or a PPP variant) so you might as well take advantage of that, unless the ISP’s nameservers are unreliable. Normally there are two (used to be called primary and secondary, although those aren’t the modern names; in any case, if the primary is slow, you query the secondary; if both are slow, you performance suffers).
To check that look ups work, you want the command line; ‘dig’ (‘dig Google’, for example) tells you what is going on. Normally, the best first check is to ping a website by IP and by URL; if both work, you look to be in good shape.
Examples
dig www.google.com
; <<>> DiG 9.5.0-P2 <<>> www.google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29021
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 7, ADDITIONAL: 7
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 221509 IN CNAME www.l.google.com.
www.l.google.com. 219 IN A 209.85.229.147
www.l.google.com. 219 IN A 209.85.229.99
www.l.google.com. 219 IN A 209.85.229.103
www.l.google.com. 219 IN A 209.85.229.104
;; AUTHORITY SECTION:
l.google.com. 48821 IN NS g.l.google.com.
l.google.com. 48821 IN NS a.l.google.com.
l.google.com. 48821 IN NS b.l.google.com.
l.google.com. 48821 IN NS c.l.google.com.
l.google.com. 48821 IN NS d.l.google.com.
l.google.com. 48821 IN NS e.l.google.com.
l.google.com. 48821 IN NS f.l.google.com.
;; ADDITIONAL SECTION:
a.l.google.com. 64887 IN A 209.85.139.9
b.l.google.com. 152176 IN A 74.125.45.9
c.l.google.com. 151557 IN A 64.233.161.9
d.l.google.com. 74094 IN A 66.249.93.9
e.l.google.com. 73960 IN A 209.85.137.9
f.l.google.com. 73585 IN A 72.14.235.9
g.l.google.com. 73956 IN A 74.125.95.9
;; Query time: 125 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Feb 21 20:30:22 2009
;; MSG SIZE rcvd: 340
ping -c 10 209.85.229.104
PING 209.85.229.104 (209.85.229.104) 56(84) bytes of data.
64 bytes from 209.85.229.104: icmp_seq=1 ttl=244 time=109 ms
64 bytes from 209.85.229.104: icmp_seq=2 ttl=244 time=120 ms
64 bytes from 209.85.229.104: icmp_seq=3 ttl=244 time=65.3 ms
64 bytes from 209.85.229.104: icmp_seq=4 ttl=244 time=91.5 ms
64 bytes from 209.85.229.104: icmp_seq=5 ttl=244 time=155 ms
64 bytes from 209.85.229.104: icmp_seq=6 ttl=244 time=114 ms
64 bytes from 209.85.229.104: icmp_seq=7 ttl=244 time=167 ms
64 bytes from 209.85.229.104: icmp_seq=8 ttl=244 time=68.0 ms
64 bytes from 209.85.229.104: icmp_seq=9 ttl=244 time=78.2 ms
64 bytes from 209.85.229.104: icmp_seq=10 ttl=244 time=108 ms
--- 209.85.229.104 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9036ms
rtt min/avg/max/mdev = 65.320/107.907/167.429/32.441 ms
ping -c 10 www.google.com
PING www.l.google.com (209.85.229.104) 56(84) bytes of data.
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=1 ttl=244 time=159 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=2 ttl=244 time=116 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=3 ttl=244 time=124 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=4 ttl=244 time=135 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=5 ttl=244 time=180 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=6 ttl=244 time=144 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=7 ttl=244 time=151 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=8 ttl=244 time=142 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=9 ttl=244 time=156 ms
64 bytes from ww-in-f104.google.com (209.85.229.104): icmp_seq=10 ttl=244 time=161 ms
Hope I haven’t overdone this for you, but I was trying to make this clear; apologies if I got it wrong. (And,oh, by the way, looking the stuff that I have posted, I realise my name resolution is set up wrong…c’est la vie!)
Sorry to bump, but I found one solution and there is more info for the audio problem that some may be interested in.
Alongside Fedora I’ve also recently reinstalled OpenSuse. Apparently not being able to connect to the internet was just a simple problem with my ISP’s DNS servers! Upon adding an OpenDNS server to the resolv.conf files, bam, connection.
As for the audio problems, while I know Red Hat isn’t Novell, nonetheless, it’s the same problem.
https://bugzilla.redhat.com/show_bug.cgi?id=506390
Cheers.
I recently found that I was the one at fault here in regards to the connection. In the Network Settings dialog (Hostname/DNS tab) I was forgetting to punch in the servers and their domains - upon adding them, voila, I could connect. What’s odd is that Mandriva was able to add them automatically (I’ve since ditched it though).
I’m still having trouble with not getting any sound. I think it’s just flat out because I’m missing M-Audio drivers or something?
If this is a Box and not a laptop, I know what I would do. Cheap basic sound card.
My sound card and network card are probably about 10yrs old
M-Audio drivers? I don’t know … typically the alsa drivers handle all sound devices.
Your original post was started when I was on vacation - hence I never saw this thread.
You could try working your way through the openSUSE audio troubleshooting guide:
SDB:AudioTroubleshooting - openSUSE
If the guide does not help you, then here is some more info (but try the guide first). …
Note, when testing if you have sound, please copy and paste the following speaker-test into a Gnome terminal or a kde konsole:
speaker-test -Dplug:front -c2 -l5 -twav
Note Linux is case sensitive, and “D” is not the same as “d”. To stop the above test, while the konsole/xterm has the mouse focus, press <CTRL><C> on the keyboard. Note you should check your mixer settings (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and Master Volume are set around 95%. Once you have basic sound established you can back off to lower volume levels. Note the test for surround sound is different.
If that test yields errors (and its not uncommon to get errors there), try instead this more simple test: speaker-test -c2 -l5 -twavYou should hear a female voice saying ‘FRONT LEFT’, ‘FRONT RIGHT’ five times. Its quite common that one of those speaker tests will work and one will NOT work, so don’t be distressed if that is the case. IF that test gives sound, stop now, post that the sound test gives sound, and we will look at other possible causes for your applications not giving you the sound you want (such as missing codecs, using the wrong packaged version … etc … ).
Try those speaker-tests as both a regular user, and also with root permissions. If you have a headset, try with your headset plugged in, and also with your headset not plugged in (for speakers).
Assuming no sound, can you provide more very detailed information so a good recommendation can be given? For openSUSE-11.1, you can do that, with your laptop connected to the internet, by opening a gnome-terminal or a kde konsole and twice copy and paste the following into that terminal/konsole
/usr/sbin/alsa-info.sh
Run it the 1st time with root permissions. It will ask if you wish to do an update of the script. Select YES.
Then run it again (as either a regular user or as root). This time it will diagnose your PC’s hardware and software configuration for audio, and it will post its output on the Internet/web. It will give you the URL of the web site. Please post that URL here. JUST the URL.
Also, please copy and paste the following commands one line at a time into a gnome-terminal or a konsole and post here the output: rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound… with that information I may be able to make a recommendation.