Re: KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43

[Alexander V. Makartsev]

On 13.11.2017 00:37, Ramon Hofer wrote:
> Dear all,
>
> Please help me passthrough my GPU the a KVM guest.
>
> The system I am using:
> lshw: https://pastebin.com/tB7FqqxN
>
> Host OS:Debian 9 Stretch
> Mainboard: Supermicro C7Z170-M (activated VT-d in Bios)
> CPU: Intel Core i7-7700K CPU @ 4.20GHz
> GPU: EVGA GeForce GTX1080 Ti
>
> The GPU is not listed because I have blacklisted it:
> $ cat /etc/modprobe.d/blacklist.conf 
> blacklist nouveau
>
> lspci: https://pastebin.com/6qYuJRPg
>
> I found this guide:
> https://scottlinux.com/2016/08/28/gpu-passthrough-with-kvm-and-debian-linux/
>
> After installing Win7 guest, enabling PCI passthrough using
> virt-manager, installing the NVidia driver in the guest, Windows reports
> the error 43 for the GPU.
>
> Windows has stopped this device because it has reported problems.
> (Code 43)
>
> This is described in the above mentioned post and a workaround is
> linked:
> https://www.reddit.com/r/VFIO/comments/479xnx/guests_with_nvidia_gpus_can_enable_hyperv/
>
> Unfortunately I do not know how to apply the workaround. I understand
> that I should create a file '/usr/libexec/qemu-kvm-hv-vendor' with the
> following content:
>
> #!/bin/sh
> exec /usr/bin/qemu-kvm \
> `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=whatever|g'`
>
> Or according to the original redhat mailing list post by Alex
> Williamson:
> https://www.redhat.com/archives/vfio-users/2016-March/msg00092.html
>
> $ cat /usr/libexec/qemu-kvm-hv-vendor 
> #!/bin/sh
> exec /usr/bin/qemu-kvm \
>   `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=KeenlyKVM|g'`
>
> But since there is no qemu-kvm present and the directory '/usr/libexec'
> does not exist on my system, I wonder how I should proceed.
>
> Any help fixing my problem would be highly appreciated.
>
>
> Thanky you very much in advance and best regards,
> Ramon
>
This is interesting topic and I hope to find some time to spare to
implement and test this setup on my system.
Can't suggest you anything yet, because this "Code 43" error is generic
and can happen even on normal systems.
The reasons could be limitless from driver version conflict to bios\uefi
firmware bug of your motherboard.
I wonder, what VEN_ID and DEV_ID are reported for your VGA in Windows guest?
Have you tried Windows 8.1 or 10 as guests? They could have more support
for virtualization in general.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[Eike Lantzsch]

On Sunday, November 12, 2017 10:06:11 PM -03 Dan Hitt wrote:
> On Sun, Nov 12, 2017 at 8:50 PM, Richard Owlett  wrote:
> > On 11/12/2017 09:45 PM, Dan Hitt wrote:
> >> I have some DFTs that i wish to inspect.  (Apparently DFT is a common
> >> acronym, but here i mean Discrete Fourier Transform.  And properly
> >> speaking it doesn't make sense to inspect a transform, but only to
> >> inspect transformed data, but i'm speaking colloquially.)
> >> 
> >> DFTs are a common artifact in digital signal processing.  Lots of
> >> Debian packages are focused on FFTs (Fast Fourier Transforms, a way of
> >> computing DFTs).  Nevertheless i couldn't find either a standard file
> >> format to store one, or software specifically for viewing DFTs.
> >> 
> >> Of course, lots of software can take data, then transform it, then
> >> display the transform that it created, but i would like something that
> >> can take an already created DFT in some standard format, then display
> >> it.
> >> 
> >> TIA for any information or pointers or advice from anybody! :)
> >> 
> >> dan
> > 
> > A useful set of expertise is available at the USENET group at comp.dsp .
> > HTH
> 
> Thanks Richard.
> 
> Maybe you're exactly right, because if i can find any free software
> that's relevant to what i want, then i can probably get it to Debian.
> (If i have something specific, then can bring it up here in fact if i
> have trouble installing it.)
> 
> How do you normally access usenet?
> 
> In the old days (meaning, decades ago) i used to read usenet with rn.
ask for an account on (€10 per year)
http://www.individual.net/
install leafnode and slrn on Debian

[snip]

-- 
Eike Lantzsch ZP6CGE

Hay potentes, impotentes y prepotentes.

Re: Debian 8 and Debian 9 Dual Boot

[Jochen Spieker]

Dan Norton:
henny|i
> My first Linux install was about one year ago. After some missteps, I have
> used Debian 8 in reasonable satisfaction on the desktop during that year.
> Now I want to leave 8 in place and do a network install for Debian 9 on the
> same disk and switch back and forth at boot time.

Your disk setup allows to do this comparably easy, but I would think
twice whether that is actually what I want to do. You end up with two
systems which you have to maintain and, most importantly, you cannot
properly share your /home. Most programs that save their settings to
$HOME will automatically upgrade their configuration files on first
start with a new version and after that you have to assume that the
older version cannot read it anymore. I realize that this is part of
your disk space calculation but I want to stress that the result is
probably not something that you will want to use for an extended period
of time.

> LVM reports as follows:
> 
> dan@debian:/$ sudo vgdisplay -C
>   VG   #PV #LV #SN AttrVSize  VFree
>   debian-vg   1 5 0wz--n- 976.56g 938.20g

You can vgreduce debian-vg easily to make room for your planned
debian9-vg.

> So there is plenty of disk space for the two Debians and more besides. The
> question is how to prepare to install 9? My guess is to define another
> volume group called debian9-vg perhaps but how will this be recognized
> during network install?

Yes, it will. It should also be possible to vgreduce debian.vg and
vgcreate debian9-vg inside the installer, but I would be more
comfortable doing that from the running system, using the regular tools.

During installation, you just have to make sure that all LVs in
debian-vg are marked as "Do not use".

> I've clobbered stuff before during installs and I'm
> gun shy. Maybe there is a better way. Any thoughts on this will be
> appreciated.

It happens to everybody. The only things that help are a good plan and
concentration on the task at hand. :)

J.
-- 
I like my Toyota RAV4 because of the commanding view of the traffic
jams.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: No KODI for buster?

[Floris]

Op Mon, 13 Nov 2017 01:51:17 +0100 schreef Man_without_clue  
:



Hi all,

There is no KODI for the buster?

How come?




If you are brave enough to try the deb-multimedia repo has Kodi:
http://www.deb-multimedia.org/

Note: these packages can/will sometimes break your system or make an  
update impossible.


Floris

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Nov 12, 2017 at 07:45:13PM -0800, Dan Hitt wrote:
> I have some DFTs that i wish to inspect.  (Apparently DFT is a common
> acronym, but here i mean Discrete Fourier Transform.  And properly
> speaking it doesn't make sense to inspect a transform, but only to
> inspect transformed data, but i'm speaking colloquially.)

Uh, oh. To answer that without getting lost in Hilbert Space means
consulting my (rusty) crystal ball :-)

Now more seriously: what do you mean by "inspecting" a DFT?

A DFT is just a trick to approximate a Fourier transform on an
(approximate) function. Are you talking about one dimensional
functions (e.g. a function of time) or two (three, etc.) dimensional
functions? Their transforms are, correspondingly, one, two (and
so on) dimensional functions, so the visualization techniques
vary, depending on dimensionality and on the conventions current
in the field (engineering, social sciences, maths, whatever).

I'd recommend looking into some of the many (excellent) scientific
packages having a visualization components, each one of which
has a teeming community willing to help you.

For three examples off the top of my head (all three packaged
in Debian):

  GNU Octave   https://www.gnu.org/software/octave/
  NumPyhttp://www.numpy.org/
  GNU Rhttps://www.r-project.org/

The last one is touted as "statistical package", but let me tell
you: all three are not only capable of visualizing (the result of)
a discrete DFT, but all three can calculate one for you :-)

Now if you are trying to visualize the result of a DFT on an image
(a special two dimensional case, where you think of the discrete
elements as of pixels), then perhaps a graphical package (e.g.
The Gimp) is your friend. Also packaged in Debian.

For more of those "scientific computing" packages, browsing this

  https://wiki.debian.org/DebianScience

might be of interest (or just drop "Debian scientific computing"
into your favourite search engine, which hopefully ain't Google).

Enjoy

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAloJZm8ACgkQBcgs9XrR2kYEmwCdHEeR7zsVXPrNIxSORJEupCmG
DnoAn01e7MOZnNVs4aIchkrsu6Fh6ASi
=qyUp
-END PGP SIGNATURE-

Re: No KODI for buster?

[Jonathan Dowland]

On Mon, Nov 13, 2017 at 01:17:23PM +0900, Man_without_clue wrote:

oh,  ok, thank you.

Hope it will be back soon.


THe root issue  that needs fixing is this one
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853485

Which has apparently been fixed in a package upload to experimental. So
Kodi should be unblocked once the maintainer makes a normal upload to
unstable.

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: Debian 8 and Debian 9 Dual Boot

[Roberto C . Sánchez]

On Sun, Nov 12, 2017 at 10:27:36PM -0500, Dan Norton wrote:
> My first Linux install was about one year ago. After some missteps, I have
> used Debian 8 in reasonable satisfaction on the desktop during that year.
> Now I want to leave 8 in place and do a network install for Debian 9 on the
> same disk and switch back and forth at boot time.
> 
If you use a desktop environment (e.g., GNOME or KDE) and want to share
the /home directory between both installations, you might encounter some
problems.  In particular, the desktop environments are known for not
behaving well when a newer version updates all the user-specific files
and then an older version tries to access them.

For example, the first time you boot to Debian 9 and log in (assume
GNOME for moment), files under ~/.config, ~/.gnome*, and possibly other
places will be modified by the new version of GNOME in Debian 9.  There
is no guarantee that when you go back to Debian 8 that the version of
GNOME there will cope will at all with the changed files under ~/.config
and ~/.gnome*.  In fact, it is quite likely that it will encounter some
sort of significant problem.

Your safest bet if you really intend to dual-boot in this way is to have
separate /home directories for each install and then use something like
/data to mount into both installations in order to share documents and
data between sessions.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[Richard Owlett]

On 11/13/2017 12:06 AM, Dan Hitt wrote:

On Sun, Nov 12, 2017 at 8:50 PM, Richard Owlett  wrote:

On 11/12/2017 09:45 PM, Dan Hitt wrote:


I have some DFTs that i wish to inspect.  (Apparently DFT is a common
acronym, but here i mean Discrete Fourier Transform.  And properly
speaking it doesn't make sense to inspect a transform, but only to
inspect transformed data, but i'm speaking colloquially.)

DFTs are a common artifact in digital signal processing.  Lots of
Debian packages are focused on FFTs (Fast Fourier Transforms, a way of
computing DFTs).  Nevertheless i couldn't find either a standard file
format to store one, or software specifically for viewing DFTs.

Of course, lots of software can take data, then transform it, then
display the transform that it created, but i would like something that
can take an already created DFT in some standard format, then display
it.

TIA for any information or pointers or advice from anybody! :)

dan




A useful set of expertise is available at the USENET group at comp.dsp .
HTH


Thanks Richard.

Maybe you're exactly right, because if i can find any free software
that's relevant to what i want, then i can probably get it to Debian.
(If i have something specific, then can bring it up here in fact if i
have trouble installing it.)


I know there are Ubuntu users on that list as one pointed me in that 
direction when I escaped Windows. That's how I found Debian ;}




How do you normally access usenet?


As a former Netscape user, I find SeaMonkey comfortable 
[http://www.seamonkey-project.org/]




In the old days (meaning, decades ago) i used to read usenet with rn.

I suppose a modern equivalent would be google groups, but if i do get
back in the usenet scene, i'm wondering if there's a more
command-liney thing or just other alternatives to consider before
walking down the google trail.


I avoid Google!
For a free news server I have used http://www.aioe.org/ .
I currently use a paid service, https://www.supernews.com/ .



Anyhow, whether or not you have an answer about the best way to go to
usenet, i appreciate the suggestion because that group (comp.dsp) is
probably where i can find what i'm looking for if it exists at all.


The group is composed primarily of those using DSP on a daily basis.



dan

Re: No KODI for buster?

[A_Man_Without_Clue]

On 11/13/2017 07:38 PM, Jonathan Dowland wrote:
> On Mon, Nov 13, 2017 at 01:17:23PM +0900, Man_without_clue wrote:
>> oh,  ok, thank you.
>>
>> Hope it will be back soon.
> 
> THe root issue  that needs fixing is this one
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853485
> 
> Which has apparently been fixed in a package upload to experimental. So
> Kodi should be unblocked once the maintainer makes a normal upload to
> unstable.
> 


Great. I will wait.

Thanks for info.

Re: No KODI for buster?

[A_Man_Without_Clue]

On 11/13/2017 06:00 PM, Floris wrote:
> Op Mon, 13 Nov 2017 01:51:17 +0100 schreef Man_without_clue
> :
> 
>> Hi all,
>>
>> There is no KODI for the buster?
>>
>> How come?
>>
>>
> 
> If you are brave enough to try the deb-multimedia repo has Kodi:
> http://www.deb-multimedia.org/
> 
> Note: these packages can/will sometimes break your system or make an
> update impossible.
> 
> Floris
> 


NO, I will stay away from that.

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[Henning Follmann]

On Mon, Nov 13, 2017 at 05:49:42AM -0300, Eike Lantzsch wrote:
> On Sunday, November 12, 2017 10:06:11 PM -03 Dan Hitt wrote:
> > On Sun, Nov 12, 2017 at 8:50 PM, Richard Owlett  wrote:
> > > On 11/12/2017 09:45 PM, Dan Hitt wrote:
> > >> I have some DFTs that i wish to inspect.  (Apparently DFT is a common
> > >> acronym, but here i mean Discrete Fourier Transform.  And properly
> > >> speaking it doesn't make sense to inspect a transform, but only to
> > >> inspect transformed data, but i'm speaking colloquially.)
> > >> 
> > >> DFTs are a common artifact in digital signal processing.  Lots of
> > >> Debian packages are focused on FFTs (Fast Fourier Transforms, a way of
> > >> computing DFTs).  Nevertheless i couldn't find either a standard file
> > >> format to store one, or software specifically for viewing DFTs.
> > >> 
> > >> Of course, lots of software can take data, then transform it, then
> > >> display the transform that it created, but i would like something that
> > >> can take an already created DFT in some standard format, then display
> > >> it.
> > >> 
> > >> TIA for any information or pointers or advice from anybody! :)
> > >> 
> > >> dan
> > > 
> > > A useful set of expertise is available at the USENET group at comp.dsp .
> > > HTH
> > 
> > Thanks Richard.
> > 
> > Maybe you're exactly right, because if i can find any free software
> > that's relevant to what i want, then i can probably get it to Debian.
> > (If i have something specific, then can bring it up here in fact if i
> > have trouble installing it.)
> > 
> > How do you normally access usenet?
> > 
> > In the old days (meaning, decades ago) i used to read usenet with rn.
> ask for an account on (€10 per year)
> http://www.individual.net/
> install leafnode and slrn on Debian
> 

aioe.org has free access to usenet (if text only groups suffice).

-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[Henning Follmann]

On Sun, Nov 12, 2017 at 07:45:13PM -0800, Dan Hitt wrote:
> I have some DFTs that i wish to inspect.  (Apparently DFT is a common
> acronym, but here i mean Discrete Fourier Transform.  And properly
> speaking it doesn't make sense to inspect a transform, but only to
> inspect transformed data, but i'm speaking colloquially.)
> 
> DFTs are a common artifact in digital signal processing.  Lots of
> Debian packages are focused on FFTs (Fast Fourier Transforms, a way of
> computing DFTs).  Nevertheless i couldn't find either a standard file
> format to store one, or software specifically for viewing DFTs.
> 
> Of course, lots of software can take data, then transform it, then
> display the transform that it created, but i would like something that
> can take an already created DFT in some standard format, then display
> it.
> 
> TIA for any information or pointers or advice from anybody! :)
> 
> dan
> 

First things first: there is no special format for FT data.
Since mostly you deal with time series/sequential data any format should work.


To display that data any plotting program will do. 
gnuplot,
mathplot...

If you look for a easy integration into your transformation routines, I
suggest numpy/scipy which uses mathplot.

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 01:10 AM, David Christensen wrote:

On 11/12/17 19:27, Dan Norton wrote:
My first Linux install was about one year ago. After some missteps, I 
have used Debian 8 in reasonable satisfaction on the desktop during 
that year. Now I want to leave 8 in place and do a network install 
for Debian 9 on the same disk and switch back and forth at boot time.


I think your best bet is to migrate from Debian 8 to Debian 9:

1.  Image, backup, and/or archive everything.  You will especially 
want to get a copy of the /etc tree onto a USB flash drive so you can 
see LVM, fstab, etc., configuration settings for mounting the Debian 8 
disk under Debian 9.


Please say more about the configuration settings. I back up /home and 
/var. The git stuff is in /opt and pushed to GitHub. Should the /etc 
tree be backed up also? How would the settings be used from 9?




2.  Put your bulk data onto a separate drive or a file server/ NAS.

3.  If your computer has a spare drive bay, buy a new drive, unplug 
your old drive, install the new drive, install Debian 9 onto the new 
drive, reconnect the old drive and mount read-only under Debian 9, and 
migrate your settings and remaining data from the old drive to the new 
drive. Your BIOS/UEFI should allow you to boot from either drive 
during this process.  So long as you don't damage the Debian 8 disk, 
you can always fall back to Debian 8 if the migration goes badly.


4.  If you computer does not have a spare drive bay, buy a new drive 
and a USB external drive enclosure, put your old drive in the 
enclosure, install the new drive, install Debian 9 onto the new drive, 
plug in the old drive and mount read-only under Debian 9, and migrate 
your settings and remaining data from the old drive to the new drive.  
Again, your BIOS/UEFI should allow you to boot from either drive and 
you can fall back to Debian 8 if necessary.


Sobering advice - good! Makes me re-think some things. A bit inefficient 
WRT disk space.

You did say "migrate" and not "upgrade" as I first read. Thanks David.

 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 03:53 AM, Jochen Spieker wrote:

Dan Norton:
henny|i

My first Linux install was about one year ago. After some missteps, I have
used Debian 8 in reasonable satisfaction on the desktop during that year.
Now I want to leave 8 in place and do a network install for Debian 9 on the
same disk and switch back and forth at boot time.

Your disk setup allows to do this comparably easy, but I would think
twice whether that is actually what I want to do. You end up with two
systems which you have to maintain and, most importantly, you cannot
properly share your /home. Most programs that save their settings to
$HOME will automatically upgrade their configuration files on first
start with a new version and after that you have to assume that the
older version cannot read it anymore. I realize that this is part of
your disk space calculation but I want to stress that the result is
probably not something that you will want to use for an extended period
of time.


Indeed, I had thought to have 9 with a complete set of partitions as if 
8 didn't exist, but I did not say so.





LVM reports as follows:

dan@debian:/$ sudo vgdisplay -C
   VG   #PV #LV #SN AttrVSize  VFree
   debian-vg   1 5 0wz--n- 976.56g 938.20g

You can vgreduce debian-vg easily to make room for your planned
debian9-vg.


So this must mean that VFree above is bound to debian-vg currently. I 
had not recognized the need to vgreduce. Thanks.





So there is plenty of disk space for the two Debians and more besides. The
question is how to prepare to install 9? My guess is to define another
volume group called debian9-vg perhaps but how will this be recognized
during network install?

Yes, it will. It should also be possible to vgreduce debian.vg and
vgcreate debian9-vg inside the installer, but I would be more
comfortable doing that from the running system, using the regular tools.


For sure. Trying to do things within the installer has been the source 
of a lot of my problems.




During installation, you just have to make sure that all LVs in
debian-vg are marked as "Do not use".


Good. This is the kind of information I need.




I've clobbered stuff before during installs and I'm
gun shy. Maybe there is a better way. Any thoughts on this will be
appreciated.

It happens to everybody. The only things that help are a good plan and
concentration on the task at hand. :)


+1 and thank you, Jochen.

 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 06:56 AM, Roberto C. Sánchez wrote:

On Sun, Nov 12, 2017 at 10:27:36PM -0500, Dan Norton wrote:

My first Linux install was about one year ago. After some missteps, I have
used Debian 8 in reasonable satisfaction on the desktop during that year.
Now I want to leave 8 in place and do a network install for Debian 9 on the
same disk and switch back and forth at boot time.


If you use a desktop environment (e.g., GNOME or KDE) and want to share
the /home directory between both installations, you might encounter some
problems.  In particular, the desktop environments are known for not
behaving well when a newer version updates all the user-specific files
and then an older version tries to access them.


Xfce is what I use and it would surely encounter the same kinds of problems.



For example, the first time you boot to Debian 9 and log in (assume
GNOME for moment), files under ~/.config, ~/.gnome*, and possibly other
places will be modified by the new version of GNOME in Debian 9.  There
is no guarantee that when you go back to Debian 8 that the version of
GNOME there will cope will at all with the changed files under ~/.config
and ~/.gnome*.  In fact, it is quite likely that it will encounter some
sort of significant problem.

Your safest bet if you really intend to dual-boot in this way is to have
separate /home directories for each install and then use something like
/data to mount into both installations in order to share documents and
data between sessions.


Although I didn't say so, each install would have its own set of 
directories. Please say more about how to mount the other installation 
and share data. How to mount things in another volume group?


Thanks, Roberto.

 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[Roberto C . Sánchez]

On Mon, Nov 13, 2017 at 11:01:27AM -0500, Dan Norton wrote:
> 
> Although I didn't say so, each install would have its own set of
> directories. Please say more about how to mount the other installation and
> share data. How to mount things in another volume group?
> 
That would be as simple as creating a logical volume, call it "data,"
and then configuring it to mount in each installation with a line in
/etc/fstab:

/dev/vg00/data /data .

Since you are talking about installing more than one version of Debian
and switching back and forth between them I assume that you are the only
user of the machine.  You would need to make sure that the assigned user
ID for your username matches in both installations and then just make
sure that /data has the appropriate permissions for your user account to
be able to write to it.

This is generally preferrable to directly mounting directories of the
other installation just to share data, as the dedicated data sharing
directory approach reduces the likelihood that a mistake will cause
problems in the other installation.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 11:07 AM, Roberto C. Sánchez wrote:

On Mon, Nov 13, 2017 at 11:01:27AM -0500, Dan Norton wrote:

Although I didn't say so, each install would have its own set of
directories. Please say more about how to mount the other installation and
share data. How to mount things in another volume group?


That would be as simple as creating a logical volume, call it "data,"
and then configuring it to mount in each installation with a line in
/etc/fstab:

/dev/vg00/data /data .
Ah. OK. If each installation is in its own volume group, then vg00 above 
would be replaced with the actual vg.


Since you are talking about installing more than one version of Debian
and switching back and forth between them I assume that you are the only
user of the machine.

Yes.

You would need to make sure that the assigned user
ID for your username matches in both installations and then just make
sure that /data has the appropriate permissions for your user account to
be able to write to it.

OK.


This is generally preferrable to directly mounting directories of the
other installation just to share data, as the dedicated data sharing
directory approach reduces the likelihood that a mistake will cause
problems in the other installation.

Great. If there's a mistake to be made ...

Thanks, Roberto.

 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[Joe]

On Mon, 13 Nov 2017 11:01:27 -0500
Dan Norton  wrote:


> Although I didn't say so, each install would have its own set of 
> directories. Please say more about how to mount the other
> installation and share data. How to mount things in another volume
> group?
> 

Good advice so far, but to add a bit: all LVM groups will be seen at
boot, and /dev will know about them. See man lvm2 and also here:

https://wiki.debian.org/LVM  for complete information about the
commands you have available. There are also numerous tutorials on the
Net which show basic usage of the simpler commands. It's worth having a
look when you have some spare time, as one day you'll need to know some
of this and won't have any spare time.

Look in /etc/fstab for lines beginning /dev/mapper/[volume] which will
be the volumes mounted in the running installation. The 'mapper' is
turning LVM volumes into things which look like partitions for many
purposes.

To mount the volumes in the non-running installation, you need to add
similar-looking lines to fstab, and don't forget to create directories
somewhere quiet, like /mnt, to mount them on. You will need to add an
option to the entries that the running mounts do not have: if you
don't, systemd will try to mount them on boot, and if it fails, will
abort the boot. No problem if the extra mounts are on a drive that is
always there, but if stored on a second drive which is later removed,
it will kill the machine.

So you want either the option noauto, which tells systemd to ignore the
volume and you will always mount it manually (just mount 
in a terminal will do that, the fstab entry will have all the options
needed), or x-systemd.automount which will also be ignored during boot
but will be automounted when you try to access it. I mount my network
shares with that option, for the same reason (losing one will only put
a huge timeout into boot, but won't actually abort it) and also so that
mounting them will not slow down booting.

Here are a couple of spare LVM volumes on my workstation, one of which I
use only occasionally and always mount manually. You might notice that
the automount point is called oldroot, guess what that is...

/dev/mapper/newerlvm-spare  /mnt/spare  ext4  rw,user,noauto  0  0
/dev/mapper/newlvm-root  /mnt/oldroot  ext4  rw,user,x-systemd.automount
0 0

If you do mount the non-running system root, which is convenient for
many purposes, do be especially careful where you are in the directory
tree. The directories will look very similar, and it is easy to
misconfigure the wrong system. Years ago, I copied a system to a second
drive, then went into it to adjust the /etc/fstab to the new values it
needed. I managed to edit the wrong fstab, and neither system would
boot... fortunately, that was an easy one to fix.

So yes, it is safer only to mount the data of the other installation,
at least once you have the new one working properly and have duplicated
what you want from the old one.

-- 
Joe

Re: Debian 8 and Debian 9 Dual Boot

[Felix Miata]

Dan Norton composed on 2017-11-13 10:26 (UTC-0500):

> David Christensen wrote:

>> Dan Norton wrote:

>>> My first Linux install was about one year ago. After some missteps, I 
>>> have used Debian 8 in reasonable satisfaction on the desktop during 
>>> that year. Now I want to leave 8 in place and do a network install 
>>> for Debian 9 on the same disk and switch back and forth at boot time.

>> I think your best bet is to migrate from Debian 8 to Debian 9:

>> 1.  Image, backup, and/or archive everything.  You will especially 
>> want to get a copy of the /etc tree onto a USB flash drive so you can 
>> see LVM, fstab, etc., configuration settings for mounting the Debian 8 
>> disk under Debian 9.

> Please say more about the configuration settings.

All my machines are multiboot. Few have as few as 4 operating system
installations, most have more than 12, and most of those not running RAID use
only one disk.

There's no need for separate home file systems to keep one installation from
causing corruption to another's user settings. Simply do not reuse UIDs[1].

On your first, your Jessie probably has a user dan with UID 1000. On the next,
don't use 1000 for user dan. Pick any other number, e.g. 1200 for user dan in
Stretch. During Stretch installation make the initial user dan8 or dan01 using
Jessie's UID (probably 1000) for dan.

In Jessie, create a new user dan2 or dan09 using the UID you picked for Stretch.

Booted to either, the homedir of the other can optionally be bind mounted as a
subdir of the current dan for more convenient data access without interference
with settings of the other. Either way you boot, you'll be user "dan", but
without risk of settings corruption.

[1] https://en.wikipedia.org/wiki/User_identifier
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debian 8 and Debian 9 Dual Boot

[David Christensen]

On 11/13/17 07:26, Dan Norton wrote:


On 11/13/2017 01:10 AM, David Christensen wrote:


1.  Image, backup, and/or archive everything.  You will especially 
want to get a copy of the /etc tree onto a USB flash drive so you can 
see LVM, fstab, etc., configuration settings for mounting the Debian 8 
disk under Debian 9.


Please say more about the configuration settings. I back up /home and 
/var. The git stuff is in /opt and pushed to GitHub. Should the /etc 
tree be backed up also? How would the settings be used from 9?


Every operating system and every software application installed on that 
operating system has configuration settings.  One of the advantages of 
the traditional Unix model is that most OS settings are in plain text 
files that you can change with a text editor.  Similarly so for server 
applications.  (Desktops and their applications are another story, see 
below.)  Good software has manual pages that explain where its 
configuration files reside and the format and meaning of the contents. 
Debian and Debian-ized applications seem to put most of their 
configuration files under /etc.



Whenever I decide to change such files, I make a copy with '-orig' 
appended, put the original file into a version control system (CVS), 
edit-test-repeat, and check-in to CVS when done.  On a typical 
workstation, I might have a dozen files under /etc checked in.  On a 
server, more.



I once tried putting the entire /etc directory into CVS.  Adding and 
removing software made a lot of changes, as expected.  But, so did 
normal operations.  Locating meaningful changes in became an exercise in 
"find the needle in the hay stack".  And, adding/removing lots of files 
and directories in CVS working directories is labor intensive.  I don't 
do that any more.



For migrations, unless you are an expert already or psychic, you will 
want the old drive in it's entirety.  (I keep my system drives under 16 
GB, to encourage me to take images at opportune moments like this.) 
It's useful to also copy /etc onto a flash drive when your old drive is 
more complex than a partition table and normal file systems (so that you 
will have clues about how to mount it, for starters).



As for how the settings are used, each OS instance and it applications 
determine that.  Migrating settings involves editing configuration files 
and/or overwriting configuration files.  You have to go through each 
subsystem one at a time and see what configuration files it wants, 
format, and content, and then do what it takes to make it happy.



As others have replied, desktop and desktop application configuration 
settings and data in home directories are not agreeable to migration.  I 
don't even try.  I backup Thunderbird mail and export address books on 
the old system, and restore/ import on the new system.  I use the sync 
service built into Firefox to keep it current on all my machines where 
it is installed.  I check in my CVS working directories on the old 
system and check them out on the new system.  My bulk data is on the 
file server.  I manually configure whatever is left -- desktop, Open 
Office preferences, etc..




2.  Put your bulk data onto a separate drive or a file server/ NAS.

3.  If your computer has a spare drive bay, buy a new drive, unplug 
your old drive, install the new drive, install Debian 9 onto the new 
drive, reconnect the old drive and mount read-only under Debian 9, and 
migrate your settings and remaining data from the old drive to the new 
drive. Your BIOS/UEFI should allow you to boot from either drive 
during this process.  So long as you don't damage the Debian 8 disk, 
you can always fall back to Debian 8 if the migration goes badly.


4.  If you computer does not have a spare drive bay, buy a new drive 
and a USB external drive enclosure, put your old drive in the 
enclosure, install the new drive, install Debian 9 onto the new drive, 
plug in the old drive and mount read-only under Debian 9, and migrate 
your settings and remaining data from the old drive to the new drive. 
Again, your BIOS/UEFI should allow you to boot from either drive and 
you can fall back to Debian 8 if necessary.


Sobering advice - good! Makes me re-think some things. A bit inefficient 
WRT disk space.


Disk space is far cheaper than data loss.  Don't make the mistake of 
trying to save money through partition, LVM, file system, etc., 
gymnastics rather than simply buying another drive and doing it the KISS 
way.




You did say "migrate" and not "upgrade" as I first read. Thanks David.


YW.  :-)


David

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 02:08 PM, Felix Miata wrote:

Dan Norton composed on 2017-11-13 10:26 (UTC-0500):


David Christensen wrote:

Dan Norton wrote:

My first Linux install was about one year ago. After some missteps, I
have used Debian 8 in reasonable satisfaction on the desktop during
that year. Now I want to leave 8 in place and do a network install
for Debian 9 on the same disk and switch back and forth at boot time.

I think your best bet is to migrate from Debian 8 to Debian 9:
1.  Image, backup, and/or archive everything.  You will especially
want to get a copy of the /etc tree onto a USB flash drive so you can
see LVM, fstab, etc., configuration settings for mounting the Debian 8
disk under Debian 9.

Please say more about the configuration settings.

All my machines are multiboot. Few have as few as 4 operating system
installations, most have more than 12, and most of those not running RAID use
only one disk.


Excellent. You have my undivided attention :-)


There's no need for separate home file systems to keep one installation from
causing corruption to another's user settings. Simply do not reuse UIDs[1].

On your first, your Jessie probably has a user dan with UID 1000. On the next,
don't use 1000 for user dan. Pick any other number, e.g. 1200 for user dan in
Stretch. During Stretch installation make the initial user dan8 or dan01 using
Jessie's UID (probably 1000) for dan.

In Jessie, create a new user dan2 or dan09 using the UID you picked for Stretch.


Interesting.



Booted to either, the homedir of the other can optionally be bind mounted as a
subdir of the current dan for more convenient data access without interference
with settings of the other. Either way you boot, you'll be user "dan", but
without risk of settings corruption.
[1] https://en.wikipedia.org/wiki/User_identifier


I'm going to study this and I may have questions later.

Thanks, Felix

 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[Jochen Spieker]

Dan Norton:
> On 11/13/2017 03:53 AM, Jochen Spieker wrote:
>> Dan Norton:
>> 
>>> LVM reports as follows:
>>> 
>>> dan@debian:/$ sudo vgdisplay -C
>>>VG   #PV #LV #SN AttrVSize  VFree
>>>debian-vg   1 5 0wz--n- 976.56g 938.20g
>>
>> You can vgreduce debian-vg easily to make room for your planned
>> debian9-vg.
> 
> So this must mean that VFree above is bound to debian-vg currently. I had
> not recognized the need to vgreduce. Thanks.

Good that you didn't, because I just noticed I was wrong. :) vgreduce is
only for removing physical volumes from a volume group.

It never occured to me before, but I think each physical volume can only
belong to exactly one volume group. That means if you want to use
separate volume groups you would need to pvresize (shrink) the physical
volume. I have never actually done this (only enlarged PVs).

I would probably accept that this is not easily possible with the
current layout and just use one VG. You do not gain much by separate
volume groups anyway.

J.
-- 
If I could travel in time I would show my minidisc to the Romans and
become Caesar until the batteries ran out.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: Re: Compatible laptops

[dekks herton]

On 11/12, Joe wrote:

On Mon, 13 Nov 2017 08:55:51 +1100
Charlie S  wrote:


On Sun, 12 Nov 2017 13:23:46 + dekkz...@gmail.com sent:

> On 11/12, rhkra...@gmail.com wrote:
> >On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote:
> >> in general - any modern laptop will run debian fine [with any DE
> >> you choose] with IMO the following caveats
> >>
> >> 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka
> >> optimus 2) Avoid anything realtek
> >
> >I'd add, "avoid Broadcom if you want to use WiFi"--it requires some
> >extra steps for installation (and is even more of a pain until you
> >realize that is what you need to do)"
>
> Until the last 18 months i would have agreed but they hired one of
> the leading kernal gfx hackers and now forced by the Pi market are
> supporting newer stuff. Enough to come off my black list, however
> i'm keeping an eye on them to see if they relapse.
>

After contemplation, my reply is:

On an older Toshiba laptop I was given, mine starting to show signs of
faults after 10 years work. I had a bit of trouble getting Broadcom
WI-FI to work and had to take a couple of runs at it to get the
desired result. That could have been because my expectation was, it
would be straight forward. So probably my fault.



It might be worth a reminder at this point that a particular 'model' of
laptop (or other form) generally represents a desired set of
capabilities, and the actual hardware may vary from time to time. It is
necessary to go down to the level of all the letters on the end of the
model name, or even an SKU designation if provided, to be sure that a
particular laptop exactly complies with a published specification.


So true, hence why i like working with Thinkpads, it's easy to get a detailed 
build manifest from the part number.




For example, an HP laptop bought by a colleague of mine about six
months after I had bought the 'same' model has a separate numeric keypad
and mine doesn't.

--
Joe



signature.asc
Description: PGP signature

Re: Re: KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43

[Ramon Hofer]

Dear Alexander,

Thank you very much for your reply.

> > The system I am using:
> > lshw: https://pastebin.com/tB7FqqxN
> >
> > Host OS:Debian 9 Stretch
> > Mainboard: Supermicro C7Z170-M (activated VT-d in Bios)
> > CPU: Intel Core i7-7700K CPU @ 4.20GHz
> > GPU: EVGA GeForce GTX1080 Ti
> >
> > The GPU is not listed because I have blacklisted it:
> > $ cat /etc/modprobe.d/blacklist.conf 
> > blacklist nouveau
> >
> > lspci: https://pastebin.com/6qYuJRPg
> >
> > I found this guide:
> > https://scottlinux.com/2016/08/28/gpu-passthrough-with-kvm-and-debian-linux/
> >
> > After installing Win7 guest, enabling PCI passthrough using
> > virt-manager, installing the NVidia driver in the guest, Windows
> > reports the error 43 for the GPU.
> > 
> > Windows has stopped this device because it has reported problems.
> > (Code 43)
> >
> > This is described in the above mentioned post and a workaround is
> > linked:
> > https://www.reddit.com/r/VFIO/comments/479xnx/guests_with_nvidia_gpus_can_enable_hyperv/
> >
> > Unfortunately I do not know how to apply the workaround. I
> > understand
> > that I should create a file '/usr/libexec/qemu-kvm-hv-vendor' with
> > the
> > following content:
> >
> > #!/bin/sh
> > exec /usr/bin/qemu-kvm \
> > `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=whatever|g'`
> >
> > Or according to the original redhat mailing list post by Alex
> > Williamson:
> > https://www.redhat.com/archives/vfio-users/2016-March/msg00092.html
> >
> > $ cat /usr/libexec/qemu-kvm-hv-vendor 
> > #!/bin/sh
> > exec /usr/bin/qemu-kvm \
> > `echo "\$@" | sed
> > 's|hv_time|hv_time,hv_vendor_id=KeenlyKVM|g'`
> >
> > But since there is no qemu-kvm present and the directory
> > '/usr/libexec' does not exist on my system, I wonder how I should
> > proceed.
> 
> This is interesting topic and I hope to find some time to spare to
> implement and test this setup on my system. Can't suggest you anything
> yet, because this "Code 43" error is generic and can happen even on
> normal systems. The reasons could be limitless from driver version
> conflict to bios\uefi firmware bug of your motherboard. I wonder, what
> VEN_ID and DEV_ID are reported for your VGA in Windows guest? Have you
> tried Windows 8.1 or 10 as guests? They could have more support for
> virtualization in general.

Interesting. I thought I was just not able to setup KVM / QEMU
properly. Because I read and heard that NVidia deliberately switches
the card off when the driver detects that it is virtualised.

I am using the newest BIOS version (updated on Sunday) on the
motherboard: 
Supermicro C7Z170-M
BIOS Version: 2.0a
BIOS Tag: 1088B
Date: 07/17/2017
Time: 15:51:37

Unfortunately I do not know anything about a bioy\uefi firmware bug. Is
this a known issue of my mainboard version?

In the BIOS for the "Boot mode select" setting, I have chosen
"Legacy" (there would also be "UEFI" or "DUAL"). Do you think it might
be worth trying to change it to the other two?

I have uploaded dmesg output if it helps:
dmesg: https://pastebin.com/79Us7WMf

In the Windows 7 guest, the reported IDs are:
VEN_ID: 10DE
DEV_ID: 1B06

The driver version in the Windows 7 guest is:
23.21.13.8813 (Date: 27.10.2017)

I have thought about buying a Windows 10 copy, but it is not possible
to get the direct download version in Switzerland, so I postponed the
purchase due to lack of patience.

But if it helps, here is the information from a Debian 9 guest with the
nvidia-driver package installed: 
ID: 10de:1b06
VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1b06]
(rev a1)

This is also what nvidia-detect says:
$ sudo nvidia-detect 
Detected NVIDIA GPUs:
00:09.0 VGA compatible controller [0300]: NVIDIA Corporation Device
[10de:1b06] (rev a1)

Checking card:  NVIDIA Corporation Device 1b06 (rev a1)
Your card is supported by the default drivers.
It is recommended to install the
nvidia-driver
package.

So I installed nvidia-driver and rebooted the Debian 9 guest.
The display setting in XFCE4 still does not show the NVidia card and
the nvidia-setting program reports that I should run nvidia-xconfig as
root, which I did.
This is the resulting config file:
xorg.conf: https://pastebin.com/sCe30emi

Unfortunately lightdm fails to start. Here is the suggested log:
systemctl status lightdm.service: https://pastebin.com/VYgKuCy1

Since there is not much information in that log I have created a
pastebin for dmesg of the failed Debian 9 guest boot attempt:
dmesg for lightdm fail: https://pastebin.com/Djx2YycH


I am not sure if I can still get a copy of Windows 8 somewhere, but if
you think it helps, I can go an buy Windows 10.
Please let me know how I can help you helping me :-)

The problem got me thinking yesterday and today I asked around if
anybody wants the card and if I should buy an AMD GPU. But since my
card came with a pre-installed water block no potential buyer could be
found...


Thank you again and best regards,
Ramon

Re: KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43

[Alexander V. Makartsev]

On 14.11.2017 02:37, Ramon Hofer wrote:
> Dear Alexander,
>
> Thank you very much for your reply.
> Interesting. I thought I was just not able to setup KVM / QEMU
> properly. Because I read and heard that NVidia deliberately switches
> the card off when the driver detects that it is virtualised.
>
> I am using the newest BIOS version (updated on Sunday) on the
> motherboard: 
> Supermicro C7Z170-M
> BIOS Version: 2.0a
> BIOS Tag: 1088B
> Date: 07/17/2017
> Time: 15:51:37
>
> Unfortunately I do not know anything about a bioy\uefi firmware bug. Is
> this a known issue of my mainboard version?
>
> In the BIOS for the "Boot mode select" setting, I have chosen
> "Legacy" (there would also be "UEFI" or "DUAL"). Do you think it might
> be worth trying to change it to the other two?
I can't tell for sure if it will help. Basically, you have to enable
VT-d, IOMMU in BIOS and stick with it.
Updated BIOS is great because this at least removes one thing from the
equation.
You can check if all features of QEMU are enabled on your host by typing:
    $ virt-host-validate

> I have uploaded dmesg output if it helps:
> dmesg: https://pastebin.com/79Us7WMf
>
> In the Windows 7 guest, the reported IDs are:
> VEN_ID: 10DE
> DEV_ID: 1B06
>
> The driver version in the Windows 7 guest is:
> 23.21.13.8813 (Date: 27.10.2017)
>
I'd try different versions of nVidia drivers, not only most recent one
and perform clean install of the drivers.
> I have thought about buying a Windows 10 copy, but it is not possible
> to get the direct download version in Switzerland, so I postponed the
> purchase due to lack of patience.
>
> I am not sure if I can still get a copy of Windows 8 somewhere, but if
> you think it helps, I can go an buy Windows 10.
> Please let me know how I can help you helping me :-)
You can download and try Windows 10 for free and play with it for a
90-days trial period. Get the regular one, not LTSB.
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise
Might be your best bet to try KVM with Windows 10 guest without spending
any money.
> The problem got me thinking yesterday and today I asked around if
> anybody wants the card and if I should buy an AMD GPU. But since my
> card came with a pre-installed water block no potential buyer could be
> found...
>
>
> Thank you again and best regards,
> Ramon

-- 

With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 02:08 PM, Felix Miata wrote:

Dan Norton composed on 2017-11-13 10:26 (UTC-0500):


David Christensen wrote:

Dan Norton wrote:

My first Linux install was about one year ago. After some missteps, I
have used Debian 8 in reasonable satisfaction on the desktop during
that year. Now I want to leave 8 in place and do a network install
for Debian 9 on the same disk and switch back and forth at boot time.

I think your best bet is to migrate from Debian 8 to Debian 9:
1.  Image, backup, and/or archive everything.  You will especially
want to get a copy of the /etc tree onto a USB flash drive so you can
see LVM, fstab, etc., configuration settings for mounting the Debian 8
disk under Debian 9.

Please say more about the configuration settings.

All my machines are multiboot. Few have as few as 4 operating system
installations, most have more than 12, and most of those not running RAID use
only one disk.

There's no need for separate home file systems to keep one installation from
causing corruption to another's user settings. Simply do not reuse UIDs[1].

On your first, your Jessie probably has a user dan with UID 1000. On the next,
don't use 1000 for user dan. Pick any other number, e.g. 1200 for user dan in
Stretch. During Stretch installation make the initial user dan8 or dan01 using
Jessie's UID (probably 1000) for dan.


Do you pick a UID during install somehow or do you login as root before 
anything else and edit /etc/passwd?


 - Dan


In Jessie, create a new user dan2 or dan09 using the UID you picked for Stretch.

Booted to either, the homedir of the other can optionally be bind mounted as a
subdir of the current dan for more convenient data access without interference
with settings of the other. Either way you boot, you'll be user "dan", but
without risk of settings corruption.

[1] https://en.wikipedia.org/wiki/User_identifier

Re: KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43

[Ramon Hofer]

Dear Adam,

On Mon, 13 Nov 2017 22:49:02 +0100
Adam Cécile  wrote:

> Here is my notes/scripts when I did that to attach an nvidia card
> inside a KVM virtual machine:
> https://github.com/eLvErDe/nvidia-docker-cuda-kvm-with-passthru/blob/master/create-kvm-for-nvidia-docker.sh

Thank you very much for your script.

Since I am new to virtualisation and a bit a purist, I hoped to not use
docker or at least understand why I should use it.
Could you please tell a word or two about it?
Is it only because of the workaround you mention in the script?

With your script I have successfully created a VM and installed
nvidia-detect but it reports:
# nvidia-detect 
Detected NVIDIA GPUs:
00:04.0 VGA compatible controller [0300]: NVIDIA Corporation Device
[10de:1b06] (rev a1) Uh oh. Your card is not supported by any driver
version up to 340.102. A newer driver may add support for your card.
Newer driver releases may be available in backports, unstable or
experimental.

I hope to have time to do further tests tomorrow by changing your
script to use Debian 9 and its newer drivers.


Thanky again and best regards,
Ramon

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 02:14 PM, David Christensen wrote:

[...]
Disk space is far cheaper than data loss.  Don't make the mistake of 
trying to save money through partition, LVM, file system, etc., 
gymnastics rather than simply buying another drive and doing it the 
KISS way.




Well I'm much in favor of the KISS principle, it's just that there is 
too much PC equipment lying around here doing nothing. I haul away, 
donate from time to time but it simply accumulates. I hate the thought 
of buying more when there is 900g unused on sda. :-)


 - Dan

Re: Debian 8 and Debian 9 Dual Boot

[David Christensen]

On 11/13/17 15:27, Dan Norton wrote:



On 11/13/2017 02:14 PM, David Christensen wrote:

[...]
Disk space is far cheaper than data loss.  Don't make the mistake of 
trying to save money through partition, LVM, file system, etc., 
gymnastics rather than simply buying another drive and doing it the 
KISS way.




Well I'm much in favor of the KISS principle, it's just that there is 
too much PC equipment lying around here doing nothing. I haul away, 
donate from time to time but it simply accumulates. I hate the thought 
of buying more when there is 900g unused on sda. :-)


So, a 1 TB drive?  Make and model?

Laptop, desktop, server, other?  Make and model?

Any spare drive bays?

Do you have any 16 ~ 128 GB HDD's or SSD's lying around?

David

Re: KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43

[Ramon Hofer]

Dear Adam,

On Mon, 13 Nov 2017 22:49:02 +0100
Adam Cécile  wrote:

> Here is my notes/scripts when I did that to attach an nvidia card
> inside a KVM virtual machine:
> https://github.com/eLvErDe/nvidia-docker-cuda-kvm-with-passthru/blob/master/create-kvm-for-nvidia-docker.sh

I rembered that I can just upgrade to Stretch the usual way by changing
the sources.list files.
Unfortunately it is exactly the same as what I described in my prvious
email to Alexander. I could install and configure the driver but
startxfce4 does not start.

startxfce4: https://pastebin.com/0MeCU492

xorg.conf: https://pastebin.com/a4qGhsxz

Maybe I do not startxfce4 correctly?
Do I need to change xorg.conf?
Or is there any way to check if the driver works in the guest?


Thanks again for your help.


Best regards,
Ramon

Re: Debian 8 and Debian 9 Dual Boot

[Felix Miata]

Dan Norton composed on 2017-11-13 18:04 (UTC-0500):

> Felix Miata wrote:

>> There's no need for separate home file systems to keep one installation from
>> causing corruption to another's user settings. Simply do not reuse UIDs[1].

>> On your first, your Jessie probably has a user dan with UID 1000. On the 
>> next,
>> don't use 1000 for user dan. Pick any other number, e.g. 1200 for user dan in
>> Stretch. During Stretch installation make the initial user dan8 or dan01 
>> using
>> Jessie's UID (probably 1000) for dan.

> Do you pick a UID during install somehow or do you login as root before 
> anything else and edit /etc/passwd?

I could have been clearer. "During installation" isn't necessarily the correct
time for user management. I don't remember whether Stretch forces ordinary user
creation at installation time, or leaves it up to the admin to do when he 
chooses.

With installers that force creation of an ordinary user in addition to providing
a root password, or that don't permit UID selection for an ordinary user, create
a throwaway user. On first boot after installation, login as root and use ls -n,
groupadd, useradd, userdel, etc. to delete the throwaway, and manage users as
you wish. Editing /etc/passwd should not be necessary, but is an option
available to the adventurous.

>> In Jessie, create a new user dan2 or dan09 using the UID you picked for 
>> Stretch.

>> Booted to either, the homedir of the other can optionally be bind mounted as 
>> a
>> subdir of the current dan for more convenient data access without 
>> interference
>> with settings of the other. Either way you boot, you'll be user "dan", but
>> without risk of settings corruption.

>> [1] https://en.wikipedia.org/wiki/User_identifier-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 07:42 PM, Felix Miata wrote:

Dan Norton composed on 2017-11-13 18:04 (UTC-0500):


Felix Miata wrote:

There's no need for separate home file systems to keep one installation from
causing corruption to another's user settings. Simply do not reuse UIDs[1].
On your first, your Jessie probably has a user dan with UID 1000. On the next,
don't use 1000 for user dan. Pick any other number, e.g. 1200 for user dan in
Stretch. During Stretch installation make the initial user dan8 or dan01 using
Jessie's UID (probably 1000) for dan.

Do you pick a UID during install somehow or do you login as root before
anything else and edit /etc/passwd?

I could have been clearer. "During installation" isn't necessarily the correct
time for user management. I don't remember whether Stretch forces ordinary user
creation at installation time, or leaves it up to the admin to do when he 
chooses.

With installers that force creation of an ordinary user in addition to providing
a root password, or that don't permit UID selection for an ordinary user, create
a throwaway user. On first boot after installation, login as root and use ls -n,
groupadd, useradd, userdel, etc. to delete the throwaway, and manage users as
you wish. Editing /etc/passwd should not be necessary, but is an option
available to the adventurous.


Gee, I had it bracketed :-)
I'll gladly refrain from editing /etc/passwd thank you.

How do you set up LVM so that install does not clobber one of the 
siblings? During installation, for partitioning, do you pick "Manual" or 
"Guided -*" ?


 - Dan



In Jessie, create a new user dan2 or dan09 using the UID you picked for Stretch.
Booted to either, the homedir of the other can optionally be bind mounted as a
subdir of the current dan for more convenient data access without interference
with settings of the other. Either way you boot, you'll be user "dan", but
without risk of settings corruption.
[1] https://en.wikipedia.org/wiki/User_identifier--

"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Reproducible bug

[David Wright]

I'll have another go. This is getting tedious.

: host bendel.debian.org[82.195.75.100] said: 550
5.7.1 : Recipient address rejected: Mail
appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct
HELO and DNS MX settings or to get removed from DNSBLs; please relay via
your ISP (lionunicorn.co.uk) (in reply to RCPT TO command)



On Sun 12 Nov 2017 at 20:53:23 (+0100), Laurent Lyaudet wrote:
> Hello,
> 
> Well, find behavior and hidden files was not the intended topic of this
> thread ;)
> I do already know about Ctrl+H, ls -a, etc.
> And indeed my find command is incorrect since I forgot the dot or some
> wildcard at the beginning.
> After correction, I can say there is no .xsession-errors file on my system.
> The only matches were
> /usr/share/xsessions
> /etc/X11/Xsession.d/40x11-common_xsessionrc

There's nothing special about the filename .xsession-errors. On this
system, it's just the value of $ERRFILE, set in /etc/X11/Xsession.
But I don't run gnome, so I couldn't say what its startup files are
like. I can only assume that some sort of juggling goes on because
~/.xsession-errors belongs to the user who started the X server,
but (again I assume) a graphical system must start X before any user
has logged in through the (graphical) display manager.

So you might be better off using find to find files newer than,
say, 5 minutes old immediately after booting and logging in.

$ find ~ -mmin -5 -type f -print

> So yes, it may be strange if usually there is plenty of X session errors.
> 
> After googling, I looked at /var/log/messages with a lot of, well, messages
> that I didn't found interesting and related to my problem.
> I also looked at /var/log/gdm3/ but it was empty.
> 
> Regarding the boot errors, I have plenty of them as with any laptop I've
> seen running with Linux since laptops tend to have weird hardware.
> However, despite the same boot errors since I installed Debian on this
> laptop, the bug I'm talking in this thread was not present until a few
> weeks ago.

Someone mentioned network timeouts. Does this button/menu/whatever
do anything involving the network which could be stalled while
DHCP is doing its dirty work.

> I also forgot to say that soon after the bug started I found that hitting
> the super/windows/apple key works despite the click not working.
> And I already know some people out there will say "problem solved, he can
> put up with the bug".

Well that's at least a workaround, not a solution, assuming that what
"works" is the functionality you expected from clicking.

But if you want to chase down this bug, you might find a gnome list
more productive than this one, viz.

> > > someone else perhaps could help on where and how to debug gtk/gnome

Cheers,
David.

Re: Debian 8 and Debian 9 Dual Boot

[Felix Miata]

Dan Norton composed on 2017-11-13 21:38 (UTC-0500):

> How do you set up LVM so that install does not clobber one of the 
> siblings? During installation, for partitioning, do you pick "Manual" or 
> "Guided -*" ?

I don't think I've ever used Debian's, or any Debian derivative's, "guided". I
can't remember the last time I didn't pick manual, after *fully* preparing in
advance to my specifications.

Manual will list what partitions and volumes exist, so if you've fully prepared
logical volumes in advance, all that should need to be done within manual is
select mount points and mount options for those you wish used. If volumes exist
but are not formatted, then formatting would be a third selection using manual.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 11/13/2017 09:52 PM, Felix Miata wrote:

Dan Norton composed on 2017-11-13 21:38 (UTC-0500):


How do you set up LVM so that install does not clobber one of the
siblings? During installation, for partitioning, do you pick "Manual" or
"Guided -*" ?

I don't think I've ever used Debian's, or any Debian derivative's, "guided". I
can't remember the last time I didn't pick manual, after *fully* preparing in
advance to my specifications.

Manual will list what partitions and volumes exist, so if you've fully prepared
logical volumes in advance, all that should need to be done within manual is
select mount points and mount options for those you wish used. If volumes exist
but are not formatted, then formatting would be a third selection using manual.


OK, I may be able to do that. Thanks for your help.

 - Dan

Re: Discrete Fourier Transform (DFT) viewer and/or file format

[Dan Hitt]

On Mon, Nov 13, 2017 at 1:31 AM,   wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Sun, Nov 12, 2017 at 07:45:13PM -0800, Dan Hitt wrote:
>> I have some DFTs that i wish to inspect.  (Apparently DFT is a common
>> acronym, but here i mean Discrete Fourier Transform.  And properly
>> speaking it doesn't make sense to inspect a transform, but only to
>> inspect transformed data, but i'm speaking colloquially.)
>
> Uh, oh. To answer that without getting lost in Hilbert Space means
> consulting my (rusty) crystal ball :-)
>
> Now more seriously: what do you mean by "inspecting" a DFT?
>
> A DFT is just a trick to approximate a Fourier transform on an
> (approximate) function. Are you talking about one dimensional
> functions (e.g. a function of time) or two (three, etc.) dimensional
> functions? Their transforms are, correspondingly, one, two (and
> so on) dimensional functions, so the visualization techniques
> vary, depending on dimensionality and on the conventions current
> in the field (engineering, social sciences, maths, whatever).
>
> I'd recommend looking into some of the many (excellent) scientific
> packages having a visualization components, each one of which
> has a teeming community willing to help you.
>
> For three examples off the top of my head (all three packaged
> in Debian):
>
>   GNU Octave   https://www.gnu.org/software/octave/
>   NumPyhttp://www.numpy.org/
>   GNU Rhttps://www.r-project.org/
>
> The last one is touted as "statistical package", but let me tell
> you: all three are not only capable of visualizing (the result of)
> a discrete DFT, but all three can calculate one for you :-)
>
> Now if you are trying to visualize the result of a DFT on an image
> (a special two dimensional case, where you think of the discrete
> elements as of pixels), then perhaps a graphical package (e.g.
> The Gimp) is your friend. Also packaged in Debian.
>
> For more of those "scientific computing" packages, browsing this
>
>   https://wiki.debian.org/DebianScience
>
> might be of interest (or just drop "Debian scientific computing"
> into your favourite search engine, which hopefully ain't Google).
>
> Enjoy
>

Thanks Tomás, Richard, Eike, and Henning for your replies! :)

As for usenet, thanks for the leads on the various providers
(aeiou.net, individual.net, supernews.com).  I'm still pondering what
to do about that, but text-only groups are a plus imvho.

Tomás, you are right to question me about the dimension.  How could i
expect anybody to read my mind?

Now, although i'm curious about how multidimensional DFTs might be
stored, what i secretly had in mind was the 1d case.

And although under suitable conditions a DFT can approximate a Fourier
transform or series, i'd be content with just the case of inspecting
the transform of finitely many points without any reference to
limiting behavior.  (More about 'inspecting' below.)

And it is true that it has never been easier to take a DFT, at least a
1d one with packages like FFTW (which presumably is compiled into
numpy and octave, and maybe R?).

The actual problem i faced was that i had a long computation and deep
in the middle somewhere was a DFT, and my results made no sense.
Subsequently it turned out that i goofed on a factor of 2, so my
question is moot now, at least, until i get stuck the same way again.

But before i knew where my mistake was, i thought surely i could emit
the DFT from the midst of the computation and do a sanity check on it.

And i didn't want to reinvent any wheels.

So since so many people deal with DFTs for doing so many things, it
seemed like there might be a standard format lying around somewhere
that i could just use.

Sort of like if you have an image you'd like to see, you can convert
it to jpg or png or some other widely known format, and take a look at
it.  The 'file' program knows exactly what such an image format is,
and there's a universal, unambiguous interpretation.

So i was hoping there was a DFT format of some sort, that would be
recognized by the standard tools, and i could just put the data in the
standard format, and use some standard tool let me inspect it -
i.e., represent the magnitude and phase somehow, maybe provide some
clues as to where most of the mass was, that sort of thing.  I
wouldn't want to code my own tool for doing it, because i was already
doing it wrong (despite how easy and reliable our modern software
development is).  I wanted to use somebody else's tool as a check
against me repeatedly making the same error of whatever sort.

However, my guess is that Henning is right, and this just doesn't
exist, but if it does exist, i'd like to know about it ! :) :)

And . . . thanks for the reference to DebianScience.

Thanks everybody for all your help!

dan

Missing qt5-designer in Stretch

[Marc Shapiro]

I am running Stretch and installed python3-pyqt, which is supposed to 
provide QtDesigner:


Description: Python 3 bindings for Qt5
 PyQt5 exposes the Qt5 API to Python 3. This package contains the 
following modules:

 * QtCore
 * QtDBus
 * QtDesigner
 * QtGui
 * QtHelp
 * QtNetwork
 * QtPrintSupport
 * QtTest
 * QtWidgets
 * QtXml


but designer does not actually seem to be there.  The only file named 
'designer' on this box is trying to start the long since purged 
qt4-designer.


Aptitude can't find a standalone package for it, either.  It only finds 
qt4-designer, not qt5-designer:


marc@quixote:~$ aptitude search designer
p kdesignerplugin - Integration of KF5 widgets in Qt Designer/Creator
p kdesignerplugin:i386 - Integration of KF5 widgets in Qt Designer/Creator
p kdesignerplugin-data - Integration of KF5 widgets in Qt Designer/Creator
v kdesignerplugin-data:i386 -
p kgendesignerplugin - Integration of KF5 widgets in Qt Designer/Creator
p kgendesignerplugin:i386 - Integration of KF5 widgets in Qt 
Designer/Creator
p libbio-primerdesigner-perl - Perl module to design PCR primers using 
primer3 and epcr

p libqscintilla2-designer - Qt4 Designer plugin for QScintilla 2
p libqscintilla2-designer:i386 - Qt4 Designer plugin for QScintilla 2
p libqscintilla2-designer-dbg - Qt4 Designer plugin for QScintilla 2 
(debug)
p libqscintilla2-designer-dbg:i386 - Qt4 Designer plugin for QScintilla 
2 (debug)

i A libqt4-designer - Qt 4 designer module
p libqt4-designer:i386 - Qt 4 designer module
p libqt4-designer-dbg - Qt 4 designer library debugging symbols
p libqt4-designer-dbg:i386 - Qt 4 designer library debugging symbols
i A libqt5designer5 - Qt 5 designer module
p libqt5designer5:i386 - Qt 5 designer module
c libqt5designercomponents5 - Qt 5 Designer components module
p libqt5designercomponents5:i386 - Qt 5 Designer components module
p libqt5scintilla2-designer - Qt5 Designer plugin for QScintilla 2
p libqt5scintilla2-designer:i386 - Qt5 Designer plugin for QScintilla 2
p libqt5scintilla2-designer-dbg - Qt5 Designer plugin for QScintilla 2 
(debug)
p libqt5scintilla2-designer-dbg:i386 - Qt5 Designer plugin for 
QScintilla 2 (debug)

p libqxt-designer0 - LibQxt extensions to Qt Designer
p libqxt-designer0:i386 - LibQxt extensions to Qt Designer
v libreoffice-reportdesigner -
p qt4-designer - graphical designer for Qt 4 applications
p qt4-designer:i386 - graphical designer for Qt 4 applications


Am I missing something, somewhere?  Or is qt5-designer not packaged for 
Debian?



Marc