On 18/02/11 20:11, Sven Joachim wrote:
On 2011-02-18 20:22 +0100, Dom wrote:
On 18/02/11 18:24, Camaleón wrote:
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
b) nvidia propietary driver
c) vesa/fb
d) nv (obsolete but still available, AFAICT)
d) is the onl
On Vi, 18 feb 11, 19:22:07, Dom wrote:
>
> d) is the only option that worked for one of my machines. It used to
> run the nvidia driver, but stopped working when I upgraded it to
> squeeze and it tried to use the nouveau driver.
>
> Removing all traces of the nvidia driver and just using nouveau
On Sat, 19 Feb 2011 15:17:15 +0100, Pier Paolo wrote:
> 2011/2/19 Camaleón
>> > Can't recall exactly... some procedure from the wiki; i think i
>> > blacklisted nouveau, and tried to install kernel-nvidia something,
>> > but substantially that won't prevent nouveau from loading and messing
>> > u
2011/2/19 Camaleón
> On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote:
>
> > 2011/2/19 Camaleón
> >
> >> I asked what you tried hard for "the easy way", what steps did you
> >> follow and what errors did you get.
> >>
> > Can't recall exactly... some procedure from the wiki; i think i
> > bla
On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote:
> 2011/2/19 Camaleón
>
>> I asked what you tried hard for "the easy way", what steps did you
>> follow and what errors did you get.
>>
> Can't recall exactly... some procedure from the wiki; i think i
> blacklisted nouveau, and tried to instal
2011/2/19 Camaleón
> On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote:
>
> > 2011/2/18 Camaleón
> >
> >> What is what you "tried hard", exactly?
> >>
> > from rescue mode chrooting to recompile kernel after a not even
> > system-base-install alternate cd netinstall. Booting from hard disk
> >
On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote:
> 2011/2/18 Camaleón
>
>> What is what you "tried hard", exactly?
>>
> from rescue mode chrooting to recompile kernel after a not even
> system-base-install alternate cd netinstall. Booting from hard disk
> resulted in complete unusable system
On Fri, 18 Feb 2011 13:49:33 -0500, Paul Cartwright wrote:
>> To make this a bit more clear, nvidia card owners can run either:
>>
>> a) KMS+nouveau
>>
> so, what is this, why would I want it?
It's another driver available for your card. It is open source and it
uses reverse engineering tech
On Fri, 18 Feb 2011 13:49:33 -0500 (EST), Paul Cartwright wrote:
> Camaleón wrote:
>>
>> You are not using "nuvó" at all but the nvidia driver:-)
>>
>
> right, I knew that.
>>
>> To make this a bit more clear, nvidia card owners can run either:
>>
>> a) KMS+nouveau
>> ...
>
> so, what is
On 2011-02-18 20:22 +0100, Dom wrote:
> On 18/02/11 18:24, Camaleón wrote:
>> To make this a bit more clear, nvidia card owners can run either:
>>
>> a) KMS+nouveau
>> b) nvidia propietary driver
>> c) vesa/fb
>> d) nv (obsolete but still available, AFAICT)
>>
>
> d) is the only option that worked
On 18/02/11 18:24, Camaleón wrote:
On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote:
On 02/18/2011 07:41 AM, Camaleón wrote:
By installing nvidia driver, "nuvó" should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) "nuvó" should not load.
wow, I just looked at my new Sq
On Fri, 18 Feb 2011 10:21:30 -0500 (EST), Chris Brennan wrote:
> On Thu, Feb 17, 2011 at 8:33 PM, Stephen Powell wrote:
>>
>> Blacklisting a module only prevents udev from loading it. That's
>> because when udev loads a module it uses the "-b" switch of the
>> modprobe command. However, when the
2011/2/18 Camaleón
> On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote:
>
> > 2011/2/18 Camaleón
> >
> >> By installing nvidia driver, "nuvó" should not be loaded.
> >>
> >> Also, by disabling KMS (nouveau.modeset=0) "nuvó" should not load.
> >>
> > At least in Debian Lenny and Fedora 12 it wa
Driver"nvidia"
^^
You are not using "nuvó" at all but the nvidia driver:-)
right, I knew that.
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
so, what is this, why would I want it?
b) nvidia propietary driv
On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote:
> On 02/18/2011 07:41 AM, Camaleón wrote:
>> By installing nvidia driver, "nuvó" should not be loaded.
>>
>> Also, by disabling KMS (nouveau.modeset=0) "nuvó" should not load.
>>
>>
> wow, I just looked at my new Squeeze xorg.conf devi
On 02/18/2011 07:41 AM, Camaleón wrote:
By installing nvidia driver, "nuvó" should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) "nuvó" should not load.
Greetings,
wow, I just looked at my new Squeeze xorg.conf device section. What is
the nouveau, and should we be using/not usi
On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote:
> 2011/2/18 Camaleón
>
>> By installing nvidia driver, "nuvó" should not be loaded.
>>
>> Also, by disabling KMS (nouveau.modeset=0) "nuvó" should not load.
>>
> At least in Debian Lenny and Fedora 12 it was not so simple as said in
> debian w
Camaleón wrote:
El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió:
On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote:
By installing nvidia driver, "nuvó" should not be loaded.
the non-free nvidia driver script/installer dies, complaining that nouveau
is present and needs to be removed f
El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió:
> On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote:
>
> > By installing nvidia driver, "nuvó" should not be loaded.
> >
>
> the non-free nvidia driver script/installer dies, complaining that nouveau
> is present and needs to be removed firs
2011/2/18 Camaleón
> On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote:
>
> > I am not new to the linux way of things but I am new to the debain way
> > of things and I have some questions that need to be answered. To start,
> > I need to ket rid of nouveau as it's screwing with uvesafb (p
On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote:
> I am not new to the linux way of things but I am new to the debain way
> of things and I have some questions that need to be answered. To start,
> I need to ket rid of nouveau as it's screwing with uvesafb (produces an
> 'Error -22').
(
> I am not new to the linux way of things but I am new to the debain
> way of things and I have some questions that need to be answered. To
> start, I need to ket rid of nouveau as it's screwing with uvesafb
> (produces an 'Error -22'). I added it to
> /etc/modprobe.d/blacklist.conf but it's stil
On Thu, 17 Feb 2011 20:07:51 -0500 (EST), Chris Brennan wrote:
>
> I am not new to the linux way of things but I am new to the debain
> way of things and I have some questions that need to be answered. To
> start, I need to ket rid of nouveau as it's screwing with uvesafb
> (produces an 'Error -2
On Tue, Feb 02, 2010 at 01:50:23AM +1300, Chris Bannister wrote:
> Looks like a bug in /usr/share/doc/grub2-splashimages/README where it
> says to run update-grub, that should be update-grub2.
Arrrgh ... I see that:
fischer:~# less /usr/sbin/update-grub2
#!/bin/sh -e
exec update-grub
Sorry abou
On Wed, Jan 27, 2010 at 09:17:51PM +0200, Andrei Popescu wrote:
> On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote:
> > I was able to achieve the desired resolution of 1280x800 (equivalent
> > to, I think, 0x361) by manually editing grub.cfg but the grub menu
> > does not show correctly. It only
On Fri,22.Jan.10, 15:38:55, Nima Azarbayjany wrote:
> Hi,
>
> I have recently installed Squeeze on my laptop and most things seem
> to work fine right now.
>
> I used to add vga=xxx to the kernel parameters line to adjust the
> console resolution but this is now deprecated as a message printed
>
> On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote:
[..]
> > > I don't know if my video card takes care of that, but I find that
> > > moving the cursor, scrolling, etc. is noticeably faster on a
> > > framebuffer console than on the vga console. Mind you, since the
> > > vesa dr
On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote:
> I was able to achieve the desired resolution of 1280x800 (equivalent
> to, I think, 0x361) by manually editing grub.cfg but the grub menu
> does not show correctly. It only fills the left top quarter of the
> screen and parts of it cannot be se
> My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
> install, yet /etc/grub.d/40_custom is there and describes it, and
> /boot/grub/menu.lst is there to upgrade from.
From
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/432254
I finally got the boot into FreeBSD to wor
On Mon, Jan 25, 2010 at 10:26:45PM EST, s. keeling wrote:
[..]
> My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
> install, yet /etc/grub.d/40_custom is there and describes it, and
> /boot/grub/menu.lst is there to upgrade from.
Just be aware that auto-detecting kernels is not
tv.deb...@googlemail.com :
> s. keeling wrote:
> >
> > Isn't it strange that we now need to `update-grub`, when having to run
> > "lilo" was such a hardship before?
> >
> > Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot
> > menu, grumble, mumble, ... Grr.
>
> Hi grumpy,
Okay... I finally got it to work. I set two different resolutions, that
is, I did not use gfxpayload=keep.
Thanks all.
Nima
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
s. keeling wrote:
> Jeffrey Cao :
>> On 2010-01-22, Nima Azarbayjany wrote:
>>> I have recently installed Squeeze on my laptop and most things
>>> seem to work fine right now.
>>>
>>> I used to add vga=xxx to the kernel parameters line to adjust the
>>> console resolution but this is now deprecat
Jeffrey Cao :
> On 2010-01-22, Nima Azarbayjany wrote:
> >
> > I have recently installed Squeeze on my laptop and most things
> > seem to work fine right now.
> >
> > I used to add vga=xxx to the kernel parameters line to adjust the
> > console resolution but this is now deprecated as a message p
On Sun, Jan 24, 2010 at 05:52:22AM EST, Nima Azarbayjany wrote:
> I was able to achieve the desired resolution of 1280x800 (equivalent
> to, I think, 0x361) by manually editing grub.cfg but the grub menu
> does not show correctly. It only fills the left top quarter of the
> screen and parts of
I was able to achieve the desired resolution of 1280x800 (equivalent to,
I think, 0x361) by manually editing grub.cfg but the grub menu does not
show correctly. It only fills the left top quarter of the screen and
parts of it cannot be seen. The rest was fine (the boot up of linux I
mean) wit
>>tv.debian wrote:
>> Hi, I use a slightly different way, I put:
>>
>> GRUB_GFXMODE="1440x900 640x480"
>>
>> in /etc/defaults/grub (native resolution first, fall-back one isn't
>> necessary, it's the default).
>>
>> Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
>> (around line
> It's weird but it's not working for me. Somehow update-grub (as well as
> update-grub2, in case they are different) ignore all modifications to
> /etc/default/grub. I'm giving up. Should I report a bug?
Are you making all the changes that have been suggested?
In short:
In
/etc/default/grub
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
Hi, I use a slightly different way, I put:
GRUB_GFXMODE="1440x900 640x480"
in /etc/default
On 2010-01-22 at 18:11:38 -0500, Chris Jones wrote:
> PIII 650MHz - 386M of RAM - ATI Rage Mobility (Mach64).
That is *lightning fast* compared to my slowest machine,
a PII 266 MHz with a very slow hard drive. And the saddest
thing is, until about three years ago, it was my fastest machine!
The
>Nima Azarbayjany wrote:
>
>> set gfxpayload=keep will tell Grub2 to hand off the graphics settings
>> to the kernel, which if configured properly will carry them forward.
>> There are some other settings to tweak as well, insmod vbe and whatnot
>> in the appropriate file, but that's about the gis
On Sat, Jan 23, 2010 at 01:15:39AM EST, Chris Jones wrote:
[..]
> I the above question the bizarre joke, or was this meant as a reply to a
> different post?
s/I the above/Is the above/
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Fri, Jan 22, 2010 at 09:39:50PM EST, Alex Samad wrote:
> On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote:
[..]
> > I don't know if my video card takes care of that, but I find that
> > moving the cursor, scrolling, etc. is noticeably faster on a
> > framebuffer console than on the
On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote:
> On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote:
>
[snip]
> I don't know if my video card takes care of that, but I find that moving
> the cursor, scrolling, etc. is noticeably faster on a framebuffer
> console than on t
On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote:
> I prefer a hardware text mode virtual console for a number of
> reasons, but one of them is that it performs better, particularly
> on the ancient under-powered hardware that I tend to use!
PIII 650MHz - 386M of RAM - ATI Rage Mobili
On 2010-01-22 at 15:50:02 -0500, Chris Jones wrote:
> On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote:
> > So then this is designed to work with framebuffer graphics mode
> > virtual consoles, right? That wouldn't help me. I prefer the
> > traditional hardware text mode virtual conso
On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote:
[..]
> So then this is designed to work with framebuffer graphics mode
> virtual consoles, right? That wouldn't help me. I prefer the
> traditional hardware text mode virtual consoles.
Just curious, but what's wrong with using a f
set gfxpayload=keep will tell Grub2 to hand off the graphics settings
to the kernel, which if configured properly will carry them forward.
There are some other settings to tweak as well, insmod vbe and whatnot
in the appropriate file, but that's about the gist of it. The nice
thing is it make
On Fri, 2010-01-22 at 13:08 -0500, Stephen Powell wrote:
> Jeffrey Cao wrote in another post that grub2 can support the traditional
> vga kernel option by means of editing /etc/default/grub and adding the
> line
>
> GRUB_CMDLINE_LINUX="vga=xxx"
>
> and then running "update-grub" to update /boot/
On 2010-01-22 at 12:08:56 -0500, Arthur Machlas wrote:
> set gfxpayload=keep will tell Grub2 to hand off the graphics settings to the
> kernel, which if configured properly will carry them forward. There are some
> other settings to tweak as well, insmod vbe and whatnot in the appropriate
> file, b
On Fri, Jan 22, 2010 at 10:03 AM, Stephen Powell wrote:
> On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote:
> > Seem like gfxpayload is the substitute, but now I can't find where is the
> > doc (it doesn't appear in kernel-parameters.txt).
>
> I'm really going out on a limb when I talk about
On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote:
> Seem like gfxpayload is the substitute, but now I can't find where is the
> doc (it doesn't appear in kernel-parameters.txt).
The "vga" kernel option is a strange option. It's really more of
a bootloader option than a kernel option. The bo
On 2010-01-22 at 08:26:27 -0500, Jeffrey Cao wrote:
> On 2010-01-22, Nima Azarbayjany wrote:
> > Hi,
> >
> > I have recently installed Squeeze on my laptop and most things seem to
> > work fine right now.
> >
> > I used to add vga=xxx to the kernel parameters line to adjust the
> > console resol
Nima Azarbayjany wrote at 2010-01-22 06:08 -0600:
> I have recently installed Squeeze on my laptop and most things seem
> to work fine right now.
>
> I used to add vga=xxx to the kernel parameters line to adjust the
> console resolution but this is now deprecated as a message printed
> at the start
Hi,
On Fri, Jan 22, 2010 at 1:08 PM, Nima Azarbayjany
wrote:
> Hi,
>
> I have recently installed Squeeze on my laptop and most things seem to work
> fine right now.
>
> I used to add vga=xxx to the kernel parameters line to adjust the console
> resolution but this is now deprecated as a message p
On 2010-01-22, Nima Azarbayjany wrote:
> Hi,
>
> I have recently installed Squeeze on my laptop and most things seem to
> work fine right now.
>
> I used to add vga=xxx to the kernel parameters line to adjust the
> console resolution but this is now deprecated as a message printed at
> the star
> The 80x50 LILO can give me, also gives me 8x8 pixel characters.
> Using SVGATextMode I have 116x51 using 16x9 pixel characters.
> Readable characters are enough reason for me.
I don't even remember what I am using in lilo but I am quite happy with
it (bully for me).
> But if you haven't config
On Sat, 21 Feb 1998, Bill Leach wrote:
> William R. Ward wrote:
> [snip]
> > I've never seen much point in svgatextmode, personally - you can get
> > 80x50 from LILO, isn't that enough?
The 80x50 LILO can give me, also gives me 8x8 pixel characters. Using
SVGATextMode I have 116x51 using 16x9 pix
58 matches
Mail list logo
