LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 03-01-2014, 12:48 AM   #16
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9

Quote:
Originally Posted by Arnim000 View Post
Hello,


@louigi600:

Yesterday I try your build script. There is no choice "cubietruck", so I try cubieboard2.

My cubietruck is booting, but my keyboard is not working.
Many users have this problem with the keyboard, because it is an cordless Logitech MK520 keyboard + mouse set with the Logitech Unifying USB-Reciver. /dev/hidraw raw HID device is missing in kernel, I think.
That's the old image builder or the old hwpack.

Quote:

Today, I tested your updated scripts.

Test with choice cubieruck: With this, my cubietruck will not boot from SD card.
I don't know why.
Yep that's what I was looking for ... thanks for testing. Obviously this issue is not just limited to my tablet. I'll see if I can get that to work. Maybe I can mix up the old boot loader with the new kernels and have a better success (actually that's what's running on my tablet 3.4.75 kernel on the old boot loader) ... I'll haveto do something.

Quote:

So I try the option "cubieboard2". Wow, it is booting.
Also my logitech keyboard is working:-)


WLAN is not working, because the modul bcmdhd is missing.
All the other hardware, I don't tested it.
Cubieboard 2 from the new hwpack or from the old hwpack ? just to know if on some boards the new bootloader is working.
Also are you usning 14.0 or 14.1 miniroot for userland on the booting setup ?

You can have a go at building a custom kernel to try support all you need.

Last edited by louigi600; 03-01-2014 at 01:08 AM.
 
Old 03-01-2014, 01:03 AM   #17
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
Quote:
Originally Posted by cycojesus View Post
Note a bug on first boot: / is mount read-write from the start and this disturbs /etc/rc.d/rc.S so there will be a warning message during boot. Just press Enter to continue booting
You should be passing and environmement variable to uboot like this (your root may be on mmcblk0p1 oe something like that since you have a single partition scheme)
Code:
  
  root=/dev/mmcblk0p2 ro rootwait
I write that to uEnv.txt

Or does that happen only on the very first boot ?

Last edited by louigi600; 03-01-2014 at 01:05 AM.
 
1 members found this post helpful.
Old 03-01-2014, 02:09 AM   #18
Arnim000
LQ Newbie
 
Registered: Feb 2014
Location: Germany
Distribution: Slackware
Posts: 7

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by cycojesus View Post
Have you tried booting from the card? It should boot just fine.
Yes, I did! But it does not boot.
I just tried it again, here what I did:
Deflate the downloaded file:
Code:
 xz -d SlackwareARM_cubitruck-0.2_rootfs_SD.raw.xz 
 cat SlackwareARM_cubitruck-0.2_rootfs_SD.raw > /dev/mmcblk0
Putting the card into the slot, switching power on:
Nothing appears. The blue LED is glowing (not flashing). The other LEDs are dark.
My Screen (HDMI) is dark.
No boot, sorry.
But cubietruck is NOT booting the preinstalled Android (nand), like when no SD card is inserted. It freezes at the SC card. You know, what I mean.

I am not an beginner in Linux, I used Linux (Slackware) over 10 years. But I am a beginner in programming, there is no specialized knowledge.
So I think, I don't made something wrong.

Sincerely,
Arnim!
 
Old 03-01-2014, 02:16 AM   #19
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
Arnim000: can you pleas checkout my questions @ post #16 ... it will help be debug what's wrong with the new image creator/hwpack.
 
Old 03-01-2014, 02:31 AM   #20
Arnim000
LQ Newbie
 
Registered: Feb 2014
Location: Germany
Distribution: Slackware
Posts: 7

Rep: Reputation: Disabled
Hello,

Of course, I will answer your questions!!
But you posted while I was answering the other post.
Writing english takes some time;-)

Quote:
Originally Posted by louigi600 View Post
Cubieboard 2 from the new hwpack or from the old hwpack ? just to know if on some boards the new bootloader is working.
Also are you usning 14.0 or 14.1 miniroot for userland on the booting setup ?
With the old hwpack, I used the old miniroot 14.0.
With the new hwpack, I used the new minitoot 14.1.
I don't mixed new and old.

I tested your new Scripts.
New hwpack, custom_hwpack_3.4.61.tar.xz + minitoot 14.1 + Kernel 3.4.61
With option "cubietruck", there is no boot.
With option cubieboard2, my cubietruck is booting.
Booting with miniroot 14.1 + new hwpack + option "cubieboard2"

Quote:
You can have a go at building a custom kernel to try support all you need.
This is the reason, while I am waiting for someone, who collates a slackware image for cubietruck ;-)

Sincerely,
Arnim!

Last edited by Arnim000; 03-01-2014 at 11:44 AM.
 
