Bug#607338: installation-report: report of my debian installation and issues after initial install
reassign 607338 libpam-runtime forcemerge 601825 607338 thanks I have already told you that I had submitted a bug report about that issue already... No need to submit another one, merging them. 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/20101217080124.gf5...@const.famille.thibault.fr
Processed: Re: Bug#607338: installation-report: report of my debian installation and issues after initial install
Processing commands for cont...@bugs.debian.org: reassign 607338 libpam-runtime Bug #607338 [installation-reports] installation-report: report of my debian installation and issues after initial install Bug reassigned from package 'installation-reports' to 'libpam-runtime'. Bug No longer marked as found in versions 2.43. forcemerge 601825 607338 Bug#601825: libpam-runtime: Loops on No PAM profiles have been selected in some installation case Bug#607338: installation-report: report of my debian installation and issues after initial install Forcibly Merged 601825 607338. thanks Stopping processing here. Please contact me if you need assistance. -- 607338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607338 601825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129257392413348.transcr...@bugs.debian.org
Bug#607350: installation-reports: HP G4 DL380 installation takes a very long time; fd0 error
Package: installation-reports Severity: minor -- Package-specific info: Boot method: CD Image version: debian weekly week50 Date: Date and time of the install Machine: HP G4 DL380 Partitions: df -Tl will do; the raw partition table is preferred 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:[o] Comments/Problems: (sorry for my bad english, but i hope you understand me) The installation takes a very long time, and gives many errors sometimes its need 10minutes from screen to screen. look at this screenshots: http://ompldr.org/vNXVtZQ http://ompldr.org/vNXVtZw http://ompldr.org/vNXVtaA and i dont habe an floppydisk in this system, only CDROM and HDD here in german: http://debianforum.de/forum/viewtopic.php?f=12t=124204 -- 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 20101127 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux csfzabbix 2.6.32-5-486 #1 Sat Oct 30 22:14:18 UTC 2010 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation E7520 Memory Controller Hub [8086:3590] (rev 0c) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3200] lspci -knn: 00:02.0 PCI bridge [0604]: Intel Corporation E7525/E7520/E7320 PCI Express Port A [8086:3595] (rev 0c) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation E7520 PCI Express Port C [8086:3599] (rev 0c) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 [8086:24d2] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 [8086:24d4] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 [8086:24d7] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 [8086:24de] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller [8086:24dd] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c2) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge [8086:24d0] (rev 02) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller [8086:24db] (rev 02) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:3201] lspci -knn: Kernel driver in use: ata_piix lspci -knn: 01:03.0 VGA compatible controller [0300]: ATI Technologies Inc Rage XL [1002:4752] (rev 27) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:001e] lspci -knn: 01:04.0 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Controller [0e11:b203] (rev 01) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:b206] lspci -knn: 01:04.2 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Processor [0e11:b204] (rev 01) lspci -knn: Subsystem: Compaq Computer Corporation Device [0e11:b206] lspci -knn: 02:00.0 PCI bridge [0604]: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A [8086:0329] (rev 09) lspci -knn: 02:00.2 PCI bridge [0604]: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B [8086:032a] (rev 09) lspci -knn: 03:01.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet [14e4:1648] (rev 10)
Bug#606242: Issue-report: Debian-squeeze-di-Beta2-i386-DVD-1. USB+PS/2 mouse and wonky install screen 'CONTINUE' button icon.
Bug#606242. I reproduced on debian-squeeze-di-beta2-i386 New install, the Wonky 'Install screen [CONTINUE] button icon', issue. First a quick conjecture. I wonder if a mouse button action is a 'two state' trigger ? 1.) Button pressed, and 2.) button released. Are these actually really sticky hardware buttons on the multiple mice maybe ? 1.) Greyed out for button pressed, and 2.)'Programme action' when button realeased. Just a thought. I could try to multiple press and click of the left button, without moving the mouse in the plain. 2010.12.10. I noticed this MINOR issue again, this time on Debian squeeze di Beta2 (Beta 2) (Beta-2) at the Partition Disks: Partition Settings: screen. Though the issue symptom may have occured earlier. I do not really know. I will keep looking. After setting up a raid1 mirroring array with 3 raid partitions on two hard disks, my last action was setting up the /boot partition on the array when I experienced the 'freeze'. Selecting the task 'Finish partitioning and write changes to disk' I went to press [CONTINUE] My [CONTINUE] button icon, on my install screen, has this issue of having a 'Two Trigger' attribute. Using a different mouse this time. Not the USB optical mouse I originally used. This time I am using, for fault finding, an original IBM PS/2 mouse, part number IBM 6450350. Left button click and the [CONTINUE] button icon on the screen GREYs out. Good. OK. I can then leave the mouse untouched for as long as I like, without any other programme reaction. Frozen. The [CONTINUE] button screen icon remains 'greyed out', without any programme action that I selected. I then eventually moved the mouse in the horizontal plane slightly and the programme reacts to the [continue] button icon being pressed, and the task completes OK. Next time, I should try the vertical plane. I selected the [GO BACK] screen icon button and followed up reproducing the symptom issue with the [continue] button icon. After selecting 'Finish partitioning' yet again and going to the 'Write changes to the disk' again, I could NOT reproduce the 'Two Trigger' issue on the [continue] icon button. The icon button worked OK, UNTIL I reached the 'Software selection' screen. I went to accept the default software selection GDE and SSU. I pressed the left button with the cursor on [CONTINUE] and the issue returned. On purpose, I placed the tip of the 'cursor arrow pointer' on the coordinates; X: The gap Horizontally, Halfway between the left hand vertical side of the [continue] screen icon button's box frame, and it's letter 'C' the first letter in [continue], and... the Y: coordinate, Vertically halfway up or down the [continue] icon box frame. I now have to correct my earlier description in my first posting. On purpose, I did NOT move the cursor outside the box frame of the [continue] icon. Eventually, I moved the mouse the tinyest amount I could, lets say one millimetre. While still well inside the icons box framework, the programme action was triggered OK, whilst the cursor pointer was still inside the icon. I wrongly said previously, that I had to move the cursor outside the icons boundaries for some programme action. Having reproduced the symptom of this MINOR issue to this degree, I now feel a total pedant. Pragmatically, I can live with this particular issue. Best of luck, I wish you all well. Thank you for all the GREAT software, everybody involved. I really do appreciate Debian, et al, your efforts and your support, In the past and in the future. Happy holidays. 2010.12.17. Regards, McTech. ---end.
Bug#605759: [s390/hercules] disk partitioning failed: no /dev/dsda1
On Thu, Dec 16, 2010 at 05:37:55PM +0100, Ferenc Wagner wrote: Niko Tyni nt...@debian.org writes: Hercules s390 emulator installation failed at disk partitioning; new partitions don't seem to show up in /dev. Thanks for the detailed but to-the-point report. This may be a kernel, a udev or a partman issue. Could you please try backing out of the partitioning menu to the main menu, start a shell in the installer environment with the appropriate menu item and do the partitioning yourself by fdasd or whatever's needed? Then please check if the new partitions show up in /proc/partitions and under /dev. This would help us narrowing down the case. It works fine if I create the partition manually with fdasd. Furthermore, if I try to create a partition first with the d-i interface (getting the error) and then invoke fdasd and write out a trivial no-op such as change the volume serial from LIN120 to LIN120, /dev/dasda1 appears. It looks te me like the problem is that d-i does not manage to reread the partition table. I'm not sure if I understand the architecture correctly here, but maybe the problem is this change in parted 2.3 ? libparted: remove now-worse-than-useless _kernel_reread_part_table Now that we're using BLKPG properly, there's no point in using the less-functional BLKRRPART ioctl to make the kernel reread the partition table. More importantly, this function would fail when any partition is in use, in spite of our having carefully vetted them via BLKPG ioctls. I see fdasd (as of s390-tools 1.8.3-3) uses BLKRRPART and not BLKPG. The timeline would also fit the successful reports #569209 and #575682. I suppose I can try to hack parted to use BLKRRPART again and see if that helps, but it's probably going to take a few days as I need to get the emulator up and running first so I can rebuild the udeb. -- Niko Tyni nt...@debian.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/20101217124018.ga3...@madeleine.local.invalid
Bug#605562: installation-report: Installation from usb stick lead to unbootable system (und unbootable usb stick)
Alexander Reichle-Schmehl toli...@debian.org writes: Am 02.12.2010 11:36, schrieb Alexander Reichle-Schmehl: I saved the contents of /var/log/installer after the installation, but need to recover mu original system for now to do some work. Ähh... Sorry. It seems it wasn't a good idea to tar /var/log/installer to /tmp. So I don't have the logs from my attempt with the daily installer, but I still have the ones from the installation with beta-1. I think I can also try to reproduce it on a similar machine whenever you want me to test something without much delay. Hi Alexander, Could you please retest with a beta-2 image, just to make sure that the issue is still present? And please keep the logs this time! :) -- Thanks, Feri. -- 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/87zks4mk57@tac.ki.iif.hu
win32-loader: offer a Boot from network with gPXE option
First of all thank you for your wonderful win32-loader. We've modified it a bit so that it adds a Boot from network entry in the Windows boot loader, instead of loading a Linux kernel. To accomplish this we statically linked gpxe.lkrn [1] to win32-loader.exe, and we modified main.nsi to load this instead of vmlinuz. No initrd was necessary. Currently the resulting ltsp-loader.exe [2] is used in some thousand Greek school PCs to netboot thin and fat clients. But many others have asked for this functionality in the #ltsp irc channel and in the ltsp-discuss mailing list, so we think it'd be much better if the upstream win32-loader Makefile supported a Boot from network with gPXE target. Unfortunately gPXE is not yet in Debian due to (afaik) some unresolved licensing issues. However if the win32-loader Makefile supported a gPXE target, maybe one of the following would be possible: * The gPXE devs to compile win32-loader with the gPXE target, and to host the resulting win32-loader-gpxe.exe on their site themselves. * Or a sysadmin or user could do that for his own use. * Or win32-loader.exe could dynamically download gpxe.lkrn from the gPXE website. If you want we can send you the .diff for main.nsi that we currently have, but we aren't very skilled with NSIS scripting so if you decide to add that functionality upstream you'd probably want to properly reimplement this yourselves. :) In any case thanks again, Alkis Georgopoulos [1]: http://www.etherboot.org/ [2]: http://users.sch.gr/alkisg/tosteki/index.php?action=dlattach;topic=2136.0;attach=1941 -- 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/1292606251.1777.68.ca...@alkis
Bug#605759: [s390/hercules] disk partitioning failed: no /dev/dsda1
Niko Tyni nt...@debian.org writes: On Thu, Dec 16, 2010 at 05:37:55PM +0100, Ferenc Wagner wrote: Niko Tyni nt...@debian.org writes: Hercules s390 emulator installation failed at disk partitioning; new partitions don't seem to show up in /dev. Thanks for the detailed but to-the-point report. This may be a kernel, a udev or a partman issue. Could you please try backing out of the partitioning menu to the main menu, start a shell in the installer environment with the appropriate menu item and do the partitioning yourself by fdasd or whatever's needed? Then please check if the new partitions show up in /proc/partitions and under /dev. This would help us narrowing down the case. It works fine if I create the partition manually with fdasd. Thanks, that's good info. Now the question is why parted_server failed to refresh the DASD partitions. It's a pity you didn't attach /var/log/partman. Could you please attach it to the bug report, preferably together with /var/log/syslog? You could get them by selecting Save debug logs from the installer main menu. Wait, see below. Furthermore, if I try to create a partition first with the d-i interface (getting the error) and then invoke fdasd and write out a trivial no-op such as change the volume serial from LIN120 to LIN120, /dev/dasda1 appears. So libparted commits the partition, only fails to notify the kernel. It looks to me like the problem is that d-i does not manage to reread the partition table. Agreed. I'm not sure if I understand the architecture correctly here, but maybe the problem is this change in parted 2.3 ? libparted: remove now-worse-than-useless _kernel_reread_part_table Now that we're using BLKPG properly, there's no point in using the less-functional BLKRRPART ioctl to make the kernel reread the partition table. More importantly, this function would fail when any partition is in use, in spite of our having carefully vetted them via BLKPG ioctls. I see fdasd (as of s390-tools 1.8.3-3) uses BLKRRPART and not BLKPG. The timeline would also fit the successful reports #569209 and #575682. This looks a fairly plausible theory, and the outcome is even more interesting, search for DASD in git log libparted/arch/linux.c. As I understand it, 9fa0e180 may even fix this problem. I suppose I can try to hack parted to use BLKRRPART again and see if that helps, but it's probably going to take a few days as I need to get the emulator up and running first so I can rebuild the udeb. Probably you'd be better off backporting the relevant changes to 2.3-4 and testing that. -- Good luck, Feri. -- 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/87r5dgmda0@tac.ki.iif.hu
Bug#605562: installation-report: Installation from usb stick lead to unbootable system (und unbootable usb stick)
Hi! * Ferenc Wagner wf...@niif.hu [101217 17:36]: I saved the contents of /var/log/installer after the installation, but need to recover mu original system for now to do some work. Ähh... Sorry. It seems it wasn't a good idea to tar /var/log/installer to /tmp. So I don't have the logs from my attempt with the daily installer, but I still have the ones from the installation with beta-1. I think I can also try to reproduce it on a similar machine whenever you want me to test something without much delay. Could you please retest with a beta-2 image, just to make sure that the issue is still present? And please keep the logs this time! :) It's on my todo list. Hopefully I'll have the time on monday or tuesday. 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/20101217192744.gt2...@melusine.alphascorpii.net
Bug#607392: installation-reports: Successful installation with small remark about char encoding at boot
Package: installation-reports Severity: minor Tags: d-i -- Package-specific info: Boot method: Netinst USB Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz Date: 2010-12-16 Machine: Lenovo ThinkPad X300 Partitions: FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/systema-root ext358757308 34397056 21375500 62% / tmpfstmpfs 1009580 0 1009580 0% /lib/init/rw udev tmpfs 1004076 236 1003840 1% /dev tmpfstmpfs 1009580 0 1009580 0% /dev/shm /dev/sda1 ext2 233191 16277204473 8% /boot 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:[O] Comments/Problems: Everything perfect. Thanks a lot for all your wonderful work. Just one remark about 2 small character encoding problems. Here they are: 1. mode (d??panage) 2. Chargement du disque m??moir initial The 1. appears on the 2nd bootloader line. This corresponds to the French translation of rescue mode, with the accented character being replaced by ?. The 2. appears when mounting an dm-crypt device. Best and warm regards -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101127 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux systema 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b3] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b5] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b5] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20b9] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ab] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ac] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) lspci -knn: Subsystem:
Bug#607265: marked as done (installation-reports: Squeeze on ASUS X71SL - All went well)
Your message dated Fri, 17 Dec 2010 20:03:04 + with message-id 201012172003.04813.el...@debianpt.org and subject line Re: Bug#607265: installation-reports: Squeeze on ASUS X71SL - All went well has caused the Debian Bug report #607265, regarding installation-reports: Squeeze on ASUS X71SL - All went well 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.) -- 607265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: installation-reports: Squeeze on ASUS X71SL - All went well Package: installation-reports Severity: normal *** Please type your report below this line *** All went perfectly well. -- Package-specific info: Boot method: usb key Image version: 172787712 21 nov. 18:08 debian-squeeze-di-beta1-amd64-netinst.iso ; http://d-i.debian.org/daily-images/amd64/daily/hd-media/ Date: 2010 21 nov. 18:08 Machine: ASUS X71SL Partitions: df -Tl will do; the raw partition table is preferred Disk /dev/sda: 320 GB, 320070320640 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1127510241406 1c Hidd FAT32 LBA /dev/sda2 *1276 11100789112807 HPFS/NTFS Warning: Partition 2 does not end on cylinder boundary. /dev/sda3 11102 14141244107675 Extended /dev/sda5 11102 11345 1951897 82 Linux swap Warning: Partition 5 does not end on cylinder boundary. /dev/sda6 11346 11589 1951897 83 Linux Warning: Partition 6 does not end on cylinder boundary. /dev/sda7 11590 11833 1951897 83 Linux Warning: Partition 7 does not end on cylinder boundary. /dev/sda8 11834 12077 1951897 83 Linux Warning: Partition 8 does not end on cylinder boundary. /dev/sda9 12078 12564 3903795 83 Linux Warning: Partition 9 does not end on cylinder boundary. /dev/sda10 12565 13051 3903795 83 Linux Warning: Partition 10 does not end on cylinder boundary. /dev/sda11 13052 13704 5237190 83 Linux Warning: Partition 11 does not end on cylinder boundary. /dev/sda12 13705 13826 971932 83 Linux Warning: Partition 12 does not end on cylinder boundary. /dev/sda13 13826 14141 2530237 83 Linux Warning: Partition 13 does not end on cylinder boundary. /dev/sda4 14142 38913 198973057 83 Linux ... many systems on my machine I installed base-system on /dev/sda8 then moved /usr and /var to lvm partitions on /dev/sda4. Installed then x11 and all needed software. I didn't dare to work through lvm from the installer, being afraid of damaging my other systems. 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: [ ] 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: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Nothing special ; all went well. Just see after the partition table up there. -- 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 20101121-00:16 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux asusqueeze 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 671MX [1039:0671] lspci -knn:
Bug#607400: installation-reports: Debootstrap Error: Failed to determine the codename for the release
Package: installation-reports Severity: normal Tags: d-i At first I tried the syslinux way, but I was not able to boot from the Flash. So I formated the Flash to ext3 and used Grub2, then I copied the hd-media files and first installation CD ISO. Boot was succesfull, first part of installation was without problems, I used installation without network configuration. Last succesfull step was partitioning and formating (all in one ext4 partition + swap). The step Install Base System failed with the message: Debootstrap Error: Failed to determine the codename for the release I did the debootstrap manually (manual mounting of the iso etc.) but then the installer was lost (step was not finished so following steps writes error messages, I ignored them and it seems that some steps was finished, but the system was not bootable) and I was not able to finish installation. -- Package-specific info: Boot method: USB Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-CD-1.iso and http://ftp.cz.debian.org/debian/dists/squeeze/main/installer-amd64/current/images/hd-media/ Date: 16.12.2010 evening Machine: Custom PC, Gigabyte motherboard, Intel i7 950, SATA HD Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [ ] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [ ] Install boot loader:[E] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == Report is created on other machine so automatically generated info has not any sense here. -- 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/20101217225638.9679.56847.report...@krabice.naxo.net
Re: debian-installer daily builds on hppa buildd
On Mon, Dec 06, 2010 at 06:14:16PM +0100, Gaudenz Steinlin wrote: [ Sorry to those that receive this mail twice. I messed up the recipient list the first time. ] Hi Dann Excerpts from Andreas Barth's message of Mit Nov 10 22:51:05 +0100 2010: * dann frazier (da...@debian.org) [101110 22:46]: I'd be glad to set this up on one of the hppa buildds (peri or penalosa) if DSA (CC'd) is ok with it. However, the above e-mail suggests we need to have working LVM snapshots. iirc, we've had problems with those on hppa in the past. Is that a hard requirement? LVM is just the way it is done now (basically we clone snapshots, install stuff there, and then toss the chroot at the end). It could be done different of course. Is there any progress on this. There are still no d-i builds for hppa. Or is this not going to happen and the daily builds for hppa should be removed from d-i.debian.org? In progress. I have builds going on a system at home am working on getting the ssh key setup now. -- 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/20101217231226.gf26...@dannf.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:hppa Jun 07 00:12 bui...@lafayette build_cdrom http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log * OLD BUILD:hppa Jun 07 00:16 bui...@lafayette build_netboot http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log * OLD BUILD:hppa Jun 07 00:21 bui...@lafayette build_miniiso http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log * OLD BUILD:mipsel Dec 09 00:12 bui...@rem build_cobalt_netboot-2.6_serial http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log * OLD BUILD:mipsel Dec 09 00:18 bui...@rem build_cobalt_netboot-2.6_ssh http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log * OLD BUILD:mipsel Dec 09 00:20 bui...@rem build_cobalt_netboot-2.6_common http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log * OLD BUILD:mipsel Dec 09 00:24 bui...@rem build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log * OLD BUILD:mipsel Dec 09 00:29 bui...@rem build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:sparc Jul 12 11:04 stapp...@dd build_cdrom http://people.debian.org/~stappers/d-i/sparc/daily/build_cdrom.log * OLD BUILD:sparc Jul 12 11:08 stapp...@dd build_netboot http://people.debian.org/~stappers/d-i/sparc/daily/build_netboot.log * OLD BUILD:sparc Jul 12 11:11 stapp...@dd build_miniiso http://people.debian.org/~stappers/d-i/sparc/daily/build_miniiso.log Totals: 116 builds (0 failed, 11 old) -- 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/e1ptl9x-0004uu...@ravel.debian.org
Bug#607417: win32-loader: please offer a Boot from network with gPXE option
Package: win32-loader Severity: wishlist X=Debbugs-CC: Alkis Georgopoulos alk...@gmail.com First of all thank you for your wonderful win32-loader. We've modified it a bit so that it adds a Boot from network entry in the Windows boot loader, instead of loading a Linux kernel. To accomplish this we statically linked gpxe.lkrn [1] to win32-loader.exe, and we modified main.nsi to load this instead of vmlinuz. No initrd was necessary. Currently the resulting ltsp-loader.exe [2] is used in some thousand Greek school PCs to netboot thin and fat clients. But many others have asked for this functionality in the #ltsp irc channel and in the ltsp-discuss mailing list, so we think it'd be much better if the upstream win32-loader Makefile supported a Boot from network with gPXE target. Unfortunately gPXE is not yet in Debian due to (afaik) some unresolved licensing issues. However if the win32-loader Makefile supported a gPXE target, maybe one of the following would be possible: * The gPXE devs to compile win32-loader with the gPXE target, and to host the resulting win32-loader-gpxe.exe on their site themselves. * Or a sysadmin or user could do that for his own use. * Or win32-loader.exe could dynamically download gpxe.lkrn from the gPXE website. If you want we can send you the .diff for main.nsi that we currently have, but we aren't very skilled with NSIS scripting so if you decide to add that functionality upstream you'd probably want to properly reimplement this yourselves. :) In any case thanks again, Alkis Georgopoulos [1]: http://www.etherboot.org/ [2]: http://users.sch.gr/alkisg/tosteki/index.php?action=dlattach;topic=2136.0;attach=1941 -- signature.asc Description: Digital signature
Bug#607392: installation-reports: Successful installation with small remark about char encoding at boot
Quoting M.-A. DARCHE (ma.dar...@cynode.org): Just one remark about 2 small character encoding problems. Here they are: 1. mode (d??panage) 2. Chargement du disque m??moir initial The 1. appears on the 2nd bootloader line. This corresponds to the French translation of rescue mode, with the accented character being replaced by ?. The 2. appears when mounting an dm-crypt device. I don't really understand what you mean by 2nd bootloader line. Could you give us the steps needed to reproduce the bug you found? Is this what you see on the installed system? signature.asc Description: Digital signature
Processed: Re: Bug#607417: win32-loader: please offer a Boot from network with gPXE option
Processing commands for cont...@bugs.debian.org: submitter 607417 Alkis Georgopoulos alk...@gmail.com Bug #607417 [win32-loader] win32-loader: please offer a Boot from network with gPXE option Changed Bug submitter to 'Alkis Georgopoulos alk...@gmail.com' from 'Christian PERRIER bubu...@debian.org' thanks Stopping processing here. Please contact me if you need assistance. -- 607417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12926565477844.transcr...@bugs.debian.org
