Bug#766570: USB keyboard unresponsive after kernel load, but mouse works (Jessie Beta 2 amd64)

[Cyril Brulebois]

Control: reassign -1 src:linux 3.16.7-2
Control: retitle -1 please add hid/hid-chicony.ko to input-modules

Daniel F. Smith  (2014-10-24):
> Thanks KiBi,
> 
> I tried the keyboard (and USB stick) in both the USB2 and USB3 ports. No
> difference.
> 
> I did find an old blog post[1] describing the issue, and it suggests adding
> the following to initrd.img (/etc/initramfs-tools/modules):
>   usbcore
>   uhci_hcd
>   ehci_hcd
>   ehci_pci
>   usbhid
>   hid_generic
> 
> I don't currently have a Jessie system to run update-initramfs, but I'll can
> copy an initrd onto the USB stick if someone can provide one.
> 
> (And you're probably right about syslinux---the BIOS found two bootloaders:
> a text one and a graphical one with swooshes; and I didn't look closely!)
> 
> Daniel
> 
> [1]
> http://www.kasploosh.com/weblog/14000/14016-debian_jessie_usb_keyboard.html

In another mail, I got the following information:
| Chicony Electronics Co., Ltd 04f2:1125
|   
| On the Ubuntu 14.04 installer, it requires modules "hid_chicony" -> "hid".

Thanks, reassigning to the linux source package, and retitling accordingly.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#766570: USB keyboard unresponsive after kernel load, but mouse works (Jessie Beta 2 amd64)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 3.16.7-2
Bug #766570 [installation-reports] USB keyboard unresponsive after kernel load, 
but mouse works (Jessie Beta 2 amd64)
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #766570 to the same values 
previously set
Ignoring request to alter fixed versions of bug #766570 to the same values 
previously set
Bug #766570 [src:linux] USB keyboard unresponsive after kernel load, but mouse 
works (Jessie Beta 2 amd64)
Marked as found in versions linux/3.16.7-2.
> retitle -1 please add hid/hid-chicony.ko to input-modules
Bug #766570 [src:linux] USB keyboard unresponsive after kernel load, but mouse 
works (Jessie Beta 2 amd64)
Changed Bug title to 'please add hid/hid-chicony.ko to input-modules' from 'USB 
keyboard unresponsive after kernel load, but mouse works (Jessie Beta 2 amd64)'

-- 
766570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766570
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: 
https://lists.debian.org/handler.s.b766570.141681305113231.transcr...@bugs.debian.org

Re: Old-timer installer, task-sysvinit?

[Cyril Brulebois]

Lennart Sorensen  (2014-11-24):
> I tested it out with a fairly minimal install and it worked fine (well
> systemd-dbus is running, but that isn't init and hence not what I was
> testing).

Pretty sure it's either dbus(-{daemon,launch}) or systemd-udev.

> So I learned a bit about preseed, and am fairly happy now.  I still
> have systemd running on my system, it has some useful features, even
> if I think process 1 is way too large and have a hard time trusting
> anything from the maker of pulseaudio (which still causes me headaches
> all the time for some reason).

Please stop posting random rants on debian-boot@.

KiBi.


signature.asc
Description: Digital signature

Re: Old-timer installer, task-sysvinit?

[Lennart Sorensen]

On Sun, Nov 23, 2014 at 11:37:41PM +0100, Holger Levsen wrote:
> Debian has agreed via the tech-ctte and via the recent GR that installing 
> systemd by default on new installations *is* the *right thing*.
> 
> And jessie is frozen. Since ages ;-)
> 
> Please accept that. 
> 
> That said, useful patches for the release-notes and the installation-guide 
> are 
> still welcome I suppose - though I (personally) don't consider patches adding 
> documentation for legacy init systems (with known deficencies for decades) to 
> be very useful for future minded people. But I don't maintain said 
> documentation.
> 
> I would imagine patches documenting how to properly use systemd and make use 
> of its features and benefits are more a.) welcomed, b.) useful (for total 
> newbies and old farts alike) and c.) better use of time. YMMV. Also, 
> wiki.debian.org/systemd should have all the info (including how to avoid it 
> in 
> Jessie.)

I added a small section with details from the bug report link and a few
other bits I found explaining how to use preseed to replace systemd with
sysvinit to the wiki.

I tested it out with a fairly minimal install and it worked fine (well
systemd-dbus is running, but that isn't init and hence not what I was
testing).

So I learned a bit about preseed, and am fairly happy now.  I still
have systemd running on my system, it has some useful features, even
if I think process 1 is way too large and have a hard time trusting
anything from the maker of pulseaudio (which still causes me headaches
all the time for some reason).

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141124052913.gx24...@csclub.uwaterloo.ca

Bug#769107: debian-installer: grub-installer fails if more than 26 SCSI devices are present

[Ben Hutchings]

On Sun, 2014-11-23 at 16:23 +0100, Cyril Brulebois wrote:
> Michael Weiser  (2014-11-11):
> > >From 333151e5eed04e7ef292bb15109131e731092674 Mon Sep 17 00:00:00 2001
> > From: Michael Weiser 
> > Date: Tue, 11 Nov 2014 16:59:05 +0100
> > Subject: [PATCH] Allow for devices with multiple enumeration characters
> > 
> > Allow for installation of grub on devices such as /dev/sdaa or
> > /dev/xvdab.
> > ---
> >  grub-installer | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/grub-installer b/grub-installer
> > index 2b61fb6..cce326f 100755
> > --- a/grub-installer
> > +++ b/grub-installer
> > @@ -252,7 +252,7 @@ case $prefix in
> >  /dev/mapper)
> > disc_offered_devfs="$bootfs"
> > ;;
> > -
> > /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
> > +
> > /dev/[hsv]d[a-z0-9]|/dev/[sv]d[a-z][a-z]*|/dev/xvd[a-z]*|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
> > disc_offered_devfs="$prefix"
> > ;;
> >  *)
> 
> Hi Ben,
> 
> could you please double check the above patch? I'd like another pair
> of eyes on it before possibly merging it.

device_to_disk already knows how to do the mapping.  We have this
complicated wildcard here which doesn't match the regexp in
device_to_disk, only because no-one got round to clearing out the devfs
cruft which is the following '*' case.

So I propose this instead:

Subject: Remove devfs case for mapping partitions to whole disk names
 (Closes: #769107)

Rather than using an unmaintainable wildcard for non-devfs
partition device names, we should remove the obsolete devfs
case and use device_to_disk by default.

Also remove one of the many pointless uses of mapdevfs.
---
 grub-installer | 10 +++---
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/grub-installer b/grub-installer
index bff4174..9059638 100755
--- a/grub-installer
+++ b/grub-installer
@@ -247,19 +247,15 @@ prefix=$(device_to_disk "$bootfs")
 
 case $prefix in
 /dev/md)
-   disc_offered_devfs="$bootfs"
+   disc_offered="$bootfs"
;;
 /dev/mapper)
-   disc_offered_devfs="$bootfs"
-   ;;
-
/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
-   disc_offered_devfs="$prefix"
+   disc_offered="$bootfs"
;;
 *)
-   disc_offered_devfs=$(echo "$bootfs_nodevfs" | sed 
"s:\(.*\)/.*:\1/disc:")
+   disc_offered="$prefix"
;;
 esac
-disc_offered=$(mapdevfs "$disc_offered_devfs")
 
 # Identify partition table of the disk containing our boot partition
 bootfslabel=$(partmap $disc_offered || echo unknown)
--- END ---

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer


signature.asc
Description: This is a digitally signed message part

Re: Old-timer installer, task-sysvinit?

[Holger Levsen]

Hi Phil,

On Sonntag, 23. November 2014, Philip Hands wrote:
> Then again, I've used d-i as a presentation tool[1] -- I'm clearly
> deranged.
> [1] http://hands.com/d-i/lenny/classes/ukuug06/early_script

nice! I was looking for that pointer since (iirc) KiBi reminded me of it's
existance at the recent mini-debconf...

And so I just did this commit to "add three new jobs:
(sid_daily|jessie|wheezy)_presentation - Thanks to Phil Hands and Frans Pop"

http://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/commit/job-cfg/g-i-installation.yaml?id=f63b04ac77fac16d4c223f72eaa4465159eb68de

For the actual jobs see for example: 

https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_jessie_presentation/

ToDo:
- drive the presentation (do keyboard input as needed)
- use preseeding files on jenkins.d.n and not hands.com :-)


thanks,
Holger


signature.asc
Description: This is a digitally signed message part.

Re: Old-timer installer, task-sysvinit?

[Lennart Sorensen]

On Mon, Nov 24, 2014 at 12:28:32AM +0100, Holger Levsen wrote:
> the last time this was mentioned in this very thread was less than 12h ago.

Oh the link to a comment in a bug report happens to contain something
useful.

I will agree that it was indirectly mentioned then.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123233753.gw24...@csclub.uwaterloo.ca

Re: Old-timer installer, task-sysvinit?

[Holger Levsen]

On Montag, 24. November 2014, Lennart Sorensen wrote:
> So far preseed has been mentioned, although without
> any details on exactly what would be needed.

the last time this was mentioned in this very thread was less than 12h ago.

*plonk*


signature.asc
Description: This is a digitally signed message part.

Re: Old-timer installer, task-sysvinit?

[Lennart Sorensen]

On Sun, Nov 23, 2014 at 11:37:41PM +0100, Holger Levsen wrote:
> Debian has agreed via the tech-ctte and via the recent GR that installing 
> systemd by default on new installations *is* the *right thing*.
>
> And jessie is frozen. Since ages ;-)

A few weeks is hardly ages in the Debian release cycle timeframe.

> Please accept that. 
> 
> That said, useful patches for the release-notes and the installation-guide 
> are 
> still welcome I suppose - though I (personally) don't consider patches adding 
> documentation for legacy init systems (with known deficencies for decades) to 
> be very useful for future minded people. But I don't maintain said 
> documentation.

They certainly have issues, but so does systemd and at least for some
people the problems are by design, so this argument isn't going to
go away.  Clearly there are people that want to be able to avoid systemd,
and currently it is very hard to figure out how to do that.

The fact the old init systems have flaws is not the question.  The
tech-ctte and GR have not said systemd is the only supported thing, so
in that case, do tell the users that for some reason don't want systemd
how to avoid it.  So far preseed has been mentioned, although without
any details on exactly what would be needed.  Clearly someone must know
given claims are made about it being doable.

> I would imagine patches documenting how to properly use systemd and make use 
> of its features and benefits are more a.) welcomed, b.) useful (for total 
> newbies and old farts alike) and c.) better use of time. YMMV. Also, 
> wiki.debian.org/systemd should have all the info (including how to avoid it 
> in 
> Jessie.)

That wiki page is useless.  It only tells you have to start using systemd,
not how to get rid of it.  I have read it multiple times today while
reading the emails in this thread.  Seems everything says to go there
for info, except there is none to be found there.

Systemd certainly does have some nice features, but I also understand
why some people want nothing to do with it, and the information on how
to avoid it is terrible at the moment.  That is highly disappointing.
I would update the wiki if I could figure out what to put there, but so
far I haven't had any luck with that.

> So I do think this is out of scope for discussion on this list right now.
> 
> (If you have code patches for stretch (=jessie+1), submit them to the bts and 
> start a discussion after the release.)

That's years away.  That is ages on the other hand.  I honestly suspect
by then the hurd and bsd ports will be dead and a lot of people will
have moved elsewhere.  Of course the lack of anywhere obviously better
to move on to makes that difficult.

Personally I don't care about BSD or hurd, but clearly some people do.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123231800.gv24...@csclub.uwaterloo.ca

Re: Old-timer installer, task-sysvinit?

[Brian Potkin]

On Sun 23 Nov 2014 at 22:43:53 +, Brian Potkin wrote:

> I think needs fixing for this to work.
 ^
   #668001   


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/23112014224510.026b22256...@desktop.copernicus.demon.co.uk

Re: Old-timer installer, task-sysvinit?

[Brian Potkin]

On Sun 23 Nov 2014 at 20:36:42 +, Philip Hands wrote:

> If you want a way to do a non-shell based preseed, you _may_ be able to
> get away with some combination of these:
> 
> =-=-=-=-
> Template: base-installer/includes
> Type: string
> Description: for internal use; can be preseeded
>  Packages to be included in base installation

I've used this and it works. There do not appear to be any drawbacks and
it seems a good method.
 
> Template: base-installer/excludes
> Type: string
> Description: for internal use; can be preseeded
>  Packages to be excluded in base installation

I think needs fixing for this to work.
 
> Template: pkgsel/include
> Type: string
> Description: for internal use; can be preseeded
>  Comma/space-separated list of extra packages to install
> =-=-=-=-

Tried it once and it worked. I prefer base-installer/includes or a
late_command.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/23112014223722.e2b5977f7...@desktop.copernicus.demon.co.uk

Re: Old-timer installer, task-sysvinit?

[Holger Levsen]

On Sonntag, 23. November 2014, Lennart Sorensen wrote:
> Perhaps it is time someone who actually knows how to make it do the
> right thing to document it officially.

Debian has agreed via the tech-ctte and via the recent GR that installing 
systemd by default on new installations *is* the *right thing*.

And jessie is frozen. Since ages ;-)

Please accept that. 

That said, useful patches for the release-notes and the installation-guide are 
still welcome I suppose - though I (personally) don't consider patches adding 
documentation for legacy init systems (with known deficencies for decades) to 
be very useful for future minded people. But I don't maintain said 
documentation.

I would imagine patches documenting how to properly use systemd and make use 
of its features and benefits are more a.) welcomed, b.) useful (for total 
newbies and old farts alike) and c.) better use of time. YMMV. Also, 
wiki.debian.org/systemd should have all the info (including how to avoid it in 
Jessie.)

So I do think this is out of scope for discussion on this list right now.

(If you have code patches for stretch (=jessie+1), submit them to the bts and 
start a discussion after the release.)


signature.asc
Description: This is a digitally signed message part.

Re: Old-timer installer, task-sysvinit?

[Lennart Sorensen]

On Sun, Nov 23, 2014 at 08:36:42PM +, Philip Hands wrote:
> Ah, oh well then.
> 
> If one starts preseeding many of the internal bits of d-i, one can do
> pretty much anything you like (and loads of things you don't like ;-) ).
> 
> If you're worried about recomending such things, I'd say that the way to
> go is with a standard install, and then using some nice package manager
> interface to change the init system.
> 
> If you want a way to do a non-shell based preseed, you _may_ be able to
> get away with some combination of these:
> 
> =-=-=-=-
> Template: base-installer/includes
> Type: string
> Description: for internal use; can be preseeded
>  Packages to be included in base installation
> 
> Template: base-installer/excludes
> Type: string
> Description: for internal use; can be preseeded
>  Packages to be excluded in base installation
> 
> Template: pkgsel/include
> Type: string
> Description: for internal use; can be preseeded
>  Comma/space-separated list of extra packages to install
> =-=-=-=-
> 
> Although you'd need to test that (I seem to remember them not doing
> quite what I'd expected when I tried using them a long time ago, at
> least when it came to excludes, so I've not touched them since).
> 
> TBH, given that one of the apparent selling features of sysvinit is how
> nice it is to be able to do whatever one likes with a few lines of
> shell, it strikes me as a bit odd to be shy of using a single shell
> command to get what one wants.  Who is the target audience here?

I think a big problem is that it isn't clear what command is necessary
to replace systemd with something else.  I just tried searching for
isntructions on installing jessie without systemd, figuring it must
be documented somewhere.  Well if it is, google is no help.  I found
various interesting ideas, some clearly not very good.  I did find
stuff on how to upgrade from wheezy to jessie and avoid systemd, but
that hardly takes care of new installations.

I know I have only used Debian since version 2.0, so I have never used
preseed, nor even seen a preseed file.  I doubt I am unusual.
The installer has always asked the right questions and done the right
thing.

Perhaps it is time someone who actually knows how to make it do the
right thing to document it officially.

Maybe rather than telling people it is too late to do something, throw
away the freeze, fix things, then freeze again.  What's the rush for a
new release anyhow?  Clearly a lot of people are not happy with the
current state of things.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123221706.gu24...@csclub.uwaterloo.ca

Bug#735160: installation-report: installation successfull - no encrypted disk possible

[Holger Levsen]

control: tags -1 + moreinfo

Hi Stephan,

thanks for your installation-report - and sorry for the late reply...

On Montag, 13. Januar 2014, Stephan wrote:
> Boot method: usb-stick+netinst
> Image version: netinst, 2014-01-10
> Date: 2013-01-10

so early jessie...

[..] 
> Detect Hard Drives:
> Laptop uses an "Intel Rapid Storage Technology" Raid. The installer did
> not find the disks at first, had to manually destroy the lvm to be able
> to detect hard drives.

ok, I have no comment about this one, maybe someone else has...

> Partition Hard Drives:
> Encrypted filesystem not possible with graphical installer.

what do you mean "was not possible"?


signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#735160: installation-report: installation successfull - no encrypted disk possible

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #735160 [installation-reports] installation-report: installation 
successfull - no encrypted disk possible
Added tag(s) moreinfo.

-- 
735160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735160
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: 
https://lists.debian.org/handler.s.b735160.141677977032654.transcr...@bugs.debian.org

Processed: making things clearer

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 646961 udhcpc: GNU/kFreeBSD support (not used by d-i/kfreebsd)
Bug #646961 [udhcpc] GNU/kFreeBSD support
Changed Bug title to 'udhcpc: GNU/kFreeBSD support (not used by d-i/kfreebsd)' 
from 'GNU/kFreeBSD support'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
646961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646961
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: 
https://lists.debian.org/handler.s.c.141677950730812.transcr...@bugs.debian.org

Re: UltraHD installation: mouse not working in graphical install

[Holger Levsen]

On Sonntag, 23. November 2014, Holger Levsen wrote:
> > good size.  After choosing graphical install, the screen goes indeed
> > graphical, but the fonts are as small as the newt frontend, i.e. very
> > hard to read!!
> ah! I didn't knew g-i c+would do this today! :)

(as just said in another mail I thought it would still default to 800x600 or 
maybe 1024x767... :)


signature.asc
Description: This is a digitally signed message part.

Re: UltraHD installation: mouse not working in graphical install

[Holger Levsen]

Hi Eugen,

On Freitag, 21. November 2014, Eugen Dedu wrote:
> I tested also with graphical install.  The very first screen, presenting
> Install, Graphical install etc. is shown graphically and at visually
> good size.  After choosing graphical install, the screen goes indeed
> graphical, but the fonts are as small as the newt frontend, i.e. very
> hard to read!!

ah! I didn't knew g-i c+would do this today! :)
 
> This is a somehow important problem, since nothing can be done to
> workaround it.  The installer is also the first program a new user sees
> when installing linux.

please file a proper bug report, eg using

reportbug installation-reports

I've looked in 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-boot%40lists.debian.org
for relevant bugs and the only one I could find is

595696 [w|  |  ] [console-setup] console-setup should be able to select the 
font size according to SCREEN_WIDTH/HEIGHT, rasterizing one if needed

so please do file a new one, displays with reasonable resolution have become a
lot more common! ;-)


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#766398: marked as done (installation-reports: Graphical Install Successful)

[Holger Levsen]

control: reopen -1
control: retitle -1 "synaptics touchpad not working in graphical installer"

On Sonntag, 23. November 2014, Cyril Brulebois wrote:
> > The synaptics touchpad on the system was non operational in the graphical
> > installer.  Proceeded by plugging in USB mouse.
> Looks like a topic to investigate…

hm, I'm surprised (but glad) it should work (*), from my memory (and seemingly 
confirmed from https://wiki.debian.org/SynapticsTouchpad) this is quite common 
(and then usually fixed by newer kernels) so that I considered it closeable. 
Thanks for a second look!

Matthew, what Lenovo modell is that?

(*) I never use the touchpad myself, just the Lenovo mouse pointer, so maybe 
my memory has made me believe the touchpad is still not supported similarily 
like I thought g-i would only do 800x600...)


signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#766398: marked as done (installation-reports: Graphical Install Successful)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #766398 {Done: Holger Levsen } 
[installation-reports] installation-reports: Graphical Install Successful
Bug reopened
Ignoring request to alter fixed versions of bug #766398 to the same values 
previously set
> retitle -1 "synaptics touchpad not working in graphical installer"
Bug #766398 [installation-reports] installation-reports: Graphical Install 
Successful
Changed Bug title to '"synaptics touchpad not working in graphical installer"' 
from 'installation-reports: Graphical Install Successful'

-- 
766398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766398
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: 
https://lists.debian.org/handler.s.b766398.141677826323036.transcr...@bugs.debian.org

Bug#766398: marked as done (installation-reports: Graphical Install Successful)

[Cyril Brulebois]

Holger Levsen  (2014-11-23):
> "Even though" (rather because..) I'm batch closing them, I have read them all 
> now and made sure reported (minor) issues have been reported / documented 
> elsewhere already.

See below.


Within the original bug report:
> Comments/Problems:
> 
> The synaptics touchpad on the system was non operational in the graphical 
> installer.  Proceeded by plugging in USB mouse.

Looks like a topic to investigate…

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#766398: marked as done (installation-reports: Graphical Install Successful)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #766398,
regarding installation-reports: Graphical Install Successful
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.)


-- 
766398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: minor

Dear Maintainer,

*** Reporter, 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 of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: USB
Image version: 
http://cdimage.debian.org/cdimage/jessie_di_beta_2/amd64/iso-cd/debian-jessie-DI-b2-amd64-netinst.iso
Date: 

Machine: Lenovo G560
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:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The synaptics touchpad on the system was non operational in the graphical 
installer.  Proceeded by plugging in USB mouse.




-- 

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="8 (jessie) - installer build 20141002"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux lenovoG560 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM 
Controller [8086:0044] (rev 02)
lspci -knn: Subsystem: Lenovo Device [17aa:391e]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core 
Processor Integrated Graphics Controller [8086:0046] (rev 02)
lspci -knn: Subsystem: Lenovo Device [17aa:3920]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 5 
Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
lspci -knn: Subsystem: Lenovo Device [17aa:38a5]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 
Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
lspci -knn: Subsystem: Lenovo Device [17aa:38aa]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series 
Chipset High Definition Audio [8086:3b56] (rev 05)
lspci -knn: Subsystem: Lenovo Device [17aa:38af]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 2 [8086:3b44] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 3 [8086:3b46] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 
Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
lspci -knn: Subsystem: Lenovo Device [17aa:38b8]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI 
Bridge [8086:2448] (rev a5)
lspci -knn: 0

Re: tasksel desktop preseed issues

[Thorsten Glaser]

Steven Chamberlain dixit:

>* standard task still seems to bring in a huge amount of dependencies
>via gnupg2 > gnupg-agent > pinentry-gtk2 > xserver-*

Break this by installing pinentry-curses before anything that
brings in gnupg-agent (same apt-get command line works).


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/pine.bsm.4.64l.1411232056250.30...@herc.mirbsd.org

Bug#763983: marked as done (Installation of Debian 8 successfully on AMD APU Desktop PC)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #763983,
regarding Installation of Debian 8 successfully on AMD APU Desktop PC
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.)


-- 
763983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with installer from jessie
Date: 2014-10-04

Machine: Self-made desktop PC
Processor: AMD A6-3650 APU with Radeon(tm) HD Graphics
Memory: 4GB RAM
Partitions:

> DateisystemTyp  1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
> /dev/sda5  ext4  14286320 6360064   7177508   47% /
> udev   devtmpfs 10240   0 102400% /dev
> tmpfs  tmpfs   707968 5887073801% /run
> tmpfs  tmpfs  1769912  12   17699001% /dev/shm
> tmpfs  tmpfs  1769912   0   17699120% /sys/fs/cgroup
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs   102400  121023881% /run/user
> /dev/sda7  ext4 247401544  305740 2345054681% /home

Output of lspci -knn (or lspci -nn):

> 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 12h 
> Processor Root Complex [1022:1705]
>   Subsystem: Advanced Micro Devices, Inc. [AMD] Family 12h Processor Root 
> Complex [1022:1705]
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
> [AMD/ATI] BeaverCreek [Radeon HD 6530D] [1002:964a]
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
>   Kernel driver in use: radeon
> 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 12h 
> Processor Root Port [1022:1709]
>   Kernel driver in use: pcieport
> 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: xhci_hcd
> 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> XHCI Controller [1022:7812] (rev 03)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: xhci_hcd
> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA 
> Controller [AHCI mode] [1022:7801] (rev 40)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:b002]
>   Kernel driver in use: ahci
> 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: ohci-pci
> 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: ehci-pci
> 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7807] (rev 11)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: ohci-pci
> 00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> EHCI Controller [1022:7808] (rev 11)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
>   Kernel driver in use: ehci-pci
> 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
> [1022:780b] (rev 13)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:4385]
>   Kernel driver in use: piix4_smbus
> 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD] FCH IDE 
> Controller [1022:780c]
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:5002]
>   Kernel driver in use: pata_atiixp
> 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
> Controller [1022:780d] (rev 01)
>   Subsystem: Gigabyte Technology Co., Ltd Device [1458:a132]
>   Kernel driver in use: snd_hda_intel
> 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge 
> [1022:780e] (rev 11)
>   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:439d]
> 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge 
> [1022:780f] (rev 40)
> 00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB 
> OHCI Controller [1022:7809] (rev 11)
>   Subsystem: 

Bug#763289: marked as done (Debian testing dayly build (2014-09-28) successfully installed)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #763289,
regarding Debian testing dayly build (2014-09-28) successfully installed
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.)


-- 
763289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB memory stick
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2014-09-28 12:15

Machine: Notebook Samsung N150 Plus

Processor:

Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):2
On-line CPU(s) list:   0,1
Thread(s) per core:2
Core(s) per socket:1
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 28
Stepping:  10
CPU MHz:   1000.000
BogoMIPS:  3324.87
L1d cache: 24K
L1i cache: 32K
L2 cache:  512K
NUMA node0 CPU(s): 0,1

Memory:

MemTotal:1013856 kB
MemFree:   79724 kB
MemAvailable: 292352 kB
Buffers:   17240 kB
Cached:   282264 kB
SwapCached: 6960 kB
Active:   360224 kB
Inactive: 353144 kB
Active(anon): 248388 kB
Inactive(anon):   241540 kB
Active(file): 111836 kB
Inactive(file):   111604 kB
Unevictable:   0 kB
Mlocked:   0 kB
SwapTotal:   2073596 kB
SwapFree:2009744 kB
Dirty:52 kB
Writeback: 0 kB
AnonPages:409556 kB
Mapped:86996 kB
Shmem: 75964 kB
Slab: 178728 kB
SReclaimable: 158124 kB
SUnreclaim:20604 kB
KernelStack:5056 kB
PageTables:19484 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit: 2580524 kB
Committed_AS:2470572 kB
VmallocTotal:   34359738367 kB
VmallocUsed:  288612 kB
VmallocChunk:   34359445148 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
DirectMap4k:   48832 kB
DirectMap2M:  989184 kB

Partitions:

DateisystemTyp  1K-Blöcke   Benutzt Verfügbar Verw% Eingehängt
auf
/dev/sda1  ext4 238191232 100381228 125687484   45% /
udev   devtmpfs 10240 0 102400% /dev
tmpfs  tmpfs   202772  49121978603% /run
tmpfs  tmpfs   506928   1445067841% /dev/shm
tmpfs  tmpfs   506928 0506928
0% /sys/fs/cgroup
tmpfs  tmpfs   102400281023721% /run/user
tmpfs  tmpfs 5120 4  51161% /run/lock

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom
Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Kernel driver in use: i915
00:02.1 Display controller [0380]: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High
Definition Audio Controller [8086:27d8] (rev 02)
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 1 [8086:27d0] (rev 02)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 2 [8086:27d2] (rev 02)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 3 [8086:27d4] (rev 02)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI
Express Port 4 [8086:27d6] (rev 02)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corp

Bug#756821: marked as done (installation-reports: Successfull system install)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #756821,
regarding installation-reports: Successfull system install
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.)


-- 
756821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
Tags: d-i

-- Package-specific info:

Boot method: DVD
Image version: Debian GNU/Linux 7.6.0 amd64 20140712-14:11 →
http://cdimage.debian.org/debian-cd/7.6.0/amd64/bt-dvd/
Date: 2014-08-01

Machine: Toshiba Satellite L455-SP2903R
Partitions: /boot - / - /home


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]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[O]

Comments/Problems:

After several tries, GRUB was not installed. However, LILO could be installed.


--

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux redstar 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series
Chipset Memory Controller Hub [8086:2a40] (rev 07)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff01]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 4
Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff01]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #4 [8086:2937] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #5 [8086:2938] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #6 [8086:2939] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9
Family) USB2 EHCI Controller #2 [8086:293c] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family)
HD Audio Controller [8086:293e] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family)
PCI Express Port 1 [8086:2940] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family)
PCI Express Port 3 [8086:2944] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family)
PCI Express Port 4 [8086:2946] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family)
PCI Express Port 6 [8086:294a] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9
Family) USB UHCI Controller #1 [8086:2934] (rev 03)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff00]
lspci -knn: Kernel driver in

Bug#756215: marked as done (Testing successfully installed on Acer Aspire One A110L to USB flash drive)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #756215,
regarding Testing successfully installed on Acer Aspire One A110L to USB flash 
drive
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.)


-- 
756215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: installation-reports
Severity: minor
Tags: d-i

Dear Maintainer,

I copied netinstall iso to an USB flash drive, then used the free space 
of that USB flash drive for my installation.

Without any problems. Great!

Boot method: USB flash drive
Image version: debian-testing-i386-netinst.iso
Date: 22 July 2014

Machine: Acer Aspire One A110L
Intel® Atom™ Prozessor N270 (1.60 GHz, 533 MHz FSB, 512 KB L2 Cache)
NAND Flash Modul: 8GB (sda)

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]

Partitions:
DateisystemTyp  1K-blocks Benutzt Verfügbar Verw% Eingehängt auf
/dev/sdb2  ext4   6544312 3231508   2957324   53% /
udev   devtmpfs 10240   0 102400% /dev
tmpfs  tmpfs999484868 950805% /run
tmpfs  tmpfs   249860   02498600% /dev/shm
tmpfs  tmpfs   249860   02498600% /sys/fs/cgroup
tmpfs  tmpfs   102400   01024000% /run/user
tmpfs  tmpfs 5120   4  51161% /run/lock

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20140721-00:06"
X_INSTALLATION_MEDIUM=cdrom

==
Hardware-Summary
==
uname -a: Linux (none) 3.14-1-486 #1 Debian 3.14.12-1 (2014-07-11) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE 
Express Memory Controller Hub [8086:27ac] (rev 03)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 
03)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller 
[8086:27a6] (rev 03)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 
Family High Definition Audio Controller [8086:27d8] (rev 02)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 
Family PCI Express Port 1 [8086:27d0] (rev 02)

lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 
Family PCI Express Port 2 [8086:27d2] (rev 02)

lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 
Family PCI Express Port 3 [8086:27d4] (rev 02)

lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 
Family PCI Express Port 4 [8086:27d6] (rev 02)

lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 
Family USB UHCI Controller #1 [8086:27c8] (rev 02)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 
Family USB UHCI Controller #2 [8086:27c9] (rev 02)

lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 
Family USB UHCI Controller #3 [8086:27ca] (rev 02)

lspci -knn:

Bug#758248: marked as done (Installation of Jessie Beta1 was successfully on Acer Aspire One 532h)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #758248,
regarding Installation of Jessie Beta1 was successfully on Acer Aspire One 532h
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.)


-- 
758248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Stick
Image version: Self-made ISO image with Debian Installer Jessie Beta 1
Date: 2014-08-15

Machine: Netbook Acer Aspire One 532h
Processor: Intel(R) Atom(TM) CPU N450   @ 1.66GHz
Memory: 1GB
Partitions:

> DateisystemTyp  1K-blocks Benutzt Verfügbar Verw% Eingehängt auf
> /dev/sda1  btrfs 19530752 6052876  12988132   32% /
> udev   devtmpfs 10240   0 102400% /dev
> tmpfs  tmpfs   20276846241981443% /run
> tmpfs  tmpfs   506912   85069041% /dev/shm
> tmpfs  tmpfs   506912   05069120% /sys/fs/cgroup
> tmpfs  tmpfs 5120   4  51161% /run/lock
> tmpfs  tmpfs   102400   81023921% /run/user
> /dev/sda6  btrfs 41036800 1116972  396525643% /home

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: agpgart-intel
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: i915
> 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
> 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
> Definition Audio Controller [8086:27d8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 1 [8086:27d0] (rev 02)
>   Kernel driver in use: pcieport
> 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 2 [8086:27d2] (rev 02)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #1 [8086:27c8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #2 [8086:27c9] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #3 [8086:27ca] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #4 [8086:27cb] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI 
> Controller [8086:27cc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: ehci-pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev e2)
> 00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller 
> [8086:27bc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family SATA 
> Controller [AHCI mode] [8086:27c1] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller 
> [8086:27da] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: i801_smbus
> 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8132 Fast Ethernet 
> [1969:1062] (rev c0)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: atl1c
> 02:00.0 Network controller [0280]: Qualcomm Atheros 

Bug#756182: marked as done (Installation successfully on Acer Aspire One 532h Netbook)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #756182,
regarding Installation successfully on Acer Aspire One 532h Netbook
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.)


-- 
756182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB Stick
Image version: Self-made ISO image with current installer from Jessie
Date: 2014-07-26

Machine: Acer Aspire One Netbook 532h
Processor: Intel Atom CPU N450 @ 1.66GHz
Memory: 1GB
Partitions: 

> DateisystemTyp  1K-blocks Benutzt Verfügbar Verw% Eingehängt auf
> /dev/sda1  btrfs 19530752 5538008  13696696   29% /
> udev   devtmpfs 10240   0 102400% /dev
> tmpfs  tmpfs   20279646881981083% /run
> tmpfs  tmpfs   506984   431564638289% /dev/shm
> tmpfs  tmpfs   506984   05069840% /sys/fs/cgroup
> tmpfs  tmpfs 5120   4  51161% /run/lock
> /dev/sda6  btrfs 41036800  810360  399594482% /home
> tmpfs  tmpfs   102400   41023961% /run/user

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: agpgart-intel
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: i915
> 00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
> 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
> Definition Audio Controller [8086:27d8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 1 [8086:27d0] (rev 02)
>   Kernel driver in use: pcieport
> 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 2 [8086:27d2] (rev 02)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #1 [8086:27c8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #2 [8086:27c9] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #3 [8086:27ca] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #4 [8086:27cb] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI 
> Controller [8086:27cc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: ehci-pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev e2)
> 00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller 
> [8086:27bc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation NM10/ICH7 Family SATA 
> Controller [AHCI mode] [8086:27c1] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller 
> [8086:27da] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: i801_smbus
> 01:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8132 Fast Ethernet 
> [1969:1062] (rev c0)
>   Subsystem: Acer Incorporated [ALI] Device [1025:0349]
>   Kernel driver in use: atl1c
> 02:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Netwo

Bug#762778: marked as done (installation-reports: Successful installation on Dell Optiplex 3020)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #762778,
regarding installation-reports: Successful installation on Dell Optiplex 3020
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.)


-- 
762778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: wishlist

Dear Maintainer,

The installation was fine. However, there were two issues. I have
described them below, in the Comments/Problems section.

Thank you.

Kumar

-- Package-specific info:

Boot method: network
Image version: netboot 20140802 from 
ftp://ftp.iitb.ac.in/distributions/debian/debian-os/dists/sid/main/installer-amd64/20140802/images/netboot/debian-installer/amd64/
Date: Wed Sep 24 15:10:41 IST 2014

Machine: Dell Optiplex 3020
Partitions:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x97b011c2

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *2048 3905535 1951744   83  Linux
/dev/sda2 3907582   976771071   4864317455  Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 390758419726335 7909376   82  Linux swap / Solaris
/dev/sda619728384   976771071   478521344   8e  Linux LVM



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]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

1. The installer would initially panic with the following:

Initramfs unpacking failed: junk in compressed archive
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block{x,y}

   The suggestion at this wiki page (passing the initrd=initrd.gz and
   mem=) helped me work around this issue:
  https://wiki.debian.org/InstallingDebianOn/Dell/XPS630i/wheezy#line-46

2. #244436 caused me much trouble, since we have an FTP only mirror
   internally, and a proxy to access outside. So, I had to work around
   by adding the proxy server to access an outside mirror.

-- 

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="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux bluemoon 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Dell Device [1028:0612]
lspci -knn: Kernel driver in use: ehci_hc

Bug#742951: marked as done (installation-reports: Wheezy successfully installed - thanx :-))

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #742951,
regarding installation-reports: Wheezy successfully installed - thanx :-)
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.)


-- 
742951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal

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 of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- Package-specific info:

Boot method: USB
Image version: Debian 7.3.0 amd64
Date: March 2014

Machine: Custom
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [0]
Detect network card:[0]
Configure network:  [0]
Detect CD:  [0]
Load installer modules: [0]
Clock/timezone setup:   [0]
User/password setup:[0]
Detect hard drives: [0]
Partition hard drives:  [0]
Install base system:[0]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

Encountered some problems regarding the wireless card which I could solve using 
ndiswrapper und internet research.


-- 

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="7 (wheezy) - installer build 20130613+deb7u1+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux pupsi 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI 
RS480 Host Bridge [1002:5950] (rev 01)
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RS480 Host 
Bridge [1002:5950]
lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI 
RS480 PCI-X Root Port [1002:5a34]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:12.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee 
ATI SB600 Non-Raid-5 SATA [1002:4380]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB (OHCI0) [1002:4387]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
(OHCI0) [1002:4387]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB (OHCI1) [1002:4388]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
(OHCI1) [1002:4388]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB (OHCI2) [1002:4389]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
(OHCI2) [1002:4389]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.3 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB (OHCI3) [1002:438a]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
(OHCI3) [1002:438a]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.4 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB (OHCI4) [1002:438b]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
(OHCI4) [1002:438b]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:13.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB600 USB Controller (EHCI) [1002:4386]
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI SB600 USB 
Controller (EHCI) [1002:4386]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 
SMBus Controller [1002:4385] (rev 13)
lspc

Bug#739818: marked as done (Installation of testing was successfully on Acer Aspire One D150)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #739818,
regarding Installation of testing was successfully on Acer Aspire One D150
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.)


-- 
739818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: USB-Stick contains self-made ISO image
Image version: Self-made ISO image with current installer from sid
Date: 2014-02-22

Machine: Acer Aspire One D150
Processor: Intel Atom N270 @ 1,6GHz
Memory: 1GB
Partitions:

> DateisystemTyp  1K-blocks Benutzt Verfügbar Verw% Eingehängt auf
> /dev/sda1  ext4  19091584 5418840  12679876   30% /
> udev   devtmpfs 10240   0 102400% /dev
> tmpfs  tmpfs   102284 2921019921% /run
> tmpfs  tmpfs 5120   0  51200% /run/lock
> tmpfs  tmpfs   594900   05949000% /run/shm
> /dev/sda6  ext4 132557184  111652 1256889241% /home
> none   tmpfs4   0 40% /sys/fs/cgroup

Output of lspci -knn:

> 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory 
> Controller Hub [8086:27ac] (rev 03)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: agpgart-intel
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE 
> Express Integrated Graphics Controller [8086:27ae] (rev 03)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: i915
> 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
> 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
> 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High 
> Definition Audio Controller [8086:27d8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: snd_hda_intel
> 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 1 [8086:27d0] (rev 02)
>   Kernel driver in use: pcieport
> 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 2 [8086:27d2] (rev 02)
>   Kernel driver in use: pcieport
> 00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express 
> Port 3 [8086:27d4] (rev 02)
>   Kernel driver in use: pcieport
> 00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #1 [8086:27c8] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: uhci_hcd
> 00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #2 [8086:27c9] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: uhci_hcd
> 00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #3 [8086:27ca] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: uhci_hcd
> 00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
> Controller #4 [8086:27cb] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: uhci_hcd
> 00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI 
> Controller [8086:27cc] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: ehci-pci
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
> [8086:2448] (rev e2)
> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface 
> Bridge [8086:27b9] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: lpc_ich
> 00:1f.2 SATA controller [0106]: Intel Corporation 82801GBM/GHM (ICH7-M 
> Family) SATA Controller [AHCI mode] [8086:27c5] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: ahci
> 00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller 
> [8086:27da] (rev 02)
>   Subsystem: Acer Incorporated [ALI] Device [1025:019c]
>   Kernel driver in use: i801_smbus
> 01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g 
> LP-PHY [14e4:4315] (rev 01)
>   Subsystem: Foxconn In

Bug#740866: marked as done (installation-reports: successful installation of Debian jessie)

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 21:52:03 +0100
with message-id <201411232152.12160.hol...@layer-acht.org>
and subject line thanks for the successful installation-report
has caused the Debian Bug report #740866,
regarding installation-reports: successful installation of Debian jessie
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.)


-- 
740866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: minor
Tags: d-i

Debian jessie installed without any problems.
(Netinstall of Debian wheezy wouldn't work because ethernet wasn't recognized.)



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
 04/02/2014
Date: 

Machine: Lenovo Thinkpad T440s
Partitions: 


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: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

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="8 (jessie) - installer build 20140204-00:05"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux thinkie 3.12-1-amd64 #1 SMP Debian 3.12.9-1 (2014-02-01) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM 
Controller [8086:0a04] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 
Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB 
xHCI HC [8086:9c31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point-LP HECI #0 [8086:9c3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I218-V [8086:1559] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:2214]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point-LP HD 
Audio Controller [8086:9c20] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI 
Express Root Port 6 [8086:9c1a] (rev e4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI 
Express Root Port 3 [8086:9c14] (rev e4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation Lynx Point-LP LPC 
Controller [8086:9c43] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation Lynx Point-LP 
SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation Lynx Point-LP SMBus 
Controller [8086:9c22] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. 
RTS5227 PCI Express Card Reader [10ec:5227] (rev 01)
lspci -knn: Subsystem: Lenovo Device [17aa:220c]
lspci -knn: 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b2] (rev 6b)
lspci -knn: Subsyst

Re: Old-timer installer, task-sysvinit?

[Philip Hands]

Jonas Smedegaard  writes:

> Quoting Cyril Brulebois (2014-11-23 14:31:00)
>> Jonas Smedegaard  (2014-11-23):
 If you're unhappy about the initial systemd installation, that's too 
 bad, because we're not going to change debootstrap, especially not 
 at this late stage of the release cycle, to behave differently 
 depending on the target distribution. The current script covers all 
 suites from etch (etch, lenny, squeeze, wheey, jessie, and now 
 stretch), and it'd really be nice if that could stay the case.
>>>
>>> I am unhappy about the need for messing non-declaratively with 
>>> debian-installer in order to override default choice of init system.
>>>
>>> It is nice that debian-installer provides hooks to do dangerous 
>>> things, but I find it worrisome that changing init system involves 
>>> use of that.
>>
>> I'm not sure why you're considering or calling preseeding “dangerous”.
>
> Use of a root shell can turn a Debian system into a non-Debian system 
> (by messing with the system in ways not following our defined rules).  
> Blame is on the user for doing so.  Typos are unsupported.
>
> Use of declarative hints should make it hard to do the same.  I would 
> expect it to be treated as a bug if some hint wreaks havoc without at 
> least popping up a strong warning first.

Ah, oh well then.

If one starts preseeding many of the internal bits of d-i, one can do
pretty much anything you like (and loads of things you don't like ;-) ).

If you're worried about recomending such things, I'd say that the way to
go is with a standard install, and then using some nice package manager
interface to change the init system.

If you want a way to do a non-shell based preseed, you _may_ be able to
get away with some combination of these:

=-=-=-=-
Template: base-installer/includes
Type: string
Description: for internal use; can be preseeded
 Packages to be included in base installation

Template: base-installer/excludes
Type: string
Description: for internal use; can be preseeded
 Packages to be excluded in base installation

Template: pkgsel/include
Type: string
Description: for internal use; can be preseeded
 Comma/space-separated list of extra packages to install
=-=-=-=-

Although you'd need to test that (I seem to remember them not doing
quite what I'd expected when I tried using them a long time ago, at
least when it came to excludes, so I've not touched them since).

TBH, given that one of the apparent selling features of sysvinit is how
nice it is to be able to do whatever one likes with a few lines of
shell, it strikes me as a bit odd to be shy of using a single shell
command to get what one wants.  Who is the target audience here?

Also, it _is_ preseeding to set this:

=-=-=-=-
Template: preseed/late_command
Type: string
Description: for internal use; can be preseeded <--- See?
 Shell command or commands to run in the d-i environment as late as possible
=-=-=-=-

Then again, I've used d-i as a presentation tool[1] -- I'm clearly deranged.

Cheers, Phil.

[1] http://hands.com/d-i/lenny/classes/ukuug06/early_script
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


pgpn_JcD150Ah.pgp
Description: PGP signature

Re: Old-timer installer, task-sysvinit?

[Holger Levsen]

...just a small addition...

On Sonntag, 23. November 2014, Cyril Brulebois wrote:
> Yes, you seem to have misunderstood me, because I did write this instead:
> So please use the available mechanisms to “avoid” systemd if you
> “need” doing so, and move on?

and "moving on" could perfectly include writing "whatever" patch and 
submitting that to the BTS for stretch (aka jessie+1)...


signature.asc
Description: This is a digitally signed message part.

Bug#770032: installer: Guided Partitioning Provides Insufficient Space

[IsitA Scam]

I just re-tested, they are not chosen by default.
This means I think the situation should be downgraded to an enhancement
request either for:
partman-auto to ask if a desktop environment was required (and then size
the / partition appropriately rather than as a fixed % of total)
and / or
tasksel to show a size estimate so it would be apparent that the desired
desktop environment won't work with the partitioning scheme prior to
spending the time on download and install and out of space failure.

On Sun, Nov 23, 2014 at 10:19 AM, Cyril Brulebois  wrote:

> Scot S  (2014-11-18):
> > Package: installer
> > Severity: important
> > Tags: d-i
> >
> > Dear Maintainer,
> >
> >
> >
> >* What led up to the situation?
> > Installation of a new system on an 8.6GB virtual harddrive using either
> of the listed NETINST cds
> > "Jessie" Official Snapshot i386 NETINST
> > Binary-1 20141117-04:37
> > "Jessie" Official Snapshot amd64 NETINST
> > Binary-1 20141117-06:40
> >
> >  Select any install method and then use Guided Partitioning with
> separate /home
> >  (with or without encryption).
> > Default setting is ~2gb / and remainder for /home.
> > This is insufficient space for install with any of the graphical
> environments so during the Install Software step, a red error box comes up
> that gives a generic Step Failed message.
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > First step was to try to resize the LVM w/Encryption which failed.
> >
> > Logs showed out of space errors, so reinstalled without separate /home.
> >
> >* What was the outcome of this action?
> > Fully functional without separate /home partition, default install with
> Cinnamon (not Gnome) appears to be just over 4gb.
> >* What outcome did you expect instead?
> > Information about the size of the packages selected, so a possible
> install could be completed with the partitioning chosen.
> > or
> > A note in the Guided Partitioning regarding space requirements (since
> non-GUI should fit in the space allocated). Possibly with a separate Guided
> for GUI option?
> > Best is one or both and a clear error message when the install fails at
> the install software step.
>
> Are you saying desktop environments were listed in tasksel with such a
> small / partition? My limited testing seems to suggest desktops aren't
> proposed in such a case.
>
> Mraw,
> KiBi.
>

Re: Old-timer installer, task-sysvinit?

[Cyril Brulebois]

Jonas Smedegaard  (2014-11-23):
> Use of a root shell can turn a Debian system into a non-Debian system 
> (by messing with the system in ways not following our defined rules).  
> Blame is on the user for doing so.  Typos are unsupported.
> 
> Use of declarative hints should make it hard to do the same.  I would 
> expect it to be treated as a bug if some hint wreaks havoc without at 
> least popping up a strong warning first.  Blame is on Debian.  We 
> support _using_ our system through the interfaces we provide - but some 
> interfaces are less governed by us, hence more dangerous to use.
> 
> I consider it more dangerous to tell users to operate a root shell than 
> have them type declarative hints.  Both gets processed as root, but the 
> latter is far less likely for typos or misunderstandings to wreak havoc.

You can “wreak havoc” plenty of things with other preseed options, or
even just answering d-i prompts. There's nothing specific to this
particular late_command option.

> >>> There won't any more debconf, udeb, or whatever addition going to 
> >>> happen. It means additional work (nobody has been doing that for a 
> >>> whole release cycle), more maintenance, and… it's just too late.
> >>
> >> Why do you say "for a whole release cycle"? Only late in the release 
> >> cycle did init system become changeable without violating policy 
> >> (removing core packages).
> >
> > Init systems have been a hot topic for most of the release cycle, with
> > #727708 being finally referred to the tech-ctte in october 2013,
> > meaning more than a year ago.
> 
> Until 4 months ago, choosing a non-default init system required typing 
> "YES, I KNOW WHAT I AM DOING" or something similar, due to requiring 
> removal of a essential package.
> 
> It is therefore no surprise to me that the idea of avoiding init from 
> debootstrap comes up now rather than a year ago (for starters, that 
> package didn't exist back then).

I hope you do realize I'm more than familiar with the timeline. That
doesn't change the fact that people could have worked towards this goal
many many months ago, and that now is too late.

> > It looks to me that people demanding so badly that debootstrap and/or 
> > d-i accomodates for their init system of choice should have started 
> > sending patches (to make init systems interchangeable or to support 
> > “choice” in debootstrap/d-i/etc.) way ahead of the freeze.
> 
> Way ahead of the freeze we talked about changing default init.  I 
> assumed that was similar to change of syslog daemon - i.e. if you want 
> something else than the default (which is in Debian and stable and does 
> not conflict with other things you also want) then you can have that 
> through ordinary standard Debian ways.
> 
> Only few months ago did I realize that this default is different from 
> other default packages, in that you cannot pick alternatives through 
> standard package selection interfaces, but must use a free-form root 
> shell.
> 
> Only now, today, do I realize that I am not even welcome to help work on 
> creating workaround declarative interfaces - only option is "shut up, 
> get in line" it seems.  I dearly hope I misunderstood you there.

Yes, you seem to have misunderstood me, because I did write this instead:

So please use the available mechanisms to “avoid” systemd if you
“need” doing so, and move on?

I'm not sure how many more times I'll have to say “no, this "feature"
isn't going to be merged into d-i, it's not needed, and it's too late”.

Anyway, I'll stop repeating myself; but please don't put any "shut up"
in my mouth.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Old-timer installer, task-sysvinit?

[Jonas Smedegaard]

Quoting Cyril Brulebois (2014-11-23 14:31:00)
> Jonas Smedegaard  (2014-11-23):
>>> If you're unhappy about the initial systemd installation, that's too 
>>> bad, because we're not going to change debootstrap, especially not 
>>> at this late stage of the release cycle, to behave differently 
>>> depending on the target distribution. The current script covers all 
>>> suites from etch (etch, lenny, squeeze, wheey, jessie, and now 
>>> stretch), and it'd really be nice if that could stay the case.
>>
>> I am unhappy about the need for messing non-declaratively with 
>> debian-installer in order to override default choice of init system.
>>
>> It is nice that debian-installer provides hooks to do dangerous 
>> things, but I find it worrisome that changing init system involves 
>> use of that.
>
> I'm not sure why you're considering or calling preseeding “dangerous”.

Use of a root shell can turn a Debian system into a non-Debian system 
(by messing with the system in ways not following our defined rules).  
Blame is on the user for doing so.  Typos are unsupported.

Use of declarative hints should make it hard to do the same.  I would 
expect it to be treated as a bug if some hint wreaks havoc without at 
least popping up a strong warning first.  Blame is on Debian.  We 
support _using_ our system through the interfaces we provide - but some 
interfaces are less governed by us, hence more dangerous to use.

I consider it more dangerous to tell users to operate a root shell than 
have them type declarative hints.  Both gets processed as root, but the 
latter is far less likely for typos or misunderstandings to wreak havoc.


>>> There won't any more debconf, udeb, or whatever addition going to 
>>> happen. It means additional work (nobody has been doing that for a 
>>> whole release cycle), more maintenance, and… it's just too late.
>>
>> Why do you say "for a whole release cycle"? Only late in the release 
>> cycle did init system become changeable without violating policy 
>> (removing core packages).
>
> Init systems have been a hot topic for most of the release cycle, with
> #727708 being finally referred to the tech-ctte in october 2013,
> meaning more than a year ago.

Until 4 months ago, choosing a non-default init system required typing 
"YES, I KNOW WHAT I AM DOING" or something similar, due to requiring 
removal of a essential package.

It is therefore no surprise to me that the idea of avoiding init from 
debootstrap comes up now rather than a year ago (for starters, that 
package didn't exist back then).


> It looks to me that people demanding so badly that debootstrap and/or 
> d-i accomodates for their init system of choice should have started 
> sending patches (to make init systems interchangeable or to support 
> “choice” in debootstrap/d-i/etc.) way ahead of the freeze.

Way ahead of the freeze we talked about changing default init.  I 
assumed that was similar to change of syslog daemon - i.e. if you want 
something else than the default (which is in Debian and stable and does 
not conflict with other things you also want) then you can have that 
through ordinary standard Debian ways.

Only few months ago did I realize that this default is different from 
other default packages, in that you cannot pick alternatives through 
standard package selection interfaces, but must use a free-form root 
shell.

Only now, today, do I realize that I am not even welcome to help work on 
creating workaround declarative interfaces - only option is "shut up, 
get in line" it seems.  I dearly hope I misunderstood you there.

Oh, and please, I do not demand anything here.  We are just talking :-)


Please cc me on replies,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: Old-timer installer, task-sysvinit?

[Jonas Smedegaard]

Quoting Wouter Verhelst (2014-11-23 14:15:27)
> On Sun, Nov 23, 2014 at 02:02:57PM +0100, Jonas Smedegaard wrote:
>> Quoting Cyril Brulebois (2014-11-23 13:13:05)
>>> Well, I'm really unsure what you're calling inaccurate in the third 
>>> point.
>>
>> It is that "preseeding" is the mechanism used - but I may indeed be 
>> wrong:
>>
>> I assumed the term "preseeding" meant "debconf preseeding", but 
>> realize now that indeed both 
>>  and e.g. 
>>  uses the 
>> term without direct ties to debconf.  Both those documents do, 
>> however, describe [not-only-debconf] preseeding as "a way to set 
>> answers to questions asked during the installation process".
>>
>> I consider preseeding to be feeding answers to questions before 
>> asked.  Executing shell scripts is something else, IMO.  You likely 
>> disagree.
>
> Implementation details, but:
>
> Debian-installer uses (c)debconf throughout, so "debconf preseeding" 
> and "installer preseeding" are really one and the same thing.

What you and I call "debconf preseeding" is then not the same thing.

What I am talking about (now lacking a name for) is what you can feed to 
debconf-set-selections.


> Debian-installer extends that by providing a few debconf templates 
> that are never shown to the user, but that *are* read by the installer 
> and acted upon. Some of those are the "early_command" and 
> "late_command" templates, which the installers assumes will contain 
> shell snippets that it must execute.
>
> So yes, it's running shell scripts, but yes, it's also feeding answers 
> to questions (albeit questions that will *not* be asked).

You can only feed declarative info to debconf-set-selections - e.g. can 
(even machine automated) resolve the package to bug about it if any data 
fed like that causes problems on the system operated on.

You cannot do that for any user-written shell code.


Please cc me on replies.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private



signature.asc
Description: signature

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Andreas B. Mundt]

Hi Jonas,

On Sun, Nov 23, 2014 at 04:56:16PM +0100, Jonas Smedegaard wrote:
> >
> > Sure thing: I will prepare git commits.
>
> I now have a fork of your git locally, and attached patches were
> produced using "git format-patch --minimal origin/master" - not sure if
> that's what you prefer, else please guide me.

You migth consider adding this improved warning to the patch set:


--- di-netboot-assistant.andi   2014-11-23 18:15:05.100283686 +0100
+++ di-netboot-assistant.jonas  2014-11-23 16:53:10.232629361 +0100
@@ -392,7 +392,7 @@

if [ -f pxelinux.cfg/default ]; then
for x in $(sed -n -e 
"s,^\s*KERNEL\s[\s:/]*\(.*menu.c32\).*,\1,p " pxelinux.cfg/default | sort -u ); 
do
+   [ ! -f ../$x ] && echo "W: The binary '${TFTP_ROOT}/$x' 
mentioned in the PXE boot menu is missing."
-   [ ! -f ../$x ] && echo "W: Some menu binaries are 
missing. Install the package syslinux"
done
else
find pxelinux.cfg/ -iregex '.*\(\.c32\|\.bak.*\|~\)$' \


It pops up when removing the debian-installer directory and not all installer
images have been installed again with di-netboot-assistant install XXX, and
the current content is rather confusing.

Best regards,

 Andi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123173321.GB14677@fuzi

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Andreas B. Mundt]

Hi Jonas,

On Sun, Nov 23, 2014 at 02:26:37PM +0100, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2014-11-23 13:05:36)
> > Quoting Cyril Brulebois (2014-11-23 12:49:58)
> > > Jonas Smedegaard  (2014-11-21):
> > >> Attached is a patch believed to fix all issues related to new syslinux:

[...]

> > > Of course I could try and split up your patches into atomic commits, but
> > > I guess it'd be better if knowledgeable could document patches. There's
> > > of course the part where Andreas had to patch a bit more what Jonas
> > > provided, so cross-checking each other would be nice.

[...]

> >
> > I am puzzled why you needed that change, Andreas.
> >
> > Perhaps it depend on the versions of syslinux involved.  I tested on
> > Jessie, with stable, testing and daily for amd64 and i386 - what did you
> > test?

I used jessie as well, fresh debian-lan installation (which already
uses di-netboot-assistant, the missing files are copied manually, and
TFTP_ROOT=/srv/tftp in /etc/di-netboot-assistant/di-netboot-assistant.conf)
But the problem is not with the different installer versions, the very
first boot menu fails here without adding my modifcation.

What I did:

I removed the existing directory 'debian-installer', applied your patch
and testet the new setup.  The tftproot '/srv/tftp' contains now:

debian-installer/  ldlinux.c32  libcom32.c32  libutil.c32

Booting a client via PXE fails with 'failed to load ldlinux.c32'.

I move the directory to debian-installer-jonas, remove the .c32-files
and use my version. Now only

debian-installer/

has been created in '/srv/tftp' and PXE-booting works fine offering
the installer menu.  The directory trees are identical except that
*.c32 ended in the debian-installer dir:

 diff -rq /srv/tftp/debian-installer-andi/ /srv/tftp/debian-installer-jonas/
 Only in /srv/tftp/debian-installer-andi/: ldlinux.c32
 Only in /srv/tftp/debian-installer-andi/: libcom32.c32
 Only in /srv/tftp/debian-installer-andi/: libutil.c32

> > Or perhaps it is related to choice and configuration of tftpd.  I use
> > tftpd-hpa with TFTP_OPTIONS="--blocksize 1468 -v -v -v -v --secure" and
> > adapting di-netboot-assistant to use /srv/tftp.

Same here :-/

> @Andreas: If you configured your tftpd to treat debian-installer subdir
> as root dir for tftpd, then you should move/copy those three files
> yourself: This script currently has configurable TFTP_ROOT but hardcoded
> debian-installer subdir - making that configurable too is independent
> from this bug.

No idea what's different in our setups/tests.  Perhaps the above
informations give some hint on that.

Best regards,

 Andi


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123164127.GA14677@fuzi

Bug#770658: fails to debootstrap debian on fedora: Failure trying to run: chroot /debian mount -t proc proc /proc

[Ben Hutchings]

On Sun, 2014-11-23 at 15:24 +0100, Cyril Brulebois wrote:
> Joey Hess  (2014-11-22):
[...]
> > Suggested fix: Before chrooting into the debootstrapped chroot to run
> > commands, debootstrap should ensure that the PATH includes all
> > directories it does on a standard debian system. Eg:
> > 
> > PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> > 
> > This way, the host system's chroot etc will still be found whereever
> > it's PATH has them, and the debian system's commands will likewise be
> > found.
> 
> I see two naive approaches here: append said $PATH unconditionally, or
> walk through each component and only append those who aren't in $PATH
> already. Not sure how reliable it would be to split current $PATH
> using ':' as a separator, in case there are some funnily-named,
> maybe-quoted directories in there. I'm happy to receive hints here.

':' is always a separator; $PATH cannot include directories whose names
contain colons.

But does it make sense to use the outer system's $PATH at all?  Why
shouldn't debootstrap reset it to the Debian default whenever it runs a
command in chroot?

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.


signature.asc
Description: This is a digitally signed message part

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2014-11-23 13:05:36)
> Quoting Cyril Brulebois (2014-11-23 12:49:58)
>> Jonas Smedegaard  (2014-11-21):
>>> Attached is a patch believed to fix all issues related to new 
>>> syslinux:
>>>
>>>  * Lookup pxelinux.0 in /usr/lib/PXELINUX (not only 
>>>/usr/lib/syslinux).
>>>  * Lookup only BIOS binaries (not accidentally include EFI 
>>>binaries).
>>>  * Install core modules at tftpd root dir.
>>>  * Keep vesamenu and menu modules in sync with PXELINUX.
>>
>> thank you both for providing patches to di-netboot-assistant; is 
>> there any chance you could submit a branch or patch series against 
>> its git repository 
>> (git://anonscm.debian.org/d-i/netboot-assistant.git)?
>>
>> Of course I could try and split up your patches into atomic commits, 
>> but I guess it'd be better if knowledgeable could document patches. 
>> There's of course the part where Andreas had to patch a bit more what 
>> Jonas provided, so cross-checking each other would be nice.
>
> Sure thing: I will prepare git commits.

I now have a fork of your git locally, and attached patches were 
produced using "git format-patch --minimal origin/master" - not sure if 
that's what you prefer, else please guide me.

My patches do not incorporate Andreas' addition, as I believe it to be 
wrong.  I could be wrong, of course, and am open to further input.


Hope this all helps,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
From e4b2ab5cd4e09daf72d51ee5b35b3a8b8b5e92d9 Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard 
Date: Sun, 23 Nov 2014 16:01:15 +0100
Subject: [PATCH 5/5] Handle core PXELINUX modules introduced in recent
 PXELINUX, required to be served at tftp root dir.

---
 di-netboot-assistant | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/di-netboot-assistant b/di-netboot-assistant
index d581507..e21112e 100755
--- a/di-netboot-assistant
+++ b/di-netboot-assistant
@@ -276,6 +276,13 @@ copy_syslinux_bin() {
 	done
 	# Smooth transition to vesamenu
 	[ ! -f "$c32_dir/menu.c32" ] && ln -s "vesamenu.c32" $c32_dir/menu.c32
+	# Add core modules at root (see )
+	if [ "$TFTP_ROOT/debian-installer/" = "$dst" ]; then
+		for f in ldlinux.c32 libcom32.c32 libutil.c32; do
+			srcf="$(find_file $f "$src")"
+			[ -z "$srcf" ] || cp -np "$srcf" "$TFTP_ROOT/$f"
+		done
+	fi
 	return 0
 }
 
@@ -925,6 +932,9 @@ setup_syslinux() {
 		  vesamenu.c32|menu.c32)
 			cp -pft "$(dirname "$f")" "$TFTP_ROOT/debian-installer/pxelinux.cfg/$(basename "$f")"
 			;;
+		  ldlinux.c32|libcom32.c32|libutil.c32)
+			cp -pft "$(dirname "$f")" "$TFTP_ROOT/$(basename "$f")"
+			;;
 		  *)
 			echo "W: Unusual PXELINUX module \"$f\" may not work." 1>&2
 			continue
-- 
2.1.3

From 8e3ffac22d2888ed0094ed3a172257836250ccbf Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard 
Date: Sun, 23 Nov 2014 15:45:48 +0100
Subject: [PATCH 4/5] Update PXELINUX modules to be in sync with PXELINUX
 itself.

---
 di-netboot-assistant | 12 
 1 file changed, 12 insertions(+)

diff --git a/di-netboot-assistant b/di-netboot-assistant
index 7b93e11..d581507 100755
--- a/di-netboot-assistant
+++ b/di-netboot-assistant
@@ -919,6 +919,18 @@ setup_syslinux() {
 	if ! copy_syslinux_bin "$expand_dir" "$TFTP_ROOT/debian-installer/" ; then
 		echo "E: No PXELinux menu installed. Please file a bug." 1>&2
 	fi
+	# ensure only a single PXELINUX version is used for all its modules
+	for f in $(find "$expand_dir" -type f -name '*.c32'); do
+		case $(basename "$f") in
+		  vesamenu.c32|menu.c32)
+			cp -pft "$(dirname "$f")" "$TFTP_ROOT/debian-installer/pxelinux.cfg/$(basename "$f")"
+			;;
+		  *)
+			echo "W: Unusual PXELINUX module \"$f\" may not work." 1>&2
+			continue
+			;;
+		esac
+	done
 
 	for f in $(find "$expand_dir" -type f -a \( -name "default" -o -name "boot.txt" -o -name '*.cfg' \) ); do
 		mv "$f" "$f.ORIG"
-- 
2.1.3

From 0a3af696406e8cb5e6f695d43118696d940ca2b9 Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard 
Date: Sun, 23 Nov 2014 13:11:08 +0100
Subject: [PATCH 1/5] Extend find_file() to support multiple paths (and fix
 order of arguments in comment while at it).

---
 di-netboot-assistant | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/di-netboot-assistant b/di-netboot-assistant
index 88c06f7..f85e381 100755
--- a/di-netboot-assistant
+++ b/di-netboot-assistant
@@ -200,12 +200,13 @@ print_do_not_edit_header() {
 #  #
 # find_file()
 #	Return the name of the first file matching criteria.
-# Parameters: dir name
+# Parameters: name dir [dir...]
 # Returns: (STRING) file
 #  #
 find_file() {
 	if [ "$1" -a "$2" ]; then
-		find "$2" -type f -name $1 | head -n 1
+		local name=$1; shift
+		find "$@" -type f -name "$name" | head -n 1
 	e

Bug#769107: debian-installer: grub-installer fails if more than 26 SCSI devices are present

[Cyril Brulebois]

Michael Weiser  (2014-11-11):
> >From 333151e5eed04e7ef292bb15109131e731092674 Mon Sep 17 00:00:00 2001
> From: Michael Weiser 
> Date: Tue, 11 Nov 2014 16:59:05 +0100
> Subject: [PATCH] Allow for devices with multiple enumeration characters
> 
> Allow for installation of grub on devices such as /dev/sdaa or
> /dev/xvdab.
> ---
>  grub-installer | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/grub-installer b/grub-installer
> index 2b61fb6..cce326f 100755
> --- a/grub-installer
> +++ b/grub-installer
> @@ -252,7 +252,7 @@ case $prefix in
>  /dev/mapper)
>   disc_offered_devfs="$bootfs"
>   ;;
> -
> /dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
> +
> /dev/[hsv]d[a-z0-9]|/dev/[sv]d[a-z][a-z]*|/dev/xvd[a-z]*|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
>   disc_offered_devfs="$prefix"
>   ;;
>  *)

Hi Ben,

could you please double check the above patch? I'd like another pair
of eyes on it before possibly merging it.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#769996: debian-installer: Possible help text for win32diskimager users

[Cyril Brulebois]

Geert Stappers  (2014-11-18):
> On Tue, Nov 18, 2014 at 06:04:20AM +0100, nodiscc wrote:
> > 
> > Hello, here is a short text that can be used in the documentation:
> > 
> >  * download win32diskimager from 
> > http://sourceforge.net/projects/win32diskimager/, unpack the archive and 
> > run Win32DiskImager.exe
> >  * in the "Image file" area, select the .iso debian installer iage you 
> > downloaded from debian.org
> >  * in the "Device" area, select the drive letter for the USB drive you want 
> > to use as an installation media
> >* you may have to format the USB drive first to affect a drive letter to 
> > it
> >  * Click "Write". **All data present on the USB drive will be erased!**
> > 
> > Thanks!
>  
> 
> Proposal:
> 
> --- manual/en/install-methods/boot-usb-files.xml  (revision 69458)
> +++ manual/en/install-methods/boot-usb-files.xml  (working copy)
> @@ -178,4 +178,32 @@
>  
>
>  
> +  
> +  Creating USB-stick Debian-installer under Windows
> +
> +
> +Download win32diskimager from 
> http://sourceforge.net/projects/win32diskimager/,
> +unpack the archive and run Win32DiskImager.exe
> +
> +
> +
> +In the "Image file" area,
> +select the .iso installer image you downloaded.
> +
> +
> +
> +In the "Device" area,
> +select the drive letter for the USB drive
> +you want to use as an installation media.
> +
> +
> +
> +You may have to format the USB drive first
> +to affect a drive letter to it.
> +Click "Write". **All data present on the USB drive will be erased!**
> +
> +
> +
> +  
> +
>   

I'm not sure how comfortable I feel with including instructions for
Windows-based stuff in to the installation guide. Maybe people more
used to dealing with the manual will voice their opinions here.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#770032: installer: Guided Partitioning Provides Insufficient Space

[Cyril Brulebois]

Scot S  (2014-11-18):
> Package: installer
> Severity: important
> Tags: d-i
> 
> Dear Maintainer,
> 
> 
> 
>* What led up to the situation?
> Installation of a new system on an 8.6GB virtual harddrive using either of 
> the listed NETINST cds
> "Jessie" Official Snapshot i386 NETINST
> Binary-1 20141117-04:37 
> "Jessie" Official Snapshot amd64 NETINST
> Binary-1 20141117-06:40
> 
>  Select any install method and then use Guided Partitioning with separate 
> /home
>  (with or without encryption).
> Default setting is ~2gb / and remainder for /home.
> This is insufficient space for install with any of the graphical environments 
> so during the Install Software step, a red error box comes up that gives a 
> generic Step Failed message.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> First step was to try to resize the LVM w/Encryption which failed.
> 
> Logs showed out of space errors, so reinstalled without separate /home.
> 
>* What was the outcome of this action?
> Fully functional without separate /home partition, default install with 
> Cinnamon (not Gnome) appears to be just over 4gb.
>* What outcome did you expect instead?
> Information about the size of the packages selected, so a possible install 
> could be completed with the partitioning chosen.
> or
> A note in the Guided Partitioning regarding space requirements (since non-GUI 
> should fit in the space allocated). Possibly with a separate Guided for GUI 
> option?
> Best is one or both and a clear error message when the install fails at the 
> install software step.

Are you saying desktop environments were listed in tasksel with such a
small / partition? My limited testing seems to suggest desktops aren't
proposed in such a case.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#770116: marked as done (installation-reports: After sucessful installation the first reboot logs "hda codec out of range")

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 16:14:17 +0100
with message-id <20141123151417.gc14...@mraw.org>
and subject line Re: Bug#770116: installation-reports: After sucessful 
installation the first reboot logs "hda codec out of range"
has caused the Debian Bug report #770116,
regarding installation-reports: After sucessful installation the first reboot 
logs "hda codec out of range"
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.)


-- 
770116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal

Dear Maintainer,

After a sucessfully terminated installation the first reboot logs "hda codec 
out of range".

-- Package-specific info:

Boot method: started with DVD ISO then chosen network installation
Image version: DVD ISO Image: Debian GNU/Linux 7.6.0 _Wheezy_ - Official amd64 
DVD Binary-1 20140712-14:11 --- Package: linux-image-3.2.0-4-amd64 --- Version: 
3.2.63-2+deb7u1
Date: 19/11/2014 11:00

Machine: desktop pc with AMD FX(tm)-8350 Eight-Core Processor × 8 and with AMD 
Radeon R9 290X Graphics Card
Partitions: df -Tl
File systemTipo 1K-blocchi   
Usati Disponib. Uso% Montato su
rootfs rootfs  1152032  
205544887968  19% /
udev   devtmpfs  10240  
 0 10240   0% /dev
tmpfs  tmpfs396084 
652395432   1% /run
/dev/disk/by-uuid/2cb4af05-d298-4b47-bba7-cac391467f9a ext41152032  
205544887968  19% /
tmpfs  tmpfs  5120  
 0  5120   0% /run/lock
tmpfs  tmpfs   2745120 
228   2744892   1% /run/shm
/dev/sda9  ext4  849737324  
244724 806328392   1% /home
/dev/sda8  ext4 960504   
17768893944   2% /tmp
/dev/sda5  ext4   96120588 
3410784  87827068   4% /usr
/dev/sda6  ext43844152  
455800   3193076  13% /var



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [ ]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: Not any comments.

-- 

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="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux pc 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI 
RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02)
lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI RD890 PCI to 
PCI bridge (external gfx0 port B) [1002:5a14]
lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI 
RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:03.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI 
RD890 PCI to PCI bridge (PCI express gpp port C) [1002:5a17]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI 
RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI 
RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:06.0 PCI bridg

Bug#770658: fails to debootstrap debian on fedora: Failure trying to run: chroot /debian mount -t proc proc /proc

[Cyril Brulebois]

Joey Hess  (2014-11-22):
> Package: debootstrap
> Version: 1.0.64
> Severity: normal
> 
> W: Failure trying to run: chroot /debian mount -t proc proc /proc
> 
> This is because mount is in a different location in fedora than in debian.
> On Debian, it's in /bin/mount, while on fedora, /usr/bin/mount.
> 
> And, on fedora, root's default path does not contain /bin:
> 
> [root@alien /]# echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
> 
> So, chroot tries each of those directories, does not find mount in them
> in the debian chroot, and fails.
> 
> Suggested fix: Before chrooting into the debootstrapped chroot to run
> commands, debootstrap should ensure that the PATH includes all
> directories it does on a standard debian system. Eg:
> 
> PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> 
> This way, the host system's chroot etc will still be found whereever
> it's PATH has them, and the debian system's commands will likewise be
> found.

I see two naive approaches here: append said $PATH unconditionally, or
walk through each component and only append those who aren't in $PATH
already. Not sure how reliable it would be to split current $PATH
using ':' as a separator, in case there are some funnily-named,
maybe-quoted directories in there. I'm happy to receive hints here.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#770217: cannot be run from source on !debian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 help
Bug #770217 [debootstrap] cannot be run from source on !debian
Added tag(s) help.

-- 
770217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770217
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: 
https://lists.debian.org/handler.s.b770217.141675249923737.transcr...@bugs.debian.org

Bug#770217: cannot be run from source on !debian

[Cyril Brulebois]

Control: tag -1 help

Joey Hess  (2014-11-19):
> Package: debootstrap
> Version: 1.0.64
> Severity: normal
> 
> make devices.tar.gz runs MAKEDEV, so the instructions to run debootstrap
> from source don't work on !debian.
> 
> setup_devices contains old code to bind mount /dev when it's managed by
> devfs. Updating that code to check for /dev managed by udev and
> bind mounting then might be one approach to improve this. The resulting
> chroot would need to have /dev/ bind mounted into it in order to be
> used, which seems reasonable.
> 
> Alternatively, a debootstrap tarball could be provided targeting this
> use case, including a prebuilt devices.tar.gz.
> 
> Alternatively, the devices.tar.gz Makefile target could, if MAKEDEV is
> not in path, just tar up the system's /dev to make it.

I'm afraid I won't be working on this part, so tagging this bug report
with help.

> I suspect that some people in this situation download the .deb from
> debian and manually unpack it to get a prebuilt devices.tar.gz. Although
> this requires both ar and (for no good reason) xz, which are not
> universally available outside debian systems.

I've just looked into switching back (binary) debootstrap's
compression from xz to gzip, and it seems to only cost 10 KB, so I've
committed this to master:
  
http://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=39faba934e3c15fe9960d5a99d9a8b43ac986145

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Old-timer installer, task-sysvinit?

[Cyril Brulebois]

Jonas Smedegaard  (2014-11-23):
> > If you're unhappy about the initial systemd installation, that's too
> > bad, because we're not going to change debootstrap, especially not
> > at this late stage of the release cycle, to behave differently
> > depending on the target distribution. The current script covers all
> > suites from etch (etch, lenny, squeeze, wheey, jessie, and now
> > stretch), and it'd really be nice if that could stay the case.
> 
> I am unhappy about the need for messing non-declaratively with
> debian-installer in order to override default choice of init system.
> 
> It is nice that debian-installer provides hooks to do dangerous
> things, but I find it worrisome that changing init system involves
> use of that.

I'm not sure why you're considering or calling preseeding “dangerous”.

> > There won't any more debconf, udeb, or whatever addition going to 
> > happen. It means additional work (nobody has been doing that for a 
> > whole release cycle), more maintenance, and… it's just too late.
> 
> Why do you say "for a whole release cycle"? Only late in the release 
> cycle did init system become changeable without violating policy 
> (removing core packages).

Init systems have been a hot topic for most of the release cycle, with
#727708 being finally referred to the tech-ctte in october 2013,
meaning more than a year ago. It looks to me that people demanding so
badly that debootstrap and/or d-i accomodates for their init system of
choice should have started sending patches (to make init systems
interchangeable or to support “choice” in debootstrap/d-i/etc.) way
ahead of the freeze.

Kenshi Muto is one of the few people having done actual work and sent
patches, but way too late.

So please use the available mechanisms to “avoid” systemd if you
“need” doing so, and move on?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2014-11-23 13:05:36)
> Quoting Cyril Brulebois (2014-11-23 12:49:58)
> > Jonas Smedegaard  (2014-11-21):
> >> Attached is a patch believed to fix all issues related to new syslinux:
> >> 
> >>   * Lookup pxelinux.0 in /usr/lib/PXELINUX (not only /usr/lib/syslinux).
> >>   * Lookup only BIOS binaries (not accidentally include EFI binaries).
> >>   * Install core modules at tftpd root dir.
> >>   * Keep vesamenu and menu modules in sync with PXELINUX.
> >
> > thank you both for providing patches to di-netboot-assistant; is there
> > any chance you could submit a branch or patch series against its git
> > repository (git://anonscm.debian.org/d-i/netboot-assistant.git)?
> >
> > Of course I could try and split up your patches into atomic commits, but
> > I guess it'd be better if knowledgeable could document patches. There's
> > of course the part where Andreas had to patch a bit more what Jonas
> > provided, so cross-checking each other would be nice.
> 
> Sure thing: I will prepare git commits.
> 
> I am puzzled why you needed that change, Andreas.
> 
> Perhaps it depend on the versions of syslinux involved.  I tested on 
> Jessie, with stable, testing and daily for amd64 and i386 - what did you 
> test?
> 
> Or perhaps it is related to choice and configuration of tftpd.  I use 
> tftpd-hpa with TFTP_OPTIONS="--blocksize 1468 -v -v -v -v --secure" and 
> adapting di-netboot-assistant to use /srv/tftp.

@Andreas: If you configured your tftpd to treat debian-installer subdir 
as root dir for tftpd, then you should move/copy those three files 
yourself: This script currently has configurable TFTP_ROOT but hardcoded 
debian-installer subdir - making that configurable too is independent 
from this bug.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: Old-timer installer, task-sysvinit?

[Cyril Brulebois]

Thorsten Glaser  (2014-11-23):
> Cyril Brulebois dixit:
> 
> >bad, because we're not going to change debootstrap, especially not at
> >this late stage of the release cycle, to behave differently depending
> >on the target distribution. The current script covers all suites from
> 
> This is not necessary. Well, not at first.
> 
> The changes to debootstrap I’d “love” to have are:
> 
> ① add a new --variant called sysvinit, which excludes all the
>   systemd bits and explicitly adds sysvinit-core; this variant
>   will only be usable with jessie and up, but as it must be
>   invoked explicitly will not do anything to older releases.
> 
>   This is the change we’d need now.

No we don't need that, for the reasons I listed, and the ones below.

> ② change the scripts for --variant minbase, buildd, fakechroot,
>   scratchbox to exclude systemd, sysvinit (and, for good measure
>   on certain downstreams) upstart. This will not touch either
>   --variant sysvinit or base (the default).
> 
>   This is a change that could be put into experimental, as it
>   is not necessary for either the release or d-i. Then upload
>   that to sid after the unfreeze.

Having init not pulled by debootstrap was mentioned recently but I'm
not sure this led to a bug report tracking this. Might be worth
investigating for jessie+1.

> ③ To be fair, add --variant=upstart based on the sysvinit variant.
>   And openrc. But this all will end up in experimental, too.

Once/if there's a way to have an initless system, people can install
whatever init they want on top of it; having a flavour per init looks
like a bad idea.

> I’d actually be happy to try and hack these myself and submit
> them for inclusion. Is the --exclude not working bug fixed by
> now btw?

Read the bug log?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: Old-timer installer, task-sysvinit?

[Wouter Verhelst]

On Sun, Nov 23, 2014 at 02:02:57PM +0100, Jonas Smedegaard wrote:
> Quoting Cyril Brulebois (2014-11-23 13:13:05)
> > Well, I'm really unsure what you're calling inaccurate in the third 
> > point.
> 
> It is that "preseeding" is the mechanism used - but I may indeed be 
> wrong:
> 
> I assumed the term "preseeding" meant "debconf preseeding", but realize 
> now that indeed both  
> and e.g.  
> uses the term without direct ties to debconf.  Both those documents do, 
> however, describe [not-only-debconf] preseeding as "a way to set answers 
> to questions asked during the installation process".
> 
> I consider preseeding to be feeding answers to questions before asked.  
> Executing shell scripts is something else, IMO.  You likely disagree.

Implementation details, but:

Debian-installer uses (c)debconf throughout, so "debconf preseeding" and
"installer preseeding" are really one and the same thing.

Debian-installer extends that by providing a few debconf templates that
are never shown to the user, but that *are* read by the installer and
acted upon. Some of those are the "early_command" and "late_command"
templates, which the installers assumes will contain shell snippets that
it must execute.

So yes, it's running shell scripts, but yes, it's also feeding answers
to questions (albeit questions that will *not* be asked).

Regards,

-- 
It is easy to love a country that is famous for chocolate and beer

  -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141123131527.gb22...@grep.be

Re: Old-timer installer, task-sysvinit?

[Jonas Smedegaard]

Quoting Cyril Brulebois (2014-11-23 13:13:05)
> Jonas Smedegaard  (2014-11-23):
>> Quoting Erich Schubert (2014-11-23 09:50:12)
>>> 1. There is a wide consensus that Debian continues to allow other 
>>> init systems.
>>> 2. The installer (currently) does install systemd.
>>> 3. The installer CAN be used to install sysvinit via preseeding (and 
>>> admins should know how to use preseeding to install systems...)
>>
>> I believe third point above is inaccurate: Debian-installer has hooks 
>> to pass hints to packages (debconf preseeding) and hooks to execute 
>> shell scripts.  What is currently possible is only the latter: Spawn 
>> a shell script late in the install process to replace init-related 
>> packages already installed by debian-installer.
>
> Well, I'm really unsure what you're calling inaccurate in the third 
> point.

It is that "preseeding" is the mechanism used - but I may indeed be 
wrong:

I assumed the term "preseeding" meant "debconf preseeding", but realize 
now that indeed both  
and e.g.  
uses the term without direct ties to debconf.  Both those documents do, 
however, describe [not-only-debconf] preseeding as "a way to set answers 
to questions asked during the installation process".

I consider preseeding to be feeding answers to questions before asked.  
Executing shell scripts is something else, IMO.  You likely disagree.


> I think I've mentioned that a few times already, but here's yet 
> another reference:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668001#60

Yes.  And thanks for pointing to that at several occasions recently.


> That's preseeding, that gives a system running sysvinit-core at the 
> first boot without any further interaction, replacing systemd bits by 
> sysvinit ones after the initial debootstrap.

Ok, I understand now that preseeding not only means answering questions 
before asked, but also non-declarative automation.  That's new to me.


> If you're unhappy about the initial systemd installation, that's too 
> bad, because we're not going to change debootstrap, especially not at 
> this late stage of the release cycle, to behave differently depending 
> on the target distribution. The current script covers all suites from 
> etch (etch, lenny, squeeze, wheey, jessie, and now stretch), and it'd 
> really be nice if that could stay the case.

I am unhappy about the need for messing non-declaratively with 
debian-installer in order to override default choice of init system.

It is nice that debian-installer provides hooks to do dangerous things, 
but I find it worrisome that changing init system involves use of that.


> There won't any more debconf, udeb, or whatever addition going to 
> happen. It means additional work (nobody has been doing that for a 
> whole release cycle), more maintenance, and… it's just too late.

Why do you say "for a whole release cycle"? Only late in the release 
cycle did init system become changeable without violating policy 
(removing core packages).


Please cc me on replies.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: Old-timer installer, task-sysvinit?

[Thorsten Glaser]

Cyril Brulebois dixit:

>bad, because we're not going to change debootstrap, especially not at
>this late stage of the release cycle, to behave differently depending
>on the target distribution. The current script covers all suites from

This is not necessary. Well, not at first.

The changes to debootstrap I’d “love” to have are:

① add a new --variant called sysvinit, which excludes all the
  systemd bits and explicitly adds sysvinit-core; this variant
  will only be usable with jessie and up, but as it must be
  invoked explicitly will not do anything to older releases.

  This is the change we’d need now.

② change the scripts for --variant minbase, buildd, fakechroot,
  scratchbox to exclude systemd, sysvinit (and, for good measure
  on certain downstreams) upstart. This will not touch either
  --variant sysvinit or base (the default).

  This is a change that could be put into experimental, as it
  is not necessary for either the release or d-i. Then upload
  that to sid after the unfreeze.

③ To be fair, add --variant=upstart based on the sysvinit variant.
  And openrc. But this all will end up in experimental, too.

I’d actually be happy to try and hack these myself and submit
them for inclusion. Is the --exclude not working bug fixed by
now btw?

bye,
//mirabilos
-- 
21:12⎜ sogar bei opensolaris haben die von der community so
ziemlich jeden mist eingebaut │ man sollte unices nich so machen das
desktopuser zuviel intresse kriegen │ das macht die code base kaputt
21:13⎜ linux war früher auch mal besser :D


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/pine.bsm.4.64l.1411231221540.24...@herc.mirbsd.org

Re: Old-timer installer, task-sysvinit?

[Thorsten Glaser]

Jonas Smedegaard dixit:

>> 3. The installer CAN be used to install sysvinit via preseeding (and
>> admins should know how to use preseeding to install systems...)
[…]
>script late in the install process to replace init-related packages 
>already installed by debian-installer.

Indeed. You can also just Alt-F2 and run
in-target apt-get --purge -y install sysvinit-core
yourself; the --purge additionally removes the configs of
removed packages, but dependencies of them are *still* there
*and* not eligible for “apt-get --purge autoremove” because
installed by debootstrap.

(I tend to install dselect to clean up junk d-i insists on,
like dictionaries, straight after the installation anyway,
so this is almost not more work for me, but…)

Plus: it installs systemd first, then switches to sysvinit.
Do we have a promise that that will keep being supported?
And it feels a bit backward…

>Please Cc me, I am not subscribed here.

Same.

bye,
//mirabilos
-- 
 Beware of ritual lest you forget the meaning behind it.
 yeah but it means if you really care about something, don't
ritualise it, or you will lose it. don't fetishise it, don't
obsess. or you'll forget why you love it in the first place.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/pine.bsm.4.64l.1411231217000.24...@herc.mirbsd.org

Re: Old-timer installer, task-sysvinit?

[Cyril Brulebois]

Jonas Smedegaard  (2014-11-23):
> Quoting Erich Schubert (2014-11-23 09:50:12)
> > 1. There is a wide consensus that Debian continues to allow other init 
> > systems.
> > 2. The installer (currently) does install systemd.
> > 3. The installer CAN be used to install sysvinit via preseeding (and
> > admins should know how to use preseeding to install systems...)
> 
> I believe third point above is inaccurate: Debian-installer has hooks to 
> pass hints to packages (debconf preseeding) and hooks to execute shell 
> scripts.  What is currently possible is only the latter: Spawn a shell 
> script late in the install process to replace init-related packages 
> already installed by debian-installer.

Well, I'm really unsure what you're calling inaccurate in the third
point. I think I've mentioned that a few times already, but here's yet
another reference:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668001#60

That's preseeding, that gives a system running sysvinit-core at the
first boot without any further interaction, replacing systemd bits by
sysvinit ones after the initial debootstrap.

If you're unhappy about the initial systemd installation, that's too
bad, because we're not going to change debootstrap, especially not at
this late stage of the release cycle, to behave differently depending
on the target distribution. The current script covers all suites from
etch (etch, lenny, squeeze, wheey, jessie, and now stretch), and it'd
really be nice if that could stay the case.

There won't any more debconf, udeb, or whatever addition going to
happen. It means additional work (nobody has been doing that for a whole
release cycle), more maintenance, and… it's just too late.

> Please Cc me, I am not subscribed here.

Done.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#762399: console-setup: WARNING: Unknown X keysym "permille"

[Martin-Éric Racine]

2014-10-07 20:17 GMT+03:00 Martin-Éric Racine :
> 2014-10-07 18:52 GMT+03:00 Anton Zinoviev :
>> On Mon, Sep 22, 2014 at 12:33:25AM +0300, Martin-Éric Racine wrote:
>>>
>>> Setting up console-setup (1.113) ...
>>> WARNING: Unknown X keysym "permille"
>>> WARNING: Unknown X keysym "permille"
>>> WARNING: Unknown X keysym "permille"
>>> WARNING: Unknown X keysym "permille"
>>> WARNING: Unknown X keysym "ezh"
>>> WARNING: Unknown X keysym "EZH"
>>> WARNING: Unknown X keysym "ezh"
>>> WARNING: Unknown X keysym "EZH"
>>> WARNING: Unknown X keysym "ezh"
>>> WARNING: Unknown X keysym "EZH"
>>> WARNING: Unknown X keysym "ezh"
>>> WARNING: Unknown X keysym "EZH"
>>> Setting up libprotobuf9:i386 (2.6.0-3) ...
>>>
>>> Could this be caused by ckbcomp's built-in (X keysym -> kernel keysym)
>>> table missing these?
>>
>> Yes.
>
> Alright. Would it be possible to re-generate that symbol table and fix
> the issue? :)

Thanks for fixing the issue in 1.115.

However, the package is currently blocked because of the freeze and it
would need an unblock request to propagate into Testing.

Martin-Éric


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/debian-boot

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Jonas Smedegaard]

Quoting Cyril Brulebois (2014-11-23 12:49:58)
> Jonas Smedegaard  (2014-11-21):
>> Attached is a patch believed to fix all issues related to new syslinux:
>> 
>>   * Lookup pxelinux.0 in /usr/lib/PXELINUX (not only /usr/lib/syslinux).
>>   * Lookup only BIOS binaries (not accidentally include EFI binaries).
>>   * Install core modules at tftpd root dir.
>>   * Keep vesamenu and menu modules in sync with PXELINUX.
>
> thank you both for providing patches to di-netboot-assistant; is there
> any chance you could submit a branch or patch series against its git
> repository (git://anonscm.debian.org/d-i/netboot-assistant.git)?
>
> Of course I could try and split up your patches into atomic commits, but
> I guess it'd be better if knowledgeable could document patches. There's
> of course the part where Andreas had to patch a bit more what Jonas
> provided, so cross-checking each other would be nice.

Sure thing: I will prepare git commits.

I am puzzled why you needed that change, Andreas.

Perhaps it depend on the versions of syslinux involved.  I tested on 
Jessie, with stable, testing and daily for amd64 and i386 - what did you 
test?

Or perhaps it is related to choice and configuration of tftpd.  I use 
tftpd-hpa with TFTP_OPTIONS="--blocksize 1468 -v -v -v -v --secure" and 
adapting di-netboot-assistant to use /srv/tftp.


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

partman-base_180_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 Nov 2014 12:38:26 +0100
Source: partman-base
Binary: partman-base partman-utils
Architecture: source
Version: 180
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 partman-base - Partition the storage devices (partman) (udeb)
 partman-utils - Utilities related to partitioning (udeb)
Closes: 770666
Changes:
 partman-base (180) unstable; urgency=low
 .
   * Avoid overwriting the bootloader area on more platforms: detect
 Freescale and AM33XX systems along with Allwinner ones, and disable
 ped_disk_clobber on such systems, when the device is /dev/mmcblk0
 (Closes: #770666). With many thanks to Vagrant Cascadian!
Checksums-Sha1:
 9e07a8068837193225e64f45fb36099106e4c196 1858 partman-base_180.dsc
 c8b82e3ba16d38377789ee6b39afe50e1ebffc66 172604 partman-base_180.tar.xz
Checksums-Sha256:
 44d9c7f4d30d94839b2a2af2b140348e84f37b13df782b8fd908f0680328637d 1858 
partman-base_180.dsc
 c8b66a31450e870629d782547a03478ecfb587eff203f5738cf12b188b0608d5 172604 
partman-base_180.tar.xz
Files:
 299c2b96d2a78bcd4254b62b34ebf6bd 1858 debian-installer standard 
partman-base_180.dsc
 b99507dfd5976a4a016832e20e7703b2 172604 debian-installer standard 
partman-base_180.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJUccf4AAoJEP+RSvDCs1Ugs9kQAJqhnKn5DG/cLoRqWkkTxcQm
m+Uu67OPHyvJQx0khM3Fi/OVoO582m0d+GfrYUlrmoYk1bSUBm0+46v7/hBqN9LN
2gTsSvba+yQ97tViB8rAoWTI0MCfObdwtZK8RoSFyRzh3PG/Zs+MHG0mhbwPoZ/X
CorSdp7DvPm9MN7IVKged+KbNlC7dPCL+VBGjVfhnVdksIa8etJZLhZPQxSOqY89
44zw34CzWr/Tgu7tI7dnuCeAke5cagFbq2+NFvde/zxh4aXanmHwi6e9tTI8Q/C7
LfxoKYnDCEkuxhfya4z6sGjI3FCE+2GRT7GRTn9FOvI8JAP9YshLWfqnffm3AazH
5bcBpBfaW8LpnwX0ChhsgSN18fmSaDRTbOEw7Ze6TzBinIK8zhWngVos4xYWGyKp
UuNgo41Q8Izn6k5n9gW6kerbdDxTodOAJWyCE1v4lTx1REy0EipBRPipRngpAK7E
e3MJOopb5rblqMsRBF+qIMif+EKPNqf2LC5pzjaG69haL8NXpbRa8wZEXFhUIYOx
V8pAu4RcwxXA09y0KHHps/pwMhNF3jVFGT5mbvQ+ddt8oOnemcjVD/FyN2pdRHrp
E+rWhV4uehdZsRA8+rU103FogOLDlA30u9L3iczf+qvXDBtJHqlk2zz0+JMx0+3M
jPni14Ge2ITvajSYoL5g
=wNHw
-END PGP SIGNATURE-


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xsvfr-0006hq...@franck.debian.org

Processed: Re: Bug#770214: source tarball should not be compressed with xz

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #770214 [debootstrap] source tarball should not be compressed with xz
Added tag(s) pending and patch.

-- 
770214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770214
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: 
https://lists.debian.org/handler.s.b770214.14167440957307.transcr...@bugs.debian.org

Bug#770214: source tarball should not be compressed with xz

[Cyril Brulebois]

Control: tag -1 patch pending

Joey Hess  (2014-11-19):
> Package: debootstrap
> Version: 1.0.64
> Severity: normal
> 
> xz is not a common format, and this makes it unncessarily difficult to
> install debootstrap from source on unfamiliar linux systems. The space
> savings are miniscule. Please switch to a tar.gz.

Thanks for the report, master has a patch:
|  dpkg-source -i -I -b debootstrap
| dpkg-source: info: using options from debootstrap/debian/source/options: 
--compression=gzip
| dpkg-source: info: using source format `3.0 (native)'
| dpkg-source: info: building debootstrap in debootstrap_1.0.65.tar.gz
| dpkg-source: info: building debootstrap in debootstrap_1.0.65.dsc

http://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=777f456324cf4f9f68dbad75853973741aa2872f

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processing of partman-base_180_source.changes

[Debian FTP Masters]

partman-base_180_source.changes uploaded successfully to localhost
along with the files:
  partman-base_180.dsc
  partman-base_180.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xsvym-00045u...@franck.debian.org

Processed: Re: Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #759424 [di-netboot-assistant] di-netboot-assistant: please update package 
for jessie / new syslinux
Added tag(s) moreinfo.

-- 
759424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759424
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: 
https://lists.debian.org/handler.s.b759424.14167434013191.transcr...@bugs.debian.org

Bug#759424: di-netboot-assistant: please update package for jessie / new syslinux

[Cyril Brulebois]

Control: tag -1 moreinfo

Hi Jonas and Andreas,

Jonas Smedegaard  (2014-11-21):
> Package: di-netboot-assistant
> Followup-For: Bug #759424
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Attached is a patch believed to fix all issues related to new syslinux:
> 
>   * Lookup pxelinux.0 in /usr/lib/PXELINUX (not only /usr/lib/syslinux).
>   * Lookup only BIOS binaries (not accidentally include EFI binaries).
>   * Install core modules at tftpd root dir.
>   * Keep vesamenu and menu modules in sync with PXELINUX.

thank you both for providing patches to di-netboot-assistant; is there
any chance you could submit a branch or patch series against its git
repository (git://anonscm.debian.org/d-i/netboot-assistant.git)?

Of course I could try and split up your patches into atomic commits, but
I guess it'd be better if knowledgeable could document patches. There's
of course the part where Andreas had to patch a bit more what Jonas
provided, so cross-checking each other would be nice.

Mraw,
KiBi.

>  - Jonas
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQF8BAEBCgBmBQJUbnZLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
> RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWlDkH/2evg6qc0Jf8Ho/BHtNw8uEZ
> MVMUq4+xD+ziLDSSVKfFCfn17SnypXLxPzDBVQ4SoLv1W6+AnTHs5ExaQ2KzgJZy
> 9qJueFkpDGBY0G6A/IUqjwTEvmN5L0FS4MxjACbswNIlCnkvnlixVnhxNonF5kS5
> q6fkbJ+M9XZNYxaMJN9croUV7KsnOGZhVJg6Rk7Mu3FUv4xzhY3+U0HHV1by2TI3
> H9qNvC1/DVJ/8oGgFgu39G5cDdSMW8kyhebE5r6X+HP7g8zJT4EYIfeaP+gBQO0g
> ZYU0GUw0fshmEKmosXw77EUtvAcXQzfytprDsMEVrP179dTHW1Q5RjfW7ggYrWE=
> =m57Q
> -END PGP SIGNATURE-

> --- di-netboot-assistant.orig 2013-07-13 10:31:11.0 +0200
> +++ di-netboot-assistant  2014-11-20 22:50:18.151437802 +0100
> @@ -200,12 +200,13 @@
>  #  #
>  # find_file()
>  #Return the name of the first file matching criteria.
> -# Parameters: dir name
> +# Parameters: name dir [dir...]
>  # Returns: (STRING) file
>  #  #
>  find_file() {
>   if [ "$1" -a "$2" ]; then
> - find "$2" -type f -name $1 | head -n 1
> + local name=$1; shift
> + find "$@" -type f -name "$name" | head -n 1
>   else
>   echo ""
>   fi
> @@ -241,7 +242,14 @@
>  
>   [ ! "$src" -o ! "$dst" ] && return 1
>  
> - newbin=$(find_file pxelinux.0 "$src" 2>/dev/null)
> + if [ "$SYSLINUX" = "$src" ]; then
> + # avoid recent SYSLINUX EFI binaries incompatible with PXELINUX
> + [ ! -d "$src/modules/bios" ] || src="$src/modules/bios"
> + # recent SYSLINUX ships PXELINUX at separate location
> + newbin=$(find_file pxelinux.0 /usr/lib/PXELINUX "$SYSLINUX" 
> 2>/dev/null)
> + else
> + newbin=$(find_file pxelinux.0 "$src" 2>/dev/null)
> + fi
>   [ ! -f "$dst/pxelinux.0" -a ! -f "$newbin" ] && return 1
>  
>   pxe_new_ver="$(pxelinux_version "$newbin")"
> @@ -253,7 +261,11 @@
>   echo "I: Upgrading PXELinux ($pxe_cur_ver to $pxe_new_ver)"
>  
>   for f in pxelinux.0 menu.c32 vesamenu.c32; do
> - srcf="$(find_file $f "$src")"
> + if [ pxelinux.0 = "$f" ]; then
> + srcf="$newbin"
> + else
> + srcf="$(find_file $f "$src")"
> + fi
>   [ "${f#*c32}" ] || f="pxelinux.cfg/$f"
>   [ -L "$dst/$f" ] && rm "$dst/$f"
>   if [ -f "$srcf" ]; then
> @@ -264,6 +276,13 @@
>   done
>   # Smooth transition to vesamenu
>   [ ! -f "$c32_dir/menu.c32" ] && ln -s "vesamenu.c32" $c32_dir/menu.c32
> + # Add core modules at root (see )
> + if [ "$TFTP_ROOT/debian-installer/" = "$dst" ]; then
> + for f in ldlinux.c32 libcom32.c32 libutil.c32; do
> + srcf="$(find_file $f "$src")"
> + [ -z "$srcf" ] || cp -np "$srcf" "$TFTP_ROOT/$f"
> + done
> + fi
>   return 0
>  }
>  
> @@ -907,6 +926,21 @@
>   if ! copy_syslinux_bin "$expand_dir" "$TFTP_ROOT/debian-installer/" ; 
> then
>   echo "E: No PXELinux menu installed. Please file a bug." 1>&2
>   fi
> + # ensure only a single PXELINUX version is used for all its modules
> + for f in $(find "$expand_dir" -type f -name '*.c32'); do
> + case $(basename "$f") in
> +   vesamenu.c32|menu.c32)
> + cp -pft "$(dirname "$f")" 
> "$TFTP_ROOT/debian-installer/pxelinux.cfg/$(basename "$f")"
> + ;;
> +   ldlinux.c32|libcom32.c32|libutil.c32)
> + cp -pft "$(dirname "$f")" "$TFTP_ROOT/$(basename "$f")"
> + ;;
> +   *)
> + echo "W: Unusual PXELINUX module \"$f\" may not work." 
> 1>&2
> + con

Bug#770666: marked as done (partman-base: partman overwrites parts of u-boot (imx6/am335x))

[Debian Bug Tracking System]

Your message dated Sun, 23 Nov 2014 11:49:25 +
with message-id 
and subject line Bug#770666: fixed in partman-base 180
has caused the Debian Bug report #770666,
regarding partman-base: partman overwrites parts of u-boot (imx6/am335x)
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.)


-- 
770666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: partman-base
Version: 179
Severity: important
Tags: patch

Several armhf platforms have u-boot installed directly to the device
in an area which gets wiped out by partman. This results in
debian-installer producing a "successful" install, but zeros out the
location of the bootloader in the process... so fails to boot.

This was fixed for sunxi/allwinner platforms (see:
https://bugs.debian.org/751704), but other platforms such as imx6
(Wandboard, CuBox-i) and am335x (BeagleBone Black) are still affected
by the issue.

The following proof-of-concept patch may be a little too broad,
affecting all Freescale or AM33XX systems, although it is limited to
installs to /dev/mmcblk0. BeagleBone Black may also need this code
when installing to /dev/mmcblk1...

Essentially it renames the is_sunxi_system to
is_system_with_firmware_on_disk, and adds cases for the additional
platforms.


diff --git a/parted_server.c b/parted_server.c
index 808a85f..e9e72a0 100644
--- a/parted_server.c
+++ b/parted_server.c
@@ -1330,9 +1330,10 @@ command_dump()
 oprintf("OK\n");
 }
 
-/* Check whether we are running on a sunxi-based system. */
+/* Check whether we are running on a sunxi-based, freescale-based, or
+   AM33XX (beaglebone black) system. */
 int
-is_sunxi_system()
+is_system_with_firmware_on_disk()
 {
 int cpuinfo_handle;
 int result = 0;
@@ -1345,6 +1346,10 @@ is_sunxi_system()
 buf[length]='\0';
 if (strstr(buf, "Allwinner") != NULL)
 result = 1;
+else if (strstr(buf, "Freescale") != NULL)
+result = 1;
+else if (strstr(buf, "AM33XX") != NULL)
+result = 1;
 }
 close(cpuinfo_handle);
 }
@@ -1365,9 +1370,9 @@ command_commit()
  * the firmware area, resulting in an unbootable system (see
  * bug #751704).
  */
-if (is_sunxi_system() && !strcmp(disk->dev->path, "/dev/mmcblk0")) {
+if (is_system_with_firmware_on_disk() && !strcmp(disk->dev->path, 
"/dev/mmcblk0")) {
 disk->needs_clobber = 0;
-log("Sunxi platform detected. Disabling ped_disk_clobber " \
+log("Sunxi/Freescale/AM33XX detected. Disabling 
ped_disk_clobber" \
 "for the boot device %s to protect the firmware " \
 "area.", disk->dev->path);
 }


Thanks for considering!

live well,
  vagrant


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: partman-base
Source-Version: 180

We believe that the bug you reported is fixed in the latest version of
partman-base, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 770...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated partman-base package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 Nov 2014 12:38:26 +0100
Source: partman-base
Binary: partman-base partman-utils
Architecture: source
Version: 180
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 partman-base - Partition the storage devices (partman) (udeb)
 partman-utils - Utilities related to partitioning (udeb)
Closes: 770666
Changes:
 partman-base (180) unstable; urgency=low
 .
   * Avoid overwriting the bootloader area on more platforms: detect
 Freescale and AM33XX systems along with Allwinner ones, and disable
 ped_disk_clobber on such systems, when the device is /dev/mmcblk0
 (Closes: #770666). With many thanks to Vagra

Bug#770666: partman-base: partman overwrites parts of u-boot (imx6/am335x)

[Cyril Brulebois]

Vagrant Cascadian  (2014-11-22):
> Package: partman-base
> Version: 179
> Severity: important
> Tags: patch
> 
> Several armhf platforms have u-boot installed directly to the device
> in an area which gets wiped out by partman. This results in
> debian-installer producing a "successful" install, but zeros out the
> location of the bootloader in the process... so fails to boot.
> 
> This was fixed for sunxi/allwinner platforms (see:
> https://bugs.debian.org/751704), but other platforms such as imx6
> (Wandboard, CuBox-i) and am335x (BeagleBone Black) are still affected
> by the issue.
> 
> The following proof-of-concept patch may be a little too broad,
> affecting all Freescale or AM33XX systems, although it is limited to
> installs to /dev/mmcblk0. BeagleBone Black may also need this code
> when installing to /dev/mmcblk1...

I've committed it as-is for now, and uploaded partman-base 180.
debian-arm@ people may want to give daily images a shot once a build has
happened with that version.

Thanks!

Mraw,
KiBi.

> Essentially it renames the is_sunxi_system to
> is_system_with_firmware_on_disk, and adds cases for the additional
> platforms.
> 
> 
> diff --git a/parted_server.c b/parted_server.c
> index 808a85f..e9e72a0 100644
> --- a/parted_server.c
> +++ b/parted_server.c
> @@ -1330,9 +1330,10 @@ command_dump()
>  oprintf("OK\n");
>  }
>  
> -/* Check whether we are running on a sunxi-based system. */
> +/* Check whether we are running on a sunxi-based, freescale-based, or
> +   AM33XX (beaglebone black) system. */
>  int
> -is_sunxi_system()
> +is_system_with_firmware_on_disk()
>  {
>  int cpuinfo_handle;
>  int result = 0;
> @@ -1345,6 +1346,10 @@ is_sunxi_system()
>  buf[length]='\0';
>  if (strstr(buf, "Allwinner") != NULL)
>  result = 1;
> +else if (strstr(buf, "Freescale") != NULL)
> +result = 1;
> +else if (strstr(buf, "AM33XX") != NULL)
> +result = 1;
>  }
>  close(cpuinfo_handle);
>  }
> @@ -1365,9 +1370,9 @@ command_commit()
>   * the firmware area, resulting in an unbootable system (see
>   * bug #751704).
>   */
> -if (is_sunxi_system() && !strcmp(disk->dev->path, "/dev/mmcblk0")) {
> +if (is_system_with_firmware_on_disk() && !strcmp(disk->dev->path, 
> "/dev/mmcblk0")) {
>  disk->needs_clobber = 0;
> -log("Sunxi platform detected. Disabling ped_disk_clobber " \
> +log("Sunxi/Freescale/AM33XX detected. Disabling 
> ped_disk_clobber" \
>  "for the boot device %s to protect the firmware " \
>  "area.", disk->dev->path);
>  }
> 
> 
> Thanks for considering!
> 
> live well,
>   vagrant


signature.asc
Description: Digital signature

Re: Old-timer installer, task-sysvinit?

[Jonas Smedegaard]

[sent again - to proper address this time]

[NB! This post sent to debian-boot - please follow up there]

Quoting Erich Schubert (2014-11-23 09:50:12)
> 1. There is a wide consensus that Debian continues to allow other init 
> systems.
> 2. The installer (currently) does install systemd.
> 3. The installer CAN be used to install sysvinit via preseeding (and
> admins should know how to use preseeding to install systems...)

I believe third point above is inaccurate: Debian-installer has hooks to 
pass hints to packages (debconf preseeding) and hooks to execute shell 
scripts.  What is currently possible is only the latter: Spawn a shell 
script late in the install process to replace init-related packages 
already installed by debian-installer.


Please Cc me, I am not subscribed here.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#770623: Fix Image version URL

[Tarin Gamberini]

In the section:
>-- Package-specific info:>> Boot method: started with DVD ISO then chosen to 
>download packeges 
> from the network> Image version: DVD ISO Image: Debian GNU/Linux 7.6.0 
> _Wheezy_ - Official amd64> DVD Binary-1 20140712-14:11, I guess the url is> 
> http://cdimage.debian.org/cdimage/ar

the URL has been truncated. The correct URL of the "Image version" 
is:http://cdimage.debian.org/cdimage/archive/7.6.0/amd64/iso-dvd/debian-7.6.0-amd64-DVD-1.iso