pmpatrick

Try logging into kde and using the KRandRTray tool(Menu>Tools>System Tools>KRandRTray). That will put the KRandRTray icon in your kicker on the right hand side. Right clicking on that icon will give you a list of the screen resolutions and refresh rates available.

From the output you posted, you have a wireless card with a broadcom chipset. I found that mdv2008 was pretty buggy about how it handled these cards. Mandriva 2008 Spring, a/k/a, mdv2008.1, has cured all these broadcom bugs AFAICT. I would recommend that you seriously consider doing a fresh install of mdv2008.1 which can be freely downloaded from here: http://www.mandriva.com/en/download/free I can't begin to tell you how much aggravation I went through trying to get my broadcom wireless card working on mdv2008. There are some very complex timing issues with the way the relevant modules load that you can run into and it can be a real bear to deal with.

You can always just throw in a cheap nic until drivers arrive in the kernel for your onboard nic. I suspect your hardware is too new to expect linux drivers at this point, particularly since this is the first time I've heard of that Atheros lan controller. Correct me if I'm wrong, but I think those 750a chipset motherboards only came out about 4 or 5 months ago.

Most people that run servers use a separate partition for /var just because of this very problem. On a server, /var can fill up very fast and if its on the same partition as /, you can run into problems when your root partition gets close to full.

Here's a bash script I either wrote or picked up somewhere a long time ago that will give the directory size in bytes of the current directory: #!/bin/bash ## Script gives size of current directory in Bytes when executed let TotalBytes=0 for Bytes in $(ls -laR | grep "^-" | awk '{ print $5 }') do let TotalBytes=$TotalBytes+$Bytes done echo "${TotalBytes}"

Are you able to boot at all into windows? There should be an entry to select windows on the initial boot screen. If you are able to select and boot into windows and just want to change the default boot up to windows instead of linux, that's easy to do. If you are unable to boot into windows at all, that's mroe complicated.

That's pretty standard hardware. Shouldn't be any problem. I would suspect either a bad download or a bad burn. You can verify that you have a good download by verifying the md5sum of the iso you downloaded. You can do that in windows with many freely available applications. See, for example: http://www.md5summer.org/ md5sum is a system for verifying that two files are identical. When you run md5sum on a file it will generate a long series of letters and numbers like this for example - a74e36523069fdb1829f975cfb21e34b. On the website where you downloaded your mandriva iso, there should be a separate text file named md5sum or something similar which will give you the md5sum of that iso. When you run md5sum on your downloaded iso, you should get the same numbers and letters generated as those in that text file. If you don't get that, it means your downloaded file is different than what's on that website, i.e. it got corrupted in the download process. Checking whether you have a good burn is more problematic from within windows. Assuming your iso is not corrupted, you could try reburning at a slower speed. If you have access to another computer, you could try booting your dvd there. If you encounter similar problems on a different box, chances are high that you have either a bad download or bad burn. By the way, the current release for mandriva is 2008.1. If you have club access, you can download the 2008.1 powerpack version. If not, I would recommend that you try the free version of mdv 2008.1 which you can download here: http://www.mandriva.com/en/download/free Get the one that includes the drivers and plugins as that will have the proprietary nvidia driver for graphics card. It's a smaller download too(one cd) but after installation you can add all the additional software sources called "repos" using the "Easy Urpmi" link at the top of the page and virtually all the software on the powerpack version will be available to you and some that mandriva can't include for legal reasons(eg win32 codecs) will also be available for download and installation.

First, check the md5 sum on the iso you downloaded and make sure you have a good download. Next, post your hardware specifications, eg cpu(intel, amd), motherboard, type of hard drives(sata or pata), type of optical drives(ide or sata), amount of ram, etc.

Thanks ianw. That saved me a whole bunch of work trying to reconfigure all those java links. Resetting the java default to Sun's java 1.6.0 worked perfectly. Frostwire is running fine now.

I can answer that because I'm having the same problem. Here's my output using mdv 2008.1, frostwire-4.13.5-2 and java-1.7.0-icedtea-1.7.0.0-24.614.2mdv2008.1 as well as java-1.6.0-sun-1.6.0.05-1mdv2008.1(both included in the powerpack version): $ frostwire Starting FrostWire... Java exec found in PATH. Verifying... OOPS, you don't seem to have a valid JRE. FrostWire works best with Sun JRE available at http://www.java.com [java = openjdk] You need to upgrade to JRE 1.5.x or newer from http://www.java.com OOPS, unable to locate java exec in /usr/lib/ hierarchy You need to upgrade to JRE 1.5.x or newer from http://www.java.com ls: cannot access /usr/java/j*: No such file or directory OOPS, unable to locate java exec in /usr/java/ hierarchy You need to upgrade to JRE 1.5.x or newer from http://www.java.com ls: cannot access /opt/j*: No such file or directory OOPS, unable to locate java exec in /opt/ hierarchy You need to upgrade to JRE 1.5.x or newer from http://www.java.com It appears to be a linking problem as all the java stuff appears to be in various subdirectories of /usr/lib/jvm/ and frostwire is not searching there. I've tried making some links into /opt and other places to no avail but I haven't really studied the problem thoroughly. The linking is kind of complicated as /usr/bin/java links into /etc/alternatives/java which further links into the icedtea version of the java exec with links back into /usr/lib/jvm/. I'll have to experiment later but I'm considering removing the icedtea rpm and see if I can get the java exec to link into the sun version. It doesn't appear that frostwire likes the icedtea java version, however.

The next step in troubleshooting would be to see if you can ping one pc from the other. That would tell you if they can see each other on the network. From PC1, run: $ ping -c3 192.168.1.102 and from PC2: $ ping -c3 192.168.1.101 However, before doing that, on each PC go into MCC>Security>Set up your personal firewall and make sure the "Echo request" box is ticked otherwise the firewall will block ping. You could also try ticking the "Everything(no firewall)" box and see if that effects your ability to see NFS shares. That will eliminate your mandriva firewall as a potential source of the problem.

It's not clear to me what you are referring to here. On PC2 try going to MCC>Network Sharing>Use NFS Shares and try configuring through there. I can't remember if the necessary NFS packages are installed by default in mdv2008, but if they are not installed on PC2 you won't ever see the NFS shares in any configuration tool.

I seriously doubt you will be able to reliably run autocad in a virtualized environment. The virtualized hardware in VirtualBox and VMWare is pretty low spec and anything graphically demanding will not run properly. Your best bet would be VMWare as it has some basic 3d acceleration; VirtualBox does not. Take a look at this VirtualBox service ticket to see what I'm getting at: http://www.virtualbox.org/ticket/6 and more specifically:

After the recent flac/xine security updates amarok will no longer play flac files. In fact, all xine based players(totem, kaffeine, xine-ui) also no longer can play flac files. Audacious is able to play all my flac files however. I have installed the updated fix for the flac/xine packages but the problem remains. Running xine-ui from the command line I get this output when attempting to play any flac file: Prior to this update, flac files played fine in all my players. Anyone else having problems??

I think I could do it if the entire install isn't too big and you have identical hardware. I would use a slim linux livecd that you can easily modify; slax would be ideal as it's only 191 MB and contains scripts for creating customized isos: http://www.slax.org/ http://www.slax.org/documentation_customize_slax.php You would also need an extra hard drive that you would use to make the livecd with your installation on it. The basic procedure would be: 1. Do your installation of mandriva with all the configuration and additional software you want; 2. Boot up slax and create a backup of the MBR on your hard drive with the mandriva installation using the dd command. You will need this to recreate the partition structure and grub bootloader on the target boxes. The backup would be made to a file your second hard drive; 3. At the same time while in slax, make a tar gzip archive of each partition containing your mandriva installation to your second hard drive. The main limitation here will be the size of the tar archives since you ultimately want to transfer them to your customized slax livecd iso. In the past, I've had troubles creating a single file greater than 2GB within an iso. That used to be an iso file size limitation which I believe has been eliminated in the newer iso spec but I still see some people reporting problems with it; 4. Boot back into mandriva and create a customized slax livecd containing your MBR backup and your mandriva backup tar archives. Burn your customized slax livecd iso to dvd. Boot up with it on a new box to receive the installation and verify that you can recreate the partition structure/bootloader from your backup of the MBR and successfully extract your tar archives to your new partitions. Reboot the box and make sure you can boot into mandriva and that everything is working properly; 5. If everything went well, boot backup into mandriva on your original box with your second hard drive and create a bash script to automate what you did in 4 above for the transfer of the mandriva installation to the new box. Add this script to your customized slax livecd. Test to make sure your customized livecd with bash installation scrip works. That's a lot of work requiring a fairly high level of skill. If your not that familiar with linux and the commands I mentioned, I would not attempt it. Unless you have a large number of identical boxes to install mandriva on, it would probably not be worth the effort. Also, rather than cutomizing a livecd, it would probably be easier to backup your mbr and tar archives to an external usb hard drive while using a livecd like slax and then use the external hard drive backups to do your new installs. Another easy alternative is to put a blank hard drive in your box with the your mandriva install that you want to reproduce and copy it over with the dd command. Assuming your drive with your mandriva install is on sda and the blank hard drive is on sdb, you would run: # dd if=/dev/sda of=/dev/sdb and then go get yourself a cup of coffee. This will work perfectly if sda and sdb are the same size.

dude67, now that you mention it, I recall having similar problems trying to build the vboxdrv on the non-free version, albeit with a different kernel. I never could get the rpm version of the non-free version to work with any kernel in 2008. I would definitely uninstall the dkms-virtualbox package for starters and see if the module will compile.

dude67, you probably need the kernel source for the new kernel to compile the vboxdrv kernel module and it's not installed by default. See if you can get it to compile after installing kernel-source-2.6.22.18-1mdv-1-1mdv2008.0: # urpmi kernel-source-2.6.22.18-1mdv-1-1mdv2008.0

Same problem here. The easiest solution I found was to install the new kernel source, kernel-source-2.6.22.18-1mdv-1-1mdv2008.0, and then install the dkms package for VirtualBox, dkms-virtualbox-1.5.0-6mdv2008.0. Reboot and a new vbox module will be automatically rebuilt and installed. Note, I don't think the vbox_build_module command will work unless you first install the kernel source for the new kernel which is not installed by default.

It's a hardware problem alright - i.e. the hardware on your mdv2008/win2K box. Legacy BIOS is for booting up with a usb mouse and keyboard and not relevant to your problem. If other usb devices are working then usb has been activated in your bios setup. Try different usb plugs with the device and see if there's any difference. Also, does this drive have a separate external power source? If not, then the drive is operating off the power from the usb plug/bus. That's very limited and hard drives are right at the maximum power threshold that usb can provide. External hard drives without external power supplies tend to behave erratically, working on some systems but not on others. Many have dual usb plugins to get more power.

Mount the device from the command line. Determine the mount point by running this if you don't already know it: $ mount Then as root run: # chmod -R 777 <mount point> That should give the world rwx permissions on the drive. Then to safely remove the device run: # sync # umount <mount point> and physically remove the drive. Try reinserting it and see if you still get the permission problem.

How is the drive formatted, eg FAT, ext3, reiserfs?

With all due respect to my European friends, you are not licensed to practice law in the US. Since 1977, when our Congress passed the Foreign Corrupt Practices Act(FCPA) it has been a crime for any US enterprise to engage in bribery of foreign officials in order to obtain business. Sanctions include heavy fines and jail time: http://www.lectlaw.com/files/bur21.htm Most non-US countries do not have similar laws, unfortunately. Our companies have been complaining for thirty years that this puts them at a competitive disadvantage in many countries where bribery of public officials is a fact of business life.

I just started having some real problems connecting under kde's fish protocol with mdv2008. Previously it worked fine. Now every time I try I get the following error message: Oddly, I can always ssh between to the two boxes and use scp or sftp, even when I'm getting this error message with fish. I saw a bug report on this already. Wondering if anyone else is experiencing problems.

Post the chipset of your wireless card, eg broadcom, and which windows driver you are using with ndiswrapper. If it is a broadcom chipset, there are all kinds of timing issues with the native driver, bcmxx and ndiswrapper.

I assume that when you boot up your Debian system, your /home partition shows only 1GB being used. Double check that by running: $ df -h Compare that with the output you get when you run that command from within one of your livecds.