unsubscribe
Re: acpi_power_off hangs
Hi, Am Montag, 21. Juni 2004 05:39 schrieb Emma Jane Hogbin: > It's very possible you will need to update your BIOS. You should check > over at the ACPI mailing list to see if they have any suggestions. > > http://acpi.sourceforge.net/ > http://lists.sourceforge.net/lists/listinfo/acpi-devel thank's for the hint! I did it already and I have also the newest BIOS and a custom DSDT installed. I am happy with kernel 2.6.5 where everything is working fine, therefor there is not really an important reason to upgrade to 2.6.7 for me. Let's see, maybe the ACPI problem will go away with some of the next kernel versions. Regards, Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: Re: Going wireless
Hi. I missed the beginning of this thread, but are you sure that the HF (high frequency) part of your WLAN card is enabled and that the HF part of the card is not damaged? If the HF part is not enabled then the driver is namely able to detect the card without problems, but the card itself is not able to send and receive data. On some notebooks you can enable the HF part by keystrokes, on others by software. Regards, Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X window woes on HP pavilion ze4600
Hi, Thanks to those who answered some questions of mine some days ago. I have now tried several variations upon several themes in order to get debian (v. 3.0) on my laptop (HP pavilion ze4600), and had gotten a stable command line version running. I thereupon started X via startx which caused for some reason first a KDE setup dialog to appear (everything freezes) and after a reboot a gnome login dialog (again, everything freezes). I presume that the configuration of X is completely wrong so that I have no ability to use keyboard or touch pad. Is there a boot setting for the debian rescue boot (using a 3.0 DVD) that will prevent X from starting so that I will be able to change the settings of X? Any other ideas? Thanks Peter
Alsa setup broken after upgrade
I have a mixed testing/unstable system running on a HP Omnibook 4150 laptop [sound chipset is cs4232]. Recently, I upgraded a number of things, including gcc (2.95.4 -> 3.3.3), alsa (0.9.4 -> 1.0.5a), and kernel-source (2.4.19 -> 2.4.26). Before the upgrades, I had a working Alsa setup, but now attempts to load the snd-cs4232 module fail with the errors: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_pointer /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_disable /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_program /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: insmod /lib/modules/2.4.26/alsa/snd-cs4231-lib.o failed /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: insmod snd-cs4232 failed Executing "cat /proc/asound/cards" results in: --- no soundcards --- Also, alsaconf fails to find my hardware. The output of lspci shows that the kernel still sees the sound hardware: :01:00.1 Multimedia audio controller: Neomagic Corporation NM2200 [MagicMedia 256AV Audio] (rev 12) My kernels were custom built using make-kpkg. Sound support was staticly compiled into the kernel, and no OSS modules were selected. Please note also that my previous version of Alsa was after the snd_ prefix was depreciated for module options, so I had already changed my configuration to correct any problems caused by that. ii alsa-base 1.0.5a-1 ALSA sound driver common files ii alsa-modules-2 1.0.5a-1+hpomn Advanced Linux Sound Architecture (drivers) ii alsa-oss 1.0.5-1Advanced Linux Sound Architecture (OSS compa ii alsa-source1.0.5a-1 ALSA sound driver source ii alsa-utils 1.0.5-1Advanced Linux Sound Architecture (utilities ii libasound2 1.0.5-1Advanced Linux Sound Architecture (libraries I would appreciate any help that people can give me with this problem. I'm not subscribed to the mailing list, so please CC any replies to me. Thanks in advance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: not enable to close X server to install latest n-vidia drivers
Thanks, I had the EXACT same problem as the person you responded to on google. I could not close X in debian to install the Nvidea drivers. I issued the command you so kindly provided chvt 1 && /etc/ini.d/gdm stop Now my system wont boot. I hope your just a total moron who just doesn't know shit, cause the Linux community doesn't need malicious dickweeds. Remember, what comes around goes around _ Make the most of your family vacation with tips from the MSN Family Travel Guide! http://dollar.msn.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: not enable to close X server to install latest n-vidia drivers
On Thu, 2004-06-24 at 00:11 +, Jed Clampett wrote: Thanks, I had the EXACT same problem as the person you responded to on google. I could not close X in debian to install the Nvidea drivers. I issued the command you so kindly provided chvt 1 && /etc/ini.d/gdm stop That is the correct way to go about it (though I use CTRL+ALT+F1 myself). Now my system wont boot. Neither of those commands could result in your system not booting. If your nvidia install did not work, X was left broken and you boot to a display manager, then you will have problems, but you should end up at the console eventually and be able to revert your changes to X. Personally I can get the NVIDIA drivers installed fine and use them, hwever on reboot the drivers will not load and I either need to revert to the nv driver or re-install the nvidia driver. I have not bothered to investigate this further but it is annoying. Regards, Tom -- Tom von Schwerdtner <[EMAIL PROTECTED]> Etria, LLP
unsubscribe
Re: acpi_power_off hangs
Hi, Am Montag, 21. Juni 2004 05:39 schrieb Emma Jane Hogbin: > It's very possible you will need to update your BIOS. You should check > over at the ACPI mailing list to see if they have any suggestions. > > http://acpi.sourceforge.net/ > http://lists.sourceforge.net/lists/listinfo/acpi-devel thank's for the hint! I did it already and I have also the newest BIOS and a custom DSDT installed. I am happy with kernel 2.6.5 where everything is working fine, therefor there is not really an important reason to upgrade to 2.6.7 for me. Let's see, maybe the ACPI problem will go away with some of the next kernel versions. Regards, Andreas
Re: Fwd: Re: Going wireless
Hi. I missed the beginning of this thread, but are you sure that the HF (high frequency) part of your WLAN card is enabled and that the HF part of the card is not damaged? If the HF part is not enabled then the driver is namely able to detect the card without problems, but the card itself is not able to send and receive data. On some notebooks you can enable the HF part by keystrokes, on others by software. Regards, Andreas
X window woes on HP pavilion ze4600
Hi, Thanks to those who answered some questions of mine some days ago. I have now tried several variations upon several themes in order to get debian (v. 3.0) on my laptop (HP pavilion ze4600), and had gotten a stable command line version running. I thereupon started X via startx which caused for some reason first a KDE setup dialog to appear (everything freezes) and after a reboot a gnome login dialog (again, everything freezes). I presume that the configuration of X is completely wrong so that I have no ability to use keyboard or touch pad. Is there a boot setting for the debian rescue boot (using a 3.0 DVD) that will prevent X from starting so that I will be able to change the settings of X? Any other ideas? Thanks Peter
Alsa setup broken after upgrade
I have a mixed testing/unstable system running on a HP Omnibook 4150 laptop [sound chipset is cs4232]. Recently, I upgraded a number of things, including gcc (2.95.4 -> 3.3.3), alsa (0.9.4 -> 1.0.5a), and kernel-source (2.4.19 -> 2.4.26). Before the upgrades, I had a working Alsa setup, but now attempts to load the snd-cs4232 module fail with the errors: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_pointer /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_disable /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: unresolved symbol snd_dma_program /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: insmod /lib/modules/2.4.26/alsa/snd-cs4231-lib.o failed /lib/modules/2.4.26/alsa/snd-cs4231-lib.o: insmod snd-cs4232 failed Executing "cat /proc/asound/cards" results in: --- no soundcards --- Also, alsaconf fails to find my hardware. The output of lspci shows that the kernel still sees the sound hardware: :01:00.1 Multimedia audio controller: Neomagic Corporation NM2200 [MagicMedia 256AV Audio] (rev 12) My kernels were custom built using make-kpkg. Sound support was staticly compiled into the kernel, and no OSS modules were selected. Please note also that my previous version of Alsa was after the snd_ prefix was depreciated for module options, so I had already changed my configuration to correct any problems caused by that. ii alsa-base 1.0.5a-1 ALSA sound driver common files ii alsa-modules-2 1.0.5a-1+hpomn Advanced Linux Sound Architecture (drivers) ii alsa-oss 1.0.5-1Advanced Linux Sound Architecture (OSS compa ii alsa-source1.0.5a-1 ALSA sound driver source ii alsa-utils 1.0.5-1Advanced Linux Sound Architecture (utilities ii libasound2 1.0.5-1Advanced Linux Sound Architecture (libraries I would appreciate any help that people can give me with this problem. I'm not subscribed to the mailing list, so please CC any replies to me. Thanks in advance.
Re: Re: not enable to close X server to install latest n-vidia drivers
Thanks, I had the EXACT same problem as the person you responded to on google. I could not close X in debian to install the Nvidea drivers. I issued the command you so kindly provided chvt 1 && /etc/ini.d/gdm stop Now my system wont boot. I hope your just a total moron who just doesn't know shit, cause the Linux community doesn't need malicious dickweeds. Remember, what comes around goes around _ Make the most of your family vacation with tips from the MSN Family Travel Guide! http://dollar.msn.com
Re: Re: not enable to close X server to install latest n-vidia drivers
On Thu, 2004-06-24 at 00:11 +, Jed Clampett wrote: Thanks, I had the EXACT same problem as the person you responded to on google. I could not close X in debian to install the Nvidea drivers. I issued the command you so kindly provided chvt 1 && /etc/ini.d/gdm stop That is the correct way to go about it (though I use CTRL+ALT+F1 myself). Now my system wont boot. Neither of those commands could result in your system not booting. If your nvidia install did not work, X was left broken and you boot to a display manager, then you will have problems, but you should end up at the console eventually and be able to revert your changes to X. Personally I can get the NVIDIA drivers installed fine and use them, hwever on reboot the drivers will not load and I either need to revert to the nv driver or re-install the nvidia driver. I have not bothered to investigate this further but it is annoying. Regards, Tom -- Tom von Schwerdtner <[EMAIL PROTECTED]> Etria, LLP
