[00:19] How can I get keyboard working in Xubuntu? [00:41] No1x3r0: do a bios update first of all [00:41] tomreyn already did [00:41] sorry to hear this :-/ [00:42] which hardware is this? [00:42] ASUS ZenBook 14 [00:42] does 20.04 LTS work? [00:42] hadn't tried, can't imagine older working better than newer [00:42] but I can give it a shot if you think it'll help [00:43] latest LTS is always worth a try [00:43] oh wait, I remember I did try it [00:43] cause I accidentally clicked it first since it was at the toop [00:44] so same results [00:44] no keyboard there either? [00:45] I don't remember testing the keyboard on it, all the rest appeared working but had boot errors so moved on, I'm going to redownload and try again [00:45] does the keyboard work on the bios configuration interface, though? [00:49] if you're running ubuntu (not sure about xubuntu) you can also run the "onboard" virtual keyboard from the menu ("dash") [00:49] tomreyn yeah in firmware menus [00:49] there's a chance that this problem may go away after installation. [00:50] not about to take the risk of chancing it [00:50] flashing LTS right now to test [00:51] the errors you got to see on your imgur screenshot are both related to the nvidia graphics card [00:52] oh waitthats wrong, i didn't read properly [00:52] so the first is about the wireless lan chipset, an acpi issue [00:53] then i8042 is about the keyboard most likely [00:53] tomreyn, yeah don't experience those in other distros, so it may be a kernel issue [00:53] nouveau is the open source nvidia driver, which is not too great [00:53] yeah kinda figured [00:57] this etch is taking a while, guess I've worn out this thumb drive with so many tests [00:58] better double check that the data was actually properly written to it then [00:59] tomreyn, getting i8042 error so far [00:59] still booting to test [00:59] tomreyn it does, it does a verification check each time [01:00] half way through progress on booting [01:00] that's not exactly as good as a byte compare, but maybe good enough [01:00] it is a byte compare [01:00] yes, but not for all the bytes ;) [01:01] you could try booting with acpi=off !kernelparm if the wlan + keyboard problems persist. [01:01] or just us a distro that works out of the box [01:01] yeah same difference on 20.04 LTS [01:02] no keyboard [01:02] !kernelparm [01:02] To add a one-time or permanent kernel boot parameter see https://wiki.ubuntu.com/Kernel/KernelBootParameters [01:03] tomreyn, yeah, thanks, I appreciate that, but I'd rather just move on to something that works [01:03] I mean out of 3 releases it not working, don't wanna follow that rabbit [01:04] i doubt the root cause is the linux distro. not only but also because you mentioned there are similar problems with fedora. buti wish you luck either way. [01:04] don't know it's kernel related though cause 21.10 is close to Fedora Beta 25 [01:05] 21.10 is unreleased [01:05] only the XFCE spin of fedora [01:05] the keyboard works fine in the worksation (GNOME) version [01:06] so chances are that default ubuntu would work, too [01:06] yeah, got 21.10 from https://cdimage.ubuntu.com/xubuntu/daily-live/current/ but also the kernel from 21.04 is close [01:06] probably [01:06] !21.10 [01:06] Ubuntu 21.10 (Impish Indri) will be the 35th release of Ubuntu, scheduled for release October 2021 (http://ubottu.com/y/ii). Join #ubuntu+1 for support and questions. [01:06] but I want XFCE [01:07] well this is October 2021 :D [01:07] it's still unrelased, and not supported, though [01:08] * No1x3r0 shrug [01:08] someone asked and suggested it here [01:08] I wouldn't have even bothered with it otherwise [01:08] but either way, none of the 3 editions worked [01:09] past, present, or future :P [01:10] bad / buggy firmware :-/ [01:12] don't think so, again worked with other distros and Windows 10 fine and it's Version 3 update [01:13] no issues with Manjaro, Archcraft, Zorin, Windows 10 [01:14] also if it were a firmware issue wouldn't Fedora 25 beta workstation (GNOME) have errors and issues too? which it doesn't [01:15] i'm sure it does, maybe they were not as obvious [01:15] keyboard works [01:16] and things work in all of those mentioned [01:17] but I will say POP and Mint are both very problematic; with POP not booting at all and Mint having no input control at all [01:37] some light on the situation: https://wiki.archlinux.org/title/ASUS_Zenbook_Q408UG === rud0lf- is now known as rud0lf === gpol2 is now known as gpol === rud01f4 is now known as rud01f === dkessel586 is now known as dkessel58 === TiZ2 is now known as TiZ === keypushe- is now known as keypusher === E_Eickmeyer is now known as Eickmeyer [06:20] Hello to all! Please help me. Where i can find xubuntu-16.04.1-desktop-i386.iso or xubuntu-16.04.1-desktop-i386.iso.torrent? [06:49] xu-irc36w http://cdimage.ubuntu.com/xubuntu/releases/16.04/release/ [06:50] xu-irc36w 32 bit is i386 [06:52] As for my issue earlier, it may be similar to https://x-lore.kernel.org/linux-input/YRZ5a30XOKVjUWDG@fedora/ [07:03] No1x3r0 [07:03] Thank you, but i need xubuntu-16.04.1 - it have old kernel. xubuntu-16.04.6 have new version kernel and not support my old (2004) pentium computer. [07:07] xu-irc36w found a torrent... http://www.pcds.fi/downloads/operatingsystem/ubuntubased/UBUNTU/archive/xubuntu/1604LTS/xubuntu.1604.html [07:10] Thank you, i hope this torrent contain original image of Xubuntu. [07:11] xu-irc36w if not try: https://ia800808.us.archive.org/21/items/linuxtracker.org_p1/xubuntu-16.04.1-desktop-i386.iso [07:13] xu-irc36w found from: https://ia800808.us.archive.org/21/items/linuxtracker.org_p1/ === HoloIRCUser is now known as xu-irc73w [07:17] No1x3r0, thank you! [07:18] xu-irc36w sure no problem, was just a quick google search === Morpheus is now known as Mekaneck === ikwyl6_ is now known as ikwyl6 [14:51] hello. i am having random hangs/freezes when using ubuntu on a 10 year old laptop with atom processor. this issue didnt occur on windows 7. any way to prevent the hangs/freezes? [14:51] i am using the 18.04 xubuntu LTS by the way [14:59] does it become totally unresponsive? [15:00] yes [15:00] only sshing from an android phone works to the laptop [15:00] and it can be rebooted with sudo reboot [15:00] does it happen right after booting up into de? [15:00] is there a way to restart xfwm4 on the laptop from a ssh client/android? [15:00] the freezes are intermittent [15:00] sometimes when opening the browser [15:01] sometimes on just starting [15:01] after a boot [15:01] i didnt figure out the actual cause [15:01] xfwm4 --replace is the command to restart the existing window manager [15:01] its an acer aspire one aod250 with atom processor [15:01] it doesnt start from a remote ssh session [15:01] says that display is not available or something [15:02] does it go away? [15:02] or once freezed, it stays like that for hours? [15:02] it stays permanently [15:03] and eventually ssh server stops working [15:03] and it has to be hard booted [15:03] so i reboot it when this issue occurs [15:03] is it a fresh install? [15:04] yes [15:04] a month ago [15:04] xubuntu 18.04 LTS [15:05] the freeze is intermittent, i havent figured out what is the cause [15:05] you might want to look at the processes [15:05] KBar is there a way to restart the xfwm4 from a terminal ssh session? [15:05] xfwm4 --replace doesnt work [15:05] im not familiar with ssh [15:05] sorry [15:05] gives a message that Display is not available [15:06] and as the GUI freezes i cannot open a terminal and type anything [15:06] so basically it stop [15:06] stops [15:06] but you can have some luck with magic sysrq key [15:06] sysrq? [15:06] any way to open the terminal from a key! [15:06] you dont need the terminal [15:06] wait a few minutes [15:07] the xfce terminal? [15:09] are you familiar with the concept of virtual consoles? [15:11] no. i do connect to it from ssh client though [15:12] i have tried sudo killall xfwm4 and sudo xfwm4 --replace [15:12] the later shows an error display not available or something like this [15:12] does it have the prtsc key? [15:12] hm it does [15:13] is it running rn? [15:13] pressed it, nothing is happening [15:13] Btw, Xubuntu 18.04 is end-of-life since April this year and therefor not supported anymore (3 years vs 5 years for Ubuntu main). [15:13] dont press it just yet [15:14] is your laptop running? [15:14] hm. but a newer build will be more resource intensive when the laptop doesnt even run properly on an older build [15:14] now it is running okay [15:14] but freezes are intermittent [15:14] xubuntu is not resource intensive [15:14] anyway [15:14] and when it freezes it stops working [15:14] open the terminal [15:14] GUI becomes unusable [15:14] right now [15:14] hm its opening now [15:15] try sudo showkey [15:15] top shows 8.7 usage [15:15] enter your password [15:15] cpu [15:15] kb mode was ?UNKNOWN? [15:16] do as i say please [15:16] once again [15:16] run sudo showkey [15:16] when when "press any key" appears [15:17] press the prtsc button [15:17] it will show you the code of the button you just pressed [15:17] press only prtsc [15:17] no other button [15:17] ok [15:17] after 10 seconds [15:17] the program stops itself [15:18] but we need to know the code of prtsc for your laptop [15:18] keyboard [15:18] its saying 99 press [15:18] 99 release [15:18] awesome [15:18] something like this [15:19] means it can function as the sysrq key as well [15:19] ok [15:19] you can use the following technique to try to unfreeze the desktop [15:19] so when it freezes will pressing prntscreen bring the terminal? [15:19] no [15:19] dont get aheed of youself :) [15:19] ahead [15:20] it apparently brings the xfcer4-screenshooter :P [15:20] as it should [15:20] hm [15:20] i will teach you a useful magic trick. would you let me please? [15:20] sure, thanks a lot [15:20] great [15:20] 1 minute [15:20] i want the terminal to open when it freezes [15:21] so that it can be used [15:21] did the showkey program stop? [15:21] stopped now [15:21] did the shell return to the prompt? [15:21] yes it has [15:21] less /proc/sys/kernel/sysrq [15:21] can you teach me to program it to bring the terminal [15:21] whats the number [15:22] you see [15:22] 176 [15:22] is it a single-user system? [15:22] yes [15:23] nobody else can access it right? [15:23] yes, only the user ubuntu [15:23] we need to turn this 176 to 1, but it's a bit unsafe [15:23] no, i mean, is there someone else who can access the computer? [15:23] physically [15:24] no [15:24] great [15:24] this is what we're trying to do: https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html [15:24] there is nothing that useful in the laptop, i am trying to make it stop freeze :P [15:25] https://en.wikipedia.org/wiki/Magic_SysRq_key [15:25] well, i dont know about stopping the freezes [15:25] but ill teach you oom-kill or safely reboot from a dead, unresponsive system [15:25] oom = out of memory [15:25] thats why they call it magic [15:26] hm i got it [15:27] so if 99 is the printscreen key [15:27] now [15:27] if i put 99 in this file, making alt+printscreen will bring the terminal? [15:27] :P [15:27] something like this, i guess? [15:27] no [15:27] ! [15:27] hehe [15:27] please. just follow my steps [15:27] sure [15:27] please proceed [15:28] what's the content of /etc/sysctl.d/10-magic-sysrq.conf [15:28] ? [15:28] specifically last line [15:28] the value of kernel.sysrq = 1? [15:28] oops [15:28] is it 176 as well? [15:28] its 176 [15:28] hm [15:29] i assume you don't know how to edit system config files? [15:29] i can edit them with mousepad /vi [15:30] you'll need superuser privileges to edit this 10-magic-sysrq.conf file [15:30] i have sudo [15:30] kernel.sysreq=176 [15:31] i have opened it with mousepad [15:31] it's very unsafe to do it this way, but for this occasion, i think its fine [15:31] just dont make it into a habit [15:31] turn the 176 into 1 [15:31] it has to be [15:31] kernel.sysrq = 1 [15:31] and what else? [15:31] nothing else [15:32] 256? [15:32] just this specific line and value [15:32] no [15:32] it has to be 1 [15:32] :ok [15:32] it gives a list of possible numbers [15:32] 128 is allow reboot [15:32] hm [15:32] all functions enabled with 1 [15:33] how do i access the terminal with alt+printscreen [15:33] please teach me [15:33] did you edit the file? [15:33] yes saved [15:33] did you change the value from 176 to 1? [15:33] yes saved it [15:34] should i reboot now? [15:34] reboot it and then see the content of /proc/sys/kernel/sysrq [15:34] yes [15:34] and what will be command to bring the terminal [15:34] /proc/sys/kernel/sysrq should show 1 now [15:34] may i know? [15:35] reboot, read that file again and come back [16:22] well, i guess they will have to learn the magic trick from some other wizard [20:17] Test