=== holstein_ is now known as holstein === TheMaster is now known as Hypnotoad [02:31] hi, I've been testing Beta 2 64bit and find that UEFI is totally broken. is this a known issue? [02:36] !uefi [02:36] UEFI is a specification that defines a software interface between an operating system and platform firmware, it is meant as a replacement for the BIOS. For information on how to set up and install Ubuntu and its derivatives on UEFI machines please read https://help.ubuntu.com/community/UEFI [02:36] em_: you mean, you cant install it? [02:43] em_: whats the issue with uefi? is this a QA test case? [03:40] holstein: FYI uefi secure boot only works with the generic kernel for now. [03:41] I think it should work without secure boot turned on though [04:10] nope, not using secure boot... see for yourself, it only takes about 5 minutes to set this up in virtualbox. I was trying to convince a windows 8 victim to switch to ubustudio but could not get it to run. [04:12] yes, I have read the https://help.ubuntu.com/community/UEFI docs, plus others, I get nowhere. [04:56] em_: i dont understand what you mean by "windows 8 victim" or "couldnt get it to run".. or whate "it" is [04:56] em_: i would install ubuntu.. not ubuntustudio.. and install/use a non-testing version.. [04:56] !uefi [04:56] UEFI is a specification that defines a software interface between an operating system and platform firmware, it is meant as a replacement for the BIOS. For information on how to set up and install Ubuntu and its derivatives on UEFI machines please read https://help.ubuntu.com/community/UEFI [04:57] ^^ that documentation should work fine with the main ubuntu version.. then, you can add what you want from the studio pacagkes [04:57] packages* [04:59] em_: i would disable the secureboot on the machine [05:14] we are going round in circles... :-( SECUREBOOT is NOT enabled... anyone stuck with windows 8 esp when they didn't want it is a victim of the m$ monopoly. booting the Beta 2 on a UEFI does eventually find it's way to the grub prompt. selecting Run Without Installing ends with a blank/black screen that never goes away. selecting test/verify cd... actually works. selecting either Install or OEM Install does... after about 4 minutes [05:14] pause with a blank/black screen does finally bring up the installer. so far I have managed to do one install, oten it hangs instead of installing, but the install that did complete was not bootable, it was only giving me a black/blank screen with no visible activity. however on that particular install I did try enabling encryption which was probably a bad idea. have now made several attempts to do the install without encryption and ha [05:14] ve yet to succeed. the install that did complete did partiton the disk and put files on it, but agin, not bootable. I cant make it any more clear than this. highly suggest you try it yourself it only takes 5 minutes to set up a virtualbox test. [05:15] em_: stuck? if you purchase a machine with an operating system on it, thats a choice.. not something one is "stuck" with [05:16] em_: get a stable version of an OS that supports the hardware.. ubuntu, main ubuntu should support your hardware fine [05:16] if it is wiped it needs a msdos partition table probably [05:16] em_: dont use the development release if you are having issues, for there is no official support for it [05:16] and the mbr area cleaned gpt remnants will cause problems [05:17] one thing i would do in that scenario is to test the hard disk for errors.. any virtualbox tests i do pass [05:17] but, i dont have that particular hardware... [05:18] virtualbox is a blank never formatted disk. windows 8 has a bootable os, was trying to run live cd, so mbr not an issue [05:18] virtualbox is not a hardware, you are apparently a troll or very troll like... bye [05:23] for the record, i meant, i dont have the *actual* hardware in particular that is failing for em_.. i only have virtualbox, which i understand is not hardware.. and it works on the iso's i test, but i dont know or have that particular iso to test with [13:21] Hi, realtive noob here. I'm trying to get my usb guitar interface to run through jack and back out of the computer. I got it setup and working yesterday, albeit with high latency. I started to tweak settings for latency, and the usb connection stopped working (hydrogen still output, though). Returning settings to default didn't help. Any ideas? [16:50] holstein: sounded like em_ wasnt in a generally good mood anyways, not much you can do to help someone like that [16:50] MaynardWaters: i probably should have been more clear though, since maybe we had a language barrier as well [22:50] Hi, I'm having an odd problem getting my usb interface to work with jack. It worked until I starting messing with latency settings, then it stopped working. Return to qjackctl defaults didn't help, nor did a reinstall of jackd. [22:52] kale_: sometimes, i try with the live CD, just to make sure its still functioning.. do you have any error messages in the jack window? [22:55] no errors. I'm very new to jack; looking for errors made me notice it mentions device hw:0 (onboard stuff) but has no mention of hw:1 (usb) in the startup messages [22:56] it does say acquired audio card Audio0. [22:57] one thing i suggest, if you can, disable the onboard audio, then, you'll know that JACK is seeing the USB [22:57] otherwise, its probably a matter of selecting the device [22:57] there are 2 drop down menus.. [22:58] "hw:1 usb audio codec" is selected as "Input Device". is this what you're talking about? [23:00] kale_: i, nor you, will ever really konw, likely [23:00] what do i do? i try and reduce the amount of cards.. .thus having only the one device [23:00] then, when i see a device, i know its it [23:00] otherwise, i literally select *every* one and test [23:00] not trusting labels [23:01] ok, I'll give that a go. Gotta go teach a guitar lesson. Thanks. [23:01] kale_: good luck