Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit
stuff along with the 64 bit stuff ?)
If you did that the update may have broken some of the 32 bit stuff and it
could lead you to a similar error.
ATB
David
Il Domenica 17 Novembre 2013 3:04, "openpand...@free.fr"
h
Things start going wrong right after the "calibrating delay loop":
[ 6.455145] Calibrating delay loop...
[ 6.460464] Unable to handle kernel NULL pointer dereference at virtual
address
I think that's the root cause ...
I'm not sure on this but I suppose the kernel aint looking at t
re 2013 11:51, Davide ha scritto:
Today I noticed that the linux-sunxi kernel has been updated in the usb host
section. Hopefully this will get all those dongles that work on the
stock android kernel functional on the linux-sunxi kernel too (currently only
some keyboard, mice and mass stora
Today I noticed that the linux-sunxi kernel has been updated in the usb host
section. Hopefully this will get all those dongles that work on the
stock android kernel functional on the linux-sunxi kernel too (currently only
some keyboard, mice and mass storage seem to work right).
I'll compile i
with a new kernel with propper usb host capabilities.
ATB
David
Il Lunedì 21 Ottobre 2013 15:54, Davide ha scritto:
The A10s should be amongs the supported devices that my image builder targets,
did you haveto do it a different way because it failed ?
Regards
David
Da: Michael
ng this on a flash device ... after all I'm
beginning to appreciate more the pros and accept the cons.
You might want to change the formatting in the script to best suit what you
prefer.
Regards
David
Da: Michael Balcos
A: Davide ; Slackware ARM port
I
The A10s should be amongs the supported devices that my image builder targets,
did you haveto do it a different way because it failed ?
Regards
David
Da: Michael Balcos
A: armedslack@lists.armedslack.org
Inviato: Lunedì 21 Ottobre 2013 3:54
Oggetto: [ARMedsla
I put in the wiki a workaround for any time the slackware installers do not
work on the PI ... it's below the links to the PI's community slackware links.
It does not feel like windows and you need to understand what you are doing
because cut and paste of the commands may not work if the rasbian
Ok I grabbed the boot stuff from rasbian (2013-09-10) and used the slackware
arm miniroot in a freshlu formatted and partitioned SD it boots (minor
issue complaining about root being already mounted rw ... probabbly need to add
ro to cmdline or edit the fstab).
ATB
David_
Oh ... I've been working in the same direction but have not got round to
finishing up.
Regards
David
Da: stanley garvey
A: Tom ; "armedslack@lists.armedslack.org"
; Davide ; Slackware ARM
port
Inviato: Venerdì 27 Settembre 2013 10
oot, to the standard
installer.
I have days when I do that multiple times a day, on different SD cards, using
different Pi boards (all model B some 256M some 512M versions) I deliberately
do it across multiple different boards, because I have to know it will work on
both.
Thanks.
Dave
---
ee if I want to try booting after the estimated 4 and 7 hour estimated
download time, that I've hadto restart over again because it got truncated and
resume does not seem to work.
ATB
David
____
Da: Tom
A: "armedslack@lists.armedslack.org"
Cc: Davi
Thanks ... I'll have a crack at that tomorrow.
Regards
David
Da: Tomasz Salwach
A: "armedslack@lists.armedslack.org"
Cc: Davide
Inviato: Giovedì 26 Settembre 2013 19:28
Oggetto: Re: [ARMedslack] A quick primer for the PI
Davide, I'
t the dude that lent it to me to lend me his
rasbian image ... maybe I can see where the difference is.
ATB
David
Da: "stan...@stanleygarvey.com"
A: Davide ; "dowe...@netscape.net" ;
"armedslack@lists.armedslack.org"
In
;stan...@stanleygarvey.com"
A: Davide ; "dowe...@netscape.net" ;
"armedslack@lists.armedslack.org"
Inviato: Giovedì 26 Settembre 2013 14:52
Oggetto: Re: [ARMedslack] A quick primer for the PI
Did you dd the image onto the card?
What suze of card?
Try the installer imag
g.
The files I use to boot to the installer are available here
http://www.dowelld.net/?p=49 the txt file explains how I use them.
Thanks
Dave
-Original Message-
From: Davide
To: stanley garvey ; dowelld ;
armedslack
Sent: Thu, Sep 26, 2013 1:38 pm
Subject: Re: [ARMedslack] A qui
ATB
David
Da: stanley garvey
A: "dowe...@netscape.net" ;
"armedslack@lists.armedslack.org" ; Davide
; Slackware ARM port
Inviato: Giovedì 26 Settembre 2013 13:15
Oggetto: Re: [ARMedslack] A quick primer for the PI
On Sep 26, 2013 08:25 "Davide&qu
>>I got a friend to lend me a PI for a week ...
>>I had a quick look at the community links for slackware on the PI but none
>>really tell me what i want to know:
>>what does the GPU look for in the SD ? (as fas as I know it's the GPU that
>>loads stuff from SD into memory and then passes c
ernel.img, start.elf,
bootcode.bin, cmdline.txt and optionally a config.txt which is used to overide
defaut settings.
--Original Message--
From: stan...@stanleygarvey.com
Sender: ARMedslack
To: Davide
To: Slackware ARM port
ReplyTo: stan...@stanleygarvey.com
ReplyTo: Slackware ARM port
Subject: Re:
I got a friend to lend me a PI for a week ...
I had a quick look at the community links for slackware on the PI but none
really tell me what i want to know:
what does the GPU look for in the SD ? (as fas as I know it's the GPU that
loads stuff from SD into memory and then passes control to it
>>> It appears that the usb driver in the linux-sunxi kernel is bust (at
>>> least on A1X based devices) and I don't think that there is any chance
>>> of them fixing it any time soon. I even downloaded the 3.0 stable
>>> version sources hoping that at least their stable version (as opposed to
>>>
>> It appears that the usb driver in the linux-sunxi kernel is bust (at
>> least on A1X based devices) and I don't think that there is any chance
>> of them fixing it any time soon. I even downloaded the 3.0 stable
>> version sources hoping that at least their stable version (as opposed to
>> the
this as s soft phone option @ work and
hadto go with ekiga, but I can't recall why)
ATB
David
Da: "openpand...@free.fr"
A: Davide ; Slackware ARM port
Inviato: Venerdì 20 Settembre 2013 21:21
Oggetto: Re: [ARMedslack] Skype on ARM linu
I'll begin my stating that I do not consider Android as having much to do with
ARM linux.
This this in mind what are the alternatives, if any, for having skype on ARM
linux ?
Is there some other instant messaging client (chat and video capable) that is
knows to work well on ARM linux ?
I read
It appears that the usb driver in the linux-sunxi kernel is bust (at least on
A1X based devices) and I don't think that there is any chance of them fixing it
any time soon.
I even downloaded the 3.0 stable version sources hoping that at least their
stable version (as opposed to the 3.4 develope
>Hi !
>I would like to buy a plug-like computer (small form, not especially
>wall-charger type) and also an ARM laptop.
>It's for a very common usage, internet, video chat, etc.
>Can you guys recommend me some products/websites ?
A lot depends on what you want out of your plug like computer
I've found that after ethernet module is loaded the link status in not reliable
until the interface has been brought up for at least a few seconds.
I often use my laptops both in presence and absence of DHCP servers. I found
the default way that the script detects the link status unreliable so I
I've figured out the touchscreen hardware (FocalTech ft5x TouchScreen) and
there's a driver for it in the linux-sunxi kernel source fork (ft5x_ts).
I've had a very partial success using it as it really could do with a
calibration:
Anyone have any idea how to go about it ?
Regards
David
_
> I have release 13.37 according to /etc/slackware-version.
> I have recenly discovered that my mutt package has been downgraded,
> and I don't understand how/why.
>>
mutt in 13.37 was last touched in 2010.
However, armedslack-13.1 has
armedslack-13.1/slackware/n/mutt-
>>> I have release 13.37 according to /etc/slackware-version.
>>> I have recenly discovered that my mutt package has been downgraded,
>>> and I don't understand how/why.
>> mutt in 13.37 was last touched in 2010.
>> However, armedslack-13.1 has
>> armedslack-13.1/slackware/n/mutt-1.4.2.3-arm-1
>
Sorry mixing html and standard ">" indentation on yahoo means a lot of manual
editing.
Taking the ordinary slackware miniroot to one with compiler is really just a
matter of installing some packages (in the d and l series ). I often do that on
a live system just after having gotten networking a
>> > I noticed RPi patches also not making it into kernel.org. Last weekend
>> > I tried to compile a generic 3.10.1 kernel for the RPi and it failed
>> > to boot. Rather than patch kernel source for a specific ARM target,
>> > are we expected to use the generic kernel and build a device tree
>> >
>> I haven't got a a20 (or earlier) device to play with (yet), but I am
>> forwarding this email to arm-netbook. I hope this will raise interest
>> of having Slackware on the Allwinner.
>I am preparing a generic armv6 and onwards Linux 3.10 kernel (the
>separate 'kirkwood' and 'versatile' kernel
I got round to syncing my new image builder:
http://ftp.slackware.org.uk/slackwarearm/people/louigi600/
Touchscreen is still not working on my device ... but if your touchscreen is on
the usb bus chances are that it will work.
Have fun
David
Da: Davide
A
> just been to kernel.org to see if the raspberry pi is supported. I see
> no support for the device in any kernel previous to 3.10.1 which
> includes support for the BCM2835. I find this odd. I would have thought
> that patches would have been submitted and merged in the the kernel
> tree. We
My new image builder for the xzpad700 (as soon as I've time to sync it) will
prepare images for all the hardware that the fedora currently supports
(including the new A20 socs). as a matter of fact I\m using their bootloader
and their kernels until I get round to building my own kernel.
Incide
>>>http://arm.slackware.com to point to it.
>>>I don't think I need to be the custodian of the support matrix. If you
>>>want to go ahead and create the page on docs.slackware.com, go ahead and
>>>let me know once it's done.
>> That's exactly what I was trying to say. Different story if you wan
>> > Stuart: what do you think about adding it to the list along with the
>> > AC100, Pandora and Pi ?
>How's about the 3rd party device support page is moved on to the ARM
>section of docs.slackware.com, and I change the link on
>http://arm.slackware.com to point to it.
>I don't think I need to
If the phone is an A1x based SOC there's chance that you can get started really
quickly by reusing info on how I got Slackware arm on my XZPAD700 tables (that
is a A13 based SOC). There's still work to do like the touchscreen and figuring
out what kind of X server will work (probably a frame-buf
>> Well actually on my live slackware 14 (x86) vi is a link to elvis
>>
>> Although both are installed, by default vi is linked to elvis (and it's
>> not something I did manually). looking at the sizes I cannot but agree
>> that on the miniroot vim is just eating up space (just guessing that th
>I got the kernel loading from uSD but then kernel panic because uboot passes
>wrong root device to kernel.
>http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet
>I discovered that I cannot have the serial console if I boot feom uSD so I
>need some other means of manip
I got the kernel loading from uSD but then kernel panic because uboot passes
wrong root device to kernel.
http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet
I discovered that I cannot have the serial console if I boot feom uSD so I need
some other means of manipulatin
I downloaded the rescue image from
http://www.hamletcom.com/docs/XZPAD700_microsd_restore_B.zip
and I found some evidence that the device uses u-boot. I'm not sure if the
u-boot image I found in the rescue image is part of the image that gets
restored into the device or if the rescue image it
I got tempted with one of these.
Integrated BGN wifi
1 usb client/host port qith support for external usb devices (is
ethernet/3G
)
4Gb internal flash (but I've only found
evidence of 3Gb maybe 1Gb is
reserved for boot/rescure/emergency restore)
7
>Kernel.org was hacked in 2011. But I think that the segmentation faults come
>from dodgy Android code. Has anybody read a dmesg on an Android device? >I can
>post one if nedeed. It's a mess!
It's not from an ARM device I'm getting those errors, I actually have not
noticed it there yet, they'r
>> Hello!
>> It's possible. But not unlikely. The other question is when was the
>> Kernel site hacked?
>It was ages ago - in 2001!
Unlikely 2001 back then we only had 2.4 stable kernels more like 2010
>Chances are that your installation has installed something dodgy,
>or you may even ha
>>> Hello!
>>> Earlier today I had my Slackware (on Intel) system uninstall system.
>>> Its installer removal program told me that I'd need to log out and log
>>> back in before there would be any changes seen. Well I did that. On
>>> logging back in I saw that the process had eaten the prompt.
>>
>> I got tempted with one of these.
>>
>> Integrated BGN wifi
>> 1 usb client/host port qith support for external usb devices (is ethernet/3G
>> )
>> 4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is
>> reserved for boot/rescure/emergency restore)
>> 7" screen 800x480 px
>
I got tempted with one of these.
Integrated BGN wifi
1 usb client/host port qith support for external usb devices (is ethernet/3G
)
4Gb internal flash (but I've only found evidence of 3Gb maybe 1Gb is reserved
for boot/rescure/emergency restore)
7" screen 800x480 px
single core cortex A8 (no
>> >Eric suggested that that would be a good place to start from so I took his
>> >advice but if we
>>> gather up all the ARM specific stuff together it would be nice too.
>> >Well whatever ... I'll be a good lamb and follow the flock :-D
>OK. I'll think about it. A separate ARM section
>> >Eric suggested that that would be a good place to start from so I took his
>> >advice but if we
>> gather up all the ARM specific stuff together it would be nice too.
>> >Well whatever ... I'll be a good lamb and follow the flock :-D
>OK. I'll think about it. A separate ARM section s
>>> http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az
>>>
>>> It was just a quick cut and paste with minor changes.
>>> I'll work on it to make it better and all comments are welcome.
>>
>>Would a separate ARM section be a good idea? It'd make content easier
>> http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az
>>
>> It was just a quick cut and paste with minor changes.
>> I'll work on it to make it better and all comments are welcome.
>
>Would a separate ARM section be a good idea? It'd make content easier to
>find
>>
>> Would http://docs.slackware.com or http://slackwiki.com be a good place
>> to put this in ? Regards David
>
>docs.slackware.com is the best place, IMO. alienBOB is keen to have more
>docs there! :-)
http://docs.slackware.com/howtos:hardware:slackware_on_the_toshiba_ac100_dynabook_az
It wa
>>> I changed the URL on http://arm.slackware.com/supportedplatforms/
>>> Once you've found somewhere else to host it, let me know.
>>
>>A cached copy is here:
>>http://web.archive.org/web/20120719012735/http://tosh-ac100.wetpaint.com/page/ARMedslack
>&
>> I changed the URL on http://arm.slackware.com/supportedplatforms/
>> Once you've found somewhere else to host it, let me know.
>
>A cached copy is here:
>http://web.archive.org/web/20120719012735/http://tosh-ac100.wetpaint.com/page/ARMedslack
>
>Davide, m
I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been
taken down thus braking the link for the information on how to get
slackware
arme on the AC100.
I'm trying to get the info from the wetpaint crew (at least the text I
wrote) to see if I can have
>> I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been
>> taken down thus braking the link for the information on how to get slackware
>> arme on the AC100.
>> I'm trying to get the info from the wetpaint crew (at least the text I
>> wrote) to see if I can have it hosted some
I noticed that the whole http://tosh-ac100.wetpaint.com/ thing has been taken
down thus braking the link for the information on how to get slackware arme on
the AC100.
I'm trying to get the info from the wetpaint crew (at least the text I wrote)
to see if I can have it hosted somewhere else.
Re
vnc client.
Regards
David
Da: Richard Lapointe
A: Davide ; Slackware ARM port
Inviato: Sabato 18 Maggio 2013 14:26
Oggetto: Re: [ARMedslack] tigervnc for slackware arm
Here one that I built but never tested.
http://dl.dropboxusercontent.com/u/90881870/tightvnc-
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
ARMedsla
slackware arm 14 userland (and has support for all features of the
goflex net )?
Regards
David
Da: Richard Lapointe
A: Davide ; Slackware ARM port
Inviato: Martedì 23 Aprile 2013 0:42
Oggetto: Re: [ARMedslack] getting SATA working on seagate goflex net
Maybe
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 fixe
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
A: Slackware ARM port
Inviato: Giovedì 18 Aprile 2013 13:42
Oggetto: Re
Yeah ... I realized just after having sent the first mail ... I was probably
typing something wrong without realizing and slackpkg was telling me there was
nothing to install because it was already installed :-D
Sorry for making a noise about my dyslexic typing on the keyboard lol.
David
___
>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
>> So I updated the uboot image with the install script (I did it by hand
>> the first time around and I;ll savemyself the trouble if possible) and
>> nor the kernel gets loaded properly. I still have an issue concerning
>> that the root filesystem on the usb stick is ext2 while the slackware
>>
d with the correct 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
A: Richard Lapointe ; Slackware ARM port
Inviato: Giovedì 18 Aprile 2013 8:48
Oggetto: Re: [
f without at least 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
A: Davide ; Slackware ARM port
Inviato: Giovedì 18 Aprile 2013 3:32
Oggetto: Re: [ARMedsl
>> 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'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 bo
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 doc
Bye
David
Da: Stuart Winter
A: Slackware ARM port
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, vi is broken looking
> for libpe
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
___
Merry Christmas and happy new year to everybody.
David___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
ll-new
probably things would have worked better.
Sorry for making a racket ... and hope this can save trouble to other people
updating.
David
________
Da: Davide
A: Slackware ARM port
Inviato: Venerdì 7 Dicembre 2012 15:09
Oggetto: Re: [ARMedslack] Updating to 1
whet installed to go on
with the upgrade process.
As soon as I'm done with the upgrading I'll try posting the udev error messages
and see if anyone can help me put it right.
Regards
David
________
Da: Davide
A: Slackware ARM port
Inviato: Venerdì 7 Dicembre 201
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
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
A: Slackware ARM port
Inviato: Venerdì 23 Novembre 2012 11:47
Oggetto: Re: [ARMedslack] fltk
>
I neaded it to build GEBC (Gnu Exterior Ballistics Calculator) on my Slackware
ARM netbook.
If you like I can give you that package too and add that to the misc too ? (it
requires libharu to build but it appears to be linked static ... ldd shows
nothing about that).
Regards
David
__
Anyone know where to get an arm binary for fltk-1.1 that also works on
Slackware ARM 14 ? ___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/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:
>ttps://plus.google.com/u/0/109993695
Thanks for all the effort you've been putting into ARM slackware port over the
years.
David
Da: Stuart Winter
A: Slackware ARM mailing list
Inviato: Venerdì 28 Settembre 2012 23:53
Oggetto: [ARMedslack] Slackware 14.0 is released
Hi!
Slackware x86, x86_
>> For information, QEMU user-mode doesn't require any "guest" kernel
>> since all privileged operations are redirected to the "host" one.
>You assume that everybody uses Linux on PC as a host. If you use
>Windows for example you need full system emulation.
I just could not resist ... this is j
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
A: Slackware ARM mailing list
Don't forget to update the mirror list in slackpkg for the upcoming current
packages ;)
Regards
David
Da: Stuart Winter
A: Slackware ARM port
Inviato: Sabato 25 Agosto 2012 23:30
Oggetto: Re: [ARMedslack] Slackware ARM "current" directory name is being
cha
>> Has anyone yet tried running Slackware ARM on any if the
>> ARM emulators, like ArcEm, SkyEye or Simit?
>> If so I'm curious to learn roughly how many instructions
>> per second are being reported.
>use QEMU
>-mike
Yeah there is some documentation on how to get going pretty fast with qemu on
>>> 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 g
>> 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 load
I had a slimmed version of the mini root working on the dockstar (that
initially ran on an external usb flashdisk untill I slimmed it enough to fit in
the docstar) ... but I subsequently spent a lot of time on an old project I had
back 2004 (Clash). Currently my dosckstar runs on that but if you
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:
>>
>> http://blogs.adobe.com/flashplayer/2012/06/flash
>>> 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
>>> 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 fo
>> 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 becaus
>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
>appli
>>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/com
>> 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
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 stil
>> 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.
>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:
1 - 100 of 240 matches
Mail list logo
