Gigabyte Brix 7200 Displays 4K

I’ve had a Gigabyte Brix GB-BKi5HA-7200 for a while now.


This is about the 3rd Mini system that I’ve had. Maybe fourth if you include one that I built from parts. This one has:

Linux Mint Fails in 4K

It was running Linux Mint 18 and recently Linux Mint 19. And this was working fine, except recently I upgraded the monitor to a Samsung 40″ 4K TV – UN40MU6300FXZA. I found the Refurbished TV for about $290 for sale by Walmart a couple of months ago. This is quite a good price for this Samsung 6300 level TV.

Walmart_- Samsung 4K UHD TV_-_2018-08-04_15.37.31xx.png

Since I use this mini system to display photos and game screen shots a large high-rez display is just the thing. However, Linux Mint has never supported the display correctly.

As you can see, when in 4K [3840×2160], the display is sliced up and repeated across the screen. It works fine in 1920×1080 mode on Linux. From all the reading of the processor and TV specs, it looked like it should work fine and when I use a long HDMI cable to plug the TV into a Windows 10 system with a GTX 1060 card, it works fine too in 4K.

I am using a pair of 2K monitors through a IOGear Displayport switch and Linux Mint works just fine with that using a GTX 1050 card, which has DisplayPort output.

After spending a couple of days on various forums trying to understand and fix the problem on the BRIX with no luck, I had the bright idea of just trying Windows 10 directly on the system. So I made a Windows 10 install Thumb drive, removed the M.2 Sata, to avoid messing up the Linux Install with Windows 10, and installed Windows 10 on the 60GB SATA SSD. Worked like a charm and brought the monitor right up in 4K without problems.

Continue reading “Gigabyte Brix 7200 Displays 4K”

Marantz – The Real Issue

Crys_00100I think I’ve found the issue. EDID.

The EDID or Extended Display Identification Data is a packet of information sent from a monitor or TV to the source of the video and tells the source what types of video the display can process.

Imagine for a moment that we have a receiver from 2013 – pre 4K – that contains an HDMI switch. Now imagine that one buys almost any TV today – almost all of them support 4K. Now imagine that one purchases something that produces video – BluRay player, XBox Console, Playstation, even a modern set top box. Most of these support 4K video.

So what happens if the EDID from the 4K TV passes unchanged through the NR1504 from 2013 to the video source that can produce 4K? Well the source happily produces 4K video and the NR1504 cannot pass it. Black screen? Apparently.

Was the Marantz 1504 never modifying the EDID? Or did it just start not modifying the EDID? Or did the Linux computer get a new driver that was willing to produce 4K video?

I hooked up an HD monitor to the NR1504 and hooked the Linux box back up to the Media input and voila. Everything works fine, of course.

It seems clear that in this world of ubiquitous 4K sources and displays, the Marantz NR1504 needs to be modifying the EDID or producing one of it’s own to continue to work.

I’ve used the display settings in Linux to use HD only and that works fine with the TV, but when I plugged it back into the NR1504 it still didn’t work. Oh well. Time for a new Receiver that gets 4K. But at least I can use the Linux system by plugging it directly into the TV and setting it to HD.


Linux Kernel Crash – Need to Back Out




I accepted a software update of the kernel on my LM 18.2 system, and now it won’t boot. Probably someone rushed out a SpecterMelt fix or something. Anyway, I need to back out these kernels later than 4.4.0-98 so they aren’t boot options. If I restart now I need to go through grub advanced options to get system started.

How do I back out these recent kernels?

Update: Use the Update Manager > View > Linux Kernels to choose which ones you want and you can back them out.

Update Update: Not a crash at all. Linux was fine. The Marantz NR1504 took an update that blacked the screen. Linux works fine to other monitors and the 4K TV without problems on the latest kernel.


Linux Mint 19 Samba Issues with Windows 10

Yet again, something changed to break network file sharing between LM19 and Windows 10. Here’s the fix. Windows 10 could see a LM19 file share just fine, but LM19 could not see the Win 10 file shares. < Again back-dated to keep it off the front page. >

[SOLVED]Mint 19 Network SAMBA shares not shownin File Manager

Re: Mint 19 Network SAMBA shares not shownin File Manager

Unread post by altair4 » Wed Jul 04, 2018 9:57 am

Can’t comment on the Printer issue but there have been changes in samba since Mint18.

Long version: Mint 19 and Samba File Sharing Changes

Short version:

Edit /etc/samba/smb.conf and right under the workgroup = WORKGROUP line add this one:

Code: Select all

client max protocol = NT1

Then reboot.

If you have Win10 on your network and it has disabled SMB1 on the server side you will not be able to connect to it.

This allows the Linux Mint 19 system to see the Windows 10 file shares.
To see the Linux Mint 19 system from the Windows 10 systems just use the Software Manager to install SAMBA and then set up a file share of say, your home folder. Be sure and change the name to something else, not just your user name. For some reason just your user name fouls up the share.
Here’s the view from the Linux Mint side:

For some reason there were two GBLM19 computers, but this was probably an artifact of the changes I was making while trying to get this to work. After a few minutes it settled down to only one that worked from Windows 10. They both worked from Linux looking in to itself.


Here is the view from the Windows 10 system:

I still cannot ping from the Linux system to the Win 10 machines. Apparently there is a fire wall issue. Well that’s for tomorrow. I can ping the LM system from the Win 10 machines.


Never works out of the box it seems.

Linux / Windows 10 Samba Issues

Back Dated

Can’t connect between Linux and Windows10 with Samba

Here’s a Forum Post.

This appears to have worked to allow me to see windows 10 systems from Linux Mint 18.3.

I don’t think iptables-persistant is the better way around.

The correct and documented way to enforce advanced iptables commands is described on … ctionality

Using that info, what solved the problem for me was to add the code bellow and the end of “/etc/ufw/after.rules” and restarting ufw:

Code: Select all

:OUTPUT ACCEPT [664:135398]
-A OUTPUT -p udp -m udp --dport 137 -j CT --helper netbios-ns

This way, there’s not need to mess with iptables-persistant and if you installed iptables-persistent you’ll need to uninstall it running sudo “apt-get purge iptables-persistent”.

Use “Sudo xed” in a terminal to get an editor so you can edit the file mentioned above. Copy / Paste the settings above at the end of the after.rules file and save it. You can safely ignore the errors about meta data that xed spits out. It’s trying to save some meta data about the formatting and of course that is nonsense when you are editing system files.

Just sharing it so I can find it from Linux.


AMD Ryzen 1800 System

Seems that I can never go too long without building a system. Now that Intel has been duly embarrassed by AMD bringing out some awesome mega-core systems, I just had to support AMD by building one. Intel rushed to build their Core i-9 Processors, but they are way expensive compared with the AMD alternatives.

I first considered an AMD Threadripper 1900x processor  but after asking for advice from the Overclockers forum, it became clear that the 8 core 1900x was not more powerful than the earlier AMD Ryzen 1800X, and this one was on sale for about $100 off.

As you can see, I got a fancy glass case, and water cooler from Corsair, and those fancy carnival lights RAM from G.Skill. Those things are blinking away as we speak.

Continue reading “AMD Ryzen 1800 System”

Sharing with Linux Mint 18.2 and Windows

I have an “Equal Opportunity” network. A few Windows 10 systems and a lot of Linux Mint systems. And I obviously want to share files among my systems.

Install Samba from 2017-10-06 09-25-01.png

Over the years and versions, Linux Mint has gotten more friendly when sharing files with Windows systems. Samba has always been a thing, but in recent versions, Linux Mint has made it easier to get it going.

Back when I was using Ubuntu – which Linux Mint is based on – in 2008, it was a pain to get Samba going. But things are better now. Now with Linux Mint 18.2 the dialog above is what you get if you navigate to Home and then try to share your personal folder, presumably for read-only, to the rest of the network. That’s a start. Look even an install button.

Continue reading “Sharing with Linux Mint 18.2 and Windows”

Linux Mint 18.2 – Printer Sharing Problems

Notice that this is posted on 2017 Oct 6 – Back dated to keep it off the first page of my blog.

I found these instructions on for how to set up printer sharing on Linux Mint. Seems recent – Jan 2016.

I’m trying to share a HP Color Laser printer connected to a Windows 10 system to my Linux Mint 18.2 system so I can print from the LM system. It fails. Printer sharing works fine to this printer from other Win 10 systems on the network. Here is how the printer is set up on the Win 10 system:

Here are screenshots for attempting to set up and use the printer from a newly installed / updated Linux Mint 18.2 system:


So in spite of the config dialog finding the printer, and apparently getting the driver,  any attempt to use the printer is unable to locate the printer.

A year or more ago, perhaps with LM 18.0, I tried to use the HP website to find sharing methods. They were very arcane, required compiling software and ultimately didn’t work. Looks like things have come a long way since then. The printer is found and the printer drivers apparently load correctly. Do we have a clue about why the Unable to Connect error is occurring?

Thanks, ww

This information was posted to Linux Mint Blog, but no responses so far. I’ll submit a bug referring to this post.

Additional information posted 6 Oct 2017

I copied a file from the Linux system to the Windows system where the printer lives and printed it there. Worked fine of course.

But then about 1/2 an hour later, the printer test page – you remember the one I tried to print about 11 hours ago? Well it came out. So I tried to print something else. Brought up an image and chose print from the menu. Then clicked preview, which apparently made a pdf from the image viewer of the image. Then I printed the PDF. Now notifications are popping up every few seconds saying “Printer Error <printer name here> ‘connecting to device’. But nothing is happening.

So it looks like printer support is DOA. Almost there, but not quite. Unless you want to wait 11 hours for your pages?

I have done some searches and can’t find a way to see the print queue or cancel a failed or failing print job.
Some stuff from 2011 / 2012 says something about an applet in the notification area, but there’s nothing showing, except the blinking notification which only lasts a couple of seconds before disappearing. Is there a printer queue or status app? Some way to cancel a print job that’s stuck? What if the printer fell off a cliff and will never answer?

Using the Troubleshooting feature of CUPS the server produced the fallowing Troubleshoot.txt file:

ZIP File of Troubleshoot.txt and terminal text produced by trouble shoot function

I see, it’s called Printers.

So system-config-printer is actually called Printers in the menus and if you select “View Print Queue” or use Ctrl-F you see the jobs. And you can cancel them. So that old post that wanted to use a terminal has a better solution. The program is not just for Configuring printers but for managing printers and their queues. Good to know. And completely overlooked in the pages that got me here.

Printer still doesn’t work, but at least I can cancel the job that was causing a failed notification every 2 sec.

end as of 7 Oct 2017




Move to Linux

Screenshot from 2016-08-13 07-12-48.png
Linux Mint 18

As you can tell from previous posts, I’m having trouble with the Windows 10 Anniversary Update on one of my machines. It’s an older machine and I suspect that Windows has broken a driver for the old motherboard. The latest version that worked properly was Version 1511 / 10586.545 and each time I restored to the last Restore Point, it went back to that. So apparently, the Anniversary Update 1607 / 14393.51 is the problem.

After going back to a Restore Point on two successive days, I turned off the Windows Update service and the machine was ok for a day, but I decided that this was too risky a state to leave the system. I have decided to move the system to Linux Mint 18, and this post is being typed into that system. It took about 2 hours to do the update, including installing a new system HD, and another couple of hours to set up Thunderbird email.

I have used Linux Mint for many years, and the latest is version 18. I prefer the Cinnamon version, but you may prefer another of the several window managers. For my choice, Cinnamon looks the most like Windows.

This machine is used for email, online shopping and document creation. It has two 1080×1200 monitors driven by an older GTX 270 card. Not the best for gaming, but just fine for it’s uses. Continue reading “Move to Linux”