LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 10-12-2006, 07:45 PM   #1
mdkusr
Member
 
Registered: Nov 2004
Location: P-town
Distribution: Slackware 10.2
Posts: 72

Rep: Reputation: 15
Custom kernel causing odd issue


Just managed to install slack on my new acer lappy, wanting the newest wireless options I opted to build my own kernel which went very smoothly. The problem starts when I go to reboot into the new kernel, cause right now I have a dual boot of Win Xp and Slack which boots both fine except something odd happens when I go to slack. Nothing comes up once the bios data checks out, no kernel panics or anything like that just a blank black empty screen. Its such an odd issue that google doesn't really provide any leads, mostly just stuff relating to X hanging on load.
Is there anything that I could have done while building the kernel that may have caused such a weird problem, because I have built many kernels never has this happened.
Although I have never built one and plugged it into a dual-boot build, anything in Lilo that might be the source of this problem.
Sorry for the long post, just trying to describe the issue as best as I can. Thank you for any help that you may be able to provide, really want to get on and enjoy KDE 3.5.
 
Old 10-12-2006, 07:49 PM   #2
dxqcanada
Member
 
Registered: Sep 2006
Location: Canada
Distribution: Gentoo
Posts: 702

Rep: Reputation: 43
Re: odd issue

Hmm, if it was an X related issue you could be able to stop the X server with a CTL+ALT+Backslash.
Does CTL+ALT+F1 take you to the virtual terminal ?
What was the last couple of boot messages you saw ?
 
Old 10-16-2006, 04:10 PM   #3
snakle
LQ Newbie
 
Registered: Oct 2006
Posts: 14

Rep: Reputation: 0
I think I'm having the same problem you are. This is the very first kernel I've tried updating (from 2.4.33.3 to 2.6.18) and so far I havn't even got to boot into the terminal yet. Every time after I select the 2.6.18 kernel (luckily i made a backup of my old kernel in lilo.conf) it just goes into a black screen. My actual computer sounds like it is trying to boot... but nothing actually happens, it just stalls at the black screen.

I'm quite sure I did everything right, with the exception of forgetting to select something in the menuconfig, but I don't know what it would be. Also, just as a general question: does the menuconfig config file save as .config or config. Also, is there an option that allows me to see the .config file on KDE without having to ctl+f to find it?
 
Old 10-16-2006, 04:26 PM   #4
kevkim55
Member
 
Registered: Dec 2005
Location: Edmonton
Distribution: BLFS, Gentoo
Posts: 353

Rep: Reputation: 32
mdkusr, do you use lilo or grub ? Do you really see nothing right after the BIOS screen ? Or, do see GRUB loading... or LILO ?

snakle, the same above question and if you are getting a blank screen whenever you select 2.6.18, you would want to check the video resolution in lilo.conf or menu.lst. You can boot into linux with your older 2.4 version kernel and check.

kernel config is saved as .config
Quote:
Also, is there an option that allows me to see the .config file on KDE without having to ctl+f to find it?
If you mean, you cannot see .config in konqueror or any other GUI tool, you can select the option "SHow hidden files" which, should be accessible from File/View or Right click pop-up menu. To see from command line you can use "ls -a"
 
Old 10-16-2006, 06:13 PM   #5
snakle
LQ Newbie
 
Registered: Oct 2006
Posts: 14

Rep: Reputation: 0
I see the splash screen for my mother board, and after that I see Lilo, and the three options (Windows, slack-2.6.18, and slack-2.4.33.3) slack-2.4.33.3 works fine, but if i select slack-2.6.18 it says something like "checking bios settings................." or something about bios... and then it goes into the black screen.

no penguin models, no terminal, no more text at all: lilo.conf says
# VESA framebuffer console @ 1024x768x64k
vga = 791
so I guess that means it's at that resolution (although it's always been like that even before kernel... my terminal has also always been at 1024x768 and i don't think i could stand any lower res)

im thinking that I may have selected a wrong option for the graphics thing... so I'll just post what I have for that from the .config

Code:
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
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_ARC 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_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA 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=y
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_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
 
Old 10-16-2006, 07:31 PM   #6
mdkusr
Member
 
Registered: Nov 2004
Location: P-town
Distribution: Slackware 10.2
Posts: 72

Original Poster
Rep: Reputation: 15
Problem fixed. It was due to a lilo.conf error, where I was pointing to a null file that lead to nothing. Now though it boots the proper kernel, except now I get a kernel panic error "Kernel Panic - not syncing : VFS: Unable to mount root fs on unknown-block(3,3)." That is odd the whole root business, cause it is pointing to the right everything but maybe something isn't done up correctly.
Going to google, see if that yields any positive results.
http://www.linuxquestions.org/questi...d.php?t=361735
Ahh.. Google saves the day again

Last edited by mdkusr; 10-16-2006 at 07:35 PM.
 
Old 10-16-2006, 08:09 PM   #7
snakle
LQ Newbie
 
Registered: Oct 2006
Posts: 14

Rep: Reputation: 0
I don't think that it's a lilo problem... or at least I don't think it is for me. I copied System.map, .config, and bzImage over to /boot (renaming them from bzImage to vmlinuz-2.6.18, .config to config, and System.map to System.map-2.6.18) and then I made links to them all (like doing "ln -s vmlinuz-2.6.18 vmlinuz)

After doing all that I ran /sbin/lilo and it didn't really show any errors... long story short, I still have a blank screen and I can't really see anything close to "kernel panic"
 
Old 10-16-2006, 09:40 PM   #8
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 151Reputation: 151
Quote:
Originally Posted by snakle
I see the splash screen for my mother board, and after that I see Lilo, and the three options (Windows, slack-2.6.18, and slack-2.4.33.3) slack-2.4.33.3 works fine, but if i select slack-2.6.18 it says something like "checking bios settings................." or something about bios... and then it goes into the black screen.

im thinking that I may have selected a wrong option for the graphics thing... so I'll just post what I have for that from the .config
According to the drivers/video/Kconfig file with 2.6.18 kernels, EDID can cause extremely long delays while booting. Can you recompile the kernel and unset CONFIG_FIRMWARE_EDID?
 
Old 10-16-2006, 11:40 PM   #9
mdkusr
Member
 
Registered: Nov 2004
Location: P-town
Distribution: Slackware 10.2
Posts: 72

Original Poster
Rep: Reputation: 15
Fixed everything just by doing make oldconfig, though I have only tried this on my Slackware 11 setup so for other distros I am just unsure.
 
Old 10-17-2006, 01:50 AM   #10
snakle
LQ Newbie
 
Registered: Oct 2006
Posts: 14

Rep: Reputation: 0
I recompiled without CONFIG_FIRMWARE_EDID and ... I still get a black screen as soon as I select the 2.6.18 kernel from Lilo
 
Old 10-17-2006, 02:24 PM   #11
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 151Reputation: 151
Have you tried booting in plain old text mode with the vga = normal setting? If that works it might be that you're using a display value that you can't display (I use 773, 1024x768x256). If you can't find a mode that works then there's probably a missing option in your kernel config. I have an nVidia 6600GT and use the following settings:
Code:
#
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
# CONFIG_FB_RIVA_DEBUG is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON 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_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_7x14=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
 
Old 10-17-2006, 03:34 PM   #12
kevkim55
Member
 
Registered: Dec 2005
Location: Edmonton
Distribution: BLFS, Gentoo
Posts: 353

Rep: Reputation: 32
snakle, remove the parameter vga = 791 from lilo.conf (or reaplace it by vga=ask) and try booting into linux. If it succeeds, it must have to do with video resolution. Otherwise, you'll have watch out for the last message you see on screen before it goes blank.
 
Old 10-18-2006, 12:08 AM   #13
snakle
LQ Newbie
 
Registered: Oct 2006
Posts: 14

Rep: Reputation: 0
ok... i booted with vga=normal and it actually booted, but I still have a couple questions
1. why doesn't my usb keyboard work? It worked with 2.4.33.3
2. why can't I use 1024x768... it worked before (i hate small resolutions with a passion)
3. why no penguin icon in the top left corner
 
Old 10-18-2006, 02:32 PM   #14
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 151Reputation: 151
1. The settings for USB are different between 2.4.x and 2.6.x kernels - have you confirmed that you have HID device support as well as USB support?
2. You should be able to use 1024x768 - try the other colour depths and confirm that you have fb support and fonts selected in your kernel .config
3. Not sure about this one - your settings for CONFIG_LOGO look OK
 
Old 11-20-2006, 07:07 PM   #15
shubb
Member
 
Registered: Oct 2003
Location: San Francisco
Distribution: Slackware 13.37
Posts: 150

Rep: Reputation: 16
In case you had not been able to fix this, I just came across this and figured out how to fix it.

When you're configuring the kernel, enable this in the kernel

Device Drivers -> Graphics Support -> Console display driver support -> Framebuffer Console Support

If you like having the penguin, enable this:

Device Drivers -> Graphics Support -> Logo configuration -> Bootup logo
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Custom kernel image on custom slack build using CUSS nykey Slackware 2 07-15-2006 03:05 AM
odd mandriva issue goofusbrain Linux - Networking 1 11-13-2005 06:09 PM
Diablo II under 9.3...odd cd mount issue crxgames Suse/Novell 2 06-03-2005 12:54 AM
Odd *nix issue with c/c++ Will_C_T Programming 3 09-09-2004 11:17 PM
LILO on NTFS mbr might be causing an issue mipia Slackware 5 08-13-2003 05:16 PM


All times are GMT -5. The time now is 01:19 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration