[04:10] <fkdsflsm> how do you change the language in ubuntu now?
[04:10] <fkdsflsm> also, it is necessary to completely change the ui each 6 months?
[04:18] <OerHeks> never knew the COMPLETE ui changed with this version.
[08:16] <lordievader> Good morning
[10:50] <BluesKaj> 'Morning all
[15:54] <Dreaman> opala
[15:54] <Dreaman> :)
[15:54] <Dreaman> kak e lameri
[15:54] <Dreaman>  HexChat: 2.10.2 ** OS: Linux 4.2.0-10-generic x86_64 ** Distro: Ubuntu "wily" 15.10 ** CPU: 2 x AMD Athlon(tm) 7750 Dual-Core Processor (AuthenticAMD) @ 1,35GHz ** RAM: Physical: 3,9GiB, 80,6% free ** Disk: Total: 227,0GiB, 58,6% free ** VGA: Advanced Micro Devices, Inc. [AMD/ATI] RV790 [Radeon HD 4890] ** Sound: HDA-Intel - HDA NVidia1: HDA-Intel - HDA ATI HDMI ** Ethernet: NVIDIA Corporation MCP77 Ethernet **
[15:54] <Dreaman> Uptime: 10m 13s **
[20:19] <Papangelo> Hi, I have a brand new hardware machine (Broadwell i7, GM204 nVidia GTX970m G-Sync, USB 3.1, possibly optimus but it only switches cards on reboot not on the fly, Atheros 1525 Killer networking). I can't get it through an install on 15.04, 15.10 or 15.10 daily from 28/08 without a kernel panic.
[20:35] <penguin42> ooh fun, what does the panic say?
[20:41] <Papangelo> When trying to install, it just locks up solid with no error and flashing CAPS. In Live mode I've seen a "machine check, not synching across CPUs" and something I didn't quite catch that mentioned a "timeout" and "CPU0"
[20:41] <Papangelo> Sorry, a timeout, microcode and CPU0
[20:42] <penguin42> Papangelo: On the boot menu of the CD is a safe mode or something like that  you normally should get some text on the screen if it does panic; if you can get a screenshot of that panic it would be good - e.g. with a camera
[20:43] <penguin42> Papangelo: Or if you can just get the screenshot of that timeout or machine check
[20:43] <Papangelo> OK. I'll try that.
[20:43] <penguin42> Papangelo: Machinechecks in general are something wrong with hardware, but not always
[20:44] <Papangelo> I've been running Windows 10 on the machine for over a month now and it's been rock solid. It's a brand new machine so it could have an issue but I'd want to be convinced as the Windows performance is so good.
[20:45] <penguin42> ok
[20:46] <penguin42> Papangelo: Anyway, try and get the screenshot; what brand/model of machine?
[20:48] <Papangelo> http://www.msi.com/product/notebook/GT72-2QD-Dominator-G.html#hero-specification MSI GT72 2QD. It's a complete monster.
[20:49] <penguin42> oh golly
[20:50] <penguin42> I bet that's good on the shoulders :-)
[20:50] <Papangelo> It's slightly lighter than my old Alienware that I destroyed when I had an accident and fell on i tin the backpack. COmes in at 3.something Kg
[20:51] <penguin42> Papangelo: So I can see people with bug reports on the GT72 2QD saying they have specific problems, e.g. with networking, so that tells me that people have got further on their systems than you have
[20:52] <Papangelo> The slightly older build of he machine has a Haswell i7 and chipset. This is the just-out version with Broadwell.
[20:52] <penguin42> Papangelo: If you're really lucky you'll get a nice backtrace visible, because a backtrace can give a hint to what's wrong
[20:53] <penguin42> Papangelo: Have you got the latest firmware in there?
[20:53] <Papangelo> Somebody at our LUG meet today said I should try to find a "crash kernel" that would capture the info as it falls over.
[20:53] <Papangelo> I have the .314 UEFI BIOS which was the latest the last time I looked (last week)
[20:54] <penguin42> ok, cool
[20:54] <Papangelo> I haven't updated the Intel Management Engine.
[20:54] <penguin42> less likely to be an issue, but hey
[20:54] <penguin42> Papangelo: Still, lets see if we can get any further with a picture of the crash messages
[20:54] <Papangelo> I tried to update the Video BIOS but the installer said it wasn't appropriate for my card.
[20:55] <penguin42> hmm a little worrying
[20:55] <Papangelo> OK. I'll try to boot it off a 15.10 standard disc and try to provoke it into dying.
[20:55] <penguin42> how long does it take - does it always fail at the same point?
[20:56] <Papangelo> My card has the new G-Sync feature that, with an enabled monitor, reclocked the refresh rate to match the game you're running on the fly if the refresh rate drops to stop tearing.
[20:57] <Papangelo> It generally falls over when the installer tries to write th epartitioning to the discs or 73% through the install but not always.
[20:57] <penguin42> Papangelo: Also, it might be worth trying doing it with the minimum stuff plugged in, say no external monitor, as few USB devices as you need - keep it simple until you get a happy install
[20:57] <Papangelo> This is with nothing external plugged at all.
[20:58] <penguin42> ok, good
[21:00] <Papangelo> The machine has Intel RST which the install disc didn't support so I changed the SSDs to a pair of larger ones then turned off RAID to run them in AHCI mode. Before the Ubuntu DVD couldn't see the internal drives and said there was no operating system installed.
[21:01] <Papangelo> The out-the-box config was a pair of 128GB SSDs RAID0 with RST to make a single 256GB volume. I stuck a pair of larger Samsung 850 EVO SSDs in so there is one drive for Linux, one for WIndows.
[21:02] <penguin42> RAID0'ing SSDs? Curious way to do it!
[21:02] <penguin42> anyway, without the error messages there's not really anything else to suggest
[21:04] <Papangelo> Yeah, I think the factory worked out that a pair of 128s was cheaper than the 256 they promised it had and thought they'd maximise the profit.
[21:05] <Papangelo> They're these new M.2. SSDs so none o my old 2.5" ones fit in the case.
[21:06] <penguin42> yeh that's just to make life easy
[21:06] <Papangelo> Those two M2s take up less room in the case than one 2.5"
[21:06] <penguin42> right, time for a shower, back soon
[21:07] <Papangelo> Thank you. I will reboot and try to record failure. Back later :)
[21:07] <Papangelo> Thank you.
[21:07] <Papangelo> Which timezone are you in?
[21:07] <penguin42> The UK lazy weekend timezone
[21:07] <Papangelo> Same here.
[21:08] <penguin42> so I'll be around for a good few hours yet, but not for about the next hour
[21:08] <Papangelo> I'm up most of the night. I start the night shift on Monday.
[23:39] <penguin42> Wily's X is just flaky as hell
[23:43] <Papangelo> penguin42. OK I just had a try with the latest daily and Ubiquity is failing on a DBUS exception now. apport thinks it's bug 1495017
[23:43] <penguin42> I guess that's a separate bug
[23:44] <Papangelo> I tried adding acpi_osi=Linux as well and got the odd lock up but I couldn't reproduce the failure in an environment that gave me a backtrace
[23:45] <penguin42> yeh that's tricky to debug then;  how far does it get before it fails?
[23:46] <TJ-> Flakey X? how so? It's been rock solid for me so far
[23:47] <Papangelo> It gets the desktop up. Once it locked before I did anything. The other times it lets me try to start Ubiquity.The desktop appears functional. In install mode, you get the wallpaper and the top bar but the dock never appears
[23:47] <penguin42> TJ-: backtrace shows WaitForSoemthing-FlushAllOutput on Intel
[23:48] <TJ-> texture buffer issue?
[23:48] <penguin42> ?
[23:50] <penguin42> hmm, I thought I'd filed a bug on it and someone said they'd fixed it, but I can't find the bug
[23:51] <penguin42> ah bug 1492503
[23:52] <penguin42> so I've probably not got the fix yet that was released on the 8th ?