Linux Mint Forums

Not finished for today gents! I found another little niggle...

i decided to disable the splash screen just to see what the big delay in the middle of boot was.
I found that the warnings to disable ipv6 came up 4 times, the first two were reasonable quick then there was a big delay, then the other two... and a few seconds after that tty and then the logon screen.

What is causing the delay in my boot? Why do i need to disable ipv6? Is it doing any harm being enabled?

I don't have a big problem with the boot times, its just a long delay always makes you nervous.

Can anyone shed any light or suggestions?

I don't remember exactly what the trouble with enabling IPv6 is, but it can cripple your internet....
And as nobody (?) uses it yet you can safely turn it off. However the appearance twice (not really four times as there are two blocked modules (or something) is a bit odd. Do you see any error between the first and the second set?
And keep it up Fergus - you are really doing great

Thanks Husse, for me its just nice to be contributing, even though the majority of the post is just my rambling nonsense.

As for ipv6, your argument is good enough. If it ain't broken don't fix it!
There are no errors between the first and second statements, is there a boot log that shows all these statements that i can look at? i've had a quick search and found /var/log/ but nothing in there seems about right.

/var/log/boot

Telic since you copied me foolishly, have you any thoughts?

No, I didn't copy you, I used the same procedure as in the Ubuntu blog. Kiba dock has worked perfectly for me, easily and every time. I don't know what you've done differently somewhere.

Last night I downloaded Sabayon Linux 3.3 miniEdition for a test drive. It comes loaded with multimedia codecs and plugins, and is the slickest-looking distro I've tried so far. It automatically installs the latest (nVidia) display driver and Beryl 3D, so you don't need to edit the Xorg config file at all. The kiba-dock tarball is easy to download and install, so I did it with the Sabayon live CD, even before loading the distro onto my HD.

Here's a screenshot of the Sabayon live CD running kiba-dock with Firefox, KWrite, and Amarok launch icons (on the righthand edge of the desktop)...


[click image to enlarge]

The kiba installation process on Sabayon is virtually the same as with Mint (Ubuntu), except without the extra step to install the dependencies.

I've abandoned Mint in favour of Ubuntu, BTW. I purchased one-year support subscriptions for my field engineers, and they're satisfied with the service.

------

I was looking at Sabayon too.... very intrigued. I think i might try a live cd. Whats that distro based upon?

I fixed the kiba dock - finally got it uninstalled then went with the script from the forum. Yes its a better dock but i'm getting very very high CPU usage when i turn the physics engine on.
Again.... i'll keep pluggin away!

Thanks for the advice!

I was looking at Sabayon too.... very intrigued. I think i might try a live cd. Whats that distro based upon?

Sabayon is based on Gentoo Linux, so there's a mountain of online documentation and community support, plus a well-stocked software repository (see Portage and Kuroo).

It's clear that the Sabayon team has focused on detail, making the installation process highly polished and seamless. It uses a customized Anaconda installer, a la Red Hat, which I think is overall superior to the GParted et al process.

For combined simplicity and glossy appearance, I won't be surprised if Sabayon challenges PCLinuxOS for popularity (though the Sabayon default theme is kind of funky and broody). Have a look-see at the Sabayon 3.3 miniEd live CD. Step-by-step instructions for installing kiba-dock are posted [here], which you can copy and paste line-by-line into Sabayon's liveCD Konsole.

FWIW, my Mint setup used the bash command shell, whereas your Bianca (Edgy) defaults to dash. Dash is POSIX compliant, but some Linux hacks use old bash quirks. This is known to jinx some script-based compiling procedures.

To switch from dash to bash, go Terminal and enter... Whenever you want to return to using dash... Mint 3.0 Cassandra (Feisty) also uses dash.

Good luck with your determined plugging-away. It's a worthwhile learning process.

------

Telic could you post a link to the kiba-dock installation instructions?
I'm still not happy with it.

I think i'll leave gentoo till i get my mint experience a little higher!
Next on my agenda is bluetooth, so i can use my headset with skype.

Another quickie from me.... i do a lot of work in electronics design and i have been asked to do some research in asynchronous logic and so i need to download the appropriate design tools.

one of which is from here

http://intranet.cs.man.ac.uk/apt/projects/tools/balsa/

Could some one please explain the correct procedure for install this for mint and then in general. The install file is not helpfull to me at just seems to send me down a garden path.
There is no instruction on installing and launching the package from the fresh install.

I'm really struggling without a .deb package. I'm still a noob at heart...

Telic could you post a link to the kiba-dock installation instructions?

Same place as before: Install kiba-dock on Edgy Eft

I'm really struggling without a .deb package. I'm still a noob at heart...

I'm a Linux n00b too, having wandered onto the scene in March.

The following procedure got Balsa up and running on my Feisty setup. No guarantee about how it might go with Mint. And whether or not Balsa will actually function as intended is something you'll discover by trying it.

The following steps should install Balsa in your home directory under a subdirectory named etc. You can copy and paste each line of code from here into Terminal. I recommend that you disable Beryl before trying to install Balsa (re-enable Beryl after you've successfully installed Balsa).

1) Use the Synaptic repository manager to find and install the following packages required by Balsa...

libgtk1.2 (Balsa looks for this specific version)
libgmp (get highest version available)
guile-1.8 (or highest version of guile available)

2) Go to your Home directory, in Terminal... 3) Download the Balsa 3.5 for Linux i686 binaries tarball file... 4) Download the Balsa User Manual, a PDF file... 5) Create the etc subdirectory and go into it... 6) Extract all the stuff that's in the Balsa tarball, creating subdirectory ~/etc/balsa ... 7) Make a backup copy of your .profile file, then open it using the gedit text editor... 8 ) To set the Linux environment variables required by Balsa, copy and paste all of these lines to the end of your .profile file...

# BEGIN Balsa Environment Variable Section
export PATH=~/etc/balsa/bin:${PATH}
export LD_LIBRARY_PATH=~/etc/balsa/lib:${LD_LIBRARY_PATH}
export BALSAHOME=~/etc/balsa
export WAVE_SHARE_DIR=~/etc/balsa/share/gtkwave
export WAVE_READER_PATH=~/etc/balsa/lib/gtkwave
# END Balsa Environment Variable Section

Save your updated .profile file, closing gedit.

Finally, close whatever other apps are open and restart X with Ctrl-Alt-Backspace.

The complete suite of Balsa tools is now installed. To invoke the Balsa Manager, go Terminal and enter... I haven't tested Balsa's proper operation. You should run the examples from the User Manual and compare your results. Watch for errors that complain of something missing.

-----

Telic,

what do you do if you have no .profile file?
The closest i got was the bash_profile, but even then there were no other environment variables.

Where do they hide in bianca?

what do you do if you have no .profile file?
The closest i got was the bash_profile, but even then there were no other environment variables.

Just use your .bash_profile file for Step 8, instead of .profile (your login command shell won't even look for ~/.profile if it finds ~/.bash_profile first).

This will set the variables for just you. To globally effect the environment variables for every user who logs onto your system, including you, edit /etc/profile instead. Everyone, including root, also has their own profile script file in their home directory.

-----

I tried again and this time terminal would not recognise the balsa-mgr command when modifying the .bash_profile, i edited the /etc/profiles and now i can launch balsa-mgr however, two errors on the basla console:

cannot open tech directory '~/etc/balsa/share/tech'
cannot open tech directory '/usr/local/balsa/share/tech'
No valid balsa technologies found

The third statement related to the first statement, but i cannot understand why it cannot open the tech directory from my home directory. Is this a permissions thing or something else?

Not convinced with the balsa install from the binary distribution. Would i be better installing it from the source or is this just stuptid.
Is this a distro specific install, or is this general install instructions that need to be taylor for mint/ubuntu?

i think i will email the help link and see if they can be a little more detailed in there installation explanation. Any thoughts in the interim?

Is this a permissions thing or something else?

A user shouldn't have access permission problems with files or subdirectories in their home directory -- unless perhaps you unwittingly used sudo to invoke tar with superuser honors.

To assure that you've got proper permissions with Balsa's files and directories, log in to Mint as your usual self and go Terminal to enter... -----

Nope still no change on that. I have yet to email the developers so i'll update when i have time.

Just a little note: many many times i have been working in windows, and left my laptop running only for it to hibernate due to lack of usage or just putting the lid down. On reboot mint will be come temperamental with disk access and will require a disk scan. I don't know the in depth reason but i believe that windows must allocate the disk to itself and does not relinquish this hold until you have shut down windows. Hence mint will try to use the disk with windows still attached to it. So if ever you see mint checking disks regularly and wont load your windows partition this will be the reason.

I split off your last post in the hope someone might have an answer - but no, so I gave an answer myself in
http://www.linuxmint.com/forum/viewtopic.php?p=25005
I forgot to add a note about it before

I have no idea how though... i just thought to myself the other day. Wipe everything apart from the actual install files then follow the binary distribution instructions. I have no idea how i didn't get this right the first time!

This was my procedure for installations with no deb or rpm file. the ctrl-alt-backspace to re-load everything!

I hope this helps someone else!
next i will try wit my bluetooth headset

You did it!?
I'm glad that it worked out for you, with the long story behind you. Never give up!