Code:
[root@wandboard ~]# iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=1496 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Got an 8 GB SD card today.
Downloaded, installed and configured F19 Alpha 1 on a Wandboard DUAL.
Im running LMS on my NAS and audio is outputted through SPDIF (coax).
Happy to report that all works well.
But I had to manually delete Desktopjive.lua again in order to get
TriggerOutput to work.
dsdreamer wrote:
I too can get alsamixer to work, but *only* by addressing the hardware
card directly, with alsamixer -c0. Are you stating that alsamixer
typed on its own (no additional options on the same line) works for you?
I've not looked at it yet, but I suspect pulseaudio is the
Mark Miksis wrote:
Can you clarify this? Specifically, are current Wandboards shipping
with a fixed carrier that corrects the SPDIF miswiring? When did this
change? Are both the dual and the quad shipping with the same new rev
carrier?
The QUAD is definitely shipping with a revised
dsdreamer wrote:
I too can get alsamixer to work, but *only* by addressing the hardware
card directly, with alsamixer -c0. Are you stating that alsamixer
typed on its own (no additional options on the same line) works for
you?
EDIT: apparently, my problem was trying to run alsamixer as
albertone74 wrote:
Glad that everything is fine:)
Can you please let me know if you your router is assigning only one IP
address to your WBDUAL (F19 alpha 1)? With my WBQUAD (F19 alpha 1)
everything is OK. I am just getting one IP address, as it should be.
Thanks.
I'm not noticing any
dsdreamer wrote:
...Perhaps that is what you're seeing?
That's correct. I have assigned an IP static address anyway. Now I am
just enjoying this great F19 on my WB's:)
Primary system: Squeezebox Touch, iPengHD/Squeezepad on iPad3, Little
Doc DAC I, Virtue Audio One, Philips DVP3580, Mission
I have the F19 Alpha1 image running without problems on a WBDUAL via
wireless. It booted normally and is playing music through a basic USB
DAC. I don't have it connected to a monitor so I can't comment on
jivelite.
A very nice Alpha image.
JackOfAll wrote:
Please do.
It's probably going to be next week before I get back to it. (Need a day
away from computers tomorrow.) Your mytek driver Noticed you
have a few more changes in git. Shall I build the module for kernel 3.11
from latest git, or stick to check-in before
So far the transition to F19 on my Quad is quite uneventful, everything
works as it should! The Mytek is happily playing music (needed the
obligatory onetime rmmod modprobe suquence).
Nice job! Looking forward to testing it with the 3.11 kernel.
JackOfAll wrote:
Sure, give me a couple of days to get to it.
Thanks a lot for that!
JackOfAll wrote:
Let us know how you get on. I think you'll be the first to run it on the
dual. I haven't yet!
It is working like a charm. Even SPDIF is working great! I have never
had any problems
albertone74 wrote:
Clive,
When you get a chance would you please explain to me how to move the
/var/lib/squeezeboxserver file to an external HDD?I remember once you
mentioned it but I have never figured out how to do it.Thanks a lot and
sorry for the off-topic question!
Alberto, below
After a number of confusing, posts, I wanted to clarify my testing
results.
WB Quad tested with Jivelite/HDMI, Ethernet and WLAN, audio output
tested via SPDIF, Analog and USB DAC: all working as expected no
issues.
WB Dual tested with Jivelite/HDMI, Ethernet and WLAN, audio output
tested via
dsdreamer wrote:
The *only* thing that I've found in testing that may need to be
addressed is that alsamixer won't start from the command line when
invoked without arguments.
I have just tried on my WBDUAL running F19 and alsamixer is working from
the CLI. Please let me know if I can
bakker_be wrote:
Alberto, below what was written earlier regarding this:
If you have any questions remaining, please don't hesitate!
Hi,
Thanks for the links. I think I have sorted out by using the command:
Code:
sudo mount -o bind
Testing F19 Alpha on my quad right now. Everything works great. I'm
using an HDMI display and wifi to stream music and control playback
using squeezer on my phone, no issues so far.
Congratulations for the great/hard work!!! :D
albertone74 wrote:
I have just tried on my WBDUAL running F19 and alsamixer is working fine
from the CLI. Please let me know if I can try something else for you.
I too can get alsamixer to work, but *only* by addressing the hardware
card directly, with alsamixer -c0. Are you stating that
I finally got around to trying R7 tonight, it is working well, the
jivelite is working well, I haven't had any freezes, I like the grid
view. I'm using an 8G class 10 card (patriot brand), I picked up several
at my local computer store for about $8 a piece.
The squeezelite part is working
This is an ALPHA image! It has had very limited testing. It works for
me. If it works for you, great. If it doesn't, go grumble elsewhere! ;)
On a serious note, as it is an ALPHA, don't go overwriting your current
working sdcard. Only install this if you have a spare sdcard.
The F19 series of
JackOfAll wrote:
This is an ALPHA image! It has had very limited testing. It works for
me. If it works for you, great. If it doesn't, go grumble elsewhere! ;)
On a serious note, as it is an ALPHA, don't go overwriting your current
working sdcard. Only install this if you have a spare sdcard.
JackOfAll wrote:
This is an ALPHA image! It has had very limited testing. It works for
me. If it works for you, great. If it doesn't, go grumble elsewhere! ;)
On a serious note, as it is an ALPHA, don't go overwriting your current
working sdcard. Only install this if you have a spare sdcard.
dsdreamer wrote:
The only thing I would like to fix is the following when trying yum
update:
Code:
Error: Cannot find a valid baseurl for repo: rpmfusion-free/19/armhfp
Is this a configuration error on our end? For now I've
Squeezed_Rotel wrote:
If I want to try it, do I use one or both images? Checksum also?
If you have a quad cpu board, you download and use the image with Quad
in the name. If you have a Dual
The CHECKSUM files contain the md5sum. Someone else asked for that.
Clive,
I have just tested the F19 ALPHA 1 Image on my WBQUAD. Everything is
working great. Thanks for this nice fedora update:)
When you get a chance would you please explain to me how to move the
/var/lib/squeezeboxserver file to an external HDD?I remember once you
mentioned it but I have
JackOfAll wrote:
This is an ALPHA image! It has had very limited testing. It works for
me. If it works for you, great. If it doesn't, go grumble elsewhere! ;)
On a serious note, as it is an ALPHA, don't go overwriting your current
working sdcard. Only install this if you have a spare sdcard.
albertone74 wrote:
When you get a chance would you please explain to me how to move the
/var/lib/squeezeboxserver file to an external HDD?I remember once you
mentioned it but I have never figured out how to do it.Thanks a lot and
sorry for the off-topic question!
Sure, give me a couple
lintweaker wrote:
Thanks, I'll try out the alpha on my Quad and report back!
Please do.
It's probably going to be next week before I get back to it. (Need a day
away from computers tomorrow.) Your mytek driver Noticed you
have a few more changes in git. Shall I build the module for
EDIT: Your using jivelite over HDMI? That something else I hadn't
actually tested myself That video output is working
I tested F19 ALPHA 1 Image using Jivelite only (no WebUI). So yes, the
video output is working fine.
--
Dreamer, easy in the chair that really
Did some testing on the DUAL version of the new F19 Alpha. Initial
finding is that USB audio output is fine, but that the sample clock
rates for SPDIF seem wrong, my DAC won't lock. Analog audio via the
internal Wandboard DAC is clicking away quite rapidly.
I would wait for someone else to get
dsdreamer wrote:
Did some testing on the DUAL version of the new F19 Alpha. Initial
finding is that USB audio output is fine, but that the sample clock
rates for SPDIF seem wrong, my DAC won't lock. Analog audio via the
internal Wandboard DAC is clicking away quite rapidly.
I would wait
'Sandisk Ultra 16GB Class 10'
(http://www.gizzmoheaven.com/SanDisk-16GB-Mobile-Ultra-Micro-SDHC-Memory-Card-with-SD-Adapter/s199896/c1853/Product.html)
Probably only makes sense for people in the UK. Need more cards
These Sandisk Ultra 16GB Class 10 cards work well with the Wandboard.
£8.99,
JackOfAll wrote:
Just a quick heads-up, there are new images on the way, where I have
re-based CSOS on Fedora 19. These images are going to require an 8GB
card, during the development phase at least. (Previous images have
always been installable to 4GB cards.) The CS packages have all been
lintweaker wrote:
Yes, I am using CSOS as intended. LMS-Squeezelite-Mytek via USB
Hummm. I am also, but my 88.2k files play @ 44.1 and my 96k files play @
48. Do you use libsoxr in Squeezelite player?
John
John Marshall
SqueezeCenter 7.3.4 running on a DIY PC, Windows 7 64 bit o.s., with
Squeezed_Rotel wrote:
lintweaker, are you playing the Wand using the Squeezelite Player?
TIA
John
Yes, I am using CSOS as intended. LMS-Squeezelite-Mytek via USB
lintweaker's Profile:
Just a quick heads-up, there are new images on the way, where I have
re-based CSOS on Fedora 19. These images are going to require an 8GB
card, during the development phase at least. (Previous images have
always been installable to 4GB cards.) The CS packages have all been
rebuilt against F19
JackOfAll wrote:
Just a quick heads-up, there are new images on the way, where I have
re-based CSOS on Fedora 19. These images are going to require an 8GB
card, during the development phase at least. .
Nice! F19 is running great so for on my desktop, a very good release. I
am eager to test
JackOfAll wrote:
Just a quick heads-up, there are new images on the way, where I have
re-based CSOS on Fedora 19.
Hi Clive,
I will be happy to test it on my WDual since a use it only as LMS server
(wired network)
Regards,
Touf.
dsdreamer wrote:
I tried this code change, but the glitch remained. I also increased the
value of usleep to 1000 in the else clause, but that still didn't
eliminate the click. I am building with make OPTS=-DRESAMPLE, stopping
the squeezelite service and copying the binary over the top of
vzs wrote:
Did you manage to fix this issue of Minimum Phase very high quality
upsampling?
Nothing to fix as far as I am concerned. Increase the buffer and period
size.
JackOfAll's Profile:
JackOfAll wrote:
Nothing to fix as far as I am concerned. Increase the buffer and period
size.
All right then. I'm eagerly waiting for my WBDUAL :)
vzs's Profile: http://forums.slimdevices.com/member.php?userid=42968
Can a couple of people with 8GB cards run fdisk on them and report back
the sector count?
I'm planning on making these new F19 8GB images with 15409152 sectors.
(ie. sector = 512 bytes. 15409152 * 512 = 7889485824 bytes.)
Anyone have a 8GB card with a smaller sector count?
JackOfAll wrote:
Can a couple of people with 8GB cards run fdisk on them and report back
the sector count?
I'm planning on making these new F19 8GB images with 15409152 sectors.
(ie. sector = 512 bytes. 15409152 * 512 = 7889485824 bytes.)
Anyone have a 8GB card with a smaller sector
[root@wandquad ~]# fdisk -l
Disk /dev/mmcblk0: 8026 MB, 8026849280 bytes, 15677440 sectors
This is a Samsung 8GB Pro microSDHC Extreme Speed (UHS-1)
--
Dreamer, easy in the chair that really fits you...
I currently have only a couple of 4 GB cards.
Will 8 GB be a requirement for F19 and onwards?
1 x SB3, 1 x SB Boom, 1 x SB Radio and 2 x SB Touch - all wireless
1 x Wandboard behind the bedroom ceiling
ReadyNAS NVX running LMS 7.7.2. w iTunes plugin
iPeng on iPod Touch.
SqueezePad iPeng on
Pascal Hibon wrote:
I currently have only a couple of 4 GB cards.
Will 8 GB be a requirement for F19 and onwards?
JackOfAll wrote:
Just a quick heads-up, there are new images on the way, where I have
re-based CSOS on Fedora 19. These images are going to require an 8GB
card, during
Pascal Hibon wrote:
I currently have only a couple of 4 GB cards.
Will 8 GB be a requirement for F19 and onwards?
At some point I intend to strip it back down, but for the moment I
don't want to keep switching between the development image I'm using and
the user image you are using. I also
JackOfAll wrote:
At some point I intend to strip it back down, but for the moment I
don't want to keep switching between the development image I'm using and
the user image you are using. I also want to mirror what the
official Fedora images have done. They've gone to a 8GB image. I kind
of
kesey wrote:
albertone, it may be the Class 10 which is causing the difficulty. Do
you have any Class 6 SD cards that you can try? Class 4 or Class 6 will
work happily on my Sheevaplug and on my Raspberry Pi. Class 10 will not.
To be honest for me it is not a big deal as the new image R7 is
Hi to all,
Just to report that R7 image work great with Quad board.
I have tested JiveLite and no Freeze at boot (I can select langage
etc...)
I do some reboot via Web Gui and always no freeze. (Tested via onboard
Wifi and RJ45)
I use my Quad Board with a Lexar 16 GB Class10 UHS-I
Touf wrote:
Clive, It's possible for you to add an MD5 Hash of your uploaded files
?
I'll start doing that the next time I make images.
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View
JackOfAll wrote:
John,
Are you saying that this behaviour, (which seems to me to be about the
reliability of firmware loading using the 3rd party Linux driver), is
specific to using the DAC with the Wandboard? Do you not have the same
issues with the Mytek DAC when running under Linux on
JackOfAll wrote:
Confident, cocky, lazy, busy. You decide. ;) These images have had
zero testing. I haven't even booted them, let alone tested. Rather
hoping that the usual suspects will download, install and test, so I can
get back to trying to make the F19 images work. (Probably the
Pascal Hibon wrote:
Downloaded, installed and configured R7 on a DUAL.
The Wandboard boots fine, jivelite does not freeze and it is playing
music fine.
Only issue is that my Trigger Output does no longer work. Did something
change in that regards?
Not as far as I am aware. I'm going to
lintweaker wrote:
Guys, this is unfortunate expected behaviour. I explained the firmware
loading issue. This is not magically resolved by a new CSOS image.
No, I didn't expect it would be resolved by a new image. All I was
trying to get at, was that if the behaviour with regard to firmware
JackOfAll wrote:
Not as far as I am aware. I'm going to ask a stupid question. New image,
new prefs. Did you re-enable it via settings menu?
No problem for asking... but yes I did re-enable it.
I still can change the state of the GPIO manually (SSH into the
Wandboard and manually set and
Pascal Hibon wrote:
No problem for asking... but yes I did re-enable it.
I still can change the state of the GPIO manually (SSH into the
Wandboard and manually set and reset the value) but the Trigger Output
Lua script doesn't work anymore.
OK, I'll take a look.
Pascal Hibon wrote:
EDIT: thinking back into my archives... we've had this issue before - I
deleted the Destop.lua file and all works fine now.
Wasn't that related to me not deleting the prefs, which then left my MAC
address being used, which obviously didn't exist on your board. But
R7
JackOfAll wrote:
No, I didn't expect it would be resolved by a new image. All I was
trying to get at, was that if the behaviour with regard to firmware
loading, was worse on the WB, compared to a desktop Linux PC, we should
try and figure out why.
At the risk of getting a slap round
JackOfAll wrote:
John,
Are you saying that this behaviour, (which seems to me to be about the
reliability of firmware loading using the 3rd party Linux driver), is
specific to using the DAC with the Wandboard? Do you not have the same
issues with the Mytek DAC when running under Linux on
JackOfAll wrote:
Wasn't that related to me not deleting the prefs, which then left my MAC
address being used, which obviously didn't exist on your board. But
R7 image, definitely didn't have the user prefs at first boot.
Yes, I believe so.
But the Desktop.lua file contains a MAC address
lintweaker wrote:
Regarding the firmware issues on a normal desktop Linux PC, they are the
same.
Should I add your silly.sh script to the firmware rpm? (I'll rename it,
of course.) Might be better for the non-geeky to run that rather than
rmmod/modprobe/aplay directly.
JackOfAll wrote:
I don't know. Lintweaker?
I'll re-check as soon as LMS on the new R7 image on my Quad is finished
with scanning. Squeezelite will set the DAC to 44.1 when it starts so
the initial 88.2 will probably be visible only briefly.
After much testing, I observe that once the MyTek usb2 firmware does
load, it's the mytek power down that causes the firmware on the wand to
unload. I can always get it back by one or two rmmod/modprobe. The
other issue is that the Wand won't play anything over 44.1 natively.
FWIW
hth
John
MYTEKUSB2-FIRMWARE-1.34.10-2
Changes...
Code:
* Tue Jul 23 2013 - 1.34.10-2
- Add firmware-loader script, /usr/sbin/mytekusb2-firmware-loader.sh.
Update...
Code:
sudo csos-cleanUpdate-testing mytekusb2-firmware
Squeezed_Rotel wrote:
After much testing, I observe that once the MyTek usb2 firmware does
load, it's the mytek power down that causes the firmware on the wand to
unload. I can always get it back by one or two rmmod/modprobe. The
other issue is that the Wand won't play anything over 44.1
JackOfAll wrote:
MYTEKUSB2-FIRMWARE-1.34.10-2
Changes...
Code:
* Tue Jul 23 2013 - 1.34.10-2
- Add firmware-loader script, /usr/sbin/mytekusb2-firmware-loader.sh.
Update...
Code:
sudo
lintweaker wrote:
BTW The script landed in both /sbin and the mentioned /usr/sbin, is this
intentional?
/sbin is a symlink to /usr/sbin. /bin - /usr/bin. /lib - /usr/lib.
It was introduced in Fedora 17, 'Features/UsrMove'
(https://fedoraproject.org/wiki/Features/UsrMove).
JackOfAll wrote:
/sbin is a symlink to /usr/sbin. /bin - /usr/bin. /lib - /usr/lib.
It was introduced in Fedora 17, 'Features/UsrMove'
(https://fedoraproject.org/wiki/Features/UsrMove).
Oops. Right, forgot about that...
After a marathon 7 1/2 hours duration of LMS scanning my music library
(over NFS) I can confirm CSOS R7 works just fine on my Wandboard Quad.
I have to see, that, at times the system feels rather slow for a quad
core with 2G of memory. I'll have to investigate that a bit more.
Playing music
JackOfAll wrote:
Alberto,
I have successfully tested the R7 quad image. No issues for me with
jivelite.. Can I suggest if you haven't already, write the image to
the card again, and start from scratch. (And of course, make sure you
use the quad image for the quad! ;))
So
lintweaker wrote:
Playing music through the Mytek DAC works just fine up to 192K.
lintweaker, are you playing the Wand using the Squeezelite Player?
TIA
John
John Marshall
SqueezeCenter 7.3.4 running on a DIY PC, Windows 7 64 bit o.s., with
Inguz Audio EQ/DRC. (1) Transporter, (4) Booms
albertone74 wrote:
So there we go the result of my tests. I can confirm that I have used
the quad image for the quad..lol...:)
1st TEST: 16 GB SandDIsk Class 10 - JiveLite starts only if I power
cycle the WB. If i reboot the WB via the CSOS web GUI jivelite won't
start either. I have
JackOfAll wrote:
John,
It's not that the firmware on the Wandboard is unloading The
firmware is uploaded from the Wandboard to the DAC by the driver. When
you power cycle the DAC, it requires that you upload the firmware to it
again. If you update the firmware package to 1.34.10-2 in
kesey wrote:
albertone, it may be the Class 10 which is causing the difficulty. Do
you have any Class 6 SD cards that you can try? Class 4 or Class 6 will
work happily on my Sheevaplug and on my Raspberry Pi. Class 10 will not.
Early Raspberry Pi's had issues with Class 10 SD cards. But
dsdreamer wrote:
Looking good!
Thank you! Making the R7 image now.
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread: http://forums.slimdevices.com/showthread.php?t=98544
Confident, cocky, lazy, busy. You decide. ;) These images have had
zero testing. I haven't even booted them, let alone tested. Rather
hoping that the usual suspects will download, install and test, so I can
get back to trying to make the F19 images work. (Probably the most
important to test,
dsdreamer wrote:
Playing music now No freezes.
Thank you! Which image did you test, Quad or Dual?
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread:
JackOfAll wrote:
If people could give the thumbs up for both the Dual and Quad images,
I'll change the links on the website to make them the default current
images.
Clive,
I have tried the image for my WBQUAD. Jivelite wan't start at all. The
CSOS web GUI is working well and I can SSH
albertone74 wrote:
Clive,
I have tried the image for my WBQUAD. Jivelite wan't start at all. The
CSOS web GUI is working well and I can SSH to my board. Is there
anything I can provide you with? Any logs?
jivelite is logging to syslog. If you open /var/log/messages, sudo less
JackOfAll wrote:
jivelite is logging to syslog. If you open /var/log/messages, sudo less
/var/log/messages, anything interesting? Is jivelite running? ps ax |
grep jivelite?
That's the output of ps ax | grep jivelite
Code:
ps ax | grep jivelite
592 pts/0S+
JackOfAll wrote:
Not running Restart it and see if second systemctl status cmd says
it is running
Code:
sudo systemctl restart autologin@tty1.service
sudo systemctl status autologin@tty1.service
After running:
Code:
albertone74 wrote:
After running:
Code:
sudo systemctl restart autologin@tty1.service
I am still waiting for the prompt...shall I power it off/on?
No, ssh into it again with another session and sudo less
/var/log/messages, '',
JackOfAll wrote:
..but I suspect you are not going to.
Indeed..
Code:
Jul 22 18:35:01 wandboard systemd[1]: Stopping Getty on tty1...
Jul 22 18:36:31 wandboard systemd[1]: autologin@tty1.service stopping timed
out. Killing.
Jul 22 18:37:04 wandboard
JackOfAll wrote:
As per usual, the images are for a 4GB SDCARD.
Clive, does this mean 4 GB min? Or 4GB only?
John Marshall
SqueezeCenter 7.3.4 running on a DIY PC, Windows 7 64 bit o.s., with
Inguz Audio EQ/DRC. (1) Transporter, (4) Booms (2) CSOS
SqueezeliteWands connected through a
Squeezed_Rotel wrote:
Clive, does this mean 4 GB min? Or 4GB only?
Min. Larger is OK. Looks like we might have an issue with jivelite on
the Quad image. So if you need jivelite via the hdmi port, you might
want to hold off for the moment.
JackOfAll wrote:
OK, I'll need to run the R7 image myself on the Quad, I think and see if
I can figure out what is going on.
OK thanks Clive. In the mean time I will test the image on my WBDUAL and
I will report back...
Primary system: Squeezebox Touch, iPengHD/Squeezepad on iPad3, Little
albertone74 wrote:
OK thanks Clive. In the mean time I will test the image on my WBDUAL and
I will report back...
OK, I'll test the QUAD image myself.
JackOfAll's Profile:
JackOfAll wrote:
OK, I'll test the QUAD image myself.
Clive,
R7 is working like a charm on my WBDUAL...Jivelite included:)
Primary system: Squeezebox Touch, iPengHD/Squeezepad on iPad3, Little
Doc DAC I, Virtue Audio One, Philips DVP3580, Mission M34i.
Secondary system: Wandboard DualQuad
JackOfAll wrote:
If people could give the thumbs up for both the Dual and Quad images,
I'll change the links on the website to make them the default current
images.
Playing music now, and have played with time changes along the following
lines:
Code:
date
albertone74 wrote:
That's the output of ps ax | grep jivelite
Code:
ps ax | grep jivelite
592 pts/0S+ 0:00 grep --color=auto jivelite
Not running Restart it and see if second systemctl status cmd says
it is
I've just spent a couple of minutes now with R7, but everything seems to
be fine to me, no jivelite locks so far (did just a few reboots though)
and music playing fine. I'm using a quad and I've tested it with both a
class 4 and a class 10 SD cards (class 4 is terribly slow, didn't
remember it to
Alcaudon wrote:
I've just spent a couple of minutes now with R7, but everything seems to
be fine to me, no jivelite locks so far (did just a few reboots though)
and music playing fine. I'm using a quad and I've tested it with both a
class 4 and a class 10 SD cards (class 4 is terribly slow,
Here's what I get:
Fiirst boot with new R7...no mytek usb2.
Then sudo rmmod snd_usb_mytek / sudo modprobe snd_usb_mytek TWICE.
Aplay -l now lists the mytek usb2
Squeezelite player shows hw:card=usb2 save and play music until the
Mytek dac is shutdown.
Restart MyTek DAC and no lock and no music.
Squeezed_Rotel wrote:
Here's what I get:
Fiirst boot with new R7...no mytek usb2.
Then sudo rmmod snd_usb_mytek / sudo modprobe snd_usb_mytek TWICE.
Aplay -l now lists the mytek usb2
Squeezelite player shows hw:card=usb2 save and play music until the
Mytek dac is shutdown.
Restart MyTek
JackOfAll wrote:
Thank you! Which image did you test, Quad or Dual?
Dual.
--
Dreamer, easy in the chair that really fits you...
dsdreamer's Profile:
Squeezed_Rotel wrote:
Thanks lintweaker, date and time are wrong, but I don't know how to
adjust this (I set US/Eastern in system settings).
I apologise in advance for not understanding the code, but I believe I
followed the steps and code entries that you indicated.
I attached the log
@Clive, could you revert the mytekusb2 driver to commit
20f1ad22a4329f38613fd918bbe5a452fe130397 ? The last commit seems not
compatible with the wandboard 3.0.35 based kernel.
Thanks.
lintweaker's Profile:
KERNEL-WAND-3.0.35-CM55
Changes...
Code:
* Sun Jul 21 2013 - 3.0.35-cm55
- Revert mytekusb2 driver to git, 20f1ad22a4329f38613fd918bbe5a452fe130397.
mytekusb2-vmalloc.patch
Update...
Code:
sudo
JackOfAll wrote:
My 2p. RTC isn't the issue. (And not directed at Adrian, I'm just
thinking out loud.) That jivelite is requiring any interface to be
active other then loopback is an issue. That jivelite is locking-up when
the time jumps forward after it is set from ntpdate is an issue.
'Subject: Re: SDL_GetTicks() goes backwards - msg#00450'
(http://osdir.com/ml/lib.sdl/2002-12/msg00450.html)
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread:
101 - 200 of 1490 matches
Mail list logo
