Activity log for bug #123718

Date Who What changed Old value New value Message
2007-07-03 09:45:13 Bogdan Ionita bug added bug
2007-07-05 17:26:27 Paul Dufresne None: status New Incomplete
2007-07-05 17:26:27 Paul Dufresne None: assignee dufresnep
2007-07-05 17:26:27 Paul Dufresne None: statusexplanation Hi, I work as a bug triager to make sure the bug is complete enough for knowing what need to be change. Thanks for your bug report, but some more information would be needed to figure out what is going wrong. Which version (7.04? Gutsy? Older?) Ubuntu, Kubuntu? x86? 32 or 64 bits? Well, do you kept it inside the computer? So sometimes it boot with it. Good, we could use it. If you get it to not boot, then next to boot, please attach /var/log/dmesg.0 to this bug. /var/log/dmesg is what happened this time when you booted (should have no errors since it worked) and /var/log/dmesg.0 should be what happened last time you booted (I hope it will show what was the error). An other thing to try first would be to boot in recovery mode (when booting, look for the good moment to press ESC, in the menu, you should see kernel... (recovery mode), booting with this option should boot up to a mode where you can do everything on the computer without protection (# prompt rather than $). The nice things is that all messages appear while booting, so this let you observe on what it is blocking. Take some note on a paper if you are lucky enough to freeze on a line. To quit this # console mode just type reboot or: exit at the # prompt. Now if you are able to boot in graphical mode with the card inside. Go in a console window (one way is Ctrl-Alt-F2, and Ctrl-Alt-F7 to return in graphical mode), and in the console type: sudo lshw -businfo if that works fine do: sudo lshw -businfo > lshw.txt That would create a lshw.txt file with the info you saw earlier in your home directory. Please attach this file to this bug.
2007-11-15 18:39:54 Paul Dufresne None: status Incomplete Invalid