Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
boot hangs without error message - what now?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
commander-keen
n00b
n00b


Joined: 09 Oct 2013
Posts: 47
Location: Europe

PostPosted: Fri Oct 31, 2014 8:41 am    Post subject: boot hangs without error message - what now? Reply with quote

Hello,

I have a Gentoo installation that crashes on boot. [Kernel: 3.14.19]
Only problem is, I do not have an error message. However the last log comes from Nouveau:
Code:
nouveau [    DRM] MM: using CRYPT for buffer copies


Here is a screenshot with the last 23 lines I got:
http://students.fim.uni-passau.de/~schieder/nouveau.jpg

Whats the usual way to find out whats wrong in this situation?

Thanks in advance,
Max
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Fri Oct 31, 2014 2:07 pm    Post subject: Reply with quote

commander-keen,

Two things may have happened.
The boot may have contined normally but with no console output. In this case you can ssh in from another system and post dmesg.
dmesg will be helpful.

From your image, you are using the nouveau driver but not its free framebuffer console. There is no tux logo as a framebuffer provides.

dmesg (from the failed boot) and your kernel .config both on a pastebin would be useful but you may not be able to get dmesg
The output of lspci may be useful too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
commander-keen
n00b
n00b


Joined: 09 Oct 2013
Posts: 47
Location: Europe

PostPosted: Fri Oct 31, 2014 4:13 pm    Post subject: Reply with quote

Hi Neddy

thanks a lot for your help.
I booted the machine connected to a router (with a dhcp server) by ethernet. But the computer did not show up in the network so I guess it really gets stuck on boot.

I also checked the framebuffer console in the kernel config. Looks fine to me. :-(

Anyways here is my kernel config:
http://students.fim.uni-passau.de/~schieder/.config

And the output of lspci:
Code:

00:00.0 Host bridge: NVIDIA Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: NVIDIA Corporation MCP79 LPC Bridge (rev b3)
00:03.1 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: NVIDIA Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.4 RAM memory: NVIDIA Corporation MCP79 Memory Controller (rev b1)
00:03.5 Co-processor: NVIDIA Corporation MCP79 Co-processor (rev b1)
00:04.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB controller: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:08.0 Audio device: NVIDIA Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: NVIDIA Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: NVIDIA Corporation MCP79 Ethernet (rev b1)
00:0b.0 IDE interface: NVIDIA Corporation MCP79 SATA Controller (rev b1)
00:0c.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
00:17.0 PCI bridge: NVIDIA Corporation MCP79 PCI Express Bridge (rev b1)
02:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9600M GT] (rev a1)
04:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
05:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 07)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Fri Oct 31, 2014 4:41 pm    Post subject: Reply with quote

commander-keen,

You may not have both
Code:
CONFIG_DRM_NOUVEAU=y
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
and
Code:
CONFIG_FB_NVIDIA=y
CONFIG_FB_NVIDIA_I2C=y
CONFIG_FB_NVIDIA_DEBUG=y
CONFIG_FB_NVIDIA_BACKLIGHT=y
in the kernel at the same time. Thats two different drivers for the same hardware.
Nouveau gives you a framebuffer console for free. FB_NVIDIA is obsolete and should not be used.

Turn off FB_NVIDIA, rebuild and reinstall your kernel, tell us what happens when you reboot.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
commander-keen
n00b
n00b


Joined: 09 Oct 2013
Posts: 47
Location: Europe

PostPosted: Fri Oct 31, 2014 5:37 pm    Post subject: Reply with quote

Hi,

thank you for pointing out the conflicting Framebuffer drivers. I disabled the NVIDIA support.
But no luck so far, the problem remains. The boot still crashes at the exact same part, same output. :-(

Max
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43198
Location: 56N 3W

PostPosted: Fri Oct 31, 2014 5:57 pm    Post subject: Reply with quote

commander-keen,

OK, I was lazy - that looked so obvious. I'll look some more. Meanwhile, get into your chroot and check some timestamps. Just to make sure you really are trying your new kernel. It won't be the first time a user has solved their problem but not known it because they did not boot the new kernel :)

/usr/src/linux/.config should be the oldest file. It drives the build
/usr/src/linux/arch/x86/boot/bzImage should be newer, if not, it did not come from the .config file
/boot/<kernel_name> should have the same timestamp as bzImage.

Lastly, your bootloader should be loading /boot/<kernel_name>, have a look at its configuration file.
lilo users need to remember to run /sbin/lilo
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Fri Oct 31, 2014 6:04 pm    Post subject: Reply with quote

you might try enabling <*> /dev/agpgart (AGP Support) --->
I don't have mcp79 chipset but have not had luck with any chipset without enabling agpgart including a much older nvidia chipset.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5761

PostPosted: Fri Oct 31, 2014 8:37 pm    Post subject: Reply with quote

