Date   
Re: Can not access UDRC after updating software

Annaliese McDermond
 



On May 29, 2018, at 10:10 AM, Herb Weiner <herbw@...> wrote:

Anna,

Thank you, thank you, thank you. Adding that missing line to config.txt and rebooting resolved the problem, and I can now see the UDRC with aplay -l and access the UDRC with alsamixer.

So now, the only remaining questions are:

  • Is there any known explanation for why my /boot/config.txt was missing the dtoverlay= line, or should I just accept that computers do funny stuff like this all the time?
Because it wasn’t necessary in the past.  To fix some other problems, we upgraded the alder kernel to 4.9.x rather than the previous 4.4.x line.  This was partially to keep up with what Raspbian is doing and make things work well together.  Unfortunately, the Device Tree Overaly, which tells the kernel what hardware is out there and where it lives on a hat like the udrc, was incorrect for the new kernel revision.  I made a new overlay, but the Pi has to be told to include it.  That’s what the config.txt changes are designed to do.  At some point we hope to have a field upgrader for the flash chip on the UDRC that should fix the error.  We need to make it pretty reliable and foolproof, though, otherwise we just cause more issues.
  • Should I be concerned that /etc/apt.d/sources.list.d/compass.list does not exist?
No.  I’m not in front of my Pi right now as I’m at $day_job, so I was going from memory on where we put the compass repository definition.
  • How can I determine whether I'm on the "alder" release?
It’s going to be in either /etc/apt/sources.list or in a file contained in /etc/apt/sources.list.d.  It’ll be a line that refers to archive.compasslinux.org.

Compass releases are named after trees in alphabetical order.  Alder was our first release, Birch was a failed release that was never ready for prime time, and we hope to come out with “cedar” soon.  The next will probably be “dogwood” but that’s a ways off.

Wilderness is our “experimental” builds.  That version is built on the very latest code nightly and packaged together into the images.  It’s a completely automated process and it isn’t tested in any way, so that version blows up occasionally when I need to do something to it.  People are more than welcome to use it with the understanding that I may blow up your whole Pi with a change I make at any point in time and I generally don’t react well to crying regarding that breakage.  The tree releases are considered to be stable and we try not to break those at all, and we certainly want to know if we do.

Herb

— Anna

Re: Can not access UDRC after updating software

Herb Weiner
 

Anna,

Thank you, thank you, thank you. Adding that missing line to config.txt and rebooting resolved the problem, and I can now see the UDRC with aplay -l and access the UDRC with alsamixer.

So now, the only remaining questions are:

  • Is there any known explanation for why my /boot/config.txt was missing the dtoverlay= line, or should I just accept that computers do funny stuff like this all the time?
  • Should I be concerned that /etc/apt.d/sources.list.d/compass.list does not exist?
  • How can I determine whether I'm on the "alder" release?

Herb

On May 29, 2018, at 9:50 AM, Jeremy McDermond <mcdermj@...> wrote:



On May 29, 2018, at 9:44 AM, Herb Weiner <herbw@...> wrote:

Anna,

First, thanks for all your help, and apologies for the name confusion.

No problem.  These things happen.


Perhaps I have a combination of incompatible components, since my Linux appears to be 4.9.80-v7+ although my Raspberry Pi bootloader is 1.20180525-1compass

pi@compass:~ $ cat /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
pi@compass:~ $ 

The kernel package version is different than the kernel version.  Confusing, I know, but because of the package versioning rules and what gets installed, it pretty much has to be done that way.

I think I see your problem here.  The bottom of your config.txt looks like this right now:


# Enable audio (loads snd_bcm2835)
dtparam=audio=on

force_turbo=1
dtoverlay=udrc

It should look like this

dtoverlay=
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

force_turbo=1
dtoverlay=udrc 

Note the line that reads “dtoverlay=“.  It is correct that it has nothing for the right hand side of the setting.  This ignore the device tree that is in the flash memory on the UDRC and uses whatever comes after instead.

— Anna


Herb

On May 29, 2018, at 8:30 AM, Jeremy McDermond <mcdermj@...> wrote:


On May 29, 2018, at 6:51 AM, Herb Weiner <herbw@...> wrote:

Jeremy,

It’s actually Anna or Annaliese now.  Thanks!

Thank you for your reply. Although I don't yet know if or how I can fix it, at least I'm beginning to get a better understanding of what I have.

pi@compass:~ $ dpkg -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version             Architecture        Description
+++-=============================-===================-===================-=============================
ii  raspberrypi-kernel            1.20180525-1compass armhf               Raspberry Pi bootloader
pi@compass:~ $ 

So, the Raspberry Pi bootloader is compass.

This means that your installed package for the Linux kernel is from Compass and not from the Pi Foundation.  If it were from the Pi Foundation it wouldn’t include the -1compass at the end

Just out of curiosity, I tried:

pi@compass:~ $ sudo apt-get install udrc-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package udrc-dkms
pi@compass:~ $ 

So, this explains why apt search udrc did not list udrc-dkms.

Right.  You appear not to be on wilderness, which is probably good.

II was not aware that apt-get upgrade would install unstable software. What I intended to do was to install the most up to date stable software. Is there something i should have done instead?

If you’re on the “alder” release, we endeavor to make sure that the apt-get update && apt-get upgrade process works correctly.  On Wilderness, anything goes.  You can tell the difference by looking in /etc/apt.d/sources.list.d/compass.list and seeing which of those words are in there.

In the mean time, it appears as though you have the drivers, they’re just not loading.  Can you post your config.txt and we may be able to see what’s up in there?

Herb

— Anna._,_._,_




Re: Can not access UDRC after updating software

Jeremy McDermond <mcdermj@...>
 



On May 29, 2018, at 9:44 AM, Herb Weiner <herbw@...> wrote:

Anna,

First, thanks for all your help, and apologies for the name confusion.

No problem.  These things happen.


Perhaps I have a combination of incompatible components, since my Linux appears to be 4.9.80-v7+ although my Raspberry Pi bootloader is 1.20180525-1compass

pi@compass:~ $ cat /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
pi@compass:~ $ 

The kernel package version is different than the kernel version.  Confusing, I know, but because of the package versioning rules and what gets installed, it pretty much has to be done that way.

I think I see your problem here.  The bottom of your config.txt looks like this right now:


# Enable audio (loads snd_bcm2835)
dtparam=audio=on

force_turbo=1
dtoverlay=udrc

It should look like this

dtoverlay=
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

force_turbo=1
dtoverlay=udrc 

Note the line that reads “dtoverlay=“.  It is correct that it has nothing for the right hand side of the setting.  This ignore the device tree that is in the flash memory on the UDRC and uses whatever comes after instead.

— Anna


Herb

On May 29, 2018, at 8:30 AM, Jeremy McDermond <mcdermj@...> wrote:


On May 29, 2018, at 6:51 AM, Herb Weiner <herbw@...> wrote:

Jeremy,

It’s actually Anna or Annaliese now.  Thanks!

Thank you for your reply. Although I don't yet know if or how I can fix it, at least I'm beginning to get a better understanding of what I have.

pi@compass:~ $ dpkg -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version             Architecture        Description
+++-=============================-===================-===================-=============================
ii  raspberrypi-kernel            1.20180525-1compass armhf               Raspberry Pi bootloader
pi@compass:~ $ 

So, the Raspberry Pi bootloader is compass.

This means that your installed package for the Linux kernel is from Compass and not from the Pi Foundation.  If it were from the Pi Foundation it wouldn’t include the -1compass at the end

Just out of curiosity, I tried:

pi@compass:~ $ sudo apt-get install udrc-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package udrc-dkms
pi@compass:~ $ 

So, this explains why apt search udrc did not list udrc-dkms.

Right.  You appear not to be on wilderness, which is probably good.

II was not aware that apt-get upgrade would install unstable software. What I intended to do was to install the most up to date stable software. Is there something i should have done instead?

If you’re on the “alder” release, we endeavor to make sure that the apt-get update && apt-get upgrade process works correctly.  On Wilderness, anything goes.  You can tell the difference by looking in /etc/apt.d/sources.list.d/compass.list and seeing which of those words are in there.

In the mean time, it appears as though you have the drivers, they’re just not loading.  Can you post your config.txt and we may be able to see what’s up in there?

Herb

— Anna._,_._,_



Re: Can not access UDRC after updating software

Herb Weiner
 

Gayland,

Thanks for trying. Learning is part of life.

Herb

On May 29, 2018, at 8:34 AM, Gayland Gump <kg7gcf@...> wrote:

live and learn

Gayland
KG7GCF

On Tue, May 29, 2018 at 8:31 AM, Jeremy McDermond <mcdermj@...> wrote:


> On May 29, 2018, at 7:27 AM, Gayland Gump <kg7gcf@...> wrote:
>
> Herb the command below will tell you if you have compass installed.  This is from one of my pis.
>
> pi@compass:~ $ uname -a
> Linux compass 4.9.35-v7+ #1 SMP Fri Feb 23 11:35:30 PST 2018 armv7l GNU/Linux

Actually, this doesn’t tell you at all if you have compass installed.  The second field is the hostname of the machine.  If you change it using /etc/hostname, it’ll end up being whatever you want.  The kernel version could be from anywhere, so that doesn’t help me much either.  The best way to figure out whether you have the compass kernel is by using dpkg -l.

> Gayland
> KG7GCF

— Anna






Re: Can not access UDRC after updating software

Herb Weiner
 

Anna,

First, thanks for all your help, and apologies for the name confusion.

Perhaps I have a combination of incompatible components, since my Linux appears to be 4.9.80-v7+ although my Raspberry Pi bootloader is 1.20180525-1compass

pi@compass:~ $ cat /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
pi@compass:~ $ 

It appears as if /etc/apt.d/sources.list.d/compass.list does not exist

pi@compass:~ $ cat /etc/apt.d/sources.list.d/compass.list 
cat: /etc/apt.d/sources.list.d/compass.list: No such file or directory
pi@compass:~ $ 

Here's my config.txt:

pi@compass:~ $ cat  /boot/config.txt
# For more options and information see
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

force_turbo=1
dtoverlay=udrc
pi@compass:~ $ 

Herb

On May 29, 2018, at 8:30 AM, Jeremy McDermond <mcdermj@...> wrote:


On May 29, 2018, at 6:51 AM, Herb Weiner <herbw@...> wrote:

Jeremy,

It’s actually Anna or Annaliese now.  Thanks!

Thank you for your reply. Although I don't yet know if or how I can fix it, at least I'm beginning to get a better understanding of what I have.

pi@compass:~ $ dpkg -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version             Architecture        Description
+++-=============================-===================-===================-=============================
ii  raspberrypi-kernel            1.20180525-1compass armhf               Raspberry Pi bootloader
pi@compass:~ $ 

So, the Raspberry Pi bootloader is compass.

This means that your installed package for the Linux kernel is from Compass and not from the Pi Foundation.  If it were from the Pi Foundation it wouldn’t include the -1compass at the end

Just out of curiosity, I tried:

pi@compass:~ $ sudo apt-get install udrc-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package udrc-dkms
pi@compass:~ $ 

So, this explains why apt search udrc did not list udrc-dkms.

Right.  You appear not to be on wilderness, which is probably good.

II was not aware that apt-get upgrade would install unstable software. What I intended to do was to install the most up to date stable software. Is there something i should have done instead?

If you’re on the “alder” release, we endeavor to make sure that the apt-get update && apt-get upgrade process works correctly.  On Wilderness, anything goes.  You can tell the difference by looking in /etc/apt.d/sources.list.d/compass.list and seeing which of those words are in there.

In the mean time, it appears as though you have the drivers, they’re just not loading.  Can you post your config.txt and we may be able to see what’s up in there?

Herb

— Anna._,_._,_


Re: Can not access UDRC after updating software

Gayland Gump
 

live and learn

Gayland
KG7GCF

On Tue, May 29, 2018 at 8:31 AM, Jeremy McDermond <mcdermj@...> wrote:


> On May 29, 2018, at 7:27 AM, Gayland Gump <kg7gcf@...> wrote:
>
> Herb the command below will tell you if you have compass installed.  This is from one of my pis.
>
> pi@compass:~ $ uname -a
> Linux compass 4.9.35-v7+ #1 SMP Fri Feb 23 11:35:30 PST 2018 armv7l GNU/Linux

Actually, this doesn’t tell you at all if you have compass installed.  The second field is the hostname of the machine.  If you change it using /etc/hostname, it’ll end up being whatever you want.  The kernel version could be from anywhere, so that doesn’t help me much either.  The best way to figure out whether you have the compass kernel is by using dpkg -l.

> Gayland
> KG7GCF

— Anna





Re: Can not access UDRC after updating software

Jeremy McDermond <mcdermj@...>
 

On May 29, 2018, at 7:27 AM, Gayland Gump <kg7gcf@...> wrote:

Herb the command below will tell you if you have compass installed. This is from one of my pis.

pi@compass:~ $ uname -a
Linux compass 4.9.35-v7+ #1 SMP Fri Feb 23 11:35:30 PST 2018 armv7l GNU/Linux
Actually, this doesn’t tell you at all if you have compass installed. The second field is the hostname of the machine. If you change it using /etc/hostname, it’ll end up being whatever you want. The kernel version could be from anywhere, so that doesn’t help me much either. The best way to figure out whether you have the compass kernel is by using dpkg -l.

Gayland
KG7GCF
— Anna

Re: Can not access UDRC after updating software

Jeremy McDermond <mcdermj@...>
 


On May 29, 2018, at 6:51 AM, Herb Weiner <herbw@...> wrote:

Jeremy,

It’s actually Anna or Annaliese now.  Thanks!

Thank you for your reply. Although I don't yet know if or how I can fix it, at least I'm beginning to get a better understanding of what I have.

pi@compass:~ $ dpkg -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version             Architecture        Description
+++-=============================-===================-===================-=============================
ii  raspberrypi-kernel            1.20180525-1compass armhf               Raspberry Pi bootloader
pi@compass:~ $ 

So, the Raspberry Pi bootloader is compass.

This means that your installed package for the Linux kernel is from Compass and not from the Pi Foundation.  If it were from the Pi Foundation it wouldn’t include the -1compass at the end

Just out of curiosity, I tried:

pi@compass:~ $ sudo apt-get install udrc-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package udrc-dkms
pi@compass:~ $ 

So, this explains why apt search udrc did not list udrc-dkms.

Right.  You appear not to be on wilderness, which is probably good.

II was not aware that apt-get upgrade would install unstable software. What I intended to do was to install the most up to date stable software. Is there something i should have done instead?

If you’re on the “alder” release, we endeavor to make sure that the apt-get update && apt-get upgrade process works correctly.  On Wilderness, anything goes.  You can tell the difference by looking in /etc/apt.d/sources.list.d/compass.list and seeing which of those words are in there.

In the mean time, it appears as though you have the drivers, they’re just not loading.  Can you post your config.txt and we may be able to see what’s up in there?

Herb

— Anna._,_._,_

Re: Can not access UDRC after updating software

Gayland Gump
 

Herb the command below will tell you if you have compass installed.  This is from one of my pis.

pi@compass:~ $ uname -a
Linux compass 4.9.35-v7+ #1 SMP Fri Feb 23 11:35:30 PST 2018 armv7l GNU/Linux


Gayland
KG7GCF

On Mon, May 28, 2018 at 6:55 PM, Herb Weiner <herbw@...> wrote:
John,

Thanks for your reply.

Would an apt-get update / upgrade have replaced the Compass kernel? Is there any way to tell? Is there any way to recover other than reinstalling Compass?

Note that the SeaPac 2017 tutorial on installing lighttpd explicitly suggested sudo apt-get update (RPi-workshop,session-1D,Tour-of-Applications) and never cautioned not to do sudo apt-get upgrade.

On a different note, what are the UDRC Support Files?

Herb

On May 28, 2018, at 6:06 PM, John D Hays - K7VE <john@...> wrote:

