[13:21] <studio-user698> hi world, after upgrade to last version > i have no sound . alsa modules are loaded, lspci show me the sound card but no sound card are visible . jack fail to start, alsamixer does not too.
[13:23] <studio-user698> (and sudo poweroff) does not actualy poweroff the computer (but the sound card problem is the most important :)
[13:30] <studio-user698> i made a apt --purge and reinstall alsa-base .. but still same situation,
[14:16] <OvenWerks> studio-user698: The power off thing is probably related to moving from int/upstart to systemd.
[14:17] <OvenWerks> studio-user698: the audio card thing is not something I have had a problem with. Did you actually use the upgrade path as oposed to reinstall?
[14:44] <studio-user698> OvenWerks, hi,  i made a upgrade from the 16.04 up to date to 18.04, actually the computer is laptop with no screen (broken and no graphic card (broken too)  i have a headless vnc server in order to access it. so it is quite painfull to perom a reinstall, i really wish to solve this sound card problem without have to do it.
[14:44] <OvenWerks> I can understand that.
[14:44] <OvenWerks> which audio card are you using?
[14:45] <OvenWerks> intenal?
[14:45] <studio-user698> lspci  | grep -i audio says> 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
[14:46] <studio-user698> lsmod | grep snd say > https://framabin.org/?1bb6625ebf2c417d#smpGxSIVje5RNwGbgioH5E1pLHpAsWrdtzgF2DqEqbU=
[14:46] <OvenWerks> Ah that seems like more than you got last time. (above)
[14:47] <studio-user698> i have change the kernel low latency to the generic one ... but no change.
[14:47] <OvenWerks> aplay -l
[14:48] <studio-user698> no device found
[14:48] <studio-user698> i m going to try to downgrade kernel. take some while :)
[14:48] <OvenWerks> the lowlatency kernel is the same as the generic with one config change
[14:49] <OvenWerks> The kernel seems to have loaded the correct modules
[14:50] <studio-user698> jackd says >  ERROR: control open "hw:0" (No such file or directory)
[14:50] <OvenWerks> if aplay doesn't see it jack won't either
[14:51] <studio-user698> dmesg show some . error message > but i don t have skill to understand it
[14:52] <OvenWerks> you can try giving me a link to a paste... I don't know if I will be any better tough.
[14:53] <OvenWerks> intel HDA is the best tested module that I can tell.
[14:53] <studio-user698> https://framabin.org/?58990a4f90624356#hKM0A8Rb+kJ4Jx07Wah54csWDTgXrKQ9dBR9I5vmhFQ=
[14:53] <studio-user698> look fore the string "Call trace"
[14:53] <studio-user698> (by the way thanks for answering :) )
[14:55] <studio-user698> it seems to be related to graphic ..
[14:55] <studio-user698> nouveau ... not the sound card.
[15:00] <OvenWerks> nouveau certainly fails b ut the system seems to go on. The networks crivers get loaded and I think you are accessing via network.
[15:01] <studio-user698> sure, wireless and wire network works both well. all seems ok but the soundcard
[15:02] <studio-user698>  /etc/default/speech-dispatcher have RUN=no ..
[15:04] <studio-user698>  systemd-udevd[340]: seq 2213 '/devices/pci0000:00/0000:00:01.0/0000:01:00.0' is taking a long time
[15:04] <studio-user698> systemd-udevd[340]: seq 2213 '/devices/pci0000:00/0000:00:01.0/0000:01:00.0' killed
[15:04] <studio-user698>  systemd-udevd[340]: worker [359] terminated by signal 9 (KILL)
[15:04] <studio-user698>  systemd-udevd[340]: worker [359] failed while handling '/devices/pci0000:00/0000:00:01.0/0000:01:00.0
[15:04] <studio-user698> i see this in journalctl
[15:06] <OvenWerks> sudo alsa force-reload
[15:07] <studio-user698> did it .. no change
[15:09] <OvenWerks> I wonder if xorg can be forced to use svga instead of the nvidia driver
[15:11] <studio-user698> actually i use this > and i can connect with vncviewer > https://framabin.org/?46052ebd60312579#xUTb/vwk/ghhFNCnCSubrZnw87DH9m/hyyq3of8vkVU=
[15:11] <studio-user698> with ligthdm disable.
[15:11] <studio-user698> it works quite well
[15:12] <studio-user698> (it is tightvncserver)
[15:13] <OvenWerks> what happens if you start with nomodeset?
[15:13] <studio-user698> as kernel parameter you mean ?
[15:13] <studio-user698> let me try. (going to takk some time ..)
[15:15] <studio-user698> nomodeset seems to be related to graphic card
[15:15] <studio-user698> i have no problem with it . it is realy broken !
[15:19] <studio-user698> OvenWerks, going to look more after, by the way thanks fot you time, i have to go now ! nice day|night !
[15:19] <OvenWerks> bye sorry not to be more help.
[20:05] <davim> dads