| === JanC_ is now known as JanC | ||
| pxeguy | yo guys | 06:12 |
|---|---|---|
| pxeguy | has anyone come across a green, blue and red display on an HP machine after the it finishes loading grub? The kernel doesn't seem to want to pickup the driver | 06:13 |
| tjaalton | no, file it upstream | 06:13 |
| pxeguy | upstream? | 06:13 |
| tjaalton | to intel | 06:13 |
| pxeguy | can you point me in the direction where I can report this? | 06:14 |
| tjaalton | but what does 'lspci -nn -s 02' tell? | 06:14 |
| pxeguy | give me a moment | 06:14 |
| RAOF | Whee! -modesetting is a hot mess on my (admittedly weird) machine. | 06:24 |
| pxeguy | yes... | 06:24 |
| pxeguy | none of these modes are currently working for me | 06:25 |
| tjaalton | RAOF: how? | 06:26 |
| tjaalton | pxeguy: irrelevant. what's your pciid | 06:26 |
| tjaalton | or the hw model | 06:26 |
| TemperoR | Hi tjaalton | 06:27 |
| TemperoR | it's pxeguy | 06:27 |
| tjaalton | k | 06:27 |
| TemperoR | 00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) | 06:27 |
| TemperoR | that's my output | 06:27 |
| tjaalton | and what are you trying to use? | 06:27 |
| tjaalton | should be well supported btw | 06:27 |
| pxeguy | yes | 06:27 |
| pxeguy | give me a moment I want to show you something else | 06:27 |
| RAOF | tjaalton: Extremely slow, it looks like at least two different framebuffers are fighting over the display (so I get torn updates, can only see the real output when moving the mouse, and so on). | 06:28 |
| tjaalton | RAOF: nice | 06:28 |
| TemperoR | *-display UNCLAIMED description: VGA compatible controller product: Sky Lake Integrated Graphics vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list configuration: latency=0 resources: m | 06:28 |
| TemperoR | that's from lwhw | 06:28 |
| TemperoR | lshw' | 06:28 |
| tjaalton | unclaimed because of nomodeset | 06:29 |
| pxeguy | correct | 06:29 |
| tjaalton | nothing useful there | 06:29 |
| tjaalton | and nightly didn't work? | 06:29 |
| tjaalton | does the grub menu work? | 06:29 |
| pxeguy | I'm very worried about using nightly | 06:29 |
| pxeguy | reason being | 06:29 |
| tjaalton | why | 06:29 |
| pxeguy | I'm putting it on a production LTSP server | 06:29 |
| tjaalton | uh | 06:30 |
| pxeguy | sorry not production | 06:30 |
| tjaalton | just try something | 06:30 |
| pxeguy | I'm building it for a client | 06:30 |
| tjaalton | don't tell them that you're testing an unofficial kernel.. | 06:30 |
| pxeguy | yes..... | 06:30 |
| tjaalton | i mean | 06:30 |
| tjaalton | do you want to see it fixed? | 06:30 |
| pxeguy | well to be honest | 06:31 |
| pxeguy | I don't think we will end up using this machine | 06:31 |
| tjaalton | ok then | 06:31 |
| pxeguy | because it is about 12 grand | 06:31 |
| pxeguy | I just wanted to see if I could fix it | 06:31 |
| tjaalton | I'll continue with xserver backports then | 06:31 |
| pxeguy | xserver back ports? | 06:31 |
| tjaalton | my work | 06:31 |
| pxeguy | okay I see | 06:31 |
| pxeguy | thank you for your help | 06:31 |
| RAOF | tjaalton: In partial defence of -modesetting, I've got both an AMD and an NVIDIA card in this box, with three display cables connected to two monitors. | 06:31 |
| tjaalton | RAOF: hehe | 06:32 |
| pxeguy | that is very weird RAOF | 06:32 |
| pxeguy | lmao | 06:32 |
| RAOF | gnome-shell-wayland works fine* by dint of not trying to drive the nvidia card at all :) | 06:34 |
| RAOF | * For values of “fine” which include Xwayland being reasonably frequently unresponsive. | 06:34 |
| tjaalton | modesetting has been working fine for me, though I know there are some corner cases that are known to be broken still | 06:43 |
| pxeguy | btw tjaalton, you say i915 is well supported? | 06:44 |
| tjaalton | like inverting the 2nd head and looking how the eDP is blanked. testing a backport now.. | 06:44 |
| tjaalton | pxeguy: skylake is, in 16.04 and up | 06:44 |
| pxeguy | then it's so weird that it's not working.... | 06:45 |
| tjaalton | that's why I asked you to try latest upstream | 06:46 |
| pxeguy | the latest upstream in terms of intel? | 06:46 |
| pxeguy | or the nightly | 06:46 |
| pxeguy | because that is a 4.8 kernel right? | 06:46 |
| tjaalton | drm-intel-nightly build has latest of i915 | 06:46 |
| pxeguy | oh I see | 06:46 |
| pxeguy | okay that makes sense | 06:46 |
| tjaalton | based on 4.8, that's irrelevant | 06:47 |
| pxeguy | okay I see | 06:47 |
| pxeguy | I downloaded only 3 of the .deb files | 06:47 |
| tjaalton | you just need on | 06:47 |
| tjaalton | one | 06:47 |
| pxeguy | oh really? | 06:47 |
| pxeguy | which one? | 06:47 |
| tjaalton | linux-image...generic | 06:47 |
| tjaalton | .deb | 06:47 |
| pxeguy | okay | 06:47 |
| pxeguy | I have that one | 06:47 |
| tjaalton | what does uname -a tell you? | 06:48 |
| TemperoR | Linux ltsp65 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | 06:48 |
| TemperoR | they said it was supported from 4.4 onwards | 06:48 |
| tjaalton | ok so it's the latest | 06:48 |
| tjaalton | skylake uses i915_bpo on it, which is from 4.7 | 06:48 |
| TemperoR | okay, so then I need 4.7 onwards | 06:49 |
| TemperoR | to get it to work | 06:49 |
| tjaalton | no | 06:49 |
| TemperoR | or can I dl i915 | 06:49 |
| tjaalton | if 4.4.0-38-generic is broken then upstream 4.7 is most likely just as broken | 06:49 |
| tjaalton | just install the nigthly kernel and boot | 06:49 |
| TemperoR | okay what I will do | 06:50 |
| TemperoR | is create a replica of this server | 06:50 |
| TemperoR | and try what you've told me | 06:50 |
| tjaalton | why can't you just install a package | 06:50 |
| tjaalton | if it doesn't work, remove it | 06:50 |
| TemperoR | you don't think it could break anything indefinitely | 06:51 |
| TemperoR | ? | 06:51 |
| tjaalton | no | 06:51 |
| TemperoR | okay I see | 06:51 |
| TemperoR | lemme give it a shot | 06:52 |
| tjaalton | oh goddammit | 06:53 |
| tjaalton | now that PSR is enabled upstream in 4.8 modesetting is b0rked | 06:53 |
| tjaalton | on skylake at least | 06:53 |
| TemperoR | borked | 06:53 |
| TemperoR | xD | 06:53 |
| TemperoR | borked = broked? | 06:53 |
| tjaalton | borkborkbork | 06:54 |
| TemperoR | you're doing me a real big frighten tjaalton xD | 06:56 |
| tjaalton | I was talking to myself, not about your case | 06:56 |
| TemperoR | no I know | 06:56 |
| TemperoR | was just making a joke | 06:56 |
| TemperoR | :p | 06:56 |
| tjaalton | looks like I'm just an idiot, had psr enabled locally | 06:57 |
| TemperoR | do you also do networking tjaalton | 06:58 |
| TemperoR | ? | 06:58 |
| TemperoR | networking and linux go hand in hand often times | 06:58 |
| tjaalton | no | 06:58 |
| tjaalton | pxeguy: so did you test the kernel? | 12:09 |
| pxeguy | hi tjaalton | 12:16 |
| pxeguy | where can I put the .deb file? | 12:16 |
| tjaalton | huh | 12:16 |
| tjaalton | install it | 12:16 |
| pxeguy | apt-get install and then the whole fiele name? | 12:16 |
| tjaalton | no | 12:16 |
| tjaalton | dpkg -i | 12:16 |
| tjaalton | I assume you're mucking with a chroot? | 12:17 |
| tjaalton | that the client boots | 12:17 |
| pxeguy | yes.... | 12:17 |
| pxeguy | yes it boots into the chrooted environment | 12:17 |
| tjaalton | so copy the deb there, then run chroot and install it there | 12:17 |
| tjaalton | unless you have the booted kernel somewhere else | 12:17 |
| tjaalton | can't help you there | 12:18 |
| pxeguy | no I don't think so | 12:18 |
| pxeguy | yeah I know you wouldn't know where I have the stuff stored | 12:18 |
| tjaalton | can you test usb live-image locally? | 12:18 |
| pxeguy | it pulls the config from /var/lib/tftpboot/ltsp/amd64/ | 12:18 |
| pxeguy | I just need to work out where it's pulling the kernel from | 12:19 |
| pxeguy | let me ask one of the other guys in my office | 12:19 |
| pxeguy | okay I know where to put it | 12:30 |
| pxeguy | but I'd need to compile the kernel again right? | 12:30 |
| tjaalton | no | 12:30 |
| tjaalton | how do you normally update the boot kernel? | 12:31 |
| pxeguy | well | 12:33 |
| pxeguy | what I have to do is | 12:33 |
| pxeguy | put the linux image | 12:33 |
| pxeguy | in /opt/ltsp/amd64/boot | 12:34 |
| tjaalton | manually? | 12:34 |
| pxeguy | that would be in the chroot | 12:34 |
| pxeguy | yes | 12:34 |
| pxeguy | I think it's pulling the kernel from there | 12:34 |
| pxeguy | well that's what makes the most sense to me | 12:34 |
| tjaalton | and in /opt/ltsp/amd64/lib/modules you have the kernel modules? | 12:35 |
| tjaalton | per version | 12:35 |
| pxeguy | let me check | 12:35 |
| pxeguy | 4.4.0-28-generic 4.4.0-38-generic | 12:36 |
| pxeguy | that's what in there | 12:36 |
| tjaalton | ok | 12:36 |
| pxeguy | give me a moment | 12:36 |
| pxeguy | I'll tell you which one it's pulling | 12:36 |
| tjaalton | so, copy the image in, say /opt/ltsp/amd64/tmp, then run 'chroot /opt/ltsp/amd64/ /bin/bash; dpkg -i /tmp/linux-image....deb' | 12:37 |
| pxeguy | btw would booting from a legacy bios affect any of the kernel crap or is a completely seperate story all together? | 12:38 |
| tjaalton | no | 12:38 |
| pxeguy | okay thanks just wanted to confirm | 12:38 |
| tjaalton | well, could be that it'd just work with uefi and local usb live | 12:39 |
| tjaalton | but who knows | 12:39 |
| pxeguy | btw, where should the i915 module be installed? | 12:41 |
| tjaalton | why? | 12:41 |
| pxeguy | and does this error "could not create tracefs" mean to you | 12:41 |
| tjaalton | no | 12:41 |
| pxeguy | I'm just curious | 12:41 |
| tjaalton | under /lib/modules | 12:41 |
| pxeguy | okay so i915 should actually be in /lib/modules | 12:44 |
| tjaalton | of the chroot | 12:45 |
| tjaalton | don't install the kernel on the host machine | 12:45 |
| tjaalton | but under the chroot, like I said | 12:45 |
| pxeguy | okay | 12:45 |
| pxeguy | will do | 12:45 |
| pxeguy | is this the correct kernel | 12:55 |
| pxeguy | linux-image-4.8.0-994-generic_4.8.0-994.201609262201_amd64.deb | 12:55 |
| tjaalton | sounds about right | 12:58 |
| pxeguy | well that's what I got from the nightly package | 13:00 |
| pxeguy | :0 | 13:00 |
| pxeguy | :) | 13:00 |
| tjaalton | 994 means nightly | 13:01 |
| pxeguy | okay sweet | 13:07 |
| pxeguy | and it won't break anything indefinitely? | 13:10 |
| pxeguy | sorry I'm just making sure | 13:10 |
| tjaalton | no | 13:11 |
| pxeguy | and what is the process to uninstall? | 13:15 |
| tjaalton | dpkg --purge linux-image linux-image-4.8.0-994-generic | 13:15 |
| tjaalton | on the chroot | 13:15 |
| pxeguy | I ran | 13:29 |
| pxeguy | dpkg -i /tmp/linux-image....deb | 13:29 |
| pxeguy | obviously with the correct file | 13:29 |
| pxeguy | and it's not popping up in lib/modules | 13:29 |
| tjaalton | you're in the chroot, and there's no 4.8.0-994 subdif? | 13:30 |
| tjaalton | *subdir | 13:30 |
| pxeguy | (Reading database ... 189752 files and directories currently installed.) Preparing to unpack .../linux-image-4.8.0-994-generic_4.8.0-994.201609262201_amd64.deb ... grep: /proc/cpuinfo: No such file or directory This kernel does not support a non-PAE CPU. dpkg: error processing archive /tmp/linux-image-4.8.0-994-generic_4.8.0-994.201609262201_amd64.deb (--install): subprocess new pre-installation script returned error exit status 1 | 13:33 |
| tjaalton | so how do you normally get new kernels there? follow the same procedure.. | 13:33 |
| pxeguy | okay I think I know what to do | 13:33 |
| tjaalton | you'd probably need to bind mount /proc etc | 13:33 |
| pxeguy | I missed the mount | 13:33 |
| pxeguy | ye | 13:33 |
| pxeguy | exactly | 13:33 |
| pxeguy | I missed that | 13:33 |
| pxeguy | sudo chroot /opt/ltsp/i386 mount -t proc proc /proc | 13:35 |
| pxeguy | think that's what I missed | 13:35 |
| pxeguy | mount -t proc proc /proc | 13:36 |
| tjaalton | and? | 17:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!