• 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle
  • I mean general advice with potential hardware issues is remove as much hardware as possible, and see if the problem still exists. If it does, swap components one-by-one until you find the faulty component.

    Since this seems to a sporadic problem, it would probably help to try find a way to trigger the problem more reliably. Maybe write a script that writes random files constantly, or something like that.


  • Very weird, I can think of some things I might check:

    • It is possible that you have files on disk that don’t have a filename anymore. This can happen when a file gets deleted while it is still opened by some process. Only the filename is gone then, but the file still exist until that process gets killed. If this were the problem, it would go away if you rebooted, since that kills all processes.

    • Maybe it is file system corruption. Try running fsck.

    • Maybe the files are impossible to see for baobab. Like if you had gigs of stuff under (say) /home on you root fs, then mount another partition as /home over that, those files would be hidden behind the mount point. Try booting into a live usb and checking your disk usage from there, when nothing is mounted except root.

    • If you have lots and lots of tiny files, that can in theory use up a lot more disk space than the combined size of the files would, because on a lot file systems, small files always use up some minimum amount of space, and each file also has some metadata. This would show up as some discrepancy between du and df output. For me, df --inodes / shows ~300000 used, or about 10% of total. Each file, directory, symlink etc. should require one inode, I think.

    • I have never heard of baobab, maybe that program is buggy or has some caveats. Does du -shx / give the same results?


  • I’m still skeptical. At the time of the original Pentium (the last 586 from Intel, the fastest of which was 300 MHz), the usual amount of RAM was something like 16 or 32 MB. A 586 with 1 GB of RAM is extremely weird and probably impossible unless it’s some sort of high-end server. This does not check out.

    Oh and DDR is also from around the time of the Pentium 4. I don’t think there exists a machine that has both DDR and an original Pentium (aka 586). Again, this does not check out and is probably impossible.

    There could be another reason it won’t boot.



  • I have never used the Steam beta or Proton-GE or whatever information is spreading out there to noobs about what they should do, and I’ve been gaming exclusively on Linux for more than 20 years. Only do this beta or bleeding edge stuff if you have a problem, and a good reason to believe that will help (like people reporting your specific issue is fixed in beta). Or I guess if you’re bored out of your mind. And expect other issues since it’s fucking beta.








  • Better acceleration, steeper inclines, tighter curves at same speed, better ride quality and less wear. As someone has mentioned below, normal trains could go a lot faster than they do in practice, because the ride quality, wear and wind resistance get atrocious, and the tracks need to be exceptionally straight. Making a maglev go fast is more feasible, though you still have the wind resistance issue obviously.