[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fw: Backported kernel is workable with FGLRX



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Begin forwarded message:

Date: Thu, 22 Dec 2016 09:09:56 +0100
From: Andreas Glaeser <andreas.glaeser@irregulaire.info>
To: bugs.andreas.glaeser@freenet.de
Subject: Fwd: Fwd: Re: Backported kernel is workable with FGLRX


- -------- Forwarded Message --------
Subject: Fwd: Re: Backported kernel is workable with FGLRX
Date: Wed, 21 Dec 2016 12:01:25 +0100
From: Andreas Glaeser <andreas.glaeser@irregulaire.info>
To: backports@lists.debian.org


Correction: I succeeded to backport a proprietary AMD-kernel, that works
with GnuPG, ie. in non-unsigned flavour, and that is doing nothing about
the zfs-problem:

andrew@a68n:~$ uname -a
Linux a68n 4.8.11-adt-bpo #1 SMP Tue Dec 20 09:19:40 CET 2016 x86_64
GNU/Linux

> andrew@a68n:~$ sudo aptitude reinstall zfs-dkms
> The following packages will be REINSTALLED:
>   zfs-dkms 
> 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 11 not upgraded.
> Need to get 0 B/1,077 kB of archives. After unpacking 0 B will be used.
> Preconfiguring packages ...              
> (Reading database ... 466906 files and directories currently installed.)
> Preparing to unpack .../zfs-dkms_0.6.5.8-1~bpo8+1_all.deb ...
> 
> -------- Uninstall Beginning --------
> Module:  zfs
> Version: 0.6.5.8
> Kernel:  3.16.36-adt (x86_64)
> -------------------------------------
> 
> Status: Before uninstall, this module version was ACTIVE on this kernel.
> 
> zavl.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> 
> zcommon.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> 
> znvpair.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> 
> zpios.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> 
> zunicode.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> 
> zfs.ko:
>  - Uninstallation
>    - Deleting from: /lib/modules/3.16.36-adt/updates/dkms/
>  - Original module
>    - No original module was found for this module on this kernel.
>    - Use the dkms install command to reinstall any previous module version.
> 
> depmod........
> 
> DKMS: uninstall completed.
> 
> ------------------------------
> Deleting module version: 0.6.5.8
> completely from the DKMS tree.
> ------------------------------
> Done.
> Unpacking zfs-dkms (0.6.5.8-1~bpo8+1) over (0.6.5.8-1~bpo8+1) ...
> Setting up zfs-dkms (0.6.5.8-1~bpo8+1) ...
> Loading new zfs-0.6.5.8 DKMS files...
> Building for 4.8.11-adt-bpo
> Building initial module for 4.8.11-adt-bpo
> Error! Bad return status for module build on kernel: 4.8.11-adt-bpo (x86_64)
> Consult /var/lib/dkms/zfs/0.6.5.8/build/make.log for more information.
>                                          
> andrew@a68n:~$   


It's OK for me, but something should be done about this anyway, ZFS used
to work well for me, I had my /home/-partitions on ZFS, so it is fine
for desktops and flash-memory, too
And XEPW, (uniX-Embedded-Web-Proxy) is also doing fine on ZFS, which is
the complexity-reduced FreeBSD-port of DEWP, employing ezjail.




See attachments




- -------- Forwarded Message --------
Subject: Re: Backported kernel is workable with FGLRX
Date: Tue, 20 Dec 2016 16:12:28 +0100
From: Alexander Wirt <formorer@formorer.de>
To: Andreas Glaeser <andreas.glaeser@irregulaire.info>
CC: backports-team@debian.org, security@debian.org

On Tue, 20 Dec 2016, Andreas Glaeser wrote:

> ,but not with ZFS, and GnuPG guys!
> 
> I have a workable new-stable kernel-version now, see attachment:  
This are not the right lists for your kernel problems. Use
backports@lists.debian.org as also written in the backports docs.
Alex


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlhbjEAACgkQ5+rBHyUt5wuzVQCeKPz+skukGlEOHU2CJYl3pOnM
awwAn0HpXW5FIrYkMMZRyCYaOQQJ6Xt5
=3TIn
-----END PGP SIGNATURE-----

Attachment: bin5vNtGOfkSL.bin
Description: application/pgp-encrypted

Attachment: encrypted.asc
Description: Binary data

Attachment: config-4.8.11-adt-bpo.xz
Description: application/xz

Attachment: make.log.xz
Description: application/xz

Attachment: dmsg.txt.xz
Description: application/xz


Reply to: