[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#563607: marked as done (linux-source-2.6.30: Will not boot past the beginning of the GUI in Xwindow -- Window manager dies)

Your message dated Tue, 23 Feb 2010 22:31:23 +0100
with message-id <20100223213123.GA23650@galadriel.inutil.org>
and subject line Re: Bug#563607: linux-source-2.6.30: Will not boot past the beginning of the GUI in Xwindow -- Window manager dies
has caused the Debian Bug report #563607,
regarding linux-source-2.6.30: Will not boot past the beginning of the GUI in Xwindow -- Window manager dies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
563607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563607
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-source-2.6.30
Version: 2.6.30-8squeeze1
Severity: important

I already wrote all of this up once!!

This bug pertains to the fact that my AMD64 machine will not boot up past perhaps 1/3 of the way into the GUI window manager in Xwindow. What happens is that the screen shuts off completely at about this point, whenever I try to boot from my own recompilation of the 2.6.30-8 kernel.

I do hope that you can identify some essential piece of software that should be marked as such in the installation files, but isn't. If you can, I will be very much in your debt.

A few words about my compilation environment:

I have tried to convert all internal drivers to internal status -- not modules. Consequently, I have initrd disabled. I have been through the initrd setup with a fine-toothed comb to ensure that the kernel indeed contains all required drivers built-in. Insofar as I can locate them at all, it does.

Thank you VERY much!!

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-source-2.6.30 depends on:
ii  binutils                      2.20-4     The GNU assembler, linker and bina
ii  bzip2                         1.0.5-3    high-quality block-sorting file co

Versions of packages linux-source-2.6.30 recommends:
ii  gcc                           4:4.3.4-1  The GNU C compiler
ii  libc6-dev [libc-dev]          2.10.2-2   GNU C Library: Development Librari
ii  make                          3.81-7     An utility for Directing compilati

Versions of packages linux-source-2.6.30 suggests:
ii  kernel-package            12.031         A utility for building Linux kerne
ii  libncurses5-dev [ncurses- 5.7+20090803-2 developer's libraries and docs for
pn  libqt3-mt-dev             <none>         (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.6.32-1

Willy Gommel wrote:

> Actually, the official 2.6.32 image is guilty of an even worse
> problem: on being booted, the kernel panics almost at once,
> complaining about the inability to find the boot drive specified in
> LILO.CONF. This is behavior I have noted in all versions of vmlinuz
> starting with 2.6.26, and corrected only with grave difficulty if at
> all.

Is there a specific reason you're using lilo? It's obsolete legacy
code. I recommend a migration to grub: http://wiki.debian.org/FromLiloToGrub

> On the other hand, my hand-created version, minus all of the initrd
> drivers and such, is now working perfectly under 2.6.32. I can only
> gather that some recent upgrade made enough of a difference to allow
> it to happen that way, because I did not reconfigure it since it
> initially failed.

Ok, marking 2.6.32 as fixed, then.

Cheers,
        Moritz

--- End Message ---
Reply to: