Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
John Burrell wrote: > Thanks for your input. All the items you mention were covered at some > point in the discussion. Armin confirmed that all the software > components associated with the nouveau driver were performing as > expected - at least as far as he could tell from the logs. There > didn't seem to be anything wrong with the installation.There seems to > be something wrong with the way the nouveau driver communicates with > my particular GPU. The card doesn't appear to recognize the signal(s) > that are sent to it and without a signal it will simply cycle through > red, green blue and white. > > The nouveau site says that drm.ko must be loaded before nouveau.ko > so I was going to check that this happens in my case. I've been following this and think you should be confirming it is not a hardware issue. I would test the nv and the proprietary drivers. If they work, then go back and look at nouveau again. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> In the first or second mail with this topic, you wrote that you > installed, among other things, the kernel module from the nouveau site. > > There is no need to do this. > > The kernel side of the nouveau driver suite has been added to the > mainline kernel tree about a year ago and a month or so ago has been > moved out of staging. This means that there is no need to pull things > from the nouveau site for the kernel. You can just take any newer > kernel. Say, Linux-3.0 or any after that. > > You should also try using releases instead of git snapshots in > mid-development, at least to verify it works. > > Also, don't forget the Xorg driver for the server: > git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/ > > I haven't seen you state that you built and installed it and there is > no way X will start without it. Thanks for your input. All the items you mention were covered at some point in the discussion. Armin confirmed that all the software components associated with the nouveau driver were performing as expected - at least as far as he could tell from the logs. There didn't seem to be anything wrong with the installation.There seems to be something wrong with the way the nouveau driver communicates with my particular GPU. The card doesn't appear to recognize the signal(s) that are sent to it and without a signal it will simply cycle through red, green blue and white. The nouveau site says that drm.ko must be loaded before nouveau.ko so I was going to check that this happens in my case. regards jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
>On Wed, 18 Jul 2012 17:53:27 + >John Burrell wrote: > You're right, it makes no difference and of course setting acpi=off > means the nouveau module is not loaded and it falls back to using > vesa. > > I guess this will have to stay as one of those quirky things that > doesn't have an obvious solution. I expect a nvidia driver programmer > could solve it but I don't have access to one of those. In the first or second mail with this topic, you wrote that you installed, among other things, the kernel module from the nouveau site. There is no need to do this. The kernel side of the nouveau driver suite has been added to the mainline kernel tree about a year ago and a month or so ago has been moved out of staging. This means that there is no need to pull things from the nouveau site for the kernel. You can just take any newer kernel. Say, Linux-3.0 or any after that. You should also try using releases instead of git snapshots in mid-development, at least to verify it works. Also, don't forget the Xorg driver for the server: git://anongit.freedesktop.org/git/nouveau/xf86-video-nouveau/ I haven't seen you state that you built and installed it and there is no way X will start without it. -- Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Wed, 2012-07-18 at 20:24 +0200, Armin K. wrote: > On 07/18/2012 07:53 PM, John Burrell wrote: > > > > > >> Are CONFIG_DELL_LAPTOP and CONFIG_DELL_WMI set as Y or M in your kernel > >> config? > > > > CONFIG_DELL_WMI is set as a module. I don't see CONFIG_DELL_LAPTOP > > In 3.4 kernel, it is located under "x86 specific drivers" or whatever. > It is marked as "DELL Laptop Extras" I think. Second option with name > beginning with DELL before DELL WMI. It's help says that it handles > rfkill and brightness, so if you can get that one, maybe it could help. And just as a point of reference, necause I have nothing else of value to add to the actual topic at hand: When in 'make menuconfig' in the kernel source, you can type '/' to do a search and it will tell you where in the hierarchy any matching CONFIG_* elements are to be found. Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Wed, Jul 18, 2012 at 05:53:27PM +, John Burrell wrote: > > Thanks for your time and comments Armin and thanks to everyone who > contributed to this thread - it's much appreciated. > From your earlier post, I had the impression that the display went weird when you ran startx ? If that is true (maybe I've misunderstood) then the Xorg log might be useful. But the main problem with nvidia cards seems to be that they are very different from each other. You might not be able to reasolve this unless one of the nouveau devs has access to the same hardware. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/18/2012 07:53 PM, John Burrell wrote: > > >> Are CONFIG_DELL_LAPTOP and CONFIG_DELL_WMI set as Y or M in your kernel >> config? > > CONFIG_DELL_WMI is set as a module. I don't see CONFIG_DELL_LAPTOP In 3.4 kernel, it is located under "x86 specific drivers" or whatever. It is marked as "DELL Laptop Extras" I think. Second option with name beginning with DELL before DELL WMI. It's help says that it handles rfkill and brightness, so if you can get that one, maybe it could help. >> >> Anyways, you can try adding acpi_osi=Linux acpi_backlight=vendor to your >> kernel command line. I doubt it will change anything, but it's worth a >> try. Other than that, I'm out of ideas. > > You're right, it makes no difference and of course setting acpi=off means the > nouveau module is not loaded and it falls back to using vesa. > > I guess this will have to stay as one of those quirky things that doesn't > have an obvious solution. I expect a nvidia driver programmer could solve it > but I don't have access to one of those. > > Thanks for your time and comments Armin and thanks to everyone who > contributed to this thread - it's much appreciated. > > jb. > > -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> Are CONFIG_DELL_LAPTOP and CONFIG_DELL_WMI set as Y or M in your kernel > config? CONFIG_DELL_WMI is set as a module. I don't see CONFIG_DELL_LAPTOP > > Anyways, you can try adding acpi_osi=Linux acpi_backlight=vendor to your > kernel command line. I doubt it will change anything, but it's worth a > try. Other than that, I'm out of ideas. You're right, it makes no difference and of course setting acpi=off means the nouveau module is not loaded and it falls back to using vesa. I guess this will have to stay as one of those quirky things that doesn't have an obvious solution. I expect a nvidia driver programmer could solve it but I don't have access to one of those. Thanks for your time and comments Armin and thanks to everyone who contributed to this thread - it's much appreciated. jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/18/2012 05:08 PM, John Burrell wrote: > > Could you post your dmesg output (or /var/log/kern.log from last boot) after nouveau starts to misbehave? >>> >>> I think I'd have to email it to you because it's more that 50 KB. Is that >>> okay? >> >> Sure, no problem. Note that you can always compress the log. xz -9 can >> work very well. I only need log from last boot (or any other where issue >> occours). > > > I tared the kern.log file and attach it here. It came down from 123 KB to 17 > KB. > > > > I removed the blacklist file and booted the system. This is the resulting log > after > SysRq+s, u and then b as Ken suggested. > Hm ... You know, everything seems great. However, I didn't see any information about dell_laptop module. Just wmi. Are CONFIG_DELL_LAPTOP and CONFIG_DELL_WMI set as Y or M in your kernel config? Anyways, you can try adding acpi_osi=Linux acpi_backlight=vendor to your kernel command line. I doubt it will change anything, but it's worth a try. Other than that, I'm out of ideas. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> >> Could you post your dmesg output (or /var/log/kern.log from last boot) > >> after nouveau starts to misbehave? > > > > I think I'd have to email it to you because it's more that 50 KB. Is that > > okay? > > Sure, no problem. Note that you can always compress the log. xz -9 can > work very well. I only need log from last boot (or any other where issue > occours). I tared the kern.log file and attach it here. It came down from 123 KB to 17 KB. I removed the blacklist file and booted the system. This is the resulting log after SysRq+s, u and then b as Ken suggested. kern.log.tar.xz Description: application/xz -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 11:04:47PM +, John Burrell wrote: > > > > > > On Tue, Jul 17, 2012 at 09:24:50PM +, John Burrell wrote: > > > Any suggestions which keys sequences to try? The only one I've found to > > > work so far is > > > Alt+sysRQ+b which reboots the machine - not a lot of use really. > > > > > To have a better chance of saving the logs : > > Alt-SysRQ-s (sync), wait for a second or so > > Alt-SysRQ-u (umount), wait briefly > > Alt-SysRQ-b > > Thanks, I'll do that. Is that sequence going to add to dmesg? You say 'logs' > - which logs exactly? I believe that dmesg is never saved, and I think I set the loglevel to remove some of the debug noise ( a quick look at my server scripts for 7.1 failed to confirm that - I'm still in the server branch of my buildscripts until I fix all the issues :), so I can't point to exactly where/how it is now set, In the context of *saving* data from the problematic boot, all of the logs (and, indeed, any other files being written at hte time). To try to solve the problem, whichever make sense - I guess that's just the system log, and (after running 'startx') the Xorg log. If they get saved, you can always take a look in all the logs, just in case anything odd appears. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/18/2012 01:02 AM, John Burrell wrote: > > > >>> So should I do startx and then try pressing different keys while it's >>> cycling through the colors? >>> Any suggestions which keys sequences to try? The only one I've found to >>> work so far is >>> Alt+sysRQ+b which reboots the machine - not a lot of use really. >>> >>> jb. >>> >>> >> >> Heh, everything that seems to be related to your problem online has been >> solved by installing nvidia proprietary drivers. > > nah, that defeats the point of this exercise - to get a non-proprietary > driver to work! >> >> Could you post your dmesg output (or /var/log/kern.log from last boot) >> after nouveau starts to misbehave? > > I think I'd have to email it to you because it's more that 50 KB. Is that > okay? > > Sure, no problem. Note that you can always compress the log. xz -9 can work very well. I only need log from last boot (or any other where issue occours). -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> > On Tue, Jul 17, 2012 at 09:24:50PM +, John Burrell wrote: > > Any suggestions which keys sequences to try? The only one I've found to > > work so far is > > Alt+sysRQ+b which reboots the machine - not a lot of use really. > > > To have a better chance of saving the logs : > Alt-SysRQ-s (sync), wait for a second or so > Alt-SysRQ-u (umount), wait briefly > Alt-SysRQ-b Thanks, I'll do that. Is that sequence going to add to dmesg? You say 'logs' - which logs exactly? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> > So should I do startx and then try pressing different keys while it's > > cycling through the colors? > > Any suggestions which keys sequences to try? The only one I've found to > > work so far is > > Alt+sysRQ+b which reboots the machine - not a lot of use really. > > > > jb. > > > > > > Heh, everything that seems to be related to your problem online has been > solved by installing nvidia proprietary drivers. nah, that defeats the point of this exercise - to get a non-proprietary driver to work! > > Could you post your dmesg output (or /var/log/kern.log from last boot) > after nouveau starts to misbehave? I think I'd have to email it to you because it's more that 50 KB. Is that okay? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 09:24:50PM +, John Burrell wrote: > Any suggestions which keys sequences to try? The only one I've found to work > so far is > Alt+sysRQ+b which reboots the machine - not a lot of use really. > To have a better chance of saving the logs : Alt-SysRQ-s (sync), wait for a second or so Alt-SysRQ-u (umount), wait briefly Alt-SysRQ-b ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 11:24 PM, John Burrell wrote: > > > >>> okay lsmod.log from Ubuntu attached. >> >> Hm. I've never seen most of the stuff you have there. But from that, I >> see the laptop is Dell. Have you selected laptop extras like WMI and >> such in your kernel? Also, it would be nice for you to build udev from >> BLFS in order to get keymap feature, then you can try messing with >> multimedia keys (you still need wmi as kernel module or built in) and >> try graphics brightness stuff and so on. > > When I boot into LFS, module wmi is loaded. It's the only one that is. > > I've built udev from BLFS already. > > So should I do startx and then try pressing different keys while it's cycling > through the colors? > Any suggestions which keys sequences to try? The only one I've found to work > so far is > Alt+sysRQ+b which reboots the machine - not a lot of use really. > > jb. > > Heh, everything that seems to be related to your problem online has been solved by installing nvidia proprietary drivers. Could you post your dmesg output (or /var/log/kern.log from last boot) after nouveau starts to misbehave? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
>On Tue, 17 Jul 2012 21:47:35 +0200 >"Armin K." wrote: > Yay, you missed the world. This is LFS, it does not use initrd ... > > And blacklisting nouveau does not disable KMS, it just disables the > driver from loading automatically by udev. That way you can boot > using VESA. Nouveau gets loaded when: Xorg Server starts or you > modprobe it manually. In either way, KMS will be enabled. > > Have you ever tried using nouveau with Ubuntu? Did it have same > behaviour? I think VESA is coliding with nouveau. Try not using it (use only the text console). The other possible problem is that you are using the newest (AKA still explosive) code from git for all three components. I have had amirable success with libdrm-2.4.26, mesa-7.11 and linux-3.4.4. Neither are bleeding edge, and they work together. Try rolling back to _releases_ of the packages and you may have success. "Success" defined as "IT WORKS AND DOESN'T CRASH!!!" and not as "I can play Mass Effect 3 with all settings maxed out and the game looks as good as on Windows!", although God may have mercy on thee. -- Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> > okay lsmod.log from Ubuntu attached. > > Hm. I've never seen most of the stuff you have there. But from that, I > see the laptop is Dell. Have you selected laptop extras like WMI and > such in your kernel? Also, it would be nice for you to build udev from > BLFS in order to get keymap feature, then you can try messing with > multimedia keys (you still need wmi as kernel module or built in) and > try graphics brightness stuff and so on. When I boot into LFS, module wmi is loaded. It's the only one that is. I've built udev from BLFS already. So should I do startx and then try pressing different keys while it's cycling through the colors? Any suggestions which keys sequences to try? The only one I've found to work so far is Alt+sysRQ+b which reboots the machine - not a lot of use really. jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 11:04 PM, John Burrell wrote: > > >> you could post lsmod output from Ubuntu so someone could guide you to >> check if you have necesary kernel stuff on your LFS kernel. Laptops have >> been always complicated when it comes to Linux (well, newer ones). > > okay lsmod.log from Ubuntu attached. Hm. I've never seen most of the stuff you have there. But from that, I see the laptop is Dell. Have you selected laptop extras like WMI and such in your kernel? Also, it would be nice for you to build udev from BLFS in order to get keymap feature, then you can try messing with multimedia keys (you still need wmi as kernel module or built in) and try graphics brightness stuff and so on. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> you could post lsmod output from Ubuntu so someone could guide you to > check if you have necesary kernel stuff on your LFS kernel. Laptops have > been always complicated when it comes to Linux (well, newer ones). okay lsmod.log from Ubuntu attached. Module Size Used by nls_iso8859_1 12617 1 nls_cp437 12751 1 vfat 17308 1 fat55605 1 vfat vesafb 13516 1 rfcomm 38139 0 parport_pc 32114 0 ppdev 12849 0 bnep 17830 2 bluetooth 158438 10 rfcomm,bnep binfmt_misc17292 1 arc4 12473 2 joydev 17393 0 snd_hda_codec_idt 60251 1 dell_wmi 12601 0 sparse_keymap 13658 1 dell_wmi snd_hda_intel 32765 2 snd_hda_codec 109562 2 snd_hda_codec_idt,snd_hda_intel snd_hwdep 13276 1 snd_hda_codec nvidia 10962290 43 snd_pcm80845 2 snd_hda_intel,snd_hda_codec dell_laptop17767 0 dcdbas 14098 1 dell_laptop snd_seq_midi 13132 0 snd_rawmidi25424 1 snd_seq_midi uvcvideo 67203 0 videodev 86588 1 uvcvideo r592 17808 0 snd_seq_midi_event 14475 1 snd_seq_midi psmouse72919 0 option 25580 0 usb_wwan 19779 1 option r852 17901 0 sm_common 16737 1 r852 nand 49667 2 r852,sm_common nand_ids8547 1 nand serio_raw 13027 0 video 19068 0 memstick 15857 1 r592 mtd35584 2 sm_common,nand usbserial 37173 2 option,usb_wwan nand_bch 13003 1 nand bch21757 1 nand_bch nand_ecc 13070 1 nand iwl4965 117368 0 snd_seq51567 2 snd_seq_midi,snd_seq_midi_event mac_hid13077 0 iwl_legacy 71134 1 iwl4965 mac80211 436455 2 iwl4965,iwl_legacy snd_timer 28931 2 snd_pcm,snd_seq snd_seq_device 14172 3 snd_seq_midi,snd_rawmidi,snd_seq usbhid 41906 0 hid77367 1 usbhid wmi18744 1 dell_wmi cfg80211 178679 3 iwl4965,iwl_legacy,mac80211 snd62064 13 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 14635 1 snd snd_page_alloc 14108 2 snd_hda_intel,snd_pcm lp 17455 0 parport40930 3 parport_pc,ppdev,lp usb_storage39646 1 sdhci_pci 18324 0 sdhci 28241 1 sdhci_pci firewire_ohci 40172 0 firewire_core 56906 1 firewire_ohci crc_itu_t 12627 1 firewire_core tg3 141369 0 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 10:45 PM, John Burrell wrote: > > >> >> Have you ever tried using nouveau with Ubuntu? Did it have same behaviour? > > No, I've not messed around with Ubuntu at all. I don't think I have the > expertise to start playing around with it. I'd have to be held by the hand to > know how to use nouveau instead of nvidia. > > I could blacklist nvidia and add a 20-nouveau.conf to > /usr/share/X11/xorg.conf.d but I have no idea if that is what is required. > > I'm not keen to break the host with LFS in a bit of a precarious state - > uncharted waters for me. I'm a geophysicist, not a computer expert! > > jb. > you could post lsmod output from Ubuntu so someone could guide you to check if you have necesary kernel stuff on your LFS kernel. Laptops have been always complicated when it comes to Linux (well, newer ones). -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> > Have you ever tried using nouveau with Ubuntu? Did it have same behaviour? No, I've not messed around with Ubuntu at all. I don't think I have the expertise to start playing around with it. I'd have to be held by the hand to know how to use nouveau instead of nvidia. I could blacklist nvidia and add a 20-nouveau.conf to /usr/share/X11/xorg.conf.d but I have no idea if that is what is required. I'm not keen to break the host with LFS in a bit of a precarious state - uncharted waters for me. I'm a geophysicist, not a computer expert! jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 10:24 PM, Maginot Junior wrote: > On Tue, Jul 17, 2012 at 5:12 PM, Bruce Dubbs wrote: >> Maginot Junior wrote: >> >>> You need the video drivers to have KMS working, you can't simple use >>> KMS without nouveau (nvidia boards). Actually, any nvidia proprietary >>> driver can't run with nouveau. >> >> That's true. >> >>> You need the initrd updated to have the KMS/DRM modules from kernel >>> since the early stages, and they should be in sync with the build in >>> the local disk so the initrd can handle to the local disk kernel and >>> Xorg can take advantage of this infrastructure. >> >> Try to read and understand LFS before posting things like this. LFS >> does *not* use initrd by default, even though a user may do that for >> himself. We also generally have users minimize kernel modules. >> > > I'm not saying anything about LFS using or not initrd. I'm just trying > to help with the KMS problem issued in the list, which will continue > to exist without an initrd afaik. Not true. KMS has nothing to do with initrd. Driver itself handles that. If you probe driver in initrd, it will get activated there. If you probe it with udev, it will get activated a bit later. If you modprobe it manually, it will get activated. > LFS doesn't have an initrd, but you can always implement it whetever > you want in your own LFS distro, like I did with mine. Mine have > Initrd, KMS, plymouth and dracut, even those not being in LFS. > but that was just my two cents, I'm out of this thread. > > > > regards > > -- > Maginot Jr. > -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 5:12 PM, Bruce Dubbs wrote: > Maginot Junior wrote: > >> You need the video drivers to have KMS working, you can't simple use >> KMS without nouveau (nvidia boards). Actually, any nvidia proprietary >> driver can't run with nouveau. > > That's true. > >> You need the initrd updated to have the KMS/DRM modules from kernel >> since the early stages, and they should be in sync with the build in >> the local disk so the initrd can handle to the local disk kernel and >> Xorg can take advantage of this infrastructure. > > Try to read and understand LFS before posting things like this. LFS > does *not* use initrd by default, even though a user may do that for > himself. We also generally have users minimize kernel modules. > I'm not saying anything about LFS using or not initrd. I'm just trying to help with the KMS problem issued in the list, which will continue to exist without an initrd afaik. LFS doesn't have an initrd, but you can always implement it whetever you want in your own LFS distro, like I did with mine. Mine have Initrd, KMS, plymouth and dracut, even those not being in LFS. but that was just my two cents, I'm out of this thread. regards -- Maginot Jr. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
Maginot Junior wrote: > You need the video drivers to have KMS working, you can't simple use > KMS without nouveau (nvidia boards). Actually, any nvidia proprietary > driver can't run with nouveau. That's true. > You need the initrd updated to have the KMS/DRM modules from kernel > since the early stages, and they should be in sync with the build in > the local disk so the initrd can handle to the local disk kernel and > Xorg can take advantage of this infrastructure. Try to read and understand LFS before posting things like this. LFS does *not* use initrd by default, even though a user may do that for himself. We also generally have users minimize kernel modules. Xorg modules are different from kernel modules. There is some kernel support needed for the nouveau drivers, but not for the nv driver. Drivers for Xorg can be specified in /etc/X11/xorg.conf, but whether that's needed depends on the needs of the user. Most of the time defaults are OK. One thing that can be tried is to set the driver in xorg.conf: Section "Device" Identifier "Videocard0" Driver "nv" EndSection -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 09:56 PM, Maginot Junior wrote: > On Tue, Jul 17, 2012 at 4:47 PM, Armin K. wrote: >> On 07/17/2012 09:42 PM, Maginot Junior wrote: >>> On Tue, Jul 17, 2012 at 4:41 PM, John Burrell >>> wrote: >>>> >>>> >>>> >>>> >>>>> From: maginot.jun...@gmail.com >>>>> Date: Tue, 17 Jul 2012 16:00:56 -0300 >>>>> To: blfs-support@linuxfromscratch.org >>>>> Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel >>>>> module loaded >>>>> >>>>> did you update your init ram disk? >>>> >>>> I didn't set aside a partition for a ramdisk so there is no ramdisk >>>> mounted. >>>> >>>> jb. >>>> >>>> -- >>>> http://linuxfromscratch.org/mailman/listinfo/blfs-support >>>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>>> Unsubscribe: See the above information page >>> >>> I don't think you can use KMS without a initrd (this is not a >>> partition, but just a initrd file, UBuntu uses one and you can easily >>> edit it) >>> check the boot option to see what inirt it's using >>> >> >> Yay, you missed the world. This is LFS, it does not use initrd ... >> >> And blacklisting nouveau does not disable KMS, it just disables the >> driver from loading automatically by udev. That way you can boot using >> VESA. Nouveau gets loaded when: Xorg Server starts or you modprobe it >> manually. In either way, KMS will be enabled. >> >> Have you ever tried using nouveau with Ubuntu? Did it have same behaviour? >> -- >> http://linuxfromscratch.org/mailman/listinfo/blfs-support >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page > > if you haven't saw this yet it can be helpful > http://nouveau.freedesktop.org/wiki/KernelModeSetting > > > > regards > -- > Maginot Jr. > Pay attention: And blacklisting nouveau does not disable KMS, it just disables the river from loading automatically by udev. That way you can boot using VESA. Nouveau gets loaded when: Xorg Server starts or you modprobe it manually. In either way, KMS will be enabled. And as you can see in his Xorg.0.log file, everything is fine. If KMS was disabled, it would print an error. I suspect it's something with ACPI stuff or the way laptop backlight is controlled. Laptops are PITA when you need to get them to work. I had too much trouble with mine. But, on my side, there was nothing on the screen. Just poor text. I solved it (after hours of searching) by just pressing "Increase brightness" button on my keyboard. (DOH!). It didnt, however, happened with driver blacklisted or with KMS disabled. Also, in my case, it was intel driver, not nouveau. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 4:47 PM, Armin K. wrote: > On 07/17/2012 09:42 PM, Maginot Junior wrote: >> On Tue, Jul 17, 2012 at 4:41 PM, John Burrell >> wrote: >>> >>> >>> >>> >>>> From: maginot.jun...@gmail.com >>>> Date: Tue, 17 Jul 2012 16:00:56 -0300 >>>> To: blfs-support@linuxfromscratch.org >>>> Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel >>>> module loaded >>>> >>>> did you update your init ram disk? >>> >>> I didn't set aside a partition for a ramdisk so there is no ramdisk mounted. >>> >>> jb. >>> >>> -- >>> http://linuxfromscratch.org/mailman/listinfo/blfs-support >>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>> Unsubscribe: See the above information page >> >> I don't think you can use KMS without a initrd (this is not a >> partition, but just a initrd file, UBuntu uses one and you can easily >> edit it) >> check the boot option to see what inirt it's using >> > > Yay, you missed the world. This is LFS, it does not use initrd ... > > And blacklisting nouveau does not disable KMS, it just disables the > driver from loading automatically by udev. That way you can boot using > VESA. Nouveau gets loaded when: Xorg Server starts or you modprobe it > manually. In either way, KMS will be enabled. > > Have you ever tried using nouveau with Ubuntu? Did it have same behaviour? > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page if you haven't saw this yet it can be helpful http://nouveau.freedesktop.org/wiki/KernelModeSetting regards -- Maginot Jr. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 09:42 PM, Maginot Junior wrote: > On Tue, Jul 17, 2012 at 4:41 PM, John Burrell > wrote: >> >> >> >> >>> From: maginot.jun...@gmail.com >>> Date: Tue, 17 Jul 2012 16:00:56 -0300 >>> To: blfs-support@linuxfromscratch.org >>> Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel >>> module loaded >>> >>> did you update your init ram disk? >> >> I didn't set aside a partition for a ramdisk so there is no ramdisk mounted. >> >> jb. >> >> -- >> http://linuxfromscratch.org/mailman/listinfo/blfs-support >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page > > I don't think you can use KMS without a initrd (this is not a > partition, but just a initrd file, UBuntu uses one and you can easily > edit it) > check the boot option to see what inirt it's using > Yay, you missed the world. This is LFS, it does not use initrd ... And blacklisting nouveau does not disable KMS, it just disables the driver from loading automatically by udev. That way you can boot using VESA. Nouveau gets loaded when: Xorg Server starts or you modprobe it manually. In either way, KMS will be enabled. Have you ever tried using nouveau with Ubuntu? Did it have same behaviour? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 4:41 PM, John Burrell wrote: > > > > >> From: maginot.jun...@gmail.com >> Date: Tue, 17 Jul 2012 16:00:56 -0300 >> To: blfs-support@linuxfromscratch.org >> Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel >> module loaded >> >> did you update your init ram disk? > > I didn't set aside a partition for a ramdisk so there is no ramdisk mounted. > > jb. > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page I don't think you can use KMS without a initrd (this is not a partition, but just a initrd file, UBuntu uses one and you can easily edit it) check the boot option to see what inirt it's using -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> From: maginot.jun...@gmail.com > Date: Tue, 17 Jul 2012 16:00:56 -0300 > To: blfs-support@linuxfromscratch.org > Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel > module loaded > > did you update your init ram disk? I didn't set aside a partition for a ramdisk so there is no ramdisk mounted. jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 4:35 PM, John Burrell wrote: > > > > >> Date: Tue, 17 Jul 2012 21:13:46 +0200 >> From: kre...@email.com >> To: blfs-support@linuxfromscratch.org >> Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel >> module loaded >> >> On 07/17/2012 08:44 PM, John Burrell wrote: >> > >> > I installed the latest git versions of libdrm, mesalib and the kernel >> > modules from the nouveau wiki site. >> > >> > I blacklisted the nouveau module so I could boot the machine. KMS is >> > therefore enabled. >> > >> > When I do modprobe nouveau or startx I still get the cycling of the >> > colored screens. >> > >> > startx now gives me a Xorg.0.log which I attach here. >> > >> > I wonder if someone (Armin?) could take a look at it and see if there's >> > anything untoward about it. >> > >> > Thanks >> > >> > jb. >> > >> >> I don't see anything wrong. In fact, everything looks GREAT. I see you >> used Ubuntu to build LFS, so tell me does it use nouveau too and does it >> experience the same problem? I forgot your configuration. Is that a >> laptop or what? > > No, Ubuntu uses a proprietary Nvidia driver. > > [18.291] (II) Module glx: vendor="NVIDIA Corporation" > [18.291] compiled for 4.0.2, module version = 1.0.0 > [18.291] Module class: X.Org Server Extension > [18.291] (II) NVIDIA GLX Module 295.40 Thu Apr 5 21:49:54 PDT 2012 > > > Yes it's a laptop with a GeForce 8700M GT - about 4 or 5 yrs old. > > If blacklisting nouveau disables KMS, how do I enable it before loading > nouveau? I guess I can't. > > jb. > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page You need the video drivers to have KMS working, you can't simple use KMS without nouveau (nvidia boards). Actually, any nvidia proprietary driver can't run with nouveau. You need the initrd updated to have the KMS/DRM modules from kernel since the early stages, and they should be in sync with the build in the local disk so the initrd can handle to the local disk kernel and Xorg can take advantage of this infrastructure. -- Maginot Jr -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
> Date: Tue, 17 Jul 2012 21:13:46 +0200 > From: kre...@email.com > To: blfs-support@linuxfromscratch.org > Subject: Re: [blfs-support] more on trying to get the drm nouveau kernel > module loaded > > On 07/17/2012 08:44 PM, John Burrell wrote: > > > > I installed the latest git versions of libdrm, mesalib and the kernel > > modules from the nouveau wiki site. > > > > I blacklisted the nouveau module so I could boot the machine. KMS is > > therefore enabled. > > > > When I do modprobe nouveau or startx I still get the cycling of the colored > > screens. > > > > startx now gives me a Xorg.0.log which I attach here. > > > > I wonder if someone (Armin?) could take a look at it and see if there's > > anything untoward about it. > > > > Thanks > > > > jb. > > > > I don't see anything wrong. In fact, everything looks GREAT. I see you > used Ubuntu to build LFS, so tell me does it use nouveau too and does it > experience the same problem? I forgot your configuration. Is that a > laptop or what? No, Ubuntu uses a proprietary Nvidia driver. [ 18.291] (II) Module glx: vendor="NVIDIA Corporation" [ 18.291] compiled for 4.0.2, module version = 1.0.0 [ 18.291] Module class: X.Org Server Extension [ 18.291] (II) NVIDIA GLX Module 295.40 Thu Apr 5 21:49:54 PDT 2012 Yes it's a laptop with a GeForce 8700M GT - about 4 or 5 yrs old. If blacklisting nouveau disables KMS, how do I enable it before loading nouveau? I guess I can't. jb. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On Tue, Jul 17, 2012 at 4:13 PM, Armin K. wrote: > On 07/17/2012 08:44 PM, John Burrell wrote: >> >> I installed the latest git versions of libdrm, mesalib and the kernel >> modules from the nouveau wiki site. >> >> I blacklisted the nouveau module so I could boot the machine. KMS is >> therefore enabled. >> >> When I do modprobe nouveau or startx I still get the cycling of the colored >> screens. >> >> startx now gives me a Xorg.0.log which I attach here. >> >> I wonder if someone (Armin?) could take a look at it and see if there's >> anything untoward about it. >> >> Thanks >> >> jb. >> > > I don't see anything wrong. In fact, everything looks GREAT. I see you > used Ubuntu to build LFS, so tell me does it use nouveau too and does it > experience the same problem? I forgot your configuration. Is that a > laptop or what? > > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page Well, since its blacklisting nouveau I don't think KMS is really running, and he said - "I blacklisted the nouveau module so I could boot the machine. KMS is therefore enabled." seeing KMS in lsmod is not necessarily an indication the KMS is running. Blacklisting nouveau is like starting with the nomodeset kernel option, but this information is just a guess on what I remember, I may be wrong because when I dont want KMS I use nomodeset instead... -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
On 07/17/2012 08:44 PM, John Burrell wrote: > > I installed the latest git versions of libdrm, mesalib and the kernel modules > from the nouveau wiki site. > > I blacklisted the nouveau module so I could boot the machine. KMS is > therefore enabled. > > When I do modprobe nouveau or startx I still get the cycling of the colored > screens. > > startx now gives me a Xorg.0.log which I attach here. > > I wonder if someone (Armin?) could take a look at it and see if there's > anything untoward about it. > > Thanks > > jb. > I don't see anything wrong. In fact, everything looks GREAT. I see you used Ubuntu to build LFS, so tell me does it use nouveau too and does it experience the same problem? I forgot your configuration. Is that a laptop or what? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] more on trying to get the drm nouveau kernel module loaded
did you update your init ram disk? it will be necessary since kms runs from the very early stages of the boot process... -- Maginot Júnior LPIC 3 - CCNA - CLA On Tue, Jul 17, 2012 at 3:44 PM, John Burrell wrote: > > I installed the latest git versions of libdrm, mesalib and the kernel modules > from the nouveau wiki site. > > I blacklisted the nouveau module so I could boot the machine. KMS is > therefore enabled. > > When I do modprobe nouveau or startx I still get the cycling of the colored > screens. > > startx now gives me a Xorg.0.log which I attach here. > > I wonder if someone (Armin?) could take a look at it and see if there's > anything untoward about it. > > Thanks > > jb. > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
