Re: [opensuse] Re: No sound in 10.3, but it work in 10.0
On Friday 18 January 2008 12:28:06 David C. Rankin wrote:
> Lutz Maibaum wrote:
> > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
> > PCI: setting IRQ 5 as level-triggered
> > ACPI: PCI Interrupt :00:1f.3[B] -> Link [LNKB] -> GSI 5 (level,
> > low) -> IRQ 5
> > ACPI: PCI Interrupt :00:1f.5[B] -> Link [LNKB] -> GSI 5 (level,
> > low) -> IRQ 5
> > ACPI: PCI interrupt for device :00:1f.5 disabled
> >
> > The device 00:1f.5 is the sound card, according to lspci.
>
> Try booting with APIC (Advanced Programmable Interrupt Controller)
> turned off _not_ ACPI. At boot, enter "noapic nolapic". noapic is just
> "no apic" nolapic is "no local apic".
Thank you for the suggestion, David. I tried booting both with "noapic
nolapic" and in failsafe mode, but both the error message and the symptom
remain.
Looking through the dmesg output under 10.0, where sound works fine, I saw
that there the device 00:1f.3 ("SMBus: Intel Corporation 82801CA/CAM SMBus
Controller (rev 02)") does not have an IRQ associated with it, so that the
sound card 00:1f.5 ("Multimedia audio controller: Intel Corporation
82801CA/CAM AC'97 Audio Controller (rev 02)") doesn't have to share it.
Does that give anybody any clues?
Lutz
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Re: No sound in 10.3, but it work in 10.0
On Thursday 17 January 2008 18:33:16 Lutz Maibaum wrote: > I cannot get my laptop to produce any sound under 10.3. However, it > works flawlessly under 10.0, so I think the problem sits in front of the > computer... Just to follow up: I noticed some suspicious messages in my dmesg output: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :00:1f.3[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 ACPI: PCI Interrupt :00:1f.5[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5 ACPI: PCI interrupt for device :00:1f.5 disabled The device 00:1f.5 is the sound card, according to lspci. Does this mean that I have some kind of IRQ conflict? I tried to reboot with ACPI turned off, but that didn't seem to change anything. Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] No sound in 10.3, but it work in 10.0
Hello, On Friday 18 January 2008 09:18:28 Chee How Chua wrote: > What I did was to modify the file /etc/modprobe.d/sound > This file contained "options snd-hda-intel enable=1 index=0" > I changed it to "options snd-hda-intel model=auto enable=1 index=0" When I add this line to /etc/modprobe.d/sound: linux:~ # more /etc/modprobe.d/sound alias snd-card-0 snd-intel8x0 alias sound-slot-0 snd-intel8x0 options snd-intel8x0 model=auto enable=1 index=0 and then try to load the snd-intel8x0 module, I get the following error message: FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.22.13-0.3-default/kernel/sound/pci/snd-intel8x0.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg says the following: snd_intel8x0: Unknown parameter `model' Maybe this option doesn't exist for all kernel modules? Thanks for your help, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] No sound in 10.3, but it work in 10.0
On Thursday 17 January 2008 20:22:48 David C. Rankin wrote: > Lutz Maibaum wrote: > > I cannot get my laptop to produce any sound under 10.3. However, it > > works flawlessly under 10.0, so I think the problem sits in front of > > the computer... > Make sure you are a member of the audio group: > > ripper:/boot # grep audio /etc/group > audio:x:17:david,deborah,sydney,zachry I wasn't. Now I added myself to the group: [EMAIL PROTECTED]:~ $ cat /etc/group | grep audio audio:x:17:lutz [EMAIL PROTECTED]:~ $ groups users dialout audio video but the machine still doesn't make a sound. Also, if I login as root in kdm, there is still no sound. Thanks for your help, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] No sound in 10.3, but it work in 10.0
Hello, I cannot get my laptop to produce any sound under 10.3. However, it works flawlessly under 10.0, so I think the problem sits in front of the computer... lspci reports the sound chip as 00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02) and the following sound-related kernel modules are loaded: $ lsmod | grep snd snd_pcm_oss50432 0 snd_mixer_oss 20096 1 snd_pcm_oss snd_seq54452 0 snd_seq_device 12172 1 snd_seq snd_intel8x0 36636 1 snd_ac97_codec 97060 1 snd_intel8x0 ac97_bus6272 1 snd_ac97_codec snd_pcm82564 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec snd_timer 26756 2 snd_seq,snd_pcm snd58164 10 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 11460 1 snd snd_page_alloc 14472 2 snd_intel8x0,snd_pcm Both alsaconf and the the sound module in Yast seem to recognize the sound card as 82801CA/CAM AC'97, and don't report any errors when configuring the card. It just doesn't make any sound ;) I played with the volume controls in the YaST sound module and in KMix, but that didn't do anything either. At this point I am not even sure if it's a driver issue, of if there is anything wrong with my sound setting. Any help would be much appreciated! Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] One Click Install - associated helper application does not exist
On Thursday 25 October 2007 19:07:02 Patrick Shanahan wrote: > * Alister Leask <[EMAIL PROTECTED]> [10-25-07 21:22]: > > One click Install is failing whenever I try to install anything with > > the error being reported by Firefox: > > I don't believe that it works with Firefox, only with konqueror. It seems to work fine here with Firefox. The helper application should be the "YaST Meta Package handler", make sure that the package yast2-metapackage-handler is installed. If you are using KDE, you can go the File Associations section in the Control Center, search for file name pattern "ymp". The MIME type is text/x-suse-ymp. Hope this helps, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] lost suse 10.0 root password
On Tuesday 23 October 2007 19:14:31 Hans Linux wrote: > if fdisk -l, i get the info : > /dev/sda1 => Linux Swap / Solaris > /dev/sda2 => Linux > > then i give it a command : > mount -t reiserfs -o remount,rw /dev/sda2 /mnt > > i get this error : > mount: /mnt not mounted already, or bad option I assume that /dev/sda2 is your root partition (the one that contains /etc/passwd and /etc/shadow). Are you sure that it is not already mounted read-write? Just type mount and it will show the current state of /dev/sda2. If it says something like /dev/sda2 on / type reiserfs (rw) then it is already writable (notice the "rw"). In this case you should be able to reset the root password using the "passwd" command. If /dev/sda2 is mounted read-only, then you have to remount it read-write. In this case the command should be mount -t reiserfs -o remount,rw /dev/sda2 / (note that the mountpoint is /, not /mnt). If this doesn't work, could you please post the output of the "mount" command? Hope this helps, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] ls command - disable color coding
On Wednesday 17 October 2007 18:20:57 Bryen wrote: > On Wed, 2007-10-17 at 17:50 -0700, Lutz Maibaum wrote: > > These are exactly the two reasons why I prefer a .dir_colors file: > > it's in your home directory, and even if you reinstall from scratch > > the setting persists as long as you keep /home. And it is specific to > > a single user. > > Any suggestions on how to make this global? If you want a global change, you can delete the content of /etc/DIR_COLORS. The file itself has to exist, so you could try mv /etc/DIR_COLORS /etc/DIR_COLORS.bak touch /etc/DIR_COLORS as root. Hope this helps, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] ls command - disable color coding
On Wednesday 17 October 2007 17:34:58 Bryen wrote:
> Regardless, you all pointed me in the right direction and I was able to
> locate the LS color section in /etc/bash.bashrc. I changed the
> following:
>
> if test "${LS_COLORS+empty}" = "${LS_COLORS:+empty}" ; then
> LS_OPTIONS=--color=tty <--- (CHANGED TTY TO NONE)
>
> That did the trick. I suppose I should follow Patrick's suggestion and
> copy the entire LS section to bash.bashrc.local so I won't lose my
> changes in an update.
>
> This seems less volatile than creating an empty LS_Colors file and
> losing all those other colors for another user.
These are exactly the two reasons why I prefer a .dir_colors file: it's in
your home directory, and even if you reinstall from scratch the setting
persists as long as you keep /home. And it is specific to a single user.
Lutz
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] ls command - disable color coding
On Wednesday 17 October 2007 16:27:16 Bryen wrote:
> Is there a way to disable color coding in the 'ls' command permanently?
> It's giving me such lovely colors across my gnome-terminal but very
> unreadable with my sight. :-)
Usually "ls" is an alias to "/bin/ls", but with some additional options.
Try "alias ls" what they are on your system.
On mine, I get
alias ls='ls $LS_OPTIONS'
where LS_OPTIONS="-N --color=tty -T 0". This is set in /etc/bash.bashrc.
You can temper with this file, but the easiest way to disable colors
permanently is to create an empty ".dir_colors" file in your home
directory ("touch .dir_colors").
> Per the 'ls' manpages (which I don't think is true here.)
> "By default, color is not used to distinguish types of files. That is
> equivalent to using --color=none. Using the --color option without the
> optional WHEN argument is equivalent to using --color=always."
The problem is probably that you are not calling /bin/ls, but the alias,
which specifies when to user color.
Hope this helps,
Lutz
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Unable to change bootloader from 10.3
I ran into an odd problem when putting 10.3 on my x86_64 desktop: during installation, when the computer restarts for the first reboot, the system would just hang when trying to boot from the hard drive. It seems like the MBR had somehow become corrupted, but there was no error message. It took me a while to figure out how to proceed. I already had a working 10.1 partition on the same hard drive, but the "Boot installed system" option from the CD grub menu seems to redirect to the HD's MBR, which was broken. After some web browsing I picked up the strange tip to boot from the installation CD, abort the installation, which drops me into a ncurses menu, when you can find another "Boot installed system" option that does not rely on the MBR. First off, it would be nice if that option would be much easier to get to. This way I managed to boot my 10.1 system, and fix the MBR by reinstalling grub in the MBR. By adding the 10.3 partition to the grub menu I was finally able to boot into the new system. Everything seems to work fine now, but there remains one problem: I cannot change the bootloader while using the 10.3 system. When I make any changes in the "Boot Loader" section of Yast and apply them, simply nothing changes. I do not get an error message, and /var/log/Yast2/y2log is so verbose that it's hard to make sense of it if you don't know what you are looking for. The funny thing is that I can change the bootloader just fine while I am working in the 10.1 system on the same hard drive. I can edit grub setting in Yast, which take effect immediately. Does anybody know what might be behind all this, or where I should start looking for potential error messages? I am not too worried since everything is working well right now, but it would be odd to keep the 10.1 partition alive just in case I ever have to change the bootloader. Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Apps tabs
On Monday 15 October 2007 17:02:38 Bryen wrote: > When I have many things running, it just builds up more and more tabs on > my panel. In 9.3, I was able to group them per application. How do I > do that in 10.3? If you are running KDE: right-click on panel -> configure panel -> taskbar -> group similar tasks = "When Taskbar Full". Hope this helps, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Re: [EMAIL PROTECTED], first problems :s
On Sunday 14 October 2007 21:44:53 Ciro Iriarte wrote: > 2007/10/10, Ciro Iriarte <[EMAIL PROTECTED]>: > > Just installed [EMAIL PROTECTED] (changing from [EMAIL PROTECTED]), > > found > > some issues and would like to comment them to see if someone else did > > it too. > > * Firefox > > In realeases before 10.3 the 32bit firefox was installed instead the > > 64bit, now it's not the case. So, trying to stay with the new standard > > run the nsplugin app and got this: > > > > [EMAIL PROTECTED]:~> nspluginscan > > KCrash: Application 'nspluginscan' crashing... > > KCrash: Application 'nspluginscan' crashing... > > KCrash cannot reach kdeinit, launching directly. > > KCrash cannot reach kdeinit, launching directly. > > KCrash: Application 'nspluginscan' crashing... > > KCrash cannot reach kdeinit, launching directly. > > KCrash: Application 'nspluginscan' crashing... > > KCrash cannot reach kdeinit, launching directly. > > KCrash: Application 'nspluginscan' crashing... > > KCrash cannot reach kdeinit, launching directly. I also just upgraded from 10.1 to 10.3 on x86_64. I didn't understand for a while why various browser plugins didn't work, but eventually went ahead and installed the i586 version of Firefox instead of the x86_64 one. I didn't know that I was supposed to run nspluginscan, maybe that would have worked as well. I just ran it, and it seems to run fine (in the sense that it doesn't crash, it doesn't generate any output at all). Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] 10.3: unable to change KDM background
On Saturday 13 October 2007 04:44:39 Fernando Costa wrote: > to change the KDM Background you must erase the value "SUSE" on the > DISPLAYMANAGER_KDM_THEME and leave it empty, this will set the defautl > KDM Theme, that is less good looking then the SUSE one and can be > configured from the Control Panel on the login manager area Yes, I figured that one out after a while. I think this is a usability bug: there is an option in the KDE Control Center, which doesn't do anything because its effect is negated by another setting which cannot be changed in an easy way. > but if > you want a better good looking graphical KDM Theme you can install the > KDM-Theme-Manger from Yast this will make the magic... or at least just > did it on 10.2 but i can't make it run on 10. 3... if you have better > luck, let me know... I just had a look, and I couldn't find a KDM Theme manager anywhere... does it still exist in 10.3? What package / repository is it in? Thanks for your help, Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] 10.3: unable to change KDM background
Hello, after I ran into some issues installing 10.3 on my x86_64 system (for some reason the GRUB installation failed, rendering the machine unable to boot...), I tried something more trivial: I wanted to change the KDM background image. So I go to the KDE Control Center, System Administration, Login Manager, where I have the opportunity to specify a wallpaper. I pick one and reboot. The selected background image appears for a split second, but then gets replaced by the default background. I tried this a few times (which is much less painful now thanks to the great boot time!), and my best guess is that the default installation uses the SUSE KDM theme, which overrides the background requested in the KDE Control Center. Was I supposed to know that I had to look in the sysconfig editor for the keyword DISPLAYMANAGER_KDM_THEME? I found it somewhat frustrating that there was a seemingly obvious way to change the background image, but this setting was overridden by a hard to find entry in a key/value file. Is there a GUI-way to change or turn off the KDM theme? I guess I learned something out of this (there is a difference between the KDM background image and the KDM theme), but this wasn't exactly what I expected. There should at least be a warning in the Control Center that the setting might be ignored if a KDM theme has been specified. Also, at least on my system, the Control Center Help does not work in the Login Manager section when I switch to "Adminstrator Mode" (it works when I am a regular user), I get the error message "There is no documentation for /kdm/index.html.". Now that this is settled, I am looking forward to using 10.3, the reduced boot time is just fabulous. Lutz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
