MX Linux Forum

Currently am running Mepis 11 64bit on a new (6mths in service) Gigabyte GA-H81M-S2H motherboard with Nvidia GeForce GT 610 card. No problems apparent and no bios setting required when the hd from an older machine was put in. It all cranked up straight away.

I have tinkered with the install of MX15 32bit on an older machine installed it from Live Disk onto a reformated hard drive and had no problems. Everything has worked perfectly.

My next step has been to download the MX15-x64_KDE_added-May_2016 iso and this is successfully burned to a DVD

When booting from the DVD however the loading gets to "...waiting for dev to be fully populated... " and then hangs.

Regards
Peter

Wrong forum, will move.

Apologies

Not a huge problem, but we try to keep KDE MX in its own place since it is not an official release and we don't want people to think that problems with that mean that MX-15 is faulty.

Do any of the cheatcodes available in the boot menu screen help? See the menu at the bottom.

Cheat codes will not help. It should continue the boot process if you wait a full minute.

This problem is usually due to a bug in the udev program. If it does complete the boot after you wait a minute then the output of the dmesg program may contain useful clues. The usual fix is to use a different version of udev. Sometimes a different kernel can help. This long delay when udev runs is a well known problem. It is very frustrating. The most charitable thing I can say is that the priorities of the udev/systemd devs are vastly different from my own.

Jerry3904 wrote:Not a huge problem, but we try to keep KDE MX in its own place since it is not an official release and we don't want people to think that problems with that mean that MX-15 is faulty.

I'm quite happy with the 32bit MX15 installation I did on the other machine and had run it for over a month. So when I noted there was a 64bit KDE opted for it as a probable replacement for Mepis 11 as an outright replacement for my Mepis 64bit on my work machine. I didnt realise the KDE may have hiccups but Ill persevere a while on a separate drive and retain my M11 meantime. Perhaps I should be safer with a MX15 64bit without KDE. Ill have to ponder on that a while ;-)

Regards
Peter

It should be noted that udev is not a part of KDE. And that there are several on this forum that use KDE on MX-15 as their primary DE without problems.

lucky9 wrote:It should be noted that udev is not a part of KDE. And that there are several on this forum that use KDE on MX-15 as their primary DE without problems.

I do not think I have have the capability to eliminate KDE from the Live disk composition that I downloaded (if that is at all possible) So do I assume that I should download the live disk image for MX15. install it, remove udev, then install KDE

Regards

Reread what BitJam posted. I do not think you understood what was being said.

I would first try installing MX-15 as it comes. Add KDE through the MX Package Manager. Then install the debian fall-back kernel. Boot the backup kernel. Then see if things straightened out. If they did then I'd use GRUB Customizer to make the backup kernel the default kernel.

lucky9 wrote:Reread what BitJam posted. I do not think you understood what was being said.

I would first try installing MX-15 as it comes. Add KDE through the MX Package Manager. Then install the debian fall-back kernel. Boot the backup kernel. Then see if things straightened out. If they did then I'd use GRUB Customizer to make the backup kernel the default kernel.

Thanks will do ;-)
Regards

My twopenceworth:-
I thought hard about why I wanted KDE and decided it was only because I like Konqueror with its web browsing/ftp and
twin-pane file-management capability - I don't need anything else from KDE.
So I have used Synaptic to install Konq and Dolphin (both are needed). This brings in dozens of dependencies and
uses up some disk space.
But MX15 now does almost everything I want.
YMMV

I like to customize and KDE is the Interface I chose. Yes, MX-15 is perfectly usable as it comes OOTB. And is easily 'tweaked' also. That's one of it's biggest strengths. "Make it your own" understates it. Linux is about choices. Enjoy

I was pondering on the comment that udev could take some time to load. So two days ago I again inserted the MX15 KDE live disk and headed out of the house leaving it to its own devices. When I returned a couple of hours later lo and behold there was MX15 KDE in all its glory.

I gave it a run through some graphics files with GIMP and spreadsheets with Office on my work drive and the results were perfect. Unfortunately the internet connection was not working and I have yet to figure that one out as it could have been my broadband link and I didnt have time to reboot and reload

It felt familiar to use after having been on Mepis since 2008 and I like it, so a new hard drive is on the shopping list ;-)

So thanks guys for your help and my problem appears solved

Regards
Peter
ps. Back around 2007-8 someone gave me a magazine cd of AntiX and that lead on to Mepis fairly quickly. I had been using Amiga up until 2004-5 and reluctantly had to use MS so the move to Mepis was a welcome one. I still have an operating Amiga and files operating under an emulator on Mepis.

I hope its okay to ask this in this thread

Ive had a second run at the live disk. It took about 30 minutes to load and as previously the application software performed okay except the internet and bluetooth were not connected. Should this be the case?

On my other machine the MX15 live disk loads in about 5 minutes and the internet connection is operational.

Both computers are connected through the same router

Regards

Did you try the Safe Boot option? Or any cheat codes? Like xdrvr=radeon, nouveau, or intel. Or noacpi?
On the GRUB boot screen F4 and F6 are full of options to try. Try each in order to see if one will help. Any one might be a fix for your booting problem. Some are more likely, but all are there for a reason.

So no, 30 minutes is not in any way acceptable. And not having a wired (Ethernet) connection isn't either. Usually you do have to do some setup for Bluetooth to work. I suggest you wait for someone that uses it to respond.

The output from terminal of inxi -F would help also. Use the code brackets in the full editor for it's output. You can use MX-14 for this, or antiX

Erring on the side of caution with respect to the invaluable data on my work hard drive........ In a weeks time I will install MX15 KDE on a brand new drive despite how long the Live Disk takes to load and take it from there. Watch this space ;-)