We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
No hardware
bytesmythe,
I'm inclined to agree. I think you may have two separate bugs here. I
thought the hanging update manager window might be bug 186465 but your
main.log looks different so I'm not sure what's causing it to hang.
For the sake of information with regard to the hardware detection what
Richard,
The laptop has the following ethernet controllers:
Wired: Realtek Semiconductor Co., Ltd. RTL8101 PCI Express Fast Ethernet
controller (rev 02)
Wireless: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Still, the network card isn't the only thing it fails to
This is from dist-upgrade/main.log
===
2008-04-23 23:27:41,782 INFO release-upgrader version '0.87.24' started
2008-04-23 23:27:42,136 DEBUG Using 'DistUpgradeViewGtk' view
2008-04-23 23:27:42,193 DEBUG enable dpkg --force-overwrite
2008-04-23 23:27:42,270 DEBUG lsb-release:
bytesmythe
update-manager puts it's log files into /var/log/dist-upgrade. So all
the files from there would be useful. I think the installer logs to
/var/log/syslog but Colin would know for certain
--
No hardware detected on Toshiba Satellite
https://bugs.launchpad.net/bugs/220017
You received
Rejecting the ubiquity task; this bug report is apparently about the
alternate install CD, not the desktop CD.
I don't suppose there's any way to get some log files here? Is it
possible to switch virtual terminals after the installer hangs? I'd like
to know whether this is a kernel-level hang (if
Milan: for the record, hw-detect was a perfectly reasonable place for
the original report, as the d-i component responsible for hardware
detection. The bug should have been left there, so I've put it back.
(Creating an update-manager task was fine, though.)
--
No hardware detected on Toshiba
Colin,
Do you mean log files from the boot CD installer or the update-manager
installer? I should definitely be able to come up with something from
the update-manager one. Are there any logs in particular that would be
helpful? (Note: this laptop isn't mine, so I won't have access to it
for
Thanks for reporting bugs. What do you mean by main hardware detection
process? How is your computer connected to the network? Did the
installer or the upgrader manage to reach the internet?
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
I'm not sure what else to call it other than main hardware detection.
The first thing it tries to detect is network hardware, which fails.
Then a bit later, it tries to detect all the hardware, which results in
the system hanging.
There is no network connection at all when booting from the Hardy
11 matches
Mail list logo
