[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: random quirkyness



On 1/23/07, Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
Mike, please don't cc: me as I subscribe to the list. thanks.

I apologize, I'm using gmail and it did that automatically for some reason.

On Tue, Jan 23, 2007 at 03:27:40PM -0600, Mike Myers wrote:
> On 1/23/07, Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
> >
> >On Tue, Jan 23, 2007 at 02:41:40PM -0600, Mike Myers wrote:
> >> Hi all,
> >>
> >> I'm still trying to adjust from Gentoo's way of doing things (do it
> >> manually) to debian's (apt-something) way.  So far everything has been
> >> great, but i'm having trouble finding docs on a couple of issues I'm
> >> having.  Both of them seem related to modules.
> >>
> >> First one is with the nvidia driver.  It seems like everytime my debian
> >box
> >> is rebooted, I have to re-apt-get nvidia-glx before I can use
> >xorg.  Also,
> >> GDM doesn't seem to like my 1440x900 (widescreen) resolution and I can't
> >> seem to do anything about it other than just not use GDM (not that
> >ditching
> >> it is a big deal).
> >
> >I can't speak to the resolution issue, but the xorg issue should not
> >be happening. when you re-apt-get it, does it download it again and
> >appear to be actually reinstalling it? I wonder if your xorg.conf is
> >not getting updated correctly and you are correcting for it by
> >reinstalling each time. how about a copy of your xorg.conf for us to
> >look at as well as dpkg -l | grep nvidia
>
>
> I'm pretty sure it's not related to xorg, since it works fine after running
> 'apt-get --reinstall install nvidia-glx', even with a widescreen.  It's only
> after a reboot that I must run that, as long as I want to use the nvidia
> driver.  If I use the 'nv' driver, then of course there's no issue there,
> but that driver sucks.  Just to oblige you, here's the contents: (hopefully
> it looks sane enough to read)
>

so, what exactly happens when you *don't* apt-get install nvidia-glx?
what output do you get?

It tries to start and then fails, saying it can't find the nvidia module, even though it's loaded.  So I get a blank screen.

>
[ snipped what looks like a perfectly reasonable xorg.conf ]
>
> Here's the output of 'dpkg -l'.  Maybe you can explain what it means?
>
> 'debian:~# dpkg -l | grep nvidia
> ii  nvidia-glx                        1.0.8776-4                      NVIDIA
> binary XFree86 4.x driver
> rc  nvidia-glx-legacy                 1.0.7184-3                      NVIDIA
> binary Xorg driver (legacy version)
> ii  nvidia-kernel-2.6-686             1.0.8776+5                      NVIDIA
> binary kernel module for 2.6 series c

****
> ii  nvidia-kernel-2.6.18-3-686        1.0.8776+5                      NVIDIA
> binary kernel module for Linux 2.6.18
****

> ii  nvidia-kernel-common              20051028+1                      NVIDIA
> binary kernel module common files

****
> ii  nvidia-kernel-legacy-2.6.18-3-486 1.0.7184+5                      NVIDIA
> binary kernel module for Linux 2.6.18
****



hmmm... you have two sets of nvidia kernel modules installed. That may
contribute to the problem. purge one of them (probably the legacy one)
and see what happens. There for different architectures, so it
*shouldn't* matter, but what the heck...

This might have happened when I was trying to narrow down which one I needed.  I didn't realize the legacy drivers were still installed.  I'll try removing those and see if it makes a difference.  It might be loading the legacy one, I guess, which would explain why xorg fails to start at first.

>
> >
> >> The other issue is that I have two soundcards.  That in itself isn't a
> >> problem, but the it is a problem with the way debian apparently handles
> >> them, which seems to be the most random thing I've ever seen.  When it
> >boots
> >> up, it picks one or the other so sometimes it works and sometimes it
> >> doesn't.  I can run alsa-conf to get it to use the correct one, but it's
> >> annoying doing it every time, especially when having to apt-get
> >nvidia-glx
> >> after rebooting also.
> >
> >sounds like a udev problem. default udev rules are not necessarily
> >predictable in terms of how it assigns device nodes to hardware. you
> >may need to write some custom udev rules to get your soundcards
> >recognised properly. check the archives from about a month ago for a
> >couple threads on using multiple sound cards.
>
>
> I'd prefer it to just not use one of the cards at all.  I would hope there
> would be an easier way to modify it's detection, I mean I don't need it to
> detect anything in the first place.  I'd rather just turn whatever is doing
> that off and have the module automatically loaded no matter what.  That's
> how I had it in Gentoo and I never had any issues.

if the cards use different modules, then just blacklist the
appropriate ones in /etc/modules and in /etc/modprobe.d/blacklist (I
think).

Thanks, I'll check that out too.

A


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFtoxzaIeIEqwil4YRApdpAJ9xQDMhsqgeA+9/teB5xhd6cu+DjwCfazRN
AOa/w9Md8KSMtbMAh6AUEB8=
=FfDm
-----END PGP SIGNATURE-----





As far as modules and autoloading them goes, in Gentoo, there was a script; /etc/modules.d/autoload/kernel- 2.6, which was basically a list of modules to be loaded when booted.  Is there some kind of equivalent to this in Debian?  I'd just rather Debian not try to detect my hardware.

Thanks!

Reply to: