Re: [gentoo-user] DRM error: couldn't read SADs

[80x24]

On Sun, Feb 11, 2018 at 12:47 AM, Peter Humphrey  wrote:
>
> [drm:dce_v11_0_afmt_setmode] *ERROR* Couldn't read SADs: 0
> [...]
> traps: plugin-containe[6833] general protection ip:7f0a2e1711b1 
> sp:7fff6f64dc30 error:0 in ld-2.25.so[7f0a2e15c000+23000]
>
> What is a SAD (other than a seasonal affective disorder)? That library comes
> from glibc, of which I've had 5 versions or revisions in that time

Never heard of it neither. Digging into the kernel source gives

static void radeon_audio_write_sad_regs(struct drm_encoder *encoder)
{
   struct drm_connector *connector = radeon_get_connector_for_encoder$
   struct radeon_encoder *radeon_encoder = to_radeon_encoder(encoder);
   struct cea_sad *sads;
   int sad_count;

   if (!connector)
   return;

   sad_count = drm_edid_to_sad(radeon_connector_edid(connector), $
   if (sad_count <= 0) {
   DRM_ERROR("Couldn't read SADs: %d\n", sad_count);
   return;
   }
   BUG_ON(!sads);

   if (radeon_encoder->audio && radeon_encoder->audio->write_sad_regs)
   radeon_encoder->audio->write_sad_regs(encoder, sads, sad_c$

kfree(sads);
}


in theses files

drivers/gpu/drm/radeon/radeon_audio.c
drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
drivers/gpu/drm/amd/amdgpu/dce_v10_0.c
drivers/gpu/drm/amd/amdgpu/dce_v11_0.c
drivers/gpu/drm/amd/amdgpu/dce_v8_0.c

which ``drm_edid_to_sad‘’ is defined in drivers/gpu/drm/drm_edid.c.
Comments read

/**
 * drm_edid_to_sad - extracts SADs from EDID
 * @edid: EDID to parse
 * @sads: pointer that will be set to the extracted SADs
 *
 * Looks for CEA EDID block and extracts SADs (Short Audio Descriptors) fr$
 *
 * Note: The returned pointer needs to be freed using kfree().
 *
 * Return: The number of found SADs or negative number on error.
 */

Considering the term ``EDID'' and some audio related words, I think
it's reading some info from your monitor.

-- 
Silence is golden.

Re: [gentoo-user] kernel choices for booting gentoo as guest in vbox vm

[80x24]

On Wed, Jan 31, 2018 at 8:44 PM, Harry Putnam  wrote:
> Installing gentoo as guest into vbox vm on solaris-11 (openindiana)
> HOST
> gentoo-17
> VBox 5.2.6
> Kernel 4.15.0
>
> My first boot resulted in resulted in a kernel panic... not able to
> mount root.
>

Maybe taking a video record or screenshot and providing a extact log
message would help.

> In a chroot now I can see lspci -k shows ata_piix in use .. but that
> would probably be because in vbox I have the gentoo install media on
> IDE secondary master.  But also shows sata controller ahci

In case device driver is fine, you would want to check the filesystem
type. I've done something like using btrfs as rootfs but didn't mark
btrfs as builtin module.

Similar kernel panic.


-- 
Silence is golden.

Re: [gentoo-user] The Project Begins!

[80x24]

Hunter Jozwiak wrote:

Hello,

I am going to now host my web site on a Gentoo server. Firstly, is there
a recommended profile for this, or will the default amd64 profile
suffice? Or would it be better to use a hardened profile for this task?
Secondly, does Linode offer the requisite information for things you
MUST have while building a kernel? And finally, I am going to have
multiple servers. Is there a package that I can use to distribute my
built kernels?

Thanks, you guys are awesome, and keep up the good work,

Hunter

As far as you know how to hardened security of your servers. Normal 
profile will be good (Though I still recommend hardened if you're 
familiar with GRsecurity and other ``hardeded'' stuff).


If you go with the hardened version, you will also need to build custom 
kernel and set kernel to pygrub in Linode profile settings (which 
selects proper generic kernel by default). And yes you will need a 
bootloader.


You can find out the kernel config options requirements at Linode website[1]

I don't know any method to build a binary kernel package. Maybe others 
can help. I use to distribute it just by copying vmlinuz and initramfs 
(I built them without any CPU-specific optimization or ``host-only'' mode).


[1]: 
https://www.linode.com/docs/tools-reference/custom-kernels-distros/run-a-custom-compiled-kernel-with-pvgrub