[SOLVED] no ip on nuc10i3

[Tecko]

Exedently did click topic solved, my mistake sorry.

[Tecko]

I installed the Aplpa 3.0 it is working. Network issue; after first install you must login. After login reboot. After that the network works. In updates it asks for alpha 4. Now it is time to config the system.


Find out one problem. System does not detect my dac, FiiO k5 pro

[Tecko]

I installed ubuntu first with device/dac on, than it is installed. But get the message device closed. Also get a message pulse audio installed must be deleted. It works now!

[Tecko]

Something else I notice, when connecting dac you have to poweron dac first than the system snakeoil is running on.

[Tecko]

Problem my dac is not reconigzed anymore (FiiO k5pro) On ubuntu it works fine. So something is going wrong with installing snakeoilOS.

[agent_kith]

Device closed is normal. Not showing any device in your list is not.

It just means your music software is not using the playback device at this time.

MPD will always should the device as closed if you're not playing music. But Squeezelite will always take control of the device when it starts up.

Play some music and re-look at this page again to see what happens. It should tell you the sample rate and bit depth.

[Tecko]

Device closed is normal. Not showing any device in your list is not.

It just means your music software is not using the playback device at this time.

MPD will always should the device as closed if you're not playing music. But Squeezelite will always take control of the device when it starts up.

Play some music and re-look at this page again to see what happens. It should tell you the sample rate and bit depth.

yes that works now, but my dac is not excectly plug and play you have to follow certain steps to get it working. I follow some steps during install (ubuntu/snakeoilOS). And some steps when saving the player in snakeoilOS. And than I get it running.

---

Device closed is normal. Not showing any device in your list is not.

It just means your music software is not using the playback device at this time.

MPD will always should the device as closed if you're not playing music. But Squeezelite will always take control of the device when it starts up.

Play some music and re-look at this page again to see what happens. It should tell you the sample rate and bit depth.

yes that works now, but my dac is not excectly plug and play you have to follow certain steps to get it working. I follow some steps during install (ubuntu/snakeoilOS). And some steps when saving the player in snakeoilOS. And than I get it running.

Dac stops working again because I got errors, think it is related: 

curl_easy_perform: could not connect to server

[agent_kith]

Dac stops working again because I got errors, think it is related: 

curl_easy_perform: could not connect to server

Can you take a screenshot? Not entirely sure of context.

[Tecko]

Dac stops working again because I got errors, think it is related: 

curl_easy_perform: could not connect to server

Can you take a screenshot? Not entirely sure of context.

No I can not, installed other system at the moment. Sorry I need music  . I will make screenshots the next time.
 
It is in the bootscreeen after the error you get ipadres;snakeOS;login 

when I install the first time and I login the dac is connected. When I got that error and login, the dac is not connecting anymore. It is a problem related to snakeoilOS because other systems running without problems.
Can I created log files from the boot proces or is there any other way to help debuging this problem?

[agent_kith]

when I install the first time and I login the dac is connected. When I got that error and login, the dac is not connecting anymore. It is a problem related to snakeoilOS because other systems running without problems.

Just because other systems work is not a good diagnostic as to why snakeoil isn't.

I can usually fix the problem if I know what it is. Include any error messages that can point me to the right direction where possible. Otherwise, I can only guess, and it's not going to fix anything.

Can I created log files from the boot proces or is there any other way to help debuging this problem?

Start with some screen caps.. And we'll work out from there.