LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 11-17-2015, 07:07 PM   #121
jonnythedreamer
LQ Newbie
 
Registered: Nov 2015
Location: Russia
Distribution: Fedora
Posts: 7

Rep: Reputation: Disabled

Ok. I will try to install when there will be a sound support. Please write in this thread if you find some solution for sound.
 
Old 11-24-2015, 10:34 PM   #122
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
There are many bug on this tablet on linux... the touch control stops if you use with the stylus, no sound, random frozens... I'ts really sad.
 
Old 01-19-2016, 11:10 PM   #123
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
No progress in Kernel 4.3 ...It's strange the really bad support that it is having.
 
Old 02-10-2016, 03:22 PM   #124
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
i didn't have any luck with 4.3 or 4.4, it looks like 4.5 has the right audio driver, but i haven't successfully booted it yet.


in other news the slackware current installer now sees the mmc drive and the install runs smoothly (after fixing the usb drive with bootia32.efi and copying the grub.cfg to /boot/grub) but the elilo install script fails or just does not run. also i thought that it failed to make a usb boot stick, but i realized that it made the stick just fine, with bootx64.efi. i guess i was too tired to realize and fix it last night when i was messing with it.
 
Old 02-14-2016, 10:30 AM   #125
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
ok so given the success with the recent update of slackware current, i will update/finish the guide to get slackware installed on this tablet. you will need a usb otg cable, a usb hub, and a usb keyboard, and a couple of usb flash drives. a quirk of the hub i have is that the keyboard has to be in the last plug in order to be seen by the linux system. don't know why, that is just how it is.

I am sure some of you may read this and have a better way to do certain parts of this, feel free to correct my mistakes, i am far from a guru, just a user trying to use a cool piece of hardware.

http://taper.alienbase.nl/mirrors/sl...4-current-iso/ has iso images for slackware64-current. i then mount the image with the command mount -o loop slackware64-current-install-dvd.iso /mnt/dvd

from here i just used thunar to select all and copy the files to a brand new straight out of the package flash drive. since it is a vfat file system, it complains about the filesystem not supporting symlinks, do i want to skip? yes to all gets the job done. I never looked into what the symlinks were because i never had a problem that i could attribute to them. there is probably a better way to do it but i do not know what that is. dd will copy everything over, but it will be a read only file system and we need to add a couple files to the drive before we use it to install. this would be a good time to dl and copy a file to the flash drive that will be needed to enable wifi. https://raw.github.com/jfwells/linux...241b4-sdio.txt. once the system is installed it will be copied to /lib/firmware/brcm/brcmfmac43241b4-sdio.txt and in theory, wifi should work.

bootia32.efi is the next step, it is available as a dl from links in the first post of this thread, but those are made for ubuntu and look for the grub.cfg in /boot/grub. slackware already has the grub.cfg in /EFI/boot so we need to follow the directions here
https://github.com/jfwells/linux-asu...ee/master/boot
and make one that works with slack. it is really as simple as follow the instructions up to the last step, then in the last command given you just need to change -p /boot/grub to -p /EFI/boot and after it compiles you should have a bootia32.efi file that can be dropped into the /EFI/boot folder of the flash drive created earlier. as long as you are using a recent version of slackware64 current then it should get you all the way through setup with no errors. i am assuming that you know how slackware setup goes, and what choices to make. if keeping windows then you should have done everything possible to shrink the c drive as small as it will let you. installing to an sd card is an option. it will be seen as mmcblk1 and you can partition it just as you would an internal drive.

unfortunately, getting through setup without errors does not mean getting through without problems. the elilo installation script will not run so no boot loader is installed and the boot stick you may have made will not boot because it does not have bootia32.efi


i attached the .config files i most recently used to build linux kernel 4.5.0-rc3 i will not claim it is perfect, but it is one that i have been using since the 3.18 or so kernels and keep moving it along to the newer version and make oldconfig with my best guesses as to what new things to include, if in doubt i usually chose m, so i am fairly sure it is making things that are not needed, but not an awful lot.

our next step is to get a working boot loader. i guess this step will be different whether or not you decided to dual boot windows or deleted it. either way, we need to get our bootia32.efi file, grub.cfg, a bzImage and an initrd.gz on to the 100mb efi system partition. in theory we should be able to get away with just bootia32.efi and a vmlinuz, but for whatever reason, it doesnt work and the kernel hangs because it cannot find init or cannot mount root

so now we are at a chicken or egg scenario. we cannot boot the system without an initrd.gz and we need to boot the system to make it. if you have another pc that can make a kernel and initrd then it can be done much simpler, the best way to do it,(that i can think of) is to use a usb flash drive on the other pc, with an ext4 file system and compile the kernel there. it may seem strange to compile on a flash drive, but by making the kernel and initrd on a different pc the modules will still need to be installed to the tablet. once the tablet boots with the kernel and initrd about to be made, you can mount the flash drive, cd to the kernel source directory, and make modules_install, reboot and be happy. once the bzImage and initrd are made, copy them to the root of the setup flash drive made earlier and boot off it, instead of running setup though we will fix up the efi partition.

the way i have done it is after fake root login, instead of running setup make a couple directories.

mkdir /efi
mkdir /sda

mount /dev/mmcblk0p1 /efi
mount /dev/sda1 /sda

cp /sda/EFI/boot/bootia32.efi /efi/EFI/Boot/
cp /sda/EFI/boot/grub.cfg /efi/EFI/Boot/

now since i have left windows8.1 on the tablet, i decided to mkdir /efi/EFI/slack and put the slackware specific boot files, bzImage-4.5-rc3 and initrd-4.5-rc3.gz there. if you erased windows then you should delete the /efi/EFI/Microsoft folder. if you did not erase windows then the ms bootloader still is in charge. there are probably better ways to do it, but i simply renamed the bootmgr.efi file in /efi/EFI/Microsoft/Boot to something else.

now we really just need to edit the grub.cfg file to point to the correct kernel and initrd file. mine looks like this

set default="0"
set timeout="3"
set hidden_timeout_quiet=false

menuentry "slacktab "{
echo "loading..... knock on wood"
linux /EFI/slack/bzImage-4.5-rc3 root=/dev/mmcblk0p5 video=VGA-1:800x1280Me
initrd /EFI/slack/initrd-4.5-rc3.gz
}

the mmcblk0p5 is the linux ext4 partition because windows is on partitions 2-4, not sure what is in partitions 2 and 3 but the main c drive is partition 4. you may have deleted windows and set things up differently.


as far as i can tell, there is no reason that the efi partition steps could not be done before package installation.



after installation, fixing the efi partition and finally booting the system and logging in you will find that you have no modules loaded and you cannot start x, the first things to do are.

put the /lib/firmware/brcm/brcmfmac43241b4-sdio.txt file in place, and then you can either make an initrd.gz for the installed 4.4.1 slackware kernel and copy it to the efi partition with the huge kernel, or mount the ext4 flash drive with the 4.5-rc source, cd to the folder and make modules_install. when you reboot you should have lots of modules loaded and be able to startx and have working wifi.

from here i would go and get sbopkg, then use it to dl, build, and install xvkbd so that we can use it to login to the system. once that is completed edit the file /etc/X11/xdm/Xsetup_0 and add the line exec /usr/bin/xvkbd -geometry 800x200+0+1080 -nokeypad &
to the bottom of the file. after that edit the inittab to have the system boot to runlevel 4. the system will look for kdm before xdm so we need to get rid of kdm, i simply renamed it to kdm.old. i couldn't get xvkbd to show up with kdm, maybe you know the trick?

after all that you should be able to boot up the system and have the xdm login screen come up with the xvkbd virtual keyboard at the bottom of the screen, logging in you should have wifi available. unfortunately audio, and bluetooth are things i have yet to get working. maybe you can figure them out.

all right, so it is really not that great of a guide, but it should get you a working slackware64 installation. when time permits i should probably make a nice boot image that will take many of the tedious steps out of this process and clean up the guide a little bit.

good luck
Attached Files
File Type: txt dot.config.txt (98.2 KB, 21 views)

Last edited by ElfShotTheFood; 02-14-2016 at 01:15 PM. Reason: continuing
 
Old 02-14-2016, 08:38 PM   #126
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
i am about to try and make a flash drive with 32bit slackware using the efi files from slackware64. i think it should work, but we shall see. i will try it on my t100taf first.

edit;
it is installing, so far so good.


so i used the efi folder from the flash drive i made before and just deleted the rest and copied the files from slackware32 current iso. the t100taf only has 1gb of ram so 32 bit will be better for it.


edit2

it worked just fine.

Last edited by ElfShotTheFood; 02-14-2016 at 09:19 PM.
 
Old 02-21-2016, 09:59 PM   #127
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
i didn't notice anything drastically different with 4.5-rc5, but there were some new errors about the audio which could be promising.
 
Old 02-21-2016, 10:58 PM   #128
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
Quote:
Originally Posted by ElfShotTheFood View Post
i didn't notice anything drastically different with 4.5-rc5, but there were some new errors about the audio which could be promising.
So, audio is there?
 
Old 02-28-2016, 01:10 PM   #129
suicidal_orange
LQ Newbie
 
Registered: Jun 2004
Distribution: kubuntu 11.10
Posts: 12

Rep: Reputation: 0
Thanks ElfShotTheFood, I got one of these for Christmas 2014 and was saddened to find no Linux support so I've continued to use my ancient netbook. Now the touchpad is dying so I looked to see if there's any progress and what do I find but a complete walkthrough for one of my favourite distros before I got lazy!

Need to find a powered USB hub then I'll be giving this a go
 
Old 03-17-2016, 08:41 PM   #130
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
yeah, i am giving myself a facepalm right now as i have realized the proper way to make the usb boot disk has been right in front of me all this time. usbimg2disk.sh copied the slackware64-14.2-rc1 package tree to the usb drive. i had to remount the usb drive rw then i was able to copy the bootia32.efi file to the drive. unfortunately, the boot disk uses elilo, so the disk boots, but only to the grub command line. so i had to also copy the /EFI/boot/grub.cfg from the iso image as well as the kernels and isolinux folders. remember those symlinks that didn't copy over, they are in the isolinux folder. i suppose i could update the script to copy the other folders, but not tonight. i successfully booted the disk to fakeroot login and that is all the time i have for this episode kiddies.

I wonder if there are reasons for not including bootia32.efi in the official image, it would certainly make the lives of baytrail users a bit easier.


happy St Patrick's day.
 
Old 03-28-2016, 05:48 PM   #131
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
from yesterdays changelog

a/grub-2.00-i586-4.txz: Rebuilt.
Include support for 32-bit EFI. Thanks to Eric Hameleers.

happydance.png


so in theory the official 14.2 image should boot without the hoop jumping.

and no audio still with 4.6-rc1. with a proper asound.state file it may work, but the one for the t100 that i tried did not work. looking for others still.

Last edited by ElfShotTheFood; 03-28-2016 at 05:55 PM.
 
Old 06-21-2016, 05:35 PM   #132
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
wow, it has been a while since my last update. not a lot to report though.

i have disabled the touchscreen to give the pen stability.

edit /usr/share/X11/x.org.conf.d/10-evdev.conf and add the line

Option "Ignore" "On"

to the section with "evdev tablet catchall" and restart x.org. as with most things, there could be a better way to do it, but this tablet has been rock solid without the touchscreen and just the pen.


also here is a script to rotate the screen, that i don't remember if i posted before, but it has the touchscreen lines commented out.


i am currently running a somewhat recent install of slack32-current with 4.7-rc2, while sound and bluetooth still don't work, everything else is good.

ubuntu-studio still cannot get through installation without crashing while attempting to install grub, but you can get it to boot by typing the paths to kernel and initrd via the grub cmd line. i didn't do any other testing with ubu.

i am tempted to try fedora 24 just to see how it works, but I likely will not have time.



oh yeah, woot has the 32gb version of this tablet on sale for $109 - open box
http://sellout.woot.com/offers/asus-...so_cnt_wp_3_17
but then again, if you are reading this you probably already have one.
 
Old 07-02-2016, 07:15 AM   #133
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
Well, today I played a little bit with my tablet.

Testing many things with my Arch instalation I reach some audio in my tablet. I am not 100% sure about the methods, but I explain what I do.

First, I upgrade the system: kernel version 4.6.3-1 (ARCH)

Later, I put kernel4.5.xand4.4.x.asound.state that is in the debian webpage: https://wiki.debian.org/InstallingDe...s/T100TA#Audio

I put as appears in the debian webpage:

# cp kernel4.5.xand4.4.x.asound.state /var/lib/alsa/asound.state

I restore alsa and restart pulseaudio, as in debian wiki says.

And the magics start.

I only have audio in the speakers, no audio in the headphones ...
 
Old 07-02-2016, 11:43 AM   #134
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
awesome news, i tried it rather quickly, and it sorta worked, but i didn't actually download and install an asound.state file, so the mixer showed up, audacious played a file, but i heard nothing.

now i am installing slackware-14.2. i have that folder on the installation thumbdrive so i'll be trying again right after installation finishes.


 
Old 07-02-2016, 12:54 PM   #135
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
<happy dance.gif>

sound works rather well, i used the 4.5.x .state file with my 4.7-rc2 kernel and the tunes are jammin while i configure the rest of the fresh slackware 14.2 system.

i didn't backup the files i changed in /etc, so i will be reading my own instructions above.
 
  


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
LXer: Rugged Bay Trail COM offers soldered RAM LXer Syndicated Linux News 0 03-24-2014 10:53 PM
LXer: Mini COM Express module runs Linux on the Bay Trail LXer Syndicated Linux News 0 03-18-2014 08:00 AM
LXer: Intel Bay Trail NUC Linux Performance Preview LXer Syndicated Linux News 0 02-13-2014 04:00 AM
LXer: Bay Trail-I Mini-ITX boards go big on expansion LXer Syndicated Linux News 0 02-01-2014 04:00 PM

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

All times are GMT -5. The time now is 10:36 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
Open Source Consulting | Domain Registration