The UDRC driver is a kernel driver. If your actions replaced the Compass kernel, then the driver is likely not available. 

On Mon, May 28, 2018, 17:20 Herb Weiner <herbw@...> wrote:
Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
  UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)         
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $ 

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb 

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb











Re: Can not access UDRC after updating software

Herb Weiner
 

Jeremy,

Thank you for your reply. Although I don't yet know if or how I can fix it, at least I'm beginning to get a better understanding of what I have.

pi@compass:~ $ dpkg -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version             Architecture        Description
+++-=============================-===================-===================-=============================
ii  raspberrypi-kernel            1.20180525-1compass armhf               Raspberry Pi bootloader
pi@compass:~ $ 

So, the Raspberry Pi bootloader is compass.

Just out of curiosity, I tried:

pi@compass:~ $ sudo apt-get install udrc-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package udrc-dkms
pi@compass:~ $ 

So, this explains why apt search udrc did not list udrc-dkms.

II was not aware that apt-get upgrade would install unstable software. What I intended to do was to install the most up to date stable software. Is there something i should have done instead?

Herb

On May 28, 2018, at 9:14 PM, Jeremy McDermond <mcdermj@...> wrote:

What is the output of “dpkg -l raspberrypi-kernel”?

I’m assuming that since you’re on kernel version 4.9 that you’re running wilderness.  I recently made some changes to the repository in preparation for some future things.  Wilderness is always considered to be unstable and subject to breakage at any point in time.

If your raspberrypi-kernel package version doesn’t have the word “compass” in it, you’ve gotten the stock Raspbian kernel.  If that’s the case, you should bed able to do an “apt-get install udrc-dkms” to have the system compile and install drivers for you.

The udrc-support package does not include drivers for anything.  It includes some configuration files for the ALSA UCM system that were intended to make it easier to get settings right for the various connectors on the UDRC.

--
Annaliese McDermond (NH6Z)
nh6z@...

On May 28, 2018, at 6:55 PM, Herb Weiner <herbw@...> wrote:

John,

Thanks for your reply.

Would an apt-get update / upgrade have replaced the Compass kernel? Is there any way to tell? Is there any way to recover other than reinstalling Compass?

Note that the SeaPac 2017 tutorial on installing lighttpd explicitly suggested sudo apt-get update (RPi-workshop,session-1D,Tour-of-Applications) and never cautioned not to do sudo apt-get upgrade.

On a different note, what are the UDRC Support Files?

Herb

On May 28, 2018, at 6:06 PM, John D Hays - K7VE <john@...> wrote:

The UDRC driver is a kernel driver. If your actions replaced the Compass kernel, then the driver is likely not available.

On Mon, May 28, 2018, 17:20 Herb Weiner <herbw@...> wrote:
Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
 UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
 udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)         
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
 Subdevices: 8/8
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
 Subdevice #4: subdevice #4
 Subdevice #5: subdevice #5
 Subdevice #6: subdevice #6
 Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
    HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
Pi 3 Model B Mfg by Embest
Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
  Static hostname: compass
        Icon name: computer
          Chassis: n/a
       Machine ID: 493bfc529b1c440f94d670686c0263bc
          Boot ID: 760f60dafb7349639167134b74bcbbc2
 Operating System: Raspbian GNU/Linux 8 (jessie)
           Kernel: Linux 4.9.80-v7+
     Architecture: arm
----- direwolf
ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb



















Re: Can not access UDRC after updating software

Jeremy McDermond <mcdermj@...>
 

What is the output of “dpkg -l raspberrypi-kernel”?

I’m assuming that since you’re on kernel version 4.9 that you’re running wilderness. I recently made some changes to the repository in preparation for some future things. Wilderness is always considered to be unstable and subject to breakage at any point in time.

If your raspberrypi-kernel package version doesn’t have the word “compass” in it, you’ve gotten the stock Raspbian kernel. If that’s the case, you should bed able to do an “apt-get install udrc-dkms” to have the system compile and install drivers for you.

The udrc-support package does not include drivers for anything. It includes some configuration files for the ALSA UCM system that were intended to make it easier to get settings right for the various connectors on the UDRC.

