>> > "PG(" == Peter G (nephros) writes:
>> PG(> I think it is .modeset=0 (e.g. "radeon.modeset=0").
>> PG(> I use both: "vmlinuz foo radeon.modeset=0 modeset=0" which does work.
OK, I finally figured it out:
$ zgrep -c modeset
/usr/share/doc/linux-doc-2.6.32/Documentation/kernel-parameters.t
On Sat, Oct 23, 2010 at 02:52:00PM EDT, jida...@jidanni.org wrote:
> Allow me to ask a stupid question.
Permission granted.
> You see, when that happens, whatever that was on the screen goes away.
> Nor was most of what was on the screen at that point stored in dmesg or
> in any /var/log/* file,
> "PG(" == Peter G (nephros) writes:
PG(> I think it is .modeset=0 (e.g. "radeon.modeset=0").
PG(> I use both: "vmlinuz foo radeon.modeset=0 modeset=0" which does work.
How does one determine the driver name to use? At one reboot per test
and with all the unsuccessful combinations I've trie
Hodie IX Kal. Nov. MMX AUC quidam/quædam/quoddam 'jida...@jidanni.org' inquit:
Fabian Henze said:
"nomodeset" is the parameter you are searching for.
I tried it.
$ cat /etc/debian_version /proc/cmdline
squeeze/sid
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=...9dc78 ro single panic=33
nom
On Sun, 24 Oct 2010 02:52:00 +0800, jidanni wrote:
> Allow me to ask a stupid question.
O.k, but better if you don't cross-post :-)
> Somewhere near this point in the dmesg messages, the console blanks and
> becomes a different resolution.
(...)
Different resolution? You mean the console text
Fabian Henze said:
> "nomodeset" is the parameter you are searching for.
I tried it.
$ cat /etc/debian_version /proc/cmdline
squeeze/sid
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=...9dc78 ro single panic=33
nomodeset
It didn't work.
> But why would you want disable that?
http://bugs.debian.
On Sun, 2010-10-24 at 02:52 +0800, jida...@jidanni.org wrote:
> Allow me to ask a stupid question.
>
> Somewhere near this point in the dmesg messages, the console blanks and
> becomes a different resolution.
>
> [ 8.135936] Marking TSC unstable due to TSC halts in idle
> [ 8.137762] processo
Allow me to ask a stupid question.
Somewhere near this point in the dmesg messages, the console blanks and
becomes a different resolution.
[ 8.135936] Marking TSC unstable due to TSC halts in idle
[ 8.137762] processor LNXCPU:00: registered as cooling_device0
[ 8.144690] Switching to clocks
Sjoerd Hardeman wrote:
> abdelkader belahcene schreef:
>> Hi,
>> I want to change screen resolution not only for user (it is done from
>> the menu), but for every body as root.
>> There is no mode resolution in last version of xorg.conf ?
>> in previous there was
>> modes with diffrent resoluti
abdelkader belahcene schreef:
> Hi,
> I want to change screen resolution not only for user (it is done from
> the menu), but for every body as root.
> There is no mode resolution in last version of xorg.conf ?
> in previous there was
> modes with diffrent resolution 800x600, 1024 ..
>
> tha
Hi,
I want to change screen resolution not only for user (it is done from the
menu), but for every body as root.
There is no mode resolution in last version of xorg.conf ?
in previous there was
modes with diffrent resolution 800x600, 1024 ..
thanks for help
Markus wrote:
>
> I have a very simple but irritating problem: I have
> started (right after installation of Debian) startx
> and now it automatically starts every time the system
> is started. The resolution is though way too low
> (340*240 or something) and this causes huge
> difficulties in try
On Wed, 5 Jun 2002 02:24:51 -0700 (PDT)
"Markus" <[EMAIL PROTECTED]> wrote:
> I have a very simple but irritating problem: I have
> started (right after installation of Debian) startx
> and now it automatically starts every time the system
You probably installed kdm/xdm/gdm. You can either remove
I have a very simple but irritating problem: I have
started (right after installation of Debian) startx
and now it automatically starts every time the system
is started. The resolution is though way too low
(340*240 or something) and this causes huge
difficulties in trying to get even to the basic
i am using debian @ work so i am using lilo. I tried the vga=791; however
on reboot, i got a blank screen. The system started up, i edited my
lilo.conf file (blindly) and rebooted. Ahhh now I can see. So i am
thinking that i need to do other stuff to get this working, what else did
you do?
thanks
I use linuxppc at home, and i can easily change the resolution of the VSs,
but at work I am stuck in 640x480, is there some way of getting more
resolution out of the VSs? I have tried vga=ext in my lilo.conf, but am
unhappy with the result. I would love 1024x768, the same res I run X.
thanks in ad
16 matches
Mail list logo