Bug#907768: debian-installer: gfx and txt installer fail on new System76 oryx pro 17in 1080P disp w nvidia GTX1070
Greetings all, System76 support informs me they have successfully reproduced the issue on a machine with hardware identical to mine, meaning this is likely a hardware compatibility issue and not a faulty hardware issue. I would like to imagine if we can just figure out the proper boot paramaters here, the installer will just work, but I am out of my wheelhouse here and could use some help. In an attempt to unblock myself, I went ahead and set up a debian live USB planning to do a manual install with debootstrap and, surprise surprise, the live USB image also has a debian-installer style boot menu, and exhibits the exact same behavior as the installer does, so I cannot boot into a live debian system from the USB images either. I'm trying to create an ubuntu live thumb drive now so I can run debootstrap from there... Thanks! -Carl -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#907768: debian-installer: gfx and txt installer fail on new System76 oryx pro 17in 1080P disp w nvidia GTX1070
Package: debian-installer Severity: important Tags: d-i Dear Maintainer, Booting to the installer on my new Oryx Pro is failing for both the text and graphical installer. I have produced a 5minute video showing exactly what it looks like: https://drive.google.com/file/d/1qSKTsWiLbauBi8ALDtzV1D225i7Zgrtn/view?usp=sharing When booting into the text installer, the screen is scaled so tiny it is only 1cm by 1cm, and tiled horizontally across the screen. If you zoom in you can see the screen is "really there" but it is so tiny you can't make out any of the options. When booting into the graphical installer, I just see a blank screen and the machine seems to hang forever. The machine came with ubuntu pre-installed and it boots into that system just fine. I was able to reproduce this problem with the following images: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-xfce-CD-1.iso https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso https://cdimage.debian.org/cdimage/buster_di_alpha3/amd64/iso-cd/debian-buster-DI-alpha3-amd64-netinst.iso I confirmed the checksum of the ISO and the validity of the usb drive, and confirmed it worked in another machine. The machine includes both intel and nvidia graphics, which are switched by software. I have tried putting it in both NVIDIA and Intel graphics modes and see the same behavior: https://support.system76.com/articles/graphics-switch-ubuntu/ I've tried several boot parameters including "nomodeset" and "vga=", DEBIAN_FRONT_END=text, fb=false, gfxpayload=1920x1080, etc. When I boot into the ubuntu install, the native resolution appears to be 1920x1080. Because I currently have it set to Intel graphics mode, the nvidia hardware doesn't even show up in $(lspci), the intel hardware is "Intel Corporation Device 3e9b" using kernel driver i915. I can get the nvidia details if needed but system76 says it is a 8GB GTX 1070. I am filing this report from another machine, so the system information below is not relevant. I am happy to try things if you have any suggestions for a workaround, at this point I have to imagine the possibilities are a (very very weird) hardware problem, or a hardware incompatibility. Thanks! -Carl Myers -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#849330: firmware-iwlwifi: intel 8260 does not work when using modfile /lib/firmware/iwlwifi-8000C-22.ucode and kernel 4.8
erm, actually, it is not a lenovo p50 it is a system76 Oryx Pro (was thinking it was my other laptop, that's what I get for writing a bug report before morning coffee) -Carl -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#849330: firmware-iwlwifi: intel 8260 does not work when using modfile /lib/firmware/iwlwifi-8000C-22.ucode and kernel 4.8
Greetings, I also experienced this bug (Lenovo P50, worked with 4.2.0-1 kernel, fails with 4.8.0-2 kernel). I was able to get things working again by downgrading - but I had to go pretty far. firmware-iwlwifi 20161130-2 did not work firmware-iwlwifi 20160824-1 did not work Downgrading to firmware-iwlwifi 20160110-1, however, worked for me. In case others following this bug are curious: wget http://snapshot.debian.org/archive/debian/20160224T164321Z/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20160110-1%7Ebpo8%2B1_all.deb sudo dpkg -i firmware-iwlwifi_20160110-1\~bpo8+1_all.deb sudo apt-mark hold firmware-iwlwifi then reboot (or maybe rmmod iwlwifi + modprobe iwlwifi?) Thanks! -Carl -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)
So, I have some bad news - the issue may not be completely fixed. Or, I might have missed something. I tried to build an iso by following the steps to check out the debian-install stuff[1] but found that the build_all target did not make the netinst ISO as I expected. I next found some directions for altering an existing iso, so I grabbed the net inst and followed the rough directions here[2]. I found I had to modify the directions to generate an efi compatible CD with these here[3]. The directions didn't seem to work due to genisoimage not recognizing all the arguments, so as per the workaround here[4] I had to grab a copy of the genisoimage binary from the ubuntu package. To modify the image, I rsync'd it to a new directory, then deleted the grub-installer 1.127 package and replaced it with a copy of 1.128. I updated the md5sums.txt file and the "Packages.gz" file (leaving everything the same except updating the verison, the path to the package, and the hashes). I then redid the install - and it WORKED! Got no grub error. Unfortunately, when I rebooted after the install, I still have the problem where it drops me into a simple grub command line, and fails to boot the rest of the way. Either something is messed up in my boot loader that a fresh install did not fix, or the fix in the grub-installer package alone is not enough (although it definitely is working better since it doesn't get errors during install anymore). -Carl [1] http://d-i.alioth.debian.org/doc/internals/ch04.html#id321776 [2] https://debmintux.wordpress.com/2010/07/21/howto-create-a-custom-debian-installer-netinstall-iso/ [3] http://askubuntu.com/questions/457528/how-do-i-create-an-efi-bootable-iso-of-a-customized-version-of-ubuntu [4] https://stackoverflow.com/questions/31831268/genisoimage-and-uefi -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)
I got my system working. I repeated the chroot experiment from above, confirmed that this time the initrd contained cryptsetup and the other necessary tools (it did), and I was able to then run the grub installer. Since in the past when I did this it didn't work, I was trying to think of something different to try, so I tried making a symlink with a "more expected" name: ln -s /dev/nvme0 /dev/sdb grub-install /dev/sdb I dunno if just running "grub-install" would have been enough, or if it worked specifically because I faked it out with a symlink like this, but after that I rebooted and grub seems to be installed correctly and is able to boot into debian. I'm happy my machine works now but I'm sorry I wasn't able to confirm the fix for you - whatever has been donein grub-installer 1.128 has improved the problem but not totally fixed it - hopefully these details will help you figure out the remaining problems (possibly with the package that provides grub-install, if it is differnet from grub-installer? otherwise some other code path in there...) Thanks! -Carl -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)
That would be great - I have a colo server at cmyers.org you could upload to, I'll email you credentials directly. If it's too much trouble, I can wait until monday, but I'm glad to be the guinea pig and try this out if you don't mind. -Carl On Thu, Dec 03, 2015 at 12:52:22PM +0100, Cyril Brulebois wrote: > Date: Thu, 3 Dec 2015 12:52:22 +0100 > From: Cyril Brulebois <k...@debian.org> > To: Carl Myers <cmy...@cmyers.org> > Cc: Julien Cristau <jcris...@debian.org>, 806...@bugs.debian.org, > 806...@bugs.debian.org > Subject: Re: Bug#806164: installation-reports: jessie install on dell xps > 13 9350 (grub-installer issues) > Organization: Debian > > Carl Myers <cmy...@cmyers.org> (2015-12-02): > > Is there a nightly ISO build I can use, or do I have to build my own? Not > > sure how to confirm the fix is in any given ISO I might download... > > I think you'd need to wait for a weekly, which means monday; that's because > grub-installer is not included in netboot images, so fetched over the > network. You might find a way by setting the right boot parameters, but that > might break other bits. > > > In case there isn't, I'm reading the wiki page about simple-cdd and > > building a custom debian installer, and looking into how to produce my own > > install CD with the updated packages now. > > I haven't used simple-cdd yet, but if that might help, I have a debian-cd > setup locally, and baring my (limited) upload bandwidth I could probably > build and push an image for you to test, somewhen today. Would that work for > you? > > Looking at debian-stretch-DI-alpha4-amd64-netinst.iso's file list, it > definitely contains grub-installer, so the tricky part I've mentioned in my > first paragraph should disappear with a similar image. > > Mraw, > KiBi. -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806849: debian-installer: d-i fails to install grub2 correctly for efi system using encrypted LVM
On Wed, Dec 02, 2015 at 04:44:46PM +, Ben Hutchings wrote: > This is a known bug. > > Ben. > > -- > Ben Hutchings > Humans are not rational beings; they are rationalising beings. I know this is a bug tracker, not a support forum, but given this is a known bug, if it isn't going to be fixed soon, could someone point me to a resource for how to fix a machine in this state? I presume the instructions would look something like this: 1. boot with live CD 2. unlock encrypted volume, mount to /media/root/ and /media/root/home 3. bind mount dev, proc, and sys 4. chroot into /media/root 5. signature.asc Description: Digital signature
Bug#806849: debian-installer: d-i fails to install grub2 correctly for efi system using encrypted LVM
Steve, Thanks for following up so quickly! Yes, the installer said UEFI on the splash screen, and the /sys/firmware/efi directory existed. I was most successful booting from a USB CD drive, which I selected from the EFI bios to start the boot. Thanks! -Carl On Wed, Dec 02, 2015 at 01:55:37PM +, Steve McIntyre wrote: > Return-Path: <st...@einval.com> > X-Original-To: cmy...@cmyers.org > Delivered-To: cmy...@cmyers.org > Received: by mail.cmyers.org (Postfix, from userid 114) id 708AF22D13; Wed, > 2 Dec 2015 06:25:24 -0800 (PST) > X-Greylist: delayed 1743 seconds by postgrey-1.35 at debian; Wed, 02 Dec > 2015 06:25:22 PST > Received: from cheddar.halon.org.uk (cheddar.halon.org.uk [93.93.131.118]) > by mail.cmyers.org (Postfix) with ESMTPS id 4A46122D0C for > <cmy...@cmyers.org>; Wed, 2 Dec 2015 06:25:22 -0800 (PST) > Received: from bsmtp by cheddar.halon.org.uk with local-bsmtp (Exim 4.80) > (envelope-from <st...@einval.com>) id 1a47tI-00069N-IO; Wed, 02 Dec 2015 > 13:56:16 + > Received: from steve by tack.local with local (Exim 4.84) (envelope-from > <st...@einval.com>) id 1a47sf-0005Dh-Sy; Wed, 02 Dec 2015 13:55:37 + > Date: Wed, 2 Dec 2015 13:55:37 + > From: Steve McIntyre <st...@einval.com> > To: Carl Myers <cmy...@cmyers.org>, 806...@bugs.debian.org > Subject: Re: Bug#806849: debian-installer: d-i fails to install grub2 > correctly for efi system using encrypted LVM > Message-ID: <20151202135537.gb28...@einval.com> > References: <20151202065120.19939.685.reportbug@debian> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > In-Reply-To: <20151202065120.19939.685.reportbug@debian> > X-attached: unknown > User-Agent: Mutt/1.5.23 (2014-03-12) > > On Tue, Dec 01, 2015 at 10:51:20PM -0800, Carl Myers wrote: > >Package: debian-installer > >Version: stretch alpha 4 > >Severity: important > >Tags: d-i > > > >Dear Maintainer, > > Hi Carl, > > >I have a new System76 Oryx Pro laptop using efi boot. Ubuntu installs > >successfully but I can't get debian to install using encrypted LVM. > > > >The laptop has an nvme device which requires efi boot so I can't just disable > >it. Here are my repro steps: > > > >1. Boot using netinst (tried both stable and testing, stable doesn't work at > >all I think due to efi?) > >2. Performed normal install (tried both text and gui) > >3. Included proprietary firmware for wifi from usb key when prompted > >4. selected encrypted LVM with separate home partition, changed root > >partition > >to 20GB and made some other lvm adjustments > >5. proceeded to install base system successfully > >6. when it comes time to install grub, it fails. no better error message > >provided, nothing in /var/logs either > > Silly question: are you sure that the installer booted in UEFI mode? > What you're describing sounds like it could be a BIOS-mode > installation instead. Did the installer splash screen mention UEFI? > > -- > Steve McIntyre, Cambridge, UK.st...@einval.com > "You can't barbecue lettuce!" -- Ellie Crane > -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806849: debian-installer: d-i fails to install grub2 correctly for efi system using encrypted LVM
On Wed, Dec 02, 2015 at 02:15:16PM -0500, Lennart Sorensen wrote: > On Wed, Dec 02, 2015 at 09:30:05AM -0800, Carl Myers wrote: > > I know this is a bug tracker, not a support forum, but given this is a > > known bug, if it isn't going to be fixed soon, could someone point me to a > > resource for how to fix a machine in this state? > > > > I presume the instructions would look something like this: > > 1. boot with live CD > > 2. unlock encrypted volume, mount to /media/root/ and /media/root/home > > Of course you do have to mount /media/root/boot and /media/root/boot/efi > as well. After all with encrypted root, you have a seperate boot > partition that is unencrypted for loading the kernel and initrd, and > since it is a UEFI machine, you have a vfat partition to sture the efi > boot loader files too. Yes, I forgot to say so, but I mounted those pieces too. > > > 3. bind mount dev, proc, and sys > > 4. chroot into /media/root > > 5. > 6. grub-install /dev/nvme0 > > 7. reboot > > > > I'm having trouble figureing out step 5, I've done the rest with success =| > > I suspect step 5 might be 'do nothing'. Step 6 is probably all you > need and the part grub-installer fails to do because it doesn't think > /dev/nvme* is a valid device name. that was my hope, but when I did that "nothing", things still didnt' work, but the grub-install command said it ran successfully. I examined the /boot/initrd-* file that was produced, extracted it, and noted it did not contain /sbin/cryptsetup, which seemed wrong. Not sure what other information I can provide to help figure out what is wrong though... it sounds like you think this might still be a bug in grub-install ? I'd be glad to run a snapshot of grub-install or poke around in there if you want to give me some pointers (I am a fairly experienced software dev, but haven't done a lot of C/C++ in a while) Thanks! > > -- > Len Sorensen -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)
Is there a nightly ISO build I can use, or do I have to build my own? Not sure how to confirm the fix is in any given ISO I might download... In case there isn't, I'm reading the wiki page about simple-cdd and building a custom debian installer, and looking into how to produce my own install CD with the updated packages now. -Carl -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806849: Bug#806164: installation-reports: jessie install on dell xps 13 9350 (grub-installer issues)
On Thu, Dec 03, 2015 at 01:00:32AM +0100, Cyril Brulebois wrote: > > sid/stretch should be behaving better since 1.122 was supposed to > introduce support for NVMe devices, but I botched it. 1.128 will > hopefully fix this, but confirmations are welcome: > > https://anonscm.debian.org/cgit/d-i/grub-installer.git/commit/?id=fa658f8a8fbd9179a5ae3abae14b6c906f6ee620 > > Backports of the relevant commits for grub-installer, along with: > > https://anonscm.debian.org/cgit/d-i/debian-installer-utils.git/commit/?id=ad2213befaa67a95943b3f13b50fd73b6dc849bb > > for debian-installer-utils might be a good idea. I've added that to my > jessie pu todo list. > > Carl: This should be fixed with the next d-i alpha/beta. This is great - thanks for this - I'll try these changes out tonight and let you know! -Carl > > Mraw, > KiBi. -- Carl Myers PGP Key ID 3537595B PGP Key fingerprint 9365 0FAF 721B 992A 0A20 1E0D C795 2955 3537 595B signature.asc Description: Digital signature
Bug#806849: debian-installer: d-i fails to install grub2 correctly for efi system using encrypted LVM
Package: debian-installer Version: stretch alpha 4 Severity: important Tags: d-i Dear Maintainer, I have a new System76 Oryx Pro laptop using efi boot. Ubuntu installs successfully but I can't get debian to install using encrypted LVM. The laptop has an nvme device which requires efi boot so I can't just disable it. Here are my repro steps: 1. Boot using netinst (tried both stable and testing, stable doesn't work at all I think due to efi?) 2. Performed normal install (tried both text and gui) 3. Included proprietary firmware for wifi from usb key when prompted 4. selected encrypted LVM with separate home partition, changed root partition to 20GB and made some other lvm adjustments 5. proceeded to install base system successfully 6. when it comes time to install grub, it fails. no better error message provided, nothing in /var/logs either The laptop came with working ubuntu on it, and I was able to boot from an ubuntu live CD. I was able to chroot into the installed system from here and everything looked right, but I still haven't figured out the right incantation of grub to get it to install so it will unlock my encrypted drive (right now, it does boot off the nvme device but drops me to a grub prompt). Short of becoming a grub wizard, the best way to get my system the way I want it is probaly to fix the installer =| if there is anything I can do to provide extra information, please do not hesitate to contact me. I also hang out on freenode as cmyers. Thanks! -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.5-x86_64-linode61 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#466819: fluxbox: Fluxbox menu integration on the fritz
Subject: fluxbox: Fluxbox menu integration on the fritz Package: fluxbox Version: 1.0.0+deb1-5 Severity: normal *** Please type your report below this line *** I have installed fluxbox to switch to that window manager (from Gnome) but the I found the menu empty. I was initially unable to do *anything* in fluxbox was was able to start a terminal/web browser from a virtual console. After extensive googling and searching I managed to tweak my fluxbox configs to get a menu with the following entries: Configuration Styles Workspaces Reconfigures Restart Exit No Applications, Games, etc. The following places seem to have inaccurate documentation: http://wiki.debian.org/FluxboxMenu This page says to gunzip and run fluxbox-generate_menu, which does not seem to exist. I also found inaccurate information here: /usr/share/doc/fluxbox/README.Debian It says: Currently, fluxbox supports the debian menu system, -however-, to use user-menus, you need to alter the ~/.fluxbox/init file. For using debian-menu You should set in Your ~/.fluxbox/init the session.menuFile option into value: session.menuFile: ~/.fluxbox/fluxbox-menu - if You want to manage the menu by starting update-menus by user session.menuFile: /etc/X11/fluxbox/fluxbox-menu - if You want to see the menu that is refreshed automatically as soon as programs are installed/deleted. You may also copy the file /etc/X11/fluxbox/fluxbox.menu-user into Your directory ~/.fluxbox and edit it additionally. --- These steps didn't work for me. The way I eventually solved my problem was by following the steps outlined in the now-closed bug #293755 Specifically, I added the line [include] (~/.fluxbox/menudefs.hook) to my ~/.fluxbox/menu file. Unless I'm missing something pretty big here, either this bug should be reopened until this line gets to the right place automagically, or the documentation should be modified to include this step. Thanks go out to schoinobates in #debian who assisted me in narrowing down the problem and pointed me to the bug reporting tool. Feel free to contact me with any further questions. Thanks! -Carl -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.troglobyte.20070923.1 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fluxbox depends on: ii libc6 2.7-8GNU C Library: Shared libraries ii libfontconfig1 2.5.0-2 generic font configuration library ii libgcc1 1:4.3-20080202-1 GCC support library ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libimlib2 1.4.0-1 powerful image loading and renderi ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-7X11 client-side library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxinerama11:1.0.2-1X11 Xinerama extension library ii libxpm4 1:3.5.7-1X11 pixmap library ii libxrandr2 2:1.2.2-1X11 RandR extension library ii libxrender1 1:0.9.4-1X Rendering Extension client libra ii menu2.1.37 generates programs menu for all me fluxbox recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
