Multiple Boot Option

Here is where you can post tips and tricks to share with other users of MX. Do not ask for help in this Forum.
Message
Author
User avatar
i-Scan
Posts: 13
Joined: Fri Nov 27, 2015 2:47 pm

Re: Multiple Boot Option

#21 Post by i-Scan »

Well, I have the next two days to work this LINRAD thing out. In the back of my mind, I am thinking of backing all of this up and restoring it on a newer drive. Several facets of this MX-15 project are going far better than my expectations. I know I will use Windows 10 because so many programs run on Windows. Then I noticed that I have not run Windows for anything serious in this past week.

I am about to give this a try with fewer su commands as you suggested. When su is needed the system says something like, "forget it; come back with access when you want to try again."
i-Scan@Win10/Pentoo/MX-15_x64 Fusion 24Dec15
Dell OptiPlex 780 A15Bios date: 08/2013
Dual core Intel Core2 Duo E8400 2992 MHz
Graphics: [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT] Gallium 0.4 on AMD RV610 GLX v: 3.0 Mesa 10.3.2 8GB RAM

User avatar
asqwerth
Developer
Posts: 7211
Joined: Sun May 27, 2007 5:37 am

Re: Multiple Boot Option

#22 Post by asqwerth »

Code: Select all

mkdir linrad

cp Downloads/lir04-07.tbz /home/iscan/linrad/

chdir linrad

tar xvfj lirxx-yy.tbz

chdir /home/iscan/linrad
You were saying that you are going to try to do without so many su commands.

I'm no commandline expert, but from what I can see, the commands I copied above could all be done via file manager, ie using a graphical interface/tool.

mkdir = create directory. So you could use the file manager (Thunar) while in your /home folder to make the linrad sub-folder.

cp = copy Again, a right click in file manager will enable you to copy the archive file you downloaded to your new sub-folder.

chdir = change directory. If you're already in the right directory in file manager from the command above, you don't need it.

tar = I think this is the command to open the archive file and extract the contents. You can just double click on the tbz file while in file manager and a graphical tool will open (just like for zipped files in Windows) to enable you to extract the contents.

It's only after you've extracted the archive file into the chosen directory that you use the make command in the terminal, and then continue on from there to install the package (for which you will need root/su access).
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
i-Scan
Posts: 13
Joined: Fri Nov 27, 2015 2:47 pm

Re: Multiple Boot Option

#23 Post by i-Scan »

Okay, while I'm attempting to deal with the 32 bit libraries for gcc that are reportedly not in place from the MX-15 repository...

Is X11 referred to below the GUI for MX-15 like I think it is? If so, I want to compile for X11 and avoid running from terminal mode, right?

Maybe I should plug in two USB receiver dongles so they are found and identified while configure runs as I don't think I need to deal with Soft66, Elektor, Funcube ProPlus, Afedri USB, PCIe-9842, bladeRF, Mirics USB dongles, ELAD or Perseus-SDR related comments and because I may never use any of these? Even then I could recompile this to include the intended unit and by then there will doubtless be yet another update anyway!

Use of a sound card is a must because that is where all my defined signal processing will happen.

Because there are so many things missing I have not; but, one of these said that I can run make without argument for info.

Here is command and output that I'm seeing:
iscan@mx1:~/linrad/linrad-04.07
$ ./configure --with-help
./configure: line 1439: config.log: Permission denied
./configure: line 1449: config.log: Permission denied
iscan@mx1:~/linrad/linrad-04.07
$ sudo ./configure --with-help
checking OS... checking for gcc... /usr/bin/gcc
checking for nasm... /usr/bin/nasm
checking for make... /usr/bin/make
checking for wget... /usr/bin/wget
checking for pkg-config... /usr/bin/pkg-config
checking for libtoolize... no
checking for automake... no
checking for cmake... no
checking for git... /usr/bin/git
checking for alien... /usr/bin/alien
checking for svn... no
checking for xxd... no
checking for g++... /usr/bin/g++
checking for /usr/lib/oss/soundcard.h... no
checking for /usr/lib/oss/include/sys/soundcard.h... no
checking for /usr/local/lib/oss/soundcard.h... no
checking for /usr/local/lib/oss/include/sys/soundcard.h... no
checking for /lib/oss/soundcard.h... no
checking for /lib/oss/include/sys/soundcard.h... no
checking for /var/lib/oss/soundcard.h... no
checking for /var/lib/oss/include/sys/soundcard.h... no
checking for /opt/oss/soundcard.h... no
checking for /opt/oss/include/sys/soundcard.h... no
checking for /root/oss/soundcard.h... no
checking for /root/oss/include/sys/soundcard.h... no
checking for /dev/dsp... no
checking for /dev/sound/dsp... no
checking for /etc/rc3.d/.... yes
checking for /etc/init.d/rc3.d/.... no
checking for /etc/rc.d/rc3.d/.... no
checking for ./users_hwaredriver.c... no
checking for ./users_hwaredriver.c... (cached) no
checking for ./wusers_hwaredriver.c... no
checking for ./wusers_hwaredriver.c... (cached) no
checking for ./users_hwaredef.h... no
checking for ./users_hwaredef.h... (cached) no
checking for ./wusers_hwaredef.h... no
checking for ./wusers_hwaredef.h... (cached) no
checking for ./users_extra.c... no
checking for ./users_extra.c... (cached) no
checking for /usr/bin/i686-w64-mingw32-gcc... yes
checking for /usr/i686-w64-mingw32/include/math.h... yes
checking for /usr/bin/i586-mingw32msvc-gcc... no
checking for /usr/bin/i586-pc-mingw32-gcc... no
checking for /usr/bin/i686-pc-mingw32-gcc... no
checking for /usr/bin/i686-w64-mingw32-gcc... (cached) yes
checking for /usr/i686-w64-mingw32/sys-root/mingw/include/math.h... no
checking for /usr/src/linux... no
checking for /usr/src/linux-2.4... no
checking for build/extlibs/libclFFT.a... no
checking for extlibs/clFFT/src/include/clFFT.h... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating conf.h
config.status: creating lconf.h
config.status: creating rusage.h
config.status: creating ft245.c

Symbol tables enabled. See options.h how to disable.

|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Missing or not working libraries (non fatal.)

The 32 bit libraries for gcc are not in place
Debian, Ubuntu: apt-get install libc6-dev-i386
Old Debian, Ubuntu: apt-get install ia32-libs-dev
New Debian,Ubunty: apt-get install lib32bz2-dev
older Fedora: yum install glibc-devel.i586
old Fedora: yum groupinstall 'Legacy Software Development'
old Fedora: yum install glibc-devel.i686
Fedora 22 and later: dnf install glibc-devel.i686 libstdc++-devel.i686
SuSE: zypper install gcc-32bit

Not present: libsoft66.so (64bit)
This package is needed for the Soft66 series receivers
Install libftdi before libsoft66

Not present: libftdi.so (needed for Soft66 or Elektor)
Debian,Ubuntu: apt-get install libftdi-dev
Mandriva, Mageia: urpmi libftdi-devel (ftdi.h may be misplaced)
----------------: cp /usr/include/libftdi/ftdi.h /usr/include
PCLinuxOS: apt-get install libftdi-devel
old Fedora: yum install libftdi-devel
Fedora 22 and later: dnf install libftdi-devel
SuSE: zypper install libftdi1-devel
Gentoo,Sabayon: emerge libftdi
Mageia: urpmi libftdi-devel
Then run ./configure --with-help again.

Can be installed from source instead.
cd /usr/src
rm -f libftdi-0.18.tar.gz
wget http://www.sm5bsz.com/linuxdsp/archive/ ... .18.tar.gz
tar xvfz libftdi-0.18.tar.gz
cd libftdi-0.18
./configure
make
make install
Then run ./configure --with-help again.

Not present: libudev.so (64bit) (Funcube ProPlus, Afedri USB)
Debian, Ubuntu: apt-get install libudev-dev
Mandriva: urpmi libudev-devel (udev.h misplaced)
PCLinuxOS: apt-get install lib64udev0-devel
vy old Fedora: yum install systemd-devel
vy old Fedora: ln -s /usr/lib64/libudev.so.1.2.1 /usr/lib64/libudev.so
old Fedora: yum install libudev-devel
Fedora 22 and later: dnf install systemd-devel
SuSE: zypper install libudev-devel
Mageia: urpmi lib64udev-devel
Then run ./configure --with-help again.
Udev is believed to be part of most Linux distributions

Not present: libwd_dask64.so (64bit) Neded for PCIe-9842
Get it from the ADLINK Internet site
http://www.adlinktech.com
Register with your email account. Go to:
Products > PXI & Modular Instruments >
Digitizers/Oscilloscopes > Drivers
Unpack the wd-dask .tgz archive and copy the libwd_dask.so
file to a suitable location.
Then run ./configure --with-help again.

Not present: libbladeRF.so (64bit)
This package is needed for the nuand.com bladeRF
You have to install cmake first.
Debian, Ubuntu: apt-get install cmake
old Fedora: yum install cmake
Fedora 22 and later: dnf install cmake
Mageia: urpmi cmake
PCLinuxOS: apt-get install cmake
SuSE: zypper install cmake
Gentoo, Sabayon: emerge cmake
Then run ./configure --with-help again.

Not present: libOpenCL.so (64 bit)
This package is needed to use the graphics card for fast FFT
Debian, Ubuntu: apt-get install amd-opencl-dev
----: Note that non-free has to be specified in /etc/apt/sources.list
Fedora 22: dnf install dnf install ocl-icd-devel opencl-utils-devel
Mageia: urpmi lib64opencl1 lib64opencl-devel
Then run ./configure --with-help again.

Not present: libmirisdr.so (64bit)
This package is needed for the Mirics USB dongles
You have to install cmake first.
Debian, Ubuntu: apt-get install cmake
old Fedora: yum install cmake
Fedora 22 and later: dnf install cmake
Mageia: urpmi cmake
PCLinuxOS: apt-get install cmake
SuSE: zypper install cmake
Gentoo, Sabayon: emerge cmake
Then run ./configure --with-help again.

Not present: libairspy.so (64bit)
This package is needed for Airspy.
You have to install cmake first.
Debian, Ubuntu: apt-get install cmake
old Fedora: yum install cmake
Fedora 22 and later: dnf install cmake
Mageia: urpmi cmake
PCLinuxOS: apt-get install cmake
SuSE: zypper install cmake
Gentoo, Sabayon: emerge cmake
Then run ./configure --with-help again.

Not present: libfdms1.so.1.0 (64 bit)
This package is needed for the ELAD FDM-S1 receiver
Install the libfdms1 library like this:
(copy and paste into the command line)
cd /usr/src
mkdir libfdms1
cd libfdms1
wget http://sdr.eladit.com/FDM-S1%20Sampler/ ... _amd64.deb .
alien --scripts --to-tgz libfdms1_1.0-1_amd64.deb
tar xvfz libfdms1-1.0.tgz
mkdir /usr/local/lib64
cp usr/local/lib64/* /usr/local/lib64
Then run ./configure --with-help again.

Not present: libperseus-sdr.so (64 bit)
Install libusb-1.0 before libperseus-sdr.so

Not present: libusb-1.0.so (64bit)
Needed for most USB hardware.
To install, use one of these commands:
Debian, Ubuntu: apt-get install libusb-1.0-0-dev
Old Fedora: yum install libusb1-devel
New Fedora: yum install libusbx-devel
Mageia: urpmi lib64usb1.0-devel
SuSE: zypper install libusb-1_0-devel
PCLinuxOS: apt-get install lib64usb1.0-devel
Then run ./configure --with-help again.

Not present: libusb.so (64bit)
This package is no longer needed but it is an alternative.
for the Si570 (Softrock, IQ+, Fifi SDR and others) and USB2LPT
It is becoming obsolete and libusb-1.0 is a replacement.
If you do not have Si570 or USB2LPT, ignore this package
To install old libusb, use one of these commands:
Debian,Ubuntu: apt-get install libusb-dev
old Fedora: yum install libusb-devel
Fedora 22 and later: dnf install libusb-devel
SuSE: zypper install libusb-compat-devel
Mageia: urpmi lib64usb-compat0.1-devel
PCLinuxOS: apt-get install lib64usb-compat0.1-devel
Then run ./configure --with-help again.

Not present: libvga.so (64bit) (and/or missing headers)
Header file vga.h vgagl.h or vgamouse.h missing or misplaced
or libx86.so.1 missing
svgalib is only needed for running Linrad in terminal mode.
If you want to compile for X11, there is no need to install it.
Read at http://www.sm5bsz.com/linuxdsp/install/svgainst.htm for info
about installing svgalib from source code. The versions supplied
by the distributions may support very old videocards only.
Obsolete svgalib versions can be used in linrad to provide a mouse
to use with the framebuffer device. Compile flinrad on marginal
platforms to avoid the X11 overhead. (Requires svgalib.)
Debian, Ubuntu: apt-get install libsvga1-dev
old Fedora: yum install svgalib-devel
Fedora 22 and later: dnf install svgalib-devel
Mageia: urpmi lib64svgalib-devel
PCLinuxOS: apt-get install lib64svgalib1-devel
Mandriva: urpmi lib64svgalib1-devel
Then run ./configure --with-help again.

You can install from source like this:
cd /usr/src
wget http://www.sm5bsz.com/linuxdsp/archive/ ... 5-3bsz.tbz
tar xvfj svga1925-3bsz.tbz
cd svgalib-1.9.25-3bsz
make install
(..../utils may fail but that does not matter)
Then run ./configure --with-help again.

Not present: libX11.so (64bit) (and/or missing headers)
The X11 package is only needed for running Linrad with X11
If you want to compile for terminal mode with svgalib there is
no need for it.
Debian, Ubuntu: apt-get install libx11-dev
Mandriva: urpmi lib64x11_6-devel
Mageia: urpmi lib64x11-devel
SuSE: zypper install xorg-x11-libX11-devel
old Fedora: yum install libX11-devel
Fedora 22 and later: dnf install libX11-devel
PCLinuxOS: apt-get install lib64x11-devel
Mac OSX: Install XQuartz http://xquartz.macosforge.org/landing
Then run ./configure --with-help again.

Not present: libasound.so (64bit)
This is the library for the ALSA sound system.
Install the ALSA package like this:
Debian, Ubuntu: apt-get install libasound2-dev
old Fedora: yum install alsa-lib-devel
Fedora 22 and later: dnf install alsa-lib-devel
Mandriva, Mageia: urpmi lib64alsa-oss-devel
SuSE: zypper install alsa-devel
PCLinuxOS: apt-get install lib64alsa-oss-devel
Then run ./configure --with-help again.


There is no 32 bit sound system (and/or header files are missing.)
The existing 64 bit sound system can not be used because there
is no 64 bit screen.
Install 64 bit libX11.so or libvga.so
or install 32 bit libportaudio .so or libasound.so
Alternatively, install the 32 bit version of 4Front OSS

Soundcards can not be used.
Input from Perseus, SDR-14 and other SDR hardwares is possible
The output can be sent to network or a disk file.

Normal End. You can now run make
(Run make without argument for info.)
To generate servers (daemons) run configure --with-server
i-Scan@Win10/Pentoo/MX-15_x64 Fusion 24Dec15
Dell OptiPlex 780 A15Bios date: 08/2013
Dual core Intel Core2 Duo E8400 2992 MHz
Graphics: [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT] Gallium 0.4 on AMD RV610 GLX v: 3.0 Mesa 10.3.2 8GB RAM

User avatar
i-Scan
Posts: 13
Joined: Fri Nov 27, 2015 2:47 pm

Re: Multiple Boot Option

#24 Post by i-Scan »

@asqwerth

Now that would have never occurred to me without you telling me. I am most definitely burning that idea into my brain for future use. I am from way back in the MS-DOS era before ppl referred to Windows without any affection as Pains. Likely it is why I head for Terminal too early!
i-Scan@Win10/Pentoo/MX-15_x64 Fusion 24Dec15
Dell OptiPlex 780 A15Bios date: 08/2013
Dual core Intel Core2 Duo E8400 2992 MHz
Graphics: [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT] Gallium 0.4 on AMD RV610 GLX v: 3.0 Mesa 10.3.2 8GB RAM

User avatar
asqwerth
Developer
Posts: 7211
Joined: Sun May 27, 2007 5:37 am

Re: Multiple Boot Option

#25 Post by asqwerth »

My feeling is that you are making things more complicated than they are.

I don't know much about Pentoo, but Gentoo is not usually used by Linux newcomers. If I understand correctly, in Gentoo applications/packages are manually made from source.


But that's not the case for many other distros.

Lots of Linux distros have been user-friendly and GUI-oriented for quite some time now; Linux is honestly not as geeky or terminal-based nowadays, unless you truly want it to be.

You should be approaching MX14 or 15 as if it was Windows version XP and beyond. Not MS-DOS. :p

1. Take time to read the Manual for MX15:
http://www.mepiscommunity.org/manuals (this link is found on a tab at the top right corner of this forum page).

From the manual, get to understand the concept of Debian's (MX is a derivative thereof) package management. Tons of programs and applications are already packaged as binary files and stored in Debian/MX repositories which you can install using Synaptic (graphical package manager).

Unless it is a rare program, you may not need to download the source files from the developer's site to make the package yourself.

Always search the repositories with Synaptic first.


2. see what tasks are available in Thunar (file manager) by right clicking on various files/folders to see what pops up on the context menu.

3. explore the MX-tools -click on the "Start/Applications" button at the bottom left corner of the MX desktop.

You'll see that tons of stuff can be done via graphical tools.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
eugen-b
Posts: 92
Joined: Tue Aug 25, 2015 1:56 pm

Re: Multiple Boot Option

#26 Post by eugen-b »

I would disagree with asqwerth, but only for the case of compiling from source and other tasks done following a guide. If a guide provides commands it is less risky to follow the commands and use the GUI only if you completely understand the commands. For compliling there are graphical pgrograms like CMake, but from my experience as a n00b it is more difficult to use than typing 5 lines into the terminal.
On the other hand, for manipulating system files I prefer to use the file manager. 'Open as root' and 'Edit as root' are very nice custom actions for this, thanks to MX devs!
I also recomend the MX User Manual! I have it in my browser's quickdial (together with Arch Linux Wiki, for some reasons I didn't come to reading the Debian Wiki).
Concerning the output of ./configure I cannot tell much. Perhaps look at Synaptic, left sidebar, section Libraries - Development. But better to wait for a knowledgeable person's advise.
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
richb
Administrator
Posts: 10322
Joined: Wed Jul 12, 2006 2:17 pm

Re: Multiple Boot Option

#27 Post by richb »

I would echo asqwerth's post. For someone new to Linux trying to start compiling or making packaged tar applications with configure, make etc. is a learning experience. My experience is that packaged programs of this type sometimes work and sometimes do not. If you want a learning experience by all means do it, but the expectation that you will end with a usable program may be optimistic.

Read the MX-15 manual cover to cover, and then read again those topics that pertain to your task. My opinion is to always find the application you want in the repositories, and if it does not exist ask our packaging experts if they can build it. These people are very good and most often can give you what you need. We have separate forums and sub-forums to make those requests.

And by all means learn the command line, it can be very useful, but also learn the power of the installed applications. Thunar can perform many of the simple tasks, like creating directories and text files, moving around the file system, and extracting files from tars and zips.

By the way when I first started using Linux many years ago I went though the same learning experience, and most of us have done so. Enjoy the journey. The end result is very satisfying..
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

User avatar
eugen-b
Posts: 92
Joined: Tue Aug 25, 2015 1:56 pm

Re: Multiple Boot Option

#28 Post by eugen-b »

richb wrote:My opinion is to always find the application you want in the repositories, and if it does not exist ask our packaging experts if they can build it. These people are very good and most often can give you what you need. We have separate forums and sub-forums to make those requests.
Agreeing with richb, the sub-forum for MX-15 packages and requests is here http://forum.mepiscommunity.org/viewforum.php?f=121
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
lucky9
Posts: 475
Joined: Wed Jul 12, 2006 5:54 am

Re: Multiple Boot Option

#29 Post by lucky9 »

Open Synaptic and left click the section labeled 'Sections' on the left side under the left window. Everything from Radio to Communication to whatever is in there. Highlight what you are interested in and Synaptic will list the programs in that category in the right hand window. Highlight a program to see a fairly detailed description.
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

User avatar
i-Scan
Posts: 13
Joined: Fri Nov 27, 2015 2:47 pm

Re: Multiple Boot Option

#30 Post by i-Scan »

Ok, my friends, most of the missing things were not listed in the repository. Got some of the stuff through means that you described.
Stumbling through terminal command lines, I have managed to get LINRAD to run and do some work. Here's what I have from terminal...

iscan@mx1:~
$ cd linrad

iscan@mx1:~/linrad
$ ls
linrad-04.07 lir04-07.tbz xlinrad64

The next command starts LINRAD configuration and then at least runs in terminal which is strange because lots of stuff was still missing when I went to configure. Strange because I expected x11 to be more graphic.

iscan@mx1:~/linrad
$ ./linrad/xlinrad64

Nevertheless, I can work with this once I figure out the program settings.

And OMG I need to thank the lot of you SO much. I guess I'm kinda in a good place, now!
i-Scan@Win10/Pentoo/MX-15_x64 Fusion 24Dec15
Dell OptiPlex 780 A15Bios date: 08/2013
Dual core Intel Core2 Duo E8400 2992 MHz
Graphics: [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT] Gallium 0.4 on AMD RV610 GLX v: 3.0 Mesa 10.3.2 8GB RAM

Post Reply

Return to “Tips & Tricks by users”