Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ianw1974

  1. Chances are it's wanting you to manually check the disk with fsck to fix it, because it can't do it on it's own. Probably wants you to choose yes or no for fixing a couple of things. I'd expect just some filesystem inconsistences other than a physical problem with the disk, although there is always a possibility for this. You'll need to boot it in single user mode (they might call it something else in the boot menu), there might be a boot entry for this, so that you can then fix it. Alternatively, if the computer boots normally, open a terminal and su to root and then type: init 1 that's the number one, so that you can be in single user mode and fix your partitions.
  2. This is what I have on Ubuntu 10.04 LTS: root@jasiek:/home/ian# aptitude search pulse | grep ^i i gstreamer0.10-pulseaudio - GStreamer plugin for PulseAudio i libcanberra-pulse - PulseAudio backend for libcanberra i libpulse-browse0 - PulseAudio client libraries (zeroconf supp i libpulse-mainloop-glib0 - PulseAudio client libraries (glib support) i libpulse0 - PulseAudio client libraries i libsdl1.2debian-pulseaudio - Simple DirectMedia Layer (with X11 and Pul i pulseaudio - PulseAudio sound server i pulseaudio-esound-compat - PulseAudio ESD compatibility layer i pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound serv i pulseaudio-module-gconf - GConf module for PulseAudio sound server i pulseaudio-module-x11 - X11 module for PulseAudio sound server i pulseaudio-utils - Command line tools for the PulseAudio soun i A vlc-plugin-pulse - PulseAudio plugin for VLC root@jasiek:/home/ian# aptitude search alsa | grep ^i i alsa-base - ALSA driver configuration files i alsa-utils - ALSA utilities i bluez-alsa - Bluetooth audio support i gstreamer0.10-alsa - GStreamer plugin for ALSA I know package names will vary etc, but generally working OK. Just connected a USB Jabra Speak 410 device to my system which didn't work at first until I gave it a firmware update under Windows, but then it worked under Linux fine when I chose it under the input and output settings in pulseaudio. Other issues might be running alsamixer and choosing the second device and making sure it's not muted. Had to do this with HDMI and if I remember with my bluetooth headset too. You can do this as root, by running: alsamixer or by specifying the card directly: alsamixer -c 1 thats a number one. Or, if you need to identify the devices: aplay -l thats a lowercase L.
  3. From your previous post, pulseaudio is running. Did you try rebooting with the Creative device attached? This would at least mean that it is detected by the system before pulseaudio starts, and maybe (long shot) it would be detected, like I mentioned about my HDMI sound issue. Other than that, I'm out of ideas, as if the system is detecting it correctly as a bluetooth audio device, it should be showing up. Have you got the bluetooth packages installed that would recognise it as a sound device? And also the pulseaudio packages that allow bluetooth usage?
  4. Not in touch with Mandriva lately, but check under /etc/init.d and see if there is anything relating to pulse here. Normally the service is pulseaudio, but could be anything I suppose.
  5. Have you tried with it being connected and rebooting the machine. Or perhaps try restarting pulseaudio - there should be init script for this: chkconfig --list | grep -i pulse and maybe something like: service restart pulseaudio I know I needed to restart when I wanted my HDMI audio connected. But I can't remember if just a restart of pulseaudio was enough.
  6. When you scroll down the output devices, does it show the Creative D80? I ask because I could see the scrollbar, so was wondering what else was lower down.
  7. Have you got pulseaudio installed? If so, when you go into the volume controls, you can choose the output there, there should be a couple listed I expect. Standard audio output and bluetooth output. I've done this with bluetooth headphones for use with Skype. I've also done similar, when trying to get sound over HDMI, so the process will be the same, but just to choose the second output thats listed in pulse audio under the volume controls.
  8. ianw1974

    cd -hd

    Hi, you don't need the CD, just remove the CD from the repositories, and configure the repositories to get packages from the internet.
  9. You will need to install the proprietary Nvidia drivers to get the HDMI to work. I had to do the same with my laptop, and then via pulseaudio you will also be able to choose HDMI for the sound output to go to the TV.
  10. Best bet is take a look at what cards fit your price range, then go to the Nvidia website for the driver downloads and see if their Linux drivers support the card you are looking to buy. My last Nvidia was bought in 2001 and was a Geforce TI 4400 which is old now, so best checking as I mentioned.
  11. 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.
  12. 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.
  13. 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.
  14. 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 -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 and if it replies, that means it's working. Then to save it: service iptables save
  15. 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.
  16. That's why it would be good to report the bug, because obviously something happened with the update.
  17. 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.
  18. 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.
  19. 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.
  20. You can change it, however, you can query some others, for example: dig @ google.com dig @ google.com see if you get DNS resolution. You can always edit /etc/resolv.conf and use Google DNS servers and or OpenDNS server and
  21. Check your /etc/resolv.conf to see if it has valid DNS settings.
  22. Check that this file exists: /usr/lib/libv4l/v4l1compat.so
  23. 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.
  24. Hi, What you said about your client computers is correct. They should get 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 can access the internet if you check DNS resolution and pinging something.
  • Create New...