Slackware 8.1 Tux oppi venstre hjørne ved oppstart!

[_Nitro_]

Er det mulig å få TUX til å stå der hele tiden?

 

TUX blir der helt til jeg kjører pico eller et annet fullscreen program!

[CAT0]

www.bootsplash.org

[Ancistrus84]

najs! Dette så tøft ut... Dette må prøves ut!

[akzj0n]

najs! Dette så tøft ut... Dette må prøves ut!

 

[_Nitro_]

Nei kor pent.! )

[osse-mon waits for alice]

Vakkert, det får man si

[Hoppesagåsa]

Æsj, jeg sikla på tastaturet...

[_Nitro_]

Finnes det noen howtoer til å sette opp dette.?

 

Jeg har patchet kjernen, laget bilde, laget ram disk og alt derre. Men bilde kommer ikke opp under boot.

[CAT0]

Sjekk dmesg, kanskje du har for liten ramdisk i forhold til bilde?

 

Også tror jeg bootsplash bare funker på vesafb....

[Klette]

Sjekk dmesg, kanskje du har for liten ramdisk i forhold til bilde?

 

Også tror jeg bootsplash bare funker på vesafb....

 

Huh?

 

Er litt ny på detta, hva er vesafb?

[sim]

2. What is vesafb?

Vesafb is a framebuffer driver for Intel architecture that works with

VESA 2.0 compliant graphic cards. It is closely related to the

framebuffer device drivers in the kernel.

vesafb is a display driver that enables the use of graphical modes on

your Intel platform for bitmapped text consoles. It can also display a

logo, which is probably the main reason why you'd want to use vesafb

:o)

Unfortunately, you can not use vesafb successfully with VESA 1.2

cards. This is because these 1.2 cards do not use framebuffering. It

may be that someone will write a vesafb12 device driver for these

cards, but this will use up precious kernel memory. :o(

There is however a potential workaround to add VESA 2.0 extensions for

your legacy VESA 1.2 card. You may be able to download a TSR type

program that will run from DOS, and used in cojunction with loadlin,

can help configure the card for the appropriate graphic console modes.

Note that this will not always work, as an example some Cirrus Logic

cards such as the VLB 54xx series are mapped to a range of memory

addresses (for example, within the 15MB-16MB range) for frame

buffering which preludes these from being used successfully with

systems that have more than 32MB of memory. [There is a way to make

this work, i.e. if you have a BIOS option to leave a memory hole at

15MB-16MB range, it might work, but I've been told that Linux doesn't

support this] If you wish to experiment with this option, there are

plenty of TSR style programs available, a prime example is UNIVBE,

which can be found on the Internet.

 

Hentet fra :

 

http://www.uno.edu/~adamico/banshee/files/vesafb.txt

[_Nitro_]

no valid ramdisk image eller.no er det som står. Har ikke helt sikker akkurat nå har ikke pcèn framfor meg.

 

Og den svitcher til vesafb under boot.

[ola555]

jeg strever også meg å få til dette med bootsplash. Jeg har følgt oppskriften men får ikke noe bilde. Her er min dmesg: (utklipp)

 

Linux version 2.4.20 (root@slackserv) (gcc version 3.2.2) #4 Sun Aug 10 19:08:01

CEST 2003

BIOS-provided physical RAM map:

BIOS-e820: 0000000000000000 - 0000000000080000 (usable)

BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)

BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 000000001dfec000 (usable)

BIOS-e820: 000000001dfec000 - 000000001dfef000 (ACPI data)

BIOS-e820: 000000001dfef000 - 000000001dfff000 (reserved)

BIOS-e820: 000000001dfff000 - 000000001e000000 (ACPI NVS)

BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)

BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)

BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)

479MB LOWMEM available.

On node 0 totalpages: 122860

zone(0): 4096 pages.

zone(1): 118764 pages.

zone(2): 0 pages.

Kernel command line: BOOT_IMAGE=torekernel ro root=301 splash=silent

bootsplash: silent mode.

Initializing CPU#0

Detected 1302.953 MHz processor.

Console: colour dummy device 80x25

Calibrating delay loop... 2601.77 BogoMIPS

Memory: 483116k/491440k available (1604k kernel code, 7812k reserved, 368k data,

272k init, 0k highmem)

Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)

Inode cache hash table entries: 32768 (order: 6, 262144 bytes)

Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)

Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)

Page-cache hash table entries: 131072 (order: 7, 524288 bytes)

 

VFS: Diskquotas version dquot_6.4.0 initialized

Journalled Block Device driver loaded

ACPI: APM is already active, exiting

vesafb: framebuffer at 0xe8000000, mapped to 0xde80d000, size 32768k

vesafb: mode is 1024x768x16, linelength=2048, pages=0

vesafb: protected mode interface info at c000:bf60

vesafb: scrolling: redraw

vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0

Console: switching to colour frame buffer device 128x48

fb0: VESA VGA frame buffer device

RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize