I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
As previously mentioned, this doesn't seem to be a ubiquity bug at all,
since the system doesn't actually get as far as trying to run the
installer, so I'm marking that task invalid. I hope somebody else can
help to narrow down what's going on.
** Changed in: ubiquity (Ubuntu)
Status: New =
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I concur with Aleksey1977, I am using an Averatec 3200, Broadcom
chipset, same exact problem, can login via command line, but startx is a
no go. 32 Bit 8.04 beta is used here. So it is safe to say confirmed by
another Averatec owner.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no f
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
Ubuntu Gutsy releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
Ubuntu Heron releases today and the exact error remains, unchanged and
intact - the b43-phy0 loop error sage continues. Would really appreciate
a work-a-round.
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug
** Summary changed:
- hardy install alpha5 loops: broadcom: no firmware file
+ [fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
--
[fixed in alpha6] hardy install alpha5 loops: broadcom: no firmware file
https://bugs.launchpad.net/bugs/188282
You received this bug notific
I can confirm that I am now getting past this problem (the endless error
message looping preventing the GUI from coming-up) in alpha 6 (the desktop AM64
version was what I tested on) using the live boot CD mode.
I think I still saw the error message, but it didn't keep repeating as before,
so I
I'm not sure what the bug is here (since there are multiple comments
with possibly unrelated symptoms), but it doesn't appear to be an issue
with wireless-tools since wireless-tools are only the userspace tools
used for managing the wireless devices - they're not involved with
firmware loading at a
48 matches
Mail list logo