Old 03-01-2014, 02:49 AM   #21
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
I noticed that my image creator script does not ckean up the /tmp/hwpack directory in which the hwpack is exploded.
If you did not clean it up manually I think you have a mixed up thing anway. I'm changing the script to clean up before extracting is a previous /tmp/hwpack is found.

Could you pleas remove /tmp/hwpack and try again with the new hwpack ?

Good to know that the 14.1 userland is booting fine on my image creator (I've not got round to testing it).
 
Old 03-01-2014, 02:50 AM   #22
cycojesus
LQ Newbie
 
Registered: Dec 2005
Posts: 29

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by louigi600 View Post
You should be passing and environmement variable to uboot like this (your root may be on mmcblk0p1 oe something like that since you have a single partition scheme)
Code:
  
  root=/dev/mmcblk0p2 ro rootwait
I write that to uEnv.txt

Or does that happen only on the very first boot ?
happens on all boots unless you patch rc.S to comment the 'read junk' line that stops the boot sequence

I'll try the ro rootwait

EDIT: it worked, thanks

Last edited by cycojesus; 03-01-2014 at 02:57 AM.
 
Old 03-01-2014, 02:51 AM   #23
cycojesus
LQ Newbie
 
Registered: Dec 2005
Posts: 29

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Arnim000 View Post
Hi,



Yes, I did! But it does not boot.
I just tried it again, here what I did:
Deflate the downloaded file:
Code:
 xz -d SlackwareARM_cubitruck-0.2_rootfs_SD.raw.xz 
 cat SlackwareARM_cubitruck-0.2_rootfs_SD.raw > /dev/mmcblk0
Putting the card into the slot, switching power on:
Nothing appears. The blue LED is glowing (not flashing). The other LEDs are dark.
My Screen (HDMI) is dark.
No boot, sorry.
But cubietruck is NOT booting the preinstalled Android (nand), like when no SD card is inserted. It freezes at the SC card. You know, what I mean.

I am not an beginner in Linux, I used Linux (Slackware) over 10 years. But I am a beginner in programming, there is no specialized knowledge.
So I think, I don't made something wrong.

Sincerely,
Arnim!
try with
Code:
dd if=SlackwareARM_cubitruck-0.2_rootfs_SD.raw of=/dev/mmcblk0 bs=1024
If it doesn't work I'll upload a new image later today
 
Old 03-01-2014, 03:19 AM   #24
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
I got round to doing a bit of testing on the new script and it seems to be working fine.
I tried also the new script.bin with the old boot stuff and is seems to work fine.
I removed boot.cmd: after having a closer look at how uboot loads the various environment settings it turnes out that boot.cmd is ignored.

If Arnim000 can boot his cubietruck by using the new hwpack and selecting cuibieboard2 (and after having cleaned up /tmp/hwpack) then there is something wrong only with some boards boot stuff. If he cannot thenn I'll assume that all the boot stuff is bust in the new hwpack.

Quote:
Originally Posted by cycojesus View Post
happens on all boots unless you patch rc.S to comment the 'read junk' line that stops the boot sequence

I'll try the ro rootwait

EDIT: it worked, thanks
Good ... please go to the post where I told you this and hit "yes" beside "Did you find this post helpful?"

Quote:
dd if=SlackwareARM_cubitruck-0.2_rootfs_SD.raw of=/dev/mmcblk0 bs=1024
I used to do this but it turns out that it has no better success then doing the cat thing but it has a really bad side effect: it writes the flash in 1K blocks while the internal flash erase block is pprobabbly much bigger then that (128k)... this could turn out equivalent to erasing the blocks several times.

Last edited by louigi600; 03-01-2014 at 03:38 AM.
 
1 members found this post helpful.
Old 03-01-2014, 03:55 AM   #25
Arnim000
LQ Newbie
 
Registered: Feb 2014
Location: Germany
Distribution: Slackware
Posts: 7

Rep: Reputation: Disabled
@cycojesus:
Quote:
Originally Posted by cycojesus View Post
try with
Code:
dd if=SlackwareARM_cubitruck-0.2_rootfs_SD.raw of=/dev/mmcblk0 bs=1024
If it doesn't work I'll upload a new image later today
It does not work, same result as writing to SD card with cat.

@louigi600:
First test:
I deleted /tmp/hwpack.
Then calling create_raw_image script,
with new hwpack + miniroot 14.1 and option cubietruck

RESULT: No boot. Same result as without deleting /tmp/hwpack

Second test:
Again, I deleted /tmp/hwpack.
Then calling create_raw_image script,
with new hwpack + miniroot 14.1 and option cubieboard2

RESULT: Cubietruck is booting preinstalled Android from nand.
What is that? No stop at the SD card?

I have done this test a second time. Again, Android is booting:-(

After deleting /tmp/hwpack before creating an new image, nothing is working.
So, you are right, there is something mixed up in /tmp/hwpack, if it is not deleted before creating a new image.


Sincerely, Arnim!

Last edited by Arnim000; 03-01-2014 at 04:22 AM.
 
Old 03-01-2014, 04:27 AM   #26
cycojesus
LQ Newbie
 
Registered: Dec 2005
Posts: 29

Original Poster
Rep: Reputation: 2
I'm uploading a new image updated with all the updates I made on my script. I've tested it and it boots fine after writing it to sd using cat. Default root password is 'password'
A major change (although it should be transparent) is the use of the 'official' linux-sunxi kernel instead of patwood's. I know little about patwood's patches and as a slacker I tend to prefer vanilla upstream (next stop is trying kernel.org latest stable kernel if possible.)

@louigi600:
interesting info about dd and cat. I've changed the README accordingly
 
Old 03-01-2014, 04:35 AM   #27
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
To get you going with something again:
clean up /tmp/hwpack (or download the new script that does that for you) and create an image with the old hwpack. If you like you can use 14.1 miniroot as I've tested that it does boot but I've not got round to adding in there the pits and pieces I did to the 14.0.

If you need a newer kernel then you can mouunt the SD cart root and boot and copy over by hand from the new hwpack:
/tmp/hwpack/kernel/3.4.61_uImage.sun7i to the sd boot/uImage
/tmp/hwpack/modules/3.4.61.sun7i+ to sd lib/modules/

this should get you booting with the old bootloader but the new kernel.

I realized there is a naming convention error in the newhwpack that will fail to copy over the modules ... this may accounf for the keyboard not working at some of the test you did.
I'll fix that asap along with something to get both hwpacks booting right.
 
Old 03-01-2014, 12:34 PM   #28
Arnim000
LQ Newbie
 
Registered: Feb 2014
Location: Germany
Distribution: Slackware
Posts: 7

Rep: Reputation: Disabled
Hello,

@cycojesus:
Your new image v0.3 is booting.
I can't modprobe module bcmdhd for wlan, because of an error.
modprobe bcmdhd
ERROR: could not insert bcmdhd: No such device

Amazing, I know, there is such a device;-)


@luigi600:
Creating an image with old hwpack and new 14.1-rootfs is working.
I can boot with it.

But booting old hwpack and old 14.0 rootfs, I have no keyboard, same as yesterday.
I have mounted SD card for changing the kernel and modules. This is working too.


Old hwpack + old 14.0-rootfs, after writing the SD card, mount the second partition from SD card, and have a look at /lib/modules!!
There are no modules! This directory is empty.
The empty directory on SD card is named /lib/modules/3.4.43.sun7i+
But the directory inside the old hwpack is named 3.4.43.sun7i
(Without ending "+"!)
No modules on SD Card --> no keyboard.

Inside the new hwpack, the modules directorys are ending with "+".
Here the modules directory on the SD card is not empty. My keyboard is working.

Quote:
I realized there is a naming convention error in the newhwpack that will fail to copy over the modules
You mean the old hwpack, I think....

Bye,
Arnim!

Last edited by Arnim000; 03-01-2014 at 12:39 PM.
 
Old 03-01-2014, 01:46 PM   #29
louigi600
Member
 
Registered: Dec 2013
Location: Italy
Distribution: Slackware
Posts: 216

Rep: Reputation: 9
I fixed the script for the new names and broke on the old hwpack, now it should work with both.
You can have the new merged hwpack with new kernel, new boards and old boot environment.
I tested it on my tablet ant it's booting ... but I'd appreciate if you had a go at it too.

Don't hesitate in mixing miniroots with new and old ... the new stuff was not to support the new 14.1 version but rather to support more boards, get newer kernel and a few other minor fixes in the script itself.

Last edited by louigi600; 03-01-2014 at 03:02 PM.
 
Old 03-02-2014, 02:22 AM   #30
cycojesus
LQ Newbie
 
Registered: Dec 2005
Posts: 29

Original Poster
Rep: Reputation: 2
I

Quote:
Originally Posted by Arnim000 View Post
Hello,

@cycojesus:
Your new image v0.3 is booting.
I can't modprobe module bcmdhd for wlan, because of an error.
modprobe bcmdhd
ERROR: could not insert bcmdhd: No such device

Amazing, I know, there is such a device;-)
[...]
I'm not using wifi so I didn't notice this before. Indeed it's not working and after a bit of research it seems I can blame the kernel for that
Quote:
WiFi will not work with latest sunxi-3.4
-- http://linux-sunxi.org/A20-Cubietruck#Wifi

I tried building a vanilla linux-3.14-rc4 but it didn't boot. Maybe I'll have better luck with sunxi
 
  


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: Cubieboard2 open SBC ships, Cubietruck model revealed LXer Syndicated Linux News 0 06-27-2013 05:20 AM
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 10:54 AM


All times are GMT -5. The time now is 04:59 PM.

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