HAL seems to be defective for ThinkPad T42p

When doing safe graphis mode, the machine comes up (with too low resolution), and I get the error "internal error. failed to initialize HAL"

CD integrity check was passed

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22.
Actually, I hesitate(d) between this and Casper, because you get quite long in the booting process.

I suppose this is the Live CD for PC (Intel x86) desktop CD
that is found on: http://cdimage.ubuntu.com/releases/gutsy/tribe-3/
Or is it Kubuntu?

I find it surprising that you can't switch to console.
By using Ctrl-Alt-F1 or Ctrl-Alt-F2 ? (suppose to come back to graphics window with Ctrl-Alt-F7)

The other trick you could try is, before pressing Enter when booting with CD, press F6
and remove 'quiet splash' before the '--', then press Enter. This MAY help to see error
messages while booting.

Basically, what I hope to do is going to console and get the files requested for a kernel bug.
We normally ask for it with:
"Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!" but until you can get these files and save them somewhere for retrieving them later with a working GUI and Internet access, we may have to work a bit.

Thanks a lot for your reply!

This is the normal (i.e. not "alternative") desktop live CD for x86. It is Ubuntu, not Kubuntu.

Until now, it was this:
X came up, I saw the GNOME starting dialogue with the animated system icons, I saw the normal background (but not the image, only the colour) and a mouse cursor, but that's it. When pressing Ctrl+Alt+Backspace, the background flashed once and the mouse cursor disappeared. Doing Ctrl+Alt+Backspace a second time didn't work. When booting up in safe mode, the boot worked, but I received the "error initializing HAL" error message in a GNOME dialog box.

All of a sudden, it works! I use the same machine and the same CD-R I tried to boot up from before, and it works even with the non-safe mode!
I tried leaving the default resolution in the CD's GRUB boot menu on "VGA", then it worked. However, the 1600x1200 are being detected and displayed correctly as soon as GNOME starts up.

Once, I had nautilus, panel and evolution-alarm-notify crashing, but the it didn't occur again.

Messages during the bootup on console are something like
- intel_rng: FWH not detected
and
- four files not found:
/var/lib/acpi-support/system-manufacturer
/var/lib/acpi-support/system-product-name
/var/lib/acpi-support/system-version
/var/lib/acpi-support/bios-version
(By the way, I think I didn't see the console when booting up directly in 1600x1200)

I think I tried out leaving the resolution at VGA even before (but I am not 100% sure), so here are some changes I did the last days on my machine:
- I repartitioned my hard drive, removing my previously existing Vista partition and installed XP again
- I updated my BIOS to the most recent one (had also a recent one before, but a new version came out some weeks ago)

I read the HAL error can be caused by mounting errors, so maybe the Vista partition was the culprit?

In conclusion, my bug seems to be partially invalid, but Ubuntu still doesn't boot up correctly with 1600x1200 when I set this in the CD's GRUB bootloader.

I am happy to see that it works now for you, at least, without specifying 1600x1200.

About intel_rng: FWH not detected, according to bug #102982, this is just an information message saying that your hardware is not
able to generate 'true' random numbers, and can be safely ignored.

Seems to me that missing files are just identification information.
Still, it is a bit strange IBM don't include these files.

If you specify 1600x1200 when booting LiveCd, does it still:
"X came up, I saw the GNOME starting dialogue with the animated system icons, I saw the normal background (but not the image, only the colour) and a mouse cursor, but that's it."?

Frankly, I would suggest we close the bug, unless you feel like giving a lot of information for a bug that would probably take
a long time to be fix anyway because it would have low priority.

I just tried removing "quiet splash" (the -- is still there) and going to a resolution of 1600x1200 in GRUB. I just see nothing during the bootup process, just a blank screen. But: When booting without "quiet splash" in 1600x1200, GNOME comes up! Maybe this is kernel related, that the framebuffer device doesn't start properly? I didn't have this with Feisty, it worked out of the box with 1600x1200 bootup. Only thing I saw is that the shutdown bootsplash doesn't work, I see a "destroyed" background image when shutting down from GNOME.

I verified a second time, and when removing "quiet splash", it works, when leaving it in, it doesn't work.

And a little correction: When doing with quiet splash, I see no starting dialogue (this one doesn't come up also when doing without quiet splash), and I see the normal background, not the wallpaper. Mouse cursor is visible. Switching to console leads to flashing, background is visible again, mouse cursor isn't.

Well, I guess I will let a developer look at this.
But first, I would need you to give the usual information for a bug related to kernel.
Just boot (with VGA option I guess) and include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Thanks again! Here is the requested information.

I now tried with Tribe 4, and I don't see any bootsplash at all when booting in 1600x1200
Funny part: GNOME boots up correctly...

The broken shutdown screen (bootsplash) is also there on the LiveCD. It shows the brown background image, with horizontal lines, instead of the Ubuntu logo.

Addendum: This only happens in LiveCD. Installed systems works fine, as bootsplash runs 640x480 there.

Sorry for this much reports, but I think the problem lies much deeper. Maybe a problem wit HAL?

Upon installation, applications randomly crashed and the whole system is *terribly* slow. Even normal menu actions have some seconds delay, and now, finally, GNOME only starts up again in safe mode. When I start it up in normal mode, it hangs at the same position it does sometimes from the LiveCD.

CPU runs on 600 MHz most of the time, only sometimes jumps for some seconds to 2 GHz.

Previous Ubuntu version ran fine on my machine. Tribe4 is unusable for me. :-(

Addendum:
Before my installation finally gets crashed, my GNOME network manager icon disappears and I can't get it to come up again. After a reboot, no logon - other than in GNOME safe mode - is possible anymore.

Seems to be fixed in 8.04.
Don't have enough rights to close this bug, so please close. ;-)

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

As per comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/127535/comments/16, Florian Effenburger has confirmed this is now fixed in 8.04. Marking it at fix released.