Bug#611570: fails on kfreebsd-amd64 CD1
Quoting Joey Hess (jo...@debian.org): Robert Millan wrote: Note: this seems related to #611569, however I'm reporting it as an apt-setup bug because apt-setup seems to be taking care of the mount/umount part already, in which case #611569 isn't supposed to have any effect. No, apt-setup still relies on apt-cdrom mounting the CD. The CD will already be mounted, as it is manually mounted for debootstrap. apt-setup unmounts it, runs apt-cdrom, and re-mounts it. And there are code paths where apt-cdrom cannot mount the CD (for example, hd-media installs), and there apt-setup prevents it doing any mounting and leaves the CD pre-mounted. But none of these should have any bearing on your case, #611569 seems at fault. So, this #611570 should then be closed, right? signature.asc Description: Digital signature
Gaucis JanisViesturs iesaka tev nevis trakot, bet smelties dolarus no laimes akas
Izla$i sho majaslapu un sac pelnit $$$ bez stresa un kaveshanaas! pec pamacibas luukojies te: http://www.kazino-metodika.info Filarets un Neja jau guust smukus ienakumus! -- 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/auto-15400...@inc.ru
Bug#611599: marked as done (Maybe a ADSL option in installer(squeeze) is better to me)
Your message dated Mon, 31 Jan 2011 06:38:19 +0100 with message-id 20110131053819.gu5...@mykerinos.kheops.frmug.org and subject line Re: Bug#611599: Maybe a ADSL option in installer(squeeze) is better to me has caused the Debian Bug report #611599, regarding Maybe a ADSL option in installer(squeeze) is better to me 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.) -- 611599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD-RW Image version: /i386/iso-cd/debian-squeeze-di-rc1-i386-netinst.iso from http://www.debian.org/devel/debian-installer/ Date: 2011.l.28--1.30 Machine: DIY, Intel mainboard ,NVIDIA MX440 Processor: Memory: Partitions: partitions by myself , 9.7G ext4 Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [Note] Detect network card:[O] Configure network: [NO DHCP,I have ADSL ] 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:[?] What is it mean? erase old data in partation? I format it. Comments/Problems: 1. I use boot from CDROM (squeeze_netinst_RC1), IT dead in mainboard LOGO(Intel MB) ,and I find the CD is OK(bootable in other PC). My win XP driver and PPPOE fauit(It be OK for a long time),HW is a old 3COM netcard. After change a realtek 8139D netcard, the boot is OK. I don't know if install_rc1 cause 3COM netcard bad ?It's not important, it's too old and only one, I have some RL8139D netcard . (If in this netcard bad situation, can installer jump it and pop a message say: Not find netcard (NIC) in your system . ? - 2. I'm in china , many people use ADSL in home. And I use graph install (shell Install I think no problem) Install try to find DHCP , and after fault, I input 192.168.x.x something. Maybe a ADSL option in installer(squeeze) is better to me? like: 1. Local network with DHCP (Had a gateway to internet) 2. ADSL use pppoe (You know your username and password) This may faster to beginer. 3. After I use expert mode to install pppoe, I find pppoeconf is in NETINST cdrom. But if I choise a sources mirror in GRAPHINSTALL mode, I lost deb cdrom in sources.list. Can you add this for me? NETINST is default in sources.list (deb cdrom xx) After user choise sources mirror, display a message : nbsp;You must use apt-get update before apt-get install anything When the squeeze is ok, if user (beginer) use : apt-get install xx and get nothing , give this message: Is the software in the list? Maybe use apt-get update first. 4. In console, the text is too small, oh my eyes In etch lenny It's OK (Other PCs), maybe add a item in grub2 (big text)? I should add vga=7xx something? I'll test afterwork... THANK all of you . Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. ---End Message--- ---BeginMessage--- 2. I'm in china , many people use ADSL in home. And I use graph install (shell Install I think no problem) Install try to find DHCP , and after fault, I input 192.168.x.x something. Maybe a ADSL option in installer(squeeze) is better to me? like: 1. Local network with DHCP (Had a gateway to internet) 2. ADSL use pppoe (You know your username and password) The option exists in expert mode. You need to load the ppp-udeb component for that. Please note that this is loosely tested as we unfortunately have few developers who use PPPoE. signature.asc Description: Digital signature ---End Message---
Bug#444017: Please document win32-loader as a possible boot method for i386 and amd64
package installation-guide retitle 444017 Please point to the win32-loader standalone version as possible boot method for x86 tags 444017 +patch thanks tags Le Tuesday 25 September 2007 15:39:30 Jérémy Bobbio, vous avez écrit : Package: installation-guide Version: 20070319 Severity: wishlist Hi! As win32-loader is now present on Debian CDs and DVDs, it should be documented in the documented as a possible boot method for the relevant architectures (i386 and amd64). This would fit in sections 5 and A of the installation guide. Cheers, Hi Jérémy, as far as I can tell, this is fixed by the 5.1.2 section. But now that the standalone flavour will be shipped as tools/win32-loader/stable/win32-loader.exe on the mirrors, this ought to be documented too. Hence retitling and tagging accordingly. Here would be a proposed patch: Index: boot-installer/x86.xml === --- boot-installer/x86.xml (révision 66346) +++ boot-installer/x86.xml (copie de travail) @@ -81,6 +81,14 @@ /parapara +It is also possible to run a small Windows executable that will download the +installer, collect some configuration options and modify the Windows +bootloader accordingly. Then, on reboot, one can start the installer. +This executable is available as tools/win32-loader/stable/win32-loader.exe on +the debian; mirrors. + +/parapara + If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB TIA, cheers, OdyX -- Didier Raboud, proud Debian Developer. CH-1020 Renens o...@debian.org signature.asc Description: This is a digitally signed message part.
Processed: Tagging…
Processing commands for cont...@bugs.debian.org: package installation-guide Limiting to bugs with field 'package' containing at least one of 'installation-guide' Limit currently set to 'package':'installation-guide' retitle 444017 Please point to the win32-loader standalone version as possible boot method for x86 Bug #444017 [installation-guide] Please document win32-loader as a possible boot method for i386 and amd64 Changed Bug title to 'Please point to the win32-loader standalone version as possible boot method for x86' from 'Please document win32-loader as a possible boot method for i386 and amd64' tags 444017 +patch Bug #444017 [installation-guide] Please point to the win32-loader standalone version as possible boot method for x86 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 444017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444017 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.12964841664633.transcr...@bugs.debian.org
Re: Bug#444017: Please document win32-loader as a possible boot method for i386 and amd64
Didier 'OdyX' Raboud, le Mon 31 Jan 2011 15:27:44 +0100, a écrit : Index: boot-installer/x86.xml === --- boot-installer/x86.xml (révision 66346) +++ boot-installer/x86.xml (copie de travail) @@ -81,6 +81,14 @@ /parapara +It is also possible to run a small Windows executable that will download the +installer, collect some configuration options and modify the Windows +bootloader accordingly. Then, on reboot, one can start the installer. +This executable is available as tools/win32-loader/stable/win32-loader.exe on +the debian; mirrors. + +/parapara + The bootloading explanation should be merged with the paragraph just below, since that's exactly the same program which gets started... 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/20110131150342.gk6...@const.bordeaux.inria.fr
Permission to upload win32-loader to *-proposed-updates (was Re: Mirroring win32-loader.exe in debian/tools/)
Le Tuesday 25 January 2011 16:14:40 Didier 'OdyX' Raboud, vous avez écrit :
CC'ing debian-release for clarity (thread starts at
http://lists.debian.org/debian-boot/2011/01/msg00592.html )
… dropping ftpmaster@ and Otavio.
Le Tuesday 25 January 2011 12:18:02 Didier 'OdyX' Raboud, vous avez écrit :
I will upload a win32-loader with a byhand win32-loader{.exe,txt} to
squeeze- proposed-updates.
Just FYI, the Release Team NACK'ed that upload over IRC, because it's too
late and because an upload to t-p-u cannot happen when sid and testing are
in sync. Hence I'm stuck with those solutions (in personal order of
preference):
1) convince them to allow me to upload both:
a) a new version to unstable
This has happened now; thanks to Joerg. A (highly) fixed version of my dak
patch
has now been merged and the needed changes have been pushed to the win32-loader
git repository, partly uploaded: 0.6.22 has been uploaded to unstable and
contains only half the changes for the autobyhand functionality (it lacks
_$version_$arch postfix).
So win32-loader-standalone.exe 0.6.22 will be made available as tools/win32-
loader/stable/win32-loader.exe as part of the release process if I understood
Joerg correctly.
I'd like to get a 0.6.22squeeze1 version uploaded to Squeeze (before or after
the freeze doesn't matter much), in order to be in sync between the
win32-loader
package in the archive and the (extracted) win32-loader.exe available as
tools/win32-loader/${SUITE}/win32-loader.exe.
Planned debdiff (between current Squeeze and planned -proposed-updates) is
attached, please comment (after next week-end if you prefer. :-) ).
(As 0.6.22 is already in unstable, I will upload a 0.6.23 before uploading that
0.6.22squeeze1 to let it go in. I would prefer not to go with 0.621squeeze1, as
that would mean a backwards-going version in the byhanded files.)
Cheers,
OdyX
--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
o...@debian.org
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 000..6bd0fe7
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,15 @@
+ README.source for win32-loader
+
+When uploading this package, it is possible to add win32-loader-standalone.exe
+as debian/tools/win32-loader/$(SUITE)/win32-loader.exe on the mirrors.
+
+If you NMU this package, be sure to have the BYHAND variable set correctly; a
+reasonable policy is:
+
+ - set BYHAND to yes for all uploads towards unstable,
+ - set BYHAND to no for all uploads towards experimental (as it will not
+work),
+ - coordinate with FTP Masters (at least) and Release Team (if needed) for
+all other cases.
+
+ -- Didier Raboud o...@debian.org Tue, 25 Jan 2011 23:26:22 +0100
diff --git a/debian/changelog b/debian/changelog
index d6bea04..01aa09f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,23 @@
+win32-loader (0.6.22squeeze1) stable-proposed-updates; urgency=low
+
+ * Append version and arch to the byhand filenames, to make dak happy;
+thanks Joerg for the digging!
+
+ -- Didier Raboud o...@debian.org Mon, 31 Jan 2011 15:36:27 +0100
+
+win32-loader (0.6.22) unstable; urgency=low
+
+ [ Joey Hess ]
+ * update Vcs fields
+
+ [ Didier Raboud ]
+ * Add a dpkg-distaddfile byhand call to install win32-loader-
+standalone.exe as tools/$(SUITE)/win32-loader.exe on the mirrors.
+ * Set BYHAND to yes.
+ * Use my @d.o address and remove the DMUA flag.
+
+ -- Didier Raboud o...@debian.org Tue, 25 Jan 2011 23:28:30 +0100
+
win32-loader (0.6.21) unstable; urgency=low
[ Updated translations ]
diff --git a/debian/control b/debian/control
index 391a328..b51a1a8 100644
--- a/debian/control
+++ b/debian/control
@@ -2,8 +2,7 @@ Source: win32-loader
Section: utils
Priority: extra
Maintainer: Debian Install System Team debian-boot@lists.debian.org
-Uploaders: Robert Millan rmh.deb...@aybabtu.com, Didier Raboud did...@raboud.com
-DM-Upload-Allowed: yes
+Uploaders: Robert Millan rmh.deb...@aybabtu.com, Didier Raboud o...@debian.org
Build-Depends:
debhelper (= 7.0.50),
nsis (= 2.43),
@@ -14,8 +13,8 @@ Build-Depends:
locales-all,
cpio-win32 (= 2.11-4), gzip-win32
Standards-Version: 3.9.1.0
-Vcs-Svn: svn://svn.debian.org/d-i/trunk/win32-loader/
-Vcs-Browser: http://svn.debian.org/wsvn/d-i/trunk/win32-loader/?op=log
+Vcs-Browser: http://git.debian.org/?p=d-i/win32-loader.git
+Vcs-Git: git://git.debian.org/d-i/win32-loader.git
Package: win32-loader
Architecture: all
diff --git a/debian/rules b/debian/rules
index 73582af..ac0f3df 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,5 +1,11 @@
#!/usr/bin/make -f
+# Install the win32-loader-standalone.exe as debian/tools/win32-loader/$(SUITE)/win32-loader.exe on the mirrors
+BYHAND ?= yes
+
+W32_VERSION := $(shell dpkg-parsechangelog | sed -rne 's,^Version: ([^-]+).*,\1,p')
+W32_BYHAND_NAME := win32-loader_$(W32_VERSION)_all
+
%:
dh $@
@@ -13,3 +19,13 @@ override_dh_auto_build:
Bug#611648: brltty-udeb: detected USB braille device just shows screen not in text mode
Package: brltty-udeb Version: 4.2-7 Severity: normal In some cases, when letting the Debian Installer detect the plugged USB braille device, the latter ends up showing only screen not in text mode. This happens because udev may need some time to actually discover that a USB braille device is connected, during which the rest of Debian Installer has the time to start bterm (or even Xorg), which is not accessible and produces this warning. A workaround is to pass brltty at the kernel command line, which will force USB device detection and disabling bterm or Xorg. A proper solution is not so easy, because udev does not really have a notion of I have finished discovering devices, udev settle is not enough. This thus boils down to the I first boot, then plug a USB braille device scenario, which is supposed to switch d-i to textmode so that brltty can read it. Samuel -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Thibault samuel.thiba...@fnac.net c hiri, le cri ici, c des marrants c j'ai un rep .uglyhackdirectorywithoutacls ds mon home -+- #ens-mim en stage -+- -- 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/20110131164821.ga5...@const.bordeaux.inria.fr
Re: Bug#611648: brltty-udeb: detected USB braille device just shows screen not in text mode
Attached is a proposed patch for the errata file, to tell about the workaround. Samuel Index: errata.wml === RCS file: /cvs/webwml/webwml/english/devel/debian-installer/errata.wml,v retrieving revision 1.154 diff -u -p -r1.154 errata.wml --- errata.wml 22 Jan 2011 22:55:01 - 1.154 +++ errata.wml 31 Jan 2011 16:59:07 - @@ -11,6 +11,15 @@ describing the problem. /p dl class=gloss + dtPossibly non-working detected USB braille devices/dt +ddWhen letting the Debian Installer detect a plugged USB braille +device, the latter may end up showing only screen not in text +mode. This is due to a potential race between detection and frame +buffer start. A workaround is to pass ttbrltty/tt on the kernel +command line to force detection. + See a href=http://bugs.debian.org/611648;#611648/a. + /dd + dtPotential installation problems with RTL8169-based network cards/dt ddThe Debian installer may be unable to use network cards based on the RTL8169 family during the installation, which includes
Re: Incorrect RO translation in d-i
Quoting Vitalie L (vitalie.l...@gmail.com): Hello, On GRUB configuration screen there is a wrong translation for screen title. Ro: Configurez man-db / Configure man-db It should be Configurez GRUB. Screenshot: http://myfiles.md/d/16821/764/d-i_grub_setup_screen.jpg I downloaded debian-testing-amd64-netinst.iso on Jan 27. Andrei suggested to post here a message, maybe some variable is missing/broken. Thanks for doing so. However, this has nothing to do, indeed, with the Romanian translation. Joey Hess or Colin Watson probably have an explanation for that behaviour (IIRC, I saw such explanation recently, but don't remember where...). signature.asc Description: Digital signature
Bug#607301: No boot from SiI 3114 + single SATA drive on di RC2 i386 20101209 New install, No raidArray.
25.01.2011 ( di-rc 2, rc-2, Release Candidate 2. ) Installing from 'Debian squeeze-di-rc2 i386 1' onto the same machine with more details above: Motherboard: MS5169 Processor: AMD K-6-2/400400.9Mhz Controller PCI, Silicon Image SiI 3114 sata raid bios version 5.3.14 2006. Using the graphical installer, gives the same symptoms as the Beta-1, Beta-2, RC-1 installs :- Initially, I installed GRUB boot loader to the master boot record ? YES, At a later install, I answered NO, for /boot to go in it's own partition. Finish the installation: Installation complete, so it is time to boot into your new system ... Having installed succesfully so far, when the install auto reboots through the bios, I get the same symptom. The hardware post and bios progress ok. When the bios hands over to continue the boot process from a hard disk. It seems unsuccessful. I get symptom :- Searching for Boot Record from CDROM... Not found. (A blank line) Boot Failure Reboot and Select proper Boot *** This is where the install fails. It does not boot up into the newly installed system. *** Using the Graphical Rescue Mode on: Debian GNU/Linux squeeze- di-rc2_squeeze_-oficial snapshot i386 DVD Binary-1 20110121-14:41 Selecting: 'Installer boot menu','Advanced Options'. At screen: 'Enter rescue mode','Device to use as Root FiLe System:' I selected /dev/sda1 ( It found the 'SiI 3114' sata disk sda1 ) At screen: 'Enter rescue mode','Rescue operations' I selected 'Execute a shell in /dev/sda1 At screen entitled: 'Enter rescue mode',Interactive Shell on /dev/sda1' # mount shows: /dev/sda1 on /target type ext2 (rw, ... /dev/sda3 on /target/boot type ext3 (rw) # mount /boot # /usr/bin/nano /boot/grub/device.map showed (hd0) /dev/disk/by-id/ata-ST3160815AS_ 9 ... I must confess I THINK device.map originally specified (hd0) I will check again, when I re install again. 26.01.2011 GRUB (Legacy) Now changing to a different environment on the same machine. Using Grub Rescue Disk 'Grub-0.95-i486-pc-iso' . Rescue Disk 'Booting command-list' I cannot get grub to recognise my single sata hard disk drive. I thought ' root (sd0,2) ' would have been the correct device. Alas any sd gives: ' Error 23: Error while parsing number '. I believe GRUB doesn't distinguish between ide and scsi (or sata), so the 'hd' nomenclature is correct for all hard drives. A drive number above hd7, such as hd8 gives: Error 12: Invalid device request.( It seems reasonable to me.) I have since tried from hd0,0 through to hd7,7 with no success. Grub 0.95 Symptom: Error 21: Selected disk does not exist . Regards Mctech. Thank you one and all for the Great Software. -- 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/aanlktimdp_xbhrbqmec7yhbvng7+nbovnco4z-lg-...@mail.gmail.com
Bug#611670: os-prober didnt detect a new gentoo installation
Package: os-prober Version: 1.42 Severity: normal os-prober didnt detect a new gentoo-installation because the kernel was callled differend than os-prober did expect. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-020637rc8-generic (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.11.2-9 Embedded GNU C Library: Shared lib os-prober recommends no packages. os-prober suggests no packages. -- no debconf information *** /home/wibke/os-prober-gentoo-detection.patch diff -ru os-prober-1.42/linux-boot-probes/mounted/common/90fallback os- prober-1.42kanotix1/linux-boot-probes/mounted/common/90fallback --- os-prober-1.42/linux-boot-probes/mounted/common/90fallback 2010-12-01 18:45:05.0 +0100 +++ os-prober-1.42kanotix1/linux-boot-probes/mounted/common/90fallback 2011-01-31 15:08:51.968608486 +0100 @@ -13,7 +13,8 @@ exitcode=1 for kernpat in /vmlinuz /vmlinux /boot/vmlinuz /boot/vmlinux /boot/vmlinuz* \ - /boot/vmlinux* /vmlinuz* /vmlinux*; do + /boot/vmlinux* /vmlinuz* /vmlinux* \ + /kernel-* /boot/kernel-*; do if echo $kernpat | grep -q boot/; then kernbootpart=$bootpart else @@ -32,8 +33,10 @@ initrdname2=$(echo $kernfile | sed -n 's/vmlinu[zx]\([0-9][0-9]*\)/kernel\1/p' | sed 's/$/.img/') # Dracut initramfses are named differently again. initrdname3=$(echo $kernfile | sed s/vmlinu[zx]/initramfs\*/ | sed 's/$/.img/') + # Gentoo + initrdname4=$(echo $kernfile | sed s/kernel/initramfs\*/) foundinitrd=0 - for initrd in $(eval ls $initrdname $initrdname1 $initrdname2 $initrdname3 2/dev/null); do + for initrd in $(eval ls $initrdname $initrdname1 $initrdname2 $initrdname3 $initrdname4 2/dev/null); do if [ -f $initrd ] [ ! -L $initrd ]; then -- 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/20110131195412.4739.13264.reportbug@wibke
Re: Bug#611648: brltty-udeb: detected USB braille device just shows screen not in text mode
A Segunda 31 Janeiro 2011 16:59:20 Samuel Thibault você escreveu: Attached is a proposed patch for the errata file, to tell about the workaround. Samuel Here it goes together with the previous issues added after RC2 release. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org Index: errata.wml === RCS file: /cvs/webwml/webwml/english/devel/debian-installer/errata.wml,v retrieving revision 1.154 diff -u -r1.154 errata.wml --- errata.wml 22 Jan 2011 22:55:01 - 1.154 +++ errata.wml 31 Jan 2011 20:21:13 - @@ -11,6 +11,46 @@ /p dl class=gloss + dtPossibly non-working detected USB braille devices/dt/dt + ddWhen letting the Debian Installer detect a plugged USB braille +device, the latter may end up showing only screen not in text +mode. This is due to a potential race between detection and frame +buffer start. A workaround is to pass ttbrltty/tt on the kernel +command line to force detection. + See a href=http://bugs.debian.org/611648;#611648/a. + /dd + + dtNo network driver for Sparc T2+/dt + ddniu network driver, required by newer T2+ sparc systems is not + included in d-i, making it impossible to install on them using any + method which relies on early network setup. Driver is included in + kernel packages, so network is expected to operate normally after + installation is completed.br / + See a ref=http://bugs.debian.org/608516;#608516/a. + /dd + + dtSystems using aty graphics cards may not boot the installer correctly/dt + dd + Systems using aty graphics cards (for example, Ultra 10) may not + boot the installer correctly, with kernel freezing early in the boot + stage with last message console [tty0] enabled, bootconsole + disabled. This is a kernel bug, for which a patch is available, + however it may be not fully fixed.br / + The issue may be worked around by adding a kernel boot parameter + 'video=atyfb:off' to turn off the framebuffer during boot, which + allows the installer (and regular kernel) to be booted on such systems.br / + See a ref=http://bugs.debian.org/609466;#609466/a. + /dd + + dtKeyboard selection, with graphical installer, does not work for some layouts/dt + dd + Preselection of keyboard is not working with graphical installations + for some combinations (Bulgaria, Swiss German, Sweden and Brazilian). + Also the choice made is not beind used, and the system + defaults to American English (/etc/default/keyboard).br / + See a ref=http://bugs.debian.org/610843;#610843/a. + /dd + dtPotential installation problems with RTL8169-based network cards/dt ddThe Debian installer may be unable to use network cards based on the RTL8169 family during the installation, which includes
Bug#611570: marked as done (fails on kfreebsd-amd64 CD1)
Your message dated Mon, 31 Jan 2011 22:33:19 +0100 with message-id aanlktimxd2fhqxkghvcqf5pe7md0mc2njufp59dar...@mail.gmail.com and subject line Re: Bug#611570: fails on kfreebsd-amd64 CD1 has caused the Debian Bug report #611570, regarding fails on kfreebsd-amd64 CD1 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.) -- 611570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt-setup Version: 1:0.53 Severity: normal User: debian-...@lists.debian.org Usertags: kfreebsd With debian-squeeze-di-rc2-kfreebsd-amd64-CD-1.iso: Jan 30 18:59:51 main-menu[106]: INFO: Menu item 'apt-setup-udeb' selected Jan 30 18:59:51 /usr/lib/apt-setup/generators/40cdrom: warning: /target/etc/mtab won't be updated since it is a symlink. Jan 30 18:59:51 apt-setup: Using CD-ROM mount point /media/cdrom/ Jan 30 18:59:51 apt-setup: Unmounting CD-ROM Jan 30 18:59:51 apt-setup: Waiting for disc... Jan 30 18:59:51 apt-setup: Please insert a Disc in the drive and press enter Jan 30 18:59:51 apt-setup: Mounting CD-ROM... Jan 30 18:59:51 apt-setup: E Jan 30 18:59:51 apt-setup: : Failed to mount the cdrom. Jan 30 18:59:51 apt-setup: mount: mounting /dev/cd0 on /cdrom failed: Device or resource busy After this error, /cdrom *is* mounted. Installation proceeds without CD support. Note: this seems related to #611569, however I'm reporting it as an apt-setup bug because apt-setup seems to be taking care of the mount/umount part already, in which case #611569 isn't supposed to have any effect. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- 2011/1/31 Christian PERRIER bubu...@debian.org: No, apt-setup still relies on apt-cdrom mounting the CD. The CD will already be mounted, as it is manually mounted for debootstrap. apt-setup unmounts it, runs apt-cdrom, and re-mounts it. And there are code paths where apt-cdrom cannot mount the CD (for example, hd-media installs), and there apt-setup prevents it doing any mounting and leaves the CD pre-mounted. But none of these should have any bearing on your case, #611569 seems at fault. So, this #611570 should then be closed, right? Yes. -- Robert Millan ---End Message---
Bug#611146: marked as done (mount /dev/cd0 fails on kFreeBSD)
Your message dated Mon, 31 Jan 2011 22:33:19 +0100 with message-id aanlktimxd2fhqxkghvcqf5pe7md0mc2njufp59dar...@mail.gmail.com and subject line Re: Bug#611570: fails on kfreebsd-amd64 CD1 has caused the Debian Bug report #611570, regarding mount /dev/cd0 fails on kFreeBSD 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.) -- 611570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: apt-setup Hi all, apt-setup: mount: mounting /dev/cd0 on /cdrom failed: Device or resource busy -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org ---End Message--- ---BeginMessage--- 2011/1/31 Christian PERRIER bubu...@debian.org: No, apt-setup still relies on apt-cdrom mounting the CD. The CD will already be mounted, as it is manually mounted for debootstrap. apt-setup unmounts it, runs apt-cdrom, and re-mounts it. And there are code paths where apt-cdrom cannot mount the CD (for example, hd-media installs), and there apt-setup prevents it doing any mounting and leaves the CD pre-mounted. But none of these should have any bearing on your case, #611569 seems at fault. So, this #611570 should then be closed, right? Yes. -- Robert Millan ---End Message---
Re: Incorrect RO translation in d-i
A Segunda 31 Janeiro 2011 16:59:40 Christian PERRIER você escreveu:
Quoting Vitalie L (vitalie.l...@gmail.com):
Hello,
On GRUB configuration screen there is a wrong translation for screen
title.
Ro: Configurez man-db / Configure man-db
It should be Configurez GRUB.
Screenshot: http://myfiles.md/d/16821/764/d-i_grub_setup_screen.jpg
I downloaded debian-testing-amd64-netinst.iso on Jan 27.
Andrei suggested to post here a message, maybe some variable is
missing/broken.
Thanks for doing so. However, this has nothing to do, indeed, with the
Romanian translation. Joey Hess or Colin Watson probably have an
explanation for that behaviour (IIRC, I saw such explanation recently,
but don't remember where...).
AFAIU it isn't provided a title for the window and 'something' is being used
instead.
In attachment a patch for finish-install, which needs to be reviewed.
(I wasn't able to test it as i am having problems with images built on my
local tree.)
--
Melhores cumprimentos/Best regards,
Miguel Figueiredo
http://www.DebianPT.org
mr diff: /home/elmig/debian/d-i/packages/finish-install
diff --git a/debian/postinst b/debian/postinst
index 243f62b..e8297e7 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -8,6 +8,8 @@ log() {
logger -t finish-install $@
}
+db_settitle debian-installer/finish-install/progress/title
+
partsdir=/usr/lib/finish-install.d
scriptcount=$(ls $partsdir/* | wc -l)
mr diff: finished (1 ok)
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:hppa Jan 17 07:06 didaily@c3700 build_cdrom http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log * OLD BUILD:hppa Jan 17 07:10 didaily@c3700 build_netboot http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log * OLD BUILD:hppa Jan 17 07:14 didaily@c3700 build_miniiso http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log * daily mipsel images build: The build daemon responsible for these builds is currently moving to a new hosting location. Daily builds should be available again within the first two weeks of 2011. * daily sparc images build: Due to the lack of buildd suitable buildd machine there are currently no daily builds for the SPARC architecture. These builds will be reenabled as soon as as a suitable machine is available. Totals: 113 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/e1pk4bd-0005zb...@ravel.debian.org
Bug#611713: installation-reports: Installation issue grub mixup between sata disk and pata disk
Package: installation-reports Severity: important Tags: d-i Box has one pata drive, master on primary ide controller, one sata drive. Installed Squeeze to pata drive, not sure of the desigation by the installer first drive in the list. When asked to installl grub okayed the installation to the mbr.Grub installed to the mbr of the sata drive, not the pata drive where the root file ystem was. On a reboot no grub found. Booted into rescue mode and ran grub-install, wrote grub into the mbr of the sata drive. -- Package-specific info: Boot method: network Image version: http://cdimage.debian.org/cdimage/squeeze_di_rc2/i386/iso-cd/debian-squeeze-di-rc2-i386-netinst.iso Date: Date and time of the install Machine: Custom: AMD64x2, 3Gb memory: Nvidia Quadro video. 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: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] 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 DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100614-00:07 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux myetch 2.6.32-5-amd64 #1 SMP Tue Jun 1 04:34:03 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: ATI Technologies Inc RX780/RX790 Chipset Host Bridge [1002:5957] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8353] lspci -knn: 00:02.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A) [1002:5978] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:0a.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F) [1002:597f] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Subsystem: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 3c) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8389] lspci -knn: Kernel driver in use: pata_atiixp lspci -knn: 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:836c] lspci -knn: 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] lspci -knn: Subsystem:
