log (b).
But the system seems to be working perfectly, so now I'm just left to
copy my files and fine tune the install.
Thanks again for the help!
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
Le 25 janvier 2012 18:10, Sven Joachim a écrit :
> On 2012-01-25 18:04 +0100, Rémi Moyen wrote:
>
>> I am also guessing, based on this (why didn't I think about that
>> earlier?) that in the 3.1 kernel, my card is supposed to be supported
>> by nouveau, hence it tri
Le 25 janvier 2012 16:07, Sven Joachim a écrit :
> On 2012-01-25 16:33 +0100, Rémi Moyen wrote:
>
>> Well, I'm guessing that at the early stage of the boot some very crude
>> driver is used and things fail when the kernel tries to load/use
>> something more compli
Le 25 janvier 2012 16:07, richard a écrit :
> OK different approach.
> You can identify if its kernel 3 problem or not by booting up off a live cd.
> Download a Fedora FC16 live CD..
Good point. If I don't find another way to tweak the install, I'll try that.
--
Rémi Moyen
Le 25 janvier 2012 14:36, Brian a écrit :
> On Wed 25 Jan 2012 at 09:56:15 +0000, Rémi Moyen wrote:
>
>> OK, so now I get what I think should be a working up-to-date testing
>> system. Rebooting on the 2.6.32 kernel works again perfectly. But
>> rebooting on the 3.1 k
hat it should)? Same
question for update-initramfs, how can I check that the generated
initrd is OK (and will it update the initrd for the 3.1 kernel and not
only the 2.6 one)?
Thanks!
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubsc
ething, add it
somewhere else to make sure it is used...)
Note also that installing the nvidia-glx adds a file in
/etc/modprobe.d that blacklists nouveau, and I still get the problem
with the nvidia-glx package installed.
So blacklisting nouveau in /etc/modprobe.d doesn't seem to be enough.
--
Ré
from the start).
So, does anyone have an idea of what is causing the problem, and how
to fix it? I must say that I am very disappointed, my old computer is
running the 3.1 kernel without ever complaining (well, not about this
at least...) and I was not expecting such big problems with a brand
new on
2010/2/11 John Hasler :
> Rémi Moyen writes:
>> aptitude man page is not helpful, I haven't found this in the online
>> doc either... Did I miss a "complete" doc (apart from the code
>> itself!) ?
>
>
> Package: aptitude-doc-en
If it
in the online
doc either... Did I miss a "complete" doc (apart from the code
itself!) ?
Thanks!
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e I only
have the problem with the 2.6.30 kernel, not 2.6.26 nor 2.6.32.
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ut deprecated udev options that have to be
changed in various files, but apart from this, I don't see any
problems and all my hardware is working fine.
Has anyone an idea as to what happens with the 2.6.30 kernel? I didn't
find anything in the bug reports nor on the web about this.
Thanks!
Le 19 janvier 2010 11:09, Rémi Moyen a écrit :
> I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
> and logged in... only to see kdm pop again! No error message.
OK, I've got a bit more news, and that's not good news...
First, about the missing files, I o
he pointer, but again, I don't see any cases where
there are missing files from the package. There seem, however, to be
indeed a problem with kdm/policykit.
Well, I'll look into it, but if I don't find a solution, I guess I'll
have to downgrade to 3.5 again (stable should do the
files
in /etc/kde4/kdm (and perhaps in other places, I just happened to
notice these ones). So my guess is that something else is wrong. No?
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
behaviour.
Does anybody have an idea of what's going on with this package, or of
any tests I could run to find the problem?
Thanks!
--
Rémi Moyen
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
16 matches
Mail list logo
