LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
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 02-05-2018, 04:38 PM   #16
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,031

Rep: Reputation: 147Reputation: 147

Quote:
Originally Posted by SCerovec View Post
FWIW,
On a Pi, I once wanted "autologin", in terminal only (run level 3).

I ended up putting an
Code:
/bin/login -f <username> &
to the end of /etc/rc.d/rc.local

It helped me get an tty login so I could have conky run, since once the user is "logged in" each and every startup procedure is invoked as well.

I used .bashrc

my2c
I have a script where it will automatically log in the user after boot from runlevel 3 by adding an entry on my /etc/inittab. I remember years ago setting up an application (not a desktop or window manager) when running startx. I'm drawing a blank now. Need to do some more digging.
 
Old 02-06-2018, 01:32 AM   #17
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 416

Original Poster
Rep: Reputation: 205Reputation: 205Reputation: 205
Dear fellow Slackers, can we move this discussion to the appropriate thread? Thank you
https://www.linuxquestions.org/quest...hf-4175613852/

I'm not starting kodi automatically at system boot but using lirc (irexec) to start it with the remote control. You can always use rc.local to start kodi ( create a kodi start script in your /home/kodi first):
Code:
su kodi -c /home/kodi/kodi-start
- more hints / script details on the Kodi thread (if asked first)
 
1 members found this post helpful.
Old 02-06-2018, 06:22 AM   #18
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,031

Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by abga View Post
Dear fellow Slackers, can we move this discussion to the appropriate thread? Thank you
https://www.linuxquestions.org/quest...hf-4175613852/

I'm not starting kodi automatically at system boot but using lirc (irexec) to start it with the remote control. You can always use rc.local to start kodi ( create a kodi start script in your /home/kodi first):
Code:
su kodi -c /home/kodi/kodi-start
- more hints / script details on the Kodi thread (if asked first)
Blah! I shouldn't be asking question so early in the morning before having coffee.
 
Old 02-09-2018, 03:19 PM   #19
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,206
Blog Entries: 2

Rep: Reputation: 190Reputation: 190
Are we missing an auto-login for Slackware thread now?
 
Old 02-10-2018, 09:50 AM   #20
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 416

Original Poster
Rep: Reputation: 205Reputation: 205Reputation: 205
Quote:
Originally Posted by stormtracknole View Post
Blah! I shouldn't be asking question so early in the morning before having coffee.
Don't worry, the ffmepg&Kodi building and using on ARM is a little complex/confusing

Kodi doesn't need X to be launched and running, and on these little/performance-weak ARM boards, due to the overhead that X is creating, it's not even recommended to have it running while using Kodi. Additionally, you need the Raspberry Pi modified and adapted mesa libs (the ones that are also needed for this FFmpeg build). Slackware ARM provides you with the generic mesa libs in /usr/lib and X is using those, Kodi needs the special ones provided by Raspberry Pi in /opt/vc, again the very ones that are also used for this FFmpeg build:
https://github.com/raspberrypi/userland

Basically you'll end up with two mesa libs versions and you also need to switch between them for using either X or Kodi. I remember trying to substitute the Slackware ARM stock mesa libs with the ones provided by Raspberry Pi and failed, then dumped the whole idea because it didn't make sense.
You'll get these details in the Kodi thread I created and referred to in my previous post. That's why I invited you to post on that thread and I'll be happy to reply/help on topic.
 
2 members found this post helpful.
Old 02-12-2018, 07:27 PM   #21
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,031

Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by SCerovec View Post
Are we missing an auto-login for Slackware thread now?
I phrased my question wrong. I have been doing auto-login for years. I should have asked how to automatically start kodi when executing startx. I know I've done it before.
 
Old 02-12-2018, 07:28 PM   #22
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,031

Rep: Reputation: 147Reputation: 147
Quote:
Originally Posted by abga View Post
Don't worry, the ffmepg&Kodi building and using on ARM is a little complex/confusing

Kodi doesn't need X to be launched and running, and on these little/performance-weak ARM boards, due to the overhead that X is creating, it's not even recommended to have it running while using Kodi. Additionally, you need the Raspberry Pi modified and adapted mesa libs (the ones that are also needed for this FFmpeg build). Slackware ARM provides you with the generic mesa libs in /usr/lib and X is using those, Kodi needs the special ones provided by Raspberry Pi in /opt/vc, again the very ones that are also used for this FFmpeg build:
https://github.com/raspberrypi/userland

Basically you'll end up with two mesa libs versions and you also need to switch between them for using either X or Kodi. I remember trying to substitute the Slackware ARM stock mesa libs with the ones provided by Raspberry Pi and failed, then dumped the whole idea because it didn't make sense.
You'll get these details in the Kodi thread I created and referred to in my previous post. That's why I invited you to post on that thread and I'll be happy to reply/help on topic.
Thank you! I'll direct my questions there.
 
Old 04-22-2018, 11:05 AM   #23
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 416

Original Poster
Rep: Reputation: 205Reputation: 205Reputation: 205
In my first post, the one I cannot edit anymore now, I suggested to use 16bit color depth for best performance. I did it because at the time I wrote the guide the support for 24 bit color in the firmware for the Raspberry Pi platform was broken.

It works now and I'd advise you to put the following color depth settings in your /boot/config.txt
Code:
framebuffer_depth=24
or, if you want to go 32 bit:
Code:
framebuffer_depth=32
framebuffer_ignore_alpha=1
 
1 members found this post helpful.
  


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
Slackware ARM on a Raspberry Pi 2 Exaga Slackware - ARM 28 05-06-2015 06:42 AM
LXer: Raspberry Pi 2: Raspbian (ARMv6) v Linaro (ARMv7) LXer Syndicated Linux News 0 03-15-2015 04:20 PM
Slackware ARM 14.1 on a Raspberry Pi Exaga Slackware - Installation 2 11-17-2013 08:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 07:22 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration