current+KDE 4.7.4 attempting to install kernel 3.1.5
Apologies in advance for a long post...I wanted to make sure I covered everything I did up to this point.
Running slackware current w/Alien Bob's KDE 4.7.4 packages. Attempting to install Kernel 3.1.5 but not having much luck. It appears to not even boot far enough to get any messages in the log files or in the bootlogd /var/log/boot file. The steps I took using Alien Bob's "Building a Linux Kernel from source" as a reference: Code:
echo $DISPLAY Code:
unxz linux-3.1.5.tar.xz Code:
cd /usr/src/linux Code:
make bzImage modules Code:
# Linux bootable partition config begins Code:
mkinitrd -c -k 3.1.5-smp -f ext3 -r /dev/sda2 -m usb-storage:pcmcia_core:pcmcia:mmc_core:ssb:modprobe:ehci-hcd:mbcache:jbd:ext3 -u -o /boot/initrd-3.1.5-smp.gz Rebooted to test the new kernel and the loading process just stopped. Had to force a reboot and try again but the loading process stopped again but at a different place. The last line it would stop at was one of the following (paraphrasing): Quote:
If I try loading the new kernel with: Code:
init=/bin/bash On one occasion it appeared as if it was going to completely boot up. Right after the screen text changes when kms kicks in the screen cleared and I was left with a blinking cursor in the upper left corner. On another occasion right after kms kicks in it stopped with the last line being (paraphrasing): Quote:
Thanks in advance for any information. Cheers & Thanks System: Quote:
|
I don't have a solution (sorry), but I recently tried upgrading the kernel to 3.1.5 and was able to log into X, but once I got there the mouse & keyboard didn't work.
So I just wiped it all out, started from scratch, switched to current, and left the kernel as is. Unless your hardware isn't supported, there's no real advantage to upgrading the kernel for the hell of it. I just did it for a learning experience. All I learned in this case was that it's not worth the trouble unless I need to fix a security hole or address some unsupported hardware. |
I hope this helps
seems the 3.1.5 has had some changes please take time and read this http://www.x.org/wiki/radeonBuildHowTo it start with how to prep your kernel config ok. i wish you luck :) |
@R3V0LV3R
Quote:
Quote:
@Drakeo Thanks, I am familiar with that page. I used the information found there to get KMS working with the radeon driver when I had Slackware 13.1 installed because my monitor would lose signal right when KMS kicked in. I had to: Add nomodeset to the lilo append line. Blacklist drm and radeon (blacklisting radeon alone did not work for me). Load the drivers with KMS enabled right before starting X. I did not have to do any of this with Slackware 13.37. Now with Slackware current I still have a problem on occasion when booting: Once in a while the bootup process stops right when KMS should kick in. And I also see error messages on occasion in the log files: Quote:
Again, Thanks. |
I am posting now from Slackware current with kernel 3.1.5 using KDE 4.7.4.
So what exactly is the problem, I am not quite sure. The machine would stop loading at a point where it looked like it was wanting to load a printer driver (I have no printer attached) so I disabled the printer port in the bios. That got me a little further. I tried a live Gparted cd w/kernel 3.1.5 and I could not get it to load with any of the options even failsafe. Failsafe would give me an error about OHCI bios handoff failed. Researching this led me to disable the usb options in the bios (so I have no access to my mouse at this moment). I also had to add acpi=off to the lilo command line. And I'm in. Now if I can just figure out what is wrong. Anyone have any ideas on where to go from here? Thanks in advance... (am going back to kernel 2.6.38.7 so I can use my mouse... as working on a computer these days without a mouse is not very easy.) Cheers |
You're way more determined than me. It's funny because I was in the exact same situation a few days ago. Tried to go to the most up-to-date kernel simply because I had nothing else to do at the moment (sad isn't it?) and wanted to go to current so I could upgrade KDE.
After the kernel FAIL, I just reinstalled 13.37 and upgraded to current through slackpkg. I just decided the kernel wasn't worth risking yet another reinstall and 25 additional slack builds. Everything works swimmingly now. P.S. - Where in the heart of Texas are you? Corpus Christi native here. :cool: |
@R3V0LV3R
Determined? No. Just a stubborn San Antonio native here. Corpus Christi? I have fond memories of CC. Went to CCSU (early 90's). @ANYONE Additional information in case anyone can shed some light on the situation: Slackware current - KDE 4.7.4 - Kernel 3.1.5 Disabled in BIOS: serial port, parallel port, and USB. screenshot: http://imageshack.us/photo/my-images...apshot001.jpg/ dmesg: http://pastebin.com/4UDM341f bootlogd: http://pastebin.com/n194x7Te lspci http://pastebin.com/TmEywfJQ Cheers |
To summarize:
When using any of the following options I can get all the way into the system. Code:
acpi=off Notes on things I have tried: From: https://wiki.ubuntu.com/DebuggingACPI Quote:
The system would just stop loading with all the other options. It stops before any message is logged and I am not seeing any errors (just the standard lines that get output as something is loaded). Tried Code:
debug initcall_debug Quote:
https://bugzilla.redhat.com/show_bug.cgi?id=155794 The thread is old but it gave me some ideas on things to check. Disabling CPU frequency: Quote:
Try: Code:
idle=poll Quote:
Quote:
"idle=poll", "idle=mwait", and "idle=halt" work. Try turning cpuidle off: Code:
cpuidle.off=1 Quote:
Quote:
Code:
cat /boot/config | grep CONFIG_ACPI_PROCESSOR Quote:
Thanks in advance... Cheers |
I never could figure out how to get the system to boot up far enough to a point where something would get logged without using any of the options mentioned.
This page leads me to believe that my cpu supports c-state modes C0, C1, and C2. From: http://www.cpu-world.com/CPUs/Celero...552356%29.html Quote:
From: http://ark.intel.com/products/27131/...533-MHz-FSB%29 Quote:
As a work around I've added idle=halt to the cmdline since the intel website indicates that my cpu does not support idle states. System: emachines w3503 Kernel: 3.2.1 DE: KDE 4.8.0 WM: Compiz http://imageshack.us/photo/my-images...0snapshot.jpg/ http://imageshack.us/photo/my-images...0snapshot.jpg/ Cheers |
Just wanted to add that I installed the latest updates to current
and the problem still occurs with all the available (3.2.2) kernels (generic, generic-smp, huge, and huge-smp). None of them will boot up far enough to get anything helpful in the logs. And there are no obvious errors echoed to the screen. They all boot fine if I add the cmdline option "idle=halt". So if anyone has any helpful tips on how to isolate the problem... please let me know. Thanks in advance. Cheers I am running: Slackware current (up to date) with Alien Bob's KDE 4.8.0. I could not find a way to update the title of this thread. |
All times are GMT -5. The time now is 10:09 PM. |