use to pass boot
options like
the ones needed in installer method of #3 above. The
rescue system get
installed on the on-board flash and will boot if
there are no bootable usb.
Hope you find this helpful
Rich
On 03/13/2011 01:13 AM, Davide wrote:
Hi,
my name is David and I'm
4) You mentioned just renaming kernel and initrd: is
that part of what
needs to be done to boot from usb ?
4 depends on the boot loader you are using and if you use
the pre-configured
boot commands.
I'm using this:
After some research I foud a listing of the trace out of some unused features
of the dockstar's SOC.
It's in German but Google translate makes it readable :-)
http://www.mikrocontroller.net/articles/Dockstar#PIN-Forschung
Pity that my software RAID1 vision on the 2 sata ports went into fumes !
4) You mentioned just renaming kernel and
initrd: is
that part of what
needs to be done to boot from usb ?
4 depends on the boot loader you are using and if
you use
the pre-configured
boot commands.
I'm using this:
I look like it replaces the original uboot on mtd0, is
that correct ?
I'm not sure anymore. I would have to investigate the
script again first.
While openwrt is using original uboot to start another
version so that if
you screw up you still have the original one to get
things
Some hints:
Create first partition as fat on usb stick, second
partition as ext4. The
first will be the boot partition and contain your uImage.
usb start
ext2load usb 0:1 0x640 /uImage
setenv bootargs root=/dev/sda2 rootfstype=ext4
run bootcmd
Something like this...
Cool this
@lists.armedslack.org
Data: Mercoledì 16 marzo 2011, 14:29
Am Wednesday 16 March 2011 13:45:53
schrieb Davide:
Yes, that's possible. AFAIK you just have to
place the
second u-boot to the
NAND address where originally the kernel can be
found. If
it fails to load
the second u-boot the first
On now that I've the basics going I'm now moving to the wireless part.
My armedslack dockstar wants to become access point but none of the usb wifi
dongles I have seem to work currently in master mode.
Today I brought a new one d-link g122 that should have been rt73 ... but the
one I got was
.
If I notice any other odd stuff I'll update on this.
Regards
David
--- Mar 19/4/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: Re: [ARMedslack] jeff Doozan's uboot
A: Slackware ARM port armedslack@lists.armedslack.org
Data: Martedì 19 Aprile 2011, 14:14
Now that I've a developement environment I'll be replicating what I did with
miniroot to get ap/3G/nas/router on a minimal busybox based environment.
As usual I'll leave a slackwareish feeling environment to the system.
Once I get it working this could be an alternative emergency rescue for those
Now that I've a developement environment I'll be
replicating what I did
with miniroot to get ap/3G/nas/router on a minimal
busybox based
environment.
So you have a Slackware system with busybox instead of the
GNU tools? How much
space saves this?
I'd stripp all that is not needed.
If you considet that you can get a dockstar for 50 Euro in Italy or possibbly
less it you look world wide ... this little wimpy nas had better cost no more
then 25 Euro or I'd just buy a dockstar instead. I know that it's infuriating
that the prices went up from 36 euro to 52 euro but for what
Sorry for starting a new thread on something that was started elsewhere
but maybe the shoot-off needs better attention with a new thread.
This is a mix of a few I built myself and some gotten from current.
This is what I'll be working with and should fit in a compressed
jffs2 image 64Mb
While going about recompiling kernel for micro root I noticed a few things that
one can do without at least for kirkwood:
Fusion MPT device support
(this is a hardware RAID SCSI controller ... I doubt anyone will ever
have one connected to an ARM based embedde system even if a working
If anyone else finds this handy this works with dhcp client on both host and
guest and also gets rid of all rc.local requirements.
On the guest os you will need to config interface once system is up (static or
via dhcp)
Needs fixing for static ip reconfiguration/rerouting on host system after
quite interested in it because I'm still thinking about
building
armedslack for armv5te (it's armv4 at the moment).
We need some valid test cases.
On Sat, 30 Apr 2011, Davide wrote:
I'm interested in the recompiling glibc thing to
regain speed on specific hardware: has this been discussed
This is probably not the cause of your problems but it's something you want to
keep in mind anyway:
Running non flash oriented journaled file-systems on flash based devices can
ware them out very quickly especially if you are using MLB flash based device
with a typical 1 cycle rewrite
It's often handy to know the physical offset of the first partition of a qemu
raw disk image.
If you do not use raw images you can convert it to raw ... do what you need and
convert it back.
I've not yet found a reliable way of mounting non raw images from ordinary
linux OS.
You can use this
Ok this is a little off topic but since I'm trying to make it look as close as
possible to a slackware system I thaught it could fit here anyway.
Although I did my best to adapt all the scripts around /etc/rc.d and /lib/udev
to work correctly with busybox (sh and slightly different PATH): udev
in the source or is it in some script ?
Regards
David
--- Lun 9/5/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: [ARMedslack] Trouble with udev on busybox based system
A: armedslack@lists.armedslack.org
Data: Lunedì 9 maggio 2011, 07:41
Ok this is a little off
Could not grep modprobe in the udev scripts nor in the binary (with the aid of
strings) ... so I looked in the rules.d and there it was.
But busybox modprobe does not support blacklists ... hope it won't hurt.
Regards
David
--- Lun 9/5/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide
--- Lun 9/5/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: [ARMedslack] R: R: Trouble with udev on busybox based system
A: Slackware ARM port armedslack@lists.armedslack.org
Data: Lunedì 9 maggio 2011, 08:42
Could not grep modprobe in the udev
scripts nor
what this should load because there is no module named
just usb and I can't find any alias with that either.
--- Lun 9/5/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: [ARMedslack] R: R: R: Trouble with udev on busybox based system
A: Slackware ARM port
I did a little fiddling with jeff's uboot environment setup and changed it so
that it looks for a bootable partition in the firs 7 usb drives.
This allows you to have your linux install on different partitions.
Just 3 conditions must be met:
1) the linux install partition must have everything
evident that a lot of work on this arm clashNG
comes right out of armedslack. If anybody feels about this just tell me the
correct level of evidence and I'll show it up.
Regards
David
--- Ven 6/5/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: [ARMedslack] R: R
If anyone likes to try it tarball containing /boot /lib/{firmware/modules} is
available on sourceforge:
http://sourceforge.net/projects/bclash/files/clashNG/ARM/kernel-kirkwood-2.6.38.7-arm.tgz/download
Be warned that I removed some stuff that I regard as not being necessary for
clashNG. I
Nice but the price ... for crying out loud you can but 2 Toshiba a100 netbooks
for that price !
--- Mar 28/6/11, Geoff Walton ge...@ohdoughnut.com ha scritto:
Da: Geoff Walton ge...@ohdoughnut.com
Oggetto: [ARMedslack] Open Pandora
A: Slackware ARM port armedslack@lists.armedslack.org
Data:
My last day at the old work the work mate gave me a Toshiba AC100 as a present
(one of those nvidia tegra dual core arm based netbooks with android): how do I
put armedslack in this thing ?
Regards
David
___
ARMedslack mailing list
Hum well I can do with the ordinary fluxbox as long as the touchpad works.
I could even accept to run on it a framebuffer kdrive as xserver as long as I
can have an ordinary linux distribution on it (possibly slackware or slackware
based).
The real questions are:
do I haveto stick with the
(BST)
schrieb Davide louigi...@yahoo.it:
I'm worried about binary compatibility as armedslack
binaries will run on almost any arm platform but that
does not mean
they will run on every arm platform.
They are built for armv4 and the Tegra should be at least
armv6 so they
should run
Like the Toschiba AC100 it's a arm7 instruction set machine so it should run
instruction set ARM4 with consequent performance loss.
So armedslack userland should run on that hardware: all you need is means to
boot custom kernel and last but not least a custom kernel that can run
armedslack
I know it's not the correct place for this but since it's ARM hardware maybe
I've a little audience here.
I'd sell off a Zaurus C760 and C860.
Anyone intrested can email me privately about this.
Sorry for disturbing.
David Rao
___
ARMedslack mailing
Non so se ti hanno rispost a soddisfazione comunque lo scopo e'
universalmente:
inizializzare l'hardware affinche si possa caricare in ram un kernel dalle
periferiche a disposizione per poi passare il controllo al kernel.
Avevo scritto una cosa interessante a riguardo dello zaurus e il
Regarding the keyboard: have you checked whether all the necessary modules were
loadad by /etc/rc.d/rc.modules ?
some modules may not get autoloaded automatically.
Regards
David
Da: lee jones slothp...@gmail.com
Oggetto: Re: [ARMedslack] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz)
A:
] Armedslack on the Efika i.MX515 (ARM Cortex-A8 800MHz)
A: Slackware ARM port armedslack@lists.armedslack.org
Data: Giovedì 1 settembre 2011, 13:51
On Thu, Sep 1, 2011 at 9:10 AM, Davide louigi...@yahoo.it wrote:
Regarding the keyboard: have you checked whether all the necessary modules were
loadad
I thaught the guy was using efika specifik cernel from some other source ... so
that the just could be loaded manually. Mut maybe I undestuud wrong.
If you are compiling your own kernel for that hardware make sure you apply all
the necessary patches that are not in the vanilla kernel upstream
I got round to doing some testing with an ubuntu kernel (2.6.38.1). With this
kernel I was able to get the basics working chrooted.
There are still some issues with kernel even with all the AC100 specific pathes
applied:
no sound,
keyboard/touchpad often reset and sometimes crash in a way that
Put this in a google search bar: Logitech Squeezebox Touch hack ... did not
look at the content but it looks like there are communities for this hardware.
Regards
David
--- Gio 1/9/11, Thorsten Mühlfelder thenk...@gmail.com ha scritto:
Da: Thorsten Mühlfelder thenk...@gmail.com
Oggetto:
/mmcblk0p7 (the onboard big partition).
Regards
David
--- Dom 4/9/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: [ARMedslack] Armedslack on the AC100
A: Slackware ARM port armedslack@lists.armedslack.org
Data: Domenica 4 settembre 2011, 10:48
I got round to doing
...@lin2go.com ha scritto:
Da: Manfred Müller manfred.muel...@lin2go.com
Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100
A: armedslack@lists.armedslack.org
Data: Domenica 4 settembre 2011, 19:36
Hi Davide,
(EE) Failed to load module fbdev (module does not
exist, 0)
...I can't seem
I should read messages from the top down :-D
Ok I'll be installing that later.
Thanks
David
--- Dom 4/9/11, Stuart Winter m-li...@biscuit.org.uk ha scritto:
Da: Stuart Winter m-li...@biscuit.org.uk
Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100
A: Slackware ARM port
of terminal though.
So I've still an issue as to why there are no ptys in /dev.
Anu ideas how to fix this ?
Regards
David
--- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100
A: Slackware ARM port
wrong.
To temporarely work around the problem I commented the check and blind make and
mount /dev/pts in rc.udev.
Regards
David
--- Lun 5/9/11, Davide louigi...@yahoo.it ha scritto:
Da: Davide louigi...@yahoo.it
Oggetto: Re: [ARMedslack] R: R: Armedslack on the AC100
A: Slackware ARM port
While looking for Flash plugin for ARM linux I found this:
http://www.ti.com/tool/adobeflash-a8
Not sure if there is an easier way to get Flash plugin on ARM linux.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
This happens on my AC100 running armedslack 13.37 (updated a few days
ago).
Any idea how to fix this ?
Not yet. Are you running it locally or via VNC ?
I can't replicate this on -current running X on the console (locally -
video, kb, mouse). xlock asks for a key, locks and then
2011 15:49
Oggetto: Re: [ARMedslack] Flash Plugin for ARM
On 6 September 2011 11:41, Davide louigi...@yahoo.it wrote:
Is anyone aware of easier ways of getting flash plugin for linux on ARM ?
How about gnash or any of the opensource alternatives ?
I have seen on the power developer website
I remember that I specifically disabled old ABI support on my kernel build. Not
sure if android bins are eabi or old abi. Mayby someone can try this out on an
old abi enabled kernel ?
Da: Davide louigi...@yahoo.it
A: Davide louigi...@yahoo.it; Slackware ARM
for some other reason.
Da: Stuart Winter m-li...@biscuit.org.uk
A: armedslack@lists.armedslack.org
Inviato: Mercoledì 14 Settembre 2011 15:10
Oggetto: Re: [ARMedslack] Flash Plugin for ARM
On Wed, 14 Sep 2011, Davide wrote:
That's not correct: AC100 has a tegra2
I know I'm not the right Dave :-D
I thought that google would have the answer for this bit apparently there's no
correct answer:
I got this as an intresting hit form Jeff Doozan's forum
There is no common arcNumber:
- iomega uses 1682
- OpenWRT uses 2870
- Debian asm/mach-types.h does not
The other day I installed mplayer on my AC100 ... but the video playback was
desparately slow.
I'm not sure if it's the Framebuffer X or some other issue ..
Just guessing: most likely some proprietary video card binary blob
that doesn't come with Slackware but comes with the default OS
I'll try ... I'm already using ununtu kernel sources to get a working
kernel. I'll surf around ubuntu forums and what more on this then.
Nowadays video card modules are in xorg not (only) in kernel modules.
Grep your /var/log/Xorg.0.log for not found.
root@slackware:~# grep -i not found
Way back in 2006 I had a working xmame for my Z that even if a little slowly it
worked.
Since then xmame has been dropped and original mame now builds on unix.
I've built mame0143 on my x86 linux pc but I've had no luck on ARM.
The old xmame sources build but produce a binary that complains
Have not yet fiddled with new 3.x.x kernels yet but experience forced me to be
carefull wneb copying .config's across releases.
Using 2.6.38.1 config on 2.6.38.x was possible but using 2.6.38.x confin on
2.6.39.x would produce unexpected results. (38 and 39 ar just examples coz I've
forgotten
.
Da: Jim Hammack hamm...@gotslack.org
A: armedslack@lists.armedslack.org
Inviato: Giovedì 9 Febbraio 2012 16:20
Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug
Davide,
I'm not sure what you mean by erasing the partition. I am
using these commands taken from
to point to the repository you wish, and run slackpkg
update ... from there getting the rest will be very easy and fast when you
need it:
slackpkg install package base name
or even get prompted for a wole set of packages
slackpkg install n
Have fun
Davide
Da
Looks like you've no resolver configured. Is your /etc/resolv.conf i empty ?
Also google might regect mail coming directly from your host ... you might like
to configure your ISP mail relay as SMART HOST in sendmail.mc ... and
subsequently make clean , make all in the sendmail config directory.
I'd bet on ro missing on cmdline.
--
Il dom 8 apr 2012 10:21 CEST, Stuart Winter ha scritto:
What does this output?
cat /proc/cmdline
If this is the case, go into u-boot and do:
printenv
and match the values found in /proc/cmdline and you should be able to
I've no idea whether the installer works directly on that platform, but you can
get the miniroot working as long as you have a working kernel for the hardware.
Look at the bottomb section in the supported platforms ... there is a paragraph
on unofficially supported platforms. Look at them to get
But tbh I'm not sure whether I want to support this device officially
(in-tree) because the RPi doesn't support initrds which means potentially
a big change to how I build the kernels and modules packages;
In my experiments with ARMedSlack on a Seagate DockStar, I remember
using a mkboot
I've no idea whether the installer works directly on that platform,
but you can get the miniroot working as long as you have a working
kernel for the hardware.
Look at the bottomb section in the supported platforms ... there is a
paragraph on unofficially supported platforms. Look at them
AC100 uses tegra chipset. I wonder how much work would it take to add the other
bits and pieces to the armedslack kegra kernel to make it usable on the AC100.
Regards
David
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
AC100 uses tegra chipset. I wonder how much work would it take to add
the other bits and pieces to the armedslack kegra kernel to make it
usable on the AC100.
root@pepa:~/ac/source/k/configs# grep AC100 config-tegra
root@pepa:~/ac/source/k/configs#
I checked in menuconfig and couldn't see
AC100 uses tegra chipset. I wonder how much work would it take to add
the other bits and pieces to the armedslack kegra kernel to make it
usable on the AC100.
root@pepa:~/ac/source/k/configs# grep AC100 config-tegra
root@pepa:~/ac/source/k/configs#
I checked in menuconfig and couldn't see it
Looking at teh config I think this would need to be enabled fro the
AC100/dynabook AZ
# CONFIG_MACH_PAZ00 is not set
This looks like : http://cateee.net/lkddb/web-lkddb/MACH_PAZ00.html
Might also be necessary to enable some grafix hardware like:
CONFIG_FB_NVIDIA
And here are some other bits
Yeah I had a build faliure too
And here are some other bits and pieces that might be necessary:
CONFIG_MMC_SDHCI_TEGRA
This one won't build as a module and I can't compile it into the kernel as
I build the main MMC support as a module (which I'm not changing).
Yeah I had a build faliure too.
And here are some other bits and pieces that might be necessary:
CONFIG_MMC_SDHCI_TEGRA
This one won't build as a module and I can't compile it into the kernel as
I build the main MMC support as a module (which I'm not changing).
I've been fiddling with 3.4.3 but all the builds I'm doing
The fbdev driver probably needs rebuilding.
I won't be pushing out any updates to -current for probably 2-3 weeks from
now, so you'll need to see if you can fix it by recompiling the fbdev
driver.
Yea that thing about version 8 and 12 looked like build incompatibility of some
sort but I
BTW: can I bug you trough any instant messangers (like skype, facebook, gtalk,
icq or anytning that is supported by IMO) ?
I promis to limit myself to only be slightly more annoying thet via email :-D
Ciao
David___
ARMedslack mailing list
Try this:
http://armed.slackware.com/test/xf86-video-fbdev-0.4.2-arm-4.tgz
Thanks X now starts but I have no mouse/keyboard response.
Looking at the Xorg log it looks like there are more version mismatches on the
input (evidev).
I did remove and re-install the server and input drivers too:
This is the driver that's making the errors show on the log:
evdev_drv.so
Try this:
http://armed.slackware.com/test/xf86-input-evdev-2.7.0-arm-1.tgz
Thanks man ... now my X is starting again. Now I can play with firefox13.
This had failed a build and hadn't been updated since 2011.
Has anyone got a working version of libflashplayer.so for armedslack ?
I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so
but I was unable to get it to work.
I also tryed this:
http://ac100.wikispaces.com/file/view/libflashplayer.so/284969210/libflashplayer.so
but it's
I tryed this: http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so
but I was unable to get it to work.
Did you see why it broke?
LoadPlugin: failed to initialize shared library
/usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open
shared object file: No such file or
LoadPlugin: failed to initialize shared library
/usr/lib/mozilla/plugins/libflashplayer.so [libGLESv2.so: cannot open
shared object file: No such file or directory]
root@pepa:~# ldd /usr/lib/mozilla/plugins/libflashplayer.so | fgrep not
libGLESv2.so = not found
Finding/compiling that
I've dropped this into /usr/lib/mozilla/plugins:
http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so
And firefox about:plugins now says:
===
Shockwave Flash
File: libflashplayer.so
Version:
Shockwave Flash 10.1 r120
MIME Type Description Suffixes
available in source code I don't see why people can assume one can
just drop libflashplayer.so for Android and expect it to work and even
if it did you'd open a can of worms.
It does work - I tested it. I suspect it doesn't work for Davide because
the library is compiled for a CPU higher
available in source code I don't see why people can assume one can
just drop libflashplayer.so for Android and expect it to work and even
if it did you'd open a can of worms.
It does work - I tested it. I suspect it doesn't work for Davide because
the library is compiled for a CPU higher than
It is a can of worms. It is closed source and lets hope it's finished.
Adobe don't fully support it and have publicly said so.
I think it's much worse then a can of worms. I really don't understand why
people use flash for things that do not need flash:
why the hell should one use flash for
It is a can of worms. It is closed source and lets hope it's finished.
Adobe don't fully support it and have publicly said so.
Yes, Adobe has officially end-of-lifed Flash Player on Android:
What else could it be ?
Dunno but you can try with the new -current updates once I push them out
this week.
Last Saturday I did an update yo current again but I still can't get
libflashplayer to load on firefox.
Maybe I'm missing something else that's not showing as error when firefox loads
Last Saturday I did an update yo current again but I still can't get
libflashplayer to load on firefox.
Maybe I'm missing something else that's not showing as error when firefox
loads plugins.
Can you give me the output of ls /var/log/pasckages on the system where
you got libflashplayer
I still find qemu useful when I want to test something out amd that qould be
emulating ARM from x86 hardware.
I know arm hardware is cheap nowadays ... but qemu is cheaper and no need to
wait for shipping ;)
Da: Stuart Winter mo...@slackware.com
A: Slackware
Thanks for all the effort you've been putting into ARM slackware port over the
years.
David
Da: Stuart Winter mo...@slackware.com
A: Slackware ARM mailing list armedslack@lists.armedslack.org
Inviato: Venerdì 28 Settembre 2012 23:53
Oggetto: [ARMedslack]
Does anybody know which ARM processor it has and if it can potentially
run Slackware ARM in a proper and easy way?
Olof Johansson has just posted a way to install an alternative Linux
distro on the new Chromebook:
Forgot the important thing: thanks a million Stuart.
I'd been trying to compile 1.1.6 that just did not build on my ARM netbook.
Thanks
David
Da: Stuart Winter m-li...@biscuit.org.uk
A: Slackware ARM port armedslack@lists.armedslack.org
Inviato: Venerdì 23
I'm thinking of updating to 14.0 on my AC100 (that unfortunately still runs on
ubuntu based kernel ... that I learn is actually a fork of chromeos kernel) ...
Will things like udev break un kernel 2.6.28 ?
Anyone think of anything else I should watcout for ?
Regards
David
things would have worked better.
Sorry for making a racket ... and hope this can save trouble to other people
updating.
David
Da: Davide louigi...@yahoo.it
A: Slackware ARM port armedslack@lists.armedslack.org
Inviato: Venerdì 7 Dicembre 2012 15:09
Oggetto: Re
Merry Christmas and happy new year to everybody.
David___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
I noticed that in the miniroot, both current and 14, vi is broken looking for
libperl and libpython .
I know most of you will like to use nano ... but I'm an old fart and I still
like vi !!!
It can be fixed by installing a few packages:
perl-5.16.1-arm-1.tgz
python-2.7.3-arm-2.tgz
Da: Stuart Winter m-li...@biscuit.org.uk
A: Slackware ARM port armedslack@lists.armedslack.org
Inviato: Lunedì 15 Aprile 2013 17:52
Oggetto: Re: [ARMedslack] miniroot 14 and current: vi is broken
On Mon, 15 Apr 2013, Davide wrote:
I noticed that in the miniroot, both current and 14
I'ts been a while since I last fiddled with the seagate dockstar ... I puklled
it back out wanting to involve it on media streaming via DLNA.
I fiddled with a slackwarearm 14 miniroot image on a versatile emulated machine
untill I thaught I had all the bits and pieces needed to boot from the
I'ts been a while since I last fiddled with the seagate dockstar ... I
puklled it back out wanting to involve it on media streaming via DLNA.
I fiddled with a slackwarearm 14 miniroot image on a versatile emulated
machine untill I thaught I had all the bits and pieces needed to boot from
Uncompressing Linux... done, booting the kernel.
And that's it ... nothing more on the serial console and nothing on the
network actually it does not even appear to mount the root
filesystem as the last mount seems to be coherent with the last time I
mounted it on my PC Do I need to
a serial cable suitable for the target
platform is difficult to say the least ... at some stage I plan to start using
jtag too ;)
Da: Richard Lapointe richard.lapoi...@gmail.com
A: Davide louigi...@yahoo.it; Slackware ARM port
armedslack@lists.armedslack.org
fstype ... maybe I just need to recheck how I pass boot
parameters to kernel from uboot when I detect a valid usb stick !
Regards
David
Da: Davide louigi...@yahoo.it
A: Richard Lapointe richard.lapoi...@gmail.com; Slackware ARM port
armedslack
One thing I noticed is that u-boot-tools (fw_printenv ... ect) seems to be
missing from the slackware arm 14 repo ... I forgot where I got it from on
13.37 but on my old armedslack 13.37 it's installed:
u-boot-tools-2010.12rc1-arm-1
ooops ... maybe something wrong with me ... it's installed
Ok ... just wish to thank you all for the help. I now have slackware arm 14 up
and running on my dockstar and have moved my attention to compiling mediatomb
on it.
David
Da: Davide louigi...@yahoo.it
A: Slackware ARM port armedslack@lists.armedslack.org
I decided it was time to pull out the goflexnet and hook up two 2.5 sata
drives on it.
I've slackware arm 14 running on it but I can't seem to see anything like a
sata bus detected on my goflex net.
Do I need to do something on uboot ro enable sata before the kernel is started ?
I've also
it on a slackware arm 14 userland (and has support for all features of the
goflex net )?
Regards
David
Da: Richard Lapointe richard.lapoi...@gmail.com
A: Davide louigi...@yahoo.it; Slackware ARM port
armedslack@lists.armedslack.org
Inviato: Martedì 23 Aprile 2013 0:42
Can't seem to get tightvnc client to interoperate with the x0vncserver running
on my desktop.
I can find tigervnc package for x86 slackware ... anyone have an idea if
there's an ARM tigervnc package ?
Regards
David
___
ARMedslack mailing list
.
Regards
David
Da: Richard Lapointe richard.lapoi...@gmail.com
A: Davide louigi...@yahoo.it; Slackware ARM port
armedslack@lists.armedslack.org
Inviato: Sabato 18 Maggio 2013 14:26
Oggetto: Re: [ARMedslack] tigervnc for slackware arm
Here one that I built but never
1 - 100 of 137 matches
Mail list logo
