Package: debootstrap
Version: 1.0.42
Severity: minor
$ sudo debootstrap --arch=armhf sid sid-armhf ftp://ftp.debian.org/debian/
fails with the errors
W: Failure trying to run: chroot /tmp/sid-armhf mount -t proc proc /proc
W: See /tmp/sid-armhf/debootstrap/debootstrap.log for details
because
Package: debian-installer
Severity: critical
The debian installer images are missing the isci.ko module.
This makes it impossible to install wheezy on any computer
that has its disks connected to an Intel C600 SAS controller
(standard on lots of motherboards).
NOTE: I'm not talking about iscsi
forgot to copy bts in previous reply.
-- Forwarded message --
From: Praveen A prav...@gmail.com
Date: 2012/11/14
Subject: Re: Bug#692540: installing with Malayalam gets stuck at
configuring apt - works fine with beta3 xfce-CD1
To: Holger Wansing li...@wansing-online.de
2012/11/14 Praveen A prav...@gmail.com:
2012/11/10 Holger Wansing li...@wansing-online.de:
So this bug is apparently not related to all beta3 images.
Praveen: probably you could try an installation with above image to
confirm this behaviour on your machine?
Will try it soon (currently on a
Your message dated Wed, 14 Nov 2012 16:32:45 +
with message-id e1tyftn-0001mq...@franck.debian.org
and subject line Bug#690978: fixed in debian-installer 20121114
has caused the Debian Bug report #690978,
regarding debian-installer: d-i unable to find disk storage on Hyper-V
to be marked
On Wed, 2012-11-14 at 14:08 +0100, Miquel van Smoorenburg wrote:
Package: debian-installer
Severity: critical
The debian installer images are missing the isci.ko module.
This makes it impossible to install wheezy on any computer
that has its disks connected to an Intel C600 SAS controller
Processing commands for cont...@bugs.debian.org:
reassign 693227 src:linux 3.2.32-1
Bug #693227 [debian-installer] missing driver for ISCI (Intel C600 SAS) (not
iscsi!)
Bug reassigned from package 'debian-installer' to 'src:linux'.
Ignoring request to alter found versions of bug #693227 to the
debian-installer_20121114_amd64.changes uploaded successfully to localhost
along with the files:
debian-installer_20121114.dsc
debian-installer_20121114.tar.gz
debian-installer_20121114_amd64.deb
debian-installer-images_20121114_amd64.tar.gz
Greetings,
Your Debian queue daemon
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 14 Nov 2012 14:56:37 +0100
Source: debian-installer
Binary: debian-installer
Architecture: source amd64
Version: 20121114
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot
2012/11/13 Praveen A prav...@gmail.com:
2012/11/10 Samuel Thibault sthiba...@debian.org:
You didn't specify which image you were using exactly, could you tell
us?
I was using debian-wheezy-DI-b3-amd64-CD-1.iso image
Using xfce i386 CD image from beta3 set worked fine - it warned of
invalid
Hi,
Michael Gilbert wrote (13 Nov 2012 00:09:04 GMT) :
On Mon, Nov 12, 2012 at 6:30 PM, Julien Cristau wrote:
Isn't this bug just a dupe of 684293, in which case it doesn't need
an os-prober change?
Possibly. I've never been able to reproduce the issue myself, so
deferring to Integeri:
I just encountered this hang while upgrading to console-setup 1.87 in testing.
setupcon was hanging while trying to configure tty3, which seemed very random,
so I checked tty3 and found that the scroll lock was on, which understandably
interferes with setupcon. Problem was solved one key press
package: debian-installer
version: 20120930+b1
/var/log/syslog shows the following message
kernel: psm0: PS/2 Mouse flags 0x100 irq 12 on atkbdc0
kernel: psm0: [GIANT-LOCKED]
kernel: model IntelliMouse Explorer, device ID 4
I can see a mouse pointer in the screen but I cannot move it.
It
Praveen A, le Wed 14 Nov 2012 22:18:07 +0530, a écrit :
2012/11/13 Praveen A prav...@gmail.com:
2012/11/10 Samuel Thibault sthiba...@debian.org:
You didn't specify which image you were using exactly, could you tell
us?
I was using debian-wheezy-DI-b3-amd64-CD-1.iso image
Using xfce
2012/11/15 Samuel Thibault sthiba...@debian.org:
Hum, I'm unable to reproduce the hang with CD-1 either.
I'm running it in kvm (from qemu-kvm 1.1.2+dfsg-2). Could you also try
with it, or tell us what virtualization tool you are using, exactly?
I'm using Virtual Box version in sid
2012/11/14 Praveen A prav...@gmail.com:
I tried xfce i386 image from beta3 set and I was able to install
without any issues. So it seems it affects only amd64 CD-1 and DVD-1
images. If someone can try amd64 xfce CD-1 image, we may be able to
track it to an amd64 issue.
even kfreebsd-amd64
I added kfreebsd disk disk as second disk on a linux vm.
I mounted the root partition with -t ufs -o ufstype=ufs2,ro options
and I can't see syslog in var/log. May be I can do a reinstall and
copy the syslog somewhere if required.
--
പ്രവീണ് അരിമ്പ്രത്തൊടിയില്
You have to keep reminding your
Philipp Kern pk...@debian.org (03/11/2012):
On Wed, Oct 03, 2012 at 05:44:59PM +0100, Martin Michlmayr wrote:
* Philipp Kern pk...@debian.org [2012-10-03 17:34]:
The preseed option name changed. That's on the to-do list for the next
beta/RC. Is use_dhcp in there? If not it might be that
Hi Søren,
please find Brian's reply below, you're probably not subscribed to
this list and probably didn't receive that mail:
Brian Potkin claremont...@gmail.com (10/11/2012):
On Sat 10 Nov 2012 at 15:24:19 +0100, Søren Karlsen wrote:
Can you see what im doing wrong and please help me with
Ben Hutchings b...@decadent.org.uk (14/11/2012):
Well those are useful for a nostalgia trip but I can't quite see how
they would help to solve the screen-blanking problem.
If you're using the graphical installer then you presumably need to
disable the X screen blanker somehow. That might
Hello,
david manyé dma...@gmail.com (06/11/2012):
i can't (net)install i386 wheezy on virtualbox. i get something in
catalan that can be translated to no kernel module found error
because of a possible kernel mismatch. some days ago it worked fine.
if i execute the command file on
Package: installation-reports
Severity: important
Tags: upstream
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
22 matches
Mail list logo
