Jeffrey Mark Siskind wrote:
>I had big issues with mptsas and 3.16 in jessie, so I am still using
>3.2.0-4-rt-amd64
>
> Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do
> I install it on a fresh jessie install that wasn't dist-upgraded from
> wheezy?
>
> Jef
I had big issues with mptsas and 3.16 in jessie, so I am still using
3.2.0-4-rt-amd64
Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do I
install it on a fresh jessie install that wasn't dist-upgraded from wheezy?
Jeff (http://engineering.purdue.edu/~qobi)
Vagrant Cascadian (2016-06-27):
> On 2016-06-27, Cyril Brulebois wrote:
> > for some reasons I failed at double checking when u-boot is used; it's
> > needed at build time for debian-installer, so we'd need the u-boot fix
> > before uploading src:debian-installer.
> >
> > Do you have any time fram
Ben Hutchings wrote:
> I think most of the problems you're still having must be caused by a
> bug in the RAID driver, mpt2sas (or its firmware, if that's not
> embedded in the BIOS).
I had big issues with mptsas and 3.16 in jessie, so I am still using
3.2.0-4-rt-amd64
rootdelay=15 did not help i
The non-determinism in which identifiers are shown might be a bug in the
installer, or it might be caused by failure of ID commands to the
drives.
I think most of the problems you're still having must be caused by a
bug in the RAID driver, mpt2sas (or its firmware, if that's not
On 2016-06-27, Cyril Brulebois wrote:
> Cyril Brulebois (2016-06-27):
>> FWIW I'm going to upload debian-installer very shortly; it'd be nice if
>> u-boot could be uploaded while src:debian-installer is getting built,
>> urgented, and dak copy-installer'd into testing; so that it has a chance
>> t
On Mon, Jun 27, 2016 at 02:05:53PM +0200, Ben Hutchings wrote:
> I've never heard of that situation before.
I think you have: PEBKAC :)
the server is located in a loud+dusty+dark room, has 4 ethernet devices
and it seems I mixed them up…
> Which hardware is this?
> Where is the need for firmwa
On Mon, 2016-06-27 at 08:07 -0400, Jeffrey Mark Siskind wrote:
[...]
> Whenever I observe any of the behavior reported in this email, it is
> almost always associated with dmesg reporting the same error on the same
> sector 2056 (sometimes 2058 or 2062). Given the dozens of attempted
>
I'd like to thank everyone for helping out.
Here is an update on installing jessie on R815s.
I succeeded in installing on three of my four R815s. But I am holding off on
the last because it is my file server and there are still issues. Please read
on. I don't believe that the problem is solved an
On Mon, 2016-06-27 at 11:54 +, Holger Levsen wrote:
> Hi,
>
> I've installed Debian jessie in a setup yesterday, where I needed to use
> vlan, so I was very happy when I saw that this bug has a patch.
>
> However, the network card I used works nicely for configurations without
> vlans without
Hi,
I've installed Debian jessie in a setup yesterday, where I needed to use
vlan, so I was very happy when I saw that this bug has a patch.
However, the network card I used works nicely for configurations without
vlans without loading additional firmware, while it needs a non free
firmware to su
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 26 Jun 2016 16:54:23 +0200
Source: preseed
Binary: preseed-common network-preseed file-preseed initrd-preseed env-preseed
Architecture: source all
Version: 1.72
Distribution: unstable
Urgency: medium
Maintainer: De
preseed_1.72_amd64.changes uploaded successfully to localhost
along with the files:
preseed_1.72.dsc
preseed_1.72.tar.xz
env-preseed_1.72_all.udeb
file-preseed_1.72_all.udeb
initrd-preseed_1.72_all.udeb
network-preseed_1.72_all.udeb
preseed-common_1.72_all.udeb
Greetings,
Yo
13 matches
Mail list logo
