[Solved] Sudo Configuration (NOPASSWD)
I am currently trying to configure sudo to not use a password for specific commands. I am specifically doing this for netcfgGUI, however I will use more basic independent commands to demonstrate my issue.
If I do the following sudo does not require a password for any commands for any user in group wheel as expected.
%wheel ALL=(ALL) NOPASSWD: ALL
Now if I change this to affect only a certain command like so:
%wheel ALL=(ALL) NOPASSWD: /bin/ls
or
%wheel ALL=NOPASSWD: /bin/ls
I get the following error:
sudo: sorry, you are not allowed to preserve the environment
Does anyone know what I am doing wrong?
Last edited by Tyriel (2009-11-17 14:52:04)
deej wrote:Are you using the 'visudo' command ?
Deej
Yes I am using visudo
t4k1t wrote:
Do you use sudo -E? Or have set an alias like
alias sudo="sudo -E"
Ahh that was it, I forgot I did not commented out the alias of "sudo -E" in my .bashrc. Thanks for the help guys
Last edited by Tyriel (2009-11-17 14:51:29)
Similar Messages
-
[solved] sudo and yaourt problems after recent updates
After recent updates (past week) yaourt started giving me problems. When using yaourt it prompts me for sudo password but it does not seem to use my sudo configuration.
I get this:
[sudo] password for root:
[sudo] password for root:
Password:
su: Authentication failure
Password:
When entering mine or root's password I just get prompt again. The last password is for su, which when I enter root's works.
It seems sudo is not using /etc/sudoers configuration either, as I have things like insults enabled and it used to work previously.
Any reason for this?
sudo works fine otherwise.
Last edited by wrm (2014-03-29 23:12:26)Looks like this: https://github.com/archlinuxfr/yaourt/issues/5
And this: https://bbs.archlinux.org/viewtopic.php?id=178776
Last edited by 2ManyDogs (2014-03-24 21:33:40) -
Getting error with sudo configuration on solaris 10
Valuable Member,
I have some issue with Sudo configuration on Solaris 10 (Sparc), I installed gcc & libiconv then install sudo package everything done well till I run "./configure" but when I run "make" its giving lots of error ... I am confused what I have to do ... Please tell me what exactly I have to do or what I am missing
---------------------------ERROR CUT-------------------------------------
# make
gcc -c -I. -I. -I/tmp/rsa -O2 -D__EXTENSIONS__ -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 check.c
In file included from /usr/include/sys/wait.h:24,
from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
In file included from /usr/include/sys/procset.h:24,
from /usr/include/sys/wait.h:25,
from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
In file included from check.c:55:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
*** Error code 1
make: Fatal error: Command failed for target `check.o'
---------------------END ERROR---------------------------
///Thanks
Mohammed TanvirHow did you install gcc, I don't think its working correctly.
There should be a copy of gcc installed with solaris 10 in /usr/sfw/bin.
I suggest you use that one instead.. -
Sudo configuration for NOPASSWD: ALL
Hey all,
I have a new mac with a fresh 10.8 installed. It's 2 days old and (probably) in the best shape of its life. Here's the problem:
As a Linux guy, I'm using sudo alot and it prompts me for a password every single time. Example:
host_name:~ user_name$ sudo cat /etc/autofs.conf
Password:
etc...
This is getting tedious. In Linux we simply add ourselves to the wheel group and uncomment this line in /etc/sudoers:
# %wheel ALL=(ALL) NOPASSWD: ALL
I've done some troubleshooting on my own but all paths lead to more questions:
Step 1; find out about me:
host_name:~ user_name$ id
uid=501(user_name) gid=20(staff), groups=20(staff), 401(com.apple.access_screensharing), 402(com.apple.sharepoint.group.1), 12(everyone), 33(_appstore), 61(localaccounts), 79(_appserverusr), 80(admin), 81(_appserveradm), 98(_lpadmin), 100(_lpoperator), 204(_developer), 403(com.apple.access_ssh)
-good.
Step 2; grep /etc/passwd for my user account
host_name:~ user_name$ grep user_name /etc/passwd
-nothing.
I can't find my user_name in the password file; OK, now I'm confused.
2 questions - 1 purpose:
How do I configure /etc/sudoers to not prompt me for the password at all - ever again? OR
What's the preferred method of getting the same functionality in OS X?
Thanks in advance,
TTThis was a "Duh" moment for me. I steped out, had some dinner and a scotch, and magically, the answer came. Being a member of the "admin" group, it was that line which needed modification, not wheel:
Open the Terminal
sudo visudo
Change this line FROM:
$ %admin ALL=(ALL) ALL
TO:
$ %admin ALL=(ALL) NOPASSWD: ALL
Write and Quit
:wq
Retest successful; sudo no-longer nags me for a password.
Scotch is good. -
[SOLVED] sudo doesnt work
Hi guys,
I'm having the strangest issues since my last installation of archlinux. First I could not login into any tty (after entering the username, nothing happened). I could solve that by installing the util-linux package. Now I cannot use sudo.
The user is in the group wheel (which is uncommented in sudoers). I have changed nothing in the sudoers file, here's the content:
## sudoers file.
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
## See the sudoers man page for the details on how to write a sudoers file.
## Host alias specification
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias WEBSERVERS = www1, www2, www3
## User alias specification
## Groups of users. These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias ADMINS = millert, dowdy, mikef
## Cmnd alias specification
## Groups of commands. Often used to group related commands together.
# Cmnd_Alias PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# /usr/bin/pkill, /usr/bin/top
## Defaults specification
## You may wish to keep some of the following environment variables
## when running commands via sudo.
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
## Run X applications through sudo; HOME is used to find the
## .Xauthority file. Note that other programs use HOME to find
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
## Uncomment to enable special input methods. Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot. Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output
## Runas alias specification
## User privilege specification
root ALL=(ALL) ALL
## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL) ALL
## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL
## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw # Ask for the password of the target user
# ALL ALL=(ALL) ALL # WARNING: only use this together with 'Defaults targetpw'
## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d
In the auth.log there are following lines which seem to be important:
Jul 12 13:46:18 localhost sudo: PAM _pam_init_handlers: no default config /etc/pam.d/other
Jul 12 13:46:21 localhost sudo: PAM no modules loaded for `sudo' service
Jul 12 13:46:22 localhost sudo: pam_unix(sudo:auth): conversation failed
Jul 12 13:46:22 localhost sudo: pam_unix(sudo:auth): auth could not identify password for [archUser]
Jul 12 13:46:22 localhost sudo: archUser: 1 incorrect password attempt ; TTY=pts/2 ; PWD=/home/archUser; USER=root ; COMMAND=/usr/bin/pacman -Syyuu
So I looked up the content of /etc/pam.d/sudo:
root@arch /etc/pam.d # cat sudo
#%PAM-1.0
auth required pam_unix.so
auth required pam_nologin.so
The files pam_unix.so and pam_nologin.so are both saved in /usr/lib/security.
I noticed that if I enter the password wrong, I need to wait one or two seconds before I can try it again (this behaviour seems to be normal). But when I enter the password correct, there is no waiting time and I can enter the pass again.
I have no idea what to do and hope that anyone can help me to use sudo again.
4 years ago, after installing archlinux the first time, I had not a single error. Everything worked just fine but now I get two errors at once after the installation!
--blackdeagle
Last edited by blackdeagle (2012-07-12 14:05:53)blackdeagle wrote:
65kid wrote:
blackdeagle wrote:Please stay away from my thread! I don't need people like you telling me to search the forums and which parameters I can use and which not!
seriously? it is stated in multiple news, the wiki and in about every third forum thread that you shouldn't use force unless you know exactly what you are doing or you are explicitly told to use it. I don't blame you that you didn't notice this, a lot of people don't (unfortunately). But when people correct you and want to help you are like "whatever, I do what I want! go away!" ???
And what do you think the search function is for?
Please stay away from Arch... geez...
Come on, do you seriously think you are the only one using the search function? Show me some threads with the solution for my issue!
https://bbs.archlinux.org/viewtopic.php?id=143335
https://bbs.archlinux.org/viewtopic.php?id=144079
https://bbs.archlinux.org/viewtopic.php?id=143487
https://bbs.archlinux.org/viewtopic.php?id=142729
https://bbs.archlinux.org/viewtopic.php?id=142720
https://bbs.archlinux.org/viewtopic.php?id=142941
https://bbs.archlinux.org/viewtopic.php?id=144599 -
[SOLVED] sudo -i changes ownership of .Xauthority to root, breaks X
From a normal user's terminal session running in xmonad, I tried to enter a root terminal session with "sudo -i".
I got sent to the virtual console and couldn't switch back to X. An error message told me .Xauthority was not writable. The user's .Xauthority file was now owned by root and not writable.
After removing the root-owned files, I could start X and everything seems normal.
"sudo -s" and "su" work as expected.
Do I have a bad configuration? Do I not understand "sudo -i"?
Edit: Could sudo's "initial login" try to start X as root? I have auto-login configured for the first virtual console. I'll try to switch that off and try again.
SOLVED: The cause was my root user's .bash_profile and .zprofile. I copied my user's .bash_profile and .zprofile over to root and didn't notice that I should comment the following line to automatically start X:
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
Last edited by Markus00000 (2013-06-13 13:04:31)Change
archimedes ALL = (ALL) NOPASSWD: SHUT, NOPASSWD: PAC
to
archimedes ALL=(ALL) NOPASSWD: SHUT, NOPASSWD: PAC -
[SOLVED] sudo doesn't ask password
Hello everyone,
I have a problem. when I run a command with sudo arch don't ask me my user password.
In fact, if I launch:
sudo -ll
the result is:
the user delvi can run the following command on delvi-arch:
Voce sudoers:
RunAsUsers: ALL
option: !authenticate
command: ALL
this is not good for me. how do I remove the !authenticate option?
P.S. sorry for my english... I'm italian.
Last edited by delvi932905 (2014-10-27 17:11:30)my sudoers file:
## sudoers file.
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
## See the sudoers man page for the details on how to write a sudoers file.
## Host alias specification
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias WEBSERVERS = www1, www2, www3
## User alias specification
## Groups of users. These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias ADMINS = millert, dowdy, mikef
## Cmnd alias specification
## Groups of commands. Often used to group related commands together.
# Cmnd_Alias PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# /usr/bin/pkill, /usr/bin/top
## Defaults specification
## You may wish to keep some of the following environment variables
## when running commands via sudo.
## Locale settings
#Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
## Run X applications through sudo; HOME is used to find the
## .Xauthority file. Note that other programs use HOME to find
## configuration files and this may lead to privilege escalation!
#Defaults env_keep += "HOME"
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
#Defaults env_keep += "DISPLAY XAUTHORIZATION XAUTHORITY"
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
## Uncomment to enable special input methods. Care should be taken as
## this may allow users to subvert the command being run via sudo.
#Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
## Uncomment to enable logging of a command's output, except for
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output
## Runas alias specification
## User privilege specification
root ALL=(ALL) ALL
#delvi ALL=(ALL) PASSWD: ALL
## Uncomment to allow members of group wheel to execute any command
#%wheel ALL=(ALL) ALL
## Same thing without a password
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL
## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
#Defaults targetpw # Ask for the password of the target user
#ALL ALL=(ALL) ALL # WARNING: only use this together with 'Defaults targetpw'
## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d
# Reset environment by default
Defaults env_reset
# Set default EDITOR to nano, and do not allow visudo to use EDITOR/VISUAL.
Defaults editor="/usr/bin/nano", !env_editor -
[solved] sudo: No password needed before graphical login?
Yesterday I was messing around a bit with SLiM. I didn't configure any sessions for it however, so I was forced to login trough a VT.
The funny thing is, on the VT, before loging in with a graphical manager, sudo didn't ask for a password. This was also the case when I using gdm. After I logged on to a graphical desktop, sudo would also ask for a password in de VT.
My /etc/sudoers:
# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
# See the sudoers man page for the details on how to write a sudoers file.
# Host alias specification
# User alias specification
# Cmnd alias specification
# Defaults specification
# Runas alias specification
# User privilege specification
root ALL=(ALL) ALL
# Uncomment to allow people in group wheel to run all commands
%wheel ALL=(ALL) ALL
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
Does anybody know if this is default behavior? Or is it more likely I made a mistake in some error file?
Last edited by lldmer (2008-08-11 12:51:23)On my machine sudo 'remembers' me for up to five minutes so if you had used sudo just prior to that time this might be what is happening.
from sudo man page:
Once a user has been authenticated, a timestamp is updated and the user may
then use sudo without a password for a short period of time (5 minutes unless
overridden in sudoers).
Otherwise, I am not sure. -
[SOLVED] Sudo does not accept user password
Hello , again !
usually i run root commands with sudo , and i enter my current user password and everything works !
Today , i updated my Arch linux with :
pacman -Syu
and my arch upgraded to 3.4.2-2.
but when i want to run a command with sudo , i cannot use my current user password ?
thankyou
Last edited by arashroshan (2012-06-19 11:10:52)thank you for reply but i have read sudo wiki and also sudo was working before updating .
by the way su is still working .
here is my sudoer file :
## sudoers file.
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
## See the sudoers man page for the details on how to write a sudoers file.
## Host alias specification
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias WEBSERVERS = www1, www2, www3
## User alias specification
## Groups of users. These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias ADMINS = millert, dowdy, mikef
## Cmnd alias specification
## Groups of commands. Often used to group related commands together.
# Cmnd_Alias PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# /usr/bin/pkill, /usr/bin/top
## Defaults specification
## You may wish to keep some of the following environment variables
## when running commands via sudo.
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
## Run X applications through sudo; HOME is used to find the
## .Xauthority file. Note that other programs use HOME to find
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
## Uncomment to enable special input methods. Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot. Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output
## Runas alias specification
## User privilege specification
root ALL=(ALL) ALL
## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL) ALL
## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
#arashr ALL=(ALL) All
## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL
## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw # Ask for the password of the target user
# ALL ALL=(ALL) ALL # WARNING: only use this together with 'Defaults targetpw'
## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d
Last edited by arashroshan (2012-06-17 10:02:55) -
[solved] Xorg -configuration crashes (signal 11)
I've been trying to get Xorg to work all day without success. What I've been doing:
* Install archlinux from scratch
* Upgrade with pacman -Syu
* Install Xorg
* Install fglrx
* Run Xorg -configure.
This is when it crashes with the following output:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux twarkie 2.6.22-ARCH #1 SMP PREEMPT Tue Sep 25 19:18:19 CEST 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 26 22:11:11 2007
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81c44a0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.1
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(--) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,00e1 card 0000,0000 rev a1 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 10de,00e0 card 10de,0c11 rev a2 class 06,01,00 hdr 80
(II) PCI: 00:01:1: chip 10de,00e4 card 10de,0c11 rev a1 class 0c,05,00 hdr 80
(II) PCI: 00:02:0: chip 10de,00e7 card 10de,0c11 rev a1 class 0c,03,10 hdr 80
(II) PCI: 00:02:1: chip 10de,00e7 card 10de,0c11 rev a1 class 0c,03,10 hdr 80
(II) PCI: 00:02:2: chip 10de,00e8 card 10de,0c11 rev a2 class 0c,03,20 hdr 80
(II) PCI: 00:05:0: chip 10de,00df card 10de,0c11 rev a2 class 06,80,00 hdr 00
(II) PCI: 00:08:0: chip 10de,00e5 card f0de,0c11 rev a2 class 01,01,8a hdr 00
(II) PCI: 00:09:0: chip 10de,00ee card 10de,0c11 rev a2 class 01,01,85 hdr 00
(II) PCI: 00:0a:0: chip 10de,00e3 card 10de,0c11 rev a2 class 01,01,85 hdr 00
(II) PCI: 00:0b:0: chip 10de,00e2 card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:0e:0: chip 10de,00ed card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0: chip 1002,4152 card 174b,7c29 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4172 card 174b,7c28 rev 00 class 03,80,00 hdr 00
(II) PCI: 02:0b:0: chip 1412,1724 card 3031,4553 rev 01 class 04,01,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:11:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000b000 - 0x0000bfff (0x1000) IX[b]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xd8000000 - 0xe7ffffff (0x10000000) MX[b]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:14:0), (0,2,2), BCTRL: 0x0202 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000c000 - 0x0000cfff (0x1000) IX[b]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b]
(--) PCI:*(1:0:0) ATI Technologies Inc RV350 AR [Radeon 9600] rev 0, Mem @ 0xd8000000/27, 0xe8030000/16, I/O @ 0xb000/8
(--) PCI: (1:0:1) ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary) rev 0, Mem @ 0xe0000000/27, 0xe8020000/16
List of video drivers:
fglrx
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.40.4
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) PCI Memory resource overlap reduced 0xd0000000 from 0xd7ffffff to 0xcfffffff
(II) Active PCI resource ranges:
[0] -1 0 0xea000000 - 0xea000fff (0x1000) MX[b]
[1] -1 0 0xea004000 - 0xea0040ff (0x100) MX[b]
[2] -1 0 0xea003000 - 0xea003fff (0x1000) MX[b]
[3] -1 0 0xea002000 - 0xea002fff (0x1000) MX[b]
[4] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[b]O
[5] -1 0 0xe8030000 - 0xe803ffff (0x10000) MX[b](B)
[6] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[b](B)
[7] -1 0 0x0000c200 - 0x0000c27f (0x80) IX[b]
[8] -1 0 0x0000c100 - 0x0000c11f (0x20) IX[b]
[9] -1 0 0x0000df00 - 0x0000df7f (0x80) IX[b]
[10] -1 0 0x0000de00 - 0x0000de0f (0x10) IX[b]
[11] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
[12] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
[13] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
[14] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
[15] -1 0 0x0000d900 - 0x0000d97f (0x80) IX[b]
[16] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[b]
[17] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
[18] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
[19] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
[20] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
[21] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[b]
[22] -1 0 0x0000d100 - 0x0000d107 (0x8) IX[b]
[23] -1 0 0x00004c40 - 0x00004c7f (0x40) IX[b]
[24] -1 0 0x00004c00 - 0x00004c3f (0x40) IX[b]
[25] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[26] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[b](B)
(II) Inactive PCI resource ranges:
[0] -1 0 0xe8020000 - 0xe802ffff (0x10000) MX[b](B)
[1] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[b](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xea000000 - 0xea000fff (0x1000) MX[b]
[1] -1 0 0xea004000 - 0xea0040ff (0x100) MX[b]
[2] -1 0 0xea003000 - 0xea003fff (0x1000) MX[b]
[3] -1 0 0xea002000 - 0xea002fff (0x1000) MX[b]
[4] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[b]O
[5] -1 0 0xe8030000 - 0xe803ffff (0x10000) MX[b](B)
[6] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[b](B)
[7] -1 0 0x0000c200 - 0x0000c27f (0x80) IX[b]
[8] -1 0 0x0000c100 - 0x0000c11f (0x20) IX[b]
[9] -1 0 0x0000df00 - 0x0000df7f (0x80) IX[b]
[10] -1 0 0x0000de00 - 0x0000de0f (0x10) IX[b]
[11] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
[12] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
[13] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
[14] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
[15] -1 0 0x0000d900 - 0x0000d97f (0x80) IX[b]
[16] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[b]
[17] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
[18] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
[19] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
[20] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
[21] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[b]
[22] -1 0 0x0000d100 - 0x0000d107 (0x8) IX[b]
[23] -1 0 0x00004c40 - 0x00004c7f (0x40) IX[b]
[24] -1 0 0x00004c00 - 0x00004c3f (0x40) IX[b]
[25] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[26] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[b](B)
(II) Inactive PCI resource ranges after removing overlaps:
[0] -1 0 0xe8020000 - 0xe802ffff (0x10000) MX[b](B)
[1] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[b](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xea000000 - 0xea000fff (0x1000) MX[b]
[5] -1 0 0xea004000 - 0xea0040ff (0x100) MX[b]
[6] -1 0 0xea003000 - 0xea003fff (0x1000) MX[b]
[7] -1 0 0xea002000 - 0xea002fff (0x1000) MX[b]
[8] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[b]O
[9] -1 0 0xe8030000 - 0xe803ffff (0x10000) MX[b](B)
[10] -1 0 0xd8000000 - 0xdfffffff (0x8000000) MX[b](B)
[11] -1 0 0xe8020000 - 0xe802ffff (0x10000) MX[b](B)
[12] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[b](B)
[13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[14] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[15] -1 0 0x0000c200 - 0x0000c27f (0x80) IX[b]
[16] -1 0 0x0000c100 - 0x0000c11f (0x20) IX[b]
[17] -1 0 0x0000df00 - 0x0000df7f (0x80) IX[b]
[18] -1 0 0x0000de00 - 0x0000de0f (0x10) IX[b]
[19] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
[20] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
[21] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
[22] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
[23] -1 0 0x0000d900 - 0x0000d97f (0x80) IX[b]
[24] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[b]
[25] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
[26] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
[27] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
[28] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
[29] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[b]
[30] -1 0 0x0000d100 - 0x0000d107 (0x8) IX[b]
[31] -1 0 0x00004c40 - 0x00004c7f (0x40) IX[b]
[32] -1 0 0x00004c00 - 0x00004c3f (0x40) IX[b]
[33] -1 0 0x0000e000 - 0x0000e01f (0x20) IX[b]
[34] -1 0 0x0000b000 - 0x0000b0ff (0x100) IX[b](B)
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.40.4
(II) ATI Proprietary Linux Driver Release Identifier: UNSUPPORTED-8.402
(II) ATI Proprietary Linux Driver Build Date: Jul 31 2007 22:20:14
Backtrace:
0: Xorg(xf86SigHandler+0x84) [0x80d0574]
1: [0xb7fdc420]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x11b) [0xb7a95bfb]
3: Xorg(DoConfigure+0x20c) [0x80ce37c]
4: Xorg(InitOutput+0x66a) [0x809fc0a]
5: Xorg(main+0x27b) [0x806e36b]
6: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7df5f90]
7: Xorg(FontFileCompleteXLFD+0xa9) [0x806d8b1]
Fatal server error:
Caught signal 11. Server aborting
If I enable the testing repository and perform a full system upgrade, I can get X to work with the open source drivers for ATI. But I need to get fglrx to work in order to use tv-out. So there seem to be a problem with Xorg itself, not the driver in this case.
Any ideas?
Last edited by twarkie (2007-09-26 23:45:54)Well, in your previous log, the crash backtrace:
Backtrace:
0: Xorg(xf86SigHandler+0x84) [0x80d0574]
1: [0xb7fdc420]
2: /usr/lib/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0x11b) [0xb7a95bfb]
3: Xorg(DoConfigure+0x20c) [0x80ce37c]
4: Xorg(InitOutput+0x66a) [0x809fc0a]
5: Xorg(main+0x27b) [0x806e36b]
6: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7df5f90]
7: Xorg(FontFileCompleteXLFD+0xa9) [0x806d8b1]
died inside /usr/lib/xorg/modules/drivers/fglrx_drv.so - so I figured if you removed fglrx, Xorg -configure wouldn't try to use that module, and the crash would go away. I'm glad I guessed right.
Could you please add [solved] to your topic title? -
SOLVED:
It seems that my monitor shows no green screen when it is ready. Instead it shows the last image rendered. In my case it was this color stripes.
Also, I upgraded to kernel 3.2.1-2, and using the include module udlfb and xf86-video-fbdev from the official repositories I made it work.
I'm struggling to configure a Green House DisplayLink monitor to work with a netbook with an eGalaxTouchscreen. It seems I have problems with udlfb and the DisplayLink driver.
Following this artilce in the wiki, I installed udlfb and xf86-video-fbdev-for-displaylink from the AUR.
Loading the module with
# modprobe udlfb fb_defio=1
does not give any problem:
dmesg
[ 509.963703] usbcore: registered new interface driver udlfb
Plugging the monitor after loading the driver gives the following output:
dmesg
[ 637.363419] usb 1-1: new high speed USB device number 6 using ehci_hcd
[ 637.470050] usb 1-1: device descriptor read/64, error -32
[ 637.701889] udlfb: DisplayLink GH-USD16K - serial #USD16K3310398
[ 637.701899] udlfb: vid_17e9&pid_016b&rev_0196 driver's dlfb_data struct at f377b800
[ 637.701905] udlfb: console enable=0
[ 637.701909] udlfb: fb_defio enable=1
[ 637.702124] udlfb: vendor descriptor length:17 data:17 5f 01 0015 05 00 01 03 00 04
[ 637.702132] udlfb: DL chip limited to 1500000 pixel modes
[ 637.702251] udlfb: allocated 4 65024 byte urbs
[ 637.785022] udlfb: 1366x768 valid mode
[ 637.785034] udlfb: Reallocating framebuffer. Addresses will change!
[ 637.788011] udlfb: 1366x768 valid mode
[ 637.788019] udlfb: set_par mode 1366x768
[ 637.793145] udlfb: DisplayLink USB device /dev/fb1 attached. 1366x768 resolution. Using 4104K framebuffer memory
But there is no visible change, the screen remains black. Nevertheless, there is a new entry /dev/fb1 as advertised. I followed the steps of the article but I didn't suceed. As I understand, the green screen assures you that udlfb is properly loaded and that the monitor is ready to use.
It seems that it is sadly not my case. Another strange thing is that if I load udlfb, then unload it and load it back again the monitor diplays green, blue, red and yellow stripes. But not the green screen.
I attach my xorg configuration, just in case.
/etc/X11/xorg.conf.d/10-monitor.conf
# eGalax TouchScreen
Section "Monitor"
Identifier "LVDS1"
EndSection
Section "Device"
Identifier "eGalaxTouchscreen"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "eGalaxScreen"
Device "eGalaxTouchscreen"
Monitor "LVDS1"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1366x768"
EndSubSection
EndSection
# Green House DisplayLink Monitor
Section "Monitor"
Identifier "GreenHouseMonitor"
EndSection
Section "Device"
Identifier "GreenHouseMonitor"
Driver "fbdev"
BusID "USB"
Option "fbdev" "/dev/fb1"
# Option "rotate" "CCW"
EndSection
Section "Screen"
Identifier "GreenHouseScreen"
Device "GreenHouseMonitor"
Monitor "GreenHouseMonitor"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1366x768"
EndSubSection
EndSection
# Dual Monitor configuration
#Section "ServerLayout"
# Identifier "eGalaxAsMainDisplay"
# Screen 0 "eGalaxScreen"
# Screen 1 "GreenHouseScreen" RightOf "eGalaxScreen"
# Option "Xinerama" "on"
#EndSection
Section "ServerLayout"
Identifier "GreenHouseAsMainDisplay"
Screen 0 "GreenHouseScreen"
Screen 1 "eGalaxScreen" RightOf "GreenHouseScreen"
Option "Xinerama" "on"
EndSection
Last edited by gjasso (2012-01-25 13:22:29)I use my DisplayLink monitor with a netbook. The best I can get at the moment is to use the DL monitor as my primary monitor in a []single monitor setup[]. This means that my netbook's monitor is not used at all (although in my case it is not vital, I would like it to work for watching videos or writing LaTeX code in the smaller screen with a big font size and read the preview in the bigger one).
This is the Xorg file I use:
/etc/X11/xorg.conf.d/10-monitor.conf
# DisplayLink Monitor
Section "Device"
Identifier "DisplayLink"
Driver "fbdev"
BusID "USB"
Option "fbdev" "/dev/fb1"
EndSection
Section "Monitor"
Identifier "Secondary Monitor"
EndSection
Section "Screen"
Identifier "External Screen"
Device "DisplayLink"
Monitor "Secondary Monitor"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1366x768"
# Virtual 4096 4096
EndSubSection
EndSection
# eGalax Touchscreen
Section "Device"
Identifier "Integrated Graphics Controller"
Driver "intel"
EndSection
Section "Monitor"
Identifier "Primary Monitor"
EndSection
Section "Screen"
Identifier "Internal Screen"
Device "Integrated Graphics Controller"
Monitor "Primary Monitor"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1366x768"
Virtual 2732 768
EndSubSection
EndSection
# Dual Monitor configuration
Section "ServerLayout"
Identifier "Dual Head Setup"
# Screen "Internal Screen"
# Screen "External Screen" RightOf "Internal Screen"
Screen "External Screen"
# Screen "Internal Screen" LeftOf "External Screen"
# Screen "Internal Screen" LeftOf "External Screen"
# Option "Xinerama" "on"
# Option "Clone" "off"
EndSection
I use xf86-input-fbdev for the DL monitor.
This has one major drawback: I've found no way to make this work dynamically, so I need to move/rename or edit this file whenever I want to change my setup (twice a day in my case). It is not absolutely unbearable but it is an unsatisfactory solution nevertheless.
Also, if I understood correctly, this seems to be a limitation of the current drivers (which include no 3D accel., so no GNOME shell for example). If you find a better way to do it (specially to detect the other monitor dynamically) please let me know.
PS: Sorry for the late response, I was on vacation. -
[solved]Sudo asking for password when it shouldn't through a sh script
Bottom of my sudoers file looks like this:
user username = (root) NOPASSWD: /usr/bin/g15daemon
user username = (root) NOPASSWD: /usr/bin/g15stats
Shell script looks like that:
#!/bin/sh
sudo /usr/bin/g15daemon -k &
sleep 2 && sudo /usr/bin/g15daemon &
sleep 5 && sudo /usr/bin/g15stats
If I run these commands from the terminal they work as intended (no password) but when I execute that shell script it asks for a password.
Last edited by rabcor (2014-05-01 14:32:00)teateawhy wrote:1. The reason it asks for a password is the first command in the script. The complete command including arguments must be specified in /etc/sudoers. If you want to allow "/usr/bin/g15daemon -k" to be run from sudo, write this string after NOPASSWD.
I've seen this claim before on these forums, but that's not true:
man sudoers wrote:A simple file name allows the user to run the command with any arguments he/she wishes.
The reason it doesn't work is the "user username" part. You probably have an actual username there that you don't want to share with us, but then what exactly is the difference between "user" and "username"? The second element should be a host list:
man sudoers wrote:The basic structure of a user specification is “who where = (as_whom) what”.
To keep it simple you can use ALL for both "where" and "as_whom". -
[SOLVED] Network Configuration -- unable to start a service file
I am following this wiki page (Using Static IP address step) and created /etc/systemd/system/network.service as instructed
[Unit]
Description=Connect to the other pc
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-lan.device
After=sys-subsystem-net-devices-lan.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network
ExecStart=/sbin/ip link set dev lan up
ExecStart=/sbin/ip addr add 192.168.1.2/24 dev lan
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev lan
ExecStop=/sbin/ip link set dev lan down
[Install]
WantedBy=multi-user.target
But I am unable to start network.service
$ sudo systemctl start network
Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.
$ systemctl status network.service
network.service - Connect to voice
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: failed (Result: resources)
$ sudo journalctl -xn
-- Logs begin at Sat 2013-03-30 03:48:02 AMT, end at Thu 2013-04-04 18:17:46 AMT. --
Apr 04 18:17:26 work sudo[24774]: pam_unix(sudo:session): session closed for user root
Apr 04 18:17:44 work sudo[25354]: void : TTY=pts/0 ; PWD=/etc/systemd/system ; USER=root ; COMMAND=/usr/bin/systemctl start network
Apr 04 18:17:44 work sudo[25354]: pam_unix(sudo:session): session opened for user root by void(uid=0)
Apr 04 18:17:44 work systemd[1]: Starting Connect to the other pc...
-- Subject: Unit network.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- Unit network.service has begun starting up.
Apr 04 18:17:44 work systemd[1]: Failed to load environment files: No such file or directory
Apr 04 18:17:44 work systemd[1]: network.service failed to run 'start' task: No such file or directory
Apr 04 18:17:44 work systemd[1]: Failed to start Connect to the other pc.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit network.service has failed.
-- The result is failed.
Apr 04 18:17:44 work sudo[25354]: pam_unix(sudo:session): session closed for user root
Apr 04 18:17:46 work sudo[25421]: void : TTY=pts/0 ; PWD=/etc/systemd/system ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Apr 04 18:17:46 work sudo[25421]: pam_unix(sudo:session): session opened for user root by void(uid=0)
Additional info:
I have connected 2 PCs with LAN (Ethernet) cable and want configure them for exchanging files. Both running Arch Linux. I am following the Network Configuration wiki page from the beginning. Didn't have luck with DHCP/dynamic IP, so trying Static IP this time. Restarting the pc with network.service enabled results in same error (in systemctl --failed). Same error message on both PCs.
Trying to run ExecStart lines one by one:
$ sudo /sbin/ip link set dev lan up
$ sudo /sbin/ip addr add 192.168.1.2/24 dev lan
RTNETLINK answers: File exists
$ sudo /sbin/ip route add default via 192.168.1.1
RTNETLINK answers: File exists
Does this mean there already is IP address and route assigned? If so, how to find out which service has done that? Do I need to remove it? Am I following the right wiki page (didn't find another)?
What am I doing wrong and how can I correct this error? / Point me in right direction.
Last edited by axper (2013-04-04 19:26:17)henk wrote:
EnvironmentFile=/etc/conf.d/network
Apr 04 18:17:44 work systemd[1]: Failed to load environment files: No such file or directory
have you checked if the network file exists?
Oh thanks, that line was causing problems! Now I do have network.service(s) running on both PC's with this content:
[Unit]
Description=Connect to my desktop/laptop
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-lan.device
After=sys-subsystem-net-devices-lan.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev lan up
ExecStart=/sbin/ip addr add 192.168.1.2/24 dev lan
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev lan
ExecStop=/sbin/ip link set dev lan down
[Install]
WantedBy=multi-user.target
I don't get any errors, and this is network's status (on both PCs) when cable is connected
$ sudo systemctl restart network
$ systemctl status network
network.service - Connect to my desktop
Loaded: loaded (/etc/systemd/system/network.service; disabled)
Active: active (exited) since Thu 2013-04-04 22:43:22 AMT; 8s ago
Process: 9761 ExecStop=/sbin/ip link set dev lan down (code=exited, status=0/SUCCESS)
Process: 9757 ExecStop=/sbin/ip addr flush dev lan (code=exited, status=0/SUCCESS)
Process: 9768 ExecStart=/sbin/ip route add default via 192.168.1.1 (code=exited, status=0/SUCCESS)
Process: 9766 ExecStart=/sbin/ip addr add 192.168.1.2/24 dev lan (code=exited, status=0/SUCCESS)
Process: 9764 ExecStart=/sbin/ip link set dev lan up (code=exited, status=0/SUCCESS)
And here wiki page is no more help. How can I test connection?
I try to ping, and it works on both machines (if it's the right thing to test?)
$ ping -c3 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.039 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.060 ms
--- 192.168.1.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.039/0.049/0.060/0.011 ms
Now I need to figure out how to share files. Thanks all.
Last edited by axper (2013-04-04 19:04:43) -
[SOLVED] makepkg / configure locks up system
This is really a continuation of this topic. That one is marked as solved, but it's not for me and it appears that others are experiencing the same lock ups.
When compiling through makepkg, at the configure stage the system locks up. kernel.log shows this:
Sep 8 08:35:43 mesh kernel: [ 6570.240246] [ 3258] 1000 3258 3506 1 0 0 0 makepkg
Sep 8 08:35:43 mesh kernel: [ 6570.240249] [ 3412] 1000 3412 3406 0 1 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240252] [ 3428] 1000 3428 2711 0 1 0 0 make
Sep 8 08:35:43 mesh kernel: [ 6570.240254] [ 3491] 1000 3491 3406 1 1 0 0 sh
Sep 8 08:35:43 mesh kernel: [ 6570.240256] [ 3492] 1000 3492 3406 7 1 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240259] [ 3497] 1000 3497 3406 7 1 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240261] [ 3498] 1000 3498 3406 7 0 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240264] [ 3499] 1000 3499 3406 7 1 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240266] [ 3500] 1000 3500 3406 7 0 0 0 configure
Sep 8 08:35:43 mesh kernel: [ 6570.240269] [ 3501] 1000 3501 3406 7 0 0 0 configure
<-snip, all the way down to->
Sep 8 08:35:47 mesh kernel: [ 6570.242780] [ 4502] 1000 4502 4934 1400 0 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242782] [ 4503] 1000 4503 4935 1401 1 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242784] [ 4504] 1000 4504 4935 1403 0 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242787] [ 4505] 1000 4505 4936 1404 1 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242789] [ 4506] 1000 4506 4936 1406 0 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242791] [ 4507] 1000 4507 4970 1409 1 0 0 configure
Sep 8 08:35:47 mesh kernel: [ 6570.242794] [ 4508] 1000 4508 4970 1409 0 0 0 configure
errors.log reports out of memory:
Sep 8 08:41:51 mesh kernel: [ 306.358181] Out of memory: Kill process 1395 (plasma-desktop) score 22 or sacrifice child
Sep 8 08:41:51 mesh kernel: [ 306.358186] Killed process 1403 (ksysguardd) total-vm:9032kB, anon-rss:4kB, file-rss:48kB
Sep 8 08:41:58 mesh kernel: [ 306.730373] Out of memory: Kill process 1395 (plasma-desktop) score 22 or sacrifice child
Sep 8 08:41:58 mesh kernel: [ 306.730378] Killed process 1395 (plasma-desktop) total-vm:803464kB, anon-rss:49096kB, file-rss:0kB
Sep 8 08:42:08 mesh kernel: [ 322.648070] Out of memory: Kill process 1678 (virtuoso-t) score 16 or sacrifice child
Sep 8 08:42:08 mesh kernel: [ 322.648073] Killed process 1678 (virtuoso-t) total-vm:208672kB, anon-rss:43624kB, file-rss:0kB
Sep 8 08:42:13 mesh kernel: [ 329.718121] Out of memory: Kill process 1356 (kwin) score 6 or sacrifice child
Sep 8 08:42:13 mesh kernel: [ 329.718125] Killed process 1356 (kwin) total-vm:631452kB, anon-rss:3392kB, file-rss:4164kB
Sep 8 08:42:14 mesh kernel: [ 332.438002] Out of memory: Kill process 1412 (mysqld) score 5 or sacrifice child
Sep 8 08:42:14 mesh kernel: [ 332.438008] Killed process 1412 (mysqld) total-vm:339192kB, anon-rss:1584kB, file-rss:0kB
Sep 8 08:42:34 mesh syslog-ng[908]: Error processing log message: <u:
Sep 8 08:42:35 mesh kernel: [ 343.448769] Out of memory: Kill process 1454 (nepomukservices) score 3 or sacrifice child
Sep 8 08:42:35 mesh kernel: [ 343.448776] Killed process 1454 (nepomukservices) total-vm:570132kB, anon-rss:308kB, file-rss:0kB
Sep 8 08:42:35 mesh kernel: [ 352.703132] Out of memory: Kill process 1482 (kio_http_cache_) score 3 or sacrifice child
Sep 8 08:42:35 mesh kernel: [ 352.703136] Killed process 1482 (kio_http_cache_) total-vm:312872kB, anon-rss:0kB, file-rss:0kB
Sep 8 08:42:49 mesh kernel: [ 365.412969] Out of memory: Kill process 1449 (nepomukserver) score 2 or sacrifice child
Sep 8 08:42:49 mesh kernel: [ 365.412976] Killed process 1701 (nepomukservices) total-vm:248868kB, anon-rss:264kB, file-rss:0kB
x86_64, AMD Athlon(tm) II X2 250 cpu, 4GiB ram, kernel 3.0.4-1, Nvidia GeForce 9600 GT, KDE. Lock-ups occurred before and after yesterday's -Syu.
Any ideas?
Edit: this is on my desktop. No such problem on my laptop (intel based).
Last edited by ploub (2011-09-10 08:09:59)All's good with pkgtools 23-2. Great work guys
-
[SOLVED] sudo pm-suspend requires password [SOLVED]
Can anyone tell me why sudo pm-suspend still requires a password even though I have set the following in my sudoers file
# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
# See the sudoers man page for the details on how to write a sudoers file.
# Host alias specification
# User alias specification
# Cmnd alias specification
# Defaults specification
# Defaults specification
# Reset environment by default
Defaults env_reset
# Set default EDITOR to vim, and do not allow visudo to use EDITOR/VISUAL.
Defaults editor=/usr/bin/nano, !env_editor
Defaults:ALL timestamp_timeout=0
# Runas alias specification
# User privilege specification
root ALL=(ALL) ALL
%power ALL=(ALL) NOPASSWD:/sbin/shutdown -h now
%power ALL=(ALL) NOPASSWD:/sbin/reboot
%power ALL=(ALL) NOPASSWD:/usr/sbin/pm-suspend
%power ALL=(ALL) NOPASSWD:/usr/sbin/pm-hibernate
%power ALL=(ALL) NOPASSWD:/usr/sbin/pm-powersave
# Uncomment to allow people in group wheel to run all commands
%wheel ALL=(ALL) ALL
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
And here are a list of the groups for my user
adm disk wheel locate games network video audio optical floppy storage power users kporter
Thanks ahead of time!
Last edited by kportertx (2010-07-15 06:00:15)# sudoers file.
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
# See the sudoers man page for the details on how to write a sudoers file.
# Host alias specification
# User alias specification
# Cmnd alias specification
Cmnd_Alias NETBOOK_CMDS = /usr/local/sbin/backlight, /usr/local/sbin/backlight_reset, /usr/local/sbin/wireless_toggle, /usr/local/sbin/cpufreq_toggle, /usr/sbin/pm-suspend
# Defaults specification
# Runas alias specification
# User privilege specification
root ALL=(ALL) ALL
meyithi ALL=(ALL) ALL
# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL
# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
%users ALL=(ALL) NOPASSWD: NETBOOK_CMDS
You definitely need the space, if you're not using visudo to edit sudoers it won't pick up the errors.
Maybe you are looking for
-
Flash is the problem. It often maxes both cores of my dual core processor and brings processing virtually to a halt. Originally, I killed flash in Task Manager whenever i heard my fan come on and also noticed slow system response. This was very distr
-
HT204545 cannot see photo library pictures in my apple devices
I cannot see photo library pictures in my apple devices. I bought extra storage of 200GB but none of them can be viewed from iPad/Phone Nila
-
Removing leading spaces in a decimal number
I have a decimal number field of length 28 with 9 spaces.I have to print it right justified and remove the leading spaces.I appreciate if anyone can let me the statement for this
-
Tip for embedding fonts while maintaining bookmarks
I've been sent a couple of very large PDFs in which the fonts aren't embedded properly. They're either missing, or the Adobe Serif MM has been used and embedded instead. This can cause the fonts to display and print poorly. Using the Preflight "Embed
-
My Screenlock froze, how do I make it work again?
My iPod screenlock isn't letting me through to my homepage, it did this two days ago but I got through. It's been on the charger for two days and it wouldn't let me open my home page, I have tried everything. How do you get it unfrozen?