1 9 10 11 12 13 180 Replies Latest reply on Dec 12, 2016 1:24 PM by hiassoft Go to original post
      • 150. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
        pronkert

        Matthias Reichl wrote:

        After that: could you check if the new precompiled 4.4.14 kernel works?

        I just tried the 4.4.14 version and unfortunately the result is the same as before.

             ssh volumio@192.168.178.47

             ssh: connect to host 192.168.178.47 port 22: Host is down

        • 151. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
          clem57

          Does this work?

          ping 192.168.178.47

          Clem

          • 152. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
            pronkert

            No response...

                 Request timeout for icmp_seq 4

                 ping: sendto: Host is down

            • 153. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
              clem57

              Could this be the wrong ip? How did you determine what ip to use? Otherwise the image is not using dynamic ip...

              Clem

              • 154. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                pronkert

                The RPi is connected to my router with a cable. The routers webinterface shows all connected devices so I can determine the Pi's IP.

                But now it doesn't show up there anymore so I guess it doesn't even get an IP which makes it hard to ping.

                • 155. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                  clem57

                  Check the cable for kinks or if you have another cable, try it. Also ports get loose and ned to be reseated. Clicks indicate good connection.

                  C

                  • 156. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                    pronkert

                    The cable is fine. I reinstalled Volumio 2 and made sure everything worked as it should. The RPi boots up and I can reach it with a web browser or ssh.

                    While logged in over ssh I download the tarball and ran `sudo tar zxf cirrus-linux-4.4.14.tgz -C /`

                    Then I added `dtoverlay=rpi-cirrus-wm5102` and `dtoverlay=i2s-mmap` to `/boot/config.txt`

                    After a `reboot` I can no longer connect through browser or ssh and the RPi no longer shows up in the overview of connected devices in my router. In the meantime the cable was never disconnected so that connection should be fine.

                    • 157. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                      hiassoft

                      I just had a look at volumio 2 (RC2 hotfix):

                       

                      It's setup is a quite different to Raspbian, it uses an initrd which sets up squashfs+overlayfs for the root partition. If you update the kernel, the modules in the initrd no longer match the kernel version, so it can't load them and setup the root filesystem which results in a nice kernel crash (visible if you connect a monitor or a serial console cable).

                       

                      I'm not sure if there's an official way to update the initrd from within a running volumio installation (there's a "volumio-init-updater" in /root, but it doesn't have the executable bits set and I'm not sure how to use it), but by looking at the buildscripts of the volumio system I figured out a way how to do it.

                       

                      After a fresh installation you first have to extract the existing initrd, there's one file we need from it, "init", which must be placed in the /root folder. Best do everything as root (use "sudo -s")

                      root@volumio:~# mkdir initrd
                      root@volumio:~# cd initrd/
                      root@volumio:~/initrd# gzip -c -d /boot/volumio.initrd | cpio -i
                      root@volumio:~/initrd# cp -a init /root/
                      

                      Then extract the cirrus kernel, setup the modprobe.d and config.txt files etc as usual (I also commented out "dtparam=audio=on" and "force_turbo=1" in config.txt - we don't want the onboard audio and I'm not sure force_turbo is a good idea on a RPi3 without a heatsink).

                       

                      Next better remove the old modules, (check version with "uname -r") - 4.4.9 in case of current Volumio 2. The script to create the initramfs might pick up the wrong modules (it just uses the first 2 directories). ATM this works fine, because alphabetical sorting puts 4.4.14 before 4.4.9, but it might fail in the future when volumio ships a different kernel version. Also we don't really need the old modules.

                      root@volumio:~# rm -rf /lib/modules/4.4.9*
                      

                       

                      Now you can create an updated initrd:

                      root@volumio:~# /usr/local/sbin/mkinitramfs-custom.sh -o /boot/volumio.initrd
                      

                       

                      Then reboot (which should now work), ssh into the RPi and check with "aplay -l" that the soundcard is there.

                       

                      Now the only thing left to do is run the appropriate usecase scripts like "Playback_to_Lineout.sh" etc. You only need to do that once, the settings are preserved via the alsa mixer settings accross reboots.

                       

                      so long,

                       

                      Hias

                      3 of 3 people found this helpful
                      • 158. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                        pronkert

                        Many many thanks for your investigation and solution!

                         

                        While typing this message I am enjoying music playing through the Cirrus DAC on my RPi running Volumio .

                        The only other option would have been to buy a new (better supported) DAC and I'm really glad that is not necessary.

                        • 159. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                          gkkpch

                          @Matthias,

                          you are right about volumio's initrd but you found a nice workaround. The volumio-init-updater does something else, it replaces the squash file on the second partition (as an alternative to doing this online).

                          We have not finished the kernel & initrd update part, yet. Getting the first version of Volumio 2 had our priority.

                          • 160. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                            rmd6502

                            I have a pi3, using your 4.4.14 kernel.  I also have a pi touchscreen display installed.  The Cirrus card doesn't show up at all, aplay -l says "no soundcards found" - here's the pastebins:

                            pi@robs-pi7:~ $ pastebinit /boot/config.txt

                            http://paste.debian.net/780269/

                            pi@robs-pi7:~ $ vcgencmd version | pastebinit

                            http://paste.debian.net/780270/

                            pi@robs-pi7:~ $ sudo vcdbg log msg 2>&1 | pastebinit

                            http://paste.debian.net/780271/

                            pi@robs-pi7:~ $ dmesg | pastebinit

                            http://paste.debian.net/780272/

                            pi@robs-pi7:~ $ lsmod | pastebinit

                            http://paste.debian.net/780273/

                            pi@robs-pi7:~ $ aplay -l | pastebinit

                            aplay: device_list:268: no soundcards found...

                             

                            I think the relevant lines in dmesg are:

                            [    4.606835] wm8804 1-003b: Failed to read device ID: -5

                            [    4.607095] wm8804: probe of 1-003b failed with error -5

                            [    4.628882] snd-rpi-wsp soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered

                            [    4.835827] snd-rpi-wsp soc:sound: ASoC: CODEC DAI wm5102-aif1 not registered

                             

                            I'll try removing the touchscreen display just in case.

                             

                            Thanks in advance!

                            • 161. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                              rmd6502

                              Yup, disconnecting the display did it!  Any way to have the display and soundcard too?  I was hoping to set up a portable audio station :-)

                              • 162. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                                hiassoft

                                Hi Gé!

                                you are right about volumio's initrd but you found a nice workaround. The volumio-init-updater does something else, it replaces the squash file on the second partition (as an alternative to doing this online).

                                We have not finished the kernel & initrd update part, yet. Getting the first version of Volumio 2 had our priority.

                                Thanks a lot for the info! A already thought this part might still be WIP (also maybe I missed some bits and pieces). No need to hurry, take your time, and good luck finishing the release!

                                 

                                so long,

                                 

                                Hias

                                • 163. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                                  hiassoft

                                  Hi Robert!

                                  I think the relevant lines in dmesg are:

                                  [ 4.606835] wm8804 1-003b: Failed to read device ID: -5

                                  [ 4.607095] wm8804: probe of 1-003b failed with error -5

                                  These are definitely the relevant lines, but it's puzzling why you get these when the touchscreen/display is connected - there shouldn't be a resource/GPIO conflict.

                                   

                                  These lines can indicate that the wm8804 reset (via GPIO) might have gone wrong and the wm8804 wasn't properly put into I2C mode. Usually that shouldn't happen unless someone/something drives the I2C bus during wm8804 reset. It could also happen when the voltage level on the I2C bus is too low. That part of the Cirrus card hardware design is rather awkward BTW...

                                   

                                  How are you powering the display? Have you tried using a separate, external power supply for it?

                                   

                                  Your config.txt looks fine, but also try to remove the "start_x" and "disable_camera_led" lines (there were some warnings/errors at the end of vcdbg log).

                                   

                                  so long,

                                   

                                  Hias

                                  1 of 1 people found this helpful
                                  • 164. Re: Driver fixes and updates to kernel 3.18.16 and 4.0.5
                                    rmd6502

                                    That could be - I'll give that a try later.  I was using a single 5v1a supply, but then added a 5v1.5a supply - I'll remove the power wire so only the monitor is powered off the lower current supply and check the voltage on the i2c pullups.  I'll also apply the cleanups to config.txt that you suggest.

                                     

                                    I don't have a storage scope (an ancient but highly functional Tektronix from the '90s) so I can't check levels the instant the card starts up, though I suppose I could trigger on low voltage and see if I get a trace during startup...