Page 1 of 1
A few problems
Posted:
Feb 17th, '12, 00:27by Yinepu
I just installed Mageia, and I'm having problems with a few things, so I'll put them all here. I anyone can fix any of them I'd be grateful!
1) I can't connect to my wifi network
2) My screen resolution doesn't go higher than 1024x768
Re: A few problems
Posted:
Feb 17th, '12, 00:59by djennings
1) I can't connect to my wifi network
Start here
viewtopic.php?f=7&t=1877
Re: A few problems
Posted:
Feb 17th, '12, 01:10by Yinepu
Well, I followed those instructions and it's still not working. It might be I'm putting the configuration in wrong. I don't know what the operating mode is, but I've tried all of them and it still fails to connect.
Re: A few problems
Posted:
Feb 17th, '12, 05:53by tleedavidson
You will need to know the Operating Mode to be able to configure the connection correctly. If the WIFI network is your own home network, as the word "my" which you used suggests, then you are in control of the WIFI configuration including the operating mode. If the WIFI is provided by someone else, then you should be able to get the operating mode and the rest of the configuration information from them. The operating mode is most likely Managed. You will also need to know the Encryption Mode, and the Encryption Key if the E. Mode is anything other than None.
I had problems with the sound out of the SoundBlaster card on my desktop. I was able to fix that by opening a console window (Konsole) and launching alsamixer. Using the appropriate key, I navigated to the Digital Output channel and disabled/muted it. That fixed it. I've had to do that only once again since then. When I was researching this problem, I read that disabling PulseAudio might help. But it did not in my situation.
Executing lspci from a console (command-line) prompt will help you determine what hardware you have installed. You can also launch the Mageia Control Center (from the start menu, under Tools -> System Tools) and look in the Hardware section to browse and configure hardware, sound, and other devices.
You might want to make sure that the graphical server is set up for the correct monitor screen size.
HTH
Re: A few problems
Posted:
Feb 17th, '12, 10:33by doktor5000
For one, please open seperate threads for each problem, there's the golden rule of one problem per thread, which helps with clarity and searchability.
For your wireless problem, please show the output of
- Code: Select all
iwconfig
as root and
- Code: Select all
lspcidrake -v | grep NET
Re: A few problems
Posted:
Feb 17th, '12, 14:08by Yinepu
Thanks! My sound's working now!
As for wifi:
- Code: Select all
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
- Code: Select all
rt2500pci : RaLink|RT2500 802.11g [NETWORK_OTHER] (vendor:1814 device:0201 subv:1043 subd:130f) (rev: 01)
skge : Marvell Technology Group Ltd.|88E8001 Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:11ab device:4320 subv:1043 subd:811a) (rev: 13)
Re: A few problems
Posted:
Feb 17th, '12, 18:16by doktor5000
OK, please show the output of
- Code: Select all
iwlist wlan0 scan
Re: A few problems
Posted:
Feb 17th, '12, 18:39by Yinepu
Well, it says
- Code: Select all
wlan0 Interface doesn't support scanning : Device or resource busy
I guess that's not what you're looking for?
Re: A few problems
Posted:
Feb 17th, '12, 20:29by doktor5000
No, that's not what i'm looking for, but seems a usual problem with your wireless chipset, since quite some time:
http://rt2x00.serialmonkey.com/pipermai ... 00417.htmlCould you try the following as root:
- Code: Select all
modprobe -fr rt2500pci && sleep 5 && modprobe rt2500pci
and please post the output here? If there's no error, try to scan again.
If it still doesn't work, try to disable power-saving via:
- Code: Select all
iwconfig wlan0 power off
Otherwise the output you showed further above looks good, system sees your wireless device and it's up and running,
just not associated to an access point yet.
Re: A few problems
Posted:
Feb 17th, '12, 22:12by Yinepu
No, it's still not working and no errors were generated. It might be because when I'm asked to put in the encryption type, it's initially Open WEP, so I change it to WPA PSK, and save the changes. When I go back into it, it's changed the encryption back to Open WEP......
Re: A few problems
Posted:
Feb 18th, '12, 17:25by doktor5000
OK, could you please tell exactly how you try to setup the connection? That issue about Open WEP reminds me of some
bug with the network center, which you shouldn't use. Also please show the output of
- Code: Select all
rpm -qa | grep networkmanager
Re: A few problems
Posted:
Feb 18th, '12, 17:43by Yinepu
Oh, is there a way to connect without using the Network Center?
that command does not give any output........
Re: A few problems
Posted:
Feb 18th, '12, 18:14by doktor5000
Yes, do it either via drakconnect as root, or right-click the network applet and choose "Configure network"
At least that's what it should be called, translating back from german.
Re: A few problems
Posted:
Feb 18th, '12, 18:59by Yinepu
Oh, that's what I was doing before. Using drakconnect via the terminal gives this output if that helps, though:
- Code: Select all
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to create host name resolver: Invalid host name
run-parts: /etc/sysconfig/network-scripts/hostname.d/avahi exited with return code 1
Reloading vnstatd configuration: [ OK ]
Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.
Waiting for network to be up [ OK ]
Re: A few problems
Posted:
Feb 18th, '12, 19:20by doktor5000
FWIW, the "Gtk-CRITICAL **:" ones are not of interest, only the ones below those.
Please show the output of
- Code: Select all
hostname -f
and
- Code: Select all
cat /etc/sysconfig/network-scripts/ifcfg-wlan0
(the latter as root)
Re: A few problems
Posted:
Feb 18th, '12, 20:44by Yinepu
- Code: Select all
localhost.localdomain
- Code: Select all
DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=BTHub3-KPCF
WIRELESS_ENC_KEY=s:e27bf55e94
WIRELESS_WPA_DRIVER=wext
WIRELESS_WPA_REASSOCIATE=no
IPV6INIT=no
IPV6TO4INIT=no
ACCOUNTING=yes
NM_CONTROLLED=yes
DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=yes
PEERYP=yes
PEERNTPD=no
Re: A few problems
Posted:
Feb 19th, '12, 04:02by absolutefunk
For the resolution issue, is this an external monitor (not a laptop display)? Sometimes if the monitor (or the vga cable if you pulled pins) is non-pnp then it is possible that your monitor's native resolution is being invalidated. If you cannot go beyond 1024x768 then that could be the issue. You could try going to "Mageia Control Center -->Hardware-->Set up the Graphical Server" and set the monitor's resolution there.
Re: A few problems
Posted:
Feb 19th, '12, 05:40by Yinepu
Well, it's fine on any other distro it goes way past 1024x768, so I'll try that....