LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices

Reply
 
Search this Thread
Old 08-23-2014, 03:39 AM   #1
sleetdrop
LQ Newbie
 
Registered: Mar 2005
Posts: 16

Rep: Reputation: 0
Slackware ARM 14.1 on RaspberryPi xorgsetup failed


It just failed to create /etc/X11/xorg.conf

The attachment is /var/log/Xorg.0.log
It did not load driver fbdev, which is said to be driver for rpi

But I have installed xf86-video-fbdev-0.4.4-arm-1
and /usr/lib/xorg/modules/drivers/fbdev_drv.so exists tool
Attached Files
File Type: log Xorg.0.log (17.5 KB, 11 views)
 
Old 08-23-2014, 10:54 AM   #2
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 202

Rep: Reputation: 9
I don't have 14.1 RTR on my PI but I've X working right on 14.0 on the PI ... here's some stuff from my Xorg.0.log:
Code:
[   310.164] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708.boardrev=0xe bcm2708.serial=0x86dcc745 smsc95xx.macaddr=B8:27:EB:DC:C7:45 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ro
[   310.353] (II) Loading extension DRI2
[   310.353] (==) Matched fbdev as autoconfigured driver 0
[   310.353] (==) Assigned the driver to the xf86ConfigLayout
[   310.353] (II) LoadModule: "fbdev"
[   310.354] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   310.358] (II) Module fbdev: vendor="X.Org Foundation"
[   310.358]    compiled for 1.12.3, module version = 0.4.3
[   310.358]    Module class: X.Org Video Driver
[   310.358]    ABI class: X.Org Video Driver, version 12.0
[   310.358] (II) FBDEV: driver for framebuffer: fbdev
[   310.359] (--) using VT number 7

[   310.385] (WW) Falling back to old probe method for fbdev
[   310.386] (II) Loading sub module "fbdevhw"
[   310.386] (II) LoadModule: "fbdevhw"
[   310.388] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   310.390] (II) Module fbdevhw: vendor="X.Org Foundation"
[   310.391]    compiled for 1.12.4, module version = 0.0.2
[   310.391]    ABI class: X.Org Video Driver, version 12.1
And on 14.0 xorgsetup seems to run fine ... Could it be that your missing some required package ?
I wanted to give you some better help by getting a miniroot 14.1 on a spare SD and working quickly upto GUI ... but I hit some other issues that slowed me down (maybe Stuart can add the paskages in next miniroot release):
libtiff (making links not functional)
mpfr

Now I've to take the kids to the park ... but I'll have a go later.

Last edited by louigi600; 08-24-2014 at 10:58 AM.
 
Old 08-24-2014, 03:11 PM   #3
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 202

Rep: Reputation: 9
I added to the miniroot 14.1 the whole package series "l, x" and added a few packages here and there to get X working (fluxbox, utmpter, nettle, libtiff, mpfr). Linked xinitrc.fluxbox to xinitrc and fired up startx without even configuring it.
I then ran xorgsetup just to make sure it was working and for me it ran OK.

I had a look at the difference from your bust Xorg lo9g and my working one. This is the first thing that struck me:
In mine
Code:
[  5744.121] X Protocol Version 11, Revision 0
[  5744.128] Build Operating System: Slackware 14.1 Slackware Linux Project
[  5744.134] Current Operating System: Linux slackware 3.10.29 #1 PREEMPT Thu Fe
b 13 22:01:13 GMT 2014 armv6l
In yours
Code:
[   529.313] X Protocol Version 11, Revision 0
[   529.314] Build Operating System: Slackware 14.1 Slackware Linux Project
[   529.316] Current Operating System: Linux armslack 3.12.26+ #704 PREEMPT Wed 
Aug 20 22:35:11 BST 2014 armv6l
Could it be that FB support in yiur kernel has something wrong ?
Code:
# zgrep  _FB /proc/config.gz  | grep -v "^#"
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_BCM2708=y
#
In any case here's mu whole Xorg log:
Attached Files
File Type: log Xorg.0.log (14.7 KB, 2 views)
 
Old 08-24-2014, 09:26 PM   #4
sleetdrop
LQ Newbie
 
Registered: Mar 2005
Posts: 16

Original Poster
Rep: Reputation: 0
I tried your command, and I got the same output.
Code:
sleetdrop@armslack:~$ zgrep  _FB /proc/config.gz  | grep -v "^#"
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_BCM2708=y
After first installation, I upgraded the kernel via rpi-update as described in the following guide.
http://rpi.fatdog.eu/index.php?p=rpiupdate
 
Old 08-25-2014, 01:57 AM   #5
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 202

Rep: Reputation: 9
That was just grepping really obvious stuff from the kernel configuration ... more may be needed but if you followed fatdog's howto you should be ok and the problem is likely to be somewhere else.

In the section where framebuffer driver is loaded our Xorg.0.log look much different.
Check that you have these packages installed on your system:
xorg-server
xf86-video-modesetting
xf86-video-fbdev
xf86-input-evdev

If they are installed then maybe there is something else preventing X from loading correctly fbdev ... possibly library dependencies.
If that's the case, and you have space in the SD card you can fix it fast by running "slackpkg install l"

Last edited by louigi600; 08-25-2014 at 02:15 AM.
 
Old 08-25-2014, 10:08 AM   #6
sleetdrop
LQ Newbie
 
Registered: Mar 2005
Posts: 16

Original Poster
Rep: Reputation: 0
The following packages is installed
xorg-server
xf86-video-modesetting
xf86-video-fbdev
xf86-input-evdev

And when I was installing Slackware ARM, I had chosen all packages in l/
 
Old 08-25-2014, 11:47 AM   #7
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 202

Rep: Reputation: 9
Ok then remove any /etc/X11/xorg.conf* like files and try startx
What do you get ? I mean on the terminal not in the log.

How big is the SD on your PI ? Can you make a compressed image of it and put it on dropbox or something like that so I can try running it on my PI ?
Like if you put it on your pc (/dev/sdb) and the do something like
Code:
dd if=/dev/sdb bs=4096 | gzip -c > /tmp/pi_image.dd.gz
You could run this from the pi itself as long as you write to somewhere else other then the SD that the system is on. Assuming you have mounted a USB stick on /mnt/tmp you could do this on the PI itself:
Code:
dd if=/dev/mmcblk0 bs=4096 | gzip -c > /mnt/tmp/pi_image.dd.gz
What version of PI do you have A,B,B+ ?

Last edited by louigi600; 08-25-2014 at 01:42 PM.
 
Old 08-26-2014, 10:47 PM   #8
sleetdrop
LQ Newbie
 
Registered: Mar 2005
Posts: 16

Original Poster
Rep: Reputation: 0
Can you leave me your email or IM here, I have not found how to PM in this forum.
I had put rpi on internet, I will send you login information to you. You can check it online.
 
Old 09-01-2014, 12:48 AM   #9
sleetdrop
LQ Newbie
 
Registered: Mar 2005
Posts: 16

Original Poster
Rep: Reputation: 0
After analyzing this problem with the help of louigi600, we found that Xorg Server works with driver fbdev even xorgsetup can't create a xorg.conf file. But it didn't have hardware acceleration, so I couldn't run XBMC.
Then we find http://slaxbmc.blogspot.jp/2014/06/s...1-upgrade.html, which works out of box for running XBMC.
 
Old 09-04-2014, 02:19 AM   #10
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 202

Rep: Reputation: 9
The X in XBMC doe not com from X11/Xorg it's coming from "XBox Media Center" and it's actually not even using X at all you can launch it directly from the text console.
I didn't try installing XBMC directly in Slackware ARM to try and figure out why sleeprodp was getting a message lamenting that XBMC could not find OpenGL acceleration.
This actually surprises me a little (which ARM platforms have openource drivers that support OpenGL acceleration ?).

Anyway I'm not sure what they've done in slaxbmc but it's working nicely (just a little slow to boot) and I think that it may be a very good way of having both a good media center and desktop replacement all in one. Previously I was running OpenELEC on the PI but that was lacking even a worthy browser, so it was really useless as a desktop system.
 
  


Reply


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
The Slackware ARM Question of the day: why xf86-video-s3-0.6.5-arm-4.tgz ?!? Darth Vader Slackware 2 09-15-2013 09:23 PM
slackware xorgsetup bug? chaosorama Slackware 3 08-21-2009 10:18 PM
xorgsetup not working slackware current samac Slackware 7 03-24-2007 07:00 AM


All times are GMT -5. The time now is 10:46 AM.

Main Menu
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