| View previous topic :: View next topic |
| Author |
Message |
bluepboy
n00b
Joined: 21 Nov 2002
Posts: 2
|
 Posted: Fri Jan 17, 2003 3:16 am Post subject: |
 |
|
I already have LVM's initrd, how can I do if is what to use this splash?
Thanks. |
|
| Back to top |
|
 |
kachaffeous
Tux's lil' helper
Joined: 07 Jun 2002
Posts: 86
|
| Posted: Fri Jan 17, 2003 4:17 am Post subject: |
|
|
| Quote: | I'm getting more and more frustrated! I'm kinda sure it has something to do with this RAMDISK error:
Code:
nick@localhost nick $ dmesg | grep -i ramdisk
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
RAMDISK: Couldn't find valid RAM disk image starting at 0. |
Here is what my dmesg looks like.
| Code: |
vesafb: framebuffer at 0xd4000000, mapped to 0xc880d000, size 16384k
vesafb: mode is 1024x768x16, linelength=2048, pages=9
vesafb: protected mode interface info at c000:4471
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Looking for splash picture.... found (1024x768, 66762 bytes).
Console: switching to colour frame buffer device 105x34
fb0: VESA VGA frame buffer device
--snip--
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
--snip--
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 65k freed
--snip--
Looking for splash picture.... found (1024x768, 83429 bytes).
Splash status on console 1 changed to on
Looking for splash picture.... found (1024x768, 59521 bytes).
Splash status on console 2 changed to on
Looking for splash picture.... found (1024x768, 89306 bytes).
Splash status on console 3 changed to on
Looking for splash picture.... found (1024x768, 27481 bytes).
Splash status on console 4 changed to on
Looking for splash picture.... found (1024x768, 85175 bytes).
Splash status on console 5 changed to on
|
This is the related dmesg output. As you can see I get both ramdisk messages. I think the first one is loading the ramdisk for boot and the second one is freeing the ramdisk when you switch over to the hard drive. So, it really isn't a error, this is a just a guess though.
Only thing I can think of is to make sure you are using a jpeg image and that the resolution of the image matches your frame buffer size.
| Code: |
I already have LVM's initrd, how can I do if is what to use this splash?
|
I have no idea, LVM=logical volume manager? I really haven't messed with LVM's on linux, I get enough of that at work . Make a backup of your initrd and give it a shot. 
[/code] |
|
| Back to top |
|
|
Joffer
Guru
Joined: 10 Sep 2002
Posts: 585
Location: Arendal, Norway
|
| Posted: Fri Jan 17, 2003 4:24 am Post subject: |
|
|
Ok.. you corrected me One possible error taken off the list.. I can't remember if I asked it before, but have anyone used bootsplash with matroxfb ? (or other fb drivers except vesa?)
Will start all over with a kernelcompilation. I want this to work. About using the correct image.. I've been using the bootsplash ebuild the few last times.. guess this ebuild has correct images for all normal resolutions.. |
|
| Back to top |
|
|
kachaffeous
Tux's lil' helper
Joined: 07 Jun 2002
Posts: 86
|
| Posted: Fri Jan 17, 2003 4:27 am Post subject: |
|
|
| Quote: | | guess this ebuild has correct images for all normal resolutions.. |
I'm not sure, just fire up gimp and check the resolution. If you are using vesa=791 make sure the image is 1024x768. If you are using a different vesa line make sure the image resoultion correlates. |
|
| Back to top |
|
|
Joffer
Guru
Joined: 10 Sep 2002
Posts: 585
Location: Arendal, Norway
|
| Posted: Fri Jan 17, 2003 6:12 pm Post subject: |
|
|
The ebuild comes with images for 800x600, 1024x768 and 1280x1024 at least. They are located in /usr/share/bootsplash/. I don't have X up and running yet, since I like to get one thing running before I go on with the next.. just my way of doing stuff.
But if the image isn't the right resolution, wouldn't I get a "splash image not found" kinda error message in my 'dmesg'? I'm not even getting that..  |
|
| Back to top |
|
|
Joffer
Guru
Joined: 10 Sep 2002
Posts: 585
Location: Arendal, Norway
|
| Posted: Fri Jan 17, 2003 7:21 pm Post subject: |
|
|
| mynameisjonas wrote: | | i still think that your problem is with where initrd is placed and grub.conf notation but then, what do i know |
Ok.. if you got time, lets go over this. My /etc/fstab looks like this: | Code: | /dev/hda2 /boot ext3 noatime 1 2
/dev/hda6 / reiserfs noatime 0 1
/dev/hda5 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0 |
My /boot/grub/grub.conf looks like this: | Code: | default 1
timeout 30
splashimage=(hd0,1)/grub/splash.xpm.gz
title=Gentoo gentoo-19-r10-2ct
root (hd0,1)
kernel /kernel-2.4.19-2ct root=/dev/hda6 hdd=ide-scsi video=matrox:1280x1024-32@85
title=Gentoo gentoo-19-r10-4ct 1280x1024
root (hd0,1)
kernel /gentoo-2.4.19-4ct root=/dev/hda6 hdd=ide-scsi vga=0x31B video=matrox:vesa:0x31B,fv:85
initrd=/initrd
title=Windows 2000 Professional
root (hd0,0)
chainloader +1 |
and here is my bootsplashfiles: | Code: | pc-cth root # ls -la /usr/share/bootsplash-0.3/
total 308
drwxr-xr-x 2 root root 776 Jan 17 19:39 .
drwxr-xr-x 98 root root 2704 Jan 17 06:56 ..
-rw-r--r-- 1 root root 59785 Jan 17 06:56 boot_splash_complete.2.4.19-vanilla.patch
lrwxrwxrwx 1 root root 27 Jan 17 06:56 bootsplash.cfg -> ./gentoo-boot-1280x1024.cfg
lrwxrwxrwx 1 root root 27 Jan 17 06:56 bootsplash.jpg -> ./gentoo-boot-1280x1024.jpg
-rw-r--r-- 1 root root 1497 Jan 17 06:56 gentoo-boot-1024x768.cfg
-rw-r--r-- 1 root root 32386 Jan 17 06:56 gentoo-boot-1024x768.jpg
-rw-r--r-- 1 root root 1498 Jan 17 06:56 gentoo-boot-1280x1024.cfg
-rw-r--r-- 1 root root 33122 Jan 17 06:56 gentoo-boot-1280x1024.jpg
-rw-r--r-- 1 root root 1496 Jan 17 06:56 gentoo-boot-800x600.cfg
-rw-r--r-- 1 root root 21018 Jan 17 06:56 gentoo-boot-800x600.jpg
-rw-r--r-- 1 root root 1499 Jan 17 06:56 gentoo-console-1024x768.cfg
-rw-r--r-- 1 root root 31081 Jan 17 06:56 gentoo-console-1024x768.jpg
-rw-r--r-- 1 root root 1500 Jan 17 06:56 gentoo-console-1280x1024.cfg
-rw-r--r-- 1 root root 31142 Jan 17 06:56 gentoo-console-1280x1024.jpg
-rw-r--r-- 1 root root 1496 Jan 17 06:56 gentoo-console-800x600.cfg
-rw-r--r-- 1 root root 21615 Jan 17 06:56 gentoo-console-800x600.jpg
-rw-r--r-- 1 root root 549 Jan 17 06:56 grub.conf.sample
-rw-r--r-- 1 root root 33142 Jan 17 19:39 initrd
|
Then I have recreated initrd just to be sure: | Code: | cd /usr/share/bootsplash-0.3/
splash -s -f bootsplash.cfg > initrd
cp initrd /boot/initrd |
Rebooting, and all I get is normal matroxfb 1280x1024x32@85 with Gentoo bootlogo on upper left corner of the screen, which of course is nice, but not as nice as it would be with bootsplash.
Do you see anything wrong? I have tried this with normal "vesafb" mode too, but no luck, just a very slow fb@60Hz instead, so I've switched back to matroxfb witch is very fast compared to "vesafb". |
|
| Back to top |
|
|
mynameisjonas
n00b
Joined: 04 Aug 2002
Posts: 25
Location: Wales, United Kingdom
|
| Posted: Fri Jan 17, 2003 10:42 pm Post subject: |
|
|
joffer
to be honest i'm almost all out of ideas, i can only see a few very obvious things to point out but i will anyway:
firstly grub.conf here's mine:
| Code: | default 2
timeout 05
splashimage=(hd0,4)/boot/grub/splash.xpm.gz
title=Gentoo Linux 1.4
root (hd0,4)
kernel /boot/bzImage root=/dev/hde7
title=Gentoo Linux 1.4 (testing)
root (hd0,4)
kernel /boot/bzImage.testing root=/dev/hde7 vga=791 video=vesa:1024x768@70
initrd /boot/initrd
title=Windows XP
root (hd0,0)
chainloader +1
|
the only difference is as i've pointed out before is : initrd /boot/initrd. Can anyone verify that it works with initrd=/initrd, whenever i change this mine breaks straight away
secondly, was /boot mounted when you did
| Code: | splash -s -f bootsplash.cfg > initrd
cp initrd /boot/initrd |
nothing new here but the only things i can think of  |
|
| Back to top |
|
|
fu_fish
n00b
Joined: 16 Dec 2002
Posts: 21
Location: Knoxville, TN
|
| Posted: Sat Jan 18, 2003 8:52 pm Post subject: Oversized Text Area? |
|
|
Has anyone else had this problem? When I boot with the spash image I get the following error:
| Code: | | Looking for splash picture.... found, but has oversized text area! |
I first tried estimating the cooridinates of the text area, then I copied directly from the 800x600 example file, then switched to using common sizes like 640x480. Has anyone come across this problem? I'm just not sure what a normal size for a text area would be. |
|
| Back to top |
|
|
Loke^
n00b
Joined: 09 Jan 2003
Posts: 51
Location: Stockholm, Sweden
|
| Posted: Mon Jan 20, 2003 4:50 am Post subject: Debian |
|
|
Im running Debian on my laptop (Dont ask me why!).
Anyone got this working in debian?
Everything seems alright, but it dosnt work.
I get the Tuxlogo BUT with the text "linux 2.4.20" on top of it.
Now, what is debians answare to /etc/conf.d/start.local?
_________________
^L |
|
| Back to top |
|
|
Joffer
Guru
Joined: 10 Sep 2002
Posts: 585
Location: Arendal, Norway
|
| Posted: Mon Jan 20, 2003 6:56 am Post subject: Re: Debian |
|
|
| Loke^ wrote: | | Now, what is debians answare to /etc/conf.d/start.local? |
I've never used debian, but does it have /etc/rc.d/rc.local ? That's the corresponding file in Trustix Secure Linux 1.5 (based upon RedHat 6.2). |
|
| Back to top |
|
|
Loke^
n00b
Joined: 09 Jan 2003
Posts: 51
Location: Stockholm, Sweden
|
| Posted: Mon Jan 20, 2003 8:34 am Post subject: |
|
|
No it dos'nt have rc.conf. 
_________________
^L |
|
| Back to top |
|
|
carambola5
Apprentice
Joined: 10 Jul 2002
Posts: 214
|
| Posted: Mon Jan 20, 2003 8:56 am Post subject: error in download? |
|
|
I'm getting a digest mismatch when emerging:
| Code: | !!! bootsplash-0.4.tar.bz2: message digests do not match!
!!! bootsplash-0.4.tar.bz2 is corrupt or incomplete.
>>> our recorded digest: a75a1f419418eacb90b23087ba88bcbe
>>> your file's digest: 2c074a46e2d229863b0df7c5dd9b21a3 |
even after 'emerge sync'ing and deleting the distfile. |
|
| Back to top |
|
|
t0nik
n00b
Joined: 11 Oct 2002
Posts: 55
Location: Moscow, Russia
|
| Posted: Mon Jan 20, 2003 11:59 am Post subject: |
|
|
| Code: | ebuild /usr/portage/media-gfx/bootsplash/bootsplash-0.4.ebuild digest
emerge bootsplash |
_________________
sorry my bad english
t0nik |
|
| Back to top |
|
|
H-Pi
Apprentice
Joined: 26 Jun 2002
Posts: 175
Location: Delft (NL)
|
| Posted: Mon Jan 20, 2003 2:33 pm Post subject: Re: Debian |
|
|
| Loke^ wrote: | Im running Debian on my laptop (Dont ask me why!).
Anyone got this working in debian?
Everything seems alright, but it dosnt work.
I get the Tuxlogo BUT with the text "linux 2.4.20" on top of it.
Now, what is debians answare to /etc/conf.d/start.local? |
I also got this on my gentoo box, because I forgot to configure grub the right way, I had vga=791 instead of vga=794 which was the right for my 1280x1024 I configure splah for
so maybe it's a wrong bootloader config, or wrong kernel config (forgot to use splahscreen instead of bootlogo) |
|
| Back to top |
|
|
TumTum
n00b
Joined: 20 Jan 2003
Posts: 2
|
| Posted: Mon Jan 20, 2003 4:03 pm Post subject: |
|
|
| Code: |
console.c:3034: redefinition of `con_remap_def_color'
console.c:701: `con_remap_def_color' previously defined here
make[3]: *** [console.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers'
make: *** [_dir_drivers] Error 2
|
Ive been trying a lot of stuff, but everytime I try to compile it with the boot image this is where it fails . As you can see I use xfs-sources, so I dont know if anyone tried it with those, but I dont know what to do. |
|
| Back to top |
|
|
Loke^
n00b
Joined: 09 Jan 2003
Posts: 51
Location: Stockholm, Sweden
|
| Posted: Mon Jan 20, 2003 7:27 pm Post subject: |
|
|
H-Pi: No the grubconf is correct. I get some error about /proc/slpash: no souch file or dir.
_________________
^L |
|
| Back to top |
|
|
arkane
l33t
Joined: 30 Apr 2002
Posts: 918
Location: Phoenix, AZ
|
| Posted: Mon Jan 20, 2003 7:44 pm Post subject: |
|
|
I know one other person has said this, and I didn't see any responses, so I'll shoot it into the air again.
If you are running LVM, you already have an initrd setup. (it's used to run vgscan and so forth to setup the Volume Groups on boot, etc) Now, with this, it tells you to make an initrd called /boot/initrd, but what if you already have an initrd setup?
I've tried mounting through loopback the /boot/initrd this creates, and it doesn't appear to be a filesystem.. I'm guessing it's pure data of some form. I'm able to get the splash going once my system is up and rolling through the splash command, but the only thing I can get at boot is the penguin and "no signature found" when it's attempting to go for the bootsplash image. Now, I don't have the initrd in my lilo.conf set to the /boot/initrd because I need to keep what I currently have to boot. Is there a way to implement it into a currently existing initrd?
Or, better yet, is there a "splash=" parameter pass or some form to tell the kernel where the boot splash image is? |
|
| Back to top |
|
|
Joffer
Guru
Joined: 10 Sep 2002
Posts: 585
Location: Arendal, Norway
|
|
| Back to top |
|
|
TumTum
n00b
Joined: 20 Jan 2003
Posts: 2
|
| Posted: Tue Jan 21, 2003 7:59 pm Post subject: |
|
|
| TumTum wrote: | | Code: |
console.c:3034: redefinition of `con_remap_def_color'
console.c:701: `con_remap_def_color' previously defined here
make[3]: *** [console.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.19-xfs-r2/drivers'
make: *** [_dir_drivers] Error 2
|
Ive been trying a lot of stuff, but everytime I try to compile it with the boot image this is where it fails . As you can see I use xfs-sources, so I dont know if anyone tried it with those, but I dont know what to do. |
I fixed the above problem, but now im faced with this problem:
| Code: |
fbcon.c:64:43: linux-2.4.20-xfs_pre5/version.h: No such file or directory
In file included from fbcon.c:113:
fbcon-splash.h:17: parse error before numeric constant
fbcon-splash.h:17: too many decimal points in floating constant
make[3]: *** [fbcon.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.20-xfs_pre5/drivers/video'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.20-xfs_pre5/drivers/video'
make[1]: *** [_subdir_video] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20-xfs_pre5/drivers'
make: *** [_dir_drivers] Error 2
|
I just dont know what to do |
|
| Back to top |
|
|
bheremans
n00b
Joined: 24 Jan 2003
Posts: 29
|
| Posted: Mon Jan 27, 2003 9:09 am Post subject: |
|
|
| Joffer wrote: | | kachaffeous wrote: | | Joffer have you tried just using the vesa fb? More then likely that should work. |
Now I've got vesafb compiled into the kernel, and man this is slow. just watching 'dmesg' takes "forever" before it is finished. AND the bad news is that this didn't fix a thing. I'm still stuck with no bootsplash, a RAMDISK complaining and also only 60Hz vrefresh
I'm getting more and more frustrated! I'm kinda sure it has something to do with this RAMDISK error: | Code: | nick@localhost nick $ dmesg | grep -i ramdisk
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
RAMDISK: Couldn't find valid RAM disk image starting at 0. |
Anyone here that can correct me? That can say they have bootsplash up and running and also this error in their 'dmesg'? |
I have the same problem, error messages but the bootsplash is working. I emerged bootsplash 0.4 with gentoo souces
2.4.20. my dmesg :
| Code: |
Linux version 2.4.20-gentoo-r1 (root@mini-itx) (gcc version 3.2.1 20021207 (Gentoo Linux 3.2.1-20021207)) #1 Thu Jan
23 10:08:54 CET 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f7f0000 (usable)
BIOS-e820: 000000001f7f0000 - 000000001f7f3000 (ACPI NVS)
BIOS-e820: 000000001f7f3000 - 000000001f800000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
503MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 129008
zone(0): 4096 pages.
zone(1): 124912 pages.
zone(2): 0 pages.
ACPI: RSDP (v000 VIA601 ) @ 0x000f6790
ACPI: RSDT (v001 VIA601 AWRDACPI 16944.11825) @ 0x1f7f3000
ACPI: FADT (v001 VIA601 AWRDACPI 16944.11825) @ 0x1f7f3040
ACPI: DSDT (v001 VIA601 AWRDACPI 00000.04096) @ 0x00000000
ACPI: BIOS passes blacklist
Kernel command line: root=/dev/hda3 vga=788
Initializing CPU#0
Detected 800.249 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 1576.96 BogoMIPS
Memory: 503508k/516032k available (1515k kernel code, 9960k reserved, 496k data, 96k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
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)
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 64K (32 bytes/line)
CPU: After generic, caps: 00803135 80803035 00000000 00000000
CPU: Common caps: 00803135 80803035 00000000 00000000
CPU: Centaur VIA Ezra stepping 08
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20021122
PCI: PCI BIOS revision 2.10 entry at 0xfb3a0, last bus=1
PCI: Using configuration type 1
ACPI-0511: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: System [ACPI] (supports S0 S1 S4 S5)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 12 14 15, disabled)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
PCI: Probing PCI hardware
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
ACPI: Power Button (FF) [PWRF]
vesafb: framebuffer at 0xe1800000, mapped to 0xe0013000, size 8192k
vesafb: mode is 800x600x16, linelength=1600, pages=7
vesafb: protected mode interface info at c000:7dac
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Looking for splash picture.... found (800x600, 13683 bytes).
Console: switching to colour frame buffer device 82x30
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 89
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8231 (rev 10) IDE UDMA100 controller on pci00:11.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DTTA-350640, ATA DISK drive
hdc: TOSHIBA DVD-ROM SD-C2502, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c0338ea4, I/O limit 4095Mb (mask 0xffffffff)
hda: 12692736 sectors (6499 MB) w/468KiB Cache, CHS=790/255/63, UDMA(33)
hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
uhci.c: USB UHCI at I/O 0xd400, IRQ 5
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
uhci.c: USB UHCI at I/O 0xd800, IRQ 5
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 13k freed
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 96k freed
Adding Swap: 248996k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,3), internal journal
via-rhine.c:v1.10-LK1.1.14 May-3-2002 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT6102 Rhine-II at 0xe800, 00:40:63:c0:fa:4f, IRQ 11.
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 41e1.
EXT2-fs warning (device ide0(3,1)): ext2_read_super: mounting ext3 filesystem as ext2
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
Looking for splash picture.... no good signature found.
Looking for splash picture.... no good signature found.
Looking for splash picture.... no good signature found.
Looking for splash picture.... no good signature found.
Looking for splash picture.... no good signature found.
Looking for splash picture.... no good signature found.
|
My Grub config (I took "initrd /boot/initrd" and not "initrd=/boot/initrd" because webmin created it like this, but I tested with a "=")
| Code: |
default 2
timeout 8
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Default
root (hd0,0)
kernel /boot/bzImage root=/dev/hda3 vga=788
title Freevo
root (hd0,0)
kernel /boot/bzImage root=/dev/hda3 vga=788 4
title ProdTest
root (hd0,0)
kernel /boot/bzImageProdTest root=/dev/hda3 vga=788
initrd /boot/initrd
title safe
root (hd0,0)
kernel /boot/bzImageSafe root=/dev/hda3
initrd /boot/initrd
|
My fstab file, normally boot is not mounted all the time but I chenged it now for testing.
| Code: |
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.10 2002/11/18 19:39:22 azarah Exp $
#
# noatime turns of atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noatime 1 1
/dev/hda3 / ext3 noatime 0 0
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
proc /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). Adding the following
# line to /etc/fstab should take care of this:
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will use almost no
# memory if not populated with files)
tmpfs /dev/shm tmpfs defaults 0 0
|
And this are the files in the boot dir
| Code: |
total 4.2M
drwxr-xr-x 4 root 1.0K Jan 23 11:06 .
drwxr-xr-x 24 root 4.0K Jan 23 19:04 ..
lrwxrwxrwx 1 root 1 Dec 3 22:51 boot -> .
-rw-r--r-- 1 root 988K Jan 23 23:03 bzImage
-rw-r--r-- 1 root 1.3M Dec 8 12:08 bzImageDev
-rw-r--r-- 1 root 1.0M Jan 23 10:54 bzImageProdTest
-rw-r--r-- 1 root 840K Jan 6 13:17 bzImageSafe
drwxr-xr-x 2 root 1.0K Jan 23 17:30 grub
-rw-r--r-- 1 root 13K Jan 23 23:11 initrd
drwx------ 2 root 12K Dec 3 22:45 lost+found
|
Anybody sees something wrong in these files ?
Bart |
|
| Back to top |
|
|
Matje
l33t
Joined: 29 Oct 2002
Posts: 619
Location: Hasselt, Belgium
|
| Posted: Mon Jan 27, 2003 10:28 am Post subject: |
|
|
It is strange that halfway the kernel boot, the kernel states that it found the bootsplash-image. Maybe something is wrong with it?
_________________
Life is like a box of chocolates... Before you know it, it's empty... |
|
| Back to top |
|
|
bheremans
n00b
Joined: 24 Jan 2003
Posts: 29
|
| Posted: Mon Jan 27, 2003 12:58 pm Post subject: |
|
|
You mean this line :
| Code: | | Looking for splash picture.... found (800x600, 13683 bytes). |
Isn't that the grub menu background splash picture that is found ? |
|
| Back to top |
|
|
amd
n00b
Joined: 26 Nov 2002
Posts: 65
Location: Saaremaa / Estonia
|
| Posted: Mon Jan 27, 2003 6:00 pm Post subject: tweaking configuration files... |
|
|
has anyone had luck, setting
tx and ty settings in .cfg files?
When i set tx bigger than 32, splash refuses to create a fb image |
|
| Back to top |
|
|
Matje
l33t
Joined: 29 Oct 2002
Posts: 619
Location: Hasselt, Belgium
|
| Posted: Mon Jan 27, 2003 9:18 pm Post subject: |
|
|
| bheremans wrote: | | Isn't that the grub menu background splash picture that is found ? |
No it isn't. The kernel has nothing to do with grub and vice versa. It is the bootsplash it has found.
_________________
Life is like a box of chocolates... Before you know it, it's empty... |
|
| Back to top |
|
|
tkdack
n00b
Joined: 12 Apr 2002
Posts: 44
Location: Sydney, Australia
|
| Posted: Mon Jan 27, 2003 10:18 pm Post subject: Re: tweaking configuration files... |
|
|
| amd wrote: | has anyone had luck, setting
tx and ty settings in .cfg files?
When i set tx bigger than 32, splash refuses to create a fb image |
Look in the .cfg file, if this line:
is there, then you need to specify the terminal size in pixels. If not you need to specify the terminal size in characters like so:
| Code: |
tx_pixels=10
ty_pixels=10
th_pixels=580
tw_pixels=780
char_w = 8
char_h = 16
tx = round(tx_pixels/char_w) # only want whole numbers, no fractions
ty = round(ty_pixels/char_h)
tw = round(tw_pixels/char_w)
th = round(th_pixels/char_h)
|
Now if you are setting tx=32 and your width (tw) is too large then the terminal will not be positioned entirely on the screen, so you need to tweak the width value as well as the tx value (same goes for ty and th).
_________________
Troy
http://linux.tkdack.com
Former Gentoo contributor TaD |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
