watkinb

At work, I'm developing LabVIEW software to run on Mandrake 10.1. I've been building executable applications that have been running great for the past couple of weeks. Yesterday, I don't know how or why, but now if I double-click on the application file, it won't run. None of the other ones will run either if you double-click on them. They will run if invoked from a shell though. If I were just going to be using this setup myself, I wouldn't care as I pretty much operate from a shell most of the time anyway, but I'm going to have to train non-linux people to run my software on linux, and they don't know anything about shell commands, so they're going to be looking for a point and click environment. The predominant symptom is if I double-click on an application (that even has the MIME application string in the association), it prompts me to assign an assocation to run the file. I never had to do this before. What could have caused this problem, and does anybody know how to fix it? It's a fresh install of 10.1 and hasn't been altered except for some /etc/rc.local and /etc/profile entries. Also, while I'm thinking of it, sometimes it has problems running commands in shell scripts. Instead of just typing in # ./ShellScriptFilename I have to type in # sh ./ShellScriptFilename Any help is greatly appreciated. I wrote this in a hurry, so if I left anything out or if you need clarification, just let me know. Thx!

You guys are scholars and gentlemen! It worked! However, is this the best (and only) way to do this? It almost feels like a work-around. Bottom line is that it's working and that's just what I needed. Thank you guys so much for your help, you don't know how much you've helped me out! I know I haven't really asked for much, but I had run into a major problem with our unit testing setup at my company and have been fighting with my combination of Linux and other software for a couple of months. I've also been under a lot of pressure to get this resolved and it's these little problems that have been holding up progress on our project. Being a complete new-b to linux hasn't helped and our resident linux expert is completely tied up with other projects and couldn't help me. Now I'll be able to move forward on test development and hopefully we'll be able to meet our delivery deadline.

Sorry I posted it twice. I'm sortof in a hurry to get this part of the project finished. Thanks!

I'm currently running Mandrake 10.1 on a bootable USB HDD that's used to boot into various units under test (UUTs) for testing purposes. When I boot into some units, the boot process hangs a little during booting while probing (I think) hdc. It will return a DMA Timeout notification, but will continue booting as normal after a couple of tries. This isn't a major problem, but it slows down the booting process and will add extra unnecessary time to testing units. Since I'm not going to be accessing the onboard hard drive (at least for now) for our testing procedures, I don't need to bother with having hdc accessible through Mandrake. I've tried passing kernel arguments like "hdx=noprobe", "hdx=none" and it seems like they're being ignored by the boot process. I've tried this on Fedora as well and it behaves the same. Other kernel arguments I pass seem to be working though. I want to be able to access other drives, just ignore the on board hard drive and use only the usb hard drive. Am I missing something, passing the wrong kernel argument or what? Thanks guys (and gals?)!

Thanks, I'll give it a shot. I was doing some internet searches yesterday and was thinking that (if your suggestion doesn't work) udev might be to blame?

Where should you put it if you want the script to run for all users, especially if it needs to be run as root? /usr/share/autostart?

Okay, I think I found the command(s) that make the device file: # mkdir /dev/bus/vme # mknod --mode=666 /dev/bus/vme/ctl c 221 8 I think I know what's going on here. I executed this in a shell and then my commands that use the module work. I created an executable (#!/bin/bash ?) file and put it in /usr/share/autostart and put in the commands above, thinking maybe I could manually create them as a work around, but when I rebooted it didn't work. Anybody have any idea what's going on? I'm SOOOOO close to being finished with this... HELP!

Okay, I think I found which file it can't find. When I install the module, /dev/bus/vme/ctl is created. When these are present, my module works fine. When I reboot, ./bus/vme/ctl aren't there. Why would this disappear upon reboot?

I went to the mandrake control center, found the correct source and installed it. Thanks for the help guys! I installed the module and it created another directory in /lib/modules/ called "[kernelversion]custom" with an "extra/" directory beneath that one that contains my module's .ko file. For some reason, when I type "modprobe [modulename]" it can't find the module, so I copied the "extra/" directory and contents to the /lib/modules/[kernelversion]/kernel/ directory. After that, it works fine. Only problem is if I reboot, and modprobe my module, the module loads, but if I try to run some of the commands associated with the module I get "file not found" errors from the command. If I do a make install and reinstall the module, then it works fine again until the next reboot. It acts like a file, dependency or something that's put in place during an install is removed when rebooted. Strange?? I'm sure I didn't explain my problem very clearly. If anybody needs clarification on something, let me know. Another question while I have you on the line: The software I installed creates a module that I want to be loaded for any user account. I had successfully done this in fedora by editing /etc/profile and adding "modprobe [moduleName]". I did the same thing in mandrake, but until I get the above problem figured out, I can't verify that it's working. Can anybody give me advice on the best place/method of loading this module at boot time? [EDIT: Nevermind, found the answer for auto-loading modules here] Thanks!

I did get the source with urpmi, but it only pulled it from CD3. I don't have a working internet connection with it yet, (that's my next challenge, to find out what's wrong with that) so I can't set it up to search online yet. When I used urpmi, like I said, it grabbed the wrong kernel versio from my disk. I'm going to try the other route through the mandrake configuration utility.

okay, I did a "urpmi kernel-source" and used the iso disk #3. It created a directory (linux-2.4.28-0.pre2.1mdk) and link (linux@). Only problem is that if I do "uname -r" I get 2.6.8.1-12mdk, and the source code directory name is 2.4.28-0.... it put this in /usr/src. My vme-memory access software is looking at /lib/modules/2.6.8.1-12mdk/build - ORIGINAL. Can anybody tell me how to do this? I'm guessing I can change the directory in the Makefiles, but I'm also wondering if there will be a lot of things I'll miss.

Well, just an update on my own situation. I installed Mandrake 10.1 and it booted off of a USB drive without modification. I couldn't get 2005LE to work this way, but I may have tried to create a new initrd file without first trying it bone stock.

I downloaded kernel-2.6.8.1.12mdk-1-1mdk.src.rpm so that I can have the source code for my 2.6.8.1-12mdk kernel. I'm trying to install a linux vme-memory access program that needs the source code in order to do a "make install". I keep getting errors that it can't find the kernel source code in the /lib/modules/2.6.8.1-12mdk/build" directory. I installed the above rpm file, but it still can't find the source code in that directory. Does mandrake's source code install in a different directory? I can edit the Makefile file to point to a different directory for the source, but dont' know where that is (would it be /lib/modules/[kernel]/kernel?). Also, I'm new to linux and especially to mandrake/mandriva. I've been working with fedora on a current project and had to switch to mandrake 10.1. Thanks for any and all help! [moved from Software by spinynorman - welcome to the board :)]

I tried this method using Mandriva 2005LE and couldn't get it to work. Has anybody had any success in doing this with other versions? I'm kind of in a jam and need to get mine up and running really soon. I've been able to create a bootable usb hard drive with Fedora 2 Linux, but not with Mandriva. I ran into some problems with Fedora2 that Mandriva doesn't seem to exhibit upon installation. Mandriva.com offers "GlobeTrotter" which uses a LaCie 40GB HDD with Mandrake 10.0 installed. I have a LaCie 80GB HDD and Mandriva 2005LE and am trying essentially to do the same thing. I'm also currently downloading Mandrake 10.1 and am going to attempt the above method again hoping it will work.