Displaying 20 results from an estimated 258 matches for "0x0100".
Did you mean:
0x0000
2015 May 11
3
ldap host attribute is ignored
On 05/11/2015 10:06 AM, Ulrich Hiller wrote:
> Hmmm...., i have made now a complete new install but the problem
> persists: ldap authentication works, but the host attribute is ignored.
Hate to say that we're running out of options. I had a CentOS 7 system
similar to yours, with LDAP authentication. I added three lines to
sssd.conf (for access provider, etc), restarted sssd, and
2015 May 12
0
ldap host attribute is ignored
...then a user
without the host attribute. The output in the logfiles are the same.
Note: USER ist not a local user. Without correct ldap password the user
cannot login.
User with correct host attribute
--------------------------------
(Tue May 12 13:16:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): command: PAM_SETCRED
(Tue May 12 13:16:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): domain: default
(Tue May 12 13:16:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): user: USER
(Tue May 12 13:16:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): service: sshd
(Tue May 12 1...
2015 May 12
3
ldap host attribute is ignored
...e May 12 10:35:35 2015) [sssd[be[default]]]
[sdap_get_generic_ext_step] (0x1000): Requesting attrs: [host]
-----
So, the user lookup definitely requested the host attribute.
The authentication process logs to the same file:
-----
(Tue May 12 10:35:36 2015) [sssd[be[default]]] [be_pam_handler]
(0x0100): Got request with the following data
(Tue May 12 10:35:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): command: PAM_ACCT_MGMT
(Tue May 12 10:35:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100): domain: default
(Tue May 12 10:35:36 2015) [sssd[be[default]]] [pam_print_data]
(0x0100...
2015 May 09
5
sssd on a DC
...e UIDs and GIDs, at which point rsync in this way should
work just fine.. However, I don't know enough about keytabs and
suchlike.
I have sssd configured at a basic level, but am getting a strange error.
>From the log files of sssd, things look fine up to this point:
[resolv_getsrv_send] (0x0100): Trying to resolve SRV record of
'_ldap._tcp.domain.tld'
but then the rest only looks like it works 50% of the time, i.e. when
the above line resolves to the *other* DC.
I have been testing sssd on DC1 first of all. When the above DNS query
resolves to DC1, I get:
[be_resolve_server_pro...
2015 May 12
0
ldap host attribute is ignored
...[sdap_get_generic_ext_step] (0x1000): Requesting attrs: [host]
> -----
>
> So, the user lookup definitely requested the host attribute.
>
> The authentication process logs to the same file:
>
> -----
> (Tue May 12 10:35:36 2015) [sssd[be[default]]] [be_pam_handler]
> (0x0100): Got request with the following data
> (Tue May 12 10:35:36 2015) [sssd[be[default]]] [pam_print_data]
> (0x0100): command: PAM_ACCT_MGMT
> (Tue May 12 10:35:36 2015) [sssd[be[default]]] [pam_print_data]
> (0x0100): domain: default
> (Tue May 12 10:35:36 2015) [sssd[be[default]]] [p...
2015 May 10
2
sssd on a DC
...work just fine.. However, I don't know enough about keytabs and
>> suchlike.
>>
>> I have sssd configured at a basic level, but am getting a strange error.
>>
>> From the log files of sssd, things look fine up to this point:
>>
>> [resolv_getsrv_send] (0x0100): Trying to resolve SRV record of
>> '_ldap._tcp.domain.tld'
>>
>> but then the rest only looks like it works 50% of the time, i.e. when
>> the above line resolves to the *other* DC.
>>
>> I have been testing sssd on DC1 first of all. When the above DNS q...
2014 Aug 01
1
howto test ddns
...12:18:30 2014) [sssd[be[tissisat.co.uk]]]
[be_nsupdate_timer_schedule] (0x0200): Timer already scheduled
(Fri Aug 1 12:18:30 2014) [sssd[be[tissisat.co.uk]]]
[ad_dyndns_update_send] (0x0400): Performing update
(Fri Aug 1 12:18:30 2014) [sssd[be[tissisat.co.uk]]]
[resolv_gethostbyname_dns_query] (0x0100): Trying to resolve A record of
'ashanti' in DNS
(Fri Aug 1 12:18:30 2014) [sssd[be[tissisat.co.uk]]]
[resolv_gethostbyname_dns_parse] (0x1000): Parsing an A reply
(Fri Aug 1 12:18:30 2014) [sssd[be[tissisat.co.uk]]]
[request_watch_destructor] (0x0400): Deleting request watch
(Fri Aug 1...
2005 Aug 03
0
Chan_bluetooth and AudioGateway phone [long]
...:CF ...
Service Name: Hands-Free voice gateway
Service Description: Hands-Free voice gateway
Service Provider: Motorola
Service RecHandle: 0x10007
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
Language Base Attr List:
...
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
Maybe the channel 7? I have also the following channels available
/etc/asterisk# sdptool browse 00:0a:28:83:a9:cf
Browsing 00:0A:28:83:A9:CF ....
2015 May 09
0
sssd on a DC
...ync in this way should
> work just fine.. However, I don't know enough about keytabs and
> suchlike.
>
> I have sssd configured at a basic level, but am getting a strange error.
>
> From the log files of sssd, things look fine up to this point:
>
> [resolv_getsrv_send] (0x0100): Trying to resolve SRV record of
> '_ldap._tcp.domain.tld'
>
> but then the rest only looks like it works 50% of the time, i.e. when
> the above line resolves to the *other* DC.
>
> I have been testing sssd on DC1 first of all. When the above DNS query
> resolves to DC...
2018 Jul 20
2
SSSD on CentOS 7 failing to start when connecting to 4.8.3 AD via LDAP
...e Samba server, but the CentOS 7 server just
gets an ACK. When I up the debug level on SSSD on the CentOS 7 server, I
see a few different errors but I'm not sure which of these show cause or
effect. Examples...
(Thu Jul 19 23:40:34 2018) [sssd[be[AD.COMPANY.COM]]]
[common_parse_search_base] (0x0100): Search base added:
[SUDO][dc=ad,dc=company,dc=com][SUBTREE][]
(Thu Jul 19 23:40:34 2018) [sssd[be[AD.COMPANY.COM]]]
[common_parse_search_base] (0x0100): Search base added:
[AUTOFS][dc=ad,dc=company,dc=com][SUBTREE][]
(Thu Jul 19 23:40:34 2018) [sssd[be[AD.COMPANY.COM]]] [dp_client_register]
(0x01...
2013 Dec 25
1
[PATCH] drm/nve4: fix size of POLY2ESETUP buffer (s/gpc_nr/tpc_total)
...u/core/engine/graph/ctxnve4.c
index e2de73e..fc1cc32 100644
--- a/drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c
+++ b/drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c
@@ -813,7 +813,7 @@ nve4_grctx_generate_mods(struct nvc0_graph_priv *priv, struct nvc0_grctx *info)
mmio_data(0x003000, 0x0100, NV_MEM_ACCESS_RW | NV_MEM_ACCESS_SYS);
mmio_data(0x008000, 0x0100, NV_MEM_ACCESS_RW | NV_MEM_ACCESS_SYS);
- mmio_data(0x060000, 0x1000, NV_MEM_ACCESS_RW);
+ mmio_data(priv->tpc_total << 17, 0x1000, NV_MEM_ACCESS_RW);
mmio_list(0x40800c, 0x00000000, 8, 1);
mmio_list(0x408010, 0x8000...
2015 Nov 03
3
[PATCH 1/2] disp: activate dual link TMDS links only when possible
...8,7 +158,7 @@ exec_clkcmp(struct nv50_disp *disp, int head, int id, u32 pclk, u32 *conf)
switch (outp->info.type) {
case DCB_OUTPUT_TMDS:
*conf = (ctrl & 0x00000f00) >> 8;
- if (pclk >= 165000)
+ if (pclk >= 165000 && outp->info.duallink_possible)
*conf |= 0x0100;
break;
case DCB_OUTPUT_LVDS:
diff --git a/drm/nouveau/nvkm/engine/disp/nv50.c b/drm/nouveau/nvkm/engine/disp/nv50.c
index 32e73a9..ceecd0e 100644
--- a/drm/nouveau/nvkm/engine/disp/nv50.c
+++ b/drm/nouveau/nvkm/engine/disp/nv50.c
@@ -391,7 +391,7 @@ exec_clkcmp(struct nv50_disp *disp, int hea...
2004 Nov 11
2
PXELINUX - no boot file found
...00 0000 0000 0000 0000 ................
0x00c0 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00d0 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00e0 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x00f0 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0100 0000 0000 0000 0000 6382 5363 3501 0137 ........c.Sc5..7
0x0110 1801 0303 0506 0b0c 0d0f 1011 122b 363c .............+6<
0x0120 4380 8182 8384 8586 8739 0204 ec61 1100 C........9...a..
0x0130 997e 931d 3d06 d511 a800 accd f1ea 391d .~..=.........9.
0x0140 5d02 0000 5e03 0102 013c 2050 5845...
2015 May 10
0
sssd on a DC
OK, I've got a little further and I think I have tracked this down to
a reverse DNS issue - which was non-obvious to me, so here is a
write-up for the benefit of the archives.
The part that was failing was this:
[sasl_bind_send] (0x0100): Executing sasl bind mech: gssapi, user: dc1$
[sasl_bind_send] (0x0020): ldap_sasl_bind failed (-2)[Local error]
[sasl_bind_send] (0x0080): Extended failure message: [SASL(-1):
generic failure: GSSAPI Error: Unspecified GSS failure. Minor code
may provide more information (Server not found in Ker...
2014 Sep 11
3
[Qemu-devel] [PATCH 1/2] virtio-gpu/2d: add hardware spec include file
....h
> @@ -0,0 +1,158 @@
> +#ifndef VIRTGPU_HW_H
> +#define VIRTGPU_HW_H
Non-trivial file, deserves a copyright and license notice.
> +
> +enum virtgpu_ctrl_type {
> + VIRTGPU_UNDEFINED = 0,
> +
> + /* 2d commands */
> + VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100,
Please consider also adding:
#define VIRTGPU_CMD_GET_DISPLAY_INFO VIRTGPU_CMD_GET_DISPLAY_INFO
and friends. It makes it MUCH nicer for application software to probe
for later extensions if every member of the enum is also associated with
a preprocessor macro.
> +
> +struct virtgpu_ctrl...
2014 Sep 11
3
[Qemu-devel] [PATCH 1/2] virtio-gpu/2d: add hardware spec include file
....h
> @@ -0,0 +1,158 @@
> +#ifndef VIRTGPU_HW_H
> +#define VIRTGPU_HW_H
Non-trivial file, deserves a copyright and license notice.
> +
> +enum virtgpu_ctrl_type {
> + VIRTGPU_UNDEFINED = 0,
> +
> + /* 2d commands */
> + VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100,
Please consider also adding:
#define VIRTGPU_CMD_GET_DISPLAY_INFO VIRTGPU_CMD_GET_DISPLAY_INFO
and friends. It makes it MUCH nicer for application software to probe
for later extensions if every member of the enum is also associated with
a preprocessor macro.
> +
> +struct virtgpu_ctrl...
2014 Sep 14
4
[PATCH 1/2] virtio-gpu/2d: add hardware spec include file
...d so anyone can use the definitions to
implement compatible drivers/servers.
> > > +
> > > +enum virtgpu_ctrl_type {
> > > + VIRTGPU_UNDEFINED = 0,
> > > +
> > > + /* 2d commands */
> > > + VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100,
> >
> > Please consider also adding:
VIRTIO_GPU_ everywhere to make it consistent with other
virtio headers?
> >
> > #define VIRTGPU_CMD_GET_DISPLAY_INFO VIRTGPU_CMD_GET_DISPLAY_INFO
> >
> > and friends. It makes it MUCH nicer for application software to...
2014 Sep 14
4
[PATCH 1/2] virtio-gpu/2d: add hardware spec include file
...d so anyone can use the definitions to
implement compatible drivers/servers.
> > > +
> > > +enum virtgpu_ctrl_type {
> > > + VIRTGPU_UNDEFINED = 0,
> > > +
> > > + /* 2d commands */
> > > + VIRTGPU_CMD_GET_DISPLAY_INFO = 0x0100,
> >
> > Please consider also adding:
VIRTIO_GPU_ everywhere to make it consistent with other
virtio headers?
> >
> > #define VIRTGPU_CMD_GET_DISPLAY_INFO VIRTGPU_CMD_GET_DISPLAY_INFO
> >
> > and friends. It makes it MUCH nicer for application software to...
2015 Nov 04
1
[PATCH 1/2] disp: activate dual link TMDS links only when possible
...utp->info.type) {
>> case DCB_OUTPUT_TMDS:
>> *conf = (ctrl & 0x00000f00) >> 8;
>> - if (pclk >= 165000)
>> + if (pclk >= 165000 && outp->info.duallink_possible)
>> *conf |= 0x0100;
> I think it might be more robust to key this off the SOR protocol, rather
> than duplicating the condition above.
You mean disp->sor.lvdsconf? What do I do with that? Or did you have
something else in mind?
>
>> break;
>> case DCB_OUTPUT_LVDS:
>>...
2011 Apr 27
3
[LLVMdev] Can I get the binary address of a for-loop statement?
Hi, all
What I want to do is to locate the range of a for-loop statement in
a binary. For example, given a for-loop statement belows,
for (stat1; stat2; stat3) {
/* do something */
}
Is it possible to get information about the range (binary address)
of the above for-loop, say, 0x0100 - 0x0120.
One idea comes up in my mind is adding passes to retrieve such
information in LLVM, then use llvm-gcc to compile the code.
Any suggestion appreciated.
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Te...