Prev: IPtables - forwarding question
Next: 13.1 and VMware Workstation
From: Arun Vidarjee on 15 Jun 2010 03:29
Hi alll

On 15.06.2010 01:37, Martin wrote:
> Arun Vidarjee wrote:
>
>> ... The 13.1 64 DVD booted
>> properly and I could install Slack on the HD. But had
>> the black screen booting from HD. I could avoid that
>> appending "nomodeset" to kernel boot parameters. The
>> kernel version is 2.6.33.4 #3 SMP ... x86_64 Intel(R)
>> Core(TM) i5 CPU M 540
>>
>> Now the big surprise: I can't start X, Xorg.0.log says
>>
> [...]
>> (EE) Failed to load module "fbdev" (module does not exist)
>
> That error is harmless
>
>> ..
>> (EE) intel(0): No kernel modesetting driver detected
>> (II) UnloadModule: "intel"
>> (EE) Screen(s) fount, but none have a usable configuration.
>
> That is your problem.
>
> As far as I can see, kernel mode setting should be enabled. Ie. you need to
> work on the other problem.

Sounds reasonable. I should not disable KMS. But for that I need a
kernel which does not switch off my screen! I'm still with the
stock kernel in 13.1 2.6.33.4. My question: Does anybody know of
a better recent kernel, or a patch for this one?


> One idea: the black screen during boot is often
> caused by a conflict between intel and other framebuffer devices like VESA.
> Make sure they are disabled.

I'm not sure how to do that. Can remember seeing some similar
discussions in a web-search. I will check, appreciate any pointers
in the meantime.

Arun
From: Aaron W. Hsu on 15 Jun 2010 11:53
Arun Vidarjee wrote:

>> One idea: the black screen during boot is often
>> caused by a conflict between intel and other framebuffer devices like
>> VESA. Make sure they are disabled.
>
> I'm not sure how to do that. Can remember seeing some similar
> discussions in a web-search. I will check, appreciate any pointers
> in the meantime.

So, what he and I are trying to say is go into your Lilo.conf file and
remove the use of the framebuffer device that gives you the high
resolution console ttys.

The lilo.conf file is suitably commented for this task, so just go in
there and see what you get, make sure to use the normal setting that
doens't use a VESA framebuffer. I'm not going to tell you exactly how to
do it because lilo.conf files are dangerous beasts, and if you haven't
read through yours carefully, and you're not confident how to edit it,
you should probably post it up for us to tell you what to change (if we
have time) rather than me guessing at this point. However, this is a
fairly routine and simple edit which should require you to change only a
couple of lines, so just go in there, change those, and try to boot up
without the VESA framebuffer; see what you get. You shouldn't get the
black screen anymore if you were having a conflict with that stuff.

Aaron W. Hsu
From: Lew Pitcher on 15 Jun 2010 12:25
On June 15, 2010 11:53, in alt.os.linux.slackware, arcfide(a)sacrideo.us
wrote:

> Arun Vidarjee wrote:
>
>>> One idea: the black screen during boot is often
>>> caused by a conflict between intel and other framebuffer devices like
>>> VESA. Make sure they are disabled.
>>
>> I'm not sure how to do that. Can remember seeing some similar
>> discussions in a web-search. I will check, appreciate any pointers
>> in the meantime.
>
> So, what he and I are trying to say is go into your Lilo.conf file and
> remove the use of the framebuffer device that gives you the high
> resolution console ttys.
>
> The lilo.conf file is suitably commented for this task, so just go in
> there and see what you get, make sure to use the normal setting that
> doens't use a VESA framebuffer.

Specifically, the OP should read the lilo.conf(5) ('man 5 lilo.conf')
section on the "per-image" vga= option.

vga=normal is a safe bet for a non-fb device, as is vga=extended

> I'm not going to tell you exactly how to
> do it because lilo.conf files are dangerous beasts, and if you haven't
> read through yours carefully, and you're not confident how to edit it,
> you should probably post it up for us to tell you what to change (if we
> have time) rather than me guessing at this point.

Agreed.

> However, this is a
> fairly routine and simple edit which should require you to change only a
> couple of lines, so just go in there, change those, and try to boot up
> without the VESA framebuffer; see what you get. You shouldn't get the
> black screen anymore if you were having a conflict with that stuff.


--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------


 | 
Pages: 1
Prev: IPtables - forwarding question
Next: 13.1 and VMware Workstation