--
Annaliese McDermond (NH6Z)
nh6z@...

On May 28, 2018, at 6:55 PM, Herb Weiner <@herbw> wrote:

John,

Thanks for your reply.

Would an apt-get update / upgrade have replaced the Compass kernel? Is there any way to tell? Is there any way to recover other than reinstalling Compass?

Note that the SeaPac 2017 tutorial on installing lighttpd explicitly suggested sudo apt-get update (RPi-workshop,session-1D,Tour-of-Applications) and never cautioned not to do sudo apt-get upgrade.

On a different note, what are the UDRC Support Files?

Herb

On May 28, 2018, at 6:06 PM, John D Hays - K7VE <@john_hays> wrote:

The UDRC driver is a kernel driver. If your actions replaced the Compass kernel, then the driver is likely not available.

On Mon, May 28, 2018, 17:20 Herb Weiner <@herbw> wrote:
Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver. I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <@herbw> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
HAT ID EEPROM
Name: hat
Product: Universal Digital Radio Controller II
Product ID: 0x0003
Product ver: 0x0001
UUID: f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor: NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
Pi 3 Model B Mfg by Embest
Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
Static hostname: compass
Icon name: computer
Chassis: n/a
Machine ID: 493bfc529b1c440f94d670686c0263bc
Boot ID: 760f60dafb7349639167134b74bcbbc2
Operating System: Raspbian GNU/Linux 8 (jessie)
Kernel: Linux 4.9.80-v7+
Architecture: arm
----- direwolf
ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb






Re: Can not access UDRC after updating software

Herb Weiner
 

John,

Thanks for your reply.

Would an apt-get update / upgrade have replaced the Compass kernel? Is there any way to tell? Is there any way to recover other than reinstalling Compass?

Note that the SeaPac 2017 tutorial on installing lighttpd explicitly suggested sudo apt-get update (RPi-workshop,session-1D,Tour-of-Applications) and never cautioned not to do sudo apt-get upgrade.

On a different note, what are the UDRC Support Files?

Herb

On May 28, 2018, at 6:06 PM, John D Hays - K7VE <john@...> wrote:

The UDRC driver is a kernel driver. If your actions replaced the Compass kernel, then the driver is likely not available. 

On Mon, May 28, 2018, 17:20 Herb Weiner <herbw@...> wrote:
Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
  UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)         
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $ 

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb 

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb










Re: Can not access UDRC after updating software

 

The UDRC driver is a kernel driver. If your actions replaced the Compass kernel, then the driver is likely not available. 


On Mon, May 28, 2018, 17:20 Herb Weiner <herbw@...> wrote:
Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
  UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)         
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $ 

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb 

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb






Re: Can not access UDRC after updating software

Herb Weiner
 

Gayland,

Thanks for your comment, which makes a lot of sense. So I tried:

pi@compass:~ $ apt search udrc
Sorting... Done
Full Text Search... Done
udrc-support/unstable,unstable 1.0 all
  UDRC Support Files

pi@compass:~ $ sudo apt-get install udrc-support
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  udrc-support
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 3,702 B of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://archive.compasslinux.org/ wilderness/main udrc-support all 1.0 [3,702 B]
Fetched 3,702 B in 0s (22.4 kB/s)         
Selecting previously unselected package udrc-support.
(Reading database ... 143096 files and directories currently installed.)
Preparing to unpack .../udrc-support_1.0_all.deb ...
Unpacking udrc-support (1.0) ...
Setting up udrc-support (1.0) ...
pi@compass:~ $ 

So, I installed the UDRC Support Files (whatever they are), rebooted, and tried again. Unfortunately, this did not resolve the problem. But again, thanks for the suggestion.

Herb 

On May 28, 2018, at 5:08 PM, Gayland Gump <kg7gcf@...> wrote:

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb






Re: Can not access UDRC after updating software

Gayland Gump
 

Going out on a limb here but the update may have resulted in a kernel sans the udrc driver.  I had similar problems when I used a build from the udrc wilderness or whatever the heck it is called.

Gayland
KG7GCF

On Mon, May 28, 2018 at 4:14 PM, Herb Weiner <herbw@...> wrote:
After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb


Can not access UDRC after updating software

Herb Weiner
 

After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb

UDRC not accessible after apt-get update upgrade

Herb Weiner <herbw@...>
 

After updating the software on my Raspberry Pi (apt-get update upgrade), I am no longer able to access my UDRC.

aplay -l shows

**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 8/8
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
  Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I checked my /boot/config.txt and the last line (dtoverlay=udrc) was missing, so I added it back in and rebooted. The last two lines are now:

force_turbo=1
dtoverlay=udrc

I then ran the following diagnostic commands that were recommended in a different thread, with the following results:

pi@compass:~ $ git clone https://github.com/nwdigitalradio/n7nix
fatal: destination path 'n7nix' already exists and is not an empty directory.
pi@compass:~ $ cd n7nix/systemd/bin
pi@compass:~/n7nix/systemd/bin $ ./udrcver.sh
Found a UDRC II
     HAT ID EEPROM
Name:        hat
Product:     Universal Digital Radio Controller II
Product ID:  0x0003
Product ver: 0x0001
UUID:        f9697d40-293b-4bb6-9940-81b0decc3a53
Vendor:      NW Digital Radio
pi@compass:~/n7nix/systemd/bin $ ./piver.sh
 Pi 3 Model B Mfg by Embest
 Has WiFi
pi@compass:~/n7nix/systemd/bin $ ./sysver.sh
----- /proc/version
Linux version 4.9.80-v7+ (jenkins@jenkins) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Fri May 25 08:05:14 PDT 2018
----- /etc/*version
8.0
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
---- systemd
   Static hostname: compass
         Icon name: computer
           Chassis: n/a
        Machine ID: 493bfc529b1c440f94d670686c0263bc
           Boot ID: 760f60dafb7349639167134b74bcbbc2
  Operating System: Raspbian GNU/Linux 8 (jessie)
            Kernel: Linux 4.9.80-v7+
      Architecture: arm
----- direwolf
 ver: Dire Wolf version 1.4
pi@compass:~/n7nix/systemd/bin $ 

./udrcver.sh does show that the UDRC is properly installed, so why can't aplay and related utilities find it?

Thanks.
Herb

Re: newbie in stall DR1 Probs

Duff <wa7bfn@...>
 

Hi John

Thanks for the help….it’s up and running… not sure why, but there was a double file in the dstarrepeaterconfig… eliminated that and bam we be working…

Interesting.  Anyway thanks again for all the help

73’s

Duff WA7BFN

WA7DRE Dstar Repeater Spokane 145.150.

Washington Digital Radio Enthusiasts

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of John D Hays - K7VE <john@...>
Sent: Tuesday, May 22, 2018 6:56:35 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] newbie in stall DR1 Probs

 

What version of firmware is on the DR-1X?

 

On Tue, May 22, 2018 at 11:56 AM, John D. Hays <john@...> wrote:

The internal controller of the DR-1X handles repeating for Analog and Fusion.  The UDRC is listening to the discriminator for a D-STAR and takes over control when it hears a D-STAR transmission. The rest is configuration.

Which setup screen is locking up (repeater or the dstarrepeater application)?   

Best to review your setup against the Wiki documentation.

Make sure the repeater has a PL (123.0 is my choice, avoid 100.0) on send and receive and that it is set to remote mode.

 

 

 

On Tue, May 22, 2018 at 11:44 AM, Duff <wa7bfn@...> wrote:

Seems to be.repeats FM ok.  However the setup screen is locked out unless I remove the dsub15

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of John D Hays - K7VE <john@...>
Sent: Tuesday, May 22, 2018 11:18:42 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] newbie in stall DR1 Probs

 

Is the dstarrepeater set to duplex mode?

 

On Tue, May 22, 2018 at 11:08 AM, Duff <wa7bfn@...> wrote:

UDRCII Decodes the Dstar signal…however does not repeat… any clues…

 

 

Sent from Mail for Windows 10

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Duff <wa7bfn@...>
Sent: Tuesday, May 22, 2018 8:52:29 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] newbie in stall DR1 Probs

 

HI John;

# Uncomment this to enable the lirc-rpi module

#dtoverlay=lirc-rpi

 

# Additional overlays and parameters are documented /boot/overlays/README

 

# Enable audio (loads snd_bcm2835)

#dtparam=audio=on

 Looks to be correct  



 

--

 

John D. Hays
Edmonds, WA

K7VE

 

   

 



 

--

 

John D. Hays
Edmonds, WA

K7VE

 

   

 



 

--

 

John D. Hays
Edmonds, WA

K7VE

 

   

 

Re: newbie in stall DR1 Probs

 

What version of firmware is on the DR-1X?

On Tue, May 22, 2018 at 11:56 AM, John D. Hays <john@...> wrote:
The internal controller of the DR-1X handles repeating for Analog and Fusion.  The UDRC is listening to the discriminator for a D-STAR and takes over control when it hears a D-STAR transmission. The rest is configuration.

Which setup screen is locking up (repeater or the dstarrepeater application)?   

Best to review your setup against the Wiki documentation.

Make sure the repeater has a PL (123.0 is my choice, avoid 100.0) on send and receive and that it is set to remote mode.



On Tue, May 22, 2018 at 11:44 AM, Duff <wa7bfn@...> wrote:
Seems to be.repeats FM ok.  However the setup screen is locked out unless I remove the dsub15


From: udrc@...o <udrc@....io> on behalf of John D Hays - K7VE <john@...>
Sent: Tuesday, May 22, 2018 11:18:42 AM
To: udrc@...o
Subject: Re: [udrc] newbie in stall DR1 Probs
 
Is the dstarrepeater set to duplex mode?

On Tue, May 22, 2018 at 11:08 AM, Duff <wa7bfn@...> wrote:

UDRCII Decodes the Dstar signal…however does not repeat… any clues…

 

 

Sent from Mail for Windows 10

 


From: udrc@...o <udrc@....io> on behalf of Duff <wa7bfn@...>
Sent: Tuesday, May 22, 2018 8:52:29 AM
To: udrc@...o
Subject: Re: [udrc] newbie in stall DR1 Probs
 
HI John;
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
 
# Additional overlays and parameters are documented /boot/overlays/README
 
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
 Looks to be correct  




--


John D. Hays
Edmonds, WA
K7VE

   




--


John D. Hays
Edmonds, WA
K7VE

   




--


John D. Hays
Edmonds, WA
K7VE

   

Re: newbie in stall DR1 Probs

 

The internal controller of the DR-1X handles repeating for Analog and Fusion.  The UDRC is listening to the discriminator for a D-STAR and takes over control when it hears a D-STAR transmission. The rest is configuration.

Which setup screen is locking up (repeater or the dstarrepeater application)?   

Best to review your setup against the Wiki documentation.

Make sure the repeater has a PL (123.0 is my choice, avoid 100.0) on send and receive and that it is set to remote mode.



On Tue, May 22, 2018 at 11:44 AM, Duff <wa7bfn@...> wrote:
Seems to be.repeats FM ok.  However the setup screen is locked out unless I remove the dsub15


From: udrc@....io <udrc@....io> on behalf of John D Hays - K7VE <john@...>
Sent: Tuesday, May 22, 2018 11:18:42 AM
To: udrc@....io
Subject: Re: [udrc] newbie in stall DR1 Probs
 
Is the dstarrepeater set to duplex mode?

On Tue, May 22, 2018 at 11:08 AM, Duff <wa7bfn@...> wrote:

UDRCII Decodes the Dstar signal…however does not repeat… any clues…

 

 

Sent from Mail for Windows 10

 


From: udrc@...o <udrc@....io> on behalf of Duff <wa7bfn@...>
Sent: Tuesday, May 22, 2018 8:52:29 AM
To: udrc@...o
Subject: Re: [udrc] newbie in stall DR1 Probs
 
HI John;
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
 
# Additional overlays and parameters are documented /boot/overlays/README
 
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
 Looks to be correct  




--


John D. Hays
Edmonds, WA
K7VE

   




--


John D. Hays
Edmonds, WA
K7VE