[Bug 667746] [NEW] vt1708 card not recognized in 10.10
Public bug reported:
!!
!!ALSA Information Script v 0.4.59
!!
!!Script ran on: Tue Oct 12 13:42:35 UTC 2010
!!Linux Distribution
!!--
Ubuntu 10.10 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 10.10"
!!DMI Information
!!---
Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD
Product Name: MS-7253
!!Kernel Information
!!--
Kernel release:2.6.35-22-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: unknown
SMP Enabled: Yes
!!ALSA Version
!!
Driver version: 1.0.23
Library version:1.0.23
Utilities version: 1.0.23
!!Loaded ALSA modules
!!---
snd_bt87x
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
ESound Daemon:
Installed - Yes (/usr/bin/esd)
Running - No
!!Soundcards recognised by ALSA
!!-
1 [Bt878 ]: Bt87x - Brooktree Bt878
Brooktree Bt878 at 0xdf9fe000, irq 18
!!PCI Soundcards installed in the system
!!--
04:05.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture
(rev 02)
04:05.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev
02)
80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High
Definition Audio Controller) (rev 10)
!!Advanced information - PCI Vendor/Device/Susbsystem ID's
!!
80:01.0 0403: 1106:3288 (rev 10)
Subsystem: 1462:7253
!!Modprobe options (Sound related)
!!
snd-atiixp-modem: index=-2
snd-intel8x0m: index=-2
snd-via82xx-modem: index=-2
snd-usb-audio: index=-2
snd-usb-caiaq: index=-2
snd-usb-ua101: index=-2
snd-usb-us122l: index=-2
snd-usb-usx2y: index=-2
snd-cmipci: mpu_port=0x330 fm_port=0x388
snd-pcsp: index=-2
snd-usb-audio: index=-2
!!Loaded sound module options
!!--
!!Module: snd_bt87x
digital_rate :
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
id :
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index :
-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2,-2
load_all : N
!!ALSA Device nodes
!!-
crw-rw+ 1 root audio 116, 6 Oct 12 08:40 /dev/snd/controlC1
crw-rw+ 1 root audio 116, 5 Oct 12 08:40 /dev/snd/pcmC1D0c
crw-rw+ 1 root audio 116, 4 Oct 12 08:40 /dev/snd/pcmC1D1c
crw-rw+ 1 root audio 116, 3 Oct 12 08:40 /dev/snd/seq
crw-rw+ 1 root audio 116, 2 Oct 12 08:40 /dev/snd/timer
/dev/snd/by-path:
total 0
drwxr-xr-x 2 root root 60 Oct 12 08:40 .
drwxr-xr-x 3 root root 160 Oct 12 08:40 ..
lrwxrwxrwx 1 root root 12 Oct 12 08:40 pci-:04:05.1 -> ../controlC1
!!Aplay/Arecord output
!!
APLAY
List of PLAYBACK Hardware Devices
ARECORD
List of CAPTURE Hardware Devices
card 1: Bt878 [Brooktree Bt878], device 0: Bt87x Digital [Bt87x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Bt878 [Brooktree Bt878], device 1: Bt87x Analog [Bt87x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
!!Amixer output
!!-
!!---Mixer controls for card 1 [Bt878]
Card hw:1 'Bt878'/'Brooktree Bt878 at 0xdf9fe000, irq 18'
Mixer name: 'Bt87x'
Components: ''
Controls : 3
Simple ctrls : 5
Simple mixer control 'FM',0
Capabilities: cswitch cswitch-joined cswitch-exclusive penum
Capture exclusive group: 0
Capture channels: Mono
Mono: Capture [off]
Simple mixer control 'Mic/Line',0
Capabilities: cswitch cswitch-joined cswitch-exclusive penum
Capture exclusive group: 0
Capture channels: Mono
Mono: Capture [off]
Simple mixer control 'Capture',0
Capabilities: cvolume cvolume-joined penum
Capture channels: Mono
Limits: Capture 0 - 15
Mono: Capture 0 [0%]
Simple mixer control 'Capture Boost',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Simple mixer control 'TV Tuner',0
Capabilities: cswitch cswitch-joined cswitch-exclusive penum
Capture exclusive group: 0
Capture channels: Mono
Mono: Capture [on]
!!Alsactl output
!!-
--startcollapse--
state.Bt878 {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 15'
iface MIXER
name 'Capture Volume'
value 0
}
control.2 {
[Bug 658516] Re: Sound Does Not Work - No Sound Card Recognized
I'm having the same problem. "lspci" list the VT1708 but it isn't there in "Sound Preferences". -- Sound Does Not Work - No Sound Card Recognized https://bugs.launchpad.net/bugs/658516 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
That is the solution I offered about four releases ago. Check reply #18 in this thread. Then read all the guff I received for daring to suggest you run a GUI app as superuser. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
As I said, there is no .nividia-settings-rc file on my machine so I don't much care where it is saved. And at the rate its taking I'm not really concerned about what happens after "the bug is later fixed." It will undoubtedly occur after I've installed another release anyway. I'm not going to do without dual monitors because they've failed to fix this bug. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
https://bugs.launchpad.net/ubuntu/+source/nvidia- settings/+bug/200868/comments/39 This pretty much says it all. Alberto was going to write the patch but asked the higher ups how they wanted it done and never got a response. "If you run with gksudo you're running a full GUI app as root for no reason _and_ causing a bug because the .nvidia-settings-rc file will be saved for the root user instead of for the user running the app so setting changes they make that _don't_ write to xorg.conf will not be saved in the correct location. I would say just making a full GUI app run as root is enough of a bug to not implement this 'fix'. We're trying to reduce the number of apps that do such a thing, not increase them." Anybody else spot the prejudice involved in the preceding statement? What makes a GUI app anymore dangerous to run as root than a non-GUI app? Sounds to me like the old bugaboo about "real Linux users don't use GUI." Pure BS. Particularly when Ubuntu's stated aim is to make things as seamless as possible for Windoze converts. As to the ".nvidia-setting-rc" claim, that file doesn't even exist on my machine. But in general, all executable files should be in root folders, not in the /home/"user" -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
To those who feel I've been overly aggressive in my comments, I'll just say that after dealing with this situation through three releases, my patience has worn thin. Over a year ago, I went so far as to write a script that would warn the user about the dangers of running the applet as root, check to see if the original xorg.conf file was saved and if not, save it. Then backup the current xorg.conf file and finally invoke nvidia-settings via gksudo. Even this was not enough for the proponents of "doing it the proper way." They warned, as someone just did, that a "work around" would prevent a "true fix" from being implemented. Well, I shut up for over a year and waited for the "true fix." It still hasn't arrived. So, yes, I've decided to take a more aggressive stand. It is obviously necessary to do so. As to the Section "Device" code someone says needs to be added to xorg.conf, implementing the nvidia drivers put that in my xorg.conf. It wasn't necessary for me to do it manually. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
And I say there is a very good reason for doing so. It is the only way to get dual monitors to work for the average user. The only other way is to change the ownership of xorg.conf which belongs to root to begin with. There is NOT a good reason for not allowing nvidia-settings to run with root privileges You claim the saving .nvidia-settings-rc with root ownership is a bug. I say BS. Just what problem does that cause other than raise the blood pressure of paranoids? I've had dual monitors running this way for close to two years and have had no problems at all. Again, if you have a BETTER solution, then implement it. Don't just talk about it. Otherwise I'll keep advising people to do what works. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
I'd really like for someone to explain in REAL terms, not some theoretical BS, just what makes gksudo a hack, and Policy-Kit, which no one seems to be capable of implementing, not a hack. If gksudo is a hack, I'll still take a working hack over a non-working Policy-Kit everyday of the week. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Calling something that works perfectly well a hack is nonsense. The perfectionists that keep claiming this have had plenty of time to fix this in the so called "right way" and it still hasn't been done. It is totally asinine to let this situation continue for two years when there is a perfectly simple solution. There is no legitimate reason at all for not using gksudo. To claim there is a "right way" to do this when it has been over a year and the so called "right way" is still waiting implementation, is laughable. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Both nv.sh and nv1.sh should be placed in the /etc/X11 directory with the Menu pointing to nv1.sh. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Alberto; Using PolicyKit is obviously the best appraoch and your effort is apprieciated. All I intended the script alternative to be is something to use while that is being done. Take a look at these and see if they won't work. nv1.sh echo "It is not recommended that this application be run in SuperUser mode unless you" echo "are experiencing proplems saving the xorg.conf file. Doing so can cause the" echo "X server to fail to execute." echo "" echo "The first time you choose SuperUser, the /etc/X11/xorg.conf file will" echo "be saved as /etc/X11/original-xorg.conf." echo "Each time after that, it will save the current /etc/X11/xorg.conf as " echo "/etc/X11/last-xorg.conf." echo "" echo "Do you wish to run in SuperUser Mode? y/n" aa="" read aa if [ $aa = "y" ] then sudo sh /etc/X11/nv.sh else nvidia-settings fi nv.sh cd /etc/X11 if [ -f "original-xorg.conf" ] then echo cp xorg.conf original-xorg.conf else cp xorg.conf last-xorg.conf fi nvidia-settings -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
"Rationale: nvidia-settings doesn't have to be launched as root as it saves the user's settings to ~/.nvidia-settings-rc (so as to have per user settings)." It may save some of the settings there, but not all. Try setting up dual monitors without modifying xorg.conf. And I still haven't seen any "rationale" that would make my last suggestion invalid. A script would not have to be written by Nvidia and it would give the user the option of running with or without superuser mode. Unless, of course, you think people shouldn't be given sudo privileges on their own computers. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
For those purist that think it is too dangerous to have nvidia-settings run as superuser by default, create a script that allows the user to choose whether run it directly or as superuser and have it warn them of the danger of possibly having to manually replace xorg-conf from the CLI. Then have the menu option run the script. At least that way, you are not asking Nvidia to re-write nvidia- settings. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Oh?? There is a law saying "Don't run nvidia-settings" as a superuser? Nonsense. So long as it requires the sudo password, there is no reason not to do so except FUD. It is far better to have nvidia-settings write to xorg-conf than to have a novice doing so through a terminal editor. BTW, if you haven't been affected by the bug, it is probably because you haven't changed anything that required saving xorg-conf. The app runs fine otherwise. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
I did read them. And your point is? -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Solution: Edit the menu properties for Nvidia X Server Settings and change the "Type" from "Application" to "Application in Terminal." Then place "sudo" at the beginning of the "Command Line." Then when the Menu option is clicked, a terminal window is openned and you are asked for the sudo password. Enter it and the app runs with root privileges. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
