Bug 232661

Summary:	Post-install: system doesn't start X due to missing module load
Product:	Gentoo Release Media	Reporter:	Andrés Becerra Sandoval <andres.becerra>
Component:	Installer	Assignee:	Gentoo Linux Installer <gli-bugs>
Status:	RESOLVED INVALID
Severity:	normal	CC:	releng
Priority:	High
Version:	2008.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Andrés Becerra Sandoval 2008-07-22 15:29:44 UTC

1. Fresh install of livecd-i686-installer-2008.0-r1.iso
2. Select gdm as xdm startup service
3. Boot the system

gdm doesn't startup


I solved the problem doing

# modprobe intel-agp 
# /etc/init.d/xdm restart

because my box has an intel video card. I think this should be automatic.

Thanks,

Comment 1 Andrew Gaffney (RETIRED) gentoo-dev

2008-07-22 15:35:28 UTC

And how exactly is the installer supposed to know what you need that module loaded?

Comment 2 Andrés Becerra Sandoval 2008-07-24 20:18:52 UTC

(In reply to comment #1)
> And how exactly is the installer supposed to know what you need that module
> loaded?
> 

I really don't know about the Gentoo installer internals, but maybe with lspci one can detect the agp modules loaded for the video card, with this information /etc/modules.d/ could be populated with a file containing the name of the appropiated module.

For me is no big deal, I already have 3 gentoo boxes, but for people approaching the first time to gentoo it could be a little disappointing not starting up X.

Thanks,

Comment 3 Andrés Becerra Sandoval 2008-07-24 20:21:29 UTC

I should have said lspci and lsmod output !

Comment 4 Chris Gianelloni (RETIRED) gentoo-dev

2008-07-28 20:52:45 UTC

The Installer never has (and likely never will) do hardware detection.  Instead, we use a very generalized kernel, and expect the kernel's module loading to pull in the correct modules.  You're still expected to configure your system and its hardware yourself.

Comment 5 Andrés Becerra Sandoval 2008-07-28 21:40:27 UTC

(In reply to comment #4)
> The Installer never has (and likely never will) do hardware detection. 
> Instead, we use a very generalized kernel, and expect the kernel's module
> loading to pull in the correct modules.  You're still expected to configure
> your system and its hardware yourself.
> 

I am sorry, I should have known that!. 

Now the bug must be closed, thanks.