different problems during the feisty installation process

[jan-teichmann]

ubuntu-7.04-desctop-i386

i tried to install the new feisty on my notebook dell latitude c610
during the sturtup i got the following errormessages:

[130.512000]SQUASHFS error: sb_bread failed reading block 0x568d9
 -||- : unable to read fragment cache block [15a33796]
 -||- : unable to read page, block 15a33796, size 2e48
 -||- : zlib_inflate returned unexpected result 0xfffffff

* enabling additional executable binary formats binfmt-support
auto/POSIX/autosplit.ix did not return a true value at /usr/share/perl/5.8/AutoLoader.pm line 160. at /ust/lib/perl/5.8/POSIX.pm line 7
Cant load /.../POSIX.so for module POSIX: /.../POSIX.so : invalide ELF header at /usr/lib/perl/5.8/XSLoader.pm line 70. at /usr/lib/perl/5.8/auto/POSIX.pm line 26
compilation failed in require at /usr/sbin/update-binfmts line 22. BEGIN failed--compilation aborted at /usr/sbin/update-binfmts line 22

also i got the following report of the x window system 7.2.0:

(EE) unable to locate/open config file
new driver is "ati"
(==) using default built-in configuration (55 lines)
dlopen: /usr/lib/xorg/modules/extensions//libextmod.so: invalid ELF header
(EE) failed to load /usr/lib/xorg/modules/extensions//libextmod.so
(EE) failed to load module "extmod" (loader failed, 7)

Backtrace:

the x window system problem exist also in the safe graphic mode installation

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Did you verify the md5sum of the ISO you burned? You can learn about md5sums at https://help.ubuntu.com/community/HowToMD5SUM. Thanks in advance.

[jan-teichmann (teichmann-jan)]

yes, the md5sum was valid and on on my secound pc with pentium4 and ati sapphire the installation works pefectly. for the dell latitude c610 i used the alternate cd to dodge the problems with the desctop cd and it works fine.

[Brian Murray (brian-murray)]

The output of 'sudo lspci -vvn' and 'dmesg' on the laptop may be helpful in determining the root cause of this issue. Thanks!

[jan-teichmann (teichmann-jan)]

lspci -vvn and dmesg output in addition

[Launchpad Janitor (janitor)]

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!

[Leann Ogasawara (leannogasawara)]

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.

[Launchpad Janitor (janitor)]

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.