Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Michael Gold (2014-03-04): > On Tue, Mar 04, 2014 at 15:11:22 +0100, Cyril Brulebois wrote: > > I suspect a bunch of things should be better with wheezy installation > > images, so I'm closing this bug report for the time being. Don't > > hesitate to reopen with details if you can still reproduce. > > > > (I'm also planning on publishing stable installation images with > > backported linux kernels, which should help in the “HW support in > > stable is behind” case.) > > Thanks. The xrandr problems went away at some point with an xorg > upgrade. Initially there were only LVDS and VGA outputs, but now HDMI > and 2 DisplayPort outputs are visible too (DP is untested; the others > all detect the proper modes). Great; thanks for the confirmation. Mraw, KiBi. signature.asc Description: Digital signature
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Hi! Am 29.08.2011 20:10, schrieb Michael Gold: > I had to connect an ethernet dongle because the onboard network port > wasn't detected by the installer; the onboard port worked after > upgrading to unstable. FWIW: I have the very same notebook (but the version without the nvidia card, only the intel one). Network controler is reported by lspci as: 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) Trying to install Squeeze, I found out, that it a) seems to need a newer kernel and b) needs some firmware files. Using the unofficial installer from kmuto at http://kmuto.jp/debian/d-i/ (I picked squeeze-custom-amd64-0614.iso as that one also contains the needed firmware file) worked for me. Best regards, Alexander -- 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/4e5de8eb.2040...@schmehl.info
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
On Tue, Aug 30, 2011 at 07:40:18 +0200, Christian PERRIER wrote: > If you're paranoid about this, I would recommend using the daily > netboot image. It downloads everything it installs on your target > machine, from the network, on authenticated archives. > The netboot image from debian may do that, but if you have no way to securely get at that... Cheers, Julien -- 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/20110830182542.gp2...@radis.liafa.jussieu.fr
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Quoting Michael Gold (mg...@qnx.com): > On Mon, Aug 29, 2011 at 19:55:38 +0100, Miguel Figueiredo wrote: > > > I wanted to install Debian unstable, but there are no cryptographic > > > signatures on the unstable installer snapshots, so I installed the > > > newest stable release and upgraded. > > > > [...] > > > > The daily images, and the checksums, can be found on: > > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ > > Thanks, but those checksums have little security value since they're not > cryptographically signed. Patches welcome. Apart from that, daily images are used...daily...but gazillion of testers for about 8 years now. So, well, it's your call to decide if that's secure enough for you. After all, they mostly use packagesfrom the official Debian archives and these *are* cryptographically signed. If you're paranoid about this, I would recommend using the daily netboot image. It downloads everything it installs on your target machine, from the network, on authenticated archives. signature.asc Description: Digital signature
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Lennart Sorensen, le Mon 29 Aug 2011 14:42:32 -0400, a écrit : > Optimus has no linux support at this time. No idea if it ever will. IIRC, there's a project on this. Enabling Optimus in the BIOS is useful anyway: it permits to choose between the Intel and NVIDIA chipsets, not only NVIDIA. Samuel -- 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/20110829191930.gc23...@type.famille.thibault.fr
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
On Mon, Aug 29, 2011 at 19:55:38 +0100, Miguel Figueiredo wrote: > > I wanted to install Debian unstable, but there are no cryptographic > > signatures on the unstable installer snapshots, so I installed the > > newest stable release and upgraded. > > [...] > > The daily images, and the checksums, can be found on: > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ Thanks, but those checksums have little security value since they're not cryptographically signed. -- Michael -- 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/20110829190646.ga15...@qnx.com
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Hi, [...] > I wanted to install Debian unstable, but there are no cryptographic > signatures on the unstable installer snapshots, so I installed the > newest stable release and upgraded. [...] The daily images, and the checksums, can be found on: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ -- Melhores cumprimentos/Best Regards, Miguel Figueiredo http://www.DebianPT.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/201108291955.38863.el...@debianpt.org
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
On Mon, Aug 29, 2011 at 02:10:07PM -0400, Michael Gold wrote: > Package: installation-reports > Version: 2.45 > Severity: wishlist > > -- Package-specific info: > > Boot method: USB > Image version: debian-6.0.1a-amd64-i386-netinst.iso (SHA1 > fec4209384a78f304817ee8f6a4ce89acbb57e21) > Date: 2011-07-14T09:41-0400 > > Machine: Dell Latitude E6520 > Partitions: > Disk /dev/sda: 60801 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End #cyls#blocks Id System > /dev/sda1 * 0+243-243- 1951744 83 Linux > /dev/sda2243+ 60801- 60559- 486432768 8e Linux LVM > /dev/sda3 0 - 0 00 Empty > /dev/sda4 0 - 0 00 Empty > > > Base System Installation Checklist: > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > Initial boot: [O] > Detect network card:[E] > Configure network: [O] > Detect CD: [O] (see comments) > Load installer modules: [O] > Detect hard drives: [O] > Partition hard drives: [O] > Install base system:[O] > Clock/timezone setup: [O] > User/password setup:[O] > Install tasks: [O] > Install boot loader:[O] > Overall install:[O] > > Comments/Problems: > > I wanted to install Debian unstable, but there are no cryptographic > signatures on the unstable installer snapshots, so I installed the > newest stable release and upgraded. I had to connect an ethernet dongle > because the onboard network port wasn't detected by the installer; the > onboard port worked after upgrading to unstable. > > After installation, I was initially unable to select my LCD's native > resolution via xrandr. The onboard nVidia controller doesn't seem to be > supported by KMS/X, so X had fallen back to the VESA driver. I enabled > "Optimus" in the BIOS (even though the BIOS's help text claims this will > only work with Windows), and an additional Intel video chip appeared in > the lspci output: > 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation > Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) > Subsystem: Dell Device [1028:0494] > Kernel driver in use: i915 > > With Optimus enabled, X will ignore the nVidia chip and use the Intel > chip which does have proper modesetting support. > > I installed from a USB storage device, and the installer wrote an fstab > entry for /dev/sdb with mountpoint /dev/cdrom0 and type "udf,iso9660" > (the real DVD drive was listed as /dev/cdrom1). This prevented GNOME > from mounting FAT-formatted USB storage devices. The installer > shouldn't write an fstab entry for an installation device that's > connected via USB. Optimus has no linux support at this time. No idea if it ever will. Your network controller device was added in Linux 2.6.35, so no support in Squeeze's 2.6.32 kernel at this time unless it is backported. -- Len Sorensen -- 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/20110829184232.gj15...@caffeine.csclub.uwaterloo.ca
Bug#639728: Dell Latitude E6520: bad fstab entry, unsupported network controller
Package: installation-reports Version: 2.45 Severity: wishlist -- Package-specific info: Boot method: USB Image version: debian-6.0.1a-amd64-i386-netinst.iso (SHA1 fec4209384a78f304817ee8f6a4ce89acbb57e21) Date: 2011-07-14T09:41-0400 Machine: Dell Latitude E6520 Partitions: Disk /dev/sda: 60801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 * 0+243-243- 1951744 83 Linux /dev/sda2243+ 60801- 60559- 486432768 8e Linux LVM /dev/sda3 0 - 0 00 Empty /dev/sda4 0 - 0 00 Empty Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [O] Detect CD: [O] (see comments) Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I wanted to install Debian unstable, but there are no cryptographic signatures on the unstable installer snapshots, so I installed the newest stable release and upgraded. I had to connect an ethernet dongle because the onboard network port wasn't detected by the installer; the onboard port worked after upgrading to unstable. After installation, I was initially unable to select my LCD's native resolution via xrandr. The onboard nVidia controller doesn't seem to be supported by KMS/X, so X had fallen back to the VESA driver. I enabled "Optimus" in the BIOS (even though the BIOS's help text claims this will only work with Windows), and an additional Intel video chip appeared in the lspci output: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) Subsystem: Dell Device [1028:0494] Kernel driver in use: i915 With Optimus enabled, X will ignore the nVidia chip and use the Intel chip which does have proper modesetting support. I installed from a USB storage device, and the installer wrote an fstab entry for /dev/sdb with mountpoint /dev/cdrom0 and type "udf,iso9660" (the real DVD drive was listed as /dev/cdrom1). This prevented GNOME from mounting FAT-formatted USB storage devices. The installer shouldn't write an fstab entry for an installation device that's connected via USB. - Michael -- 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="6.0 (squeeze) - installer build 20110106+squeeze1" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux kain 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0104] (rev 09) lspci -knn: Subsystem: Dell Device [1028:0494] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Sandy Bridge PCI Express Root Port [8086:0101] (rev 09) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: Dell Device [1028:0494] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) lspci -knn: Subsystem: Dell Device [1028:0494] lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) lspci -knn: Subsystem: Dell Device [1028:0494] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 04) lspci -knn: Subsystem: Dell Device [1028:0494] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 3 [8086:1c14] (rev b4) lspci -knn: Kernel driver in use: pcieport lspci -k
