Dir.mnu dependency conflict

Hi all,
I am using LV2009 SP1, and I am having an dir.mnu dependency conflict. See attached. The dir.mnu is in conflict with a lvlib in my instr.lib. I understand that dir.mnu is a generic name, but isn't it inside a lvlib, which will provide a library specific name scope? The error said that it is conflicting with a dir.mnu in Signal Processing, which is not used or even appear in my project. What's going on?
Kudos and Accepted as Solution are welcome!
Attachments:
1.JPG ‏29 KB

Hi Kevin,
I upgraded the inst drivers to the 2009 version.
Started a new project, made 2 new VI's
Placed the Keithley 2000 init into one VI
When I placed the HP E3631A init into the second VI this is what I get
I close and re-open the Project
Here is what I get when I open the "keithley 2000 dmm init.vi"

Similar Messages

Dependency conflict in LV 2009

Hello!
I migrate from LV8.6 to LV2009. I open existing project, developed with LV8.6. When i open one VI inside of the project the dependency conflict is reported. This message was not detected in LV8.6. The program is running normal, but i don't have explanation why is dependency reported in LV2009 and not in LV8.6.
Can you help me?
Attachments:
proj_open_vi.JPG ‏123 KB
proj_problem.JPG ‏74 KB
proj_reason.JPG ‏42 KB

Hello,
I'm facing problem like PROJECT DEPENDENCY CONFLICTS DETECTED.
I've copied drivers of hp 54520a fron LabView 8.6 's instr lib to Labview 2009 instr lib.
When I open the Calling vi.the confict detected window opens.And it shows the conflictins items which are all .mnu files.
these files are in hp54529a\public folder also and also in _template_generic folder.
I can't delete driver file as I've modified them according to my application.
and deleting files in generic folder also gives error.
got stuck.
vaishali

"dir.mnu warning" after editing the function palette

Hello everybody!
I´ve got a small problem, which is getting on my nerves! I created a new subfolder with vi´s in the function-palette (with the advanced palette tool)... after all i deleted it, because now i use other vi´s. So the problem is everytime i open a vi of my project which has something to do with the "signal processing palette", i got this warning that the "dir.mnu" has changed.
So far i created a new project, but the problem is still there... How can i restore the default palette settings? Can i delete the false dependencies? Or are there global files i can delete and then labview uses the default palette?
Thanks,
Michael
Attachments:
warning.JPG ‏28 KB

I think when i installed Labview, there was a symbol for every VI in the function-palette. Could it be that i somehow have overwitten the defaults in the ...\National Instruments\LabVIEW 2009\menus folder? So thats why the "restore defaults" button is grayed out, because these ARE the default values. Is it possible to get the "dir.mnu" for the signal processing subpalette (...\National Instruments\LabVIEW 2009\menus\Categories\Signal Processing\dir.mnu) of somebody?... Reinstalltation is al little more complicated, because the DVDs are at our computer administrative department.
So, thanks for your help....
Michael
Attachments:
palette.JPG ‏37 KB

[SOLVED] Dependency conflict details - hidden in new yaourt

Hi folks,
after recent upgrade of yaourt (to version 0.9.4-2) its behavior has changed. Previously, when there were a dependency conflict, it printed the reason. But now, there's only generic message. In yaourt and yaourtrc manuals isn't said anything about this feature. Besides, pacman still shows required info.
Compare pacman output:
$ sudo pacman -Su
:: Starting full system upgrade...
warning: e-modules-extra-svn: local (48190-1) is newer than community (47744-1)
warning: e_dbus-svn: local (48091-1) is newer than community (47398-1)
warning: ecore-svn: local (48064-1) is newer than community (47760-2)
warning: eet-svn: local (48204-1) is newer than community (47721-1)
warning: efreet-svn: local (48110-1) is newer than community (47737-1)
warning: eina-svn: local (48099-1) is newer than community (47741-1)
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-glibc-devel: requires lib32-glibc=2.11.1
and yaourt one (surely less logical):
$ yaourt -Su
error: failed to prepare transaction (could not satisfy dependencies)
Is it a bug or a hidden feature? If it's a feature, how it can be reversed to normal output?
P.S. The reason of conflict is quite clear (new AUR packages), but only with pacman help (
Last edited by Kosmonavt (2010-06-09 10:04:26)

Sorry, forgot to mark the topic as solved ) This way didn't help. I needed to remove lib32-glibc with -Rd, and then build lib32-glibc-devel again. Then it grabbed dependencies in a right way. Otherwise there was a circle - lib32-glibc couldn't be upgraded because dependency problem blocked upgrading, but lib32-glibc-devel wouldn't compile because of old lib32-glibc .

Dependency Conflict for eDirectory Installation

Hi,
I was installing eDirectory for the first time from NOWS SBE package which includes SLES 10, OES2 SP1.
I have reached the step where I need to select the OES pattern to install. Wanting to try it out first I selected eDirectory and iManager only and their respective dependent services including SMS, LUM and Remote Manager. When I check the dependency a warning pop up that says:
There are no installable providers of xntp for pattern:novell-edirectory
I know that I can configure the ntp server once I have installed the whole thing in YaST, but I don't understand why there would be a dependency conflict on this. I have to uncheck xntp package in the eDirectory details in order to move on.
Philip

Originally Posted by smflood
On 15/02/2011 23:36, sunnywood wrote:
> I was installing eDirectory for the first time from NOWS SBE package
> which includes SLES 10, OES2 SP1.
>
> I have reached the step where I need to select the OES pattern to
> install. Wanting to try it out first I selected eDirectory and iManager
> only and their respective dependent services including SMS, LUM and
> Remote Manager. When I check the dependency a warning pop up that says:
>
>
> There are no installable providers of xntp for
> pattern:novell-edirectory
>
> I know that I can configure the ntp server once I have installed the
> whole thing in YaST, but I don't understand why there would be a
> dependency conflict on this. I have to uncheck xntp package in the
> eDirectory details in order to move on.
Since it's not clear from the above, have you already got a server up &
running that you now want to install eDirectory on or are you trying to
install NOWS SBE?
I ask because I would expect an existing NOWS SBE install to already
have eDirectory (it's kind of a key component).
HTH.
Simon
Novell Knowledge Partner (NKP)
It is very clear that he said he was installing eDirectory for the first time. What happened is that when you install the patterns with a NOWS CD, yast will throw a dependency error saying that xntp is not available for installing the eDirectory. And if you check to install xntp under the base package, another dependency error will occur.
I just choose to ignore these errors and move forward with the installation, and then go back to install the xntp at a later stage.
William

Cannot upgrade due to dependency conflict

Hello, I wanted to upgrade my system through
pacman -Syu
However, the update procedure aborts with an error saying that Firefox-3.5 requires Xulrunner-1.9.1, below is the relevant part of the output:
resolving dependencies...
warning: dependency cycle detected:
warning: xorg-server will be installed before its nvidia-utils dependency
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: firefox-3.5: requires xulrunner=1.9.1
I have checked, and it seems that the correct version of xulrunner is installed:
$ pacman -Qi xulrunner
Name : xulrunner
Version : 1.9.1-1
URL : http://wiki.mozilla.org/XUL:Xul_Runner
Licenses : MPL GPL LGPL
Groups : None
Provides : gecko-sdk
Depends On : gtk2>=2.16.2 gcc-libs>=4.4.0 libidl2>=0.8.13 mozilla-common nss>=3.12.3 nspr>=4.8 libxt
hunspell>=1.2.8 startup-notification>=0.10 mime-types
Optional Deps : libgnomeui
Required By : firefox-3.5
Conflicts With : None
Replaces : gecko-sdk
Installed Size : 65784.00 K
Packager : Unknown Packager
Architecture : i686
Build Date : Fri 03 Jul 2009 03:46:14 PM CEST
Install Date : Fri 10 Jul 2009 06:03:42 PM CEST
Install Reason : Explicitly installed
Install Script : No
Google has given me little help in this issue, so I am asking wether someone else has already encountered this problem, and what the solution can be.

wonder wrote:
evr wrote:you shoud be able to force the update of xulrunner and then recompile firefox-3.5 with the new version. Any reason you're using that version instead of the firefox in extra?
why force it when it can do much easy. pacman -R firefox-3.5 and then pacman -Syu firefox
Hi, Wonder, thanks for the reply. That solved my problem.
Evr: I was using the AUR-version only by fault, I do not know how I have not seen that there was the same package available in the repositories as well...

Dependency conflicts when installing WebLogic Server Tools in Eclipse Juno

Installing the WebLogic Server Tools in Eclipse (Juno) on Windows 7, 64 bit cannot be completed. Eclipse is up to date and several other plugins are installed.
When installing the server tools, either via the Marketplace or the Server view -> New Server -> Download additional server adapters it fails because of incompatible dependencies. The error message is:
Cannot complete the install because one or more required items could not be found.
Software being installed: Oracle WebLogic Server Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.weblogic.feature.group 2.2.0.201211211917)
Missing requirement: Oracle Eclipse Tools Environment Checker 5.2.0.201211211917 (oracle.eclipse.tools.envcheck 5.2.0.201211211917) requires 'bundle org.eclipse.ui [3.8.0,3.104.0)' but it could not be found
Cannot satisfy dependency:
From: Oracle Common Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.common.feature.group 2.2.0.201211211917)
To: oracle.eclipse.tools.envcheck [5.2.0.201211211917]
Cannot satisfy dependency:
From: Oracle WebLogic Server Tools 2.2.0.201211211917 (oracle.eclipse.tools.juno.weblogic.feature.group 2.2.0.201211211917)
To: oracle.eclipse.tools.juno.common.feature.group 0.0.0
Does anyone know how to solve this and get the WebLogic Server Tools installed?
rob schlüter
Edited by: Rob Schlüter on Mar 11, 2013 3:12 AM

See this thread:
Juno 4.2 SR2 and OEPE
Until the next OEPE release comes out, you need to make sure that you are running with Juno SR1 when installing OEPE. Installing into Juno SR2 will not work.
- Konstantin

"Inherit" DIR authorizations from linked material

Hello All,
we would like to control DIR authorizations dependent on material master authorizations.
Example: User has "read"-authorization for material master (via authorization group of material master) means he has automatically "read"-authorizations for all linked documents.
Background: we want to control access to product (material) information and product documentation (linked documents such as data sheet, drawing...) at one place, e.g. the material master authorization group.
Any suggestions how to achieve this?
Thanks for all answers!
Best regards
Wolfgang Henkel

Only way to do this is through ABAP. Its not available as standard functionality. The only area of SAP that offers this is HR ArchiveLink which inherits the authorisations via infotype.

Dependecy conflict freetype2 vs freetype2-ubuntu

Hi there,
my system update just failed due to a dependency conflict. This is the output:
schorsch@archie:~$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: nvidia: ignoring package upgrade (180.22-1 => 180.29-3)
warning: nvidia-utils: ignoring package upgrade (180.22-1 => 180.29-3)
resolving dependencies...
looking for inter-conflicts...
:: freetype2 conflicts with freetype2-ubuntu. Remove freetype2-ubuntu? [Y/n] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: freetype2: conflicts with freetype2-ubuntu
schorsch@archie:~$
Why is pacman canceling the whole system update just because of freetype? Why can't I keep freetype2-ubuntu if pacman gives me the choice of saying "no"? How do I find out which package is requesting freetype2?
How should I proceed? Just add freetype2 to my IgnorePkg list?
TIA,
Blackhole

The freetype2-ubuntu package should have a "provides=('freetype2')" line in it. So, its not pacman's fault, but the PKGBUILDs fault...

Having difficulty creating MNU for packed library

Hello All,
I am using a packed library and I am attempting to create a .mnu for it.
I want to be able to drop my packed library into the user.lib or vi.lib folder so my coworkers and I can use common VI's.
Every time I create the .mnu and add it to my packed library, my links get broken.
I can create a .mnu using the Edit Palette Set.
I can add the .mnu to my packed library.
I can import the packed library .mnu using the Edit Pallete Set. But at this time, any VI's inside that menu are now just broken links.
I have tried multiple processes. What I have observed is I cannot import VI's from the library. I have to import them prior to being packed. So I copy all my VI's to my user.lib folder.
However, the path does not match the packed library.
How do I make a .mnu for a Packed Library with subdirectories and no broken links?
I need to be able to put it in any folder with the links of the packed library not being broken.
I would like to use subdirectories for easy navigation.
Do I need to put the VI's into a folder named the same file name as my packed library to preserve the relative paths?
I have searched the forums and the help and I am missing something. Perhaps I am doing things out of order.
Any advice would be helpful.

I sort of answered my own question. Here is what I did, for those who have similar issues.
1.) Opened my packed library project.
2.) Selected the top level project item.
3.) When to tools -> advanced -> edit palette set. (This is why I selected the top level item. for me, this option does nothing unless I select a VI or some sort of project in the file tree first. I can also do it inside a VI with no problems.)
4.) Under the user libraries, I created a new subpalette.
5.) Under new subpalette, I selected the fourth option (link directly to directory)
6.) I browse to the directory where I stored my VI's in the packed library. I DID Not move them to the user.lib folder.
7.) Once the import was completed, the VI's appeared in my control panel under user libraries. I also customized my Icons and directory names at this point.
8.) A dir.mnu file is created as part of the import inside the folder my VI's are contained in.
9.) I right click on the top level library in the project viewer, and select properties. I set the dir.mnu file as the default .mnu
10.) I build the library
11.) I copy my packed library into the user.lib folder.
12.) I once again go to edit palette set, I remove the palette created in step 5.
13.) I create a new palette, this time choosing option 5 (link to palette file in a project library). The packed library is now part of my control panel. My Icons and directories are preserved.
My project structure is to create a folder with the packed library project. I then have a subfolder called VI. Inside that volder I store all of my VI's that are part of the packed library project.
This seems to work. But I need to do more testing. I used basic structures. I have not done one yet with a more elaborate scheme such as sub palettes.

Multiple palette files in a library/class file causes problems

While developing a labview class, I wanted to set the default palette, so I added the relevant dir.mnu file to the class. Unfortunately, the class already had a dir.mnu file in it. On adding the file, I got some error message about a dependency change*(which makes no sesne, how can a palette file have any dependencies !). On saving the class and then attempting to reopen it, LabVIEW claims it is corrupt. Inspecting the xml .lvclass files reveals that when I added the new paletee file, LabVIEW actually just added a second reference to the palette file already in the project, which it then considers to be a problem when it tries loading the class. This is clearly a bug on a number of levels:
It should not be possible for the user to induce LabVIEW to create corrupt xml files through such simple attempts to use documented features.
The underlying problem is that LabVIEW appears to be using the conventional search/linking rules to load library items irrespective of whether they are a vi (which should ahve a unique name) or other file (which might well be legitimately non-unique).
Given the near impossibility of renaming a palette file without breaking palette links this particular bug is extra annoying.
Gavin Burnell
Condensed Matter Physics Group, University of Leeds, UK
http://www.stoner.leeds.ac.uk/
Solved!
Go to Solution.

