ugh i can ssh in and the machine is up
> and running, just no output to the monitor. Still just the grub
> statements up on the screen.
>
> running hwinfo --framebuffer results in no output.
>
> efifb appears to get loaded and has grubs resolution
> [1.451694] efifb: pro
grub
statements up on the screen.
running hwinfo --framebuffer results in no output.
efifb appears to get loaded and has grubs resolution
[1.451694] efifb: probing for efifb
[1.451712] efifb: framebuffer at 0xe000, using 8640k, total 8640k
[1.451712] efifb: mode is 1920x10
On 4/12/20 2:47 AM, Paul Scott wrote:
Hi,
I haven't posted for a long time!
I just successfully did my first UEFI installation.
It's a new AMD machine with. X is failing to start. I have solved a
number of related problems within online information including finding
the firmware-amd-graphi
On 4/12/20 11:23 AM, Paul Scott wrote:
On 4/12/20 3:10 AM, Paul Scott wrote:
On 4/11/2020 5:47 PM, Paul Scott wrote:
Hi,
I haven't posted for a long time!
I just successfully did my first UEFI installation.
It's a new AMD machine with. X is failing to start. I have solved
a number of rela
On 4/12/20 3:10 AM, Paul Scott wrote:
On 4/11/2020 5:47 PM, Paul Scott wrote:
Hi,
I haven't posted for a long time!
I just successfully did my first UEFI installation.
It's a new AMD machine with. X is failing to start. I have solved a
number of related problems within online information i
On 4/11/2020 5:47 PM, Paul Scott wrote:
Hi,
I haven't posted for a long time!
I just successfully did my first UEFI installation.
It's a new AMD machine with. X is failing to start. I have solved a
number of related problems within online information including finding
the firmware-amd-grap
Hi,
I haven't posted for a long time!
I just successfully did my first UEFI installation.
It's a new AMD machine with. X is failing to start. I have solved a
number of related problems within online information including finding
the firmware-amd-graphics package. I can't easily post log co
On 03/09/18 10:33, Lucio wrote:
On 03/09/18 09:46, Felix Miata wrote:
Does /dev/fb0 exist?
I can't check the notebook just now, but in the desktop system yes, it
exists and the firmware-amd-graphics package was already installed.
The notebook was missing the firmware-amd-graphics package,
On 03/09/18 09:46, Felix Miata wrote:
Does /dev/fb0 exist?
I can't check the notebook just now, but in the desktop system yes, it
exists and the firmware-amd-graphics package was already installed.
ok I've just bought, with AMD RX 540
> graphics. I've installed Debian using the latest Debian Buster testing
> ISO (August 27th, as today's one wasn't available yet), and Xorg doesn't
> start.
> Both Xorg.0.log show the same error:
> Fatal server error:
>
led Debian using the latest Debian Buster testing
ISO (August 27th, as today's one wasn't available yet), and Xorg doesn't
start.
Both Xorg.0.log show the same error:
Fatal server error:
Cannot run in framebuffer mode please supply the busIds for all
framebuffer devices
Both s
On 06/20/2016 04:44 AM, Daniel A wrote:
> Up until kernel 4.5.0-1 my console had the following geometry:
...
> mode "1920x1200"
> geometry 1920 1200 1920 1200 32
...
> Since kernel 4.5.0-2 it changed to this:
>
...
> mode "1024x768"
> geometry 1024 768 1920 1200 32
I also compared the Xor
Daniel A composed on 2016-06-20 04:44 (UTC+0200):
...
]$ fbset -i
mode "1920x1200"
...
Since kernel 4.5.0-2 it changed to this:
...
]$ fbset -i
mode "1024x768"
...
-Console: switching to colour frame buffer device 240x75
+Console: switching to colour frame buffer device 128x48
Is there a
Hi
Up until kernel 4.5.0-1 my console had the following geometry:
]$ fbset -i
mode "1920x1200"
geometry 1920 1200 1920 1200 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode
Frame buffer device information:
Name: radeondrmfb
Address : 0xd047500
Hello,
I have laptop with intel graphics chipset, and I would like to prevent it
from using framebuffer, while allow X intel driver.
I'm using wheezy+backports, kernel 3.16.5 (linux-image-3.16-0.bpo.3-686-pae)
When I disabled mode switching by kernel option i915.modeset=0 or nomo
udlfb
as driver to provide a framebuffer node at /dev/fb1. The X system
worked with using fbdev as xorg driver if write the configuration
manually, but xrandr could not find that monitor without a static
screen configuration. And simply include a static config for only the
displaylink monitor will
;J. B" wrote:
> Dear list,
>
> With the ongoing process of my full disk encryption ( exclude /boot), I have
> now
> come with another issue. The framebuffer device which resides under /root/dev
> is
> not available prior to opening luks and it is quite normal. IS the
Dear list,
With the ongoing process of my full disk encryption ( exclude /boot), I have now
come with another issue. The framebuffer device which resides under /root/dev is
not available prior to opening luks and it is quite normal. IS there any
alternative
so that required drivers (like
On Sun, Oct 23, 2011 at 4:27 AM, daniel jimenez
wrote:
>
> Thanks! It worked wonders, my ttys work at native resolution now :D
>
> My /etc/default grub has these lines now:
>
> GRUB_GFXMODE=1280x800
> GRUB_GFXPAYLOAD=keep
> GRUB_GFXPAYLOAD_LINUX=1280x800x32
"GRUB_GFXPAYLOAD" no longer exists. It
rub has these lines now:
GRUB_GFXMODE=1280x800
GRUB_GFXPAYLOAD=keep
GRUB_GFXPAYLOAD_LINUX=1280x800x32
Hope this helps others too. I'm adding some keywords to this reply.
solution grub nvidia fullscreen resolution tty framebuffer
What a great community this is. Many thanks again.
--
Daniel Ji
On Sat, 22 Oct 2011 12:14:00 -0700, daniel jimenez wrote:
>> Ah... you're using the nvidia closed driver.
>
> I'm sorry, forgot about the nvidia thing.
With nvidia closed driver this can be tricky because it does not use KMS.
>> > upon checking /etc/default/grub
>> >
>> > i was able to find
>>
> Ah... you're using the nvidia closed driver.
I'm sorry, forgot about the nvidia thing.
> > upon checking /etc/default/grub
> >
> > i was able to find
> > GRUB_GFXMODE=1280x800
> > GRUB_GFXPAYLOAD=keep
> >
> > thanks for the help
>
> If that did it, fine then :-)
Not really.. I found the GRUB_
ot;GRUB_CMDLINE_LINUX" and/or "GRUB_GFXPAYLOAD_LINUX" parameters, tweak
>> them as required (remember to run "update-grub" after any change).
> the requested output is:
> $ grep -i buffer /var/log/Xorg.0.log
> [24.428] (II) Loading extension DOUBLE-BUFFER
&
the requested output is:
$ grep -i buffer /var/log/Xorg.0.log
[24.428] (II) Loading extension DOUBLE-BUFFER
[26.904] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[29.538] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
upon checking /etc/default/grub
i was able to find
looks again really low res.
Most likely you want to add this to /etc/default/grub
GRUB_GFXPAYLOAD_LINUX=1280x800x32
It will enable framebuffer, which seems to be disabled currently.
--
Max Tsepkov (a.k.a. Gary Golden)
A freelancing web engineer
http://www.garygolden.me
--
To UNSUBSCRIBE, ema
On Thu, 20 Oct 2011 03:42:59 -0700, daniel jimenez wrote:
> I've got a problem with my framebuffer (tty) resolution. Currently
> running debian testing (through linux mint debian edition).
>
> Grub2 works with my native resolution, which is 1280x800. The rest of
> the b
Hello everyone,
I've got a problem with my framebuffer (tty) resolution. Currently running
debian testing (through linux mint debian edition).
Grub2 works with my native resolution, which is 1280x800. The rest of the
boot sequence runs at 800x600 or so. After starting X, my desktop runs
har
On Fri, 13 May 2011 16:00:45 +0800, Magicloud Magiclouds
wrote:
> Then I installed xorg from testing branch. With '# startx', I had
> the xterm window. But when I exited, the console turned into
> framebuffer mode. /proc/fb shows interdrmfb.
> What happened? Did the sta
But when I exited, the console turned into framebuffer
> mode. /proc/fb shows interdrmfb.
> What happened? Did the stage with xterm also run in framebuffer mode?
Xorg log could provide additional info on what's going on (look at "/var/
log/Xorg.0.log").
Greetings,
--
Camal
Hi,
I'd like to try out gnome3. So I had a laptop for a installation of
debian testing.
Then I installed xorg from testing branch. With '# startx', I had
the xterm window. But when I exited, the console turned into
framebuffer mode. /proc/fb shows interdrmfb.
What happened
X won't start: xf86MapVidMem: Could not mmap framebuffer (0x000a,0x2)
(Invalid argument)
Note: X always worked with grsecurity kernel provided that I disabledmmprotect
(and other protections) on /etc/X11/X . I have done that. Iam using a config
based on a config that worked i
On Thu, Jul 16, 2009 at 11:06, Amit Uttamchandani wrote:
>
> I'm trying to get framebuffer loaded for the Radeon X1300/X1550 card
> that I have but have had no luck.
>
> Tried loading the following framebuffer drivers:
>
> * radeonfb
> * atyfb
> * aty128fb
>
I'm trying to get framebuffer loaded for the Radeon X1300/X1550 card
that I have but have had no luck.
Tried loading the following framebuffer drivers:
* radeonfb
* atyfb
* aty128fb
The only framebuffer driver that works is vga16fb.
Other info:
* Debian Squeeze on an x86 machine.
*
Why does the X Window System reset kbdrate? I've set keyboard delay
and repeat for the framebuffer console with "kbdrate -r 30 -d 250 -s",
but starting up X will reset these values to slower settings.
Switching from X to another VT and issuing "kbdrate -r 30 -d 250 -s&quo
I'm trying to boot my machine into mode vga=873 (1680x1050 24bit native for my
screen) in vesa frame buffer mode. This mode is given by hwinfo --framebuffer
(0x369, translated to the vga mode). This works when conenected with dvi but in
analog mode I get the message that this is an undefined
On Thu, Jul 03, 2008 at 07:10:13PM +0800, Can-Hua Chen wrote:
> I am using Inter810 driver.
> I tried:
> modprobe i810 vram=16 xres=1024 yres=768 bpp=32 accel=1 mtrr=1.
> After that I know the module did be loaded via "lsmod" command,
> while /dev/fb0 was still missing.
> I even "mknod /dev/fb0 c 2
I am using Inter810 driver.
I tried:
modprobe i810 vram=16 xres=1024 yres=768 bpp=32 accel=1 mtrr=1.
After that I know the module did be loaded via "lsmod" command,
while /dev/fb0 was still missing.
I even "mknod /dev/fb0 c 29 0" according to a googled webpage,
but "mplayer -vo fbdev Some.avi" stil
On Fri, May 09, 2008 at 09:38:41PM +1200, Chris Bannister wrote:
> On Fri, May 09, 2008 at 08:11:40AM +1000, Alex Samad wrote:
> > Hi
> >
> > recently got a new laptop, with a nvidia gpu. I have installed the
> > nvidia driver for X. But I also like using the vt's as well.
> >
> > How do I driv
On Fri, May 09, 2008 at 08:11:40AM +1000, Alex Samad wrote:
> Hi
>
> recently got a new laptop, with a nvidia gpu. I have installed the
> nvidia driver for X. But I also like using the vt's as well.
>
> How do I drive them in a high mode the 80x40 and can I use frame buffers
> at the same time
On Thu May 8 2008 03:11:40 pm Alex Samad wrote:
> Hi
>
> recently got a new laptop, with a nvidia gpu. I have installed the
> nvidia driver for X. But I also like using the vt's as well.
>
> How do I drive them in a high mode the 80x40 and can I use frame buffers
> at the same time as using the nv
Hi!
AFAIK the nvidia fb and X driver don't work well together. You'd better
use the vesa fb driver.
Ciao,
Olaf
On Fri, 9 May 2008 08:11:40 +1000
Alex Samad <[EMAIL PROTECTED]> wrote:
> Hi
>
> recently got a new laptop, with a nvidia gpu. I have installed the
> nvidia driver for X. But I also
Hi
recently got a new laptop, with a nvidia gpu. I have installed the
nvidia driver for X. But I also like using the vt's as well.
How do I drive them in a high mode the 80x40 and can I use frame buffers
at the same time as using the nvidia driver for X
alex
--
"We've tripled the amount of m
On 29 Ott, 11:00, Dieter Faulbaum <[EMAIL PROTECTED]> wrote:
> intelfb: Video mode must be programmed at boot time.
> intelfb: cleanup
I also tried to enable intelfb on my laptop but didin't find a way out,
perhaps because I didn't include all necessary dependant module in my
initrd.
I noticed
I have a Notebook with an Intel VGA-Controller and the
framebuffer will not work. Any idea what could be wrong?
What does the line mean 'Video mode must be programmed at boot time'?
How can I do this? There is no parameter, which I can give in the
'make menuconfig' process
I'm trying with a stable Etch and all seems ok...
On May 8, 4:10 pm, Mat <[EMAIL PROTECTED]> wrote:
> Hi all.
> I have problems with a G450 eTV on kernel 2.6.15-26.
> Any idea?
> ...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
Hi all.
I have problems with a G450 eTV on kernel 2.6.15-26.
Any idea?
===
# lspci | grep Matrox
:01:00.0 VGA compatible controller: Matrox Graphics, Inc. G400/
G450 (rev 85)
# modprobe matroxfb_g450
Nothing new in dmesg...
# modprobe matroxfb_base
Nothing new in dmesg...
# lsmod | grep
On Fri, Jun 02, 2006 at 04:01:46PM EDT, 46kmz5j02 wrote:
> I use framebuffer console mode by appending "vga=787" to kernel line
> in /boot/grub/menu.lst. I would like to know if possible to change color
> of console text and background color also.
>
> I have google
Sure,use settermfor examplesetterm -background greenOn 6/2/06, 46kmz5j02 <[EMAIL PROTECTED]
> wrote:I use framebuffer console mode by appending "vga=787" to kernel line
in /boot/grub/menu.lst. I would like to know if possible to change colorof console text and background color als
I use framebuffer console mode by appending "vga=787" to kernel line
in /boot/grub/menu.lst. I would like to know if possible to change color
of console text and background color also.
I have googled and not found this info.
Thank you very much.
--
To UNSUBSCRIBE, email to [EMAIL
On Fri, Aug 19, 2005 at 11:27:37PM -0600, Bob Proulx wrote:
> L.V.Gandhi wrote:
> > Bob Proulx wrote:
> They are complementary. The discover process runs at boot time to
> load up statically attached hardware. This would typically be things
> like PCI network cards, PCI sound cards, and things li
Malcolm Carlock wrote:
> I guess my only wonderment is why these utilities aren't installed by
> default.
Good question. But the problem is how to do that?
Certainly the new kernel you are installing does not *require* the
'discover' package to be installed. So the kernel package can't list
it
Bob Proulx wrote:
Install 'discover' and 'hotplug' and that should take care of most of
your problems. Those are hardware discovery programs. They will map
the hardware found to the current device drivers. Very nice.
If you have the 2.6 kernel installed then install 'udev' too since it
makes
On 8/20/05, Bob Proulx <[EMAIL PROTECTED]> wrote:
> L.V.Gandhi wrote:
> > Bob Proulx wrote:
> > > Install 'discover' and 'hotplug' and that should take care of most of
> > > your problems. Those are hardware discovery programs. They will map
> > > the hardware found to the current device drivers.
L.V.Gandhi wrote:
> Bob Proulx wrote:
> > Install 'discover' and 'hotplug' and that should take care of most of
> > your problems. Those are hardware discovery programs. They will map
> > the hardware found to the current device drivers. Very nice.
>
> Whether both discover and hot plug are comp
On 8/19/05, Bob Proulx <[EMAIL PROTECTED]> wrote:
> Install 'discover' and 'hotplug' and that should take care of most of
> your problems. Those are hardware discovery programs. They will map
> the hardware found to the current device drivers. Very nice.
Whether both discover and hot plug are c
M Carlock wrote:
> I recently upgraded from woody to sarge per the
> instructions (aptitude etc), which was successful.
>
> However, after then upgrading the kernel from
> 2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
> but I'd lost eth0 and the ATI framebuffer.
Mark Fletcher wrote:
M Carlock wrote:
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspc
M Carlock wrote:
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspci can see both devices
d lost eth0 and the ATI framebuffer.
>
> lspci can see both devices, but I'm at a loss as to
> how to make the kernel see them again.
>
> modprobe eth1349 seems to work OK. modprobe eth16i
> fails, no hardware found. The card is a 3c905.
>
> This must be a common question,
I recently upgraded from woody to sarge per the
instructions (aptitude etc), which was successful.
However, after then upgrading the kernel from
2.2.20-idepci to 2.6.8-2-386, I found I could boot OK,
but I'd lost eth0 and the ATI framebuffer.
lspci can see both devices, but I'm at a
s with a Hercules Prophet Kyro
> > >>>PCI video card on an aging 233 MHz Pentium. the one that isn't
> > >>>VESA, or even VGA, but EGA (remember those?). I found a report
> > >>>dated 2002 that someone got such a setup to work with
> > >
Dear all,
I have integrated VGA based on KM400 chipset from VIA.
when I boot from *lnx-bbc* and *Knoppix* I can see the boot-logo. now I have
configured 2.6.10 kernel from debian and enable framebuffer-support,
vesa-support,linux-logo support all as *built-in features*
but the newly
On Wed, May 25, 2005 at 08:46:27PM +0530, Joydeep Bakshi wrote:
> *dmesg|grep vesa* shows ---> vesafb: probe of vesafb0 failed with error -6
>^
I'm not really knowledgable in this area, but I saw this message on my
box a
Dear all,
I have integrated VGA based on KM400 chipset from VIA.
when I boot from *lnx-bbc* and *Knoppix* I can see the boot-logo. now I have
configured 2.6.10 kernel from debian and enable framebuffer-support,
vesa-support,linux-logo support all as *built-in features*
but the newly
Hello,
Anyone has installed the qingy login manager under debian-ubuntu?
I have only black screens instead of qingy on my ttys.
thank you?
Bayrouni.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hellow!
How do I turn on framebuffer via rivafb module?
It's always vesafb module loades instead.
I need rivafb to have bigger refresh rate in console.
Thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Works fine with custom 2.4.18 kernel with "graphical console" enabled.
Maybe Debian is correct not to include this in the stable default
kernels since the feature is experimental. otoh.. default vga modes on a
15" laptop makes working in the console almost impossible. Maybe this
feature is now matu
Tried with 2.4.18 - seems to be the most recent kernel w/ woody (?) -
same difference.. Then I took a look at the .config file in /boot and
sure enough the VESA VGA option is unchecked. So the woody kernels
apparently ship with the graphical console disabled. I googled a bit
more and found a c
Andrea Vettorello wrote:
Ah ok, so no configuration script that i'm aware of.
I mean, you can configure your boot loader (Grub or Lilo) to pass the
needed option to the kernel to enable the framebuffer with resolution,
depth, draw strategies and so on, or if 60 Hz refresh rate is enough
fo
functional part of the kernel (compiled-in or module). fbset is
> a utility that lets you switch/display console settings after boot.
>
I once had a "/usr/bin/fbset -a 1280x1024-60" in /etc/profile only
because I wanted to have the framebuffer driver built as a module.
O.
t; to be a functional part of the kernel (compiled-in or module). fbset is
> a utility that lets you switch/display console settings after boot.
>
Ah ok, so no configuration script that i'm aware of.
I mean, you can configure your boot loader (Grub or Lilo) to pass the
needed option
Andrea Vettorello wrote:
Thanks much for your reply.
In /boot you should find the config used to compile the kernel, i'm
not quite sure if is the same for Woody, anyway you can look in
/usr/share/doc/kernel-image-2.4-X where you should find all the info
you need.
About the only place I didn't thin
s not
> enabled by default. This is a major problem in my case since I do not
> plan to install 'X' as this point. So I need to get this to work before
> I can further configure the system (I don't feel too comfortable with
> chroot..). I tried to check whether the frame
install 'X' as this point. So I need to get this to work before
I can further configure the system (I don't feel too comfortable with
chroot..). I tried to check whether the framebuffer console was enabled
in the kernel (builtin or module) but I cannot find where the kernel's
sour
Hi Debian!
I asked the author of vsefb-tng what that means.
He is very good in replying to email you send him:
On Sat, Nov 20, 2004 at 09:16:52AM -0600, Hugo Vanwoerkom wrote:
Hi,
>> Thanks a lot for the latest vesafb-tng. I use the 2.6.9 version.
>> I have a question on what you say in your vesafb
I never
need, so I drop them.
Regards,
Because your config file shows you load 2 fonts:
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
so the reason for my question was, what font gets loaded, since the only
framebuffer boot parm you have seems to be vga=791.
I do just that, but with the CONFIG_FONT_
On Sat, Nov 20, 2004 at 09:59:48AM -0600, Hugo Vanwoerkom wrote:
> Sridhar M.A. wrote:
> >On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
> > > I have been trying to get frambuffer bootup work in 2.6.9 without
> > > success so far. Cannot get the logo at all.
> >
> >I
Sridhar M.A. wrote:
On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
> I have been trying to get frambuffer bootup work in 2.6.9 without
> success so far. Cannot get the logo at all.
I have it on my machine with a custom logo on bootup. I thought I would
like to see something other t
H. S. wrote:
I have been trying to get frambuffer bootup work in 2.6.9 without
success so far. Cannot get the logo at all. Screen is blank till X
starts up. I have same experience on Sid machines, one uses nv driver
and the other ati.
If somebody has that high resolution screen boot up working
Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> Sridhar M.A.([EMAIL PROTECTED]) is reported to have said:
> > On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
> >> I have been trying to get frambuffer bootup work in 2.6.9 without
> >> success so far. Cannot get the logo at
Apparently, _Sridhar M.A._, on 19/11/04 19:53,typed:
On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
> I have been trying to get frambuffer bootup work in 2.6.9 without
> success so far. Cannot get the logo at all.
I have it on my machine with a custom logo on bootup. I thought I wo
At Fri, 19 Nov 2004 15:55:23 -0500,
H. S. wrote:
>
> I have been trying to get frambuffer bootup work in 2.6.9 without
> success so far. Cannot get the logo at all. Screen is blank till X
> starts up. I have same experience on Sid machines, one uses nv driver
> and the other ati.
>
> If somebo
Sridhar M.A.([EMAIL PROTECTED]) is reported to have said:
> On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
>> I have been trying to get frambuffer bootup work in 2.6.9 without
>> success so far. Cannot get the logo at all.
>
> I have it on my machine with a custom logo on bootup.
On Fri, Nov 19, 2004 at 03:55:23PM -0500, H. S. wrote:
> I have been trying to get frambuffer bootup work in 2.6.9 without
> success so far. Cannot get the logo at all.
I have it on my machine with a custom logo on bootup. I thought I would
like to see something other than Tux on bootup sc
nto
framebuffer. I was considering trying just the vanilla sources without
the debian patches to see if its a patch thats conflicting, apart from
that, i get the same as you.
No luck with that either. I did as you mentioned above and tried by
putting first vesafb into /etc/modules and then aty128fb (
*the module that is* the screen will go into
framebuffer. I was considering trying just the vanilla sources without
the debian patches to see if its a patch thats conflicting, apart from
that, i get the same as you.
--
*-*
| Glyn Te
I have been trying to get frambuffer bootup work in 2.6.9 without
success so far. Cannot get the logo at all. Screen is blank till X
starts up. I have same experience on Sid machines, one uses nv driver
and the other ati.
If somebody has that high resolution screen boot up working with the tux
e working properly. Using
> vga=791, I was not getting anything meaningful during the boot process.
> Just some noise in the top 25% or so of the screen. I then removed the
> framebuffer support and recompiled and now 2.6.9 boots okay (but with
> the usual lower resolution of
the top 25% or so of the screen. I then removed the
framebuffer support and recompiled and now 2.6.9 boots okay (but with
the usual lower resolution of course). Anyone else experience this problem?
->HS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&q
ogo on boot if you're using frambuffer
> > support. If you have the kernel-source package installed, read the
> > files in /usr/src/linux/Documentation/fb/
>
> Like I said, I'm missing info. Like adding video= or vga= to the
> menu.lst to tell grub I want to use framebuff
t point.
>
> VESA FB != Nvidia FB != X Driver
>
> VESA frame buffer code relies on gfx cards having implemented an old
> 'common' standard. If there was an Nvidia fb driver, you could probably
> get various extra features switched on for your fb console. Not sure
>
rds having implemented an old
'common' standard. If there was an Nvidia fb driver, you could probably
get various extra features switched on for your fb console. Not sure
there is an Nvidia framebuffer driver even.
The X driver for your Nvidia card is a completely different kettle of
fish. Besi
;>> I'm making progress. By adding video=vesa vga=0x317 I get a blank screen
> >>> up to the point that X starts. That's not a problem for now, because I
> >>> know I'm on the right track. I'm recompiling a kernel right now that has
> >>>
roblem for now, because I
know I'm on the right track. I'm recompiling a kernel right now that has
vesa included, and not a module, as well as console framebuffer support.
the blank screen means you dont have the proper frame buffer defined
( same probelm as my stuff ... just need to
hi ya
On Tue, 31 Aug 2004, Brian Pack wrote:
> I compiled a new kernel, with vesa included instead of a module, same
> for console framebuffer. Added video=vesa and vga=0x317 in menu.lst for
> grub.
>
> I've got Tux! :)
congrats ... now add your own corp logo next to tu
m on the right track. I'm recompiling a kernel right now that has
> > vesa included, and not a module, as well as console framebuffer support.
>
> the blank screen means you dont have the proper frame buffer defined
> ( same probelm as my stuff ... just need to tweek the various fb o
vesa included, and not a module, as well as console framebuffer support.
the blank screen means you dont have the proper frame buffer defined
( same probelm as my stuff ... just need to tweek the various fb options )
> Once I get that, *then* I can start playing with the bootsplash patch.
led, read the
> files in /usr/src/linux/Documentation/fb/
Like I said, I'm missing info. Like adding video= or vga= to the
menu.lst to tell grub I want to use framebuffer mode at boot. Google is
my friend. :)
I'm making progress. By adding video=vesa vga=0x317 I get a blank screen
up
On Tue, 31 Aug 2004 11:07:34 -0400, Brian Pack <[EMAIL PROTECTED]> wrote:
> I want to have either the Tux logo or a bootsplash screen at boot. I've
> found a few pages that explain this, but each time I delve deeper I hit
> roadblocks. I've been referred to kernel patches at www.bootsplash.de,
> bu
I want to have either the Tux logo or a bootsplash screen at boot. I've
found a few pages that explain this, but each time I delve deeper I hit
roadblocks. I've been referred to kernel patches at www.bootsplash.de,
but I have no idea which package I need.
I know I'm missing something here, but ha
1 - 100 of 407 matches
Mail list logo
