debian-installer_20170615+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Mar 2018 20:38:06 +0100
Source: debian-installer
Binary: debian-installer
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer - Debian Installer documentation
Changes:
 debian-installer (20170615+deb9u3) stretch; urgency=medium
 .
   * Bump Linux kernel version from 4.9.0-4 to 4.9.0-6.
Checksums-Sha1:
 f230e309702ad41fffd0b027f2afbee842711e28 3622 
debian-installer_20170615+deb9u3.dsc
 e07a32877cc09b8c4d1375c5c99cfaa20a204ec8 1387486 
debian-installer_20170615+deb9u3.tar.gz
 78c04f69aa1b17e4325e055e0b3c4ff4af8927ca 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 988e84986454e4780df979883d26b30abd7b42bf2a7b45128a0ec7508a30906b 3622 
debian-installer_20170615+deb9u3.dsc
 e89961fda069262bac20ed80e472a1e210ca78c17be1853490b0d18bcd7e3f38 1387486 
debian-installer_20170615+deb9u3.tar.gz
 d8e6a6e8f57f42c174a161e86e50e90de57cd456f4594b18ee590c1f135cc6df 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Files:
 1f50b13f305db8e1bf0b91187e2a44eb 3622 devel optional 
debian-installer_20170615+deb9u3.dsc
 f8c8e0da4524c0ecafac7f54df88f0d2 1387486 devel optional 
debian-installer_20170615+deb9u3.tar.gz
 5dd3f504686cd640b9cf8f41137ad2a0 7045 devel optional 
debian-installer_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqctuIACgkQ/5FK8MKz
VSAYgw/9FClfp6GYsuHt8JquRKJCIsqI3CeTdMQdezEUz3PUQZqHZ3DpL+AqG7e2
dGiCxMFlY+Ex4wUeU92h5Dtiv+xY1/sW/azbVF8vhny9/eL+1i6hqR/DZ5enB5UD
VNYVr2pihSfHvpnokhzQVrTQc/hlzXesX3tepGEkNDTCazMB3EqVdgy3EZPqe/FP
6dPQRkRWpWOGtxG06efALc6Yt7V5lKBRXYn5uPOJhrfCbboKmdW8Ct99pp2Qojau
3ctbt56d8489EkLvouRA5nwacBCZtY82c1L9aJRHpVbrPTcFRS1C9xVOKz8uKSuK
5OrDTYOvZNfwFzG3+i46YY+aAeBFueSsfSMcOcXA9NDYeOt6cglZ+lC8exgOL+Fv
DZsWxGTnXatzsstPYEcxqN2vQtvdwkBQxjTzxU51x6mm2R0YpQGCfl+hM7QG65KB
cIUJdplwN5Mmdl0I+FB2Uy6hlytQB9ohNIH2h94gihI1nEcwGHvK2fmisSHKx58L
/KDlx4uex64R22NgE2daZrhVi4Hw2gSMbJExzmhTsOFQxg4F8xZ02NGREeLBivRO
Q9POJ8+vDrddZJ+znfZXk0ITDdjKqcxvMO+/fBI56a36QQptTnyIruCNdY6q/QbM
xeTbJHKf/dPSGqB7+vEifGsXVy0Gdey6cao+uhJow1n5m1RDRDE=
=2l2Q
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Accepted debian-installer 20170615+deb9u3 (source) into proposed-updates->stable-new, proposed-updates

[Cyril Brulebois]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Mar 2018 20:38:06 +0100
Source: debian-installer
Binary: debian-installer
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer - Debian Installer documentation
Changes:
 debian-installer (20170615+deb9u3) stretch; urgency=medium
 .
   * Bump Linux kernel version from 4.9.0-4 to 4.9.0-6.
Checksums-Sha1:
 f230e309702ad41fffd0b027f2afbee842711e28 3622 
debian-installer_20170615+deb9u3.dsc
 e07a32877cc09b8c4d1375c5c99cfaa20a204ec8 1387486 
debian-installer_20170615+deb9u3.tar.gz
 78c04f69aa1b17e4325e055e0b3c4ff4af8927ca 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 988e84986454e4780df979883d26b30abd7b42bf2a7b45128a0ec7508a30906b 3622 
debian-installer_20170615+deb9u3.dsc
 e89961fda069262bac20ed80e472a1e210ca78c17be1853490b0d18bcd7e3f38 1387486 
debian-installer_20170615+deb9u3.tar.gz
 d8e6a6e8f57f42c174a161e86e50e90de57cd456f4594b18ee590c1f135cc6df 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Files:
 1f50b13f305db8e1bf0b91187e2a44eb 3622 devel optional 
debian-installer_20170615+deb9u3.dsc
 f8c8e0da4524c0ecafac7f54df88f0d2 1387486 devel optional 
debian-installer_20170615+deb9u3.tar.gz
 5dd3f504686cd640b9cf8f41137ad2a0 7045 devel optional 
debian-installer_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqctuIACgkQ/5FK8MKz
VSAYgw/9FClfp6GYsuHt8JquRKJCIsqI3CeTdMQdezEUz3PUQZqHZ3DpL+AqG7e2
dGiCxMFlY+Ex4wUeU92h5Dtiv+xY1/sW/azbVF8vhny9/eL+1i6hqR/DZ5enB5UD
VNYVr2pihSfHvpnokhzQVrTQc/hlzXesX3tepGEkNDTCazMB3EqVdgy3EZPqe/FP
6dPQRkRWpWOGtxG06efALc6Yt7V5lKBRXYn5uPOJhrfCbboKmdW8Ct99pp2Qojau
3ctbt56d8489EkLvouRA5nwacBCZtY82c1L9aJRHpVbrPTcFRS1C9xVOKz8uKSuK
5OrDTYOvZNfwFzG3+i46YY+aAeBFueSsfSMcOcXA9NDYeOt6cglZ+lC8exgOL+Fv
DZsWxGTnXatzsstPYEcxqN2vQtvdwkBQxjTzxU51x6mm2R0YpQGCfl+hM7QG65KB
cIUJdplwN5Mmdl0I+FB2Uy6hlytQB9ohNIH2h94gihI1nEcwGHvK2fmisSHKx58L
/KDlx4uex64R22NgE2daZrhVi4Hw2gSMbJExzmhTsOFQxg4F8xZ02NGREeLBivRO
Q9POJ8+vDrddZJ+znfZXk0ITDdjKqcxvMO+/fBI56a36QQptTnyIruCNdY6q/QbM
xeTbJHKf/dPSGqB7+vEifGsXVy0Gdey6cao+uhJow1n5m1RDRDE=
=2l2Q
-END PGP SIGNATURE-

debian-installer_20170615+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Mapping stretch to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Mar 2018 20:38:06 +0100
Source: debian-installer
Binary: debian-installer
Architecture: source
Version: 20170615+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Description:
 debian-installer - Debian Installer documentation
Changes:
 debian-installer (20170615+deb9u3) stretch; urgency=medium
 .
   * Bump Linux kernel version from 4.9.0-4 to 4.9.0-6.
Checksums-Sha1:
 f230e309702ad41fffd0b027f2afbee842711e28 3622 
debian-installer_20170615+deb9u3.dsc
 e07a32877cc09b8c4d1375c5c99cfaa20a204ec8 1387486 
debian-installer_20170615+deb9u3.tar.gz
 78c04f69aa1b17e4325e055e0b3c4ff4af8927ca 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Checksums-Sha256:
 988e84986454e4780df979883d26b30abd7b42bf2a7b45128a0ec7508a30906b 3622 
debian-installer_20170615+deb9u3.dsc
 e89961fda069262bac20ed80e472a1e210ca78c17be1853490b0d18bcd7e3f38 1387486 
debian-installer_20170615+deb9u3.tar.gz
 d8e6a6e8f57f42c174a161e86e50e90de57cd456f4594b18ee590c1f135cc6df 7045 
debian-installer_20170615+deb9u3_source.buildinfo
Files:
 1f50b13f305db8e1bf0b91187e2a44eb 3622 devel optional 
debian-installer_20170615+deb9u3.dsc
 f8c8e0da4524c0ecafac7f54df88f0d2 1387486 devel optional 
debian-installer_20170615+deb9u3.tar.gz
 5dd3f504686cd640b9cf8f41137ad2a0 7045 devel optional 
debian-installer_20170615+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAlqctuIACgkQ/5FK8MKz
VSAYgw/9FClfp6GYsuHt8JquRKJCIsqI3CeTdMQdezEUz3PUQZqHZ3DpL+AqG7e2
dGiCxMFlY+Ex4wUeU92h5Dtiv+xY1/sW/azbVF8vhny9/eL+1i6hqR/DZ5enB5UD
VNYVr2pihSfHvpnokhzQVrTQc/hlzXesX3tepGEkNDTCazMB3EqVdgy3EZPqe/FP
6dPQRkRWpWOGtxG06efALc6Yt7V5lKBRXYn5uPOJhrfCbboKmdW8Ct99pp2Qojau
3ctbt56d8489EkLvouRA5nwacBCZtY82c1L9aJRHpVbrPTcFRS1C9xVOKz8uKSuK
5OrDTYOvZNfwFzG3+i46YY+aAeBFueSsfSMcOcXA9NDYeOt6cglZ+lC8exgOL+Fv
DZsWxGTnXatzsstPYEcxqN2vQtvdwkBQxjTzxU51x6mm2R0YpQGCfl+hM7QG65KB
cIUJdplwN5Mmdl0I+FB2Uy6hlytQB9ohNIH2h94gihI1nEcwGHvK2fmisSHKx58L
/KDlx4uex64R22NgE2daZrhVi4Hw2gSMbJExzmhTsOFQxg4F8xZ02NGREeLBivRO
Q9POJ8+vDrddZJ+znfZXk0ITDdjKqcxvMO+/fBI56a36QQptTnyIruCNdY6q/QbM
xeTbJHKf/dPSGqB7+vEifGsXVy0Gdey6cao+uhJow1n5m1RDRDE=
=2l2Q
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of debian-installer_20170615+deb9u3_source.changes

[Debian FTP Masters]

debian-installer_20170615+deb9u3_source.changes uploaded successfully to 
localhost
along with the files:
  debian-installer_20170615+deb9u3.dsc
  debian-installer_20170615+deb9u3.tar.gz
  debian-installer_20170615+deb9u3_source.buildinfo

Greetings,

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

Bug#892082: debian-installer: PCMCIA cards not assigned resources on DELL Latitude CPx J650GT

[Selina Gross]

Package: debian-installer
Version: debian-9.3.0-i386-netinst.iso
Severity: normal

Dear Maintainer,

trying to install using the network installer CD, it fails autodetecting the 
network card. The NIC cannot be manually detected either using the F2 console 
of the installer, as it does not get assigned resources.

The problem appears to be specific to this laptop, since the same installer CD 
works flawlessly on another (newer) laptop using the same NIC.
Possibly the issue relates to the PCMCIA bridge (lspci reports it as):

00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)

Maybe the issue appears only in conjunction with 5V 16 bit cards (I have no 
others to test).


Observations:
The driver "yenta_socket" gets loaded and assigns an IRQ (IRQ 11 in this case) 
to the bridge itself, which then correctly reports that cards are inserted.

Then, however, nothing is done about the cards, IOW, there is no indication in 
e.g. dmesg that they are assigned resources.

Network card detection then fails to find the NIC (but other cards, like a 
modem aren't assigned resources either). The driver (pcnet_cs in this case) can 
be modprobed manually and loads, but does not work either.

Unloading and re-loading the pcmcia, yenta etc. modules does not change this 
behaviour, nor does forcing yenta_socket to ignore the BIOS settings, or 
removing and re-inserting the cards.

Upgrading the BIOS to the latest version (V16 from 2003) did not change this, 
either.

After completing the installation without network access, when the resulting 
minimal system boots, the cards do get properly initialized, assigned 
resources, and are then detected normally by pcnet_cs (or the relevant drivers) 
and work normally. This suggests that the issue lies with the installer script 
and not with the drivers themselves.


Thank you for your continued efforts and kind regards!


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: (solved) Re: wireless fail after stretch installation

[Philip Hands]

Jude DaShiell  writes:

...
> Many ways exist to solve this problem and it took a while to find out
> what to do and how because there's more and better support from
> debian-users than is in debian wiki

If you can see a way to improve the information on the wiki, please go
ahead and do so -- that's what wikis are for, after all.

> or debian documentation.

We also have a bug tracker, and patches are generally welcome.

> I had learned how to do this earlier but apparently an individual
> known as longwind from China ran into this problem after I had learned
> to solve it on this end and the original message I read from Brian had
> a solution I hadn't read earlier and hadn't tried yet which involved
> far fewer steps.  Fortunately I have a hard drive available so I will
> try Brian's solution out on this end and see how it works.

Contributions can take a while to get incorporated, but if you come up
with an improvement for the documentation and/or the code (assuming that
it doesn't break things elsewhere) it will generally get used.

Please take notes during your testing, and try to find a way to use your
findings that will help people bumping into the same issue in future.

> Thanks for your assistance and interest.

Thank you for your future contributuons :-)

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


signature.asc
Description: PGP signature

discover_2.1.2-7.1+deb9u1_source.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Mapping stretch to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Feb 2018 21:38:40 +0200
Source: discover
Binary: discover libdiscover2 libdiscover-dev
Architecture: source
Version: 2.1.2-7.1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Adrian Bunk 
Description:
 discover   - hardware identification system
 libdiscover-dev - hardware identification library development files
 libdiscover2 - hardware identification library
Closes: 876388
Changes:
 discover (2.1.2-7.1+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Use correct type for the length parameter of the getline() call,
 thanks to Anatoly Borodin and Simon Quigley for writing and for
 forwarding the patch (Closes: #876388, LP: #1718687).
Checksums-Sha1:
 bde86ae0c88c968f7b7d10b3c90bbce8d63a 2038 discover_2.1.2-7.1+deb9u1.dsc
 1358a88e798b9566415be8b9b37e213ad9c89c9a 188594 
discover_2.1.2-7.1+deb9u1.diff.gz
Checksums-Sha256:
 792665fc3975c836e6d05ae2203bbec9cdf851a83afd8a0aa9f9fdcc057fc66b 2038 
discover_2.1.2-7.1+deb9u1.dsc
 35c8122525ca046b0b3a1e7bfb2fdc2a6d243994191fbc910b9d57457c411b91 188594 
discover_2.1.2-7.1+deb9u1.diff.gz
Files:
 9e4c6e1aa0bb32c12b4f3c67c3871280 2038 admin optional 
discover_2.1.2-7.1+deb9u1.dsc
 a087662e36d9dd6d645effbc944f5f89 188594 admin optional 
discover_2.1.2-7.1+deb9u1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqUY8oACgkQiNJCh6LY
mLG85w//XMm7KVGmqfjqZefzXZbWFczQ9P0D/JdvkOFg44Qck33v1uvOQ5tXmIcG
MMGwf/UCHweNq0aaIqpBuQFJjyiydH0OItblvfLR/UL399bykmFIG+EIR7lvVmbO
DS2B2/pgIhpbhcvp8xjmr77KvAhIDQCMHasqkCbmUmeetquAD6ju/Hs/V0PdhToz
KW961s4y65BH0I5qs27DSM8zg72TlmX2Mk+WbOayytdvc7znMhMZwSPCG0krMgTd
BGZdTcY72xquXEGtBR3QQFmRJA8XTUxvhB8sniSsa5d3vMmS04PVxDSXe8IFj3aT
kotBXTmrtXA9TEu0E+av4OG0eEkEsrz7aL7cxRtc3o7q2u4uTVs5PY+/3aoNAFKV
IhvddJ2Nh6D2OO2Adx55bZ6Q8tV6QZT+ZnCF3pcUS0eJ7bGmElaPANm4FtrQmrto
O+7uHnmeAEP33p4YsP4/7gPE+RaEPKNhPCyMMSKPTwBRMG6WcpaWcdIPuSxtdUml
cxrkq6HI1U0rw6KqduGLzOLgHnCu0L7n/hYZnELkATJ3MoRZR8GijJsUcp0OIvTQ
GumBJ3vqaR4ubYcxbMI49dtT8YKuKgQDr+vNtoPMOUSEjCqo9ugLWHyU5HHLCZU+
R3Q3nDeu0n7t/fjflvY84rGvxHy42yUqaKtqsy+Dv8w79WcgXbA=
=K7pY
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of discover_2.1.2-7.1+deb9u1_source.changes

[Debian FTP Masters]

discover_2.1.2-7.1+deb9u1_source.changes uploaded successfully to localhost
along with the files:
  discover_2.1.2-7.1+deb9u1.dsc
  discover_2.1.2-7.1+deb9u1.diff.gz

Greetings,

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

Re: (solved) Re: wireless fail after stretch installation

[Jude DaShiell]

Wifi doesn't come up after a console login once a normal install happens 
until after the network is configured on the post-install system unless 
the /etc/networks/interfaces file created as a result of the install 
process originally gets copied to the hard drive in the correct 
directory with the proper name and contents.  Many ways exist to solve 
this problem and it took a while to find out what to do and how because 
there's more and better support from debian-users than is in debian wiki 
or debian documentation.  I had learned how to do this earlier but 
apparently an individual known as longwind from China ran into this 
problem after I had learned to solve it on this end and the original 
message I read from Brian had a solution I hadn't read earlier and 
hadn't tried yet which involved far fewer steps.  Fortunately I have a 
hard drive available so I will try Brian's solution out on this end and 
see how it works.  Thanks for your assistance and interest.


On Sun, 4 Mar 2018, Philip Hands wrote:


Date: Sun, 4 Mar 2018 13:10:02
From: Philip Hands 
To: Jude DaShiell , Brian ,
debian-u...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: (solved) Re: wireless fail after stretch installation

Jude DaShiell  writes:


The least debian-boot membership could do would be to have a note come
up for installers to execute a shell and do the file copy before
rebooting once hard drive got mounted.  This is a problem for wifi users
with no impact for ethernet users.


Your tone does not encourage a civil response, but you're going to get
one anyway I'm afraid.

Since you didn't bother to say what you are complaining about in any
useful way, I thought I'd look at the first post in the first thread
referred to in the mail from Brian, which is about the fact that
desktop-configured wifi connections don't come up until someone logs in.

Given that one has generally specified the wifi password as the user in
the desktop environment, or at least indicated the fact that you want to
connect to that network, it would be inappropriate for the wifi to come
up earlier, because that might allow other users on the machine to
access a network that was intended to be private.

There is generally an option available in network manager that allows
one to indicate that the connection should be made available to others.
Ticking that box should make it come up at boot time AFAIK.

This seems to have very little to do with the installer.

Cheers, Phil.



--

Re: Failing to install Stretch on QNAP TS-420

[Martin Michlmayr]

I copied debian-boot since this issue may be more appropriate there

* Mark Duggan  [2018-02-24 09:53]:
> I attached the log previously but the reply didn't seem to hit the list
> No 'unhandled fault' in the log
> 
> https://pastebin.com/9Ymxeu9b

It's possible I missed something but I don't see any errors until it fails with:

Feb 18 23:25:17 in-target: Reading package lists...
Feb 18 23:25:18 localechooser: error: the command 'validlocale' is not available
Feb 18 23:25:30 base-installer: info: Found kernels ''
Feb 18 23:26:17 base-installer: error: exiting on error 
base-installer/kernel/no-kernels-found
Feb 18 23:26:19 main-menu[1382]: (process:7509): Aborted

Maybe some debian-boots folks can look over the log with their
trained eyes.

I don't know what the validlocale error is about.

And I don't see why no kernel is found.

debian-boot, any idea?

-- 
Martin Michlmayr
http://www.cyrius.com/

Re: (solved) Re: wireless fail after stretch installation

[Philip Hands]

Jude DaShiell  writes:

> The least debian-boot membership could do would be to have a note come 
> up for installers to execute a shell and do the file copy before 
> rebooting once hard drive got mounted.  This is a problem for wifi users 
> with no impact for ethernet users.

Your tone does not encourage a civil response, but you're going to get
one anyway I'm afraid.

Since you didn't bother to say what you are complaining about in any
useful way, I thought I'd look at the first post in the first thread
referred to in the mail from Brian, which is about the fact that
desktop-configured wifi connections don't come up until someone logs in.

Given that one has generally specified the wifi password as the user in
the desktop environment, or at least indicated the fact that you want to
connect to that network, it would be inappropriate for the wifi to come
up earlier, because that might allow other users on the machine to
access a network that was intended to be private.

There is generally an option available in network manager that allows
one to indicate that the connection should be made available to others.
Ticking that box should make it come up at boot time AFAIK.

This seems to have very little to do with the installer.

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


signature.asc
Description: PGP signature

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

[Kari Tanninen]

To be exact, I have Guruplug Server plus -version, and this device SoC 
is 88F6281.


KariT

Kari Tanninen kirjoitti 4.3.2018 15:11:

Ben wrote:

"This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB"

That is obvious cause of these uInitrd relocation problems.

I don't exactly know how U-boot passes ATAG-values to kernel but in
multiprocessing environment it is very difficult task anyway
(and there is even BareBox forked from U-boot for non-flexible
attitude of U-boot for these kernel/bootloader API issues).

ARM MMU/multiprocessing environment is straightforward, but very
complex. I found GuruPlug PXA168 SoC specifications, but there is
thousands of
pages of information and it is very difficult to guess how
kernel/U-boot uses it. Linux kernel is expecting very complete setup
on boot,
and most difficult part (MMU init) must be done on bootloader.

I think that BareBox approach is not very healthy either, there is
some odd features to use FDT, too. Keeping up two versions of FDT, for
example.

Best way to do it with Linux -kernel is to use one FDT-blob generated
by kconfig at kernel compile and load it by bootloader. At Kernel API
point of view
that should be same situation as PC and command line parameters and
other boot-time variables is supplied by bootloader by modifying
FDT-blob
(for example "choosen") nodes.

KariT

Ben Hutchings kirjoitti 3.3.2018 16:13:

On Fri, 2018-03-02 at 14:48 +0200, Kari Tanninen wrote:

"In Debian installer, for the various plug devices, we append to
the DTB at the end of the kernel rather than loading it separately."


Is that possible/reasonable?

U-boot have to link all files on boot and it is impossibe to append
command line parametres to fdt-blob
without resize fdt-blob at U-boot. U-boot is using physical 
addressing

only(?) and I think kernel cannot
resize itself before boot without relocation problems -> bootm_size
variable issue.

If fdt is used, kernel should discard ATAG-variables by default, I
think.

[...]

This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB.

Ben.

Re: (solved) Re: wireless fail after stretch installation

[Jude DaShiell]

The least debian-boot membership could do would be to have a note come 
up for installers to execute a shell and do the file copy before 
rebooting once hard drive got mounted.  This is a problem for wifi users 
with no impact for ethernet users.


On Sun, 4 Mar 2018, Brian wrote:


Date: Sun, 4 Mar 2018 05:35:28
From: Brian 
To: debian-u...@lists.debian.org
Subject: Re: (solved) Re: wireless fail after stretch installation
Resent-Date: Sun,  4 Mar 2018 10:35:45 + (UTC)
Resent-From: debian-u...@lists.debian.org

On Sun 04 Mar 2018 at 08:41:00 +, Long Wind wrote:


Thank Brian! Your instructions are right, wireless works now!
the 1st time i use network installthis time i use cdrom install, it has same
problemas this problem is easily reproduced, why don't they fix it??
i attach wrong and right interfaces:t1 and t2 respectively(key removed)


The installer team do not consider there is anything to fix. This is the
way they want it. Some users think it is a bug and have said so in the
BTS (see the netcfg package).

We discused this recently on -user. The thread starts at

 https://lists.debian.org/debian-user/2018/01/msg00800.html

and continues at

 https://lists.debian.org/debian-user/2018/02/msg0.html




--

Re: Armel: Debian installer freeezes (GuruPlug Server plus)

[Kari Tanninen]

Ben wrote:

"This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB"

That is obvious cause of these uInitrd relocation problems.

I don't exactly know how U-boot passes ATAG-values to kernel but in 
multiprocessing environment it is very difficult task anyway
(and there is even BareBox forked from U-boot for non-flexible attitude 
of U-boot for these kernel/bootloader API issues).


ARM MMU/multiprocessing environment is straightforward, but very 
complex. I found GuruPlug PXA168 SoC specifications, but there is 
thousands of
pages of information and it is very difficult to guess how kernel/U-boot 
uses it. Linux kernel is expecting very complete setup on boot,

and most difficult part (MMU init) must be done on bootloader.

I think that BareBox approach is not very healthy either, there is some 
odd features to use FDT, too. Keeping up two versions of FDT, for 
example.


Best way to do it with Linux -kernel is to use one FDT-blob generated by 
kconfig at kernel compile and load it by bootloader. At Kernel API point 
of view
that should be same situation as PC and command line parameters and 
other boot-time variables is supplied by bootloader by modifying 
FDT-blob

(for example "choosen") nodes.

KariT

Ben Hutchings kirjoitti 3.3.2018 16:13:

On Fri, 2018-03-02 at 14:48 +0200, Kari Tanninen wrote:

"In Debian installer, for the various plug devices, we append to
the DTB at the end of the kernel rather than loading it separately."


Is that possible/reasonable?

U-boot have to link all files on boot and it is impossibe to append
command line parametres to fdt-blob
without resize fdt-blob at U-boot. U-boot is using physical addressing
only(?) and I think kernel cannot
resize itself before boot without relocation problems -> bootm_size
variable issue.

If fdt is used, kernel should discard ATAG-variables by default, I
think.

[...]

This behaviour is configurable.  For armel and armhf we enable
CONFIG_ARM_ATAG_DTB_COMPAT and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER so that ATAG
variables override the DTB.

Ben.