Linux on Asus z170 ws and Problems

Hi,
I guess that this will be the unofficial problem and solving thread for linux on this board, so let me begin:

No audio in mint 17.3 and i cant figure out how to fix it.
The board features a Realtek ALC 1150 who in my experience should not cause any problems, but he unfortunately does.
This might be due to the 3.19 kernel, so i have tried updating.
Manual and automated update to 4.4.0-22 and 4.5.3-..... and both get me stuck in busy box.

There are no Dummy devices, instead, audio over HDMI of the NVDIA gfx is detected, nothing else is.

Any suggestion how to get out of busy box?
Or how to get the Audio working ?

im pretty much through all the google search words i could imagine.
Thx in Advance.

Assuming you've got alsa and pulseaudio installed.
Try with pavucontrol if you haven't yet, it's another gui for sound settings, the default sound prefs don't always show everything you want to see or manage.
Is the card even recognized? What's the output of

$ aplay -l

(that's an L not an i)

If the card is recognized but not working try creating a config ".asoundrc" in your home directory, assuming the card identifies as "card 0" by 'aplay -l'

$ gedit /home/youruser/.asoundrc

and copy-paste this into it

pcm.!default {
type hw
card 0
}

ctl.!default {
type hw
card 0
}

You might have to reboot if logging out and back in doesn't cut it

EDIT: yet another solution can be found here:

Ubuntu Realtek ALC1150

aplay -l :

$ aplay -

**** List of PLAYBACK Hardware Devices ****
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0

i guess the card is not recognized. -.-

Did you try the link?

yes, but sadly no change with the solutions provided by the link.

Ok kernel upgrade next, uninstall the nvidia drivers first then boot to the new 4+ kernel if you already had it installed, then reinstall the proprietary drivers.
This is assuming u meant the tty when u mentioned busybox, nvidias proprietary drivers can't cope with kernel upgrades.

1 Like

i did that before upgrading the nvidia driver, it wasn't installed at the time of fidling around with the kernel.
Im actually surprised that mint didn't die on me already...

so, the proprietary nvidia driver is not the cause of being stuck in tty / busybox.

But you can login right? Login and type "startx" and enter, if it throws errors at you take a pic with your phone and upload here

1 Like

Update:

busybox ... bla ...bla
(initramfs)

tried startx

/bin/sh: startx: not found

ls:

dev lib etc init lib64 var sbin proc
root run ..............

update:
i overlooked initramfs as a search term, interesting stuff.

recovery comes further with a lot more messages.

Begin: Mounting root file system ........
Reading all physical volumes. this may take a while.....
no volume groups found
the same ......
Begin: waiting for encrypted source device ... ...

nothing for a long time.
then a lot of usb hid devices and finaly, busybox
with

initramfs

Ok I'm pretty sure you're getting thrown into rescue mode, kinda weird actually.
But we can fix it or install another distro with a more up-to-date kernel.... Either way you're gonna need a live media to boot from.
So do you wanna fix or reintall? You dualbooting or does mint take up the whole drive?
EDIT: sorry for the late reply, was at the pub

1 Like

no problem, its not that urgent.
Hope it was fun at the pub!

i would actually like to stay with mint,
allready tried out:
ubuntu 15.?
elementary
and Fedora
and so far i like mint with xfce the most.

Its installed on a samsung 950 pro and i plan on later adding another to raid 0 for mooooorrrrrreeeeeeee speeeeeeed and storage.

And plan was to single - boot linux, and put win10 in a vm cage, where it belongs!

so i guess itll be FIX.

Kay then grab SystemRescueCD from here: https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/4.7.2/systemrescuecd-x86-4.7.2.iso/download
boot from it and choose to boot to the existing OS, then post the outcome

1 Like

the download of that tool takes ages for me right now, guess i will proceed tomorow

Aight. The issue is most likely a borked GRUB, in which case you can boot into your existing mint system from SystemRescueCD.
Then once in Mint if you run

$ lsblk

It will list your drive and its partitions, likely the drive is 'sda' and your boot partition is 'sda1'. In that case run

$ sudo mount /dev/sda1 /mnt
$ sudo grub-install --root-directory=/mnt /dev/sda

And it should be fixed.

1 Like

I managed to download the rescue-image this morning and installed it onto a usb stick with the dd command on an old macbook.

So far it does not change the boot options in grub,
and it doesent change the outcome.

On the other side, i managed to boot into the old kernel through recoverymode.

The output of lsblk is this:

A bit more understandable.
The rescue image did not help getting into mint under thw 4.4 kernel.

Instead i managed to get the old 3.19 running again.
I could runn rhe b code youve given me, but as you can see in the picture, there is no sda or sdb, and i guess that it would be nvme0n1 instead of sda, but because im a noob, id like to hear that from somwone whos less of a noob then me.
I currently fear that i could brick it to death, nearly everything i need is running allready.

Thx!

Correct, sda or sdb are used for SATA based block devices, since you don't have a SATA drive, but an nvme, there's just nvme0n1.

Also the mount command gave you an error becase there's a space between /dev/nvme0n1 and /mnt that you didn't type.

1 Like

Tring to boot. 4.4 kernel, in busybox :

mount /dev/nvme0n /mnt
No such file or directory

The same for nvme0np1

cd ing into dev unvails a lot:

But thats probably not of any interest.

Ok, progress, Kernel is the culprit!

update from 3.19.0-31 who is recommended to the last 3. kernel ( 3.19.0-59) worked pretty flawless. Update to 4.2.0-18 from there, no problems booting so far, and with 4.2 i have more then one audio device. Yay.

should have tried that earlyer!

lets see how far i can get with the incremental kernel upgrades.
4.2 works , 4.4 not.

Thanks for all the help guys!

1 Like