SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
#dmesg
[ 1.429388] md: If you don't use raid, use raid=noautodetect
[ 1.472714] EXT3-fs (sda6): error: couldn't mount because of unsupported optional features (240)
[ 1.486176] EXT2-fs (sda6): error: couldn't mount because of unsupported optional features (240)
[ 2.828592] ACPI: resource 0000:00:1f.3 [io 0x0400-0x041f] conflicts with ACPI region SMRG [io 0x400-0x40f]
[ 2.831307] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.098607] nouveau 0000:04:00.0: setting latency timer to 64
[ 3.100576] [drm] nouveau 0000:04:00.0: Detected an NV40 generation card (0x046100a3)
[ 3.103466] checking generic (d0000000 8000000) vs hw (d0000000 10000000)
[ 3.103468] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
[ 3.106487] Console: switching to colour dummy device 80x25
[ 3.395751] [drm] nouveau 0000:04:00.0: allocated 1600x1200 fb: 0x49000, bo ffff88007a55f400
[ 3.395817] fbcon: nouveaufb (fb0) is primary device
[ 3.406337] [drm] nouveau 0000:04:00.0: Setting dpms mode 0 on vga encoder (output 0)
[ 3.406340] [drm] nouveau 0000:04:00.0: Output VGA-1 is running on CRTC 0 using output A
[ 3.406346] Console: switching to colour frame buffer device 200x75
[ 3.410156] fb0: nouveaufb frame buffer device
[ 3.410172] drm: registered panic notifier
[ 3.410190] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0
Have looked at some ARCH guides but still need help with: commands to change raid search during boot to raid=noautodetect & unload,load or pass options to kernel modules.
Will someone please explain the ACPI region SMRG driver conflict. Which is the native driver, the asus_atk0110? I turned off all Power Management on Xfce since its a desktop and screen saver stopped working since I tried to just use Blank Screen Saver Option. Tried using some tutorials to write monitor.conf, Device.conf, Screen.conf, and Layout.conf but my syntax was bad so they wouldn't parse? Are there nouveau options I need to pass to it and how would I do so? Why don't I have FBDEV? Been struggling for a week with this problem. No clue how this problem started. Your help & time is appreciated. Thank you
I rebooted about 4, 5 times blind, black screen but i just give it time to boot, login blind as root & then do:shutdown -h now and it shuts down, then I reboot till i get a screen. You say there is nothing wrong with my dmesg out but its says I have no frame buffer, there is conflicting fb hw usage nouveaufb vs VESA VGA, issues with APCI, and I would like to know how to keep boot from searching for raid setup that I am not using. Thank you for looking at this.
Are you saying that sometimes it works and most of the time it doesn't?
The conflict between nouveau and the fb is normal and is resolved by unloading the fb driver as nouveau is a closer match than a generic driver, this is what your seeing there.
The raid device is not auto-detecting anything and is thus not doing anything, you don't need to stop it doing this it wont hurt anything.
The ACPI error message is common and is not a problem, if it was I would have the same problem you do but I don't have anything wrong.
Now kernel command lines, you can do testing from the lilo prompt (kernel-image-name is the name of the kernel image, you will see this on the initial lilo screen or you can hit TAB to get possible choices)
This might help with the video problems if your card and nouveau do not play nicely together
kernel-image-name video=normal vga=normal
you can also add the :-
raid=noautodetect
if you really can't stand those messages
Thank you wildwizard, I was trying to follow this guide on Kernel Modules: https://wiki.archlinux.org/index.php...Fmodprobe.d.2F
Your instructions helped stop the search for raid setup, which I'm happy about and eliminated monitor and video card turning my attention to the cable connection between them. Will get a dvi & vga cable then post back.
Thank you wildwizard, I was trying to follow this guide on Kernel Modules: https://wiki.archlinux.org/index.php...Fmodprobe.d.2F
Your instructions helped stop the search for raid setup, which I'm happy about and eliminated monitor and video card turning my attention to the cable connection between them. Will get a dvi & vga cable then post back.
Was hoping for a bad cable but it's working connected to the 32" screen TV now, only other monitor I could think of. lol Great image! Now I'm wondering what I need a monitor for if I can use the TV? Awesome! Wonder how many people are using TVs instead of computer monitors?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.