Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by dude67

  1. It's Mageia, but anyway...


    Here's what's in /etc/init.d directory:

    $ ll
    total 276
    -rwxr-xr-x 1 root root  1473 Apr 28 02:03 acpid*
    -rwxr-xr-x 1 root root  6963 Apr 30 13:29 alsa*
    -rwxr-xr-x 1 root root  1814 Mar  9  2011 apmd*
    -rwxr-xr-x 1 root root  1565 Apr 28 18:29 avahi-daemon*
    -rwxr-xr-x 1 root root  1212 May 12 02:40 bpalogin*
    -rwxr-xr-x 1 root root   706 Apr 28 02:52 cpufreq*
    -rwxr-xr-x 1 root root  2817 May  9 00:10 crond*
    -rwxr-xr-x 1 root root 10337 Jun 11 01:47 cups*
    -rwxr-xr-x 1 root root  1517 Apr 28 04:39 dm*
    -rw-r--r-- 1 root root 26126 Apr 28 04:39 functions
    -rwxr-xr-x 1 root root  7835 Apr 28 04:39 halt*
    -rwxr-xr-x 1 root root  1795 Feb  5  2012 hddtemp*
    -rwxr-xr-x 1 root root 17341 Jan 30  2012 hsqldb*
    -rwxr-xr-x 1 root root  4960 Apr 28 04:43 ip6tables*
    -rwxr-xr-x 1 root root  5496 Apr 28 04:43 iptables*
    -rwxr-xr-x 1 root root  1945 Apr 28 04:46 irqbalance*
    -rwxr-xr-x 1 root root   666 Apr 28 04:39 killall*
    -rwxr-xr-x 1 root root  2985 Apr 28 04:57 lm_sensors*
    -rwxr-xr-x 1 root root  2693 Mar  6 14:53 lvm2-monitor*
    -rwxr-xr-x 1 root root  1185 Dec  4  2011 mandi*
    -rwxr-xr-x 1 root root  4136 Apr 28 04:39 mandrake_everytime*
    -rwxr-xr-x 1 root root   345 Apr 28 04:39 mandrake_firstime*
    -rwxr-xr-x 1 root root  2844 Apr 30 03:27 messagebus*
    -rwxr-xr-x 1 root root  2360 Jan 16  2011 microcode_ctl*
    -rwxr-xr-x 1 root root  1791 Jan 26  2012 msec*
    -rwxr-xr-x 1 root root  3317 Apr 28 04:39 netconsole*
    -rwxr-xr-x 1 root root  5848 Apr 28 04:39 netfs*
    -rwxr-xr-x 1 root root  9540 Apr 28 04:39 network*
    -rwxr-xr-x 1 root root   535 Apr 28 04:39 network-auth*
    -rwxr-xr-x 1 root root  6593 Apr 28 04:39 network-up*
    -rwxr-xr-x 1 root root  4511 Sep 30  2011 nfs-common*
    -rwxr-xr-x 1 root root  4334 Sep 30  2011 nfs-server*
    -rwxr-xr-x 1 root root  3816 May 15 19:00 ntpd*
    -rwxr-xr-x 1 root root  1163 Apr 28 04:39 partmon*
    -rwxr-xr-x 1 root root  1495 Apr 28 06:31 portreserve*
    -rwxr-xr-x 1 root root  1413 May 12 02:45 pppoe*
    -rwxr-xr-x 1 root root  1323 Mar  8  2011 pptp*
    -rwxr-xr-x 1 root root  2116 Apr  6  2011 preload*
    lrwxrwxrwx 1 root root 	4 May 22 02:16 reboot -> halt*
    -rwxr-xr-x 1 root root  2155 Jan 13  2011 resolvconf*
    -rwxr-xr-x 1 root root  1617 May 20 15:02 rpcbind*
    -rwxr-xr-x 1 root root  2159 Apr 28 06:46 rsyslog*
    -rwx------ 1 root root  2981 Apr  9 15:10 shorewall*
    -rwxr-xr-x 1 root root   944 Apr 28 04:39 single*
    -rwxr-xr-x 1 root root  3864 Apr 30 13:29 sound*
    -rwxr-xr-x 1 root root  3486 Apr 28 06:17 sshd*
    -rwxr-xr-x 1 root root  1473 Oct 28  2011 vnstat*


    No pulseaudio there.


    But I can see pulseaudio in:

    $ locate pulseaudio

  2. First:

    # chkconfig --list | grep -i pulse
    Note: This output shows SysV services only and does not include native
     	systemd services. SysV configuration data might be overriden by native
     	systemd configuration.


    And then I cannot get the service to work:

    # service restart pulseaudio
    Cannot find restart service
    Usage: service -[Rfshv] SERVICE ARGUMENTS
       	-f|--full-restart:  	Do a fullrestart of the service.
       	-R|--full-restart-all:  Do a fullrestart of all running services.
       	-s|--status-all:    	Print a status of all services.
       	--ignore-dependencies:  Do not start required systemd services
       	--skip-redirect:    	Do not redirect to systemd
       	-d|--debug: 			Launch with debug.
       	-h|--help:          	This help.
    # service -f pulseaudio
    Cannot find /etc/init.d/pulseaudio
    Usage: service -[Rfshv] SERVICE ARGUMENTS
       	-f|--full-restart:  	Do a fullrestart of the service.
       	-R|--full-restart-all:  Do a fullrestart of all running services.
       	-s|--status-all:    	Print a status of all services.
       	--ignore-dependencies:  Do not start required systemd services
       	--skip-redirect:    	Do not redirect to systemd
       	-d|--debug: 			Launch with debug.
       	-h|--help:          	This help.


    I can't find the pulseaudio service in the services list in MCC... So is it runnig and if it's not, how can I start it? I see that pulseaudio packages are installed and should be running.


    $ pulseaudio
    E: [pulseaudio] pid.c: Daemon already running.
    E: [pulseaudio] main.c: pa_pid_file_create() failed.

  3. OK, got the BT working. But I'm not sure if it sticks... When I try to connect to the device (D80), it shortly tells me "Creative D80: audio service connection timeout". But I can see that the dongle is now connected (see BlueDevil.png).


    However, I cannot see the BT output in Pulse audio volume control devices (see PulseVolume.png). There's only Speakers and Headphones. This headphones requires small audioplug connection and there's no choice for bluetooth and the speakers obviously output the sound in the speakers (and not on the BT device).



  4. Thx Ian. I was going to try that, but now I can't get the dongle to work... I can find it in MCC hardware section - Bluetooth devices - Bluetooth USB dongle (module: btusb). But the notifier says "Bluetooth is off". And on the System Settings (KDE system settings) Bluetooth devices cannot find any devices...


    I'll try to sort this out first and then will let you know how this worked.

  5. I recently bought a Creative D80 BT speaker. I would like to be able to listen to my music collection on my backyard, but I cannot get the audio on my Acer laptop to play through BT dongle/Creative D80 speaker. I've managed to make the speaker work with my Nokia E7 phone and iPad (3rd gen), but how can I make my Mageia laptop play through BT.


    I was able to make the pairing OK (BlueDevil found the Creative D80 speaker OK), but I cannot direct the sound to the BT speaker.


    Is there anyone who would be able to help me out here...? :unsure:

  6. Yes, running Mag2 on two of my computers and they are working very nice. I was a bit upset about the non-free drivers missing and the free drivers for my NVidia NIC not working. That caused me problems on both machines. I couldn't get the screen to work for a long time. The solution for me was to get the system running up to the point where it stopped loading due to "no screen" and switching to another session with Ctrl-Alt-F2. Then I could log in and install the xorg vesa driver to get the screen to work (as Yankee did).


    Before I could come up with that solution I had to re-install the system and that whole upgrade/install mess was a pain. Still managed to keep my /home partition, but I think I messed up my other partitioning in the process as I was originally just updating from Mag1 to Mag2 through on-line upgrade.


    So once you know that issue (even with upgrade from Mag1 to Mag2) and get to boot to GUI (mine is KDE4), then it seems very nice. I haven't been able to use 3D desktop on my better rig (with NVidia GeForce GTX560 Ti 2GB), and the problems with Compiz continues as is the case with Yankee.


    But all and all, I've been very happy with Mageia - now running Mag2 and liking it.


    It does include Gimp 2.8.0 which has the single window mode and a few other goodies. :thumbs:

  7. I don't consider myself particularily talented, but do like to fool around with the graphics (gimp mainly)...


    Also, I'm quite busy at work these days, so I don't have too much leisure time on my hands.


    With all this, I don't know if I'm able to help, but if you like, I could take a shot at it. :unsure:


    = I'm not a gynecologist, but I'll take a look = :P

  8. .kde4 is a hidden directory directly under your /home/rogerh (replace rogerh with your username) directory. If you rename that directory, KDE4 will create you a new .kde4 folder with default settings.


    This helps if your KDE4 is not working correctly.


    Remember it's hidden, so if you use Dolphin remember to turn on the option to show hidden files (View - Show hidden files). If you use command line (terminal), then you should be able to see it right away.


    You can rename it .kde4.old (or something like that) so you can return to those settings, if you don't like the new (default) settings just by deleting the new .kde4 and renaming the .kde4.old back to .kde4.

  9. OK, thanks. That sounds so terribly easy... :) But, could you explain this a little bit more detailed for me...?


    I will first remove the current 750 GB sda (reported bad in SMART) and replace it with a new 1 TB disk. Do I need to mark it as failed, or just remove the old one and insert the new one?


    Then I do not get this part:

    Add a partition to it marked as Raid Autodetect.
    I should add a partition to the new disk (1 TB) marked as Raid Autodetect? For the hole disk or to a portion of it?


    How do I mark the second disk as missing in /etc/mdadm.conf?


    Sorry, but this is little confusing. Perhaps I should sleep on it :zzz: (and buy some new disks first) before trying to wrap my brain around this. :unsure:


    I'll get some new disks and try to get the bad disk replaced first. I'll post back after that.

  10. On this one set I'm not, I'm afraid.


    I could just install fresh Mageia1 on a new HD (let's say 1 TB) and then copy all from that 750 GB drive into the new one. But how can I set up (after copying the contents to the new hd) RAID1 (perhaps even with LVM) into an already installed hd?

  11. I have a set of two 750 GB Samsung Spinpoints installed as RAID1. Now one of the drives' SMART reports "bad" during boot even though the raid still seems to work fine.


    I don't seem to find an identical 750GB drive - and even though I may be able to find a suitable 750 GB drive or install a 1 TB drive (and lose 250 GB of that space), I may want to update my array to 1 TB if possible.


    So my question is: is it possible and if so, how do I do it?

  12. dude67, no one can force you to join the Mageia community and report bugs and no one can prevent your use of Mageia. :D


    But I am a member of the Mageaia forum and have asked there a question recently...


    I just thought this was a better forum for this type of question. Had it been a purely Mageia related problem, I would have asked it there.


    And I think it's their (the developers) loss, if they don't frequent here at MUB. We have a huge database of solutions to different problems. B)

  13. Now thinking about that, it would have had the same effect if I'd added the full path to the existing rule (40-usb_modeswitch.rules file).


    Perhaps I should test that. But if that's the case, how come it works with the first system and not the second?


    OK, in the first case (worked out of the box) it was recognized as

    Bus 002 Device 004: ID 12d1:1506 Huawei Technologies Co., Ltd.

    But in the second system (did not work originally) it was recognized as

    Bus 001 Device 008: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552 (HSPA modem)

    Is that the reason it worked on one machine and not on the other? If so I guess the question is: why is it recognized as different types in different Mageia1 system?

  14. Why did you seek help here on a Mandriva forum rather than on the Mageia forum?

    I knew that people here are friendly and have the knowledge regardless of the distro. And even though this forum's name is Mandrivausers, it's long been a general linux help forum.


    Please report the problem on the Mageia forum so others won't have to jump through the hoops that you did.

    I don't want to report this to another forum because I've already done this here, but can report a bug to Mageia if you think it's worth it. I can also link this conversation to the Mageia forum, but somehow I don't think the admins would appreciate it.


    Also I think one can find this if they Google...


    - EDIT - typo

  • Create New...