You are not logged in.
Same here: "Decompressing Linux" and then reboot itself after update 2.6.30 to 2.6.30.1
i686.
Asus eeePC1000H: 1024 RAM, Intel Atom CPU, Intel Mobile 945GM/GMS/GME Graphic Card
Offline
For all of you still with this problem (and JFS filesystem), read the bugreport (brain0 und my last posts at the end) for the solution.
http://bugs.archlinux.org/task/15416
Offline
Same here: "Decompressing Linux" and then reboot itself after update 2.6.30 to 2.6.30.1. I use JFS file system
I seem to have Solved it for me,
1st using parted magic I did a disc check tried to reboot the same then used parted magic opened the boot file made a new folder copy paste system map, vmlinux files into the folder, then copy paste back to boot file using overwrite option reboot everything Ok. I done this on both i686 and x86_64 partitions they both now boot into the system.
64 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AuthenticAMD GNU/Linux
asus NVidia motherboard
NVidia 7600gs graghics
5gb ram
Last edited by mandog (2009-07-07 21:06:19)
I'm dyslexic Please do not complain about puntuation or spelling and remember most dyslexic people have above average iq.
Offline
Same problem! me too !!
(Intel i915, CPU 3.0G, ddr 400 1G ram. 320G Harddisk , in jfs File Sytem)
Offline
For all of you still with this problem (and JFS filesystem), read the bugreport (brain0 und my last posts at the end) for the solution.
http://bugs.archlinux.org/task/15416
Thank you for the solution!
Fixed by dual booting into Debian with kernel 2.6.21, chroot back to Arch and resync the kernel26 package.
x86_64 AMD JFS Grub
Offline
Hi,
I tried the solution in the bug tracker but received the error:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error.
In some cases useful infor is found in syslog - try dmesg | tail or so
Am I just making a dumbass newbie mistake or is something more serious going on here?
Thanks
Update - just tried running a fsck.jfs on the drive since I read a jfs partition can't be mounted until it's journal log is checked. I received the error
Error: Cannot open device /dev/sda1
Last edited by neosenate (2009-07-16 13:00:51)
Offline
I suffered from the same and I managed to bring my system back to life again with the install-cd. After that I blocked the kernel-upgrades in pacman.conf....
But for how long?
Does anyone know if the problem is solved and can the newest kernels boot from my JFS partition again?
Somewhere between "too small" and "too large" lies the size that is just right.
- Scott Hayes
Offline
Does anyone know if the problem is solved and can the newest kernels boot from my JFS partition again?
yes sir
ᶘ ᵒᴥᵒᶅ
Offline
Thanks, I'll will open my system for the newest kernels again
Somewhere between "too small" and "too large" lies the size that is just right.
- Scott Hayes
Offline
Hi Guys, I have the same Problem Here, with a fresh installation of Arch i686 , I used the net install image the one with isolinux bootloader, but cannot load any thing elp
keep rebooting after this message "Decompressing Linux".......................... Please Help me
Offline