Sorry for the delay, it took me a little longer to reproduce the problem systematically. Attached are three zip files of the same trivial class. The only difference between them is the contents of the class file itself.
The key point is that I have two folders in my class - Public and Protected (although I haven't actually set the access scope I realise). Each folder has a dir.mnu file in it and there is also a dir.mnu file in the main class folder. The class virtual folder structure maps directly to the on disc version.
In the first zip file the dir.mnu files are not added to the class.
In the second zip dile I added the dir.mnu by right clicking and doing Add file... This is allowed because each dir.mnu has a distinct path. I then save the class file and close it.
To get the third zip file, I reopen the class file. I get a single dependency warning about dir.mnu in one of the sub folders. So I think "fine ok, somethign funny about that dir.mnu file" - note if I'm loading a whole heirarchy of classes I may be told LabVIEW is laoding the dir.mnu file from somewhere completely different in my class structure. I then save the class file to give the thrid zip file.
The lvclass file in the third zip file is corrupt because it has multiple entries for the same file, because it didn't handle having more than 2 items conflicting.
The correct behaviour would be not to invoke the conflicting item names for non vi/ctl document types. I could imagine that there would be similar problems if I had a say a whole range of say README.html files strewn over the place.
Gavin Burnell
Condensed Matter Physics Group, University of Leeds, UK
http://www.stoner.leeds.ac.uk/
Attachments:
Break Class File-1.zip ‏21 KB
Break Class File-2.zip ‏21 KB
Break Class File-3.zip ‏21 KB

Missing VI - RF Record and Playback Reference Application

Tried to load and run "RF Record and Playback Reference Application" just posted on Developer zone. Have all correct versions of SW. Missing MITEoptimization.llb containing optimizeMITe.vi. Found the win32fileiovis but still missing this one. Reference to "file below" on web site but not there.

Thanks, Andrew. I do have the files, but the strangest thing happened. Although the locations of the web page linked to as well as the file locations appear to be identical, the file that is downloaded is different depending on whether I link to it with Firebird browser or IE. Same behavior whether I double click on the file or right click & save as
File sizes are 383KB (short file) and 628 KB (complete file including MITEOptimization and benchmarking files)
Using Winzip 9.0
Should be OK now though.
Tried again later and both were the same. Is it possible that I linked to different servers which had different files?? Noticed that dir.mnu in the win32filieio directory has different time stamp for the two.

Building multisync 0.8

Trying to build multisync 0.8 with the following PKGBUILD:
pkgname=multisync
pkgver=0.80
pkgrel=1
pkgdesc="MultiSync is a program to synchronize calendars, addressbooks and
url="http://www.multisync.org"
source=(http://heanet.dl.sourceforge.net/sourceforge/multisync/multisync-0.80-1.tar.gz)
build() {
cd $startdir/src/$pkgname-$pkgver
./autogen.sh --prefix=/usr
make || return 1
make prefix=$startdir/pkg/usr install
mv $startdir/pkg/usr/sbin $startdir/pkg
mkdir -p $startdir/pkg/etc
cp ../modules.conf $startdir/pkg/etc
Note: the pkgdesc line is actually complete (my eterm window was too small).
Makepkg ends on this:
if test -f $includefile; then
/bin/install -c -m 644 $includefile /home/hcman/sources/pkgs/multisync/pkg/usr/include/multisync;
fi
done
fi
mkdir -p -- /home/hcman/sources/pkgs/multisync/pkg/usr/include/multisync
rm -f /home/hcman/sources/pkgs/multisync/pkg/usr/include/multisync/*~
MultiSync syncengine installed.
** Now enter the plugins/ directory and build the *
** sync plugins you need. MultiSync will not be *
** able to do anything without these plugins. *
make[2]: Leaving directory `/home/hcman/sources/pkgs/multisync/src/multisync-0.80'
make[1]: Leaving directory `/home/hcman/sources/pkgs/multisync/src/multisync-0.80'
mv: cannot stat `/home/hcman/sources/pkgs/multisync/pkg/usr/sbin': No such file or directory
cp: cannot stat `../modules.conf': No such file or directory
==> Build Failed. Aborting...
Any tips?
HC

Ok, multisync works. I got the dependencies (I think) so this I think I will upload it.
This is the PKGBUILD
pkgname=multisync
pkgver=0.80
pkgrel=1
pkgdesc="A free modular program to synchronize calendars,
addressbooks and other PIM data"
url="http://www.multisync.org"
depends=('esd' 'openssl' 'gtk2' 'libgnomeui')
conflicts=()
backup=()
install=
source=(http://heanet.dl.sourceforge.net/sourceforge/multisync/multisync-0.80-1.tar.gz)
md5sums=('f1b1ff5665d7de82b2a2948752b818c7')
build() {
cd $startdir/src/$pkgname-$pkgver
./autogen.sh --prefix=/usr
make || return 1
make DESTDIR=$startdir/pkg install
Building one of the plugins, evolution_sync, I ran into some trouble.
I'm using this PKGBUILD (following red_over_blue's advice to keep it simple at first)
pkgname=evolution_sync
pkgver=0.80
pkgrel=1
pkgdesc="Ximian Evolution synchronization, supporting calendar, ToDos and contacts for Multisync"
url="http://www.multisync.org"
depends=()
conflicts=()
backup=()
install=
source=(http://heanet.dl.sourceforge.net/sourceforge/multisync/multisync-0.80-1.tar.gz)
build() {
cd $startdir/src/multisync-0.80/plugins/evolution_sync
./autogen.sh --prefix=/usr --with-evo-libs=/opt/gnome/lib/evolution/1.4
make || return 1
make DESTDIR=$startdir/pkg install
It goes to the correct dir (a subdir in the multisync source pkg) and configures and starts make. It ends on this:
make all-recursive
make[1]: Entering directory `/home/hcman/sources/pkgs/evolution_sync/src/multisync-0.80/plugins/evolution_sync'
Making all in libversit
make[2]: Entering directory `/home/hcman/sources/pkgs/evolution_sync/src/multisync-0.80/plugins/evolution_sync/libversit'
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -DORBIT2=1 -pthread -I/opt/gnome/include/evolution-1.4 -I/opt/gnome/include/gconf/2 -I/opt/gnome/include/libbonobo-2.0 -I/opt/gnome/include/gal-2.0 -I/opt/gnome/include/libgnome-2.0 -I/opt/gnome/include/orbit-2.0 -I/opt/gnome/include/bonobo-activation-2.0 -I/opt/gnome/include/libglade-2.0 -I/opt/gnome/include/libgnomeprint-2.2 -I/opt/gnome/include/gnome-vfs-2.0 -I/opt/gnome/lib/gnome-vfs-2.0/include -I/opt/gnome/include/libgnomeui-2.0 -I/opt/gnome/include/libgnomecanvas-2.0 -I/opt/gnome/include/libbonoboui-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/X11R6/include/freetype2 -I/usr/include/libart-2.0 -g -O2 -MT vcc.lo -MD -MP -MF ".deps/vcc.Tpo"
-c -o vcc.lo `test -f 'vcc.c' || echo './'`vcc.c;
then mv -f ".deps/vcc.Tpo" ".deps/vcc.Plo";
else rm -f ".deps/vcc.Tpo"; exit 1;
fi
../libtool: ../libtool: No such file or directory
make[2]: *** [vcc.lo] Error 1
make[2]: Leaving directory `/home/hcman/sources/pkgs/evolution_sync/src/multisync-0.80/plugins/evolution_sync/libversit'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/hcman/sources/pkgs/evolution_sync/src/multisync-0.80/plugins/evolution_sync'
make: *** [all] Error 2
When I run a regular ./configure, make it gives me the same thing so I'm thinking (hoping) it's not my PKGBUILD this time... :-)
Does it have something to with libtool since it complains it cannot find that?
HC

Step by step for 2.6

So I think im finally ready to make the plundge to the 2.6 kernel.
So I need some help. Ive only compiled a kernel a few times, and I never changed many settings.
So could someone give a step by step for it (being sure to list any arch-specific quirks)? I would greatly appreciate it.
Also, I hear theres a patch that lets you run the Official Nvidia drivers with the 2.6 kerne, has anyone gone through this? I really have no idea how to go about doing this,as i've only ever installed the .run file.
Any help would be appreciated.
Also, its possible to switch between the 2.4 and 2.6 kernel, right? (obviously with a reboot).
Lastly, Is a new release of the 2.6 due out anytime soon? I dont want to download and compile this just to find a new version comes out.

You have to use module-init-tools which supercedes modutils. I made a PKGBUILD for it for my local system simply so I could uninstall it easier if I wanted. However, you still need the old modutils as well.
Here is my hack to get module-init-tools working:
1. Use the PKGBUILD below to compile and install module-init-tools.
2. For each of modprobe, lsmod, rmmod, depmod, and modinfo from modutils, rename those to modprobe.old, lsmod.old, etc. To find where these binaries are, use "pacman -Ql modutils".
3. Create symbolic links from the binaries that modutils used to provide to the new binaries that module-init-tools provides. Again, use "pacman -Ql module-init-tools" to figure out where the new ones are.
Example - modutils provides /sbin/lsmod. Rename that to /sbin/lsmod.old. module-init-tools provides /usr/bin/lsmod. Create a symbolic link as follows:
[root@limbo root]# ln -s /usr/bin/lsmod /sbin/lsmod
If you aren't 100% sure what i am trying to say here, don't try any of it, or you will bork your system. Also, this is more of a hack, and that's why I didn't upload the package to incoming. I only made the PKGBUILD to keep track of where everything was going.
Anyway... hope this helps you on your way to:
[john@limbo john]$ uname -r
2.6.0-test5
[john@limbo john]$
PKGBUILD
pkgname=module-init-tools
pkgver=0.9.13
pkgdesc=""
url="http://www.kernel.org/pub/linux/kernel/people/rusty/modules/"
depends=()
conflicts=()
backup=()
install=
source=(http://www.kernel.org/pub/linux/kernel/people/rusty/modules/$pkgname-$pkgver.tar.gz)
build() {
cd $startdir/src/$pkgname-$pkgver
./configure
make || return 1
make prefix=$startdir/pkg/usr install

Xorg only allows access to 1 screen/monitor

I actually have this problem on two separate systems, both running an up to date stable Arch install. Both have the same xorg version (X.Org X Server 1.9.2), both running 2.6.36-ARCH kernel, both on x86_64. One is using an nVidia GeForce GTS 250, the other an ATI Radeon HD 4250. Both are using Fluxbox as the window manager.
I can use the main display and it works perfectly, but the 2nd display doesn't seem to have access. If I load X via startx, the first display loads just as it did before the problem started happening. The 2nd display loads, Fluxbox's menu bar displays at the bottom, and I can even change the desktops from 1-4. However, if I try to run any apps on the 2nd display, nothing can open it. I've tried running urxvt, chrome, anything, and get errors such as this:
(Opening a terminal app) urxvt: can't open display :1, aborting.
(Setting a desktop background) Esetroot: Unable to open display :1
(Running chrome) (chromium:5872): Gtk-WARNING **: cannot open display: :1
All the same. My systems rarely reboot, so it's hard to pinpoint what package could be the problem, as I never restart X or the system after upgrades, usually unless there is a power outage. I have tried removing all Fluxbox settings and starting with a stock setup, and the problem is the same. Any suggestions?

Unless things have changed, I'm pretty sure mixing ati with nvidia is tricky could be your trouble. I never tried mixing the two, but read a few times it's possible and think it's best to install the ati driver first and configure it before setting up the nvidia deiver. Even so, I think you may have to work out some dependency conflict between the two drivers? If you had it working before, I'm sure you figured all that out. Look at your /var xorg log file for EE errors. It will no doubt point you in the right direction.

Dir.mnu dependency conflict

Similar Messages

Maybe you are looking for