Bug#494608: installation-report: KVM install debian lenny 20080810-09:14: no detection of hard drive
Hello, Just to say that the disk is detected with http://cdimage.debian.org/cdimage/daily-builds/daily/20080808-2/amd64/iso-cd/debian-testing-amd64-businesscard.iso Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#492751: Lenny beta 2 dies on boot up
I had the same problem on the VIA Nehemiah (in my case: stepping 8, 1 GHz) as explained in this link http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-07/msg11568.html this seems to be a problem of the via chip (something about stepping and NOP's) in kernels above 2.6.22 I installed the 2.6.22-3-486 from the lenny repository (via rescue mode of the installer) kernel is now booting - some dma problems remain maybe there is a chance to choose the 2.6.22 image by default for the buggy cpu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494608: installation-report: KVM install debian lenny 20080810-09:14: no detection of hard drive
Subject: installation-report: KVM install debian lenny 20080810-09:14: no detection of hard drive Package: installation-reports Version: 2.35 Severity: normal *** Please type your report below this line *** -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20080810-1/amd64/iso-cd/debian-testing-amd64-netinst.iso build 20080810-09:14, di 20080809-23:00 Date: Machine: KVM x86_64 Partitions: 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: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Detection of the hard drive did not work (it worked tow day before). What ever block device I use it did not work: - ide - scsi - virtio The device is present in /dev/ put d-i ask me to select a module, even if the right one is already loaded. I manually create a parition table on the disk without any problem, so it seems to be d-i related. I successfully install a debian etch, the following information are from the etch upgraded to lenny kvm virtual machine. Regards. -- 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 [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="4.0 (installer build 20070308etch3)" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux lenny 2.6.18-6-amd64 #1 SMP Sat Jan 26 08:39:14 UTC 2008 x86_64 unknown lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -nn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -nn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -nn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -nn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -nn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 20) lspci -vnn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -vnn: Flags: fast devsel lspci -vnn: lspci -vnn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -vnn: Flags: bus master, medium devsel, latency 0 lspci -vnn: lspci -vnn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (prog-if 80 [Master]) lspci -vnn: Flags: bus master, medium devsel, latency 64 lspci -vnn: I/O ports at c000 [size=16] lspci -vnn: lspci -vnn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -vnn: Flags: medium devsel, IRQ 9 lspci -vnn: lspci -vnn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] lspci -vnn: Flags: fast devsel lspci -vnn: Memory at f000 (32-bit, prefetchable) [size=32M] lspci -vnn: Memory at f200 (32-bit, non-prefetchable) [size=4K] lspci -vnn: lspci -vnn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 20) lspci -vnn: Flags: bus master, fast devsel, latency 64, IRQ 11 lspci -vnn: I/O ports at c100 [size=256] lspci -vnn: Memory at f2001000 (32-bit, non-prefetchable) [size=256] lspci -vnn: modulemap: 8086:7010 piix modulemap: 10ec:8139 8139cp lsmod: Module Size Used by lsmod: sd_mod 25600 0 lsmod: qnx4 16840 0 lsmod: ntfs 190728 0 lsmod: sha256 13312 0 lsmod: aes31040 0 lsmod: dm_crypt 16400 0 lsmod: dm_mod 62800 8 dm_crypt lsmod: xfs 485192 0 lsmod: reiserfs 231168 0 lsmod: jfs 166992 0 lsmod: ext3 138512 3 lsmod: jbd65392 1 ext3 lsmod: vfat 17792 0 lsmod: fat56752 1 vfat lsmod: ext2 70416 1 lsmod: mbcache13832 2 ext3,ext2 lsmod: 8139too33408 0 lsmod: 8139cp
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for controlbugs.debian.org: > # Sun Aug 10 08:03:07 UTC 2008 > # Tagging as pending bugs that are closed by packages in NEW > # http://ftp-master.debian.org/new.html > # > # Source package in NEW: trilinos > tags 362293 + pending Bug number 362293 not found. (Is it archived?) > # Source package in NEW: cdebconf-terminal > tags 339855 + pending Bug#339855: g-i should offer a shell within the graphical environment There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494532: lenny di-2 on dell optiplex 755 fail disk detection
Package: installation-reports Severity: important Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/netboot/netboot.tar.gz Date: 10 aug 2008, 13:00 Machine: Dell Optiplex 755 Processor: Core2 Quad Q6600 @ 2.40GHz Memory: 4 GB Partitions: n/a Output of lspci -knn (or lspci -nn): (this is from Ubuntu 8.04 which installed OK) 00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) 00:02.1 Display controller [0380]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b3] (rev 02) 00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02) 00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02) 00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02) 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) 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 AHCI Controller [8086:2922] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) 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: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Harddrive was not detected. I assume the installer is missing the driver for the chipset, Intel 82Q35 Express PT IDER Controller [8086:29b6] (rev 02) Interestingly, I found that http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452134 detected the harddrive, but did not detect the network (which worked for me) Regards, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Enable graphical installation for Xen flavour installer
On Fri, 2008-08-08 at 14:21 -0300, Otavio Salvador wrote: > Ian Campbell <[EMAIL PROTECTED]> writes: > > > On Fri, 2008-08-08 at 17:00 +0200, Frans Pop wrote: > >> On Thursday 07 August 2008, Ian Campbell wrote: > >> > The patch below, when combined with an update to 2.6.26 (required for > >> > Xen's paravirtual framebuffer, I used Otavio's recent patches) allows > >> > Xen to be installed using the graphical interface when a virtual > >> > framebuffer is configured for the guest. > >> > >> My first question would be whether we really need/want a G-I variant for > >> Xen. > > > > I wasn't intending to to create a second Xen variant, but rather to > > enhance the existing one with the graphical option. (I think you > > realised that but thought I'd make sure) > > I personally like the idea. Me too ;-) > Except from the size of the image, I see no issues. Me neither. I'll give it a few more days for objections to be raised but I'm inclined to enable the support after that. Ian. -- Ian Campbell My, how you've changed since I've changed. signature.asc Description: This is a digitally signed message part
Bug#427939: marked as done (mention discover1/discover difference in Descriptions)
Your message dated Sun, 10 Aug 2008 09:53:16 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: mention discover1/discover difference in Descriptions has caused the Debian Bug report #427939, regarding mention discover1/discover difference in Descriptions 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 [EMAIL PROTECTED] immediately.) -- 427939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427939 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: discover1 Version: 1.7.21 Severity: wishlist May I suggest putting something about the difference between discover1 and discover in the package Descriptions, and not wait until the user has installed the package only to find in the Readme: Discover 1.5 has only minimal support for kernel 2.6 (see below). As discover 2.0 is now in Debian (package discover), you're probably better off using this package if you run on 2.6. Mention it in both packages and both library and data packages' Descriptions. (Or else we think "1" must be better than "", but then the libraries are "2" must be better than "1".) --- End Message --- --- Begin Message --- Version: 2.1.2-3 This issue is no longer relevant after version 2.1.2-3 of discover was uploaded, as it provide the transition packages for discover1 to migrate all users to discover. The old discover1 package have been removed from unstable and testing. Happy hacking, -- Petter Reinholdtsen --- End Message ---
Bug#471233: marked as done (discover1: obsolete initscript blocks insserv)
Your message dated Sun, 10 Aug 2008 09:55:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: discover1: obsolete initscript blocks insserv
has caused the Debian Bug report #471233,
regarding discover1: obsolete initscript blocks insserv
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 [EMAIL PROTECTED]
immediately.)
--
471233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471233
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: discover1
Version: 1.7.22
Severity: normal
Usertags: obsolete-initscript
*** Please type your report below this line ***
Hi,
# sudo dpkg-reconfigure insserv
info: Checking if it is safe to convert to dependency based boot.
error: Obsolete conffile /etc/init.d/discover left behind by package discover1
info: Please check out this manually.
info: Refusing to convert boot sequence until this is fixed
info: See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
info: for more information on how to solve these issues. Most likely,
info: it is a bug in the binary package with the init.d script in
info: question, and not with insserv.
error: Unable to enable dependency based boot system.
And here's the obsolete script:
# dpkg-query -W -f='${Conffiles}\n' discover1
/etc/discover.conf 909aa5c740bbf1fa23d88be8d175e049
/etc/discover.conf-2.6 c486ab1e23b205b82006311ef34ba73d
/etc/init.d/discover fac8bbcb8d1d0c1f8dbd189e7687aba9 obsolete
# md5sum /etc/init.d/discover
fac8bbcb8d1d0c1f8dbd189e7687aba9 /etc/init.d/discover
The contents of /etc/init.d/discover:
#!/bin/sh
### BEGIN INIT INFO
# Provides: discover
# Required-Start:mountdevsubfs checkroot $local_fs
# Required-Stop:
# Default-Start: S
# Default-Stop:
### END INIT INFO
set -e
test -x /sbin/discover || exit 0
# Only work with discover version 1, not with version 2
case "`/sbin/discover --version`" in
"discover version 1"*)
break
;;
*)
exit 0
;;
esac
# file that determines the discover program's default behavior
CONFFILE=/etc/discover.conf
# list of modules for which to skip loading attempts
SKIPFILE=/etc/discover-autoskip.conf
# file that controls this init script's management of device symlinks
INITFILE=/etc/default/discover
# module we're loading, if it crashes then we know the culprit and can skip it
CRASHFILE=/lib/discover/crash
# cache, used more than once
KVERS=$(uname -r)
case "$1" in
start|restart) ;;
stop|reload|force-reload) exit 0 ;;
*) echo "Usage: $0 {start|restart}"; exit 1 ;;
esac
# Load init script parameters.
if [ -r $INITFILE ]; then
. $INITFILE
fi
if [ -f /lib/lsb/init-functions ]; then
. /lib/lsb/init-functions
else
log_begin_msg() { echo "$@"; }
log_success_msg() { echo "$@"; }
log_warning_msg() { echo "$@"; }
fi
. /etc/default/rcS
discover_uniq() {
local result=""
while read module; do
if ! ( echo "$result" | grep -q "$module " ); then
result="$result $module "
fi
done
echo "$result"
}
if [ -f $CRASHFILE ]
then
# The system crashed trying to load a module during the last boot
# cycle, so add an appropriate "skip" line to the skip file:
echo "skip $(<$CRASHFILE)" >> $SKIPFILE
rm -f $CRASHFILE
sync
fi
read_configuration()
{
filename="$1"
if [ ! -f "$1" ]; then return; fi
while read action arg argb; do
case "$action" in
enable | disable) DISCOVER_ARGS="$DISCOVER_ARGS --$action=$arg" ;;
skip) SKIPLIST="$SKIPLIST $arg"
;;
boot) TYPES="$TYPES $(echo $arg | sed 's/,/ /g')" ;;
map)
under=$(echo $arg | sed 's/-/_/g')
case "$KVERS" in
2.6.* | 2.5.*) argb=$(echo $argb | sed 's/-/_/g') ;;
esac
eval "map_$under=$argb"
;;
esac
done < "$filename"
}
read_configuration "$CONFFILE"
case "$KVERS" in
2.6.* | 2.5.*) read_configuration "$CONFFILE-2.6" ;;
esac
read_configuration "$SKIPFILE"
SKIPFILE_DIR="/etc/discover.d"
if [ -d "$SKIPFILE_DIR" ]; then
for part in $(run-parts --list "$SKIPFILE_DIR" 2>/dev/null || true); do
read_configuration "$part"
done
case "$KVERS" in
2.6.* | 2.5.*)
if [ -d "$SKIPFILE_DIR/2.6" ]; then
for part in $(r
Bug#494001: debian-installer: /etc/mtab must be a symlink to /proc/mounts with linux >= 2.6.26
On Thu, Aug 07, 2008 at 02:19:33PM +0200, Radim X. wrote: [please CC the submitter as well as the bug number, or else they don't get a reply!] > Are you sure that this won't break things elsewhere? Yes; the whole point of this change is to stop breaking things that are currently broken, including a whole plethora of bugs in mount(1). > Other packages > might use /etc/mtab with inotify to watch mount events (especially for > removable media). They would have to switch to a different method, > since /proc does not support inotify and udev doesn't help either. Do you have any examples of packages which use /etc/mtab in this way? I checked KDE 3.5.5 and it seems to be working fine. Note that inotify is very new, is Linux-specific, and all of the common desktop environments are portable to many different platforms and hence will detect changes using mechanisms other than inotify. IMO this is not a stopper for moving to a symlink. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#491376: I give up
After a good night sleep, I think I won't be updating my patches, or continue trying to justify why they're necessary. I decided I want to spend my time on more rewarding things. I explained everything in my previous mails. If you consider that there is indeed a problem, it should be trivial to adjust any of my patches to whatever your requirements are. I personally think it is a shame that when legacy MSDOS partitions are finally replaced after 20 years, we end up with something that is _less_ robust than what we had before. I also think it is a shame that coordination between the GRUB maintainer and the D-I team is basicaly inoperative. Anyway, my involvement ends here. The only thing I will do, is try to get this problem documented in the release notes, once it becomes clear that it won't be fixed. Have a nice day -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
flash-kernel_2.5_armel.changes ACCEPTED
Accepted: flash-kernel-installer_2.5_armel.udeb to pool/main/f/flash-kernel/flash-kernel-installer_2.5_armel.udeb flash-kernel_2.5.dsc to pool/main/f/flash-kernel/flash-kernel_2.5.dsc flash-kernel_2.5.tar.gz to pool/main/f/flash-kernel/flash-kernel_2.5.tar.gz flash-kernel_2.5_armel.deb to pool/main/f/flash-kernel/flash-kernel_2.5_armel.deb Override entries for your package: flash-kernel-installer_2.5_armel.udeb - standard debian-installer flash-kernel_2.5.dsc - source utils flash-kernel_2.5_armel.deb - optional utils Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of flash-kernel_2.5_armel.changes
flash-kernel_2.5_armel.changes uploaded successfully to localhost along with the files: flash-kernel_2.5.dsc flash-kernel_2.5.tar.gz flash-kernel_2.5_armel.deb flash-kernel-installer_2.5_armel.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Moving to 2.6.26
Thanks for Otavio for updating kernel-wedge to 2.6.26. I've now updated arm, armel and mipsel in SVN. I also changed mips according to the mipsel changes, so hopefully it will build but I cannot verify this at the moment. I made successful installations on armel/orion5x on a QNAP TS-409 and with mipsel/4kc-malta in QEMU. Are we ready to move to 2.6.26? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cdebconf-terminal_0.1_i386.changes is NEW
(new) cdebconf-gtk-terminal_0.1_i386.udeb extra debian-installer cdebconf gtk plugin dislaying a terminal cdebconf plugin to display a terminal inside the debian-installer graphical frontend. (new) cdebconf-terminal_0.1.dsc extra debian-installer (new) cdebconf-terminal_0.1.tar.gz extra debian-installer Changes: cdebconf-terminal (0.1) unstable; urgency=low . [ Jérémy Bobbio ] * Initial release. (Closes: #339855) Override entries for your package: Announcing to [EMAIL PROTECTED] Closing bugs: 339855 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
