1 |
On Wednesday 25 Jan 2012 20:23:33 BRM wrote: |
2 |
> Well, just to follow up on this - I did get the nouveau driver working and |
3 |
> the system operational. |
4 |
> |
5 |
> - The console still does not work; don't know why but it seems to not get a |
6 |
> working resolution. Not sure how to fix that right now. - Starting XDM |
7 |
> (KDM) works, and brings up the login. |
8 |
> - I am able to SSH in from another system now. |
9 |
> |
10 |
> Now, this was after I paid a little closer attention to some updates. I |
11 |
> resync'd emerge, and got the 3.1.6 linux kernel, which I promptly upgraded |
12 |
> to. I also went back and rebuilt the X11 drivers (nouveau, keyboard, |
13 |
> mouse, evdev), and paid closer attention to the output of the nouveau |
14 |
> driver which immediately started off saying there was an issue with the |
15 |
> ACPI_WMI and MXM_WMI interfaces from the kernel - another kernel rebuild |
16 |
> after enabling those (it had when I selected the driver I think, but I |
17 |
> kept disabling the x86 features which removed them) and then it didn't |
18 |
> complain any longer. |
19 |
> |
20 |
> So, I seem to have a working X environment; but no working console |
21 |
> environment for now. I'm guessing I probably need to tell the nouveau |
22 |
> frame buffer driver what resolution to use to resolve that one. |
23 |
> |
24 |
> Thanks all! |
25 |
> |
26 |
> Ben |
27 |
> |
28 |
> >________________________________ |
29 |
> > |
30 |
> > From: BRM <bm_witness@×××××.com> |
31 |
> > |
32 |
> >To: "gentoo-user@l.g.o" <gentoo-user@l.g.o> |
33 |
> >Sent: Sunday, January 22, 2012 8:49 PM |
34 |
> >Subject: Re: [gentoo-user] System shuts off on boot-up |
35 |
> > |
36 |
> >> From: BRM <bm_witness@×××××.com> |
37 |
> >> To: "gentoo-user@l.g.o" <gentoo-user@l.g.o> |
38 |
> >> Cc: |
39 |
> >> Sent: Sunday, January 22, 2012 11:50 AM |
40 |
> >> Subject: Re: [gentoo-user] System shuts off on boot-up |
41 |
> >> |
42 |
> >>> From: Neil Bothwick <neil@××××××××××.uk> |
43 |
> >>> |
44 |
> >>> On Fri, 20 Jan 2012 19:57:31 -0800 (PST), BRM wrote: |
45 |
> >>>> As the system starts to boot-up, it switches like it is going to |
46 |
> >>>>start X - changing a video mode somehow. I don't have xdm in the |
47 |
> >> |
48 |
> >> runlevels |
49 |
> >> |
50 |
> >>>> yet, so it can't be starting XDM at all.This seems to happen right |
51 |
> >>>> after udevd is started, while it waiting on the udev events. The |
52 |
> >>>>system then just shuts off (power remain on - fans are still on, but |
53 |
> >>>>monitors are off, and nothing responds, etc.) , and it never |
54 |
> >>>>completes boot-up. |
55 |
> >>>> |
56 |
> >>> Do you have another computer you can use to test if it is alive with |
57 |
> >>> ping or SSH? This is occurring around the point at which KMS kicks in, |
58 |
> >>> you may be just losing your display but still have an otherwise |
59 |
> >>> working system. |
60 |
> >> |
61 |
> >> Yes SSH is enabled; no I can't SSH into it. It seems to be completely |
62 |
> >> dead. |
63 |
> >> |
64 |
> >>> Try adding nomodeset (or intel.modeset=0) to your kernel boot |
65 |
> >>> parameters to disable KMS. |
66 |
> >> |
67 |
> >> Ok. Setting "nomodeset" works. However, if I understand the nouveau |
68 |
> >> driver correctly then that won't work for using the nouveau driver as it |
69 |
> >> requires KMS. |
70 |
> >> |
71 |
> >> Digging a little deeper into the nouveau driver and KMS[1], I discovered |
72 |
> >> that I probably need to have CONFIG_VT_HW_CONSOLE_BINDING set in the |
73 |
> >> kernel config as well - which it wasn't. So that probably explains what |
74 |
> >> was happening as CONFIG_HW_CONSOLE was set, so there may have been two |
75 |
> >> drivers competing for fb0. |
76 |
> >> |
77 |
> >> Now off to build a new kernel... |
78 |
> > |
79 |
> >Well, that doesn't seem to have been the only problem at least...still |
80 |
> >don't know what's doing it. |
81 |
|
82 |
Does it work satisfactorily with kernel 3.0.6? |
83 |
|
84 |
I found the 3.1.6 breaking suspend on my machine so have gone back to 3.0.6, |
85 |
but my hardware and video driver is different to yours. |
86 |
-- |
87 |
Regards, |
88 |
Mick |