 Once. Oh, yeah. Might be useful for the first minute. Maybe set up for two careers. Yeah. I guess we can... Yeah, we can do some more prep, but yeah. Well? Yeah, whatever. That was quick. Tainter of rooms. Good morning, everyone. My name is Hans de Goudel, and I work for Red Hat. I'm giving a presentation today about making Fedora run better on laptops, which seems to be a popular topic, which is good. And, well, let's just get started. So for starters, I would like to introduce our team. We are a new team in Red Hat who is going to focus on making Fedora run better on laptops. So what do we want to do specifically? We try to look at things from a user point of view, from a user experience point of view, and improve the user experience. Specifically, we focus on hardware-related problems. So if there's something like evolution not syncing properly with your calendar or something that's not something our team will be doing, but suspending zoom issues, issues with docking stations, things like that, is where our focus will be. Currently, if you buy, say, the new Lenovo ThinkPad T470S, which is the KB-Lake generation of the T460S, you'll probably have a suboptimal experience. Usually, if you buy a new generation laptop the day they come out, that doesn't end well. You go to a painful phase until everything is fixed upstream. We want to make that better. We hope to make that better. That's going to be tricky to do, actually, because that will require our hardware vendors to give us early hardware access, which is a problem. I really want a friend of mine going to phrase friction-free computing or friction-free user experience. We want to make it as easy to run Fedora on a select list of laptops as it currently is to run Mac OS X on a Mac, right? Because a lot of people in the tech sector, even though they're working with open-source things or they're working on the web using open-source technology, they opt for a Macbook. I think one of the reasons that's being done is just because the experience of running Linux on a laptop is not that great. If you're not a tech-saving user who can fix their own stuff. So that's what we're aiming for. Well, who are we? We're Alberto Ruiz in the back, who is our manager who's based in the UK at the moment. Benjamin Berg, who starts February 1st. He was here for a meeting with the rest of us already, even though he hasn't started yet. He's traveling back home today. Christian Calder, who's in the Munich office just like Benjamin. They will have access to a lot of laptops because a lot of the laptops for Amiga Associates are distributed from the Munich office. Amira Schodil, an intern who is currently back at the Uni but will be back in July, I guess, to work with us. Oliver Kutiras, who is currently giving a talk. I'm a fleet commander, so he's not here. John Jones, who should be here somewhere. And Rob Marshall. Oh, yeah, sure, of course. Hi, Christian. So yeah, this is us. And, well, we're going to try to make your life easier if you run Flora on the laptop. So we had our first team kickoff meeting this week. We got together to make a plan. So what we're going to do, we're going to do a bunch of things. The main thing is we're going to select a couple of popular laptop models because it will be impossible to support every existing laptop model out there. Think on models which are used a lot by Linux users but also by Red Hat internally. So ThinkBats, the T460s, the T470s, the X1 Carbon, the latest gen, the Dell XPS models are popular, right, including the developer editions. So we're going to try to get access to a number of these models and make a list of them and then make sure if you use these models you have a smooth experience. We plan to, the way we plan to do that is run a standardized test suite. A run of test suite, I can use test plan. It needs to be done manually. And then see what doesn't work and then file box and start working on resolving those issues. We also plan to document all this work. So a user can see, I want to buy a laptop. I want to run Fedora. Which models are being tested and what is the status of them? How will they work at the moment? We currently have some skeleton web pages for them. Well, they're not full skeletons, but this is the landing page, basically, which we have, which is not much yet. It explains that we strive for Fedora working well on any laptop. But yeah, since that's impossible, we focus on a number. I specifically worded it that way because I believe it's important that we're not seen as playing favors to a certain handler or certain models. We have written a test plan which looks like this and it's long. So we also have a bunch of suspended resume tests. The second test is interesting because my colleagues pointed that out to me like, are you checking if things work after a resume? Yes, because that's all called in one point of the plan. After a resume, we check all general functionality tests. So this is actually again running 20 or 25 tests again after a suspended resume. So we try to cover all our bases here. And if you're interested in what we're doing, you could take a look here and if you think like you're missing this or that, let us know. Although the goal is to keep this plan somewhat limited, not too in-depth, because we want to be able to say test a laptop in a day, a work day, so eight hours. Because we also need to re-test after kernel updates and things like that. There's going to be a lot of work then. Then per laptop we're going to create a report page which will be linked from the main landing page. You can use it over here. There's only one, my laptop, which is an XPS-15. And this is the skeleton page for that for now. It has room for no issues. It explains it was tested with that kernel on the Fedora 25 workstation. When I say make Fedora run better on laptops, I mean make Fedora workstation or the GNOME 3 desktop running on Fedora run better on laptops. We don't have the manpower or plans to look at XFCE or KDE or whatever. Some of the work we do will of course also benefit those if it's at the kernel level. But if it's higher level integration work then sorry, the people who care about these desktops will. They can always ask us questions, how did you solve that? But it's not something we will actively be working on. I think that's important to mention. As I said before, we'll of course found work for any issues found and work on them or work with relevant teams to try and get things fixed. My advice would be if you want to buy a laptop and there is a model which sort of suits your needs in the list we try to support. Look at the testing results page because for example we'll soon have access to the T470S and we're going to run it through all the tests, create a wiki page for it but it might be too early for some users to buy it, right? I expect there to be a list of known issues which we are going to resolve on that page in a week or while probably. So as I said before, the test plan we want to be able to execute it in one working day because we're going to re-run it because the next step of the plan is that we'll test them as they come out, right? And a lot of the issues with laptops are when they just hit the market and we just need to work on Linux integration and pick certain hardware related bugs. But another problem is which is also in my eyes a big problem for four users. As I said before, the integration free user experience is that if they install updates and they get a new kernel from Fedora because we jumped kernel version when possible because it's impossible to do security updates for the older kernels with the mempower we have, you can get regressions, right? I just heard a story today that someone within Red Hat is actually already using the T470S and it was... Oh, no, it was the XPS 13.0 version, wrong laptop, but he's using a laptop, it worked, he installed a bunch of updates and the Touchpad no longer worked. Well, not being able to control your mouse cursor is sort of an unpleasant user experience to put it mildly, right? So we want to also retest them at least when the RC1 kernel comes out because I don't know if you're familiar with the kernel release cycle, but what happens is most kernel developers work on changes which all get merged in the merge window which is just after a final has been released before RC1. So after RC1 in the release cycle of the kernel we're basically only talking about bug fixes. So we want to take that RC1 which is the bulk of all the changes which are going to land in the next kernel and then run tests with them on the laptop's models we support so we can detect problems caused by kernel regressions early and actually get the upstream community pointed out to them before the final gets released which should help a lot with fixing them because Linus will bash people over their head if they don't fix regressions. But that only works if you point them out before the final, right? If it happens after the final, then Linus is already focusing on the next one. So that's part of it. Well, there's a lot of testing going on here and we're actually, most of us are software engineers. We want to focus on fixing stuff and not testing it. So we plan to work also on automated tests especially in the Munich office that will happen. We hope to build a test lab there to run continuous integration tests as far as possible, right? Touchpad is a difficult one. We could maybe build some little robot with a servo which means something left right over the touchpad, right? Well, we can try. We need to look into those kinds of things also depending on how often touchpads regress, right? A big problem for our team is going to be prioritizing stuff I think because we can spend all our time in writing the test suite and not fix a single bug. Or we can spend all our time fixing bugs with new models and have old models regress because we don't detect them in time. So we're going to have to do a balancing act there. A last thing which we also want to look at if we have time over but maybe also prioritize it a bit because otherwise it won't happen is look into improving power consumption on laptops. At least definitely in some cases we just suck in power consumption at some places where we're bad we really need to fix those and then as we have time slowly improve also some of the more areas where we're not as good as we could be. So maybe before I switch to this next topic because it's sort of semi-related it's also something user experience focused, laptop focused which I've been working on as part of the team I might actually just jump forward to this one first because the laptop testing stuff and improving in general is the main focus of our team in this talk so are there any ideas or suggestions what can we do to make your life better as a laptop user? Okay so the question is what is the targeted user base? The targeted user base is I would say non-specialized use cases which is indeed browsing the web watching YouTube but also video conferencing and if you have a really special niche use case we're going to probably not read so Blender is probably a little bit on the side already right? Say that's something which we use but again those are mostly high software things right? Although something like video conferencing would be interesting to look at for us because that also plays into power consumption for example and then video conferencing would be a use case which is something we would look at for power consumption point of view right? But not from I cannot connect to the server point of view because then you're talking higher levels so the question is what about window managers? As I said before we support Fedora Workstation we support GNOME 3, GNOME Shell and that's it If you're running another window manager if you're doing one of the spins now don't have people from the KDE or XSEE spin here please do talk to us we're interested in helping you with like but we don't have manpower to do anything more than share our experience and let you benefit that way So the question is what about Apple hardware? It's a difficult one because a lot of the Apple users just want to use Mac OS X but a few people want to run Fedora it's on our radar we discussed it and it's sort of in the nice to have category so depending on how all the other stuff goes and how overworked we get we may or may not look into that We discussed that it's on our radar I assume we're talking about running Fedora on Apple hardware right? Yeah I cannot make any promises but it's somewhere on our radar Yes Sorry can you speak up a bit? Yes So the remark was that Fedora actually already runs pretty well on some generation MacBooks and it's completely true that it's because there are people in the Fedora community and why Fedora project who care about this newer generations I've heard are less well supported because at one time there was this thing where there were a number of people actively looking into doing Fedora on Macs and I know for example that the Anaconda team has a bunch of MacBooks which they test installation on but those are older MacBooks right? So one issue here is going to be hardware access and other issues going to be manpower issues going to be prioritization So yeah there is no easy answer but MacBooks are definitely on our radar running Fedora on MacBooks and you're right the other person who asked the question that it also is a chicken and egg problem that if we can tell Mac users that it's possible to run Fedora then we may get more users that way and more bug fixes from them or more valuable feedback from them so the question is will we take care of older hardware generations let me switch back to the wiki page stuff so currently this is very flat it just has a tested laptop we want to do Fedora tested laptops and Fedora community tested laptops maybe as two separate pages and our team will not be able to do that because of manpower reasons we do plan to make a lot of the PCI tests also those which don't require dedicated hardware external to the laptop available to the community we actually want to fully integrate them into the workstation so that you get the workstation live CD and you get an option boot workstation test memory run Fedora workstation test suite and then you can provide feedback so we're sort of looking it's a valid question it's a valid point that a lot of people are happy with older thinkpads and want to have more older Dell laptops or whatever and it's definitely a valid point but we're not specifically going to spend resources on them because there's only eight of us and so much work to do okay sure we'll talk to Christian behind you he's also in unix so there are some things that can suggest how to do this I guess you know what I have for you now is I know that you're doing a lot of stuff through wiki and I have some crazy tools to interact with wiki but I think you may benefit from better tools absolutely yeah we're currently at the very early stages of writing a thing and we're doing manual validation tests better than anything wiki pages and I suspect we may be able to put your workflow into that and that might well Oliver who isn't here right now is actually a web developer he's working on fleet commander but slowly moving over to our team Oliver don't remember so is actually a web developer and we already talked to the Fedora OpenQE guys we've already we've actually in the Brno office we've been through all the floors we started talking to the anaconda team what do we use for testing and then the RTT team and then the real desktop QE team and the Fedora OpenQE team so we're aware what infrastructure is there for example results DB looks interesting but it needs a better frontend no but we definitely discuss tooling during our team meeting and we want to piggyback on what's already there probably OpenQE results DB but do a better web interface so we don't need to edit like this web page right this needs to be generated and not manually edited I completely agree with you so the remark is it might be good to document how you fix common issues for example one thing which comes to my mind is backlight control laptops right that doesn't always work you can control the backlight brightness a very valid point can someone write this down okay so the question is we're essentially going to do a bit Fedora hardware compatibility database right and currently if you run if you say you look for XPS 13 Linux on Google before you buy the laptop you end up usually on some Ubuntu forum page are we going to work with them it's an interesting question it's not on a radar and I think it's outside of our scope to do that but yeah I understand what you're saying you first that could be used like that could be you know using the time of the let's talk about my laptop the ideal time for my laptop and of course my authorization to you know run some kind of automation test and read the things like I said you have the software for let's just put one more quick comment I'm talking about this because we know that we want to have the better Fedora running for most of the large type of hardware we have and I know that's so such a challenge for us yeah so the question is will it be possible to do something like currently you have a number of internet things where you can share compute time from your computer for to analyze radio waves from the galaxy if there's a life out there and things like that then we do something similar where I can share my laptop to run some of the test you guys are going to do maybe we're currently looking at a live CD approach so your laptop would then need to reboot or net boot or whatever into that CD which then has the latest version of Fedora 25 with all updates also applied on top and then it would run the tests because we do want to run the tests in somewhat of a controlled environment it's something to think about but okay so the question is would it be a good idea to focus on models which are available without windows I know that's not realistic there are just almost no laptops available without windows especially for for consumers and if you're a big company you can sort of negotiate that but no I don't think that's realistic but they have no users almost no users we want to pick the models which a lot of people use right we want to pick the popular models within the Linux community and also the wider computer user community so you were talking about power management yeah we are we are Christian specifically in the back has been looking for the last month or so on power top what power top does and what it doesn't do and making it more user friendly maybe putting all that into a library that we can put reporting demons on top of that library and things like that so yeah that's definitely on our radar looking into improving the tools for power management research or figuring out what is actually consuming the power so that you can in a targeted way focus on optimizing stuff really include the check and the vendor supports the upgrade I was interesting point interesting point yeah I guess we should put that on the test list oh sorry so the question was yesterday Peter Jones also from our team gave the firmware update talk about how it's now possible with GNOME software to just say at least on some vendor laptops that it recognizes what firmware you have there's an update available one that you can just install from Linux the question is will we have that as part of the test plan I think it should be there yes you can run the test plan you can run the test plan and repeatedly run the test plan right to catch regressions so we want to make that easy or anyone say we want to provide a live CD where it's just a boot option to run a whole bunch of the test automated test will be interactive you can probably choose when you choose the option boot into test mode I only want to run the automated test because I'm willing to do that and walk away when I don't have time to do the manual stuff or give me the full blown test what? at the moment? zero but we're working we had our kickoff with this team this week right we are starting basically February 1st so yeah we hope to get there but we'll have to see it will be difficult to automate everything yes so Adam's question was you have a list of models you want to support as a team or make sure that they're well tested and documented what any known issues are and on the other hand I'm talking about community testing as I said before we have two lists we want to have a list like this which we as the Fedora laptop team or whatever officially the Fedora desktop hardware enablement team support and on the other hand if the community wants to support some different models for example a model which can be bought without windows more power to the community right yes that's basically the idea so there's a question in the back I understood yes so I tried to keep the list limited but the the red hats internal models are definitely part of our hit list but we try to maybe keep the older ones which will be faced out soon off of it because we have to limit the set right so for example the T460S is actually being used in red hat right and the X1 Carbon that's one of the reasons why they're up there so we definitely want to also help make the CSB experience better basically through fixing things upstream and then having the reality backport them to CSB so now with this effort but is there some let's say temporary or something I mean it's just around testing the model and that's not bad but how that's important finding so it's like some way to help you let's say results being helpful to you or something because I believe that it's gonna kick start your effort so the community gets involved and they have an easy way to actually get involved so the question is let's say we get community involvement how can a community member get results on the wiki in an easier way than editing the wiki it's sort of the same as Adam's question about the tooling we want to test we need in the end to just have a report button where it will then enter the results into resultDB you'll probably need FES credentials or something like that we need some authentication to avoid spam but yeah we definitely want to make it not only easy to run the test but providing a live image where you can run the test suite partly automatic partly manual but also we want to have an automated mechanism to submit results as I said before the page I have here now currently this is manually written we want these to be generated from a database probably not even in the wiki probably just our own tool under the fedora umbrella but that's all future music basically right where we're going to do that when we get around to it hopefully somewhere the next year basically okay last question about this and then I'm going to do the other bit of stuff oh and now I can only return it on again so yeah you can disable it without needing to go into the bias sorry okay yeah yeah so actually the question was for the recording can I are we going to offer a way to for example disable the touchpad because some people don't like the touchpad because it gets in the way with typing well we're targeting GNOME 3 that already has a checkbox to disable the touchpad but we really don't want people to need to do this right I actually used to work on libinput together with Peter Hutterer and we spend a lot of time on actually making this not necessary currently I don't know when you last tried it or if you're actually already using libinput in XFCE but if you use libinput as long as you're typing the touchpad gets disabled and it stays disabled for 200 or 300 milliseconds after your last key press same actually if you use the trackpoint the trackpoint also disables other touchpad because some people because when you use the trackpoint you use the mouse buttons and then you rest your hand on the touchpad so we're really trying to make it that's again the friction of the user you shouldn't have to touch of your touchpad we should be able to see that it's not really a finger trying to move the mouse but it's a hand or part of a thumb or whatever which is touching the touchpad but we want to do both we want to make it easy to turn it off if it really gets in your way and we also want to make it so you don't have to turn it off final question so basically you stop where the knife keeps the previous action ok so the question is about what happens if you have a finger down on the touchpad and you're moving something and you hit with the second finger and our behavior there currently is to switch to two fingers scrolling and the Mac just keeps already we're clearly moving the pointer around it just keeps moving the pointer around I think we could do better there please file a bug against lip input go to Baxilla, choose component lip input Peter Hutter will pick it up and I actually noticed the same thing when I was working in open office that my slide would slide to the side where I was trying to edit it because I accidentally touched with the second finger so I completely agree and we need to do better there ok so although this is really interesting I also prepared a bit of presentation about something which I believe is also interesting which is a lot of laptop users have Optimus which has an extra NVIDIA GPU in there for doing more graphical demanding stuff and we support that somewhat using the Nouveau the open source driver for NVIDIA GPUs but the performance that way is not optimal so a lot of people want to use the NVIDIA binary driver but currently the experience is you need to install the NVIDIA binary driver and hopefully it works well actually if you install it on an Optimus laptop it doesn't work you need to manually create an XORG.com which matches your exact hardware with PCI pads in there etc like at which PCI slot the card actually is which is a pain but let's say you even get to that point or you're using a desktop with NVIDIA then if you install a kernel update things break and you get a black screen nothing works and you need to reboot into the BIOS machine off by holding the power button for four seconds and any grub add a command line option to not boot into the graphical user environment and I can fix it but our target audience cannot fix it so we need to do better here because this is something people want this is also something which for example is important for people who want to use Steam on Linux so for the last two months this is actually what I've been working on mostly for also as part of part of the new team already about two months ago slightly longer so what have I done? I have made some changes to the XORG.com syntax so that we can have smarter configuration that you can say if you see the NVIDIA kernel driver installed then behave in this way else behave in another way so you don't need to manually edit config files when you switch basically what will happen now is if you do the kernel upgrade and you don't get the NVIDIA kernel model against the new kernel it will fully automatically fall back to Nouveau that's the idea so it will do a number of things we actually in X to talk to do OpenGL you need a GLX module which implements the GL over X protocol and NVIDIA has its own module and we can load only one in the X server so you can talk MesaGLX or NVIDIAGLX another thing is the whole Optimus story I just was telling about it if you install the binary driver it just won't work unless you create a whole load of manual config so what I what we do now or rather what the NVIDIA package from third-party repositories does is it can drop this config file in place and this config file basically says if the kernel driver is NVIDIA DRM then use the NVIDIA X-site driver make the NVIDIA GPU the primary GPU all your rendering is happening on the NVIDIA GPU that's mandatory with the NVIDIA driver it cannot do offload rendering and it adds something to the module path so that the right GLX module will get loaded so with this little snippet as part of third-party NVIDIA drivers almost all the manual configuration goes away actually which is nice another thing, another big problem with using the NVIDIA driver is applications who use OpenGL they open libgl.so dynamic library and that used to be Mesa and the NVIDIA driver used to fix that by just copy its own copy over an open source version which means that if you need to fall back to the open source driver because the NVIDIA driver doesn't work things still don't work because the application is loading the wrong OpenGL library so we have a new library for that so the actual OpenGL library now is a stop which dispatches into the right library it knows from the GLX module which one it needs to use and then so this is finished now this is in updates testing and hopefully soon we'll be able to make an announcement that we are working together with the third-party repository that you can just in GNOME software say give me the NVIDIA binary driver and we'll be there if you have enabled third-party sources there is a checkbox for that if you're open source and you don't want this you're not getting it we're not forcing it on anyone so a little demo currently if you look at my kernel command line it says blacklist is the NVIDIA driver so it will load the open source driver and if I now run GLXgears it will say that actually it will say here that it's running better on Intel HD graphics so it's using my CPU integrated graphics for OpenGL and if I now run this thing I actually had time to create a little it says it's using the NVIDIA driver and I can switch to the NVIDIA driver and hit OK and now it says it needs to reboot or you can reboot later but you won't get the change until you reboot I'm going to hit no now because I want to show one more thing and then if you now look at the only change that tool makes is it changes the blacklist to NVIDIA it says don't use the NVIDIA driver and the NVIDIA driver will auto load and vice versa now I'm not going to get demo effect so after this it should be using the NVIDIA driver so no other changes just change which kernel module gets loaded I still need to write a little demon which actually checks before it starts the graphical login manager if the NVIDIA driver successfully loaded and if it didn't then force load Nouveau even if it was blacklisted so you at least get a user interface and all the black screen but that's the last bit okay so the question is will these tools, the switching to and the demon to make sure Nouveau gets loaded even if it was blacklisted and all Fedora machines no it won't it will only get installed as part of the NVIDIA driver package which you get from a third-party repository ah it didn't remember the settings for the beamer oh well maybe it changed because driver changes whatever you should get more interesting picture now yes and as you can see it's now running on the GeoForce there's no more MESA in there because this is actually the NVIDIA binary driver so my entire desktop environment is now running being rendered by the NVIDIA GPU but being displayed by the Intel GPU all the rendered frames are being passed over the PCI bus because the NVIDIA GPU on this laptop isn't hooked up to any video outputs but it works so if you now want to play games on this laptop which need advanced NVIDIA OpenGL features it should work and what I forgot to do was run PowerTop idle on my machine is about 8 watts and now it's 70.3 watts it will probably get slightly better if I keep talking for a minute or two but it won't get much better so the difference is about 8 watts just because I turned on the NVIDIA GPU which is also why I did the switching tool so if you then need your horsepower you can switch to the binary driver and if you don't you can run the open source stack which is way more energy efficient because it does everything on the Intel GPU unfortunately it requires a reboot or it actually dropped down to only oh that's not bad it's only 2 or 3 watts more they improved a lot in this generation GPUs so I guess I any more questions about this or about the original topic hey Hans, can you share the device stats instead of the overview? can I show device stats instead of oh you mean this one yeah so are there any more questions in Tarsen? this is all requiring its odd stack, isn't it? no this is all requiring well using the NVIDIA driver the binary driver requires using the X11 stack yes this is not yet available on Wayland a very good question it is possible to drop back to text mode and then oh sorry the question was why did you have to reboot? can you just remove one kernel module and insert the other kernel driver so it is possible to switch back to text mode to disable the frame buffer console remove the Nouveau driver and install the NVIDIA driver or the other way around but both of them expect to find the GPU in a pristine state so it will work most of the time but not all of the time so I prefer to just reboot and make sure it works everywhere I know that actually what you're saying is what Ubuntu does it actually allows this that way you only need to log out and in you don't need to reboot but that's pretty fragile and I don't want to go there I've talked to both the NVIDIA UNIX guys who I've met a number of times and to BenchX one of the Nouveau developers and neither of them are really enthusiastic about the way Ubuntu is doing this they both think it's a bad idea any more questions? you can use the NVIDIA driver on an Optimus laptop the whole desktop is rendered by the NVIDIA GPU are there some plans to allow offload rendering so that you use the Intel GPU for desktop thingies but if you want to run Blender or a game you can use the NVIDIA GPU at the moment there are to the best of my knowledge no plans for that from NVIDIA's side they don't care much about that use case so the remark about doing this so using the Intel GPU for most of and offloading some stuff to the NVIDIA GPU does work with the open source stack that's correct it works on both Wayland and XORG X11 you can run the more energy efficient Intel GPU and use the NVIDIA GPU when you need to but the performance of Nouveau is such that you don't win a lot on modern GPUs because we don't allow changing the clock speed oh AMD it's possible with the open source stack for NVIDIA too on AMD we get much better performance then yes if there are no more questions I'm exactly within time thank you for your time are you changing the format of the presentations just a bit because you're more cooperative you know and ask a question now oh yeah I was thinking I've got a presentation then question I was thinking you have two topics and there will be lots of discussion do you know how to provide the signs it's useful there's a clock over there yeah we'll have to provide some feedback to the session chair managers that the signs there's a font on the signs it's just very small we can't see it over there but it was possible to give you a new flash to sign repeat the question every now and then nowhere because somehow you forget it's normal right you're just focusing on the dog and just forget about it it doesn't really matter I should be sitting over there the font has to be what's the matter being you know it's portrait it should be landscape it should be landscape yeah it should be landscape yeah it should be landscape yeah it should be landscape yeah it should be very easy it should be it should be one two three two two three four five six five six five we will be using bg bg okay the only thing you have to do is to solve the resolution of the output some mapping by the attribute cool give that a try when you will be speaking this is the microphone only for recording we don't have any hand out microphone so we just stay in the area speak a bit louder so everyone can hear and also repeat the question please we've got some signs that we're showing you during the talk 10 minutes remaining if there are questions I will be almost constantly holding up the signs and repeat the questions to the microphone for recording what should we do until questions 40 minutes so you've got the longest of the one hour so you've got 45 minutes for the talk and then 10 minutes for questions we can modify depending on how much time you need for your talk we can improvise or if you plan to change the form of your presentation so you've got a logical part of your presentation so you've got 20 minutes then let the audience ask questions and then do another 20 minutes and then let them ask questions again basically it depends on you I just did it show you the signs 10 minutes left out of time and last question do we know or do we add up questions during the talk you don't mind questions during the talk yeah, I'll say that I didn't rename it I'm just gonna I guess I didn't rename the the the new power I don't have to turn on the battery and again also it's the clicker of the presentation with the laser camera there you go