I'm not sure what I'm working with.
My Intel powered gigabyte laptop has had a history of locking up with an half minute delay before shutdown.
A failed upgrade to the new stable branch triggered a fresh install and I thought it would cure my problems as well, but it's the same.
Somehow I have just ignored this, but now it also started refuse to connect to the Wi-Fi so it's time to spend a few hours to sort out this problems.
Where do I start? I honestly got no idea. Please?
Stian1979 wrote:
Where do I start?
First, enable persistent logging for systemd's journal:
Thanks. Been looking for a way to log this event, but seams I been searching for the wrong keywords. Thought getting the wireless back up would be a easy, but turned out to be quite a problem. Removed the network manager since I thought it might conflict with wicd, but no change.
The card is RTL8723BE and has been working even I needed some reboots in order to find the wireless at times.
02:00.0 network controller: realtek semiconductor Co., Ltd. Etc8723be pcie wireless network adapter.
Kan see the kernel modules are in use by lspci -K
Wheelerof4te wrote:
Did you install firmware-realtek? Debian separates non-free firmware from the kernel.
It's been working the whole time until yesterday. I accepted to enable nonfree at install. Have not run a update of the kernel either. And the wired connection is not working either.
02:00.0 network controller: realtek semiconductor Co., Ltd. Etc8723be pcie wireless network adapter.
Kan see the kernel modules are in use by lspci -K
Well, letter case (capitol or lowercase) makes a difference.
When you first used the grep command your interface wasn't found because you looked for a lowercase word but it is listed as uppercase(capitol) word. I suggested the argument(switch), -i because then grep returns either word, ignoring letter case.
Then you wrote that lspci -K returned something when it would have told you that -K was an invalid option because, -k lowercase is what identifies kernel drivers in use.
Is your keybord working correctly?
Well, letter case (capitol or lowercase) makes a difference.
When you first used the grep command your interface wasn't found because you looked for a lowercase word but it is listed as uppercase(capitol) word. I suggested the argument(switch), -i because then grep returns either word, ignoring letter case.
Then you wrote that lspci -K returned something when it would have told you that -K was an invalid option because, -k lowercase is what identifies kernel drivers in use.
Is your keybord working correctly?
It's working like it should. The computer is not so posting go trough a HTC that corrects everything I type in its own liking.
I'm sorry, I can't try to help you any further because I can't understand what you are trying to say, I only see bits and pieces that I understand.
You mentioned that you removed Network Manager and if it is what was managing the network, that might be why there isn't a network any longer.
All I can suggest is to follow the procedure in the Debian Wiki for the wireless you identified, RTL8723BE.
https://wiki.debian.org/rtl819x#rtl8723be
Maybe someone else will see this and have further ideas, if not maybe there is a local Linux User Group where you could get help in person.
https://www.tldp.org/HOWTO/User-Group-HOWTO-3.html
When the kernel initialize I get.
ffff8908bf0c26f0) AE_NO_MEMORY (20160831/psparse-543) [ 1.464064] r8169 0000:01:00.2 (unnamed net_device) (initialized): rtl_chip cmd_cond == 1 (loop: 100, delay: 100).
[ 1.479828] r8169 0000:01:00.2 etc0........
Downloaded the latest kernel and firmware.
And improvements are zero.
Blacklisted the kernels driver and got rid of the messages at kernel initialization.
Tried to modprobe modules, but command won't work.
Been downloading all files by Android and transferred with USB so still no wireless and no cable witch was both working just a week ago.
What can I show to get help? I will just need to get the outputs in a text document from the laptop and into the phone to get it posted.
Output from all I can think off.
A fresh install never fixed the problem and new versions of debian did not either.
Not been using this laptop again for a while, but decided to try to get to the root of this problem.
two versions seams to always be at the end of the kernel log when this shutdowns appear.
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: Machine check events logged
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 2: d4200004000d110a
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: TSC 0 ADDR 983d8ec0
aug. 18 22:43:16 debian kernel: mce: [Hardware Error]: PROCESSOR 0:30678 TIME 1660855396 SOCKET 0 APIC 0 microcode 815
What you're looking at is a hardware problem. Your CPU is not pleased, and assuming you're not oveclocking or undervolting it prime suspects would be memory, power, or cooling.
What you're looking at is a hardware problem. Your CPU is not pleased, and assuming you're not oveclocking or undervolting it prime suspects would be memory, power, or cooling.
I would instantly reject cooling since I can instantly turn it back on en run it for anything between 2 hours and 2minuntes. There is no consistency about what it will happen.
The OS will freeze and will reboot after about 30sec, but sometimes shut down directly.
When you say memory do you mean RAM or do you mean memory at the CPU/GPU?
