| rrq | is your RAM broken? | 00:00 |
|---|---|---|
| coyotes4ys_ | back hello this is my only system and it's crashing over and over. can someone pls help me? | 00:02 |
| rrq | .. problem at that level tends to be hardware related; and first option is always mechanical | 00:02 |
| coyotes4ys_ | i've been using this setup for months | 00:02 |
| coyotes4ys_ | why now? i didn't change anything | 00:02 |
| coyotes4ys_ | is there a log i can check that you are able to figure out anything from? | 00:03 |
| rrq | temperature? | 00:03 |
| coyotes4ys_ | could it be from stray current going where it shouldn't? | 00:03 |
| rrq | do the fans work? | 00:04 |
| coyotes4ys_ | cat /sys/class/thermal/thermal_zone*/temp is showing all kinds of numbers | 00:05 |
| coyotes4ys_ | 39000 | 00:05 |
| coyotes4ys_ | 20000 | 00:05 |
| coyotes4ys_ | 50 | 00:05 |
| coyotes4ys_ | 35050 | 00:05 |
| coyotes4ys_ | 35050 | 00:05 |
| coyotes4ys_ | 38000 | 00:05 |
| coyotes4ys_ | 40000 | 00:05 |
| coyotes4ys_ | 34000 | 00:05 |
| coyotes4ys_ | 39000 | 00:05 |
| rrq | do "more /sys/class/thermal/thermal_zone*/* | cat" instead so you can associate numbers with "file" | 00:06 |
| coyotes4ys_ | massive response | 00:08 |
| coyotes4ys_ | https://hastebin.skyra.pw/kakahuqomo.bash | 00:08 |
| coyotes4ys_ | honestly rrq, i have never felt or heard the fan working in two to three months of use. haven't gamed really, have watched videos | 00:11 |
| coyotes4ys | rrq, i'm back | 00:13 |
| rrq | yes. almost definitly hardware. | 00:13 |
| cos1 | coyotes4ys: i'd strongly suggest you get a second computer. a used laptop should be affordable, assuming you're not in the subsaharan economy. | 00:13 |
| coyotes4ys | the system isn't hot to the touch. minimal warmth as usual | 00:13 |
| coyotes4ys | rrq what makes u think that? | 00:14 |
| coyotes4ys | clue me in? | 00:14 |
| rrq | unplug all usb things | 00:14 |
| rrq | it's a laptop I guess .. unplug AC | 00:15 |
| coyotes4ys | i had a thumb drive in, unplugged it along with headphones and AC | 00:15 |
| rrq | is it more stable now? | 00:15 |
| coyotes4ys | it usually takes a few minutes, just rebooted | 00:16 |
| coyotes4ys | still here | 00:16 |
| coyotes4ys | waiting | 00:16 |
| rrq | rigth. watch some short vide or do something fun while waiting :) | 00:17 |
| coyotes4ys | lol | 00:17 |
| |cos| | coyotes4ys: did you run memtest86? | 00:18 |
| coyotes4ys | no |cos| should i install it. i can't remember how i did a mem check before i know i did though | 00:19 |
| rrq | if it stays good significantly longer then the problem is due to one of those things you unplugged | 00:20 |
| |cos| | coyotes4ys: no, you boot straigt into it without any operating system. from a thumb-drive, the network or however you prefer. | 00:20 |
| |cos| | coyotes4ys: https://memtest.org/ | 00:21 |
| rrq | might also be the associated connector | 00:21 |
| coyotes4ys_ | rrq back. that wasn't much longer if at all | 00:23 |
| coyotes4ys_ | |cos|, i got your message. ok i may do that, but is it a boot stick? | 00:23 |
| |cos| | coyotes4ys_: booting it off a usb stick is possible yes. let it run for a while. if the screen turns red your memory is faulty. | 00:25 |
| coyotes4ys_ | ok |cos| | 00:27 |
| coyotes4ys_ | is it free software? | 00:27 |
| |cos| | ya. gpl. | 00:27 |
| coyotes4ys_ | good ok | 00:27 |
| |cos| | it's been reliable in detecting faulty memory whenever i've had them. | 00:28 |
| |cos| | unfortunately i'm unaware of good ways to stress test other components. | 00:29 |
| coyotes4ys_ | ugg i have to use wine? | 00:36 |
| Xenguy | coyotes4ys_, For what? | 00:36 |
| coyotes4ys_ | oh wait no. it's the memtest86-usb.img | 00:36 |
| coyotes4ys_ | it's this memtest86 that |cos| is recommending | 00:36 |
| Xenguy | Right, I think that will either install to a USB key, or (in my case) to the GRUB menu | 00:37 |
| coyotes4ys_ | wow how do i install to grub? | 00:38 |
| |cos| | 00:21 |cos| | coyotes4ys: https://memtest.org/ | 00:38 |
| |cos| | anyways. it's getting way too late for me now. off to bed, i am. | 00:39 |
| coyotes4ys_ | gnight thank you |cos| !! | 00:39 |
| Xenguy | coyotes4ys_, I think it was maybe the default option offered by apt-get | 00:40 |
| Xenguy | Was awhile ago so can't recall exactly | 00:40 |
| coyotes4ys_ | memtest is on apt? | 00:40 |
| coyotes4ys_ | or only if i add repo | 00:40 |
| rrq | there's memtest86+ | 00:41 |
| Xenguy | coyotes4ys_, https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=memtest*&x=submit | 00:41 |
| Xenguy | rrq, I take it that's recommended over regular 'memtest' | 00:42 |
| coyotes4ys_ | it was already in my repos! memtest86+ | 00:42 |
| coyotes4ys_ | how cool! apt can do stuff to grub? how nice | 00:42 |
| Xenguy | Yeah, that's what I installed | 00:42 |
| coyotes4ys_ | rebooting cya all soon i HOPE | 00:43 |
| Xenguy | good luck | 00:43 |
| rrq | yeah looking to version codes it looks like a progression: memtest86 -> memtester -> memtest86+ | 00:44 |
| rrq | perhaps a series of different maintainers | 00:45 |
| Xenguy | On beowulf, dpkg only offers a version for memtest86+ | 00:45 |
| Xenguy | dpkg -l | 00:45 |
| rrq | use "apt-cache search memtest" instead | 00:46 |
| Xenguy | That output lists no version numbers at all though | 00:47 |
| rrq | "dpkg -l" only knows about current and previous installs | 00:47 |
| rrq | ok "apt-cache policy memtest\*" | 00:48 |
| Xenguy | Aha, that did the trick | 00:48 |
| coyotes4ys | |cos|, i got a pass banner, then it (repeated using 4 cores instead of 1?) | 01:08 |
| coyotes4ys | Xenguy, rrq, so that ^ happened, now i'm back in and feeling stabler even though i have no particular reason to | 01:10 |
| coyotes4ys | i plugged in the AC adapter and i guess i'll test it that way for a little while, then headphones... | 01:10 |
| coyotes4ys | sorry i jumped to a software problem, but because crowz is called "linux" not "gnu/linux" i tend to go there for the problems. if people don't care as much about software freedom, then they choose the software for the distro, then i choose that distro...i only chose it for a short time til i can find a LAN card compatible with Free Software (firmware in this case) | 01:12 |
| coyotes4ys | (the part after the ellipsis ... is a new thought) | 01:12 |
| coyotes4ys | ok rrq Xenguy did you get any of that | 01:25 |
| rrq | you might want to re-seat the memory card(s) .. especially if you've added RAM expansion(s) | 01:27 |
| coyotes4ys | rrq, Xenguy thanks. i won't call u anymore. feel free to type at me if i manage to be uptime for long enough and you want to | 01:32 |
| gnarface | someone tell coyotes4ys to try the devuan live iso | 03:46 |
| bob123 | Hi all . I would be grateful for help or advice. This error breaks Devuan, the system becomes uncontrollable, the cursor moves randomly, the pages themselves close, etc. | 10:23 |
| bob123 | This error occurs on qemu-devuan. Local machine -Devuan, virtual machine -Devuan | 10:23 |
| bob123 | This is the error | 10:23 |
| bob123 | kernel: [362.059103] psmouse serio1: VMMouse at isa0060/serio1/input0 lost sync at byte 1 | 10:23 |
| bob123 | 2024-01-29T11:06:02.376836-05:00 bob123 kernel: [ 362.059948] psmouse serio1: VMMouse at isa0060/serio1/input0 - driver resynced | 10:23 |
| Joril | bob123: the problem occurs INSIDE the VM but not on the host machine? | 11:13 |
| * _jay_ thinks: mice are overrated anyway :P | 12:08 | |
| buZz | i dont think those two lines are actual errors | 14:32 |
| buZz | but why use a PS/2 mouse inside qemu? why not just usb | 14:33 |
| buZz | or 'no mouse at all' and just use barrier or x2x or synergy or ... | 14:33 |
| onefang | "-usb -device virtio-tablet" works for me as a qemu mouse. | 14:39 |
| gnarface | maybe the host user isn't in the input group? | 14:43 |
| onefang | Oh and bob123 left 40 minutes ago. | 14:45 |
| buZz | ah, great | 14:52 |
| nemo | rwp: BTW, the CIFS crasher I was hitting was resolved by switching to the daedalus-backports 6.5 kernel | 15:19 |
| nemo | hopefully that doesn't have other repercussions :) | 15:20 |
| raub | I have two monitors connected to my devuan desktop. According to xrandr, the monitor on the right is the primary, but the menu bars are all on the left screen. | 17:18 |
| gnarface | just move that one to the other side :) | 17:19 |
| gnarface | uh, nevermind that. window managers all have their own different controls for setting the primary | 17:20 |
| raub | Yeah. I first try setting it up in lxqt(?) and it cheerfully ignored me. Then I switched to xfce and the same happened | 17:20 |
| gnarface | well, in theory you can change it with xrandr directly, but xfce should have some control panel for it... | 17:35 |
| gnarface | at least changing the positions should be possible with xrandr | 17:36 |
| gnarface | changing which one the desktop actually sees as primary might be more difficult if the desktop itself doesn't provide an option for that, unless you're using the nvidia proprietary drivers, which can force it with a interface in nvidia-settings | 17:37 |
| n4dir | truth to be told: i am not really disappointed if the bass is only the base note and only on 1 and 3 | 17:50 |
| n4dir | wrong channel. lol | 17:51 |
| raub | gnarface: yeah, I have used xrandr before to set the monitor layout in the computer that this one is replacing. I was not able to force it ehre | 18:01 |
| raub | With that said, someone in #debian showed me which control panel Ineeded to be to set the menus (in xfce). It seems they were setup to "automatic" instead of "primary" | 18:02 |
| raub | Now all is well | 18:03 |
| rwp | gnarface, It's a repeating theme that primary and secondary numbering will be opposite for every different thing that chooses. My display outputs are numbered 1 and 2 and X numbers them the opposite. | 19:02 |
| rwp | nemo, The theory goes that libc is the software interface between programs and the kernel, and the kernel is the interface between libc and the hardware. So in theory the choice of kernel should not matter as long as it has working drivers for all of the hardware. Beyond that it is all fluff and glitter. | 19:03 |
| coyotes4ys | ok, for any who saw me in here yesterday blaming OS, forgive me, and don't pack your laptop too tightly if it's an asus ux433fa | 19:18 |
| coyotes4ys | connections were made that shouldn'ta | 19:18 |
| coyotes4ys | current running where it daint | 19:18 |
| rwp | coyotes4ys, You removed the RAM DIMMs and then inserted them again and things improved? Is that what I am reading? | 19:28 |
| coyotes4ys | no i let it sit then didn't pack it tightly in my bag. literal packing. | 19:29 |
| rwp | I am sorry but I don't understand. But I see that gnarface above after you left the channel wanted someone to suggest to you to try a live-boot iso as that would test without the currently installed system. | 19:35 |
| coyotes4ys | ok, laptop bought used two months ago. no crashing until yesterday, crashed several times within one hour. prior symptom of detectable current flowing through chassis when AC plugged in. | 19:37 |
| coyotes4ys | removed AC yesterday and no more crashing. plug back in, crash after a few minutes. | 19:37 |
| coyotes4ys | but before that, i was in here and someone suggested memtest86+. used it, it worked perfectly, even after plugging ac adapter back in. however it should be noted that memtest86+ is a massively less complex OS than any complete OS. | 19:39 |
| coyotes4ys | today, made sure to pack less tightly. ac adapter has been in and no crashes for an hour or two. | 19:39 |
| rwp | Two things I read. You could notice AC current flowing through the chassis? The AC charge plug is shorting? That's a danger! That must be fixed. And I can't imagine who that could happen. | 19:41 |
| coyotes4ys | it's quite obviously related to the squishing of the laptop | 19:42 |
| rwp | And packing and crashing... You are running your laptop under AC power charging it while it is packed into your bag? The concern I have there is heat. It will get hot. It will overheat. Which is also a fire danger. | 19:42 |
| coyotes4ys | not necessarily the charge port, issue could be anywhere that current is only flowing when charger is plugged in. | 19:43 |
| coyotes4ys | no not charging while in bag. but if metal is squished in bag it retains some of that shape for awhile, even after pulling out of bag. | 19:43 |
| rwp | I suspend-to-ram my laptop when I put it into my backpack. Then wake it up when I pull it out of the bag. If I forget to suspend it but stow it then I find it extremely hot after only a short time pull it out of the bag. | 19:43 |
| coyotes4ys | i mean, it could be something else but packing the bag differently worked so far. | 19:44 |
| rwp | If things are working for you then who am I to disagree? Also I am not there to observe it first hand. But the description and my experience makes me skeptical. | 19:45 |
| coyotes4ys | yeah i haven't even been suspending becausse crowz OS isn't my final OS, just trying it out until i can get a wifi usb adapter that doesn't require nonfree firmware. | 19:45 |
| coyotes4ys | yeah it's not heat. it's never hot really. it's an amazing lappie | 19:45 |
| rwp | Being able to suspend-to-ram and resume from suspend is one of the tests for a laptop because it so often fails. Yet I consider it a required feature. | 19:45 |
| coyotes4ys | except for everything is soldered except M.2 and LAN card is proprietary firmwared | 19:46 |
| coyotes4ys | suspend always works when i tell it to, sometimes doesn't work when i use power manager to make it suspend when lid is closed. | 19:47 |
| rwp | Proprietary drivers needed for WiFi (Broadcom!) is often a problem. Firmware blobs are not a problem. If you have decided to use the hardware then just load the blobs. But free drivers are critically important. | 19:47 |
| rwp | I avoid hardware that does not have free software drivers. | 19:48 |
| coyotes4ys | nonfree blobs mean i can't see what my own computer is doing | 19:48 |
| * coyotes4ys makes "X" shape with arms | 19:48 | |
| rwp | We can discuss the philosophical nature of blobs in -offtopic and keep this channel available for support help. | 19:49 |
| coyotes4ys | i'm busy right now but i'll go to offtop | 19:49 |
| rwp | I need to $WORK too. | 19:50 |
| coyotes4ys | thanks for the thoughts rwp | 19:50 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!