Gutsy Alternate Macbook Santa Rosa - No installable kernel found

Bug #133349 reported by MightyE on 2007-08-18
6
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Doing a clean install on Macbook Pro rev.3 (santa rosa), with the most recent alternate daily build, I get, "No installable kernel was found in the defined apt sources"

I'm new to this bleeding edge stuff, but going to a command line, I am unable to install linux-image-generic manually, nor am I able to install linux-image-`uname -r`-generic

I will attach my lspci and my /proc/cpuinfo

MightyE (mightye) wrote :

I'm sorry, apparently I saved those to my ramdisk and not my fixed disk as I intended. I'm not even sure if they are significant in this case, please let me know if they are and I will go back into the installer and get them (as I formatted the Feisty partition, so it is no longer bootable into Linux). I'd like to let this cool off for now though because both it and my power supply got VERY HOT during the install process (uncomfortable to touch, I did not hear the fans spinning as fast as I suspect they should have)

I have had exactly this problem with a white box Intel P4 system. I was using the 2007-08-19 Kubuntu alternate daily CD.

I have run every version of Kubuntu on this system since Breezy; I typically upgrade to new versions late in the alpha development process.

I have attached a tarball of the debug logs made by the installer.

Jean-Baptiste Lallement (jibel) wrote :

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.

MightyE (mightye) wrote :

Thanks for following up Jean-Baptiste; I assumed this was closed a long time ago. I'm not comfortable attempting this install on my Santa Rosa macbook at the moment.

This was reported against a daily build for 7.10; my guess is that it's safe to close this ticket as it's either been reported against a more recent build by someone else, has been resolved, or is a corner case exclusive to me.

Jean-Baptiste Lallement (jibel) wrote :

I'm closing this report due to your last comment.

Thank you for your time.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers