I have a Dell branded card and this used to happen to me also. One thing you need to check is that your ifcfg-wlan0 file in /etc/sysconfig/network is properly configured. Yes, it is, as far as I can tell.

If you run the wireless configuration utility in Yast, it will actually fill in all the values for you that you will need in that file. Nevertheless I did this too (again), and the stupid YaST thinks that the

On Wednesday 15 December 2004 21:38, Jake Sallee wrote: prism54 driver is required. It isn't ! This card does not have the prism chip. So, I had to disable the prism54 driver, which certainly will not work.

Also, make sure you disable your eth0 connection before actually turning up your wireless card:

ifdown eth0

I sure did.

then run: modprobe ndiswrapper which will enable your card.

Yes, that works fine, for about 10 minutes. The card is functioning well. And then suddenly the system freezes (again).

If that doesn't work, I would try searching your entire hard drive for *ndiswrapper* and remove any file you find. Then reinstall ndiswrapper from scratch.

Did you download your windows drivers from the known list of drivers on the ndiswrapper sourceforge page or did you download drivers from your manufacturer? I've noticed the drivers they list on sourceforge works better.

Yes, I downloaded the driver via sourceforge (which referred me to the manufacturer, so effectively I downloaded the latest driver from the manufacturer) Bottomline question still : where to look for causes of the freeze - after appr. 10 minutes of good operation ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 16 December 2004 02:26, Richard wrote:

On Wednesday 15 December 2004 04:11 pm, Jan Elders wrote:

...

Bottomline question still : where to look for causes of the freeze - after appr. 10 minutes of good operation ?

Jan, there has been some discussion lately about the powersaved thingie causing some random freezes. As I understand it, it aint needed on anything but laptops, MAYBE!

I uninstalled it on all my machines, including the laptops, and no more freezes the past week. You might give that a try.

OK Richard : I did "disable" powersave with the runlevel editor of YaST and then retried to use the SMC2835W. It started working allright for a few minutes and then ......... the system froze again. So it looks like "powersaved" is not the cause of those freezes, right ? Or would I have to do more than just disable in runlevel editor ? How did you uninstall it ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 17 December 2004 21:54, Joe Morris (NTM) wrote:

Jan Elders wrote:

...

OK Richard : I did "disable" powersave with the runlevel editor of YaST and then retried to use the SMC2835W. It started working allright for a few minutes and then ......... the system froze again. So it looks like "powersaved" is not the cause of those freezes, right ?

Or would I have to do more than just disable in runlevel editor ?

You would also need to Stop it as well. Disable only removes it from the different runlevels, which only affect your next boot (which could be a while ;-) ). Or from a CLI run "rcpowersaved stop". HTH

With all due respect, I disagree. The runlevel editor clearly tells me that it has "stopped" powersaved, and I also get system messages waring me that there is no powersaved (anymore) running on my laptop. So I am pretty convinced that it is stopped. Am I wrong ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Friday 17 December 2004 22:18, Sunny wrote:

On Fri, 17 Dec 2004 22:14:06 +0100, Jan Elders wrote:

...

On Friday 17 December 2004 21:54, Joe Morris (NTM) wrote:

...

Jan Elders wrote:

...

OK Richard : I did "disable" powersave with the runlevel editor of YaST and then retried to use the SMC2835W. It started working allright for a few minutes and then ......... the system froze again. So it looks like "powersaved" is not the cause of those freezes, right ?

Or would I have to do more than just disable in runlevel editor ?

You would also need to Stop it as well. Disable only removes it from the different runlevels, which only affect your next boot (which could be a while ;-) ). Or from a CLI run "rcpowersaved stop". HTH

With all due respect, I disagree. The runlevel editor clearly tells me that it has "stopped" powersaved, //cut

To know the truth :) :

rcpowersaved status

Right ! And it tells me : unused So it is really stopped. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Fri, 17 Dec 2004 13:50:44 -0800, Randall R Schulz wrote:

Sunny,

On Friday 17 December 2004 13:18, Sunny wrote:

...

...

To know the truth :) :

rcpowersaved status

Which must be done as root.

Yes, you are right, forgot to mention this.

I don't know (or remember) what choices I made during installation and configuration of my desktop system, but the reported status is "running".

I do get my monitor to blank after the specified idle time and it turns on just fine when I touch the keyboard or mouse. I have had none of the symptoms others have described.

The monitor is controlled by X. If you have DPMI enabled in XF86config, X will power down the monitor. It is not part of powersaved as far as I know. powersaved is used for more specific tasks like IDE disks spin down, freq. changes on the processor, etc. Of course I may be wrong, but that's how I understand the things, as I do not have powersaved enabled on my machine, and still my monitor shuts down when needed.

Randall Schulz

Cheers Sunny

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85

On Fri, 2004-12-17 at 15:18, Jan Elders wrote:

...

On Thursday 16 December 2004 02:26, Richard wrote:

...

On Wednesday 15 December 2004 04:11 pm, Jan Elders wrote:

...

Bottomline question still : where to look for causes of the freeze - after appr. 10 minutes of good operation ?

Jan, there has been some discussion lately about the powersaved thingie causing some random freezes. As I understand it, it aint needed on anything but laptops, MAYBE!

I uninstalled it on all my machines, including the laptops, and no more freezes the past week. You might give that a try.

OK Richard : I did "disable" powersave with the runlevel editor of YaST and then retried to use the SMC2835W. It started working allright for a few minutes and then ......... the system froze again.

Did you also remember to stop the process from running? Disabling something in runlevel editor in YaST does not shut down the process if it running. Well apparently, it does ! The runlevel editor clearly tells me that it has "stopped" powersaved, and the command "rcpowersaved status" returns : unused So it is really stopped. Cheers, -- Jan Elders

On Friday 17 December 2004 22:19, Ken Schneider wrote: the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Saturday 18 December 2004 03:35, Richard Atcheson wrote:

...

...

...

On Wednesday 15 December 2004 04:11 pm, Jan Elders wrote: Bottomline question still : where to look for causes of the freeze - after appr. 10 minutes of good operation ? Jan, I made sure it wasnt working by uninstalling the thing via YAST. OK Richard, thanks. That's what I now also did, powersave is now completely removed from the system.

I have since been reading more about the powersaved and it warns you that you must not have apm or acpi daemons running while powersave is going. You can verify they are off by doing a: chkconfig apmd chkconfig acpid Both commands return : unknown service So, there cannot be a conflict with these. :-) Subsequently I start ndiswrapper, and insert the SMC2835W card. All is working fine ........... for about 10 minutes and then the system freezes again. Sigh !

BTW, I'm running the same kernel you are with ndiswrapper on one laptop and driverloader on the other and both are working fine.. Ehhh, which same kernel ? 2.6.5-7.111.5-default or 2.6.9 ?

Have you tried the driverloader from linuxant? I had to go to it for my dell after an upgrade screwed up the nidswrapper stuff. I have a compaq that the ndiswrapper works fine on. Same type of chipset though. Yes I have also tried driverloader with exactly the same results : it works fine for a while and then the system freezes.

I wonder if there would be a buffer somewhere that is filling up, or a timer that expires ?????? The freeze usually happens after about 10 minutes. Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Thursday 16 December 2004 06:19, Osho GG wrote:

On Wednesday 15 December 2004 12:20 pm, Jan Elders wrote:

...

Hello,

Some time ago, I installed Ndiswrapper 0.12 on my SuSE 2.6.5-7.111.5-default in order to get my new SMC 2835W wireless LAN card working. (Ndiswrapper is needed because this version of the 2835W uses a Frisbee chip, for which there are no Linux drivers yet)

That worked fine .... for a few minutes and then my system "froze". I could not think of a particular reason for that to happen, but I suspected that maybe something was wrong in my kernel. So, I decided to install the latest 2.6.9 kernel from kernel.org. That went well and I could work with the card via ndiswrapper ....... for a while, after which also the 2.6.9 system "froze".

I am totally lost where to look for causes / clues. I don't see anything peculiar in my /var/log/messages, but maybe I'm overlooking something ?

Any ideas ?

I had some other issues with 2.6.5-7.111.5-default that was supplied by SuSE for SuSE 9.1 Professional. To get rid of these issues, I compiled and installed my own 2.6.8.1 and then 2.6.9 kernels. What I found was that it did fix some of these issues but created others.

I then switched to kernel-of-the-day apt repositories' 2.6.8 kernel compiled for SuSE 9.1 and all my issues disappeared :).

I haven't tried using ndiswrapper so YMMV but installing kernel from kernel-of-the-day apt repository is something worth a try.

Hmm, so I will first have to prepare my system for using "apt", before being able to do this, right ? That will be another, new, road to follow for me. I'll try to do this, hoping that I will not get more problems on top of the ones that I am already having (such as the "freeze", being the subject of this thread). Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"

On Sunday 19 December 2004 19:40, Carlos E. R. wrote:

The Wednesday 2004-12-15 at 21:20 +0100, Jan Elders wrote:

...

I am totally lost where to look for causes / clues. I don't see anything peculiar in my /var/log/messages, but maybe I'm overlooking something ?

Correct file would be /var/log/kernel, which you might have to enable first in /etc/syslog.conf.

Ehh Carlos, There is no /var/log/kernel file and there is no such entry in my /etc/syslog.conf (SuSE 9.2) Does that mean something is wrong ? Cheers, -- Jan Elders the Netherlands http://www.xs4all.nl/~jrme/ "Home of the Network Acronyms"