Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Partitioning on a chromebook
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Fri Oct 07, 2016 10:11 pm    Post subject: Partitioning on a chromebook Reply with quote

Hello all, I'm just starting an install of gentoo on my chromebook, with the intention to completely remove chromeos - hence the reason I can't use premade partitioning scripts.
The current partitioning scheme is pretty confusing, and I want to completely clear the 32GB SSD of all previous partitions and just leave an empty disk - how should I go about doing this?
Output of lsblk:
Code:
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    1  960M  0 disk
└─sda1         8:1    1  959M  0 part /run/archiso/bootmnt
loop0          7:0    0  328M  1 loop /run/archiso/sfs/airootfs
mmcblk0rpmb  179:24   0    4M  0 disk
mmcblk0boot0 179:8    0    4M  1 disk
mmcblk0boot1 179:16   0    4M  1 disk
mmcblk0      179:0    0 29.1G  0 disk
├─mmcblk0p1  179:1    0   25G  0 part
├─mmcblk0p2  179:2    0   16M  0 part
├─mmcblk0p3  179:3    0    2G  0 part
├─mmcblk0p4  179:4    0   16M  0 part
├─mmcblk0p5  179:5    0    2G  0 part
├─mmcblk0p6  179:6    0  512B  0 part
├─mmcblk0p7  179:7    0  512B  0 part
├─mmcblk0p8  259:0    0   16M  0 part
├─mmcblk0p9  259:1    0  512B  0 part
├─mmcblk0p10 259:2    0  512B  0 part
├─mmcblk0p11 259:3    0    8M  0 part
└─mmcblk0p12 259:4    0   16M  0 part

From the output above, I believe the SSD must be mmcblk0, and sda is my arch usb - but mmcblk0rpmb, mmcblk0boot0, and mmcblk0boot1 are completely foreign to me. I know I should delete the partitions of mmcblk0 and use it for my /boot, swap and / partitions - but I'm not sure about the other three mmc partitions. Does anyone have any idea what they could be used for, or if they could impact my gentoo install or its booting?
Thanks.
Back to top
View user's profile Send private message
heiwa
n00b
n00b


Joined: 24 Oct 2012
Posts: 70

PostPosted: Fri Oct 07, 2016 10:45 pm    Post subject: Reply with quote

Please have a careful look at http://www.chromium.org/chromium-os/chromiumos-design-docs/disk-format

You are very free in the partition layout. But be sure to read the
section on Secure Boot carefully to avoid getting the Chromebook into
an unbootable state.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sat Oct 08, 2016 4:32 pm    Post subject: Reply with quote

I decided to go ahead and wipe the partitions on mmcblk0, since they didn't seem to play a role for anything other than chromeos.
I noticed that there was an efi partition, but decided to install gentoo without efi support, as I noticed that seabios was booting my arch usb without uefi.
I continued a standard gentoo install, but on booting, I got the following kernel panic:
Code:
VFS: Cannot open root device "mmcblk0p3" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I had a similar message on my main machine a short while ago, but configuring grub to not use UUIDs didn't fix this panic.
My fstab file references dev files - mmcblk0p1 for boot, mmcblk0p2 for swap, and mmcblk0p3 for root.
Any ideas on how to fix this?
Note that I can't access grub just before the kernel boots, as the grub menu doesn't actually display - it only prints a welcome message - so any fixes would have to involve chrooting in.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sat Oct 08, 2016 8:18 pm    Post subject: Reply with quote

Bladesy,

unknown-block(0,0) usually indicates that the there is a bit missing from the kernel.

It could also be that the kernel is too fast trying to mount root and the /dev entry does not yet exist.
Its down to your kernel, kernel command line and initrd if any. Noting else can be read until root is mounted.

Is your SSD really an NVMe device?

Pastebin your
Code:
lspci -k
and your kernel .config
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sat Oct 08, 2016 11:19 pm    Post subject: Reply with quote

lspci -k output:
Code:
00:00.0 Host bridge: Intel Corporation Device 2280 (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i915
        Kernel modules: i915
00:0b.0 Signal processing controller: Intel Corporation Device 22dc (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: proc_thermal
        Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:1b.0 Audio device: Intel Corporation Device 2284 (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 35)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 35)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 35)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: lpc_ich
        Kernel modules: lpc_ich
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
        Subsystem: Intel Corporation Dual Band Wireless-AC 7265
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

Kernel .config: http://pastebin.com/C2SSSj5J

I hope the config file is the right one, it was in my /boot directory alongside the kernel.
Also, I honestly have no idea what type of SSD I have - I bought this chromebook just last week.
I hope the panic doesn't have anything to do with the ssd or its controllers, because I have no idea how to configure seabios.
Thanks again.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sun Oct 09, 2016 12:04 pm    Post subject: Reply with quote

Bladesy,

That's interesting, there is no block device controller on the PCI bus.
So your built in block device is either on USB or SDIO.

What does lsusb show?

Looking at your kernel
Code:
# CONFIG_MMC is not set
is a very bad thing.
Its a menu item. You need that and some of the options inside for the SD slot and possibly for your built in
SSD.

Check your kernel over for all the drivers listed in lspci -k too. Its possible that they could be hidden if options that they depend on are hidden.
In memuconfig, press 'z' to toggle the display of all the hidden options.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sun Oct 09, 2016 2:31 pm    Post subject: Reply with quote

Here is the ouput of lsusb:
Code:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 0408:2010 Quanta Computer, Inc.
Bus 001 Device 002: ID 1908:1320 GEMBIRD PhotoFrame PF-15-1
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of lsusb -v: http://pastebin.com/mZwNuLbQ
New kernel configuration file: http://pastebin.com/GsCawVVL
I compiled a new kernel with the above settings and updated my grub configuration file to include everything in CONFIG_MMC, but the same error occurred when I rebooted.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sun Oct 09, 2016 2:59 pm    Post subject: Reply with quote

Bladesy,

There are no storage devices on USB either.
Turn off both
Code:
CONFIG_MMC_DEBUG=y
CONFIG_MMC_TEST=y

They may interfere with normal operation.

Code:
CONFIG_MMC_BLOCK_MINORS=8
is a good default setting.
Keep in mind that it will limit you to a maximum of 7 partitions on an mmc card.

You probably don't need either of
Code:
CONFIG_SDIO_UART=y
CONFIG_MMC_SDHCI_PCI=y
but they should be harmless meanwhile.

Turn on
Code:
# CONFIG_BLK_DEV_NVME is not set
This is for block devices connected directly to the PCIe bus.
I've never seen one but they are out there.
I've also heard of some of them being slow to get started.
Add rootdelay=30 to your kernel command line. That's a 30 second wait which is really excessive.
The alternative is to use rootwait. That will wait forever for the root device to appear, and you will never get the kernel panic and error message.
If rootdelay=30 works (eventually), switch to rootwait, so you don't wait longer than needed.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sun Oct 09, 2016 4:55 pm    Post subject: Reply with quote

I recompliled the kernel and updated grub with rootwait, but at "Waiting for root device /dev/mmcdlk0p3", it only continues by printing "kworker/dying (560) used greatest stack depth: 13416 bytes left", and just stays there.
I've kept it on a while before posting, just to see if it would progress beyond this, but it seems stuck.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sun Oct 09, 2016 6:44 pm    Post subject: Reply with quote

Bladesy,

That says that /dev/mmcdlk0p3 never appears, so the rootwait never ends.
That's why I suggested the rootdelay. That way, if the error message has changed, you get to see it after the timeout.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sun Oct 09, 2016 7:23 pm    Post subject: Reply with quote

I tried with rootdelay, and the kernel panic message was exactly the same.
Is there anything else I can try?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Mon Oct 10, 2016 5:27 pm    Post subject: Reply with quote

Bladesy,

Try the testing kernel, 4.8.1.
It has some new NVME options you can play with.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5917

PostPosted: Mon Oct 10, 2016 9:09 pm    Post subject: Reply with quote

What's your full bootloader command line?
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Mon Oct 10, 2016 10:32 pm    Post subject: Reply with quote

I was using rootdelay=60 or rootwait, rw, and root=/dev/mmcblk0p3.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Mon Oct 10, 2016 10:57 pm    Post subject: Reply with quote

Bladesy,

Build an initrd with a shell, just so you can see what's happening.
Maybe your internal SSD isn't called mmcblk0.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Mon Oct 10, 2016 11:04 pm    Post subject: Reply with quote

Using the new kernel, I did a complete reinstall and went back through the gentoo handbook, and found that genkernel should work with my hardware - so I used it in conjunction with the newest kernel, 4.8.1.
I believe an initrd was created, while another change I tried was using UUIDs in my fstab.
After booting however, now I just get a completely blank screen after grub.
Does this mean I went down the wrong path in fixing this?
Should I just do a reinstall without genkernel and try fixing from there - if so, is there anything I should do differently?
I can't actually find the kernel config, but I think genkernel uses a set configuration file anyway.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Wed Oct 12, 2016 8:25 pm    Post subject: Reply with quote

I figured there was definitely something up with my last install not booting entirely, so my lastest install includes the newest kernel sources - 4.8.1 - which does seem to have new features in the MMC section.
I compiled a kernel with most of the new MMC settings enabled, regardless of whether I thought they would work or not, and I also set up an initrd.
As soon as I booted for the first time, I got a prompt asking me for a valid root device, after stating that /dev/mmcblk0p3 was not valid.
The only other output that seemed of interest was the line "Could not specify the root device in ." - the absense of something after the "in" looking a little strange.
I'll be keeping this same install for the rest of the thread most likely, as it doesn't seem like I just simply messed up the standard install - do these new messages give anything away that I haven't picked up on?
Also, is there possibly any options in the new kernel that I may have missed?
New kernel configuration file: http://pastebin.com/nH8mmpgr
Thanks again.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Wed Oct 12, 2016 8:35 pm    Post subject: Reply with quote

Bladesy,

Code:
Could not specify the root device in .

Is significant for what it doesn't say.

There should be a list of all the block devices the kernel can see and there is nothing.

Try a card in the microSD slot. As long as its partitioned, it doesn't matter whats on it.
We just want to see it listed in that message.
Also try a USB block device. Again, we just want to see it listed.

Use rootwait=30 on the kernel command line or USB won't be ready.

genkernel-next may be worth trying. I don't know how its different from the genkernel you have.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Wed Oct 12, 2016 10:06 pm    Post subject: Reply with quote

I've tried my full size SD card and 2 separate USB drives - but nothing shows up for block devices.
I didn't think this was a big deal at first, but the on-board keyboard doesn't work either - I didn't expect it to, since it didn't when I booted arch from USB, but not even my USB keyboard works (not even its LEDS), so I've no way of interacting with the initrd.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Fri Oct 14, 2016 10:35 pm    Post subject: Reply with quote

What exactly does it mean that my block devices aren't being picked up?
Would it maybe be worth trying another distro just for testing, or would the results likely be the same?
Are there any other things I should try?
Back to top
View user's profile Send private message
324874
Apprentice
Apprentice


Joined: 26 Jul 2014
Posts: 168

PostPosted: Sat Oct 15, 2016 8:40 am    Post subject: Reply with quote

Hello Bladesy!

Your post should be in the Unsupported Hardware/Software "forum"! :lol:
Indeed, the procedure for installing another operating system on a Chromebook computer seems specific.
A chromebook is a laptop running ChromeOS as its operating system. Could you give the model name of the computer, please?

I searched on the Gentoo wiki; maybe this search result would be helpful?

Best regards, feng.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sat Oct 15, 2016 9:20 am    Post subject: Reply with quote

I actually have the Lenovo N22, but the Toshiba 2 has a similar processor, and seems to have the same memory.
In the article for the T2, it's mentioned that the card is eMMC, but they also refer to using an SD card.
My current install must be on the eMMC card, but is it possible that I must have to boot from an SD card?
Could this be my current problem, or do I have a different problem entirely?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sat Oct 15, 2016 10:23 am    Post subject: Reply with quote

Bladesy,

It would be useful to know what you have in /dev by way of block devices.
That would help identify what you need in the kernel.

USB devices do not normally appear until after root is mounted, hence the rootdelay=30, so that they appear before root fails to mount.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Bladesy
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2015
Posts: 113

PostPosted: Sun Oct 16, 2016 4:50 pm    Post subject: Reply with quote

I've been trying to see if there was anyway for me to get the dev files straight from the gentoo install, but I haven't been able to.
I was going to post the dev files from the chroot, but when chrooting I mount the dev directory as rbind, which I believe makes a copy of what the arch usb sees.
Should I post that, or is there a way of getting the gentoo install's dev directory?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43764
Location: 56N 3W

PostPosted: Sun Oct 16, 2016 5:19 pm    Post subject: Reply with quote

Bladesy,

Anything would help. Gentoo with an initrd that drops you to a shell when mounting root fails would let you see what Gentoo sees.
As long as you have a working keyboard and display
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum