Thanks Mark, but I can’t get far enough to invoke mkinitrd. The boot process from hard disc stops quite early and does not seem to load much of the Linux kernel. I cannot see much of the log as it is sent to tty only, but I cannot log in from the $ prompt. Is it possible to do this from the Rescue functon on the 11.1 CD?
Rob
If I hadn’t seen it on the factory 11.2 version, I would have thought the same as you. Just wondering about KDE. I’m on 3.5.10 for 11.1, what about you?
Do you get the grub menu? One possibility may be to do hand edits to the boot via the grub menu (but I confess I myself do NOT know how to do that).
Failing that, then its possible you may be able to recover with the 11.1 liveCD. Possibly it will roll back to the original 11.1 kernel release, which may break your graphic driver (if you had your driver optimised for the 2.6.27.21 kernel), but then you may be able to use openGL graphic driver (or vesa graphic driver) to boot. As a bar minimum, you should be able to access your hard drive and possibly fix the problem.
Note user syampillai’s observation, that in their case, the /boot/grub/menu.lst needed to be edited. syampillai observed “**It always generates “root (hd0,0)” instead of “root (hd0,1)”. **”
Thanks Mark,
This fix appears to have resolved all issues ex. sound. Still no luck there.
Here’s the alsa-info.sh output: http://www.alsa-project.org/db/?f=3f49b3b9966c5f573b904879168e6df0867f145d
Your sound device is not even detected. I note this:
!!Aplay/Arecord output
!!------------
APLAY
aplay: device_list:217: no soundcards found…
ARECORD
arecord: device_list:217: no soundcards found…
What is the output from dmesg ? You can get that by using curl with dmesg with your PC connected to the internet as follows (and post here the URL):
dmesg > dmesg.txt && curl -F file=@dmesg.txt nopaste.com/a
that may indicate the error. Only post the URL. Please don’t flood this thread with the massive dmesg output. Only the URL.
Its possible you need to update alsa to be consistent with the new kernel release. The SuSE-GmbH packager who packages updated alsa versions for new kernels, has not yet released a new alsa version for the new kernel. Thursday is a holiday in Germany, so its possible they took vacation this week. I recommend you wait until next week, and then check to see if the new alsa version (for the 2.6.27.23 kernel) has been released yet, and if so, update to it.
The output is not pretty … I note this:
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2008 Intel Corporation
hda_codec: Unknown model for ALC268, trying auto-probe from BIOS...
ALSA sound/pci/hda/hda_codec.c:3188: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3192: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3196: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3197: mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3205: inputs: mic=0x19, fmic=0x18, line=0x1a, fline=0x0, cd=0x0, aux=0x0
hda_codec: Unknown model for ALC268, trying auto-probe from BIOS...
ALSA sound/pci/hda/hda_codec.c:3188: autoconfig: line_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3192: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3196: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3197: mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3205: inputs: mic=0x0, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0
hda_codec: Cannot set up configuration from BIOS. Using base mode...
ALSA sound/pci/hda/hda_intel.c:1878: SPDIF already defined
ALSA sound/core/control.c:329: control 2:0:0:Front Playback Volume:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Front Playback Switch:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Headphone Playback Volume:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Headphone Playback Switch:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Mic Boost:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Front Mic Boost:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Capture Volume:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Capture Switch:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Input Source:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Beep Playback Volume:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:Beep Playback Switch:0 is already present
ALSA sound/core/control.c:329: control 2:0:0:IEC958 Default PCM Playback Switch:0 is already present
HDA Intel 0000:00:1b.0: PCI INT A disabled
HDA Intel: probe of 0000:00:1b.0 failed with error -16
I see your wireless is being configured in the middle of the alsa driver loading. What happens if you try to configure your sound device with “alsaconf” or with “yast > hardware > sound” ? Or if you type: su -c ‘rcalsasound restart’
I also note it is struggling to figure out your PC’s alc268 hardware audio codec … You could try to force a model option to your PC for the alc268 hardware audio codec upon boot. Do you know what those options are? If not, I can post the list (and how to edit your /etc/modprobe.d/sound file).
You are spot on! I had already tried the Rescue option from the CD without success and the Repair option always gives big problems with RAIDed discs. However, I went for the Upgrade and this worked, once the Framebuffer driver was invoked. I now have to put the nVidia driver back in place and see what else has been mangled. However, I do have a usable system back!
The only problem I seem to have now is that on shutdown, I get a dialogue box telling me there is a root user on tty1, although there isn’t. I have to OK that to shut down.
Thanks again for your help.
Rob
alsaconf ran and claimed success but then:Loading driver…
Starting sound driver: hda-intel done
Setting default volumes…
amixer: Mixer attach default error: No such file or directory .
yast>hardware>sound>edit produces the following error message: “The kernel module snd-hda-intel for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters.”
**su -c ‘rcalsasound restart’ **produced: “Shutting down sound driver done
Starting sound driver: hda-intel”
but did not have any other effect
I also note it is struggling to figure out your PC’s alc 268 hardware audio codec … You could try to force a model option to your PC for the alc268 hardware audio codec upon boot. Do you know what those options are? If not, I can post the list (and how to edit your /etc/modprobe.d/sound file).
Sorry, I don’t know what those options are. Any help you can offer would be greatly appreciated, thanx in advance.
OK, can you post the output of:
rpm -qa | grep alsa
cat /etc/modprobe.d/sound
which will tell us what is in your /etc/modprobe.d/sound file. I can provide the precise syntax you can use. Here is a list of 9 different model options (with a brief description) for 1.0.18 version of alsa (from the alsa-configuration.txt file), and there is a specific syntax to be used in the /etc/modprobe.d/sound file to force a specific alsa model configuration.
ALC267/268
quanta-il1 Quanta IL1 mini-notebook
3stack 3-stack model
toshiba Toshiba A205
acer Acer laptops
acer-aspire Acer Aspire One
dell Dell OEM laptops (Vostro 1200)
zepto Zepto laptops
test for testing/debugging purpose, almost all controls can
adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
auto auto-config reading BIOS (default)
I ran su -c ‘rcalsasound restart’ and still no sound but then i checked kmix and the master was muted.
Seems enabling pulseaudio in yast (as mentioned in another thread) was only a only a temporary fix as it stopped working after a reboot
Did you mean this thread. I didn’t actually enable P/A i.e.
This is very strange! If I select YaST>Hardware>Sound and click on nothing further, the Kmix icon in the system tray is immediately unmuted.
I have the problem, but sound works once unmuted. Your right it didn’t fix beyond reboot. It was just odd :. I run without P/A enabled, since first 11.1 install.
alsa-tools-1.0.18-1.16
alsa-1.0.18-8.9
alsa-utils-1.0.18-6.4
alsa-oss-1.0.17-1.43
alsa-oss-32bit-1.0.17-1.37
alsa-plugins-1.0.18-6.13
alsa-devel-1.0.18-8.9
alsa-plugins-pulse-1.0.18-6.13
alsa-firmware-1.0.17-1.42
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
Ok, so given these are the model options:
ALC267/268
quanta-il1 Quanta IL1 mini-notebook
3stack 3-stack model
toshiba Toshiba A205
acer Acer laptops
acer-aspire Acer Aspire One
dell Dell OEM laptops (Vostro 1200)
zepto Zepto laptops
test for testing/debugging purpose, almost all controls can
adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
auto auto-config reading BIOS (default)
you could try each of those model options, one at a time, restarting your sound after each. ie try auto, test, zepto, dell, acer-aspire, acer, toshiba, 3stack, quanta-il1 one at a time. So to start with “auto”, change your /etc/modprobe.d/sound file to:
options snd-hda-intel model=auto
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
then restart your alsa sound driver with su -c ‘rcalsasound restart’ enter root password when prompted for a password, restart your mixer (kmix for kde, alsamixer for gnome) and test your audio. If that does not work, in the same file change “auto” to “test”, and try again (restart alsa, restart mixer, test). Then replace “test” with “zepto” … etc … trying each option, restart alsa and mixer for each test.
auto, test, zepto & 3stack resulted in no change
dell & acer-aspire did get kmix to show a volume control (front only) but no sound
acer & toshiba & quanta-il1 did the same + also produce sound with # speaker-test -c2 -l5 -twav
It was very faint, barely audible (even with volume maxed in kmix) and no additional controls showing in kmix (i.e. no microphone etc), but it was progress.
ps. in all cases yast>hardware>sound shows “not configured” and no sound from other>play test sound
In prior versions, ‘S2ram -f -a 3’ gracefully suspended my desktop and WOL woke it up.
As of right now, with 2.6.27.23, Suse stops (can’t tell yet if it is suspended properly) but the power and fans remain on
Ok, but when you get the low volume sound, did you try YAST > HARDWARE > SOUND > OTHER > VOLUME and move up the PCM and Master volume controls to 95% (if there is a “speaker” volume control , move that up also). Then go to kmix and adjust your volume.
Note that in KDE4 one needs to add extra “channels” (for extra controls) to their kmix to get the extra controls …
And finally with the model option applied that gives low sound, run the diagnostic script so we can check your mixer settings:
/usr/sbin/alsa-info.sh
and post here the URL provided. Just the URL.
As noted above, when I go into yast>hardware>sound>other>voume or >play test sound there is no result at all, i.e. the mouse click is completely non-responsive. In the sound window yast2 reports that the card is not configured, so I’ve gone to >edit> to attempt to configure the card. I can not configure though, and I get an error message saying “The kernel module snd-hda-intel for sound support could not be loaded. This can be caused by incorrect module parameter, including invalid IO or IRQ parameters.”
When that happened I backed out of yast2 and reopened kmix, but there was no longer any sound card found. I ran su -c ‘rcalsasound restart’ and saw the sound card reappear in kmix.
This is way over my head, so I’m giving you two links here in hopes that you can make some sense of this.
http://www.alsa-project.org/db/?f=0c15acd8087f2e1579390b9c6b694974e54a59b6 was recorded before running yast’s edit option
http://www.alsa-project.org/db/?f=54c9df1eb93b747244dc770807f99627aab8db2b was recorded after the attempt
Thanks again for your time.
I did not ask you to use the YaST test sound. It is known to be buggy.
I asked this:
Ok, but when you get the low volume sound, did you try YAST > HARDWARE > SOUND > OTHER > VOLUME and move up the PCM and Master volume controls to 95% (if there is a “speaker” volume control , move that up also). Then go to kmix and adjust your volume.
When adjusting kmix volume, use the speaker-test from the audio troubleshooting guide:
speaker-test -c2 -l5 -twav
You need to do a test outside of YaST. So I have absolutely no idea as to whether those links you provided incorporate my recommendation, … and hence its difficult to give you an additional recommendation, as that volume recommendation was key (as you noted you had sound with low volume). Where do we stand?
So if you did not do so, please go back and try my recommendation.
That looks ugly (re: the mixer). Did you try testing your audio with root permissions ?