Re: Booting Debian on NVMe Dirive with killer E2400 ethernet next to Impossible!!!!

2016-10-23 Thread Humberto Hassey
Finally got it to work!! here is the procedure, I hope it helps someone else: Step 1 start the installation with the Debian DVD and go through it unitl it sais Grub failed Step 2 in a separate USB memory and with a working debian system do: sudo apt-get -t jessie-backports download grub-efi-amd6

Re: Booting Debian on NVMe Dirive with killer E2400 ethernet next to Impossible!!!!

2016-10-23 Thread Ben Hutchings
On Sun, 2016-10-23 at 22:26 -0400, Lennart Sorensen wrote: > On Sun, Oct 23, 2016 at 01:43:49PM -0700, Humberto Hassey wrote: > > Hello I am a Debian user and just bought a nice laptop from system 76, I > > wiped ubuntu and proceed to install Debian, well it turns our that Debian > > does not recog

Re: Booting Debian on NVMe Dirive with killer E2400 ethernet next to Impossible!!!!

2016-10-23 Thread Lennart Sorensen
On Sun, Oct 23, 2016 at 01:43:49PM -0700, Humberto Hassey wrote: > Hello I am a Debian user and just bought a nice laptop from system 76, I > wiped ubuntu and proceed to install Debian, well it turns our that Debian > does not recognize my network card, and the Grub packed on the installer > does n

Bug#826844: netcfg ignoring BOOTF= in kernel cmdline

2016-10-23 Thread James Mackie
Hi Philipp, Thanks for your response. Yeah I actually figured that out after looking looking at the netcfg code and seeing the "01-" being purposefully excluded from the address capture. So then I looked up the specification for PXELINUX and saw the hardware type at the start. So, I've just hardc

zipl-installer_0.0.35_s390x.changes ACCEPTED into unstable

2016-10-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Oct 2016 23:25:37 +0200 Source: zipl-installer Binary: zipl-installer Architecture: source s390x Version: 0.0.35 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Philipp

Bug#840230: marked as done (When installing to rootfs on LVM, an empty subvol= is appended to rootflags)

2016-10-23 Thread Debian Bug Tracking System
Your message dated Sun, 23 Oct 2016 23:49:06 + with message-id and subject line Bug#840230: fixed in zipl-installer 0.0.35 has caused the Debian Bug report #840230, regarding When installing to rootfs on LVM, an empty subvol= is appended to rootflags to be marked as done. This means that you

Bug#826844: netcfg ignoring BOOTF= in kernel cmdline

2016-10-23 Thread Philipp Kern
On 06/09/2016 01:11 PM, James Mackie wrote: > This is me checking /proc/cmdline: > ~ # cat /proc/cmdline > auto=true priority=critical url=http://thebooting.dev2.internal/preseed > interface=auto DEBCONF_DEBUG=5 BOOTIF=0c:c4:7a:8e:ad:4a BOOTIF= is generated by PXELINUX, which also prepends a hardw

Processed: retitle 835499 to netcfg: support pointopoint for Ethernet devices

2016-10-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 835499 netcfg: support pointopoint for Ethernet devices Bug #835499 [netcfg] netcfg: Does not allow for pointopoint addresses, not even in export mode Changed Bug title to 'netcfg: support pointopoint for Ethernet devices' from 'netcfg:

Bug#815916: Followup

2016-10-23 Thread Philipp Kern
On 08/31/2016 01:21 PM, Viktor Mihajlovski wrote: > the patches have been incorporated in Ubuntu's d-i since their 16.04 > release ([1],[2]) and I would hope that thereby they have gotten > sufficient test coverage in the meantime. I haven't heard of breakages > for other architectures and they hav

Bug#835499: netcfg: Does not allow for pointopoint addresses, not even in export mode

2016-10-23 Thread Philipp Kern
On 08/26/2016 01:12 PM, Michael Neuffer wrote: > netcfg does not ask for a pointopoint address when entering the > network config manually, not even in expert mode > > In expert mode it will show you, after collecting all the information, > that is has NOT set a pointopoint address. > > Please

Bug#825931: s390-netdevice virtio interface choice misleading

2016-10-23 Thread Philipp Kern
Hi, On 05/31/2016 09:01 PM, Dimitri John Ledkov wrote: > I find logic in s390-netdevice. The priority of many questions is too > high, thus e.g. if one uses qeth port 0, one has to explicitely > preseed that, even though a common case qeth port 0 will work in > majority (sensible default) cases.

Processing of zipl-installer_0.0.35_s390x.changes

2016-10-23 Thread Debian FTP Masters
zipl-installer_0.0.35_s390x.changes uploaded successfully to localhost along with the files: zipl-installer_0.0.35.dsc zipl-installer_0.0.35.tar.xz zipl-installer_0.0.35_s390x.udeb Greetings, Your Debian queue daemon (running on host usper.debian.org)

Booting Debian on NVMe Dirive with killer E2400 ethernet next to Impossible!!!!

2016-10-23 Thread Humberto Hassey
Hello I am a Debian user and just bought a nice laptop from system 76, I wiped ubuntu and proceed to install Debian, well it turns our that Debian does not recognize my network card, and the Grub packed on the installer does not recognize the NVMe drive correctly, so I can not boot, nor connect to

Bug#841842: debian-installer: should use EXT4's native file-system-level encryption

2016-10-23 Thread Marcos Mobley
Package: debian-installer Severity: wishlist Dear Maintainer, it would be nice to be able to use EXT4's native file-system-level encryption instead of LUKS. Thanks -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500

Bug#837625: Trekstor miniPC W2 after dist-upgrade

2016-10-23 Thread christina_c
There is an improvement after a dist-upgrade a week ago. Now kernel 4.7.0-1-686-pae is running and since one week there are no freezes at boot anymore. But with xfce running the system often freezed after a while. It never happened at the console. I found here: https://bugzilla.kernel.org/sh

Re: Next d-i release

2016-10-23 Thread Samuel Thibault
Hello, Cyril Brulebois, on Wed 19 Oct 2016 15:33:03 +0200, wrote: > Feel free to mention packages you want to see in testing, We have the newer brltty release, 5.4, which provides support for some more devices, and fixes various issues. It has been tested for some time in experimental and sid now