| Summary: | Bootup or trying to install impossible on C51 [GeForce 6150 LE] | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Brian Rockwell <brtians1> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | Keywords: | 6sta1.5, NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | MAGEIA_6_LIVEDVD_i586_GNOME (Date: July 22nd build) | CVE: | |
| Status comment: | |||
| Attachments: | Screen photo of text going by during the loop. | ||
|
Description
Brian Rockwell
2016-07-24 00:43:09 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?). (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 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 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? (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 (Installer component is only for traditional installs) Component:
Installer =>
RPM Packages 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
try to boot with xdriver=modesetting I tried that and removed splash quiet from the script. Attaching Screen print - still looping. Created attachment 8283 [details]
Screen photo of text going by during the loop.
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?
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 fixed a long time ago Resolution:
(none) =>
FIXED |