Try also enabling CONFIG_X86_SYSFB and CONFIG_FB_SIMPLE, they may increase your chances of getting *some* output.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Fri Oct 31, 2014 9:08 pm    Post subject: Reply with quote

rather than adding I'd suggest reducing:
Quote:
Graphics support --->
<*> /dev/agpgart (AGP Support) --->
--- /dev/agpgart (AGP Support)
< > AMD Opteron/Athlon64 on-CPU GART support
< > Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< > SiS chipset support
< > VIA chipset support
-*- VGA Arbitration
(2) Maximum number of GPUs
[ ] Laptop Hybrid Graphics - GPU switching support
Direct Rendering Manager --->
< > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ----
Frame buffer Devices --->
<*> Support for frame buffer devices --->
--- Support for frame buffer devices
--- Support for frame buffer devices
[*] Enable firmware EDID
[ ] Framebuffer foreign endianness support ----
[*] Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
*** Frame buffer hardware drivers ***
< > Cirrus Logic support
< > Permedia2 support
< > CyberPro 2000/2010/5000 support
< > Arc Monochrome LCD board support
[ ] Asiliant (Chips) 69000 display support
[ ] IMS Twin Turbo display support
< > VGA 16-color graphics support
< > Userspace VESA VGA graphics support
[*] VESA VGA graphics support
[ ] EFI-based Framebuffer Support
< > N411 Apollo/Hecuba devkit support
< > Hercules mono graphics support
< > OpenCores VGA/LCD core 2.0 framebuffer support
< > Epson S1D13XXX framebuffer support
< > nVidia Framebuffer Support
< > nVidia Riva support
< > Intel740 support
< > Intel LE80578 (Vermilion) support
< > Matrox acceleration
< > ATI Radeon display support
< > ATI Rage128 display support
< > ATI Mach64 display support
< > S3 Trio/Virge support
< > S3 Savage support
< > SiS/XGI display support
< > VIA UniChrome (Pro) and
< > NeoMagic display support
< > IMG Kyro support
< > 3Dfx Banshee/Voodoo3/Voodoo5 display support
< > 3Dfx Voodoo Graphics (sst1) support
< > VIA VT8623 support
< > Trident/CyberXXX/CyberBlade support
< > ARK 2000PV support
< > Permedia3 support
< > Fujitsu carmine frame buffer support
< > SMSC UFX6000/7000 USB Framebuffer support
< > Displaylink USB Framebuffer support
< > Virtual Frame Buffer support (ONLY FOR TESTING!)
< > E-Ink Metronome/8track controller support
< > Fujitsu MB862xx GDC support
< > E-Ink Broadsheet/Epson S1D13521 controller support
< > AUO-K190X EPD controller support
[ ] Simple framebuffer support
[*] Backlight & LCD device support --->
--- Backlight & LCD device support
<*> Lowlevel LCD controls
< > Platform LCD controls
<*> Lowlevel Backlight controls
< > Generic (aka Sharp Corgi) Backlight Driver
< > Generic PWM based Backlight Driver
< > Apple Backlight Driver
< > Tabletkiosk Sahara Touch-iT Backlight Driver
< > Backlight Driver for ADP8860/ADP8861/ADP8863 using WLED
< > Backlight Driver for ADP8870 using WLED
< > Backlight Driver for LM3630A
< > Backlight Driver for LM3639
< > Backlight driver for TI LP855X
< > Sanyo LV5207LP Backlight
< > Rohm BD6107 Backlight
Console display driver support --->
-*- VGA text console
[*] Enable Scrollback Buffer in System RAM
(256) Scrollback Buffer Size (in KB)
<*> Framebuffer Console support
[*] Map the console to the primary display device
[ ] Framebuffer Console Rotation
[*] Bootup logo --->
--- Bootup logo
[ ] Standard black and white Linux logo
[ ] Standard 16-color Linux logo
[*] Standard 224-color Linux logo
should boot to the CLI (or different problem)
_________________
Defund the FCC.
Back to top
View user's profile Send private message
commander-keen
n00b
n00b


Joined: 09 Oct 2013
Posts: 47
Location: Europe

PostPosted: Sat Nov 01, 2014 8:28 pm    Post subject: Reply with quote

Hi everyone,

first of all thank you all very much for your ideas. Today I once more experimented with lots of different kernel configurations following your hints. But no matter what I tried I always ended with the kernel crashing at the very same step. By comparing to a proper nouveau bootup on a different machine I figured the crash occurs shortly before turning on KMS. So I eventually figured I might sidestep the problem rather than solving it. Long story short, staring the kernel with the argument
Code:
nomodeset

did the job. The fonts on the TTYs are a big clumsy now but I reach the login prompt.
Not sure if I should mark the thread as solved :-/ but I am happy.

Max
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
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