LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 03-16-2013, 07:47 AM   #1
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Rep: Reputation: Disabled
Unhappy Cant boot my old pc


Hello ,

I have this error showing when booting my debian:

Driver 'pcspkr' is already registered, aborting.

I have read that I should disable snd-pscp module in /etc/modprobe.d/blacklist.conf. But after I did that, I'm still unable to boot my system.

This is what displays:

[10.175214] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
[10.175223] [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output 0
[10.181152] Console: switching to colour frame buffer device 240x67
[10.188268] registered panic notifier
[10.188302] [drm] Initialized nouveau 0.0.15 20090420 for 0000:01:00.0 on minor 0
udevadm settle - timeout of 180 seconds reached, the event queue contains:
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda (718)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda/sda1 (719)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda/sda2 (720)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda/sda5 (721)
/sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda/sda6 (722)
/sys/devices/pci0000:00/0000:00:1f.1/host1/target1:0:0/1:0:0:0/block/sdb (731)
/sys/devices/pci0000:00/0000:00:1f.1/host1/target1:0:0/1:0:0:0/block/sdb1 (732)
done (timeout).
udevd[294]: worker [327] unexpectedly returned with status 0x0100
udevd[294]: worker [327] failed while loading '/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sda'
udevd[294]: worker [317] unexpectedly returned with status 0x0100
udevd[294]: worker [317] failed while loading '/devices/pci0000:00/0000:00:1f.1/host0/target0:0:1/0:0:1:0/block/sdb'


I can type text on screen, but cannot run any command (nothing happens on enter). I thought it may be problem with my partitions, but I'm able to mount them using live distributions. Anyway, I have checked them using e2fsck and even repaired superblock successfully. But nothing has changed, still got the same error

Please, what can cause the problem? What would you do (try) in my situation?
Thank you in advance
 
Old 03-16-2013, 10:18 AM   #2
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
What's tha box? Does it really have a 240x67 screen?
 
Old 03-16-2013, 11:04 AM   #3
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
I dont know why theres "240x67" ... I have there installed server version of debian without graphic manager. It is connected to monitor with native resolution 1920x1080
 
Old 03-16-2013, 02:59 PM   #4
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
I would try booting from an install dvd or cd, and run an fsck on the disks. That failing, you can add

init=/bin/bash

to the boot line, but you halt with a ro / and one terminal and you have to start from there
Quote:
PATH=/bin:/sbin:/usr/bin:/uisr/sbin
mount -o remount, rw /
Then go to /etc/inittab, set the console run level, usually something like
Quote:
id:3:initdefault:

and see if you can boot that. I'm suspicious of some interrupt lockup in the pci bus. Other possible boot options on the kernel command line

noapic
or

pcie_aspm=force

or

pcie_aspm=off
 
1 members found this post helpful.
Old 03-16-2013, 04:00 PM   #5
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
Thank you for helping me,

Unfortunately, I'm not sure if I understand what I should do.

I have hiren's cd and theres Parted Magic live distro (I was able to mount my filesystem using it and backup some files). I have already checked partitions with e2fsck.

So, just to be sure, you want me to:

1. In Grub, edit boot options and add "init=/bin/bash"
2. Rewrite line with "rw /" option to "ro /"
3. edit /etc/inittab and set to "id:3:initdefault:"
4. restart and boot

if this doesnt work, I should edit grub boot options and add "noapic" or "pcie_aspm=force" or "pcie_aspm=off"

Is this right? Thank you
 
Old 03-17-2013, 03:46 AM   #6
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
I have eddited /etc/inittab and replaced 2 to 3 so I have there "id:3:initdefault"

After this still unable to boot

So I kept it there and tried to edit grub options and added "pcie_aspm=force"
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=... ro pcie_aspm=force quiet

After this I was still unable to boot, but 2 new lines has appeared:

[12.038926] intel8x0_measure_ac97_clock: measured 55606 usecs (2672 samples)
[12.039006] intel8x0: clocking to 48000


So I tried to replace pcie_aspm=force with pcie_aspm=off
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=... ro pcie_aspm=off quiet

After this, still unable to boot (no new messages on screen)

So I tried "noapic" option
linux /boot/vmlinuz-2.6.32-5-686 root=UUID=... ro quiet noapic

After this still unable to boot and hangs on messages I have written in first post.

What next can I try, should I keep edits made to inittab?
 
Old 03-17-2013, 03:58 AM   #7
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
In /etc/inittab, there are usually comments that explain the runlevels It will have a list of numbers, usually 0 to 6 and tell you what they are. You want multiuser mode and not X11. What you provided is not enough for a serious diagnosis. Normally
1. you see grub stuff
2. It loads a kernel
3. It boots the kernel
4. It runs init, and finds the other disks
5. All your startup services are processed.
6. you get a bash console.

Exactly where do you get stuck - 'not boot' isn't enough. We can't fix vague errors, but we can diagnose specific errors. It would be good to see or know as much as you can show us.
 
2 members found this post helpful.
Old 03-17-2013, 06:07 AM   #8
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
I'm sorry I can't tell what stage it does hang on.

Here is my inittab
Code:
# The default runlevel.
#id:2:initdefault:
id:3:initdefault:

...
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
...
I will try to describe my problem as clearly as I can:
1. power on machine
2. see grub options
3. choose "Debian GNU/Linux, with Linux 2.6.32-5.686"
4. there are some messages, but I cant rewrite them they are quick
5. Messages from my first post shows, I can type text, but cant run any command (nothing happens after enter (you can see I wrote helo,help,pwd there))

I have made some pics of those quick messages and last screen is what I see and where it stops.

Also, I have uploaded some logs and more pics here http://buksy.netkosice.sk/senior/ I tried to empty logs first and then reboot, but they were still emtpy after reboot, so there are backups

Will this help to determine what stage is the problem one? What more can I do? Thank you
Attached Images
File Type: jpg __messages1.jpg (111.7 KB, 14 views)
File Type: jpg __messages4.jpg (99.3 KB, 10 views)
File Type: jpg __last_messages.jpg (70.8 KB, 11 views)

Last edited by buksy; 03-17-2013 at 06:14 AM. Reason: updated message
 
1 members found this post helpful.
Old 03-17-2013, 01:20 PM   #9
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
It seems to be the kernel that's running when the error occurs. Kernels usually moan big time and panic and fill your screen with bilge, but this just seems to be hanging. That sequence suggests a hardware problem.

Divide and conquer. Try booting from a live cd, or the like. It's got a different kernel. If it's a really old pc you might have issues with interrupt sharing, because that wasn't always possible. There's even a floppy linux that will boot to a console - and you can make the floppy under m$ windows - get the .zip to do that. To make under linux, use the tgz.
http://www.toms.net/rb

I'm also suspicious of that nouveau module, because all the errors come just after it loads. What exactly is the pc, & how old? Much Ram? etc.

What's the GPU?

Last edited by business_kid; 03-17-2013 at 01:23 PM.
 
1 members found this post helpful.
Old 03-17-2013, 02:58 PM   #10
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
It's about 10 years old. Bios writes copyright 1984-2001 , I'm not sure about the ram, here are the specs:
Intel Celeron 1.3GHz
Ram 3x128Mb or 256MB+64MB (probably this)
Geforce 2 MX 400 (64MB)
HDD 1x20GB & 1x140GB

I found my debian install cd, it's not so old 6.0.3 (current 6.0.7). I was able to run rescue mode
and it has started shell from my linux root partition. So it may be that newer kernel doesn't work.
I'm thinking about downgrading kernel (gotta google it), but, isn't it better to find what kernel
feature is causing the problem? How will I update my system if I won't be able to update kernel?

What should I do, should I try to replace kernel with older one to see if it works and then upgrade again and
try to set the new kernel to work with my system?

EDIT: PS: If I am able to run shell from my partition, isn't it possible to easily install older kernel using apt-get ?

Last edited by buksy; 03-17-2013 at 03:02 PM.
 
Old 03-18-2013, 05:01 AM   #11
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
Geforce MX-400 :-))).
I have one of those - working still. Don't use it. They have passed the stage that they could be given away free in breakfast cereal boxes. I got nervous because mesa kept getting updated, and the binary blob overwrites mesa libs (LibGL.so & co) with proprietary ones of unknown vintage.

That aside, on a 10 year old box, you might try one last boot. In the file /etc/modprobe.d/blacklist, add the line
Quote:
blacklist nouveau
On the kernel command line, put
Code:
noapic acpi=off
and try one last time. The fans are probably hard wired, but if the cpu fan is not running, turn it off quickly.
 
Old 03-19-2013, 04:04 PM   #12
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
I have tried blacklisting nouveau and adding "noapic acpi=off" to the boot options but it still didn't work. This time, my computer freezes with messages from first picture

If I run my computer just with blacklisted nouveau without editing boot options, it stops with messages from second picture

Last thing I tried was running without blacklisted nouveau and with "noapic acpi=off" boot options set, result is third picture.
Attached Images
File Type: jpg __DSC_0715.jpg (182.3 KB, 8 views)
File Type: jpg __DSC_0716.jpg (166.3 KB, 9 views)
File Type: jpg __DSC_0718.jpg (181.9 KB, 8 views)
 
Old 03-19-2013, 04:33 PM   #13
goumba
Member
 
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Debian Wheezy (7.0), Jessie (future 8) and Sid (unstable)
Posts: 508
Blog Entries: 2

Rep: Reputation: 55
This may or may not help, I've had similar happen when a libc update got botched... could type a command, hit enter, but no output. Maybe something to look into.
 
