*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
The bug task for the somerville project has been removed by an automated
script. This bug has been cloned on that project and is available here:
https://bugs.launchpad.net/bugs/1305821
** No longer affects:
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
** No longer affects: dell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/271024
Title:
RTNL: assertion faile
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
My apologizes... good work! =)
--
RTNL: assertion failed when modprobing 'wl'
https://bugs.launchpad.net/bugs/271024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
@Pablo - it really is a duplicate. The root issue is that a fix was
added in Hardy 2.6.24 to set the VLAN mode default to 0 so that normal
ssh/ssl traffic worked. The fix was forward ported to Intrepid 2.6.27
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
I'm sorry if I'm wrong.
I wanted to say that both bugs don't seem to be the same: error messages are
different.
--
RTNL: assertion failed when modprobing 'wl'
https://bugs.launchpad.net/bugs/271024
You rece
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
Marking a bug as duplicate doesn't (have to) mean it's fixed. As you can
see in the other bug's comments (from me, for example), the bug is still
open. "Fix Committed" is not the same as "Solved".
--
RTNL: a
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
Tim, have you checked it before marking as duplicate?
Last week I installed xubuntu and It hadn't been solved yet so I don't think
it's a duplicate.
--
RTNL: assertion failed when modprobing 'wl'
https://bu
*** This bug is a duplicate of bug 252630 ***
https://bugs.launchpad.net/bugs/252630
** This bug has been marked a duplicate of bug 252630
'wl' driver is broken in lrm 2.6.24.14-20.46
--
RTNL: assertion failed when modprobing 'wl'
https://bugs.launchpad.net/bugs/271024
You received this b
I have blacklisted ssb from initrd and my dmesg is now similar to theirs.
Network is working anyway.
--
RTNL: assertion failed when modprobing 'wl'
https://bugs.launchpad.net/bugs/271024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I think my case is similar.
It happens when I do modprobe -r ssb; modprobe -r wl; modprobe wl; (Note that I
did it several times in the attached log).
But my dmesg output is shorter.
Also fully updated intrepid 18 sept.
** Attachment added: "murdok_dmesg.txt"
http://launchpadlibrarian.net/17
Same bug here using a fully updated intrepid install as of Sept 18:
This is on a Latitude E6400.
Linux version 2.6.27-3-generic
I have the same bug log (as part of dmesg).
** Attachment added: "dmesg"
http://launchpadlibrarian.net/17717403/dmesg
--
RTNL: assertion failed when modprobing 'wl'
** Attachment added: "wl_output.txt"
http://launchpadlibrarian.net/17663362/wl_output.txt
** Also affects: dell
Importance: Undecided
Status: New
--
RTNL: assertion failed when modprobing 'wl'
https://bugs.launchpad.net/bugs/271024
You received this bug notification because you are
12 matches
Mail list logo
