Multiple Issues after installing Linux Mint 18.1 Serena Cinnamon

[emmanualvnebu]

Hello Guys....
I am new to Linux & the forum and I hope some one will be able to help...
I installed Linux Mint 18.1 Serena Cinnamon on ASUS Vivobook E200HA (Single OS)
I am having multiple issues with it:
1. No Audio (Both headset & internal speakers) Output device showing Dummy
2. System not coming back from Hibernation
3. I setup power button to hibernate but when I press it, its not doing anything.
4. Closing lid set as suspend, but the power light keep on and when I open the lid, its not coming backup
5. If I hibernate, it won't wake from hibernation.
6. Asus logo gone at startup, instead of Asus logo I get a black screen for 10 sec and then the mint logo come up.

Can some one help me with these please...
Thanks in advance...
Cheers!!
Emmanual

[Cosmo.]

It is a bad attempt to open 3 identical threads abut the same issue, see also the forum rules.

[xenopeek]

I've deleted all your cross-posts as per our forum rules.

To know a little about your system's hardware and drivers please open the terminal program from your menu and type the following command in it and press enter:
inxi -Fxz

Copy the output and share it here. You can select and copy text from the terminal through its Edit menu.

[turtlebay]

If your example is similar spec to this ( https://www.notebookcheck.net/Asus-Vivo ... 391.0.html) then the 2GB ram is not enough to run the Cinnamon version. I'd suggest trying the XFCE version which uses considerably less resources.

[xenopeek]

If your example is similar spec to this ( https://www.notebookcheck.net/Asus-Vivo ... 391.0.html) then the 2GB ram is not enough to run the Cinnamon version. I'd suggest trying the XFCE version which uses considerably less resources.

Amount of RAM has nothing to do with not having audio or not being able to hibernate. And 2 GB RAM is plenty to run Cinnamon (32-bit).

That said, if indeed this device has an Atom processor, I would also recommend Xfce (32-bit) instead of Cinnamon but only because of it having such a low performance processor. That will not solve the issue of no audio or not being able to hibernate.

[emmanualvnebu]

I've deleted all your cross-posts as per our forum rules.

To know a little about your system's hardware and drivers please open the terminal program from your menu and type the following command in it and press enter:
inxi -Fxz

Copy the output and share it here. You can select and copy text from the terminal through its Edit menu.

Code: Select all

System:    Host: Asus-E200HA Kernel: 4.4.0-81-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.1 Serena
Machine:   Mobo: ASUSTeK model: E200HA v: 1.0
           Bios: American Megatrends v: E200HA.303 date: 12/21/2016
CPU:       Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11519
           clock speeds: max: 1920 MHz 1: 1179 MHz 2: 914 MHz 3: 521 MHz
           4: 883 MHz
Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.01hz
           GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail)
           GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes
Audio:     Card Failed to Detect Sound Card! Sound: ALSA v: k4.4.0-81-generic
Network:   Card: Qualcomm Atheros Device 0042
           driver: ath10k_pci bus-ID: 01:00.0
           IF: wlp1s0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB
Partition: ID-1: / size: 27G used: 6.6G (27%) fs: ext4 dev: /dev/mmcblk0p2
           ID-2: swap-1 size: 2.04GB used: 0.00GB (0%) fs: swap dev: /dev/mmcblk0p3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 6280.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 187 Uptime: 6 min Memory: 686.4/1894.7MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[emmanualvnebu]

Hello guys..
I updated the Kernal to 4.10.0-24 and the Hibernate started working fine now, but if I suspend the system then the system won't wake also the sound still don't work.
Below is my system info.
Can some one suggest what can be done...

Code: Select all

System:    Host: Asus-E200HA Kernel: 4.10.0-24-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.1 Serena
Machine:   Mobo: ASUSTeK model: E200HA v: 1.0
           Bios: American Megatrends v: E200HA.303 date: 12/21/2016
CPU:       Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520
           clock speeds: max: 1920 MHz 1: 500 MHz 2: 667 MHz 3: 489 MHz
           4: 506 MHz
Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.01hz
           GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail)
           GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes
Audio:     Sound: Advanced Linux Sound Architecture v: k4.10.0-24-generic
Network:   Card-1: Qualcomm Atheros Device 0042
           driver: ath10k_pci bus-ID: 01:00.0
           IF: wlp1s0 state: up speed: N/A duplex: N/A mac: <filter>
           Card-2: Atheros AR9271 802.11n driver: ath9k_htc usb-ID: 001-004
           IF: wlx98ded00b9065 state: N/A mac: N/A
Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB
Partition: ID-1: / size: 27G used: 8.8G (36%) fs: ext4 dev: /dev/mmcblk0p2
           ID-2: swap-1 size: 2.04GB used: 0.00GB (0%) fs: swap dev: /dev/mmcblk0p3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 47.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 196 Uptime: 6 min Memory: 926.8/1892.7MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[michael louwe]

@ emmanual

About your problematic netbook, please refer to .......
https://linuxfetishism.wordpress.com/20 ... us-e200ha/

Seems, the OEM and M$ have colluded to scam ignorant consumers like yourself into buying very cheap but dud Win 10/8.1 netbooks, ie low-end Intel Atom processors and only 32GB of eMMC Flash-drive storage.

Likely, you only resorted to installing LM 18.1 because after some time of use, the Win 10 "bloatware" could no longer be updated/upgraded due to the limited 32GB internal drive-storage - since Win 10 takes up about 20GB of disk/drive space after install and it's system files also have to be auto-compressed = need to be auto-decompressed during use = a very slow netbook.

Avoid such buying mistakes/scams. Maybe, you should buy a better and new budget laptop(= about US$300) or a used Win 7 desktop.

[JerryF]

Not sure if this is relevant: Did you verify the ISO before installing? Maybe you had a bad ISO.

[xenopeek]

ISO file corruption would lead to issues with the ISO before installing, not after.

[JerryF]

ISO file corruption would lead to issues with the ISO before installing, not after.

Thanks xenopeek, wasn't sure.

[emmanualvnebu]

Yes I do understand the fact that the system do not have enough disc space..
But here in this case, I have seen that other people also had the same issues which I am having now..
1. Don't wake from suspend (Lid close+Suspend)
2. Once in 5 time, black screen with mouse pointer after entering the password
3. No Sound

Any fix for this guys?
Thanks in advance..
Emmanual

[michael louwe]

@ emmanual

Stop using Suspend = "fixed".
The fix for black screen has already been given to you from my link.
To get sound, you need to buy a USB sound-card.

The better fix is to get a better laptop and avoid getting scammed by M$/OEM.

[Spearmint2]

ISO file corruption would lead to issues with the ISO before installing, not after.

How so?

[xenopeek]

ISO file corruption would lead to issues with the ISO before installing, not after.

How so?

I think wishful thinking on my part. One can dream of a better world! The ISO boots a casper filesystem which is stored as a single gzip compressed squashfs format file on the ISO. gzip includes a CRC-32 checksum. But that checksum is likely not checked as part of default boot. My mistake. Lesson being: verify the ISO after downloading to confirm your file is good.