LinuxQuestions.org
Review your favorite Linux distribution.
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 08-06-2014, 01:06 PM   #16
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0

Here is what I did. I typed it enough times to remember


Grub. Linux /kernels/huge.s/bzImage
Grub. initrd /isolinux/initrd.img
Grub. boot



I tried setting the vid mode on the kernel line.


Can't wait to get home and try out your suggestions


Thanks
 
Old 08-06-2014, 02:29 PM   #17
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
I completed my previous post, adding some commands since your answer.

I didn't find a specific command to grab the video mode, but the output of dmesg should give us enough information.

We should see the initial video mode as well as the one after handover (look for console, Console, "frame buffer", fb in dmesg.txt).

The command "lspci -knn | grep-A3 VGA" will probably trigger an error about the resource libkmod missing. This error will prevent to display the kernel modules fitting your video card, but at least the output will give us the exact vendor and model, as well as the kernel driver in use.

Also, which ISO did you use that allowed you to go as far as typing setup?

Last edited by Didier Spaier; 08-06-2014 at 03:21 PM.
 
1 members found this post helpful.
Old 08-06-2014, 09:05 PM   #18
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
i used the flash drive with the files that i copied from the slack64-current dvd iso. i will try your isos soon to see if they work the same. that nouveau driver page was a winner.


grub> linux /kernels/huge.s/bzImage video=VGA-1:800x600Me (the M in the video part seems to be what makes it work)

grub> initrd /isolinux/initrd.img

grub> boot


i have a nice screen with clearly displayed text. a slacktab will soon be born.


edit spoke too soon, sda is the flash drive, no sign of the ssd in dmesg or any of the files made with the commands you listed...





here is an interesting line from dmesg
0.000000] efi: efi: Setup done, disabling due to 32/64-bit mismatch,

so does that mean it will not see my efi hdd due to the mismatch..... efi mixed mode support is in 3.15 kernels.....


i tried the same boot procedure with your 32 bit iso, but it did not boot the kernel, just hung at the cmd line. might try the 32 bit current dvd files, but i should go to bed instead...
Attached Files
File Type: txt dmesg.txt (44.3 KB, 2 views)
File Type: txt cpuinfo.txt (3.6 KB, 1 views)
File Type: txt lspci2.txt (804 Bytes, 1 views)

Last edited by ElfShotTheFood; 08-06-2014 at 10:48 PM.
 
Old 08-06-2014, 11:30 PM   #19
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
video=VGA-1:800x1280Me. Looks great and uses the whole screen,
 
Old 08-07-2014, 09:11 AM   #20
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
Quote:
Originally Posted by ElfShotTheFood View Post
sda is the flash drive, no sign of the ssd in dmesg or any of the files made with the commands you listed...
I should have added "cat /proc/partitions > /key/partitions.txt"

But there's is a better tool:
Code:
lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE > /key/lsblk.txt
there are other options, "lsblk -h" lists them.
Quote:
Here is an interesting line from dmesg
0.000000] efi: efi: Setup done, disabling due to 32/64-bit mismatch,

so does that mean it will not see my efi hdd due to the mismatch.....
I wouldn't bet for that. This message comes from /usr/src/linux/arch/x86/kernel/setup.c (near the end):
Code:
#ifdef CONFIG_EFI
    /* Once setup is done above, unmap the EFI memory map on
     * mismatched firmware/kernel archtectures since there is no
     * support for runtime services.
     */
    if (efi_enabled(EFI_BOOT) && !efi_is_native()) {
        pr_info("efi: Setup done, disabling due to 32/64-bit mismatch\n");
        efi_unmap_memmap();
    }
#endif
That looks purely informative (just an assumption as I don't understand well neither what triggers this message nor what these runtime-services are).

Anyhow, I'd suggest that you first check lsblk's output.

Quote:
efi mixed mode support is in 3.15 kernels...
I just checked: the code snipped above is not in mainline kernel, aka linux-3.16 at time of writing. But that's all I know.

Anyhow Slackware-current now ships linux-3.14.5, not 3.15.n.

Incidentally, I saw that, even in the huge Slackware kernel 3.10.17:
Code:
CONFIG_EFI_VARS=m
CONFIG_EFI_VARS_PSTORE=m
CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y
CONFIG_CACHEFILES=m
CONFIG_EFIVAR_FS=m
But I have no idea which of these settings possibly matters.

A slacker as I be, I guess that time has come for me to read the UEFI specification [1]

PS This page from Arch's documentation looks very interesting. See especially the text under the subtitle Intel Atom SoC Bay Trail near end of page.

If I understand well you could just try to include the noefi kernel parameter in the command line to boot a 64 bit Slackware. That's worth trying, I think.

PS Other than that, the frame buffer driver handover EFI VGA (efi fb) => i915 (inteldrmfb) seems to occur without a hitch according to dmesg.

PPS Reading what is said in Arch's documentation, I'm a bit surprised that you can't boot the full 32 bit ISO I provided. I'd have done it that way:
Code:
wget http://slint.fr/misc/m80ta/slint-14.1-m80ta.iso
wget http://slint.fr/misc/m80ta/slint-14.1-m80ta.iso.md5
md5sum -c slint-14.1-m80ta.iso.md5 # output should be OK
# insert the USB key
lsblk # triple check the output not to wipe out a hard disk!!! I'll assume that's /dev/sdx
dd if=slint-14.1-m80ta.iso of=/dev/sdx bs=1M; sync
# Now try to boot off that USB key.
I guess that's what you did, but else please try.

[1] I just downloaded it (2.4 errata B). Shouldn't take long to learn by heart as it has only 2298 pages

Last edited by Didier Spaier; 08-07-2014 at 05:04 PM. Reason: PPS added.
 
Old 08-07-2014, 10:38 PM   #21
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
i did try your iso again but it still hung after boot.


noefi gives me a blank screen, i guess cause it is using the efifb driver maybe.

lsblk doesnt show anything relevant other than the flash drive, the 2gb microsd card has not shown up either. no sign of the hdd

i compiled up and booted a 3.16 kernel, the dmesg is attached. i need to get to sleep before midnight tonight.
Attached Files
File Type: txt 316dmesg.txt (49.9 KB, 2 views)
 
Old 08-08-2014, 07:21 PM   #22
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
Amazon.com has the 32gb version of this tablet for $199.00. Not a bad price.



Thankfully I should have more time to work on this machine this weekend...
 
Old 08-10-2014, 10:20 AM   #23
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
Booted a daily version of the Ubuntu live cd that has a 3.16 kernelthis morning before work (where I am now) it did manage to see the hard drive and SD card and didn't seem to have any trouble going to the desktop. I did save dmesg, and a few other commands to text files, but didn't have any real time to look at them. Also the grub menu worked just fine, so I guess I will try to see what they do different to make the grub menu work. There was a lot of errors on bootup about the hard drive. Mmcblk0



The 3.16 kernel I built did not seem to bring any modules with it. Are the modules stored in the system map.gz file with the Slackware kernels? I basically built the kernel with make all, then copied bzImage, config, and system.map to the bootdisk, but I did not have a system map.gz, and no modules loaded when I booted the kernel. What did I do wrong? Modules were built but not moved over to the boot drive.
 
Old 08-10-2014, 12:19 PM   #24
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
Quote:
Originally Posted by ElfShotTheFood View Post
Booted a daily version of the Ubuntu live cd that has a 3.16 kernel
Please provide a link, I'd like to have a look at it.
Quote:
There was a lot of errors on bootup about the hard drive. Mmcblk0
Here mmcblk0 is the nick name of a SD card.

Why do you speak about a hard drive as according the its specifications this tablet doesn't contain one but ship an eMMC for mass storage? Please post the output (already requested) of:
Code:
lsblk -o MAJ:MIN,NAME,KNAME,FSTYPE,MODEL,SIZE,TYPE,MOUNTPOINT,STATE > /key/lsblk.txt
Also, 316dmesg.txt that you posted shows two stack traces that could matter.

Quote:
The 3.16 kernel I built did not seem to bring any modules with it. Are the modules stored in the system map.gz file with the Slackware kernels? I basically built the kernel with make all, then copied bzImage, config, and system.map to the bootdisk, but I did not have a system map.gz, and no modules loaded when I booted the kernel. What did I do wrong? Modules were built but not moved over to the boot drive.
"make all" doesn't build the modules_install target, so you have to do a "make modules_install" yourself. "make help" will tell you more, see also Building a Linux Kernel from source from Eric Hameleers.

Last edited by Didier Spaier; 08-10-2014 at 12:28 PM.
 
Old 08-10-2014, 01:12 PM   #25
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
The link to the daily Ubuntu is in the Asus t100 page that is the second link in this threads first post. Followed the instructions right up to booting the live CD.

Mmcblk0 is the hard drive/ssd. I guess referring to the mass storage device as a hard drive is just an old habit. Ubuntu showed the SD card as mmcblk1.

I will post ubuntus results of lsblk later. Slackware's results only showed the usb flash drive.


I didn't do make modules install because I was building on my and laptop and didn't want to use the kernel there. I guess it wouldn't really matter though since the laptop will not be booting that kernel.


Thanks
Attached Files
File Type: txt lsblkdashoubu.txt (1.1 KB, 3 views)
File Type: txt lsblkdashoslack.txt (219 Bytes, 2 views)
File Type: txt ulspciknn.txt (1.0 KB, 1 views)

Last edited by ElfShotTheFood; 08-10-2014 at 09:43 PM. Reason: attached stuff
 
Old 08-10-2014, 03:21 PM   #26
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
Quote:
Originally Posted by ElfShotTheFood View Post
I didn't do make modules install because I was building on my and laptop and didn't want to use the kernel there. I guess it wouldn't really matter though since the laptop will not be booting that kernel.
For the records, a "clean way" in this case would be to make yourself packages for the kernel and the modules using the stuff in /source/k in the Slackware distribution media, then install these packages using installpkg with the --root option..

Nevertheless kernel-modules.SlackBuild still expects that the modules be already installed in /lib/modules/${VERSION} so you'll still have to run "make modules_install" before running the SlackBuild. But afterwards you can just remove all stuff used as input by the SlackBuilds on your laptop, having saved the packages somewhere to reinstall them if need be.
 
Old 08-10-2014, 09:48 PM   #27
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
uploaded files to this one and my previous post.


i now understand why you suggested i read the build a kernel file. i need to make an initrd with the 3.16 modules
Attached Files
File Type: txt ulsmod.txt (2.8 KB, 4 views)
File Type: txt udmesg.txt (111.3 KB, 4 views)
File Type: txt catprtshns.txt (507 Bytes, 3 views)
 
Old 08-11-2014, 09:04 AM   #28
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
According to udemsg your the driver i915 doesn't seem to like a 3.16 kernel (or reverse).

Other than that, using the option suggested for the lsblk command would have helped to know who's who (or what's why). I checked in a VM, these options are available in utopic-desktop-amd64.iso as of today (run as a live system, I don't intend to install that <not nice word here>), see attached snapshot.
Attached Images
File Type: png snapshot.png (78.3 KB, 5 views)

Last edited by Didier Spaier; 08-11-2014 at 09:09 AM.
 
1 members found this post helpful.
Old 08-11-2014, 11:20 AM   #29
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 34

Original Poster
Rep: Reputation: 0
I posted the results from lsblk with all the options, but I attached them to an earlier post

Lsblkdasho. One from slack and one from Ubuntu.


Files with a u. Like udmesg were from Ubuntu. If you didn't already realize that.

Last edited by ElfShotTheFood; 08-11-2014 at 11:24 AM.
 
Old 08-11-2014, 11:30 AM   #30
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,388

Rep: Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090Reputation: 1090
Sorry I need better glasses (or just clean the ones that lie on my nose).

So what's remain to be understood is why Slackware can't see all your block devices...

Last edited by Didier Spaier; 08-11-2014 at 11:33 AM.
 
  


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


All times are GMT -5. The time now is 09:58 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