Greetings,

I'm running suse 10.0 on a sony vaio(vgn-b55g, pentium m 1.5ghz-centrino, 768mb ram), kernel version 2.6.13-15.7-default. Recently (since the past few days) my computer has started freezing randomly. Bios functions seem to work still, but everything else just goes dead (screen,mouse, network,hard disk read/write, etc freezes completely). There doesn't seem to be any sort of indication/cause of the hang. The cpu and ram usage is normal (no jump to 100% before freeze, etc), and frequency scaling works as normal. Bios/acpi works ok, the fans n stuff come on/change speed as they should, i monitored temperatures, also normal. I haven't made any major changes like kernel stuff,etc. Anyone have ideas?

p.s. i've looked on the forum for similar questions, but didn't find any that might've solved this. If there is, my apologies, and i'd appreciate it if you could point me there. Thanks.

Hi

Not sure if I can help but are u using ndiswrapper. I'm having the same problem since trying to get my wireless working with suse 10,0. I have a thread on the matter under networking >> wireless

Negative on ndiswrapper, i'm using ipw2200. However it does seem to be related somewhat to the wireless connection. I've upgraded my access point from 802.11b to g, and the problem seemed to start after that. I reinstalled suse 10, hoping that might fix it, but no luck. That would suggest a hardware issue, but then it works perfectly fine on ms windows xp. I set the access point back to 802.11b, and so far it's been working(praying hard). Interestingly, it seems to hang when 1)the maximum bandwidth of the connection is used, or 2)there are many simultaneous connections. I'll try to find out more, and post back here. Hope this thing doesn't go on too long though, i love my computer very much and i hate using the power switch:-(

Edit: btw it's nothing wrong with the stock suse 10 distribution, i've been using that for quite a while now without problems. If it's the software then it has to be something from the updates, or related to my network infrastructure.

Got it. I went back to 802.11b, and manually set the card to 11Mbps, and it's been running fine for 2 days now. Something to do with the driver, perhaps? Or, this may sousd a bit farfetched, is it possible that my particular model of access point (d-link) sends out a certain type of packet that the driver doesn't like? Anyway, i'll be surprised if it is in fact the driver, i always thought it was fine with 802.11g as well. Should i change the topic to include 'solved'? If so how? Probably didn't belong here in the first place, but i didn't know what problem it was...i'll read up some more on this driver, hopefully i'l have more to add here. Cheers.