[SOLVED] Mint 17.3 Cinammon Crash after kernel upgrade K4.4.0-109(132)

[slipstick]

I am on LM17.3, Cinnamon and upgraded from the 4.4.0-45 kernel to the 4.4.0-109 and Cinnamon crashes on boot. So apparently that bug is not completely corrected.

Code: Select all

steve@steve-Z97X ~ $ inxi -Fxz
System:    Host: steve-Z97X Kernel: 4.4.0-45-generic x86_64 (64 bit gcc: 4.8.4)
           Desktop: Cinnamon 2.8.8 (Gtk 3.10.8~8+qiana) Distro: Linux Mint 17.3 Rosa
Machine:   Mobo: Gigabyte model: Z97X-Gaming 3 v: x.x Bios: American Megatrends v: F6h date: 01/29/2015
CPU:       Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27998
           clock speeds: max: 3900 MHz 1: 3189 MHz 2: 3153 MHz 3: 2795 MHz 4: 2656 MHz
Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Card-2: NVIDIA GM107 [GeForce GTX 750 Ti] bus-ID: 01:00.0
           Display Server: X.Org 1.15.1 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1200@60.0hz
           GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.111 Direct Rendering: Yes
Audio:     Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-3 NVIDIA Device 0fbc driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.4.0-45-generic
Network:   Card: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: d000 bus-ID: 03:00.0
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1000.2GB (10.9% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 20G used: 9.3G (50%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 20G used: 6.3G (34%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 17.18GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:34C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 213 Uptime: 27 min Memory: 2570.4/7820.7MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4
           Client: Shell (bash 4.3.111) inxi: 2.3.0 

[karlchen]

Hi, slipstick.

Oops, this is annoying.
Last night I upgraded the kernel on Linux Mint 18.1 64-bit Cinnamon from 4.4.0-104(127) to 4.4.0-108(131).
The machine has got an old Nvidia card.
Nonetheless I did not experience any problem even with the buggy kernel 4.4.0-108(131). I assume it might be because I stuck with the nouveau driver and did not install the proprietary Nvidia driver. (Might be the relevant factor, might be not.)
I am really keen to learn what my experience will be when the same machine has been upgraded to the bugfixed kernel 4.4.0-109(132) ...

With respect to your problem:
The question really is is the culprit the Nividia driver 384.111 or the kernel or something else.
Can you boot to the kernel 4.4.0-45 and find out whether Cinnamon works correctly again?
This would suggest that the kernel 4.4.0-109(132) might be causing your problem.

Regards,
Karl
--
Perhaps your report and my reply should be split off and turned into a separate thread so as not to highjack windywether's thread.

[ytene]

Hope this isn't misleading information, but I was reading earlier today, see here:-

https://news.slashdot.org/story/18/01/1 ... -computers

that a Canonical-written kernel upgrade which delivers the 108 kernel is apparently bricking native ubuntu systems. The linked slashdot article narrows the scope of the impact to 16.04, but of course we're on a derivative platform and thus the same rules might not apply.

This is beyond my technical ability to interpret with confidence, but I would suggest that this is too close to be coincidence and that we might learn more from watching the ubuntu story unfold.

Hope this helps.

[slipstick]

Hi Karlchen,

I'm not sure what you mean by booting to the kernel before 4.4.0-45. I am currently running on 4.4.0.45 which works fine. Do you mean go back to the 3.19.0.32 which I had before I upgraded many months ago to 4.4.0-45 ?

Note - I just remembered that when I first installed LM on this computer (don't remember if it was 16 or 17 or 17.1) I had to add a couple of things to grub when I booted up in order to avoid a black screen (nomodeset, xforcevesa). Then I could install the correct nVidia driver (don't remember the version). Anyway, as a result, my grub.cfg file has those items on all kernel versions. They have never caused a problem before, but do you think that might be causing a problem with 4.4.0-109 ?

EDIT - corrected to "problem with 4.4.0-109 ?"

[karlchen]

Hi, slipstick.

I corrected the confusing sentence. I had rephrased it before, but only half, thus leaving it in a confusing state.
OK. You already told in your reply what I wanted to be sure of. When you boot kernel 4.4.0-45 Cinammon starts and does not crash immediately.
This suggests indeed that there still may be one more bug to fix in kernel 4.4.0-109(132.)

As I stated, here on Mint 18.1, not 17.3 like on your system, both kernels, the known faulty kernel 4.4.0-108(131) and the assumed bugfix K4.4.0-109(132), seem to work fine. And my Cinnamon does not crash right after starting.
Yet, this is a different system, different hardware, different operating system, different graphics driver software.

Code: Select all

karl@voyager ~ $ inxi -Fxz
System:    Host: voyager Kernel: 4.4.0-109-generic x86_64 bits: 64 gcc: 5.4.0
           Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.1 Serena
Machine:   Device: desktop System: MEDIONPC product: MS-7358 serial: N/A
           Mobo: MICRO-STAR model: MS-7358 v: Fab D serial: N/A BIOS: Phoenix v: 6.00 PG date: 07/24/2007
CPU:       Quad core Intel Core2 Quad (-MCP-) arch: Conroe rev.7 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 19139
           clock speeds: max: 2400 MHz 1: 1600 MHz 2: 1600 MHz 3: 1600 MHz 4: 1600 MHz
Graphics:  Card: NVIDIA G86 [GeForce 8500 GT] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: NV86 version: 3.3 Mesa 17.2.4 Direct Render: Yes
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.4.0-109-generic
Network:   Card: Realtek RTL8169 PCI Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: ac00 bus-ID: 04:00.0
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 507.9GB (5.2% used)
           ID-1: /dev/sda model: ST3500830AS size: 500.1GB
           ID-2: USB /dev/sdb model: Premium size: 7.8GB
Partition: ID-1: / size: 46G used: 11G (26%) fs: ext4 dev: /dev/sda7
           ID-2: swap-1 size: 8.22GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 46.0C mobo: N/A gpu: 48.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 202 Uptime: 34 min Memory: 1020.3/3258.5MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.3.45

Will be interesting (for me) to learn what happens when I update my Linux Mint 17.1 Cinnamon tomorrow or the day after.

Sorry, at the moment I have got no better idea than sticking with K4.4.0-45 on your system, inspite of Meltdown and Spectre.

Regards,
Karl

[karlchen]

Hello, ytene.

The term "bricking" is a bit exaggerated. Some systems will not boot in the worst case. But the affected users can still boot the previous kernel. So nothing will be bricked.
Moreover Ubuntu has already published a bugfix for the faulty kernel 4.4.0-108(131) which is 4.4.0-109(132). cf. USN-3522-3: Linux kernel regression, please.
Updating to this kernel should solve the issue for most affected users.

Slipstick's case seems to be a bit different, because he can boot the machine; but right after logging into the GUI, Cinnamon will crash and drop to fallback mode. The culprit still may be the kernel 4.4.0-109(132). But it is imaginable that the NVidia driver 384.111 is also involved in the problem.

Regards,
Karl
--
P.S.:
Neither of my native Ubuntu systems, 16.04.3 64-bit and 14.04.5 64-bit, has exhibited any problems after updating to K4.4.0-109(132) so far. (Fingers crossed.)

[karlchen]

<moderator on>
Slipstick's problem report has been cross-posted here as well: Cinnamon crashes after kernel update.
Crossposting may lead to contradictory pieces of advice and wasted time easily. It is not recommended for these reasons.
</moderator off>

[slipstick]

Sorry for the cross post. I added a post in that other thread that any future replies to my particular problem should go in this thread and not that other one.

[slipstick]

I tried removing the "nomodeset xforcevesa" (which I mentioned in an earlier post) from grub at bootup. I ended up looking at a black screen, never saw a login screen or anything. When I boot with the nomodeset xforcevesa, I get a login screen, but the resolution is wrong - the login window is much larger than normal (my monitor is 1920 x 1200). When I enter my password, Cinnamon crashes - if I restart it, it crashes again. I can see the top part of the desktop with the normal icons I expect in that area, but all much larger than normal. There is a white bar at the bottom, like a panel, but only a few icons - at the left is the "show desktop" icon and on the right are some boxes to select workspaces (4 boxes, I think). There is no Menu button. After a few seconds, I get a message that HPLIP service does not detect a system tray and has closed. I have to use the REISUB trick to reboot as I don't see a Menu button and Ctrl-Alt-t does not open a terminal.

[dwvisser]

I had this "Cinnamon crash" issue today. Actually, first I had the "4.4.0-109 won't boot" issue first. I think it was all precipitated by my system having a messy kernel history, probably due to old kernel upgrades gone awry when disk space ran out. E.g., there was a ramdisk still sitting around for 4.4.0-103 even though that kernel had already been removed. There were also DKMS modules for bbswitch present for old removed kernel versions. In the end, I think the following sequence solved it for me:

1. Only one known good kernel installed.
2. DKMS: Remove DKMS modules for kernel versions that don't exist on the system
3. Select proper recommended Nvidia driver and install; reboot; confirm graphics all working like it should
4. Use the View|Linux Kernels menu item in Update Manager to install 4.4.0-109 and reboot

I hope that's useful for someone.

My system:

Code: Select all

System:    Host: dale-Latitude-E6410 Kernel: 4.4.0-109-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: Dell (portable) product: Latitude E6410 v: 0001
           Mobo: Dell model: 0K42JR v: A00 Bios: Dell v: A16 date: 12/05/2013
CPU:       Dual core Intel Core i7 M 620 (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10640
           clock speeds: max: 2667 MHz 1: 1333 MHz 2: 2133 MHz 3: 1466 MHz
           4: 2266 MHz
Graphics:  Card: NVIDIA GT218M [NVS 3100M] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1440x900@60.00hz
           GLX Renderer: NVS 3100M/PCIe/SSE2
           GLX Version: 3.3.0 NVIDIA 340.102 Direct Rendering: Yes
Audio:     Card-1 Intel 5 Series/3400 Series High Definition Audio
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.4.0-109-generic

[slipstick]

Well, this has been interesting. I decided to try using the Nouveau driver instead of the Nvidia 384.111. While on kernel 4.4.0-45 I went to the Driver Manager and selected Nouveau, then rebooted to 4.4.0-109. This time Cinnamon did not crash, but ran in software rendering mode, though I couldn't get the display resolution right - it was in 1024x768 and the only other option was 800x600. So I decided to switch back to the Nvidia driver (while still running kernel 109), then rebooted and now it wouldn't work with kernel 4.4.0-45 - it had the same problem as before with Cinnamon crashing.

To get out of this, I had to boot from a 17.3 USB stick, install Timeshift, and restore the snapshot from just before I upgraded the Nvidia driver and the 4.4.0-109 kernel. The driver was Nouveau at this point, so I decided to try installing the 109 kernel before installing the Nvidia 384.111 driver (I had originally done the driver first, then the kernel). I installed the 109 kernel and it worked. So now, just for kicks, I decided to install the Nvidia 384.111 driver just to see if reversing the installation order made any difference, and it seems to work.

EDIT: I'm not really sure that the installation order was what made the difference. I vaguely remember that the first time I installed the 109 kernel (after I had already installed the new Nvidia driver) the update manager only listed about 3 items to be installed as part of that kernel package. But when I did the last kernel installation, before installing the Nvidia driver, I think there were about 6 or 7 items listed as part of the package. Maybe something just went wrong with the first installation.

Code: Select all

steve@steve-Z97X ~ $ inxi -Fxz
System:    Host: steve-Z97X Kernel: 4.4.0-109-generic x86_64 (64 bit gcc: 4.8.4)
           Desktop: Cinnamon 2.8.8 (Gtk 3.10.8~8+qiana) Distro: Linux Mint 17.3 Rosa
Machine:   Mobo: Gigabyte model: Z97X-Gaming 3 v: x.x Bios: American Megatrends v: F6h date: 01/29/2015
CPU:       Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27999
           clock speeds: max: 3900 MHz 1: 3883 MHz 2: 3867 MHz 3: 3884 MHz 4: 3864 MHz
Graphics:  Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
           Card-2: NVIDIA GM107 [GeForce GTX 750 Ti] bus-ID: 01:00.0
           Display Server: X.Org 1.15.1 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1200@60.0hz
           GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.111 Direct Rendering: Yes
Audio:     Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:03.0
           Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-3 NVIDIA Device 0fbc driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.4.0-109-generic
Network:   Card: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: d000 bus-ID: 03:00.0
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1000.2GB (11.4% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 20G used: 9.4G (51%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 20G used: 2.1G (12%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 17.18GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:34C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 195 Uptime: 24 min Memory: 2245.2/7820.5MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4
           Client: Shell (bash 4.3.111) inxi: 2.3.0 

[Spearmint2]

I updated 17.3 MATE to this and have no problems. Supposedly it's one of the kernels with the fix in it.

viewtopic.php?f=90&t=261343&start=20#p1412673

Code: Select all

inxi -S
System:    Host: mint16 Kernel: 3.13.0-139-generic i686 (32 bit) Desktop: MATE 1.12.0
           Distro: Linux Mint 17.3 Rosa 

[vandamme]

Previous kernel 4.10.0-42-generic works fine for me.

4.13.0-26-generic gives me the Cinnamon crash, fallback mode, no recognize monitor, goes to 640x480.
I don't remember any previous kernels crashing Cinnamon.... on a regular basis, anyhow.

i'm using nVidia 304.135 driver.

[throwaway1]

Have the same problem since updating to kernel 4.4.0-109, cinnamon crashes on login repeatedly (immediately).

The difference to the reports here so far is that I don't have NVidia but an AMD Radeon HD 6800, with catalyst driver 15.201.1151-150908a-188977E

I guess I'll stick with the 3.19.0-32 kernel for some time, that's the kernel that was shown in grub2 advanced and it seems to work.

Code: Select all

System:    Host: [systemname] Kernel: 3.19.0-32-generic x86_64 (64 bit gcc: 4.8.2) // Old kernel that I booted just to have a running system
           Desktop: Cinnamon 2.8.8 (Gtk 2.24.23) Distro: Linux Mint 17.3 Rosa
Machine:   Mobo: Gigabyte model: GA-970A-D3 v: x.x Bios: Award v: F12 date: 09/03/2013
CPU:       Quad core AMD Phenom II X4 955 (-MCP-) cache: 2048 KB
           flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 25772
           clock speeds: max: 3200 MHz 1: 2100 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Barts XT [Radeon HD 6870] bus-ID: 01:00.0
           Display Server: X.Org 1.17.1 driver: fglrx Resolution: 1920x1080@60.0hz, 1920x1080@60.0hz
           GLX Renderer: AMD Radeon HD 6800 Series GLX Version: 4.5.13399 - CPC 15.201.1151 Direct Rendering: Yes
Info:      Processes: 195 Uptime: 30 min Memory: 1345.5/7981.9MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4
           Client: Shell (bash 4.3.111) inxi: 2.2.28 

[karlchen]

Hello, throwaway1.

The point for users of older AMD cards is this:
The kernel series 4.x.x, this includes the current LTS kernel 4.4.0-xxx, do no longer support the proprietary AMD driver flgrx.
The kernel series 3.x.x, this includes the no longer maintained kernel 3.19.0-32, still supported the proprietary AMD driver flgrx.

This driver flgrx is present on your system.
So either you have to stick to a supported combination of kernel 3.13.0-139(188) and flgrx.
Or you have to use a supported kernel 4.4.0-109(132) or 4.13.0-26; but you have to give up flgrx and return to the open source AMD/Radeon driver.

Sorry for the not so pleasant news.

Karl

[berni123]

Next case:

Mint 1.73 upgrade to 4.4 109 upstream results in reboot loop.

AMD A10-6700 APU with Radeon(tm) HD Graphics
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D]
driver:
ii xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 amd64 X.Org X server -- AMD/ATI display driver wrapper

lsmod:
radeon 1556480 6

Only stable under:
3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

All other kernels >3.19.0-32 , for example 3.19.0.33 oder 3.19.0-80 oder 4.4 109 results in crashing rebooting or in cinnamon entering software rendering mode an being slow slow slow ...

So Mint 17.3 end up only running fast and stable with kernel 3.19.0-32.
No other kernel is working because cinnamon ends up with slow software rendering or in the reboot loop.

Any way out?

[RyanC]

Next case:

AMD A10-6700 APU with Radeon(tm) HD Graphics
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D]

So Mint 17.3 end up only running fast and stable with kernel 3.19.0-32.
No other kernel is working because cinnamon ends up with slow software rendering or in the reboot loop.

Any way out?

Same here. Guess I'm sticking with the old kernel and security holes for now?

[Spearmint2]

What's the safest approach for Linux users? Determine where a threat might emerge. For most, it would come through browser, or email client, or newer software than currently exists that is downloaded from some PPA instead of the repository.

So, upgrade to protected browser, email client and only get programs out of repository and your risk becomes very minimal. That's why most Linux users can just wait it out till the best kernel fixes are established and the best micrcode from Intel and AMD is developed fully. If you dual boot with windows, then that's a Microsoft problem and that OS would need it's own AMD and Intel microcode upgrades, and with windows 10 you will get those whether you want them or not.

[sichenia]

Same here. Mint 17.3 and same problem.
Called a friend who is a programmer to ask for his help and he tries all these solutions and more, and concluded that there is no way to solve the problem until a new kernel comes up.
The best compromise he could get was a 640x480 resolution that couldn't be changed, so I too went back to the previous kernel. Now if only I could get Palemoon to install I'd feel safer. Don't like the new firefox...
As further info in case anyone needs it, I have an integrated graphic card, my motherboard is ASUS and chip intel.

[Spearmint2]

The best compromise he could get was a 640x480 resolution that couldn't be changed, so I too went back to the previous kernel.

You can change it by creating an .xprofile named file with the proper entries into your user's home folder. For instance, here's the one I created for myself. It's simple to do in Text program, save as .xprofile and then log out and back in, go to Display and choose the one you want.

Here's mine. If those are the resolutions you want, the copy/paste to a text file, name it .xprofile, and save to your user profile folder.

Code: Select all

xrandr --newmode "1280x720_60.00"   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync
xrandr --addmode VGA-0 1280x720_60.00
xrandr --addmode DVI-0 1280x720_60.00
xrandr --newmode "1280x720_70.00"   88.25  1280 1352 1480 1680  720 723 728 752 -hsync +vsync
xrandr --addmode VGA-0 1280x720_70.00
xrandr --addmode DVI-0 1280x720_70.00
xrandr --newmode "1600x900_60.00"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync
xrandr --addmode VGA-0 1600x900_60.00
xrandr --addmode DVI-0 1600x900_60.00
xrandr --newmode "1600x900_75.00"  151.25  1600 1704 1872 2144  900 903 908 942 -hsync +vsync
xrandr --addmode VGA-0 1600x900_75.00
xrandr --addmode DVI-0 1600x900_75.00