Christopher M. Penalver, problem update, a day later: (a) I was able to get back to the boot capability to boot into my trusted old FC3 installation. I had to do a "sudo update-grub" from the new installation (13.10). The only way I could do it by Ctr-Alt-F1 switching into terminal. The gui desktop was useless. Apparently the aborted installation changed but not finished MBR. Grub now looks at the new installation. When I did the sudo grub-update from the 13.04 boot it did recognize the FC3 installation, but it looks like grub from MBR now reads the cfg from the 13.10 installation. Anyway, I'm glad that at least I'm back to square one.
(b) Also, from 13.10 terminal mode I did a "uname -a", see attached. This is to tell what kernel was installed. Let me know how to proceed, and thanks. Janos ** Attachment added: "uname -a from test installation (13.10)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+attachment/3830672/+files/JanosSaucySalamanderUnamea -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: 03f0:1205 Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
