Live CD 10.04 not bootable on FSC Lifebook E8010

[Gejza Büchler]

- The problem described in summary was confirmed on several (3-4 pieces) Fujitsu Siemens Lifebooks E8010: machine freezes, black screen, no disc activity
- The problem does not appear for example on Lifebook E8020 and also not on newer FSC notebooks or desktops, i.e. these machines can be booted from the Live CD fine.

Before "playing" with Live CD, the regular on-line upgrade of running 9.10 to 10.04 was performed. The results:
- The last running kernel in 9.10 is 2.6.31-21
- With upgrade to 10.04 the kernel 2.6.32-21 was installed
- Booting with this kernel (2.6.32-21) causes after several seconds the same result as booting from the Live CD: machine freezes, black screen, no HDD activity
- Machine is still bootable with previous kernel (2.6.31-21) and it "pretends" to be 10.04 (i.e. the kernel from 9.10, the rest from 10.04)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gejza 1404 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC203 at irq 11'
   Mixer name : 'Realtek ALC203 rev 0'
   Components : 'AC97a:414c4770'
   Controls : 31
   Simple ctrls : 20
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=eb5c3958-d6fb-4427-bff5-2a4382ad64b4
MachineType: FUJITSU SIEMENS LIFEBOOK E8010 INT
Package: linux (not installed)
ProcCmdLine: root=UUID=17a7bd6a-0796-42f8-9247-49d785b428fa ro single
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid kconfig needs-upstream-testing
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
WifiSyslog:

WpaSupplicantLog:

dmi.bios.date: 11/01/2004
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.10
dmi.board.name: FJNB185
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: E8010
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd11/01/2004:svnFUJITSUSIEMENS:pnLIFEBOOKE8010INT:pvr:rvnFUJITSU:rnFJNB185:rvr:cvnFUJITSUSIEMENS:ct10:cvrE8010:
dmi.product.name: LIFEBOOK E8010 INT
dmi.sys.vendor: FUJITSU SIEMENS

[Jeremy Foshee (jeremyfoshee)]

Hi Gejza,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 576294

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Gejza Büchler (buchlerg)]

apport information

[Piotr Goczał (bilbo-lodz)]

I've the same situation Ubuntu 10.04 (upgraded from 9.10) is running correctly on FS Lifebook E8410 but NOT working (the same "upgrade path") on FS Lifebook C1110. Now I'm running on 2.6.31-21 but got a lot of errors and strange behaviour during start up.

[Gejza Büchler (buchlerg)]

Just downloaded and installed the latest upstream kernel:
Linux pegas 2.6.34-999-generic #201005121008 SMP Wed May 12 10:11:28 UTC 2010 i686 GNU/Linux.
Described booting problem does not appear with this upstream kernel.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Gejza Büchler (buchlerg)]

I have tried to provide all the information requested by Jeremy on 2010-05-07. I don't know what "requested information may have been missing". Any suggestion?

Anyway, as the problem still persists, I have reopened this bug.

[Michael von Glasow (michael-vonglasow)]

I'm having the same problem with a Lifebook S7010, similar upgrade path:

Booted from a 9.x Live CD, everything fine. Installed OS, still everything OK. The upgrade to 10.x added a new kernel; with that, the system would hang on reboot with the same symptoms described above. Booting with the "old" kernel everything is fine and the system is fully usable. A few kernel upgrades I got since did not change this; the only kernel that works is the one originally installed with 9.x. The 10.x Live CD gives the same behavior as the upgraded kernel (hangs on boot), so I guess the issue affects multiple Lifebook models.

[Michael von Glasow (michael-vonglasow)]

PS: this might be the same issue as described in #568939. The S7010 has an Intel graphics chip, I'm just not sure about the exact model.

Last working kernel is 2.6.31-14-generic for me (I haven't tried any later 2.6.31 builds), 2.6.32 fails as described above.

[Michael von Glasow (michael-vonglasow)]

Two updates: the graphics chip in my Lifebook S7010 is an Intel 8285x (82852 or 82855, at least that's what the Windows driver supplied by Fujitsu-Siemens reports).

Second: today I downloaded the Ubuntu 10.10 Live CD and tried that. The system comes up without hanging, but the mouse pointer is missing. The mouse itself works - if I blindly aim for an object in the corner of the screen and click it, I get the desired action - but the pointer is invisible, which makes me suspect yet another graphics driver issue.

[Michael von Glasow (michael-vonglasow)]

I see the mouse pointer issue has already been reported as #631494.

This issue here seems in act identical to #568939, we might want to close one of the two with reference to the other.

[Michael von Glasow (michael-vonglasow)]

Upgraded to 10.10 Maverick today, and the issue is gone. Screen output is fine, I am also getting a mouse pointer (i.e. #631494 is also solved).

Backporting the graphics driver from Maverick would probably solve the issue also on Lucid.

[Gejza Büchler (buchlerg)]

Reported problem affecting FSC Lifebook E8010 has been also solved with release of 10.10 Maverick.

I'm going to try to close this report.

[Gejza Büchler (buchlerg)]

Can't find how to close the bug report... Any suggestion? Or can anyone do that instead of me? Thanks

[penalvch (penalvch)]

Gejza Büchler, yhis bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.