[gentoo-user] fbsplash problems

[gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

 Hello 
 I am trying to get fbsplash to work and am stuck. I have followed the
directions on the gentoo-wiki site but still no luck. Im using vesafb
with a 2.6.12-r6 kernel. my grub.conf looks like this 

title=Gentoo-2.6.12-r6-fbsplash
root (hd0,0)
kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
video=vesafb:ywrap,mtrr,1024x768@70 spla$
initrd (hd0,0)/fbsplash-gentoo-1024x768

 It tries to go to it but it just stays in text mode with no splash it
doesnt even go to 1024x768. I get this when booting

 Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1

 Im not sure what that means though. Any ideas, thanks.
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Ramón Gutiérrez]

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

I think the Fbsplash isnt working in 2.6-rx dont know why but i cant get it 
to work neither.

On 7/19/05, LostSon <lostson@lostsonsvault.org> wrote: 
> 
> Hello
> I am trying to get fbsplash to work and am stuck. I have followed the
> directions on the gentoo-wiki site but still no luck. Im using vesafb
> with a 2.6.12-r6 kernel. my grub.conf looks like this
> 
> title=Gentoo-2.6.12-r6-fbsplash
> root (hd0,0)
> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> video=vesafb:ywrap,mtrr,1024x768@70 spla$
> initrd (hd0,0)/fbsplash-gentoo-1024x768
> 
> It tries to go to it but it just stays in text mode with no splash it
> doesnt even go to 1024x768. I get this when booting
> 
> Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
> splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1
> 
> Im not sure what that means though. Any ideas, thanks.
> --
> LostSon
> 
> http://www.lostsonsvault.org
> 
> Fox Cities Linux User Group = www.foxlug.org <http://www.foxlug.org>
> 
> 
> BodyID:45422903.2.n.logpart (stored separately)
> 
> 


-- 
Ramon Gutierrez

[-- Attachment #2: Type: text/html, Size: 1440 bytes --]

Re: [gentoo-user] fbsplash problems

[Holly Bostick]

LostSon schreef:
>  Hello 
>  I am trying to get fbsplash to work and am stuck. I have followed the
> directions on the gentoo-wiki site but still no luck. Im using vesafb
> with a 2.6.12-r6 kernel. my grub.conf looks like this 
> 
> title=Gentoo-2.6.12-r6-fbsplash
> root (hd0,0)
> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> video=vesafb:ywrap,mtrr,1024x768@70 spla$
> initrd (hd0,0)/fbsplash-gentoo-1024x768
> 
>  It tries to go to it but it just stays in text mode with no splash it
> doesnt even go to 1024x768. I get this when booting
> 
>  Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
> splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1
> 
>  Im not sure what that means though. Any ideas, thanks.

That means, afaik, that there is an error in the syntax of that specific 
line, and you need to fix it, as GRUB can't figure out or even guess 
what the heck you mean.

For reference, here's my kernel command line (splash does work for me):

kernel /vmlinuz root=/dev/hda5 
video=vesafb-tng:ywrap,mtrr,pmipal,1280x1024-32@60 
splash=silent,theme:emergence quiet CONSOLE=/dev/tty1

The (main) difference I see is that you have no bit depth specified in 
your video= command, but perhaps vesafb doesn't need one. I also see 
that I'm using pmipal and you aren't but since I don't even know what 
that is anyway, I'll assume it's not important.

So what I'm wondering is-- you're asking for vesafb in the command line, 
but is that actually the framebuffer that you've selected in the kernel 
(in menuconfig, Device Drivers section =>Graphics support, what is the 
actual name of the vesa framebuffer being built)?

Mine looks like

VESA VGA graphics support

VESA driver type (vesafb-tng)  --->

Does it actually say 'vesafb' between your parentheses (as I believe 
that vesafb-tng is the default if you enable VESA VGA graphics support)?

Also what version of splashutils, did you recently upgrade the kernel 
from 2.6.11, and if so, did you re-generate the splash initrd (there's 
an einfo to this effect in the recent splashutils ebuilds)?

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 2685 bytes --]

On Tue, 2005-07-19 at 17:50 +0200, Holly Bostick wrote:
> LostSon schreef:
> >  Hello 
> >  I am trying to get fbsplash to work and am stuck. I have followed the
> > directions on the gentoo-wiki site but still no luck. Im using vesafb
> > with a 2.6.12-r6 kernel. my grub.conf looks like this 
> > 
> > title=Gentoo-2.6.12-r6-fbsplash
> > root (hd0,0)
> > kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > video=vesafb:ywrap,mtrr,1024x768@70 spla$
> > initrd (hd0,0)/fbsplash-gentoo-1024x768
> > 
> >  It tries to go to it but it just stays in text mode with no splash it
> > doesnt even go to 1024x768. I get this when booting
> > 
> >  Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
> > splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1
> > 
> >  Im not sure what that means though. Any ideas, thanks.
> 
> That means, afaik, that there is an error in the syntax of that specific 
> line, and you need to fix it, as GRUB can't figure out or even guess 
> what the heck you mean.
> 
> For reference, here's my kernel command line (splash does work for me):
> 
> kernel /vmlinuz root=/dev/hda5 
> video=vesafb-tng:ywrap,mtrr,pmipal,1280x1024-32@60 
> splash=silent,theme:emergence quiet CONSOLE=/dev/tty1
> 
> The (main) difference I see is that you have no bit depth specified in 
> your video= command, but perhaps vesafb doesn't need one. I also see 
> that I'm using pmipal and you aren't but since I don't even know what 
> that is anyway, I'll assume it's not important.
> 
> So what I'm wondering is-- you're asking for vesafb in the command line, 
> but is that actually the framebuffer that you've selected in the kernel 
> (in menuconfig, Device Drivers section =>Graphics support, what is the 
> actual name of the vesa framebuffer being built)?
> 
> Mine looks like
> 
> VESA VGA graphics support
> 
> VESA driver type (vesafb-tng)  --->
> 
> Does it actually say 'vesafb' between your parentheses (as I believe 
> that vesafb-tng is the default if you enable VESA VGA graphics support)?
> 
> Also what version of splashutils, did you recently upgrade the kernel 
> from 2.6.11, and if so, did you re-generate the splash initrd (there's 
> an einfo to this effect in the recent splashutils ebuilds)?
> 
> HTH,
> Holly

 Ok i tried adding that in my line but still no luck alot of what im
getting is errors about not being able to load config files and fd0 or
fb0 it goes by so fast and i cannot find these error messages in any of
my logs either. Im using splashutils-1.1.9.7 btw, thanks
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[cafairle]

If you use the nvidia driver, you might have problems. I tried using fbsplash
with 2.6.12-r6 and -r4 using vidia 7667 drivers, but no luck with rivafb, vesafb
or nvidiafb. I then searched nvidia forums and read their readme and apparently
their driver deosnt support framebuffering very well.

So after spending a day messing with and research fb'ing, i gots nothing but
messed up fonts in xfce which i'm STILL trying to fix and actaully, i might send
a email to the list about it 

chris

Quoting LostSon <lostson@lostsonsvault.org>:

> On Tue, 2005-07-19 at 17:50 +0200, Holly Bostick wrote:
> > LostSon schreef:
> > >  Hello 
> > >  I am trying to get fbsplash to work and am stuck. I have followed the
> > > directions on the gentoo-wiki site but still no luck. Im using vesafb
> > > with a 2.6.12-r6 kernel. my grub.conf looks like this 
> > > 
> > > title=Gentoo-2.6.12-r6-fbsplash
> > > root (hd0,0)
> > > kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > > video=vesafb:ywrap,mtrr,1024x768@70 spla$
> > > initrd (hd0,0)/fbsplash-gentoo-1024x768
> > > 
> > >  It tries to go to it but it just stays in text mode with no splash it
> > > doesnt even go to 1024x768. I get this when booting
> > > 
> > >  Kernel command line: root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768@70
> > > splash=silent,theme:gentoo quiet CONSOLE=/dev/tty1
> > > 
> > >  Im not sure what that means though. Any ideas, thanks.
> > 
> > That means, afaik, that there is an error in the syntax of that specific 
> > line, and you need to fix it, as GRUB can't figure out or even guess 
> > what the heck you mean.
> > 
> > For reference, here's my kernel command line (splash does work for me):
> > 
> > kernel /vmlinuz root=/dev/hda5 
> > video=vesafb-tng:ywrap,mtrr,pmipal,1280x1024-32@60 
> > splash=silent,theme:emergence quiet CONSOLE=/dev/tty1
> > 
> > The (main) difference I see is that you have no bit depth specified in 
> > your video= command, but perhaps vesafb doesn't need one. I also see 
> > that I'm using pmipal and you aren't but since I don't even know what 
> > that is anyway, I'll assume it's not important.
> > 
> > So what I'm wondering is-- you're asking for vesafb in the command line, 
> > but is that actually the framebuffer that you've selected in the kernel 
> > (in menuconfig, Device Drivers section =>Graphics support, what is the 
> > actual name of the vesa framebuffer being built)?
> > 
> > Mine looks like
> > 
> > VESA VGA graphics support
> > 
> > VESA driver type (vesafb-tng)  --->
> > 
> > Does it actually say 'vesafb' between your parentheses (as I believe 
> > that vesafb-tng is the default if you enable VESA VGA graphics support)?
> > 
> > Also what version of splashutils, did you recently upgrade the kernel 
> > from 2.6.11, and if so, did you re-generate the splash initrd (there's 
> > an einfo to this effect in the recent splashutils ebuilds)?
> > 
> > HTH,
> > Holly
> 
>  Ok i tried adding that in my line but still no luck alot of what im
> getting is errors about not being able to load config files and fd0 or
> fb0 it goes by so fast and i cannot find these error messages in any of
> my logs either. Im using splashutils-1.1.9.7 btw, thanks
> -- 
> LostSon
> 
> http://www.lostsonsvault.org
> 
> Fox Cities Linux User Group = www.foxlug.org
> 




----------------------------------------
This mail sent through www.mywaterloo.ca
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Christoph Eckert]

> So after spending a day messing with and research fb'ing, i
> gots nothing but messed up fonts in xfce which i'm STILL
> trying to fix and actaully, i might send a email to the
> list about it

please do so, I have the same troubles :( .


Best regards


    ce

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Richard Fish]

LostSon wrote:

> Hello 
> I am trying to get fbsplash to work and am stuck. I have followed the
>directions on the gentoo-wiki site but still no luck. Im using vesafb
>with a 2.6.12-r6 kernel. my grub.conf looks like this 
>
>title=Gentoo-2.6.12-r6-fbsplash
>root (hd0,0)
>kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
>video=vesafb:ywrap,mtrr,1024x768@70 spla$
>initrd (hd0,0)/fbsplash-gentoo-1024x768
>
>  
>

Um, is fbsplash-gentoo-1024x768 in the /boot directory?  Is your root 
filesystem /dev/hda1?

If the answer to both is yes, then the initrd line should say:

initrd (hd0,0)/boot/fbsplash-gentoo-1024x768

-Richard


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Richard Fish]

Ramón Gutiérrez wrote:

> I think the Fbsplash isnt working in 2.6-rx dont know why but i cant 
> get it to work neither.


WFM with the emergence theme and 2.6.12-gentoo-r5 (r2-r4 were also ok).

I have a Radeon mobility 9600 and am using the radeonfb driver.  
Unfortunately my initrd is highly custom, and linked into my kernel, so 
comparisons will be tough.

Do you get the frame buffer, but no graphics?  If so, you most likely 
need to add "RAM disk support" and "Initial RAM disk (initrd) support" 
to your kernel.  Both options are found under Device Drivers->Block devices.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
> 
> LostSon wrote:
> 
> > Hello 
> > I am trying to get fbsplash to work and am stuck. I have followed the
> >directions on the gentoo-wiki site but still no luck. Im using vesafb
> >with a 2.6.12-r6 kernel. my grub.conf looks like this 
> >
> >title=Gentoo-2.6.12-r6-fbsplash
> >root (hd0,0)
> >kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> >video=vesafb:ywrap,mtrr,1024x768@70 spla$
> >initrd (hd0,0)/fbsplash-gentoo-1024x768
> >
> >  
> >
> 
> Um, is fbsplash-gentoo-1024x768 in the /boot directory?  Is your root 
> filesystem /dev/hda1?
> 
> If the answer to both is yes, then the initrd line should say:
> 
> initrd (hd0,0)/boot/fbsplash-gentoo-1024x768
> 
> -Richard
> 
> 

 OK I have tried this as well and still no luck i just keep getting an
error about Cant open config file in /etc/splash/emergence or /gentoo
depending o which splash i use. There is more stuff about /dev/fb0
or /dev/fd0 i cant seem to find these messages in any of my log files
though. 
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Richard Fish]

LostSon wrote:

>On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
>  
>
>>LostSon wrote:
>>
>>    
>>
>>>Hello 
>>>I am trying to get fbsplash to work and am stuck. I have followed the
>>>directions on the gentoo-wiki site but still no luck. Im using vesafb
>>>with a 2.6.12-r6 kernel. my grub.conf looks like this 
>>>
>>>title=Gentoo-2.6.12-r6-fbsplash
>>>root (hd0,0)
>>>kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
>>>video=vesafb:ywrap,mtrr,1024x768@70 spla$
>>>initrd (hd0,0)/fbsplash-gentoo-1024x768
>>>
>>> 
>>>
>>>      
>>>
>>Um, is fbsplash-gentoo-1024x768 in the /boot directory?  Is your root 
>>filesystem /dev/hda1?
>>
>>If the answer to both is yes, then the initrd line should say:
>>
>>initrd (hd0,0)/boot/fbsplash-gentoo-1024x768
>>
>>-Richard
>>
>>
>>    
>>
>
> OK I have tried this as well and still no luck i just keep getting an
>error about Cant open config file in /etc/splash/emergence or /gentoo
>depending o which splash i use. There is more stuff about /dev/fb0
>or /dev/fd0 i cant seem to find these messages in any of my log files
>though. 
>  
>

Does your kernel configuration include both RAM disk and Initial RAM 
disk support (under Device Drivers->Block Devices)?  Both are required 
for loading the initramfs through the initrd memory protocol.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[charly ghislain]

On Tue, 19 Jul 2005 22:12:38 +0200, Richard Fish <bigfish@asmallpond.org>  
wrote:

> LostSon wrote:
>
>> On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
>>
>>> LostSon wrote:
>>>
>>>
>>>> Hello I am trying to get fbsplash to work and am stuck. I have  
>>>> followed the
>>>> directions on the gentoo-wiki site but still no luck. Im using vesafb
>>>> with a 2.6.12-r6 kernel. my grub.conf looks like this  
>>>> title=Gentoo-2.6.12-r6-fbsplash
>>>> root (hd0,0)
>>>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
>>>> video=vesafb:ywrap,mtrr,1024x768@70 spla$
>>>> initrd (hd0,0)/fbsplash-gentoo-1024x768
>>>>
make sure nano didnt cut your kernel line. The video= option should be on  
the same line than the kernel one. It should look like:

title=Gentoo-2.6.12-r6-fbsplash
root (hd0,0)
kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3  
video=vesafb:ywrap,mtrr,1024x768@70 splash=...  #(one line)
initrd (hd0,0)/fbsplash-gentoo-1024x768

This is very annoying, but while editing a line larger than the console,  
nano cut it into two lines :(  You have to check every time, go to the end  
of the first part of the cuted line and press delete

charly
>>>>
>>> Um, is fbsplash-gentoo-1024x768 in the /boot directory?  Is your root  
>>> filesystem /dev/hda1?
>>>
>>> If the answer to both is yes, then the initrd line should say:
>>>
>>> initrd (hd0,0)/boot/fbsplash-gentoo-1024x768
>>>
>>> -Richard
>>>
>>>
>>>
>>
>> OK I have tried this as well and still no luck i just keep getting an
>> error about Cant open config file in /etc/splash/emergence or /gentoo
>> depending o which splash i use. There is more stuff about /dev/fb0
>> or /dev/fd0 i cant seem to find these messages in any of my log files
>> though.
>
> Does your kernel configuration include both RAM disk and Initial RAM  
> disk support (under Device Drivers->Block Devices)?  Both are required  
> for loading the initramfs through the initrd memory protocol.
>
> -Richard
>


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Tony Davison]

