LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 06-11-2010, 06:11 PM   #16
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201

You seem to have gotten caught up in the libata switchover which is what's going on with the reordering of your drives? The fact that it only happens with the generic kernel seems odd, but I would think that http://slackware.mirrors.tds.net/pub..._AND_HINTS.TXT specifically the "LIBATA SWITHCOVER" section would give you an answer. I'm not familiar with raid, but if you can use uuid's for the raid drive you can take the sd[A,B,C] bit out of the equation.
 
Old 06-11-2010, 06:48 PM   #17
ahmadj
Member
 
Registered: Jun 2010
Distribution: Slackware64_13.37 \ Slackware_13.1 \ ARMedslack_13.37
Posts: 80

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by damgar View Post
You seem to have gotten caught up in the libata switchover which is what's going on with the reordering of your drives? The fact that it only happens with the generic kernel seems odd, but I would think that http://slackware.mirrors.tds.net/pub..._AND_HINTS.TXT specifically the "LIBATA SWITHCOVER" section would give you an answer. I'm not familiar with raid, but if you can use uuid's for the raid drive you can take the sd[A,B,C] bit out of the equation.
I think it's to do with the order the drivers are loaded in. In huge, scsi drivers are compiled in and load before ata drivers, meaning the raid controller gets the first device nodes. In generic, only ata drivers are compiled in (and therefore load before the raid drivers), so they get the first call on sda.
 
Old 06-12-2010, 10:35 AM   #18
ahmadj
Member
 
Registered: Jun 2010
Distribution: Slackware64_13.37 \ Slackware_13.1 \ ARMedslack_13.37
Posts: 80

Original Poster
Rep: Reputation: 16
@ponce -

turns out it doesn't work so well after all. It was working last night, not working this morning. After a few cold reboots, it worked again. Weird.

What I've ended up doing is setting vga=ask in lilo.conf instead of the actual vesa mode, and selecting from the menu on bootup. This seems to work consistently.

EDIT: No, it still doesn't work. I can only get framebuffer after a warm reboot. All other times it fails and locks up the PC. Something to do with KMS perhaps? ie. BIOS not configuring the card correctly for bootup, but KMS doing something (on a successful boot) which makes it work on the reboot? A quick browse of dmesg (from a bootup where framebuffer worked) showed me that the new (since 2.6.32) vgaarb (vga arbiter) comes in really early in the boot process. Could that have something to do with it?

I'm clutching at straws here to be honest, no idea what's really going on. Seems like it was a bad decision to 'upgrade' to 13.1, though...

Last edited by ahmadj; 06-12-2010 at 11:43 AM.
 
Old 06-12-2010, 12:02 PM   #19
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
i confirm you i tried and (as I remember the last time I tried some kernels ago), nvidia drivers and vesa modes don't play well together, as I wrote early.

as vesa modes aren't vital for me (3d stuff instead it is), it's better if I move on on other thingies: tnx for the hints, btw

but I don't think in my case it's related to kms/13.1 as it always happened to me, like I wrote before.

Last edited by ponce; 06-12-2010 at 12:07 PM.
 
  


Reply

Tags
framebuffer, nvidia


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Incorrect screen resolution with slackware64 13.1 and nvidia 195.36.15 driver Phorize Slackware 14 05-28-2010 05:58 AM
blank screen at boot when using lilo FB wufo Slackware 5 11-20-2007 11:03 PM
LCD screen is blank after lilo on VGN-S580P dasoberdick Slackware 10 06-16-2007 01:03 PM
yet again need help,screen goes blank in tv out nvidia zeltak Linux - Software 1 02-13-2006 09:58 AM
Kernel recompiling woes (blank screen) jrdioko Linux - Software 2 08-14-2005 08:15 PM


All times are GMT -5. The time now is 12:15 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration