[SOLVED] MX Often Hanging at Boot on SysV...

[Snake420]

Just a thought.
Did you use the Windows 7 tool to resize your Windows partition, or gparted?
I've seen a variety of issues with ntfs partitions shrunk with gparted. It's not common for one to work properly in Windows & error in Linux afterwards but that "invalid offset" along with the other report with the ipmi:dmi error linked to an ntfs partition that needed a chkdsk in Windows makes me wonder.

If you did use gparted on the ntfs partition then you could shrink it a minimal amount with the Windows tool and see if that corrects the problem.

I shrunk down the Windows 7 partition (sda3) with the Windows tool, to as small as it would shrink the Windows partition, to create the empty partition for Linux.
After that, I then installed MX 18.3 (via usb flash) onto that partition, using GParted on the install to create the EXT4 and Swap partitions to install, pointing everything to root and Grub to pick up Windows to add to Grub on the sda partition.

[Huckleberry Finn]

And, as you already know, you can use Cclean for the empty space at least (and Bleachbit on Linux partition).. In fact, I know that I encountered that offset error before, but can't remember, myself? or where? .. But it can really be about that shrinking, although Win. works with no issues..

[Huckleberry Finn]

It's also a good idea to run chkdsk inside Win. nothing to lose and easy. (Although after shrinking it must've done that...)

[Snake420]

I think what I may do is split my current MX Linux partition (taking Huckleberry's idea) and install MX into that newly created, cleaned and checked partition, but hold on to my current MX partition, thus having a Triple Boot, while I setup and check that new MX install for that ipmi:dmi: invalid offset: 0 error. This way, if I still have the same issue, then nothing is lost, and I can then just basically retake that partition from the new install to the current MX if the error is there as well, at least until I hopefully can find what the true problem is, if it exists there as well.

If I could just axe Windows all together, I would be happy, but unfortunately there are some paid for Windows programs that I need, and no alternative on Linux to replace them, and Wine is worthless to me.

If anyone comes across a fix or brilliant idea, before I do all of this, please do post so that I can give all a shot before moving ahead on this project.

Again, thank you all for all of your help ! It's greatly appreciated. This forum is fantastic !

I really want for MX to work out for me...long term.

[Huckleberry Finn]

My Goodness !

It may be kernel related. And I think I remember now where I encountered it before: the 4.13 kernel, both I tried with Mint and *buntus with original 4.13 that time..

And now there are complaints about 4.19 (and 4.13 before, about the same issue)

Though the forum is in Russian https://debianforum.ru/index.php?topic=14670.0

When loading on the 4.19 kernel (Buster) pops up: ipmi: dmi: invalid offset: 0. The numbers in square brackets are new each time. The problem is not in the distribution, namely in the kernel. At 4.9. there is no such problem. Tried a lot of distributions with the kernel 4.19 all have the same error. There is very little information in the net, and then basically just some questions, no answers.
If anyone encountered may have a solution to this problem?

After what started the problems?

I now use Debian 9.8., MX-Linux 18 (based on Debian 9, but the kernel is 4.19 installed) and Debian 10. On Debian 9.8., Where the kernel is 4.9. This entry does not pop up at boot time, but where the 4.19 kernel is installed, it appears. This applies to all distributions with kernel 4.19., Which I tried (Kubuntu, KDE Neon, Ubuntu, Xubuntu, Linux Mint).
This is manifested even when using the LIVE mode. At work, it seems to cause no problems. At least, which climbs obviously, was not.
And by the way, when booting MX-Linux with kernel 4.9. such an inscription does not appear

Meanwhile, this is also about Dell:

Kernel 4.19, as I understand it, is stable. The problem manifests itself only on my particular machine. On the other not. Hike the kernel considers my Dell server. And therefore such problems

And a few more sites showing it may be kernel-related...

[Huckleberry Finn]

Again, Dell and kernel: https://bugs.launchpad.net/ubuntu/+sour ... ug/1773526

Bug Description

Linux 4.16.12-041612-generic ...
DELL INSPIRION 5547 i5-4210u
...
any one can help?
at boot on all distributives and on all lasts kernels i see this two errors

1)ipmi:dmi: invalid offset 0(im not have any ipmi interface and installed software)

summary: - kernel bug

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-kernel-headers (Ubuntu):
status: New → Confirmed

status: Confirmed → Fix Released

status: Fix Released → Confirmed

[Huckleberry Finn]

So,

You can install and try kernels with an easy GUI:

(Since the highest one in the Stable Repo is 5.1.xx currently)

Menu=> MX Tools => MX Package Installer => Stable repo from tabs above and type in the search box -5.1.11

Linux-headers-5.1.11....
Linux-image-5.1.11...

Check both and install that kernel, reboot. (It'll automatically start with it as it'll be the highest one installed)

and if that doesn't work try especially 4.9.182 (the same way) and start the pc with that kernel (advanced options in Grub)
________________________________________________

And please let us know in a few days, how it's going on :)

[Snake420]

So,

You can install and try kernels with an easy GUI:

(Since the highest one in the Stable Repo is 5.1.xx currently)

Menu=> MX Tools => MX Package Installer => Stable repo from tabs above and type in the search box -5.1.11

Linux-headers-5.1.11....
Linux-image-5.1.11...

Check both and install that kernel, reboot. (It'll automatically start with it as it'll be the highest one installed)

and if that doesn't work try especially 4.9.182 (the same way) and start the pc with that kernel (advanced options in Grub)
________________________________________________

And please let us know in a few days, how it's going on :)

Thanks Huckleberry !

I noticed that also, when I was searching for an answer, that it seemed like what little conversations that there were about this issue, they were talking about kernels and/or servers, or some other odd thing that didn't seem to relate to me, but like you noticed, there was little information as far as an answer was concerned, and conversations didn't seem to apply to my situation.

What irritates me is that everything on MX runs fantastic...No Issues...all but this one odd error that leaves me hung up at boot about every sixth boot.
If it wasn't for that, I'd be ecstatic !

I'll try out some kernels, starting with 5.1.11, and if not I'll try 4.9.182, and come back here in a couple days with some info.

Thanks for all of the great help !

[Huckleberry Finn]

You''re welcome.

And in case this topic (hopefully) gets marked as "solved" we can write a reply post to the previous one with no answer, and link here so that people searching should find an answer in the future..

And, as I mentioned, I recognized that issue, the moment I saw it but couln't remind where and what was the solution.

Three interesting common points about all :

1- Kernels can cause problems on some pcs, although they're the official ones provided by the distribution iso. In my case, I had trouble only with all *buntus (17.10 artful) with 4.13 originally. And also I was using Ukuu on Mint and trying the newest kernels with no problems until I tried 4.13 .. Only with that..

2- Strangely, the brand is Dell on all similar cases. And also there's a Qualcomm Atheros wireless (built-in device issue with Dell again which is known to be unsolved everywhere, so far.. (Like this: viewtopic.php?f=108&p=516688#p516688 )

3- The most weird one: In both cases above, everything may work flawlessly on live-session, but when it's installed problems begin to occur. Though they're the same kernels, same firmware/drivers and same devices.. The difference is one is a squashed file system..

As the last thing, no matter it works or not, I'd humbly suggest to install on a small partition, it has the advantages of easy & quick backup / scan / dd zero before installation etc.. You can save big files in other partitions (therefore be in peace of mind, should the system gets screwed) and also can keep it small especially using Bleachbit (like CCleaner). (As mentioned, mine is only 4.7 GB on a 8GB partition - it was even 3.5 when removed libreoffice & gimp and icon themes I don't use..)

Waiting for the good news

[Snake420]

Just a little status update, but I'm going to continue with testing...

So far, it seems the antix kernel 4.9.182 is working well with my Dell computer, with no error text showing at all.

I tried out a few kernels, just for testing purposes, including the 5.1.11, but found that any of the 5+ kernels all show errors in the install, using MX Package Installer, but for some reason still install despite those errors. Needless to say, all of those kernels cause me freezes on boot up on my computer between splash and login screens.

Another thing I found is that the kernels that I have tested so far... 4.13, 4.14, 4.15 and 4.19 all show different variations of the ipmi:dmi: Invalid offset: error when booting up, and in most cases hang up on boot up just after the boot splash and before the login screen on a black screen, sometimes with the error showing, but most times just with a still cursor. It seems to me that these kernels want to connect to a non-existent ipmi, but that's my take as I'm not even remotely close to a dev or anything like that...just a user.

Like I said, I'll keep testing and post here the results after some time.

One quick question, if I may...
Is there any way at all to stop or disable the login screen from boot up, and only use it during logouts ?
That way I boot into my desktop directly from the boot splash screen, bypassing the login screen all together.
I have a funny feeling that the short delay between my splash screen and the login screen, which in my case is set as autologin, may also be causing some of the hanging at that space on my boot ups.

Please let me know if you can.

Thanks again.