Old 03-20-2013, 04:47 AM   #14
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,131

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
For some reason that remains unclear to me, your box is not booting. Neither is it complaining of anything except possibly interrupts. The likelihood of a distro kernel going awol like that on even a 10 year old box is low, imho. There are some workarounds for dodgy hardware in the kernel, but you seem to have an Intel chipset, which are normally good enough.

Looking again at post #1, it's possible that udev is acting up. I've never seen bootup errors on udev, so I really don't know what to advise. Is this a fresh install? Does it boot other kernels/OSes? Like does it run from a live cd? Did anything lead up to this happening? What did you fix on it last before the problem started? You want to try for as much information as possible.
 
1 members found this post helpful.
Old 03-23-2013, 09:31 AM   #15
buksy
LQ Newbie
 
Registered: Mar 2013
Location: Slovakia
Distribution: Debian
Posts: 8

Original Poster
Rep: Reputation: Disabled
No, it is not a fresh install, it has been installed about a year ago. I am able to boot other distros (Parted Magic live, Debian rescue mode), I dont think this is a hardware failure.

I'm using this computer as web server mainly. I had there some dependency problems after installing python, had to fix it with apt-get -f. Later on I think I haddf run "apt-get update" and "apt-get upgrade".

I dont use this computer often, so I cant tell exactly what was the last action taken, but it should be upgrade.

Could you point me to any good tutorial on how to downgrade kernel? Is it necessary to run shell on that computer? Can I replace the kernel by just copying it without any install? What can be influenced and what directories should I back up first. I have backed up /boot


I have booted debian install cd in rescue mode and has run shell from my linux partition. I downloaded 'linux-image-2.6.32-5-686_2.6.32-48squeeze1_i386.deb' and tried to install it with dpkg -i. But I get the following error
dpkg: unable to access dpky status area: no such file or directory
 
  


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
Boot Camp (fixing boot loaders, learning your way around boot & chainloaders) Siljrath Linux - General 7 05-29-2007 11:22 AM
When I boot my comp. (dual boot sys-Suse 10.1 & Win XP) the first boot stalls. philip niedermeyer Linux - Desktop 5 11-13-2006 06:04 PM
Kind souls: help getting Mandriva install 2 boot? edit boot.ini/grub /boot device or NoMoreReinstallMS Linux - Newbie 1 08-09-2006 04:34 AM
GRUB: How to boot WinXP (NTLDR, NTDETECT.COM & BOOT.INI) from boot partition (EXT2) ? Rayen16 Linux - Software 1 05-25-2006 12:09 PM
failed features: boot.shm boot.loadmodules boot.swap cccc Suse/Novell 1 08-08-2005 07:23 AM


All times are GMT -5. The time now is 07:21 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