Bug#834974: Installation Report: Stretch Alpha 7 on Cubox-i4pro
On 2016-09-04, Rick Thomas wrote: > On Sep 4, 2016, at 3:12 AM, Rick Thomas wrote: > >>> On Sep 2, 2016, at 5:12 PM, Vagrant Cascadian wrote: >>> I'd be curious if you re-install and delete each partition individually and re-create manually vs. using one of the auto-partitioning methods. ... > I followed the standard script and did the Testing install. This time > I did the manual partitioning correctly, deleting the first (and only) > partition on the uSD and creating two partitions in the resulting free > space, i.e. /boot and root. > > As expected, when it came time to reboot from the installer to the > installed system, it hung and did not reboot. > > However, when I un-plugged and re-plugged the Cubox, just to see what > would happen, lo and behold, It booted! And the installed system > appears to be intact. Good! > The only unusual thing is that when it was starting up, u-boot > remarked, “*** Warning - bad CRC, using default environment”. What > this seems to be saying is that the “make bootable” part of the > installer is not putting the boot script (or, indeed, any of the > u-boot environment) where u-boot is expecting to find it. That warning is unnecessarily alarming, in my opinion. It basically means it's using the default, compiled-in environment variables, and with modern u-boot using distro_bootcmd, this is a good thing. If you save the environment variables, you don't benefit from fixes and improvements to the default environment in newer u-boot versions without manually resetting to the new compiled in defaults and then re-saving them each time you update u-boot. With distro_bootcmd, there should generally be no need to save the environment variables, just update the boot script(s) used to do various different things. With flash-kernel from stretch or jessie-backports, the boot scripts are customizable in /etc/flash-kernel/bootscripts/. > I wonder if it’s possible that the installer is using the wrong > version of “/etc/fw_env.config”? The installer doesn't, and in general, shouldn't mess with the u-boot environment in such an invasive way... at least on most of the armhf platforms I've dealt with. Maybe some older armel platforms need this. live well, vagrant signature.asc Description: PGP signature
Re: How to preseed.cfg with official installation cdrom
> > > > > > Well, Question: So what could one campaign or achieve as a volunteer to > > > help to fix this bug in end and in these cases and after all? Boo! some > > > secrets!?! Some Tips from your part for on how to help it from > > > here? Some pointers on how to precede for such cases? > > > > > > > Just do. > > > > Feel comfortable, accept the journey, > image being Livingstone, Marco Polo or another great traveller. > > Prepare an USB storage device. > > Boot from CDROM. > > At the boot menu of the installation CDROM > tell that preseed file is available at USB device. > > Keep feeling comfortable, overcome the nuisances. > Write about the journey.
Bug#836745: installation-reports: cant change monitor resolution to work.
Package: installation-reports Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * Problem at usb boot * Nothing I did was effective, I'm not linux expert, therefore using terminal is out of my knowledge * n\a * n/a *** End of the template - remove these template lines *** -- Package-specific info: Boot method: usb Image version: cant't provide that. its avl32 Date: Machine: mini desktop, celeron at 2 GHzGb RAM 160gb rom Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0 ] Detect network card:[0 ] Configure network: [0 ] Detect CD: [0 ] Load installer modules: [0 ] Clock/timezone setup: [0 ] User/password setup:[0 ] Detect hard drives: [0 ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == == Installer hardware-summary: == -- System Information: Debian Release: stretch/sid Architecture: i386 (i686) Kernel: Linux 4.4.6-rt13-avl1 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#836769: debian-installer: use DNS provided by the "router advertisement"
Package: debian-installer Severity: normal Tags: ipv6 Hi, In the network configuration panels, the system discovers the subnets and take automatically an ipv6. But it does not use automatically the list of DNS provided by the RA. Regards. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Processed: Re: Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel
Processing commands for cont...@bugs.debian.org: > unmerge 836679 Bug #836679 [src:linux-signed] DTBs are not included in signed kernel packages Bug #836255 [src:linux-signed] DTBs are no longer bundled Disconnected #836679 from all other report(s). > reassign 836679 flash-kernel Bug #836679 [src:linux-signed] DTBs are not included in signed kernel packages Bug reassigned from package 'src:linux-signed' to 'flash-kernel'. No longer marked as found in versions linux-signed/2. Ignoring request to alter fixed versions of bug #836679 to the same values previously set > severity 836679 normal Bug #836679 [flash-kernel] DTBs are not included in signed kernel packages Severity set to 'normal' from 'serious' > retitle 836679 Warning for missing DTB unclear Bug #836679 [flash-kernel] DTBs are not included in signed kernel packages Changed Bug title to 'Warning for missing DTB unclear' from 'DTBs are not included in signed kernel packages'. > thanks Stopping processing here. Please contact me if you need assistance. -- 836255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836255 836679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: How to preseed.cfg with official installation cdrom
On Mon, Sep 05, 2016 at 12:38:41PM +0200, Geert Stappers wrote: > > > > > > > > Well, Question: So what could one campaign or achieve as a volunteer to > > > > help to fix this bug in end and in these cases and after all? Boo! some > > > > secrets!?! Some Tips from your part for on how to help it from > > > > here? Some pointers on how to precede for such cases? > > > > > > > > > > Just do. > > > > > > > Feel comfortable, accept the journey, > > image being Livingstone, Marco Polo or another great traveller. > > > > Prepare an USB storage device. > > > > Boot from CDROM. > > > > At the boot menu of the installation CDROM > > tell that preseed file is available at USB device. > > > > Keep feeling comfortable, overcome the nuisances. > > > > Write about the journey. Plug a USB stick into a Linux machine. Format the USB stick as FAT32 Copy an example preseed file to the USB stick. Edit the preseed file as appropriate. As Geert says above Boot the install CD ROM - use the expert install. It's not too complicated and is documented in the install manual, wiki.debian.org or, if you have a Debian system, install debian-handbook Hope this helps, Andy C
Re: Debian kernel 4.7.2-1 build on Sid and Jessie fails
On Sat, Sep 3, 2016 at 10:30 AM, Ben Hutchings wrote: > > On Fri, 2016-09-02 at 16:49 +0100, Ben Hutchings wrote: > > On Fri, 2016-09-02 at 03:35 -0700, Jose R Rodriguez wrote: > > > > > > Niltze, all! > > > > > > Currently running Reiser4-patched kernel 4.7 built from pristine > > > source upstream: > > > > > > Linux mictlantecuhtli 4.7.0.tezcatlipoca #1 SMP PREEMPT Wed Aug 10 > > > 05:04:17 PDT 2016 x86_64 GNU/Linux > > > > > > On the other hand, I have experienced multiple issues building > > > Debian'ized kernel 4.7.2-1 -- first building on Jessie modified for > > > GCC 4.9; > > > and then attempting build on Jessie-built GCC 5.3. And finally I > > > attempted the build on Debian Unstable and it failed, as well. > > > Below are the offending sections -- which, by the way -- roughly > > > correspond in all instances of Debian and GCC: > > [...] > > > > This happens if you invoke debian/rules directly and not through dpkg- > > buildpackage. > > Rather, it can happen in some circumstances, but... > > > debian/rules.real does: > > > > ifdef OVERRIDE_HOST_TYPE > > CROSS_COMPILE := $(OVERRIDE_HOST_TYPE)- > > else ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH)) > > CROSS_COMPILE := $(DEB_HOST_GNU_TYPE)- > > else > > CROSS_COMPILE := > > endif > > > > So the assumption is that all those architecture variables, or none, > > are defined. dpkg-buildpackage does define them all. > > > > However, debian/rules does: > > > > DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) > > > > and does not define any other architecture variables. > > ...variable definitions in debian/rules don't automatically propagate > to debian/rules.real, so this doesn't explain the failure. And > although I have seen this failure myself, I can't reproduce it now. > > > We should probably include /usr/share/dpkg/architecture.mk in > > debian/rules instead. > > I now think it should be included in debian/rules.real. However, until > I have a way to reproduce the problem, I'm not going to attempt a fix. > > Ben. > > -- > Ben Hutchings > Once a job is fouled up, anything done to improve it makes it worse. I much appreciate your hints, Ben. The fault was mine. After a couple of days of struggle, I modified debian/rules.real by inserting a couple of extra directives and compared the generated debian/control file output with previous ones - which provided me relevant insight to correct my mistake and generate required *.udebs for d-i. Thank you again, Ben. Best Professional Regard. -- Jose R R http://metztli.it - Try at no charge http://b2evolution.net for http://OpenShift.com PaaS - from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
