Bug#989066: torrent no fun
On Mon, 2021-05-24 at 15:19 -0700, ddueh...@verizon.net wrote: > > Comments/Problems: > > It’s far easier to just download an image than to try to figure out how to > download via bittorrent. The downloads are small enough that I can wait for them to download. I spent much more time finding a non-malware bittorrent client for Windows where I’m creating a ISO USB for a Debian based Zoom kiosk type install. You should make download by bit torrent an option not a requirement. Obviously this bothered me enough to send this email. You don't mention where you started looking, or what image you downloaded, but there is not any requirement to download via bittorrent. Look here: https://cdimage.debian.org/cdimage/
Re: serial console install issues
On Sun, 2021-04-11 at 21:18 +1200, Richard Hector wrote:
>
> I think so, yes. But my problems started earlier than booting linux, at
> the SysLinux menu. Perhaps what's needed is more of an appendix for
> dealing with serial consoles?
>
> Anyway, I'll try to be more helpful tomorrow :-)
I tried to help Richard's quest on IRC a little. One of the issues was that his
first serial TTY lashup did not include arrow keys, for navigating the choices
of the boot menu. It would help if any additions to the documentation for the
serial console could include mention of ctrl-N ("Next") for down arrow, and
ctrl-P ("previous") for up arrow.
Thanks.
LWP
Re: Installing firmware and ISO images on CD/DVD
On Tue, 2021-02-09 at 07:22 -0500, Jeffrey Walton wrote: > Hi Everyone, > > I'd like to install the additional firmware required for PowerPC. It > is briefly discussed at > https://www.debian.org/releases/jessie/amd64/ch06s04.html.en. > > The problem I am having is, PowerMac's don't have an eject button. I > can't eject the installer to add the firmware CD from > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/8.10.0+nonfree/powerpc/iso-cd/. > I tried to use a USB stick but the firmware was not found. (I don't > even think the USB bus was scanned - the led on the usb stick did not > blink). > > I think the installer should be modified in two places to support an > eject operation. The first place is the "Missing firmware" screen. The > second place is the "Configure Apt" screen. > > Jeff > The second CD you reference [8.10.0+nonfree] is both an installer and a source of firmware files. You should be able to install without ejecting, I think?
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote: > > But, as I think I mentioned earlier, I am very reluctant indeed to mess > around with Windows itself. > I have backed up the user data, but I am not at all sure how to > re-install Windows itself. If the machine failed I suspect I would take > it to a specialist with a copy of the user data. I suggest at this point you should try out one of the debian "live" images. These can be copied to a USB stick (via win32diskimager or others) just like you copied the installer to USB. Then, you boot into the live image and it runs completely from the USB stick -- you have a mostly complete linux system you can experiment with, without permanently writing it onto any other disks, and without the live system needing to write to any other disks. I would suggest the current stable "gnome" live system, which is familiar to Windows users -- and I also suggest the so-called "non-free" version (which just means it includes various firmware files for wifi or fancy graphics adapters, etc.) Download here: https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/current-live/amd64/iso-hybrid/debian-live-10.8.0-amd64-gnome+nonfree.iso
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 22:59 +, Bernard McNeill wrote: > > On 08/02/2021 22:44, Lou Poppler wrote: > > On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote: > > [...] > > > I have one SSD (which has Win-10 on it), there is no other disk > > > (spinning or otherwise) on the machine. > > > The BIOS System Information says 'M.2. SATA =(none)' > > > and 'M.2. PCIe SSD-0=87NB51ASK5HS'. > > > However: Under BIOS System Configuration, 'SATA Operation' is set to > > > 'RAID On', [other options are 'Disabled' and 'AHCI' ]. > > > > > > > Interesting that Dell is making a distinction here between SATA and PCIe > > mass > > storage, but calling its RAID foolishness "SATA Operation - RAID On". > > Does this imply maybe that the SSD connected via PCIe and not via the SATA > > wiring/controller, is exempt from the RAID interference? I don't know. > > > > It sure would be nice if that is what they mean though. > > Maybe you can carefully test how this really works. > > (Make the backup first though) > > > > > > Is it even possible to RAID an SDD? > With software RAID, you can combine all manner of storage devices into a "managed device" even different physical types of storage. What this built-in factory RAID might be is unclear to me. From the misbehavior of the system regarding your sometimes attached external USB disk (with the attempted debian install on it) it seems likely that the factory/BIOS RAID thing might be interposing itself between disks as seen by running programs (like the debian installer) and the actual hardware storage itself. > But, as I think I mentioned earlier, I am very reluctant indeed to mess > around with Windows itself. > I have backed up the user data, but I am not at all sure how to > re-install Windows itself. If the machine failed I suspect I would take > it to a specialist with a copy of the user data.
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote: [...] > I have one SSD (which has Win-10 on it), there is no other disk > (spinning or otherwise) on the machine. > The BIOS System Information says 'M.2. SATA =(none)' > and 'M.2. PCIe SSD-0=87NB51ASK5HS'. > However: Under BIOS System Configuration, 'SATA Operation' is set to > 'RAID On', [other options are 'Disabled' and 'AHCI' ]. > Interesting that Dell is making a distinction here between SATA and PCIe mass storage, but calling its RAID foolishness "SATA Operation - RAID On". Does this imply maybe that the SSD connected via PCIe and not via the SATA wiring/controller, is exempt from the RAID interference? I don't know. It sure would be nice if that is what they mean though. Maybe you can carefully test how this really works. (Make the backup first though)
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 22:26 +, Bernard McNeill wrote: > > On 08/02/2021 21:57, Lou Poppler wrote: > > On Mon, 2021-02-08 at 20:47 +, Bernard McNeill wrote: > > > > > > On 08/02/2021 20:33, Cyril Brulebois wrote: > > > > Bernard McNeill (2021-02-08): > > > > > It says to 'Change the SATA from RAID On to AHCI, without this change > > > > > Linux > > > > > will not find SSD'. > > > > > Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my > > > > > copy of this model - so not relevant ? > > > > > > > > Used for almost anything really, HDD, SSD, USB sticks, etc. > > > > > > > > > In passing, I note the same link shows a need to disable Secure Boot - > > > > > is this now obsolete? > > > > > > > > Likely. We've started supporting SB with Debian 10 (buster). > > > > > > > > > > > > Cheers, > > > > > > > > > > If I change the SATA from RAID On to AHCI, do I mess up whatever is > > > currently on the SSD? > > > > > > Best regards > > > > > > > See > > https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984 > > > > You have Windows on a regular, spinning hard disk in the machine, and you > > also have an > > unused SSD -- is this correct? Or maybe they are already RAIDed together > > by the factory? > > > > I thing especially if you are now introducing a third external disk to the > > mix, you probably > > do not want this factory RAID thing, but I don't know how safe it is to > > turn it off if you > > already have two mass-storage devices controlled by the thing. > > > > + You have Windows on a regular, spinning hard disk in the machine, and > + you also have an > + unused SSD -- is this correct? Or maybe they are already RAIDed > + together by the factory? > I have one SSD (which has Win-10 on it), there is no other disk > (spinning or otherwise) on the machine. > The BIOS System Information says 'M.2. SATA =(none)' > and 'M.2. PCIe SSD-0=87NB51ASK5HS'. > However: Under BIOS System Configuration, 'SATA Operation' is set to > 'RAID On', [other options are 'Disabled' and 'AHCI' ]. > > Best regards That Dell Community webpage also says there is a *chance* that you can change the BIOS option, and get into Windows "safe mode" and recover. I strongly suggest making a backup now, of anything in the windows install that you do not want to lose. [ also note, I made a couple small modernizing edits to https://wiki.debian.org/InstallingDebianOn/Dell/Dell_XPS_13_9360 ]
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 14:57 -0700, Lou Poppler wrote: > > See > https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984 > Reading more on that page looks like you should not change the setting unless you are prepared to re-install your Windows; but also looks like you cannot install linux beside your Windows unless you _DO_ change the setting. Can you backup and then restore your existing windows setup?
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 20:47 +, Bernard McNeill wrote: > > On 08/02/2021 20:33, Cyril Brulebois wrote: > > Bernard McNeill (2021-02-08): > > > It says to 'Change the SATA from RAID On to AHCI, without this change > > > Linux > > > will not find SSD'. > > > Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my > > >copy of this model - so not relevant ? > > > > Used for almost anything really, HDD, SSD, USB sticks, etc. > > > > > In passing, I note the same link shows a need to disable Secure Boot - > > > is this now obsolete? > > > > Likely. We've started supporting SB with Debian 10 (buster). > > > > > > Cheers, > > > > If I change the SATA from RAID On to AHCI, do I mess up whatever is > currently on the SSD? > > Best regards > See https://www.dell.com/community/XPS/Pros-Cons-AHCI-vs-Raid-On-XPS13-9300-NVMe/td-p/7636984 You have Windows on a regular, spinning hard disk in the machine, and you also have an unused SSD -- is this correct? Or maybe they are already RAIDed together by the factory? I thing especially if you are now introducing a third external disk to the mix, you probably do not want this factory RAID thing, but I don't know how safe it is to turn it off if you already have two mass-storage devices controlled by the thing.
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 20:07 +, Bernard McNeill wrote: [...] > I was planning the re-install, and came across this page: > https://wiki.debian.org/InstallingDebianOn/Dell/Dell_XPS_13_9360 > > It says to 'Change the SATA from RAID On to AHCI, without this change > Linux will not find SSD'. > Questions: 1. To me, SATA is a reference to HDD, no internal HDD on my > copy of this model - so not relevant ? > 2. I don't care if Linux just 'finds' the SSD. >But I care very greatly about Linux _disturbing_ the > contents of the SSD - I consider this Win-10's domain. >Do I need to worry about this? SATA is the wiring/controller for the internal storage, spinning or SSD. I don't see why you should change it. I am suspicious of the idea of some kind of Dell RAID settings though. Are you using or planing to use a RAID setup? > In passing, I note the same link shows a need to disable Secure Boot - > is this now obsolete? Yes, you can leave Secure Boot on, modern debian versions are fine with that.
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Mon, 2021-02-08 at 11:46 +, Bernard McNeill wrote: > > On 07/02/2021 22:26, Lou Poppler wrote: > > On Sun, 2021-02-07 at 15:14 -0700, Lou Poppler wrote: > > > On Sun, 2021-02-07 at 20:44 +, Bernard McNeill wrote: > > > > [...] > > > > Trial-1. Reboot, no attempt to use F12. > > > > Boots directly into Windows. > > > > > > > > [...] > > > See install manual https://www.debian.org/releases/stable/installmanual > > > > > > Also worth asking: > > > . Is the machine booting in BIOS mode or UEFI mode, with or without > > > "Secure Boot"? Was the machine booting in that same mode during your > > > debian installation? > > > . Are the "disks" involved both/all partitioned in the same schema -- > > >i.e. GPT partitions or MBR partitions? > > > > I forgot when writing the above, but another important question is whether > > you > > have already disabled the Windows Fast Startup option in Windows 10. This > > is > > mandatory, and things will work differently depending on whether it is > > disabled > > already or not. See section 3.6.4 of the install manual. > > > > Fast startup was _not_ disabled - I thought (from install manual) only > applicable to Win-8, and this machine Win-10. > It is disabled now. Good. This is updated in the new version of the install manual, thanks to Holger Wansing. (see https://www.debian.org/releases/testing/amd64/ch03s06.en.html ) > In the same spirit, found a 'Fastboot' option in BIOS: It was set to > 'Minimal', it is now set to 'Thorough'. > > UEFI mode, Secure Boot always set. > > Nothing much has changed, except that reboot now offers opportunity to > skip a disk check (not taken). > > I am nervous that not disabling 'Fast startup' might have messed up > process from beginning - I may repeat entire installation. Yes worth a re-do. Pay attention to section 6.3.7 of the install manual, about getting the grub boot loader installed (onto your removable disk). > +++ Are the "disks" involved both/all partitioned in the same schema -- > +++ i.e. GPT partitions or MBR partitions? > I have partitioned nothing on the laptop's SSD (and don't really want to > - the idea of the external USB HDD for Debian was to make that drive a > sandbox - no possible corruption of other work under Win-10). > The external USB HDD was partitioned by the debian_installer (Guided > total disk). This should be OK. You said above UEFI/Secure-boot always set, which implies that all the disks should be setup as GPT style. > > FWIW I sense that in some way the 'Debian' option in the boot list > points to Win-10 on the SSD, rather than the Debian on the external HDD. > If it pointed to rubbish surely the machine would simply hang. > > Best regards >
Re: Problem installing Debian on Dell XPS 13 9360 laptop
On Fri, 2021-02-05 at 20:05 +, Bernard McNeill wrote: > This machine does not have either CD or DVD drive. Does have internal SSD. > This machine normally runs Windows-10. > Objective is to have Debian on external HDD (Toshiba), connected to > laptop via USB3. > > Events: > Under Windows, downloaded iso to SSD. > Win32diskimage from SSD to HDD. > Restarted, F12, picked out HDD from bootlist, booted, got into Debian > installer. > Does a few steps (language etc). > Gets stuck at 'No common CD-ROM drive was detected'. > > Ideas? I suggest writing the installer iso to a USB stick, and booting from that to install. Win32diskimager should be fine for that purpose. If you still have difficulty, please also say exactly which iso image. Good luck.
Install Guide vs. Secure Boot
Hopefully this is already changed in the Bullseye install guide, but if not, I don't think I will learn how to make edits before Bullseye releases. The Buster install guide says in Section 3.6.3 https://www.debian.org/releases/stable/amd64/ch03s06.en.html#UEFI Another UEFI-related topic is the so-called “secure boot” mechanism. Secure boot means a function of UEFI implementations that allows the firmware to only load and execute code that is cryptographically signed with certain keys and thereby blocking any (potentially malicious) boot code that is unsigned or signed with unknown keys. In practice the only key accepted by default on most UEFI systems with secure boot is a key from Microsoft used for signing the Windows bootloader. As the boot code used by debian-installer is not signed by Microsoft, booting the installer requires prior deactivation of secure boot in case it is enabled. My test on a recent weekly-build testing netinst seems to show that the above is no longer correct -- it booted fine for me in UEFI/SecureBoot mode. I thought I remembered reading (somewhere) that all recent debian installers (and live systems??) can boot in legacy BIOS mode or UEFI mode with or without secure boot.
Bug#939862: installation-guide-amd64: "Windows 8 fast boot" is now "Windows 10 fast startup"
Package: installation-guide-amd64 Severity: minor Tags: d-i Dear Maintainer, Buster installation guide section 3.6.4. documents the dangers of the Windows 8 "fast boot" feature. Most users now have Windows 10, where this feature is renamed "fast startup". I suggest this section (and its title) should mention both Windows versions, and both feature names. I suggest also adding additional text something like: "Sometimes the Windows Update mechanism has been known to automatically re-enable this feature, after it has been previously disabled by the user. It is suggested to re-check this setting periodically."
Bug#855144: installation-reports: Jessie netinst OK - 8.7.1 amd64 EFI raid-4
Package: installation-reports -- Package-specific info: Boot method: CD Image version: debian-8.7.1-amd64-netinst.iso via BT Date: Feb 13, 2017 23:00 UTC Machine: Dell 3620 Partitions: Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 0AE58CC0-098E-4EFB-95E9-0F4BE3717BFB Device StartEnd Sectors Size Type /dev/sda120481026047 1024000 500M EFI System /dev/sda2 10260487317503 6291456 3G Microsoft basic data /dev/sda3 7317504 15130623 7813120 3.7G Linux filesystem [/boot] /dev/sda415130624 648138751 633008128 301.9G Linux RAID /dev/sda5 648138752 1281146879 633008128 301.9G Linux RAID /dev/sda6 1281146880 1914155007 633008128 301.9G Linux RAID /dev/sda7 1914155008 1953413119 39258112 18.7G Linux swap 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] 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: My first time with EFI boot install, and with RAID. Everything worked just right, no 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 20150422+deb8u4+b2" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux william 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:191f] (rev 07) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:1901] (rev 07) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:1912] (rev 06) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a12f] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:14.2 Signal processing controller [1180]: Intel Corporation Device [8086:a131] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a13a] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:17.0 SATA controller [0106]: Intel Corporation Device [8086:a102] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a110] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:a118] (rev f1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a149] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:1f.2 Memory controller [0580]: Intel Corporation Device [8086:a121] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a170] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a123] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-LM [8086:15b7] (rev 31) lspci -knn: Subsystem: Dell Device [1028:06b7] lspci -knn: Kernel driver in use: e1000e lspci -knn: 02:00.0 PCI bridge [0604]: Texas Instruments XIO2001 PCI Express-to-PCI Bridge [104c:8240] lspci -knn: 04:00.0 Communication controller [0708]: SUNIX Co., Ltd. Multiport serial controller [1fd4:1999] lspci -knn: Subsystem: SUNIX Co., Ltd. Device [1fd4:0101] usb-list: usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 3.16.0-4-amd64 xhci_hcd usb-list:Interface 00: Class 09(hub )
Bug#848383: Installation: i915 - Oh no! Something has gone wrong
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.6.0+nonfree/i386/bt-cd/firmware-8.6.0-i386-netinst.iso.torrent Date: Dec 13, 2016 17:00 UTC Machine: Uniwill 223ii0 Processor: CPU: Intel(R) Pentium(R) M processor 2.00GHz (fam: 06, model: 0d, stepping: 06) Memory: 500 MB Partitions: /dev/sda1 * 2048 115181567 115179520 54.9G 83 Linux /dev/sda2 115183614 117209087 2025474 989M 5 Extended /dev/sda5 115183616 117209087 2025472 989M 82 Linux swap / Solaris Output of lspci -knn (or lspci -nn): root@hermes:/home/lwp# lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3580] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: agpgart-intel 00:00.1 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:9022] 00:00.3 System peripheral [0880]: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:9022] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:9500] 00:02.1 Display controller [0380]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:9500] 00:1d.0 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: ehci-pci 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 83) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 03) Kernel driver in use: lpc_ich 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:9022] Kernel driver in use: i801_smbus 00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:8401] Kernel driver in use: snd_intel8x0 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 03) Subsystem: Uniwill Computer Corp Device [1584:4007] Kernel driver in use: snd_intel8x0m 01:03.0 CardBus bridge [0607]: Texas Instruments PCI1410 PC card Cardbus Controller [104c:ac50] (rev 02) Subsystem: Uniwill Computer Corp Device [1584:3200] Kernel driver in use: yenta_cardbus 01:07.0 Ethernet controller [0200]: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter [168c:0013] (rev 01) Subsystem: Askey Computer Corp. Device [144f:7005] Kernel driver in use: ath5k 01:0a.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023] Subsystem: Uniwill Computer Corp Device [1584:7000] Kernel driver in use: firewire_ohci 01:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10) Subsystem: Uniwill Computer Corp Device [1584:9700] Kernel driver in use: 8139too 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: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:
Re: Bug#694777: Wheezy Beta4 installs but X server unusable
On Fri, 7 Dec 2012, Brian Potkin wrote: A minimal patch to the Guide is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695403 Thanks Brian, this looks very helpful. -- 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/20121207235027.q62...@shell.msen.com
Re: Bug#694777: Wheezy Beta4 installs but X server unusable
On Mon, 3 Dec 2012, Brian Potkin wrote: I've tried to read http://d-i.debian.org/manual/en.i386/ch02s02.html and http://d-i.debian.org/manual/en.i386/ch06s04.html from a new user's perspective. There is nothing there, as far as I can see, which says only missing firmware for network cards will be attended to at that stage of the installation. Indeed, the first paragraph of section 2.2 also mentions USB devices, disk controllers, and graphics cards needing firmware. The following discussion discusses firmware in general (not specifically network card firmware) including the last paragraph which suggests the installer will prompt for firmware. Section 6.4 also says the installer will display a dialog offering to install missing firmware, as part of a completely general discussion of firmware. As I answered before, at no time did the installer ask me or offer me to install any firmware at all, even though my radeon display controller will not work at all with the installed kernel without firmware. Even this excellent page http://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/ doesn't make it clear that non-free firmware detection in D-I is for network hardware only. However, the suggestion that the kernel update post-installation process will eventually inform the new user of all missing firmware, is the best answer I've seen so far to my own concern that I might never have known I needed to install some firmware. With the work-around patch from bug 693324 that would allow the new system to boot to a framebuffer screen (instead of black screen), and the eventual discovery of the need for firmware installation from eventually updating the kernel and thus seeing the firmware messages from the post-install scripts, I would eventually get the message. Irrespective of anything else which could be done, there is a case for the Manual to reflect this situation and to offer some advice for missing firmware detection post-installation. Agree. This situation with newer devices *requiring* firmware reloads at bootup, and with some firmware walled off in non-free, can surprise even somewhat experienced users who have done previous installs without having to think about firmware at all. I suggest including lots of references/hyperlinks in these sections of the installer manual. Thanks, Lou -- 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/20121203134057.c20...@shell.msen.com
Bug#694777: Wheezy Beta4 installs but X server unusable
On Sat, 1 Dec 2012, Christian PERRIER wrote: Quoting Brian Potkin (claremont...@gmail.com): Perhaps the installer could warn the user if her video card is among those listed in AtiHowTo and the installer doesn't see the firmware supplied somewhere by the user. Perhaps just a referral to the wiki page ? Didn't the installer ask for RV610_pfp.bin to be supplied? Logically, no. Firmware for video cards is none of the installer's business. Of coure, from the user point of view, all this is related, but from the logical organisation of packages, it is not. Unless I missed something somewhere (which is possible), we focus out firmware-related attention on network cards. Disagree, somewhat. In my case, I had a vague awareness that sometimes non-free firmware might be required, but no motivation to investigate further until my newly installed system booted into a black screen. The patch which will probably close this bug, detailed in bug 693324, will eliminate the black screen problem, which is good, but leaves the video card running in a degraded state, which some users (probably including myself) might never understand is caused by missing firmware. Before this firmware was exiled to non-free, I suspect that there was some trail of dependencies from the driver modules, which would have caused the installers to install the firmware automatically. Now we have only general warnings about firmware from dirty sources, and some messages in the installed system's logs. I probably would never have looked for these log warnings without a black screen to motivate me. I understand why the modules are non-free, and why they won't be installed automatically any more. But firmware for video cards is still the installer's business, and probably is installed automatically still, if it is found in the mainline debian depositories, i.e. not non-free. The installer is indeed the logical place from a user's point of view, to find out about what software to install on a new system. I repeat my suggestion at least to mention http://wiki.debian.org/AtiHowTo if the user has one of those unfortunate cards mentioned there. This target machine is a newly installed Windows7 computer at my wife's office; she is a professor in a small scientific department at a small university; the university's IT department gave their blessing to install a dual-boot linux setup, with the understanding that they would provide no support for the linux part. I rarely see her office, and probably will not sit at this computer very often. So, please imagine if the workaround bugfix were installed, leaving the machine running degraded video without its firmware *under linux*, but running full-featured video under its Windows7 installation. Imagine I have walked away, thinking OK, it works and mostly only visit the machine via SSH in the future. Imagine my wife and her colleagues over time seeing that the machine looks much better under Windows than it does under linux. It seems like bad linux evangelism. -- 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/20121201112721.x8...@shell.msen.com
Bug#694777: Wheezy Beta4 installs but X server unusable
Package: installation-reports Boot method: CD Image version: debian-wheezy-DI-b4-amd64.netinst Date: Nov 28, 2012, 01:00 UTC Machine: Dell Inc. OptiPlex 755 Processor: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Memory: 4 GB Partitions: root@ivanovad:/var/log# /sbin/fdisk -l /dev/sda Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa62a3850 Device Boot Start End Blocks Id System /dev/sda1 *2048 244337985 1221679697 HPFS/NTFS/exFAT /dev/sda2 244338688 254103551 4882432 83 Linux /dev/sda3 254103552 44941516797655808 83 Linux /dev/sda4 449415168 48839679919490816 82 Linux swap / Solaris root@ivanovad:/var/log# df -Tl Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs96121612 3608508 87630316 4% / udev devtmpfs 10240 0 10240 0% /dev tmpfs tmpfs 392984 656392328 1% /run /dev/disk/by-uuid/7712d588-c97c-4890-a3b1-3d8dfacf1624 ext4 96121612 3608508 87630316 4% / tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 4684120 72 4684048 1% /run/shm /dev/sda2 ext4 4805760 158140 4403500 4% /boot Output of lspci -knn (or lspci -nn): (from running system) root@ivanovad:/var/log# lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02) Subsystem: Dell OptiPlex 755 [1028:0211] 00:01.0 PCI bridge [0604]: Intel Corporation 82Q35 Express PCI Express Root Port [8086:29b1] (rev 02) Kernel driver in use: pcieport 00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02) Subsystem: Dell OptiPlex 755 [1028:0211] 00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02) Subsystem: Dell OptiPlex 755 [1028:0211] Kernel driver in use: ata_generic 00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02) Subsystem: Dell OptiPlex 755 [1028:0211] Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02) Subsystem: Dell OptiPlex 755 [1028:0211] Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) Subsystem: Dell Optiplex 755 [1028:0211] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller [8086:2914] (rev 02) 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
Bug#694777: Wheezy Beta4 installs but X server unusable
On Fri, 30 Nov 2012, Lou Poppler wrote: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV610 [Radeon HD 2400 XT] [1002:94c1] Subsystem: Dell Optiplex 755 [1028:0d02] Kernel driver in use: radeon [ ... ] Various online research brings me to http://wiki.debian.org/AtiHowTo which looks like I should install some non-free firmware for this card. I find this in the running dmesg: root@ivanovad:/var/log# dmesg |grep -i firmware [8.322395] r600_cp: Failed to load firmware radeon/RV610_pfp.bin [8.322442] [drm:r600_startup] *ERROR* Failed to load firmware! I am happy to report that installing the non-free firmware blob fixed my problem, everything worked correctly upon the next wheezy boot. Perhaps the installer could warn the user if her video card is among those listed in AtiHowTo and the installer doesn't see the firmware supplied somewhere by the user. Perhaps just a referral to the wiki page ? However, the instructions at AtiHowTo didn't quite work as written: : The firmware in question, id est the CP/PFP microcode, can be installed : by first enabling the non-free repository for your Debian release : and issuing the following command: : : aptitude install firmware-linux-nonfree I added contrib non-free to my sources list entries, and tried the command: : root@ivanovad:/etc/apt# vi sources.list : root@ivanovad:/etc/apt# aptitude install firmware-linux-nonfree : Couldn't find any package matching firmware-linux-nonfree. However, the following : packages contain firmware-linux-nonfree in their description: : firmware-linux-free : Couldn't find any package matching firmware-linux-nonfree. However, the following : packages contain firmware-linux-nonfree in their description: : firmware-linux-free : No packages will be installed, upgraded, or removed. : 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. : Need to get 0 B of archives. After unpacking 0 B will be used. I ran aptitude interactively. I think I probably did a [u] update. When I searched for it, I found this package listed as p status [purged? I think], so I gave it a + and a g, and it installed OK then: : root@ivanovad:/etc/apt# aptitude : Selecting previously unselected package firmware-linux-nonfree. : (Reading database ... 125749 files and directories currently installed.) : Unpacking firmware-linux-nonfree (from .../firmware-linux-nonfree_0.36_all.deb) ... : Setting up firmware-linux-nonfree (0.36) ... : update-initramfs: deferring update (trigger activated) : Processing triggers for initramfs-tools ... : update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 : Press Return to continue. I don't know if the update was implicit in the wiki-page's instructions, but if so that wasn't clear to this non-expert. Anyway, I'm happy now. I hope my pitiful example is helpful to those who follow after me -- 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/20121130154554.p20...@shell.msen.com
Bug#694777: Wheezy Beta4 installs but X server unusable
On Fri, 30 Nov 2012, Brian Potkin wrote: [AMD] nee ATI RV610 [Radeon HD 2400 XT] [1002:94c1] Subsystem: Dell Optiplex 755 [1028:0d02] Kernel driver in use: radeon [ ... ] http://wiki.debian.org/AtiHowTo which looks like I should install some non-free firmware for this card. I find this in the running dmesg: root@ivanovad:/var/log# dmesg |grep -i firmware [8.322395] r600_cp: Failed to load firmware radeon/RV610_pfp.bin [8.322442] [drm:r600_startup] *ERROR* Failed to load firmware! I am happy to report that installing the non-free firmware blob fixed my problem, everything worked correctly upon the next wheezy boot. That is good to know. May I inquire why you did not have the contents of firmware-linux-nonfree available to use during the installation on a just in case basis? It is something I have got into the habit of doing, especially when I'm unfamiliar with the machine's hardware. I ask because the Guide does have some detailed information on firmware in sections 2.2 and 6.4. It would be useful to have some feedback on whether the documenation is deficient in some way amd you did not quite realise its importance. I certainly read those sections more than once without getting the feeling that I should always have the unofficial extras available in advance. In advance, I felt like the installer might ask for it if needed, or I might see the need when something completely failed to work. Indeed these warnings made me more willing to consider the possibility of firmware as I researched my problem post-install, and followed layers of links in various documentation, eventually finding the wiki-page which made it clear that my display controller does need firmware, period. Note also that section 6.4.2 of the Guide warns about non-packaged firmware evading updates later via the package management system. Perhaps the installer could warn the user if her video card is among those listed in AtiHowTo and the installer doesn't see the firmware supplied somewhere by the user. Perhaps just a referral to the wiki page ? Didn't the installer ask for RV610_pfp.bin to be supplied? No, never. It looks like the installer itself always runs the card in some kind of framebuffer mode which worked throughout without problem. Only after booting the installed system, resulting in a blank screen, did I have any hint of a problem with this card. http://myweb.cableone.net/ytpoppler/hardware-summary http://myweb.cableone.net/ytpoppler/status http://myweb.cableone.net/ytpoppler/syslog http://myweb.cableone.net/ytpoppler/Xorg.0.log (I also have the cdebconf subdirectory and the partman file from installer saved logs, as well as various system logs, if they are interesting.) -- 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/20121130201822.h66...@shell.msen.com
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
On Thu, 22 Nov 2012, Brian Potkin wrote: On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote: I see that the beta-4 version is available today. I'll grab that, and try it out to see if it will work automatically. It works for me. It worked for me too. The installation completed, and GRUB installed OK, dual-booting works. I grabbed the installer logfiles from the unsuccessful beta-3 install, and from today's successful beta-4 install. If anyone wants any part of them, I can supply it. I have another issue with the new install, display problems, but I assume you might want me to start a new bug number for this ? Thanks, Lou -- 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/20121127222149.f29...@shell.msen.com
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
Thanks for your reply -- for some reason it didn't arrive here as email, but I found it tonight while looking in the debian-boot list archives. On Mon, 19 Nov 2012 11:00:49 +, Brian Potkin wrote: : On Mon 19 Nov 2012 at 02:09:47 -0500, Lou Poppler wrote: : : Comments/Problems: This machine started with Win7 installation occupying :the entire disk. I resized the windows partition to 1/2 of the disk, :and installed wheezy into the new partitions [ /boot and / plus swap ], :which I created using manual partitioning in the installer. :When we got to the install GRUB phase, I see this message: : [!] Install the GRUB boot loader on a hard disk : It seems that this new installation is the only operating system on this : computer. If so, it should be safe to install the GRUB boot loader to : the master boot record of your first hard drive. : : Bug#650819 maybe. Should be fixed in beta-4. : :This is not what I want -- I want to set this up as dual-boot, win7/wheezy. :I said no to installing GRUB, and finished the install with no boot loader :changes. This should be a simple case for the installer to get right. :The manual for beta D-I doesn't steer me to any way to solve this, other :than to see the GRUB manual. : : Did you get that advice from section 6.3.6.1? I'd agree it is less : helpful than intended. Yes, exactly. The mention of black arts also makes me hesitant to interfere when the automatic process gets it wrong. The GRUB ecosystem seems more complicated, the more I try to understand it, with the various scripts which probe and update and install, but aren't really discussed in the mainline grub documentation sources, such as they are. Perhaps in section 6.3.6.2 where it says See the grub manual for complete information. there could be some hyperlink[s]. : So now I'm trying to become enough of a GRUB :expert to be able to create a manual boot loader configuration that will :maybe result in a working dual boot. : : It's a pity you declined to install GRUB. At least you should have got a : bootable system from which to attempt to get the missing entry into the : GRUB menu. It's too bad the ISO doesn't provide a way to boot into the completed installation, without overwriting the disk's MBR. I would be more confident to experiment with GRUB configurations and probing if I could see what it was trying to install before I commit to it. I don't want to lose the ability to boot the existing Win7 system on my wife's computer. : You could consider a reinstall. Then boot into the new system and run : :update-grub : : as root. : : Alternatively, you could boot the netinst ISO in Rescue mode. From there : you can reinstall GRUB and get a shell to use 'update-grub'. I see that the beta-4 version is available today. I'll grab that, and try it out to see if it will work automatically. -- Don't anthropomorphize computers. They don't like it. -- 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/20121121235054.r70...@shell.msen.com
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/debian-wheezy-DI-b3-amd64-netinst.iso Date: November 19, 2012, 01:00 UTC Machine: Dell Optiplex 770 Processor: dual Core3 intel Memory: Partitions: SCSI3 (0,0,0) (sda) - 250.1 GB ATA WDC WD2500AAKX-0 #1 Primary 125.1 GB B ntfs #2 Primary5.0 GB ext4 #3 Primary 100.0 GB ext4 #4 Primary 20.0 GB swap 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: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: This machine started with Win7 installation occupying the entire disk. I resized the windows partition to 1/2 of the disk, and installed wheezy into the new partitions [ /boot and / plus swap ], which I created using manual partitioning in the installer. When we got to the install GRUB phase, I see this message: [!] Install the GRUB boot loader on a hard disk It seems that this new installation is the only operating system on this computer. If so, it should be safe to install the GRUB boot loader to the master boot record of your first hard drive. This is not what I want -- I want to set this up as dual-boot, win7/wheezy. I said no to installing GRUB, and finished the install with no boot loader changes. This should be a simple case for the installer to get right. The manual for beta D-I doesn't steer me to any way to solve this, other than to see the GRUB manual. So now I'm trying to become enough of a GRUB expert to be able to create a manual boot loader configuration that will maybe result in a working dual boot. -- 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/20121119013634.d64...@shell.msen.com
Bug#416944: dist-upgrade stuck
Package: installation-reports Trying to upgrade from sarge to etch, not doing well. I net-installed sarge a couple weeks ago, and got it working mostly well, with gdm X desktop and kernel 2.6.8. I was having some minor ethernet driver problems which googling suggested might be fixed by a newer kernel. I was encouraged by the reports of successful dist-upgrades to etch, so I went through the Method C process. I am now running etch on this machine, with kernel 2.6.18-4-686, but many things seem to no longer be installed -- notably the X desktop (and I just noticed also no ssh). I found that X wasn't starting because gdm was not installed, so I [re-]installed gdm from aptitude. This got me into X, but after I login to gdm I get only a little shell window, probably an xterm. I stopped gdm, and last night started: tasksel install desktop It started downloading, and I went to bed with it showing 1hr30min more download time. When I came back to the machine after my nap, I find it stuck in tasksel. The screen shows Package configuration on the very top line, and a text box in the middle saying: Installing packages \ Installed libdiscover1 and a status bar stuck at 75%. I don't know what to try next. I looked for any logs which might show what is happening, but didn't find them. Below is some output from ps and df. If someone wiser than me can suggest what I might do next, I would appreciate it. Right now I'm just leaving the stuck tasksel as it is. If it would be easier, I don't mind nuking this installation, and just installing etch from scratch. USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 1940 636 ?Ss Mar30 0:01 init [2] root 2 0.0 0.0 0 0 ?SMar30 0:00 [migration/0] root 3 0.0 0.0 0 0 ?SN Mar30 0:00 [ksoftirqd/0] root 4 0.0 0.0 0 0 ?S Mar30 0:00 [events/0] root 5 0.0 0.0 0 0 ?S Mar30 0:00 [khelper] root 6 0.0 0.0 0 0 ?S Mar30 0:00 [kthread] root 9 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kblockd/0] root10 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kacpid] root63 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kseriod] root97 0.0 0.0 0 0 ?SMar30 0:00 \_ [pdflush] root98 0.0 0.0 0 0 ?SMar30 0:01 \_ [pdflush] root99 0.0 0.0 0 0 ?S Mar30 0:02 \_ [kswapd0] root 100 0.0 0.0 0 0 ?S Mar30 0:00 \_ [aio/0] root 567 0.0 0.0 0 0 ?S Mar30 0:00 \_ [khubd] root 982 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1477 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kpsmoused] root 1498 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kgameportd] root 1786 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kmirrord] root 1824 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1826 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1828 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1830 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1832 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1834 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1836 0.0 0.0 0 0 ?S Mar30 0:00 \_ [kjournald] root 1838 0.0 0.0 0 0 ?S Mar30 0:01 \_ [kjournald] root 1143 0.0 0.2 2196 784 ?Ss Mar30 0:00 udevd --daemon daemon1961 0.0 0.0 1684 372 ?Ss Mar30 0:00 /sbin/portmap root 2234 0.0 0.2 2556 928 ?Ss Mar30 0:00 /sbin/syslogd root 2240 0.0 0.0 1576 384 ?Ss Mar30 0:00 /sbin/klogd -x bind 2252 0.0 0.7 30272 2772 ?Ssl Mar30 0:00 /usr/sbin/named -u bind root 2266 0.0 0.7 30276 2788 ?Ssl Mar30 0:00 /usr/sbin/lwresd root 2306 0.0 0.5 5440 2040 ?Ss Mar30 0:00 /usr/sbin/cupsd root 2359 0.0 0.2 2808 976 ?SMar30 0:00 /usr/sbin/inetutils-inetd root 2403 0.0 0.2 3200 1136 ?Ss Mar30 0:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive statd 2428 0.0 0.2 2684 1048 ?Ss Mar30 0:00 /sbin/rpc.statd ntp 2449 0.0 0.4 5060 1608 ?Ss Mar30 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -u 106:115 -g daemon2461 0.0 0.1 1824 412 ?Ss Mar30 0:00 /usr/sbin/atd root 2468 0.0 0.2 2196 876 ?Ss Mar30 0:00 /usr/sbin/cron root 2526 0.0 1.4 13668 5648 ?Ss Mar30 0:00 /usr/sbin/apache2 -k start www-data 2571 0.0 0.9 13668 3644 ?SMar30 0:00
Bug#413931: d-i missing ide modules
Package: installation-reports
Boot method: CD
Image version: debian-31r5-i386-netinst.iso, from usc.edu mirror, md5sum good
Date: 7 Mar 2007, 22:00 UTC
Machine: Old Gateway, Tabor{2,3} motherboard
Processor: P3 (Katmai) 596MHz
Memory: 384 MB ECC
Partitions: none
Output of lspci and lspci -n: /bin/sh: lspci: not found
dmesg says:
: PCI: Probing PCI hardware (bus 00)
: PCI: Using IRQ router PIIX/ICH [8086/7110] at :00:07.0
: PCI: Found IRQ 9 for device :00:07.0
: PCI: Sharing IRQ 9 with :00:10.0
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O] looks correct in dmesg
Partition hard drives: [ ]
Create file systems:[ ]
Mount partitions: [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]
Comments/Problems:
Missing modules for ide.
Running as expert26 installation.
The last installer screen before starting disk partitioning says this:
: [.] Detect hardware
: Unable to load some modules
: Linux kernel modules needed to drive some of your hardware are not
: available yet. Simply proceeding with the install may make these
: modules available later.
:
: The unavailable modules, and the devices that need them are: agpgart
: (Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge), ide-scsi
: (Linux IDE-SCSI emulation layer), ide-mod (Linux IDE driver),
: ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE
: detection), ide-floppy (Linux IDE floppy)
:
: Continue
Selecting Continue brings us to the start of partitioning and making
filesystems.
As I searched Google's archives of various debian lists for this problem,
the recurrent answer seems to be that this is an informative message only,
and the modules will be loaded later. This seems to be contradicted by
this section from the Installation Guide:
: 6.3.2.B Partitioning and Mount Point Selection
:
:At this time, after hardware detection has been executed a final time,
:debian-installer should be at its full strength, customized for the
:user's needs and ready to do some real work. As the title of this
:section indicates, the main task of the next few components lies in
:partitioning your disks, creating filesystems, assigning mountpoints
:and optionally configuring closely related issues like LVM or RAID
:devices.
The text of the error screen, and the text of the Installation Guide,
seem to be saying clearly that these modules are needed to drive the IDE
hardware, and this was the last chance to automatically find them, and it
did not succeed.
I am _very_ reluctant to proceed to partitioning and file-system making,
for this reason: A week ago I tried installing on this machine, using the
3.1R4 netinst CD and the original 4MB Seagate IDE disk that came with this
machine. I saw the same errors about missing modules, but proceeded anyway.
The installer pretended to partition the disk, and pretended to install some
stuff for a while, then croaked with an error about the disk being Busy.
After much investigating of the disk with Knoppix and smartctl, it seemed
that the disk was permanently bad, giving errors on self-tests, unable
to successfully write to some parts of it, and hanging busy. I replaced it
with 2 nice new high-capacity IDE Ultra-ATA disks, and downloaded the newest
netinst 3.1R5 CD, and tried again today.
I don't want to destroy my new disks by trying to partition them when the
installer is plainly telling me it doesn't have the necessary kernel modules
to do the job. Is there some way I can supply these missing modules to
the installer ? Should I try to partition/mk*fs them from Knoppix ?
Is there any other documentation I should read ?
Please advise.
Note: I am subscribed to the debian-bugs-dist list.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#413931: d-i missing ide modules
On Thu, 8 Mar 2007, Frans Pop wrote: On Wednesday 07 March 2007 23:58, Lou Poppler wrote: The text of the error screen, and the text of the Installation Guide, seem to be saying clearly that these modules are needed to drive the IDE hardware, and this was the last chance to automatically find them, and it did not succeed. No, the message is just informing you that those modules those modules are associated with your hardware, but have not been loaded. To be honest, that message is there more for debugging than for signalling any real issues. Unfortunately it tends to be more confusing than helpful to users. Yes, confusing and scary. Perhaps the words needed and need are too strong in this message. I leave this bug open only to allow d-i maintainers to consider if they want to reword it. [...] It is extremely unlikely that your disk problems were in any way caused by the installer, and certainly not by the presence of this message. Note that the message would not even be shown during a regular (non-expert) installation. That would be unthinkable if it contained any real information. If you select manual partitioning in the first dialog of the partitioner and the next screen shows your harddisk and the existing partitions that are on it, there is nothing to worry about. [...] Given the age of your system it should be well supported by Sarge. If it were a recent system I'd advice to install Etch instead of Sarge, but for a Pentium 3 box there is no reason for that. Hope this gives you the confidence to proceed. Yes, thank you. The CD part of the install finished fine, the disks are partitioned and OK, and now it has rebooted from the hard disk and is happily downloading more packages. Thanks again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
