micro SD cards not recognized

[firenice03]

[member=45699]adml[/member]
You say the card reader is working in the 4.4 kernel?
With it working...
Running through some of those initial commands... inxi etc etc, may give insight to the driver its using - perhaps it could be loaded into the later releases or compiled...??.,... its a thought....


May try

Code:

inxi -Fxz

[adml]

[member=5414]firenice03[/member]

Yes, the card reader is recognized when using a live USB of Linux Lite 3.8, which uses the 4.4 kernel. I'd like to install the 4.4 kernel in Linux Lite 5.2 but as we've found out, there's a problem. Jerry has discovered that something has been changed in the kernel build process. This is apparently what is disallowing different kernels to be installed.

Below are the outputs of...

inxi -Fxz

and

lsblk

...when using a live USB of Linux Lite 3.8, with the card reader mounted and a 32GB card inserted.

Is there anything else that I could post that might be helpful ?


linux@linux:~$ inxi -Fxz
System:    Host: linux Kernel: 4.4.0-112-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Xfce 4.12.3 (Gtk 2.24.28)
          Distro: Ubuntu 16.04 xenial
Machine:  System: LENOVO product: 80R9 v: Lenovo ideapad 100S-14IBR
          Mobo: LENOVO model: Aristotle 14 v: SDK0J91145 WIN Bios: Lenovo v: E4CN13WW date: 09/11/2015
CPU:      Dual core Intel Celeron N3050 (-MCP-) cache: 1024 KB
          flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6399
          clock speeds: max: 2160 MHz 1: 1037 MHz 2: 1439 MHz
Graphics:  Card: Intel Device 22b1 bus-ID: 00:02.0
          Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) Resolution: [email protected]
          GLX Renderer: Mesa DRI Intel HD Graphics 400 (Braswell)
          GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes
Audio:    Card Intel Device 2284 driver: snd_hda_intel bus-ID: 00:1b.0 Sound: ALSA v: k4.4.0-112-generic
Network:  Card: Intel Wireless 3160 driver: iwlwifi bus-ID: 02:00.0
          IF: wlp2s0 state: up mac: <filter>
Drives:    HDD Total Size: 31.9GB (3.4% used) ID-1: /dev/mmcblk0 model: N/A size: 62.5GB
          ID-2: USB /dev/sda model: Flash_Disk size: 31.9GB temp: 0C ID-3: /dev/mmcblk1 model: N/A size: 31.3GB
Partition: ID-1: / size: 857M used: 73M (9%) fs: overlay dev: N/A
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:  System Temperatures: cpu: 37.0C mobo: N/A
          Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 183 Uptime: 8 min Memory: 739.4/1713.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
          Client: Shell (bash 4.3.481) inxi: 2.2.35



linux@linux:~$ lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    1 29.7G  0 disk
└─sda1        8:1    1 29.7G  0 part /cdrom
loop0          7:0    0  979M  1 loop /rofs
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 58.2G  0 disk
├─mmcblk0p1  179:1    0  512M  0 part
└─mmcblk0p2  179:2    0 57.8G  0 part
mmcblk1      179:32  0 29.1G  0 disk
└─mmcblk1p1  179:33  0 29.1G  0 part /media/linux/0403-0201

[Valtam]

Try the Ubuntu ones here - https://kernel.ubuntu.com/~kernel-ppa/ma...v4.4-wily/

linux-headers-4.4.0-040400_4.4.0-040400.201601101930_all.deb
linux-headers-4.4.0-040400-generic_4.4.0-040400.201601101930_amd64.deb
linux-image-4.4.0-040400-generic_4.4.0-040400.201601101930_amd64.deb

https://ubuntuhandbook.org/index.php/201...in-ubuntu/

[adml]

[member=2]Jerry[/member]

Thank you for the links.

Per the instructions in the last link I downloaded the files via the command line and then ran sudo dpkg -i *.deb to install. Below is the output. The file libssl1.0.0 is still the sticking point, even though 1.1 is installed. I rebooted but inxi shows that I'm still using 5.4.0-67-generic x86_64.

Is there a way to get to the Grub screen during boot ? I'm thinking that it's a certain key(s) press but I don't know what it is.

sudo dpkg -i *.deb
[sudo] password for:
Selecting previously unselected package linux-headers-4.4.0-040400.
(Reading database ... 366242 files and directories currently installed.)
Preparing to unpack linux-headers-4.4.0-040400_4.4.0-040400.201601101930_all.deb ...
Unpacking linux-headers-4.4.0-040400 (4.4.0-040400.201601101930) ...
Selecting previously unselected package linux-headers-4.4.0-040400-generic.
Preparing to unpack linux-headers-4.4.0-040400-generic_4.4.0-040400.201601101930_amd64.deb ...
Unpacking linux-headers-4.4.0-040400-generic (4.4.0-040400.201601101930) ...
Selecting previously unselected package linux-image-4.4.0-040400-generic.
Preparing to unpack linux-image-4.4.0-040400-generic_4.4.0-040400.201601101930_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
Done.
Unpacking linux-image-4.4.0-040400-generic (4.4.0-040400.201601101930) ...
Setting up linux-headers-4.4.0-040400 (4.4.0-040400.201601101930) ...
dpkg: dependency problems prevent configuration of linux-headers-4.4.0-040400-generic:
linux-headers-4.4.0-040400-generic depends on libssl1.0.0 (>= 1.0.0); however:
  Package libssl1.0.0 is not installed.

dpkg: error processing package linux-headers-4.4.0-040400-generic (--install):
dependency problems - leaving unconfigured
Setting up linux-image-4.4.0-040400-generic (4.4.0-040400.201601101930) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
* dkms: running auto installation service for kernel 4.4.0-040400-generic                                                      [ OK ]
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-040400-generic
modinfo: ERROR: could not get modinfo from 'crc32': No such file or directory
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-040400-generic /boot/vmlinuz-4.4.0-040400-generic
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found background: /boot/grub_linux_lite.png
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found background image: /boot/grub_linux_lite.png
Found linux image: /boot/vmlinuz-5.4.0-67-generic
Found initrd image: /boot/initrd.img-5.4.0-67-generic
Found linux image: /boot/vmlinuz-5.4.0-66-generic
Found initrd image: /boot/initrd.img-5.4.0-66-generic
Found linux image: /boot/vmlinuz-5.4.0-52-generic
Found initrd image: /boot/initrd.img-5.4.0-52-generic
Found linux image: /boot/vmlinuz-4.8.0-linuxlite
Found initrd image: /boot/initrd.img-4.8.0-linuxlite
Found linux image: /boot/vmlinuz-4.4.0-040400-generic
Found initrd image: /boot/initrd.img-4.4.0-040400-generic
Adding boot menu entry for UEFI Firmware Settings
done
Errors were encountered while processing:
linux-headers-4.4.0-040400-generic

[Valtam]

Is there a way to get to the Grub screen during boot ? I'm thinking that it's a certain key(s) press but I don't know what it is.

Esc key or hold down Shift key.

[Şerban S.]

[member=25275]Şerban S.[/member]
[...]My thinking is that it is a kernel issue. [...] since the card reader is recognized in one kernel, but not others, wouldn't that point to the kernel being the cause ?

Hello, again!
Obviously, the management of the drivers and the IRQ assignment, is a kernel job. At least... in theory.
Practical issues occur though... Since we're dealing with patented hardware, the idilic theory of "open sourced architecture" seems to fail. See the Intel CPUs story. In any patented hardware, there are hidden "features" that serve a certain agenda, closely related to big money making. It is impossible to predict each and every small "twist" in each revision. Now, given the fact that Windows is commercial software, they have access to technical specs that are unavailable to the OpenSource world and this is well known for decades. This is why under Windows, it works. See the NVidia case for one.
As for what is happening under Linux, if it is a kernel issue (I too belive it is! ), patching might prove an extremely difficult task since newer kernels include more and more hardware support and sometimes, support for old hardware is wiped out, due to conflicts with the new hardware support. This leaves only one option: Tweaking the kernel with the blacklist option in the config file. This will allow ignoring a certain driver and install/load the driver that actually does the job properly, even if it is said to be "old" or "deprecated".
This is nothing like a child's play and should be done with a great deal of attention. Messing with kernel configuration, might render the machine unusable and this leads to reinstallation. In some cases, might render the hardware unusable or maybe worse, might damage it (for video cards, that might happen).

With those being said, the only thing that remains to do as I see things, is hope for a good fix from Jerry, although this will get you stucked with the respective kernel and the inherent limitations that emerge from this.

Good luck!
Best regards!

[adml]

@Serban S.

Thank you for letting me know your ideas. Please read my next post for an apparent solution, at least at this point in time, to my ongoing saga.

[adml]

[member=2]Jerry[/member]

Neither the Escape key, or the Shift key would bring up the Grub menu. In searching for a solution I discovered Grub Customizer. I installed it and what I found, to borrow a quote from Alice, made me, "Curiouser and Curiouser."

In addition to 3 different 5.4.0 Linux kernel entries, there is a Linux Lite 4.8.0 kernel entry as well as an Ubuntu 4.4.0 kernel entry. I'm guessing that the LL 4.8 kernel is from one of the Lite Tweaks or CLI attempts. The Ubuntu 4.4 kernel would have to be from the attempt made with the links you provided, even though the install message said there were errors.

I checked the box in Grub Customizer for the menu to show, rebooted, and chose the Ubuntu 4.4.0 kernel at boot. After booting I verified that 4.4.0 was in use. I then tried the card reader, and it worked. There do not appear to be any broken packages. Is there anything specific that I should do, or check for, to find any potential problems ?

A side note, the PC will not boot when choosing the LL 4.8 kernel.

[Valtam]

IF you are getting a successful boot into 4.4 kernel, then that is your solution. You will have to stick with that kernel.

[firenice03]

IF you are getting a successful boot into 4.4 kernel, then that is your solution. You will have to stick with that kernel.

I would second this -- you have a working kernel; this is the way it is sometimes - I too have systems that don't make use of the newer stuff.
If anything you could try removing 4.8 as long as dont attempt to boot to it your fine.....