You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2007-04-21 18:06:13
- gazj
- Member
- From: /home/gazj -> /uk/cambs
- Registered: 2007-02-09
- Posts: 681
- Website
fbsplash hook kills kernel26beyond
Please be gentle with me, this is my first Arch post. not bad seeing i have been using arch for 6mths or more.
I have successfully managed to use fbsplash before without much problem, but this time i am struggling. Kernel = 2.6.19-beyond
When i use mkinitcpio -p kernel26beyond with fbsplash within my hooks, i get a kernel panic - not syncing, when i take out the fbsplash and make a new init, everything is fine again, for the life of me i cannot see why. Please help. Also do i really scsi and sata hooks?? i only have ide drives but they do show up as sdx so i am a little confused there.
Here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_via ata_generic"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect ide scsi sata filesystems"
#FBTHEMES="darch"
#FBRES="800x600"Please note that fbsplash is not in the hooks at the moment and the fb* lines are commented out so i can have a working kernel
Also for reference my grub's menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
#
# Linux Grub
# -------------------------
# /dev/fd0 (fd0)
# /dev/hda (hd0)
# /dev/hdb2 (hd1,1)
# /dev/hda3 (hd0,2)
#
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /vmlinuz26beyond root=/dev/sda3 ro vga=789 quiet video=vesafb:mtrr:3,ywrap splash=silent,kdgraphics,theme:darch console=tty1
initrd /kernel26beyond.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,1)
kernel /vmlinuz26beyond root=/dev/sda3 ro vga=771
initrd /kernel26beyond-fallback.img
# (1) Windows
title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1What is it that i seem to be missing ?!?!?!
I thank you all in advance for your answers to this post and answers i have found here before without posting.
Oh and thank you all for Arch, i have used many distro's over the years and finally found the one perfect for me. Thanks
Last edited by gazj (2007-04-21 18:09:23)
Offline
#2 2007-04-22 00:25:25
- raymano
- Member
- Registered: 2006-10-13
- Posts: 357
- Website
Re: fbsplash hook kills kernel26beyond
Glad you found arch 
Your problem might be related to your graphics card's framebuffer. I am using beyond with fbsplash and have no problem.
Here's my mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ata_generic ata_piix"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb fw pcmcia keymap filesystems resume fbsplash"
FBTHEMES="darch"
FBRES="1024x768"And my grub section.
title Arch Linux Beyond
root (hd0,0)
kernel (hd0,0)/boot/vmlinuz26beyond root=/dev/sda1 vga=792 video=vesafb:mtrr:3,ywrap splash=silent,kdgraphics,theme:darch console=tty1 quiet resume2=swap:/dev/sda2
initrd (hd0,0)/boot/kernel26beyond.imgAlso, I'm using grub-gfx from the community repo that allows showing background pics on the grub menu.
I don't know if any of this helps you but thought I'd share.
Last edited by raymano (2007-04-22 00:26:36)
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
#3 2007-04-22 14:00:57
- gazj
- Member
- From: /home/gazj -> /uk/cambs
- Registered: 2007-02-09
- Posts: 681
- Website
Re: fbsplash hook kills kernel26beyond
i fixed it
i removed quiet from my grub config, so i could see what was happening with init, i realised i was getting a hang on the filesystems hook.
So after reading the notes in mkinitcpio.conf i noticed you could remove the filesystems hook if you add your filesystem in modules, so that what i did. I added ext2 to modules and removed filesystems from hooks.
## vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="pata_via ata_generic ext2"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
#
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
#
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide raid encrypt filesystems"
#
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect ide scsi sata fbsplash"
FBTHEMES="darch"
FBRES="800x600"I am still confused though, lol, how come the filesystems way worked when fbsplash was not in hooks, but as soon as it was it messed up the filesystems hook. I would still like to find out why?? Wierd??
Offline
Pages: 1