lahirdenganselamat wrote:why apt-get update took so long?? its been 15min now.. and not yet finished...grrrr...

You may want to take a look at apt-fast. It's pretty good for speeding up apt-get, although it's not on my system any more. Not sure why because it was pretty quick when I checked it out earlier this summer.

uninstall process stalled, twice, at first, its halted (or hang?) on removing fglrx-driver, the unistallation continue after i close the konsole (no warning from the konsole like it should be when it host running process), the second was on "ATI card found: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310]" so i decide to close the ddm window (and it closed without any delay).

Going to go test the 32 bit iso on another machine of mine to see if I can replicate the issue. There may be a problem with the current UP4 isos /etc/default/grub configurations as I just noted that they have the failsafes enabled such as fixed resolution 800x600, whereas the Linux Mint 13 KDE iso did not. So I'm going to test and see if another computer (extremely different hardware) runs into the same issue. I'll edit this post on my findings.

EDIT:

Same result. Two entirely different units (One a 2010-ish gaming rig, one a 2006 tablet) had the same result. Grub was configured wrong, and was setting some failsafes which could cause system issues.

A fix, if this is a bug other people have and it truely isn't just me, is to go into recovery mode, log in as root, and do the following:

By the way, Schoelje. If it's not just me, and the grub has been setup to have failsafes on by default, you may wish to correct it for UP5 if still there. Failsafes don't cause problems on most computers (as far as I know), but mine in particular, and a few others I have at school, will utterly freak out and begin to display errored graphics and crash constantly with some of them turned on.

Life is like hot chocolate. Sometimes it's so hot it burns your mouth. Other times it's just right.

Ah one more issue that needs correcting! The up4 x64 ISO doesn't have multiarch enabled. As a result, programs which rely on i386 binaries such as skype and wine cannot be installed until this is fixed. (A placeholder program for wine is installed instead which explains the process of activating multiarch within debian). After following the wine64-bin instructions it works again. One moment and I'll post them.

Were the instructions to follow to enable multi-arch, and the installation of x64 packages which need i386/i686

Note that the second command basically just adds "[arch=amd64,i386]" between the deb and url portions of the sources.list entries.

ALSO: This is EXTREMELY important for x64 users to be enabled given that the ia32 compatibility libraries have been (or are being) MOVED over to i386, and cannot even be located within x64 alone. Thus you need multiarch enabled to enable 32-bit compatibility (VERY IMPORTANT for people like me that use programs from both archs. Secondlife is one such program, given it's almost never compiled in x64)

EDIT:Likely going to go for Linux Mint 13 KDE for the time being, but if you need any further x64 testing just give me a shout. Switching only because I need the stability for one or two of my classes, but I really do want to see a kick-butt Debian KDE distro out in the wild, so I'll be willing to help with anything you want me to! I hope these pre (grub issue was prior to up5 update) and post up5 update UP4 issues I found help with the UP5 release, as well. I know its not much, but maybe somewhere it'll make someone's life a little easier (even if they just find a "Fix" via finding my posts ) I'll be keeping a partition open just for this ;P

Life is like hot chocolate. Sometimes it's so hot it burns your mouth. Other times it's just right.

ALSO: This is EXTREMELY important for x64 users to be enabled given that the ia32 compatibility libraries have been (or are being) MOVED over to i386, and cannot even be located within x64 alone. Thus you need multiarch enabled to enable 32-bit compatibility (VERY IMPORTANT for people like me that use programs from both archs. Secondlife is one such program, given it's almost never compiled in x64)

I've been experimenting with multiarch and left it very disappointed. Also, it doesn't seem to be a Mint policy as LMDE isn't offering it either and I do not wish to stray to much from the Mint path.

Step 3) Replace the line that reads "GRUB_CMDLINE_LINUX_DEFAULT="JUNK HERE"" (NOTE: It won't actually say junk here, but there'll be things such as 800x600 and the like) with "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash""

The junk is there to enable Plymouth. As far as I know, no other users has reported any issues.

So, to all the other users: please report any issues you have with Plymouth.

I've been experimenting with multiarch and left it very disappointed. Also, it doesn't seem to be a Mint policy as LMDE isn't offering it either and I do not wish to stray to much from the Mint path.

Just make sure you mention this in release notes or such, as packages like skype and wine are moving half their content to the i686 packages which means that they won't install at all, or won't install properly without multiarch enabled. Ia32 is moving over as well (already moved in ubuntu), so that'll be another big reason to at least mention it's not enabled.

The junk is there to enable Plymouth. As far as I know, no other users has reported any issues.

So, to all the other users: please report any issues you have with Plymouth.

I had assumed such after a time. However, it caused my Asus G73sw to have a heart attack. It started up in 800x600 with a flashing cursor, low graphics, and I'd crash to terminal or crash out of terminal periodically. Another school computer LOOKED fine, but it couldn't reboot.

Life is like hot chocolate. Sometimes it's so hot it burns your mouth. Other times it's just right.

multiarch afaik will only be default in debian with the upcoming debian 7. so eventually not even the next respins (if they come out fairly quick) will have multiarch enabled by default.Schoelje here and me here >> viewtopic.php?f=190&t=111026 have been trying multiarch and for me it's still a solution looking for problems.

zerozero wrote:multiarch afaik will only be default in debian with the upcoming debian 7. so eventually not even the next respins (if they come out fairly quick) will have multiarch enabled by default.Schoelje here and me here >> viewtopic.php?f=190&t=111026 have been trying multiarch and for me it's still a solution looking for problems.

I'll admit its more of an annoyance than a help, but I'd assume its being done to free up x64 packages from repositories...not that they really take up much space. It really only helps with things like wine. Still, it's something to at least mentioning being disabled because I was clueless for a time why wine wasn't installing. It might be a solution looking for a problem, but not including it and not mentioning it being disabled will just lead to confusion as its used more and packages are moved. I was able to find out the problem by trying to run wine through commandline, but someone who isn't used to such things would just be baffled for an hour, give up, and leave to use something else.

Life is like hot chocolate. Sometimes it's so hot it burns your mouth. Other times it's just right.

Setting up oss-compat (2) ...libkmod: ERROR ../libkmod/libkmod-module.c:1791 kmod_module_get_holders: could not open '/sys/module/ufs/holders': No such file or directorylibkmod: ERROR ../libkmod/libkmod-module.c:1791 kmod_module_get_holders: could not open '/sys/module/qnx4/holders': No such file or directorylibkmod: ERROR ../libkmod/libkmod-module.c:1791 kmod_module_get_holders: could not open '/sys/module/hfsplus/holders': No such file or directorylibkmod: ERROR ../libkmod/libkmod-module.c:1791 kmod_module_get_holders: could not open '/sys/module/hfs/holders': No such file or directorylibkmod: ERROR ../libkmod/libkmod-module.c:1791 kmod_module_get_holders: could not open '/sys/module/minix/holders': No such file or directory

This seems to be an endless loop and freezes the system completely and there's nothing left then a hard reset.Running dpkg --configure -a starts the same loop which means I cannot get out of the process and have to start all over again.

I cannot find anything conclusive on the net. The 32-bit version has no trouble with it whatsoever.I'm going to try to purge oss-compat first, before upgrade and hope that completes the upgrade process.

I don't know Schoelje, but I've checked on my system (64bit, tracking testing) oss-compat version 2 is installed..

ah, I have a question right now, how to prevent mint-update to startup? I can't find it on startup application on control center.. I think if I can prevent some apps and service to load on startup, the boot time can be faster.. For now, dmseg show 48 sec, but on stopwatch, its 2 minutes 4 second (from grub > enter until fully loaded desktop)

I found that url also and probably it's got to do with some usb thingy, but I'm to impatient to find out (have to get those isos working and tested asap).So, removing oss-compat before upgrade works just as well and a lot faster Now to find out what I can do to reinstall it...

the result:before I do all of that: from grub to end of plymouth > 58 secfrom KDE loading (I dont know how to call it) to desktop > 40 sec, total = 1 minutes, 38 sec

then I reboot, I think it supposed to do a "profiling", but the boot process take 1 minutes 42 sec, so I reboot again to see the profiling result:from grub to end of plymouth > 55 secfrom KDE loading to desktop > 30 sec, total = 1 minutes, 25 secyea, not much, but its better I think

But I think its because I never re-format that sda6 for about 2 years (sda6 is my /home), ah, sorry if my post oot..

back again, Schoelje, what about my post earlier?

lahirdenganselamat wrote:uninstall process stalled, twice, at first, its halted (or hang?) on removing fglrx-driver, the unistallation continue after i close the konsole (no warning from the konsole like it should be when it host running process), the second was on "ATI card found: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310]" so i decide to close the ddm window (and it closed without any delay).

uninstall process stalled, twice, at first, its halted (or hang?) on removing fglrx-driver, the unistallation continue after i close the konsole (no warning from the konsole like it should be when it host running process), the second was on "ATI card found: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310]" so i decide to close the ddm window (and it closed without any delay).

A few days ago, Clem and I moved DDM to the linuxmint github. This means that I'm not the only one developing on DDM now. Hopefully there are some ATI users that know how to improve the ATI code. A big problem is the driver itself. As you know it's not in wheezy so I got them from sid and that alone introduces new risks. DDM will be part of the upcoming LMDE KDE iso (I can do that as long as LMDE KDE isn't officially a Linux Mint distro). Hopefully there are more ATI users out there that can help me out improving DDM.