On Thursday 15 October 2009 06:37:43 pm Mikael Eriksson wrote:

On Thu, Oct 15, 2009 at 06:30:29PM -0500, David C. Rankin wrote:

...

Guys,

After picking around in the logs, one recurring error seems to be:

FATAL: Module fbcon not found.

This comes from modprobe.

...

What provides the "fbcon" module? I presume it some framebuffer connect module. I have loaded xf86-video-fbdev package, but still no luck.

fbcon is a kernel module, but it should be compiled into the kernel. Do you have the latest kernel26?

...

Still stumped with intel :-(

Yep kernel26-2.6.31.4-1-i686.pkg.tar.gz -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

On Friday 16 October 2009 03:45:44 am pascal wrote:

Le Thu, 15 Oct 2009 19:46:36 -0500

"David C. Rankin" a écrit:

...

On Thursday 15 October 2009 06:37:43 pm Mikael Eriksson wrote:

...

On Thu, Oct 15, 2009 at 06:30:29PM -0500, David C. Rankin wrote:

...

Guys,

After picking around in the logs, one recurring error seems to be:

FATAL: Module fbcon not found.

This comes from modprobe.

...

What provides the "fbcon" module? I presume it some framebuffer connect module. I have loaded xf86-video-fbdev package, but still no luck.

fbcon is a kernel module, but it should be compiled into the kernel. Do you have the latest kernel26?

...

Still stumped with intel :-(

Yep

kernel26-2.6.31.4-1-i686.pkg.tar.gz

this error about fbcon module not found can be ignored, fbcon seems to be builtin in the kernel and not as a module, hence "module not found". See http://bbs.archlinux.org/viewtopic.php?id=79362

pascal, if that is so, why is it listed as the FATAL error? Maybe just as you say, it doesn't find it, issues the FATAL error message, keeps going and dies somewhere else, but it is the last error I see. The strace shows this sequence: (==) Using default built-in configuration (30 lines) (EE) Failed to load module "fbdev" (module does not exist, 0) WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/framebuffer_blacklist.pacsave, it will be ignored in a future release. FATAL: Module fbcon not found. Setting master record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 waiting for X server to shut down Dropping master [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 2370 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD (Child exited) @ 0 (0) --- waitpid(-1, 0xbf9938fc, WNOHANG) = -1 ECHILD (No child processes) sigreturn() = ? (mask now []) <snip> Then X just dies. Full strace at: http://www.3111skyline.com/download/Archlinux/bugs/supersff/strace-startx.tx... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

Hi In data sabato 17 ottobre 2009 12:32:49, Dario ha scritto:

Well, I usually had a FATAL kind of error in DMESG, due to a missing module that I insisted on having loaded in rc.conf, but the "fatality" was related to the attempt to load it, and didn't not harm the rest of the boot sequence. I agree that indeed it's the wrong name.

But you are right: in the strace, looking at the syntax, the error is not coming from X, but from the kernel, and X reads the fatality as a bad thing, I suppose, so this could be a X server bug. Maybe you can recompile the kernel with fbcon as a module and see what happens... ciao! Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com

David C. Rankin schreef:

On Saturday 17 October 2009 05:53:12 am Dario wrote:

...

Hi

In data sabato 17 ottobre 2009 12:32:49, Dario ha scritto:

...

Well, I usually had a FATAL kind of error in DMESG, due to a missing module that I insisted on having loaded in rc.conf, but the "fatality" was related to the attempt to load it, and didn't not harm the rest of the boot sequence. I agree that indeed it's the wrong name.

But you are right: in the strace, looking at the syntax, the error is not coming from X, but from the kernel, and X reads the fatality as a bad thing, I suppose, so this could be a X server bug. Maybe you can recompile the kernel with fbcon as a module and see what happens...

Well, I'm not an Arch kernel guru, but I guess you mean adding fbcon to the MODULES="" line in /etc/mkinitcpio.conf so it would read:

MODULES="fbcon intel_agp i915"

and then rebuilding with

mkinitcpio -p kernel26

I'll give it a shot and report back....

David, i'm really impressed with your persistence in this. Way to go! On the other hand, if the fbcon module is built-in now, than adding it MODULES probably won't change anything as it isn't compiled as module. I think it is about this line in the kernel .config: CONFIG_FRAMEBUFFER_CONSOLE=y But i'm not sure. Anyone? mvg, Guus

On Saturday 17 October 2009 09:20:40 am David C. Rankin wrote:

Well, I'm not an Arch kernel guru, but I guess you mean adding fbcon to the MODULES="" line in /etc/mkinitcpio.conf so it would read:

MODULES="fbcon intel_agp i915"

and then rebuilding with

mkinitcpio -p kernel26

I'll give it a shot and report back....

Nope: ==> Building image "default" ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c /etc/mkinitcpio.conf - g /boot/kernel26.img :: Begin build ERROR: module 'fbcon' not found <snip> ==> Building image "fallback" ==> Running command: /sbin/mkinitcpio -k 2.6.31-ARCH -c /etc/mkinitcpio.conf - g /boot/kernel26-fallback.img -S autodetect :: Begin build ERROR: module 'fbcon' not found <snip> Back to the drawing board.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

Ciao In data domenica 18 ottobre 2009 00:54:16, David C. Rankin ha scritto:

...

Well, I'm not an Arch kernel guru, but I guess you mean adding fbcon to the MODULES="" line in /etc/mkinitcpio.conf so it would read:

[SNIP]

ERROR: module 'fbcon' not found

You have to reconfigure the kernel, then recompile it, and finally run mkinitcpio. Configuring the kernel is not such an hard task (I used to do it at every update on my previous Slackware box), besides, I think that you can keep everything as it is now in the standard arch configuration except, as someone else said, activating, somewhere in the kernel configuration, fbcon as a module. Then you can run the X server and telling us about the next fatal error:) ciao! Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com

On Saturday 17 October 2009 05:32:49 am Dario wrote:

In data sabato 17 ottobre 2009 06:27:55, David C. Rankin ha scritto:

...

pascal, if that is so, why is it listed as the FATAL error?

Well, I usually had a FATAL kind of error in DMESG, due to a missing module that I insisted on having loaded in rc.conf, but the "fatality" was related to the attempt to load it, and didn't not harm the rest of the boot sequence. I agree that indeed it's the wrong name.

Do I need to remove something from my rc.conf?

Other thing: have you tried with another recent distro?

Not yet, which live CD do you think would be a good test case. Not openSuSE 11.2 Milestone8 is buggy enough as it is. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com