New ROM Release – 181114

There’s a new ROM release today. What’s changed? Not very much, hopefully:

  1. Same underlying coreboot build/revision.
  2. Updated SeaBIOS which aside from improved SD/MMC support contains a “keyboard-polling” option, which may (or may not) have an effect for people who’ve been experiencing keyboard issues.
  3. Some slight tweaks to Jeltka, the main of which being the addition of the tg3 driver for the C710, so C710 owners can use Jeltka with a wired connection.

If your current ROM is working well, there’s no need to update, but this release will hopefully help improve things for the people who’ve had niggly problems.

16 thoughts on “New ROM Release – 181114”

  1. I’m not sure where this question belongs, or even if it belongs!, so feel free to move it as needed. (And if you can, let me know where it went :-) .)

    I have an Acer c710-2615 which I flashed with the relevant ROM here. I have LinuxMint17 on usb, and that boots fine. But here’s the problem: I bought a 250GB solid state drive for the drive slot, formatted it with gparted, and installed LinuxMint17 on it. At least when attached as a USB drive, the system doesn’t even see it at boot up. The only option is Jeltka.

    The 250GB SD does work fine to boot other computers.

    Any idea what the problem might be? Searching for an answer only gets me endless links about how to dual boot with chromeOS and similar irrelevant stuff. ChromeOS isn’t I think, anywhere on the system at this point. So I don’t need GPT-formatted partitions do?

    (I was the person a while back having issues making contact across the jumpers so I could reflash my system. I wound up soldering the damn thing. After that it worked….)

  2. I continued putzing and what with one thing and another, tried putting the apparently unrecognizable drive into the drive memory slot inside the computer. Then — hallelujah! — the system could see it!

    It’ll only boot via grub rescue because it somehow has a different UUID in its tiny mind than the actual UUID of the 250GB drive, but once it does boot everything’s fine.

    So I’ll fuss around and see if I can deal with the UUID problem somehow. This is progress!

  3. Yes exactly. I bought a Crucial 250GB M500 solid state drive. It’s 7mm thick (instead of 9mm) so it fits in the space.

    When I had trouble with the install, I took it out and put it into a usb drive enclosure. Partitioned on another computer using gparted and installed linuxmint17 using a live iso. (I also edited /etc/fstab to point to the right UUIDs.) Then I tried to boot the chromebook with the ssd still in its enclosure. (The assumption being that was less wear and tear on the equipment.)

    The Acer c710 only saw the ssd once I moved it back into its regular spot inside the machine.

    I found on this Debian forum the commands that made the grub-rescue permanent:

    After going through the usual grub-rescue list of commands and booting successfully, these commands made the changes permanent:

    su –
    grub-install /dev/sda

    The part I’d missed before was the “grub-mkdevicemap”.

    (Jeltka install over network, by the way, did not work for me. It complained about missing kernel modules for all the OS choices and failed. Maybe that’s because I have this too-old c710.)

    Are there *any* chromebooks out there with decent processors AND high screen resolution AND upgradeable SSDs??

    1. Not yet, no – that’s my holy grail too – a Core i3 or above, with high IPS screen, and hopefully expandable storage (thought the last one isn’t a deal-breaker, using a large USB stick/SD card works okay if it’s decent). Those Baytrail jobbies, although they look nice, are far too slow.

      You’d be helping if you detailed the error message you’re getting in Jeltka, so I can fix it.

  4. Sorry, just checked back.

    I’m terrified of messing up my hard-won working install. I don’t remember the jeltka process clearly enough: does it give me the option to install only to a specific partition? I do have a spare one.

    I also plan on loading the coreboot script onto that machine Real Soon Now. :D

    1. Jeltka simply starts the respective installer – with RedHat derivatives the installer is graphical, with Debian derivatives, not so much. Therefore, you can install to a specific partition/repartition if you choose to.


  5. The continuing adventures…

    I put the original 15GB ChromeOS SSD in and took my new drive out, being a belt-and-suspenders kind of person. The 15GB SSD still had the 12 (?) GPT partitions on it. I started up jeltka and got to the debian install process. After asking the usual install questions about language and mirrors, it gets to Download Installer components and gives this message:

    No kernel modules were found. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive.

    If you’re installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install wil probably fail to work if you continue without kernel modules.

    Continue the install without loading kernel modules?

    I was using a mirror, but couldn’t see where I could choose a different version of Debian. I didn’t try to continue without modules. I did try several different mirrors, but always got the same message.

    Ubuntu gave me the exact same thing, as might be expected.

    Fedora20 seemed to get a lot further, but when it was to the point of formatting the partition (I selected “standard” instead of LVM) it failed and said I could send a bug report to Fedora or a server of my choice. Unfortunately, I couldn’t get either one to work. There was something that went flitting by about failure because it couldn’t communicate with the kernel. The first few lines of the long bug report were complaining about lines it didn’t like in python scripts in a “backup” subdir.

    So, none of this seems very useful. I’ll be glad to try other steps if there’s something else I could try.

  6. I selected from the choices within jeltka. The first one I tried was the default at the top. (I think it was instead of The first one resolves to osuosl on my system if I just type the url into a browser.) Later I tried a couple further down the list. One I remember was

    For the Fedora attempt I just took whatever was the first choice default.

  7. (When I say “within jeltka” I don’t actually know whether maybe the script has handed control to something else at that point. I just mean I’m not aware of having done anything except accepted or rejected the choices as presented.)

    1. I get the same, so something has changed. Can you try continuing without modules?

      On the Fedora/CentOS front, Jelkta copies the squashfs image to a disk partition it creates, so if you try to create a new partition table the installer will fail, as there is a partition in use. Try the Fedora installer again without modifying sda4, and you should find it goes through.

Leave a Reply