Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Could not find the root block device in UUID=........
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sat Jul 16, 2016 11:02 am    Post subject: Could not find the root block device in UUID=........ Reply with quote

Hello everybody, i'm a new gentoo user.It's a while that i tried to install this fabolous distro after i read a lot of posts.
It's a small Acer Laptot Aspire E11 con ssd (eMMC 32GB)
I used "genkernel --menuconfig all" for set vfat fs support, scsi support and all file system.

I don't have any errors during the installation, but when i reboot i get "Could not find the root block device in UUID=d5777................."
-Please specify another value or:
-press Enter for the same
type shell for a shell
type "q" to skip
I used system rescue cd for installation, grub for the bootloader.
the partition are:

mmcblk0p1 uefi 512M
mmcblk0p2 / 27.6G
mmcblk0p3 swap 1G

this is my fstab:
Code:

/dev/mmcblk0p1   /boot/   vfat   noauto,noauto   1 2
/dev/mmcblk0p2   /   ext4           noatime   0 0
/dev/mmcblk0p3   none   swap   sw   0 0


Thanks in advance.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7553
Location: Goose Creek SC

PostPosted: Sat Jul 16, 2016 1:45 pm    Post subject: Reply with quote

Boot the sysresccd, run parted -l | wgetpaste -t and blkid | wgetpaste -t and lspci -k | wgetpaste -t .
Mount the gentoo partitions and run wgetpaste -t /mnt/gentoo/boot/grub/grub.cfg and wgetpaste -t /mnt/gentoo/usr/src/linux/.config.
Post the url's returned by wgetpaste.
What was the exact command used to install grub?
If you retained windows and are planning to dual boot suggest a look at https://wiki.gentoo.org/wiki/UEFI_Dual_boot_with_Windows_7/8 (also works for win10) .
Recommend scrapping grub; using rEFInd with efi stub kernel for dual boot or efi stub kernel for single boot (with or without rEFInd).
_________________
Defund the FCC.
Back to top
View user's profile Send private message
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sat Jul 16, 2016 2:16 pm    Post subject: Reply with quote

Thanks for reply Donahue.

1)
-parted -l | wgetpaste - t https://bpaste.net/show/11230919a2e3
-blkid | wgetpaste -t https://bpaste.net/show/824ea469ad15
-lspci -k | wgetpaste -t https://bpaste.net/show/325653f74fd7

After Mount the gentoo partitions like so:
Code:
mount /dev/mmcblk0p2 /mnt/gentoo
mount /dev/mmcblk0p1 /mnt/gentoo/boot/


-wgetpaste -t /mnt/gentoo/boot/grub/grub.cfg https://bpaste.net/show/9041ab3dcd6a
-wgetpaste -t /mnt/gentoo/usr/src/linux/.config https://bpaste.net/show/e6e895e3a94f

2)The installation grub command was :

Code:
grub2-install --target=x86_64-efi --efi-directory=/boot

and then
Code:
grub2-mkconfig -o /boot/grub/grub.cfg


3) I don't want other OS on this Laptop. I want only gentoo . So i don't care about dual boot.
I tried a lot of attemps, from the beginning, the EFI stub with efibootmng. but was'nt a success :D but in this case i did'knew where i was wrong...i had a sever error of kernel panic and root partition non reachable.
so i decide to reach step by step...start with a working kernel configuration for achieve later an a clean Gentoo installation with Efistub and Kernel cmd_line.

Thanks so much Donahue....i getting crazy...but i didn't release. :wink:
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Jul 16, 2016 2:44 pm    Post subject: Reply with quote

beetterfly,

Welcome to Gentoo.

I don't see any storage devices of any sorf attached via the PCI bus or its descendants.
This makes me suspect its on the USB subsystem. Please post the output of lsusb, so we can check that.
If that guess is correct, you need to add rootwait to the kernel command line in grub.cfg

What happens now is that the kernel will try to mount root before the usb subsystem is started, so it will fail.
Subsequent attempts should work though.

When you get to
Code:
Could not find the root block device in UUID=d5777................."
-Please specify another value or:
-press Enter for the same
pressing enter may well work ... USB will be started when you read the message
If you
Code:
type shell for a shell
do /dev/mmcblk0, /dev/mmcblk0p1, /dev/mmcblk0p2 and /dev/mmcblk0p3 all exist?

If not, there is a piece missing from your kernel.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sat Jul 16, 2016 3:03 pm    Post subject: Reply with quote

Thanks for welcome NeddySeagoon.

1)
- lsusb
Code:
Bus 001 Device 007: ID 0781:5583 SanDisk Corp.
Bus 001 Device 006: ID 0489:e055 Foxconn / Hon Hai
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f2:b48a Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


i have to specify that i bought this laptop with Windows 8, i delete windows.
With any other linux distibution i never had problem with this kind of disk:
i never used:
Disk /dev/mmcblk0rpmb: 4194kB;
Disk /dev/mmcblk0boot0: 4194kB;
Disk /dev/mmcblk0boot1: 4194kB;

But i always use this disk
Model: MMC HBG4e (sd/mmc)
Disk /dev/mmcblk0: 31.3GB

2) i tried your tips. i type shell for a shell

and a tried to type
Code:
mount /dev/mm...


its doesn't find any disk! mmcblk0 or the other...
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Jul 16, 2016 3:39 pm    Post subject: Reply with quote

beetterfly,

Thats really useful information.
lsusb:
Bus 001 Device 007: ID 0781:5583 SanDisk Corp.
is your HDD.

Looking up the vendor and device IDs on google shows that its one of these. It won't have the connector in your laptop. The electronics will be soldered to the motherboard.

I would expect your storage device to appear as /dev/sda rather than /dev/mmcblk0 too. /dev/mmcblk0 is typically a memory card plugged into a slot, not a USB storage device.
Memory cards plugged into USB card readers get /devsd* names too.

Looking back at
blkid:
/dev/sda1: LABEL="SYSRCD-4_7_" UUID="58D9-1D6C" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="27405d7e-7b32-4aa0-99b4-a2ec8b7e1a12"
/dev/mmcblk0: PTUUID="3fb1d450-00e2-424a-ad77-c9027756aaaf" PTTYPE="gpt"
you do indeed have two storage devices.

Bus 001 Device 006: ID 0489:e055 Foxconn / Hon Hai is a Broadcom BCM43142A0 bluetooth device.
Bus 001 Device 005: ID 04f2:b48a Chicony Electronics Co., Ltd is your webcam
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub is a USB hub.

So far, there is no sign of the card reader that /dev/mmcblk0 could be attached to.

-- edit --

Boot your install media. That can see and use /dev/mmcblk0, so it must be able to show the USB or PCI hardware that the card reader is attached to.
If not, its not a USB or PCI device. That's not the end of the world. You said that other Linux distros work. If they can see it so can Gentoo.

-- edit 2 --

I'm having a senior moment ... your /dev/sda1 is System Rescue CD on a USB memory stick. Ignore most of what I wrote above.
It can see /dev/mmcblk0 but your own kernel cannot.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sat Jul 16, 2016 7:07 pm    Post subject: Reply with quote

Thanks a lot NeddySeagoon.
Yes the sda is the System rescue usb stick.
So i should try to set a rootwait to the kernel command line in grub.cfg?

Should i disinstall Grub2 and try with Refind?


Quote:
Boot your install media. That can see and use /dev/mmcblk0, so it must be able to show the USB or PCI hardware that the card reader is attached to.
If not, its not a USB or PCI device. That's not the end of the world. You said that other Linux distros work. If they can see it so can Gentoo.


With other distro, It always work property using the disk /dev/mmcblk0

this is the lsblk command:
Code:
lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    1 14.5G  0 disk
└─sda1         8:1    1 14.5G  0 part /livemnt/boot
loop0          7:0    0  339M  1 loop /livemnt/squashfs
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  512M  0 part
├─mmcblk0p2  179:2    0 27.6G  0 part
└─mmcblk0p3  179:3    0    1G  0 part


Thanks in advance
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Jul 16, 2016 8:11 pm    Post subject: Reply with quote

beetterfly,

The problem is either with your kernel or the initrd init script not loading a module you need to make your eMMC device visible.

Grub is doing its thing as your kernel loads, starts and then panics.
The bootloader has finished then.

Boot SystemRescueCD, make sure you can see /dev/mmcblk0 and friends.
Run
Code:
lsmod
the kernel modules its using are listed there.

Boot normally and go into the shell when it panics. Run lsmod.
Taking the list from System Rescue CD, cross off everything that appears in Gentoo.
Modules in both lists cannot be the problem.

