Re: [Tails-dev] Finalizing MacBook 2015 support

[Marco Betschart]

@intrigeri: Done; Assigned to you and pointed it to the GitLab branch.
FWIW: The ticket was rejected by @mercedes508 - details at Redmine.


> Am 14.06.2018 um 13:24 schrieb intrigeri :
> 
> Marco Betschart:
>> @intrigeri added a Redmine ticket:
>> https://labs.riseup.net/code/issues/15652 
>> <https://labs.riseup.net/code/issues/15652>
> 
> \o/
> 
>> Two questions:
>> 1. How to set the status field to „in Progress“ as described in your merge 
>> policy <https://tails.boum.org/contribute/merge_policy/#index2h1>?
> 
> I've just given you "Contributor" status on our Redmine so you should
> now be able to do so.
> 
>> 2. How/where to push the git branch (write access / pull request…)? As of 
>> now the
>> changes are only available in my forked repo
>> <https://gitlab.com/marbetschar/tails/tree/feature/macbook12-applespi>.
> 
> That's fine. Just ensure the "Feature Branch" field points there
> ("feature/macbook12-applespi" implicitly means "the
> feature/macbook12-applespi branch in the official tails.git", which
> is incorrect here).
> 
> Then assign to me and I'll review this.
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Finalizing MacBook 2015 support

[Marco Betschart]

@intrigeri added a Redmine ticket:
https://labs.riseup.net/code/issues/15652 
<https://labs.riseup.net/code/issues/15652>

Two questions:
1. How to set the status field to „in Progress“ as described in your merge 
policy <https://tails.boum.org/contribute/merge_policy/#index2h1>?
2. How/where to push the git branch (write access / pull request…)? As of now 
the changes are only available in my forked repo 
<https://gitlab.com/marbetschar/tails/tree/feature/macbook12-applespi>.


> Am 12.06.2018 um 08:26 schrieb intrigeri :
> 
> Marco Betschart:
>> @intrigeri thanks for pointing me towards the right direction. The *.iso 
>> finally built and Tails now works perfectly on my MacBook 12“ 2015! 
> 
> Great!
> 
>> I’d love to see the changes merged into upstream; what would be the
>> right approach to accomplish this?
> 
> Please read https://tails.boum.org/contribute/how/code/
> and in particular the "Submit your work" section.
> (In this case I'd like a Redmine ticket and a Git branch
> rather than patches on the mailing list.)
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Finalizing MacBook 2015 support

[Marco Betschart]

I’ve managed to get the applespi driver compiled  changes pushed here:
https://gitlab.com/marbetschar/tails/commit/13c3a185586f122ceffad7228c9ed009402a4def
 


Unfortunately the *.iso is not created successfully, since the subsequent hook 
50-dkms fails. Probably due to kernel version mismatch. My branch 
feature/macbook12-applespi is based on develop and I’ve not changed any kernel 
version stuff.

How can I get my branch compiled, so I finally can test the changes on actual 
hardware?

Thanks in advance,
  Marco___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Kernel Headers?

[Marco Betschart]

Would love to push the branch; but don’t seem to have access rights to do it.
Attached the git patch with my changes. Hope you can help out on this:



0001-Added-support-for-MacBook-12-using-apple-spi-drivers.patch
Description: Binary data


> Am 10.06.2018 um 00:51 schrieb intrigeri :
> 
> Marco Betschart:
>> Changed the setup according to your suggestions. But the main issue remains. 
>> Still got following error:
> 
>>>> DKMS: Add completed.
>>>> Error! echo
>>>> Your kernel headers for kernel 4.9.0-6-amd64 cannot be found at 
>>>> /lib/modules/4.9.0-6-amd64/build or /lib/modules/4.9.0-6-amd64/source
> 
>> how to fix?
> 
> It's hard to tell without seeing your code. Care to push a Git branch?
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Kernel Headers?

[Marco Betschart]

Changed the setup according to your suggestions. But the main issue remains. 
Still got following error:

>> DKMS: Add completed.
>> Error! echo
>> Your kernel headers for kernel 4.9.0-6-amd64 cannot be found at 
>> /lib/modules/4.9.0-6-amd64/build or /lib/modules/4.9.0-6-amd64/source


how to fix?


> Am 09.06.2018 um 19:48 schrieb intrigeri :
> 
> Marco Betschart:
>> Quick heads up on MacBook 12“ 2015 support:
>> Was able to successfully build Tails. It works within Parallels.
> 
> Great!
> 
>> Now I’m stuck compiling the apple spi drivers. I added a script in 
>> config/chroot_local-hooks called 13-1-apple-spi.
>> I also added the code of its Git repository to 
>> config/chroot_local-includes/usr/src/applespi-0.1
> 
> I suggest you instead do the same as we do for the aufs module, see
> the submodules/aufs4-standalone Git submodule
> and the corresponding bits in auto/config.
> 
> This allows to keep all submodules in one single place, which I hope
> simplifies a tiny bit submodules handling (by making it more explicit)
> for contributors who are not at ease with them.
> 
>> Now, the config/chroot_local-hooks/13-1-apple-spi just does:
> 
>> dkms install -m applespi -v0.1
> 
>> And I always get the following error during build; how to fix?
> 
>> DKMS: Add completed.
>> Error! echo
>> Your kernel headers for kernel 4.9.0-6-amd64 cannot be found at 
>> /lib/modules/4.9.0-6-amd64/build or /lib/modules/4.9.0-6-amd64/source
> 
> Same as above, see the build hook we use for aufs in
> config/chroot_local-hooks/13-aufs.
> 
> Cheers,
> -- 
> intrigeri
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Kernel Headers?

[Marco Betschart]

Quick heads up on MacBook 12“ 2015 support:
Was able to successfully build Tails. It works within Parallels.

Now I’m stuck compiling the apple spi drivers. I added a script in 
config/chroot_local-hooks called 13-1-apple-spi.
I also added the code of its Git repository to 
config/chroot_local-includes/usr/src/applespi-0.1

Now, the config/chroot_local-hooks/13-1-apple-spi just does:

dkms install -m applespi -v0.1

And I always get the following error during build; how to fix?

DKMS: Add completed.
Error! echo
Your kernel headers for kernel 4.9.0-6-amd64 cannot be found at 
/lib/modules/4.9.0-6-amd64/build or /lib/modules/4.9.0-6-amd64/source___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Build Tails on MacBook 2015?

[Marco Betschart]

A quick heads up on the „Waiting for IP address…“ issue:

Seems like this is macOS/VMWare Fusion related. Trying to vagrant up a regular 
debian/stretch64 shows the same symptoms.
Conclusion: VirtualBox does not support passing VT-x, VMWare Fusion does not 
seem to handle vagrant up as it expects.

Any chance to build Tails natively on macOS, without any VM? Unfortunately I 
don’t own any other hardware as of now.


> Am 05.06.2018 um 09:59 schrieb intrigeri :
> 
> Marco Betschart:
>> I was able to fix that; VMWare does support passing VT-x to
>> the guest.
> 
> Progress, good!
> 
>> But now I’m stuck with this IP Address issue. For some reason, the
>> vagrant machine is not capable in getting one. Any idea how to fix
>> this? Below the full output I get - the build stucks while waiting
>> for the IP address. Please note: this is the master branch of the
>> repo, no changes made from my end.
> 
>> $: rake build
>> Using HTTP proxy: http://vagrant-stretch:3142
>> Bringing machine 'default' up with 'libvirt' provider...
>> [...]
>> ==> default: Starting domain.
>> ==> default: Waiting for domain to get an IP address...
> 
> I don't know what's going on. I suggest:
> 
> - looking at the logs in /var/log/libvirt/qemu/
>  (probably:
>  tails-builder-amd64-stretch-20180301-2f443fafad_default.log)
> - looking at the systemd Journal with the journalctl command
> - checking that your VMWare VM has enough RAM; I think you should give
>  it at least 1.5 GiB and even that might not be enough so if you can,
>  try with 3 GiB or more
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Fwd: Tails on MacBook?

[Marco Betschart]

Does anybody know how to fix the never ending „Waiting for domain to get an IP 
Address…“ below?
I’m running a fresh Debian 9.3 in VMWare Fusion on my macOS. VT-x is enabled; 
dependencies according to the Tails guide 
<https://tails.boum.org/contribute/build/> are installed.

Would be awesome if anybody can help out….


> Anfang der weitergeleiteten Nachricht:
> 
> Von: Marco Betschart 
> Betreff: Aw: [Tails-dev] Tails on MacBook?
> Datum: 3. Juni 2018 um 10:51:05 MESZ
> An: The Tails public development discussion list 
> Antwort an: The Tails public development discussion list 
> 
> Hi Intrigeri,
> 
> I was able to fix that; VMWare does support passing VT-x to the guest. But 
> now I’m stuck with this IP Address issue. For some reason, the vagrant 
> machine is not capable in getting one. Any idea how to fix this? Below the 
> full output I get - the build stucks while waiting for the IP address. Please 
> note: this is the master branch of the repo, no changes made from my end.
> 
> $: rake build
> Using HTTP proxy: http://vagrant-stretch:3142 <http://vagrant-stretch:3142/>
> Bringing machine 'default' up with 'libvirt' provider...
> ==> default: Creating image (snapshot of base box volume).
> ==> default: Creating domain with the following settings...
> ==> default:  -- Name:  
> tails-builder-amd64-stretch-20180301-2f443fafad_default
> ==> default:  -- Domain type:   kvm
> ==> default:  -- Cpus:  1
> ==> default:  -- Memory:1024M
> ==> default:  -- Management MAC:
> ==> default:  -- Loader:
> ==> default:  -- Base box:  
> tails-builder-amd64-stretch-20180301-2f443fafad
> ==> default:  -- Storage pool:  default
> ==> default:  -- Image: 
> /var/lib/libvirt/images/tails-builder-amd64-stretch-20180301-2f443fafad_default.img
>  (20G)
> ==> default:  -- Volume Cache:  default
> ==> default:  -- Kernel:
> ==> default:  -- Initrd:
> ==> default:  -- Graphics Type: vnc
> ==> default:  -- Graphics Port: 5900
> ==> default:  -- Graphics IP:   127.0.0.1
> ==> default:  -- Graphics Password: Not defined
> ==> default:  -- Video Type:cirrus
> ==> default:  -- Video VRAM:9216
> ==> default:  -- Keymap:en-us
> ==> default:  -- TPM Path:  
> ==> default:  -- Disks: vdb(qcow2,15G)
> ==> default:  -- Disk(vdb): 
> /var/lib/libvirt/images/apt-cacher-ng-data.qcow2 (Remove only manually) Not 
> created - using existed.
> ==> default:  -- INPUT: type=mouse, bus=ps2
> ==> default:  -- Command line : 
> ==> default: 
> ==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
> ==> default: Should be mounting folders
> ==> default:  /vagrant, opts: {:type=>:"9p", :readonly=>true, 
> :guestpath=>"/vagrant", :hostpath=>"/home/osboxes/tails/vagrant", 
> :disabled=>false, :__vagrantfile=>true, :target=>"/vagrant", 
> :accessmode=>"passthrough", :mount=>true, 
> :mount_tag=>"2c56346e7960721c6c3f8de5e712c67"}
> ==> default: 
> ==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
> ==> default: Should be mounting folders
> ==> default:  /amnesia.git, opts: {:type=>:"9p", :readonly=>true, 
> :guestpath=>"/amnesia.git", :hostpath=>"/home/osboxes/tails", 
> :disabled=>false, :__vagrantfile=>true, :target=>"/amnesia.git", 
> :accessmode=>"passthrough", :mount=>true, 
> :mount_tag=>"87850e485a799696ca30413b1dff3e1"}
> ==> default: Creating shared folders metadata...
> ==> default: Starting domain.
> ==> default: Waiting for domain to get an IP address...
> 
> 
>> Am 03.06.2018 um 09:57 schrieb intrigeri > <mailto:intrig...@boum.org>>:
>> 
>> Hi,
>> 
>> Marco Betschart:
>>> Got a local VMWare Fusion setup with Debian 9.3 and VT-x enabled on my 
>>> MacBook
>>> (Downloaded from OS-Boxes <https://www.osboxes.org/debian/ 
>>> <https://www.osboxes.org/debian/>>).
>> 
>>> There was an error in Libvirt. The error is shown below:
>>> Call to virDomainCreateWithFlags failed: internal error: process excited 
>>> while
>>> connecting to monitor: Could not access KVM kernel module: Permission 
>>> denied failed
>>> to initialize KVM: permission denied.
>> 
>> I suspect VMWare does not expose (nested) VT-x capabilities to the
>> Debian guest VM whi

Re: [Tails-dev] Tails on MacBook?

[Marco Betschart]

Hi Intrigeri,

I was able to fix that; VMWare does support passing VT-x to the guest. But now 
I’m stuck with this IP Address issue. For some reason, the vagrant machine is 
not capable in getting one. Any idea how to fix this? Below the full output I 
get - the build stucks while waiting for the IP address. Please note: this is 
the master branch of the repo, no changes made from my end.

$: rake build
Using HTTP proxy: http://vagrant-stretch:3142
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default:  -- Name:  
tails-builder-amd64-stretch-20180301-2f443fafad_default
==> default:  -- Domain type:   kvm
==> default:  -- Cpus:  1
==> default:  -- Memory:1024M
==> default:  -- Management MAC:
==> default:  -- Loader:
==> default:  -- Base box:  
tails-builder-amd64-stretch-20180301-2f443fafad
==> default:  -- Storage pool:  default
==> default:  -- Image: 
/var/lib/libvirt/images/tails-builder-amd64-stretch-20180301-2f443fafad_default.img
 (20G)
==> default:  -- Volume Cache:  default
==> default:  -- Kernel:
==> default:  -- Initrd:
==> default:  -- Graphics Type: vnc
==> default:  -- Graphics Port: 5900
==> default:  -- Graphics IP:   127.0.0.1
==> default:  -- Graphics Password: Not defined
==> default:  -- Video Type:cirrus
==> default:  -- Video VRAM:9216
==> default:  -- Keymap:en-us
==> default:  -- TPM Path:  
==> default:  -- Disks: vdb(qcow2,15G)
==> default:  -- Disk(vdb): 
/var/lib/libvirt/images/apt-cacher-ng-data.qcow2 (Remove only manually) Not 
created - using existed.
==> default:  -- INPUT: type=mouse, bus=ps2
==> default:  -- Command line : 
==> default: 
==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
==> default: Should be mounting folders
==> default:  /vagrant, opts: {:type=>:"9p", :readonly=>true, 
:guestpath=>"/vagrant", :hostpath=>"/home/osboxes/tails/vagrant", 
:disabled=>false, :__vagrantfile=>true, :target=>"/vagrant", 
:accessmode=>"passthrough", :mount=>true, 
:mount_tag=>"2c56346e7960721c6c3f8de5e712c67"}
==> default: 
==> default: Machine id: 3a12845b-e5a6-44c9-9d2a-6833d15b5e0f
==> default: Should be mounting folders
==> default:  /amnesia.git, opts: {:type=>:"9p", :readonly=>true, 
:guestpath=>"/amnesia.git", :hostpath=>"/home/osboxes/tails", :disabled=>false, 
:__vagrantfile=>true, :target=>"/amnesia.git", :accessmode=>"passthrough", 
:mount=>true, :mount_tag=>"87850e485a799696ca30413b1dff3e1"}
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...


> Am 03.06.2018 um 09:57 schrieb intrigeri :
> 
> Hi,
> 
> Marco Betschart:
>> Got a local VMWare Fusion setup with Debian 9.3 and VT-x enabled on my 
>> MacBook
>> (Downloaded from OS-Boxes <https://www.osboxes.org/debian/>).
> 
>> There was an error in Libvirt. The error is shown below:
>> Call to virDomainCreateWithFlags failed: internal error: process excited 
>> while
>> connecting to monitor: Could not access KVM kernel module: Permission denied 
>> failed
>> to initialize KVM: permission denied.
> 
> I suspect VMWare does not expose (nested) VT-x capabilities to the
> Debian guest VM which prevents that VM from itself running a VM (as
> part of our build process). So either fix the Vmware VM configuration
> (if that's possible at all) or adjust vagrant/Vagrantfile, e.g.
> this line:
> 
>   domain.driver = 'kvm'
> 
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to 
> tails-dev-unsubscr...@boum.org.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Tails on MacBook?

[Marco Betschart]

Hi Intrigeri,

Was able to fix the permission issue and I think I know how to apply the kernel 
modules.
But I’m not able to run rake build successfully. It stucks while it’s waiting 
to obtain an IP address for the virtual machine.

Any suggestions?

Thanks,
  Marco


> Am 02.06.2018 um 13:11 schrieb Marco Betschart :
> 
> Hi Intrigeri,
> 
> Got a local VMWare Fusion setup with Debian 9.3 and VT-x enabled on my 
> MacBook (Downloaded from OS-Boxes <https://www.osboxes.org/debian/>). Took me 
> a while to figure out this is not possible with VirtualBox.
> Anyway, I’m now trying to build Tails master branch to figure out if my setup 
> works in general. I’m now running into the following two bummers:
> 
> 
> 1. Build of master branch fails with the following error
> 
> I’m executing as root:
> 
> rake build && rake vm:halt
> 
> Which aborts with the error:
> 
> There was an error in Libvirt. The error is shown below:
> Call to virDomainCreateWithFlags failed: internal error: process excited 
> while connecting to monitor: Could not access KVM kernel module: Permission 
> denied failed to initialize KVM: permission denied.
> 
> 
> 2. Where to put the additional kernel modules
> I’ve seen the HACKING.mdwn - but I not really figured out where and how to 
> apply the instructions of the macbook12-spi-driver 
> <https://github.com/cb22/macbook12-spi-driver>  Can you give a short walk 
> through where to put the changes? Just some bullet points should be enough to 
> get me going.
> 
> 
> Thank you very much for your help!!
>   Marco
> 
> 
>> Am 02.06.2018 um 12:39 schrieb intrigeri > <mailto:intrig...@boum.org>>:
>> 
>> Hi Marco, 
>> Marco Betschart:
>>> Thanks for your feedback. I understand the situation and your
>>> proposed steps are absolutely legitimate from a Tails angle.
>> 
>> :)
>> 
>>> What would be the best approach for provide you a patch? I’ve seen
>>> https://tails.boum.org/contribute/how/code 
>>> <https://tails.boum.org/contribute/how/code>
>> 
>> Yes, that's the best entry point we have. See also HACKING.mdwn at the
>> root of our Git tree, which can also be useful.
>> 
>>> But since I only own my MacBook 12“ I’m not quite sure if it is fast
>>> enough to build the whole project
>> 
>> I'm not concerned about that. Worst case it'll take an hour or so to
>> build an ISO, which is still manageable (that's what it took me in
>> the first couple years of Tails development :)
>> 
>>> and how I would ensure everything is working correctly afterwards?
>> 
>> Assuming your changes are restricted to building an additional dkms
>> kernel module, there's little chance they break anything unrelated;
>> testing on various computers should be good enough.
>> 
>> But if you're curious you can take a look at our automated test suite:
>> https://tails.boum.org/contribute/release_process/test/automated_tests/ 
>> <https://tails.boum.org/contribute/release_process/test/automated_tests/>
>> 
>> Cheers!
> 

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Tails on MacBook?

[Marco Betschart]

Hi Intrigeri,

Got a local VMWare Fusion setup with Debian 9.3 and VT-x enabled on my MacBook 
(Downloaded from OS-Boxes <https://www.osboxes.org/debian/>). Took me a while 
to figure out this is not possible with VirtualBox.
Anyway, I’m now trying to build Tails master branch to figure out if my setup 
works in general. I’m now running into the following two bummers:


1. Build of master branch fails with the following error

I’m executing as root:

rake build && rake vm:halt

Which aborts with the error:

There was an error in Libvirt. The error is shown below:
Call to virDomainCreateWithFlags failed: internal error: process excited while 
connecting to monitor: Could not access KVM kernel module: Permission denied 
failed to initialize KVM: permission denied.


2. Where to put the additional kernel modules
I’ve seen the HACKING.mdwn - but I not really figured out where and how to 
apply the instructions of the macbook12-spi-driver 
<https://github.com/cb22/macbook12-spi-driver>  Can you give a short walk 
through where to put the changes? Just some bullet points should be enough to 
get me going.


Thank you very much for your help!!
  Marco


> Am 02.06.2018 um 12:39 schrieb intrigeri :
> 
> Hi Marco, 
> Marco Betschart:
>> Thanks for your feedback. I understand the situation and your
>> proposed steps are absolutely legitimate from a Tails angle.
> 
> :)
> 
>> What would be the best approach for provide you a patch? I’ve seen
>> https://tails.boum.org/contribute/how/code
> 
> Yes, that's the best entry point we have. See also HACKING.mdwn at the
> root of our Git tree, which can also be useful.
> 
>> But since I only own my MacBook 12“ I’m not quite sure if it is fast
>> enough to build the whole project
> 
> I'm not concerned about that. Worst case it'll take an hour or so to
> build an ISO, which is still manageable (that's what it took me in
> the first couple years of Tails development :)
> 
>> and how I would ensure everything is working correctly afterwards?
> 
> Assuming your changes are restricted to building an additional dkms
> kernel module, there's little chance they break anything unrelated;
> testing on various computers should be good enough.
> 
> But if you're curious you can take a look at our automated test suite:
> https://tails.boum.org/contribute/release_process/test/automated_tests/
> 
> Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] MacBook 2015: Keyboard & Trackpad

[Marco Betschart]

Found, that loading some additional modules on boot might solve the issue of 
non responding keyboard & trackback on my MacBook 2015:
https://askubuntu.com/questions/1003055/macbook-12-2015-keyboard-and-trackpad 


How to make Tails load these modules on boot?
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Tails on MacBook?

[Marco Betschart]

Hi Intrigeri,

Thanks for your feedback. I understand the situation and your proposed steps 
are absolutely legitimate from a Tails angle.
What would be the best approach for provide you a patch? I’ve seen 
https://tails.boum.org/contribute/how/code 
<https://tails.boum.org/contribute/how/code>

But since I only own my MacBook 12“ I’m not quite sure if it is fast enough to 
build the whole project and how I would ensure everything is working correctly 
afterwards?

Cheers,
  Marco


> Am 29.05.2018 um 20:08 schrieb intrigeri :
> 
> Hi Marco,
> 
> Marco Betschart:
>> I wanted to boot Tails on my MacBook 12“ from 2015, but the keyboard as well 
>> as the trackpad do not work at all.
>> Seems like this is a known issue and there is a driver available which 
>> should help out:
>> https://mknowles.com.au/wordpress/2017/11/02/installing-fedora-27-on-a-2017-macbook-12-retina-macbook-101/
>> <https://mknowles.com.au/wordpress/2017/11/02/installing-fedora-27-on-a-2017-macbook-12-retina-macbook-101/>
> 
>> Are there any plans for adding this to the official Tails?
> 
> This driver is marked "WIP" (work in progress) and as far as I know
> it's not been submitted for inclusion into the Linux kernel yet.
> The list of known issues on
> https://github.com/cb22/macbook12-spi-driver is not exactly confidence
> inspiring. So it's not available in Debian and thus not in Tails yet.
> Once the authors of this driver deem it ready for prime time, it'll
> propagate to Debian and then to Tails.
> 
> In the meantime, the amount of work required to go out of our way and
> include this third-party driver does not fit into our
> current resources. But assuming it's Free Software and builds
> reproducibly, I think we would happily consider a good patch that
> implements this :)
> 
> Cheers,
> -- 
> intrigeri

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Tails on MacBook?

[Marco Betschart]

Hi there,

I wanted to boot Tails on my MacBook 12“ from 2015, but the keyboard as well as 
the trackpad do not work at all.
Seems like this is a known issue and there is a driver available which should 
help out:
https://mknowles.com.au/wordpress/2017/11/02/installing-fedora-27-on-a-2017-macbook-12-retina-macbook-101/
 


Are there any plans for adding this to the official Tails?

Thanks in advance,
  Marco___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.