Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1574 - no boot after updating

Attached to Project: Arch Linux
Opened by Bieler Batiste (faden) - Monday, 04 October 2004, 13:19 GMT
Last edited by Judd Vinet (judd) - Monday, 04 October 2004, 18:28 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I have installed archlinux 0.6 with a CDROM and everthing work fine. I updated to current ( maybe the kernel was updated ) and after that, the distrib don't boot anymore. The kernel load but nothing after that.
This task depends upon

Closed by  Judd Vinet (judd)
Wednesday, 06 October 2004, 18:19 GMT
Reason for closing:  Not a bug
Comment by Judd Vinet (judd) - Monday, 04 October 2004, 18:29 GMT
Are you using GRUB or LILO?

How far did the boot process get? Did you see any errors? When did it hang?
Comment by Bieler Batiste (faden) - Tuesday, 05 October 2004, 06:27 GMT
Finaly I add a ligne to tell pacman to dont upgrade kernel26 and it works. My computer seems to dont correctly handle the last kernel ( or the last kernel dont handle my computer ( or both )).
Comment by Bieler Batiste (faden) - Tuesday, 05 October 2004, 06:37 GMT
I am using lilo. I have tested GRUB and it dont boot ( I admit that I don't read the config file ).

With lilo it's booting with the default kernel in 06. An 2.6.3 kernel.

After updating I can see the loading points but after that nothing. I don't wait for a while because I was thinking my computer was frozen.

It's certainly due to a particular hardware configuration. Anyway it's a very annoying bug and I decide to reinstall all because I don't know another solution.
Comment by Judd Vinet (judd) - Tuesday, 05 October 2004, 16:21 GMT
Okay. You re-ran 'lilo' when you upgraded to the new kernel, right?

Also, try booting with "acpi=off" and/or "noapic". These features can be screwy on some hardware.
Comment by Bieler Batiste (faden) - Tuesday, 05 October 2004, 22:56 GMT
Oupss ... no I forget to re-ran lilo ... I certainly that

Loading...