For each module not crossed off, run
Code:
modprobe <module_name>

If there is an error, note it by the module name.
If there is no error, check for /dev/mmcblk0 ... make a note of the module name that made in appear.
That's what we need to know to fix it.

If you get to the end of the list and /dev/mmcblk0 is still missing, its produced by one of the modules that gave a modprobe error.
We can use that list to fix your kernel.

In the first case, the module has been build but its not being loaded. That may be a bug in genkernel.
In the second case, its a feature. Genkernel does not support your hardware unaided.

System Rescue CD is a Gentoo derivative, so we know it works on Gentoo.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sun Jul 17, 2016 8:44 am    Post subject: Reply with quote

Thanks NeddySeagoon, nice trick.i follow your instruction.
i get the list of loaded modules from Boot SystemRescueCD.
i rebooted the laptop, typed shell for the shell and iit appear busybox prompt.
i typed lsmod on busybox.:
it take my attention one point in that list:

Code:
raid0 20480 0 - Live 0xffffffffa04ac000

it's normal that all modules has LIVE and that address?

Anyway, i type
Code:
 modprobe <modulename>

for each SystemRescueCD loaded module. Only few module was ok. the most give back to me :"can't open '/lib/modules/4.4.6-gentoo/kernel/xxxxxxxxx':no such file or directory" or "not found in modules.dep". i report all modprobe result.
Code:
Module                  Size  Used by               RESULT
binfmt_misc            12390  1                             not found in modules.dep
intel_rapl             16546  0                        not found in modules.dep
acer_wmi               16486  0                        not found in modules.dep
iTCO_wdt               12390  0               can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/watchdog/iTCO_vendor.ko':no such file or directory
intel_soc_dts_thermal    12457  0                     not found in modules.dep
iTCO_vendor_support    12938  1                        not found in modules.dep
mmc_block              25205  0               can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/watchdog/iTCO_vendor.ko':no such file or directory
sparse_keymap          13019  1             can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/input/sparse-keymap.ko':no such file or directory
coretemp               12390  0               can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/hwmon/coretemp':no such file or directory
crct10dif_pclmul       12497  0                        not found in modules.dep
crc32_pclmul           12503  0                        not found in modules.dep   
crc32c_intel           16583  0               can't open '/lib/modules/4.4.6-gentoo/kernel/arch/x86/crypto/crc32c-intel.ko':no such file or directory   
btusb                  24738  0               can't open '/lib/modules/4.4.6-gentoo/kernel/net/rfkill/rfkill.ko':no such file or directory
bluetooth             292401  2 btusb         can't open '/lib/modules/4.4.6-gentoo/kernel/net/rfkill.ko':no such file or directory
microcode              41758  0               not found in modules.dep
joydev                 16547  0               not found in modules.dep
bcma                   37120  0               not found in modules.dep      
uas                    16546  0               not found in modules.dep
rfkill                 18094  2 acer_wmi,bluetooth      can't open '/lib/modules/4.4.6-gentoo/kernel/net/rfkill/rfkill.ko':no such file or directory
serio_raw              12460  0               can't open '/lib/modules/4.4.6-gentoo/kernel/driver/input/serio/serio_raw.ko':no such file or directory
lpc_ich                20642  0               can't open '/lib/modules/4.4.6-gentoo/kernel/driver/mfd/mfd-core.ko':no such file or directory
mfd_core               12807  1 lpc_ich       can't open '/lib/modules/4.4.6-gentoo/kernel/driver/mfd/mfd-core.ko':no such file or directory
i2c_i801               16543  0               not found in modules.dep
mei_txe                16787  0               not found in modules.dep
dw_dmac                12460  0               not found in modules.dep
dw_dmac_core           21614  1 dw_dmac         not found in modules.dep
i2c_hid                16619  0               not found in modules.dep
mei                    58790  1 mei_txe         not found in modules.dep
int3403_thermal        12500  0               not found in modules.dep
int3400_thermal        12461  0               not found in modules.dep
acpi_thermal_rel       12781  1 int3400_thermal   not found in modules.dep
i2c_designware_platform    12457  0            not found in modules.dep
i2c_designware_core    13304  1 i2c_designware_platform not found in modules.dep
sdhci_acpi             12454  0               not found in modules.dep
shpchp                 29586  0               not found in modules.dep
sdhci                  30190  1 sdhci_acpi      can't open '/lib/modules/4.4.6-gentoo/kernel/driver/mmc/host/sdci.ko':no such file or directory
mmc_core               85282  3 mmc_block,sdhci,sdhci_acpi   not found in modules.dep
raid10                 37123  0                  OK
raid456                57671  0                  OK
async_raid6_recov      12621  1 raid456            OK   
async_pq               12640  2 raid456,async_raid6_recov   OK
async_xor              12573  3 async_pq,raid456,async_raid6_recov   OK
async_memcpy           12464  2 raid456,async_raid6_recov         OK
async_tx               12840  5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov   OK
raid1                  28900  0                  OK                        
raid0                  16515  0                  OK
multipath              12390  0               not found in modules.dep
linear                 12390  0               OK
usb_storage            56586  2 uas            not found in modules.dep
i915                  725330  1         can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/video/fbdev/core/fbsys_fops.ko':no such file or directory
drm_kms_helper         66289  1 i915    can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/video/fbdev/core/fbsys_fops.ko':no such file or directory     
drm                   232399  3 i915,drm_kms_helper   can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/gpu/drm/drm.ko':no such file or directory
video                  17102  2 i915,acer_wmi can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/acpi/video.ko':no such file or directory
i2c_algo_bit           12633  1 i915           OK   
iosf_mbi               12815  1 intel_soc_dts_thermal    can't open '/lib/modules/4.4.6-gentoo/kernel/arch/x86/platform/intel/iosf_mbi.ko':no such file or directory
wmi                    13130  1 acer_wmi       can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/platform/x86/wmi.ko':no such file or directory
r8169                  53503  0            not found in modules.dep
mii                    13085  1 r8169      not found in modules.dep


Each right feedback modprobe i i tried to mount the disk /dev/mmcblk0, but nothing.still doesn't are visible.


I Observed, in a live environmental System Rescue CD, that if i insert a microsd card in the side slot, it's get name /dev/mmcblk1. look like the same family of the ssd disk /dev/mmcblk0 where i mounted the system.
I hope that i'have been clear to show the details.
Thanks a lot NeddySeagoon
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Jul 17, 2016 9:28 am    Post subject: Reply with quote

beetterfly,

You need at least
Code:
mmc_block

The modprobe failed
Code:
mmc_block              25205  0               can't open '/lib/modules/4.4.6-gentoo/kernel/drivers/watchdog/_
iTCO_vendor.ko':no such file or directory
so mmc_block depends on iTCO_vendor.ko which you don't have, or at least, its not in the initrd.

You probably need
Code:
mmc_core               85282  3 mmc_block,sdhci,sdhci_acpi   not found in modules.dep
too.

As we don't know where your card reader is,
Code:
usb_storage            56586  2 uas            not found in modules.dep
may be required too.

You have mmc_block configured as a module. Unfortunately its a menu item. As it would not load, the above test tells us nothing about the options inside the menu.
We will change your kernel. Then it will either work, or we need to redo the above test.

In the chroot, save the file /usr/src/linux/.config to /usr/src/my.config That's your current kernel config.
Do
Code:
genkernel --menuconfig all

That's just wiped out /usr/src/linux/.config, so load /usr/src/my.config, so we can go on from where you were. genkernel provides a way to do this properly but I don't know what it is.
Press / for search and enter mmc_block. Navigate to the option and set it to <*> so its built into the kernel. No more need to modprobe

Rinse and repeat for mmc_core and usb_storage. Some of these options may depend on parents being set to <*> before you can set them to <*>
Read the Depends on list in the search help and set them to <*> too.

Now the hard one. You need iTCO_wdt for mmc_block to work. That probably means you need all the other things with iTCO in their names too.
Try to search for iTCO.

To make the kernel configuration more manageable, things that you cannot select are hidden. That's a double edged sword.
You don't really care about PowerPC only options, so thats good. When you know the option you need, but its hidden as one of the Depends on items is off, its bad as it won't be in the search either. However, there is a toggle to turn ALL options on/off. Press z. The search will find 'hidden' options now, so you can check the Depends on.
You will see a new symbol, - -, meaning forced off, much as, -*-, means forced on.

Reinstall your new kernel and reboot to test.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sun Jul 17, 2016 12:24 pm    Post subject: Reply with quote

thanks a lot NeddySeagoon.I tried to compile again with genkernel config all....
i set new configuration. but still doesn't work... :evil:
i get the same situation. i hope i set everithing correct.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7553
Location: Goose Creek SC

PostPosted: Sun Jul 17, 2016 1:40 pm    Post subject: Reply with quote

The problem may be genkernel itself. I emerged genkernel-next, ran genkernel all on the existing gentoo-sources which included a working /usr/src/linux/.config. genkernel ran oldconfig incorporating my existing settings (verified by running cd /usr/src/linux; make menuconfig). Upon rebooting I was confronted by the same kernel panic as beeterfly. A few years ago genkernel had a similar problem when it's default config included a hardware raid controller that failed. Suggest forget genkernel and go with a manual kernel. The manual kernel default config is advertised as supporting the sdio bus out of the box.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Jul 17, 2016 2:03 pm    Post subject: Reply with quote

beetterfly,

Post your kernel .config file as it is now.

I'm inclined to go with what DONAHUE suggested but then, I've never used genkernel so I'm biased.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sun Jul 17, 2016 3:07 pm    Post subject: Reply with quote

Thanks agains..

this is my /usr/scr/linux/.config

https://bpaste.net/show/049dfbdee947

Can i use this configuration for manual kernel operation?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Jul 17, 2016 3:19 pm    Post subject: Reply with quote

beetterfly,

That looks almost correct. You have some debug options on. They are intended for developers working on the code in that area of the kernel.
They all generate lots of log spam and a few debug options interfere with correct operation of the kernel too.

You can't quite use that kernel configuration for a manual build. A normal manual build has everything needed to mount root built into bzImage, so that no initrd is required.
You will have some changes there.
You also need to turn off all the debug 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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sun Jul 17, 2016 3:30 pm    Post subject: Reply with quote

thanks NeddySeagoon,now i try a manual build.it'll be my first manual build experience.
I hope will be the solution.
Thanks a lot everybody for the suggest and informations.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Jul 17, 2016 4:06 pm    Post subject: Reply with quote

beetterfly,

You don't need a lot to be set to <*>
The partitiions code, the root filesystem code and the hardware drivers to get at the root filesystem.
That's the absolute minimum.

After that everything can be modular. My 11 year old guide is still about right.
These days you nee a bigger pot of coffee and tho output of lsusb.

There is another 'get you going' route.
Take the kernel, modules and firmware from SystemRescueCD. You are allowed to do that, its all provided under one open licence or another.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Sun Jul 17, 2016 5:17 pm    Post subject: Reply with quote

Great guide...now i start to study it.
i known that one time it will be necessary the manual build.So it's time right now to start.
Probably i put a lot of [*] even on debug stuff that i don't need.

Quote:
There is another 'get you going' route.
Take the kernel, modules and firmware from SystemRescueCD. You are allowed to do that, its all provided under one open licence or another.

So you advice to get the modules and firmware from SystemRescueCD like i did before? lsmod in SystemRescueCD environmental?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Jul 17, 2016 5:57 pm    Post subject: Reply with quote

beetterfly,

The SystemRescueCD contains a kernel that boots your system.
Once you boot SystemRescueCD, (do not chroot) you can see some of it.

The some of it you can see you can copy to the same places in your install.
Thats
/lib/firmware ... that goes to /mnt/gentoo/lib/firmware
Its the firmware for devices supported by limux. Normally from the linux-firmware package.
The other piece is /lib/modules/`uname -r'/ that goes to /mnt/gentoo/lib/modules/`uname -r'/
Its the kernel modules provided by SystemRescueCD.

The kernel and initrd are a little harder to find. They are probably not visible inside /boot as they are not located on the SystemRescueCD root filesystem.
Your raw SystemRescueCD is on /dev/sda1 which you normally do not mount.
Do
Code:
mkdir /mnt/cdrom
, if that does not exist.
Code:
mount -ro /dev/sda1 /mnt/cdrom
-ro for read only.
Code:
ls /mnt/cdrom
will show you SystemRescueCD 'from the outside'.
There are a few interesting things here.
sysrcd.dat is the root filesystem you use when you boot SystemRescueCD.

/mnt/cdrom/syslinux/ contains all the files used to boot SystemRescueCD.
There is only one initram.igz copy that to your /boot.
There is a choice of kernels. rescue32 and rescue64 are the default 32 bit and 64 bit kernels, altker32 and altker64 are the alternate kernels.
Pick the one you use to boot with and copy it to your /boot.

Now you have all the bits.
Code:
umount /dev/sda1
as you don't need it any more.
Get into your chroot and tell grub about your new kernel and initrd.

Reboot to test. If all is well, your Gentoo will start on top of the SystemRescueCD kernel.
This will let you postpone building your own kernel.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Tue Jul 19, 2016 8:49 pm    Post subject: Reply with quote

NeddySeagoon thanks so much for the precious informations. I tryed for curiosity the SystemRescueCD kernel. it worked.

So i reistalled everithing, i compile in manual mode the kernel, following your advise and the printed lspci and lsmod.
But something i miss again in the kernel config: i still have the same error:
"Could not find the root block device in UUID=d5777................."
-Please specify another value or:
-press Enter for the same
type shell for a shell
type "q" to skip

this is my .config
[code]wgetpaste -t /mnt/gentoo/usr/src/linux/.config[code] [url] https://bpaste.net/show/1a406ecd0b64[/url]

my grub.cfg
[code]wgetpaste -t /mnt/gentoo/boot/grub/grub.cfg[/code] [url] https://bpaste.net/show/59836cb10a22[/url]

i'm really getting crazy.
One thing, could be not important. The disk's name is /dev/mmcblk0.
I see that if i insert an a memory stik in a card reader, it call /dev/mmcblk1. look like the same family disk.
In the busybox shell doesn't recognice any kind of disk. but if i insert an usb, i can see it.
So set in the kernel the Realtek card Reader.
But still doesn't work.I hope that i'll not trow away that laptop :twisted:
Thanks everibody in advance
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Tue Jul 19, 2016 9:11 pm    Post subject: Reply with quote

beetterfly,

Since the SystemRescueCD kernel works, use that for now.

You can have several kernels installed at the same time and use the grub menu to choose between them.
Everyone makes a dud kernel from time to time and its good to fix it without doing the chroot dance :)

You can use the SystemRescueCD kernel to get you going, while you make your own.

I have a similar problem on by Raspberry Pi install. The kernel does not see /dev/mmcblk0 either.
Enough of my troubles. Maybe fixing one will fix the other too.

At the weekend, I will try to configure a kernel for you. I'll post the .config file, then you can build and test it.
It will not need an initrd.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Wed Jul 20, 2016 6:43 am    Post subject: Reply with quote

Thanks a lot NeddySeagoon, i'm such grateful for your interest. I learned a lot following your posts.
You acted like an older brother.
I'll wait an your kernel configuration.
Meanwhile i'll do other attemps. i hope to resolve it.
Thanks again
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Wed Jul 20, 2016 9:17 pm    Post subject: Reply with quote

beetterfly,

I've read some reviews of the E11. Your storage might actually be a real NVMe device, even though in appears as an mmc card.
If so, you need <*> NVM Express block device and maybe
[*] SCSI emulation for NVMe device nodes.

Also add rootwait to the kernel command line, as we have seen an Intel NVMe drive be slow to get started.


You did have <M> NVM Express block device in your original kernel but the genkernel initrd init script does not load it.
_________________
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
beetterfly
n00b
n00b


Joined: 17 Jun 2016
Posts: 26

PostPosted: Thu Jul 21, 2016 7:02 pm    Post subject: Reply with quote

Thanks so much NeddySeagoon.
I compiled the kernel with NVM Express block device support and SCSI emulation for NVMe too.
i give again the grub mkconfig
Code:
grub2-mkconfig -o /boot/grub/grub.cfg

i reboot and press e.
typed rootwait.
it look like recognize the disk:
waiting for root device /dev/mmcblk0p2
random: nonblocking pool is initialized
and get stuck here.

without rootwait
VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6
Please appena a correct "root=" boot option ;

kernel panic

kernel offset:disabled

Thanks in advance
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Thu Jul 21, 2016 7:12 pm    Post subject: Reply with quote

beetterfly,

That looks like rootwait waiting for ever and /dev/mmcblk0p2 never appearing, so root is never mounted.
I have your .config half done.
_________________
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, 3  Next
Page 1 of 3

 
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