search for: dmm

...ealm'), > flags=(nbt.NBT_SERVER_LDAP | > samba.NTSTATUSError: (3221225524, 'The object name is not found.') I was able to get it to work by setting up a simple smb.conf, and doing a `net ads join`. SSSD is still the auth provider. My simple smb.conf looks like this: dmulder at dmm-tw:~> cat /etc/samba/smb.conf [global] ?? ?idmap config * : backend = tdb ?? ?idmap config * : range = 10000-20000 ?? ?idmap config dmm : backend = rid ?? ?idmap config dmm : range = 20001-99999 ?? ?kerberos method = secrets and keytab ?? ?security = ADS ?? ?usershare allow guests = No ?...

On 18/04/2023 18:15, David Mulder via samba wrote: > I was able to get it to work by setting up a simple smb.conf, and doing > a `net ads join`. SSSD is still the auth provider. > > My simple smb.conf looks like this: > > dmulder at dmm-tw:~> cat /etc/samba/smb.conf > [global] > ?? ?idmap config * : backend = tdb > ?? ?idmap config * : range = 10000-20000 > ?? ?idmap config dmm : backend = rid > ?? ?idmap config dmm : range = 20001-99999 > ?? ?kerberos method = secrets and keytab > ?? ?security = ADS...

hi, im trying to log on to my win2003 ADS from Samba3-0.2a, buet every time to run i got the same message dmm:/home/dmagana # net ads join -U dmagana dmagana password: [2004/04/06 09:09:48, 0] libads/kerberos.c:ads_kinit_password(134) kerberos_kinit_password dmagana@GENESIS.LOCAL failed: Cannot contact any KDC for requested realm dmm:/home/dmagana # my domain is genesis.local, but i don't know what...

Hello Samba Team, how are you? I'm joining linux clients in the company's environment and I would like to apply GPOs to linux clients, I'm in the testing phase. I'm testing with ubuntu clients version 22.04 and the software I used to join the samba AD was sssd. The 22.04 ubuntu client has joined and everything is working fine except for the GPOs for linux clients. I compiled

Hey guys, I've been struggling with hangup detection on a Centrex system for a bit now, I was on site Saturday and I took my DMM with me. It would appear that this Centrex service provider uses polarity reversal at the beginning of a call and several times after hangup. I've been reading the archives for the last year and it looks like there was some work done that matches my situation. With the DMM, my readings a...

...l/qxl_kms.c index 2b1e1f3..a9a741c 100644 --- a/drivers/gpu/drm/qxl/qxl_kms.c +++ b/drivers/gpu/drm/qxl/qxl_kms.c @@ -31,19 +31,9 @@ int qxl_log_level; -static void qxl_dump_mode(struct qxl_device *qdev, void *p) -{ - struct qxl_mode *m = p; - DRM_DEBUG_KMS("%d: %dx%d %d bits, stride %d, %dmm x %dmm, orientation %d\n", - m->id, m->x_res, m->y_res, m->bits, m->stride, m->x_mili, - m->y_mili, m->orientation); -} - static bool qxl_check_device(struct qxl_device *qdev) { struct qxl_rom *rom = qdev->rom; - int mode_offset; - int i; if (ro...

...l/qxl_kms.c index 2b1e1f3..a9a741c 100644 --- a/drivers/gpu/drm/qxl/qxl_kms.c +++ b/drivers/gpu/drm/qxl/qxl_kms.c @@ -31,19 +31,9 @@ int qxl_log_level; -static void qxl_dump_mode(struct qxl_device *qdev, void *p) -{ - struct qxl_mode *m = p; - DRM_DEBUG_KMS("%d: %dx%d %d bits, stride %d, %dmm x %dmm, orientation %d\n", - m->id, m->x_res, m->y_res, m->bits, m->stride, m->x_mili, - m->y_mili, m->orientation); -} - static bool qxl_check_device(struct qxl_device *qdev) { struct qxl_rom *rom = qdev->rom; - int mode_offset; - int i; if (ro...

...l/qxl_kms.c index 2b1e1f3..a9a741c 100644 --- a/drivers/gpu/drm/qxl/qxl_kms.c +++ b/drivers/gpu/drm/qxl/qxl_kms.c @@ -31,19 +31,9 @@ int qxl_log_level; -static void qxl_dump_mode(struct qxl_device *qdev, void *p) -{ - struct qxl_mode *m = p; - DRM_DEBUG_KMS("%d: %dx%d %d bits, stride %d, %dmm x %dmm, orientation %d\n", - m->id, m->x_res, m->y_res, m->bits, m->stride, m->x_mili, - m->y_mili, m->orientation); -} - static bool qxl_check_device(struct qxl_device *qdev) { struct qxl_rom *rom = qdev->rom; - int mode_offset; - int i; if (ro...

...l/qxl_kms.c index 2b1e1f3..a9a741c 100644 --- a/drivers/gpu/drm/qxl/qxl_kms.c +++ b/drivers/gpu/drm/qxl/qxl_kms.c @@ -31,19 +31,9 @@ int qxl_log_level; -static void qxl_dump_mode(struct qxl_device *qdev, void *p) -{ - struct qxl_mode *m = p; - DRM_DEBUG_KMS("%d: %dx%d %d bits, stride %d, %dmm x %dmm, orientation %d\n", - m->id, m->x_res, m->y_res, m->bits, m->stride, m->x_mili, - m->y_mili, m->orientation); -} - static bool qxl_check_device(struct qxl_device *qdev) { struct qxl_rom *rom = qdev->rom; - int mode_offset; - int i; if (ro...

...s really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at drm drivers and the basic vesa/efi fbdev drivers shows that only 3 drivers support any kind of acceleration: - nouveau, seems to be enabled by default - omapdrm, when a DMM remapper exists using remapper rewriting for y/xpanning - gma500, but that is getting deleted now for the GTT remapper trick, and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA flag, so unused (and could be deleted already I think). No other driver supportes accelerated fbcon...

...s really only treat fbcon as an dumb kernel console until userspace takes over, and Oops printer for some emergencies. Looking at drm drivers and the basic vesa/efi fbdev drivers shows that only 3 drivers support any kind of acceleration: - nouveau, seems to be enabled by default - omapdrm, when a DMM remapper exists using remapper rewriting for y/xpanning - gma500, but that is getting deleted now for the GTT remapper trick, and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA flag, so unused (and could be deleted already I think). No other driver supportes accelerated fbcon...

...n dumb kernel console until userspace takes over, and Oops > printer for some emergencies. Looking at drm drivers and the basic > vesa/efi fbdev drivers shows that only 3 drivers support any kind of > acceleration: > > - nouveau, seems to be enabled by default > - omapdrm, when a DMM remapper exists using remapper rewriting for > y/xpanning > - gma500, but that is getting deleted now for the GTT remapper trick, > and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA > flag, so unused (and could be deleted already I think). > > No other driv...

...serspace takes over, and Oops > > printer for some emergencies. Looking at drm drivers and the basic > > vesa/efi fbdev drivers shows that only 3 drivers support any kind of > > acceleration: > > > > - nouveau, seems to be enabled by default > > - omapdrm, when a DMM remapper exists using remapper rewriting for > > y/xpanning > > - gma500, but that is getting deleted now for the GTT remapper trick, > > and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA > > flag, so unused (and could be deleted already I think). >...

...that is on battery OB and after it shutdown because of low battery LO. > I wondered how old is your battery ? > Roger > I have change it 2019.03.08. 12V/10Ah YUASA. > I was checked not only battery voltage (13.6V without load), but charging > voltage and output voltage using true rms dmm. > It is working well with Debian 6 > > tovis After long struggling, check every parts of UPS and cable, I have realized that is after boot I reload the driver the system work well: # systemctl restart nut-driver.service I was checked up to real "battery low" and shutdown, switc...

...n dumb kernel console until userspace takes over, and Oops > printer for some emergencies. Looking at drm drivers and the basic > vesa/efi fbdev drivers shows that only 3 drivers support any kind of > acceleration: > > - nouveau, seems to be enabled by default > - omapdrm, when a DMM remapper exists using remapper rewriting for > y/xpanning > - gma500, but that is getting deleted now for the GTT remapper trick, > and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA > flag, so unused (and could be deleted already I think). > > No other driv...

Hello all, I''m having the same problem here, any news? I need to use ACL''s on the GNU/Linux clients. I''m using nfsv3, and on the GNU/Linux servers that feature was working, i think we need a solution for solaris/opensolaris. Now, with the "dmm" project, how we can start a migration process, if we can not provide the same services on the target machine? Thanks a lot for your time! Leal. This message posted from opensolaris.org

CentOS 6.4 died on me again. Didn't leave any traces that I could find. The screen just suddenly went black. Couldn't switch to another virtual terminal. Pushing the reset button worked. Didn't have to power off this time. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my

...ement legacy fbdev interface on top of drm driver > */ > > -#define to_omap_fbdev(x) container_of(x, struct omap_fbdev, base) > - > struct omap_fbdev { > - struct drm_fb_helper base; > + struct drm_device *dev; > bool ywrap_enabled; > > /* for deferred dmm roll when getting called in atomic ctx */ > @@ -41,7 +40,7 @@ static struct drm_fb_helper *get_fb(struct fb_info *fbi); > static void pan_worker(struct work_struct *work) > { > struct omap_fbdev *fbdev = container_of(work, struct omap_fbdev, work); > - struct drm_fb_helper *he...

...an dumb kernel console until userspace takes over, and Oops > printer for some emergencies. Looking at drm drivers and the basic > vesa/efi fbdev drivers shows that only 3 drivers support any kind of > acceleration: > > - nouveau, seems to be enabled by default > - omapdrm, when a DMM remapper exists using remapper rewriting for > y/xpanning > - gma500, but that is getting deleted now for the GTT remapper trick, > and the accelerated copyarea never set the FBINFO_HWACCEL_COPYAREA > flag, so unused (and could be deleted already I think). > > No other driver s...

I was check out that is the connection between driver-monitor-server-client is working or not. I was put my server directly on power cable, keep control cable connection and use command: $ watch upsc APC600 I was switch to battery, after 2-3 second it show that is on battery OB and after it shutdown because of low battery LO. I think that systemd scripts some what unsynchronized, but after it