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
-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
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
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
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
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
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:
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)
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
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
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.
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
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
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
14 matches
Mail list logo