Re: Are follow-up steps for Lomiri desktop required?

[Mike Gabriel]

On  Mi 22 Mai 2024 17:50:06 CEST, Cyril Brulebois wrote:


Mike Gabriel  (2024-05-22):



The Lomiri Operating Environment packaging for Debian is currently seeing
quite a boot because we have found a sponsor that finance the related work.

  

Good one!


/me grins, s/boot/boost/, of course.

Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgphh1spMpy5v.pgp
Description: Digitale PGP-Signatur

Re: Are follow-up steps for Lomiri desktop required?

[Mike Gabriel]

Hi Roland,
(Cc:ing Guido who also works on Lomiri in Debian with correct now)

On  Mi 22 Mai 2024 16:50:02 CEST, Roland Clobus wrote:


Hello installer team,

I've noticed that (currently as draft) preparations [1] are ongoing  
to add Lomiri as task-lomiri-desktop into task-desktop.


Is it intended to have Lomiri available in the installer and to have  
live images?


If so, it would need some coordination to have it all set up. (I'm  
thinking of d-i, regular builds, openQA, Jenkins, live-build, ...)


With kind regards,
Roland Clobs

[1] https://salsa.debian.org/installer-team/tasksel/-/merge_requests/30/


The plan is indeed to propose Lomiri as possible selection for a  
desktop environment in D-I.


Unfortunately, I don't know what steps are required to get Lomiri in.  
Neither do I know who has a say in this, where it gets decided what  
gets included as installer option in D-I and what not.


The Lomiri Operating Environment packaging for Debian is currently  
seeing quite a boot because we have found a sponsor that finance the  
related work. The overall goal is to have Lomiri available in Debian,  
so we can pre-install a Debian based tablet OS for Debian Edu.


Thanks for picking this up starting the discussion!
Mike (aka sunweaver at d.o)
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpQ4qzUSvBtv.pgp
Description: Digitale PGP-Signatur

Re: Re-planning for 12.6

[Mike Hosken]

Just one thing could you please pull all world wide repos so the repos that are 
new are there and defunct repositories don’t appear. My repositories have been 
registered repositories for years and newer been in one release 
Mike Hosken 
Sent via my iPhone 

> On 3 Apr 2024, at 08:40, Jonathan Wiltshire  wrote:
> 
> On Mon, Apr 01, 2024 at 01:07:27PM +0100, Adam D. Barratt wrote:
>> April 13th
>> April 20th
>> April 27th
> 
> At current progress I expect to be available for the SRM side 13th or 27th.
> We're in a good position to freeze this weekend to make the 13th, if others
> are available then.
> 
> The 20th is a no for me.
> 
>> May 4th
>> May 11th
> 
> Currently OK for me.
> 
> Though as soon as we're heading into the middle of May we might as well
> wait for the next cadence in June.
> 
> --
> Jonathan Wiltshire  j...@debian.org
> Debian Developer http://people.debian.org/~jmw
> 
> 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
> ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
> 

Bug#1008587: installation-reports: dist-upgrade to sid works but autoremove takes out most of the Mate DE

[Mike Thompson]

Package: installation-reports
Severity: important
X-Debbugs-Cc: kneedragon1...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: netinstall-virtualmachine
Image version: debian-11.3.0-amd64-netinst.iso
Date: 

Machine: i7-6700-non-k
Partitions: 


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

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect media:   [ ]
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:

https://www.debian.org/Bugs/Reporting.en.html
.. and I don't know that it is appropriate.
Allow me to explain.
I have a copy of Debian in a virtualbox, on a machine running Mint as the host.
I have converted to sid, so my sources.list looks like ~
--
deb http://ftp.us.debian.org/debian/ sid main
deb-src http://ftp.us.debian.org/debian/ sid main
---
~ I then go sudo apt dist-upgrade, and I get sid, and roughly 1 GB of left-over 
files, and apt encourages me to remove them by ~
sudo apt autoremove
~ all perfectly normal.
What happens next is I can't reboot, I get a TTY.
I can force a startx, but many of my Mate packages are gone.
So an effort to manually reinstall mate, results in a dependency error, the 
version of mate to be installed requires an earlier version of python and you 
can't install that...
I have made a clone of that install before I ran the autoremove and tried 
various fixes but so far I have been stumped.
As long as I don't run the autoremove I have a perfectly functional sid + Mate, 
but there's about a GB of stuff I should be able to autoremove, and I can't...

Sorry this doesn't comply with your format request, but in the circumstances, I 
think an effort to make it fit would simply confuse the problem.

Yours respectfully, Mike Thompson.
.>


Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u3"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung 
GmbH VirtualBox Graphics Adapter [80ee:beef]
lspci -knn: Subsystem: VMware Device [15ad:0405]
lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM 
Gigabit Ethernet Controller [8086:100e] (rev 02)
lspci -knn: Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter 
[8086:001e]
lspci -knn: Kernel driver in use: e1000
lspci -knn: Kernel modules: e1000
lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH 
VirtualBox Guest Service [80ee:cafe]
lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 
82801AA AC'97 Audio Controller [8086:2415] (rev 01)
lspci -knn: Subsystem: Dell Device [1028:0177]
lspci -knn: Kernel driver in use: snd_intel8x0
lspci -knn: Kernel modules: snd_intel8x0
lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB 
[106b:003f]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: Kernel modules: ohci_pci
lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 08)
lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM 
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
usb-list: 
usb-list: Bus 01 Device 01: OHCI PCI host controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.10.0-13-amd64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: USB Tablet [80ee:0021]
usb-list:Level 01 P

Re: Debian CD

[Mike Hosken]

It’s an HP Storageworks P4300 G2 san. I’ve tried different usb sticks and cd 
rom drive. 

I’m guessing it’s a configvodd

 Mike Hosken 
Sent via my iPhone 

> On 5/03/2022, at 08:52, John Paul Adrian Glaubitz 
>  wrote:
> On 3/4/22 20:22, Mike Hosken wrote:
>> It’s a RP4300 G3
> 
> What kind of hardware is that? When I google this, I'm getting results
> for hamradio hand receivers.
> 
> Adrian
> 
> -- 
> .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Debian CD

[Mike Hosken]

Hi team,

I’m trying to install Debian/Linux after a large amount of effort replacing 
drives and fans etc. I configured the raid with no problems using the raid 
card. 

When it comes to installing from usb it boots into the section of what you want 
to install Debian 11.2 official, enter to boot tab for options. 

This is where it gets stuck, and try’s to reboot every 15 seconds to so. Cd 
won’t boot so apart from setting up a bootstrapping from the network. 

It’s a RP4300 G3

Mike Hosken 
Sent via my iPhone 

Bug#995063: os-prober fails to detect partition when the device name is a substring of another device

[Mike]

Package: os-prober
Version: 1.77
Severity: important
Tags: patch

Dear Maintainer,

My system has another linux install located on /dev/sde1, which os-prober 
should detect
There is also a /dev/sde127 which is part of a raid array

In this case, os-prober line 141 incorrectly believes that /dev/sde1 is part of 
a raid array, because
grep -q "^/dev/sde1" $OS_PROBER_TMP/raided-map 
returns true as it matches the /dev/sde127 line.

This can be fixed by changing the line to read
 if grep -q "^$mapped\$" "$OS_PROBER_TMP/raided-map" ; then

Thanks

-- System Information:
Debian Release: 10.10
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages os-prober depends on:
ii  grub-common  2.02+dfsg1-20+deb10u4
ii  libc62.28-10

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information

Bug#991417: simple-cdd generated iso: No kernel modules were found

[Mike Depot]

Package: installation-reports

Boot method: "simple-cdd --qemu-only"
Image version: 5.10.0-7-amd64
Date: 2021-07-22

Machine: qemu kvm, on top of bullseye amd64
Processor: QEMU Virtual CPU version 2.5+ (over i7-6920HQ physical)
Memory: 4G in QEMU (64G physical)

I've been using simple-cdd running on my bullseye host to generate a custom iso 
(also bullseye).  My simple-cdd config had been working fine until a couple 
days ago.  Now I am getting an error early in debian-installer when I boot from 
the generated ISO:

"No kernel modules were found. This probably is due to a mismatch between the 
kernel used by this version of the installer and the kernel version available 
in the archive."

I find that simple-cdd is generating the iso with the following kernel:
Linux ... 5.10.0-7-amd64 #1 SMP Debian 5.10.40.1 (2021-05-28) x86_64 GNU Linux

However the host system (recently apt upgraded) has the following kernel:
Linux ... 5.10.0-8-amd64 #1 SMP Debian 5.10.46.2 (2021-07-20) x86_64 GNU Linux
(note the date on the kernel is only 2 days prior from when I ran into this 
issue)

I am not specifying mirror/codename nor mirror/suite in the preseed that 
simple-cdd is using.  My understanding is this allows debian-installer to 
install whatever version ends up in the generated iso's initrd.  I also tried 
again with these values enabled and set to "bullseye" however the problem 
remained.

Searching for this error I find that other people that have had the same issue 
in the past.  In past bug reports this seems to have been fixed somewhere in 
the distro, so I'm reporting it here.

Since this problem seems to come back every now and again, I'd also like to 
know if there is a workaround that people can put into their simple-cdd config 
to allow things to keep working when the kernels occasionally get out of sync 
like this.  If that's possible, it might be good to mention that workaround 
here, for future searchers.

Thanks!

Publish guest contributions

[mike]

"Hi,

We need an advertising space with do-follow links on your blog  
security-tracker.debian.org.


• We provide 500+ words
• no copy article
• the duration will be a minimum of 1 year

Can you please write to us if possible to place an article with a link  
leading to betting related site and how much it will cost?


Please let me know if you are interested.

Stay safe and healthy.

Regards,
"

Bug#979386: debian-installer: Install Annoyance

[Mike McCulley]

Package: debian-installer
Version: buster
Severity: normal

Dear Maintainer,

I have a triple-boot setup so GRUB and swap both exist, and that creates the
annoyance.

Debian installer displays messages about the necessity of having GRUB
installed, which implies it's possible to not install GRUB, but that option is
not available. After installing Debian it's necessary to boot the primary OS
and reinstall the custom GRUB. Life would be better if there was an option to
skip the 'install GRUB' step.

Debian installer formats swap, which changes the UUID, and not formatting is
not an option. After installing Debian it's necessary to edit any other fstabs
and update the swap UUIDs. Life would be better if there was an option to not
format swap.



-- System Information:
Debian Release: 10.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#726137: Info received (DVD remains locked when requested to switch DVDs during Package Scan)

[Mike Stanton]

It also appears that every time it goes through a package install there is a 
mount message for the DVD Generated which requires a remount of the DVD media 
because it thinks the medisa CHANGED. This can add up to a lot of mount 
messages if you are doing a fresh install. The error happened during 
installations on two  machines, with two different DVD Readers. After a remount 
it appears multiple packages are being loaded so I can only presume that there 
are multiple package requests being submitted behind one mount request.

-Original Message-
From: Debian Bug Tracking System  
Sent: Sunday, October 11, 2020 3:27 PM
To: Mike Stanton 
Subject: Bug#726137: Info received (DVD remains locked when requested to switch 
DVDs during Package Scan)

Thank you for the additional information you have supplied regarding this Bug 
report.

This is an automatically generated reply to let you know your message has been 
received.

Your message is being forwarded to the package maintainers and other interested 
parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Install System Team 

If you wish to submit further information on this problem, please send it to 
726...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish to report a 
problem with the Bug-tracking system.

--
726137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#726137: DVD remains locked when requested to switch DVDs during Package Scan

[Mike Stanton]

I have seen the same problem. It is because the driver for the DVD locks the 
DVD when processing the files and does not unlock it when it asks for the 
volume to be swapped. The workaround is to use a paper clip to manually release 
the media tray for the DVD/CD device.  It is a small hole in the case near the 
DVD Eject button.  Barring that if the device is an External device, cycling 
power on the device will release it. When you put the new media into the tray, 
it will recover the loss of power condition after you issue the next I/O 
request by answering the Swap message.  It appears this message has been out 
there a long time

Michael Stanton
GEOSPAN Corporation
6901 E. Fish Lake Road
Suite 156
Maple Grove, MN  55369
763-493-9320 X5003
651-270-3191 (mobile)
www.geospan.com

Fresh install of Debian 10.2 subject to bug #860533

[Mike Hommey]

Hi,

I wasn't sure where to report this, so I'm shooting here.

I recently installed Debian 10.2 on a new machine, and went with manual
partitioning, putting the swap on an encrypted mdraid with a random key,
and the result is that booting the system would have a very large delay
on boot.

In recovery mode (or normal more without quiet on the kernel command
line), I was able to see a loop of messages saying "Running
/scripts/local-block ... done", which led me to find bug #860533, and it
turns out the problem was related: something in the installer had filled
/etc/initramfs-tools/conf.d/resume with "RESUME=/dev/mapper/md2_crypt",
and that doesn't work, which makes sense considering the random key.

Arguably, the initramfs hooks should probably complain about this setup
too, but it seems the installer should also avoid creating it in the
first place.

Cheers,

Mike

Bug#851189: keyboard-configuration: ALT+Cursor-Left switches consoles instead of working on app in focus

[Mike McGuire]

It's a xenial chroot and it indeed doesn't have that test in 
keyboard-configuration.postinst. Perhaps just an ubuntu issue then, sorry for 
the noise. ;-)

Bug#851189: keyboard-configuration: ALT+Cursor-Left switches consoles instead of working on app in focus

[Mike McGuire]

Hi again. In short I kind of just copied that post blindly and only now looked 
into things further.

> Mmm, do you mean that this postinst script ends up calling setupcon
> --force --save in a living Ubuntu system, not the installer of Ubuntu?

> The script checks for the presence of the /lib/debian-installer.d
> directory, does that directory really exist in an installed Ubuntu
> system?  If so, that's the problem, that directory shouldn't exist on an
> installed system.

>> To reproduce:
>> sudo apt install --reinstall keyboard-configuration

> That doesn't trigger the issue on an installed Debian system (which
> doesn't have /lib/debian-installer.d).

I did just try this myself and you're right, this didn't trigger it. Which got 
me to think more of what could have and I did recently build wine in an ubuntu 
chroot which is a plausible cause, I think?

Bug#851189: keyboard-configuration: ALT+Cursor-Left switches consoles instead of working on app in focus

[Mike McGuire]

This started happening to me recently, not sure what change could be to blame 
but I found a lengthy thread on the ubuntu bug tracker that seems to confirm 
things. Copying the relevant post: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/comments/66

---

In my case, I traced the issue to the keyboard-configuration package postinst 
script, which ends up calling 'setupcon --force --save' which in turn calls 
'kbd_mode -u'

To reproduce:
sudo apt install --reinstall keyboard-configuration

setupcon documentation states:
"--force Do not check whether we are on the console. Notice that you can be 
forced to hard-reboot your computer if you run setupcon with this option and 
the screen is controlled by a X server."

It looks like the checks to avoid this behavior while a graphic environment is 
active don't work in the context of the installer.

---

In any case they've found 'sudo kbd_mode -s' to be a workaround.

Bug#798772: Ahoj kamaráde

[Curtis Mike Scaparrotti]

Ahoj kamaráde,
Jsem generál Curtis M. Scaparrotti. Generální státní americká armáda ze 
Spojených států amerických. Jsem pečující a podpůrný člověk, který hledá 
přítele, aby vytvořil vzájemný vztah. Prosím, odpovězte mi na další diskusi, 
pokud máte zájem.
S přátelským pozdravem.

GEN. CURTIS M. SCAPARROTTI.

Re: Curious case of /lib/libkmod.so.2

[Mike Purvis]

Small update here. I broke out of the make run and manually invoked
mklibs-copy in verbose mode. It turns out that libkmod.so.2 does it fact
get copied out of the /lib directory on the system being used to construct
the initrd (I guess I must have had that package installed after all). See
the highlighted line in the mklibs-copy output here:

https://gist.github.com/mikepurvis/a7182157f63ea01649cfca01a57f1068#file-mklibs-copy-L275

The same thing happens with libslang.so.2, a few lines further down.

This behaviour seems very odd and undesirable to me— wouldn't it break the
ability to generate an installer for a different architecture? These
libraries should be coming from libkmod2-udeb and libslang2-udeb,
respectively, right? Should there be a bug filed for this?

Mike

On 15 March 2018 at 16:17, Mike Purvis <mpur...@clearpath.ai> wrote:

> Hi d-i developers,
>
> I'm working on an bootloader/installer system for some industrial
> equipment. Until now, my main interaction with d-i has been grabbing the
> pre-cooked kernel/initrds from Debian or Ubuntu, and tacking on a few extra
> files to the tail of the initrd, like preseed, scripts, and an extra udeb
> or two.
>
> However, I've come to a place where I'd like to have more control over
> some things (incl exact kernel version) and so I want to generate my own
> initrd with just the particular udebs I require. I'm basing most of my work
> on the Makefile here, which details downloading a dependency tree of
> packages, and creating a bare bones dpkg setup into which they are
> installed:
>
> https://anonscm.debian.org/git/d-i/debian-installer.git/
> tree/build/Makefile#n308
>
> My system actually mostly works, but one key file I'm missing is
> /lib/libkmod.so.2. This file isn't contained within any of the udebs
> (libkmod2-udeb is just a multi-call binary with no libs), and in fact a
> little tracing reveals that it springs into existence as a result of the
> mklibs-copy call which happens here:
>
> https://anonscm.debian.org/git/d-i/debian-installer.git/
> tree/build/Makefile#n526
>
> Without this lib, systemd-udevd fails to link at runtime (called by the
> init script), and the kernel panics shortly after boot.
>
> So my main question is, what is going on with the mklibs-copy call? Where
> are the contents of libkmod.so.2 coming from? They're byte-for-byte
> identical with the copy in the libkmod2 package, but in a different
> location, and I don't even have that package installed.
>
> I'm sure there's some silly explanation here that I'm just not seeing, but
> a I think I need a poke in the right direction to get there. Thanks,
>
> Mike
>

Curious case of /lib/libkmod.so.2

[Mike Purvis]

Hi d-i developers,

I'm working on an bootloader/installer system for some industrial
equipment. Until now, my main interaction with d-i has been grabbing the
pre-cooked kernel/initrds from Debian or Ubuntu, and tacking on a few extra
files to the tail of the initrd, like preseed, scripts, and an extra udeb
or two.

However, I've come to a place where I'd like to have more control over some
things (incl exact kernel version) and so I want to generate my own initrd
with just the particular udebs I require. I'm basing most of my work on the
Makefile here, which details downloading a dependency tree of packages, and
creating a bare bones dpkg setup into which they are installed:

https://anonscm.debian.org/git/d-i/debian-installer.git/tree/build/Makefile#n308

My system actually mostly works, but one key file I'm missing is
/lib/libkmod.so.2. This file isn't contained within any of the udebs
(libkmod2-udeb is just a multi-call binary with no libs), and in fact a
little tracing reveals that it springs into existence as a result of the
mklibs-copy call which happens here:

https://anonscm.debian.org/git/d-i/debian-installer.git/tree/build/Makefile#n526

Without this lib, systemd-udevd fails to link at runtime (called by the
init script), and the kernel panics shortly after boot.

So my main question is, what is going on with the mklibs-copy call? Where
are the contents of libkmod.so.2 coming from? They're byte-for-byte
identical with the copy in the libkmod2 package, but in a different
location, and I don't even have that package installed.

I'm sure there's some silly explanation here that I'm just not seeing, but
a I think I need a poke in the right direction to get there. Thanks,

Mike

Bug#888709: debootstrap: Silently fails if the target directory exists and is not empty.

[Mike Hommey]

Package: debootstrap
Version: 1.0.89
Severity: normal

Dear Maintainer,

I was running sbuild-createchroot, and it failed with:
I: Chosen extractor for .deb packages: dpkg-deb
I: Extracting libacl1...
E: Error running debootstrap at /usr/sbin/sbuild-createchroot line 268.

Turns out that was happening because the target directory existed and
was not empty.

But neither debootstrap nor sbuild-createchroot printed out something
useful. Debootstrap surely shouldn't fail without saying what went
wrong.

Mike

Fwd: Headless installer boot

[Mike Hosken]

Also implement the serial console as primary console after installation. 

Mike Hosken

Sent from my iPhone

Begin forwarded message:

> From: Mike Hosken <m...@purple-cat.net>
> Date: 17 January 2018 at 22:17:51 NZDT
> To: debian-boot@lists.debian.org
> Subject: Headless installer boot
> 
> Hi Team,
> 
> Just a quick question I wish to use serial port as console to install 
> servers. I’m not familiar with grub etc as I’ve only ever used palo. Could 
> someone point me in the right direction as to implement console=/dev/ttys0, 
> for the AMD64 port and I386. I assume it would be a change when building the 
> install media. 
> 
> Mike Hosken
> 
> Sent from my iPhone

Headless installer boot

[Mike Hosken]

Hi Team,

Just a quick question I wish to use serial port as console to install servers. 
I’m not familiar with grub etc as I’ve only ever used palo. Could someone point 
me in the right direction as to implement console=/dev/ttys0, for the AMD64 
port and I386. I assume it would be a change when building the install media. 

Mike Hosken

Sent from my iPhone

Thanks for your help

[Mike Hosken]

After some good help, I've managed to bend the stable debian-installer into 
compiling for the hppa arch. 

There were a few changes made to the config files and debian rules files to 
enable to an unofficial build based off my unofficial repo. 

I am very thankful for the constructive advise given by Jose which was 
priceless. 

Thanks
Mike Hosken

> 
>> On Tue, Jul 18, 2017 at 3:24 PM, Mike Hosken <mik...@csystems.co.nz> wrote:
>> Thank you for you assistance. I'll give these a try and get back to you.
>> 
>> Mike Hosken
>> 
>> Sent from my iPhone
>> 
>> On 18/07/2017, at 22:32, Jose R R <jose@metztli-it.com> wrote:
>> 
>> On Mon, Jul 17, 2017 at 1:20 PM, Mike Hosken <mik...@csystems.co.nz> wrote:
>> 
>> Let's try this again.
>> 
>> 
>> I am trying to build stable install images for HPPA. I have built 'sid'
>> 
>> images previously from Debian ports.
>> 
>> 
>> The troubles I'm having is when I build the installer -
>> 
>> 
>> It says while building that my mirror appears invalid and will not use it.
>> 
>> 
>> When using the git checkout it gives two errors while building. The invalid
>> 
>> mirror and it's the wrong kernel, as in not the stable but testing.
>> 
>> 
>> I am hoping someone can help me with these questions.
>> 
>> 
>> Is there a git repo for the stable installer ?  If so how do I check it out
>> 
>> As far as I know, git is only for unstable Debian-Installer (d-i)
>> 
>> ? Or do I use the source package in stretch.
> *also*
> To wean out any potential Debian-Installer (d-i) dependencies
> errors/issues, please do as below commands:
> 
> apt-get install debian-installer
> apt-get build-dep debian-installer
> 
> then (if not already there) cd to your d-i directory created at your
> file system location where you executed:
> apt-get source debian-installer
> 
> and do:
> dpkg-checkbuilddeps
> 
> Install any dependencies output to your screen and...
> 
> repeat above command until there are no more dependency issues.
> 
> References:
> < https://wiki.debian.org/DebianInstaller/Build >
> 
> Additionally, please consider the use of a virtual machine where to
> test your images; it allows peeking inside the installer environment
> to check/verify what's going on. tty CTRL +ALT + F4 (in Linux/AMD64 --
> but I don't know in HPPA) will output useful info, giving you hints on
> what snags may prevent success of your d-i effort.
>> 
>> If you are building on *and* for (stable) Stretch on HPPA,
>> 
>> apt-get update
>> apt-get source -d debian-installer
>> 
>> 
>> What changes do I need to make ( in the source code) to get Debian-Installer
>> 
>> when building to trust my unofficial but signed repo to download the udebs
>> 
>> etc.
>> 
>> Please look in
>> d-i/build/config/common
>> 
>> OR (dirty but works)
>> 
>> If you are only downloading your kernel & modules you may do a hack in
>> source of:
>> < https://packages.debian.org/stretch/base-installer >
>> and rebuild the udeb(s) and place them under
>> d-i/build/localudebs/
>> 
>> Might also work (have not tested) by
>> 
>> doing a hack in source -- by adding your mirror to be listed:
>> < https://packages.debian.org/stretch/choose-mirror >
>> and rebuild the udeb(s) and place them under
>> d-i/build/localudebs/
>> 
>> *Add* name of created UDEBs in proper format into list:
>> 
>> d-i/build/pkg-lists/[directory image]/*cfg
>> 
> []
> Good Luck!
> 
> 
> Best Professional Regards.
> 
> -- 
> Jose R R
> http://metztli.it
> -----
> Download Metztli Reiser4: Debian Stretch with Linux 4.11
> -
> for AMD64 https://sf.net/projects/metztli-reiser4/
> -
> Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
> -
> from our GitHub http://Nepohualtzintzin.comrepository. Cloud the easy way!

Mike Hosken

Sent from my iPhone

Debian installer.

[Mike Hosken]

Let's try this again. 

I am trying to build stable install images for HPPA. I have built 'sid' images 
previously from Debian ports. 

The troubles I'm having is when I build the installer -

It says while building that my mirror appears invalid and will not use it. 

When using the git checkout it gives two errors while building. The invalid 
mirror and it's the wrong kernel, as in not the stable but testing. 

I am hoping someone can help me with these questions. 

Is there a git repo for the stable installer ?  If so how do I check it out ? 
Or do I use the source package in stretch. 

What changes do I need to make ( in the source code) to get Debian-Installer 
when building to trust my unofficial but signed repo to download the udebs etc. 

Also what changes do I need to make again to source code to specify the kernel 
in my repo. 

Any constructive advice would be appreciated. 

Mike Hosken

Sent from my iPhone

Re: Building Debian installer error

[Mike Hosken]

Mike Hosken

Sent from my iPhone

> On 17/07/2017, at 23:13, Geert Stappers <stapp...@stappers.nl> wrote:
> 
>> On Sun, Jul 16, 2017 at 09:16:09PM +1200, Mike Hosken wrote:
>> Hi, 
>> 
>> I'm trying to build debian-installer-20170615 for hppa
>> 
>> I'm getting an error stating mirror appears to be invalid ; skipping. 
>> 
>> This makes the build fail as it can't download the udebs etc. 
>> 
>> How do I get Debian installer to trust my mirror?  The mirror unofficial
>> but is signed and has had the key added to apt via apt key. Apt has
>> no errors.
>> 
>> Also is there a git repo for the stable installer instead of d/i,
>> if so how would one check it out. 
> 
> https://wiki.debian.org/DebianInstaller/CheckOut 

This was the method I used to create hppa cds. So my question is where in the 
code do I tell it what kernel to use and how do I get it to trust my repo. 

Thanks for some assistance. 

Mike
> 
>> I don't have much experience with Debian-Installer
> 
> Advise: Start with getting experience on popular architecture,
> pick exoctic architectures like hppa when more experiencement.
> 
>> so any help would be appreciated. 
> 
> Advise: Avoid retransmits
> 
> In case you think a message wasn't seen, was lost in transmission,
> then tell it is a retransmit. Karma bonus points for telling
> about the progress since the previous transmit.
> 
> 
> Groeten
> Geert Stappers
> -- 
> Leven en laten leven
> 

Building Debian installer error

[Mike Hosken]

Hi, 

I'm trying to build debian-installer-20170615 for hppa

I'm getting an error stating mirror appears to be invalid ; skipping. 

This makes the build fail as it can't download the udebs etc. 

How do I get Debian installer to trust my mirror?  The mirror unofficial but is 
signed and has had the key added to apt via apt key. Apt has no errors. 

Also is there a git repo for the stable installer instead of d/i, if so how 
would one check it out. 

I don't have much experience with Debian-Installer so any help would be 
appreciated. 

Mike Hosken

Sent from my iPhone

Building Debian installer error

[Mike Hosken]

Hi, 

I'm trying to build debian-installer-20170615 for hppa

I'm getting an error stating mirror appears to be invalid ; skipping. 

This makes the build fail as it can't download the udebs etc. 

How do I get Debian installer to trust my mirror?  The mirror unofficial but is 
signed and has had the key added to apt via apt key. Apt has no errors. 

Also is there a git repo for the stable installer instead of d/i, if so how 
would one check it out. 

I don't have much experience with Debian-Installer so any help would be 
appreciated. 

Mike Hosken

Sent from my iPhone

Building Debian installer

[Mike Hosken]

Mike Hosken

Sent from my iPhone

Bug#688336: os-probe: subvol: patches to provide bootloaders with all the subvolume info.

[Mike Mestnik]

These patches can be tested from here:
https://launchpad.net/~cheako/+archive/ubuntu/boot-subvol
Code from here:
https://github.com/cheako/os-prober/tree/aggregate

Bug#688336: os-probe: subvol: patches to provide bootloaders with all the subvolume info.

[Mike Mestnik]

Here are corrected versions of these patches.  Filesystem raid is
almost certainly a separate bug.
From 3d4b580dea4592793af3411fc0543af36de0e958 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Fri, 9 Jun 2017 13:04:05 -0500
Subject: [PATCH 2/6] Process filesystem raid entries

---
 common.sh | 14 --
 os-prober |  5 +
 2 files changed, 17 insertions(+), 2 deletions(-)

diff --git a/common.sh b/common.sh
index e1646d4..d6fee58 100644
--- a/common.sh
+++ b/common.sh
@@ -146,12 +146,22 @@ is_dos_extended_partition() {
 	return 1
 }
 
+canonical_dev () {
+	local dev="${1#/dev/}"
+	local sys="$(find /sys/fs/btrfs -path \*/devices/"$dev")"
+	if [ -e "$sys" ]; then
+		echo /dev/"$(ls "${sys%/$dev}" | head -n1)"
+	else
+		echo "$1"
+	fi
+}
+
 parse_proc_mounts () {
 	while read -r line; do
 		set -f
 		set -- $line
 		set +f
-		printf '%s %s %s\n' "$(mapdevfs "$1")" "$2" "$3"
+		printf '%s %s %s\n' "$(canonical_dev "$(mapdevfs "$1")")" "$2" "$3"
 	done
 }
 
@@ -245,7 +255,7 @@ linux_mount_boot () {
 fi
 			fi
 			shift
-			set -- "$(mapdevfs "$tmppart")" "$@"
+			set -- "$(canonical_dev "$(mapdevfs "$tmppart")")" "$@"
 
 			if grep -q "^$1 " "$OS_PROBER_TMP/mounted-map"; then
 bindfrom="$(grep "^$1 " "$OS_PROBER_TMP/mounted-map" | head -n1 | cut -d " " -f 2)"
diff --git a/os-prober b/os-prober
index a48863e..e4439a7 100755
--- a/os-prober
+++ b/os-prober
@@ -137,6 +137,11 @@ for partition in $(partitions); do
 		continue
 	fi
 
+	if ! [ "$mapped" = "$(canonical_dev "$mapped")" ]; then
+		log "Device '$mapped' is part of filesystem raid; skipping"
+		continue
+	fi
+
 	# Skip partitions used in software RAID arrays
 	if grep -q "^$mapped" "$OS_PROBER_TMP/raided-map" ; then
 		debug "$partition: part of software raid array"
-- 
2.11.0

From bd6d7a78e88eba3a03940e84f6e168ab5c8d Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:08:42 -0500
Subject: [PATCH 5/6] Pass subvol data for /boot to bootloadter(s)

---
 common.sh   | 36 +
 linux-boot-prober   |  6 +++--
 linux-boot-probes/common/50mounted-tests|  3 ++-
 linux-boot-probes/mounted/common/40grub2|  3 ++-
 linux-boot-probes/mounted/common/90fallback |  5 ++--
 linux-boot-probes/mounted/powerpc/40yaboot  |  3 ++-
 linux-boot-probes/mounted/sparc/50silo  |  3 ++-
 linux-boot-probes/mounted/x86/40grub|  3 ++-
 linux-boot-probes/mounted/x86/50lilo|  3 ++-
 9 files changed, 55 insertions(+), 10 deletions(-)

diff --git a/common.sh b/common.sh
index 1001c74..ff278c3 100644
--- a/common.sh
+++ b/common.sh
@@ -253,6 +253,42 @@ linux_mount_boot () {
 			shift
 			set -- "$(mapdevfs "$tmppart")" "$@"
 
+			if bootsubvolid="$(echo "$4" | grep -o 'subvolid=[0-9][0-9]*')"; then
+bootsubvolid="$(echo "$bootsubvolid" | cut -d= -f2-)"
+if mount -o "subvolid=$bootsubvolid" "$1" "$tmpmnt/boot"; then
+	if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+		mountboot="$1 1"
+		return
+	else
+		mountboot="$1 1 $bootsubvolid"
+		return
+	fi
+else
+	debug "failed to subvolid-mount $1 onto $tmpmnt/boot"
+	mountboot="$1 0 $bootsubvolid"
+	return
+fi
+			else
+if bootsubvol="$(echo "$4" | grep -o 'subvol=[^,]*')"; then
+	bootsubvol="$(echo "$bootsubvol" | cut -d= -f2-)"
+	bootsubvol="${bootsubvol#/}"
+	if mount -o "subvol=${bootsubvol:=/}" "$1" "$tmpmnt/boot"; then
+		bootsubvolid="$(grep "^/dev/" /proc/mounts | parse_proc_mounts | grep " $tmpmnt/boot " | cut -d ' ' -f 4)"
+		if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+			mountboot="$1 1"
+			return
+		else
+			mountboot="$1 1 ${bootsubvolid:-@$bootsubvol}"
+			return
+		fi
+	else
+		debug "failed to subvol-mount $1 onto $tmpmnt/boot"
+		mountboot="$1 0 @$bootsubvol"
+		return
+	fi
+fi
+			fi
+
 			if grep -q "^$1 " "$OS_PROBER_TMP/mounted-map"; then
 bindfrom="$(grep "^$1 " "$OS_PROBER_TMP/mounted-map" | head -n1 | cut -d " " -f 2)"
 bindfrom="$(unescape_mount "$bindfrom")"
diff --git a/linux-boot-prober b/linux-boot-prober
index 4a86119..ae34670 100755
--- a/linux-boot-prober
+++ b/linux-boot-prober
@@ -36,19 +36,21 @@ else
 	mpoint="$(unescape_mount "$mpoint")"
 	if [ "$mpoint" != "/target/boot" ] && [ "$mpoint" != "/target" ] && [ "$mpoint" != "/" ]; then
 		type="$(echo "$mrecord" | head -n1 | cut -d ' ' -f 3)"
-		if ! grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map"; then
+		if ! bootrecord="$(grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map")"; then
 			linux_mount_boot "$partition" "$mpoint" "$subvolid"
 			set -- $mountboot
 			bootpart="$1"
 			bootmounted="$2"
+			bootsubvolid="$3"
 		else
 			bootpart="$partition"
 			bootmounted=0
+			bootsubvolid="$(echo "$bootrecord" | head -n1 | cut -d ' ' -f 4)"
 		

Bug#864246: os-probe: Also skip over bcache partitions.

[Mike Mestnik]

Here is an updated copy of this patch.
From 6439f5a40bd4e610a462292c646098eeb4d5bcb1 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:52:17 -0500
Subject: [PATCH 1/6] Add in bcache devices

---
 linux-boot-probes/common/50mounted-tests |  3 +++
 os-prober| 10 ++
 os-probes/common/50mounted-tests |  3 +++
 3 files changed, 16 insertions(+)

diff --git a/linux-boot-probes/common/50mounted-tests b/linux-boot-probes/common/50mounted-tests
index ad68874..937553a 100755
--- a/linux-boot-probes/common/50mounted-tests
+++ b/linux-boot-probes/common/50mounted-tests
@@ -25,6 +25,9 @@ elif [ "$types" = swap ]; then
 elif [ "$types" = crypto_LUKS ]; then
 	debug "$1 is a LUKS partition; skipping"
 	exit 0
+elif [ "$types" = bcache ]; then
+	debug "$1 is an bcache partition; skipping"
+	exit 0
 elif [ "$types" = ntfs ]; then
 	if type ntfs-3g >/dev/null 2>&1; then
 		types='ntfs-3g ntfs'
diff --git a/os-prober b/os-prober
index a48863e..ab2dee1 100755
--- a/os-prober
+++ b/os-prober
@@ -45,6 +45,16 @@ partitions () {
 			fi
 		done
 
+		# bcahce
+		for part in /sys/block/bcache*; do
+			if [ -f "$part/inflight" ]; then
+name="$(echo "${part##*/}" | sed 's,[!.],/,g')"
+if [ -e "/dev/$name" ]; then
+	echo "/dev/$name"
+fi
+			fi
+		done
+
 		# Add Serial ATA RAID devices
 		if type dmraid >/dev/null 2>&1 && \
 		   dmraid -s -c >/dev/null 2>&1; then
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index fca15cb..09c88b3 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -27,6 +27,9 @@ elif [ "$types" = crypto_LUKS ]; then
 elif [ "$types" = LVM2_member ]; then
 	debug "$1 is an LVM member; skipping"
 	exit 0
+elif [ "$types" = bcache ]; then
+	debug "$1 is an bcache partition; skipping"
+	exit 0
 elif [ "$types" = ntfs ]; then
 	if type ntfs-3g >/dev/null 2>&1; then
 		types='ntfs-3g ntfs'
-- 
2.11.0

Bug#688336: os-probe: subvol: patches to provide bootloaders with all the subvolume info.

[Mike Mestnik]

Using these patches reveals they are not complete, there are two areas
that need to be addressed.

Firstly the kernel can and will use any device in a filesystem for the
contents of /proc/mount.  This causes problems in multiple areas that
os-probe will have to compensate for.

Second 50mounted-tests was not updated at all, so these patches only
work if the subvolume is mounted and you don't encounter the first
issue.

Bug#864181: Fwd: Bug#864181: os-prober: dmraid detection not functional.

[Mike Mestnik]

In that case the proposed patch is wrong, dmraid is run every time the
file exists.  Not only is the conditional in test wrong, but the file
is created when it should be being removed.

Bug#688336: os-probe: subvol: patches to provide bootloaders with all the subvolume info.

[Mike Mestnik]

Hello,
  This is the result of several days working the issues and analysing
each aspect.  These patches include only what is necessary to support
subvol.  Care has been taken to future proof by preparing for other
filesystems, currently this only works with btrfs.  These patches have
been split, solving four main goals.

1. Scan btrfs filesystems only once, regardless of how many devices they span.
2. Report to the bootloader the existence of OS lurking on subvolumes.
3. Add option to linux-boot-prober for subvolume and output
appropriate rootoptions.
4. Tell bootloader about boot filesystems on a subvolume.

1 is simple and can be applied with no changes to the bootloader.

2 extends the output of os-prober to support subvolumes. Existing
bootloaders should ignore these records as the key was changed from
linux to linux-subvol and the device is listed as device@subvolid.

3 requires the bootloader to be patched to support the above
linux-subvol records.  It should be a noop for bootloaders that don't
pass a subvolid as the second parameter to linux-boot-prober.

4 I would hold off on, it requires the bootloader to support
subvolumes and I think it's ok to restrict the boot device to
non-subvolumes until such support is added.
From c37c722edba11566ce4bd73e80120b56a37dfa37 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:08:42 -0500
Subject: [PATCH 4/4] Pass subvol data for /boot to bootloadter(s)

---
 common.sh   | 36 +
 linux-boot-prober   |  6 +++--
 linux-boot-probes/mounted/common/40grub2|  3 ++-
 linux-boot-probes/mounted/common/90fallback |  5 ++--
 linux-boot-probes/mounted/powerpc/40yaboot  |  3 ++-
 linux-boot-probes/mounted/sparc/50silo  |  3 ++-
 linux-boot-probes/mounted/x86/40grub|  3 ++-
 linux-boot-probes/mounted/x86/50lilo|  3 ++-
 8 files changed, 53 insertions(+), 9 deletions(-)

diff --git a/common.sh b/common.sh
index 1001c74..ff278c3 100644
--- a/common.sh
+++ b/common.sh
@@ -253,6 +253,42 @@ linux_mount_boot () {
 			shift
 			set -- "$(mapdevfs "$tmppart")" "$@"
 
+			if bootsubvolid="$(echo "$4" | grep -o 'subvolid=[0-9][0-9]*')"; then
+bootsubvolid="$(echo "$bootsubvolid" | cut -d= -f2-)"
+if mount -o "subvolid=$bootsubvolid" "$1" "$tmpmnt/boot"; then
+	if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+		mountboot="$1 1"
+		return
+	else
+		mountboot="$1 1 $bootsubvolid"
+		return
+	fi
+else
+	debug "failed to subvolid-mount $1 onto $tmpmnt/boot"
+	mountboot="$1 0 $bootsubvolid"
+	return
+fi
+			else
+if bootsubvol="$(echo "$4" | grep -o 'subvol=[^,]*')"; then
+	bootsubvol="$(echo "$bootsubvol" | cut -d= -f2-)"
+	bootsubvol="${bootsubvol#/}"
+	if mount -o "subvol=${bootsubvol:=/}" "$1" "$tmpmnt/boot"; then
+		bootsubvolid="$(grep "^/dev/" /proc/mounts | parse_proc_mounts | grep " $tmpmnt/boot " | cut -d ' ' -f 4)"
+		if [ "$bootsubvolid" = "$(get_default_subvolid "$tmpmnt/boot")" ]; then
+			mountboot="$1 1"
+			return
+		else
+			mountboot="$1 1 ${bootsubvolid:-@$bootsubvol}"
+			return
+		fi
+	else
+		debug "failed to subvol-mount $1 onto $tmpmnt/boot"
+		mountboot="$1 0 @$bootsubvol"
+		return
+	fi
+fi
+			fi
+
 			if grep -q "^$1 " "$OS_PROBER_TMP/mounted-map"; then
 bindfrom="$(grep "^$1 " "$OS_PROBER_TMP/mounted-map" | head -n1 | cut -d " " -f 2)"
 bindfrom="$(unescape_mount "$bindfrom")"
diff --git a/linux-boot-prober b/linux-boot-prober
index c53f05d..ba1a0bf 100755
--- a/linux-boot-prober
+++ b/linux-boot-prober
@@ -36,19 +36,21 @@ else
 	mpoint="$(unescape_mount "$mpoint")"
 	if [ "$mpoint" != "/target/boot" ] && [ "$mpoint" != "/target" ] && [ "$mpoint" != "/" ]; then
 		type=$(echo "$mrecord" | head -n1 | cut -d " " -f 3)
-		if ! grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map"; then
+		if ! bootrecord="$(grep -q " $mpoint/boot " "$OS_PROBER_TMP/mounted-map")"; then
 			linux_mount_boot "$partition" "$mpoint"
 			set -- $mountboot
 			bootpart="$1"
 			bootmounted="$2"
+			bootsubvolid="$3"
 		else
 			bootpart="$partition"
 			bootmounted=0
+			bootsubvolid="$(echo "$bootrecord" | head -n1 | cut -d ' ' -f 4)"
 		fi
 		for test in /usr/lib/linux-boot-probes/mounted/*; do
 			if [ -f $test ] && [ -x $test ]; then
 debug "running $test on mounted $partition"
-if $test "$partition" "$bootpart" "$mpoint" "$type" "$subvolid"; then
+if $test "$partition" "$bootpart" "$mpoint" "$type" "$subvolid" "$bootsubvolid"; then
 	debug "$test succeeded"
 	break
 fi
diff --git a/linux-boot-probes/mounted/common/40grub2 b/linux-boot-probes/mounted/common/40grub2
index 9d0b48c..06b8744 100755
--- a/linux-boot-probes/mounted/common/40grub2
+++ b/linux-boot-probes/mounted/common/40grub2
@@ -7,6 +7,7 @@ bootpart="$2"
 mpoint="$3"
 type="$4"
 

Bug#864181: Fwd: Bug#864181: os-prober: dmraid detection not functional.

[Mike Mestnik]

This does look better, I love the use of operators over if statements.
I don't think using a temp file is necessary here.  I also wish the
regex wouldn't ever match a device containing the name of another
device, in that it should match the surrounding bits.

{ dmraid -r -c 2>/dev/null || true } | grep -q "$device" && return 0

Bug#864246: os-probe: Also skip over bcache partitions.

[Mike Mestnik]

This patch also adds bcache to list of partitions types to skip.

Note that linux-boot-probes/common/50mounted-tests is missing
LVM2_member from said list.
From 6439f5a40bd4e610a462292c646098eeb4d5bcb1 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:52:17 -0500
Subject: [PATCH] Add in bcache devices

---
 linux-boot-probes/common/50mounted-tests |  3 +++
 os-prober| 10 ++
 os-probes/common/50mounted-tests |  3 +++
 3 files changed, 16 insertions(+)

diff --git a/linux-boot-probes/common/50mounted-tests b/linux-boot-probes/common/50mounted-tests
index ad68874..937553a 100755
--- a/linux-boot-probes/common/50mounted-tests
+++ b/linux-boot-probes/common/50mounted-tests
@@ -25,6 +25,9 @@ elif [ "$types" = swap ]; then
 elif [ "$types" = crypto_LUKS ]; then
 	debug "$1 is a LUKS partition; skipping"
 	exit 0
+elif [ "$types" = bcache ]; then
+	debug "$1 is an bcache partition; skipping"
+	exit 0
 elif [ "$types" = ntfs ]; then
 	if type ntfs-3g >/dev/null 2>&1; then
 		types='ntfs-3g ntfs'
diff --git a/os-prober b/os-prober
index a48863e..ab2dee1 100755
--- a/os-prober
+++ b/os-prober
@@ -45,6 +45,16 @@ partitions () {
 			fi
 		done
 
+		# bcahce
+		for part in /sys/block/bcache*; do
+			if [ -f "$part/inflight" ]; then
+name="$(echo "${part##*/}" | sed 's,[!.],/,g')"
+if [ -e "/dev/$name" ]; then
+	echo "/dev/$name"
+fi
+			fi
+		done
+
 		# Add Serial ATA RAID devices
 		if type dmraid >/dev/null 2>&1 && \
 		   dmraid -s -c >/dev/null 2>&1; then
diff --git a/os-probes/common/50mounted-tests b/os-probes/common/50mounted-tests
index fca15cb..09c88b3 100755
--- a/os-probes/common/50mounted-tests
+++ b/os-probes/common/50mounted-tests
@@ -27,6 +27,9 @@ elif [ "$types" = crypto_LUKS ]; then
 elif [ "$types" = LVM2_member ]; then
 	debug "$1 is an LVM member; skipping"
 	exit 0
+elif [ "$types" = bcache ]; then
+	debug "$1 is an bcache partition; skipping"
+	exit 0
 elif [ "$types" = ntfs ]; then
 	if type ntfs-3g >/dev/null 2>&1; then
 		types='ntfs-3g ntfs'
-- 
2.11.0

Bug#864246: os-prober: Add bcache support.

[Mike Mestnik]

Package: os-prober
Version: 1.75
Severity: normal
Tags: patch

Looks like bcache devices are not detected.

- -- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable'), (490, 'testing'), (480, 'unstable'),
(470, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages os-prober depends on:
ii  grub-common  2.02~beta3-5
ii  libc62.24-9

os-prober recommends no packages.

os-prober suggests no packages.

- -- no debconf information
From c297939ba83ae45f0a0eb6bee10b9641d4f2d798 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Mon, 5 Jun 2017 11:52:17 -0500
Subject: [PATCH] Add in bcache devices

---
 os-prober | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/os-prober b/os-prober
index a48863e..ab2dee1 100755
--- a/os-prober
+++ b/os-prober
@@ -45,6 +45,16 @@ partitions () {
 			fi
 		done
 
+		# bcahce
+		for part in /sys/block/bcache*; do
+			if [ -f "$part/inflight" ]; then
+name="$(echo "${part##*/}" | sed 's,[!.],/,g')"
+if [ -e "/dev/$name" ]; then
+	echo "/dev/$name"
+fi
+			fi
+		done
+
 		# Add Serial ATA RAID devices
 		if type dmraid >/dev/null 2>&1 && \
 		   dmraid -s -c >/dev/null 2>&1; then
-- 
2.11.0

Bug#864181: os-prober: dmraid detection not functional.

[Mike Mestnik]

Package: os-prober
Version: 1.75
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Here is the code as found in os-prober:17
: >"$OS_PROBER_TMP/dmraid-map"
DMRAID=$(type dmraid >/dev/null 2>&1 || true)
if [ "$DMRAID" ]; then
dmraid -r -c >"$OS_PROBER_TMP/dmraid-map"
fi

The problem is that $DMRAID will always be empty because stdout is redirected.

- -- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable'), (490, 'testing'), (480, 'unstable'), (470, 
'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages os-prober depends on:
ii  grub-common  2.02~beta3-5
ii  libc62.24-9

os-prober recommends no packages.

os-prober suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJZNHjXAAoJEOPRqa2O3KuKcVMP/0Ad2IjgqvOCVuQgu3aSmc4P
390JFx8OPEBNh0C8OAEy+1d4EhKi2n50nvMUBy8Kg3iNpKBdwEgTAnGe3P35wkHZ
QKW4deSvHLg0jutuodiLzANTdc7UKGwpF1js3oEB73Yrg1WOyj+0uLGMGnwnu3a7
uYWzuwyZlRaBenMAFD52Uov6zUNo7i/LTUwUIXI4qzGtycHkYVZhLPe6XolnfK/w
BMugsTxWC4a7Y5d0WK/eQn1qEkqaB5NHV3OWgVnzhKqSAZa3ucnSyETAHgp/aJZT
S2+WNsNEC3t1nZdQz5gmzK1bGn6AmmSIS1RMO2n20Ih/e+7gbfbqSo3WETwFuX+o
LGefi+PFp5Jv9524e2T2DTPwfTFfvaes2+L5NFlvWV6oYf2rXLdt6Ky5wWJJBhg6
illjQVOGAwwkbEdB3xlv+zjx91vgrbQKhE2XN2eHcM0xIhd84BEuvnyOBK7BL07Z
PuF0+FfAHNYi/jra6Q+0Ddtuc2QS/tkEJ+kYCn5TU+c6d0265sBCM3lQueNj4Tdz
4lPsd6AHOYL7l03XQ0i0+IifnYWAV97l2oauKToIujaBcTfJ9VoDS++Jik1UrXwE
o9KNQJQ8gq7wRpeKTZr+fmiUulfvXId2ETXXnSTbfJvv2hJJpjtGBnq1jHsWb219
8DgV9lKM1ys/brYwq/NU
=aTuF
-END PGP SIGNATURE-

Bug#688336:

[Mike Mestnik]

Forget about all of this, I'm going to simplify the design.  I have in
mind to make the following changes.
1. Don't just change $1 from being the path of a block device to being
a reserved word.
a. Instead append an additional parameter.
2. Use subvolume id, instead of names.

Bug#688336:

[Mike Mestnik]

The patches have changes that have nothing to do with btrfs, I'll
attempt to isolate these.

Bug#688336:

[Mike Mestnik]

The patches introduce a bug.
/usr/lib/os-probes/50mounted-tests
calls fs_type on "btrfs"

I'll look into this some more.

Bug#688336:

[Mike Mestnik]

Refresh and simplify the patches.
https://github.com/cheako/os-prober/tree/btrfs-subvol

Also note os-probe fork:
https://github.com/campadrenalin/os-prober/commit/b571c0c7c3fe8986cc17dd200173fb7d86ef0c24
This commit reorgs the project making merges with the fork difficult.
From af1753acff410e6984466f88233855ad971cbc87 Mon Sep 17 00:00:00 2001
From: Michael Mestnik 
Date: Tue, 30 May 2017 00:15:36 -0500
Subject: [PATCH 1/2] Add support for btrfs subvol.

---
 README.btrfs |  15 
 common.sh|  13 ++-
 linux-boot-prober| 133 ++-
 linux-boot-probes/mounted/common/40grub2 |  12 ++-
 os-prober|  28 ++-
 os-probes/common/50mounted-tests |  72 -
 os-probes/mounted/common/90linux-distro  |   8 +-
 7 files changed, 272 insertions(+), 9 deletions(-)
 create mode 100644 README.btrfs

diff --git a/README.btrfs b/README.btrfs
new file mode 100644
index 000..f9b4d45
--- /dev/null
+++ b/README.btrfs
@@ -0,0 +1,15 @@
+BTRFS is a new filesystem which combines the filesystem with logical volume
+management (subvolumes).  For further information, see:
+  https://btrfs.wiki.kernel.org/index.php/Main_Page
+  https://btrfs.wiki.kernel.org/index.php/FAQ
+
+In order to support BTRFS, a number of changes were necessary to os-prober,
+os-probes/common/50mounted-tests, os-probes/mounted/common/90linux-distro,
+linux-boot-prober, and linux-boot-probes/common/50mounted-tests.
+
+The biggest impact will be to grub2 where there is additional information
+output by os-prober and where, if a BTRFS subvolume is being used for root,
+the parameters for linux-boot-prober have changed.
+
+Sun 30 Dec 2012 11:49:52 AM EST Gene Czarcinski 
+
diff --git a/common.sh b/common.sh
index e1646d4..4045d05 100644
--- a/common.sh
+++ b/common.sh
@@ -155,6 +155,7 @@ parse_proc_mounts () {
 	done
 }
 
+# add forth parameter to pickup btrfs subvol info
 parsefstab () {
 	while read -r line; do
 		case "$line" in
@@ -165,12 +166,22 @@ parsefstab () {
 set -f
 set -- $line
 set +f
-printf '%s %s %s\n' "$1" "$2" "$3"
+printf '%s %s %s %s\n' "$1" "$2" "$3" "$4"
 			;;
 		esac
 	done
 }
 
+#check_btrfs_mounted $bootsv $bootuuid)
+check_btrfs_mounted () {
+	bootsv="$1"
+	bootuuid="$2"
+	bootdev=$(blkid | grep "$bootuuid" | cut -d ':' -f  1)
+	bindfrom=$(grep " btrfs " /proc/self/mountinfo |
+		   grep " $bootdev " | grep " /$bootsv " | cut -d ' ' -f 5)
+	printf "%s" "$bindfrom"
+}
+
 unescape_mount () {
 	printf %s "$1" | \
 		sed 's/\\011/	/g; s/\\012/\n/g; s/\\040/ /g; s/\\134/\\/g'
diff --git a/linux-boot-prober b/linux-boot-prober
index e32dc84..2a60fa2 100755
--- a/linux-boot-prober
+++ b/linux-boot-prober
@@ -5,16 +5,143 @@ set -e
 
 newns "$@"
 require_tmpdir
+ERR="n"
+
+tmpmnt=/var/lib/os-prober/mount
+if [ ! -d "$tmpmnt" ]; then
+	mkdir "$tmpmnt"
+fi
+
+mounted=
+bootmnt=
+bootsv=
+bootuuid=
 
 grep "^/dev/" /proc/mounts | parse_proc_mounts >"$OS_PROBER_TMP/mounted-map" || true
 
-partition="$1"
+if [ -z "$1" ]; then
+	ERR=y
+elif [ "$1" = btrfs -a -z "$2" ]; then
+	ERR=y
+elif [ "$1" = btrfs -a -z "$3" ]; then
+	ERR=y
+elif [ "$1" = btrfs ]; then
+	type=btrfs
+	echo "$2" | grep -q "^UUID=" || ERR=y
+	echo "$3" | grep -q "^subvol=" || ERR=y
+	export "$2"
+	export "$3"
+	partition=$(blkid | grep "$UUID" | cut -d ':' -f 1 | tr '\n' ' ' | cut -d ' ' -f 1)
+	debug "btrfs: partition=$partition, UUID=$UUID, subvol=$subvol"
+else
+	partition="$1"
+	type=other
+fi
 
-if [ -z "$partition" ]; then
+if [ "x$ERR" != xn ]; then
 	echo "usage: linux-boot-prober partition" >&2
+	echo "   linux-boot-prober btrfs UUID=<> subvol=<>" >&2
 	exit 1
 fi
 
+if [ "$type" = btrfs ]; then
+	# handle all of the btrfs stuff here
+	if [ ! -e "/proc/self/mountinfo" ]; then
+		warn "/proc/self/mountinfo does not exist, exiting"
+		umount "$tmpmnt" 2>/dev/null
+		rmdir "$tmpmnt" 2>/dev/null
+		exit 1
+	fi
+	mpoint=$(grep "btrfs" /proc/self/mountinfo | grep " /$subvol " | grep " $partition " | cut -d ' ' -f 5)
+	if [ "$mpoint" = "/" ]; then
+		warn "specifying active root not valid, exiting"
+		umount "$tmpmnt" 2>/dev/null
+		rmdir "$tmpmnt" 2>/dev/null
+		exit 1
+	fi
+	if [ "$mpoint" = "$tmpmnt" ]; then
+		warn "btrfs subvol=$subvool, UUID=$UUID, already mounted on $tmpmnt **ERROR**"
+		umount "$tmpmnt" 2>/dev/null
+		rmdir "$tmpmnt" 2>/dev/null
+		exit 1
+	fi
+	if [ -z "$mpoint" ]; then
+		# mount the btrfs root
+		if ! mount -o subvol=$subvol -t btrfs -U $UUID "$tmpmnt" 2>/dev/null; then
+			warn "error mounting btrfs subvol=$subvol UUID=$UUID"
+			umount "$tmpmnt/boot" 2>/dev/null
+			umount "$tmpmnt" 2>/dev/null
+			rmdir "$tmpmnt" 2>/dev/null
+			exit 1
+		fi
+	else
+		# bind-mount
+		if ! mount -o bind "$mpoint" "$tmpmnt" 2>/dev/null; then
+			warn "error mounting btrfs bindfrom=$mpoint subvol=$subvol UUID=$UUID"
+			

Bug#863688: os-prober: Source has witespace at end of lines.

[Mike Mestnik]

Package: os-prober
Version: 1.75
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Please consider using some form of source buitification or tidy
to remove this whitespace.

- -- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable'), (490, 'testing'), (480, 'unstable'), (470, 
'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages os-prober depends on:
ii  grub-common  2.02~beta3-5
ii  libc62.24-9

os-prober recommends no packages.

os-prober suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJZLQOhAAoJEOPRqa2O3KuKipcP/Ru3sg/RzqRZjRe/uaxL320j
pS2xfJiYDM+d4gXWLCwc/Pjb6NzXol382IxnFnz9x1O9SXvjyvOwibvZq0t33B4r
XWU5dewcWC69LclmdVtnbprzHnaGF/Cxc7tRODqNqUi3O4G94k9T6HkXhi0wZaJX
zkUk3XrR5AOOmyeD7VA1m762GXDKvYuYQu+p18iw29ZZEucahXnQJd091STfgng1
VHt9JA8Zqxgs+9OdBr5T8Ypv6yhZunohpIZjvZ79VZmBoxJH/dX9YA919tufKbQx
JOZl12BsvtZVFFUXIQnoQK9Mbzlvq36xRTUUJjWXKrmR2XVDwj9MDL6SFDQzu1c1
4RBwPfl6ZXYeTCOKO24IlMzZYC3g9ECPn8X/+tfEBPGiLLx07ucFnUzRzm2UF2jO
f6wWoc/gBfXjIYzr82LDMM0dd6N32EoJ9hq+ErYzPGOFBGjRd5XelKat4cciZ6rg
TZX8HMF0HCuIRuPjoFyXLZNvQNbcLcvqAc5HTIKsOCH/qOtwb4EJYr41zT/h3NmZ
BxmQJZqhKc09Fzg47Suc99qiT5jZAdpWw/JMzaLmbFWYFYkD/mxHap3UroJSHuou
xr8lSLUEAq0YcyWZMSpvXivvaYJYs1D/uLnkRPaocRfl58Pf0wzuwl+kLAFj0pUv
55YW9FAESj6krRSZEunl
=dMfT
-END PGP SIGNATURE-

Bug#863651: debian-installer: no bcache support

[Mike Mestnik]

Package: debian-installer
Version: 20170525
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I created bcache backing store and was unable to install into it.

- -- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable'), (490, 'testing'), (480, 'unstable'), (470, 
'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJZLGirAAoJEOPRqa2O3KuKr5UQAK+I+38SE53oBM2UNH5QUymQ
11fGPcQvHOqpKkocHMFq78rXUavwTc/+TwICzn/jnt/+Lho2AGtZDW/BB9hmRDCd
4bA6jEqEv4oAkQsZLggMxC7YK6KDlkRvb8/hJJNx1nErUAKXq3copgGLQdLlJNnR
iMtfYf+HEtdROZqJd8VoY5zYhmy0y991iiqEePC1HcfdTnOESnGD8hAKWqE7FNm0
Jf2PyAmw5mAANT8ocHlglFxFZ9jBPXrUvTL82jqB/P8dEDvTzQVc0RorRHq7Gtci
qLrNSoKSaKAnuXNec/OOXWtjU7NuwXNz6SE0JDXIIoWkPFeT2f5R+ZkqOvJXceuY
l9KigA0ELsMp3+7pSkVnstECgutzdN93WGGtCTO2ubuSNkoQO5bRGjuGv/Hf4c/q
iDFiuzxBxZYFQtspDOBs99b0n12o6JIzjIJBtHXh1RO0i60MwlHDOKvGAtNGfSpd
Hs4fwEKJ3G3a/k+gtd3EG+yGYkdIhRrfmATM5cCNfWaDSbKBHm0oOnzE66MRrdte
oduMyvObPiWdq5vajl7O9jJQnes9/LJiJT8Xz1cQhzBXiebr/fMUq3h4Yi67T7qW
F/bAkRnMCnDTSj36ps1FxQJe0ElC5ylP46x9IgKH0qDeItaR0yniGIpJoSen4AE5
7xPOqhsOc+alGG8GmyzV
=UmYJ
-END PGP SIGNATURE-

Bug#809611: d-i fails to boot on HP mv2120

[Mike Thompson]

OK Martin, that image worked.  I did a full install of Debian Stretch from
it.  Below is the output at the tail end of bootup and login.


Debian GNU/Linux stretch/sid backup ttyS0

backup login: root
Password:
Linux backup 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18) armv5tel


The 0x60 change also still continues to boot my existing Debian Jessie
install.

Thanks for the work you do to keep these old pieces of NAS hardware working.

Mike

On Sat, Aug 6, 2016 at 12:37 PM, Martin Michlmayr <t...@cyrius.com> wrote:

> Hi Mike,
>
> * Mike Thompson <mpthomp...@gmail.com> [2016-08-05 20:23]:
> > The good news is that given the load address change from 0x40 to
> > 0x60 allowed the MV2120 to boot into the ssh based installer.
>
> Great!
>
> > The bad news is the installed failed from what looked like some sort of
> > segmentation faults in the installer from the looks of the logs which I
> > included below.
>
> I wonder if this is the same as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833599
>
> Can you please test this image:
> http://ftp.nl.debian.org/debian/dists/testing/main/
> installer-armel/current/images/orion5x/network-
> console/hp/mv2120/netboot.img
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

Bug#809611: d-i fails to boot on HP mv2120

[Mike Thompson]

1:50:27 netcfg[1396]: DEBUG: Success!
Aug  6 21:50:28 main-menu[989]: (process:1395): udhcpc (v1.22.1) started
Aug  6 21:50:28 main-menu[989]: (process:1395): Sending discover...
Aug  6 21:50:28 main-menu[989]: (process:1395): Sending select for
192.168.0.8...
Aug  6 21:50:28 main-menu[989]: (process:1395): Lease of 192.168.0.8
obtained, lease time 3600
Aug  6 21:50:28 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:50:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:50:28 main-menu[989]: INFO: Menu item 'network-console' selected
Aug  6 21:50:49 sshd[1498]: Server listening on 0.0.0.0 port 22.
Aug  6 21:50:49 apt-install: Queueing package openssh-server for later
installation
Aug  6 21:50:55 sshd[1516]: WARNING: /etc/ssh/moduli does not exist, using
fixed modulus
Aug  6 21:51:05 sshd[1516]: Accepted password for installer from
192.168.0.160 port 56579 ssh2
Aug  6 21:51:05 sshd[1518]: lastlog_openseek: Couldn't stat
/var/log/lastlog: No such file or directory
Aug  6 21:51:05 sshd[1518]: lastlog_openseek: Couldn't stat
/var/log/lastlog: No such file or directory
Aug  6 21:51:07 debconf: Setting debconf/language to en
Aug  6 21:51:11 debconf: Setting debconf/priority to low
Aug  6 21:51:11 debconf: Setting debconf/language to en
Aug  6 21:51:11 main-menu[1531]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:51:11 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:11 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:13 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:13 main-menu[1531]: INFO: Menu item 'choose-mirror' selected
Aug  6 21:51:13 main-menu[1531]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:14 anna-install: Queueing udeb apt-mirror-setup for later
installation
Aug  6 21:51:14 main-menu[1531]: (process:1557): Segmentation fault
Aug  6 21:51:14 main-menu[1531]: WARNING **: Configuring 'choose-mirror'
failed with error code 139
Aug  6 21:51:14 main-menu[1531]: WARNING **: Menu item 'choose-mirror'
failed.
Aug  6 21:51:14 main-menu[1531]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:14 main-menu[1531]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:51:28 main-menu[989]: INFO: Menu item 'choose-mirror' selected
Aug  6 21:51:28 main-menu[989]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:28 main-menu[989]: (process:1587): Segmentation fault
Aug  6 21:51:28 main-menu[989]: WARNING **: Configuring 'choose-mirror'
failed with error code 139
Aug  6 21:51:28 main-menu[989]: WARNING **: Menu item 'choose-mirror'
failed.
Aug  6 21:51:28 main-menu[989]: WARNING **: Unable to set title for
choose-mirror.
Aug  6 21:51:28 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:22 main-menu[989]: INFO: Modifying debconf priority limit from
'high' to 'medium'
Aug  6 21:52:22 debconf: Setting debconf/priority to medium
Aug  6 21:52:22 main-menu[989]: DEBUG: resolver (libgcc1): package doesn't
exist (ignored)
Aug  6 21:52:23 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:23 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:34 main-menu[989]: INFO: Falling back to the package
description for choose-mirror
Aug  6 21:52:34 main-menu[989]: INFO: Menu item 'save-logs' selected
Aug  6 21:53:08 kernel: [  218.089782] TCP: request_sock_TCP: Possible SYN
flooding on port 80. Sending cookies.  Check SNMP counters.
Aug  6 21:53:25 kernel: [  234.906280] TCP: request_sock_TCP: Possible SYN
flooding on port 80. Sending cookies.  Check SNMP counters.
-----


On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr <t...@cyrius.com> wrote:

> Mike, can you please give these instructions a go?  This is what I
> intend to post to the mv2120 list.
>
> --
>
> Mike Thompson reported that Debian stretch (the upcoming Debian 9)
> doesn't boot on the HP mv2120 anymore.  I don't know how many Debian
> users are left who run Debian on their mv2120.  I gave away my device
> several years ago.  Recently I bought an mv2120 from eBay in order to
> debug this issue.
>
> While I found a solution, it requires users to change a setting on their
> device.  Please make sure to make this change, otherwise your device
> will no longer b

Bug#809611: d-i fails to boot on HP mv2120

[Mike Thompson]

Hi Martin,

Sure.  It may take me a few days to get some time, but I'll give it a try
and let you know how it goes.

Mike

On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr <t...@cyrius.com> wrote:

> Mike, can you please give these instructions a go?  This is what I
> intend to post to the mv2120 list.
>
> --
>
> Mike Thompson reported that Debian stretch (the upcoming Debian 9)
> doesn't boot on the HP mv2120 anymore.  I don't know how many Debian
> users are left who run Debian on their mv2120.  I gave away my device
> several years ago.  Recently I bought an mv2120 from eBay in order to
> debug this issue.
>
> While I found a solution, it requires users to change a setting on their
> device.  Please make sure to make this change, otherwise your device
> will no longer boot when you upgrade to Debian 9.
>
> The new settings are compatible with Debian 8 (jessie) and Debian 9
> (stretch), so I suggest you make the changes now.
>
> If you have serial console access to the mv2120, you can run some
> commands in u-boot.  Simply interrupt the boot process by pressing a key
> and type the following:
>
> setenv loadAddr 0x060
> setenv bootcmd 'bootext2 0,1:1,2 0x060 /boot/uImage /dev/sda
> /dev/sdb'
> saveenv
>
> If you don't have a serial console, you can make the changes from within
> Debian.  Run the following commands:
>
> cat >/etc/fw_env.config < /dev/mtd0   0x0 0x1000 0x2
> EOF
>
> fw_setenv loadAddr 0x060
> fw_setenv bootcmd "bootext2 0,1:1,2 0x060 /boot/uImage /dev/sda
> /dev/sdb"
>
> This will create a config file so you can modify the u-boot environment
> and use fw_setenv to update two boot variables.
>
> Once you made the changes, upgrades to Debian 9 should work fine and you
> can also use the Debian installer if you want to perform a new
> installation.
>
> Please note that Debian 9 will be the last release to support the HP
> mv2120.
>
> --
>
> Note that the installer from
>
> https://d-i.debian.org/daily-images/armel/daily/orion5x/network-console/hp/mv2120/netboot.img
> will not boot right now with these settings.  However, you can change the
> loadAddr to 0x050 and it should work.  I just commited a fix in Git so
> it should work in a day or so with 0x060.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

Bug#826511: Aarch64 QEMU Bug

[Mike]

Package: debian-installer
Version: 20160516+b1

Installing Debian using QEMU aarch64 (and looks like arm as well) requires
extra steps due to lack of initrd and kernel support for virtio devices.
While there is a workaround documented below, this seems like something
that should be added to the distro build to incorporate support directly.

https://gmplib.org/~tege/qemu.html

See block 14.

Best,

Mike

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic

[Mike]

Good call on the CPU. Here's what I was using to run it:

qemu-system-mips64 -M malta -kernel vmlinux-4.5.0-2-4kc-malta -initrd
initrd.gz -hda hda.img -append root=/dev/ram console=ttyS0 -m 1G -nographic

After adding the -cpu option you mentioned it started up without issue.

Thanks!

Mike


On Sat, Jun 4, 2016 at 5:26 AM, Aurelien Jarno <aurel...@aurel32.net> wrote:

> On 2016-06-03 19:03, Ben Hutchings wrote:
> > Control: reassign -1 debian-installer 20160516+b1
> >
> > On Fri, 2016-06-03 at 08:48 +, Mattia Rizzolo wrote:
> > > control: reassign -1 src:linux  4.5.4-1
> > >
> > > On Thu, Jun 02, 2016 at 07:13:04PM -0400, Mike wrote:
> > > > Package: kernel
> > >
> > > this is not a valid package name.
> > >
> > > > Version: Testing
> > >
> > > and this is not a valid version
> > >
> > > >
> > > > I am working on installing Debian under a QEMU MIPS emulator. I was
> able to
> > > > get the Debian Stable branch to install and run properly using this:
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/stable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > However, when I attempt to use unstable or testing, I receive a
> kernel
> > > > panic immediately on boot for install. I cannot really give a
> package name
> > > > because it appears there's a problem in the kernel or init somewhere.
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/unstable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > The error I get it as follows:
> > > > [2.463767] Kernel panic - not syncing: Attempted to kill init!
> > > > exitcode=0x0004
> > > > [2.463767]
> > > > [2.464725] ---[ end Kernel panic - not syncing: Attempted to
> kill init!
> > > > exitcode=0x0004
> >
> > That usually means something is wrong with the initrd.  So reassigning
> > to the installer.
>
> It would be interested to know which QEMU command you used to start this
> image. Since the switch to GCC 5, the mips architecture requires a R2
> CPU.
>
> QEMU defaults emulating a R2 CPU in 32-bit mode, but a R1 CPU in 64-bit
> mode. In the later case try to pass "-cpu 5KEf" to QEMU.
>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic

[Mike]

I've discovered that the corresponding mipsel testing and development
releases work fine. Its only the mips testing and development versions.
On Jun 3, 2016 2:18 PM, "Ben Hutchings" <b...@decadent.org.uk> wrote:

> On Fri, 2016-06-03 at 14:07 -0400, Mike wrote:
> > I set the memory to 1024. I can try higher if need be.
>
> That should be more than enough.
>
> Ben.
>
> --
> Ben Hutchings
> Nothing is ever a complete failure; it can always serve as a bad
> example.
>

Bug#826173: Debian Testing/Unstable MIPS Installer Kernel Panic

[Mike]

I set the memory to 1024. I can try higher if need be.
On Jun 3, 2016 2:04 PM, "Ben Hutchings" <b...@decadent.org.uk> wrote:

> On Fri, 2016-06-03 at 19:03 +0100, Ben Hutchings wrote:
> > Control: reassign -1 debian-installer 20160516+b1
> >
> > On Fri, 2016-06-03 at 08:48 +, Mattia Rizzolo wrote:
> > > control: reassign -1 src:linux  4.5.4-1
> > >
> > > On Thu, Jun 02, 2016 at 07:13:04PM -0400, Mike wrote:
> > > > Package: kernel
> > >
> > > this is not a valid package name.
> > >
> > > > Version: Testing
> > >
> > > and this is not a valid version
> > >
> > > >
> > > > I am working on installing Debian under a QEMU MIPS emulator. I was
> able to
> > > > get the Debian Stable branch to install and run properly using this:
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/stable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > However, when I attempt to use unstable or testing, I receive a
> kernel
> > > > panic immediately on boot for install. I cannot really give a
> package name
> > > > because it appears there's a problem in the kernel or init somewhere.
> > > >
> > > >
> http://ftp.de.debian.org/debian/dists/unstable/main/installer-mips/current/images/malta/netboot/
> > > >
> > > > The error I get it as follows:
> > > > [2.463767] Kernel panic - not syncing: Attempted to kill init!
> > > > exitcode=0x0004
> > > > [2.463767]
> > > > [2.464725] ---[ end Kernel panic - not syncing: Attempted to
> kill init!
> > > > exitcode=0x0004
> >
> > That usually means something is wrong with the initrd.  So reassigning
> > to the installer.
>
> *Or* the VM is too small for the kernel to even unpack the initrd.   I
> think that may be true with the default QEMU memory size now.
>
> Ben.
>
> > Ben.
> >
> > > > At no point do I get to a location in the installer for me to
> interact with.
> > > >
> > > > Best,
> > > >
> > > > Mike
> > >
> > Ben Hutchings
> > Nothing is ever a complete failure; it can always serve as a bad
> > example.
> --
> Ben Hutchings
> Nothing is ever a complete failure; it can always serve as a bad
> example.
>

Bug#792152: PredictableNetworkInterfaceNames not used in installed /etc/network/interfaces

[Mike Roark]

Package: installation-reports

Boot method: CD (virtual)
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: July 11, 2015

Machine: VirtualBox VM
Processor: Intel Core i7-2600K
Memory: 512 MB
Partitions: df -Tl will do; the raw partition table is preferred
Filesystem Type 1K-blocks   Used Available Use% Mounted on
/dev/sda1  ext4   1931600 825488989940  46% /
udev   devtmpfs 10240  0 10240   0% /dev
tmpfs  tmpfs   101264   4472 96792   5% /run
tmpfs  tmpfs   253156  0253156   0% /dev/shm
tmpfs  tmpfs 5120  0  5120   0% /run/lock
tmpfs  tmpfs   253156  0253156   0% /sys/fs/cgroup

Output of lspci -knn (or lspci -nn):
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma]
[8086:1237] (rev 02)
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
[Natoma/Triton II] [8086:7000]
00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE
[8086:7111] (rev 01)
Kernel driver in use: ata_piix
00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH
VirtualBox Graphics Adapter [80ee:beef]
00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit
Ethernet Controller [8086:100e] (rev 02)
Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter [8086:001e]
Kernel driver in use: e1000
00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox
Guest Service [80ee:cafe]
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97
Audio Controller [8086:2415] (rev 01)
Subsystem: Intel Corporation Device [8086:]
Kernel driver in use: snd_intel8x0
00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f]
Kernel driver in use: ohci-pci
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
[8086:7113] (rev 08)
00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
Kernel driver in use: ahci

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:[E]

Comments/Problems:

Network non-functional after first boot, but works during install.
Problem appears to be that network interface is called eth0 in
/etc/network/interfaces, but name after first boot is enp0s3. This is
shell-only install.
Reinstalled several times, it's reproduced 100% of the time.
Problem seems to be related to this:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
I switched to terminal during install, and 80-net-setup-link.rules is not
under /lib/udev/rules.d. So during install network interface is still
called eth0, could that be the problem?
If I switch to terminal during install and do: ln -s /dev/null
/target/etc/udev/rules.d/80-net-setup-link.rules
then old network names are used after first boot and network starts ok. But
that's a step backwards... proper thing would be if the network name
written to /target/etc/network/interfaces is correct on first boot.
Alternatively if I change eth0 to enp0s3 in /etc/network/interfaces after
install, then ifup, that also fixes it.

My /etc/network/interfaces at first boot looks like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

Bug#775120: task-mate-desktop: Should install mate-system-tools

[Mike Gabriel]

Hi Jean-Philippe,

On  Mo 11 Mai 2015 20:33:58 CEST, MENGUAL Jean-Philippe wrote:


Le 11/05/2015 09:37, Samuel Thibault a écrit :

Mike Gabriel, le Mon 11 May 2015 03:27:17 +, a écrit :

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Once the system boots, after lightdm, I want to change password, set

the date,

network, etc. through a GUI.r

   * What was the outcome of this action?

No item appears for this. I only can use CLI tools.

Fix: add mate-system-tools in installed packages.

Looks to me that mate-desktop-environment should pull it instead?

What's your stance on this?

Furthermore, mate-system-tools will be deprecated for MATE 1.10.

What replaces it?  Does MATE not provide anything to accomplish those
tasks?
In Debian Jessie, no. Not adding the package means the user cannot  
change his passwd, network, etc through GUI. I don't know what will  
be with 1.10, but in stable, this package is needed.


If the package is needed:

  $ sudo apt-get install mate-system-tools

The issues with mate-system-tools, I have are:

  o not well tested inside Debian
  o not needed on enterprise sites (they are useless with
LDAP, Kerberos, etc.).

So what you can convince me of is adding mate-system-tools to  
Suggests: in mate-desktop-environment-extras, but that does not make a  
change for the installation procedure and won't be much appreciated by  
the Debian release team either, I guess.


I'd say, we should compensate this via documentation, how about  
helping out with improving [1] and mentioning mate-system-tools there?


light+love,
Mike

[1] https://wiki.debian.org/Mate

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgptL3891ZuJ4.pgp
Description: Digitale PGP-Signatur

Bug#775120: task-mate-desktop: Should install mate-system-tools

[Mike Gabriel]

Hi Cyril,

On  Fr 08 Mai 2015 23:21:08 CEST, Cyril Brulebois wrote:


Hello MATE people,

Cyril Brulebois k...@debian.org (2015-01-11):

Jean-Philippe MENGUAL te...@accelibreinfo.eu (2015-01-11):
 Package: task-mate-desktop
 Version: 3.29
 Severity: normal

 Dear Maintainer,

 *** Reporter, please consider answering these questions, where  
appropriate ***


* What led up to the situation?

 I choosed, in the installer, MATE and desktop.

* What exactly did you do (or not do) that was effective (or
  ineffective)?

 Once the system boots, after lightdm, I want to change password,  
set the date,

 network, etc. through a GUI.r

* What was the outcome of this action?

 No item appears for this. I only can use CLI tools.


* What outcome did you expect instead?

 In System - Admin, I should have items to accomplish such tasks.

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

 Fix: add mate-system-tools in installed packages.

Looks to me that mate-desktop-environment should pull it instead?


What's your stance on this?

Mraw,
KiBi.


mate-system-tools has been added last minute to the set of available  
MATE packages in Debian (that's is the reason why id did not get added  
as dep to any of the meta packages).


Furthermore, mate-system-tools will be deprecated for MATE 1.10. Thus,  
I'd suggest closing this bug with won't fix for stretch/unstable. And  
for jessie, the issue is not severe enough to justify a j-p-u upload  
IMHO.


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpHHxzAQHDnF.pgp
Description: Digitale PGP-Signatur

Bug#773763: Acknowledgement (task-mate-desktop: Should install libreoffice-gnome)

[Mike Gabriel]

Control: tag -1 patch

On  Di 06 Jan 2015 21:07:10 CET, MENGUAL Jean-Philippe wrote:

Just a precision: actually libreoffice-gnome installs  
libreoffice-gtk, it's a dependency. And it's libreoffice-gtk which  
is responsible for accessibility it LO. It can be installed without  
libreoffice-gnome, it works.


A .debdiff is attached to this mail.

The MATE packaging team will highly appreciate it if one of the  
tasksel maintainers fixes this accessibility issue in  
tasksel-mate-desktop on our behalf.


THANKS in advance!!!
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
diff -Nru tasksel-3.29/debian/changelog tasksel-3.29+nmu1/debian/changelog
--- tasksel-3.29/debian/changelog	2014-10-21 17:21:08.0 +0200
+++ tasksel-3.29+nmu1/debian/changelog	2015-01-07 11:35:18.0 +0100
@@ -1,3 +1,12 @@
+tasksel (3.29+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  * task-mate-desktop: Provide out-of-the box libreoffice accessibility
+with orca by installing libreoffice-gtk. (Closes: #773763).
+
+ -- Mike Gabriel sunwea...@debian.org  Wed, 07 Jan 2015 11:34:03 +0100
+
 tasksel (3.29) unstable; urgency=high
 
   * Gnome only works on i386 and amd64, so default to xfce on other arches.
diff -Nru tasksel-3.29/debian/control tasksel-3.29+nmu1/debian/control
--- tasksel-3.29/debian/control	2014-09-24 22:19:56.0 +0200
+++ tasksel-3.29+nmu1/debian/control	2015-01-07 11:33:49.0 +0100
@@ -281,6 +281,8 @@
 	network-manager-gnome,
 # orca works with mate, adding accessability
 	gnome-orca,
+# make libreoffice accessible with orca + provide a GTK'ish design in libreoffice
+	libreoffice-gtk,
 
 Package: task-laptop
 Architecture: all


pgphJzD2tC617.pgp
Description: Digitale PGP-Signatur

Bug#772441: installation-reports: successful jessie install on ASUS Eee PC 901

[Mike Miller]

Package: installation-reports
Severity: normal

Dear Maintainer,

Completely successful netinst install of jessie beta 2 on my ASUS Eee PC 901.

-- Package-specific info:

Boot method: netinst
Image version: 
http://cdimage.debian.org/cdimage/jessie_di_beta_2/i386/iso-cd/debian-jessie-DI-b2-i386-netinst.iso
Date: 2014-12-06T17:44:54-0500

Machine: ASUS Eee PC 901
Partitions:

Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/mapper/eeepc--vg-root ext4   3361360 2428120742776  77% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   204336   21484182852  11% /run
tmpfs  tmpfs   510832 220510612   1% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs   510832   0510832   0% 
/sys/fs/cgroup
/dev/sda1  ext2240972   29654198877  13% /boot
/dev/mapper/eeepc--usr-usr ext4  15378836 3231988  11342600  23% /usr
tmpfs  tmpfs   102168  12102156   1% 
/run/user/119
tmpfs  tmpfs   102168  20102148   1% 
/run/user/1000


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:

No problems encountered.

Caveats:
 * Made a separate /usr partition on the secondary internal flash disk
   (sdb) to accomodate the size of a default desktop install.
 * Installed over the network using wired network, wifi requires
   non-free firmware in the firmware-ralink package.


-- 

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 eeepc 3.16-2-486 #1 Debian 3.16.3-2 (2014-09-20) 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: ASUSTeK Computer Inc. Device [1043:830f]
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: ASUSTeK Computer Inc. Device [1043:830f]
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: ASUSTeK Computer Inc. Device [1043:830f]
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family 
High Definition Audio Controller [8086:27d8] (rev 02)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:831a]
lspci -knn: Kernel driver in use: snd_hda_intel
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: ASUSTeK Computer Inc. Device [1043:830f]
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: ASUSTeK Computer Inc. Device [1043:830f]
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: Subsystem: ASUSTeK Computer Inc. Device 

Bug#761598: task-mate-desktop: pull in lightdm

[Mike Gabriel]

Package: tasksel
Version: 3.24
Tag: patch
X-Debbugs-Cc: pkg-mate-t...@lists.alioth.debian.org

Hi Joey,

SynrG on IRC made me aware of MATE not pulling in any display manager  
when installed via a MATE-flavoured livebuild.


As the MATE pkg-team doesn't want to attach a display manager to close  
to the mate meta packages (a desktop environment does not necessarily  
require a display manager to be usable - e.g. when used via X2Go or  
VNC, nor does it require a local X11), we'd appreciate it if the  
display manager (preferably lightdm) could be pulled in via tasksel  
(task-mate-desktop).


I hope the attached patch is ok. (Does tasksel allow  
x-display-manager | lightdm in Recommends: field?).


Thanks+Greets,
Mike



--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
diff -Nru tasksel-3.24/debian/changelog tasksel-3.25/debian/changelog
--- tasksel-3.24/debian/changelog	2014-09-10 00:19:19.0 +0200
+++ tasksel-3.25/debian/changelog	2014-09-14 23:22:41.0 +0200
@@ -1,3 +1,10 @@
+tasksel (3.25) unstable; urgency=medium
+
+  * Pull-in a display manager via task-mate-desktop (preferably lightdm,
+but any other DM that provides x-display-manager is fine).
+
+ -- Mike Gabriel sunwea...@debian.org  Sun, 14 Sep 2014 23:21:39 +0200
+
 tasksel (3.24) unstable; urgency=medium
 
   * Add missing dependency task-cinnamon-desktop - task-desktop
diff -Nru tasksel-3.24/debian/control tasksel-3.25/debian/control
--- tasksel-3.24/debian/control	2014-09-10 00:16:21.0 +0200
+++ tasksel-3.25/debian/control	2014-09-14 23:17:00.0 +0200
@@ -261,6 +261,9 @@
 	task-desktop,
 	mate-desktop-environment,
 Recommends:
+# the MATE desktop environment packages don't pull in a
+# display manager, doing it in task-mate-desktop instead.
+	x-display-manager | lightdm,
 # temporarily moved from task-desktop due to #525077
 	gimp,
 # Package management.


pgpMbaylv5fU7.pgp
Description: Digitale PGP-Signatur

Bug#712696: marked as done (debian-installer: Add Cinnamon and Mate as alternative DEs.)

[Mike Gabriel (Frontdesk)]

clone #712696 -1
reopen -1
retitle #712696 Add task for Cinnamon desktop environment
retitle -1 Add task for MATE desktop environment
tag -1 patch
thanks

Hi Stevem, hi Joey,

On  Mo 08 Sep 2014 22:52:24 CEST, Steven Chamberlain wrote:


On 07/09/14 19:03, Debian Bug Tracking System wrote:

 tasksel (3.22) unstable; urgency=medium



   * Add task-cinnamon-desktop. Thanks, Margarita Manterola.
 Closes: #712696


Bug #712696 also mentioned the MATE desktop, but AFAICT no task was
added for it yet.  If someone wants that to happen, they must put
together a metapackage (something similar to
cinnamon-desktop-enironment) as was requested here:
https://bugs.debian.org/712696#80

Regards,


patch attached to make MATE selectable via Tasksel. Hope the format is ok.

Thanks+Greets,
Mike

--
For Debian Frontdesk:

mike gabriel aka sunweaver (Debian Developer, Member of Frontdesk)

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net

diff -Nru tasksel-3.22/debian/changelog tasksel-3.23/debian/changelog
--- tasksel-3.22/debian/changelog	2014-09-07 18:26:27.0 +0200
+++ tasksel-3.23/debian/changelog	2014-09-09 23:07:57.0 +0200
@@ -1,3 +1,9 @@
+tasksel (3.23) unstable; urgency=medium
+
+  * Add task-mate-desktop. Thanks, Mike Gabriel.
+
+ -- Mike Gabriel sunwea...@debian.org  Tue, 09 Sep 2014 23:07:21 +0200
+
 tasksel (3.22) unstable; urgency=medium
 
   * Avoid using each() on a hash ref, which causes perl to output a
diff -Nru tasksel-3.22/debian/control tasksel-3.23/debian/control
--- tasksel-3.22/debian/control	2014-09-07 18:24:51.0 +0200
+++ tasksel-3.23/debian/control	2014-09-09 23:04:44.0 +0200
@@ -44,7 +44,7 @@
 # The order here is significant when installing this task manually;
 # when tasksel installs this task it instead selects one of these based
 # on the tasksel/desktop debconf setting.
-	task-xfce-desktop | task-gnome-desktop | task-kde-desktop | task-lxde-desktop | task-cinnamon-desktop, 
+	task-xfce-desktop | task-gnome-desktop | task-kde-desktop | task-lxde-desktop | task-cinnamon-desktop | task-mate-desktop, 
 # For use by third-party apps.
 	xdg-utils,
 # mdns/zeroconf stuff
@@ -248,6 +248,36 @@
 Depends: ${misc:Depends}, 
 	cinnamon-desktop-environment
 
+Package: task-mate-desktop
+Architecture: all
+Description: MATE desktop environment
+ This task package is used to install the Debian desktop, featuring
+ the MATE desktop environment, and with other packages that Debian users
+ expect to have available on the desktop.
+Depends: ${misc:Depends},
+mate-desktop-environment,
+Recommends:
+# temporarily moved from task-desktop due to #525077
+gimp,
+# Package management.
+synaptic,
+# firefox (ne iceweasel) is the most popular web browser at the moment,
+# although both gnome and kde offer their own too
+iceweasel,
+# libreoffice is the best word processor / office suite at the moment
+libreoffice,
+libreoffice-gcj,
+# make help menu work
+libreoffice-help-en-us,
+# make thesaurus work
+mythes-en-us,
+# make spellchecker work
+hunspell-en-us,
+# make hyphenation work
+hyphen-en-us,
+# we need a working network setup at least
+network-manager-gnome
+
 Package: task-laptop
 Architecture: all
 Description: laptop
diff -Nru tasksel-3.22/tasks/mate-desktop tasksel-3.23/tasks/mate-desktop
--- tasksel-3.22/tasks/mate-desktop	1970-01-01 01:00:00.0 +0100
+++ tasksel-3.23/tasks/mate-desktop	2014-09-09 23:06:16.0 +0200
@@ -0,0 +1,7 @@
+Task: mate-desktop
+Relevance: 8
+Section: user
+Enhances: desktop
+Test-preferred-desktop: mate
+Key:
+  task-mate-desktop


pgpXMXi4CJPm5.pgp
Description: Digitale PGP-Signatur

Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel

[Mike Gabriel]

Hi Jonas, hi all,

On  Do 28 Aug 2014 18:39:34 CEST, Jonas Smedegaard wrote:


...another more descriptive, I believe, answer could be You don't
really have a Debian Edu system when installing it on a Debian system.

I believe that second elaborated view is the reason for Mike's question.

To me it is far from perfectly sense to offer Debian Edu in
debian-installer to get some educational software - I would expect to
get a Debian Edu system.

 - Jonas


That's what I was aiming at! Jonas, thanks for reading inbetween my  
lines and verbalizing the unsaid.


:-)

We are currently testing deployment of Debian Edu systems by  
installing vanilla Debian and then pulling in required packages on  
post-installation. The results will come in by the end of next week  
(once I have time for looking at finalizing those installations).


There are packages in debian-edu SVN [1] (educlient, eduroaming)  
that have some post-installation logic turning a Debian system into a  
Skolelinux / Debian Edu system, as well. I will probably take a look  
at those, as well, during our test cycle. Originally, they were  
designed to turn Ubuntu systems into Debian Edu client machines AFAIR.  
So let's see.


But still, I guess it is pointless offering a Debian Edu blend in D-I  
if the result after installation won't be a proper Debian Edu  
workstation.


Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgp6I3lcHC3oM.pgp
Description: Digitale PGP-Signatur

Bug#758116: Please be verbose whether you would like to get your Blend promoted by tasksel

[Mike Gabriel]

Hi Andreas,

[taking all lists except debian-blends and debian-edu off the loop...]

On  Di 26 Aug 2014 13:27:23 CEST, Andreas Tille wrote:


Hi,

yesterday I joined the videostream of the installer BoF at DebConf[1].
I also became a bit involved via IRC.  Joey Hess raised the question
about the criteria to add a Blend or not.  I answered all in the list
of the bug report #758116 which IMHO fits the criterion of actively
maintained and some valuable content for users.

I think it should be also a criterion that the team behind the Blend
confirms that they are interested and so I'm hereby pinging all lists in
question to ask you for confirmation.  I have set Reply-To to the bug
report and the general Blends list in case you are interested in further
discussion with other Blends.

Any input is welcome to make sure users will realise the fruits of your
great work at the earliest point in time.

Kind regards

 Andreas.


I guess this only makes sense if a Debian Edu machine (standalone) can  
be installed via Debian's normal D-I, right?


@Petter: is that possible? Do you know?

Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgp0rBzjiiUJm.pgp
Description: Digitale PGP-Signatur

Bug#747045: base-installer: Install hangs when attempting to format EFI system partition

[Mike]

Package: base-installer
Severity: important

Dear Maintainer,

When installing on an EFI based computer, the installation will hang while
attempting to format an EFI system partition. If the partition already exists
and is already formatted, the install proceeds normally.

I have seen this behavior on two EFI based systems with very different hardware
(A desktop PC and a Macbook).



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/20140505000751.26138.90793.report...@server.lan

Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash

[Mike Miller]

: Committed_AS:  26144 kB
/proc/meminfo: VmallocTotal: 753664 kB
/proc/meminfo: VmallocUsed:2056 kB
/proc/meminfo: VmallocChunk: 747260 kB
/proc/bus/input/devices: I: Bus=0019 Vendor=0001 Product=0001 Version=0100
/proc/bus/input/devices: N: Name=gpio-keys
/proc/bus/input/devices: P: Phys=gpio-keys/input0
/proc/bus/input/devices: S: Sysfs=/devices/platform/gpio-keys/input/input0
/proc/bus/input/devices: U: Uniq=
/proc/bus/input/devices: H: Handlers=kbd event0 
/proc/bus/input/devices: B: PROP=0
/proc/bus/input/devices: B: EV=3
/proc/bus/input/devices: B: KEY=100 0 0 0 0 0 0 0 20 0 0 0 0
/proc/bus/input/devices: 

-- 
mike


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130625165449.ga7...@xps14z.home.local

Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p

[Mike]

 have you been able to test either patch now?

Not yet, dealing with Xen issues.  Had to abandon UEFI because of Xen 
incompatibility.  See my Xen bug.  Probably deserves a warning in the 
d-i manual.  Also busy setting up the system.  Would like to actually 
*use* my computer for a change


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130331055052.ga32...@64-142-29-25.dsl.static.sonic.net

Bug#704191: HP EliteBook 8570p BIOS-GPT install fails

[Mike]

Package: installation-reports

Boot method: ISO on USB stick on USB 2.0 port
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso
Date: 2013-03-29

Machine: HP EliteBook 8570p (C6Z56UT)
Processor: Intel Core i5-3320M
Memory: 4 GiB
Partitions:

# df -Tl | human
rootfs   rootfs   /
udev devtmpfs /dev
tmpfstmpfs/run
/dev/mapper/___-root ext4 /   - dm_crypt
tmpfstmpfs/run/lock
tmpfstmpfs/run/shm
/dev/sda_ext4 /boot
/dev/sda_vfat /boot/efi   - ESP


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:[E]
Overall install:[E]

Comments/Problems:

Xen currently seems not to function with the 3.2.39 kernel for the
dom0 on a UEFI system, so I can't use UEFI.  This is an attempt to use
a GPT-partitioned disk with BIOS.

This assumes a Boot Mode of Legacy.  (HP startup screen  Startup
Menu  BIOS Setup  System Configuration  Boot Options)

Boot to the Startup Menu, F9 Boot Device Options, choose USB Hard
Drive 1, Advanced options, Expert install.  Following the advice
of http://www.debian.org/devel/debian-installer/errata :

  When there is more than one disk available during installation (for
  example one hard disk and one USB stick, as it is commonly the case
  when booting the installer from a USB stick), grub-install may run
  into problems: it was reported several times, that the GRUB
  bootloader was installed onto the USB stick instead of the hard disk
  containing the newly-installed system.

  To avoid running into this, make sure to answer No when the
  following question is asked during the installation process:
  Install the GRUB boot loader to the master boot record?; it should
  be possible to specify the right device at the next step: Device
  for boot loader installation.

or not, the result is the same: The d-i seems to think that GRUB
succeeded in the console:


grub-installer: Installation finished. No error reported.
grub-installer: info: grub-install ran successfully


But rebooting fails to find boot code, gives HP screen:


BootDevice Not Found

Please install an operating system on your hard disk.
[...]


Rebooting the USB stick to rescue mode, I umount the /boot and
/boot/efi partitions--because mount thinks they're mounted--before I
truly mount them.  Running grub-install /dev/sda appears to succeed,
but rebooting yields the same HP screen.

From rescue mode, aptitude install gdisk on the target system, to
confirm that the biosgrub partition has GUID code
21686148-6449-6e6f-744e-656564454649.

So BIOS-GPT GRUB installation doesn't work, and I have no idea how to 
force it to.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130329070549.ga30...@64-142-29-25.dsl.static.sonic.net

Bug#704191: HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag

[Mike]

Control: retitle -1 HP EliteBook 8570p BIOS-GPT install succeeds, with bootable 
flag

 But rebooting fails to find boot code, gives HP screen:
 
 
 BootDevice Not Found
 
 Please install an operating system on your hard disk.
 [...]
 

With hints from http://www.rodsbooks.com/gdisk/bios.html this can be 
made to work.  In rescue mode, use fdisk to set the bootable flag on the 
one partition in the protective MBR.  Rebooting boots into GRUB/Linux.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130329073522.ga30...@64-142-29-25.dsl.static.sonic.net

Bug#704191: HP EliteBook 8570p BIOS-GPT install succeeds, with bootable flag

[Mike]

Xen/Linux also runs properly with this configuration.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130329083838.ga30...@64-142-29-25.dsl.static.sonic.net

Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p

[Mike]

 You could try it yourself using the attached patch and the 
 instructions at 
 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.

These instructions don't work.  One needs to aptitude install dpkg-dev 
to get dpkg-source before apt-get source linux.  Then apt-get install 
build-essential fakeroot isn't needed.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130327070523.ga26...@64-142-29-25.dsl.static.sonic.net

Bug#703469: HP EliteBook 8570p UEFI install works, with some effort

[Mike]

I managed to get the USB storage working, so that I could grab the lspci 
output.
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
00:16.3 Serial controller [0700]: Intel Corporation 7 Series/C210 Series 
Chipset Family KT Controller [8086:1e3d] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection [8086:1502] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 3 [8086:1e14] (rev c4)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 4 [8086:1e16] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation QM77 Express Chipset LPC 
Controller [8086:1e55] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 
6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: ahci
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI 
Thames [Radeon 7500M/7600M Series] [1002:6841]
Subsystem: Hewlett-Packard Company Device [103c:17a9]
Kernel driver in use: radeon
01:00.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI 
Turks/Whistler HDMI Audio [Radeon HD 6000 Series] [1002:aa90]
Subsystem: Hewlett-Packard Company Device [103c:17a9]
Kernel driver in use: snd_hda_intel
24:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host 
Controller [197b:2380] (rev 30)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: firewire_ohci
24:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host 
Controller [197b:2392] (rev 30)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
Kernel driver in use: sdhci-pci
24:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard SD Host 
Controller [197b:2391] (rev 30)
Subsystem: Hewlett-Packard Company Device [103c:17a7]
25:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 
[Taylor Peak] [8086:0082] (rev 34)
Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1301]
Kernel driver in use: iwlwifi

Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p

[Mike]

Control: retitle -1 UEFI USB stick installation fails to detect its media on a 
USB 3.0 port

As mentioned in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469 ,
I was able to install by booting without EFI.  While having problems 
getting that system to recognize a USB stick that I plugged in, it 
occurred to me that I was using one of the USB 3.0 ports.  A USB 2.0 
port recognizes the device.

Applying the same idea to this bug, I got the d-i to work just as well 
in EFI mode on a USB 2.0 port.  I booted the existing system by choosing 
F9 Boot Device Options from the Startup Menu, then External USB 
Hard Drive (as opposed to USB Hard Drive 1 - ...).  I stopped after 
configuring the network, since I don't want to destroy the system I've 
already installed.

So the remaining issue is that the d-i doesn't find the installation 
media in a USB 3.0 port.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130326214131.ga24...@64-142-29-25.dsl.static.sonic.net

Bug#703469: HP EliteBook 8570p UEFI install works, with some effort

[Mike]

dmesg output truncated after the USB stuff.  There are two USB 2.0, one 
USB 2.0/eSATA, and two USB 3.0 ports on the hardware.
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 
root=/dev/mapper/laptop-root ro quiet
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 000a (usable)
[0.00]  BIOS-e820: 0010 - bdcf3000 (usable)
[0.00]  BIOS-e820: bdcf3000 - beebc000 (reserved)
[0.00]  BIOS-e820: beebc000 - befbc000 (ACPI NVS)
[0.00]  BIOS-e820: befbc000 - befff000 (ACPI data)
[0.00]  BIOS-e820: befff000 - bf00 (usable)
[0.00]  BIOS-e820: e00f8000 - e00f9000 (reserved)
[0.00]  BIOS-e820: fed1c000 - fed2 (reserved)
[0.00]  BIOS-e820: ffee - ffeff000 (reserved)
[0.00]  BIOS-e820: 0001 - 00013e00 (usable)
[0.00] NX (Execute Disable) protection: active
[0.00] EFI v2.10 by HPQ
[0.00]  ACPI=0xbeffe000  ACPI 2.0=0xbeffe014  SMBIOS=0xbe56b698 
[0.00] Kernel-defined memdesc doesn't match the one from EFI!
[0.00] EFI: mem00: type=3, attr=0xf, 
range=[0x-0x1000) (0MB)
[0.00] EFI: mem01: type=7, attr=0xf, 
range=[0x1000-0x00058000) (0MB)
[0.00] EFI: mem02: type=4, attr=0xf, 
range=[0x00058000-0x00059000) (0MB)
[0.00] EFI: mem03: type=7, attr=0xf, 
range=[0x00059000-0x0007d000) (0MB)
[0.00] EFI: mem04: type=4, attr=0xf, 
range=[0x0007d000-0x0007e000) (0MB)
[0.00] EFI: mem05: type=3, attr=0xf, 
range=[0x0007e000-0x000a) (0MB)
[0.00] EFI: mem06: type=2, attr=0xf, 
range=[0x0010-0x003b) (2MB)
[0.00] EFI: mem07: type=7, attr=0xf, 
range=[0x003b-0x00c0) (8MB)
[0.00] EFI: mem08: type=3, attr=0xf, 
range=[0x00c0-0x0100) (4MB)
[0.00] EFI: mem09: type=7, attr=0xf, 
range=[0x0100-0x36958000) (857MB)
[0.00] EFI: mem10: type=2, attr=0xf, 
range=[0x36958000-0x374a4000) (11MB)
[0.00] EFI: mem11: type=7, attr=0xf, 
range=[0x374a4000-0x88ddc000) (1305MB)
[0.00] EFI: mem12: type=2, attr=0xf, 
range=[0x88ddc000-0xb6cf4000) (735MB)
[0.00] EFI: mem13: type=4, attr=0xf, 
range=[0xb6cf4000-0xb6d14000) (0MB)
[0.00] EFI: mem14: type=7, attr=0xf, 
range=[0xb6d14000-0xb80be000) (19MB)
[0.00] EFI: mem15: type=1, attr=0xf, 
range=[0xb80be000-0xb80db000) (0MB)
[0.00] EFI: mem16: type=3, attr=0xf, 
range=[0xb80db000-0xb8604000) (5MB)
[0.00] EFI: mem17: type=4, attr=0xf, 
range=[0xb8604000-0xb9ce4000) (22MB)
[0.00] EFI: mem18: type=3, attr=0xf, 
range=[0xb9ce4000-0xb9cf3000) (0MB)
[0.00] EFI: mem19: type=7, attr=0xf, 
range=[0xb9cf3000-0xb9da) (0MB)
[0.00] EFI: mem20: type=4, attr=0xf, 
range=[0xb9da-0xba6e4000) (9MB)
[0.00] EFI: mem21: type=7, attr=0xf, 
range=[0xba6e4000-0xba6e5000) (0MB)
[0.00] EFI: mem22: type=4, attr=0xf, 
range=[0xba6e5000-0xba736000) (0MB)
[0.00] EFI: mem23: type=7, attr=0xf, 
range=[0xba736000-0xba737000) (0MB)
[0.00] EFI: mem24: type=4, attr=0xf, 
range=[0xba737000-0xbbdce000) (22MB)
[0.00] EFI: mem25: type=7, attr=0xf, 
range=[0xbbdce000-0xbbdd8000) (0MB)
[0.00] EFI: mem26: type=2, attr=0xf, 
range=[0xbbdd8000-0xbbdde000) (0MB)
[0.00] EFI: mem27: type=4, attr=0xf, 
range=[0xbbdde000-0xbbddf000) (0MB)
[0.00] EFI: mem28: type=7, attr=0xf, 
range=[0xbbddf000-0xbbde1000) (0MB)
[0.00] EFI: mem29: type=4, attr=0xf, 
range=[0xbbde1000-0xbbde4000) (0MB)
[0.00] EFI: mem30: type=7, attr=0xf, 
range=[0xbbde4000-0xbbde7000) (0MB)
[0.00] EFI: mem31: type=4, attr=0xf, 
range=[0xbbde7000-0xbbe04000) (0MB)
[0.00] EFI: mem32: type=7, attr=0xf, 
range=[0xbbe04000-0xbbe06000) (0MB)
[0.00] EFI: mem33: type=4, attr=0xf, 
range=[0xbbe06000-0xbbecb000) (0MB)
[0.00] EFI: mem34: type=7, attr=0xf, 
range=[0xbbecb000-0xbbecc000) (0MB)
[0.00] EFI: mem35: type=4, attr=0xf, 

Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p

[Mike]

Ben Hutchings wrote:
 However, the lspci output you attached to #703469 shows that the xHCI 
 does not have a driver bound to it.  Perhaps the kernel log (from 
 dmesg) would explain why.

Thanks Ben.  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703469#25 
request interrupt 255 failed?

That's the dmesg output from the running (non-Xen, that's another bug) 
system, not from the UEFI d-i.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130327042309.gb25...@64-142-29-25.dsl.static.sonic.net

Bug#703469: HP EliteBook 8570p UEFI install works, with some effort

[Mike]

Package: installation-reports

Boot method: ISO on USB drive
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso
Date: 2013-03-19

Machine: HP EliteBook 8570p (C6Z56UT)
Processor: Intel Core i5-3320M
Memory: 4 GiB
Partitions:

# df -Tl | human
rootfs   rootfs   /
udev devtmpfs /dev
tmpfstmpfs/run
/dev/mapper/___-root ext4 /   - dm_crypt
tmpfstmpfs/run/lock
tmpfstmpfs/run/shm
/dev/sda_ext4 /boot
/dev/sda_vfat /boot/efi   - ESP


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:[E]
Overall install:[E]

Comments/Problems:

In order to document this failure mode, I made this installation attempt on a
system that I cleaned after a successful installation.  So it isn't quite
the same as a brand-new machine.

At the HP startup screen, hit ESC for the Startup Menu, F10 for BIOS
Setup, in System Configuration tab, Boot Options, change Boot Mode from
Legacy to UEFI Hybrid (With CSM).  (I made other, irrelevant, settings
changes, too.)

Reboot to the Startup Menu, F9 for Boot Device Options, choose USB Hard
Drive 1, Advanced options, Expert install.

The Installer seemed to think that GRUB succeeded: grub-installer: info:
grub-install ran successfully.  But rebooting fails to find boot code, gives
HP screen:


BootDevice Not Found

Please install an operating system on your hard disk.


etc.  Rebooting the USB stick to rescue mode, I umount the /boot and /boot/efi
partitions--because mount thinks they're mounted--before I truly mount them.
Then I install grub-efi-amd64, and:


# grub-install /dev/sda
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI 
variables.
Try 'modprobe efivars' as root.
Fatal: Couldn't open either sysfs or procfs directories for accessing EFI 
variables.
Try 'modprobe efivars' as root.
Installation finished. No error reported.
# modprobe efivars
ERROR: could not insert 'efivars': Unknown symbol in module, or unknown 
parameter (see dmesg)
# dmesg | tail -1
[...] efivars: Unknown symbol efi_enabled_facility (err 0)


I assume that's because I haven't booted the USB stick in UEFI mode.

So mkdir /boot/efi/EFI/boot and cp -p /boot/efi/EFI/debian/grubx64.efi
/boot/efi/EFI/boot/bootx64.efi (Thanks to
http://tanguy.ortolo.eu/blog/article51/debian-efi.) and reboot.  That boots
to the GRUB menu, followed by:


  Booting 'Debian GNU/Linux, with Linux 3.2.0-4-amd64

error: file not found.
error: file not found.
Loading Linux 3.2.0-4-amd64 ...
Loading initial ramdisk ...

Press any key to continue...
error: no suitable mode found.
Booting however


and no further output.

Rebooting to USB stick rescue mode again, dpkg-reconfigure grub-efi-amd64
which now decides to add insmod efi_gop and insmod efi_uga to
/boot/grub/grub.cfg.  Why didn't it do it when I installed the package?  Then
reboot.  login:


Side note: Why isn't Debian or GRUB in
http://www.uefi.org/specs/esp_registry?


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130320002524.ga9...@64-142-29-25.dsl.static.sonic.net

Bug#703470: UEFI USB stick installation fails on HP EliteBook 8570p

[Mike]

Package: installation-reports

Boot method: ISO on USB drive
Image version: 
http://cdimage.debian.org/cdimage/wheezy_di_rc1/amd64/iso-cd/debian-wheezy-DI-rc1-amd64-netinst.iso
Date: 2013-03-19

Machine: HP EliteBook 8570p (C6Z56UT)
Processor: Intel Core i5-3320M
Memory: 4 GiB
Partitions: none (erased MBR  GPT)

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

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

Comments/Problems:

In order to document this failure mode, I made this installation attempt on a
system that I cleaned after a successful installation.  So it isn't quite
the same as a brand-new machine.

At the HP startup screen, hit ESC for the Startup Menu, F10 for BIOS
Setup, in System Configuration tab, Boot Options, change Boot Mode from
Legacy to UEFI Hybrid (With CSM).  (I made other, irrelevant, settings
changes, too.)

System now boots automatically from the USB stick.  For a second I see the
message:


Welcome to GRUB!

error: prefix is not set.


in the top left of the screen, then the graphical D-I menu comes up.  Choose
Advanced options, Expert install.  At Detect and mount CD-ROM, get a
message that No common CD-ROM drive was detected., prompt to Load CD-ROM
drivers from removable media?

Saying Yes gets Cannot read removable media, or no drivers found.  Returns
to the main menu.

Saying No, gets No common CD-ROM drive was detected., prompt to Manually
select a CD-ROM module and device?.  Say No, the step fails; say Yes and
enter /dev/sda (the only present removable device), also fails.  Returns to
the main menu.

In the screen prompting You may switch to the shell on the second terminal
(ALT+F2), ALT+F2 toggles the appearance of a few raster lines at the top of
the screen--mostly black, one part red, two white dots flashing--nothing more.
(In Rescue mode, it gives a proper shell prompt.)

I don't see any mention of installing to a UEFI/GPT system under
http://www.debian.org/releases/testing/amd64/.

See bug #703469 for the workaround.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130320012136.ga9...@64-142-29-25.dsl.static.sonic.net

Bug#703469: HP EliteBook 8570p UEFI install works, with some effort

[Mike]

Ben Hutchings wrote:
 At a guess, this option might result in booting the installer in 
 legacy mode.

See the next bug #703470 for why I boot legacy.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130320022933.ga9...@64-142-29-25.dsl.static.sonic.net

Bug#683867: grub-installer: Fails to install grub: line 45: syntax error: unexpected else

[Mike Miller]

Package: grub-installer
Version: 1.76
Severity: important
Tags: patch

Installation with the daily build from August 3 fails at grub-installer.

(process:26576): /usr/bin/grub-installer: line 45: syntax error: unexpected
else (expecting then)
WARNING **: Configuring 'grub-installer' failed with error code 2
WARNING **: Menu item 'grub-installer' failed.

Simple syntax typo, attached patch fixes (patched while installing and
installation succeeded).



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
From adab600b7412379da97e13e12d87bbe6a547bc53 Mon Sep 17 00:00:00 2001
From: Mike Miller mtmil...@ieee.org
Date: Sat, 4 Aug 2012 18:57:23 -0400
Subject: [PATCH] Fix shell unexpected else syntax error

---
 grub-installer |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/grub-installer b/grub-installer
index 768fbed..a0a4d8c 100755
--- a/grub-installer
+++ b/grub-installer
@@ -40,7 +40,7 @@ info architecture: $ARCH
 local initial_proc_contents=$(ls $ROOT/proc)
 if [ -z $initial_proc_contents ]; then
 	info Mounting /proc into $ROOT
-	if [ $(udpkg --print-os) = kfreebsd ];
+	if [ $(udpkg --print-os) = kfreebsd ]; then
 		mount -t linprocfs proc $ROOT/proc
 	else
 		mount -t proc proc $ROOT/proc
-- 
1.7.10.4

Bug#675294: installation-reports: No disk drive was detected during 6.0 install

[Mike Bianchi]

Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable


While installing squeeze from a netinstall cd, after entering the user name and 
password,
the message No disk drive was detected came up with a list of driver names.

The drive is a new SATA 6.0Gb/s on an Intel DZ68BC mother board + I5-2500K 
processor.
 The blue SATA cable was wired to the SATA 6 connector on the MoBo.

The fix was to use a red SATA cable wired to the SATA 3.0 connector during the 
install.
 Afterwards, the 6.0 connection fails --
 grub starts and lets me select the Debian entry or the recovery entry, but the 
boot fails
with a message that it cannot find 
/dev/disk/by-uuid/15f48ced-09a9-43a7-be73-c0fd7554dc14 .

Switching back to the 3.0 connector lets me run the system, which is a 
get-around I'm using now.

I'm guessing there isn't SATA 6.0 support.


Package-specific info:

Boot method: cd
Image version: 6.0.5 AMD64 netinstall
Date: Date and time of the install

Machine: Intel DZ68BC mother board + I5-2500K processor
Partitions: df -Tl will do; the raw partition table is preferred

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00035b26

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1 262 2103296   82  Linux swap / Solaris
Partition 1 does not end on cylinder boundary.
/dev/sda2   * 262 524 2097152   83  Linux
Partition 2 does not end on cylinder boundary.
/dev/sda32873940152428800   83  Linux
/dev/sda49401   40986   253710337f  W95 Ext'd (LBA) 
   
Partition 4 does not start on physical sector boundary. 
   
/dev/sda59401   22455   10482   83  Linux   
   
/dev/sda6   22455   2882851197646   83  Linux   
   
/dev/sda7   28829   3490748827392   83  Linux   
   
/dev/sda8   34907   4098648827392   83  Linux   

/dev/sda8 on / type ext4 (rw,errors=remount-ro)

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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.

Before I installed squeeze, I installed Suse 12.1 on /dev/sda2,
 Xubuntu 12.04 on /dev/sda6,
 Ubuntu 12.04 on /dev/sda7
All worked with the 6.0 SATA connection. 

I strongly suspect they benefit from using Linux kernel 3.2.0 .

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110106+squeeze4+b1
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux foveal5 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM 
Controller [8086:0100] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:201c]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Sandy Bridge PCI 
Express Root Port [8086:0101] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy 
Bridge Integrated Graphics Controller [8086:0112] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:201c]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Cougar 
Point HECI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:201c]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V 
Gigabit Network Connection [8086:1503] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:201c]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 

Bug#673110: debian-installer: wheezy installer on macmini3, 1 should run gptsync before reboot

[mike warren]

Package: debian-installer
Version: 20110106+b1
Severity: normal
Tags: d-i

Dear Maintainer,

I recently re-installed after replacing a drive on macmini3,1 which worked
nearly flawlessly except
that I needed to drop to a shell and install gptsync and run it during the now
we'll reboot dialog at
the end. I believe this is needed if anything was changed in partitioning. Of
course, one may run gptsync
from rEFIt or the Mac OS X installer instead, but since gptsync is packaged and
works fine it would be
great to just run it.

I note that guided partitioning used a biosgrub partition, which is needed for
bios compatibility mode
on mac hardware, from what I gather. The installer also selected grub-pc, which
would be correct for
bios compatibility -- however, the MBR needs to be correct for (at least) the
default Apple bootloader
to try. I had rEFIt installed on a USB key, and was installing from a
(different) USB key but wanted to do
away with rEFIt (and OS X) for this one.

Otherwise, the installer worked great, and continues to look better and better.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120516081605.19088.60302.report...@pangea.cg.shawcable.net

Bug#671751: installation-reports: wheezy nearly works on macmini3, 1 except for missing gptsync

[mike warren]

Package: installation-reports
Severity: important

Dear Maintainer,

Overall, the wheezy installer works great on macmini3,1 with the exception
of syncing GPT/MBR partition tables for default-bootloader-based booting.

-- Package-specific info:

Boot method: USB
Image version: hd-media wheezy daily build from May 1, 2012
Date: Date and time of the install

Machine: macmini3,1
Partitions: df -Tl will do; the raw partition table is preferred

gfdisk --list /dev/sda reports:

Disk /dev/sda: 750 GB, 750153761280 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System 
/dev/sda1   1   18001   83  Linux 
Warning: Partition 1 does not end on cylinder boundary.   
/dev/sda2   *   1  32  249007   83  Linux 
Warning: Partition 2 does not end on cylinder boundary.   
/dev/sda3   *  32  63  249007   83  Linux 
Warning: Partition 3 does not end on cylinder boundary.   
/dev/sda4  63   91202   732074017   83  Linux 

df -Tl reports:

Filesystem  Type  1K-blocks   Used Available Use% Mounted on
rootfs  rootfs682892580  409831340 238881556  64% /
udevdevtmpfs3949748  0   3949748   0% /dev
tmpfs   tmpfs791256972790284   1% /run
/dev/mapper/pangea-root ext4  682892580  409831340 238881556  64% /
tmpfs   tmpfs  5120  4  5116   1% /run/lock
tmpfs   tmpfs   1582508 763596818912  49% /tmp
tmpfs   tmpfs   1582508 16   1582492   1% /run/shm
/dev/sda2   ext2 234297  18237203560   9% /boot


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

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
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:[E]

Comments/Problems:

If you edit the partitions at all, with at least the newer macmini3,1
firmware, the default Apple bootloader (hold option to get to 
it) won't recognize the debian (biosgrub) bootloader until you run 
gptsync. This can be done from rEFIt, for example, but it's also in 
Debian so dropping to a shell and doing the following immediately 
before reboot is a good workaround for now: 
 
chroot /target 
apt-get install gptsync 
gptsync /dev/sda 
 
It seems the installer is already detecting we're on an EFI-based mac 
since it's setting up the required biosgrub partition properly. Guided
partitioning also works well. I was installing this time with no OS X
partition at all. Note that the lack of GPT/MBR syncing won't be quite
as much of an issue if you're using a bootloader like rEFIt. Also note
there's a ~30 second pause (grey screen) on boot if they only bootable
partition is an (un-blessed) Debian system.

Below, I don't know where the installer version information comes from, but
I definitely downloaded a wheezy daily build. If there's a way to get the 
version
off the image itself, I can still do that. Note that I did not yet install
B43 firmware for the wireless and that I upgraded the RAM to 8GB.

Overall, the installer just keeps getting better and better! 

One suggestion I have is to do something when you select a menu item from 
the main menu as it sort of seems like it's just hanging currently.

-- 

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=5.0 (lenny) - installer build 20090123lenny4
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
umame -a: Linux pangea 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009 
x86_64 unknown
lspci -knn: 00:00.0 Host bridge [0600]: nVidia Corporation Device [10de:0a82] 
(rev b1)
lspci -knn: 00:00.1 RAM memory [0500]: nVidia Corporation Device [10de:0a88] 
(rev b1)
lspci -knn: 00:03.0 ISA bridge [0601]: nVidia Corporation Device [10de:0aae] 
(rev b2)
lspci -knn: 00:03.1 RAM memory [0500]: nVidia Corporation Device [10de:0aa4] 
(rev b1)
lspci -knn: 00:03.2 SMBus [0c05]: nVidia Corporation Device [10de:0aa2] (rev b1)
lspci -knn: 00:03.3 RAM memory [0500]: nVidia 

Bug#641685: Debian Installer writes false network configuration

[Mike 'AmP' Liebsch]

Package: debian-installer
Version:  not sure - used as installer on debian-6.0.2.1-amd64-netinst.iso

Short: When you change your network configuration twice during installation 
only the first (and surely false) one is written to system.

Long: You install - after you let the installer send DHCP requests you're able 
to provide your IP address information.  If you have a typo or (like me) choose 
the wrong net, the installer is unable to connect to the mirrors. So I went 
back to Configure Network and provided the right address, net and router. 
Installation went fine and i rebooted.

First thing after reboot i wanted to install some packages and was very 
surprised to see, that my very first and false information was written to 
/etc/network/interfaces.

I hope these are all the information you may need. 

regards,
 -AmP




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/91f056db-58e4-4edd-b858-0736d8a49...@ampersize.org

Bug#637284: Can't install wheezy on a 2011 iMac

[Mike Hore]

On 10/08/11 6:55 PM, Gergely Nagy wrote:

reassign 637284 installation-reports
thanks

Installation reports (failure or success) should not be reported against
the Work Needing and Prospective Packages virtual package, but against
installation-reports.


Ah, thanks Gergely -- I'm still new to this  :-)

-- Mike.




It can then be reassigned from there to the appropriate package, if
confirmed.

I have reassigned the report to installation-reports, so it gets
forwarded to the right place.




--
---
  Mike Horemike_h...@aapt.net.au
---



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e424bd5.4080...@aapt.net.au

Bug#618929: Additional info

[Tremblay, Mike A]

It is certainly possible that my CD drive is flaky. Do you know of a
diagnostic test in the Debian release that I could use to simply read
several known good CDs for errors?

Thanks,
Mike

-Original Message-
From: Miguel Figueiredo [mailto:el...@debianpt.org] 
Sent: Sunday, April 03, 2011 10:21 AM
To: Tremblay, Mike A
Cc: 618...@bugs.debian.org
Subject: Re: Bug#618929: Additional info

Hi,

according to the log you sent grub was successfully installed:

Mar 25 17:22:36 grub-installer: info: Installing grub on '/dev/sda'
Mar 25 17:22:37 grub-installer: info: grub-install supports --no-floppy
Mar 25 17:22:37 grub-installer: info: Running chroot /target
grub-install  --no-floppy --force /dev/sda
Mar 25 17:22:57 grub-installer: Installation finished. No error
reported.
Mar 25 17:22:57 grub-installer: info: grub-install ran successfully

 Mar 25 16:55:48 kernel: [ 3697.543489] sr 1:0:1:0: [sr0] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
 Mar 25 16:55:48 kernel: [ 3697.543539] sr 1:0:1:0: [sr0] Sense Key :
Illegal Request [current] 
 Mar 25 16:55:48 kernel: [ 3697.543587] Info fld=0x504c0, ILI
 Mar 25 16:55:48 kernel: [ 3697.543661] sr 1:0:1:0: [sr0] Add. Sense:
Illegal mode for this track
 Mar 25 16:55:48 kernel: [ 3697.543740] sr 1:0:1:0: [sr0] CDB:
Read(10): 28 00 00 05 04 c0 00 00 02 00
 Mar 25 16:55:48 kernel: [ 3697.543823] end_request: I/O error, dev
sr0, sector 1315584

On your log there are also several read errors from the CD used to
install the system. 
This could be due to bad hardware, bad disk or even a driver issue. 
The read errors can lead to unexpected result.

I would be great if you burn an image on a cd-recorder /disc known to
work properly and verify if the burned cd is properly written/read
before installing.

You can also use a daily image with a newer kernel, those are available
on:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/is
o-cd/

Also Debian 6.0 got an update:
http://cdimage.debian.org/debian-cd/6.0.1a/i386/iso-cd/

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org



This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this 
 
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/7575324f915a05448800386f6ceaf3670e049...@aeromsg2.aero.ball.com

Bug#618929: Additional info

[Tremblay, Mike A]

I have discovered, purely by accident, that if I have my Windows 98 O/S
disc in the CD drive as the Linux system is powering up, a program on
the Win98 disc will gain control and offer me the choices  Boot from
Hard disc, or Boot from CD ROM. On selecting the Hard disc choice, the
Linux systems boots. I briefly see the GRUB prompt on the screen as the
process starts, but it quickly scrolls off as the other start-up
messages are output.

 

I would rather the system start without the need for a CD in the drive.

 

Mike




This message and any enclosures are intended only for the addressee.  Please  
notify the sender by email if you are not the intended recipient.  If you are  
not the intended recipient, you may not use, copy, disclose, or distribute this 
 
message or its contents or enclosures to any other person and any such actions  
may be unlawful.  Ball reserves the right to monitor and review all messages  
and enclosures sent to or from this email address.

Bug#618929: Debian bootup/install bug report

[Mike Tremblay]

Package: Installer

  Problem: Will not boot after installation



  System: ~2000 vintage HP Vecta XU, 6/200, system D4365N, dual Pentium II 
processors, 64 MB RAM, three hard drives - 200G IDE, two 1.3 G SCSI (Quantum 
Fireball), network card, no USB 

   

  The most common outcome of an installation session is that the bootup step at 
the end of the session results in the letters GRUB appearing in the upper 
left corner of the screen with the blinking cursor to the right of the B, and 
nothing else. The system does not respond to any keystrokes, or combination of 
CTRL-key, ALT-key, etc. It seems like the system is waiting for keyboard 
input, but the keyboard is not enabled. If I had a responsive keyboard AND I 
knew what to type, this could be an acceptable outcome, since it does occur 
most times.

   

  What I've tried: All combinations of discs (all three drives plugged in, each 
one separately, all combinations of two drives).  The drives all appear to be 
accessed but the boot ultimately fails as described above.

   

  I've tried most combinations of answering the partitioning questions and 
placement of the boot sector.

   

  The failures are not all as stated above; it's just the most common outcome. 
Other results are  GRUB being continuously written to the screen, until I 
power off.

   

  I was able to get the boot to succeed once, but that particular system build 
led to other problems causing me to attempt a second install. This one time the 
result was that the system would, after powering on and all the verbiage of the 
boot up process, presents me with a login prompt, accepts my login and allows 
me to use the system. I was able to run with this system for a couple of weeks, 
loading packages, etc. until I filled the discs and had to start over.  The 
disc full issue occurred because the IDE drive (most of the system's capacity) 
was not mounted. I did not realize this until the disc full failure. 

   

  The version of Debian is 2.4. I have a 15 CD set, purchased in roughly 2004. 
Last week I downloaded disc image 1 of Debian 6.0 in hopes that the boot 
problem has been fixed, but the results are the same.

   

  Thanks,

  Mike Tremblay

   

Bug#554896: closed by Miguel Figueiredo el...@debianpt.org ()

[mike]

this bug persists - the recommended RC also FAILED to Install with this
network card in place.  The installation freezes at network device
detection.

mike


 This is an automatic notification regarding your Bug report
 which was filed against the installation-reports package:

 #554896: installation-reports

 It has been closed by Miguel Figueiredo el...@debianpt.org.

 Their explanation is attached below along with your original report.
 If this explanation is unsatisfactory and you have not received a
 better one in a separate message then please contact Miguel Figueiredo
 el...@debianpt.org by
 replying to this email.


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






-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1bf9168b8aeda1ed1d90ffef7b5818be.squir...@mmail.virtdom.com

Bug#608850: Unable to continue without a bootloader

[Mike Perry]

Package: live-installer

While testing an install of squeeze_live_beta2 I was unable to
continue without a bootloader. When selecting Continue without boot
loader or going directly to Finish the installation then selecting
Continue without boot loader you are brought back to the menu. You
cannot finish the installation until you select either grub (or
potentially lilo although I did not test that).

kthxbye

~Mike



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikhaojq2gnibkff_a+2kyigchgqfzg=vupco...@mail.gmail.com

Bug#602292: Squeeze disk detection failed on MacBook Air 11.6

[mike dentifrice]

 This is a bug in the Debian installer; for some reason it doesn't
 include the ata_generic driver.

Thanks for the clarification!

Another bugreport regarding this was sent a week ago, including a patch:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605325

-- 
mike dentifrice fl...@poivron.org




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

Re: Bug#605009: serious performance regression with ext4

[Mike Hommey]

On Mon, Nov 29, 2010 at 07:18:17AM +0100, Guillem Jover wrote:
  What's going on here?  sync_file_range() is a Linux specific system
  call that has been around for a while.  It allows program to control
  when writeback happens in a very low-level fashion.  The first set of
  sync_file_range() system calls causes the system to start writing back
  each file once it has finished being extracted.  It doesn't actually
  wait for the write to finish; it just starts the writeback.
 
 Hmm, ok so what about posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
 instead, skimming over the kernel source seems to indicate it might
 end up doing more or less the same thing but in a portable way?

On the other hand, there is no guarantee that other kernels do the same,
nor that Linux will keep doing it in the future. Using sync_file_range
and possibly the corresponding BSD syscall seems a better solution.
(and apparently the assumption with fadvise doesn't work with xfs)

Mike


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

Re: Bug#605009: serious performance regression with ext4

[Mike Hommey]

On Tue, Nov 30, 2010 at 10:35:11AM +0100, Samuel Thibault wrote:
 Mike Hommey, le Tue 30 Nov 2010 10:07:55 +0100, a écrit :
  On Mon, Nov 29, 2010 at 07:18:17AM +0100, Guillem Jover wrote:
What's going on here?  sync_file_range() is a Linux specific system
call that has been around for a while.  It allows program to control
when writeback happens in a very low-level fashion.  The first set of
sync_file_range() system calls causes the system to start writing back
each file once it has finished being extracted.  It doesn't actually
wait for the write to finish; it just starts the writeback.
   
   Hmm, ok so what about posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
   instead, skimming over the kernel source seems to indicate it might
   end up doing more or less the same thing but in a portable way?
  
  On the other hand, there is no guarantee that other kernels do the same,
 
 Err, that's posix.

Being posix doesn't guarantee that posix_fadvise(fd, 0, 0,
POSIX_FADV_DONTNEED) is going to start write back, which is the desired
effect, but not what you may actually get, depending on the kernel.

Mike


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

Re: Bug#603578: installation-reports: Fails to boot after successful install on a btrfs root

[mike]

I have the same problem. Btrfs in the initramfs depends on crc32c, but 
that module is not included in the initramfs image. I am not sure of the 
sequence of events and how that is missed but the bottom line is that 
crc32c.ko needs to be listed as a dependency and included.




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ce79fba.4030...@tiedyenetworks.com

Bug#604176: kernel-wedge: add ralink wireless drivers to nic-wireless-modules

[Mike Miller]

Package: kernel-wedge
Version: 2.71
Severity: normal
Tags: d-i patch

Please add rt61pci, rt73usb, rt2860sta, and rt2870sta to nic-wireless-modules.
I have two systems with perfect wifi operation once the system
is installed, provided firmware-ralink is also installed.  However I cannot
test the beta installer over wifi because the drivers are not loaded.



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kernel-wedge depends on:
ii  debhelper 8.0.0  helper programs for debian/rules
ii  make  3.81-8 An utility for Directing compilati

kernel-wedge recommends no packages.

kernel-wedge suggests no packages.
Index: kernel-wedge/modules/nic-wireless-modules
===
--- kernel-wedge/modules/nic-wireless-modules	(revision 65711)
+++ kernel-wedge/modules/nic-wireless-modules	(working copy)
@@ -23,8 +23,10 @@
 rt2500pci ?
 rt2500usb ?
 rt2400pci ?
-# rt61pci - needs firmware
-# rt73usb - needs firmware
+rt61pci ?
+rt73usb ?
+rt2860sta ?
+rt2870sta ?
 
 # Crypto modules needed for ieee80211 WEP support
 ecb ?

Bug#603021: installation-reports: UI doesn't update while downloading packages in tasksel

[Mike Miller]

Package: installation-reports
Severity: normal

I observed the same behavior on my install.  I switched to VT-2 and confirmed
the installer was downloading packages but no progress bar or status was shown
on the graphically installer until it completely finished installing all
packages.

- mike



-- Package-specific info:

Boot method: USB
Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta1/amd64/iso-cd
/debian-squeeze-di-beta1-amd64-netinst.iso
Date: 2010-11-14 15:35:15 -0500

Machine: Custom ASUS P5QL PRO / Pentium(R) Dual-Core CPU E5200
Partitions: df -Tl will do; the raw partition table is preferred


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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.



-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101020
X_INSTALLATION_MEDIUM=hd-media

==
Installer hardware-summary:
==
uname -a: Linux tesla 2.6.32-5-amd64 #1 SMP Fri Oct 15 00:56:30 UTC 2010 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM 
Controller [8086:2e20] (rev 03)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d3]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset PCI 
Express Root Port [8086:2e21] (rev 03)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #4 [8086:3a37]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #5 [8086:3a38]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #6 [8086:3a39]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB2 EHCI Controller #2 [8086:3a3c]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 
Family) HD Audio Controller [8086:3a3e]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82fe]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) 
PCI Express Root Port 1 [8086:3a40]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) 
PCI Express Root Port 6 [8086:3a4a]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #1 [8086:3a34]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #2 [8086:3a35]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB UHCI Controller #3 [8086:3a36]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 
Family) USB2 EHCI Controller #1 [8086:3a3a]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev 90)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JIB (ICH10) LPC 
Interface Controller [8086:3a18]
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043

Bug#603685: Missing Chinese, Japanese and Korean characters in Select your location list

[Mike Hommey]

On Tue, Nov 16, 2010 at 07:39:02PM +0800, Anthony Wong wrote:
 Package: debian-installer
 Version: 20101116-3 daily snapshot
 Severity: important
 
 In graphical installer, if I choose Chinese (Simplified), Chinese
 (Traditional), Japanese or Korean as the language, there will be
 some missing characters in the next page (Selection your location).
 Please see the attached screenshots and notice the unicode squares.

Moreover, on your screenshots, we can see at least two fonts being used
in the same sentence. This makes my eyes bleed.

Mike



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

Bug#601011: debootstrap: Fails without an error when it can't create devices

[Mike Hommey]

Package: debootstrap
Version: 1.0.25
Severity: important

When debootstrap can't extract devices.tar.gz for some reason, it exists
with an error code 2, but doesn't say anything as to why it failed.

Following with strace, it appears the one failing is tar, because it can't
extract (mknod) the devices from devices.tar.gz. This happened on my system
because I was trying to debootstrap from within an lxc instance created
with the default template which disabled a whole bunch of devices.

Please at least handle the error and display tar's error message.

A bonus point if you just ignore the error, as the failing devices here were
really not important to the chroot:
dev/full
dev/kmem
dev/loop*
dev/mem
dev/port
dev/ram*

