Bug 19040 - Bootup or trying to install impossible on C51 [GeForce 6150 LE]
Summary: Bootup or trying to install impossible on C51 [GeForce 6150 LE]
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: 6sta1.5, NEEDINFO
Depends on:
Blocks:
 
Reported: 2016-07-24 00:43 CEST by Brian Rockwell
Modified: 2019-02-19 16:04 CET (History)
1 user (show)

See Also:
Source RPM: MAGEIA_6_LIVEDVD_i586_GNOME (Date: July 22nd build)
CVE:
Status comment:


Attachments
Screen photo of text going by during the loop. (450.72 KB, image/jpeg)
2016-07-29 05:12 CEST, Brian Rockwell
Details

Description Brian Rockwell 2016-07-24 00:43:09 CEST
Description of problem:  Whether trying to go to Live or do Installation get xt_addrtype message


Version-Release number of selected component (if applicable):mageia-6-livedvd-i586-gnome


How reproducible:  Choose either live or Install Mageia from boot-up menu

hardware
C51 [GeForce 6150 LE]
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+

Steps to Reproduce:
1.  Install DVD
2.  Boot up to menu (I get that far)
3.  During load it gets to this and starts looping:

[126.208949] xt_addrtype:  ipv6 does not support BROADCAST matching
Comment 1 David Walser 2016-07-24 00:56:10 CEST
Guessing this was a kernel change.  I've been seeing this on my Mageia 5 workstation at home, seems like for a few months (maybe since 4.4 kernel?).
Comment 2 Marja Van Waes 2016-07-24 08:37:07 CEST
(In reply to David Walser from comment #1)
> Guessing this was a kernel change.  I've been seeing this on my Mageia 5
> workstation at home, seems like for a few months (maybe since 4.4 kernel?).

Yeah, I see that error in cauldron, too, since many months. However, the message never looped and I never noticed any related problems. After QA-iso-syncing I'll try what happens on this hardware with the  "MAGEIA_6_LIVEDVD_i586_GNOME (Date:  July 22nd build)"-iso Brian used.

@ Brian

In case it is hardware related, do you mind _attaching_ the output of 

   lspcidrake -v

Keywords: (none) => 6RC, NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => tmb
Summary: Bootup or trying to install get ipv6 does not support BROADCAST matching => Bootup or trying to install ends with "ipv6 does not support BROADCAST matching"-loop

Comment 3 Thomas Backlund 2016-07-24 08:41:13 CEST
The "xt_addrtype:  ipv6 does not support BROADCAST matching" is only a kernel informational message when getting probed for ipv6 functions.

It is not a bug

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Brian Rockwell 2016-07-28 14:17:14 CEST
ok - I guess I can translate to - I get that message and then no progress there after.

Regardless on this old nvidia hardware this live media doesn't work.  What do you need or is there a mode I can override to get more detail?
Comment 5 Marja Van Waes 2016-07-28 18:02:45 CEST
(In reply to Thomas Backlund from comment #3)
> The "xt_addrtype:  ipv6 does not support BROADCAST matching" is only a
> kernel informational message when getting probed for ipv6 functions.
> 
> It is not a bug

(In reply to Brian Rockwell from comment #4)
> ok - I guess I can translate to - I get that message and then no progress
> there after.
> 
> Regardless on this old nvidia hardware this live media doesn't work.  What
> do you need or is there a mode I can override to get more detail?

Reopening this report and removing the unrelated kernel message from the summary, then.

* It would still be nice to have a complete lspcidrake -v output attached (from an older install would be fine)

* Can you switch to a different tty when you get that loop?

* If not: Can you boot a Live in text mode, by appending a "3" to the kernel options line in the Live bootloader (click F6 in the boot menu screen, you'll see the kernel options line appear. First make sure the "Boot Mageia" entry is selected and then append a space + a 3, so " 3" to the kernel options line).

If you can log in in text mode, then more is possible to debug things :-)

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)
Summary: Bootup or trying to install ends with "ipv6 does not support BROADCAST matching"-loop => Bootup or trying to install impossible on C51 [GeForce 6150 LE]

Comment 6 Marja Van Waes 2016-07-28 18:03:29 CEST
(Installer component is only for traditional installs)

Component: Installer => RPM Packages

Comment 7 Brian Rockwell 2016-07-28 21:29:18 CEST
I tried getting to console.  Eventually it shows, but is flashing.  Something is looping in the background.  Typing doesn't register.

>>Can you boot a Live in text mode, by appending a "3" to the kernel options line in the Live bootloader (click F6 in the boot menu screen, you'll see the kernel options line appear. First make sure the "Boot Mageia" entry is selected and then append a space + a 3, so " 3" to the kernel options line).

I tried this, but doing something wrong.  It still goes to graphical and loops.  I tried put the 3 at the front of the parameters and in the back.  Also tried "Text Mode" and it went to graphical
Comment 8 Thomas Backlund 2016-07-28 22:03:54 CEST
try to boot with

xdriver=modesetting
Comment 9 Brian Rockwell 2016-07-29 05:11:06 CEST
I tried that and removed splash quiet from the script.

Attaching Screen print - still looping.
Comment 10 Brian Rockwell 2016-07-29 05:12:00 CEST
Created attachment 8283 [details]
Screen photo of text going by during the loop.
Comment 11 Marja Van Waes 2016-07-29 10:00:45 CEST
Comment on attachment 8283 [details]
Screen photo of text going by during the loop.

i don't understand what gdm-session-worker is doing there.

maybe for a live iso apending ' 3' is not the correct way to get runlevel 3?

could you try again and apend ' systemd.unit=multi-user.target' instead?
Comment 12 Marja Van Waes 2016-07-29 10:03:59 CEST
oops, sorry, i read the bugzilla mail with your reply on my phone and had neither seen tmb's comment, nor noticed you replied him when i went staight from the mail to the attachment
Comment 13 Brian Rockwell 2019-02-19 16:04:07 CET
fixed a long time ago

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED


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