Ticket #1756 (closed defect: worksforme)

Opened 1 year ago

Last modified 1 year ago

lfslivecd-x86-6.3-r2032 freezes on boot

Reported by: kitche Assigned to: livecd@linuxfromscratch.org
Priority: highest Milestone: 6.3
Component: CD Version:
Keywords: Cc:

Description

I have an intel chipset when I boot up the livecd it gets stuck trying to detect devices, irqs. lfslivecd-x86-6.2.5 seems to work fine on the computer

Attachments

lspci output (1.9 kB) - added by kitche on 09/27/07 10:24:58.

Change History

09/27/07 07:26:32 changed by alexander@linuxfromscratch.org

Very interesting.

Could you please post the last few lines of output from the non-working r2052 CD (or, better, boot with vga=795 or vga=792, and attach a photo of the screen to this ticket), and the "lspci && lspci -n" output from any working system?

Have you tried the following troubleshooting options?

linux noapic nolapic pci=noacpi nomsi clock=pit

09/27/07 07:27:45 changed by alexander@linuxfromscratch.org

If you have a working config for a 2.6.22.X kernel, please attach it too - it will help. In the case of problems with Trac, send mail to livecd@linuxfromscratch.org.

09/27/07 10:24:58 changed by kitche

  • attachment lspci output added.

09/27/07 10:25:17 changed by kitche

linux noapic nolapic pci=noacpi nomsi clock=pit worked to get into the cli environment for my computer.

The last few lines of the boot without the above troubleshooting is ICH4: chipset revision 2 ICH4: not 100% native mode: will probe irqs later

ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:pio

I have attached lspci && lspci -n output

09/27/07 22:10:57 changed by alexander@linuxfromscratch.org

Resolution: this is a hardware or BIOS bug, not a LiveCD bug. The fact that you were able to get to the command line means that the CD worked as it would normally do. In order to get to the GUI, everyone (not only you) has to run the "startx" command, i.e., the CD never starts the GUI automatically.

Try upgrading your BIOS.

The troubleshooting options for LFS-6.3 LiveCD are all (except nolapic and/or clock=pit, depending on the LiveCD revision) listed in the boot loader help screen. Press F4 to see them.

BTW, could you please determine the minimal subset of troubleshooting options that still allow your computer to boot this CD?

09/27/07 22:18:10 changed by alexander@linuxfromscratch.org

As for the lspci output: you have two video cards. The LiveCD is known to activate a random video card in xorg.conf by default in this setup, so you have to edit this file before running "startx".

Also, if you use a dual-head setup, could you please confirm or deny the following issue (first noticed on the Xorg development list): "if one of the video cards uses the intel driver, one cannot configure dual-head even by hand, because Xorg crashes when two video drivers are loaded and only one of them (intel) supports RandR-1.2"?

09/30/07 17:04:25 changed by kitche

Sorry but can't update bios since there is no update.

This is the minimal troubleshooting options that allow my computer to boot linux noapic nolapic pci=noacpi nomsi clock=pit. I do not use dual-head setup at all

but no clue why you guys brought up X when it deals with booting the livecd with just using linux since it seems the 6.3 livecd is the only one that I have to use any options on to even get it to boot. guess I'll just have to use the troubleshooting options to get the cd working

Just so you guys know, I do know a bit about how to get a system working also. I worked on SourceMage? for a while

10/02/07 03:18:34 changed by alexander@linuxfromscratch.org

Sorry for the delay with the answer - the conference on semiconductor physics really eats all my time.

This is the minimal troubleshooting options that allow my computer to boot linux noapic nolapic pci=noacpi nomsi clock=pit.

Sorry, this does not look minimal. You can almost certainly remove nomsi - please try it. Please try removing other options and report the _really_ minimal workaround. The question about a working 2.6.22 config still stands.

I do not use dual-head setup at all, but no clue why you guys brought up X

This was just a side question, since your lspci indicated that you can reproduce the (completely unrelated) dual-head bug. The real problem is that nany people who encounter bugs do not report them (maybe because they don't recognize such issues as bugs), so I try to use the existing bug reporters as much as possible.

11/30/07 08:20:15 changed by alexander@linuxfromscratch.org

  • status changed from new to closed.
  • resolution set to worksforme.

No feedback, closing.