#null

Message

GWilliam · Post by **GWilliam** » Sun May 27, 2007 10:02 pm

#NULL

RayDude · Post by **RayDude** » Mon May 28, 2007 3:15 am

GWilliam wrote:I've been using framebuffer splash for a while now (probably about a year).

During boot, I used to be able to see init script messages by pressing <F2>.

I've just discovered that this no longer works.

I've no idea why. Everything else regarding framebuffer, tty, and init setup seems to work.

I don't even know where to begin troubleshooting this. I've gone through all the FAQs, Wikis, How-Tos, and other documentation, checked everything step by step, unmergeg and re-emerged splashutils, splash themes, created more initial ram device images, etc.--all to no avail.

What should I check?

--And why the heck would this feature just stop working? It's been working.

Did you change your kernel configuration to remove /dev/input support?

Code: Select all

   Device Drivers  --->  Input device support  ---> [*] Event interface

Raydude

GWilliam · Post by **GWilliam** » Mon May 28, 2007 4:35 am

#NULL

RayDude · Post by **RayDude** » Mon May 28, 2007 5:23 am

GWilliam wrote:
Code: Select all
Did you change your kernel configuration to remove /dev/input support?
I didn't think to check that! However, I just checked my current kernel config and yeah, I've got the event interface built in.

I'll keep playing around with this and maybe install an old installation of Gentoo from a previous backup on another filesystem and test it. I don't know what that would accomplish, but I'm at the point now at which I'm pretty much grasping at straws anyway.

Either the keyboard is not being read during boot or whatever it is that provides the actual functionality isn't working.

The keyboard is a USB keyboard, so maybe the kernel... no... I'm not building USB support as modules. I'm statically linking EVERYTHING--no modules--except for nVidia's proprietary drivers.

I'll bet you updated a package, like UDEV or something and something got changed.

Good luck!

Raydude

GWilliam · Post by **GWilliam** » Tue May 29, 2007 1:07 am

#NULL

JeliJami · Post by **JeliJami** » Tue May 29, 2007 9:01 am

can you switch to verbose mode with the <Alt><F1> combination?

GWilliam · Post by **GWilliam** » Thu May 31, 2007 4:41 am

#NULL

JeliJami · Post by **JeliJami** » Thu May 31, 2007 7:42 am

GWilliam wrote:
can you switch to verbose mode with the <Alt><F1> combination?
Yes! Yes, I can. <Alt><F1> gets me verbose mode.

I bet you use a USB keyboard. The <F2> key still works with a PS/2 keyboard.

GWilliam · Post by **GWilliam** » Mon Jun 04, 2007 10:24 pm

#NULL

bulsa · Post by **bulsa** » Wed Jun 27, 2007 9:01 pm

Are there any updates on this, because I have exactly the same problem with 2.6.20-gentoo-r8?

yuwy · Post by **yuwy** » Mon Jul 02, 2007 1:10 am

hmm strange, i use a usb keyboard and it works fine as far as the f2 key is concerned for verbose mode.

GWilliam · Post by **GWilliam** » Tue Jul 03, 2007 12:12 am

#NULL

chrsin · Post by **chrsin** » Fri Aug 10, 2007 8:20 am

Hi i have followed they guide at http://gentoo-wiki.com/HOWTO_fbsplash and the installation wen't flawless.

But i do have one problem. When i try to switch from silent to verbose (i press F2) nothing happens (same happens when trying the other way around)
I think i have looked everywhere for a solution, and i have been asking the question at #gentoo for a couple of days now, even searched the https://bugs.gentoo.org site but to no avail.

I have CONFIG_INPUT_EVDEV (event interface) activated in the kernel.

I'm running:
gentoo-sources-2.6.21-r4 on amd64.
have splashutils-1.4.2

my gentoo grub entry:
title=Gentoo Linux (2.6.21-r4)
root (hd0,0)
kernel /boot/kernel-2.6.21-r4 splash=silent,fadein,theme:gentoo vga=792 quiet CONSOLE=/dev/tty1 fbcon=scrollback:128K
initrd (hd0,0)/boot/fbsplash-gentoo

not sure what information you would need more but ask and i'll supply it.(no i don't supply passwords)

Any help in what could be a solution is appreciated.

Tolstoi · Post by **Tolstoi** » Sun Aug 12, 2007 6:48 pm

Did you try this?
kernel /boot/kernel-2.6.21-r4 splash=silent,fadein,theme:gentoo vga=792,ywrap,mtrr2 quiet CONSOLE=/dev/tty1 fbcon=scrollback:128K

chrsin · Post by **chrsin** » Sun Aug 12, 2007 11:12 pm

Hey thanks for the reply, i have tried it now, but to no avail.
Aren't those switches for vesa-tng? im using vesa since im on x86_64.

shaumux · Post by **shaumux** » Mon Aug 13, 2007 2:32 am

Are you using USB Keyboard?

chrsin · Post by **chrsin** » Mon Aug 13, 2007 12:38 pm

shaumux yes i am.

shaumux · Post by **shaumux** » Mon Aug 13, 2007 1:02 pm

I think you need to build the driver for the USB HID and the keyboard in the kernel.
Also if there is any option in the bios to initialise the HID device at boot enable them.

chrsin · Post by **chrsin** » Mon Aug 13, 2007 2:46 pm

Hi Shaumux, you could be on to something.

I have in my kernel gentoo-sources-2.6.22-r2

Device drivers --> HID Devices
<*> USB Human Interface Device (full HID) support

I could instead turn that one of and insted do

Device drivers --> HID Devices --> USB HID Boot Protocol drivers
<*> USB HIDBP Keyboard (simple Boot) support

but the warning in the help section is a bit unnerving

Say Y here only if you are absolutely sure that you don't want
to use the generic HID driver for your USB keyboard and prefer
to use the keyboard in its limited Boot Protocol mode instead.

This is almost certainly not what you want. This is mostly
useful for embedded applications or simple keyboards.

To compile this driver as a module, choose M here: the
module will be called usbkbd.

If even remotely unsure, say N

In the Device drivers --> USB support section i have turned on anything i can possible image could have anything to do with my keyboard (most is default)

I have looked around my bios for something usefull but could find nothing about USB that wasn't enabled.
Im using PHOENIX v6.00PG

Tolstoi · Post by **Tolstoi** » Mon Aug 13, 2007 3:07 pm

Tolstoi wrote:Did you try this?
kernel /boot/kernel-2.6.21-r4 splash=silent,fadein,theme:gentoo vga=792,ywrap,mtrr2 quiet CONSOLE=/dev/tty1 fbcon=scrollback:128K

When you use vega you should use for example video=vesafb:1280x1024-24@60,ywrap,mtrr2 etc. of course with your preferred resolution, I think.

shaumux · Post by **shaumux** » Mon Aug 13, 2007 4:32 pm

Tolstoi wrote:
Tolstoi wrote:Did you try this?
kernel /boot/kernel-2.6.21-r4 splash=silent,fadein,theme:gentoo vga=792,ywrap,mtrr2 quiet CONSOLE=/dev/tty1 fbcon=scrollback:128K
When you use vega you should use for example video=vesafb:1280x1024-24@60,ywrap,mtrr:2 etc. of course with your preferred resolution, I think.

You forgot the colons there

Tolstoi · Post by **Tolstoi** » Mon Aug 13, 2007 4:37 pm

shaumux wrote:
Tolstoi wrote:
Tolstoi wrote:Did you try this?
kernel /boot/kernel-2.6.21-r4 splash=silent,fadein,theme:gentoo vga=792,ywrap,mtrr2 quiet CONSOLE=/dev/tty1 fbcon=scrollback:128K
When you use vega you should use for example video=vesafb:1280x1024-24@60,ywrap,mtrr:2 etc. of course with your preferred resolution, I think.
You forgot the colons there

Yes, wright. Sorry!

shaumux · Post by **shaumux** » Mon Aug 13, 2007 4:39 pm

chrsin wrote:I have looked around my bios for something usefull but could find nothing about USB that wasn't enabled.
Im using PHOENIX v6.00PG

I am absolutely sure that the problem is with the USB keyboard.
You can verify by connecting a ps2 keyboard and checking.
I think the problem is with the time of initialisation of the device.

chrsin · Post by **chrsin** » Mon Aug 13, 2007 6:36 pm

Tolstoi, the instructions you give are for vesa-tng, i have booted with them and i get low resolution and everything

Shaumux i think your right on the spot (or what ever one says

)

But i don't see any solution for it. So i'm going to live with it.

Thx alot for the feedback Tolstoi and Shaumux.

Tolstoi · Post by **Tolstoi** » Mon Aug 13, 2007 7:02 pm

Maybe this thread http://forums.gentoo.org/viewtopic-t-57 ... board.html helps. It points to the issue that Shaumux meant.

#null

#null

Re: Bootsplash: Press F2 for verbose mode no longer works

gensplash problem