Debian Configuration :: Samba Denies Login After Upgrade To Jessie

Jan 2, 2016

I just upgraded to jessie and now Samba won't let me log in anymore. I merged smb.conf manually. It now looks like this (removed comments):

Code: Select all[global]
   workgroup = WORKGROUP
   dns proxy = no
   bind interfaces only = no
   log file = /var/log/samba/log.%m
   max log size = 1000
   syslog = 0

[Code] .....

With smbclient logs as follows:
Code: Select allsmbclient -L 192...

Enter user's password:
session setup failed: NT_STATUS_UNSUCCESSFUL

If I provide a wrong password, it raises NT_STATUS_LOGON_FAILURE, also if retry with the correct password.

Not sure about what resolved the issue. But after I purged samba, reconfigured it, added the users AND set www-data's shell to bash again (which was changed during the update), it now seems to work

View 0 Replies


ADVERTISEMENT

Debian Configuration :: Samba Denies Symbolic Links After Upgrade

Mar 14, 2010

I just upgraded samba on my lenny-server:

apt-cache policy samba
samba:
Installed: 2:3.4.7~dfsg-1~bpo50+1

...and since then my windows xp clients cannot follow a symbolic link to a common area from their home folders.

I have googled and tried to add follow symlinks and wide links to my homes share

[homes]
= Home Directories
browseable = no
follow symlinks = yes
wide links = yes

...but after restarting samba on the server and rebooting the windows machine the user still cannot follow the link.

View 3 Replies View Related

Debian Configuration :: Printing From Windows After Upgrade To Jessie - Samba Seems To Crash Completely

Sep 22, 2015

I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.

STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid
[2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3)
PANIC (pid 3704): assert failed: pjob->jobid == jobid
[2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace)
BACKTRACE: 27 stack frames:

[Code] ....

View 0 Replies View Related

Debian Configuration :: Jessie - Service Samba Restart

Oct 20, 2014

I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.

Output of "systemctl status samba.service":

Code:
Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd)
   Loaded: loaded (/etc/init.d/samba)
   Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago
  Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)

Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating.
Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).

[Code] ....

Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.

View 2 Replies View Related

Debian Configuration :: Jessie After Dist-upgrade / Password Not Working

Jul 13, 2015

updated my jessie by apt-get dist-upgrade and there was an error said there was something wrong with some database, and I needed to run some command, but after the upgrade I forgot to run the command. After I rebooted my system I found there was not any password needed for a normal user or the root. But if I change to the emergency mode, a root password is needed.

View 4 Replies View Related

Debian Configuration :: Jessie Upgrade Broke NTFS Drive

Sep 22, 2015

I had a Linux server with Wheezy, I have 2 internal drive, one for linux OS, the other our Video On Demand drive that must be accessible to Windows and online. (That's why I chose NTFS, with our large video files, FAT will not work, and EXT isn't compatible with windows sharing, and I haven't gotten FTP to work right .

So I upgraded to Jessie today, and everything went smoothly until I tried to access my NTFS drive. (Named WowzaStorage)

I used FSTAB to auto-mount the drive (/dev/sdb1) to /media/ntfs/ on boot. All of this worked swimmingly on Wheezy, but since the update, something got mucked up and I cannot figure it out.

When accessing the mounted NTFS folder in /media/ (if it even shows up) gives me a 'Cannot be found' 'Input/Output error'

When in gParted to examine the drive, I can select it and view all the correct info, but I keep getting "error informing the kernel about modifications to partition /dev/sdb1/ --invalid argument"

Now first I thought maybe the NTFS driver was faulty and I removed 'ntfs-3g' and reinstalled it.

Now when I am in Terminal, after i umount and mount sdb1, I can CD to the drive but not the folders on it... Also using the File Browser, I get errors, and missing folders.

I get "Unhandled error message: Error when getting information for file '/media/ntfs': Input/output error"

View 2 Replies View Related

Debian Configuration :: Jessie Upgrade Ssh Command Line Reboot

Nov 13, 2015

I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.

If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.

View 4 Replies View Related

Debian Configuration :: Dmraid Device Fails To Mount After Jessie Upgrade

Oct 18, 2015

I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem

[URL] ....

I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here

[URL] ....

After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.

[URL] .....

This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?

The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.

View 2 Replies View Related

Debian Configuration :: Courier Including SSL - No Shared Cipher After Upgrade To Jessie

Feb 26, 2016

I had a pretty much standard installation according to some tutorial (I don't remember, which one) for courier, including ssl. After upgrading from Wheezy (7) to Jessie (8) everything continued working fine, excep ssl connections to pop or imap.

In the log I get this error message while connecting to imapd-ssl:

Code: Select allFeb 26 20:16:22 mx imapd-ssl: couriertls: connect: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher

First I thought there got some chiphers removed from default configuration. But even when I try to allow all protocols and all ciphers:

Code: Select allTLS_PROTOCOL="SSL23"
TLS_CIPHER_LIST="ALL"

And then test via s_client:

Code: Select all# openssl s_client -connect 127.0.0.1:993 -cipher ALL
CONNECTED(00000003)
3073349308:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:770:

---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 341 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
---

TLS over STARTTLS is also not working and does not invoke a log-entry. So I want to solve the ssl-problem first. I guess the STARTTLS-problem is automatically solved then.

My update procedure was:

Editing /etc/apt/sources.listapt-get updateapt-get upgradeapt-get dist-upgradeKeep all configuration files regarding courier.

View 2 Replies View Related

Debian Configuration :: Samba - Cannot Access Server After Upgrade

Mar 12, 2016

Following yesterday's and then today's upgrade of my Debian 8 32-bit system (among other things to samba 2:4.1.17+dfsg-2+deb8u2 (yesterday: ...deb8u1)) I cannot connect my Mint 17.3 laptop to the server anymore. Were there any changes to smb.conf regarding authentication or other aspects that might lead to this problem? I am enclosing part of my smb.conf. By the way - I also have trouble using ssh to connect to the Debian machine, such as the ssh-command taking "for ever" and then getting the message "Write failed: Broken pipe" when entering an ls-command on the command line.

H. Stoellinger
smb.conf:
[global]
workgroup = RAINERMUSIK
netbios name = hsdesk
server string = Samba Server hsdesk

[Code] ....

View 1 Replies View Related

Ubuntu Networking :: Samba Share Denies Write, Smb.conf Snippet Included?

Aug 10, 2010

I'm a very -slightly- advanced Samba user. I believe I know the basics of editing the smb.conf and I know to use smbpasswd to update the Samba users database.I have a group of identical shares.They are readOnly for the group @movies-play and they are (supposed to be) writeable by specific users. The readOnly group works great, no prob there, but I cannot get write access for the specified users. They are in the Samba user database using smbpasswd -a mark and neelix.Here is the share section in my smb.conf...

Code:
[movies-usb3]
path = /media/usb3/movies
guest ok = no[code]....

I have the workgroup and netbios info set. I have security=user set. The folder 'movies' in the path above is owned by 'mark' so it seems I should be able to write in it but I can't.I'm connecting to the share (it's on a server running Lucid) from my laptop (running Lucid. I added this mount info to fstab...

Code:
//spock/movies-usb3 /media/spockmovies3 cifs credentials=/home/mark/.smbpasswd 0 0
Of course spock in the hosts file so it resolves. I can see the share fine, just can't write.

View 9 Replies View Related

Debian Configuration :: Jessie - How To See What DNS Servers Are Actually In Use

Sep 24, 2015

I am running Jessie 8.2, upgraded from Wheezy about a week ago.

KDE Desktop, static IP
NetworkManager.conf shows:
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true
dns=none

The dns=none is to keep NetworkManager from overwriting /etc/resolv.conf (which shows):

nameserver aaa.bbb.ccc.ddd
nameserver aaa.eee.fff.ggg
nameserver aaa.hhh.iii.jjj
search mydomain.com

It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?

View 10 Replies View Related

Debian Configuration :: 8.0 Jessie Can't Log In With SSH Anymore

Jan 11, 2016

I installed Debian Jessie on my Hummingbaord. I use it with apache, owncloud and minidlna but after some days i rebooted the system and then i can't log in with SSH anymore.

The message I get:

Access denied
Using keyboard-interactive authentication.
Password:

And this again and again, although I enter the right password. If I login directly on the Hummingboard all works normally...

View 6 Replies View Related

Debian :: How To Do Auto Login With Gdm3 On Jessie

Jul 4, 2015

How can i do auto login with gdm3 on debian jessie?

View 1 Replies View Related

Debian Configuration :: Java Uses High CPU In Jessie

Jun 24, 2015

I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.

I have to kill java to go back to normal. So, when I do a
Code: Select allkillall -KILL java
the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.

Currently I am based on openjdk
Code: Select allupdate-alternatives --display java
java - auto mode
  link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071
  slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz
Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.

But I have also tried the SUN version with the same result.

Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...

View 2 Replies View Related

Debian Configuration :: Fsck On Boot Jessie 8.1

Jun 25, 2015

I use debian jessie 8.1 and when i boot it, pc start fsck block clean etc.. but the fsck control is activated every on boot?

View 14 Replies View Related

Debian Configuration :: How To Get Boot Log On Jessie / Stretch

Oct 14, 2015

When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.

View 4 Replies View Related

Debian :: Possible To Upgrade From Squeeze To Jessie?

Jun 25, 2015

I installed a Debian server a few time ago, with the Squeeze version.

Now I want to upgrade it to Jessie, but all related documentation only talk about the procedures to upgrade from Wheezy to Jessie.

What should I do? Upgrade first Squeeze to Wheezy and after that to Jessie, or I can upgrade from Squeeze to Jessie?

View 3 Replies View Related

Debian :: How Does One Bring Up The Gpsd Configuration Dialog With Jessie

Jun 5, 2015

Configuring gpsd with Wheezy was a breeze. Just had to run "sudo dpkg-reconfigure gpsd", answer a few questions, and it worked like a charm. With Debian Jessie the following happens:

tsi@sxf-tsi:~$ sudo dpkg-reconfigure gpsd
Warning: Stopping gpsd.service, but it can still be activated by:
gpsd.socket
Creating/updating gpsd user account...
tsi@sxf-tsi:~$

How does one bring up the gpsd configuration dialog with Jessie?

View 1 Replies View Related

Debian Configuration :: How To Config Touchpad On Jessie In Gnome3

Jun 20, 2015

I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.

I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.

etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?

View 2 Replies View Related

Debian Configuration :: Apt-get Auto-remove After Installing Jessie

Jun 20, 2015

After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?

linux-image-3.14-0.bpo.1-amd64
linux-image-3.14-0.bpo.2-amd64
linux-image-3.16-0.bpo.2-amd64
linux-image-3.16-0.bpo.3-amd64
linux-image-3.2.0-4-amd64

How about results shown by deborphan?

View 9 Replies View Related

Debian Configuration :: Jessie Will Not Reboot On Remote Server

Jun 27, 2015

Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.

how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.

View 3 Replies View Related

Debian Configuration :: Jessie WD Disk Mount Fail

Aug 20, 2015

A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.

umount My passport
fdisk -l (to see device name)
mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4
dmesg | tail
[ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found
[ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through

[code]....

View 2 Replies View Related

Debian Configuration :: Jessie Xrandr Rotation Bad Corruption

Nov 25, 2015

DE: lxde
version: Jessie
using xorg file: no

After changing my video cards from gigabyte HD5450 and saphire X550 to two saphire r7 240s one of my debian installs no longer supports rotating the monitors either with 'Monitor Settings' or xrandr. The only difference between these 2 Jessie installs is that one was upgraded and the other one was fresh. The problem is with the upgraded one. On the fresh installed debian I just put the ati proprietary driver so I won't do further testing on it but xrandr was working fine on it before that.

I tried going over the ATIHowTo [URL] .... and everything looks good. Tried purging the non free firmware and reinstalling. I verified the version numbers of libxrandr2 and kernel of both installs. It is either some scrap left over from wheezy or a configuration file I am not aware of.

So what actually happens is xrandr does not say anything, blanks out all windows on the screen with only their background color and title bar showing, changes the lxpanel to its background pattern except for 2 blanked out boxes almost to the right of the screen( I have 10 tray icons there before it blanks), activates the screen I wanted to rotate with the proper rotation. On my main screen I can't click on anything. On the rotated screen I can right click and I get my openbox right click menu like I do on my main monitor before the command but when I try to run something nothing happens. The only way I can get out of this situation is to go to ctrl-alt-f1, log in as root and type 'service lightdm restart'.

Both of these monitors are connected to the primary video card, an ati r7 240 saphire. The main one is on vga and the other one is on DVI. I also have another monitor connected to HDMI but it's not being used. I have yet another monitor connected to the VGA of the secondary GPU I don't think it's a problem is it? I tried not using 'xrandr --setprovideroutputsource 1 0' and it still did the same thing.

I tried just launching openbox with no LXDE and it did the same thing.

Also another strange thing is when I stop the lightdm service and try to 'startx' or 'xinit' my screens go blank; numlock, control-alt-delete and control-alt-f1 do nothing and the only thing I can do is an emergency REISUB. I didn't configure this install to use startx or xinit yet but should it really lock up my system?

On the affected system my script looks like this (I already did this step by step and the 'rotate left' line is causing the problem):

Code: Select allxrandr --setprovideroutputsource 1 0
xrandr --output VGA-0 --primary --mode 1680x1050 --pos 0x0 --rotate normal
 --output DVI-0 --mode 1680x1050 --pos 0x1050 --rotate left
 --output HDMI-0 --off
 --output VGA-1-1 --off

lxpanelctl restart

Additional info:

Code: Select all$ inxi -G
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
           Card-2: Advanced Micro Devices [AMD/ATI] Oland PRO [Radeon R7 240]
           Display Server: X.Org 1.16.4 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz, 1680x1050@59.95hz
           GLX Renderer: Gallium 0.4 on AMD OLAND GLX Version: 3.0 Mesa 10.3.2

[Code] .....

View 14 Replies View Related

Debian Configuration :: Jessie With XFCE - Service Fails

Feb 10, 2016

I am using Jessie with XFCE and I tried to write a service which executes a script to change my wallpaper. When I try to start the service with systemctl start wallpaper.service it fails and I get the outout below from systemctl status wallpaper.service

I don't think it to be a permissions issue, they are -rw- r-- r--

This service is called by a timer that goes off daily. Below is wallpaper.service

View 5 Replies View Related

Debian Configuration :: Slower Than Usual Boot In Jessie

Feb 22, 2016

I've recently noted that the boot process in my Jessie installation is occasionally taking longer than usual, not dramatically as in "really hanging", but still noticeably slower, during which some messages are printed along the lines of

Code: Select alla starting job is running (2 of 5) and also after that, once lightdm (I'm using the MATE desktop) comes up the screen gets painted slower as well.

Unfortunately, once the system is up and running there's no longer trace in the logs (either traditional syslogs or journalctl) of such messages, however what comes to mind is that I've just recently enabled persistent logging in systemd: could this be the reason of such (occasional) slower boot process?

Other than that, what else could cause such behaviour? What should I eventually check to ensure things are OK?

View 11 Replies View Related

Debian Configuration :: How To Load Own Kernel-module (KO) In Jessie

Mar 14, 2016

I built a kernel-module for a new usb wifi-card. This worked well and resulted in a 8821au.ko-file. But now I'm trying to load this kernel module since half an hour and it doesn't work. I copied the ko-file into /lib/modules/3.16.0-4-amd64/kernel/drivers/edimax. If I just type

Code: Select allsudo modprobe 8821au

I get a

Code: Select allmodprobe: FATAL: Module 8821au not found..

But if I enter the full path inside the /lib/modules/3.16.0-4-amd64-folder:

Code: Select allsudo modprobe -v ./kernel/drivers/edimax/8821au.ko

it seems to work:

Code: Select allbuiltin ./kernel/drivers/edimax/8821au.ko.

But lsmod doesn't show me the module after that.

I also added

Code: Select all./kernel/drivers/edimax/8821au.ko

to /etc/modules but this also doesn't seem to work. When booting I get an error-message, but it's too fast to read it and I can't find the right log-file, where the booting-part with the "[ OK ]"-messages is reported.

So my driver is ready, the onliest thing which I can't get working is loading it as a kernel-module.

View 3 Replies View Related

Debian Configuration :: Jessie Missing Fan Control / Sensor

Apr 27, 2016

My laptop fan sensor shows fine in psensor in sid. But today I downgrade to jessie and sensor for fan gone. I check if fancontrol is running but I can not manage to make it work

sensors
Code: Select allacpitz-virtual-0
Adapter: Virtual device
temp1:        +55.0°C  (crit = +108.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +55.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:         +55.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:         +54.0°C  (high = +87.0°C, crit = +105.0°C)

[Code] ....

I google and have tried but no luck
Code: Select allacpi_enforce_resources=lax

This is an Asus laptop with controllable fan. I am not sure if fan is running by Bios, and how it might run. But I feel the laptop seem quieter and at higher temperature than it was under sid.

View 9 Replies View Related

Debian :: No Internet After Upgrade From Wheezy To Jessie

May 27, 2015

I upgraded my Wheezy 7.8 to make sure all packages were installed Before taking the next step to upgrade to Jessie.I upgraded to Jessie and it seemed to run OK....but after reboot I had no network Connection..I checked ifconfig and the wrong network card mac address is being assigned to the wrong card....?I have a clonezilla server on my server, so this was my network interfaces before and after upgrade

Code: Select all# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback

[code]...

I even checked nano /etc/resolv.conf and sure enough my gateway was the same for my Internet eth0.When I ran ifconfig I could see that the eth0 mac address was set as eth1..I tried to reset my drbl for clonezilla but that only sees the vmware Connection and not my actural cards.. have taken alook at /etc/udev/rules.d/70-persistent-net.rules and the assignment is right but not ifconfig?

View 14 Replies View Related

Debian :: Wheezy To Jessie Upgrade Will Not Boot

May 28, 2015

With "quiet" removed from the grub linux line, I'm getting the following error messages when the boot hangs up early in the boot process (19.768231 seconds into boot).:

input: HDA NVidia HDMI/DP,pcm=3 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
input: HDA NVidia HDMI/DP,pcm=7 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input7
input: HDA NVidia HDMI/DP,pcm=8 as devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input8

So, is this a NVidia issue or a sound card issue?

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved