** Changed in: linux (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Title:
Network Does Not Start Using be2net Driver on Lucid
--
ubuntu-bugs mailing
Thanks for the feedback, Tim.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Title:
Network Does Not Start Using be2net Driver on Lucid
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Joseph - The 10.04.2 DVD has the Maverick kernel version as a boot and
install option. The magnitude and number of changes required to update
the Lucid in-kernel driver do not meet SRU requirements. Those appear to
be your choices.
--
You received this bug notification because you are a member of
@Tim
This may not be the best solution since all of the servers affected by
this live in a data center, in another building. PXE is used to boot
and install Ubuntu over the network. Its not feasible to have people
going to remote labs with other ethernet devices to plug into the blade
chassis ev
** Tags added: kj-triage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Title:
Network Does Not Start Using be2net Driver on Lucid
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
It looks like the 2.6.32 driver simply doesn't support this new
BladeEngine hardware. Would it be sufficient if I provided a linux-
backports-module package that could be installed after the fact? The
user would have to initially install using a USB ethernet dongle, but
could then get native ethern
@Tim, we also tried an install using the proposed 10.04.2 point release
at http://cdimage.ubuntu.com/lucid/daily/current. However, this has the
same issue.
Are there any other suggestions we may want to try?
Thanks,
Joe
--
You received this bug notification because you are a member of Ubuntu
@Tim, we tried a boot with pci=nomsi. However, there was no change,
still the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Title:
Network Does Not Start Using be2net Driver on L
Thanks, Tim. We will try booting with pci=nomsi and update the bug with
the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Title:
Network Does Not Start Using be2net Driver on Lucid
I'm seeing some ACPI errors during the be2net startup which suggests MSI
routing might be an issue. Can you boot the kernel with 'pci=nomsi' ?
Otherwise it looks like eth0 and eth1 found a link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
lspci output
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717388/+attachment/1843894/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
dmesg output
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717388/+attachment/1843893/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717388
Output from apport-bug
** Attachment added: "apport-bug-output-717388"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717388/+attachment/1843892/+files/apport-bug-output-717388
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo
