Find the answer to your Linux question:
Results 1 to 2 of 2
I have a mythtv backend setup. But my audio keeps reversing on boot and reboot. Basically tuner1 audio is heard on tuner 2 or white noise is heard on tuner ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie Mad Professor's Avatar
    Join Date
    May 2006
    Posts
    142

    Need help creating udev rules.


    I have a mythtv backend setup. But my audio keeps reversing on boot and reboot. Basically tuner1 audio is heard on tuner 2 or white noise is heard on tuner 1 and tuner2 doesn't work.

    I posted this problem over at mythbuntu and someone said I need to set udev rules for my sound devices. But no one could tell me how to write them or if I wrote my rules correctly.

    /etc/udev/rules.d/10-mythsound.rules
    Code:
    KERNEL=="card0", SUBSYSTEM=="sound", ATTRS{id}=="Audigy2", SYMLINK+="dsp"
    
    KERNEL=="card1", SUBSYSTEM=="sound", ATTRS{id}=="SAA7134", SYMLINK+="dsp1"
    Code:
    pvr@pvr1:~$ udevadm info -a -p $(udevadm info -q path -n /dev/dsp)
    
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    
      looking at device '/devices/pci0000:00/0000:00:0b.0/sound/card0/dsp':
        KERNEL=="dsp"
        SUBSYSTEM=="sound"
        DRIVER==""
    
      looking at parent device '/devices/pci0000:00/0000:00:0b.0/sound/card0':
        KERNELS=="card0"
        SUBSYSTEMS=="sound"
        DRIVERS==""
        ATTRS{id}=="Audigy2"
        ATTRS{number}=="0"
    
      looking at parent device '/devices/pci0000:00/0000:00:0b.0':
        KERNELS=="0000:00:0b.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="EMU10K1_Audigy"
        ATTRS{vendor}=="0x1102"
        ATTRS{device}=="0x0008"
        ATTRS{subsystem_vendor}=="0x1102"
        ATTRS{subsystem_device}=="0x1001"
        ATTRS{class}=="0x040100"
        ATTRS{irq}=="19"
        ATTRS{local_cpus}=="ff"
        ATTRS{local_cpulist}=="0-7"
        ATTRS{modalias}=="pci:v00001102d00000008sv00001102sd00001001bc04sc01i00"
        ATTRS{broken_parity_status}=="0"
        ATTRS{msi_bus}==""
    
      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""
    
    pvr@pvr1:~$ udevadm info -a -p $(udevadm info -q path -n /dev/dsp1)
    
    Udevadm info starts with the device specified by the devpath and then
    walks up the chain of parent devices. It prints for every device
    found, all possible attributes in the udev rules key format.
    A rule to match, can be composed by the attributes of the device
    and the attributes from one single parent device.
    
      looking at device '/devices/pci0000:00/0000:00:0d.0/sound/card1/dsp1':
        KERNEL=="dsp1"
        SUBSYSTEM=="sound"
        DRIVER==""
    
      looking at parent device '/devices/pci0000:00/0000:00:0d.0/sound/card1':
        KERNELS=="card1"
        SUBSYSTEMS=="sound"
        DRIVERS==""
        ATTRS{id}=="SAA7134"
        ATTRS{number}=="1"
    
      looking at parent device '/devices/pci0000:00/0000:00:0d.0':
        KERNELS=="0000:00:0d.0"
        SUBSYSTEMS=="pci"
        DRIVERS=="saa7134"
        ATTRS{vendor}=="0x1131"
        ATTRS{device}=="0x7133"
        ATTRS{subsystem_vendor}=="0x1043"
        ATTRS{subsystem_device}=="0x4843"
        ATTRS{class}=="0x048000"
        ATTRS{irq}=="17"
        ATTRS{local_cpus}=="ff"
        ATTRS{local_cpulist}=="0-7"
        ATTRS{modalias}=="pci:v00001131d00007133sv00001043sd00004843bc04sc80i00"
        ATTRS{broken_parity_status}=="0"
        ATTRS{msi_bus}==""
    
      looking at parent device '/devices/pci0000:00':
        KERNELS=="pci0000:00"
        SUBSYSTEMS==""
        DRIVERS==""
    Any help is appreciated.

  2. #2
    Linux Newbie Mad Professor's Avatar
    Join Date
    May 2006
    Posts
    142
    No one knows how to do udev rules?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •