lundmar | trying out pre-release 19.04, it seems grub no longer loads the correct modules to support usb keyboard input? | 09:28 |
---|---|---|
lundmar | I can get keyboard working if I manually load the modules (GRUB_PRELOAD_MODULES="usb usb_keyboard ehci ohci uhci") but then it fails to find my nvme disk. Anyone else with similar issue? | 09:29 |
lundmar | tested on xps 15 (9570) | 09:30 |
guiverc | lundmar, i just booted a 19.04 laptop (thinkpad) & it let me use usb keyboard (instead of laptop kbd) at all steps, so it may be specific to your/some devices.. | 09:34 |
lundmar | guiverc: yes, it might be specific to xps 15. Some say that usb legacy support needs to be enable in bios but I have already done that. | 09:37 |
guiverc | lundmar, i'm unlikely to be able to help you, if you wait maybe someone else will be able. i just tried a sony thing and didn't have the success i expected; but I didn't see grub at all so i wanna explore what i saw instead | 09:44 |
lundmar | guiverc: ok thanks. xps 15 is pretty popular - I simply hope we can get it sorted out before release. | 09:46 |
guiverc | lundmar, file a bug report is probably the best advice anyone can give you, at least it leaves a 'paper' trail that people can comment on, track etc | 09:47 |
lotuspsychje | lundmar: biosupdate might help | 10:11 |
lotuspsychje | lundmar: see also if you can trace acpi issues in your logs | 10:13 |
lundmar | lotuspsychje: I'm running latest. Worked fine with ubuntu 18.10 but after upgrade to 19.04 grub usb input stoppped working. | 10:13 |
lotuspsychje | lundmar: sounds like a kernel issue then, can we have your dmesg pastebin plz? | 10:13 |
lundmar | grub kernel? | 10:14 |
lotuspsychje | !dmesg | 10:14 |
ubottu | dmesg is a console command which outputs the kernel ring buffer - an important log for diagnosing problems in Linux. Often when something errors with hardware it will result in additional lines reported which can be seen by running dmesg in a console. | 10:14 |
lundmar | no no, this is before loading OS | 10:14 |
lundmar | grub ignores my keyboard on xps 15 | 10:14 |
lotuspsychje | lundmar: keyboard works on desktop? | 10:14 |
lundmar | yes | 10:15 |
lotuspsychje | oh right | 10:15 |
lundmar | 19.04 broge grub keyboard :/ | 10:15 |
lundmar | breaks* | 10:15 |
lotuspsychje | lemme search around | 10:15 |
lundmar | i'm even booting non-secure mode now | 10:15 |
lotuspsychje | lundmar: legacy usb enabled in bios? | 10:16 |
lundmar | lotuspsychje: enabled | 10:16 |
lundmar | lotuspsychje: its very similar to the issue seen here (long ago): https://ubuntuforums.org/showthread.php?t=2226621 | 10:17 |
lotuspsychje | lundmar: you sure this works in 18.10 right? | 10:17 |
lundmar | yes, never had any issues with 18.10 | 10:17 |
lundmar | but 19.04 upgrade blew things up | 10:17 |
lotuspsychje | interesting | 10:17 |
lundmar | I suspect maybe they messed up the default grub payload | 10:18 |
lundmar | lotuspsychje: I've tried the stuff from the link with GRUB_PRELOAD_MODULES and I can get the keyboard working but then it can't find my nvme disk :/ | 10:18 |
lotuspsychje | lundmar: are you dualbooting or singleboot? | 10:19 |
lundmar | lotuspsychje: singleboot ubuntu | 10:20 |
lotuspsychje | lundmar: i think for nvme ssd you need advanced partitioning in setup | 10:20 |
lundmar | lotuspsychje: im not using lvm | 10:22 |
lotuspsychje | lundmar: did you try another keyboard? | 10:24 |
lundmar | lotuspsychje: i've tried the laptop keyboard which i think is usb and then my logitech wireless via usb dongle | 10:25 |
lundmar | neither works | 10:25 |
lotuspsychje | allright | 10:25 |
lotuspsychje | lundmar: so your keyboard works also in bios itself right? | 10:26 |
lundmar | lotuspsychje: correct | 10:27 |
lotuspsychje | lundmar: allright, lets create a new bug you have time for it? | 10:27 |
lundmar | and I can force it to work by forcing preload of the grub modules | 10:27 |
lotuspsychje | ubuntu-bug grub2 from terminal | 10:28 |
lundmar | lotuspsychje: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1821709 | 10:33 |
ubottu | Launchpad bug 1821709 in grub2 (Ubuntu) "Ubuntu 19.04 breaks grub keyboard input on XPS 15" [Undecided,New] | 10:33 |
lotuspsychje | lundmar: tnx for taking your time to create it | 10:33 |
lotuspsychje | lemme take a look | 10:33 |
lotuspsychje | !info linux-image-generic | 10:34 |
ubottu | linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 5.0.0.7.8 (disco), package size 2 kB, installed size 15 kB | 10:34 |
lotuspsychje | lundmar: ah, i have a suggest could you try this with a 19.04 fresh liveusb? | 10:34 |
lotuspsychje | lundmar: testing dev branch best always cleans instead of upgrades | 10:35 |
lundmar | lotuspsychje: I'm using liveusb to try fix grub. The liveusb grub works fine. | 10:36 |
lotuspsychje | lundmar: also please describe your grub pre modules test too | 10:36 |
lotuspsychje | lundmar: so keyboard works on grub livemode? | 10:37 |
lundmar | I know I took at risk upgrading at this early stage but thats why im here - to avoid this issue in final release. | 10:37 |
lundmar | lotuspsychje: correct | 10:37 |
lotuspsychje | lundmar: ok please add this to the bug too | 10:37 |
lotuspsychje | lundmar: must be some upgrade flaw somewhere then | 10:37 |
lotuspsychje | we strongly reccomend testing dev versions clean always | 10:39 |
lundmar | yes, i took a chance haha | 10:40 |
lundmar | still, someone needs to test upgrade :D | 10:40 |
lotuspsychje | lundmar: reccomended upgrades at final mate | 10:41 |
lotuspsychje | lundmar: mark your bug solved ok, as this works on 19.04 live daily | 10:42 |
lundmar | lotuspsychje: but running from live and install is a different thing no? | 10:44 |
lundmar | i mean, this could still be a real issue | 10:44 |
lotuspsychje | lundmar: did you try installing a daily 19.04 fresh? | 10:44 |
lundmar | lotuspsychje: no, upgrade. | 10:45 |
lotuspsychje | lundmar: test please | 10:45 |
lotuspsychje | if live works, the daily install 'should' also work | 10:45 |
lundmar | I can't do a fresh install atm. | 10:46 |
lotuspsychje | lundmar: ok thats your choice np, but hopefully you understand we cant bug out on a non-daily | 10:46 |
lundmar | sure | 10:46 |
lotuspsychje | lundmar: its not fair towards the devs and avoid making more work then necesary | 10:47 |
lundmar | i understand, I took at chance upgrading early just before beta release. Time will tell if the issue will persist. | 10:48 |
lotuspsychje | anyway final will be there for you soon | 10:48 |
lotuspsychje | !final | 10:48 |
ubottu | If you install a development version of Ubuntu Disco and keep up with package updates, then you will be upgraded to the official release of 19.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal. | 10:48 |
lotuspsychje | lundmar: but that doesnt mean this will get your issue solved, hence it might hold leftovers from the upgrade | 10:49 |
lotuspsychje | its also a move from non-lts to non-lts, less stable | 10:49 |
lundmar | lotuspsychje: is it possible to do a fresh install without destroying home ? | 10:50 |
lotuspsychje | lundmar: setup can choose to install 'next' your current install | 10:51 |
lotuspsychje | lundmar: but ideal is to backup and fresh install 19.04 (if you want to help test) | 10:52 |
lotuspsychje | cause until final, things can still break (not reccomended for daily usage yet) | 10:53 |
lundmar | ok, i'll give it a try and follow up after final | 10:53 |
isomari | greetings, I update my kubuntu 19.04 everyday but my kernel is still at 4.18.0-13-generic. How can I update it? | 13:57 |
isomari | to 5.0 I mean. | 13:58 |
nacc | isomari: `lsb_release -sd` | 14:09 |
nacc | isomari: 4.18.0-13 isn't even the right 18.10 kernel | 14:09 |
isomari | nacc: I said I'm on 19.04 | 14:10 |
nacc | isomari: you said that, but that's not the correct kernel | 14:10 |
nacc | isomari: so i would like actual proof :) | 14:10 |
nacc | isomari: 18.10 is at 4.18.0-16 for one thing. | 14:11 |
isomari | 1 sec ..... | 14:11 |
isomari | I got that from uname -r | 14:11 |
nacc | isomari: ok, not what i asked for. also when you say you 'update' every day, what specifically do you mean? | 14:12 |
isomari | lsb returns Ubuntu Disco Dingo (development branch) | 14:13 |
nacc | isomari: ok, in a pastebin `apt-cache policy linux-image-generic; ls /boot` | 14:13 |
isomari | by update I mean apt-get update; apt-get upgrade | 14:13 |
nacc | isomari: you should be using dist-upgrade or apt full-upgrade during the development release | 14:15 |
isomari | nacc: sorry, my system just lost power, 1 sec .... | 14:20 |
isomari | proof? what do you want me to do? | 14:21 |
nacc | isomari: we've moved on | 14:21 |
nacc | isomari: you should be using dist-upgrade or apt full-upgrade during the development release | 14:21 |
isomari | nacc: that's what I used to originally upgrade from cosmic. | 14:22 |
isomari | dist-upgrade | 14:22 |
nacc | isomari: no you didn't | 14:22 |
teward | isomari: dist-upgrade doesn't upgrade you between Ubuntu releases | 14:22 |
nacc | isomari: do-release-upgrade, is probably waht you mean | 14:22 |
teward | isomari: apt-get dist-upgrade will install all packages that have updates INCLUDING their dependent packages | 14:22 |
isomari | nacc: with all du respect, It's still in my history. I'm not a layman. | 14:23 |
nacc | isomari: if you did do a manual sources.list modification and dist-upgrade, then you didn't do it correctly. | 14:23 |
teward | ^ that | 14:23 |
isomari | ok. That's what i did. So what can I do now? | 14:23 |
nacc | isomari: have you done a `sudo apt-get update; sudo apt-get dist-upgrade` ? | 14:24 |
isomari | originaly yes | 14:24 |
nacc | isomari: no, right now. | 14:24 |
isomari | no | 14:24 |
nacc | as I've said a few times. | 14:24 |
isomari | should I? | 14:24 |
nacc | isomari: yes. | 14:24 |
isomari | ok thanks ........ | 14:24 |
isomari | after that ill I be ok? | 14:25 |
nacc | isomari: i don't know. | 14:25 |
isomari | I C | 14:25 |
isomari | well here goes nothing.. | 14:26 |
isomari | funny. after the update, the dist-ugrade only wants to upgrade vivaldi-snapshot. | 14:27 |
nacc | isomari: ok, then the command i asked for 15 minutes ago | 14:29 |
isomari | which one? | 14:29 |
nacc | isomari: ok, in a pastebin `apt-cache policy linux-image-generic; ls /boot` | 14:29 |
isomari | 1 sec ..... | 14:29 |
isomari | https://pastebin.com/c8SghCza | 14:36 |
isomari | https://pastebin.com/80Q3XkFN | 14:39 |
isomari | this is the site I followed to do my upgrade a while back: https://linuxconfig.org/how-to-upgrade-ubuntu-to-19-04-disco-dingo | 14:45 |
isomari | the only difference from that site is that I was/am on kubuntu. | 14:47 |
tomreyn | previously you said you used this (wrong) method to do the release upgrade: edited sources.list manually, replacing the previous release codename by 'disco'. now you're saying you actually followed this how-to, which uses the do-release-upgrade utility to carry out the release upgrade. what you're saying doesn't seem to add up. | 14:58 |
tomreyn | if you used the former method, you should rather do a fresh installation, if you used the latter method, then maybe, too. but then, 19.04 is unreleased and not yet supported, so really you're on your own there. | 14:59 |
isomari | tomreyn: sorry , I was mistaken for a different machine. Not my laptop. | 15:01 |
isomari | sothere's no way to upgrade my kernel? | 15:01 |
tomreyn | install linux-image-generic | 15:03 |
isomari | when the final is released, will I be able to upgrade from this beat? | 15:03 |
isomari | beta | 15:03 |
nacc | isomari: sorry was on the phone | 15:04 |
nacc | isomari: yes, to your last question | 15:04 |
isomari | ok | 15:04 |
nacc | isomari: ... your pastebin doesn't make sense | 15:04 |
isomari | which one? | 15:04 |
nacc | the policy one | 15:05 |
nacc | isomari: `sudo apt-get update` in a pastebin ? | 15:06 |
isomari | I followed that site I posted and I've had n problems with this installation so far. | 15:06 |
isomari | I don't know what could have happened or what I could have done worng. | 15:06 |
nacc | isomari: did you run do-release-upgrade or not? | 15:07 |
isomari | I did | 15:07 |
isomari | it's in my history on feb 2 | 15:07 |
nacc | isomari: your machine is sayng that there is no linux-image-generic package from the mirrors you are using | 15:08 |
nacc | which there is, i just looked on it | 15:08 |
tomreyn | may depend on architecture | 15:08 |
tomreyn | i386? | 15:08 |
nacc | tomreyn: maybe, i see the binary deb for both | 15:08 |
nacc | and rmadison says both are published | 15:09 |
nacc | isomari: are you on i386? | 15:09 |
isomari | 64bit | 15:09 |
tomreyn | ok, i was just guessing | 15:09 |
nacc | tomreyn: ack | 15:09 |
nacc | isomari: please pastebin the `sudo apt-get update` output | 15:09 |
isomari | 1 sec ... | 15:09 |
isomari | it's comming. It's showing 1386 packages. I never noticed that before. | 15:11 |
isomari | still working. Bad connection where I'm at. | 15:11 |
* tomreyn kthxbye | 15:12 | |
isomari | really bad link. zzzzzzzzzzzzzzzzzz | 15:14 |
isomari | in the meantime, how can i upgrade the repos to 64bit? | 15:14 |
isomari | I already pastebinned the soruces.lsit file. I don't see anywhere in there that explains wht apt-get is using 32bit repos. | 15:15 |
isomari | stil updating ............ | 15:16 |
isomari | these typos make me look retarded. ;-) | 15:16 |
isomari | actually, it's showing both 32bit and 64bit repos. still going ....... | 15:24 |
isomari | somewhow I lost the first line: https://pastebin.com/WHBwWVEB | 15:29 |
nacc | isomari: it also failed to download several package lists? | 15:30 |
nacc | isomari: what does `apt-cache policy linux-image-generic` say now? | 15:30 |
isomari | 1 sec ..... | 15:31 |
isomari | https://pastebin.com/7BrsV1WA | 15:32 |
nacc | isomari: ok, now try a `sudo apt-get dist-upgrade` | 15:32 |
isomari | 1 sec ... | 15:32 |
nacc | isomari: afaict, you have network issues, or your mirror is broken, or your were not running `sudo apt-get update` regularly. | 15:33 |
isomari | 266 to upgrade and 86 new. I don't see any kernel though. Should I proceed? | 15:34 |
nacc | isomari: pastebin the output | 15:34 |
isomari | 1 sec .... | 15:34 |
isomari | https://pastebin.com/WP6SXgHp | 15:35 |
nacc | isomari: what are you talkinga bout? line 18. | 15:36 |
isomari | don't mind me. I havent slept in days. ;-) | 15:36 |
isomari | so what was the original problem that I caused? | 15:37 |
nacc | isomari: i don't know, it woudl appear you didn't run `apt update` | 15:37 |
isomari | so should I proceed now? | 15:38 |
nacc | isomari: yes | 15:38 |
isomari | thanks for your patience... | 15:38 |
lundmar | lotuspsychje: I've found a workaround/fix for my grub usb input issue. I've updated the bug report. | 17:49 |
lotuspsychje | lundmar: nice work | 19:48 |
Bashing-om | lundmar: Bug squashing ? | 19:49 |
lotuspsychje | Bashing-om: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1821709 | 19:50 |
ubottu | Launchpad bug 1821709 in grub2 (Ubuntu) "Ubuntu 19.04 breaks grub keyboard input on XPS 15" [Undecided,New] | 19:50 |
Bashing-om | lotuspsychje: Looking :) | 19:51 |
Bashing-om | ^^ Good to know .. noted :) | 19:53 |
lotuspsychje | we adviced to test 19.04 clean instead of upgrade, but he found workaround so | 19:54 |
lundmar | lotuspsychje: at least the bug report will be there if anyone experiences the same post 19.04 release. | 20:08 |
lotuspsychje | yeah its good | 20:09 |
lotuspsychje | we will see what happens at final right | 20:09 |
lundmar | yeah | 20:09 |
lundmar | now that i can use grub again I can continue to try get the intel gpu up and running - the dell xps 15 onboard intel gpu just blanks when booting. I saw the same issue with linux 5.0 on ubuntu 18.10. | 20:11 |
lotuspsychje | weird | 20:12 |
lundmar | yeah, the only way i can get it up and running is with nomodeset but that means software rendering instead of gpu :/ | 20:13 |
tomreyn | you should get a log and post it to get an idea of what the actual issue is. | 20:21 |
tomreyn | one thing you may want to try: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment (remove leading #) the line: #WaylandEnable=false | 20:22 |
tomreyn | that's a workaround for a bug which was since fixed: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356 - so *maybe* it just helps here, too | 20:24 |
ubottu | Launchpad bug 1727356 in mutter (Ubuntu Cosmic) "Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)" [High,Fix released] | 20:24 |
lundmar | tomreyn: that would disable wayland right? I would like to try run wayland. | 20:26 |
tomreyn | it would make gdm not use wayland. i assume this also means you cannot run wayland at all, but i'm not certain there. | 20:27 |
lundmar | also, it worked fine with 17.10 but breaks with any use of linux 5.0 in either 17.10 or 19.04 | 20:27 |
tomreyn | i assume right now you'd be happy to have any kind of graphical output at all | 20:27 |
tomreyn | is this an optimus / prime system? | 20:28 |
lundmar | llvmpipe rendering works, however - not using the gpu features such as my external dock DP monitors do not work | 20:28 |
lundmar | tomreyn: i've blacklisted the noveau driver | 20:28 |
tomreyn | this sounds like you're saying "yes" | 20:29 |
lundmar | i only want to use the intel 630 gpu | 20:29 |
lundmar | yes | 20:29 |
tomreyn | do you know the exact model? | 20:29 |
tomreyn | of the laptop | 20:29 |
lundmar | sure, its the new xps 9570 | 20:29 |
lundmar | aka xps 15 | 20:30 |
tomreyn | then ignore my workaround suggestion, it most likely wont help | 20:30 |
lundmar | its a pretty popular laptop | 20:30 |
lundmar | should work | 20:30 |
tomreyn | this? https://www.notebookcheck.net/Updated-Dell-confirms-that-it-is-fixing-the-XPS-15-9570-GPU-issue-that-it-previously-denied-existed.376516.0.html | 20:31 |
lundmar | tomreyn: i dont think its related - it concerns gpu throttling limits. | 20:33 |
lundmar | either way, the noveau driver is not in play since I've blacklisted it. | 20:34 |
lotuspsychje | lundmar: an optimus card you should not blacklist nvidia, but disable performance mode in nvidia-prime | 20:35 |
tomreyn | but the firmware surely is. maybe this is what your keyboard not working issue is really about: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179 | 20:35 |
ubottu | Launchpad bug 1803179 in linux (Ubuntu) "System does not reliably come out of suspend" [Medium,Confirmed] | 20:35 |
tomreyn | i.e. maybe you did suspend? | 20:36 |
lundmar | i dont use suspend at all | 20:38 |
tomreyn | ok. but you use a docking station, you said? | 20:38 |
lundmar | the last comment in the thread hints at using "acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" | 20:38 |
lundmar | i'm gonna give that a try | 20:39 |
tomreyn | on (just) a quick glance, this really looks like a firmware issue | 20:39 |
lundmar | tomreyn: yes, i've successfully used a dell docking station with 2 external daisy chained DP monitors. | 20:39 |
tomreyn | but without a log it's not possible to say, and even then, maybe, too. | 20:39 |
lundmar | but first step would be to simply have laptop display working with gpu | 20:40 |
OerHeks | maybe "i915.alpha_support=1" helps with that intel 630 ? | 20:40 |
lundmar | OerHeks: I've thought about that but isn't alpha support a bit late for for this chipset? | 20:41 |
lundmar | I would expect it to be fully supported at this point | 20:41 |
OerHeks | worth a try .. | 20:41 |
lundmar | but I will try the option if nothing else works | 20:41 |
OerHeks | it used to be a fix for 620, iirc | 20:41 |
tomreyn | i915.alpha_support=1 was (in some cases) needed for linux 4.14 to 4.18 only, i think | 20:42 |
lundmar | i've seen some use it for intel 630 on a 4.7 kernel | 20:43 |
lundmar | but linux 5.0 .... | 20:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!