black screen m5110 dell xerus ao5 bios dispair

Is m5110 a RAID controller?

no, it is my computer model, so actually i found out nodemodeset fixed the bug partially, but nomodeset needed to be set permanently, i had to get into the grub file and change permissions, so now my bot up sequence is working, but i see a lot of code scrolling as it boots instead of the splash screen.. however when I close the lid, the screen goes black and cant be recovered without rebooting, if i can solve that it wouldbe sufficient, however I think this is all a bug, it worked on windows.. anyways.. help with this is highly appreciated.

Which grub file do you mean?

Windows is a completely different OS with completely different support so what Windows does or doesn't do is completely irrelevant.

/etc/default/grub this is my grub file.. What i meant about windows is, that there is some code that can run this hardware(mostly smoothy , so i assume we can make code to run it smoothly as well, if not, therin lies the bug. However, i dont know much about it, and Ive got a feeling, they introduced these bios hardware glitches.. I'dlike to be able to run my own splashscreen during that bootup time.. but i'll save that for another day.

What video chip does the system use?

If you run:

sudo lshw -C display; lsb_release -a; uname -a

What is the output please?

heres the output ...

  *-display UNCLAIMED
       description: VGA compatible controller
       product: Sumo [Radeon HD 6480G]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 1
       bus info: pci@0000:00:01.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:a0000000-afffffff ioport:f000(size=256) memory:ff700000-ff73ffff
  *-display UNCLAIMED
       description: VGA compatible controller
       product: Seymour [Radeon HD 6400M/7400M Series]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller cap_list
       configuration: latency=0
       resources: memory:b0000000-bfffffff memory:ff620000-ff63ffff ioport:e000(size=256) memory:ff600000-ff61ffff
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial
Linux gigatron 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I also compounded the problem by trying to install an apparently incompatible wrapper for the suspend function, i cant find the commands that i used in the terminal, and it hangs up on boot, this occured after running this command # s2disk. I suspect it chand a boot critical image file.. so help on that would be great.. im able to boot using a rollback offered from the advanced bootmenu.

the new boot problem began after installing uswsusp

ok i uninstalled uswsusp and it fixed my new boot problem.. so now its mostly just the suspend problem.

I'm also in China teaching here, so if you ever wonder why i have untimely responses, that is why, apologies.

ok thanks for pointing it out, i tried installing a driver and ended up getting some state where i had to login in over and over again and actually never logged in.. so i reinstalled. So that is the root of the issue i suppose.. but it seems to indicate that i have ubuntus default driver instead of the original one.. and it doesnt interact with the hardware then in some cases.. such as suspend.. but i think there are workarounds, like mapping power downs to a command in the terminal and power back up on some keystroke.. maybe creating a disk image to reload at that time.. but im just a beginner at this.. not sure if this solved my problem or just recognised it.. im not sure just because amd and ubuntu are working on this hardware driver combo because its too complicated doesn't mean a community member doesnt have the knowhow to do a quick and dirty workaround.. I feel i was close, i found a wrapper that circumvents the suspend code but, i think it was for another version and some things weren't supported like "kms" i think.. i thought i'd check here for a wizard before i try any further on my own. (or much further) im a little driven at this.. haha

now i must sleep its 1:17 here in China, but when I rise, i hope that I can be pointed in the right direction or made to know the difficulty involved in suspending the system and bringing it back upon keypress.. it sounds very basic to me.. suspend-->(or not but not freeze and go to black screen when closing the lid) > continue or start again after key press or lid open. I just want to be able to shut the lid really and not have to reboot.. thats doable right?

i found some files to change, to block the suspend operation, but they weren't effective, the ubuntu system seems to be complicated in this respect and build sensitive.. this is why I'm asking here.

Thanks actionparsnip, that solved my question.

/boot/config-4.4.0-24-generic has a setting for configure suspend I changed it to no... fixed I think this was the real fix

and or setting the power options to not suspend on lid close, also updated the kernel to prerelease.. it was some or all of these things.