You are not logged in.
Pages: 1
Hi,
Update to 2.6.20-7 lilo dropped out chrooted in rolled back kernel then rebooted kernel panic anyway using full image atm but cdrom is now at sr0?
Why does rolling back kernel a problem ?
Can I clean out old kernels and reinstall a kernel cleanly ?
Kinda bugging me as no one else seems to have a problem with new kernel
O lilo.conf
boot=/dev/sda
default=Arch
timeout=50
lba32
prompt
image=/boot/vmlinuz26
label=Arch
vga=791
root=/dev/sda3
initrd=/boot/kernel26.img
append="nmi_watchdog=0"
read-only
Last edited by Mr Green (2007-04-19 05:37:17)
Mr Green
Offline
I've had some issues with the new kernel as well, although not the ones your having. It keeps reading my pata drive as sda and messing up my drive names. I'm going to try tinkering around with grub so I don't have to use a live cd anymore.
Cancel That: I srcpac'd the kernel and everything went back to normal.
Last edited by jb (2007-04-19 00:22:07)
...
Offline
check this out
http://wiki.archlinux.org/index.php/Con … io#Problem
it may be whay you need
Offline
emm not noticed that in lilo before ... I will give it a go, always run lilo after kernel update, kept kernel26 in IGNORE in pacman.conf just to be on the safe side. This is first time I have a had a kernel problem in months.....
Mr Green
Offline
Lilo is now a big issue for me ... cannot run stock kernel at all ... added root line to append ... do I still need nmi_watchdog?
Cannot figure out why stock kernel will not boot
Get error rootfstype ?????? never had that before
This output from lilo
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
;-S
Last edited by Mr Green (2007-04-19 17:01:05)
Mr Green
Offline
wasn't nmi_watchdog needed with virtualbox?
maybe you got some incompatible vbox modules loading?
been messing with mkinitcpio? have you? or the presets?
other than the acpi modules change 2.6.20 series worked with the same settings as 6.19 for me.
Offline
emmm you have a point there .... but should not affect it .... but I will check [me memory not what it used to be!]
not touched mkinitcpio ever!
Virtualbox still runs ok ...
Just plain Weird.....
Thanks for heads up ... 8)
Mr Green
Offline
Pages: 1