• Pop!_Planet is still very much under development. Data for the wiki is being sourced from the Arch Linux and Ubuntu wikis, along with a bunch of completely unique content specific to Pop!_OS, and sourcing, converting and updating that content takes time; please be patient. If you can't find what you're looking for here, check the Arch Linux and Ubuntu wikis.
  • Welcome!

    I'll get straight to the point.

    When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.

    Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.

    I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.

    Support Pop!_Planet

    Thank you for your time,

    Dan Griffiths
    Pop!_Planet Founder

Question Autostart a command with crontab

emilrudolf

New member
Sep 17, 2020
5
0
4
19
Hi,
In order to fix the sound on my Computer, I followed this guide: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439
with the solution:
Before run it, I installed alsa-tools:
sudo apt install alsa-tools


then I run these commands:
sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b
sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74


Awesome, the sound is working good now on UX533FTC and Ubuntu 20.04 LTS!


It does not work after rebooting.
So, I created bash script and run it on startup.


1) Create a bash script:


nano fix_sound.sh


#!/bin/bash


hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b
hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74


2) Change the permission of the script you saved
sudo chmod 774 fix_sound.sh


3) Add it to startup


sudo crontab -e


4) Then add this to your crontab:
@reboot /path/to/fix_sound.sh

The sound is fixed now, but the part with cronetab isn't working, so I have to insert the command after every reboot. A Picture of the cronetab FIle is below.
Can You spot what I did false there? I really don't know what I can do different.
Thank you a lot in advance,

emilrudolf

Bildschirmfoto von 2020-09-17 11-29-47.png



Bildschirmfoto von 2020-09-17 11-35-17.png
 

emilrudolf

New member
Sep 17, 2020
5
0
4
19
Now I know at least, what the Problem is:

I wrote: 2>/tmp/script-fehler.txt behind my comand in the Crontab, and got this as answer:

Bildschirmfoto von 2020-09-20 12-10-52.png

so the Problem must be with /home/emilrudolf/Downloads/ but I topple-checket it, and the scribt is in the Downloads folder, and the name is also write.
 

Members online

Latest posts

Latest projects

Forum statistics

Threads
1,105
Messages
5,079
Members
1,123
Latest member
KarlosMDK