Bug 28127 - i586 Classical install does not recognize USB install medium as installer meduim
Summary: i586 Classical install does not recognize USB install medium as installer meduim
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: IN_ERRATA8
Depends on:
Blocks:
 
Reported: 2021-01-17 04:23 CET by Ben McMonagle
Modified: 2021-02-07 14:32 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Ben McMonagle 2021-01-17 04:23:26 CET
Description of problem: attempting to add extra applications failed as the USB install medium was not recognized.

eg: with install meduim inserted.

urpmi parole
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Core Release (Installer)")
  libgtop2                       2.40.0       3.mga8        i586    
  libgtop2.0_11                  2.40.0       3.mga8        i586    
  libtaglib_c0                   1.11.1       6.mga8        i586    
  libxfce4ui                     4.16.0       1.mga8        i586    
  libxfce4ui2_0                  4.16.0       1.mga8        i586    
  libxfce4util-i18n              4.16.0       1.mga8        i586    
  libxfce4util7                  4.16.0       1.mga8        i586    
  libxfconf0_3                   4.16.0       1.mga8        i586    
  parole                         4.16.0       1.mga8        i586    
  xfconf                         4.16.0       1.mga8        i586    
5.9MB of additional disk space will be used.
1.4MB of packages will be retrieved.
Proceed with the installation of the 10 packages? (Y/n) y
Please insert the medium named "Core Release (Installer)"

this does not occur with the x86_64 install and medium.

Version-Release number of selected component (if applicable):
ISO:  Mageia-8-rc-i586.iso
DATE: Wed 13 Jan 2021 11:27:14 PM CET

How reproducible:


Steps to Reproduce:
1.install a single DE from above .iso
2.insert install USB medium and attempt to add extra applications
3.
Ben McMonagle 2021-01-17 04:24:02 CET

Keywords: (none) => 8rc1
Target Milestone: --- => Mageia 8

Comment 1 Lewis Smith 2021-01-17 10:53:55 CET
Thanks for the report, Ben.
Assigning to MGAtools grouup; CC'ing ISO team in case the problem is there.

CC: (none) => isobuild
Assignee: bugsquad => mageiatools

Comment 2 Morgan Leijström 2021-01-17 11:22:51 CET
This really should work.

Priority: Normal => High
CC: (none) => fri

Comment 3 Manuel Hiebel 2021-01-17 12:17:42 CET
I'm not sure this was working on previous releases
Comment 4 Martin Whitaker 2021-01-17 20:20:42 CET
This doesn't work (and as Manuel rightly says, has never worked), because the protective partition on the 32-bit ISOs starts at sector 1, not sector 0. That prevents the iso9660 filesystem from being automatically detected and mounted.

Starting the protective partition at sector 1 avoids a bug in some old BIOSs - see bug 5036 - so we can't change that.

If you manually mount the raw device (e.g. 'mount /dev/sdb /mnt') then it will be detected and used.

I don't know any way to fix this without re-introducing bug 5036.

CC: (none) => mageia

Comment 5 Morgan Leijström 2021-01-17 20:30:23 CET
Have never worked, not critical, no solution in sight -> setting normal prio.

I suggest to keep bug open so others experiencing this see it, and if someone may get a bright idea...

With work, i guess our tools could be made to do the "manual" mounting in previous post when needed, but our devs have full hands...


Until then, For Errata, I presume?

Possibly even in documentation saying that installer IOS repo do not work on 32 bit?

Keywords: 8rc1 => FOR_ERRATA7, FOR_ERRATA8
Target Milestone: Mageia 8 => ---
Priority: High => Normal

Comment 6 Martin Whitaker 2021-01-17 23:13:36 CET
It does work if it's on DVD, just not on USB.
Morgan Leijström 2021-02-07 14:32:40 CET

Keywords: FOR_ERRATA7, FOR_ERRATA8 => IN_ERRATA8


Note You need to log in before you can comment on or make changes to this bug.