Ubuntu

obligate to dial alt+F1 to launch startup... bug of splash

Bug #152470 reported by Max on 2007-10-13

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Invalid	Undecided	Unassigned

Bug Description

In the rc release of gutsy at startup I can see the grub but just after that the screen become black (I haven't the "scrollbars"... the splash)...
I am obligated to dial Alt+F1 and, after that, the startup begin ...

I resolved the problem by remove in the grub the kernel's splash option.

I have also another bug ... But it had already discribe in Bug #152027.

kernel module iwlwifi ?? doesn't work ...

After that all it's OK .

$ dmesg | grep wifi
[ 55.356000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_unregister
[ 55.356000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_put
[ 55.356000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_sta_info_get
[ 55.356000] iwlwifi_rc80211_simple: Unknown symbol iwlwifi_ieee80211_rate_control_register

In attachment, my dmesg (with splash kernel option activated)

PS : sorry for my bad english... :-s

See original description

Tags:

Revision history for this message

Max (maxime1986) wrote on 2007-10-13:

my dmesg Edit (25.3 KiB, text/plain)

description:	updated
description:	updated

Max (maxime1986) on 2007-10-17

description:

updated

Revision history for this message

Michael Nagel (nailor) wrote on 2008-07-29:

thanks for reporting! is this still a problem with hardy?

ps: please have a seperate bug report for each problem, this helps to keep track, everything else results in chaos on the long run...

Revision history for this message

Max (maxime1986) wrote on 2008-07-29:

to see how to resolve this bug : http://doc.ubuntu-fr.org/problemes_usplash#methode_2_modification_du_fichier_de_configuration

Revision history for this message

Max (maxime1986) wrote on 2008-07-29:

It was still a problem with hardy just after install.

Revision history for this message

Michael Nagel (nailor) wrote on 2008-11-01:

ping! this has been marked fix commited but last comment says its still a problem...

Revision history for this message

Michael Nagel (nailor) wrote on 2008-12-19:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!