Bug 27847

Thank you for reporting

Could you try using Mageia 8 beta 2 ?

CC: (none) => fri

(In reply to Morgan Leijström from comment #1)
> Thank you for reporting
> 
> Could you try using Mageia 8 beta 2 ?

Thank you for quick reply.

I didn't know Mageia 8 beta 2 existed. How can I access it?

https://www.mageia.org/en/downloads/prerelease/
Your testing is very welcome :)

Also see
https://wiki.mageia.org/en/Mageia_8_Release_Notes
https://wiki.mageia.org/en/Mageia_8_Errata

(In reply to Morgan Leijström from comment #3)
> https://www.mageia.org/en/downloads/prerelease/
> Your testing is very welcome :)
> 
> Also see
> https://wiki.mageia.org/en/Mageia_8_Release_Notes
> https://wiki.mageia.org/en/Mageia_8_Errata

Sorry for delay.(medical problems)

I have now tried Mageia 8 beta.


The machine now does the following

 1.boot from USB stick
2.detects USB device
3.Loads into memory
4.asks for language, I set english british, click next
5.displayes license agreement I tick accept and click next
6.message "installing hard drive controller
7 .screen to select keyboard. I select UK and click next.
8.screen displays
         "An error occurred"
"Can't call method"first_usable_sector" on unblessed reference."

Hope you are well

Thank you - we now have an error message.

Seem to be something for the kernel and drivers team

Summary: instaler does not find eMMC storage on Lenovo IdeaPad 1 (14",05) laptop => Classic Installer fail to use eMMC storage on Lenovo IdeaPad 1
Assignee: bugsquad => kernel
Version: 7 => Cauldron

Alan, with a second, formatted USB stick to hand (FAT formatted is OK), please repeat the process. When you get to the error message, press Ctrl-Alt-F2. That should switch to a text console. Insert the second USB stick and at the command prompt enter the command

  bug

That should write a file named report.bug to the USB stick. Compress that file (xz is best, but other methods are OK) and attach it to this bug report.

Keywords: (none) => NEEDINFO
CC: (none) => mageia

(In reply to Martin Whitaker from comment #6)
> Alan, with a second, formatted USB stick to hand (FAT formatted is OK),
> please repeat the process. When you get to the error message, press
> Ctrl-Alt-F2. That should switch to a text console. Insert the second USB
> stick and at the command prompt enter the command
> 
>   bug
> 
> That should write a file named report.bug to the USB stick. Compress that
> file (xz is best, but other methods are OK) and attach it to this bug report.


Ctrl-Alt-F2    does nothing. I don't think it's loaded the keyboard. When I select UK keyboard, it flash a message so fast I can't read it, then 
displays the message

Can't call method etc.

If it were going to, the keyboard should be working by the time the installer presents the first dialogue screem - Select Keyboard just chooses the correct keyboard layout (it assumes a US keyboard before then). So that's another problem.

Could you try one of the 8-beta2 Live ISOs and boot the live system. If that works, open a terminal window, and type

  su -
  drakbug_report | xz > /home/live/report.xz

then attach the resulting report.xz file to this bug report.

(In reply to Martin Whitaker from comment #8)
> If it were going to, the keyboard should be working by the time the
> installer presents the first dialogue screem - Select Keyboard just chooses
> the correct keyboard layout (it assumes a US keyboard before then). So
> that's another problem.
> 
> Could you try one of the 8-beta2 Live ISOs and boot the live system. If that
> works, open a terminal window, and type
> 
>   su -
>   drakbug_report | xz > /home/live/report.xz
> 
> then attach the resulting report.xz file to this bug report.



darkbug etc.

response 

bash: darkbug_report: command not found


A silly thought     Could I have a 32 bit machine???   Because it's brand new current production I just assumed it's 64 bit.

It is the dark time off the year yes, but "drak"... not "dark"...   ;)

Installer would have warned you early if trying 64 bit on 32 bit machine.

Created attachment 12115 [details]
report file

(In reply to Alan Moss from comment #11)
> Created attachment 12115 [details]
> report file



I'm well past my knowledge and ability with computers. So hope I managed to add attachment.  I'v never learned to work in a terminal.

Thanks Alan, the attachment is fine. Looking through it, there's no sign your eMMC device has been detected. One more piece of information please. Again boot from one of the 8-beta2 Live ISOs, open a terminal window, and type

  su -
  journalctl -b | xz > /home/live/journal.xz

then attach the resulting journal.xz file to this bug report.

Created attachment 12116 [details]
xz file

I can see no mention of the eMMC device there either. Over to our kernel and drivers maintainers to see if they can suggest anything.

(In reply to Martin Whitaker from comment #15)
> I can see no mention of the eMMC device there either. Over to our kernel and
> drivers maintainers to see if they can suggest anything.

two of my qestions

1st question  Is this a machine or Mageia problem?

so I have tried to install Linux Mint - 20 and very quickly came to a screen that said
       "you need at least 12.5 gh space to install Linux Mint. This computer has only 4 gh"

So It must be a problem with the machine.

2nd question    Can there be something in the BIOS settings that stop non Windowes software from seeing the eMMC memory?????  

I had to disable secure boot to get the computer to look at a USB stick.

I've found someone else asking the same question:

https://askubuntu.com/questions/1301390/lenovo-ideapad-1-11ada05-can-i-use-the-emmc

Do any eMMC device names show up?

ls -l /dev/mmcblk*

CC: (none) => davidwhodgins

Also try "modprobe -v mmc_block", then try the "ls -l /dev/mmcblk*" and
partitioning tools again.

(In reply to Dave Hodgins from comment #19)
> Also try "modprobe -v mmc_block", then try the "ls -l /dev/mmcblk*" and
> partitioning tools again.

comment 18

ls -l /dev/mmcblk*

ls: canot access @/dev/mmcblk*:no such file or directory.

comment 19

modprobe -v mmc_block

insmod /lib/modules/5.9.12-desktop-1.mag8/kernel/drivers/mmc/core/mmc_core.ko.xz
modprobe: ERROR: could not insert 'mmc_block': operation not permitted

su
modprob etc

insmod /lib/module/5.9,12-desktop-1.mga8/kernel/drivers/mmc/core/mmc_core.ko.xz
insmod /lib/module/5.9,12-desktop-1.mga8/kernel/drivers/mmc/core/mmc_block.ko.xz

ls -l /dev/mmcblk*

ls canot access '/dev/mmcblk no such file etc.



how can I find the two "insmod ------------------.xz  to attach them using Dolphin because I am totaly lost trying to use the command line

After the modprobe/insmod commands as root in the live did you try again to use the partitioning tool (local disks) in mcc? ... or the hardware detect as you did last night?
Any mention of the eMMC device?
If there is try the install from the desktop icon.

Note that if you reboot the live you will need to use those commands again as changes are lost between boots.

(In reply to Barry Jackson from comment #21)
> After the modprobe/insmod commands as root in the live did you try again to
> use the partitioning tool (local disks) in mcc? ... or the hardware detect
> as you did last night?
> Any mention of the eMMC device?
> If there is try the install from the desktop icon.
> 
> Note that if you reboot the live you will need to use those commands again
> as changes are lost between boots.

I'v tried now. There is no mention of mmc storage memory in mcc

I have now returned the computer to seller under Ebay return policy.

I would like to thank everyone who have tried to resolve my problem.

May I suggest that a warning be added to Hardware requirements section on the Support page. To avoid computers with eMMC storage memory.

Again THANK YOU ALL


Alan Moss

Thank you for the testing and report!
Sorry we could not find a quick solution.
Have a happy christmas :)

Leaving this bug open for others to chime in to.

I had similar issue with another Lenovo Ideapad.

https://askubuntu.com/questions/946291/installing-ubuntu-on-lenovo-ideapad-710s-13ikb

But I can't find anything like that about Ideapad 1. The only BIOS version available is for Windows 10.

CC: (none) => mageia

see also bug 30096 (enhancement request)

in this instance, the error:

8.screen displays
         "An error occurred"
"Can't call method "first_usable_sector" on unblessed reference." 

is repeatable on multiple types of storage device, (incl MBR Virtualbox), so the requirement for specific hardware may be overcome for confirmation and repeatable testing purposes.

perhaps they are related?

on a similar/related note, a google search for "Can't call method "first_usable_sector" on unblessed reference" turns up several (5) posts from pclinuxos from mid 2019 onwards.

CC: (none) => westel

Hi Ben,
No, I don't think they are related. That message will appear when one of the drakx tools is scanning for disks and fails to find any. It's a bug - the tool should detect the condition and output a more user-friendly message, but it can occur for different reasons. In this bug I think the problem is that the Linux kernel doesn't (or didn't at that time) support the eMMC device.