You are not logged in.
Hi all,
I recently upgraded the kernel26, one was supposed to write "radeon" in modules array in the mkinitcpio.conf which I did, ...now I can't get past the loading of modules after udev-events. It gets stuck there, and if I do a Cntrl + C and try to login as root, so that I can edit the mkinitcpio.conf and disable KMS and regenerate mkinitcpio, system tells me I can't write to the file. It's read only even though I'm root!
Same problems when I boot into single mode - I don't have write permission to any system file.
Update: I tried the Arch live cd and could chroot into my partition and remove "radeon" in the mkinitcpio.conf file, but I cannot regenerate the kernel. All I get is failed errors...
Any ideas?
Thanks.
Last edited by new2arch (2009-10-16 07:23:47)
Offline
I have the very same problem.
At booting my system hangs afer modules and I can only push the power button.
My graphics card: ATI Radeon Mobility 7500
In the meantime I have installed kernel26-lts, it works perfectly!
Offline
Update: I tried the Arch live cd and could chroot into my partition and remove "radeon" in the mkinitcpio.conf file, but I cannot regenerate the kernel. All I get is failed errors...
How did you try regenerating the initramfs? I had the same problem (has anyone filed a bug report?) and recovered via the chroot/mkinitcpio method. Remember that you need to generate an initrams for different kernel than the one you're running.
On another note, kms works fine for me "late".
Offline
Ajaj, same problem here.
Offline
I tried radeon.modeset=0 and nomodeset in grub and radeon.modeset=0 in the /etc/modprobe.d/modprobe.comf file.
Sometimes after the modules the screen goes to full screen but then it hangs completely without showing anything.
For installing another kernel: I just took the kernel26-lts package from the repos and installed it with this instructions:
http://wiki.archlinux.org/index.php/Kernel_Panics
It created another image with *-lts at the end and I added it to grub.
Offline
Right, the wiki instructions are for installing another kernel, and basically identical with my post. The OP asked for rebuilding the initramfs:
chroot, adjust mkinitcpio.conf/modprobe.conf, then run:
mkinitcpio -v -k <kernel version-ARCH> -g /boot/kernel26.img.
Offline
Hi all, thanks for replies.
I cannot access my main Arch computers right now and internet connection
is really flaky...but I will try to piece together what I have done and
what I will try to do with the broken system.
@PeteMo - Chrooting: I think I did something wrong because now
that I think about it the chrooting failed. I got an error message
saying /bin/bash command not found or similar (I followed the kernel panic wiki).
Sorry. I was sitting in the office, failed the update and got pretty stressed
because I had a plane to catch. So, the only thing I managed to do
via the live cd was to mount my boot and / partitions.
And all mountings could be done only to /mnt not /mnt/boot for
instance (if I remember the Arch wiki "kernel panic" instructions
correctly)
At this point I had write permission to mkinitcpio.conf but the regeneration well,
I am pretty lost here.
@hokasch - logging in as a single user, root, by interrupting the boot
process, I become "root@(none)".
Funny thing is I have only read permission on all
system files. Maybe the file system are not properly mounted
as read-write because of the early hickup during boot?
@Doehni and Hokasch - I wish I could install another kernel but
again I am totally stuck because mounting my partitions are only
half-baked as it seems and also chrooting fails...
I have a clonezilla mirror that I can use if nothing can be done
to remedy this problem but I am willing to try to do everything I can before I
do that.
Thanks again for all replies.
Offline
I personally have a great talent screwing up my install in times I really need it and can not spare half a day just fixing it again - but mostly that goes like "I'm bored with the stuff I really have to finish now, hey, let's try out KMS (or whatever)".
For when you have more time and access to the machine:
I did not mean adding "single" to the kernel line, but parameters that may turn off modesetting^^.
If you try chroot again, it is important to follow all the steps in the "kernel panics" wiki (sys/proc/dev), in the correct order (first mount root, then your boot partition inside it).
To rebuild the initramfs, you have to specify the kernel version (-k) and the output file (-g).
Offline
wrong topic
Last edited by Szelek (2009-10-13 07:48:51)
Offline
radeon.modeset=0 takes me past udev, but now the pc stops saying checking my partitions had a failure, press ctrl-d to reboot or root password to continue for manual maintanence... how can I fix that?
Offline
yikes. what filesystem is your partition? try the corresponding .fcsk and look for a more descriptive error message.
Offline
ext4, I'll do that. But just one thing, what do I type? Plainly fcsk?
Offline
fsck.ext4 followed by your partition (/dev/sdXX)
Offline
Somehow this time there was no error. I tried late start this time, but no compositing effects. So I disabled the thing. How do I know if I should use intel_agp?
Offline
no idea what you mean with intel_agp, but here is a nice script to troubleshoot compiz: compiz-check. you can get it from the aur.
Offline
from the wiki:
2) Add "radeon" (without quotes) to MODULES array in /etc/mkinitcpio.conf. Depending on your chipset it may be necessary to add "intel_agp" before the radeon module.Offline
This may sound obvious, but check the "Ati/Amd bar and grill thread..the last 2-3 pages. They were very useful in getting my modules to work after the upgrade, there are some module that need to be blacklisted for these to work
Offline
Just had the same problem with the boot process getting stuck at "Modules loading ...". Adding intel_agp solved it for me.
Offline
Same here, I have to add intel_agp to the modules line as well.
Offline
I personally have a great talent screwing up my install in times I really need it and can not spare half a day just fixing it again - but mostly that goes like "I'm bored with the stuff I really have to finish now, hey, let's try out KMS (or whatever)".
For when you have more time and access to the machine:
I did not mean adding "single" to the kernel line, but parameters that may turn off modesetting^^.
If you try chroot again, it is important to follow all the steps in the "kernel panics" wiki (sys/proc/dev), in the correct order (first mount root, then your boot partition inside it).
To rebuild the initramfs, you have to specify the kernel version (-k) and the output file (-g).
Hi again, thanks.
I will have access to my laptop tomorrow and will update you guys how it went. ^^
Offline
Hi all,
Managed to chroot into my system and downgrade the kernel (an upgrade to the most recent kernel followed).
Added nomodeset into the menu.lst and everything's well again.
Thanks!
Offline