Also, if it's supposed to change splash=silent to splash quiet, what I'm seeing now is splash quiet splash=silent.  So it's not removing the old splash=silent.

any news?

ping

CC: (none) => alien

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

We always have Cauldron :o)  It's just not open at the moment.

Given Maarten's ping on the 18th, I'm guessing this wasn't fixed.

given that this was an upgrade issue, i guess we can't fix this now.

better close as wontfix now.

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

It can be fixed for Mageia 3.  Let's give tv/tmb a chance.

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

i donno, iinm, this is a change between mga1 and mga2 wrt to kernel append parameters. AFAIK the new installs do it correctly, so since this is only during upgrade, and only mga2 to mga3 is supported, i see no solution for this.

unless i'm mistaken here, of course.

(In reply to comment #8)
> i donno, iinm, this is a change between mga1 and mga2 wrt to kernel append
> parameters. AFAIK the new installs do it correctly, so since this is only
> during upgrade, and only mga2 to mga3 is supported, i see no solution for this.
> 
> unless i'm mistaken here, of course.

Maarten, I'm not sure we're talking about the same problem.  My original bug (Comment 0) is for a problem that will affect any upgrade.  It has nothing to do with with new installs.

It sounds like you're talking about the Comment 1 problem, which yes, is irrelevant now.

(In reply to comment #9)
> Maarten, I'm not sure we're talking about the same problem.  My original bug
> (Comment 0) is for a problem that will affect any upgrade.  It has nothing to
> do with with new installs.
> 
> It sounds like you're talking about the Comment 1 problem, which yes, is
> irrelevant now.

ah, mea culpa, i missed it :-(

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Still valid in current Cauldron.

The video mode from my old kernel was not copied to my new one doing a Mageia 2 -> Mageia 3 upgrade.  Also, "splash" was added to the Append line of my new kernel when it was not there in the old one.

Keywords: NEEDINFO => (none)
Source RPM: drakx-installer-stage2-14.19-1.mga2.src.rpm => drakx-installer-stage2-15.18-2.mga3.src.rpm

it might not be easy to migrate those over... what with video drivers changing and kms and such. and dracut changes, etc... maybe it's better to just have everyone the same options?

well, i don't know, its just my idea...

Within the confines of GRUB, it's as simple as copying things like "vga=791" from the line in /boot/grub/menu.lst.  As long as you aren't changing bootloaders, should be relatively simple.  Really, video drivers and KMS has nothing to do with this either.

Still valid in current Cauldron as of Saturday, April 20.

Tracing through the code of what happens when a new kernel is installed, it looks like the bug would be in /usr/lib/libDrakX/bootloader.pm from drakxtools-backend (from drakxtools).  It's not apparent exactly where the bug is.  It looks like it's at least trying to do the right thing in write_grub().

As of Mageia 3, it also adds "splash" for the new kernel entry after the upgrade, even when your previous one didn't have it.  It also should not be doing that.

Still valid in current Cauldron as of Friday, December 15.

Still valid with Mageia 5 I suppose?

Keywords: (none) => NEEDINFO
Status: REOPENED => NEW
Hardware: i586 => All

It was as of January at least.  tmb fixed something just this week that may have been related to this issue (mentioned in the council meeting), so it needs to be checked again.

Testing in i586 with MGA5

CC: (none) => neoser10

Presumed fixed

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