Le 23/11/2019 à 18:38, Christopher Gregory via blfs-support a écrit :
>
>
>> Sent: Saturday, November 23, 2019 at 11:13 AM
>> From: "Pierre Labastie via blfs-support"
>> <[email protected]>
>> To: [email protected]
>> Cc: "Pierre Labastie" <[email protected]>
>> Subject: Re: [blfs-support] More weirdness in this install
>>
>> Le 23/11/2019 à 06:19, Christopher Gregory via blfs-support a écrit :
>>>
>>>
>>>> Sent: Saturday, November 23, 2019 at 6:06 AM
>>>> From: "Ken Moffat via blfs-support"
>>>> <[email protected]>
>>>> To: "BLFS Support List" <[email protected]>
>>>> Cc: "Ken Moffat" <[email protected]>
>>>> Subject: Re: [blfs-support] More weirdness in this install
>>>>
>>>> On Fri, Nov 22, 2019 at 05:43:21PM +0100, Pierre Labastie via blfs-support
>>>> wrote:
>>>>> Le 22/11/2019 à 15:04, Christopher Gregory via blfs-support a écrit :
>>>> [...]
>>>>>
>>>>> Christopher, I think you do not need (yet) to "destroy" everything again.
>>>>> What
>>>>> you describe really looks like some missing kernel feature: if a dvd
>>>>> drive is
>>>>> correctly connected (either through sata or scsi), and all the relevant
>>>>> options are correctly set when building the kernel, the kernel itself
>>>>> should
>>>>> create /dev/sr0 in the devtmpfs. Udev is not involved I think.
>>>>>
>>>>> So compare what you build in or as module for your kernel to what the host
>>>>> distro has (lsmod on host distro). Note: builtin modules list is at
>>>>> /lib/modules/<version>/modules.builtin.
>>>>>
>>>>> For example, from host distro (with the lfs root mounted on $LFS, and
>>>>> VERSION
>>>>> set to the lfs kernel version string):
>>>>> ------
>>>>> lsmod | while read module notused; do
>>>>> if ! find $LFS/lib/modules/$VERSION/ -name ${module}\* > /dev/null; then
>>>>> if ! grep -q $module $LFS/lib/modules/$VERSION/modules.builtin; then
>>>>> echo $module is missing
>>>>> fi
>>>>> fi
>>>>> done
>>>>> ------
>>
>> First:
>> Sorry, the above is completely wrong: find exits with 0 code even when it
>> does
>> not find a file (if no error occurred). A possible command is:
>> ------
>> lsmod | while read module notused; do
>> if [ -z "$(find $LFS/lib/modules/$VERSION/ -name ${module}\*)" ]; then
>> if ! grep -q $module $LFS/lib/modules/$VERSION/modules.builtin; then
>> echo $module is missing
>> fi
>> fi
>> done
>> ------
>>
>> Second: I understand that you have no way to start a distro, but you have a
>> debian dvd with an installer, don't you? I think you can start in "rescue
>> mode" (avoid graphical mode), and execute a shell in the installer
>> environment. Then mount the lfs drive (maybe you'll need to start some lvm
>> modules), set $LFS and $VERSION, then type the command above (no way to
>> copy-paste in this case).
>>
>> Pierre
>> --
>> http://lists.linuxfromscratch.org/listinfo/blfs-support
>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>> Unsubscribe: See the above information page
>>
>
> Hello Pierre,
>
> I managed to burn a debian live dvd by "burning" a live dvd onto my 8 gig usb
> stick.
>
> The results of your command are:
Hi,
I've since then found that there can be false positive, because kernel folks
do not know the difference between "-" (dash) and "_" (underscore). So the
results are to be taken with a grain of salt.
You can change the command to:
------
lsmod | while read module notused; do
moduledash=${module//_/-}
if [ -z "$(find $LFS/lib/modules/$VERSION/ -name ${module}\* \
-o -name ${moduledash}\*)" ]; then
if ! grep -q "\($module\|$moduledash\)" \
$LFS/lib/modules/$VERSION/modules.builtin; then
echo $module is missing
fi
fi
done
------
but see below one suspicious result, if not a false positive.
>
> root@debian:/var/lib/dpkg# lsmod | while read module notused; do if [ -z
> "$(find $LFS/lib/modules/$VERSION/ -name ${module}\*)" ]; then if ! grep -q
> $module $LFS/lib/modules/$VERSION/modules.builtin; then echo $module is
> missing; fi; fi; done
>
> Module is missing
This one does not count: it is the first word of the first line, and not a
module...
> dm_mod is missing
> fscrypto is missing
> rfcomm is missing
> bnep is missing
> snd_hda_codec_realtek is missing
> snd_hda_codec_generic is missing
> snd_hda_codec_hdmi is missing
> snd_hda_intel is missing
> snd_hda_codec is missing
> joydev is missing
> snd_hda_core is missing
> snd_hwdep is missing
> snd_pcm is missing
> kvm_amd is missing
> ansi_cprng is missing
> ccp is missing
> snd_timer is missing
> sp5100_tco is missing
> ppdev is missing
> parport_pc is missing
> rng_core is missing
> pcc_cpufreq is missing
> parport is missing
> acpi_cpufreq is missing
> wmi_bmof is missing
> serio_raw is missing
> pcspkr is missing
> crct10dif_pclmul is missing
> crc32_pclmul is missing
> ghash_clmulni_intel is missing
> squashfs is missing
> zstd_decompress is missing
> xxhash is missing
> overlay is missing
> uas is missing
> usb_storage is missing
> hid_generic is missing
> crc32c_intel is missing
> ohci_pci is missing
> i2c_algo_bit is missing
> aesni_intel is missing
Up to now, I think a basic system can run without those (although it may lack
sound and other fancy things)
> pata_atiixp is missing
If not a false positive, that may be a reason for the observed behavior. Any
required pata/sata module should be into your kernel.
> aes_x86_64 is missing
> crypto_simd is missing
> cryptd is missing
> glue_helper is missing
> i2c_piix4 is missing
Again no harm for a basic system
> xhci_pci is missing
> ohci_hcd is missing
> xhci_hcd is missing
> ehci_pci is missing
> ehci_hcd is missing
> usb_common is missing
If not false positives, you'll have no USB on lfs.
> wmi is missing
Try adding this one too. It allows to access supplemental hardware information
from BIOS. But nothing sure, though...
>
> I need to add that debian is running the 4.x series of kernel.
>
> I have no idea if the "is missing" modules would be causing the kernel to not
> create /dev/sr0 or not. When I attempted to create the dev using mknod,
> after it was created, it gave an error that /dev/sr0 is not a valid block
> device, so that did not solve anything unfortunately. I did try the sed for
> the udev rule, and that also made no difference.
>
> There is no /dev/cdrom created either, so I have absolutely no idea where to
> go from here.
Yes, we have to get /dev/sr0 first. /dev/cdrom is just a symlink to /dev/sr0.
>
> I have most of my required modules installed directly into the kernel rather
> than as a seperate module that can be inserted using insmod.
The list of modules installed directly into kernel are in
/lib/modules/<version>/modules.builtin (after running "make modules_install").
That's how we know that they are missing.
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