Cheers,

Mike

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  wget  1.12-2.1   retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg 1.4.10-4   GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20101022130428.16347.31045.report...@jigen.glandium.org

Bug#571136: please remove useless devices from devices.tar.gz

[Mike Hommey]

On Tue, Feb 23, 2010 at 07:58:17PM +0100, Marco d'Itri wrote:
 Package: debootstrap
 Version: 1.0.20
 Severity: normal
 
 devices.tar.gz should contain only the devices which are strictly
 needed, even if udev is not installed the others can be created by
 makedev.
 
 At least the ram* devices should be removed because they were needed
 by initrds and are not useful anymore.
 
 Why create loop*?
 
 Why create mem kmem core port?
 
 FYI, the only devices needed by udev to start are null and console.

FWIW, the inclusion of these devices in devices.tar.gz makes debootstrap
fail without even a message (filed a separate bug for that) when tar
can't mknod the devices (which happens from within a lxc container with
the default template).

Note cdebootstrap either doesn't create them or doesn't care if it can't
create them.

Cheers,

Mike



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

Bug#601011: debootstrap: Fails without an error when it can't create devices

[Mike Hommey]

On Fri, Oct 22, 2010 at 03:04:28PM +0200, Mike Hommey wrote:
 Package: debootstrap
 Version: 1.0.25
 Severity: important
 
 When debootstrap can't extract devices.tar.gz for some reason, it exists
 with an error code 2, but doesn't say anything as to why it failed.
 
 Following with strace, it appears the one failing is tar, because it can't
 extract (mknod) the devices from devices.tar.gz. This happened on my system
 because I was trying to debootstrap from within an lxc instance created
 with the default template which disabled a whole bunch of devices.
 
 Please at least handle the error and display tar's error message.
 
 A bonus point if you just ignore the error, as the failing devices here were
 really not important to the chroot:
 dev/full
 dev/kmem
 dev/loop*
 dev/mem
 dev/port
 dev/ram*

FWIW, cdebootstrap doesn't create these expect dev/full, which it fails
to create but doesn't care.

Mike



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

Bug#597799: installation-report: GPT related issues

[Mike Hommey]

On Thu, Sep 23, 2010 at 12:28:45PM -0400, Lennart Sorensen wrote:
 On Thu, Sep 23, 2010 at 03:39:08PM +0200, Mike Hommey wrote:
  The disk is a new one, though I didn't check if there was a
  pre-existing partitioning (but I really doubt it). OTOH, the disk is
  2000GB, which is not quite over 2TB, but close enough that it may have
  mattered.
 
 Certainly MBR partitions do not work when you pass 2TB (2^32 512byte
 sectors).  After all if it had a partition table already, it would have
 just used it.

Well, 2000GB should still work with MBR partitions.

 Now so far I have been running a few machines with GPT partitions on a
 2.5TB raid for a few years and with grub2 it works just fine, even with
 a machine that just uses a plain old BIOS.

The point is, grub just works, if I don't forget to create a small boot
partition, which I didn't know I had to create until grub-setup failed
because of the lack of it.

Mike



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

Bug#597799: installation-report: GPT related issues

[Mike Hommey]

On Fri, Sep 24, 2010 at 11:38:09AM -0400, Lennart Sorensen wrote:
 Disk /dev/sda: 2250.1 GB, 2250128752640 bytes
 255 heads, 63 sectors/track, 273562 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Disk identifier: 0x
 
