Xfce4 and gnome-network-manager [solved]

I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
Last edited by anarxi (2009-01-14 00:22:42)

quoted from a previous thread
I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
en_US.UTF8 UTF-8
en_US ISO-8859-1
After you've enabled the necessary locales, you have to run locale-gen as root to update them:
# sudo locale-gen
Generating locales...
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.

Similar Messages

Gnome-network-manager

Hi Everybody
I just tried to play a little with gnome-network-manager from AUR, first of all the normal network manager was missing a few files, but I managed to find them(http://aur.archlinux.org/packages/networkmanager/networkmanager/).
But when i start up gnome, it is shown fine in the Status Area, and shows all the networks, but it won't connect to any...
When connecting to an unencrypted network it says it is waiting for the network, when connecting to an encrypted network, it is waiting for the key to be verified.
My assumption is, that it is waiting for DHCP, in both cases.
If I use wifi-radar it gets an IP perfectly, also if I use dhclient or dhpcd it works fine.
Any suggestions?

I tried to use the one from testing, along with the gnome GUI from testing, but with no luck...
As you can see here, it tells me it is waiting fr the key, http://gallery.timmy.dk/Screenshots/gno … anager.png
But in the consle, iwconfig says I'm already connected...
So I'm pretty sure there something wrong with the dhcp

Gnome-network-manager problems

Hello all,
I'm trying to use gnome-network-manager to connect to my wifi as it is WEP enabled and I don't know how to get it working in 'network'.
I followed this tutorial: http://wiki.archlinux.org/index.php/NetworkManager
However, when I reboot under those settings, I can't connect to anything, including ethernet.
Is there a problem in the wiki or is there a workaround that hasn't been posted there yet? I'm utterly confused as to why it will not work.
Also, if you need me to paste any code from any file, can you also tell me an easy way to copy/paste between aterm and Opera as I haven't found a way to do that yet.
Thank you very much for any help.
Matt

[matt@myhost ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"3KR98"
Mode:Managed Frequency:2.427 GHz Access Point: 00:18:01:E0:43:1A
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=21/100 Signal level=-72 dBm Noise level=-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:76 Missed beacon:31
[matt@myhost ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:B0:A1:71:02
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:fea1:7102/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:82717 errors:300 dropped:592 overruns:300 frame:0
TX packets:61302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:79395572 (75.7 Mb) TX bytes:9179527 (8.7 Mb)
Interrupt:22 Base address:0x6800
eth1 Link encap:Ethernet HWaddr 00:13:CE:6A:FE:C1
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:ceff:fe6a:fec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:309 errors:0 dropped:76 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2420181 (2.3 Mb) TX bytes:2012 (1.9 Kb)
Interrupt:23 Base address:0x4000 Memory:bc005000-bc005fff
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:232 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20464 (19.9 Kb) TX bytes:20464 (19.9 Kb)
ill post output of disabling gnome-net-manager in a bit (i have to reboot and save it as a file first).
also, im running fluxbox, not gnome, so could that be part of the problem? am i missing something flux specific?

Gnome-network-manager & XFCE 4.4

Hey guys, someone know if gnome-network-manager also run on XFCE 4.4?
It won't run on my XFCE
Solutions to problem?
Bye,
Riccardo

Captain Spaulding wrote:
OK, open NetworkManager.conf and search for the line
<policy at_console="true">
and add this line:
<allow own="org.freedesktop.NetworkManagerInfo"/>
That, at least, should fix your initial issue. I have only just begun to learn more about dbus, so I have no clue about the second problem.
Mmmmm no entries as <policy at_console="true"> in my NetworkManager.conf....
So here we are my NetworkManager.conf:
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<policy user="root">
<allow own="org.freedesktop.NetworkManager"/>
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy group="users">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy user="hal">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
<policy context="default">
<deny own="org.freedesktop.NetworkManager"/>
<deny send_destination="org.freedesktop.NetworkManager"/>
<deny send_interface="org.freedesktop.NetworkManager"/>
</policy>
</busconfig>

Gnome Network Manager Isues

Hi Guys,
I have some weird issues with Gnome Network manager when I first boot up. I seem to have 2 profiles for my network connection enp3s0. I have a static IP for my PC, xxx.xxx.xxx.66, as I share music and photo's with a media centre PC in another room. But when I boot up or reboot the PC, it defaults to what appears to be another static IP address, xxx.xxx.xxx.109, that was used during the installation of Arch. I have disabled dhcpcd via
systemctl disable dhcpcd.service
but I can't seem to find where this weird IP is coming from.
If I open a command prompt at first login, and I issue ifconfig, my PC has the 109 IP address. If I expand on the Wired icon in Gnome's top right panel, I can see the two profiles, the incorrect one has a small dot next to it, to indicate its active. If I click on it, it disappears and my network becomes disconnected. When I reconnect, I get the correct profile with the correct IP address of 66, the 109 profile has gone.
If I go into the Weird Settings just after login, without clicking on any profiles, I have 2 settings in the box, the top one has a tick next to it and ther bottom one hasn't. If I click on the cog for the first profile, I can see it has a static of 109. Under identity, I remove the ticks for connect automatically and make available to ther users and apply. I reboot and the 109 profile is still there.
Cheers

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

Gnome-network-manager shouldn't require Gnome?

According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
Maybe it would be a good idea to include a version that isn't compiled for Gnome in Extra, so that people using E17 or XFCE or whatever can easily use networkmanager? If people think this is practical I'll file a feature request...

Gullible Jones wrote:According to its page on Gnomefiles, network-manager-applet (gnome-network-manager on Arch) doesn't need Gnome deps.
It does need gnome deps. Requires libgnomegui and gnome-keyring... in turn it also uses gconf and other things. These can't be disabled.
James

Gnome-network-manager doesn't work at all

Hello, guys!
Gnome-network-manager starts but doesn't show its icon in Notification Area.
ps -A shows that the process is running correctly.
[sergo@myhost ~]$ ps -A |grep nm
4360 pts/2 00:00:00 nm-applet
I carefully studied all solutions listed here. My DAEMONS string is
DAEMONS=(syslog-ng !hotplug !pcmcia network netfs crond alsa sensors portmap fam dbus hal dhcdbd networkmanager networkmanager-dispatcher @cups gdm)
Please help.

yes, I have done it, and nothing happen
edit : I have reinstall the software, and now it is OK, tks for the help
Last edited by serafimsaudade (2007-05-20 17:34:56)

WPA on gnome-network-manager

Hi!
I have a rather small problem. I tried to get a wireless connection by using networkmanager and the gnome-network-manager applet. It all ran fine but when I took a closer look at the applet today I saw that there's only WEP protection showing up. So I googled a little bit and recompiled the nm-applet with wpa_supplicant support. I reinstalled the package but still no WPA shows up. S can anyone help me with this, since I rather don't want to go back using unsecure WEP protection.
Thanks a lot!

gnome-keyring :< it's ugly but now works
And this made me looking like an idiot in my university today ;(
Bluman's plugin for NM isn't working too ;( I even couldn't compile it from abs
checking for a Python interpreter with version >= 2.5... python
checking for python... /usr/bin/python
checking for python version... 3.2
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python3.2/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.2/site-packages
checking for headers required to compile python extensions... File "<string>", line 1
import sys; print sys.prefix
^
SyntaxError: invalid syntax
File "<string>", line 1
import sys; print sys.exec_prefix
^
SyntaxError: invalid syntax
not found
configure: error: Could not find Python headers
EDIT: Adding "export PYTHON=/usr/bin/python2" before "./configure" helps
Last edited by swiftgeek (2011-10-03 17:52:24)

[Solved] Can't get gnome network manager running

Alright this one is a head scratcher. I've folowed the wiki for network manager to a T except I can't get the network manager icon to show up (I have notification addon already running). I don't have any network loss though.
Here's my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Pacific"
KEYMAP="dvorak/dvorak"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(powernow-k8 cpufreq_ondemand cpufreq_powersave forcedeth snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo !eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network netfs crond laptop-mode dhcdbd networkmanager @alsa @hal @fam @gdm)
Last edited by dr/owned (2009-01-09 05:16:43)

I assume you're running nm-applet --sm-disable once you get a window manager session up?
Try starting networkmanager after hal. From the wiki:
You must also "disable" the default network daemon, and add the hal, dhcdbd and networkmanager daemons in this order:
DAEMONS=( ... !network hal dhcdbd networkmanager ... )

No interfaces shown in network manager [SOLVED]

Hi All,
I have just done a fresh install of Arch on my new Sony Vaio VGN-FW53GF, all goes well, except for Network Manager.
I can use my wired connection ok as eth0 shows up as active when I hover over the kde applet in the task bar. However when I go to "Manage Connections"
I do not see any Wireless networks or even my "working" wired connection in any list.
Wireless seems to be working as iwconfig shows an interface.
wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But a scan gives this:
iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
This machine is using the Intel driver "iwlagn" supplied by the kernel (2.6.31).
My /etc/rc.conf is:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Pacific/Auckland"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Laptop2"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal networkmanager netfs crond)
Can anyone offer some suggestion on how to get network manager going, I would like to use it. In the past
I have used Wicd, but it has some limitations.
Cheers,
Bernie
Last edited by bmentink (2009-12-24 04:19:49)

bmentink wrote:
Ok, I found the issue. I was missing the firmware for the card. I downloaded firmware from the intel site as per the wiki on wireless and
my interface comes up (shown with ifconfig) and I can see all the networks.
However, I cannot seem to connect to my network with WPA. When I go to connect I get network manager thinking the access point is WEP and asking for pass phrase.
If I select WPA(personal) and fill in a password, nothing happens .... just says unavailable.
Can anyone give some idea's here. I have not used network manager before for WPA.
Cheers,
Bernie
I use WPA2 with network manager without a problem. It should "just work", im not sure why you have issues, can you switch your router to a different security protocol to test?

Gnome settings do not take, and gnome-settings-manager breaks things.

I just updated my Arch install. I hadn't done a full system upgrade since December (I think). The install went fine as far as I can tell. It broke my xorg.conf again, but it always does that, no biggie.
My biggest fight seems to be with the gnome-settings-manager. I am now getting no icons in the menus, the mouse runs extremely slow and the only way to get it to run at a normal tracking speed is to use the KDE 'systemsettings' to change it (bizarre). Also, any desktop background that I assign is essentially covered over on startup with a background color and I cannot (using any settings program in the menus) actually put something there. I'm sure there's just some confusion over what is in control of the desktop and which config file is being used, but I cannot find any other mention of this issue in the forums, and forcefully re-installing gnome has yielded no help. I also moved all my '.gnome' dirs under home to some other location, and this made no difference.
Some info:
# pacman -Q gnome-applets gnome-desktop gnome-settings-daemon gnome-session
gnome-applets 2.24.3.1-1
gnome-desktop 2.24.3-1
gnome-settings-daemon 2.24.1-1
gnome-session 2.24.3-1
When I run gnome-mouse-properties from a command line, I see this:
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Then, when I try to change the mouse acceleration:
(gnome-mouse-properties:7165): capplet-common-WARNING **: Unable to find a default value for key for /desktop/gnome/peripherals/mouse/motion_acceleration.
I'll assume it is an integer, but that may break things.
Please be sure that the associated schema is installed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
Any ideas?

Just to reinforce what byte said: I had similar problems and moving .gconf worked. If it doesn't, you can also try moving .gnome2. And then if you are versed in the edition of gnome settings files, you can search and repair the faulty ones. If not (like me)... start from scratch, delete the moved dir.
It would be great if the gnome devs simplified the format of settings files (make it more like rc.conf!) and made it so they don't break so often. Maybe a system a la windows where previous versions of the registry get saved. Then upon breakage one could just bring up the last working version. Of course the best thing would be for the settings to not get corrupted in the first place.

Udev and gnome-power-manager

Hi,
Recently I upgrade the udev from 141-5-i686 to 145-1-i686 in my MSI wind. Then the following problem begins:
When the system boots this characters can be seen in the screen just before udev is finished: ^@^@
I can add more characters during the whole boot process if I press Fn+F5 (the brightness hotkey).
When gnome is running, in few minutes the screen change the brightness very fast, like blinking. This problem only happens if the gnome-power-manager is enabled.
Downgrading udev fix the problem.
Does anyone know if this is something related with this particular version of udev, or can I do something to fix it?
I don't know if the following messages will help, because them can be seen with the current and with the old udev version. But they are the only ones that I think are related with hotkeys amb modules loading. So I post them just in case.
messages.log:
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd06/26/2008:svnMICRO-STARINTERNATIONALCO.,LTD
:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:' is
not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d000027A6sv00001462sd00000110bc03sc80i00' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0F03:PNP0F13:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'usb:v0C45p62C0d0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
Aug 29 14:57:08 peremsi ntfs-3g[2611]: Version 2009.4.4 integrated FUSE 27
(so many times) This message is because the kernel do not map some hotkeys. Gnome do it.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.

recently, I updated system, and now I have same problem like you had. I was not sure, what could cause this brightness fast changing. I thought about hal, dbus, udev. Never tried to downgrade udev. Now, I have udev 146. I am not sure what version I had before system upgrading.
Now, I have kernel 2.6.31, and I am not sure if udev 141 will work with this kernel...
I have MSI WIND, also...
Last edited by kunalagon (2010-01-08 11:15:54)

Firewire and gnome-volume-manager

I have a firewire scanner, when hotplugged, nothing happens in gnome. I have 'run when scanner is plugged' checked, but I get nothing.
Does gnome-volume-manager work with firewire devices? or is it just my scanner? (Canon 2540 photo)

I don't know about scanners, but my firefire external HD is recognised perfectly by gnome-volume-manager. So it does listen for firewire devices. Maybe you'll need to add something to udev to make gnome-volume-manager know it's a scanner?
I have a scsi scanner, so I won't try hotplugging it

[solved/cannot be solved]Xorg-server and gnome-power-manager

I was wondering if there is hope that someone will put patches to main tree of Xorg-server which are here: http://blogs.gnome.org/hughsie/2009/08/ … of-bodges/
It should remove this weird blanking effect and time gap before screen is backlighted again. I didn't tested it, because it requires rebuild of xorg-server and I don't want to use git version, but guys there says that it's working.
Last edited by megawebmaster (2010-02-08 22:24:26)

OK, thanks for advice, I'll try building xorg-server with ABS.
I've got another problem with automatic turn off screen - media players don't prevent turning screen off while they are playing film. Is there any possibility to fix it? Only way I've found is to turn off automatic screen backlight off after couple of minutes, but it's not how tigers want this to work

Gnome Network Manager under Fluxbox

Hello! Im using fluxbox and I had wifi-radar to connect wifi but I missed a lot the gnome networkmanager so I've removed wifi-radar and installed it.
Now Im getting mad because, after following all the steps the networkmanager starts correctly but says there are no network devices and I cant solve this.
Some info
ifconfig:
eth1 Link encap:Ethernet HWaddr 00:13:02:13:BC:DD
inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:2ff:fe13:bcdd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1306 errors:0 dropped:4620 overruns:0 frame:0
TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:871040 (850.6 Kb) TX bytes:258880 (252.8 Kb)
Interrupt:19 Base address:0xc000 Memory:d0100000-d0100fff
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:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:400 (400.0 b) TX bytes:400 (400.0 b)
iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"WLAN_0A"
Mode:Managed Frequency:2.462 GHz Access Point: 00:01:38:6C:DA:1D
Bit Rate:54 Mb/s Tx-Power:15 dBm
Retry limit:15 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=86/100 Signal level=-47 dBm Noise level=-47 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:4620 Missed beacon:0
and /etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="es_ES.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Madrid"
KEYMAP="es"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(b44 mii ipw3945 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-al
loc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Nosferatu"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="dhcp"
INTERFACES=(lo !eth0 !eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network dhcdbd networkmanager netfs crond ipw3945d)
Someone knows what's going on?
Thank You!

wonder wrote:i mean add hal to DAEMON list.
DAEMONS=(syslog-ng !network hal dhcdbd networkmanager netfs crond ipw3945d)
Yeaaaaah! Now its working!!
I added the daemon.
Thank you very much!

Xfce4 and gnome-network-manager [solved]

Similar Messages

Maybe you are looking for