You are not logged in.

#1 2008-03-09 12:24:42

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

[solved] (nVidia the prob?) - First Kernel Panic with Latest Update

After I ran the latest pacman -Syu my system is encountering a Kernel Panic at startup. It says something about that no filesystem could mount my root partition.

Now as I never had that before in my life - what can I do? smile

Last edited by Stalafin (2008-03-09 20:19:39)

Offline

#2 2008-03-09 15:26:55

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

No ideas? I will post any logs u want! hmm



Fallback is working of course...

Last edited by Stalafin (2008-03-09 15:27:12)

Offline

#3 2008-03-09 16:07:28

tigrmesh
IRC Op
From: Florida, US
Registered: 2007-12-11
Posts: 794

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

Try http://bbs.archlinux.org/viewtopic.php?pid=339949.

Last edited by tigrmesh (2008-03-09 16:56:44)

Offline

#4 2008-03-09 17:02:18

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

I have tried the approach mentioned in the thread. Yet, it didn't work out for me. I am on fallback again.

It looks like kernel26-2.6.24.3-3 was the first one that failed me.

I tried kernel26-2.6.24.3-1 first, and then kernel26-2.6.24.1-2, which both didn't work either after rebooting. Installing them gave me a success in both cases.

I received the following message:

No filesystem could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

What can I do about that now?
Current Kernel:

$ pacman -Q kernel26
kernel26 2.6.24.1-2

This one did work of course... (in the past)

Last edited by Stalafin (2008-03-09 17:02:29)

Offline

#5 2008-03-09 17:53:35

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

I ran mkinitcpio -p kernel 26 and received the following output:

$ sudo mkinitcpio -p kernel26
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
/etc/mkinitcpio.conf: line 1: state.NVidia: command not found
/etc/mkinitcpio.conf: line 2: control.1: command not found
/etc/mkinitcpio.conf: line 3: comment.access: command not found
/etc/mkinitcpio.conf: line 4: comment.type: command not found
/etc/mkinitcpio.conf: line 5: comment.count: command not found
/etc/mkinitcpio.conf: line 6: comment.range: command not found
/etc/mkinitcpio.conf: line 7: iface: command not found
/etc/mkinitcpio.conf: line 8: name: command not found
/etc/mkinitcpio.conf: line 9: value.0: command not found
/etc/mkinitcpio.conf: line 10: value.1: command not found
/etc/mkinitcpio.conf: line 11: syntax error near unexpected token `}'
/etc/mkinitcpio.conf: line 11: `    }'
:: Begin build
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.d/kernel26-fallback.conf -g /boot/kernel26-fallback.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [ide]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [raid]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS

I suspect there is something wrong with my mkinitcpio; here is my mkinitcpio.conf:

state.NVidia {
    control.1 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 2
        comment.range '0 - 31'
        iface MIXER
        name 'Front Playback Volume'
        value.0 27
        value.1 27
    }
    control.2 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 2
        iface MIXER
        name 'Front Playback Switch'
        value.0 true
        value.1 true
    }
    control.3 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 2
        comment.range '0 - 31'
        iface MIXER
        name 'Surround Playback Volume'
        value.0 28
        value.1 28
    }
    control.4 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 2
        iface MIXER
        name 'Surround Playback Switch'
        value.0 true
        value.1 true
    }
    control.5 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 1
        comment.range '0 - 31'
        iface MIXER
        name 'Center Playback Volume'
        value 28
    }
    control.6 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 1
        comment.range '0 - 31'
        iface MIXER
        name 'LFE Playback Volume'
        value 28
    }
    control.7 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 1
        iface MIXER
        name 'Center Playback Switch'
        value true
    }
    control.8 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 1
        iface MIXER
        name 'LFE Playback Switch'
        value true
    }
    control.9 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 2
        comment.range '0 - 31'
        iface MIXER
        name 'Side Playback Volume'
        value.0 28
        value.1 28
    }
    control.10 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 2
        iface MIXER
        name 'Side Playback Switch'
        value.0 true
        value.1 true
    }
    control.11 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 2
        iface MIXER
        name 'Headphone Playback Switch'
        value.0 true
        value.1 true
    }
    control.12 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 2
        comment.range '0 - 31'
        iface MIXER
        name 'Mic Playback Volume'
        value.0 31
        value.1 31
    }
    control.13 {
        comment.access 'read write'
        comment.type BOOLEAN
        comment.count 2
        iface MIXER
        name 'Mic Playback Switch'
        value.0 true
        value.1 true
    }
    control.14 {
        comment.access 'read write'
        comment.type INTEGER
        comment.count 2
        comment.range '0 - 31'
        iface MIXER

Is it normal that there is such an entry? Is there maybe something missing?

EDIT: That control.14 part is obviously messed up...

Last edited by Stalafin (2008-03-09 17:59:40)

Offline

#6 2008-03-09 17:59:01

fwojciec
Member
Registered: 2007-05-20
Posts: 1,411

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

your mkinitcpio.conf does not look like a mkinitcpio.conf.  I suggest reinstalling the "mkinitcpio" package and, if necessary, copying /etc/mkinitcpio.conf.pacnew as /etc/mkinitcpio.conf.

Offline

#7 2008-03-09 18:01:00

Stalafin
Member
From: Berlin, Germany
Registered: 2007-10-26
Posts: 617

Re: [solved] (nVidia the prob?) - First Kernel Panic with Latest Update

I thought about that - the point is, I don't have anything like a mkinitcpio.conf.pacnew...

But yeah, I gonna reinstall it rite now.


EDIT: Alright, I deleted my old mkinitcpio.conf and got a new one. Shall I reinstall the graphics drivers? Looks like they have a connection to the whole thing.

EDIT2: Killed the old mkinitcpio.conf, reran sudo mkinitcpio -p kernel26, rebooted the system. Everything works nicely now. I still don't know what caused my old mkinitcpio.conf to become such a mess. Should I submit a bug report or something?

Last edited by Stalafin (2008-03-09 18:27:01)

Offline

Board footer

Powered by FluxBB