Re: 2.6.11.x: bootprompt: ALSA: no soundcard detected
It's definetly ACPI! I played around with ACPI options in the BIOS and got my card working again. However, now reiserfs sometimes hangs and remembers this state so that I must check it from a live-cd. Linux 2.6 is definetly more sensible than 2.4. Regards, Dennis - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.11.x: bootprompt: ALSA: no soundcard detected
It's definetly ACPI! I played around with ACPI options in the BIOS and got my card working again. However, now reiserfs sometimes hangs and remembers this state so that I must check it from a live-cd. Linux 2.6 is definetly more sensible than 2.4. Regards, Dennis - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.11.x: bootprompt: ALSA: no soundcard detected
Aehhm, you are completely on the wrong track! I installed 2.6.11.7 the same way I installed 2.6.11, with sound support statically included, but, though it worked fine without ACPI under 2.6.11, the same configuration under 2.6.11.7 does not work. There was no change in practise, only a change in behaviour. Dennis That means you didn't load the correct module for your soundcard. On Sun, 10 Apr 2005 10:16:49 +, Dennis Heuer <[EMAIL PROTECTED]> wrote: > This doesn't help. Alsamixer prints: > > failure in snd_ctl_open: no such device > > Dennis -- Time is what you make of it - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[no subject]
unsubscribe linux-kernel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.11.x: bootprompt: ALSA: no soundcard detected
Hello, I switched from 2.4 to 2.6.11 and found that the hard power-down now definetly needs ACPI, which stopped my soundplayer life from playing (stucking display and no sound), though. I installed 2.6.11.4, 2.6.11.5, and 2.6.11.7 but all three broke the hardware detection on my system. Now, with or without ACPI, the soundcard isn't even found. There is no further error message, linux installs as always. Regards, Dennis Heuer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.11.x: bootprompt: ALSA: no soundcard detected
Hello, I switched from 2.4 to 2.6.11 and found that the hard power-down now definetly needs ACPI, which stopped my soundplayer life from playing (stucking display and no sound), though. I installed 2.6.11.4, 2.6.11.5, and 2.6.11.7 but all three broke the hardware detection on my system. Now, with or without ACPI, the soundcard isn't even found. There is no further error message, linux installs as always. Regards, Dennis Heuer - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[no subject]
unsubscribe linux-kernel - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.11.x: bootprompt: ALSA: no soundcard detected
Aehhm, you are completely on the wrong track! I installed 2.6.11.7 the same way I installed 2.6.11, with sound support statically included, but, though it worked fine without ACPI under 2.6.11, the same configuration under 2.6.11.7 does not work. There was no change in practise, only a change in behaviour. Dennis That means you didn't load the correct module for your soundcard. On Sun, 10 Apr 2005 10:16:49 +, Dennis Heuer [EMAIL PROTECTED] wrote: This doesn't help. Alsamixer prints: failure in snd_ctl_open: no such device Dennis -- Time is what you make of it - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: A way to smoothly overgive graphics control to an other process/program
> Is this technically feasible? It's technically pointless. Take a look at bootsplash, though. -- Måns Rullgård [EMAIL PROTECTED] Bootsplash does exactly what I was complaining about. It controls only some part of the process of *booting* into the desktop without smooth transition (though it's at least a nice toy). The rest of your answer hits me but doesn't help me a little. Sorry if I am a pointless non-geek. Dennis - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
A way to smoothly overgive graphics control to an other process/program
Hello, I feel disturbed by the fact that when display-controlling programs are started in line (like the bootloader, linux, and finally xdm/gdm/kdm), there appear several switches of display resolution, text- and graphics mode, and background images. I asked myself how to get that more smooth as if there was only one presentation from the time the bootloader started up to the gnome/kde session. I thought that one could implement a small api that allows a running process to freeze display updates until the next process has overtaken the display, loaded the same presentation (from same location or just by similar configuration), dumped it to the working buffer of the graphics card, and released the display (a timeout with fallback-mode could make this transaction more fault-resistent). This way, the image loaded by the bootloader could be held on display up to the graphical login, and even as the desktop background, without any visible effect. Is this technically feasible? Regards Dennis Heuer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
A way to smoothly overgive graphics control to an other process/program
Hello, I feel disturbed by the fact that when display-controlling programs are started in line (like the bootloader, linux, and finally xdm/gdm/kdm), there appear several switches of display resolution, text- and graphics mode, and background images. I asked myself how to get that more smooth as if there was only one presentation from the time the bootloader started up to the gnome/kde session. I thought that one could implement a small api that allows a running process to freeze display updates until the next process has overtaken the display, loaded the same presentation (from same location or just by similar configuration), dumped it to the working buffer of the graphics card, and released the display (a timeout with fallback-mode could make this transaction more fault-resistent). This way, the image loaded by the bootloader could be held on display up to the graphical login, and even as the desktop background, without any visible effect. Is this technically feasible? Regards Dennis Heuer - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: A way to smoothly overgive graphics control to an other process/program
Is this technically feasible? It's technically pointless. Take a look at bootsplash, though. -- Måns Rullgård [EMAIL PROTECTED] Bootsplash does exactly what I was complaining about. It controls only some part of the process of *booting* into the desktop without smooth transition (though it's at least a nice toy). The rest of your answer hits me but doesn't help me a little. Sorry if I am a pointless non-geek. Dennis - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
