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