Yeah, I think it does:
  $ X >/tmp/foo 2>&1
  $ grep -A1 ^sh /tmp/foo
  sh: sed: not found
  sh: grep: not found
  Not loading fglrx module; not used in /etc/X11/xorg.conf
  sh: sed: not found
  sh: grep: not found
  Not loading fglrx module; not used in /etc/X11/xorg.conf
  $ which sed
  /bin/sed
  $ which grep
  /bin/grep
The modprobe action is running with PATH=/sbin at that point, so you need full 
paths in /etc/modprobe.d/fglrx. 

Also, for some reason I don't yet understand, it still says fglrx is not
used after adding full paths to grep & sed, probably some quoting issue
or something.  I just removed /etc/modprobe.d/fglrx and it started
loading the module.

-- 
Module fglrx isn't loaded
https://launchpad.net/bugs/63912

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to