Jump to content

ianw1974

Admin
  • Content Count

    14036
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by ianw1974

  1. I prefer NVidia if I was to buy a separate card, otherwise onboard Intel or lastly ATI because of so many problems trying to get them working well enough. Although they seem a little bit better of late than a while back.
  2. Photorec is data carving, it doesn't care what the filesystem is, it looks at the sectors on the disk, and gives you random filenames. Testdisk is what you want if you want to recover with the filenames. Testdisk should be able to recover files and directories/folders from what I remember.
  3. Have you tried testdisk? It might be able to help. Photorec is part of the testdisk program, so if you have this installed, testdisk should be there somewhere. If not, you can download it and use it to try and recover.
  4. As I said, it depends what you're using, so if iptables, this is what you need to do: From here: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch14_:_Linux_Firewalls_Using_iptables#Masquerading_.28Many_to_One_NAT.29 iptables -A POSTROUTING -t nat -o eth0 -s 192.168.1.0/24 -d 0/0 -j MASQUERADE assuming that eth0 is your internet connection, because you mentioned eth1 is your internal network. Replace the IP address with your internal network if it's different. Check if your machines can then access the internet or simply from a machine do: ping 8.8.8.8 and if it replies, that means it's working. Then to save it: service iptables save
  5. iptable has the rules for setting the nat stuff with postforwarding. I'm not sure what firewall you are using that's why I mentioned about it generally. To get from a private address, so 192.168.x.x to a public address (internet) you need to nat to do it, and the PC that is your gateway to the internet needs to do this. Since you have ip_forwarding enabled, you need to set up the nat on this machine to let the other machines access the internet.
  6. That's why it would be good to report the bug, because obviously something happened with the update.
  7. Have you tried updating your system? If not, try doing this to see if they fixed it. If not, you can open a bug report with Mandriva and report it there, so that they can fix it.
  8. Let's get some misconceptions cleared up first. 1. Each distro is different and behave differently, so while in one distro you don't have to add your user to certain groups, in others you do. This is due to security and the fact that your user does not have the permissions to access the devices directly, whereas the groups do. Whilst you might not feel you have to do it, or shouldn't, sometimes you have to. The misconception here either comes from Windows users who expect things just to work, or that because you used one distro it worked, and then another it doesn't. Perhaps Mandriva changed and now made this a requirement. Or perhaps printerdrake sorts this out for you. 2. While the drake tools are good, sometimes they cause more problems than they actually solve. That's why sometimes, it's best to use the management apps that have been designed specifically for managing cups than printerdrake. The web-based cups interface is the best there is, but it's down to personal preference, and I've never ever come across anywhere that nobody like it - first time I saw it here when you wrote about it. That kind of information is not required and doesn't help in solving your problem. 3. Seeing that you cannot delete it from cups, but from printerdrake shows exactly why point 2 that I wrote about is completely valid. To print you need cups, and now you see that printerdrake is causing you more problems than it actually solves. 4. Task-printing is a virtual package for pulling in the dependencies needed for you to print. That's why it's zero bytes. So nothing to worry about here. And now, back to your problem. I would delete the printer from printerdrake, and manage it solely with cups, and ensure that you choose the correct make/model when you install it and see if it works. If not, the printer model might not be correct, and you might need to search the internet and find the correct PPD file to add the printer with this.
  9. If the clients are not working, then you need to check what the default route is on the machines and if they are the machine that is acting as the gateway to your internet. Also check DNS on these machines, because maybe its misconfigured. And if you enabled ip_forwarding in /etc/sysctl.conf. And NAT, if iptables then postrouting.
  10. You can change it, however, you can query some others, for example: dig @8.8.8.8 google.com dig @208.67.222.222 google.com see if you get DNS resolution. You can always edit /etc/resolv.conf and use Google DNS servers 8.8.8.8 and 8.8.4.4 or OpenDNS server 208.67.222.222 and 208.67.220.220.
  11. Check your /etc/resolv.conf to see if it has valid DNS settings.
  12. Check that this file exists: /usr/lib/libv4l/v4l1compat.so
  13. Try running skype from the console and see what it complains about in the console window. This is the best way to see what's going on, usually if something is missing it will tell you. I have a feeling though that the module is either not loaded for the camera, or the wrong one, or conflict between two modules.
  14. Hi, What you said about your client computers is correct. They should get 192.168.1.1 as the default gateway, because they then have their connection routed out to the internet here. Did you enable ip routing on this machine? You have the NAT working, but wondered if you enabled IP routing in /etc/sysctl.conf? You can check it easily, because it should have this line: net.ipv4.ip_forward = 0 these means that ip routing is disabled, so change it to: net.ipv4.ip_forward = 1 to enable it. Then try and see if the other machines can access the internet. I expect that machine 192.168.1.1 can access the internet if you check DNS resolution and pinging something.
  15. Yes, please change to: 127.0.0.1 myhost localhost localhost.localdomain .localdomain should not be added to your hostname.
  16. Make sure your /etc/hosts has your hostname in it and also shows localhost as well - you need this. 127.0.0.1 myhostname localhost something like this. Of course, myhostname being the name of your machine.
  17. ianw1974

    Mageia2-rc

    Thanks John for the info, do post back with your thoughts and views on your install and how it's working for you :)
  18. The link I provided in an earlier post shows the luna.svg for download, and also comments about people with the same problem and error that you were experiencing. People suggesting copying it to the correct location fixed the problem. Now, if you installed an rpm package, with urpmi or mcc or installing packages available in Mageia repos, and the luna svg is missing - this suggests only one of two situations. Either they built the package without including luna.svg or that it was included, but was located in the wrong place on the disk. And so why you experienced the problem. This is assuming of course, that you installed it how I believe you did. If it was installed using another method, then that would depend on the installation method to get that plasmoid installed, and again, didn't put luna.svg in the correct place that it should do.
  19. Package was built wrong, with the luna.svg in the wrong place. Assuming you installed this plasmoid from rpm of course, or using MCC. I expect that you did. Seems in the newer version it was fixed.
  20. Leave it installed, and manually copy the luna.svg to this location to fix it. Copy it from your Mageia 2 install, and place it in the correct location on Mageia 1. Or download fm the link I gave you previously.
  21. OK, understand that it installed properly, but it seems that luna.svg is missing, hence why I asked if you can verify with the commands I put to make sure the file is exactly there. If you've done this, and it is, then I'm expecting it's searching in a place where it should be but it isn't. Which was why wanted to find out, if the luna.svg is in the place where I mentioned it should be.
  22. Hi John, Try here, some comments about where to put the luna.svg: http://kde-look.org/content/show.php/luna.svg?content=93779 you can also download the luna.svg here. Alternatively, search to see if there is a luna package in Mandriva, if not, then download and unpack this to the correct location as per the comments in the link. It looks like it should be here: /usr/share/apps/desktoptheme/default/widgets/luna.svg You can always try to locate it: updatedb locate luna.svg of course, su to root first so that you can update the locate database, and then search. A slower method without updating the locate database, would be something like this: find / -iname luna.svg
  23. Are you using an NVIDIA card? If so, right click the flash movie and click settings and then disable the hardware acceleration. It will then be OK. As for the other error, please post exactly the error message, and will try to help.
  24. I would say something hardware related, try running memtest and see what happens. I've had problems recently with an old laptop and the graphical display crashing on me, but from the console the laptop would work fine. Took the whole thing apart and cleaned it out, removing the CPU, memory and reseating all the components. I would try this and see what happens. Also go into your BIOS and choose the Load Optimised Defaults option to ensure no bad setting has been chosen in here. Incorrect memory config in the BIOS can cause hardware issues, I've had this as well. The i915.modeset or nomodeset or other such boot options are only for when you start X, GDM, KDM etc and get a black screen and the system stops responding. This isn't going to help your X crashing problem. If you see X/GDM/KDM normally, then this is not going to help in this instance.
  25. Having auto in fstab is a bad idea, because if you boot the machine without a disk in the drive it will attempt to mount something that is not there. If you have an fstab entry for it, it must be noauto.
×
×
  • Create New...