I can confirm that installation of kernel 2.6.27-7.11 solved the bug
#275227 in my case.
covox: Do you experience hangs each time you trying to boot? Do you get the
same error message as reported here:
...
[ 161.964196] kernel BUG at
/build/buildd/linux-2.6.27/net/mac80211/ieee80211_i.h:764!
[ 1
Loïc : I have installed the kernel from your ppa and it solved my issue.
I can modprobe iwl3945. It works and doesn't produce an error message.
Unfortunately, now I experience
https://bugs.launchpad.net/intellinuxwireless/+bug/263059 . I did
several reboots and I got a hang 2 times.
--
[Regress
... sorry, I didn't notice that i386 and AMD64 are OK. Only "lpia"
failed to build - whatever it is.
--
[Regression] iwl3945 module always crashes on load and hangs boot process
https://bugs.launchpad.net/bugs/275227
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Loïc : It seems that your package failed to build. Could you check it?
--
[Regression] iwl3945 module always crashes on load and hangs boot process
https://bugs.launchpad.net/bugs/275227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- [Regression] iwl3945 module crashes on load and hangs boot process
+ [Regression] iwl3945 module always crashes on load and hangs boot process
--
[Regression] iwl3945 module always crashes on load and hangs boot process
https://bugs.launchpad.net/bugs/275227
You received th
I have reported the issue at kernel.org -
http://bugzilla.kernel.org/show_bug.cgi?id=11746 .
It seems that patch is already prepared. Unfortunately, it is not
incorporated into the intrepid kernel. I can confirm that the issue
persist in the 2.6.27-7.
** Description changed:
Kubuntu Intrepid u
Sebastian: No problem. I have also originally reported my problem in
this thread. I decided to fill in a new bug because my system have never
finished boot process if the driver wasn't blacklisted. However there
are many similarities to the situation reported in this thread.
I think it can be usef
I have a similar issue but in my case iwl3945 _always_ crashes on load.
Please, look at the description of bug #275227 (marked as a duplicated
of this one). Do you get the same error message in your dmesg output? I
am curious is this really the same or just related problem. I have also
reported i
** Description changed:
Kubuntu Intrepid updated daily + Asus V6J
The boot process always permanently hangs on "Configuring network
- interfaces" when started with kernels from 2.6.27-3 / 2.6.27-4 but It
- works with my hardy kernel 2.6.24-19-generic.
+ interfaces" when started with kernels
** Attachment added: "dmesg"
http://launchpadlibrarian.net/18004353/iwl3945_error
--
[Regression] iwl3945 module crashes on load and hangs boot process
https://bugs.launchpad.net/bugs/275227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Kubuntu Intrepid updated daily + Asus V6J
The boot process always permanently hangs on "Configuring network
interfaces" when started with kernels from 2.6.27-3 / 2.6.27-4 but It
works with my hardy kernel 2.6.24-19-generic.
The system boots with 2.6.27 kernels only when the
2.6.27-4 fails to boot too. In my case it _always_ hangs on iwl3945
driver activation. Maybe this bug should have more general title i.e:
"2.6.27-3 - boot freezes when the iwl3945 is being loaded"
--
[regression] 2.6.27-3 fails to boot on Dell XPS M1710
https://bugs.launchpad.net/bugs/263059
You
I can confirm the same problem on Asus V6J (nvidia + iwl3945). System
always hanging on "Starting Network Interfaces" when booted from
2.6.27-3. When started with 2.6.24-19-generic kernel it works properly.
When wireless card is turned off (using BIOS settings) system boot
process goes further and
The same dmsg output for iwl3945 on Kubunty Hardy Alpha 3 . The wireless
card does not work with the new driver.
--
iwlwifi-4965-1.ucode firmware file req failed: Reason -2
https://bugs.launchpad.net/bugs/179488
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The same problem as described by Eythian makes networkmanager-openvpn
unusable to me. I cross my fingers for 'pull' support that should be
really useful.
Thank you Soren!
--
[Feisty] NetworkManager OpenVPN doesn't have a pull option
https://bugs.launchpad.net/bugs/88069
You received this bug not
Same on my ASUS V6J (Intel T2400 + Nvidia 7400) Feisty with nvidia-glx.
Supends witout any problem. After resume Wifi does not work. Than on
reboot computer hang before restart. After next start I get this crash
report .
--
[apport] vbetool crashed with signal 5
https://bugs.launchpad.net/bugs/83
Public bug reported:
Binary package hint: pymol
PyMol prints an error message when starts with multiple input files
(i.e. "pymol .pdb .pdb" or "pymol *.pdb" in dir with multiple
pdb files):
Error: Argument processing aborted due to exception.
Then only first provided file is loaded to P
Public bug reported:
Binary package hint: pymol
It is similar to the bug nr 71045 but in Feisty the default paths have
been changed. Unfortunately they are still invalid. When one tries to
align any 2 structures pymol raises an exception:
PyMOL>align obj02, 2.50-A-1N1M
Match-Error: unable to op
Public bug reported:
Binary package hint: update-manager
Traceback (most recent call last):
File "/tmp/kde-root/adept_updatervf75ka.tmp-extract/dist-upgrade.py", line
48, in ?
app.run()
File "/tmp/kde-root/adept_updatervf75ka.tmp-extract/DistUpgradeControler.py",
line 839, in run
se
Public bug reported:
Binary package hint: pymol
Default start script (/usr/bin/pymol) calls python interpreter using
wrong version notation - python2.4.4 instead of python2.4. Look below:
{{{
#!/bin/sh
# debian wrapper script for pymol
export PYMOL_DATA=/usr/share/pymol
export PYMOL_PATH=/usr/l
Public bug reported:
Binary package hint: pymol
Default start script (/usr/bin/pymol) calls python interpreter using
wrong version notation - python2.4.4 instead of python2.4. Look below:
#!/bin/sh
# debian wrapper script for pymol
export PYMOL_DATA=/usr/share/pymol
export PYMOL_PATH=/usr/lib/p
21 matches
Mail list logo
