Installing Ethernet Drivers on Installation Media

[xevra]

[pingtoo]

[xevra]

Part 1:

[xevra]

Part 3:

[xevra]

Part 4a:

[xevra]

Part 4b:

[xevra]

Part 4c:

[xevra]

A few things I see in here that concern me are:
- various mentions of systemd, while I thought I had openrc installed, and have a use flag that excludes the systemd flag when compiling packages like the distkernel
- various mentions of x86, which I know less about, except that I should be using AMD.
I'm going to try a emerge --changed-use @world, and let that run overnight (going to bed).

My make.conf currently looks like this:

[NeddySeagoon]

xevra,

That looks good.

[pingtoo]

xevra,

Thank you for the information.

You don't need to concern about systemd stuff. Because dracut internally use udev/systemd to parallel executions during initramfs. So it does not mean your system have systemd stuff installed.

I have not work on initrd(initramfs) for sometime now so I don't remember all the detail dracut work. But it looks strange the last warning messages mention something not defined anywhere. And the waning messages come out far from end of kernel messages this lead me to think you were in dracut command line (emergency shell), so where you doing something at dracut command line? like testing locate root device?

Was there some other messages indicate the boot failed beside those warning messages?

[xevra]

Thank you both for the continued assistance.

After it failed to boot, it dumped me into the Dracut command line. That is how I copied the rdsosreport.txt file onto a flash drive.

Just to double-check, I did a search for 03F4-8F7A in the file, and confirmed that it does not appear anywhere except at the end, after the "failed to boot" message.

I am also curious if this line means anything:

[xevra]

One thing I failed to mention previously is that one of my flash drives corrupted while I was sneakernet-ing things, mounting and unmounting it.

Should I try wiping everything and following the same instructions, but this time use an un-corrupted flash drive to move packages around?

Or would portage have caught any issues with file corruption?

[pingtoo]

xevra,

Let us distinguish configuration problem vs setup problem.

setup problem, if the rootfs missing something critical and dracut detected that, it will cause problem.

configuration problem, if given wrong configuration dracut will not able to continue due to incorrect parameters.

So first try to find if there is setup problem. At dracut command line, try

1. Mount rootfs
   
2. Examine rootfs content
   
3. if everything look ok in rootfs, try to boot into it to see if anything else need to work

if setup have no problem, than work on dracut configuration, This will need to

• Understand how you generate the dracut initramfs
  
• At dracut command line examine some configuration files to see if it bring in some clues.

to mount rootfs use commands in dracut command line

• mount /dev/nvme0n1p3 /sysroot
  
• ls -l /sysroot/etc
  
• ls -l /sysroot/sbin/init

The two ls commands is to eye ball if anything critical missing, so please share those output.

what action need to follow depend on the above conditions. so let's take small steps at a time for now.[/list]

[xevra]

pingtoo,

Thank you for the instructions.

Here is the output of each command:

ls -l /sysroot/etc

[pingtoo]

xevra,

Thanks for the information.

I forgot to check /sysroot/etc/fstab. Let's assume it is OK for now.

In dracut command line; if you execute

[NeddySeagoon]

xevra,


That errant 03F4-8F7A looks like VFAT filesysystem ID of some sort.

[xevra]

Thank you both again for your time and assistance.

exec switch_root /sysroot /sbin/init did not work, even while the device was mounted. I think it got stuck in a loop, and it was moving too quickly to read. Some of the messages that appeared (not necessarily in order) are:

[xevra]

Additionally, I will be traveling for work for the next two weeks, starting tomorrow. I will therefore need to take a break from working on this until I return (I have a wireguard VPN on a raspberry pi with port forwarding so that I can access other machines on my local network while traveling, but we have not successfully set up ethernet / sshd).

I will obviously still be able to check the forum and respond, but I can't bring a tower with me in my luggage.

I thank you again for all of your help so far, and I hope you will still be willing to help me when I return.

I will still check in periodically today, and keep trying things until I leave tomorrow.

[pingtoo]

[NeddySeagoon]

xevra,

[xevra]

Thank you both for your continued assistance.

pingtoo, I can verify that after mounting /dev/nvme0n1p3 in /sysroot, I see the same filesystem that I see when I mount that partition on the installation media.

NeddySeagoon,

ls -l /dev/null in the rescue shell shows:

[pingtoo]

So I am thinking, could there be some kind of loop mounting? I don't know

anyway, there are usually few steps prior to execute "exec switch_root ..." that is unmount/move /proc, /sys and /dev to the new root.

I don't know if not doing them is relate to your case. but may be you can give it a try. Also just another thoughts, udev/systemd might need to stopped prior to switch_root.

will check to see what are related commands.

[NeddySeagoon]

xevra,

That's all good.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[pingtoo]

Just learned that Gentoo's dracut is actually based on dracut-ng, not the old scripted based version.

And the dracut-ng use util-linux which does the unmount/move /proc, /sys, etc... automatically.

So no need to concern about unmount/move prior to switch_root.

However I learn from the init script that you may need to do following

[xevra]

Thank you,

I executed those three commands, and tried to switch_root again.

I got stuck in the same loop.