On Tuesday 19 July 2005 21:27, charly ghislain wrote:
> On Tue, 19 Jul 2005 22:12:38 +0200, Richard Fish
> <bigfish@asmallpond.org>
>
> wrote:
> > LostSon wrote:
> >> On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
> >>> LostSon wrote:
> >>>> Hello I am trying to get fbsplash to work and am stuck. I have
> >>>> followed the
> >>>> directions on the gentoo-wiki site but still no luck. Im using
> >>>> vesafb with a 2.6.12-r6 kernel. my grub.conf looks like this
> >>>> title=Gentoo-2.6.12-r6-fbsplash
> >>>> root (hd0,0)
> >>>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> >>>> video=vesafb:ywrap,mtrr,1024x768@70 spla$
> >>>> initrd (hd0,0)/fbsplash-gentoo-1024x768
>
> make sure nano didnt cut your kernel line. The video= option should
> be on the same line than the kernel one. It should look like:
>
> title=Gentoo-2.6.12-r6-fbsplash
> root (hd0,0)
> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> video=vesafb:ywrap,mtrr,1024x768@70 splash=...  #(one line)
> initrd (hd0,0)/fbsplash-gentoo-1024x768
>
> This is very annoying, but while editing a line larger than the
> console, nano cut it into two lines :(  You have to check every time,
> go to the end of the first part of the cuted line and press delete
>
Use nano -w <file.name> to avoid line wraps.
-- 
Tony Davison
tony.davison2@ntlworld.com
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

On Tue, 2005-07-19 at 21:45 +0100, Tony Davison wrote:
> On Tuesday 19 July 2005 21:27, charly ghislain wrote:
> > On Tue, 19 Jul 2005 22:12:38 +0200, Richard Fish
> > <bigfish@asmallpond.org>
> >
> > wrote:
> > > LostSon wrote:
> > >> On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
> > >>> LostSon wrote:
> > >>>> Hello I am trying to get fbsplash to work and am stuck. I have
> > >>>> followed the
> > >>>> directions on the gentoo-wiki site but still no luck. Im using
> > >>>> vesafb with a 2.6.12-r6 kernel. my grub.conf looks like this
> > >>>> title=Gentoo-2.6.12-r6-fbsplash
> > >>>> root (hd0,0)
> > >>>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > >>>> video=vesafb:ywrap,mtrr,1024x768@70 spla$
> > >>>> initrd (hd0,0)/fbsplash-gentoo-1024x768
> >
> > make sure nano didnt cut your kernel line. The video= option should
> > be on the same line than the kernel one. It should look like:
> >
> > title=Gentoo-2.6.12-r6-fbsplash
> > root (hd0,0)
> > kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
> > video=vesafb:ywrap,mtrr,1024x768@70 splash=...  #(one line)
> > initrd (hd0,0)/fbsplash-gentoo-1024x768
> >
> > This is very annoying, but while editing a line larger than the
> > console, nano cut it into two lines :(  You have to check every time,
> > go to the end of the first part of the cuted line and press delete
> >
> Use nano -w <file.name> to avoid line wraps.
> -- 
> Tony Davison
> tony.davison2@ntlworld.com

 I checked this per your instructions as well and no it hasnt cut it off
its all on one line. Still no luck im still just getting the cant open
config file on /etc/splash error and fd0 crap, heh
-- 

LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Christoph Eckert]

>  I checked this per your instructions as well and no it
> hasnt cut it off its all on one line. Still no luck im
> still just getting the cant open config file on /etc/splash
> error and fd0 crap, heh

same for me. I've been playing the whole evening eith 
different settings but no result.

Interesting: The splash image gets loaded as soon as the 
machine switches to runlevel three.

BTW: I try to set it up @ 1400x1050.


Best regards


    ce

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

On Tue, 2005-07-19 at 23:10 +0200, Christoph Eckert wrote:
> >  I checked this per your instructions as well and no it
> > hasnt cut it off its all on one line. Still no luck im
> > still just getting the cant open config file on /etc/splash
> > error and fd0 crap, heh
> 
> same for me. I've been playing the whole evening eith 
> different settings but no result.
> 
> Interesting: The splash image gets loaded as soon as the 
> machine switches to runlevel three.
> 
> BTW: I try to set it up @ 1400x1050.
> 
> 
> Best regards
> 
> 
>     ce
> 
 Yeah its been 3 days here building kernels with different options and
the like im about to give up on it. I have my terminal set at 1024x768
anyway which looks nice by itself, i just thought this would be
interesting to try and see what it looks like, but im starting to think
it isnt worth the trouble,lol
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Christoph Eckert]

>  Yeah its been 3 days here building kernels with different
> options and the like im about to give up on it. I have my
> terminal set at 1024x768 anyway which looks nice by itself,
> i just thought this would be interesting to try and see
> what it looks like, but im starting to think it isnt worth
> the trouble,lol

Same for me. I'm happy to have 1400x1050 at the console now.

OK, booting with a deep blue background still looks a bit more 
interesting than plain black white, and I especialoly like 
the silent splash.

But I'll give up. Spend some hours with it, I should better 
have catched my guitar instead ;-) .


Best regards


    ce


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Holly Bostick]

Christoph Eckert schreef:
>> I checked this per your instructions as well and no it
>>hasnt cut it off its all on one line. Still no luck im
>>still just getting the cant open config file on /etc/splash
>>error and fd0 crap, heh

Umm... pardon me for asking, but you've said at least twice that an 
error informs you that splash can't open the config file on 
/etc/splash-- but you've never said that you checked the config file at 
/etc/splash to confirm that it 1) exists 2) is readable (permissions, 
syntax).... does something in or related to /etc/splash (like 
/etc/conf.d/splash, or in some strange twist of fate, 
/etc/init.d/splash, in addition to the config file found in each theme 
folder in /etc/splash itself) have some association with fd0 (the floppy 
drive) for some reason? Do you even have a floppy drive? Even so, the 
splash config file certainly won't be found there.

The nice thing about Linux is that error messages are in fact 
meaningful, and often lead directly to a solution. Perhaps you should 
heed this one a bit more closely.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Richard Fish]

Christoph Eckert wrote:

>> I checked this per your instructions as well and no it
>>hasnt cut it off its all on one line. Still no luck im
>>still just getting the cant open config file on /etc/splash
>>error and fd0 crap, heh
>>    
>>
>
>same for me. I've been playing the whole evening eith 
>different settings but no result.
>
>Interesting: The splash image gets loaded as soon as the 
>machine switches to runlevel three.
>
>BTW: I try to set it up @ 1400x1050.
>
>  
>

So, this means you have the framebuffer device and fbsplash 
working...just not at kernel boot time.  This probably means you do not 
have the right kernel options for initrd loading, or a bad grub 
configuration.  Could you post your dmesg output...specifically looking 
for a line that says something like "checking if initrd is 
initramfs...it (is/isn't)"...

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]

On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote:
> Christoph Eckert schreef:
> >> I checked this per your instructions as well and no it
> >>hasnt cut it off its all on one line. Still no luck im
> >>still just getting the cant open config file on /etc/splash
> >>error and fd0 crap, heh
> 
> Umm... pardon me for asking, but you've said at least twice that an 
> error informs you that splash can't open the config file on 
> /etc/splash-- but you've never said that you checked the config file at 
> /etc/splash to confirm that it 1) exists 2) is readable (permissions, 
> syntax).... does something in or related to /etc/splash (like 
> /etc/conf.d/splash, or in some strange twist of fate, 
> /etc/init.d/splash, in addition to the config file found in each theme 
> folder in /etc/splash itself) have some association with fd0 (the floppy 
> drive) for some reason? Do you even have a floppy drive? Even so, the 
> splash config file certainly won't be found there.

 Yes the files exist and the permissions are right where i should be
able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they
are.
> 
> The nice thing about Linux is that error messages are in fact 
> meaningful, and often lead directly to a solution. Perhaps you should 
> heed this one a bit more closely.
> 
> Holly
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Holly Bostick]

LostSon schreef:
> On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote:
> 
>>Christoph Eckert schreef:
>>
> >>>>I checked this per your instructions as well and no it
>>>>hasnt cut it off its all on one line. Still no luck im
>>>>still just getting the cant open config file on /etc/splash
>>>>error and fd0 crap, heh
>>
>>Umm... pardon me for asking, but you've said at least twice that an 
>>error informs you that splash can't open the config file on 
>>/etc/splash-- but you've never said that you checked the config file at 
>>/etc/splash to confirm that it 1) exists 2) is readable (permissions, 
>>syntax).... 

>  Yes the files exist and the permissions are right where i should be
> able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they
> are.

Now that we know they're /dev/fb and not /dev/fd (which is the floppy 
drive), I would imagine that they refer to the framebuffer devices 
(which are apparently not being created? or are being created too late?)

Now, on my system, /dev/fb0 is a symlink to /dev/fb/0, which is as it 
should be-- and makes me think that this is a udev issue, as that's udev 
device creation-type naming.

Since the devices are eventually being created (as you've indicated that 
your framebuffer later works), that suggests that you have hotplug 
creating the device late in the boot process. Do you have coldplug, 
which is responsible for creating the early devices (presumably like 
this one)?

Holly

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Christoph Eckert]

Thanks Richard,


> So, this means you have the framebuffer device and fbsplash
> working...just not at kernel boot time.  This probably
> means you do not have the right kernel options for initrd
> loading, or a bad grub configuration.  Could you post your
> dmesg output...specifically looking for a line that says
> something like "checking if initrd is initramfs...it
> (is/isn't)"...

at least for my part I got it to work by trial and error. The 
machine didn't like the 1400x1050 resolution, but now I'm 
fine with 1280x1024.


Thanks & best regards


    ce


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Richard Fish]

LostSon wrote:

>On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote:
>  
>
>>Christoph Eckert schreef:
>>    
>>
>>>>I checked this per your instructions as well and no it
>>>>hasnt cut it off its all on one line. Still no luck im
>>>>still just getting the cant open config file on /etc/splash
>>>>error and fd0 crap, heh
>>>>        
>>>>
>>Umm... pardon me for asking, but you've said at least twice that an 
>>error informs you that splash can't open the config file on 
>>/etc/splash-- but you've never said that you checked the config file at 
>>/etc/splash to confirm that it 1) exists 2) is readable (permissions, 
>>syntax).... does something in or related to /etc/splash (like 
>>/etc/conf.d/splash, or in some strange twist of fate, 
>>/etc/init.d/splash, in addition to the config file found in each theme 
>>folder in /etc/splash itself) have some association with fd0 (the floppy 
>>drive) for some reason? Do you even have a floppy drive? Even so, the 
>>splash config file certainly won't be found there.
>>    
>>
>
> Yes the files exist and the permissions are right where i should be
>able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they
>are.
>  
>

/dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing 
the framebuffer device.  During services startup (i.e, the part that 
happens after after the root filesystem is mounted and the kernel starts 
init) these nodes are created automatically when udevstart is run by 
/sbin/rc.  This only happens if a usable framebuffer driver is compiled 
into your kernel (not as a module!) and the driver found a usable 
graphics card.

Could you post your dmesg output right after booting.  I want to make 
sure that the framebuffer device is being found at boot time.  You 
should be seeing messages like this:


radeonfb: Retreived PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, 
System=236.00 MHz
radeonfb: PLL min 20000 max 35000
Non-DDC laptop panel detected
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: 1600x1200
radeonfb: detected LVDS panel size from BIOS: 1600x1200
radeondb: BIOS provided dividers will be used
radeonfb: Dynamic Clock Power Management enabled
Console: switching to colour frame buffer device 200x75
fbsplash: console 0 using theme 'emergence'
fbsplash: switched splash state to 'on' on console 0
radeonfb (0000:01:00.0): ATI Radeon NP

I think yours should say something about vesafb-tng.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[charly ghislain]

On Tue, 19 Jul 2005 22:45:47 +0200, Tony Davison  
<tony.davison2@ntlworld.com> wrote:

> On Tuesday 19 July 2005 21:27, charly ghislain wrote:
>> On Tue, 19 Jul 2005 22:12:38 +0200, Richard Fish
>> <bigfish@asmallpond.org>
>>
>> wrote:
>> > LostSon wrote:
>> >> On Tue, 2005-07-19 at 20:44 +0200, Richard Fish wrote:
>> >>> LostSon wrote:
>> >>>> Hello I am trying to get fbsplash to work and am stuck. I have
>> >>>> followed the
>> >>>> directions on the gentoo-wiki site but still no luck. Im using
>> >>>> vesafb with a 2.6.12-r6 kernel. my grub.conf looks like this
>> >>>> title=Gentoo-2.6.12-r6-fbsplash
>> >>>> root (hd0,0)
>> >>>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
>> >>>> video=vesafb:ywrap,mtrr,1024x768@70 spla$
>> >>>> initrd (hd0,0)/fbsplash-gentoo-1024x768
>>
>> make sure nano didnt cut your kernel line. The video= option should
>> be on the same line than the kernel one. It should look like:
>>
>> title=Gentoo-2.6.12-r6-fbsplash
>> root (hd0,0)
>> kernel (hd0,0)/boot/bzImage.new25 root=/dev/hda3
>> video=vesafb:ywrap,mtrr,1024x768@70 splash=...  #(one line)
>> initrd (hd0,0)/fbsplash-gentoo-1024x768
>>
>> This is very annoying, but while editing a line larger than the
>> console, nano cut it into two lines :(  You have to check every time,
>> go to the end of the first part of the cuted line and press delete
>>
> Use nano -w <file.name> to avoid line wraps.

Thanks. I remember now that it was the command used in the handbook.
It will save me usefull time :)

charly


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 3046 bytes --]

On Wed, 2005-07-20 at 07:11 +0200, Richard Fish wrote:
> LostSon wrote:
> 
> >On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote:
> >  
> >
> >>Christoph Eckert schreef:
> >>    
> >>
> >>>>I checked this per your instructions as well and no it
> >>>>hasnt cut it off its all on one line. Still no luck im
> >>>>still just getting the cant open config file on /etc/splash
> >>>>error and fd0 crap, heh
> >>>>        
> >>>>
> >>Umm... pardon me for asking, but you've said at least twice that an 
> >>error informs you that splash can't open the config file on 
> >>/etc/splash-- but you've never said that you checked the config file at 
> >>/etc/splash to confirm that it 1) exists 2) is readable (permissions, 
> >>syntax).... does something in or related to /etc/splash (like 
> >>/etc/conf.d/splash, or in some strange twist of fate, 
> >>/etc/init.d/splash, in addition to the config file found in each theme 
> >>folder in /etc/splash itself) have some association with fd0 (the floppy 
> >>drive) for some reason? Do you even have a floppy drive? Even so, the 
> >>splash config file certainly won't be found there.
> >>    
> >>
> >
> > Yes the files exist and the permissions are right where i should be
> >able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they
> >are.
> >  
> >
> 
> /dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing 
> the framebuffer device.  During services startup (i.e, the part that 
> happens after after the root filesystem is mounted and the kernel starts 
> init) these nodes are created automatically when udevstart is run by 
> /sbin/rc.  This only happens if a usable framebuffer driver is compiled 
> into your kernel (not as a module!) and the driver found a usable 
> graphics card.
> 
> Could you post your dmesg output right after booting.  I want to make 
> sure that the framebuffer device is being found at boot time.  You 
> should be seeing messages like this:
> 
> 
> radeonfb: Retreived PLL infos from BIOS
> radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, 
> System=236.00 MHz
> radeonfb: PLL min 20000 max 35000
> Non-DDC laptop panel detected
> radeonfb: Monitor 1 type LCD found
> radeonfb: Monitor 2 type no found
> radeonfb: panel ID string: 1600x1200
> radeonfb: detected LVDS panel size from BIOS: 1600x1200
> radeondb: BIOS provided dividers will be used
> radeonfb: Dynamic Clock Power Management enabled
> Console: switching to colour frame buffer device 200x75
> fbsplash: console 0 using theme 'emergence'
> fbsplash: switched splash state to 'on' on console 0
> radeonfb (0000:01:00.0): ATI Radeon NP
> 
> I think yours should say something about vesafb-tng.
> 
> -Richard
> 
  My dmesg output shows nothing like that at all im digging around for
the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must
of screwed something up pretty damn bad.
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 4062 bytes --]

On Thu, 2005-07-21 at 11:14 -0500, LostSon wrote:
> On Wed, 2005-07-20 at 07:11 +0200, Richard Fish wrote:
> > LostSon wrote:
> > 
> > >On Tue, 2005-07-19 at 23:31 +0200, Holly Bostick wrote:
> > >  
> > >
> > >>Christoph Eckert schreef:
> > >>    
> > >>
> > >>>>I checked this per your instructions as well and no it
> > >>>>hasnt cut it off its all on one line. Still no luck im
> > >>>>still just getting the cant open config file on /etc/splash
> > >>>>error and fd0 crap, heh
> > >>>>        
> > >>>>
> > >>Umm... pardon me for asking, but you've said at least twice that an 
> > >>error informs you that splash can't open the config file on 
> > >>/etc/splash-- but you've never said that you checked the config file at 
> > >>/etc/splash to confirm that it 1) exists 2) is readable (permissions, 
> > >>syntax).... does something in or related to /etc/splash (like 
> > >>/etc/conf.d/splash, or in some strange twist of fate, 
> > >>/etc/init.d/splash, in addition to the config file found in each theme 
> > >>folder in /etc/splash itself) have some association with fd0 (the floppy 
> > >>drive) for some reason? Do you even have a floppy drive? Even so, the 
> > >>splash config file certainly won't be found there.
> > >>    
> > >>
> > >
> > > Yes the files exist and the permissions are right where i should be
> > >able to use them. and the /dev/fb0 and /dev/fb/0 i have no idea wtf they
> > >are.
> > >  
> > >
> > 
> > /dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing 
> > the framebuffer device.  During services startup (i.e, the part that 
> > happens after after the root filesystem is mounted and the kernel starts 
> > init) these nodes are created automatically when udevstart is run by 
> > /sbin/rc.  This only happens if a usable framebuffer driver is compiled 
> > into your kernel (not as a module!) and the driver found a usable 
> > graphics card.
> > 
> > Could you post your dmesg output right after booting.  I want to make 
> > sure that the framebuffer device is being found at boot time.  You 
> > should be seeing messages like this:
> > 
> > 
> > radeonfb: Retreived PLL infos from BIOS
> > radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, 
> > System=236.00 MHz
> > radeonfb: PLL min 20000 max 35000
> > Non-DDC laptop panel detected
> > radeonfb: Monitor 1 type LCD found
> > radeonfb: Monitor 2 type no found
> > radeonfb: panel ID string: 1600x1200
> > radeonfb: detected LVDS panel size from BIOS: 1600x1200
> > radeondb: BIOS provided dividers will be used
> > radeonfb: Dynamic Clock Power Management enabled
> > Console: switching to colour frame buffer device 200x75
> > fbsplash: console 0 using theme 'emergence'
> > fbsplash: switched splash state to 'on' on console 0
> > radeonfb (0000:01:00.0): ATI Radeon NP
> > 
> > I think yours should say something about vesafb-tng.
> > 
> > -Richard
> > 
>   My dmesg output shows nothing like that at all im digging around for
> the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must
> of screwed something up pretty damn bad.

 Ok i switched to vesafb-tng and now im getting some dmesg like this 

 vesafb: NVIDIA Corporation, NV36 Board - p190-3n , Chip Rev    (OEM:
NVIDIA)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:e510
vesafb: pmi: set display start = c00ce546, set palette = c00ce5b0
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce
3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da 
vesafb: hardware supports DDC2 transfers
vesafb: monitor limits: vf = 160 Hz, hf = 85 kHz, clk = 190 MHz
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
fbsplash: console 0 using theme 'emergence'
vesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 600k,
total 131072k
fb0: VESA VGA frame buffer device

 but still no image getting closer though maybe yet today 
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[LostSon]

[-- Attachment #1: Type: text/plain, Size: 2395 bytes --]

On Thu, 2005-07-21 at 23:36 +0200, Richard Fish wrote:
> LostSon wrote:
> 
> >>/dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing 
> >>the framebuffer device.  During services startup (i.e, the part that 
> >>happens after after the root filesystem is mounted and the kernel starts 
> >>init) these nodes are created automatically when udevstart is run by 
> >>/sbin/rc.  This only happens if a usable framebuffer driver is compiled 
> >>into your kernel (not as a module!) and the driver found a usable 
> >>graphics card.
> >>
> >>Could you post your dmesg output right after booting.  I want to make 
> >>sure that the framebuffer device is being found at boot time.  You 
> >>should be seeing messages like this:
> >>
> >>
> >>radeonfb: Retreived PLL infos from BIOS
> >>radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, 
> >>System=236.00 MHz
> >>radeonfb: PLL min 20000 max 35000
> >>Non-DDC laptop panel detected
> >>radeonfb: Monitor 1 type LCD found
> >>radeonfb: Monitor 2 type no found
> >>radeonfb: panel ID string: 1600x1200
> >>radeonfb: detected LVDS panel size from BIOS: 1600x1200
> >>radeondb: BIOS provided dividers will be used
> >>radeonfb: Dynamic Clock Power Management enabled
> >>Console: switching to colour frame buffer device 200x75
> >>fbsplash: console 0 using theme 'emergence'
> >>fbsplash: switched splash state to 'on' on console 0
> >>radeonfb (0000:01:00.0): ATI Radeon NP
> >>
> >>I think yours should say something about vesafb-tng.
> >>
> >>-Richard
> >>
> >>    
> >>
> >  My dmesg output shows nothing like that at all im digging around for
> >the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must
> >of screwed something up pretty damn bad.
> >  
> >
> 
> No, don't be so hard on yourself.  Most likely you just missed a kernel 
> configuration option, or configured things as modules instead of 
> statically into the kernel, both of which are pretty common mistakes.
> 
> What does "grep CONFIG_FB /usr/src/linux/.config" report?
> 
> -Richard
> 
Aha!! Success yeah it was just me screwing up my kernel config not
setting a resolution right. And switching to vesafb-tng helped out alot
also. Thanks for your help and patience, it is greatly appreciated.
-- 
LostSon

http://www.lostsonsvault.org

Fox Cities Linux User Group = www.foxlug.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Richard Fish]

LostSon wrote:

>>/dev/fb/0 (symlinked from /dev/fb0) are the device nodes for accessing 
>>the framebuffer device.  During services startup (i.e, the part that 
>>happens after after the root filesystem is mounted and the kernel starts 
>>init) these nodes are created automatically when udevstart is run by 
>>/sbin/rc.  This only happens if a usable framebuffer driver is compiled 
>>into your kernel (not as a module!) and the driver found a usable 
>>graphics card.
>>
>>Could you post your dmesg output right after booting.  I want to make 
>>sure that the framebuffer device is being found at boot time.  You 
>>should be seeing messages like this:
>>
>>
>>radeonfb: Retreived PLL infos from BIOS
>>radeonfb: Reference=27.00 MHz (RefDiv=6) Memory=344.00 Mhz, 
>>System=236.00 MHz
>>radeonfb: PLL min 20000 max 35000
>>Non-DDC laptop panel detected
>>radeonfb: Monitor 1 type LCD found
>>radeonfb: Monitor 2 type no found
>>radeonfb: panel ID string: 1600x1200
>>radeonfb: detected LVDS panel size from BIOS: 1600x1200
>>radeondb: BIOS provided dividers will be used
>>radeonfb: Dynamic Clock Power Management enabled
>>Console: switching to colour frame buffer device 200x75
>>fbsplash: console 0 using theme 'emergence'
>>fbsplash: switched splash state to 'on' on console 0
>>radeonfb (0000:01:00.0): ATI Radeon NP
>>
>>I think yours should say something about vesafb-tng.
>>
>>-Richard
>>
>>    
>>
>  My dmesg output shows nothing like that at all im digging around for
>the /dev/fb0 and /dev/fb/0 but dont have either of these either. I must
>of screwed something up pretty damn bad.
>  
>

No, don't be so hard on yourself.  Most likely you just missed a kernel 
configuration option, or configured things as modules instead of 
statically into the kernel, both of which are pretty common mistakes.

What does "grep CONFIG_FB /usr/src/linux/.config" report?

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Vitaly Kovalyshyn aka samael]

[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]

Hello!

I've problems with fbsplash 2!

in grub.conf:
title  Gentoo Linux
root (hd0,0)
kernel /kernel-2.6.11-gentoo-r11 root=/dev/hda3 video=vesafb:1024x768-16@85 
plash=silent,theme:livecd-2005.0
initrd /fbsplash-livecd-2005.0-1024x768

in dmesg:
# dmesg | grep vesafb
Kernel command line: ro root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768-16@85 
splash=silent
vesafb: ATI Technologies Inc., V280, 01.00 (OEM: ATI RADEON 9200)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:5767
vesafb: pmi: set display start = c00c57fb, set palette = c00c5847
vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2 a0b4
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, using 3072k, total 
16384k

grep CONFIG_FB /usr/src/linux/.config:
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=y
CONFIG_FB_VESA=y
# CONFIG_FB_VESA_STD is not set
CONFIG_FB_VESA_TNG=y
CONFIG_FB_VESA_DEFAULT_MODE="1024x768@85"
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_SPLASH=y

But still no image on boot!!! :(
Can somebody help me? Because I new in Gentoo, last 4 years I worked on 
FreeBSD....

-- 
Vitaly Kovalyshyn aka samael
ICQ: 169219607
e-mail: samael@ugcc.org.ua
Jabber: samael@jabber.ugcc.org.ua
Unix System Administrator
Ukrainian Greek-Catholic Church

~~~~~~~~~~~~~~~~~~~
Open Your mind - use OpenSource!
"Nothing else matters", © Metallica
"Цели ясны, задачи определены, за работу, товарищи", ©

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] fbsplash problems

[Richard Fish]

Vitaly Kovalyshyn aka samael wrote:

>Hello!
>
>I've problems with fbsplash 2!
>
>in grub.conf:
>title  Gentoo Linux
>root (hd0,0)
>kernel /kernel-2.6.11-gentoo-r11 root=/dev/hda3 video=vesafb:1024x768-16@85 
>plash=silent,theme:livecd-2005.0
>initrd /fbsplash-livecd-2005.0-1024x768
>
>in dmesg:
># dmesg | grep vesafb
>Kernel command line: ro root=/dev/hda3 video=vesafb:ywrap,mtrr,1024x768-16@85 
>splash=silent
>vesafb: ATI Technologies Inc., V280, 01.00 (OEM: ATI RADEON 9200)
>vesafb: VBE version: 2.0
>vesafb: protected mode interface info at c000:5767
>vesafb: pmi: set display start = c00c57fb, set palette = c00c5847
>vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2 a0b4
>vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
>vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
>vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, using 3072k, total 
>16384k
>
>  
>

Do you also get a message about "checking if initrd is initramfs..." in 
dmesg?  If not, then you probably don't have ram disk or initrd support 
in your kernel configuration.  If so, then everything looks right, and 
maybe you can try a couple of different resolutions, and particularly, 
bit depths.  1024x768-24 or 1024x768-32 might work better.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] fbsplash problems

[Vitaly Kovalyshyn aka samael]

[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]

Thanx, Richard!

I've tried 1024x768-32!
And everything works ok! ;)

п'ятниця 22 липень 2005 18:00, Richard Fish Ви написали:
> Vitaly Kovalyshyn aka samael wrote:
> >Hello!
> >
> >I've problems with fbsplash 2!
> >
> >in grub.conf:
> >title  Gentoo Linux
> >root (hd0,0)
> >kernel /kernel-2.6.11-gentoo-r11 root=/dev/hda3
> > video=vesafb:1024x768-16@85 plash=silent,theme:livecd-2005.0
> >initrd /fbsplash-livecd-2005.0-1024x768
> >
> >in dmesg:
> ># dmesg | grep vesafb
> >Kernel command line: ro root=/dev/hda3
> > video=vesafb:ywrap,mtrr,1024x768-16@85 splash=silent
> >vesafb: ATI Technologies Inc., V280, 01.00 (OEM: ATI RADEON 9200)
> >vesafb: VBE version: 2.0
> >vesafb: protected mode interface info at c000:5767
> >vesafb: pmi: set display start = c00c57fb, set palette = c00c5847
> >vesafb: pmi: ports = a010 a016 a054 a038 a03c a05c a000 a004 a0b0 a0b2
> > a0b4 vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
> >vesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
> >vesafb: framebuffer at 0xe0000000, mapped to 0xe0880000, using 3072k,
> > total 16384k
>
> Do you also get a message about "checking if initrd is initramfs..." in
> dmesg?  If not, then you probably don't have ram disk or initrd support
> in your kernel configuration.  If so, then everything looks right, and
> maybe you can try a couple of different resolutions, and particularly,
> bit depths.  1024x768-24 or 1024x768-32 might work better.
>
> -Richard

-- 
Vitaly Kovalyshyn aka samael
ICQ: 169219607
e-mail: samael@ugcc.org.ua
Jabber: samael@jabber.ugcc.org.ua
Unix System Administrator
Ukrainian Greek-Catholic Church

~~~~~~~~~~~~~~~~~~~
Open Your mind - use OpenSource!
"Nothing else matters", © Metallica
"Цели ясны, задачи определены, за работу, товарищи", ©

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]