Bug#686927: installation does not detect existing Lubuntu
Quoting Rick Thomas (rbtho...@pobox.com): PS: Is anybody working on this bug? It would be a shame if it got into beta2... I'd be happy to take a look and see if I could find anything, but I don't know where to look. Can somebody point me in the right direction? Thanks in advance! No. So far, nobody is actively woking on grub-related bugs. Most of them probably belong to grub-installeror the grub package itself. Sorry for not being very precise, but all this has often been some kind of black magic to me (or more precisely, something I never worked on). signature.asc Description: Digital signature
Bug#686927: installation does not detect existing Lubuntu
On Sep 7, 2012, at 11:33 PM, Christian PERRIER wrote: Quoting Rick Thomas (rbtho...@pobox.com): PS: Is anybody working on this bug? It would be a shame if it got into beta2... I'd be happy to take a look and see if I could find anything, but I don't know where to look. Can somebody point me in the right direction? Thanks in advance! No. So far, nobody is actively woking on grub-related bugs. Most of them probably belong to grub-installeror the grub package itself. Sorry for not being very precise, but all this has often been some kind of black magic to me (or more precisely, something I never worked on). I have pretty much the same problem. It's all dark grey magic (read: something I never worked on...[(-:]) to me too. However, I'm not sure this is directly grub related. In fact, given that it also occurs on PowerPC with the Yaboot bootloader (quite un- grub-like) and with lilo on x86 (also fairly un-grub-like), I'd say it has to do with the code that finds other operating systems and the way it notifies the code that builds the boot-loader config files... Does that help any? Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686927: installation does not detect existing Lubuntu
Package: installation-reports Boot method: netboot Image version: http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/ Date: 05-SEP-2012 20:00 GMT Machine: Toshiba Satellite A100 Processor: Intel Core2 duo Memory: 1GByte Partitions: df -Tl will do; the raw partition table is preferred Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[0] Configure network: [0] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[E] Overall install:[E] Comments/Problems: 1. The install into an encrypted partition worked well, albeit somewhat slow ;-) In addition to the encrypted installation partition, it correctly created an unencrypted boot partition and encrypted swap. 2. The installation did not detect the existing Lubuntu 10.04 and wanted to install grub into the master boot record (I did not allow that). 3. the grub installer was unable to install grub into any partition of the harddisk, encrypted or not. So I could not boot into wheezy. 4. Manually editing the configuration of the existing grub-legacy in the master boot record, I was able to boot into wheezy. So, grub seems to be the only problem of wheezy, at least for me. Thanks for your good work! Herbert -- Herbert Kaminski Dipl.Phys. Memeler Str. 4 26122 Oldenburg Fon: 0441-9558938 Fax: -9558939 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686927: installation does not detect existing Lubuntu
On Sep 7, 2012, at 1:51 AM, Herbert Kaminski wrote: Comments/Problems: 2. The installation did not detect the existing Lubuntu 10.04 and wanted to install grub into the master boot record (I did not allow that). 3. the grub installer was unable to install grub into any partition of the harddisk, encrypted or not. So I could not boot into wheezy. 4. Manually editing the configuration of the existing grub-legacy in the master boot record, I was able to boot into wheezy. So, grub seems to be the only problem of wheezy, at least for me. I think this is the same as bug#684265, which I submitted a while back for a PowerPC install using Beta1. See Bug#686471 for a workaround, if you've got a spare USB flash stick you can use to put the lilo bootloader on. Quote from that bugreport... Fortunately, the amd64 grub boot loader creation script did some self-checking, and noticed that there was only one OS in the setup it was about to write. It asked me if I wanted to write a MBR that I'd only have to re-do later to pick up the other OS's (if any). I decided to see if there were other options and answered no. It then asked if I wanted to write the boot block to the partition I was installing to. I said yes but that failed for some reason (I don't remember the error message, and I don't think it was helpful even if I could remember.) So then I tried using lilo to a second USB stick. That worked and booted fine. If I booted without the USB stick, it booted to the previous default OS. Cool! that there's a workaround, but Uncool! that it's so roundabout! I'll be happy to supply the syslog file if you want to take a look. Rick PS: Is anybody working on this bug? It would be a shame if it got into beta2... I'd be happy to take a look and see if I could find anything, but I don't know where to look. Can somebody point me in the right direction? Thanks in advance! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
