BCMA : Unsupported SPROM Revision: 11



  • Bonjour

    J’ai un soucis lors du téléchargement de l’image de mon mac j’ai ce message d’erreur.
    Vous avez une idée ?

    bcma: Unsupported SPROM revision: 11
    bcma: bus0: No SPROM available
    i8042 : No controller found
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
    Kernel Offset: disabled
    ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
    

    ###############
    Hello

    I have a concern when downloading the image of my mac I have this error message .
    You have an idea ?

    bcma: Unsupported SPROM revision: 11
    bcma: bus0: No SPROM available
    i8042 : No controller found
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
    Kernel Offset: disabled
    ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
    


  • Bonjour
    Oui c’est bien FOG 1.2.0 et c’est bien la modification initrd=$imagefile qui à fait fonctionné sur MAC

    #########
    Hy
    Yes it’s good FOG 1.2.0 and it is changing initrd=$imagefile who in fact worked on MAC


  • Senior Developer

    @Tom-Elliott I’m guessing this is while on FOG 1.2.0? initrd=$imagefile is on the current.


  • Senior Developer

    @melvinpaz What modification was made?



  • Bonjour
    C’est bon tout fonctionne avec la modification

    $this->kernel = "kernel $bzImage initrd=$imagefile root=/dev/ram0 ...
    

    C’est parfait encore merci pour tout

    #########
    Hello
    It’s all good works with modification

    $this->kernel = "kernel $bzImage initrd=$imagefile root=/dev/ram0 ...
    

    It’s even perfect for thank you all


  • Developer

    @Junkhacker said:

    @Sebastian-Roth i’m certain there are changes in the way partitions are handled in the init that would be helpful too

    Yeah!! Ultimately you definitely want to go for FOG trunk to have proper Mac support! Quite a few things we changed. Back at my old working place they probably still use FOG 1.2.0 (well a patched version of it) to image Macs. So it’s definitely doable. But installing FOG trunk might be a lot less work compared to fixing 1.2.0 to image Mac clients…


  • Developer

    @Sebastian-Roth i’m certain there are changes in the way partitions are handled in the init that would be helpful too


  • Developer

    Looking at his other post it should be FOG 1.2.0 with an updated kernel I reckon.

    If I remember correctly this is caused on Macs because UEFI systems need the kernel parameter initrd=...! FOG 1.2.0 didn’t have that. I guess you really want to try out FOG trunk at some point. But you can try fixing this by hand as well.

    Edit /var/www/fog/lib/fog/BootMenu.class.php and make line 142 look like this: $this->kernel = "kernel $bzImage initrd=$imagefile root=/dev/ram0 ...

    Possibly there is another fix needed to make it work but I cannot remember right now. Give this a try and let us know.

    PS: I guess you can ignore those ‘‘bcma’’ warnings…


  • Developer

    please provide the version of fog you’re using, as well as the model of mac


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.