LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 04-11-2015, 02:57 AM   #61
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled

Well, I can open the installer of Arch. The tty is working but the xorg is not. KMS or gnome doesn't work. I need to explore more.

On internet there are lots of information of Bay Trail, often about the T100. It is possible that I try with ubuntu or other tipical distros to test.

About wifi, there are some patch for T100 that works with M80TA since is the same chip. Basically, you need to put this file https://raw.github.com/jfwells/linux...241b4-sdio.txt in /lib/firmware/brcm and the wifi is working. But have lots of cuts and errors.
 
Old 04-12-2015, 09:21 PM   #62
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
wish i could help with the arch stuff, but i have no experience at all with that distro. i will say that in my experience, xorg will not run unless the i915 module gets loaded. i now have three baytrail devices, and none of them want to play nice with slackware or ubuntu. i think once slackware bumps the kernel version to 3.16 or higher it will get a bit less complicated.


the tons of pages about the t100 mostly suggest using rufus or unetbootin to make usb boot sticks, but i have come up with a much simpler way. dd'ing an image to a flash drive will give you a read only file system that you will not be able to put the bootia32.efi file on. but if you mount the iso as a loopback device (mount -o loop image.iso /mnt/wherever) you can simply select all the files and copy them straight over to the flash drive, and then put the bootia32.efi file into the /EFI/boot/ folder and you should be good to go, or at least good to boot the drive.

unfortunately the slackware installer seems to have trouble with the mmc storage of these systems. when i have managed to run setup, it has failed saying the device is full, usually early in the installation, like the ap series. i have gotten around this problem by installing to a different flash drive, or to the sd card.

linux-4.0 is official, i'm going to see if any of the patches out there can actually fix the rpmb errors of the mmc drive that seem to cause most of my problems.
 
Old 04-12-2015, 09:40 PM   #63
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
Quote:
Originally Posted by ElfShotTheFood View Post
wish i could help with the arch stuff, but i have no experience at all with that distro. i will say that in my experience, xorg will not run unless the i915 module gets loaded. i now have three baytrail devices, and none of them want to play nice with slackware or ubuntu. i think once slackware bumps the kernel version to 3.16 or higher it will get a bit less complicated.


the tons of pages about the t100 mostly suggest using rufus or unetbootin to make usb boot sticks, but i have come up with a much simpler way. dd'ing an image to a flash drive will give you a read only file system that you will not be able to put the bootia32.efi file on. but if you mount the iso as a loopback device (mount -o loop image.iso /mnt/wherever) you can simply select all the files and copy them straight over to the flash drive, and then put the bootia32.efi file into the /EFI/boot/ folder and you should be good to go, or at least good to boot the drive.

unfortunately the slackware installer seems to have trouble with the mmc storage of these systems. when i have managed to run setup, it has failed saying the device is full, usually early in the installation, like the ap series. i have gotten around this problem by installing to a different flash drive, or to the sd card.

linux-4.0 is official, i'm going to see if any of the patches out there can actually fix the rpmb errors of the mmc drive that seem to cause most of my problems.
I have the i915 loaded but the KMS does not work and the xorg does not work also. Probably the next weekend I'll try other distros based on T100. But I'm shocked with that because the graphics is an intel one and usually it works perfectly... In tutorilas for T100 the people usualy use some kernel optins as video=VGA-1:1368x768e but didn't work in Arch Linux.

In arch, we have now the 3.19.3 kernel image and the mmc is working but there are some errors in the loading of the distro without any bad consequence. The patch that I put before is working on Arch, I suppose that works in other distros because is a patch for ubuntu. There are other patch to solve the problem in SD.

About the loader, yes, the problem is the bootia32.efi. The tablet don't have any support for old loaders or EFI 64 and rEFInd cannot do it. When I started with the tablet I don't understand this point and I lost lots of times in that.
 
Old 04-13-2015, 09:17 PM   #64
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
the vivo tab uses portrait mode, while the t100 uses landscape. i think the correct vid mode is video=VGA-1:800x1280e to be sure it is on page one of this thread.
 
Old 04-17-2015, 01:19 AM   #65
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
Well, yesterday I finally start a graphic interface... For some reason that I don't understand, the intel driver is working but it doesn't detect correctly the screen. For this reason, KMS is not working and the desktop didn't open in my Arch. Well it works but a black screen is obtained. I suppose that it will solve in few months. The problem in arch is that the intel module is charge in the beginning, it has to been blocked previously.
I started gnome-shell and, well, without any graphic potency, it is slow... but well, I suppose that it works in some time. On the other hand, the touch and the stylus is not detected in kernel 3.19.3. Neither in 4.0. I read that this kernel is a little conservative because they want use it as a LTS, probably the advances will be in the 4.1 or 4.2. Today I'll try linux-next.
 
Old 04-24-2015, 08:14 PM   #66
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
woohooo major update to slackware current. but i downloaded 32 instead of 64..........
 
Old 04-24-2015, 09:36 PM   #67
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
In fact, is not the best option? I mean, the tablet only have 2 GB, I think that is a good option save some RAM memory...
 
Old 04-25-2015, 12:07 AM   #68
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
32 bit doesn't have efi boot files,

but i booted both on my t100, and neither one saw the mmc drive.....
 
Old 04-27-2015, 12:59 AM   #69
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
I'm using the 32-bits arch Linux. With rEFInd, the 32-bits kernel can be charged correctly (no EFI boot files, only the kernel is used). I think that you can do the same in Slackware because the Linux kernel has included a built-in boot loader, since version 3.3.0.

In Arch, the mmc drive is writable, but some errors in dsmeg are obtaining, often in the first charge. I'm using the 3.19 and the 4.0 kernel. Both can read the mmc memory. However, I cannot install the linux-next kernel. It is failing with the mmc memory, I think it can not read the mmc.
 
Old 04-27-2015, 06:06 PM   #70
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
yeah, the efi files work with 32 bit slackware, but they do not come with it.


btw. i am posting this from the tablet!!!!!!



the 4.1-rc1 kernel was released last night. it is working very well, but the rpmb errors are still there. looks like bluetooth and audio modules are loading, hopefully they just need firmware loaded
 
Old 04-27-2015, 09:37 PM   #71
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
With the 4.1, the touch is working?
 
Old 04-27-2015, 10:04 PM   #72
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
working great, the button on the stylus even pastes text like a middle mouse button.

applied the mmc-card-not-access-RPMB-partition-for-normal-read-and-write.patch successfully, and those errors are gone. but it appears i have some debugging messages turned on in the kernel .config that i need to find that keeps filling up dmesg. sound and bt still not working. when i get things all figured out i will attach a .config file.



damn, it has been quite a long ride to get to this point.


i got fed up with the x205a, recovered it to windows and gave it to my niece, she loves it, the t100 i have is the taf variant, it is currently running ubuntu-studio, hopefully it will run slackware soon.
 
Old 04-27-2015, 10:30 PM   #73
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
What about the graphic card? Are you using nomodeset or it is possible to use the intel correctly?
 
Old 04-27-2015, 11:01 PM   #74
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 71

Original Poster
Rep: Reputation: 0
it is working correctly
 
Old 04-29-2015, 09:11 AM   #75
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
linux 4.1-rc1 compiled and installed. As ElfShotTheFood said, the graphic card works correctly, more or less, the screen can be rotated (but is not rotated automatically) and the touch screen is working correctly too. The stylus and the fingers works as in windows. The driver has some errors, as some times is blocked and the touch screen don't work, but in general is usable.

On the other hand I think the Arch Linux is a little more slow than windows, but I think that the problem is basically some bugs in rc and some not completely implemented things of BayTrail.

For example, MyPaint works perfectelly.
 
  


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 09:41 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