Bug#704523: fixed IPv6 Configuration only in installer fails
On 2013-04-03 03:09, Ben Hutchings wrote: Control: tag -1 unreproducible On Wed, 2013-04-03 at 00:59 +0200, Samuel Thibault wrote: Philipp Kolmann, le Tue 02 Apr 2013 13:33:23 +0200, a écrit : On console 4 I see the following logmessage looping: nc_v6_interface_configured(eth0, scope global) Running ip addr show eth0 to look for address ip line: 2: eth0: mtu 1500 qd isc pfifo_fast qlen 1000 ip line: link/ether 00:50:56:be:XX:XX brd ff:ff:ff:ff:ff:ff ip line: inet6 2001:629:1005:323:250:56ff:febe:/64 scope global dynamic ip line: valid_lft 2591972sec preffered_lft 604772sec ip line: inet6 2001:629:1005:323::161/64 scope global tentative flags 08 ip line: valid_lft forever preffered_lft forever ip line: inet6 fe80::250:56ff:febe:/64 scope link ip line: valid_lft forever preffered_lft forever And the tentative flag never disappears? You should probably check why that doesn't happen, as that's what netcfg is waiting for AIUI. I just tested this configuration and as expected the tentative status goes away after 2 seconds. Your ip output includes 'flags 08' which corresponds to IFA_F_DADFAILED (duplicate address detection failed). Which means either someone else is already using the address you selected, or else a switch is reflecting the packets sent during DAD. Sorry for bothering. I had the IPv6 Address already in use, but not pingable, so I thought it was not in use. Everything works fine now. thanks Philipp -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/515bfa0b.3000...@kolmann.at
Bug#704523: marked as done (fixed IPv6 Configuration only in installer fails)
Your message dated Wed, 03 Apr 2013 11:44:43 +0200 with message-id <515bfa0b.3000...@kolmann.at> and subject line Re: Bug#704523: fixed IPv6 Configuration only in installer fails has caused the Debian Bug report #704523, regarding fixed IPv6 Configuration only in installer fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: iso mounted into virtual machine Image version: http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso Date: 2013-04-02 12:50:00 CEST Machine: VMware ESX 5.1 Virtual Machine, configured to run Debian 6.0 AMD 64 Processor: Intel Xeon E5-26500 (1vCPU) Memory: 1024MB Partitions: none specified Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: On my network we have IPv6 enabled. I wanted to configure the new box IPv6 only with a fixed Address to test. Booting off the RC1 ISO, I set following options Regular install Language: English Country: Austria Default Setting: en_US.UTF-8 Keymap: German At the nameserver screen I go back twice to specify a fixed IPv6 Address. IP Address: 2001:629:1005:323::161 Netmask: ::::: Gateway: 2001:629:1005:323::1 Nameservers: 2001:629:1001:1::53 2001:629:1001:2::53 Then the screen stays blue and never goes on. On console 4 I see the following logmessage looping: nc_v6_interface_configured(eth0, scope global) Running ip addr show eth0 to look for address ip line: 2: eth0: mtu 1500 qd isc pfifo_fast qlen 1000 ip line: link/ether 00:50:56:be:XX:XX brd ff:ff:ff:ff:ff:ff ip line: inet6 2001:629:1005:323:250:56ff:febe:/64 scope global dynamic ip line: valid_lft 2591972sec preffered_lft 604772sec ip line: inet6 2001:629:1005:323::161/64 scope global tentative flags 08 ip line: valid_lft forever preffered_lft forever ip line: inet6 fe80::250:56ff:febe:/64 scope link ip line: valid_lft forever preffered_lft forever On console 2 I can ping both nameservers but the installer hangs at a blue screen. Thanks Philipp --- End Message --- --- Begin Message --- On 2013-04-03 03:09, Ben Hutchings wrote: Control: tag -1 unreproducible On Wed, 2013-04-03 at 00:59 +0200, Samuel Thibault wrote: Philipp Kolmann, le Tue 02 Apr 2013 13:33:23 +0200, a écrit : On console 4 I see the following logmessage looping: nc_v6_interface_configured(eth0, scope global) Running ip addr show eth0 to look for address ip line: 2: eth0: mtu 1500 qd isc pfifo_fast qlen 1000 ip line: link/ether 00:50:56:be:XX:XX brd ff:ff:ff:ff:ff:ff ip line: inet6 2001:629:1005:323:250:56ff:febe:/64 scope global dynamic ip line: valid_lft 2591972sec preffered_lft 604772sec ip line: inet6 2001:629:1005:323::161/64 scope global tentative flags 08 ip line: valid_lft forever preffered_lft forever ip line: inet6 fe80::250:56ff:febe:/64 scope link ip line: valid_lft forever preffered_lft forever And the tentative flag never disappears? You should probably check why that doesn't happen, as that's what netcfg is waiting for AIUI. I just tested this configuration and as expected the tentative status goes away after 2 seconds. Your ip output includes 'flags 08' which corresponds to IFA_F_DADFAILED (duplicate address detection failed). Which means either someone else is already using the address you selected, or else a switch is reflecting the packets sent during DAD. Sorry for bothering. I had the IPv6 Address already in use, but not pingable, so I thought it was not in use. Everything works fine now. thanks Philipp--- End Message ---
Bug#704605: installation-reports: kernel panic Wheezy
Package: installation-reports Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Kernel Panic requiring hard reset possibly having to do with lightdm-gtk-gre * What exactly did you do (or not do) that was effective (or ineffective)? On the Wheezy RC1 I installed the linux-image-486 and got a similar result (kernel panics requiring hard reset), but I was able to use the system for a few minutes as opposed to panic on startup * What was the outcome of this action? kernel panic * What outcome did you expect instead? a normally functioning system (no kernel panics that lock the system, make it unusable and require a hard reset) *** End of the template - remove these lines *** -- Package-specific info: Boot method: CD Image version: cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ from April 2, 201 2013 Date: Machine: Dell Dimension 2400 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Two major problems: 1)kernel panic as described above 2)initial attempts to install failed and required a hard reset due to a cryptic error message(almost illegible): Undefined videomode number: 314. The workaround for this was to press TAB and set vga=normal instead of the default setting of 788. The only reason I was able to decipher this illegible message was to attempt to install Ubuntu 13.04 and I got the same message that was readable. The Ubuntu installation did not hang and was going to let me continue. -- 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: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130211" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux dellian 3.2.0-4-486 #1 Debian 3.2.35-2 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 81) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge [8086:24c0] (rev 01) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801DB (ICH4) IDE Controller [8086:24cb] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lspci -knn: 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01) lspci -knn: Subsystem: Dell Device [1028:0160] lsp
Re: Installation flash drive problem.
On Sun, Mar 24, 2013 at 09:44:19PM +1300, Philip Charles wrote:
>Hi,
Hi Philip,
> I have been playing with usb flash drives as installation media.
>
>The good news is that 64 bit installs nicely with the machine efi turned
>on and a home made 44.5GiB stick also installed.
Cool.
>The bad news is that once rebooted the system did not recognise the stick
>as the installation medium. If /etc/apt/apt.conf.d/00CDMountPoint is
>modified to read
>
>Acquire::cdrom {
> mount "/media/usb0;
>}
>Dir::Media::MountPath "/media/usb0";
>
>Then the stick will be recognised as the "cdrom".
>But the gui needs to be installed for this to work.
Right.
>Has any one else come accross this problem? If so do they have a
>solution? Should a bug report be filed? It is probably too late for a
>fix for Wheezy.
>However, with the wholesale price of 64GB sticks now being less than $10
>it seems that flash drives will be the installation media of the future.
You have a point, although it's not clear it's worth targeting such
large media for installation sources in most cases. More and more
people seem to be wanting network installations, in my experience.
Anyway, it's probably worth asking on d-boot too about this; CCing
there.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130403172320.ga...@einval.com
Bug#701884: kfreebsd: unknown method 'inet6 auto'
Control: tags -1 serious Justification: if an IPv6 route announcement is seen at install time, the kfreebsd-* system would have no network connectivity on first boot, ifup will fail and even the loopback interface will not be set up. Also IPv6 and GNU/kFreeBSD are both still release goals I believe. This has been fixed in sid for some time but we absolutely must see it fixed in wheezy. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/515c81c0.1040...@pyro.eu.org
Processed: Re: Bug#701884: kfreebsd: unknown method 'inet6 auto'
Processing commands for cont...@bugs.debian.org:
> # oops
> severity 701884 serious
Bug #701884 {Done: Andrew Shadura } [ifupdown,netcfg]
kfreebsd: unknown method 'inet6 auto'
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
701884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.136501728013646.transcr...@bugs.debian.org
Bug#704635: [Wheezy] Package authentication issue during base installation: BusyBox
Package: base-installer Version: 1.130 During the setup of a Debian Box (hardware: IBM NetVista A40 model 6840-QDG, 512 MB RAM, Promise Fastrak TX2300 SATA RAID and two Western Digital Caviar Red NAS 2 TB SATA hard drives configured as RAID-1 on it => dmraid=yes option at CD boot. Installation done using mini.iso and mirror.switch.ch as FTP source) I get a Apr 3 18:32:02 in-target: WARNING: The following packages cannot be authenticated! Apr 3 18:32:02 in-target: busybox Apr 3 18:32:02 in-target: E: There are problems and -y was used without --force-yes Apr 3 18:32:03 base-installer: error: exiting on error base-installer/kernel/failed-package-install error and the installation aborts during the base system phase with a red screen. Full details including syslog see http://beilagen.dreael.ch/Diverses/Bug_Wheezy_Install_BusyBox/ I hope this helps improve the next Debian release. :-) Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
