Description of problem: When sel4ecting hardware detection tool from the dual DVD built 30/7 all works well, except when selecting the menu entry "Kernel modules": It makes a mess of the gui and the HDT stops working. All other choices work as expected. Reproducible: Steps to Reproduce:
Whiteboard: (none) => 5alpha2
Assignee: bugsquad => thierry.vignaud
Applies to 32 bit classical iso.
Source RPM: Mageia-5-alpha2-dual-DVD built Wed Jul 30 16:13:04 => Mageia-5-alpha2-dual-DVD built Wed Jul 30 / 32 bit class.built Aug 01
In beta1 first build applicable to 64 bit iso. Should it not be fixed by final time, consider to remove from boot menu.
Whiteboard: 5alpha2 => 5beta1Source RPM: Mageia-5-alpha2-dual-DVD built Wed Jul 30 / 32 bit class.built Aug 01 => Mageia-5-beta1 built 23 Oct 2014
adding release manager then
Source RPM: Mageia-5-beta1 built 23 Oct 2014 => (none)Priority: Normal => release_blockerCC: (none) => ennael1, tmbAssignee: thierry.vignaud => erwanaliasr1
(In reply to Dick Gevers from comment #2) > In beta1 first build applicable to 64 bit iso. > > Should it not be fixed by final time, consider to remove from boot menu. Here it is worse (classical 64bits from October 31st), just selecting the HDT tool made the system reboot the first time I tried. The second time it gave a frozen black screen with a blinking white underscore. Nothing worked, the only way to get out was powering off.
CC: (none) => marja11
it works oerfectly on my side. on all installations
Created attachment 5642 [details] result of "lspci -vv" Yes, I acknowledge that on another machine it does, But not on: https://wiki.mageia.org/en/QA_iso_hardware_list#Notebooks: item dvgevers. I am attaching the result of "lspci -vv"
CC: (none) => eeeemail
Can you switch to the "CLI" mode of HDT and do "show kernel" and show me the result ?
Okay, this is all I see: --- CPU (8 logical / 1 phys) Manufacturer; Intel POroduct: Intel (r) Celeron (R) CPU 1037U @ 1.80GHz CPU Cores: 8 CPU Threads: 2 L2 Cache: 256K Features: 1800 Mhz: x86_64 64 bit SMP HwVIRT System Manufacturer: TOSHIBA Product Name: Satellite C55-A Bios Version: 1.30 Release: 09/16/2013 Memory Size: 12172 MB (12463728 KB) PCI NB devices: 13 Kenel modules hdt> ---
Still valid.
Whiteboard: 5beta1 => 5beta3
Any clue about this one Erwan?
CC: (none) => remi
CC: (none) => sysadmin-bugsComponent: Installer => Release (media or process)
Valid for rc classical iso, build # 1
Whiteboard: 5beta3 => 5rc
Created attachment 6094 [details] hdt-0.5.3-beta1
(In reply to Dick Gevers from comment #9) > Still valid. Can you make a try usb booting the image I've been attaching to this ticket ? tar -xf hdt-0.5.3-beta1.img.xz dd if=hdt-0.5.3-beta1.img. of=/dev/<your_usb_key> Then boot on it. If you could picture the graphical result and then do also the same "show" command from the cli and picture it also. What would help me to understand that bug. Thanks,
I've been able to reproduce your case in my testing case. If for any reason, syslinux isn't able to read the modules.alias (corrupted iso, corrupted file, broken bios), the file is said to be valid and the menuing system is creating stupid entries which generates what your bug reports explains. I've been fixing the modules.alias reading function to report a failure if we cannot read any valid line in it. That should solve your case. The .img I asked you to test doesn't have this fix.
Status: NEW => ASSIGNED
Created attachment 6103 [details] hdt with pcilib fix Can you try this usb bootable image to validate it does work properly with the patch ? Thanks,
The proposed fix: https://svnweb.mageia.org/packages?view=revision&revision=818980
Yes, as soon as I find the time...
I don't understand what you want me to test: there is an image dated 19th but next you say it doesn't have the fix. Then there is a fixed image, but it is only 200 bytes. So is not going to boot. Please clarify.
Created attachment 6104 [details] hdt with pcilib fix Ok sorry for the confusing. I was searching for your problem and asked you to test a build to better understand the situation. Then I found a way to reproduce it and did upload another image with a fix.... Ok I missed the upload. Please find attached the proper image with the fix. Tell me if it's better for you. Cheers,
The "problem" is gone, because now the menu option "Kernel modules" is no longer available. As a result the HDT cannot be messed up anymore. From cli the command 'show kernel' gives this result: --- CPU (8 logical / 1 phys) Manufacturer: Intel Product: Intel (r) Celeron (R) CPU 1037U @ 1.80GHz CPU Cores: 8 CPU Threads: 2 L2 Cache: 256K Features: 1800 Mhz: x86_64 64 bit SMP HwVIRT System Manufacturer: TOSHIBA Product Name: Satellite C55-A Bios Version: 1.30 Release: 09/16/2013 Memory Size: 12172 MB (12463728 KB) PCI NB devices: 13 Kenel modules modules.pcimap and modules.alias files are missing hdt> ---
So that's a good news. I've been able to reproduce your case and the fix is working. That doesn't still explain why you system is not able to read this file. Did you double-check the md5 of your iso ? What's your booting method ?
I booted with the image from attachment 6104 [details]. I a. not aware if this has an md5sum that is verifiable (and I am not using Linux at the moment, just ipad, so I can't check). I wrote the image to a bootable CDRW, because the bios did not allow me in to change the boot order to use USB. But CDRW works as good as USB, I think.
So that's maybe a bios/syslinux issue...
Well the bios has always been accessible, last time was less than ~3 months ago. ItS a cheap machine or I am a fool that I can't access it. So in this respect the bios does not look to be the cause.
The fopen & fread is failing reading data from the bootable device. Syslinux is using int13 from bios do to that and that bug shows that something is clearly wrong here. So the bug is in between bios & syslinux. I'll try to make a POC to show off this bug.
Decreasing priority as seen in last council meeting. Screen is not borked anymore even if the module list does not exist anymore in some cases. Should be worked for Mageia 6
Priority: release_blocker => High
Adding to the Mageia 6 tracker.
Blocks: (none) => 15527
Whiteboard: 5rc => FOR_ERRATATarget Milestone: --- => Mageia 6
Valid for today's classical iso - 32 bits
Whiteboard: FOR_ERRATA => FOR_ERRATA, 6dev1
Valid for today's new isos
Whiteboard: FOR_ERRATA, 6dev1 => 6dev1; FOR_ERRATA
Valid for isos dated 7th March.
Keywords: (none) => 6dev1Whiteboard: 6dev1; FOR_ERRATA => FOR_ERRATA
Valid for classical iso dated 20 May 2016 (64 bit)
Keywords: 6dev1 => 6sta1
Valid for 6RC iso dated 12th July 2016
Keywords: 6sta1 => 6RC
Moving to a Mga7 tracker, because there seems to be no current activity to fix this issue. @ Erwan Of course, that doesn't mean it is forbidden to now work on it again ;-)
Target Milestone: Mageia 6 => Mageia 7Blocks: 15527 => 18932
Keywords: 6RC => FOR_ERRATA5, FOR_ERRATA6Whiteboard: FOR_ERRATA => (none)
Blocks: 18932 => (none)
Valid for M6 sta2 dated 05 12 2016 (back in boot menu, thought it was removed earlier ??)
Keywords: (none) => 6sta2
(In reply to Dick Gevers from comment #34) > Valid for M6 sta2 dated 05 12 2016 (back in boot menu, thought it was > removed earlier ??) If it's still valid with current 6sta2, could you then please add it to https://wiki.mageia.org/en/Mageia_6_Errata ?
Marja this is unclear: it was decided earlier to remove HDT from the install disk boot menu but later it came back again (not clear why). It is not new: here for 3 years. I would rather have it removed until it is fixed or maybe it is already in earlier errata ??
(In reply to Dick Gevers from comment #36) > Marja this is unclear: it was decided earlier to remove HDT from the install > disk boot menu but later it came back again (not clear why). It is not new: > here for 3 years. I would rather have it removed until it is fixed or maybe > it is already in earlier errata ?? Maybe because no one else reported this issue, and because it wouldn't make sense to remove all of HDT if only part of it dysfunctions on only some systems? Btw, you don't seem to have the latest BIOS http://www.toshiba.eu/support/bios/ Did you consider flashing a later version? Was the Toshiba Satellite C55-A with bios v.1.30 the only system on which you've hit this bug, or do you see it on different hardware, too? I've added: In rare cases, selecting 'kernel modules' can make a mess of the GUI and cause HDT to stop working to the errata.
Keywords: FOR_ERRATA6 => IN_ERRATA6CC: sysadmin-bugs => isobuild
(In reply to Marja van Waes from comment #37) > Btw, you don't seem to have the latest BIOS > http://www.toshiba.eu/support/bios/ Very clever that you found this, I wasn't aware of it: updated it but for this bug it makes no difference, though. > Was the Toshiba Satellite C55-A with bios v.1.30 the only system on which > you've hit this bug, or do you see it on different hardware, too? That is the only machine I test on.
Closed since hdt is not (visible) on the isos
Resolution: (none) => OLDStatus: ASSIGNED => RESOLVED