Device Boot  Start End  Blocks   Id  System
 /dev/sda1   1  267350  2147483647+  ee  EFI GPT
 
 So I would say there is no requirement for a /boot partition.  There might
 be a requirement for /boot to not be on LVM.  Not sure.

I probably haven't made myself clear enough. I was not talking about a
/boot partition, but about a GPT grub boot partition, or whatever grub
called it in its grub-setup failure message. One you give a bios_grub
flag. But then, maybe your core.img is small enough to fit in the 17.4kB
before the first partition. Here it doesn't. I made the boot partition
128kB big because I didn't have a clue and found that to be enough in
most cases through a google search, though seeing the size of my current
core.img, 32 or 64kB would have been enough.

Mike



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

Bug#597799: installation-report: GPT related issues

[Mike Hommey]

Package: installation-reports
Version: 2.42
Severity: important
Tags: squeeze



-- Package-specific info:

Boot method: network
Image version: 
http://ftp.nl.debian.org/debian/dists/lenny/main/installer-amd64/current/images/netboot/gtk/netboot.tar.gz
 17:58 26-06-10
Date: 22-09-2010

Machine: Custom-made i7 machine


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

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

Comments/Problems:

First, a little digression about the network card. The on-board network
controller is a Realtek controller for which the installer told me I needed
a non-free firmware. It happens that answering No left the network...
working. It would have been helpful if the installer told me the network
may still work without the firmware.

Back to the core of my issues. I went through a manual partitionning, and
didn't create a boot partition for the grub core image, assuming I was
creating an MBR partition. It turned out, in the end, that GRUB failed
because of that, because the partition table was GPT. I didn't see anything
about GPT being used (or maybe wasn't paying too much attention), and surely
the partitioner could issue a warning that no such partition was created and
that the risk is that GRUB can't be installed.

Other than that, everything went fine. Awesome installer.

Thanks

Mike

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100912
X_INSTALLATION_MEDIUM=netboot-gtk

==
Installer hardware-summary:
==
uname -a: Linux goemon 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI 
[8086:d131] (rev 11)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:7588]
lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI 
Express Root Port 1 [8086:d138] (rev 11)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation Core Processor 
System Management Registers [8086:d155] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
lspci -knn: 00:08.1 System peripheral [0880]: Intel Corporation Core Processor 
Semaphore and Scratchpad Registers [8086:d156] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
lspci -knn: 00:08.2 System peripheral [0880]: Intel Corporation Core Processor 
System Control and Status Registers [8086:d157] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
lspci -knn: 00:08.3 System peripheral [0880]: Intel Corporation Core Processor 
Miscellaneous Registers [8086:d158] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
lspci -knn: 00:10.0 System peripheral [0880]: Intel Corporation Core Processor 
QPI Link [8086:d150] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
lspci -knn: 00:10.1 System peripheral [0880]: Intel Corporation Core Processor 
QPI Routing and Protocol Registers [8086:d151] (rev 11)
lspci -knn: Subsystem: Device [0062:0088]
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: Micro-Star International Co., Ltd. Device [1462:7588]
lspci -knn: Kernel driver in use: ehci_hcd
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: Micro-Star International Co., Ltd. Device [1462:7588]
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.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 6 [8086:3b4c] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series 
Chipset PCI Express Root Port 8 [8086:3b50

Bug#597799: installation-report: GPT related issues

[Mike Hommey]

On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote:
 Back to the core of my issues. I went through a manual partitionning, and
 didn't create a boot partition for the grub core image, assuming I was
 creating an MBR partition. It turned out, in the end, that GRUB failed
 because of that, because the partition table was GPT. I didn't see anything
 about GPT being used (or maybe wasn't paying too much attention), and surely
 the partitioner could issue a warning that no such partition was created and
 that the risk is that GRUB can't be installed.

Oh I forgot to add this: the installed fdisk is pointless as the only
thing it can do is tell you to use parted, which supports GPT... except
parted is not installed. If the install is done on GPT, shouldn't parted
be installed (or any other fdisk equivalent supporting GPT)

Mike



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

Bug#597799: installation-report: GPT related issues

[Mike Hommey]

On Thu, Sep 23, 2010 at 09:29:55AM -0400, Lennart Sorensen wrote:
 On Thu, Sep 23, 2010 at 12:12:37PM +0200, Mike Hommey wrote:
  On Thu, Sep 23, 2010 at 08:13:26AM +0200, Mike Hommey wrote:
   Back to the core of my issues. I went through a manual partitionning, and
   didn't create a boot partition for the grub core image, assuming I was
   creating an MBR partition. It turned out, in the end, that GRUB failed
   because of that, because the partition table was GPT. I didn't see 
   anything
   about GPT being used (or maybe wasn't paying too much attention), and 
   surely
   the partitioner could issue a warning that no such partition was created 
   and
   that the risk is that GRUB can't be installed.
  
  Oh I forgot to add this: the installed fdisk is pointless as the only
  thing it can do is tell you to use parted, which supports GPT... except
  parted is not installed. If the install is done on GPT, shouldn't parted
  be installed (or any other fdisk equivalent supporting GPT)
 
 Was this a blank unused HD or had something else already been installed
 before?

 How big is the HD?
 
 I have not seen Debian efault to GPT unless the disk was over 2TB before,
 or unless windows 7 had already chosen to make it GPT.

The disk is a new one, though I didn't check if there was a
pre-existing partitioning (but I really doubt it). OTOH, the disk is
2000GB, which is not quite over 2TB, but close enough that it may have
mattered.

Mike



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