Install help on Lenovo Yoga 300-11IBY
ian at dijix.com
Fri Sep 8 10:57:36 PDT 2017
Thank you Matt, adding the sdhci_acpi.ko module fixed it for me.
For the benefit of others who may not have done this before these are the steps I had to take to get my fresh 4.8 install to boot on a Lenovo Yoga 300 11iBY
It’s an Atom powered netbook with 32Gb MMC ‘SSD’ drive.
After install the machine will reboot and you are presented with the DragonFly boot screen.
Press ESC to stop the countdown.
You’ll see the OK prompt, it’s here we need to load a few kernel modules so the internal drive can be recognised.
Type the following in this order
You may need to load more modules for your machine.
When you’re done loading modules type:
Which will then boot the system
Which will boot the system, and show you more detailed messages which may help with troubleshooting.
I’m now up and running and DF is fast on this little laptop!
As Matt and the docs mention if you’re using Hammer FS it’s important to prune data frequently on smaller drives like these as Hammer will store backups and may fill your drive up quickly.
> On 6 Sep 2017, at 19:06, Matthew Dillon <dillon at backplane.com> wrote:
> You probably need the sdhci_acpi.ko module. Make sure you have sdhci and sdhci_acpi in there too.
> On Tue, Sep 5, 2017 at 5:10 AM, Ian <ian at dijix.com <mailto:ian at dijix.com>> wrote:
> I’m just getting to grips with DragonFly BSD, I’ve installed it ok on one laptop, which is great apart from ACPI S3 sleep.
> I’m trying to install it on another laptop, a cheap Yoga with a 32GB MMC as the internal disc.
> It installs fine, there’s no warnings similar to Dmitry Postolovs issues earlier however once installed the machine won’t boot to the login prompt.
> I accepted the default partition layout e.g.:
> /boot 1024M
> Swap ~2Gb
> / * the rest
> It boots from the MMC ok, I press 1 to Boot DragonFly Kernel, then boot proceeds as normal.
> After USB device discovery the boot process halts with this message:
> No B_DEVMAGIC (bootdev=0)
> Mounting root from hammer:mmcdsd0s1d
> No disk named `mmcdsd0s1d`
> hammer_vfs_mount: can’t find devvp
> hammer_vfs_mount: No root volume found!
> Root mount failed: 22
> Then I’m presented with mount root which lists various devices but not the mmcsd device
> Typing hammer:[device name]
> Fails as these are not proper devices.
> If I boot from the USB installer I can mount the mmcsd device and see the filesystem and everything seems okay.
> I have tried loading the mmc and mmcdd modules before boot, but they appear to be loaded automatically (or built into the kernel)
> Obviously the device is recognised as it is booting from the /boot partition, however when it comes time to mount the main partition the device is no longer recognised.
> Any pointers would be appreciated.
> Are there any magic flags that need to be set on the / partition.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users