[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194523
moa, thank you for reporting this and helping make Ubuntu better. Hardy
desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue on a supported release? If
so, can you
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194523
Title:
computer frozen
To manage notifications about this bug go to:
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm the bug. It is caused by some combination of modules b43,
rfkill, rfkill_input. I have observed the problem in 2.6.25 kernel image
available in repositories as well as unofficial 2.6.27 kernel image
created by Michael Casadevall (NCommander/sonicmctails). I remember
seeing this
In my case, the problem was also present when not using b43. since then i only
use ndiswrapper with the windows driver working much better than the free
driver. I never tried to look at rfkill* modules
However, in my case, this is a probem occuring in all operating systems
(knoppix,
@moa,
Do you have any powerpc machine around where you can check if the
problem is present on 2.5.25 or greater kernel versions. It is possible
that it is fixed for 386 but not for powerpc.
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because
Actually i think the problem is not even present on i386...
I only had this problem on my AMD64 Turion PC, not on my i386 one.
Maybe the problem on AMD64 was fixed and it is now present on powerPC?
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification
kernel version: 2.6.24-12-generic.
I'm not using ndiswrapper, rather using the b43 driver.
I'll check if this occurs with ndiswrapper kernel 2.6.22.
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hardy Beta (with all latest updates) on my Compaq v3000 seems to have this
problem. So you are not alone!
The laptop randomly freezes mostly resulting in a hard reboot. But recently i
just switched off the wireless antenaa and after a few minutes it starts
responding! I have been able to
Ok, that's good.
Actually i have noticed after a few days of using kernel 2.6.22 i was
not able to reproduce the freeze.
Comming back to the last kernel 2.6.24 is causing the problem to come
back.
I am using ndiswrapper, and don't know if it's related to it or not, but
one think is sure:
I have observed a few facts:
* the freeze happends more offten when i use compiz play a game or watch a
video (this is true even when using nvidia driver without compiz)
* when the freeze hapeneds, if i reboot my computer, some times it will
continue to hapend after only a few minutes
* once
I have installed ndiswrapper instead of b43 and ssb... My computer still
freezes.
Conclusion: it is not a problem of b43 or of nvidia. Since i have done
no other change, it is surely a problem caused by the upgrade from
Feisty to Hardy, most probably the kernel itself or a new module in the
I've done a one pass memory test, no errors.
I've uninstalled yesterday nvidia and used nv driver with metacity and
without compiz since. It behaved ok yesterday but today i had a freeze
right a few minutes after i started my laptop.
I had also a problem with the wifi card: it was working only
Using no encription and the nv driver i got a system freeze
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have an intuition it might be related to the buggy nvidia-glx-new
drivers. I'll try to investigate this in the next days for
confirmation...
Same bug as???
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/176589
nvidia-glc-new 169.12 for Linux x86/x86-64 released (not yet in ubuntu)!
I've installed the latest nvidia driver and it did NOT solved the
problem. Now i am back to nvidia-glx-new from ubuntu
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
UPDATE:
I've noticed in the last few weeks that some times when the computer was
frozen, when pressing the power off button for about 5 secconds, right
one second before hard shuting down the system responded.
Since i've tried not to shut it down and i noticed that rarely the
system gets back
You should _uninstall_ the compat-linux-wireless drivers, not reinstall
them. Please get rid of these drivers before you do anything else.
Hardy kernel already includes the b43 and b43legacy drivers, there is no need
for recompiling them from the package prepared by linuxwireless.org. The
Actually i have installed the version 011 of b43-fwcutter, not the driver. I
don't remember having installed any compat-linux-wireless driver. Now i have
erased all firmware files from /var/firmware/b43* Then i have installed
b43-fwcutter official package (version 008 it says) and extracted
Actually i have installed the version 011 of b43-fwcutter [...]
What do you mean exactly by _uninstall_ the compat-linux-wireless driver?
Ok, in that case it's a misunderstanding. When I asked you if you did
install the driver from linuxwireless.org I thought about the kernel-
driver (that is
Yes, my card works now as well as it was working with the firmwares
b43-fwcutter version 11 from the web site despite the _rename.
On the other hand, i observed that this system freeze happends more
offten when i play the game openttd (using 2D acceletation) than whe
just using firefox
Other changes i made is installing the b43 proprietary driver for my
wifi card (instead of the old ndiswrapper driver) - i do'nt know if it is
because of this driver or not.
http://linuxwireless.org/en/users/Drivers/b43
What did you exactly do? Did you try to compile the driver for yourself
Yes, i compiled the latest version for myself. I'll install the
b43-fwcutter package now to see the diference.
I've put noacpi noapic to the kernel and it still frozes. I've installed
the latest kernel update and recent updates and it still do the same but
with a diference: i think it is less
I have reinstalled b43-fwcutter and still have the wlan0_rename. Should
i reinstall the b43 driver also?
--
computer frozen
https://bugs.launchpad.net/bugs/194523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
ifconfig:
wlan0_rename Link encap:Ethernet HWaddr 00:14:a5:f9:95:53
inet adr:192.168.1.20 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::214:a5ff:fef9:9553/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:9605
26 matches
Mail list logo
