Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
Package: installation-reports Severity: critical Tags: newcomer Hello. After installation Debian Jessie with the debian jessie di-rc1 network installer I have no notwork interfaces after boot the installed system. My Laptop is a ASUS PRO7BSV. I have use my wlan to install and download the packages from the internet, but after the installation, no network cards with ifconfig found. After installation my /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] 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: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20131124-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:836b] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) lspci -knn: 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) lspci -knn: 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) lspci -knn: 00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82ea] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 [8086:3a44] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 [8086:3a48] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn:
Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
Am Sonntag, 8. Februar 2015, 10:39:28 schrieb Karsten Merker: > On Sun, Feb 08, 2015 at 10:24:16AM +0100, Heiko Ernst wrote: > > Package: installation-reports > > Severity: critical > > Tags: newcomer > > > > Hello. > > > > After installation Debian Jessie with the debian jessie di-rc1 network > > installer I have no notwork interfaces after boot the installed system. My > > Laptop is a ASUS PRO7BSV. I have use my wlan to install and download the > > packages from the internet, but after the installation, no network cards > > with ifconfig found. > > > > After installation my /etc/network/interfaces > > > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > Hello, > > could you provide the output of the "dmesg" command on the installed > system? > > Regards, > Karsten [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=3bc199dc-c4e3-41b1-907d-ce1e1ccfb355 ro quiet [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x3fff] usable [0.00] BIOS-e820: [mem 0x4000-0x401f] reserved [0.00] BIOS-e820: [mem 0x4020-0xaabd1fff] usable [0.00] BIOS-e820: [mem 0xaabd2000-0xaacf8fff] reserved [0.00] BIOS-e820: [mem 0xaacf9000-0xaacfafff] usable [0.00] BIOS-e820: [mem 0xaacfb000-0xaad8dfff] reserved [0.00] BIOS-e820: [mem 0xaad8e000-0xaad8efff] usable [0.00] BIOS-e820: [mem 0xaad8f000-0xaadb7fff] reserved [0.00] BIOS-e820: [mem 0xaadb8000-0xaadc7fff] usable [0.00] BIOS-e820: [mem 0xaadc8000-0xaade7fff] reserved [0.00] BIOS-e820: [mem 0xaade8000-0xaaf18fff] usable [0.00] BIOS-e820: [mem 0xaaf19000-0xaafe7fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaafe8000-0xaaffcfff] usable [0.00] BIOS-e820: [mem 0xaaffd000-0xaaff] ACPI data [0.00] BIOS-e820: [mem 0xab00-0xaf9f] reserved [0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed13fff] reserved [0.00] BIOS-e820: [mem 0xfed18000-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff98-0xffbf] reserved [0.00] BIOS-e820: [mem 0xffd8-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00014fdf] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.6 present. [0.00] DMI: ASUSTeK Computer Inc. N73SV/N73SV, BIOS N73SV.306 08/18/2011 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x14fe00 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-E7FFF uncachable [0.00] E8000-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 08000 mask FE000 write-back [0.00] 2 base 0A000 mask FF800 write-back [0.00] 3 base 0A800 mask FFC00 write-back [0.00] 4 base 0AB00 mask FFF00 uncachable [0.00] 5 base 1 mask FC000 write-back [0.00] 6 base 14000 mask FF000 write-back [0.00] 7 base 14FE0 mask FFFE0 uncachable [0.00] 8 disabled [0.00]
Bug#777459: debian installer firmware loader problem
Package: installation-reports Severity: critical Tags: newcomer I have a problem in debian jessie DI-rc1 installer. It need the Firmware iwlwifi-100-5 iwlwifi-100-4 iwlwifi-100-3 iwlwifi-100-2 iwlwifi-100-1 iwlwifi-100-5 iwlwifi-100-4 iwlwifi-100-3 iwlwifi-100-2 iwlwifi-100-1. But only iwlwifi-100-5 is needed. After loading of iwlwifi-1000-5 there can be checked whether the other files are still made? -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] 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: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20131124-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:836b] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) lspci -knn: 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) lspci -knn: 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) lspci -knn: 00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82ea] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3 [8086:3a44] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 [8086:3a48] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 [8086:3a34] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 [8086:3a35] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn:
Bug#777439: the newcomer tags is for bugs easily solvable by newcomers
control: tags -1 - newcomer thanks Hi Heiko, thanks for your bug reports! It seems you misunderstood something, the newcomer tags is for bugs easily solvable by newcomers, not for bugs filed by newcomers. Is there maybe some documentation which could be made more clear? cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: the newcomer tags is for bugs easily solvable by newcomers
Processing control commands: > tags -1 - newcomer Bug #777459 [installation-reports] debian installer firmware loader problem Removed tag(s) newcomer. -- 777459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777459 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: https://lists.debian.org/handler.s.b777459.142340252010357.transcr...@bugs.debian.org
Processed: the newcomer tags is for bugs easily solvable by newcomers
Processing control commands: > tags -1 - newcomer Bug #777439 [installation-reports] Jessie DI-rc1 amd64 after installation no network interfaces Removed tag(s) newcomer. -- 777439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777439 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: https://lists.debian.org/handler.s.b777439.142340252010348.transcr...@bugs.debian.org
Bug#777439: marked as done (Jessie DI-rc1 amd64 after installation no network interfaces)
Your message dated Sun, 08 Feb 2015 15:10:15 + with message-id <1423408215.2349.132.ca...@decadent.org.uk> and subject line Re: Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces has caused the Debian Bug report #777439, regarding Jessie DI-rc1 amd64 after installation no network interfaces 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.) -- 777439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: critical Tags: newcomer Hello. After installation Debian Jessie with the debian jessie di-rc1 network installer I have no notwork interfaces after boot the installed system. My Laptop is a ASUS PRO7BSV. I have use my wlan to install and download the packages from the internet, but after the installation, no network cards with ifconfig found. After installation my /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] 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: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20131124-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:836b] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) lspci -knn: 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) lspci -knn: 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) lspci -knn: 00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn:
Bug#777459: marked as done (debian installer firmware loader problem)
Your message dated Sun, 08 Feb 2015 15:10:54 + with message-id <1423408254.2349.133.ca...@decadent.org.uk> and subject line Re: Bug#777459: debian installer firmware loader problem has caused the Debian Bug report #777459, regarding debian installer firmware loader problem 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.) -- 777459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: critical Tags: newcomer I have a problem in debian jessie DI-rc1 installer. It need the Firmware iwlwifi-100-5 iwlwifi-100-4 iwlwifi-100-3 iwlwifi-100-2 iwlwifi-100-1 iwlwifi-100-5 iwlwifi-100-4 iwlwifi-100-3 iwlwifi-100-2 iwlwifi-100-1. But only iwlwifi-100-5 is needed. After loading of iwlwifi-1000-5 there can be checked whether the other files are still made? -- Package-specific info: Boot method: Image version: Date: Machine: Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] 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: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="8 (jessie) - installer build 20131124-00:05" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux debian 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port [8086:3405] (rev 13) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:836b] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:14.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) lspci -knn: 00:14.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) lspci -knn: 00:14.2 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) lspci -knn: 00:14.3 PIC [0800]: Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: ehci-pci lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82ea] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Thu, Dec 18, 2014 at 03:04:38PM +0100, Peter Valdemar Mørch wrote: > netcfg: Do not kill_dhcp_client after setting the hostname and domain, > otherwise Linux udhcpc will stop renewing its lease, and on other > platforms dhclient will de-configure the network interface (#757711, > #757988). The call chain is this: udpkg --configure --force-configure netcfg \_ netcfg Z \_ dhcp6c \_ udhcpc udpkg does not collect netcfg's exit code. Instead it continues poll()ing to forward stderr. It receives the SIGCHLD but does not act upon it with a wait() or waitpid(). The function udpkg uses to invoke netcfg's configure comes from libdebian-installer: [...] snprintf(buf, sizeof(buf), "exec %s configure", config); if ((r = di_exec_shell_log(buf)) != 0) [...] Essentially dhcp6c and udhcpc need to be daemonized off correctly once they go into "lease acquired, renew in the background" mode and close their file descriptors[*]. However doing that early likely loses logging, so it'd be best if the programs would do the right thing. At least udhcpc calls bb_daemonize(0), which doesn't do any fd closing. For dhcp6c (wide-dhcpv6-client) we currently force foreground mode (-f). It is not sufficient for netcfg to simply close stderr, as all producers need to close it, as far as I understand. On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. Kind regards Philipp Kern [*] It has been a long-standing problem with some d-i (maybe just Ubuntu with isc-dhcp-client) that leases are not renewed during the runtime of the installation. Which might break networking when the switch throws you off post-expiry. signature.asc Description: Digital signature
Bug#777474: Saving logs to first-user account just installed (wishlist)
Package: installation-reports Boot method: USB image Image version: CD Debian GNU/Linux testing "Jessie" - Official Snapshot i386 NETINST Binary-1 20150126-04:46 Date: 20150129-12:00 Machine: OptiPlex GX520 A11 (11/30/06) Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz Memory: 2.0 GB 533 MHz Dual Interleaved DDR2 SDRAM Partitions: /dev/disk/by-label/ezra02 ext4 28798012 3792184 23519900 14% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 412500 6320406180 2% /run tmpfs tmpfs 103124480 1031164 1% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 1031244 0 1031244 0% /sys/fs/cgroup /dev/sdb1 fuseblk 102396 24712 77684 25% /media/olaf01 /dev/sdb2 fuseblk 78020548 22018424 56002124 29% /media/olaf02 /dev/sda1 ext4 28608412 11128372 16003752 42% /agogs /dev/sda3 ext4 419068132 103884372 293873220 27% /home tmpfs tmpfs 20625212206240 1% /run/user/118 tmpfs tmpfs 206252 0206252 0% /run/user/1000 Output of lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02) 00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) 00:02.1 Display controller [0380]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2776] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01) 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 01) 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 01) 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 01) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1) 00:1e.2 Multimedia audio controller [0401]: Intel Corporation 82801G (ICH7 Family) AC'97 Audio Controller [8086:27de] (rev 01) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01) 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) 00:1f.2 IDE interface [0101]: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01) 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 01) 02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express [14e4:1677] (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [*] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments: A successful non-graphical expert install. Thanks very much for all the hard work. * Only used partitioner to reformat sda2, and avoided touching swap partition. The ability of the installer's "partitioner" to avoid touching the partition table (and reformatting any of their contents) could perhaps be spelled out more emphatically nowadays because some people have issues with precisely which partition program touches their disk(s). Problems: Wishlist: I would like to be able to copy the installation logs to /target/home// (using the option "Mounted Filesystem") so that when first-user reboots the system, the logs are all there in ~/install/ ready for consultation and archival. Unfortunately, all the while that "Save Logs" is available as an optional step, /target/home// does not yet exist because the accounts are only created *after* "Finish Installation" is executed. There may be an ugly hack: let "Finish Installation" create the user accounts and ask about the RTC. Use the opportunity on these screens to "Go Back" and then "Save Logs". Now repeat "Finish Installation". The user accounts are recreated, and I assume (unchecked) that extra files in /target/home// are not an issue (one can install with
Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
On Sun, 08 Feb 2015 15:10:15 + Ben Hutchings wrote: > On Sun, 2015-02-08 at 10:24 +0100, Heiko Ernst wrote: > > Package: installation-reports > > Severity: critical > > Tags: newcomer > > > > Hello. > > > > After installation Debian Jessie with the debian jessie di-rc1 network > > installer I have no notwork interfaces after boot the installed system. > > Based on the log, I don't think that's correct. > > > My > > Laptop is a ASUS PRO7BSV. I have use my wlan to install and download the > > packages from the internet, but after the installation, no network cards with > > ifconfig found. > > By default, ifconfig lists only the interfaces that are up. Use 'ip l' > or 'ifconfig -a' to list all interfaces. > > > After installation my /etc/network/interfaces > > > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > This is normal behaviour after installing the Desktop task. You should > then use Network Manager to configure the network interfaces. I have no install a Desktop system only a shell, "ifconfig -a" show all devices yes but how can I configure the devices that they are up on start and why do this not the installer ? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6881726.9TWnxPdOSE@debian
Re: Bug#776928: unblock: debian-installer-netboot-images/20150107
(Adding -boot@ for reference.)
Hi,
Niels Thykier (2015-02-06):
> A debhelper compat is an explicit no-go per the freeze policy.
>
> Otherwise, looks good to me.
It's a bit unfortunate that d-i-n-i is huge and not too useful to upload
during the release cycle in that we get to only notice this kind of
things ("woops, we bumped the debhelper version compat in that package
too but it never reached testing") during the freeze; sorry about that.
Since d-i-n-i is basically about collecting files in packages (see
get-images.sh), and about shipping them through various binaries, this
kind of things is /possibly/ harmless, but I really didn't check
anything. It would probably be helpful to double check that dh 7 and dh
9 lead to identical binaries, and maybe think about letting this change
slide with the rest (but so far I really have no opinion on this).
In case the explicit no-go stays (which I'd consider fair, to be
honest), I'd rather avoid doing nasty things with the release version
numbering (see Holger's reply), and get the revert through an upload
matching RC 2. Which means getting d-i-n-i even later in testing but
that would probably be safer.
On a slightly different note: Why we're still using a non-debian.org
mirror (MIRROR in debian/rules) is still beyond me.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Bug#777474: Saving logs to first-user account just installed (wishlist)
Hi, Thanks for the feedback. David Wright (2015-02-08): > Wishlist: I would like to be able to copy the installation logs to > /target/home// (using the option "Mounted Filesystem") so > that when first-user reboots the system, the logs are all there in > ~/install/ ready for consultation and archival. > > Unfortunately, all the while that "Save Logs" is available as an > optional step, /target/home// does not yet exist because > the accounts are only created *after* "Finish Installation" is > executed. > > There may be an ugly hack: let "Finish Installation" create the user > accounts and ask about the RTC. Use the opportunity on these screens > to "Go Back" and then "Save Logs". Now repeat "Finish Installation". > The user accounts are recreated, and I assume (unchecked) that extra > files in /target/home// are not an issue (one can install > with a populated /home). Maybe I should ask this first: why do installer logs need to be saved under /target/home/ while they're already available under (/target)/var/log/installer by default? Mraw, KiBi. signature.asc Description: Digital signature
Bug#777474: Saving logs to first-user account just installed (wishlist)
Quoting Cyril Brulebois (k...@debian.org): > David Wright (2015-02-08): > > Wishlist: I would like to be able to copy the installation logs to > > /target/home// (using the option "Mounted Filesystem") so > > that when first-user reboots the system, the logs are all there in > > ~/install/ ready for consultation and archival. > Maybe I should ask this first: why do installer logs need to be saved > under /target/home/ while they're already available under > (/target)/var/log/installer by default? Only a wish (not a need); because I will own them (I presume) and I browse/archive them from mc which I don't trust to run as root. Sorry it's not a compelling reason for any degree of hard work to change! > Mraw, I think you've just expanded my vocabulary. Cheers, David. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150208230028.ga18...@alum.home
Bug#775395: partman-zfs in d-i jessie image does not create grub-compatible /boot ZFS mirror
This may help... 10.1 added a bunch of feature flags that grub may need to now support in the ZFS code and are probably tripping this all up. http://www.daemon-security.com/blog-2014.html Regards, Mike On 01/27/2015 02:19 PM, Steven Chamberlain wrote: > Control: severity -1 important > > Michael Milligan wrote: >> Package: partman-zfs >> Version: 42 >> Severity: grave >> Tags: d-i >> Justification: renders package unusable for ZFS-based install >> >> (which is probably the reason someone is trying Debian/kFreeBSD .. to >> use ZFS) > Since this is a kfreebsd-any package, and we're not part of the > official stable release, I have to lower this to non-RC severity. > > We should still fix it for the GNU/kFreeBSD release though. > > Regards,
Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
Control: reopen -1 Control: reassign -1 netcfg On Sun, 2015-02-08 at 19:09 +0100, Heiko Ernst wrote: > On Sun, 08 Feb 2015 15:10:15 + Ben Hutchings wrote: [...] > > This is normal behaviour after installing the Desktop task. You should > > then use Network Manager to configure the network interfaces. > > I have no install a Desktop system only a shell, "ifconfig -a" show all > devices > yes but how can I configure the devices that they are up on start and why do > this not the installer ? OK, then this is not expected. Ben. -- Ben Hutchings Editing code like this is akin to sticking plasters on the bleeding stump of a severed limb. - me, 29 June 1999 signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
Processing control commands:
> reopen -1
Bug #777439 {Done: Ben Hutchings } [installation-reports]
Jessie DI-rc1 amd64 after installation no network interfaces
Bug reopened
Ignoring request to alter fixed versions of bug #777439 to the same values
previously set
> reassign -1 netcfg
Bug #777439 [installation-reports] Jessie DI-rc1 amd64 after installation no
network interfaces
Bug reassigned from package 'installation-reports' to 'netcfg'.
Ignoring request to alter found versions of bug #777439 to the same values
previously set
Ignoring request to alter fixed versions of bug #777439 to the same values
previously set
--
777439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777439
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:
https://lists.debian.org/handler.s.b777439.142345719926836.transcr...@bugs.debian.org
Bug#777439: Jessie DI-rc1 amd64 after installation no network interfaces
On Mon, 09 Feb 2015 04:46:17 + Ben Hutchings wrote: > OK, then this is not expected. This is my etc/network/interfaces file I have wrote hope this is a workaround for this time but why show me the network manager in kde not the connection? I see only a ? over the icon. --- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # The wlan interface auto wlan0 iface wlan0 inet dhcp wpa-ssid $myssid wpa-psk xx wpa-key-mgmt WPA-PSK -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/29658599.tJVmDS0lqi@debian
