OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - Arch Linux ARM support => Topic started by: greguu on September 30, 2015, 11:49:07 pm
-
Hi,
this thread is about to get ALARM running on the C3x00 series.
We aim to provide a basic functioning console only ArchLinuxArm for C3x00.
No intention to support Xorg, Touchscreen and over-clocking at this stage.
NOTE : Please post in the new threads if you have questions / issue with kernel or rootfs.
GitHub HowTo : https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
GitHub Kernels : https://github.com/greguu/linux-4.4-cxx00/releases/ (https://github.com/greguu/linux-4.4-cxx00/releases/)
GitHub RootFS : https://github.com/greguu/alarm-zaurus-c3x00/releases (https://github.com/greguu/alarm-zaurus-c3x00/releases)
-
Thanks for sharing this....
If my work ever slows down and I have some time, I'd like to give this a try....
-
Hi daalnroti
I haven't used my C3000 in about 4 or more years but I'd like to make use of it again, mainly as a pocket SSH client. It seems better suited to that than my smartphone - with or without a BT keyboard - even if its specs are feeble in comparison.
I was excited to see you have got Arch running on the c3x00 as that is my preferred Linux distro/OS these days (I've been impressed with it on my BananaPi) but I was disappointed to read suspend doesn't work. I can live without X or the touchscreen but I'd definitely want to be able to suspend. Have you tried to get suspend to work? Which 3x00 model are you running Arch on?
Why kernel 3.11.3 vs a more recent one? Is that the last one that supports C3x00 devices?
My last (failed) attempt to get something runnng on my Z was Debian 7 IIRC. If I'm really out of luck with suspend under Arch with your kernel then I'm thinking I might try the latest OpenBSD. Have you tried Net or OpenBSD on the Z? Are there any other modern Linux distros we can run on the Z apart from Arch and Debian? I'd love to hear your thoughts.
Thanks
-
Hi danboid,
I'll let daalnroti chime in about Arch and suspend....somehow suspend always seems to be an issue this sort of thing I've found on other distros and devices....
As for OpenBSD, it has been the most active distro around here the past few years.....
See this thread for a fairly recent update....as well as other threads in that forum section..
https://www.oesf.org/forum/index.php?showto...mp;#entry281633 (https://www.oesf.org/forum/index.php?showtopic=34298&st=0&gopid=281633&#entry281633)
Mark
-
Thanks ArchiMark!
I'm going to try installing OpenBSD on my C3000 tonight. I've been wanting an excuse to run BSD somewhere - I'm currently waiting for FreeBSD to get released for my BananaPi. I tried PC-BSD and DragonFlyBSD on my laptop recently but the hardware support and performance as a desktop computer is crap compared to (Arch) Linux.I can see how ZFS is a big win for servers so I'm hoping to use that on my BPi, although you could say ZFS doesn't make as much sense without RAID.
I'm kinda surprised you kept your Z when you have a Pandora and you sold your Netwalker and N900. What has kept you using your Z (and reading these forums)?
I see hrw (ex-OZ / Angstrom dev) now works on ARM stuff for RedHat. I wonder what happened to Meanie?
I've just noticed I've been a user of these forums for almost a decade now! That's pretty scary in a way but also shows how cool the Z was that I still want to use it ten years on. I see you've almost entered your OESF teens Archimark!
-
Thanks ArchiMark!
I'm going to try installing OpenBSD on my C3000 tonight. I've been wanting an excuse to run BSD somewhere - I'm currently waiting for FreeBSD to get released for my BananaPi. I tried PC-BSD and DragonFlyBSD on my laptop recently but the hardware support and performance as a desktop computer is crap compared to (Arch) Linux.I can see how ZFS is a big win for servers so I'm hoping to use that on my BPi, although you could say ZFS doesn't make as much sense without RAID.
I'm kinda surprised you kept your Z when you have a Pandora and you sold your Netwalker and N900. What has kept you using your Z (and reading these forums)?
I see hrw (ex-OZ / Angstrom dev) now works on ARM stuff for RedHat. I wonder what happened to Meanie?
I've just noticed I've been a user of these forums for almost a decade now! That's pretty scary in a way but also shows how cool the Z was that I still want to use it ten years on.
You might want to read OmegaMoon webpage on OpenBSD install....while info is old, it still might be of some help...although there is (at least was...) Zaurus install info through OpenBSD related site..and readme file.....
Need to update my sig again.....I had a Pandora.....but sold it earlier in the year, as I've just been so busy with work the past few years, I haven't had the time I thought I would to play with little mobile computers.... I have been following the next-gen Pandora progress, the Pyra, and it is moving along quite well now. So, it will be available later this year or early next year....might get one just for fun....
I had sold my Z's a few years back, but then about a year ago, I read about OpenBSD on Z, so, got another one....played a bit with it when I first got it a year ago with Ubuntu, Debian, etc....then discovered that OpenBSD seemed to be a current distro option. Then early this year ran into some snags with making packages I wanted to use plus being busy with work, so haven't touched the Z since then....
Hadn't read the forums in almost 6 months I think, but got another email notification about a post the other day, so, while I was here, I checked on new posts and found this one...
Arch on Z would be great, but I'd want xorg, etc, so, don't think it will be option for me at this point....
Will be great to here if you have some luck with the latest OpenBSD....please post in one of the OpenBSD section threads we've had going with your experience...
As for Meanie, that is THE question......he just disappeared one day....although when I checked a few months ago, his Z pages were still up....best I can tell he was very busy with work and couldn't deal with Zaurus stuff and everyone pestering him for updates and questions....
Yes, you and I are some of the 'old-timers' here......those were fun times when the Z was still in production....just wish that Sharp had released a C4000 series with a slightly larger display, built-in wifi and a USB port.....that would have been great for me....
Mark
-
I'd heard about the Pyra. I might get one IF Imagination finally release a fully working Linux/X/Wayland driver, like they've said they would for the last decade or whatever it is. Otherwise, they should've gone for the Tegra K1 / X1 or an Adreno chipset supported by Rob Clarks Freedreno driver. My Pandaboard was always shit under X because the PVR drivers were absolute trash with no open alternative.
Funny to hear you ended up selling your Z's only to buy another a year ago! The C3000 was a crazy cool device when it got released. I got mine signed by RMS at a talk he did in Manchester a few years ago but unfortunately I chose a bad ink/pen and his sig got smudged.
I'll let you know how I get on with my OpenBSD installl. I'll prob send a report into the BSD Now webcast too as they'll love it!
-
The BPi is a cool bit of budget ARM computing kit, I must say. Mine runs Arch off a 2.5" SATA SSD and has an uptime of over 6 months now - 187 days thus far, with no fan and entirely powered by the one USB port. Having SATA makes a huge difference to the system performance, of course.
I'm half tempted to buy the Nvidia Shield TV Pro, or at least I will be if someone gets a SATAIII SSD into it and if you get full OGL accel with FLOSS drivers under proper AArch64 Linux! That'd be a notable upgrade over the BPi for my leading ARM device!
-
I'd heard about the Pyra. I might get one IF Imagination finally release a fully working Linux/X/Wayland driver, like they've said they would for the last decade or whatever it is. Otherwise, they should've gone for the Tegra K1 / X1 or an Adre no chipset supported by Rob Clarks Freedreno driver. My Pandaboard was always shit under X because the PVR drivers were absolute trash with no open alternative.
Sorry, not familiar with the products you're referring to...but understand your point....
Funny to hear to ended up selling your Z's only to buy another a year ago - the C3000 was a crazy cool device when it got released.
Yep, who woulda thunk it....
I got mine signed by RMS at a talk he did in Manchester a few years ago but unfortunately I chose a bad ink/pen and it got smudged.
Is that Richard Stallman you're referring to or ?..................
I'll let you know how I get on with my OpenBSD installl. I'll prob send a report into the BSD Now webcast too as they'll love it!
Sounds good.....
The BPi is a cool bit of budget ARM computing kit, I must say. Mine runs Arch off a 2.5" SATA SSD and has an uptime of over 6 months now - 187 days thus far, with no fan and entirely powered by the one USB port. Having SATA makes a huge difference to the system performance, of course.
Sorry, have no idea what BPi is......but sounds good......like I said, I've been way too busy with work the past few years....
I'm half tempted to buy the Shield TV pro, or at least I will be if someone gets a SATAIII SSD into it and if you get full OGL accel with FLOSS drivers under proper AARCH64 Linux. That'd be a notable upgrade over the BPi for my leading ARM device!
Ummm, no idea what the Shield TV pro is either.....guess I gotta get out more.....
-
Damn! I didn't get to clean up my typos before you replied!
Yep, Richard Stallman signed my C3000! I've got a crappy video of it too but its more like an audio recording.
I bought my BPi and PSU from newit.co.uk. Its like the RPi 2 but with the advantage of including a SATA2 port and gigabit ethernet for the same very low price- ~£30. It makes for a cool, budget ARM computer. There is a NetBSD port already but I'm holdiing out for FreeBSD as I want ZFS.
The Nvidia Shield has just been released in Europe. Its got a fast 64bit ARM CPU, powerful Nvidia Maxwell GFX chipset (with open drivers like the Tegra K1 I'd hope but I'm not 100% it's there yet) 3GB RAM, USB3 ports, gige etc for about £150. The Pro version has a SATA HD so it'd make for a poweful and modern ARM Linux computer that can compete well with modern Intel stuff. It runs Android by default but Phoronix did benchmarks of it running Ubuntu a while back.
-
http://www.phoronix.com/forums/forum/linux...pro-and-nouveau (http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/nvidia-linux/826824-nvidia-shield-tv-pro-and-nouveau)
-
Hi daalnroti
I haven't used my C3000 in about 4 or more years but I'd like to make use of it again, mainly as a pocket SSH client. It seems better suited to that than my smartphone - with or without a BT keyboard - even if its specs are feeble in comparison.
I was excited to see you have got Arch running on the c3x00 as that is my preferred Linux distro/OS these days (I've been impressed with it on my BananaPi) but I was disappointed to read suspend doesn't work. I can live without X or the touchscreen but I'd definitely want to be able to suspend. Have you tried to get suspend to work? Which 3x00 model are you running Arch on?
Why kernel 3.11.3 vs a more recent one? Is that the last one that supports C3x00 devices?
My last (failed) attempt to get something runnng on my Z was Debian 7 IIRC. If I'm really out of luck with suspend under Arch with your kernel then I'm thinking I might try the latest OpenBSD. Have you tried Net or OpenBSD on the Z? Are there any other modern Linux distros we can run on the Z apart from Arch and Debian? I'd love to hear your thoughts.
Thanks
Hi danboid,
simple answer to Xorg, suspend and touchscreen. I have not tried and investigated the issue. I had a pretty good setup with debian before, except suspend everything worked.
My Z is mainly for SSH console work. However, it does not mean suspend is still broken, someone needs to spent some time testing and figuring it out I guess.
Why kernel 3.11.3 ? Well that was the last time I went through the effort of compiling one. ArchLinuxArm still works with it and I see no reason to upgrade until it breaks.
There are hardly any changes to the zaurus code in the kernel anymore.
ArchLinuxArm runs very well, fast and stable. Slightly more memory usage because of systemd. You need to limit your tty sessions to 4, everything is fine. Boots up pretty quick.
ArchLinux pacman is fast when updating and installing, compared to apt-get. Packages a pretty fresh.
Just let me know if you are keen on testing it out and have issue.
Cheers!
-
and by the way, I have been running ArchLinuxArm on C3100 since June 2012, rolling release and still going. No issues with updates, except the odd systemd issue asking for a newer kernel. Since 3.11.3 all good so far.
-
Archi:
obsd no bootio!
https://www.oesf.org/forum/index.php?showtopic=34386 (https://www.oesf.org/forum/index.php?showtopic=34386)
Any ideas?
-
Damn! I didn't get to clean up my typos before you replied!
Yep, Richard Stallman signed my C3000! I've got a crappy video of it too but its more like an audio recording.
I bought my BPi and PSU from newit.co.uk. Its like the RPi 2 but with the advantage of including a SATA2 port and gigabit ethernet for the same very low price- ~£30. It makes for a cool, budget ARM computer. There is a NetBSD port already but I'm holdiing out for FreeBSD as I want ZFS.
The Nvidia Shield has just been released in Europe. Its got a fast 64bit ARM CPU, powerful Nvidia Maxwell GFX chipset (with open drivers like the Tegra K1 I'd hope but I'm not 100% it's there yet) 3GB RAM, USB3 ports, gige etc for about £150. The Pro version has a SATA HD so it'd make for a poweful and modern ARM Linux computer that can compete well with modern Intel stuff. It runs Android by default but Phoronix did benchmarks of it running Ubuntu a while back.
http://www.phoronix.com/forums/forum/linux...pro-and-nouveau (http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/nvidia-linux/826824-nvidia-shield-tv-pro-and-nouveau)
Thanks for all the info, got it now!
-
Archi:
obsd no bootio!
https://www.oesf.org/forum/index.php?showtopic=34386 (https://www.oesf.org/forum/index.php?showtopic=34386)
Any ideas?
Yep, please read my reply to your post over in the OpenBSD section...........
Mark
-
Thanks!
-
daalnroti:
I want to give Arch a go on my C3000.
I presume a rough outline of the install goes something like:
* Install kexecboot
* Create partitions
* Extract Arch tarball to root fs
* Extract boot.cfg, config-3.11.3-borzoi and zImage-3.11.3-borzoi.bin to /boot on the Arch rootfs
What about the 3.11.3-borzoi folder within your kernel tar file? I think that belongs under /usr/lib/modules , right?
Did you say you've got a keymap file I could borrow and tweak for my imperialist, UK loving ways?
Anything else that might trip me up, apart from me not running on Borzoi?
Thanks!
-
I'm now running Arch on my C3000!
kexecboot was simple to install but I had a bit of trouble installing the Arch tarball. I was trying to untar it from the D+B console and I also tried doing it from the pdaXii13 installer console. Both of these use busybox so there's little difference but I think the pdaXii13 busybox is a bit newer than the D+B one. It turns out you can't use busybox tar or even GNU tar to uncompress ArchARM (or ALARM as they prefer to call it), you have to use bsd tar. If you already have a Linux or BSD installed then you should be able to install and use BSD tar but I didn't so instead I uncompressed the Arch latest tar.gz on my laptop then re-tarr'ed it with GNU tar. I still had problems when I gzipped my new tarball for some reason so I had to leave it uncompressed for busybox tar to be happy.
I haven't been able to properly use it yet because, as warned, the keymap isn't set up properly yet although it is working well enough for me to be able to log in. I can't type forward slash currently so real use is a no-go unless I plug in a USB keyboard, maybe.
Suspend isn't working properly but it works better than under OpenBSD on the C3000. When I hit suspend, apm acknowedges the suspend request and the screen goes blank for a couple of seconds before turning back on. This seems closer to the expected behaviour than the grey screen I get under OBSD.
The other oddity is that my orange power LED is blinking twice every second or so when I have AC connected. None of the other distros I've tried do this. Does your C3100 do that daalnroti?
I love it how ALARM only uses 10MB RAM OOTB!
Thanks for bringing Arch to the Z daalnroti - I think this is going to be great once I've got the keyboard and wifi working!
-
I'm now running Arch on my C3000!
kexecboot was simple to install but I had a bit of trouble installing the Arch tarball. I was trying to untar it from the D+B console and I also tried doing it from the pdaXii13 installer console. Both of these use busybox so there's little difference but I think the pdaXii13 busybox is a bit newer than the D+B one. It turns out you can't use busybox tar or even GNU tar to uncompress ArchARM (or ALARM as they prefer to call it), you have to use bsd tar. If you already have a Linux or BSD installed then you should be able to install and use BSD tar but I didn't so instead I uncompressed the Arch latest tar.gz on my laptop then re-tarr'ed it with GNU tar. I still had problems when I gzipped my new tarball for some reason so I had to leave it uncompressed for busybox tar to be happy.
I haven't been able to properly use it yet because, as warned, the keymap isn't set up properly yet although it is working well enough for me to be able to log in. I can't type forward slash currently so real use is a no-go unless I plug in a USB keyboard, maybe.
Suspend isn't working properly but it works better than under OpenBSD on the C3000. When I hit suspend, apm acknowedges the suspend request and the screen goes blank for a couple of seconds before turning back on. This seems closer to the expected behaviour than the grey screen I get under OBSD.
The other oddity is that my orange power LED is blinking twice every second or so when I have AC connected. None of the other distros I've tried do this. Does your C3100 do that daalnroti?
I love it how ALARM only uses 10MB RAM OOTB!
Thanks for bringing Arch to the Z daalnroti - I think this is going to be great once I've got the keyboard and wifi working!
Hi Danboid,
great to hear you had success with the ALAM tar ball. I used my debian port to install arch on the same drive (dual boot).
KEYMAP:
if you can not get a forwards slash, use TAB in the command line after typing a directory name
then create a new folder /usr/share/kbd/keymaps/zaurus
cd /usr/share/kbd/keymaps
mkdir zaurus
then copy the attached file borzoi.map.gz into that folder, then edit you /etc/vconsole.conf
(install terminus font via pacman and also add the FONT part for better console font reading)
KEYMAP=borzoi
FONT=ter-v14n
reboot. Hopefully this will get your keymap fixed.
Note : This is a custom keymap I have created from a pdaxrom one. Look into the borzoi.map.gz file to see what it does.
SUSPEND:
I have not played with it. I suggest to leave this until you got a proper running system and then investigate from there.
POWER LED:
Back then I patched the kernel code to have the orange light show the "cpu heartbeat" instead of charging status. This was mainly for debugging purpose.
If it stops blinking, your Z kernel hangs. This never happened with kernel 3.11.3, as it is stable. I can remove that patch if you like, but there
was an issue with off-line charging...??
WIFI :
The kernel is a custom build used for debugging and testing and has only DLINK and and ASUS USB driver installed for WiFi.
As simple recompile can add any other driver you need. What WiFi card do you have ?
MEMORY:
to reduce memory usage, install dropbear instead of ssh.
with systemd, limit the ttys you open to maybe 4 in the console to save memory.
switching tty with the new keymap (FN - RIGHT or LEFT)
BORZOI:
Myself I have only a C3100 (borzoi) but I included in the kernel support for the C3x00 series. It should work!
KERNEL:
I might attempt to get a 4.x series kernel compiled, but at this stage I am not too worried as there will be no improvements, probably more issues.
If there is an issue with ALARM and the current 3.11.3 kernel, I will update.
Cheers!
-
Hi daalnroti
Thanks for the keymap and answering my questions. I'll be trying the keymap shortly.
What's off vs online charging? I would've guessed one is charging when suspended but you've obviously not tested that.
I'm glad you pointed out the limited wifi options at present. I currently have a planex gw-cf11x which uses the PRISM 3 chipset but yesterday I ordered a SparkLAN WCFM-100 because thats faster and supports 802.11g so that should arrive in the next couple of days. Might you make another kernel release with more PCMCIA wifi (and PCMCIA ethernet) drivers included? That would be handy as it must take an age to compile the kernel on the Z!
I was right to copy your kernels 3.11.3-borzoi dir into /usr/lib/modules , was I?
One good thing about trying a newer kernel would be we would escape the Tux flying the Windows logo flag boot icon offence! 3.11 is of course the 'Linux for Workgroups' release!
The other great thing I've already noticed with ALARM is that it boots literally twice as fast, if not more than twice as fast than any other Z OS I've tried. It boots in about 40 seconds off my stock 4GB MD. That is no doubt thanks to systemd combined with Arch's lean default state.
-
Hi daalnroti
Thanks for the keymap and answering my questions. I'll be trying the keymap shortly.
What's off vs online charging? I would've guessed one is charging when suspended but you've obviously not tested that.
I'm glad you pointed out the limited wifi options at present. I currently have a planex gw-cf11x which uses the PRISM 3 chipset but yesterday I ordered a SparkLAN WCFM-100 because thats faster and supports 802.11g so that should arrive in the next couple of days. Might you make another kernel release with more PCMCIA wifi (and PCMCIA ethernet) drivers included? That would be handy as it must take an age to compile the kernel on the Z!
I was right to copy your kernels 3.11.3-borzoi dir into /usr/lib/modules , was I?
One good thing about trying a newer kernel would be we would escape the Tux flying the Windows logo flag boot shock! 3.11 is of course Linux for Workgroups!
The other great thing I've already noticed with ALARM is that it boots literally twice as fast, if not more than twice as fast than any other distro I've tried. It boots in about 40 seconds. That is no doubt thanks to systemd combined with Arch's lean default state.
Hi danboid.
offline charging is when the Z is plugged in , but not turned on. This has been an issue with 3.x series kernels and has never been fixed.
The Z only charges when turned on...
Yes, the modules for kernel 3.11.3-borzoi go into dir usr/lib/modules
I can do a kernel recompile for the 3.11.3 with drivers requested, remove some patches or the logo.
Whats wrong with the logo ? My 3.5 kernel had a proper archlinuxarm logo, I can add that again ...
No problem, with a tool chain it takes just 5 min. on the Z with distcc, maybe 2h, on the Z alone about 8h for a minimal kernel.
Let me know what modules you need, if you have no tool chain to compile the kernel from my github.
ALARM boots fast, because of systemd, yes, and because it is lean.
Just wait until you can use pacman, you will be amazed how fast it is compared to obsd or debian apt-get.
Once you got your keymap fixed, do some testing and let me know what drivers/modules you might need.
Cheers!
-
I remembered what offline charging was as soon as I'd finished writing that last mail. Its what happens what you don't use your Z for 5 years!
That's a shame with offline charging not working. I hope apm works apart from that (and suspend) ie it accurately tells me the battery charge etc?
As for the LED, if it's doing what you say it is, why does it only do it when AC is plugged in? Could you have the power LED behave as it does under the official ROM, or closely mimic it except for offline behaviour for obvious reasons?
I already know how much faster pacman is than dpkg - check my signature!
distcc! I've never tried it but that could come in very handy for big builds, as you say.
To use wifi I'll need hostap_cs for the PRISM card and libertas_cs for my new wifi card. If you could provide an update kernel / modules to save me the hassle, that'd be much appreciated!
Can I overclock the CPU to 624Mhz under 3.11?
Thanks daalnroti!
-
Hi danboid,
In regards to charging, I guess I got it wrong. When turned on and with a 3.x kernel , the Z charges really slow. When off line, normal charging speed.
If you like, I can remove the LED patch and make it behave as usual. no problem there.
Also I can add the wifi modules for you and recompile, then upload to github.
Overclock, well I never tried, cpufreq on ALARM shows only 416 as max.
This does not mean it cant be done, but I have no need for it to be honest.
Do you have a CF LAN card too , or only WiFi ?
Any USB drivers you may need ?
Cheers
-
That's good news on the charging and having a normal power LED!
I don't have a CF LAN card yet no, but I'm tempted to get one.
One of the things I'm keen to try under Arch is MAME. If I get it running I'll be wanting to plug in my USB gamepad but I think thats part of the standard HID driver?
Apart from a USB keyboard and USB memory sticks / hard drives, the only other thing I can see myself plugging into USB would be my phone in an attempt to get tethering to work. I've not tested it yet but just in case the gentoo wiki tells you what needs to be enabled in the kernel to get USB tethering to work:
https://wiki.gentoo.org/wiki/Android_USB_Tethering (https://wiki.gentoo.org/wiki/Android_USB_Tethering)
Let me know when you've updated the kernel on github please!
Thanks v.much!
-
danboid,
if you want to get mame going you should try this first : https://code.google.com/p/zgrom/wiki/Emulators (https://code.google.com/p/zgrom/wiki/Emulators)
Back in the days, I invested a lot of time to get SDL apps working in pure console, using the framebuffer only for emulators etc.
zgrom is the way to go, anything else is just frustrating. The Z uses a rotated frambuffer as default for landscape view. this is a big performance draw back.
and is a real nightmare to get proper Xorg running fast. it has always to rotate in software ! zgrom is the most optimized as far as I know, for gaming.
Thats why I stick to console only. The impact of rotated console is minimal. obsd has the same issue, has to rotate in software, using wcons for SDL.
In regards to led, logo and wifi / tethering . I will post a testing kernel tar.gz in this thread before uploading the sourced to github.
I will post a testing build later tonight (NZ time) or tomorrow. Different timezones man.
Cheers.
-
I've read about zgrom but I've not tried it. It's based on OE/Angstrom as I understand. I never had any luck with either distro and of course its package selection pales in comparison to Arch, as is the case for all other distros!
Why would it provide better performance than Arch? Has its author tweaked its kernel or SDL somehow? Surely it still has to rotate the FB in software. On top of that, it runs its emus through the wine-like GINGE GP2X compat layer and so the author says the included emus would run faster if they were fully native builds, of course.
I won't be using X. It seems ridiculous to bother on anything less than a HD (or at least 1024x768) display with some hardware acceleration but I'm hopeful for running some old arcade or computer games at 320x240.
Have you tried (Advance)MAME or MESS under Arch?
I'm looking forward to testing the updated kernel.
Cheers
-
danboid,
zgrom uses a sdl library optimized for the the Z, not sure the source code of that library was ever made public..
anyway, the 3.11.3 kernel has hostap support. also for prism 2/3 , I checked.
can you please give me some more details about your card. ? try a "modprobe hostap" first and check "dmesg"
also you may need just the kernel firmware package, that is available via pacman. but you need to get network going first ..
Cheers,
-
I have just tried to recompile the kernel, but since my system is now way up to date, I will need to upgrade the kernel to at least 3.18 or 4.x
Maybe a good chance to get a new kernel going. just give me a few days and I will see what I can get going.
But saying this, I still can compile the 3.11.3 kernel on a older system backup , using older gcc.
I will find out what is more efficient and will let you know. Give me a couple of days, I am busy working at IT daytime and will work on it at nights.
Cheers.
-
Sounds good to me!
I can confirm the keymap works. I'm just looking into setting wifi up now.
Yes, it does seem to include hostap already but I I'll need to install the firmware. libertas_cs seems to be missing though and I'll need that for my new wifi card which I should have tomorrow.
Shame about the custom SDL source. It might be worth me checking to see if he's willing to share it with us so we can enjoy better SDL under Arch.
-
Danboid,
great you got the keymap working.
you can download the firmware package manually and may be able to install it using pacman -U
still, I will put in some effort to get an updated kernel going and add any needed drivers.
The zaurus is a dying platform, but I will keep it going until my Z hardware dies.
Cheers!
-
Dying? It died almost a decade ago!
Weedy as its specs may be today, the fact remains we can still run modern software on it and thats one of the main reasons I bought it. I'd say the Z makes a better pocket SSH client than any of the latest gen smartphones because of its hardware keyboard so its still very useful to us techies.
I think its a shame that, apart from the Pandora which I don't think is available any more either, there hasn't been anything to supercede the Z for pocket Linux boxes. The Pyra should be out soon but I won't buy one unless Imagination release a fully-functional, open source X driver for their PVR GPUs. I can't believe they went that route when it could've used Tegra or Adreno.
-
Dying? It died almost a decade ago!
Weedy as its specs may be today, the fact remains we can still run modern software on it and thats one of the main reasons I bought it. I'd say the Z makes a better pocket SSH client than any of the latest gen smartphones because of its hardware keyboard so its still very useful to us techies.
I think its a shame that, apart from the Pandora which I don't think is available any more either, there hasn't been anything to supercede the Z for pocket Linux boxes. The Pyra should be out soon but I won't buy one unless Imagination release a fully-functional, open source X driver for their PVR GPUs. I can't believe they went that route when it could've used Tegra or Adreno.
You got a point there, it is dead already, we are the last souls to keep it alive.
Also I agree, as a pocket ssh client, it is still useful and more secure compared to android devices.
Saying this, lets focus on one thing. Keep the Z alive , with ALARM.
I appreciate a tester and user a like you. hopefully there might be more joining us with their Z!!
Cheers.
-
It looks like there is a good chance you were the first to run Arch on the Z and I'm the second? I'm prob the first to run it on the C3000. Maybe there are a few others who'll show up and some will have just wanted some 'adventurous' types like us to go first? Others might try it after reading my reports of its greatly improved performance and modernity over say pdaXrom?
Do you think there is a chance the Z (or at least the C3x00 series) could become a supported platform for ALARM? Have you talked to them about this already? There are prob as many Z C3x00 owners as there are say Pogoplug owners, which is supported, so it could happen on that basis. I've seen ArchiMark has brought this up on their forum but the lead ALARM dev dismissed it on the grounds that Mark didn't think we had a recent enough kernel to run systemd but that's obviously not true and hasn't been for a few years at least, according to you.
-
It looks like there is a good chance you were the first to run Arch on the Z and I'm the second? I'm prob the first to run it on the C3000. Maybe there are a few others who'll show up and some will have just wanted some 'adventurous' types like us to go first? Others might try it after reading my reports of its greatly improved performance and modernity over say pdaXrom?
Do you think there is a chance the Z (or at least the C3x00 series) could become a supported platform for ALARM? Have you talked to them about this already? There are prob as many Z C3x00 owners as there are say Pogoplug owners, which is supported, so it could happen on that basis. I've seen ArchiMark has brought this up on their forum but the lead ALARM dev dismissed it on the grounds that Mark didn't think we had a recent enough kernel to run systemd but that's obviously not true and hasn't been for a few years at least, according to you.
Are you saying I said we didn't have a recent enough kernel or are you referring to another Mark?
Anyway, congrats on getting Arch running......
If I can get a few programs I want built with OBSD, then I might stick with it.....otherwise, might join you guys on Arch.....although I'd probably want X working if I do...
Will follow your progress here.....
Meanwhile I'm building OBSD packages.....
-
Yep - I meant you of course - unless there are two Zaurus users called ArchiMark doing the rounds?
http://archlinuxarm.org/forum/viewtopic.php?f=27&t=7746 (http://archlinuxarm.org/forum/viewtopic.php?f=27&t=7746)
I'm not having much luck getting my PLANEX wifi working so far. Hopefully the SparkLAN will be easier to get going as I can't really do much until I can get pacman (and pacaur / packer etc) working - well not without significant pain manually copying and installing hundreds of pkg files from their repos although some might prefer that to multi-day build marathons.
I should mention before I forget that I had to add a line into fstab:
/dev/sda1 / ext3 defaults,rw,relatime 0 1
Otherwise the root drive gets mounted read only.
vi under D+B was playing up so I had to add that line by running:
echo "/dev/sda1 / ext3 defaults,rw,relatime 0 1" >> /etc/fstab
-
OK, I get it now.....
Reading that thread, I was reacting to the info supplied by the person responding to my post. Based upon that info, I didn't think we'd meet the requirements...
Glad to see that was not correct....
Hope you get pacman running......
Will keep reading about Arch progress here.....
Something to do while I'm building OBSD packages.....
-
poweroff
Seems to be the only clean and reliable way to shut down the Z under Arch, vs using halt or shutdown.
If I'm lucky my 32GB CF (which cost me £15 inc. postage) and new wifi card should be arriving today although I don't think I'll be able to use the wifii until dallnroti gets the new kernel uploaded or I build one myself of course. I think I can wait!
Excluding your tweak to get the power LED to indicate the kernels heartbeat, have you applied any custom patches to your kernel or is it all mainlined, upstream code daalnroti?
-
poweroff
Seems to be the only clean and reliable way to shut down the Z under Arch, vs using halt or shutdown.
If I'm lucky my 32GB CF (which cost me £15 inc. postage) and new wifi card should be arriving today although I don't think I'll be able to use the wifii until dallnroti gets the new kernel uploaded or I build one myself of course. I think I can wait!
Excluding your tweak to get the power LED to indicate the kernels heartbeat, have you applied any custom patches to your kernel or is it all mainlined, upstream code daalnroti?
The 3.11.3 kernel has follwing patches :
Power LED => cpu heartbeat
HDD LED => disk activity ( needed to be patches, vanilla kernel does not show HDD activity )
USB => increased max power to 180mA ( _may_ work to get some USB sicks running )
BOOT => some boot hang fix that happenend with 3.x kenels
thats about it.
I will have rebuild 3.11.3 kernel ready this afternoon, containing all USB / CF WiFi drivers, no heartbeat LED and no boot logo.
The 3.18 series did not boot from a vanilla kernel and I will need to troubleshoot later this week. Possibly some patches required.
Cheers!
-
If you want to overclock, you can try to add
pxa27x_maxfreq=624 to your kernel parameters and see if you can get a higher clock rate.
I have not played with it under ALARM.
-
new release 3.11.3 kernel (https://github.com/greguu/linux-3.11.3-borzoi/releases)
-
Hi daalnroti
Enjoy reading about progress and updates with Arch.....
Haven't given up on OpenBSD yet, still building programs....
But if I do decide to try Arch, will your files work with my 3200?
Thanks,
Mark
-
Hi daalnroti
Enjoy reading about progress and updates with Arch.....
Haven't given up on OpenBSD yet, still building programs....
But if I do decide to try Arch, will your files work with my 3200?
Thanks,
Mark
I can not confirm, but I am confident that C3200 will work.
-
Hi daalnroti
Enjoy reading about progress and updates with Arch.....
Haven't given up on OpenBSD yet, still building programs....
But if I do decide to try Arch, will your files work with my 3200?
Thanks,
Mark
I can not confirm, but I am confident that C3200 will work.
Understand.....thanks for your input...
-
These are some examples to help you going. No guarantee these work in all circumstances. Just as a guideline.
Kexecboot :
Create a file boot.cfg in /boot on you ALARM partition if you need a boot menu entry for dual boot etc.
Make sure to change your root= entry to match your setup.
Example: LABEL=ArchLinux
KERNEL=/boot/zImage-3.11.3-c3x00
APPEND=root=/dev/sda3 rootfstype=ext3 fbcon=rotate:1 noinitrd loglevel=3 pxa27x_maxfreq=624
LABEL=Debian
KERNEL=/boot/zImage-2.6.36-rc3
APPEND=console=ttyS0,115200n8 root=/dev/hda1 rootfstype=ext3 console=tty1 noinitrd fbcon=rotate:1 debug dyntick=enable
fstab :
Make sure to change to your file system type, and root device /dev/hdax etc
Example:
/dev/hda3 / ext3 noatime,nodiratime,commit=600,reservation,defaults,errors=remount-ro 0 1
-
Some more info for the curious:
boot log dmesg 3.11.3-c3x00-arch on C3100:
[ 0.573342] 0x000000140000-0x000000800000 : "Boot PROM Filesystem"
[ 0.580806] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
[ 0.580922] Scanning device for bad blocks
[ 0.631902] 3 cmdlinepart partitions found on MTD device sharpsl-nand
[ 0.631945] Creating 3 MTD partitions on "sharpsl-nand":
[ 0.631989] 0x000000000000-0x000000700000 : "smf"
[ 0.637892] 0x000000700000-0x000002700000 : "root"
[ 0.643755] 0x000002700000-0x000008000000 : "home"
[ 0.651137] hdlc: HDLC support module revision 1.22
[ 0.651262] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.651290] ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96
[ 0.652402] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.652452] ohci_hcd: block sizes: ed 64 td 64
[ 0.652666] In ohci_hcd_pxa27x_drv_probe
[ 0.652983] pxa27x-ohci pxa27x-ohci: PXA27x OHCI
[ 0.653129] pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
[ 0.653269] pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
[ 0.653295] pxa27x-ohci pxa27x-ohci: ohci_pxa27x_start, ohci:c3afc4d8
[ 0.653465] pxa27x-ohci pxa27x-ohci: created debug files
[ 0.712511] pxa27x-ohci pxa27x-ohci: OHCI controller state
[ 0.712580] pxa27x-ohci pxa27x-ohci: OHCI 1.0, NO legacy support registers, rh state running
[ 0.712619] pxa27x-ohci pxa27x-ohci: control 0x083 HCFS=operational CBSR=3
[ 0.712647] pxa27x-ohci pxa27x-ohci: cmdstatus 0x00000 SOC=0
[ 0.712680] pxa27x-ohci pxa27x-ohci: intrstatus 0x00000004 SF
[ 0.712711] pxa27x-ohci pxa27x-ohci: intrenable 0x8000005a MIE RHSC UE RD WDH
[ 0.712736] pxa27x-ohci pxa27x-ohci: hcca frame #0009
[ 0.712771] pxa27x-ohci pxa27x-ohci: roothub.a 04001202 POTPGT=4 NOCP NPS NDP=2(3)
[ 0.712797] pxa27x-ohci pxa27x-ohci: roothub.b 00000000 PPCM=0000 DR=0000
[ 0.712827] pxa27x-ohci pxa27x-ohci: roothub.status 00008000 DRWE
[ 0.712864] pxa27x-ohci pxa27x-ohci: roothub.portstatus [0] 0x00000100 PPS
[ 0.712895] pxa27x-ohci pxa27x-ohci: roothub.portstatus [1] 0x00000100 PPS
[ 0.712927] pxa27x-ohci pxa27x-ohci: roothub.portstatus [2] 0x00000100 PPS
[ 0.713110] usb usb1: default language 0x0409
[ 0.713182] usb usb1: udev 1, busnum 1, minor = 0
[ 0.713212] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.713238] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.713261] usb usb1: Product: PXA27x OHCI
[ 0.713283] usb usb1: Manufacturer: Linux 3.11.3-c3x00 ohci_hcd
[ 0.713305] usb usb1: SerialNumber: pxa27x
[ 0.715507] usb usb1: usb_probe_device
[ 0.715567] usb usb1: configuration #1 chosen from 1 choice
[ 0.715701] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 0.716849] hub 1-0:1.0: usb_probe_interface
[ 0.716893] hub 1-0:1.0: usb_probe_interface - got id
[ 0.716921] hub 1-0:1.0: USB hub found
[ 0.717023] hub 1-0:1.0: 3 ports detected
[ 0.717046] hub 1-0:1.0: standalone hub
[ 0.717065] hub 1-0:1.0: no power switching (usb 1.0)
[ 0.717086] hub 1-0:1.0: no over-current protection
[ 0.717109] hub 1-0:1.0: power on to power good time: 8ms
[ 0.717195] hub 1-0:1.0: 180mA bus power budget for each child
[ 0.717228] hub 1-0:1.0: local power source is good
[ 0.717485] hub 1-0:1.0: trying to enable port power on non-switchable hub
[ 0.719822] usbcore: registered new interface driver cdc_wdm
[ 0.721353] mousedev: PS/2 mouse device common for all mice
[ 0.723558] input: matrix-keypad as /devices/platform/matrix-keypad/input/input0
[ 0.728793] pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
[ 0.730848] APM Battery Driver
[ 0.734017] PXA CPU 27x max frequency not defined (pxa27x_maxfreq), assuming pxa271 with 416000kHz maxfreq
[ 0.734076] PXA CPU frequency change support initialized
[ 0.794110] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.797497] usbcore: registered new interface driver usbhid
[ 0.797533] usbhid: USB HID core driver
[ 0.808392] soc-audio soc-audio: ASoC: machine Spitz should use snd_soc_register_card()
[ 0.815143] hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
[ 0.884205] mmc0: new SDHC card at address aaaa
[ 0.886253] mmcblk0: mmc0:aaaa SD04G 3.79 GiB
[ 0.889989] mmcblk0: p1
[ 1.304623] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 1.308715] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
[ 1.314702] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1
[ 1.319517] pcmcia 1.0: pcmcia: registering new device pcmcia1.0 (IRQ: 202)
[ 1.369945] scsi0 : pata_pcmcia
[ 1.372078] ata1: PATA max PIO0 cmd 0xc4880000 ctl 0xc488000e irq 202
[ 1.545011] ata1.00: CFA: HMS360404D5CF00, DN4SCA2A, max PIO4
[ 1.545063] ata1.00: 7999488 sectors, multi 0: LBA
[ 1.822474] soc-audio soc-audio: wm8750-hifi <-> pxa2xx-i2s mapping ok
[ 1.830083] TCP: cubic registered
[ 1.830625] XScale iWMMXt coprocessor detected.
[ 1.841233] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[ 1.843996] pxa-rtc pxa-rtc: setting system clock to 2000-01-01 07:11:19 UTC (946710679)
[ 1.844230] ALSA device list:
[ 1.844245] #0: Spitz
[ 2.684995] ata1.00: configured for PIO0
[ 2.686431] scsi 0:0:0:0: Direct-Access ATA HMS360404D5CF00 DN4S PQ: 0 ANSI: 5
[ 2.691239] sd 0:0:0:0: [sda] 7999488 512-byte logical blocks: (4.09 GB/3.81 GiB)
[ 2.693255] sd 0:0:0:0: [sda] Write Protect is off
[ 2.693317] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.694157] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 2.704233] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.725683] sda: sda1 sda2 sda3
[ 2.736186] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.791667] EXT3-fs (sda3): mounted filesystem with writeback data mode
[ 2.791847] VFS: Mounted root (ext3 filesystem) readonly on device 8:3.
[ 2.792338] kjournald starting. Commit interval 5 seconds
[ 2.848378] devtmpfs: mounted
[ 2.849349] Freeing unused kernel memory: 172K (c04dd000 - c0508000)
[ 7.463956] NET: Registered protocol family 10
[ 7.714201] ip_tables: (C) 2000-2006 Netfilter Core Team
-
but yesterday I ordered a SparkLAN WCFM-100 because thats faster and supports 802.11g so that should arrive in the next couple of days. Might you make another kernel release with more PCMCIA wifi (and PCMCIA ethernet) drivers included? That would be handy as it must take an age to compile the kernel on the Z!
Let me know if you can get the new card to work.
It would be very interesting what throughput you can achieve with that card.
My Buffalo CF LAN is 10mbit only, the DLINK 660W 802.11b and with a USB 100mbit LAN adapter I get still not more than 750KB/s to the internal 4GB MicroDrive (via SSH) and about 850KB/s to a class 4 SD card via the USB1.1 port. Please give some benchmarks with your 32GB CF card too.
Cheers!
-
Hi daalnroti!
Great to see you've got the new kernel config up before my new gear arrives! I was hoping it might arrive yesterday but that was the absolute earliest they could've arrived. Stuff arriving today is more realistic.
I have failed to find a photo guide to swapping out the C3x00 MD drive but there is at least one thread on here discussing the process and it sounds pretty straightforward, if a bit fiddly.
We're never going to get more than about 1MB/s via the USB port as thats what USB 1 tops out at. Its not much but that should suffice for acceptable tethering speeds, if it will work over USB OTG 1? Did you check the USB tethering stuff was enabled? Of course, CF will achieve much faster rattes so I may get more than that with my new wifi card and lets see how fast the CF memory card is. I'll be sure to get some before and after boot times and transfer rates for the drives.
Shame about the newer kernel. I'm very interested to see what the newest we can get to run is.
Seeing as I'll have physical access to my new CF card, I'll be writing ALARM to it via my laptops USB CF reader, if it can read it! I'll be formatting it as ext4 as I'm pretty sure kexecboot supports ext4. I think you can tell fstab / mount to mount ext3 partitions as ext4 without reformatting drives anyway.
Thanks!
-
Hi daalnroti!
Great to see you've got the new kernel config up before my new gear arrives! I was hoping it might arrive yesterday but that was the absolute earliest they could've arrived. Stuff arriving today is more realistic.
I have failed to find a photo guide to swapping out the C3x00 MD drive but there is at least one thread on here discussing the process and it sounds pretty straightforward, if a bit fiddly.
We're never going to get more than about 1MB/s via the USB port as thats what USB 1 tops out at. That should should suffice for acceptable tethering speeds, if that will work over USB OTG 1? Did you check the USB tethering stuff was enabled? Of course, CF will achieve much faster rattes so I may get more than that with my new wifi card and lets see how fast the CF memory card is. I'll be sure to get some before and after boot times and transfer rates for the drives.
Shame about the newer kernel. I'm very interested to see what the newest we can get to run is.
Seeing as I'll have physical access to my new CF card, I'll be writing ALARM to it via my laptops USB CF reader, if it can read it! I'll be formatting it as ext4 as I'm pretty sure kexecboot supports ext4. I think you can tell fstab / mount to mount ext3 partitions as ext4 without reformatting drives anyway.
Thanks!
Hi danboid,
there must be some photo guides somewhere on google cache. I am sure I saw some not too long ago.
take care when doing it, do not break your Z
Sure, USB1 has it limits, but with the card you ordered, higher speed might be possible.
I will give my best to get a new kernel going, but saying that, 3.11.3 is stable and does what is should do.
Let me know how you go with WiFi and the rebuild kernel.
Cheers!
-
and yes, I enabled everything needed for the tethering you mentioned.
-
Seeing as I'll have physical access to my new CF card, I'll be writing ALARM to it via my laptops USB CF reader, if it can read it! I'll be formatting it as ext4 as I'm pretty sure kexecboot supports ext4. I think you can tell fstab / mount to mount ext3 partitions as ext4 without reformatting drives anyway.
The oe-kexecboot possibly supports ext4, but I am not sure. I am still on ext3.
I am not sure there is a real advantage for the Z to use ext4 on CF flash drive over ext3.
The 3.11.3 kernel does support ext4.
If we need a new kexecboot kernel , I may find the time to compile one. I have done it before.
Cheers!
-
As for the tethering, I'd prob get better speeds using my new 54Mb/s card with portable wifi hotspot on my phone versus a USB link but the USB option would certainly be very handy to have, especially for those who don't have a (working) wifi or ethernet card or struggle to get wifi to work due to various potential issues.
I doubt using ext4 over ext3 would be detrimental to performance although I'm not expecting a huge or even a very noticeable gain by switching. I'm going to try it now.
Good to hear you have already recompiled kexec. What did you need to rebuild it for previously?
-
Good to hear you have already recompiled kexec. What did you need to rebuild it for previously?
Need to build a minimal kernel with a build in initrd image.
That image contains the kexecboot binary and will get executed on boot.
It is possible to change boot logo etc for that.
Cheers!
-
danboid : any success with the "new" kernel and WiFi ?
-
Thanks for explaining how to overclock! I'll be trying that soon - after I have networking sorted and hence something installed that would benefit from a higher clock (gcc, MAME or something).
My new hardware didn't arrive today. I've checked the tracking and I should have both tomorrow so there is no progress on the wifi or CF benchmarks to report. I don't think its worth the hassle trying to get my prism card to work now.
I've installed the new kernel and it seems to be running fine - better than fine actually! Suspend works now! I was NOT expecting that! This is shaping up very nicely now!
Why are there two kernel images in the new archive? One has -arch appended but I've only tried the one without because there wasn't a -arch kernel module dir to go with it.
The power LED is no longer blinking but I've noticed some odd beviour with it in that it sometimes doesn't light up when AC is plugged in. Do you get this? I've not worked out what might be causing that yet.
Looks like I might be out of luck with the USB tethering - I just get lots of "hub 1-0:1.0: connect-debounce failed, port 2 disabled" errors when I connect my phone and USB tethering is still greyed out under Android.
Indeed you can mount an ext3 partition as ext4 under Arch. You need to change the fs type in both /boot/boot.cfg and fstab. My tests indicate reading is slightly faster with ext4 but it makes no discernable difference to write speed:
Stock 4GB MD, ext3
kexec menu to login prompt boot time: 49s
hdparm -Tt /dev/sda
cached reads: 44.55 MB/s
buffered disk reads: 2.25 MB/s
hdparm -Tt --direct /dev/sda
cached reads: 1.99 MB/s
disk reads: 2.02 MB/s
sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"
2.4MB/s (write speed)
1m 27s real
Stock 4GB MD mounted as ext4
kexec menu to login prompt boot time: 49s
hdparm -Tt /dev/sda
cached reads: 46.69 MB/s
buffered disk reads: 2.31 MB/s
hdparm -Tt --direct /dev/sda
cached reads: 2.03 MB/s
disk reads: 2.04 MB/s
sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"
2.4MB/s (write speed)
1m 27s real
-
I've just noticed there is a note on github explaing the differences between the two kernel images altough I'm still unsure about it.
It seems the -arch version has a different boot logo and still has the LED heartbeat indicator but the note makes it sound like the included firmware might only work with zImage-3.11.3-c3x00-arch? That would seem a bit odd to me but you must have a reason if that's the case?
In any case I'd presume they share the same modules dir and thats why there is only one included?
-
I've just noticed there is a note on github explaing the differences between the two kernel images altough I'm still unsure about it.
It seems the -arch version has a different boot logo and still has the LED heartbeat indicator but the note makes it sound like the included firmware might only work with zImage-3.11.3-c3x00-arch? That would seem a bit odd to me but you must have a reason if that's the case?
In any case I'd presume they share the same modules dir and thats why there is only one included?
Yes, modules, firmware work with both versions. I might fix that github entry to make this more clear.
-
Thanks for explaining how to overclock! I'll be trying that soon - after I have networking sorted and hence something installed that would benefit from a higher clock (gcc, MAME or something).
My new hardware didn't arrive today. I've checked the tracking and I should have both tomorrow so there is no progress on the wifi or CF benchmarks to report. I don't think its worth the hassle trying to get my prism card to work now.
I've installed the new kernel and it seems to be running fine - better than fine actually! Suspend works now! I was NOT expecting that! This is shaping up very nicely now!
Why are there two kernel images in the new archive? One has -arch appended but I've only tried the one without because there wasn't a -arch kernel module dir to go with it.
The power LED is no longer blinking but I've noticed some odd beviour with it in that it sometimes doesn't light up when AC is plugged in. Do you get this? I've not worked out what might be causing that yet.
Looks like I might be out of luck with the USB tethering - I just get lots of "hub 1-0:1.0: connect-debounce failed, port 2 disabled" errors when I connect my phone and USB tethering is still greyed out under Android.
Overclocking : let me know if you have success. I had no time to test it really.
Great you got suspend working. It does work somewhat, but needs some tweaking to make it useful. See /etc/systemd/logind.conf for some settings. Also SD card does not get unmounted proberly when suspending...
The power LED does not blink when turned on because online charging is broken. The Z does charge, but I guess very slowly. To charge properly you need to turn off. ;(
Actually that was the reason why I added the CPU heartbeat instead if I remember correctly. It has been a few years ago when I build the 3.5 and 3.11.3 kernels.
The tethering issue may be related to the low power on the usb port? Try with a powered usb hub just to test if that is the case.
-
If the SD card not getting unmounted is the only prob with suspend then I can live with that.
As for the USB tethering, I suppose there is a chance its lack of power but I doubt it and if it does require a powered hub for me to use USB tethering then I don't think I'd bother.
You forgot to include an example boot.cfg file in the updated kernel tarball like you did in the previous release.
My 32GB CF card arrived this morning so I'm just setting it up now before I disassemble my Z to replace the MD. I'll hopefully be back shortly with some benchmarks rather than bad news!
I'm still awaiting delivery of my wifi card...
-
If the SD card not getting unmounted is the only prob with suspend then I can live with that.
As for the USB tethering, I suppose there is a chance its lack of power but I doubt it and if it does require a powered hub for me to use USB tethering then I don't think I'd bother.
You forgot to include an example boot.cfg file in the updated kernel tarball like you did in the previous release.
My 32GB CF card arrived this morning so I'm just setting it up now before I disassemble my Z to replace the MD. I'll hopefully be back shortly with some benchmarks rather than bad news!
I'm still awaiting delivery of my wifi card...
Tethering : I understand that a powered usb hub is not an option, but it would clarify if the issue is the power on the usb port or not. There is still the chance it may work if some further kernel or userland settings are required.
boot.cfg : you are right, I forgot to add the file.
did you have any success with you current WiFi card ? Would be good to know that you can use pacman and do an update of packages.
Thanks for testing, very much appreciated, any input welcome.
Cheers!
-
I've now replaced my Microdrive and my Zaurus is still alive! I was helped by this guide:
http://www.ayati.com/kobako/c3bara.htm (http://www.ayati.com/kobako/c3bara.htm) ( https://translate.google.com/translate?hl=e...ko%2Fc3bara.htm (https://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Fwww.ayati.com%2Fkobako%2Fc3bara.htm) )
The only thing I didn't do that the guide did was disconnect the two ribbon cables as I didn't fancy trying to reconnect them.
Although the hdparm results below seem to indicate liitle gain in R/W performance, I am happy to report my Z boots up a full 10s faster now! Not a bad upgrade for £15! £10 if you exclude the postage. I should imagine I should get slightly better battery life now too and the extra space always helps!
Seeing as my new wifi card is getting delivered to work I won't get that until at least Monday now so I think I will try to get my current wifi card working as I'm keen to actually use my Z after spending most of this week setting it up.
Next time you update the kernel tarball I think it'd be a good idea to include the keymap and a short README on how to configure the keymap, where to place the kernel modules etc- basically extract the key bits of info from this thread in case OESF disappears. I don't think github is going away any time soon.
Kingston 32GB Ultimate 266X ext4
kexec menu to login prompt boot time: 39s
hdparm -Tt /dev/sda
cached reads: 51.78 MB/s
buffered disk reads: 2.56 MB/s
hdparm -Tt --direct /dev/sda
cached reads: 2.06 MB/s
disk reads: 2.07 MB/s
sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"
2.4MB/s (write speed)
1m 29s real
-
It'd be nice if I could get kexec to default to loading Arch instead of System Tools and being able to set a timeout would be handy too.
Would you know if it can do either?
Note that I've updated my sig now with storage device info and some double ALARM action!
-
Networking update
I have now tried USB tethering connecting via a powered USB hub. I tried the hub with a memory stick first to check it was OK. It mounted fine but when I tried connecting my phone I got the same connect-debounce errors I get when I connect my phone via the OTG cable alone. Searching for this error returns reports of people seeing ths error since at least as far back as Fedora 5 and normally in relation to a USB wifi or BT device. They found that disabling the wifi/BT device stops the error but obviously I'm trying to use that very same USB device so thats not a fix. Turns out enabling debug mode stops the connect-debounce error but USB tethering remains greyed out on my phone.
I could try finding the right combo of primary and secondary firmware to get my current wifi card to work but even if I succeed its 802.11b only and I don't think my router has that enabled of if it even supports b. I think I'd have a better chance of getting a connection via BT tethering instead. My phone supports BT tethering and I've dug out a USB BT adapter and plugged it direct into the OTG cable -I've not installed bluez etc yet nor have I tried pairing with my phone but lsusb can see the BT adapter so I think it should work, after all the required config.
I've never tried BT tethering before because it sounds like a total ballache to do from the teriminal, unlike USB tethering which normally just involves running one simple command to connect if your network manager doesn't auto-connect you. Here's one guide to Linux BT tethering ('dial-up') I've found:
https://www.howtoforge.com/linux_internet_a...tooth_gsm_phone (https://www.howtoforge.com/linux_internet_access_gprs_edge_via_bluetooth_gsm_phone)
I could do to check alll those modules are available in your current kernel before I start on the BT tether quest.
It'd definitely be easier just to wait until Monday when my wifi card will hopefully have arrived!
-
daalnroti:
I want to give Arch a go on my C3000.
I presume a rough outline of the install goes something like:
* Install kexecboot
* Create partitions
* Extract Arch tarball to root fs
* Extract boot.cfg, config-3.11.3-borzoi and zImage-3.11.3-borzoi.bin to /boot on the Arch rootfs
What about the 3.11.3-borzoi folder within your kernel tar file? I think that belongs under /usr/lib/modules , right?
Did you say you've got a keymap file I could borrow and tweak for my imperialist, UK loving ways?
Anything else that might trip me up, apart from me not running on Borzoi?
Thanks!
kexecboot was simple to install but I had a bit of trouble installing the Arch tarball. I was trying to untar it from the D+B console and I also tried doing it from the pdaXii13 installer console. Both of these use busybox so there's little difference but I think the pdaXii13 busybox is a bit newer than the D+B one. It turns out you can't use busybox tar or even GNU tar to uncompress ArchARM (or ALARM as they prefer to call it), you have to use bsd tar. If you already have a Linux or BSD installed then you should be able to install and use BSD tar but I didn't so instead I uncompressed the Arch latest tar.gz on my laptop then re-tarr'ed it with GNU tar. I still had problems when I gzipped my new tarball for some reason so I had to leave it uncompressed for busybox tar to be happy.
Think I would like to try Arch on my 3200.....
However, before I mess up my Z that is currently got Cacko as bootloader and BSD on it, would like a bit more install info if that's possible....might help others that come along too....
I downloaded the files, but what should I do to install them, untar them to a SD or CF card?
And sounds like it would be good for me to uncompress the ALARM tarball to a card while I still have OBSD on my Z.
Would greatly appreciate some guidance as to how to proceed, in what order, etc...
Thanks.
-
I have no idea if it will be possible to multiboot OBSD alongside Arch but it'd be good to have another Zaurus ALARMer! I'm not sure you'll be able to install kexecboot without losing your ability to boot OBSD. I tried writing to the guy who ported OBSD to the Z (Uwe) to ask about how to boot OBSD without Cacko but I have yet to receive a response, weeks later.
You're lucky ArchiMark as I've documented everything I've gone through so far in this thread. The outline for the install is something like this but not neccessarily in this order:
* Install kexecboot
* Create partitions
* Extract Arch tarball to root fs using bsdtar
* Edit/Extract boot.cfg (its in the old kernel tarball - edit it to point to the new kernel image) and the kernel image into /boot on the Arch rootfs, copy the kernel modules dir into /usr/lib/modules
* See daalnroti's notes on setting up the keymap and create an fstab file as I detailed so you can read and write to your Arch drive.
I realise that's lacking all the real details but I presume you already know how to do all of that and I don't think there is anything else you need to do to get a base install running. When I was upgrading my MD I was able to do all the partitioning, extracting of files and config with the speed and comfort of my x64 Arch box. You could do the same if you end up running Arch off a removable CF or SD card too of course.
-
I have not yet been able to get ALARM to activate swap on boot. If I specify swap in fstab by dev or by UUID I get an error during boot like:
A start job is running for dev-sda2.device (1min 30s / 1min 39s)
Then I have to wait 90s before booting resumes. After logging in, swap isn't active (according to `swapon -s`) but I can manually activate it with swapon.
It's not a showstopper but its not ideal either. I'm hoping a pacman sync/upgrade will sort it out with a systemd upgrade maybe?
Have you got swap activating on boot OK daalnroti?
-
I have no idea if it will be possible to multiboot OBSD alongside Arch but it'd be good to have another Zaurus ALARMer! I'm not sure you'll be able to install kexecboot without losing your ability to boot OBSD. I tried writing to the guy who ported OBSD to the Z (Uwe) to ask about how to boot OBSD without Cacko but I have yet to receive a response, weeks later.
You're lucky ArchiMark as I've documented everything I've gone through so far in this thread. The outline for the install is something like this but not neccessarily in this order:
* Install kexecboot
* Create partitions
* Extract Arch tarball to root fs using bsdtar
* Edit/Extract boot.cfg (its in the old kernel tarball - edit it to point to the new kernel image) and the kernel image into /boot on the Arch rootfs, copy the kernel modules dir into /usr/lib/modules
* See daalnroti's notes on setting up the keymap and create an fstab file as I detailed so you can read and write to your Arch drive.
I realise that's lacking all the real details but I presume you already know how to do all of that and I don't think there is anything else you need to do to get a base install running. When I was upgrading my MD I was able to do all the partitioning, extracting of files and config with the speed and comfort of my x64 Arch box. You could do the same if you end up running Arch off a removable CF or SD card too of course.
Thanks....
Did not mean to imply that I need/want to multi-boot with OBSD...not sure it's possible and given issues with OBSD, don't think it's needed now....
Feeling a bit confused about install order....as I assume I need to redo partitions from my OBSD install at least I think I do given way OBSD formats them....yet, need to extract tarball using BSD, which will be wiped out if I reformat partitions now and if I install kexecboot now that will prevent me from booting with OBSD to do the extraction, correct?......
see why I'm feeling a bit confused as to best way to go about this?......
-
Some of your install options are:
* Install on a removable CF/SD, that way you can use bsdtar on your desktop/laptop to uncompress
* Install another OS alongside Arch, maybe just a temp one running off a card just and uncompress from there. Debian etc all have bsdtar in their repos.
* Decompress the Arch tarball on your Linux/UNIX PC (to preserve the file permissions etc) and then recompress it using gnutar so you can uncompress it using the busybox tar. Don't gzip the gnu tarball as I had probs uncompressing it when I did that
I expect it would also be possible to find or build a version of bsdtar that you could run off the same card as the arch install tarball so you can decompress it under busybox/D+B.
-
What probs did you run into with OBSD?
-
Some of your install options are:
* Install on a removable CF/SD, that way you can use bsdtar on your desktop/laptop to uncompress
* Install another OS alongside Arch, maybe just a temp one running off a card just and uncompress from there. Debian etc all have bsdtar in their repos.
* Decompress the Arch tarball on your Linux/UNIX PC (to preserve the file permissions etc) and then recompress it using gnutar so you can uncompress it using the busybox tar. Don't gzip the gnu tarball as I had probs uncompressing it when I did that
I expect it would also be possible to find or build a version of bsdtar that you could run off the same card as the arch install tarball so you can decompress it under busybox/D+B.
Thanks for the suggestions....
So, maybe the order is something like this:
A. While I have OBSD installed on Zaurus:
* Extract Arch tarball to root fs using bsdtar onto SD card
* Edit/Extract boot.cfg onto SD Card
B. Install kexecboot
C. Create New Partitions
D. Copy Arch and boot.cfg over to microdrive
Does this make sense if I want to do install on Zaurus itself?
Or is it just better to do this on my laptop with LinuxMint 17 ?
Thanks.
What probs did you run into with OBSD?
After trying several times to make cmake and it failing with same errors, I think I'm done with OBSD...too much time to try and build packages and then have process fail....
-
I said my rough outline of the install procedure could be done in almost any order but two parts that have to be done in a certain order are partition creation first, then extracting the Arch tarball later because of course you can't extract the tarball unless you have a sufficiently large ext3/4 partition to mount and extract it to. You're going to have a pretty small Arch root partition if you are wanting to keep OBSD installed, which requires Cacko be installed too.... on a 4GB MD!
-
daalnroti:
I was hoping I might be able to get a BT tether internet connection running today. I got bluez and bluez-utils installed but I was foiled by the current kernel's lack of a btusb module. I'd like to see that included in your next kernel update to give us the maximum amount of options in getting a connection up. BT adapters are available for £1 so BT tethering should be the cheapest and likely most easily available if not the fastest or easiest solution.
I think that previous guide I posted to Linux BT tethering was quite old. I found a more modern solution to BT tethering on the Arch wiki and it apparently only requires one or two commands be run, after you've paired the devices:
https://wiki.archlinux.org/index.php/Androi...g_via_Bluetooth (https://wiki.archlinux.org/index.php/Android_tethering#Tethering_via_Bluetooth)
-
I said my rough outline of the install procedure could be done in almost any order but two parts that have to be done in a certain order are partition creation first, then extracting the Arch tarball later because of course you can't extract the tarball unless you have a sufficiently large ext3/4 partition to mount and extract it to. You're going to have a pretty small Arch root partition if you are wanting to keep OBSD installed, which requires Cacko be installed too.... on a 4GB MD!
Per my post above #67....I do not need or want OBSD/Cacko on my Z anymore...given the problems with it....
Understand you have to create the partitions first and then extract tarball to one.....
btw, the 3200 has a 6GB MD.....
Thanks.
-
daalnroti:
I was hoping I might be able to get a BT tether internet connection running today. I got bluez and bluez-utils installed but I was foiled by the current kernel's lack of a btusb module. I'd like to see that included in your next kernel update to give us the maximum amount of options in getting a connection up. BT adapters are available for £1 so BT tethering should be the cheapest and likely most easily available if not the fastest or easiest solution.
I think that previous guide I posted to Linux BT tethering was quite old. I found a more modern solution to BT tethering on the Arch wiki and it apparently only requires one or two commands be run, after you've paired the devices:
https://wiki.archlinux.org/index.php/Androi...g_via_Bluetooth (https://wiki.archlinux.org/index.php/Android_tethering#Tethering_via_Bluetooth)
Hi,
sorry I was away over the weekend.
KEXECBOOT : timeout and default boot. Example boot.cfg https://github.com/andrea-adami/kexecboot/b...master/boot.cfg (https://github.com/andrea-adami/kexecboot/blob/master/boot.cfg) does not document it but I will lookinto the kexec cfg parser...
SWAP : I have the same issue on my Z after recently upgrading my systemd. It is possibly a trivial fix, to prevent systemd from doing this to sda2. I will look into it. I removed swap from fstab already but it still does it. This issue is documented in Arch forums somewhere and not just a ALARM issue.
BT : I can add the modules, no problem. As mentioned I was away and will add the modules when back home today.
INSTALL GUIDE : It would be a good Idea to get all the steps together and add them to a README file on github once we got it booting clean with all modules needed and cfg files.
BSD DualBoot : Some time ago I looked into this, as I wanted to try out oBSD alongside Arch. I did not find anything and stopped looking. If you can kexec a BSD kernel, it should be doable.
Cheers!
-
It'd be nice if I could get kexec to default to loading Arch instead of System Tools and being able to set a timeout would be handy too.
Would you know if it can do either?
Note that I've updated my sig now with storage device info and some double ALARM action!
The kexecboot parser source file revealed these additional settings:
/* Global bootmenu settings */
{ CFG_FILE, 1, "TIMEOUT", set_timeout },
{ CFG_FILE, 1, "UI", set_ui },
{ CFG_FILE,-1, "DEBUG", set_debug },
/* Individual item settings */
{ CFG_FILE, 0, "DEFAULT", set_default },
{ CFG_FILE, 1, "LABEL", set_label },
{ CFG_FILE, 1, "KERNEL", set_kernel },
{ CFG_FILE, 1, "ICON", set_icon },
{ CFG_FILE, 1, "APPEND", set_cmdline },
{ CFG_FILE, 1, "INITRD", set_initrd },
{ CFG_FILE, 1, "PRIORITY", set_priority },
{ CFG_CMDLINE, 1, "FBCON", set_fbcon },
{ CFG_CMDLINE, 1, "MTDPARTS", set_mtdparts },
{ CFG_CMDLINE, 1, "CONSOLE", set_ttydev },
This _might_ work. I can test later today. Example:
TIMEOUT=10
LABEL=ArchLinux
KERNEL=/boot/zImage-3.11.3-c3x00
APPEND=root=/dev/sda3 rootfstype=ext3 fbcon=rotate:1 noinitrd loglevel=3 pxa27x_maxfreq=624
DEFAULT
LABEL=Debian
KERNEL=/boot/zImage-2.6.36-rc3
APPEND=console=ttyS0,115200n8 root=/dev/hda1 rootfstype=ext3 console=tty1 noinitrd fbcon=rotate:1 debug dyntick=enable
-
Thanks daalnroti! I'll try those kexc options shortly.
With any luck I'll get my new wifi card tomorrow and then I can start using/testing my Z for real! It looks likely I will be buying a CF ethernet adapter soon but I may not be able to find a new one by the looks of things.
After Mark is up and running, we'll just need a Z ALARMer from both Australia and Canda to form the Five Eyes zALARMers!
https://en.wikipedia.org/wiki/Five_Eyes (https://en.wikipedia.org/wiki/Five_Eyes)
-
Five Eyes sounds cool.....
Meanwhile, got kexecboot working....
Have created new partitions:
/dev/hda1 FAT32 (100MB)
/dev/hda2 linux swap (256MB)
/dev/hda3 linux (rest of 6GB drive...)
Did the following to mount the filesystems:
# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot
# mkswap /dev/hda2
Having problem creating fs for ext3 or ext4 for /hda3......
Everything I try, I get not found message....
Tried:
# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3
What's the right way?
Thanks!
-
Five Eyes sounds cool.....
Meanwhile, got kexecboot working....
Have created new partitions:
/dev/hda1 FAT32 (100MB)
/dev/hda2 linux swap (256MB)
/dev/hda3 linux (rest of 6GB drive...)
Did the following to mount the filesystems:
# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot
# mkswap /dev/hda2
Having problem creating fs for ext3 or ext4 for /hda3......
Everything I try, I get not found message....
Tried:
# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3
What's the right way?
Thanks!
Hi ArchiMark,
First, I believe there is no need for a FAT32 boot partition if you want to run Arch.
If you are using the sharp emergency console, (busybox), it will have no ext3/4 support I think.
You will need to boot of a newer ROM from a SD card to create the file system with ext3/4.
Alternatively, create a ext2 /dev/hda4 with 2GB, mkfs ext2 then install Arch, once installed and booted of ext2, mkfs ext3 on hda3 and move Arch.
Boot to ext3 and the remove hda4 and extend your hda3.
Actually a good point raised, we need to cover this issue in the install guide somehow.
Cheers,
-
Five Eyes sounds cool.....
Meanwhile, got kexecboot working....
Have created new partitions:
/dev/hda1 FAT32 (100MB)
/dev/hda2 linux swap (256MB)
/dev/hda3 linux (rest of 6GB drive...)
Did the following to mount the filesystems:
# mkfs.vfat /dev/hda1
# mkdir boot
# mount /dev/hda1 boot
# mkswap /dev/hda2
Having problem creating fs for ext3 or ext4 for /hda3......
Everything I try, I get not found message....
Tried:
# mksf.ext3 /dev/hda3
# mksf -t ext3 /dev/hda3
# mkext3fs /dev/hda3
What's the right way?
Thanks!
Hi ArchiMark,
First, I believe there is no need for a FAT32 boot partition if you want to run Arch.
If you are using the sharp emergence console, (busybox), it will have no ext3/4 support I think.
You will need to boot of a newer ROM from a SD card to create the file system with ext3/4.
Alternatively, create a ext2 /dev/hda4 with 2GB, mkfs ext2 then install Arch, once installed and booted of ext2, mkfs ext3 on hda3 and move Arch.
Boot to ext3 and the remove hda4 and extend your hda3.
Actually a good point raised, we need to cover this issue in the install guide somehow.
Cheers,
Thanks for your help and input!
What partition layout would you recommend since I have a 6GB micro drive ?
Mark
-
Thanks for your help and input!
What partition layout would you recommend since I have a 6GB micro drive ?
If you want to use all of the 6GB for Arch / Home use a simple
/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)
If you can spare a few GB for a second Arch for fall back you can use
/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch
Cheers,
-
Thanks for your help and input!
What partition layout would you recommend since I have a 6GB micro drive ?
If you want to use all of the 6GB for Arch / Home use a simple
/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)
If you can spare a few GB for a second Arch for fall back you can use
/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch
Cheers,
Thanks!
-
Thanks for your help and input!
What partition layout would you recommend since I have a 6GB micro drive ?
If you want to use all of the 6GB for Arch / Home use a simple
/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)
If you can spare a few GB for a second Arch for fall back you can use
/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch
Cheers,
Thanks!
Keep in mind that after booting into Arch the harddrive / cf card will be named /dev/sda.
So boot.cfg and fstab for Arch need to be /dev/sdaX instead of /dev/hda.
-
Thanks for your help and input!
What partition layout would you recommend since I have a 6GB micro drive ?
If you want to use all of the 6GB for Arch / Home use a simple
/dev/hda1 5.5 GB ext4
/dev/hda2 0.5 GB Swap (128 MB may be enough)
If you can spare a few GB for a second Arch for fall back you can use
/dev/hda1 2 GB ext4 (fall-back Arch minimal)
/dev/hda2 0.5 GB Swap (128 MB may be enough)
/dev/hda3 3.5 GB ext4 Arch
Cheers,
Thanks!
Keep in mind that after booting into Arch the harddrive / cf card will be named /dev/sda.
So boot.cfg and fstab for Arch need to be /dev/sdaX instead of /dev/hda.
OK, will keep this in mind.....
Thanks!
-
You can format ext3 using busybox by using
mkext2fs -j /dev/hdax
The -j switch enables journaling which means its really ext3 but I would recommend you mount it as ext4 as my tests earler in this thread show you get a little extra read speed when using ext4.
-
You can format ext3 using busybox by using
mkext2fs -j /dev/hdax
The -j switch enables journaling which means its really ext3 but I would recommend you mount it as ext4 as my tests earler in this thread show you get a little extra read speed when using ext4.
This does work, but I would not recommend this.
It would be better to create a proper ext4 partition from a running system that has ext4 support or follow the conversion guide shown here.
https://wiki.archlinux.org/index.php/Ext4 (https://wiki.archlinux.org/index.php/Ext4)
Unless you need to be able to mount it again as ext2/3 in the future, there is no need to run mkfs.ext2 -j
-
BT : I have added all BT modules to a new kernel release (https://github.com/greguu/linux-3.11.3-borzoi/releases/tag/v0.4). Please test.
KEXECBOOT : The settings for TIMEOUT and DEFAULT did not work for me. May be the kexecboot version needs to be updated, it is quite old.
-
Thanks daalnroti!
I didn't get to try the kexecboot options but I'd be willing to upgrade to get the default and timeout options. I installed the version you uploaded to github (0.5.9).
Unfortunately my USB BT adapter died over the weekend. It seemed to be working on Saturday but when I tried it again on Sunday - no go. I tried it on my laptop too to make sure it was dead so I'll try the BT tethering out when I get a replacement adapter.
EDIT
My new wifi adapter has failed to show again so I'm going to try and get a new BT adapter if I can find one cheap locally. The tracking says I should have the wifi tomorrow.
-
Mark:
I don't think daal or I have mentioned it so far but you also have to copy the firmware dir within the kernel; tarball to /usr/lib .
That's the correct location isn't it daalnroti?
-
Mark:
I don't think daal or I have mentioned it so far but you also have to copy the firmware dir within the kernel; tarball to /usr/lib .
That's the correct location isn't it daalnroti?
Thanks for the heads up.....
Will be trying to get Arch setup in about 5 hours or so....
Tried using my MacBook last night to uncompress the Arch tarball, but didn't work well....
As I'd left my laptop with LM17 on it at the office, I had to wait until now to proceed further with Arch install.
Almost done downloading the Arch tarball and other files now. After I get back from a meeting, I will try to do the rest of the install....
When I get back I'll check if there's any further clarifications or tips regarding install.....
Thanks!
-
I bought a new USB BT adapter but it looks like I'm unlikely to get it working under kernel 3.11. My £1 BT adapter is manufactured by SIGNALEX and lsusb describes it as:
0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
It works on my x64 Arch box running kernel 4.1.6 but I'm not the only person struggling to get it to work under 3.11.x according to this thread:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995)
The good news is that the btusb kernel module loads OK but obviously I can't confirm it actually works.
EDIT
I've got a bit further with this device now on the Z. I thought it wasn't going to work as the `hciconfig` command showed a hci0 device but `hcitool dev` showed nothing UNTIL I ran:
hciconfig device up
Which is something I've not had to do before in my limited BT experience. After running that, `hcitool dev` shows a hci0 device but scanning is failing currently so I cannot pair with my phone. I've only tried it plugged directly into the OTG port so I'll be trying again with a powered hub later to see if that helps.
-
Mark:
I don't think daal or I have mentioned it so far but you also have to copy the firmware dir within the kernel; tarball to /usr/lib .
That's the correct location isn't it daalnroti?
The firmware files go to /lib/firmware.
-
I bought a new USB BT adapter but it looks like I'm unlikely to get it working under kernel 3.11. My £1 BT adapter is manufactured by SIGNALEX and lsusb describes it as:
0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
It works on my x64 Arch box running kernel 4.1.6 but I'm not the only person struggling to get it to work under 3.11.x according to this thread:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221995)
The good news is that the btusb kernel module loads OK but obviously I can't confirm it actually works.
EDIT
I've got a bit further with this device now on the Z. I thought it wasn't going to work as the `hciconfig` command showed a hci0 device but `hcitool dev` showed nothing UNTIL I ran:
hciconfig device up
Which is something I've not had to do before in my limited BT experience. After running that, `hcitool dev` shows a hci0 device but scanning is failing currently so I cannot pair with my phone. I've only tried it plugged directly into the OTG port so I'll be trying again with a powered hub later to see if that helps.
I can add this https://bugzilla.kernel.org/show_bug.cgi?id=60824#c6 (https://bugzilla.kernel.org/show_bug.cgi?id=60824#c6) patch to the 3.11.3 and compile again, it might fix the issue with your BT.
Later I will find some time upgrade the kernel but for now I like to get a proper kexecboot and stabel 3.11.3 going before messing around with a new kernel.
-
daalnroti:
I don't think there'll be any need for that patch as I've got my phone to pair with my Z but I'm still working on getting the tether working as that dbus-send command on the Arch wiki didn't work for me.
-
Not sure what's going on.....
Been trying to get the Arch tarball untarred on my laptop running LM17.....but keep getting different error messages...
Either can't change ownership or other messages...
I'm doing the tar command as root in terminal.....
Hmmmm.....................
Assume once I am able to uncompress file onto my SD card, I'll just copy them over to my microdrive partition.....
-
So you're using a command ike
bsdtar xvf Arch.tar.gz -C /mnt/cf
Or similar to extract are you?
Note you have to extract Arch to a Linux partition or you'll get errors - vfat, exfat etc won't work.
-
So you're using a command ike
bsdtar xvf Arch.tar.gz -C /mnt/cf
Or similar to extract are you?
Note you have to extract Arch to a Linux partition or you'll get errors - vfat, exfat etc won't work.
Oops....forgot about bsdtar....been using tar....
OK, installed bsdtar.....
And another oops....was trying to extract to a vfat formatted card.....
Just downloaded Arch tarball again....
Will try again to extract to card in the morning....had a long day at work.....
Thanks for your help...
-
My SparkLAN WCFM-100 finally arrived but its not working properly unfortunately.
Before I could use it at all I had to copy the firmware into the right dir as the current Z ALARM kernel tarball didn't include any libertas firmware so I created /lib/firmware/libertas and I copied these files into it:
cf8385.bin
cf8385_helper.bin
I had these files under /usr/lib/firmware/libertas/ on my Arch Linux PC. I expect they are shipped with most kernels / distros. I wouldn't think the architecture of the kernel would matter.
I had to manually download and install libnl, dialog and wpa-supplicant before I was able to run netctl's wifi-menu program. It found my access point fine and let me connect but a few seconds after running
pacman -Syu
I start to get and endless stream of errors like:
libertas_cs 0.0 wlan0: TX lockup detected
netctl / Arch seemed to be defaulting to IPv6 so I disabled that with the ipv6.disable=1 kernel argument in boot.cfg and rebooted but I still have the same problem. pacman doesn't even finish syncing before the TX lockup error breaks the connection.
I wonder if libertas_cs still has a maintainer? :/
-
OK, here's where I am at...
1. Installed kexecboot on my Z and it boots up with it
2. Created ext2 partitions on microdrive. Will change to ext3 or ext4 later after I get Arch running on Z....
3. Extracted Arch tarball using bsdtar to my SD card
4. Copied boot.cfg, contents of 3.11.3-c3x00, and zImage-3.11.3-c3x00 to /boot on SD card
5. Copied contents of firmware to lib/firmware on SD card [ see a lot of individual files, not in folders in /firmware, is this OK? There's lots of folders in there too...]
6. Copied modules for kernel 3.11.3 to /usr/lib/modules on SD card
In /boot on SD card I see another zImage file there besides zImage-3.11.3-c3x00. Should I delete the zImage file? Do I need to then rename zImage-3.11.3-c3x00 to be zImage?
From here (assuming I have contents of the SD card correct) I plan on copying the contents of the SD card over to one of my microdrive partitions and then boot up Zaurus and hope that it works....
Thanks.
-
Mark:
Sounds like you're pretty much there -have you tried booting it yet?
I don't think the extra kernel image in /boot really matters - I deleted it without any probs. All that really matters in the kexec config is that the path to the kernel in boot.cfg is correct.
daalnroti:
The only report I've found of someone having my wifi prob is this:
http://lists.infradead.org/pipermail/liber...May/003490.html (http://lists.infradead.org/pipermail/libertas-dev/2011-May/003490.html)
Thankfully he includes a patch so I'd appreciate it if you could try applying it for me if it never got mainlined?
Thanks!
-
Mark:
Sounds like you're pretty much there -have you tried booting it yet?
I don't think the extra kernel image in /boot really matters - I deleted it without any probs. All that really matters in the kexec config is that the path to the kernel in boot.cfg is correct.
Haven't booted it yet.....
Still need to copy contents of SD card over to /dev/hda1 partition on microdrive.....
But have some issues now with mounting SD card...
Last time I used SD it was formatted as vfat...now it's ext2, at least when I read what it says in terminal on laptop when doing mount command. However, when I use the file explorer program window in LM17 and then open up properties about the SD card it says 'ext3/ext4' ! How do I know which one is correct?
And I assume that if card is actually ext3 or ext4 that would explain why I can't mount card on Z, right?
But if card is ext2 as it says in terminal, then how can I mount card now?
# mount /dev/mmcda1 /mnt/card
mount: Mounting /dev/mmcda1 on /mnt/card failed: Invalid argument
And when I check with dmesg:
mmcda: mmcda1
mmcda: mmcda1
EXT3-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
EXT2-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
Any suggestions?................
Thanks for your help....
-
My SparkLAN WCFM-100 finally arrived but its not working properly unfortunately.
Before I could use it at all I had to copy the firmware into the right dir as the current Z ALARM kernel tarball didn't include any libertas firmware so I created /lib/firmware/libertas and I copied these files into it:
cf8385.bin
cf8385_helper.bin
I had these files under /usr/lib/firmware/libertas/ on my Arch Linux PC. I expect they are shipped with most kernels / distros. I wouldn't think the architecture of the kernel would matter.
I had to manually download and install libnl, dialog and wpa-supplicant before I was able to run netctl's wifi-menu program. It found my access point fine and let me connect but a few seconds after running
pacman -Syu
I start to get and endless stream of errors like:
libertas_cs 0.0 wlan0: TX lockup detected
netctl / Arch seemed to be defaulting to IPv6 so I disabled that with the ipv6.disable=1 kernel argument in boot.cfg and rebooted but I still have the same problem. pacman doesn't even finish syncing before the TX lockup error breaks the connection.
I wonder if libertas_cs still has a maintainer? :/
Firmware : Yes, you need to copy additional firmwares. Not all can be distributed with the kernel. There exists a firmware package for Arch x86 and ALARM. The firmwares are the same, between the versions as far as I know but better to double check. This here might be an outdated guide :
http://linuxwireless.sipsolutions.net/en/u...ivers/libertas/ (http://linuxwireless.sipsolutions.net/en/users/Drivers/libertas/)
Check the kernel git repo for latest firmwares :
http://git.kernel.org/cgit/linux/kernel/gi...t/tree/libertas (http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/libertas)
IPv6 : Arch has as default IPv6 support, you can disable it if you have no use for it as you mentioned. It does not interfere with normal IPv4 operation and is unlikely the reason for the issue you have.
Libertas_CS : I have no such card and can not troubleshoot or test for you. You may have a faulty card or the driver is unstable. There might be some kernel modules settings for this driver that can improve the connection. Also the WiFi Access Point you are connecting to may show some hints why you get TX lockups ? Maybe try to limit you WiFi speed. Can you show some dmesg etc and config files ?
-
OK, here's where I am at...
1. Installed kexecboot on my Z and it boots up with it
2. Created ext2 partitions on microdrive. Will change to ext3 or ext4 later after I get Arch running on Z....
3. Extracted Arch tarball using bsdtar to my SD card
4. Copied boot.cfg, contents of 3.11.3-c3x00, and zImage-3.11.3-c3x00 to /boot on SD card
5. Copied contents of firmware to lib/firmware on SD card [ see a lot of individual files, not in folders in /firmware, is this OK? There's lots of folders in there too...]
6. Copied modules for kernel 3.11.3 to /usr/lib/modules on SD card
In /boot on SD card I see another zImage file there besides zImage-3.11.3-c3x00. Should I delete the zImage file? Do I need to then rename zImage-3.11.3-c3x00 to be zImage?
From here (assuming I have contents of the SD card correct) I plan on copying the contents of the SD card over to one of my microdrive partitions and then boot up Zaurus and hope that it works....
Thanks.
You can name the kernel file anything you like as long as your boot.cfg is correct.
Kexecboot will show also kernels from SD or Mircordrive that are not listed in boot.cfg but you will be unlikely to get them to boot correctly without the correct parameters.
The latest kernel release from my github (v0.4) has only one kernel image inside to avoid confusion.
When booting kexecboot, make sure you have no SD card inserted with a kernel image on it.
Also you can ungzip the ALARM tarball using " gunzip -d " to your SD. Then properly untar the uncompressed tar to your microdrive.
Copying your files from SD to Microdrive might work if done correctly as root, better would be to untar directly to preserve all permissions.
-
Mark:
Sounds like you're pretty much there -have you tried booting it yet?
I don't think the extra kernel image in /boot really matters - I deleted it without any probs. All that really matters in the kexec config is that the path to the kernel in boot.cfg is correct.
Haven't booted it yet.....
Still need to copy contents of SD card over to /dev/hda1 partition on microdrive.....
But have some issues now with mounting SD card...
Last time I used SD it was formatted as vfat...now it's ext2, at least when I read what it says in terminal on laptop when doing mount command. However, when I use the file explorer program window in LM17 and then open up properties about the SD card it says 'ext3/ext4' ! How do I know which one is correct?
And I assume that if card is actually ext3 or ext4 that would explain why I can't mount card on Z, right?
But if card is ext2 as it says in terminal, then how can I mount card now?
# mount /dev/mmcda1 /mnt/card
mount: Mounting /dev/mmcda1 on /mnt/card failed: Invalid argument
And when I check with dmesg:
mmcda: mmcda1
mmcda: mmcda1
EXT3-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
EXT2-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
Any suggestions?................
Thanks for your help....
Try again from scratch with a known working card.
You can use FAT on the SD card if you dont extract the tar ball onto it, just decompress it.
(Better use ext2)
Ungzip ALARM tar ball to SD card. You should have a file ending in .tar
Boot into D+B mode.
Mount Microdrive and SD card.
Extract tar ball to Microdrive from SD card.
Hope this helps.
We need to get a HowTo together to help with these installation steps. I may find some time this week.
Cheers!
-
Mark:
Sounds like you're pretty much there -have you tried booting it yet?
I don't think the extra kernel image in /boot really matters - I deleted it without any probs. All that really matters in the kexec config is that the path to the kernel in boot.cfg is correct.
Haven't booted it yet.....
Still need to copy contents of SD card over to /dev/hda1 partition on microdrive.....
But have some issues now with mounting SD card...
Last time I used SD it was formatted as vfat...now it's ext2, at least when I read what it says in terminal on laptop when doing mount command. However, when I use the file explorer program window in LM17 and then open up properties about the SD card it says 'ext3/ext4' ! How do I know which one is correct?
And I assume that if card is actually ext3 or ext4 that would explain why I can't mount card on Z, right?
But if card is ext2 as it says in terminal, then how can I mount card now?
# mount /dev/mmcda1 /mnt/card
mount: Mounting /dev/mmcda1 on /mnt/card failed: Invalid argument
And when I check with dmesg:
mmcda: mmcda1
mmcda: mmcda1
EXT3-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
EXT2-fs: unsupported inode size: 256
mmcda: mmcda1
mmcda: mmcda1
Any suggestions?................
Thanks for your help....
Try again from scratch with a known working card.
You can use FAT on the SD card if you dont extract the tar ball onto it, just decompress it.
(Better use ext2)
Ungzip ALARM tar ball to SD card. You should have a file ending in .tar
Boot into D+B mode.
Mount Microdrive and SD card.
Extract tar ball to Microdrive from SD card.
Hope this helps.
We need to get a HowTo together to help with these installation steps. I may find some time this week.
Cheers!
OK, will try again....thanks!
-
OK, here's where I am at...
1. Installed kexecboot on my Z and it boots up with it
2. Created ext2 partitions on microdrive. Will change to ext3 or ext4 later after I get Arch running on Z....
3. Extracted Arch tarball using bsdtar to my SD card
4. Copied boot.cfg, contents of 3.11.3-c3x00, and zImage-3.11.3-c3x00 to /boot on SD card
5. Copied contents of firmware to lib/firmware on SD card [ see a lot of individual files, not in folders in /firmware, is this OK? There's lots of folders in there too...]
6. Copied modules for kernel 3.11.3 to /usr/lib/modules on SD card
In /boot on SD card I see another zImage file there besides zImage-3.11.3-c3x00. Should I delete the zImage file? Do I need to then rename zImage-3.11.3-c3x00 to be zImage?
From here (assuming I have contents of the SD card correct) I plan on copying the contents of the SD card over to one of my microdrive partitions and then boot up Zaurus and hope that it works....
Thanks.
You can name the kernel file anything you like as long as your boot.cfg is correct.
Kexecboot will show also kernels from SD or Mircordrive that are not listed in boot.cfg but you will be unlikely to get them to boot correctly without the correct parameters.
The latest kernel release from my github (v0.4) has only one kernel image inside to avoid confusion.
When booting kexecboot, make sure you have no SD card inserted with a kernel image on it.
Also you can ungzip the ALARM tarball using " gunzip -d " to your SD. Then properly untar the uncompressed tar to your microdrive.
Copying your files from SD to Microdrive might work if done correctly as root, better would be to untar directly to preserve all permissions.
Thanks for all the info! Very helpful!
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....
Thanks!
UPDATE:
Tried it, but now get other error message:
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....
Thanks!
UPDATE:
Tried it, but now get other error message:
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#
This is odd, did you try with the bsd-tar from the kexecboot package ?
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....
Thanks!
UPDATE:
Tried it, but now get other error message:
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#
This is odd, did you try with the bsd-tar from the kexecboot package ?
Ummmm.....no......used 'tar -xvf.....'
Just tried again....
# bsdtar -xvf.....
bsdtar: not found
How do I either 'install' bsdtar or invoke it from kexecboot package?
Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....
Thanks.
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....
Thanks!
UPDATE:
Tried it, but now get other error message:
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#
This is odd, did you try with the bsd-tar from the kexecboot package ?
Ummmm.....no......used 'tar -xvf.....'
Just tried again....
# bsdtar -xvf.....
bsdtar: not found
How do I either 'install' bsdtar or invoke it from kexecboot package?
Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....
Thanks.
No worries, we will get it going.
Copy the bsd-tar from the oe-kexecboot package to the SD card alongside with the ALARM tar file.
Mount SD card and Microdrive.
Then try something like this :
cd /mnt/hda1
/path/to/bsd-tar -xvf /path/to/ALARM.tar
Did you gunzip the ALARM tar.gz before saving it on the SD ?
Maybe document all the steps you do and share.
-
Just tried to decompress the Arch tarball onto my microdrive from my SD card.....
Get the following:
# tar -xvf ArchLinuxARM-armv5-latest.tar -C /mnt/arch
tar: Error opening 'ArchLinuxARM-armv5-latest.tar' : No such file or directory
#
# ls
ArchLinuxARM-armv5-latest.tar
....plus other files listed.....
I am in directory of the arch tarball on SD card (vfat)...
/dev/hda1 (on microdrive...) is mounted on /mnt/arch....
What am I doing wrong?.................
Try this :
cd /mnt/arch
tar -xvf /path/to/ArchLinuxARM-armv5-latest.tar
You need to change /path/to to the SD card location where your tar is.
Hmmmm...thought I could do it the reverse....I cd'd to the directory of the Arch tarball is located and provided path to where the uncompressed files go to......
Oh well, will try your suggestion.....
Thanks!
UPDATE:
Tried it, but now get other error message:
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Bad tar header, skipping
tar: Error exit delayed from previous errors
#
This is odd, did you try with the bsd-tar from the kexecboot package ?
Ummmm.....no......used 'tar -xvf.....'
Just tried again....
# bsdtar -xvf.....
bsdtar: not found
How do I either 'install' bsdtar or invoke it from kexecboot package?
Sorry, if my questions are dumb.....but I know just enough linux to be dangerous....
Thanks.
No worries, we will get it going.
Copy the bsd-tar from the oe-kexecboot package to the SD card alongside with the ALARM tar file.
Mount SD card and Microdrive.
Then try something like this :
cd /mnt/hda1
/path/to/bsd-tar -xvf /path/to/ALARM.tar
Did you gunzip the ALARM tar.gz before saving it on the SD ?
Maybe document all the steps you do and share.
Think I gunzip'd it.....I think.....
Just checked the oe-kexexboot package.....
Don't see bsdtar there, but I do see gnu-tar there....is this the one?
Thanks!
UPDATE:
OK, used gnu-tar file......
cd /mnt/hda1
/path/to/gnu-tar -xvf /path/to/ALARM.tar
and now it's scrolling through a long list.....very fast....
But I see error messages.....on each line....
Could not create symlink....: No such file or directory
Could not create file.......: No such file or directory....
Thanks!
-
Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....
I know it's easy for me to say.....
-
Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....
I know it's easy for me to say.....
aw, my fault. Of course I meant gnu-tar.
Ok,
do a reboot, go into D+B emergency console.
there do :
fdisk /dev/hda
the press "p" then "enter" and post us the output. use "q" then "enter" to quit fdisk.
after do:
mkdir /mnt/arch
mount /dev/hda1 /mnt/arch
and then:
mount
df -h
ls -la /mnt/arch
and post the output.
also please :
mkdir /mnt/sdcard
mount /dev/mmcblk0p1 /mnt/sdcard
mount
df -h
ls -la /mnt/sdcard
you can take photos and post them if you can not ssh / telnet to the device yet.
It could be your /dev/hda is not partitioned, formated properly (/dev/hda1 /dev/hda2 etc)
Cheers.
-
Think it would be really helpful if there was a way to post the Arch tarball in the right format to untar on the Z.....
I know it's easy for me to say.....
Hi ArchiMark,
the idea would be to make a custom tar ball, containing kernel and initial fixes to get someone going.
I will see if I can provide one once I got a new kexecboot going.
What network / wifi / bt cards do you use ArchiMark?
Any needs for special USB drivers etc ?
Cheers!
-
New kexeboot release added : arch-kexecboot (https://github.com/greguu/linux-3.11.3-borzoi/releases/tag/v0.4)
If you are keen, please test.
- Based on Linux Kernel 3.5
- Based on Kexecboot 0.6 (latest release)
- Boots Linux kernels from ext2/3/4 (SD,CF,USB) and ubifs (NAND)
- Features ArchLinux logos and theming (wonder why I did that)
- Auto Boots first entry in your boot.cfg after 5 seconds (hard coded)
I will attempt to build a newer kernel 3.18 series first, maybe 4.2. series later in the coming days.
-
Hi ArchiMark,
here a step by step guide to get you a ALARM booting of a SD card. From there everything else should be a breeze.
Following steps have been confirmed and tested. Any issues , just ask.
00. Wipe your microdrive partitions (OPTIONAL)
(following steps will erase all on your microdrive card)
Boot into D+B emergency then do a:
fdisk /dev/hda
"d" enter until all partitions are deleted
"w" to write and exit
01. Install arch-kexecboot from my github
https://github.com/greguu/linux-3.11.3-borz...leases/tag/v0.4 (https://github.com/greguu/linux-3.11.3-borzoi/releases/tag/v0.4)
02. On you linux machine LM17 download
http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz (http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz)
and save it on your home folder /home/yourusername
open terminal as user
cd ~
wget http://archlinuxarm.org/os/ArchLinuxARM-armv5-latest.tar.gz
03. Take a working SD card and place it in your LM17 laptop
(do not mount it from you desktop environment)
(following steps will erase all on your SD card)
open a terminal and become root
(this is an example, change sdc to the sdX that reflects the SD card)
fdisk /dev/sdc
"d" enter until all partitions are deleted
then
"n" enter to create a new partition
"p" to set primary
"1" to set partition number one
and double enter to accept default size (full SD card)
"p" to verify you new partition layout
"w" to write to disk
Then format to ext4 and mount.
mkfs.ext4 /dev/sdc1
mkdir /mnt/sdarch
mount /dev/sdc1 /mnt/sdarch
04. Unpack the ArchLinuxARM-armv5-latest.tar.gz
cd /mnt/sdarch
tar xf /home/yourusername/ArchLinuxARM-armv5-latest.tar.gz (this will take a while)
05. Remove zImage from /mnt/sdarch/boot
06. Copy kernel "zImage-3.11.3-c3x00" and "boot.cfg" from my git hub to /mnt/sdarch/boot
07. Edit boot.cfg to look like this:
LABEL=ArchLinuxARM
KERNEL=/boot/zImage-3.11.3-c3x00
APPEND=root=/dev/mmcblk0p1 rootfstype=ext4 fbcon=rotate:1 noinitrd loglevel=3
08. Copy 3.11.3-c3x00 folder to /mnt/sdarch/lib/modules
(no need to copy firmware files, they are already installed)
(you can remove the 4.x kernel and other modules folder under /mnt/sdarch/lib/modules)
09. Edit /mnt/sdarch/etc/fstab to look like this
/dev/mmcblk0p1 / ext4 noatime,nodiratime,commit=600,reservation,defaults,errors=remount-ro 0 1
10. Download keymap file from github , borzoi.map.gz
as root :
cd /mnt/sdarch/usr/share/kbd/keymaps
mkdir zaurus
cp /home/yourusername/borzoi.map.gz /mnt/sdarch/usr/share/kbd/keymaps/zaurus
create and edit /mnt/sdarch/etc/vconsole.conf to like this:
KEYMAP=borzoi
11. Unmount SD card and place in Z, boot Z ! (user "root" / pass "root" )
12. Then repeat all these steps for the microdrive
( Once you got ALARM on your micro drive, keep this SD card, it might come in handy as a rescue system.)
-
daalnroti:
The only report I've found of someone having my wifi prob is this:
http://lists.infradead.org/pipermail/liber...May/003490.html (http://lists.infradead.org/pipermail/libertas-dev/2011-May/003490.html)
Thankfully he includes a patch so I'd appreciate it if you could try applying it for me if it never got mainlined?
Thanks!
Hi danboid,
this patch is already included in 3.11.3
it is just for tx timeouts.
the issue you experience are tx lockups, different matter.
there is code about the lockups in main.c of the libertas driver :
/**
* lbs_tx_lockup_handler - handles the timeout of the passing of TX frames
* to the hardware. This is known to frequently happen with SD8686 when
* waking up after a Wake-on-WLAN-triggered resume.
*
* @data: &struct lbs_private pointer
*/
static void lbs_tx_lockup_handler(unsigned long data)
{
struct lbs_private *priv = (struct lbs_private *)data;
unsigned long flags;
lbs_deb_enter(LBS_DEB_TX);
spin_lock_irqsave(&priv->driver_lock, flags);
netdev_info(priv->dev, "TX lockup detected\n");
if (priv->reset_card)
priv->reset_card(priv);
priv->dnld_sent = DNLD_RES_RECEIVED;
wake_up_interruptible(&priv->waitq);
spin_unlock_irqrestore(&priv->driver_lock, flags);
lbs_deb_leave(LBS_DEB_TX);
}
I would suggest to get at least your other WiFi card going first and then see maybe if a newer kernel does make the libertas_cs work.
Did you buy the libertas card new ?
Or use a USB WiFi on a powered hub, or a CF/USB ethernet adapter to get further.
I am happy to apply patches but I am not sure removing the lockup handler fixes your issue. You want me to try ?
-
I dared to post on ALARM forums after being registered since 2012!
http://archlinuxarm.org/forum/viewtopic.php?f=27&t=9381 (http://archlinuxarm.org/forum/viewtopic.php?f=27&t=9381)
what a lame attempt to get more users
-
daalnroti:
The only report I've found of someone having my wifi prob is this:
http://lists.infradead.org/pipermail/liber...May/003490.html (http://lists.infradead.org/pipermail/libertas-dev/2011-May/003490.html)
Thankfully he includes a patch so I'd appreciate it if you could try applying it for me if it never got mainlined?
Thanks!
Hi danboid,
this patch is already included in 3.11.3
it is just for tx timeouts.
the issue you experience are tx lockups, different matter.
there is code about the lockups in main.c of the libertas driver :
/**
* lbs_tx_lockup_handler - handles the timeout of the passing of TX frames
* to the hardware. This is known to frequently happen with SD8686 when
* waking up after a Wake-on-WLAN-triggered resume.
*
* @data: &struct lbs_private pointer
*/
static void lbs_tx_lockup_handler(unsigned long data)
{
struct lbs_private *priv = (struct lbs_private *)data;
unsigned long flags;
lbs_deb_enter(LBS_DEB_TX);
spin_lock_irqsave(&priv->driver_lock, flags);
netdev_info(priv->dev, "TX lockup detected\n");
if (priv->reset_card)
priv->reset_card(priv);
priv->dnld_sent = DNLD_RES_RECEIVED;
wake_up_interruptible(&priv->waitq);
spin_unlock_irqrestore(&priv->driver_lock, flags);
lbs_deb_leave(LBS_DEB_TX);
}
I would suggest to get at least your other WiFi card going first and then see maybe if a newer kernel does make the libertas_cs work.
Did you buy the libertas card new ?
Or use a USB WiFi on a powered hub, or a CF/USB ethernet adapter to get further.
I am happy to apply patches but I am not sure removing the lockup handler fixes your issue. You want me to try ?
Yes, the libertas card is new. I've only tried it with the one AP in work so far but I'll get to try it at home tonight,
I'm pretty much out of ideas for getting my old wifi card to work under ALARM - it just won't find any primary firmware and I've tried every one I could find.
I don't think I've got access to any other devices with a CF slot so I may end up having to reinstall OBSD or pdaX to see if it works with those unless you have some kernel options I can try that might help?
I've not finished my experiments with BT tethering. There is a script called 'test-network' included with bluez that can supposedly configure BT tethering although I'll only get ~2Mb/s tops over my BT2 adapter.
I'd like to get a CF ethernet adapter but I was struggling to find a new one. I used to have a USB ethernet adapter that worked well with Linux but I lent it to a friend and I think he's lost it so I'll prob buy another one of those as they're cheap and more likely to work than USB wifi adapters.
-
I'll be installing the new kexecboot later too as I want the timeout auto-boot feature.
Thanks daalnroti!
-
Yes, the libertas card is new. I've only tried it with the one AP in work so far but I'll get to try it at home tonight,
I'm pretty much out of ideas for getting my old wifi card to work under ALARM - it just won't find any primary firmware and I've tried every one I could find.
I don't think I've got access to any other devices with a CF slot so I may end up having to reinstall OBSD or pdaX to see if it works with those unless you have some kernel options I can try that might help?
I've not finished my experiments with BT tethering. There is a script called 'test-network' included with bluez that can supposedly configure BT tethering although I'll only get ~2Mb/s tops over my BT2 adapter.
I'd like to get a CF ethernet adapter but I was struggling to find a new one. I used to have a USB ethernet adapter that worked well with Linux but I lent it to a friend and I think he's lost it so I'll prob buy another one of those as they're cheap and more likely to work than USB wifi adapters.
Hi danboid,
I understand your frustration with the CF WiFi card you bought and it is not working. As mentioned, give me some time and I will get a newer kernel going, it _might_ work with a new kernel.
Kernel options : I will have a look into the matter, but since I do not have that card, it will be hard to test.
USB Ethernet : I use a ASIX AX772 USB 10/100 that works without additional powered USB hub
CF WiFi : my DLINK works fine, just not as fast.
CF Ethernet : the BUFFALO 10mbit card also is supported and works.
No need to give up, but if you want to test with obsd or pdax rom, fine. It will help to rule out any kernel issues or alarm package or firmware problems.
Thanks for trying. We will get there.
I wonder what ArchiMark is using :?
Cheers
-
I've not finished my experiments with BT tethering. There is a script called 'test-network' included with bluez that can supposedly configure BT tethering although I'll only get ~2Mb/s tops over my BT2 adapter.
does this mean you can tether ? and get a connection ?
if so , are you able to do a pacman -Syu successfully ?
-
I'll be installing the new kexecboot later too as I want the timeout auto-boot feature.
Thanks daalnroti!
great, did you get it going and did it auto boot ?
I tested on my Z, but would be good to know if it works for someone else, too.
-
Well, I made some effort , posting on #kexecboot at freenode, to the last know Z users to lurk around... lets hope some join.
-
aw, my fault. Of course I meant gnu-tar.
Ok,
do a reboot, go into D+B emergency console.
there do :
fdisk /dev/hda
the press "p" then "enter" and post us the output. use "q" then "enter" to quit fdisk.
Number of cylinders for this disk is set to 11905.
Nothing wrong with that, but it's larger than 1024,
and could in certain setups.....
1)...
2)....
Disk /dev/hda: 6144MB, 6144284672 bytes
16 heads, 63 sectors/track, 11905 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks ID System
/dev/hda1 1 3876 1953472+ 83 Linux
/dev/hda2 3877 4846 488880 82 Linux Swap
/dev/hda3 4847 11905 3557736 83 Linux
after do:
mkdir /mnt/arch
mount /dev/hda1 /mnt/arch
and then:
mount
df -h
ls -la /mnt/arch
and post the output.
# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
/proc on /proc type proc (rw)
/dev/shm on /tmp type tmpfs (rw)
none on /dev/pts type devpts (rw)
/dev/hda1 on /mnt/arch type ext2 (rw)
# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 7.7M 7.7M 0 100% /
/dev/root 7.7M 7.7M 0 100% /
/dev/shm 16.0M 0 16.0M 0% /tmp
/dev/hda1 1.8G 20.0K 1.7G 0% /mnt/arch
#ls -la /mnt/arch
drwxrwxr-x 2 root root 1024 Feb 21 2006 .
drwxr-xr-x 18 root root 1024 Feb 21 2006 ..
-rw-rw-r-- 1 root root 272 Jan 14 2006 .profile
also please :
mkdir /mnt/sdcard
mount /dev/mmcblk0p1 /mnt/sdcard
mount
df -h
ls -la /mnt/sdcard
you can take photos and post them if you can not ssh / telnet to the device yet.
It could be your /dev/hda is not partitioned, formated properly (/dev/hda1 /dev/hda2 etc)
Cheers.
*** Please note that my SD is automatically recognized as /dev/mmcda1
So, when I tried to do what your request, it returns error message:
mount: Mounting /dev/mmcblk0p1 on /mnt/sdcard failed: No such file or directory
Here's what I see for /dev/mmcda1 which is mounted on /mnt/card automatically:
#df -h
/dev/mmcda1 1.8G 639.1M 1.2G 34% /mnt/card
# ls -la
**** SEE Attached Photo Below ****
[img]http://i473.photobucket.com/albums/rr100/ArchiMark/P1070863_zps4eededjm.jpg\" border=\"0\" class=\"linked-image\" /]
THANKS for all your help with this!
-
Hi danboid,
I understand your frustration with the CF WiFi card you bought and it is not working. As mentioned, give me some time and I will get a newer kernel going, it _might_ work with a new kernel.
Kernel options : I will have a look into the matter, but since I do not have that card, it will be hard to test.
USB Ethernet : I use a ASIX AX772 USB 10/100 that works without additional powered USB hub
CF WiFi : my DLINK works fine, just not as fast.
CF Ethernet : the BUFFALO 10mbit card also is supported and works.
No need to give up, but if you want to test with obsd or pdax rom, fine. It will help to rule out any kernel issues or alarm package or firmware problems.
Thanks for trying. We will get there.
I wonder what ArchiMark is using :?
Cheers
I use the following cards. They have always worked well with all the various OS's I've used in the past:
CF Ethernet: Socket 10/100
CF WiFi: AmbiCom WL1100-CF
-
THANKS for all your help with this!
No worries, happy to help.
Well this looks all ok to me.
There might be issues with the D+B emergency mode not being able to untar or something else.
Danboid had issues but somehow managed to get it working.
If it is not too much to ask, I would recommend to use the SD card guide I posted earlier.
This will give you a backup system and a good start to install arch on the microdrive while running from SD card.
This way you can use the full 6GB (and swap) because your backup system sits on an SD card. (5.8 GB + 0.2 GB swap)
Let me know if you have issues with the how to.
Your cards are very likely supported, would be good to test once you got Arch going.
You can test your cards once you got Arch on a SD card, to make sure, before proceeding.
Cheers and thanks for trying
-
THANKS for all your help with this!
No worries, happy to help.
Well this looks all ok to me.
There might be issues with the D+B emergency mode not being able to untar or something else.
Danboid had issues but somehow managed to get it working.
If it is not too much to ask, I would recommend to use the SD card guide I posted earlier.
This will give you a backup system and a good start to install arch on the microdrive while running from SD card.
This way you can use the full 6GB (and swap) because your backup system sits on an SD card. (5.8 GB + 0.2 GB swap)
Let me know if you have issues with the how to.
Your cards are very likely supported, would be good to test once you got Arch going.
You can test your cards once you got Arch on a SD card, to make sure, before proceeding.
Cheers and thanks for trying
I will be glad to try again by using your SD card guide.....
All sounds good....I've been mostly using my 2GB Sandisk card....I have other larger (16GB...) newer SD cards, but wasn't sure if Zaurus would recognize them or if such large cards were even needed...
And THANKS again for all your help....
Will report back after I've tried this out....
-
I will be glad to try again by using your SD card guide.....
All sounds good....I've been mostly using my 2GB Sandisk card....I have other larger (16GB...) newer SD cards, but wasn't sure if Zaurus would recognize them or if such large cards were even needed...
And THANKS again for all your help....
Will report back after I've tried this out....
Hi ArchiMark,
1GB would be enough for a backup / testing Arch SD card.
Make sure to use a "really working" card. SD cards can cause all sorts of issues when being faulty.
I got a 16GB SD that works fine under Arch, for testing I would recommend max 4GB to rule out any issues.
-
Progress on the networking front n' stuf!
As you can imagine I got a bit tired of fighting CF wifi issues and decided to buy a USB to ethernet adapter. I've not given up on the wifi. I still really need to get CF wifi working to use the Z for what I mainly want it for which is a wireless pocket SSH client.
I bought the Maplin £15 USB 2.0 to Ethernet adapter which according to lsusb is:
0b95:7720 ASIX Electronics Corp. AX88772
It works fine with Linux but on the Zaurus I need to plug it into a powered USB hub to use it so its not ideal. This has enabled me to finally run the holy `pacman -Syu` successfully at last! Doing so updated systemd and some other stuff but it hasn't done anything to fix my wifi issue or the swap problem.
Hopefully the newer kernel will fix my wifi prob but I think we'll be lucky. I suspect no-one has noticed my problem because no-one is using CF wifi cards anymore apart from me!
I didn't give you all the details with my wifi card, mainly that it prints the following whenever I insert it and I don't think its so good:
Oct 14 20:22:06 alarm kernel: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
Oct 14 20:22:06 alarm kernel: pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
Oct 14 20:22:06 alarm kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 14 20:22:06 alarm kernel: lib80211: common routines for IEEE802.11 drivers
Oct 14 20:22:06 alarm kernel: lib80211_crypt: registered algorithm 'NULL'
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): 00:0e:8e:11:68:50, fw 5.0.20p2, cap 0x00000303
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x00a3 failed: 2
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x10ac failed: 2
Oct 14 20:22:07 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x00a3 failed: 2
Oct 14 20:22:07 alarm kernel: libertas_cs 0.0 wlan0: Marvell WLAN 802.11 adapter
I've not updated kexec yet but I'll let you know when I do. Right now I have the unstoppable urge to finally get some apps installed and compiled!
-
Progress on the networking front n' stuf!
As you can imagine I got a bit tired of fighting CF wifi issues and decided to buy a USB to ethernet adapter. I've not given up on the wifi. I still really need to get CF wifi working to use the Z for what I mainly want it for which is a wireless pocket SSH client.
I bought the Maplin £15 USB 2.0 to Ethernet adapter which according to lsusb is:
0b95:7720 ASIX Electronics Corp. AX88772
It works fine with Linux but on the Zaurus I need to plug it into a powered USB hub to use it so its not ideal. This has enabled me to finally run the holy `pacman -Syu` successfully at last! Doing so updated systemd and some other stuff but it hasn't done anything to fix my wifi issue or the swap problem.
Hopefully the newer kernel will fix my wifi prob but I think we'll be lucky. I suspect no-one has noticed my problem because no-one is using CF wifi cards anymore apart from me!
I didn't give you all the details with my wifi card, mainly that it prints the following whenever I insert it and I don't think its so good:
Oct 14 20:22:06 alarm kernel: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
Oct 14 20:22:06 alarm kernel: pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
Oct 14 20:22:06 alarm kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 14 20:22:06 alarm kernel: lib80211: common routines for IEEE802.11 drivers
Oct 14 20:22:06 alarm kernel: lib80211_crypt: registered algorithm 'NULL'
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): 00:0e:8e:11:68:50, fw 5.0.20p2, cap 0x00000303
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x00a3 failed: 2
Oct 14 20:22:06 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x10ac failed: 2
Oct 14 20:22:07 alarm kernel: libertas_cs 0.0 (unregistered net_device): PREP_CMD: command 0x00a3 failed: 2
Oct 14 20:22:07 alarm kernel: libertas_cs 0.0 wlan0: Marvell WLAN 802.11 adapter
I've not updated kexec yet but I'll let you know when I do. Right now I have the unstoppable urge to finally get some apps installed and compiled!
To bad with the ASIX USB to ethernet. Guess you got a model that chews more than 180mA
The libertas_cs dmesg output looks ok, "the “command 0×00a3 failed” messages are harmless, and have to do with features that are not supported."
I would try to connect to an AP without encryption to test if that issue is WPA related.
Also it may pay to play around with iwconfig to set the rate etc.
example:
iwconfig wlan0 rate 3
and see if that gives a stable connection .
rates supported:
12 54 Mbps
11 48 Mbps
10 36 Mbps
9 24 Mbps
8 18 Mbps
7 12 Mbps
6 9 Mbps
5 6 Mbps
4 Reserved
3 11 Mbps
2 5.5 Mbps
1 2 Mbps
0 1 Mbps
-
good summary of USB ethernet adapters and if they need powered usb hub.
http://elinux.org/RPi_USB_Ethernet_adapters (http://elinux.org/RPi_USB_Ethernet_adapters)
-
Thanks daalnroti!
I'll experiment with the speed settings tomorrow and report back.
xf86-video-fbdev works under Arch but the screen is in the wrong orientation (which I'm sure can be fixed with a xrandr command and/or an xorg.conf file) and I have no idea how to configure the touchscreen with is not calibrated currently. The good news is suspend seems to work fine under both X and the console by default.
As I've already said, I don't think I'll really be using X much but I'm still interested to see if we can get it working properly.
-
I will be glad to try again by using your SD card guide.....
All sounds good....I've been mostly using my 2GB Sandisk card....I have other larger (16GB...) newer SD cards, but wasn't sure if Zaurus would recognize them or if such large cards were even needed...
And THANKS again for all your help....
Will report back after I've tried this out....
Hi ArchiMark,
1GB would be enough for a backup / testing Arch SD card.
Make sure to use a "really working" card. SD cards can cause all sorts of issues when being faulty.
I got a 16GB SD that works fine under Arch, for testing I would recommend max 4GB to rule out any issues.
Thanks for the added input, daalnroti...
Pretty sure my 2GB Sandisk card is working fine as I've put it in my laptops as well as Zaurus recently....
Good to know that a larger card should work OK with Arch later on....
-
Thanks daalnroti!
I'll experiment with the speed settings tomorrow and report back.
xf86-video-fbdev works under Arch but the screen is in the wrong orientation (which I'm sure can be fixed with a xrandr command and/or an xorg.conf file) and I have no idea how to configure the touchscreen with is not calibrated currently. The good news is suspend seems to work fine under both X and the console by default.
As I've already said, I don't think I'll really be using X much but I'm still interested to see if we can get it working properly.
I'll be glad to help test out X and getting it working as I'd like to have it if possible...
-
The X keymap needs some work too. As it stands I can't type a forward slash and other important characters like * and _ . I expect we'll be able to borrow the xorg.conf and keymap etc from pdaXrom or another X-based Z distro.
I'm sure you'll get it running eventually Mark but I can't really add anything to what daal and I have already told you about the pitfalls of uncompressing and installing Arch on the Z.
-
Thanks daalnroti!
I'll experiment with the speed settings tomorrow and report back.
xf86-video-fbdev works under Arch but the screen is in the wrong orientation (which I'm sure can be fixed with a xrandr command and/or an xorg.conf file) and I have no idea how to configure the touchscreen with is not calibrated currently. The good news is suspend seems to work fine under both X and the console by default.
As I've already said, I don't think I'll really be using X much but I'm still interested to see if we can get it working properly.
TOUCHSCREEN : I guess we need to port the touch screen calibration tool from pdaxroom. It was outdated back then already, maybe there is another way to calibrate now.
XORG ROTATE : this can be done via a command line parameter I think and also via xorg.conf
SPEED : this will be done via cpufreq but not sure the 624 will work, never tried.
-
The X keymap needs some work too. As it stands I can't type a forward slash and other important characters like * and _ . I expect we'll be able to borrow the xorg.conf and keymap etc from pdaXrom or another X-based Z distro.
I'm sure you'll get it running eventually Mark but I can't really add anything to what daal and I have already told you about the pitfalls of uncompressing and installing Arch on the Z.
I can have a look on my debian partition, I used xorg there and may have keymap too.
-
The X keymap needs some work too. As it stands I can't type a forward slash and other important characters like * and _ . I expect we'll be able to borrow the xorg.conf and keymap etc from pdaXrom or another X-based Z distro.
I'm sure you'll get it running eventually Mark but I can't really add anything to what daal and I have already told you about the pitfalls of uncompressing and installing Arch on the Z.
Understand, danboid.....thanks....
Thanks daalnroti!
I'll experiment with the speed settings tomorrow and report back.
xf86-video-fbdev works under Arch but the screen is in the wrong orientation (which I'm sure can be fixed with a xrandr command and/or an xorg.conf file) and I have no idea how to configure the touchscreen with is not calibrated currently. The good news is suspend seems to work fine under both X and the console by default.
As I've already said, I don't think I'll really be using X much but I'm still interested to see if we can get it working properly.
TOUCHSCREEN : I guess we need to port the touch screen calibration tool from pdaxroom. It was outdated back then already, maybe there is another way to calibrate now.
XORG ROTATE : this can be done via a command line parameter I think and also via xorg.conf
SPEED : this will be done via cpufreq but not sure the 624 will work, never tried.
The X keymap needs some work too. As it stands I can't type a forward slash and other important characters like * and _ . I expect we'll be able to borrow the xorg.conf and keymap etc from pdaXrom or another X-based Z distro.
I'm sure you'll get it running eventually Mark but I can't really add anything to what daal and I have already told you about the pitfalls of uncompressing and installing Arch on the Z.
I can have a look on my debian partition, I used xorg there and may have keymap too.
Thanks, daalnroti.....
-
06. Copy kernel "zImage-3.11.3-c3x00" and "boot.cfg" from my git hub to /mnt/sdarch/boot
Noticed in the there's two zImage-3.11.3-c3x00 files when I untarred '3.11.3-c3x00.tar.xz'.
One file has '-arch' at the end of the filename and was created after the other one.
Any reason to use one or the other?
Thanks.
-
06. Copy kernel "zImage-3.11.3-c3x00" and "boot.cfg" from my git hub to /mnt/sdarch/boot
Noticed in the there's two zImage-3.11.3-c3x00 files when I untarred '3.11.3-c3x00.tar.xz'.
One file has '-arch' at the end of the filename and was created after the other one.
Any reason to use one or the other?
Thanks.
the latest release has only one zImage. Please use the latest release : https://github.com/greguu/linux-3.11.3-borz...leases/tag/v0.4 (https://github.com/greguu/linux-3.11.3-borzoi/releases/tag/v0.4)
-
06. Copy kernel "zImage-3.11.3-c3x00" and "boot.cfg" from my git hub to /mnt/sdarch/boot
Noticed in the there's two zImage-3.11.3-c3x00 files when I untarred '3.11.3-c3x00.tar.xz'.
One file has '-arch' at the end of the filename and was created after the other one.
Any reason to use one or the other?
Thanks.
the latest release has only one zImage. Please use the latest release : https://github.com/greguu/linux-3.11.3-borz...leases/tag/v0.4 (https://github.com/greguu/linux-3.11.3-borzoi/releases/tag/v0.4)
Oops, thanks.....thought I had done that....
-
On step 10.....
Question....
10. Download keymap file from github , borzoi.map.gz
as root :
cd /mnt/sdarch/usr/share/kbd/keymaps
mkdir zaurus
cp /home/yourusername/borzoi.map.gz /mnt/sdarch/usr/share/kbd/keymaps/zaurus
Don't you need to uncompress the map?
-
nope
-
I've just spent all afternoon experimenting with wifi. I haven't made any real progress but I still wanted to share my findings for anyone else interested in zALARM wifi.
Up until now I've been using Arch's netctl tool to connect to wifi but netctl doesn't let you adjust the rate of the connection and you can't set it within its wifi profile files. I was unable to test networkmanager until I got my USB ethernet as it has about 25 deps and I wasn't willing to install all that manually. I gave nmtui a quick go but no sooner had I started it up to try to configure my connection the wifi driver / kernel started repeatedly printing an error that I didn't make a note of.
I have been able to manually establish a wifi connection without using netctl by following this guide:
http://linuxcommando.blogspot.co.uk/2013/1...fi-network.html (http://linuxcommando.blogspot.co.uk/2013/10/how-to-connect-to-wpawpa2-wifi-network.html)
but the resultant connection gives me the same errors as netctl does.
I have tried using both iw and iwconfig to configure the rate but neither seem to work for libertas_cs. The iw command to set the rate is something like:
iw wlan0 set bitrates legacy-2.4 12 18 24
but for that I get an error like `operation not supported (-95)` whereas the iwconfig equivent would be something like
iwconfig wlan0 rate 5.5M fixed
but that tells me
SET failed on devic wlan0; Operation not supported
So far I've had no luck changing the rate but I'm sure there are other connection or driver settings I can try adjusting that could help. Turning off WPA isn't really an option - I will be using WPA(2) with all wifi connections I use and I know there's nothing wrong with the router or the connection itself as my laptop and phone connect to it fine.
-
I've just spent all afternoon experimenting with wifi. I haven't made any real progress but I still wanted to share my findings for anyone else interested in zALARM wifi.
Up until now I've been using Arch's netctl tool to connect to wifi but netctl doesn't let you adjust the rate of the connection and you can't set it within its wifi profile files. I was unable to test networkmanager until I got my USB ethernet as it has about 25 deps and I wasn't willing to install all that manually. I gave nmtui a quick go but no sooner had I started it up to try to configure my connection the wifi driver / kernel started repeatedly printing an error that I didn't make a note of.
I have been able to manually establish a wifi connection without using netctl by following this guide:
http://linuxcommando.blogspot.co.uk/2013/1...fi-network.html (http://linuxcommando.blogspot.co.uk/2013/10/how-to-connect-to-wpawpa2-wifi-network.html)
but the resultant connection gives me the same errors as netctl does.
I have tried using both iw and iwconfig to configure the rate but neither seem to work for libertas_cs. The iw command to set the rate is something like:
iw wlan0 set bitrates legacy-2.4 12 18 24
but for that I get an error like `operation not supported (-95)` whereas the iwconfig equivent would be something like
iwconfig wlan0 rate 5.5M fixed
but that tells me
SET failed on devic wlan0; Operation not supported
So far I've had no luck changing the rate but I'm sure there are other connection or driver settings I can try adjusting that could help. Turning off WPA isn't really an option - I will be using WPA(2) with all wifi connections I use and I know there's nothing wrong with the router or the connection itself as my laptop and phone connect to it fine.
After connecting, can you ping your router or does the connection not work at all ?
WPA2 : disabling WPA/2 temporarily would help to find out if your issue is related to WPA/2 and wpa_supplicant with that card.
KERNEL : I have uploaded a pre release of a vanilla kernel 4.2.3. It seems to boot, but I had not time to test or add any patches. Possibly LEDs do not work, USB is 150mA only and no ALARM logo. However test your WiFi with it.
NOTE : libertas firmware not included.
https://github.com/greguu/linux-4.2.3-c3x00...leases/tag/v0.1 (https://github.com/greguu/linux-4.2.3-c3x00/releases/tag/v0.1)
-
Wow! A bang up-to-date kernel for the Z!
I might install that tonight but I'm not doing any more wifi tests today - there's only so much I can handle in a day!
Fingers crossed - thanks d!
-
Why is so little firmware included with your kernels but not none?
-
Why is so little firmware included with your kernels but not none?
I guess by default the kernel scripts install only the modules supported by drivers enabled in the kernel .config file
The source has plenty more firmwares but these do not get installed because the drivers are not included in this kernel.
However I can force this with "make firmware" and "make "firmware_install"
Libertas firmware is not included in the source tar ball and does not get installed automatically. No sure why, maybe a licensing issue.
I have updated the 4.2.3 v0.1 tar ball to include all firmwares, just in case.
-
I've not installed the new kernel yet but I hope to do that shortly.
Instead, I've spent all day trying to get distcc to work - mainly to try building advancemame. AM configures fine but doesn't get very far into building on my unassisted C3K so it pushed me into giving distcc a go.
I followed the guides on the ALARM site for setting up the building of Arch PKGBUILDs using distcc:
http://archlinuxarm.org/developers/distributed-compiling (http://archlinuxarm.org/developers/distributed-compiling)
http://archlinuxarm.org/developers/distcc-cross-compiling (http://archlinuxarm.org/developers/distcc-cross-compiling)
I've got it configured as that guide describes using the ARM5 x-tools tarball (instead of building the x-tools myself) but I when I try building AM with makepkg/distcc I end up with errors like:
distcc ERROR: compile foo.c on xxx.xxx.xxx.xxx failed with exit code 110
Exit code 110 apparently means distcc isn't finding the x compiler but I've triple checked the PATH in /etc/conf.d/distccd and I've tried exporting it with both PATH= and DISTCCD_PATH= but I still get exit code 110.
I think you said you've got distcc working didn't you daalnroti? Have you got any tips for getting it to work? Have you tried building advancemame using distcc already?
-
I've installed 4.2.3 now. I've connected to wifi with both netctl and NetworkManager but both give me the same TX errors as before when I try using pacman. I can ping the Google DNS servers fine, for all thats worth.
Also like 3.11.3 I am unable to use iw or iwconfig to adjust the rate, I'm just told doing so is unsupported.
-
I have tried connecting to an unprotected/uncrypted wifi connection now. The TX lockups don't happen as quickly without it but they still show up before I get to finish doing a pacman -Syu so its not wpa_supplicant that's at fault.
-
Although the new kernel doesn't seem to have helped my wifi prob much, I was pleasantly surprised by how much faster Arch boots now. 3.11.3 takes about 39s to boot compared to 27s for 4.2!!
Such a great speedup was a totally unexpected surprise.
-
Although the new kernel doesn't seem to have helped my wifi prob much, I was pleasantly surprised by how much faster Arch boots now. 3.11.3 takes about 39s to boot compared to 27s for 4.2!!
Such a great speedup was a totally unexpected surprise.
Sounds good.....
As I wasn't able to do the install yet, but hope to do so this evening, I will try the new kernel too....
-
For reference, here are my previous benchmarks:
Kingston 32GB Ultimate 266X ext4 on 3.11.3:
kexec menu to login prompt boot time: 39s
hdparm -Tt /dev/sda
cached reads: 51.78 MB/s
buffered disk reads: 2.56 MB/s
hdparm -Tt --direct /dev/sda
cached reads: 2.06 MB/s
disk reads: 2.07 MB/s
sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"
2.4MB/s (write speed)
1m 29s real
...and the new
Kingston 32GB Ultimate 266X ext4 on 4.2.3:
kexec menu to login prompt boot time: 27s
hdparm -Tt /dev/sda
cached reads: 65.57 MB/s
buffered disk reads: 3.63 MB/s
hdparm -Tt --direct /dev/sda
cached reads: 2.62 MB/s
disk reads: 2.62 MB/s
sync;time bash -c "(dd if=/dev/zero of=bf bs=8k count=25000; sync)"
3.0MB/s (write speed)
1m 11s real
Significant gains I'd say! The HDD LED doesn't work for me though, as daal said it might not.
-
Hi danboid,
DISTCC:
example /etc/conf.d/distccd
PATH=/usr/local/x-tools/arm-unknown-linux-gnueabi/bin:$PATH
DISTCC_ARGS="--user nobody --allow 10.10.10.0/24 --port 3632"
DISTCCD_OPTS=" -j4"
also make sure you got the correct symlinks in arm-unknown-linux-gnueabi/bin and right permissions for the user running distccd.
WIFI:
this is odd and could be related to the firmware. I read somewhere there are tools for libertas to extract the firmware somehow.
I think I had debug enabled for the libertas driver in 4.2.3. Did you get more specific output / error messages ?
KERNEL :
good to hear it is working I had no time testing it yet. I will add the hdd led and some other patches and make a new release.
Cheers
-
I'll give distcc another go tomorrow probably. As for its -j switch, how does that work with cores/threads? For example, if I'm just using disctcc with just the master (the Z) and 1 client that is a quad core (or octacore w/ HT) CPU then what do I set -j to? 3, 6 or 10?
The Linux wireless docs mention extracting the libertas firmware but I've not been able to find a working link to the source required to do this.
How do I enable VT switching? I could do with setting up a keybinding to page up/down through the console output too. I prefer that to using less or more.
I've tried a few (SDL) emus but none have worked outside of X yet and seeing as I've not put any effort into configuring X yet I can't use them anyway. I don't think we're going to get passable framerates at VGA res or under X anyway so I'm hoping to get advancemame, VBA etc running under QVGA (320x240) SDL using the framebuffer. Would you know if this is possible with the SDL from the Arch repos of if'll we'll need to build a custom SDL to get QVGA working? What would you use to test SDL QVGA FB output?
I know pdaXii13's SDL could manage QVGA under the console but I've not been able to find the source and the zgrom author hasn't responded to my enquiry about his distros SDL.
Thanks
-
I'll give distcc another go tomorrow probably. As for its -j switch, how does that work with cores/threads? For example, if I'm just using disctcc with just the master (the Z) and 1 client that is a quad core (or octacore w/ HT) CPU then what do I set -j to? 3, 6 or 10?
The Linux wireless docs mention extracting the libertas firmware but I've not been able to find a working link to the source required to do this.
How do I enable VT switching? I could do with setting up a keybinding to page up/down through the console output too. I prefer that to using less or more.
I've tried a few (SDL) emus but none have worked outside of X yet and seeing as I've not put any effort into configuring X yet I can't use them anyway. I don't think we're going to get passable framerates at VGA res or under X anyway so I'm hoping to get advancemame, VBA etc running under QVGA (320x240) SDL using the framebuffer. Would you know if this is possible with the SDL from the Arch repos of if'll we'll need to build a custom SDL to get QVGA working? What would you use to test SDL QVGA FB output?
I know pdaXii13's SDL could manage QVGA under the console but I've not been able to find the source and the zgrom author hasn't responded to my enquiry about his distros SDL.
Thanks
Hi danboid.
QVGA in console : first install fbset : "pacman -S fbset" and create a new file fb.modes with contents shown below :
/etc/fb.modes
mode "qvga"
# D: 7.428 MHz, H: 22.787 kHz, V: 70,547 Hz
geometry 240 320 240 320 16
timings 134617 20 46 1 0 20 2
accel true
endmode
mode "vga"
# D: 51.991 MHz, H: 75,252 kHz, V: 116,851 Hz
geometry 480 640 480 640 16
timings 19231 46 125 1 0 40 3
accel true
endmode
after this you should be able to switch to QVGA in the console by using "fbset qvga" and back with "fbset vga"
SDL : to get QVGA in SDL you need SDL with a fbcon or/and directfb backend compiled in. I used to compile my SDL from source under debian to get that functionality. Arch may have directfb and fbcon support already enabled. You will need to set SDL_VIDEODRIVER=fbcon and SDL_VIDEO_FBCON_ROTATION=CW before starting the SDL application in the console. Advancedmame may have inbuilt rotation that is faster than the software SDL/FBCON rotation. Some emulators use rotated "blitting" that is much faster. I have no experience with AdvancedMame but I compiled the game "Flashback" for the Z to run in pure console with SDL fine. I also got "Decent" working but had issues with mouse support under console.
DISTCC : You need to set DISTCC_HOSTS="yourfastcomputer/4" then it will accept 4 threads at the same time. Keep in mind the Z will do all the preprocessing and I had issues with more than 2 preprocessors running on the Z and big compiles. The Z would run out of memory. I suggest to do -j2 to be safe, but you can try higher. You will notice the fast computer will wait a lot for the Z to preprocess and then compile the file. That waiting makes it slow, but still faster than on the Z alone. There exists now a "pump mode" for distcc, so all compilation is done on the hosts. However I have not used this as this mode can cause issues.
VT Switching : under my console keymap it is "Fn" + Left / Right to change a VT. I use "screen" alot when working in the console and all F keys work by using Fn+Number. Also scrolling in console content within "screen" works. To enter screen copy mode press CTRL-a and then ESC (Cancel).
Firmware : You may have luck posting on the libertas mailing list or find a freenode channel and ask the developers about your issue. Extracting the firmware might be something worth trying.
Xorg Keymap : I have not found my keymaps for Xorg, but must have some from Debian somewhere. pdaxrom and debian used Xfbdev a simple minimal X server and not full Xorg. I am sure you find some keymap files in a pdaxrom image ?
-
Linux 4.2.3 Kernel update : Linux 4.2.3-c3x00 v0.2 (https://github.com/greguu/linux-4.2.3-c3x00/releases)
ArchLinuxARM minimal rootfs tar ball for SD/CF cards. : Minimal rootfs October 2015 (https://github.com/greguu/alarm-zaurus-c3x00/releases/tag/October2015)
-
Excellent!
Thanks for your many tips! I'll get the updated kernel and kexec installed today and try to make some progress with my other issues and let you know how far I get.
I used to have Flashback on the Amiga and it'd be great to have Descent running on the Z so I may give that a shot too.
I bet you're thinking yourself lucky you only have one user to support so far!
Mark:
Have you still not got it to boot?
-
Linux 4.2.3 Kernel update : Linux 4.2.3-c3x00 v0.2 (https://github.com/greguu/linux-4.2.3-c3x00/releases)
ArchLinuxARM minimal rootfs tar ball for SD/CF cards. : Minimal rootfs October 2015 (https://github.com/greguu/alarm-zaurus-c3x00/releases/tag/October2015)
Sounds great.....
Is the tarball in a format that can be uncompressed on the Z or still need another computer?
Excellent!
Thanks for your many tips! I'll get the updated kernel and kexec installed today and try to make some progress with my other issues and let you know how far I get.
I used to have Flashback on the Amiga and it'd be great to have Descent running on the Z so I may give that a shot too.
I bet you're thinking yourself lucky you only have one user to support so far!
Mark:
Have you still not got it to boot?
Unfortunately, I was super busy with work the past week.....got as far as reflashing Z with the Arch-kexecboot.....
And it might be a few more days before I get time for this as I'm going away for a few days probably starting later today......
But will give it a try when I have the time to focus on it for a few hours....
-
Is the tarball in a format that can be uncompressed on the Z or still need another computer?
The tar ball is mainly for getting uncompressed on a x86 Linux machine to a ext 4 SD card to get you started and not for uncompressing from emergency console on the Z itself.
You can uncompress the tar ball again from a running alarm session of the SD card but the xz compression will take a long time to decompress on the Z.
For this I recommend to unxz the tar ball first on a x86 machine.
-
Excellent!
Thanks for your many tips! I'll get the updated kernel and kexec installed today and try to make some progress with my other issues and let you know how far I get.
I used to have Flashback on the Amiga and it'd be great to have Descent running on the Z so I may give that a shot too.
I bet you're thinking yourself lucky you only have one user to support so far!
Well, I don't think there will be much more than 3 users in total, once Mark gets his alarm installed. No sign of any more users so far....
-
Is the tarball in a format that can be uncompressed on the Z or still need another computer?
The tar ball is mainly for getting uncompressed on a x86 Linux machine to a ext 4 SD card to get you started and not for uncompressing from emergency console on the Z itself.
You can uncompress the tar ball again from a running alarm session of the SD card but the xz compression will take a long time to decompress on the Z.
For this I recommend to unxz the tar ball first on a x86 machine.
Thanks...
Excellent!
Thanks for your many tips! I'll get the updated kernel and kexec installed today and try to make some progress with my other issues and let you know how far I get.
I used to have Flashback on the Amiga and it'd be great to have Descent running on the Z so I may give that a shot too.
I bet you're thinking yourself lucky you only have one user to support so far!
Well, I don't think there will be much more than 3 users in total, once Mark gets his alarm installed. No sign of any more users so far....
I know of one more possible user.....
-
Looks like you might've made a mistake packaging the new kernel daal - it seems to actually contain 3.11.3.
-
I have installed the latest kexec and that works fine for me. Nice to have the 5s timeout! VT switching works great too now you've pointed out how its mapped.
I've installed fbset and your config file for it and switching between VGA and QVGA works fine but I'm yet to get an SDL console app/emu to work, thats with or without exporting those two SDL envvars. I expect the reason for that is that everything I've tried so far likely isn't trying to output at 320x240 (or 240x320).
The emu that looks the most promising out of everything I've tried so far is mednafen. It supports a number of systems (inc GBA, SNES, NES, MD and PSX amongst others), it is in the repos, it doesn't require X and it uses console SDL by default. Disabling scaling in its config file and the SDL rotation EV have both helped me get closer.
Any tips for scrolling the console buffer outside of screen, less/more and X? On a regular Linux PC I do this with SHIFT + PGUP/PGDOWN and under BSD its SCROLL LOCK + arrow keys.
Thanks!
-
Looks like you might've made a mistake packaging the new kernel daal - it seems to actually contain 3.11.3.
Ups, thanks. Fixed.
-
Any tips for scrolling the console buffer outside of screen, less/more and X? On a regular Linux PC I do this with SHIFT + PGUP/PGDOWN and under BSD its SCROLL LOCK + arrow keys.
According to the borzoi.map.gz : PageUp / Down is ALTGR + UP/DOWN, so try SHIFT + ALTGR + UP/DOWN, it may work!
-
SDL and ROTATION :
If I remember correctly, SDL apps / games scan the fb.modes file when using FBCON as back-end. Since the fb.modes are 240x320 or 480x640, the game / app bails out without finding a proper mode. The libSDL is looking for a 320x240 mode in fb.modes, but will not find it. I had to modify game / app / sdl source to tweak the detection of the modes I think. It was not too hard and also I added an additional EV to SDL that handled the qvga/vga and orientation for the Z in console modes. Long story short, the prebuild SDL lib from Arch might not do the trick for rotated frame buffers in console mode. The DirectFB backend of SDL2.0 might be worth looking into, too. DirectFB support in SDL1.2/3 was ok but not great and had heaps of bugs. Saying that, most older games will possibly only compile fine with SDL1.2. - Well all this has been quite some time ago since I played with it.. Let me know how you get a long with running a simple SDL app rotated in console for a start.
-
Any tips for scrolling the console buffer outside of screen, less/more and X? On a regular Linux PC I do this with SHIFT + PGUP/PGDOWN and under BSD its SCROLL LOCK + arrow keys.
According to the borzoi.map.gz : PageUp / Down is ALTGR + UP/DOWN, so try SHIFT + ALTGR + UP/DOWN, it may work!
I can confirm this is not working This might need some tweaking in the keymap or somewhere else. I would suggest to use screen because the F keys seem to work properly only when I use screen . Fn+1 = F1 etc.
-
I'm not having much luck with the new kernel daal - have you tried it yet?
The HDD LED is working now but when I boot I get a few errors that I didn't get with the previous kernels:
ipv6: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
pxaficp_ir: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
ads7846: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
I deleted the old 4.2.3 kernel modules and put the new ones under /usr/lib/modules but its not finding them as I can't mount cards, for example.
-
I'm not having much luck with the new kernel daal - have you tried it yet?
The HDD LED is working now but when I boot I get a few errors that I didn't get with the previous kernels:
ipv6: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
pxaficp_ir: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
ads7846: version magic '4.2.3-c3x00+ preempt mod_unload ARMv5 p2v8 ' should be '4.2.3-c3x00 preempt mod_unload ARMv5 p2v8 '
I deleted the old 4.2.3 kernel modules and put the new ones under /usr/lib/modules but its not finding them as I can't mount cards, for example.
looks like the kernel modules are from an older build. I will fix and upload later today. Thanks for testing.
EDIT : updated kernel tar ball 4.2.3 v0.2 - git adds annoying "+" to local version name when adding code to vanilla kernel, I had to disable that and recompile.
-
That sounds irritating re the git prob. Thankfully it seems its third time lucky for 4.2.3 0.2! I've installed the latest tarball and it seems fine so far - thanks daal!
I've not made any progress on my wifi or anything else. It looks like I'll have to write to the linux-wireless ML to see what they say for my CF card driver and its firmware.
I'd prefer to get a b/g CF wfi card working - hopefully the one I've already got - but I wonder if there is USB wifi adapter that will run OK off the Z's bus power alone? CF cards are a bit of a rarity now.
-
There is one issue with 4.2.3 that I've encountered but forgot to mention up until now. If you don't touch the Z for 10/15 minutes or so, 3.11.3 blanks the screen but under 4.2.3 the screen goes white. As soon as you push a key you are returned to the console OK though.
-
That sounds irritating re the git prob. Thankfully it seems its third time lucky for 4.2.3 0.2! I've installed the latest tarball and it seems fine so far - thanks daal!
I've not made any progress on my wifi or anything else. It looks like I'll have to write to the linux-wireless ML to see what they say for my CF card driver and its firmware.
I'd prefer to get a b/g CF wfi card working - hopefully the one I've already got - but I wonder if there is USB wifi adapter that will run OK off the Z's bus power alone? CF cards are a bit of a rarity now.
hm, I do not think you can get WiFi USB stick running with 150 to 180 mA. You will need a powered USB hub.
-
There is one issue with 4.2.3 that I've encountered but forgot to mention up until now. If you don't touch the Z for 10/15 minutes or so, 3.11.3 blanks the screen but under 4.2.3 the screen goes white. As soon as you push a key you are returned to the console OK though.
Hm, sounds strange. There are always things with new kernels that do not work out of the box. This needs investigating. I have not had time to boot 4.2.3 on my Z yet and will not find much time in the coming days, but I will look into it. Probably good you let me know of any issues you experience with the new kernel. Cheers.
-
That sounds irritating re the git prob. Thankfully it seems its third time lucky for 4.2.3 0.2! I've installed the latest tarball and it seems fine so far - thanks daal!
Git issue with kernel local version : http://stackoverflow.com/questions/1933391...-kernel-version (http://stackoverflow.com/questions/19333918/dont-add-to-linux-kernel-version)
I am relatively new to git , but hey, you never stop learning.
The correct answer for me was :
To prevent the script scripts/setlocalversion to append the + to the end of the kernel local version, create an empty .scmversion file in the root of the kernel sources.
touch .scmversionthis way, you'll be able to leave LOCALVERSION as is in the kernel configuration file, in case you want to append a local signature to the kernel name.
-
I'd prefer to get a b/g CF wfi card working - hopefully the one I've already got - but I wonder if there is USB wifi adapter that will run OK off the Z's bus power alone? CF cards are a bit of a rarity now.
The DLINK DCF-660W Wireless 2.4GHz (802.11b) works well, but is slow. Also it is a bit clunky compared to the Ambicom or others.
In Japan they sold CF 3G/HDSPA cards. These would give you 3.6Mbit only, but basically everywhere in Japan !
http://www.ymobile.jp/lineup/old/d01nx2/ (http://www.ymobile.jp/lineup/old/d01nx2/)
The japanese recommend these to work with a Z and 802.11g.
http://petit-noise.net/download/gw-cf54g/ (http://petit-noise.net/download/gw-cf54g/)
This one looks good.
http://www.amazon.co.jp/gp/product/B000N4A...ASIN=B000N4AVRA (http://www.amazon.co.jp/gp/product/B000N4AVRA?ie=UTF8&tag=mden3sq-22&linkCode=as2&camp=247&creative=7399&creativeASIN=B000N4AVRA)
Back in the days when I was mobile with my Z I used my Nokia 6020 and IrDA to connect to the Internet with my Z. That was flash, no cable or extra card needed.
Just GPRS dialup speed, but hey it worked, and in the console with lynx/links and mutt pretty well. IrDA is still enabled in the current kernel
I probably should stock up on a 32GB CF card and a 54g CF too. Did anyone try 32GB+ in a Z ?
-
There is one issue with 4.2.3 that I've encountered but forgot to mention up until now. If you don't touch the Z for 10/15 minutes or so, 3.11.3 blanks the screen but under 4.2.3 the screen goes white. As soon as you push a key you are returned to the console OK though.
Hm, sounds strange. There are always things with new kernels that do not work out of the box. This needs investigating. I have not had time to boot 4.2.3 on my Z yet and will not find much time in the coming days, but I will look into it. Probably good you let me know of any issues you experience with the new kernel. Cheers.
I can confirm. After booting 4.2.3 and idle for about 10min , the screen blanks white instead of black.
Could not find an explanation for this, but a workaround at the moment would be to add "setterm -blank x" (where "x" is number of minutes after when to blank ) to your .bashrc.
Then it will blank correctly. However this workaround only works for the VT when you have logged in.
I will investigate if this can be fixed properly, it seems to be kernel related indeed.
Cheers!
-
Thanks for your recommendations on wifi / irda connectivity. Unfortunately my phone (SGS3) dosn't have IRDA so thats not an option and I'd imagine irda is slow right? I didn't think there would be any USB wifi adapters that would run off the Z's rather low bus power but I thought I'd ask here anyway.
I sent an email to the linux-wireless ML last night but no-one has replied yet. If no-one has replied by tomorrow I'll look in the driver source to see if I can see who wrote libertas_cs and try emailing them directly.
Hopefully you can find a proper fix to the screen blanking issue but your workaround sounds like it'll be good enough to work in most cases.
I'm using a 32GB CF as the internal drive on my Z but maybe you're asking about CF drives larger than 32GB? 32GB seems to be the sweetspot right now - it's ~£10 for 32GB but ~£50 or more for 64GB.
EDIT
There used to be a dedicated libertas ML but that is no more.
-
Danboid,
in regards to your WiFi issue, thanks to user "ant" from OE who just compiled a set of rootfs and kernel from the OE stack after I posted on their irc channel.
It has a 4.0 kernel. It _should_ work with Arch , too.
This would be a good time to test if the issue with libertas is related to my kernel etc. See here : https://github.com/LinuxPDA/builds_2015_10_...ee/master/spitz (https://github.com/LinuxPDA/builds_2015_10_18/tree/master/spitz)
You would need :
modules-spitz.tgz
zImage-spitz.bin
and add to your boot.cfg as a second / third boot option.
Just be aware I can not give any support to this kernel but it would be good to test. This way we can improve the arch kernel if needed. Possibly the same issue persists, but who knows.
Cheers,
-
Thanks for your recommendations on wifi / irda connectivity. Unfortunately my phone (SGS3) dosn't have IRDA so thats not an option and I'd imagine irda is slow right?
IrDA is dial up speed, horrible slow, yes.
-
Oh dear!
I thought I'd try that 4.0 OE kernel but in doing so I've trashed my install and now neither of my Arch kernels boot now due to a kernel panic - no init found.
The last thing I did before it went titsup was to extract the OE kernel modules from its tarball on my SD card like so:
tar xvf modules--blahblah.tgz -C /
I had inspected the tarballs internal folder structure on my PC before I extracted it so I thought this would be safe to do. The tarball seemed to extract fine but it must've overwritten something it shouldn't have because after it had finished extracting every command I typed failed with a 'file not found' type error like I'd just formatted the root partition.
I have tried mounting my root partition under D+B to inspect the damage but it will not mount. fdisk shows it but mount just says 'invalid argument' when I try to mount it. This could be because I partitioned and formatted the CF on my PC before I inserted it into my Z. This is my first attempt at mounting my 32GB internal CF from the D+B busybox and it seems I'm SOL. Looks like D+B busybox cannot mount ext4.
There's no way I'm pulling the CF drive out of my Z to do an autopsy so I'll prob just have to do a re-install. In future I will have to rsync or rdiff-backup my rootfs to an ext formatted CF card so I can quickly recover from stuff like this!
-
Seeing as I've been forced to re-install I may as well write an install guide for ArchMark and anyone else who might be interested.
The main question is where should it live? It'd be best on a wiki that we can all edit.
EDIT
Install guide is almost half done. I'll upload it to the Arch wiki and then maybe it could be linked under https://wiki.archlinux.org/index.php/Catego...installing_Arch (https://wiki.archlinux.org/index.php/Category:Getting_and_installing_Arch) or somewhere.
ALARM doesn't seem to have a separate wiki as far as I can tell.
-
Seeing as I've been forced to re-install I may as well write an install guide for ArchMark and anyone else who might be interested.
The main question is where should it live? It'd be best on a wiki that we can all edit.
EDIT
Install guide is almost half done. I'll upload it to the Arch wiki and then maybe it could be linked under https://wiki.archlinux.org/index.php/Catego...installing_Arch (https://wiki.archlinux.org/index.php/Category:Getting_and_installing_Arch) or somewhere.
ALARM doesn't seem to have a separate wiki as far as I can tell.
Hm, that is not good news.
Did you make a second entry in your boot.cfg ? This way you can safe boot back to arch kernel. This way I test all kernels in case they do not boot correctly.
If you have an Arch SD card ready you can mount you CF and fix things and save time to re install. There is a base rootfs for arch with the 4.2.3 kernel ready to make an SD card from your main Linux ! Safe yourself the time of re installing ! https://github.com/greguu/alarm-zaurus-c3x00 (https://github.com/greguu/alarm-zaurus-c3x00) Use it as emergency boot SD, it can mount ext4 !
Looks like OE uses a initrd to boot. I was not aware of that. This initrd may be found in the root tar gz. I can play around with this later this weekend, currently too busy.
WIKI : Not sure, I will have a look what I can do on github and if there is a way to allow others to modify the wiki.
-
Yes, I had two boot.cfg entries for the 3.11.3 and 4.2.3 kernels but that didn't help me.
I am using your latest rootfs to reinstall to an external CF card now. I have documented the entire process with my world-class Linux dox skillz so I shall be posting an unformatted, unfinished version of my guide here shortly for you and Mark to have a read of. I've tried to make the process as simple and foolproof as poss.
I've already got a github account so I suppose that's another option if you'd prefer it to be hosted there instead?
I'll be trying the other kernel as soon as my Z is back on its feet albeit with a backup this time!
-
Installing Arch Linux ARM (ALARM) on the SHARP Zaurus SL-C3x00 series
INTRODUCTION
This guide covers the process of installing a base Arch Linux system on the SHARP Zaurus SL-C3x00 series of PDAs. If you're new to Arch Linux, be warned that it is not designed for Linux newbs like say Ubuntu and Mint are. Arch has quite a steep learning curve but it is a great way to learn Linux, you have easy access to many up-to-date packages and it is often more lightweight and faster than many other popular Linux distros.
The following instructions require that you have access to a working Linux computer with internet access and a SD card/Compact Flash device, a free SD or Compact Flash card of at least 1GB in size that can be used to install Arch and that you are comfortable using the Linux command line. You are also required to install the kexecboot bootloader before you can boot or install Arch. CF or USB ethernet adapters provide the easiest and most reliable way to access the internet under Arch and install additional packages.
WHY DO I NEED A LINUX COMPUTER (OR VM) TO INSTALL ARCH ON MY ZAURUS?
There are a few reasons why it is recommended you use another Linux computer to install ALARM:
* You will get faster disk read speeds if you install ALARM to a ext4 partition but the D+B busybox recovery console cannot format nor mount ext4 partitions so you need to format your internal drive and install Arch by booting Arch (or another Linux distro) from a removable SD or CF card.
* The ALARM base tarball is compressed with BSD tar so you cannot uncompress it with busybox tar.
* Having ALARM installed on an external SD or CF card acts as both a system backup and a more modern recovery OS than the D+B busybox console.
Windows and OSX lack the required tools to create the Arch installation media required to address these points.
INSTALL KEXECBOOT
kexecboot is a bootloader similar to GRUB. kexecboot is needed to boot ALARM and hence it is required you install it first. It is recommended you use the ALARM kexecboot if you want your first kernel to be autobooted after 5 seconds.
To install kexecboot, download the tarball from the same page as the Zaurus ALARM kernel downloads ( https://github.com/greguu/linux-4.2.3-c3x00/releases (https://github.com/greguu/linux-4.2.3-c3x00/releases) ) then extract its contents into the root directory of a FAT formatted SD or CF card. Completely turn off your Zaurus and insert the card with the kexec install files. Plug in the charger whilst holding the OK button then turn your Zaurus on. You should then see a grey, Japanese menu with four options. Choose option number four (update) then choose the device that contains the kexec install files. Your Z should then reboot, install kexecboot and then reboot again - this time into kexecboot.
CREATE THE ARCH INSTALL MEDIA
You can use either a Compact Flash or an SD card to install Arch to as long as its 1GB or larger. In this example I'm using a 4GB CF card that was pre-formatted as a vfat (Windows) drive so the first step is to insert the card to the card reader of a Linux PC and repartition and reformat the card as an ext4 Linux partition.
Before you repartition and format your card, you need to make sure you know the correct device name for the device you wish to format. You can use the lsblk or dmesg commands to see what device name your card has been assigned. If you get the device name wrong you risk losing data so be very careful! In my case the card device was /dev/sdb so I ran the following commands, which may require you to install parted first depending on your distro:
# umount /dev/sdb1
# parted -s -a optimal /dev/sdb mklabel msdos -- mkpart primary ext4 1 -1
# mkfs.ext4 /dev/sdb1
Your card should now be partitioned and formatted correctly for Arch so download the latest Zaurus C3x00 ALARM rootfs tarball ( https://github.com/greguu/alarm-zaurus-c3x00/releases (https://github.com/greguu/alarm-zaurus-c3x00/releases) ). Presuming that the ALARM rootfs is saved within the current directory and your target card is mounted on /dev/sdb1 you'd run something like the following to extract the rootfs:
# mount /dev/sdb1 /mnt/
# bsdtar xvf alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz -C /mnt/
# cp alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz /mnt/root/
# umount /mnt/; sync
If you have installed Arch onto a CF card instead of an SD card you also need to edit /mnt/boot/boot.cfg and change APPEND=root=/dev/mmcblk0p1 to APPEND=root=/dev/sdb1.
BOOT ARCH
Insert your Arch install media into your Zaurus - you should now be able to boot into Arch. When you are presented with the login prompt you can login with the username and password root.
PARTITION AND FORMAT THE INTERNAL DRIVE
If you have not already done so you will need to partition your internal drive using fdisk or cfdisk before formatting the root partition as ext4 and running mkswap on your swap partition, if you decide to create one. I would create a swap partition of at least 256MB if you are attempting to compile large programs on your Zaurus. Note that there is a bug in systemd that prevents swap partitions being auto-mounted on boot so you will need to enable swap manually using the swapon command until this gets fixed.
EXTRACT ROOTFS, UPDATE BOOT.CFG AND FSTAB
When your internal drive has been partitioned and formatted, you can extract the rootfs tarball from the root dir onto the internal drive using similar mount and bsdtar commands to those used before.
After extracting the rootfs onto the internal drive, all that remains is to adjust the APPEND statement in /boot/boot.cfg to APPEND=root=/dev/sda1 (or whatever device it will be booting from) as well as adjusting the device name for the rootfs partition in /etc/fstab, both on the internal drive.
-
Yes, I had two boot.cfg entries for the 3.11.3 and 4.2.3 kernels but that didn't help me.
I am using your latest rootfs to reinstall to an external CF card now. I have documented the entire process with my world-class Linux dox skillz so I shall be posting an unformatted, unfinished version of my guide here shortly for you and Mark to have a read of. I've tried to make the process as simple and foolproof as poss.
I've already got a github account so I suppose that's another option if you'd prefer it to be hosted there instead?
I'll be trying the other kernel as soon as my Z is back on its feet albeit with a backup this time!
Hi danboid.
I have tried the 4.0.0 yocto kernel but it does not boot. If testing a new kernel I first try to do this in qemu. You can get a complete alarm-zaurus setup in a qemu emulator on you main linux machine for testing.
To just test if the kernel boots :
qemu-system-arm --machine borzoi --kernel zImage-4.2.3-c3x000
For more, check the qemu man page or Wiki and set up a testing environment based on the rootfs tar ball.
It would be good to get a howto going but I suggest to move back to 3.11.3 kernel for a default installation process. I might remove the 4.2.3 from the rootfs until we got it working as much as good as 3.11.3 was ?
I noticed that cpufreq support in my 4.2.3 release is gone / broken. I need to investigate that too.
WIKI : feel free to put it on your github and I can link to it from my github in the description.
I would focus on a few things:
- Get a basic console only ALARM working proper, optimized for speed and low memory usage ( eg replace openssh with dropbear ?) and create a more optimized rootfs.
- Focus on testing on SD cards, this way you can easy fix things and test. You can keep a stable working system on the CF.
- Get a 4.x series kernel going. If we have to go back to 4.0 or 4.1 to have proper cpufreq and blank screen, it would be not a show stopper ?
- or stick with 4.2.x and get the issues fixed ?
- Troubleshoot CF WiFi issues and get 54g card going
- Update and maintain a relatively easy to read HowTo on a Wiki (GitHub ?)
- Get more users to test and play
BACKUP : I would suggest to tar your system regularly to a SD card or USB stick to have a roll back option, yes!
Cheers,
-
Update :
beware of doing a pacman -Syu at the moment. Latest systemd (juck) update causes some issues with pam_nologin and only root can login to the system.
to fix this temporarily log in as root and do a "systemctl start systemd-user-sessions.service" . Then you can login as user. This fix does not survive a reboot.
This will get fixed very likely soon, so just avoid updating systemd until then.
See alarm forums : http://archlinuxarm.org/forum/viewtopic.ph...94&start=10 (http://archlinuxarm.org/forum/viewtopic.php?f=57&t=9394&start=10)
-
Hi daal
That's a shame re the yocto kernel and more systemd bugs but thanks for the heads-up!
As far as I know the only issues we have with the 4.2 kernel are the screen blanking prob and cpufreq doesn't work, right? I won't be overclocking too often so in most cases I'd prefer the extra IO speed the 4.2 kernel offers.
Its at this point I should mention that I get frequent ATA errors under 3.11.3 that I don't see under 4.2.3. I've ignored them so far and I dont believe its led to any corruption but generally the ATA driver seems in much better shape in 4.2. I'll get the full error for you if you don't see this too.
I've converted my install guide to markdown and uploaded it to github:
https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
Let me know if you have any problems following that ArchiMark. I know you said you wanted to install Arch without resorting to using another Linux computer but I explain in my guide why thats the best way to install.
I've only vaguely outlined the steps required after booting Arch from an external card because I wanted to keep the guide brief, the partitioning process and extraction process will be familiar to anyone who has installed Linux before and if you can't do that without verbose instructions then Arch probably isn't for you. Like the Arch wiki, my guide presumes you already know the Linux basics.
-
Hi daal
That's a shame re the yocto kernel and more systemd bugs but thanks for the heads-up!
As far as I know the only issues we have with the 4.2 kernel are the screen blanking prob and cpufreq doesn't work, right? I won't be overclocking too often so in most cases I'd prefer the extra IO speed the 4.2 kernel offers.
Its at this point I should mention that I get frequent ATA errors under 3.11.3 that I don't see under 4.2.3. I've ignored them so far and I dont believe its led to any corruption but generally the ATA driver seems in much better shape in 4.2. I'll get the full error for you if you don't see this too.
I've converted my install guide to markdown and uploaded it to github:
https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
Let me know if you have any problems following that ArchiMark. I know you said you wanted to install Arch without resorting to using another Linux computer but I explain in my guide why thats the best way to install.
I've only vaguely outlined the steps required after booting Arch from an external card because I wanted to keep the guide brief, the partitioning process and extraction process will be familiar to anyone who has installed Linux before and if you can't do that without verbose instructions then Arch probably isn't for you. Like the Arch wiki, my guide presumes you already know the Linux basics.
SYSTEMD : I know you are a Arch user, so I guess you are aware of the issues of running a rolling release distribution. These issues are not zaurus specific and can hit users anytime because of the nature of a rolling release. In the past years, since running ALARM on my Z, I did not encounter to many upgrade issues, but the more frequent you do a full upgrade (pacman -Syu) the more you will be exposed to potential bugs.
ATA ERRORS : This might be tricky to debug for you, but did you have these issues with the original CF micro-drive ? This could be related to your 32GB CF card ? I do not have these with my 4GB micro-drive.
ArchiMark : I hope you make it to join us. Dont be put off by the issues we face right now. We will get there! \
Wiki : Thanks for that danboid, but please understand I hope you will update the Wiki and add any futher changes. I will focus on getting ALARM supported kernels going and hope to provide an up to date basic rootfs. This will be team work, so thanks for your support !!!
KERNEL: I will do my best to improve / fix the 4.2.x kernel but as mentioned, for the time being we should leave the 3.11.3 kernel as default in the rootfs and Wiki HowTo for new users until the 4.2.x series does the job.
YOCTO / OE : I will mention to ant that the kernel will not boot. I hope on getting some feedback and support, but not sure I we can count on it, as we are ALARM users not OE. In the end I guess, it should not be down to what distribution we use, it is essentially about to keep the Z alive. My preference is to go with ALARM.
in general I guess we are the last "active" users of this platform. Eventually it will be up to us what me make of it. Hopefully some join and use and test, or contribute with their skills !
Thanks for all your testing and interest. We will get there..
-
In respect to systemd and Arch, I'm well aware of the pros and cons of both so I'm not surprised by the hiccups we've had with them. I realise they're not your fault.
Thinking about it, I think I did only start to get the ATA errors under 3.11.3 after upgrading my drive. Thankfully I've not seen it happen under 4.2. I hope its only a warning - I think so as nothing bad seemed to occur after the complaints, which it does pretty often under 3.x. Note that when I trashed my drive with an errant tar command I was running 4.2.3.
I'll update the install guide for as long as my Zaurus survives or as long as I'm using ZALARM, as I like to call it. I'll consider my guide complete after Mark or somebody else follows it successfully. I know it works for C3000 users (read: me) as I tested and documented each step as I installed it. The post first boot part could be made more verbose but I think its detailed enough already for any competant Linux user to follow. Even if my Z does die soon, feel free to copy, update and modify my guide - it's your project!
I'm surprised how little activity there is on here. Linux has literally took over the world since the heyday of the Z! Linux is more popular than ever and there's plenty of people using RPi's BBB's, BananaPi's etc and there's even still a fair bit of activity in the world of Commodore and other (more) retro platforms so WTF?
EDIT
Could you update the OP to link to my install guide please? You know, just in case?
-
Hi daal
That's a shame re the yocto kernel and more systemd bugs but thanks for the heads-up!
As far as I know the only issues we have with the 4.2 kernel are the screen blanking prob and cpufreq doesn't work, right? I won't be overclocking too often so in most cases I'd prefer the extra IO speed the 4.2 kernel offers.
Its at this point I should mention that I get frequent ATA errors under 3.11.3 that I don't see under 4.2.3. I've ignored them so far and I dont believe its led to any corruption but generally the ATA driver seems in much better shape in 4.2. I'll get the full error for you if you don't see this too.
I've converted my install guide to markdown and uploaded it to github:
https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
Let me know if you have any problems following that ArchiMark. I know you said you wanted to install Arch without resorting to using another Linux computer but I explain in my guide why thats the best way to install.
I've only vaguely outlined the steps required after booting Arch from an external card because I wanted to keep the guide brief, the partitioning process and extraction process will be familiar to anyone who has installed Linux before and if you can't do that without verbose instructions then Arch probably isn't for you. Like the Arch wiki, my guide presumes you already know the Linux basics.
THANK YOU for your guide, danboid.....
I followed your instructions and got to point where I need to boot up Z with the SD card. Unfortunately, I can't boot up Z as my battery must not be charged and I left my charger at the office....so, will try booting in about 4 - 5 hours......
Now, I am concerned as to whether I will be able to charge my battery when running Arch?....
Also, to clarify, I was saying that it would be nice if you could uncompress tarball from SD card to the Z, but is not a big deal to do with laptop....
Thanks again for the guide. Do think it would be good to have it more in numbered step format within sections, like daalnroti's guide in post # 116 on page 8.....makes it easier to reference a particular step if someone has questions about it.
-
Hi daal
[snip ..... ]
I've converted my install guide to markdown and uploaded it to github:
https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
Let me know if you have any problems following that ArchiMark. I know you said you wanted to install Arch without resorting to using another Linux computer but I explain in my guide why thats the best way to install.
I've only vaguely outlined the steps required after booting Arch from an external card because I wanted to keep the guide brief, the partitioning process and extraction process will be familiar to anyone who has installed Linux before and if you can't do that without verbose instructions then Arch probably isn't for you. Like the Arch wiki, my guide presumes you already know the Linux basics.
[ snip.....]
ArchiMark : I hope you make it to join us. Dont be put off by the issues we face right now. We will get there! \
in general I guess we are the last "active" users of this platform. Eventually it will be up to us what me make of it. Hopefully some join and use and test, or contribute with their skills !
Thanks for all your testing and interest. We will get there..
Not to worry. Just didn't have time until late last evening and then per my post above this one, my battery is not charged and don't have AC charger with me.....
Instructions are good....
Will I be able to charge battery with this setup?
danboid, as soon as I get my Z working, I'll test my AmbiCom CF WiFi card. It always worked before with other ROMs...and efficient power-wise I think....
As for other users, as mentioned recently, I know of at least one other that may try this soon....think he's just watching to see this progress to a certain point first....
Thanks.
-
Hi Mark
Yes, it charges OK just you need to poweroff if you want to charge at full speed according to daal. Online charging is slow.
Of course I'm very interested to see if you can use your wifi card. Is it the Ambicom WL54-CF?
I think the quickest and easiest way to get a wifi connection configured under the Arch console is to install dialog and wpa_supplicant. You can then run wifi-menu which gives you a nice ncurses interface to configuring your connection.
EDIT
If you have DNS issues with wifi you may need to run
systemctl start systemd-resolved
& 'enable' it if you find you always need it, of course.
-
Hi Mark
Yes, it charges OK just you need to poweroff if you want to charge at full speed according to daal. Online charging is slow.
Thanks for clarifying.....
Of course I'm very interested to see if you can use your wifi card. Is it the Ambicom WL54-CF?
Will let you know....probably later today....
Don't have the card with me now, I posted the model number a few pages back when the question came up before....but I can post the info here again later today...it's also a very slim card which is nice...
I think the quickest and easiest way to get a wifi connection configured under the Arch console is to install dialog and wpa_supplicant. You can then run wifi-menu which gives you a nice ncurses interface to configuring your connection.
EDIT
If you have DNS issues with wifi you may need to run
systemctl start systemd-resolved
& 'enable' it if you find you always need it, of course.
Thanks for this info....
Meanwhile, I thought of at least one more possible Arch on Z candidate....will let him know about this....
I know another guy, but don't think his Z is working properly now.....but will let him know too....
-
Hi again,
Made it back to my office and plugged in charger.....after a few minutes, the Z was able to start up....
Booted up OK and was able to login at the prompt.....YEAH!!!
My trusty ol' Socket CF Ethernet card was recognized and is working without any configuration on my part......YEAH!!!
Will tryout my WiFi card and report back....and will post some pics of it and my Socket card for reference...
AmbiCom model number WL1100-CF........
Display just turned white....but was able to wake it up.....
Later today will copy over install to my microdrive....
Thanks again for your install guide, danboid....
Now onto trying to install dialog and wpa_supplicant.....
-
Left Z for a few more minutes.....display went black this time....but it wakes up OK....
Used pacman and installed dialog and wpa_supplicant.....will try out AmbiCom card later....
Here's a few pics in meantime....
-
Forgot to ask.....
What's best way in console to 'eject' my ethernet CF card in order to insert my WiFi card?
Thanks!
-
Forgot to ask.....
What's best way in console to 'eject' my ethernet CF card in order to insert my WiFi card?
Thanks!
depending what you use to initiate the connection. I use netctrl and would do :
Example :
netctl stop ethernet
# remove CF ethernet and plug in CF WiFi
netctl start wifi
-
Forgot to ask.....
What's best way in console to 'eject' my ethernet CF card in order to insert my WiFi card?
Thanks!
depending what you use to initiate the connection. I use netctrl and would do :
Example :
netctrl stop ethernet
# remove CF ethernet and plug in CF WiFi
netctrl start wifi
Thanks for the input!
However, when I tried this, I get:
# netctrl stop ethernet
-bash: netctrl not found
So, I tried installing it, but I got this:
# pacman -S netctrl
error: target not found: netctrl
Assume that either netctrl is part of some other package or I need to do something else to get it?
Thanks.
-
Forgot to ask.....
What's best way in console to 'eject' my ethernet CF card in order to insert my WiFi card?
Thanks!
depending what you use to initiate the connection. I use netctrl and would do :
Example :
netctrl stop ethernet
# remove CF ethernet and plug in CF WiFi
netctrl start wifi
Thanks for the input!
However, when I tried this, I get:
# netctrl stop ethernet
-bash: netctrl not found
So, I tried installing it, but I got this:
# pacman -S netctrl
error: target not found: netctrl
Assume that either netctrl is part of some other package or I need to do something else to get it?
Thanks.
sorry, it is netctl.
Please follow the Arch guide on setting up netctl : https://wiki.archlinux.org/index.php/Netctl (https://wiki.archlinux.org/index.php/Netctl)
What connection manager you using currently to connect to the WiFi or Ethernet ?
-
Forgot to ask.....
What's best way in console to 'eject' my ethernet CF card in order to insert my WiFi card?
Thanks!
depending what you use to initiate the connection. I use netctrl and would do :
Example :
netctrl stop ethernet
# remove CF ethernet and plug in CF WiFi
netctrl start wifi
Thanks for the input!
However, when I tried this, I get:
# netctrl stop ethernet
-bash: netctrl not found
So, I tried installing it, but I got this:
# pacman -S netctrl
error: target not found: netctrl
Assume that either netctrl is part of some other package or I need to do something else to get it?
Thanks.
sorry, it is netctl.
Please follow the Arch guide on setting up netctl : https://wiki.archlinux.org/index.php/Netctl (https://wiki.archlinux.org/index.php/Netctl)
What connection manager you using currently to connect to the WiFi or Ethernet ?
No worries....thanks for clarifying and the additional info...
Please note that I haven't used Arch for about 2 years or so....so, re-familiarizing myself now with Arch again.....
Tried 'netctl stop ethernet' again, but lights on ethernet card are still lit up and one blinking as before....
So, card still working.....
As for connection manager, I haven't used one yet....I just booted up Z with the ethernet card plugged in and connected with ethernet cable and it recognized card and connection.....
btw, not seeing any ncurses window when using wifi-menu.......just console.....
No luck so far getting wifi working.....
Card had indicator light working when I booted up I think, but no light is off....
According to netctl page on ArchWiki, you need to setup a profile in /etc/netctl....did the following to try and generate the profile file in /etc/netctl/:
# wifi-menu -o
But nothing created there....
Just tried copying wireless-wpa example and editing it.....
Then
# netctl start wireless-wpa
Job for netctl1@wireless\x2dwpa.service failed because the control process exited with error code. See "systemctl status "netctl1@wireless\\x2dwpa.service"" and "journalctl -xe" for details.
# systemctl status "netctl1@wireless\\x2dwpa.service
* netctl1@wireless\\x2dwpa.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Tried to get more info on WiFi card:
# lspci | grep -i wireless
pclib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
In searching online for info on this card, I came across a page with this card for sale, info it lists about it says:
Wireless Security 128-bit WEP RC4 Wireless Data Encryption
Also, found on another site some more info about card:
Chipset Driver
Prism2/2.5/3 hostap
Been reading more info on this.....
https://wiki.archlinux.org/index.php/Wirele...k_configuration (https://wiki.archlinux.org/index.php/Wireless_network_configuration)
Rebooted with Ethernet card inserted so I can install some other programs.
Tried to install networkmanager...but got error message on 2 files:
libpgm
zeromq
Tried again and now I get '404' and 'error: failed to commit transaction (unexpected error)' and 'error: failed to retrieve some files'....
Any tips on how to get card working?
-
Hi ArchiMark!
Good to hear you can finally boot Arch! That's a big step forward!
As you say, the screen does sometimes blank properly under 4.2.3 kernel but more often the screen goes white for me.
You won't see an ncurses interface for wifi-menu unless you install dialog.
Unfortunately though it seems your Ambicom is using the same wifi chipset as my old wifi card - a PLANEX GW-CF11X which uses the PRISM 3 chipset and I've had even less luck with getting that to work than my new card which I can at least get to scan and connect. The prob with my new card is if you try to download something or use pacman it starts off very slow, like 10K/s then rapidly gets slower and slower before it gives up, errors and stops working completely.
My new wifi card - the SparkLAN WCFM-100 only has 1 set of firmware files for the CF chipset version. The prob with the PRISM devices is there are at least 20 or so different versions of the primary and secondary firmware files and non of the ones I tried worked.
To turn off your ethernet or wifi card you run:
ip link set eth0 down
I've found this guide to be helpful:
http://linuxcommando.blogspot.co.uk/2013/1...fi-network.html (http://linuxcommando.blogspot.co.uk/2013/10/how-to-connect-to-wpawpa2-wifi-network.html)
Good luck!
-
I wouldn't let my bad experience with PRISM stop you from trying though Mark - you do have a different model which may require different firmware and so it could work?
This page seems to be the definitive resource for PRISM info:
http://linux.junsun.net/intersil-prism/ (http://linux.junsun.net/intersil-prism/)
I tried writing to the author of that page to see if he knew of any more PRISM firmware download sites but he did not and no longer maintains the page or uses Prism devices.
If you do find some suitable firmware for your device then copy it into /lib/firmware and try it out!
-
wifi-menu won't work unless you have dialog installed AND it finds your wlan0 device, which won't appear until you have the correct firmware installled.
EDIT
You'll need to run
modprobe hostap_cs
To load the prism driver
-
Thanks, danboid!
Appreciate all daalnroti's and your help with getting Arch going.......
And appreciate your help with WiFi card too....
Here's a page I found with lots of WiFi cards listed with info about them.....
It has the AmbiCom model card I have listed too:
http://linux-wless.passys.nl/query_alles.php (http://linux-wless.passys.nl/query_alles.php)
It has link to driver files:
http://hostap.epitest.fi/ (http://hostap.epitest.fi/)
Which leads to:
http://w1.fi/releases/ (http://w1.fi/releases/)
Do you think any of these files are what I need for the card?
I just got up this morning and when I saw my Z the display had turned white all during the night.....
I did install dialog....but no ncurses window comes up when doing
# wifi-menu wlan0
Is that what you use 'wlan0' for wifi interface?
I get 'No such interface: wlan0'
Just noticed you use 'eth0'.....so, you use it for WiFi card too.....hmmmm..............
-
Looking at that list of files you linked to it seems you have a PRISM 2 based card whilst mine is PRISM 3. That page on prism I linked to earlier explains how to identify what firmware your card needs but it looks like you don't need to do any hunting like I've had to.
I used eth0 in that example ip command as I presumed you wanted to turn off your ethernet card? Mine is USB and needs to be plugged into a powred hub so I have no use for such a command. Swap eth0 for wifi0 to turn off your wifi card, if/when you get it working.
I've found I don't need to specify a network device with wifi-menu. So long as my wifi card is plugged in and its module/firmware has been loaded, wifi-menu auto-detects it. Its not working for you because you've not loaded the hostap_cs module and/or not copied the correct firmware files into /lib/firmware.
Run that modpobe command from my previous post when you have your wifi plugged in then check the output of dmesg -it'll prob be complaining of missing firmware for wifi0 if you''ve not installed it.
You'll need to also install iw and/or wireless_tools to get iwconfig. iw was supposed to have deprecated iwconfig but some (old) wifi drivers apparently still work better with iwconfig. To check for wifi devices you run
iw dev
For more info on configuring wifi read the guide I linked to earlier.
That s really all I know about Linux wifi!
-
Decided to try stopping Ethernet card, eject it, and then insert WiFi card again.....
Now, when I did it, this time it recognized there was a WiFi card inserted after I did
# netctl start wifi
Lignt on card blinked....
So, did
# ifconfig wlan0
And I see info about wlan0 interface listed!
So, did
# wifi-menu wlan0
And voila! the ncurses window came up!
And I see my wireless network listed and long with some others in the area.....
Selected it in menu.....
Screen went black for about 5 seconds.....then I see the command prompt again at top of screen.....
Tried to ping and voila! it worked! So AmbiCom card is working!!!
However, when I tried to install something via pacman, I got error message:
# pacman -S screen
resolving dependencies.....
looking for conflicting packages..
Packages (1) screen-4.3.1-2
Total Download Size: 0.44 MiB
Total Installed Size: 0.80 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages......
error: failed retrieving file 'screen-4.3.1-2-arm.tar.xz' from mirror.archlinux.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.
OK, tried it again, and this time it worked and installed it!
So, I've got working wifi!!!
Yeah!!!
-
Looking at that list of files you linked to it seems you have a PRISM 2 based card whilst mine is PRISM 3. That page on prism I linked to earlier explains how to identify what firmware your card needs but it looks like you don't need to do any hunting like I've had to.
I used eth0 in that example ip command as I presumed you wanted to turn off your ethernet card? Mine is USB and needs to be plugged into a powred hub so I have no use for such a command. Swap eth0 for wifi0 to turn off your wifi card, if/when you get it working.
I've found I don't need to specify a network device with wifi-menu. So long as my wifi card is plugged in and its module/firmware has been loaded, wifi-menu auto-detects it. Its not working for you because you've not loaded the hostap_cs module and/or not copied the correct firmware files into /lib/firmware.
Run that modpobe command from my previous post when you have your wifi plugged in then check the output of dmesg -it'll prob be complaining of missing firmware for wifi0 if you''ve not installed it.
You'll need to also install iw and/or wireless_tools to get iwconfig. iw was supposed to have deprecated iwconfig but some (old) wifi drivers apparently still work better with iwconfig. To check for wifi devices you run
iw dev
For more info on configuring wifi read the guide I linked to earlier.
That s really all I know about Linux wifi!
Thanks again for all your help.....sorry, I was writing post below while you were writing your post above.....
But good info to have here....
As you can see, I got card working!
Without having to get any files or do much work!
Meanwhile, it might be helpful (or it might not....) to you and daalnroti check out the thread over at maemo.org regarding Arch on the Nokia N900.....
I had one until about 2 years and managed to get Arch running OK on it and with Xorg and XFCE too!......
Maybe there's some useful and relevant info, even thought these are different devices?
Just a thought....
http://talk.maemo.org/showthread.php?t=81892 (http://talk.maemo.org/showthread.php?t=81892)
-
I'm happy to hear you've got your wifi working Mark! Do you know if your card supports 802.11g or is it just b?
Have you tried doing a pacman -Syu or downloading something big like xorg yet?
What about suspend? Does your connection still work or can you at least get it back up easily after going in and out of suspend mode?
-
I'm happy to hear you've got your wifi working Mark! Do you know if your card supports 802.11g or is it just b?
Have you tried doing a pacman -Syu or downloading something big like xorg yet?
What about suspend? Does your connection still work or can you at least get it back up easily after going in and out of suspend mode?
Thanks......
According to this page, it's b.....
http://www.rakuten.com/prod/ambicom-wave2n...#specifications (http://www.rakuten.com/prod/ambicom-wave2net-wl1100c-cf-wireless-lan-compactflash-card/10345629.html#specifications)
I can only assume that info listed is accurate.....
Haven't tried -Syu or dowloading xorg or suspend......yet.....but while try soon....gotta head out to work now....but will try from there.....
-
UPDATE
Tried pacman -Syu and it worked OK....but did get 2 warning messages about permissions differences between directory and packages for:
/var/games
/var/spool/mail
Decided to be brave and try getting Xorg working.....
Not so good....
Installed xf86-video-fbdev, xorg-server, xorg-server-utils.....then installed xfce4
Did startx and got:
xauth: file /root/.xauthority does not exist
Then long lines of text regarding X.org X Server.....
rebooted.....
tried again.....
Screen went white (or maybe grey...) but then went black.....then back to console....
then tried startxfce4 and same thing happened, but.......screen did not go back to console....now just have black screen and can't figure out how to go back to console....
Any suggestions???
Also, is Alt key the left or right key with Japanese characters on it (these are keys to the right of the Ctrl key...) ?
Also, what key or key combo is meant when I see 'altgr' ?
Thanks!
-
I got those same permissions errors when I did a -Syu after installing from the ZALARM rootfs but I did not get those errors when I installed using the official ALARM ARMv5 tarball. I doubt it's anything to worry about.
I only asked if you'd tried downloading X because it was the first biggish thing that came to mind as a decent way to test the reliability of your connection. I have got X to run kinda but I didn't install any DE, just twm or whatever the default wm is. X isn't usable yet unless you fix the keymapping, screen rotation (ie configure xorg.conf) and we need a touchscreen calibration tool but I don't think I could bear trying to use X at 640x480 in 2015 when I'm so used to 1920x1080 and multiple monitors! I'm much more interested in getting SDL fixed up so we can run some emus as they don't require a decent resolution screen.
You can switch VTs by holding Fn and pushing left/right - that would let you login to another console and run something like
killall -15 X
To kill X.
I'm not sure the Z has an AltGr (aka right Alt) key mapped as standard as its almost never used. What made you ask about that?
Have you checked to see if wifi survives suspend with your Ambicom?
-
Thanks for your help......understand now your points about X......
By "You can switch VTs by holding Fn and pushing left/right", do you mean left or right arrow on the D-pad or ?
I tried the arrow keys + Fn, but does not change screen....still black......
I asked about AltGr as I seem to recall reading that it was part of key combo to scroll back up in console.....is that correct or is there other keys we can use with our Z for this?
Haven't gotten around to testing suspend yet......
Thought I'd have fun with X first......
Meanwhile, I've been scanning through the posts over at talk.maemo.org regarding Arch on N900....got it working plus LXDE (posted some screenshots, post #386...) back on May 1 2013.......so, been a while......some interesting info there....I've been noting which posts may have some useful info.....
-
Was it difficult to get twm or whichever it is to run?
-
Dunno why I never bought the N900 as I was excited about its release and I got to use one a week or so before they went on general release in the UK. It could still be the coolest Linux phone ever. My mate Rui is one of the few owners of the N950, I expect because of his standing in the Qt community.
-
No twm 'just ran' - no xorg.conf or anything but thats why the screen was orientated wrong, most of the keys don't work....
I did have to install a few other packages that are really X org deps that you just need to know about like xterm, xinit amd stuff.
-
No twm 'just ran' - no xorg.conf or anything but thats why the screen was orientated wrong, most of the keys don't work....
I did have to install a few other packages that are really X org deps that you just need to know about like xterm, xinit amd stuff.
Thanks for the info......very helpful...
Can you please read my post above....#216 regarding getting back to console.....
Thanks!
PS. In reading one of the maemo posts, I found a post by someone there that said they had 5 Zaurus.....so, just sent them a message telling them about this project here and to check it out.....
-
Yes, I meant hold Fn and push the left/right arrows or directional keys/ whatever you call those things surrounding the OK button to switch VTs. It works for me and apparently daal too so it seems strange its not working for you.
5 Zaurii! I had 2 at one point but my 3100 died many years ago. I thought I'd kept it (for parts if nothing else) but I can't find it - I've spent most of this afternoon looking for it!
I have noticed a newcomer reading this thread so maybe that was Mr 5Z!
-
Yes, I meant hold Fn and push the left/right arrows or directional keys/ whatever you call those things surrounding the OK button to switch VTs. It works for me and apparently daal too so it seems strange its not working for you.
5 Zaurii! I had 2 at one point but my 3100 died many years ago. I thought I'd kept it (for parts if nothing else) but I can't find it - I've spent most of this afternoon looking for it!
I have noticed a newcomer reading this thread so maybe that was Mr 5Z!
Thanks for clarifying...although odd as you say that it doesn't work for me....
Guess I'll have to shutdown Z and restart....
Think the person visiting was here before I sent message to Mr 5 Z's....
Doing my best to drum up interest for this...had hoped to at least of 2 my OBSD on Z buddies here by now...
Will see if I can get twm working....
-
Sound works OK - I've just tried playing a FLAC file under moc.
I had to install alsa-utils for alsamixer which I had to use to unmute some of the left, right and left mixer right controls before any sound came out.
ArchiMark:
I've since realised that when I tried X under ZALARM I didn't know how to switch VTs so I just hard reset the Z or pulled the battery so I'm not sure if the VT switching works when X is loaded. It works when in the console for me. It will probably not be working because the X keymap hasn't been set correctly.
-
Sound works OK - I've just tried playing a FLAC file under moc.
I had to install alsa-utils for alsamixer which I had to use to unmute some of the left, right and left mixer right controls before any sound came out.
You must have been reading my mind....I just made a note earlier today to bring up the subject of audio.......
Thanks for the info, will try to do as you describe.....
ArchiMark:
I've since realised that when I tried X under ZALARM I didn't know how to switch VTs so I just hard reset the Z or pulled the battery so I'm not sure if the VT switching works when X is loaded. It works when in the console for me. It will probably not be working because the X keymap hasn't been set correctly.
Thanks for clarifying.....
Meanwhile, I just approved 2 new members for OESF forum.....1 mentioned joining to be able to put Arch on his Z.....
Hopefully, we'll hear from him soon......
It's been so long now, but someone with admin rights at OESF, gave them to me as well probably 5 years ago or so, thinking that I might end up being the last man standing here.....
-
Hi all,
I will try to catch up with all this happening here but in the meantime a new kernel build for those that are keen to test !
https://github.com/greguu/linux-4.2.3-c3x00...leases/tag/v0.3 (https://github.com/greguu/linux-4.2.3-c3x00/releases/tag/v0.3)
Note : I had, like always, not much time to test. It seems to boot, but thats about all I know. Any feedback welcome.
Cheers!
-
Thanks for the new kernel daal!
I've installed it. It boots OK but for some reason my USB ethernet adapter doesn't work under this kernel so now I have no networking at all - well at least until I re-install the previous kernel or you fix it!
dmesg 'sees' my hub and ethernet adapter, there are no errors that I can see and I never had to load a module to get it working before so I'm at a bit of a loss. Could this be related to you supposedly enablling more USB wifi adapters somehow?
EDIT
lsusb sees it too - 0b95:7720 ASIX electronics corp AX88772 . ifconfig -a does not.
EDIT 2
The screen still goes white after 10m in this version - not that you claimed to have fixed it.
-
My prob with my ethernet adapter doesn't seem to be the fault of the new kernel as I've just reverted back to 0.2 and its still not working. It works on my laptop so it must be a prob with my hub or one of its cables.
I need to get one that will run off bus power like daal has.
-
Ethernet is back! So it wasn't a hardware issue either - for some reason Linux had previously been autoloading the asix kernel module for me but today it decided the free ride was over so I had to:
modprobe asix
Which depends on usbnet.
I'm going to try again with the latest kernel now that scare is over then
-
Hi daal
I noticed the release notes for 4.2.3 0.3 state:
* Added PXA2xx cpufreq
It doesn't seem to be working for me but maybe I missing something? I have got:
pxa27x_maxfreq=624
Appended to my kernel parameters in boot.cfg for the latest kernel but lscpu says I'm still running at 416Mhz.
-
Don't know what happened, but having problems accessing and posting on this website today. Both at home and at office....
Meanwhile having various issues with Z after doing system upgrade via pacman...
Main issue is Ethernet not working now...assume this has to with upgrading system....
Any suggestion as to how to get this working again?
Otherwise, I assume I'll need to reinstall Arch again....
Thanks!
-
It sounds like you're having the same problem as I had earlier. You need to find out what kernel module your ethernet adapter requires and then use modprobe to dynamically load it or add the module name to /etc/modules to have it loaded at boot.
-
It sounds like you're having the same problem as I had earlier. You need to find out what kernel module your ethernet adapter requires and then use modprobe to dynamically load it or add the module name to /etc/modules to have it loaded at boot.
Thanks for your help...
Think it might be 'hostap_cs' ?
Will try it soon and report back...
Only way I can post right now is by using my mobile phone.....
Very odd....
-
hostap_cs is the kernel module for your wifi, not your ethernet
-
hostap_cs is the kernel module for your wifi, not your ethernet
Oh yeah.....thanks.....got too many things going on today....
Hmmm...will do a search on my Socket 10/100 card.....
Thanks!
-
Can't seem to find the card info online....
Is there a command I can use with card inserted to get needed info?
Thanks!
-
You could try lspcmcia and dmesg.
I've got video playback working under the console although it def. struggles to play back VGA res MP4 files.
I had to use the SDL EVs mentioned earlier in this thread then I used:
mplayer -vo sdl video.mp4
mpv is the best video player but unfortunately its Arch package is compiled without SDL support which is what it requires to play video outside of X as mpv has no direct fbdev support.
I've got some more exciting news too but I'm goiing to deliver that in the form of a video soon!
-
You could try lspcmcia and dmesg.
Thanks!.....
lspcmcia: command not found
dmesg......scrolls by too quick....I see some lines of text about midway during scrolling that look red......
Ok, figured out how to get dmesg to show without scrolling by......
# dmesg | grep -i pcmcia
or
# dmesg | less
Unfortunately, don't get much info on card with dmesg:
# dmesg | grep -i pcmcia
[ 1.360213] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 1.365150] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 1.370279] pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1
[ 1.375084] pcmcia 1.0: pcmcia: registering new device pcmcia1.0 (IRQ: 218)
[ 1.427098] scsi host0: pata_pcmcia
I've got video playback working under the console although it def. struggles to play back VGA res MP4 files.
I had to use the SDL EVs mentioned earlier in this thread then I used:
mplayer -vo sdl video.mp4
mpv is the best video player but unfortunately its Arch package is compiled without SDL support which is what it requires to play video outside of X as mpv has no direct fbdev support.
I've got some more exciting news too but I'm goiing to deliver that in the form of a video soon!
Wow, sounds great........standing by for video soon......
-
That's weird. lspcmcia is part of the pcmciautils package under x64 Arch but it doesn't seem to be in the ALARM repos.
If you have a Linux PC with a CF card reader it might be easier to try to get some info out of the card that way.If there is no model number or manfacturer printed on the card and/or you have no luck with lspcmcia you may have to compile your own pcmciatools. Or you could boot another distro where it works and find out the module name by running lsmod.
As you've noticed, we have no good way to scroll the console buffer yet - you just have to use good ol' grep, less, more and pals. That'd be one good thing about getting X going - scrollable console buffers!
-
That's weird. lspcmcia is part of the pcmciautils package under x64 Arch but it doesn't seem to be in the ALARM repos.
Yep......and I've noticed other items that aren't found.....
If you have a Linux PC with a CF card reader it might be easier to try to get some info out of the card that way.If there is no model number or manfacturer printed on the card and/or you have no luck with lspcmcia you may have to compile your own pcmciatools. Or you could boot another distro where it works and find out the module name by running lsmod.
Yes, have 2 other laptops with linux...so, will see what I can find out that way...
There are two numbers on the back of the card that might be model number, but they're not labeled.....
One is under a bar code: 00E098 C38EC8
Hmmm.....looks like this is a hardware address according to info on:
http://www.mit.edu/~map/Ethernet/vendor.html (http://www.mit.edu/~map/Ethernet/vendor.html)
Other is below another bar code: 8510-00179C
On the bottom of this webpage:
https://www.socketmobile.com/support/downloads/ethernet (https://www.socketmobile.com/support/downloads/ethernet)
NE2000 Compatibility
The Socket Rugged CF 10/100 card is not NE2000 compatible. NE2000 compatible drivers should function with this card after some small changes are implemented. These changes involve the initialization process and are limited in scope. Small differences exist in the NE2000 compatible register set but these do not affect general operation of the Rugged CF 10/100 card.
The zip file contains Driver porting notes, PHY files and the ASIX AX88790 L 10/100 Ethernet Controller datasheet.
So, thought maybe this card has asix controller......
# modprobe asix
#
# modprobe asix_ax88790
modprobe: FATAL: Module asix_ax88790 not found.
Dang!!!...................
OK, will try card on laptop and see what I can find out......
As you've noticed, we have no good way to scroll the console buffer yet - you just have to use good ol' grep, less, more and pals. That'd be one good thing about getting X going - scrollable console buffers!
Yes, indeed......
-
Try
modprobe pcnet_cs
or
modprobe axnet_cs
and run ifconfig -a after probing for each
http://tuxscreen.net/wiki/view/PCMCIA (http://tuxscreen.net/wiki/view/PCMCIA)
-
Try
modprobe pcnet_cs
or
modprobe axnet_cs
and run ifconfig -a after probing for each
http://tuxscreen.net/wiki/view/PCMCIA (http://tuxscreen.net/wiki/view/PCMCIA)
THANKS!!!
pcnet_cs worked......
Got ethernet working again!.....
Yeah!
Now, just gotta hope that Arch fixes systemd or whatever it is that made system wonky.....
-
That's weird. lspcmcia is part of the pcmciautils package under x64 Arch but it doesn't seem to be in the ALARM repos.
If you have a Linux PC with a CF card reader it might be easier to try to get some info out of the card that way.If there is no model number or manfacturer printed on the card and/or you have no luck with lspcmcia you may have to compile your own pcmciatools. Or you could boot another distro where it works and find out the module name by running lsmod.
As you've noticed, we have no good way to scroll the console buffer yet - you just have to use good ol' grep, less, more and pals. That'd be one good thing about getting X going - scrollable console buffers!
pcimciautils have been removed from the ALARM repo a long time ago. I compiled a binary, see attached.
example :
./pccardctl status
Socket 0:
3.3V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "pcnet_cs"
Socket 1:
3.3V 16-bit PC Card
Subdevice 0 (function 0) bound to driver "pata_pcmcia"
./pccardctl info
PRODID_1="BUFFALO"
PRODID_2="LPC-CF-CLT"
PRODID_3="R01"
PRODID_4=""
MANFID=026f,0307
FUNCID=6
PRODID_1="HITACHI"
PRODID_2="microdrive"
PRODID_3=""
PRODID_4=""
MANFID=0319,0000
FUNCID=4
I might add this binary to the next rootfs release.
-
You could try lspcmcia and dmesg.
Thanks!.....
lspcmcia: command not found
dmesg......scrolls by too quick....I see some lines of text about midway during scrolling that look red......
What's the trick (key combo...) to be able to scroll back up through the text....have tried various combos, but no luck so far.....
I've got video playback working under the console although it def. struggles to play back VGA res MP4 files.
I had to use the SDL EVs mentioned earlier in this thread then I used:
mplayer -vo sdl video.mp4
mpv is the best video player but unfortunately its Arch package is compiled without SDL support which is what it requires to play video outside of X as mpv has no direct fbdev support.
I've got some more exciting news too but I'm goiing to deliver that in the form of a video soon!
Wow, sounds great........standing by for video soon......
MPLAYER : It would playback faster if you re-encode the video rotated and use "-vo fbdev" . You can rotate with mplayer, but this is slow too. (-vf rotate=1)
I have not tried video playback with arch on the Z. x264 would be to hard to decode for the Z. I think divx3 or mpeg2 would play more fluent if I remember correctly.
CPUFREQ : the previous 4.2.3 kernel did not have cpufreq support. Current one does but I have not found out how to over clock. Not sure this is possible without a patch.
ETHERNET : I have tested the current kernel and did a pacman -Syu. My card modules get still auto loaded, no need for /etc/modules. I wonder what the issues is. Saying that I have still issues because of systemd as mentioned earlier. I tested on a clean rootfs, the same issue when upgrading to latest systemd via pacman -Syu
SYSTEMD : You can downgrade to systemd-226-3 and systemd-sysvcompat-226-3. I have attached the previous systemd version in case you do not have it. If your modules autoload with the previous version then at least we know that the issue is systemd.
-
Thanks for this, daalnroti.....
Will try these files out in the next day or so....
Meanwhile, I tried pacman now that I can connect to internet again....
But I either get 'target not found' or 'error: failed retrieving file 'xxxx.....' from mirror.archlinuxarm.org:
Could not resolve host: mirror.archlinuxarm.org'
-
As you've noticed, we have no good way to scroll the console buffer yet - you just have to use good ol' grep, less, more and pals. That'd be one good thing about getting X going - scrollable console buffers!
Really, installing X just to get a scrollable console buffer ? I found some time and mapped Fn + n (ScrollUp), Fn + m (ScrollDown). See attached map file.
It was simple as that :
keycode 49 = n
altgr keycode 49 = Scroll_Backward
keycode 50 = m
altgr keycode 50 = Scroll_Forward
-
Thanks for this, daalnroti.....
Will try these files out in the next day or so....
Meanwhile, I tried pacman now that I can connect to internet again....
But I either get 'target not found' or 'error: failed retrieving file 'xxxx.....' from mirror.archlinuxarm.org:
Could not resolve host: mirror.archlinuxarm.org'
Confirm first that you can connect to the internet.
ping google.com
ping mirror.archlinuxarm.org
If these fail, you may not have a proper connection ? Do you use DHCP ?
what does
ip addr
route
show ?
-
Hi daal
I noticed the release notes for 4.2.3 0.3 state:
* Added PXA2xx cpufreq
It doesn't seem to be working for me but maybe I missing something? I have got:
pxa27x_maxfreq=624
Appended to my kernel parameters in boot.cfg for the latest kernel but lscpu says I'm still running at 416Mhz.
Hi danboid.
I did some testing and it turns out the pxa27x_maxfreq=624 does not get passed on to cpufreq. I hardcoded now the 624Mhz in the kernel.
See attached a 4.2.3 v0.3 kernel that will boot with maxfeq 624 Mhz.
Setting it to 624Mhz or 520Mhz causes a known issue with the LCD driver, resulting in flickering.
You can change the frequency and governor via the cpufreq-set tool and check with cpufreq-info.
The PXA270 CPU found in the Cxx00 series is capable of running stable at 624 Mhz, but will get more hot.
The Z was not designed to run at that speed and components (LCD for example) are not in tune with higher clock speeds.
If I remember correctly , there used to be a fix for the LCD issue when over-clocking back in the pdaxrom days...
Cheers!
-
Meanwhile, I've been scanning through the posts over at talk.maemo.org regarding Arch on N900....got it working plus LXDE (posted some screenshots, post #386...) back on May 1 2013.......so, been a while......some interesting info there....I've been noting which posts may have some useful info.....
My main phone is a Nokia N9. I possibly could install Arch on it too, as it is almost the same as the N900. I still run the stock ROM plus Sailfish Theme.
It is outdated but still has all the apps I need and works fine. I pre-ordered a Jolla Tablet and hope to get it delivered this year.
-
You may find Tmux usefull : https://wiki.archlinux.org/index.php/Tmux (https://wiki.archlinux.org/index.php/Tmux) (pacman -S tmux)
-
The screen still goes white after 10m in this version - not that you claimed to have fixed it.
Hi danboid,
I have not fixed that issue yet. You can add
consoleblank=120
to your boot.cfg kernel options. It will set the time when the console will blank in seconds.
It seems the first few blanks will go white, then it goes black.
I will need to compare 3.11.3 code for framebuffer and vt with the 4.2.3 code to see what changed.
In the meantime the "setterm -blank" fix would be sufficient, I guess.
-
daal:
Great to hear you fixed the keymap to add scrolling!
I'll try your overclocked kernel today but I don't think Arch uses the cpufreq tools any more to manually set the CPU as its not in the repos any more. cpupower is the replacement ( see https://wiki.archlinux.org/index.php/CPU_frequency_scaling (https://wiki.archlinux.org/index.php/CPU_frequency_scaling) ) and when I run:
# cpupower frequency-info
With the latest normal kernel (not the hard overclocked one) it says 416Mhz is the max and its already set to the performance governor. I've tried using
# cpupower frequency-set -f 624
but that gives me an error saying no can do. I'm not really concerned about it though - if the hard-coded overclocked kernel works I'm fine rebootiing to change CPU speed.
Could you update post #1 with a link to my guide now that ArchiMark has proved it works please? Thanks for that and also for the tips on screenblanking which I'll try soon.
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
EDIT
daal: You could also update the first post to mention that sound works and that one user has had success getting wifi working using wifi-menu.
-
daal:
Great to hear you fixed the keymap to add scrolling!
I'll try your overclocked kernel today but I don't think Arch uses the cpufreq tools any more to manually set the CPU as its not in the repos any more. cpupower is the replacement ( see https://wiki.archlinux.org/index.php/CPU_frequency_scaling (https://wiki.archlinux.org/index.php/CPU_frequency_scaling) ) and when I run:
# cpupower frequency-info
With the latest normal kernel (not the hard overclocked one) it says 416Mhz is the max and its already set to the performance governor. I've tried using
# cpupower frequency-set -f 624
but that gives me an error saying no can do. I'm not really concerned about it though - if the hard-coded overclocked kernel works I'm fine rebootiing to change CPU speed.
Could you update post #1 with a link to my guide now that ArchiMark has proved it works please? Thanks for that and also for the tips on screenblanking which I'll try soon.
daal: You could also update the first post to mention that sound works and that one user has had success getting wifi working using wifi-menu.
Hi danboid,
I have updated the OP to include the changes you requested.
My main arch setup still has cpufrequtils installed. I read about cpupower, but was not aware cpufrequtils as been obsolete !
I can provide a cpufrequtils package if needed. Please test with cpupower, but keep in mind I have no intention to troubleshoot and support the over-clocked kernel.
Cheers!
-
Thanks Daal!
I'll still let you know if the overclocked kernel boots and does what it says on the tin later.
http://smjrifle.net/restore-asroot-yaourtmakgpkg-arch/ (http://smjrifle.net/restore-asroot-yaourtmakgpkg-arch/)
"Let me build stuff as root goddammit!" fixed under Arch the lazy way - yay!
-
http://smjrifle.net/restore-asroot-yaourtmakgpkg-arch/ (http://smjrifle.net/restore-asroot-yaourtmakgpkg-arch/)
"Let me build stuff as root goddammit!" under Arch fixed the lazy way - yay!
I use yaourt on my x86 machine, but not on the Z. I agree, yaourt not allowing builds as root is annoying, but I got used to it. Good to know there is a fix.
BTW : you can use most AUR packages under ALARM. you just need to modify the architecture to include arm.
https://github.com/archlinuxarm/PKGBUILDs (https://github.com/archlinuxarm/PKGBUILDs) is a good resource if you need to do a custom build of any application.
Building Packages for Arch Linux ARM, you need to.
Install the build essentials. These are needed to compile packages on Arch Linux ARM.
$ sudo pacman -S kernel26-headers file base-devel abs
( NOTE : kernel26-headers may be outdated, check for the most recent package )
Obtain the PKGBUILD. You need to download the tarball that you want. You can find the tarballs for programs at the AUR.
Make the packages. Next you need to run makepkg in order to generate a package that pacman can install.
$ makepkg -Acs
The -A option ignores the target Arch architecture. The -c option cleans up the directory after makepkg is done, and -s installs the needed dependencies.
It is advised that you do NOT run makepkg as root as it can cause permanent damage to your system. If you really need to run it as root though, use the --asroot option.
Install the package. makepkg should have create a file in the directory with the filetype .pkg.tar.xz. You should install this package by using the -U option with pacman.
$ sudo pacman -U x.pkg.tar.xz
Make sure you replace x.pkg.tar.xz with the actual package name.
-
TIME : when cold booting your Z , do you get the correct time after boot ? As far as I know the RTC does not work. I installed fake-hwclock. It helps a bit.
-
Just as a general advise, if doing a pacman -Syu , make sure you do merge / update all new config files in /etc
pacman will mention which new config files got installed during the upgrade process.
For more info : https://wiki.archlinux.org/index.php?title=...new_and_Pacsave (https://wiki.archlinux.org/index.php?title=Pacman/Pacnew_and_Pacsave)
Please report any issues within this thread, but also keep in mind some issues are ALARM specific and not related to the zALARM port.
Checking the Arch Wiki and forums as well the ALARM forums is a good place to start to troubleshoot any issues.
-
I wonder if we should move over to "Distro Support and Discussion" and have ArchLinuxARM added there.
ArchiMark : can you do this ?
This would allow us to open new topics about issues and have it all more organized.
There is also the option to move to ALARM forum and create a new entry under community supported devices ?
-
This thread is getting pretty long now so it would be good if Archi can make a new zALARM distro sub-forum? I'd presume he can as I think he's basically the boss round these parts now!
AFAIK the Z doesn't have a hardware clock. It normally has the right date for me which NTP must've set but making sure my clock is right is somethng I'll only bother with after I've got the basics up and running. There's still too much churn for me to be bothering with that just yet!
-
This thread is getting pretty long now so it would be good if Archi can make a new zALARM distro sub-forum? I'd presume he can as I think he's basically the boss round these parts now!
AFAIK the Z doesn't have a hardware clock. It normally has the right date for me which NTP must've set but making sure my clock is right is somethng I'll only bother with after I've got the basics up and running. There's still too much churn for me to be bothering with that just yet!
HWCLOCK :
I consider having a correct time quite important.
Attached is a fake hwclock package if anyone is interested.
It does not ensure a correct time, but keeps time recorded somewhat between cold reboots. (if you are not online and don't have NTP. )
You will need to extract it first and then add with "pacman -U" . (This forum does not allow uploading of tar.xz)
-
This thread is getting pretty long now so it would be good if Archi can make a new zALARM distro sub-forum? I'd presume he can as I think he's basically the boss round these parts now!
zALARM ? I know you created that name. What about ALARMz ?
In the end it does not matter, but I would suggest to call the forum subsection ArchLinuxARM to keep it standard and simple.
-
And what about a freenode IRC channel :? (#zalarm or #alarmz)
This would be good to troubleshoot issues in real time.
I know there are timezone differences between the users but why not ?
Do we need to add a "log-bot" on the channel to keep track of conversations ?
ArchiMark, danboid , what is your take on this ?
-
I've mainly been calling it ZALARM up until now but ALARMZ or ALARMz is arguably slightly better in that you can say it a little bit faster, it's almost a real word an it's at the start of the alphabet instead of the end!
I agree that the new forum should probably be called just "Arch Linux ARM" so people will know what it is on first sight but I propose 4 semi-official distro-specific monikers coz we're too good for just one:
ALARMz
ALARMZ
ZALARM
zALARM
The ALARM bit is always capitlalised as the ALARM team like it that way and we should try to keep them happy!
EDIT
I think the IRC channel should be #ALARMZ
-
I've mainly been calling it ZALARM up until now but ALARMZ or ALARMz is arguably slightly better in that you can say it a little bit faster, it's almost a real word an it's at the start of the alphabet instead of the end!
I agree that the new forum should probably be called just "Arch Linux ARM" so people will know what it is on first sight but I propose 4 semi-official distro-specific monikers coz we're too good for just one:
ALARMz
ALARMZ
ZALARM
zALARM
The ALARM bit is always capitalized as the ALARM team like it that way and we should try to keep them happy!
EDIT
I think the IRC channel should be #ALARMZ
Well, lets make a decision then.
If ArchiMark could create a sub-forum called "ArchLinuxARM" and appoint you and me as moderators, so we can pin topics etc, that would be a start.
Alternatively we could move to the ALARM forums, but being OESF veterans, I guess we like to stay here ...
IRC : well, go ahead and create the channel. l am ready to join.
-
The OC kernel seems to work great so far - thanks daal! I do remember X flickering a bit when I ran the Z at 624Mhz under pdaXrom but the console doesn't flicker under ALARMZ. I'm sure the battery won't last as long at 624Mhz but that's only to be expected
I'm logged into #ALARMZ on freenode now.
-
Thanks for this, daalnroti.....
Will try these files out in the next day or so....
Meanwhile, I tried pacman now that I can connect to internet again....
But I either get 'target not found' or 'error: failed retrieving file 'xxxx.....' from mirror.archlinuxarm.org:
Could not resolve host: mirror.archlinuxarm.org'
Confirm first that you can connect to the internet.
ping google.com
ping mirror.archlinuxarm.org
If these fail, you may not have a proper connection ? Do you use DHCP ?
what does
ip addr
route
show ?
Thanks for your help.....
When I said in prior post I could connect to internet again, this was after I tested pinging google....
I usually do it this way:
# ping -c 4 8.8.8.8
And it works....4 packets transmitted, 4 received, 0% packet loss.....
But when I ping mirror.archlinuxarm.org, I get:
# ping -c 4 mirror.archlinuxarm.org
ping: unknown host
# ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid _lft forever preferred_lft forever
inet6 : : 1/128 scope host
2: eth0: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 00:e0:98:c3:8e:c8 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.5/24 brd 192.168.0.255 scope global dynamic eth0
valid _lft 37944sec preferred_lft 37944sec
inet6 fe80: :2e0:98ff:fec3:8ec8/64 scope link
valid _lft forever preferred_lft forever
# route
Kernel IP Routing Table
Destination Gateway Gemask Flags Metric Ref Use Iface
default gateway 0.0.0.0 UG 1024 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
gateway * 255.255.255.255 UH 1024 0 0 eth0
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
-
Just as a general advise, if doing a pacman -Syu , make sure you do merge / update all new config files in /etc
pacman will mention which new config files got installed during the upgrade process.
For more info : https://wiki.archlinux.org/index.php?title=...new_and_Pacsave (https://wiki.archlinux.org/index.php?title=Pacman/Pacnew_and_Pacsave)
Please report any issues within this thread, but also keep in mind some issues are ALARM specific and not related to the zALARM port.
Checking the Arch Wiki and forums as well the ALARM forums is a good place to start to troubleshoot any issues.
Hmmmmmm.......didn't do this when I did -Syu..........
I wonder if we should move over to "Distro Support and Discussion" and have ArchLinuxARM added there.
ArchiMark : can you do this ?
This would allow us to open new topics about issues and have it all more organized.
There is also the option to move to ALARM forum and create a new entry under community supported devices ?
This thread is getting pretty long now so it would be good if Archi can make a new zALARM distro sub-forum? I'd presume he can as I think he's basically the boss round these parts now!
AFAIK the Z doesn't have a hardware clock. It normally has the right date for me which NTP must've set but making sure my clock is right is somethng I'll only bother with after I've got the basics up and running. There's still too much churn for me to be bothering with that just yet!
I don't know if I'm the boss, but I got the keys handed to me.....
I hope someone else still has them too.....and someone must still be paying the bills to keep this site going....
When I get a chance, maybe later today, I'll try to create a new section as requested.....
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
Do you know how DNS works? You should read up on it if not.
Anyway, if you can't access the Arch mirrors or any site that isn't being reference by IP address alone (ie via DNS) you'll likely need to run
systemctl start systemd-resolved.service
If that fixes pacman etc then run:
systemctl enable systemd-resolved.service
To start the systemd DNS resolver daemon automatically at boot.
-
It seems we still have 5 keys (the Calendar/Address etc keys) not mapped to anything useful in the borzoi keymap. I think the Calendar/Address keys should map to F11 and F12 then it might make sense to map HOME to PgUP and MENU to PgDown.
Also, rather than using Fn+n/m to scroll up and down, how about using either Fn+UP/DOWN instead? Seems more logical and memorable to me alhough there may be a reason why you didn't choose that key combo daal?
EDIT
Haha! It was only a couple of days ago I was saying how AltGr is hardly ever used and now I try out a program (hatari) that relies heavily on using AltGr! Maybe AltGr is a good candidate for the Mail key?
-
It seems we still have 5 keys (the Calendar/Address etc keys) not mapped to anything useful in the borzoi keymap. I think the Calendar/Address keys should map to F11 and F12 then it might make sense to map HOME to PgUP and MENU to PgDown.
Also, rather than using Fn+n/m to scroll up and down, how about using either Fn+UP/DOWN instead? Seems more logical and memorable to me alhough there may be a reason why you didn't choose that key combo daal?
Hi danboid,
the 5 zaurus specific keys are currently mapped to some F keys. We can change that sure.
F11 and F12 are already mapped as FN + o and FN + p.
I used Fn +n/m for scrolling because I like to keep PageUp/ PageDown on the arrows.
Nothing stops you from modifying your borzoi.map.gz !
You can load the keyfile while running with "loadkeys" and test.
ALTGR : Fn is AltGr !
FYI : https://wiki.archlinux.org/index.php/Keyboa...tion_in_console (https://wiki.archlinux.org/index.php/Keyboard_configuration_in_console)
Cheers!
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
HI ArchiMark,
odd, you can try different DNS servers if you can not resolve mirrors.archlinuxarm
I had no issue with this so far.
Keep in mind that you should only use one network connection manager at a time.
Do not run "netctl" and "networkd" or "networkmanager" or "connman" or "wicd" at the same time, this will surely mix things up.
Since there are so many choices, troubleshooting can be a nightmare. I use netctl because it is simple and has no extra dependencies.
Also I would suggest to revert back to previous systemd to module auto loading again (if related) and start from there.
This modules not loading automatically is the first thing to get fixed.
Cheers!
-
The OC kernel seems to work great so far - thanks daal! I do remember X flickering a bit when I ran the Z at 624Mhz under pdaXrom but the console doesn't flicker under ALARMZ. I'm sure the battery won't last as long at 624Mhz but that's only to be expected
I'm logged into #ALARMZ on freenode now.
Great, when I played with it and ran "cpufreq-set -f" I thought it started flickering like it did under pdaXrom. Would be good to have some benchmarks but I guess I stay with 416 Mhz at this stage.
Freenode : good I will join today, its Sunday already here so I might be away from the Z for some time.
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
have a look what your /etc/resolv.conf looks like .
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
HI ArchiMark,
odd, you can try different DNS servers if you can not resolve mirrors.archlinuxarm
I had no issue with this so far.
OK, will try that.....thanks...
Keep in mind that you should only use one network connection manager at a time.
Do not run "netctl" and "networkd" or "networkmanager" or "connman" or "wicd" at the same time, this will surely mix things up.
Since there are so many choices, troubleshooting can be a nightmare. I use netctl because it is simple and has no extra dependencies.
Understand....only running netctl.....
Also I would suggest to revert back to previous systemd to module auto loading again (if related) and start from there.
This modules not loading automatically is the first thing to get fixed.
Cheers!
Agree.......think my various issues started after systemd got updated....
If that takes care of things, then good.....
If not, then I'll probably create a new fresh install and go from there.....
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
have a look what your /etc/resolv.conf looks like .
/etc/resolv.conf is empty................
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
HI ArchiMark,
odd, you can try different DNS servers if you can not resolve mirrors.archlinuxarm
I had no issue with this so far.
OK, will try that.....thanks...
Keep in mind that you should only use one network connection manager at a time.
Do not run "netctl" and "networkd" or "networkmanager" or "connman" or "wicd" at the same time, this will surely mix things up.
Since there are so many choices, troubleshooting can be a nightmare. I use netctl because it is simple and has no extra dependencies.
Understand....only running netctl.....
Also I would suggest to revert back to previous systemd to module auto loading again (if related) and start from there.
This modules not loading automatically is the first thing to get fixed.
Cheers!
Agree.......think my various issues started after systemd got updated....
If that takes care of things, then good.....
If not, then I'll probably create a new fresh install and go from there.....
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
have a look what your /etc/resolv.conf looks like .
/etc/resolv.conf is empty................
There you go Check https://wiki.archlinux.org/index.php/Resolv.conf (https://wiki.archlinux.org/index.php/Resolv.conf)
Example using OpenDNS :
# OpenDNS IPv4 nameservers
nameserver 208.67.222.222
nameserver 208.67.220.220
There are several ways to have resolv.conf auto generated. Have a a look at "resolvconf" too.
If you use DHCP your resolv.conf should contain your gateways IP as nameserver. If not using DHCP you need to add it manually ether in you netctl profile or resolv.conf.
-
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
HI ArchiMark,
odd, you can try different DNS servers if you can not resolve mirrors.archlinuxarm
I had no issue with this so far.
OK, will try that.....thanks...
Keep in mind that you should only use one network connection manager at a time.
Do not run "netctl" and "networkd" or "networkmanager" or "connman" or "wicd" at the same time, this will surely mix things up.
Since there are so many choices, troubleshooting can be a nightmare. I use netctl because it is simple and has no extra dependencies.
Understand....only running netctl.....
Also I would suggest to revert back to previous systemd to module auto loading again (if related) and start from there.
This modules not loading automatically is the first thing to get fixed.
Cheers!
Agree.......think my various issues started after systemd got updated....
If that takes care of things, then good.....
If not, then I'll probably create a new fresh install and go from there.....
Mark:
As for your connection probs, you may recall me saying that if you have DNS issues you should make sure systemd-resolved.service is running?
https://wiki.archlinux.org/index.php/Systemd-networkd (https://wiki.archlinux.org/index.php/Systemd-networkd)
Thanks, danboid......
I assume it's running if I can ping google, right?
......but lots of good info on that page....
have a look what your /etc/resolv.conf looks like .
/etc/resolv.conf is empty................
There you go Check https://wiki.archlinux.org/index.php/Resolv.conf (https://wiki.archlinux.org/index.php/Resolv.conf)
Example using OpenDNS :
# OpenDNS IPv4 nameservers
nameserver 208.67.222.222
nameserver 208.67.220.220
There are several ways to have resolv.conf auto generated. Have a a look at "resolvconf" too.
If you use DHCP your resolv.conf should contain your gateways IP as nameserver. If not using DHCP you need to add it manually ether in you netctl profile or resolv.conf.
Thanks, was already working in this after last post.....but having problem saving /etc/resolv.conf file....
Nano won't let me save file....
So, did:
# ls -l /etc/
lrwxrwxrwx 1 alarm alarm 32 Oct 4 05:10 resolv.conf -> /run/systemd/resolve/resolve.conf
-rw-r--r-- 1 root root 459 Oct 22 13:08 resolv.conf.bak
So, resolv.conf got symlinked over to systemd?........
Does this look right?
-
Notice anything different, guys????
-
daal:
Thanks for the notes on the keymap. I must admit I've been too lazy to ungzip and inspect it myself yet. I realise I can tweak it to my own liking but my last post was to try and come to an agreement over what we should use for a default keymap ie what comes with the rootfs.
Mark:
Thanks for moving this thread and creating a new subforum!
I should've mentioned /etc/resolv.conf. If yours is empty, you'll notice that running
systemctl start systemd-resolved.service
Populates it.
Note that if you downgrade to the older systemd, which I'll prob do too, be sure to edit /etc/pacman.conf and add the name of the package(s) (systemd etc) that you want to stop from being upgraded to the IgnorePkg line or else -Syu will revert you to the latest.
-
Mark:
Thanks for moving this thread and creating a new subforum!
You're most welcome.....
I should've mentioned /etc/resolv.conf. If yours is empty, you'll notice that running
systemctl start systemd-resolved.service
Populates it.
Thanks, can ping mirror.archlinuxarm.org and pacman works now!
Note that if you downgrade to the older systemd, which I'll prob do too, be sure to edit /etc/pacman.conf and add the name of the package(s) (systemd etc) that you want to stop from being upgraded to the IgnorePkg line or else -Syu will revert you to the latest.
OK, thanks.....
-
I've downgraded systemd and systemd-sysvcompat on my ALARMZ install back to 226-3 using the packages daal posted yesterday (in #243) although I suppose I could've used the downgrade script (https://aur.archlinux.org/packages/downgrade/) to achieve the same result. Now the kernel module for my USB ethernet adapter gets auto-loaded again and I don't get any pam errors during login.
To stop pacman -Syu updating systemd before I want it to be updated, I've added this line to /etc/pacman.conf
IgnorePkg = systemd systemd-sysvcompat
-
I've downgraded systemd and systemd-sysvcompat on my ALARMZ install back to 226-3 using the packages daal posted yesterday (in #243) although I suppose I could've used the downgrade script (https://aur.archlinux.org/packages/downgrade/) to achieve the same result. Now the kernel module for my USB ethernet adapter gets auto-loaded again and I don't get any pam errors during login.
To stop pacman -Syu updating systemd before I want it to be updated, I've added this line to /etc/pacman.conf
IgnorePkg = systemd systemd-sysvcompat
Thanks for the info.....will do this when I downgrade systemd.....
X and Window Manager
Just got X running and twm....
But like you, twm is opening up sideways.....need to rotate display 90 degrees....
Just tried fluxbox and it opens up sideways too.....
And just started new 'X and Window Manager' thread to continue discussion there.
Since we now have our own forum, no reason not to have some specific threads for specific topics....
https://www.oesf.org/forum/index.php?showtopic=34400 (https://www.oesf.org/forum/index.php?showtopic=34400)
-
Thanks for the update Mark!
I would say that the quest to get X working is worthy of creating a new thread for, if you want to? This thread is not over but its long enough already!
-
Thanks for the update Mark!
I would say that the quest to get X working is worthy of creating a new thread for, if you want to? This thread is not over but its long enough already!
Brilliant idea, Dan!
No reason we can't split off threads by specific topics now.....
-
I've downgraded systemd and systemd-sysvcompat on my ALARMZ install back to 226-3 using the packages daal posted yesterday (in #243) although I suppose I could've used the downgrade script (https://aur.archlinux.org/packages/downgrade/) to achieve the same result. Now the kernel module for my USB ethernet adapter gets auto-loaded again and I don't get any pam errors during login.
To stop pacman -Syu updating systemd before I want it to be updated, I've added this line to /etc/pacman.conf
IgnorePkg = systemd systemd-sysvcompat
Just decompressed the .gz file on my laptop......
Now I see 2 files; systemd-226-3-arm.tar.xz and systemd-sysvcompat-226-3-arm.tar.xz
As I would like to avoid messing up system further, where should I decompress these to files to on my SD card?
/usr/lib/systemd/system/
or
/etc/systemd/system/
or ???
UPDATE
Just checked ArchWiki about manual package install.....
Assume I do:
# pacman -U /root/Download/packagename.tar.gz
OR
# pacman -U /root/Download/*.tar.gz
for multiple package installs at one time....
I am checking Wiki and other pages quite a bit to refresh myself on Arch as it's been about 2.5 years since I last used it...
Thanks!
-
When I try to install packages manually per post above, I get error messages:
# pacman -U /path to package/packagename.tar.gz
loading packages...
error: missing package metadata in /root/systemd226.tar/gz
error: '/root/systemd226.tar/gz': invalid or corrupted package
Same message for both systemd226 and pccardctl......
Am I missing something in process???
Thanks.
UPDATE
Realized that perhaps a reason for problem is related to my copying files from laptop to SD card instead of untarring them to card?
So, then thought of maybe it's best to download files directly to SD from forum.....using wget....
But having issue with file downloaded this way.....get error message when using pacman about unrecognized archive format....
What do you recommend as best way to install files like systemd226 and pccardctl, etc that get posted here?
-
I have been mainly copying files over via SD card but thats mainly because I'm currently stuck with USB ethernet + powered hub and the mass of cables that involves if I want any networking. If I had wifi working I would be using scp or sftp to copy files from my laptop but otherwise yes, you might be better off using wget to download files directly.
One thing to note if you're copying files to SD or CF cards from a Linux machine is after unmounting a drive its best to run the sync command to make sure all files have fully transferred.
-
I have been mainly copying files over via SD card but thats mainly because I'm currently stuck with USB ethernet + powered hub and the mass of cables that involves if I want any networking. If I had wifi working I would be using scp or sftp to copy files from my laptop but otherwise yes, you might be better off using wget to download files directly.
One thing to note if you're copying files to SD or CF cards from a Linux machine is after unmounting a drive its best to run the sync command to make sure all files have fully transferred.
Thanks for the input and reminder about 'sync'.......
Have tried various ways of doing wget, including username and password info, but get error message, about syntax error near unexpected token ';&'...
and another message when I try adding username and password info another way.....
Also, get weird situation where wget starts going to other zaurus related sites/repos to try to get file......
So, think best at least for now is to copy files over......
-
OK, recopied files over to SD card from laptop. Did 'sync' after I copied.....
Now when I do 'pacman -U /root/pccardctl.tar.gz' I still get error message:
error: missing package metadata in /root/pccardctl.tar.gz
error: '/root/pccardctl.tar.gz' : invalid or corrupted package
????
UPDATE
Tried downloading files on laptop, but saving them directly to SD card....
But I get exact same error message as above when trying to install using pacman.....
-
OK, recopied files over to SD card from laptop. Did 'sync' after I copied.....
Now when I do 'pacman -U /root/pccardctl.tar.gz' I still get error message:
error: missing package metadata in /root/pccardctl.tar.gz
error: '/root/pccardctl.tar.gz' : invalid or corrupted package
????
UPDATE
Tried downloading files on laptop, but saving them directly to SD card....
But I get exact same error message as above when trying to install using pacman.....
PCCARDCTL :
extract the file with tar, and run it
cd /root
tar xf pccardctl.tar.gz
./pccardctl info
this means the binary will be at /root, you can copy the binary to /usr/local/bin, a better place if you intend to use the tool more often and from everywhere.
SYSTEMD :
extract the files with tar, and run pacman -U
cd /root
tar xf systemd226.tar.gz
pacman -U systemd-226-3-arm.tar.xz systemd-sysvcompat-226-3-arm.tar.xz
and see danboids' post about masking these packages and prevent them from getting updated when you do a pacman -Syu
-
OK, recopied files over to SD card from laptop. Did 'sync' after I copied.....
Now when I do 'pacman -U /root/pccardctl.tar.gz' I still get error message:
error: missing package metadata in /root/pccardctl.tar.gz
error: '/root/pccardctl.tar.gz' : invalid or corrupted package
????
UPDATE
Tried downloading files on laptop, but saving them directly to SD card....
But I get exact same error message as above when trying to install using pacman.....
PCCARDCTL :
extract the file with tar, and run it
cd /root
tar xf pccardctl.tar.gz
./pccardctl info
this means the binary will be at /root, you can copy the binary to /usr/local/bin, a better place if you intend to use the tool more often and from everywhere.
SYSTEMD :
extract the files with tar, and run pacman -U
cd /root
tar xf systemd226.tar.gz
pacman -U systemd-226-3-arm.tar.xz systemd-sysvcompat-226-3-arm.tar.xz
and see danboids' post about masking these packages and prevent them from getting updated when you do a pacman -Syu
Thank you, daalnroti....really appreciate your help.....
Will do as you suggest.....and danboid....
Still seems very odd that this is happening though.....
-
This thread and the installl guide both refer to installing on the C3x00 but I'd expect the same kernel should also work for the C1000, right daal?
I suppose we shoud wait until a C1000 user has verified that before I update the installl guide etc.
-
Started working on this today and of course show stopper before I even got started.
For some reason recovery flash can't see my SD card, but it mounts in BSD just fine on the Z (and also on the linux machine I copied files from), so I can't get kexecboot going *sigh*
Been long enough I don't remember but was there some size limit with the Z? It's only 2gb sandisk ... its a micro in a SD adapter, maybe that is the problem?
-
The card should be formatted as FAT or ext2. I've only ever tried FAT though so I'd stick with that.
I've heard some people say you have to use FAT12 but I'm certain I've installed off fat32 fine.
2GB should be fine. I think I've installed kexecboot off a 4GB CF card before.
-
PCCARDCTL :
extract the file with tar, and run it
cd /root
tar xf pccardctl.tar.gz
./pccardctl info
this means the binary will be at /root, you can copy the binary to /usr/local/bin, a better place if you intend to use the tool more often and from everywhere.
Done and works!
SYSTEMD :
extract the files with tar, and run pacman -U
cd /root
tar xf systemd226.tar.gz
pacman -U systemd-226-3-arm.tar.xz systemd-sysvcompat-226-3-arm.tar.xz
and see danboids' post about masking these packages and prevent them from getting updated when you do a pacman -Syu
Done and system now works the way it did before.......Whew!!
Thanks for all the help, daalnroti and danboid!!
OK, back to having fun with Arch.............
-
The card should be formatted as FAT or ext2. I've only ever tried FAT though so I'd stick with that.
I've heard some people say you have to use FAT12 but I'm certain I've installed off fat32 fine.
2GB should be fine. I think I've installed kexecboot off a 4GB CF card before.
+1 for FAT.....
And Walt, I used 2GB SanDisk card too (although not the microSD...)....but think you should be good....
-
Now that I've got Arch running OK.....on my SD card....I'd like to have it running from the internal drive.....
Think I'll put my 32GB CF card in Zaurus to replace 6GB microdrive.....
I had thought of copying the current install over to the internal drive rather than extracting the rootfs tarball on it.
What do you guys think is best?
Trying to avoid more headaches if possible....
If it's safe to copy over install from SD card, then would I use DD command or ?
Thanks for your input...
UPDATE
Decided to go all the way and use my 32GB CF card. Therefore, doing a fresh install.....figure that's best for the long run....
Going to try the experimental rootfs too....what the heck.....
UPDATE 2
Ready to swap out my microdrive with the 32GB Card, but now I realize the little screwdriver I have with me is not small enough.....
Will try to pickup a super tiny one soon.....
-
Best Day Ever!
Ok, maybe not that crazy but I am for sure super excited to have ArchLinux|ARM running on my Z. BIG THANKS to all that put work into making this possible, and esp danboid for the guide.
I have ran Archlinux|ARM on pogoplugs since Feb 2012 (give or take), so pretty familiar with how things work as far as that goes. I now have a full install running off microdrive at the moment, but of course want to swap it out for a CompactFlash as well. I can't remember, is it an easy unplug/plug and that's it?
BTW: Never got the SD to read for some reason. I found an old 1GB compact flash that I installed from, zero issues. I also have my TRENDnet TE-CF100 network card working just fine.
So at this point I have installed htop and sudo just to test pacman, but haven't done any system upgrades not knowing what will break. I think i saw some posts about having to IgnorePkg some files, will read through all that. Also need to check out if any newer kernel is worth upgrading to vs what was in the tarball.
Hope I can test and contribute to this project from now on.
-
Best Day Ever!
Ok, maybe not that crazy but I am for sure super excited to have ArchLinux|ARM running on my Z. BIG THANKS to all that put work into making this possible, and esp danboid for the guide.
I have ran Archlinux|ARM on pogoplugs since Feb 2012 (give or take), so pretty familiar with how things work as far as that goes. I now have a full install running off microdrive at the moment, but of course want to swap it out for a CompactFlash as well. I can't remember, is it an easy unplug/plug and that's it?
BTW: Never got the SD to read for some reason. I found an old 1GB compact flash that I installed from, zero issues. I also have my TRENDnet TE-CF100 network card working just fine.
So at this point I have installed htop and sudo just to test pacman, but haven't done any system upgrades not knowing what will break. I think i saw some posts about having to IgnorePkg some files, will read through all that. Also need to check out if any newer kernel is worth upgrading to vs what was in the tarball.
Hope I can test and contribute to this project from now on.
EXCELLENT, Walt!
This is great news....glad you came aboard the ArchLinuxARM Train......
Now if ol' Sean hops on, we'll be close to our goal of Five Eyes.....
-
Good to hear you got ALARMZ installed Walt!
As for upgrading your MD, I found it a bit scary pulliing my Z to bits but you can do it in an hour or so. See post #61 (at the top of page 5) of this thread for my notes on the process.
Are we closer to five eyes? We need ZALARM users from Canada and Australia to complete the five. Where do you live Walt?
-
Good to hear you got ALARMZ installed Walt!
As for upgrading your MD, I found it a bit scary pulliing my Z to bits but you can do it in an hour or so. See post #61 (at the top of page 5) of this thread for my notes on the process.
Are we closer to five eyes? We need ZALARM users from Canada and Australia to complete the five. Where do you live Walt?
I finished swapping out the MD for the CF an hour ago.....as you say, a bit scary, especially with those itsy bitsy little tiny screws....plus the battery compartment plastic piece falling out, etc....but somehow managed to get it done and my Z now has 30+ GB's available.....nice!!...
You need to get a super tiny philips head (#000) and standard screwdriver (3/64")- to take out the screws....
Dan's link to the Japanese website with all the photos of Z disassembled was extremely helpful. However, the Japanese translation to English is awkward at best. I misunderstood the text and took out the aluminum sheild under the battery compartment, not necessary, and saves dealing with 3 less super tiny screws...
Be careful when trying to remove the black plastic piece that contains the microdrive from the circuit board. the two tiny tabs that hold it to the circuit board are very fragile, just use very tiny amount of pressure with fingernail or screwdriver to barely push it to get plastic piece free from circuit board. I almost tore off one of the tabs...fortunately didn't break off....
Worth the trouble though in the end....very nice having a 32GB drive....
Walt's in US, so, guess we're only at 3 Eyes....maybe 3.5?..............
-
Are we closer to five eyes? We need ZALARM users from Canada and Australia to complete the five. Where do you live Walt?
On a clear day I can see Canada from across Lake Erie in Ohio, does that count?
-
3.2 to match our internal CF drive capacity or 3.3 eyes at a push to go with the real 5 eyes undoubted Masonic leanings
-
Has anyone tried a >=64GB CF card with their Z yet?
-
3.2 to match our internal CF drive capacity or 3.3 eyes at a push to go with the real 5 eyes undoubted Masonic leanings
Hmmm.....something to look forward to!.....
Should I dust off my decoder ring?
Has anyone tried a >=64GB CF card with their Z yet?
Not yet.....
I'm still enjoying all the space with 32GB card versus the dinky 6GB MB I just yanked out....
-
Should I dust off my decoder ring?
We should have a decoder ring as the ALARMZ 'mascot' / logo.
-
Has anyone tried a >=64GB CF card with their Z yet?
Saw the posts about putting a CF card into the Z. iamasmith documented the process in 2006 on here. I hope the link I include will take you there. Seems clearer and more detailed than the link in this thread?
iamasmith's posts about CF card (https://www.oesf.org/forum/index.php?showtopic=19684&st=0&p=129173&#entry129173)
-
Should I dust off my decoder ring?
We should have a decoder ring as the ALARMZ 'mascot' / logo.
Great idea!.....So, we'll have 3.2 eyes on it?
Has anyone tried a >=64GB CF card with their Z yet?
Saw the posts about putting a CF card into the Z. iamasmith documented the process in 2006 on here. I hope the link I include will take you there. Seems clearer and more detailed than the link in this thread?
iamasmith's posts about CF card (https://www.oesf.org/forum/index.php?showtopic=19684&st=0&p=129173&#entry129173)
Where were you yesterday, tux, when I was trying to take apart my Z???
Great post and pics.....
Thanks, for sharing this. Should help Walt and others that come along.......
or when I put in a 256GB CF card and need to open it up again...
-
A question please...
Time & Date - Timezone
Want to get time correct....date is one day behind and time of day is off.
When I check it, I get:
# timedatectl
Local time: Thu 2015-10-29 14:06:33 UTC
Universal time: Thu 2015-10-29 14:06:33 UTC
RTC time: Sat 2000-01-01 00:16:50
Time zone: UTC (UTC, +0000)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
When I try to set local timezone, I get:
# timedatectl set-timezone America/Los_Angeles
Failed to set time zone: Access denied
Seems odd since I logged in as root.....but I did read on Arch wiki, to try reinstalling tzdata and then set timezone....
Any suggestion to change timezone and set proper time?
Use ntp or ?
Thanks!
-
Have more serious issue now....
Hope there's a relatively simple fix....
I thought I had put the systemd related pkg names in /etc/pacman.conf on the IgnorePkg line as instructed here.
I did, later came to realize I had forgot to uncomment that line.....
So, when I did 'pacman -Syu' I noticed midway that it was starting to update systemd......panicked and did ctrl-C to stop process thinking it would not update it if process was halted. However, it must have done some updating as I noticed strange behavior afterwards. For example, when I did 'poweroff' it failed.
So, thought I would downgrade systemd again with the files provided here as I did before. But would not work this time.
Do 'pacman -U systemd-226-3-arm.pkg.tar.xz', then it starts process, but I get error messages:
# pacman -U systemd-226-3-arm.pkg.tar.xz
loading packages...
warning: downgrading package systemd (226-3.2 => 226-3)
resolving dependencies...
looking for conflicting packages....
error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory
Packages (1) systemd-226-3
Total Installed Size: 68.27 MiB
:: Proceed with installation? [Y/n]
If I say Yes, then it starts, but get error messages at each line saying that the item referred to 'exists in filesystem'
Then says at end 'Errors occurred, no packages were upgraded.'
I shutdown system by removing battery and restarted. Of course, won't boot up now with system on internal CF card.
So, put in my SD card with Arch on it and have now booted up Z and chrooted into the CF Card. But still get same error messages when doing 'pacman - U systemd-226-3-arm.pkg.tar.xz'......
Any suggestions as to how to get pacman to do the downgrade?
Or have I borked system to where I need to start with fresh install again?
Thanks.
-
So tried with --force to see if I could downgrade, but I get other messages now:
# pacman -U --force systemd-226-3-arm.pkg.tar.xz
loading packages...
warning: downgrading package systemd (226-3.2 => 226-3)
resolving dependencies...
looking for conflicting packages....
error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory
Packages (1) systemd-226-3
Total Installed Size: 68.27 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [*********] 100%
(1/1) checking package integrity [*********] 100%
(1/1) loading package files [*********] 100%
(1/1) checking for file conflicts [*********] 100%
error: could not open file: /etc/mtab: No such file or directory
error: could not determine filesystem mount points
error: not enough free disk space
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
Any suggestions now ?
Thanks!
-
I've not got much useful to suggest really other than to point out 226-3.2 coud actually have worked OK if you had let it fully install as it was 227 that had issues. Maybe 226-3 is fine?
I would imagine that cancelling midway through a systemd upgrade / downgrade wouldn't go down well as I think systemd is prob the biggest single package on most Arch systems.
-
I've not got much useful to suggest really other than to point out 226-3.2 coud actually have worked OK if you had let it fully install as it was 227 that had issues. Maybe 226-3 is fine?
I see your point about 226-3.2 now...but when I saw that systemd was on verge of updating, I panicked a bit thinking it was updating to 227...and figured I'd better stop it immediately....
seemed like a good idea at the moment.....
I would imagine that cancelling midway through a systemd upgrade / downgrade wouldn't go down well as I think systemd is prob the biggest single package on most Arch systems.
Yep, agree......but too late now.....
Seems like it's reinstall Arch time.....
-
Want to reinstall Arch onto my internal 32GB card. But don't want to remove it from my Zaurus....
Thought I'd download the rootfs file onto my SD card that has the Arch install on it that I use now to boot my Z with....
Did the following:
# wget -i https://github.com/greguu/alarm-zaurus-c3x00/releases/download/October2015/alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz
Get lots of text....then
Resolving github-cloud.s3.amazonaus.com.....54.231.112.136
Connecting to github-cloud.....connected.
HTTP request sent, awaiting response.....200 OK
Length: 135779144 (129M) [application/octet-stream]
Saving to: 'alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.1'
alarm-zaurus-c3x00- 0%[ ] 0 --, -KB/s in 0/004s
Cannot write to 'alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.1' (Success).
No URLs found in https://github.com/greguu/alarm-zaurus-c3x00/releases/download/October2015/alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz.
What am I missing here?
Thanks.
-
If you'd followed my install guide step-by-step then you would've already copied the rootfs tarball (in its unextracted form) onto your SD card but I presume thats not the case here.
The bit of terminal output you pasted showed you trying to download the tarball but where to, direct to the SD card? It says it cannot write to the current device so either:
* You didn't run the command as root
* There isn't enough space on your SD card or
* Your SD card is write protected
One of those was most likely tripping you up.
I wonder if daal will return now the rugby is over (and they won, again, of course)?
EDIT
If you do end up doing a re-install / upgrade Mark it would be useful for us if you tried out systemd 226-3. You may be better off with that than running 226-2 and you may not need the IgnorePkg?
-
Hey gang. I gave this a go today.
I ran into some issues with the KEXECBOOT updater not working on my Zaurus. I wound up having to do a complete NAND restore to factory settings to be able to install KEXECBOOT. The SD / CF updater would always fail.
After doing that, I was able to at least install KEXECBOOT and boot into ALARM on my CF card.
I then attempted to replace the internal 4GB microdrive with a 64GB microSD card housed in a Type 2 CF to MicroSD card adapter. I had planned on setting up the internal drive from the CF install of ALARM but to my surprise ALARM would not boot properly after putting in the new internal drive. I suspect that KEXECBOOT (or the NAND app) writes some data to the partitions on the Microdrive normally.
So I took out the internal CF / MicroSD card and partitioned it so that the two Sharp original partitions and files (.SYS directory) were on the new card.
I had planned on reinstalling from scratch (reinstall KEXECBOOT, etc) but even after the new partitioning of the SD / CF adapter, the KEXECBOOT install script tells me the microdrive is not found. Suxxor.
I'll continue with it some time next week. I don't know much about Arch Linux (avid OpenBSD user) so I'll have to learn the ecosystem. It's different enough for me to not know how to do a majority of the stuff I'd like to.
-
Started working on this today and of course show stopper before I even got started.
For some reason recovery flash can't see my SD card, but it mounts in BSD just fine on the Z (and also on the linux machine I copied files from), so I can't get kexecboot going *sigh*
Been long enough I don't remember but was there some size limit with the Z? It's only 2gb sandisk ... its a micro in a SD adapter, maybe that is the problem?
I had the same issue with mine. I used a 1gb standard SD and a 2gb micro SD card. Neither worked. Had to flash recovery from CF instead. OBSD and ALARM have no problem with the card. *shrug*
-
If you'd followed my install guide step-by-step then you would've already copied the rootfs tarball (in its unextracted form) onto your SD card but I presume thats not the case here.
Think I must have deleted the file at some point as the 2GB card was almost full..... will make a new backup SD card on a larger capacity card.....
Think it would be good if you mention in your instructions page that card should be larger than 2GB to allow for keeping various package files on it.
The bit of terminal output you pasted showed you trying to download the tarball but where to, direct to the SD card? It says it cannot write to the current device so either:
* You didn't run the command as root
* There isn't enough space on your SD card or
* Your SD card is write protected
One of those was most likely tripping you up.
Yep, you're right, not enough room on the SD card as noted above.....had to delete a bunch of other package files to free up space to be able to put the rootfs file back on the card....
I wonder if daal will return now the rugby is over (and they won, again, of course)?
OK, that explains it......
EDIT
If you do end up doing a re-install / upgrade Mark it would be useful for us if you tried out systemd 226-3. You may be better off with that than running 226-2 and you may not need the IgnorePkg?
OK, will do......
Reinstalling Arch now......
Hey gang. I gave this a go today.
I ran into some issues with the KEXECBOOT updater not working on my Zaurus. I wound up having to do a complete NAND restore to factory settings to be able to install KEXECBOOT. The SD / CF updater would always fail.
After doing that, I was able to at least install KEXECBOOT and boot into ALARM on my CF card.
I then attempted to replace the internal 4GB microdrive with a 64GB microSD card housed in a Type 2 CF to MicroSD card adapter. I had planned on setting up the internal drive from the CF install of ALARM but to my surprise ALARM would not boot properly after putting in the new internal drive. I suspect that KEXECBOOT (or the NAND app) writes some data to the partitions on the Microdrive normally.
So I took out the internal CF / MicroSD card and partitioned it so that the two Sharp original partitions and files (.SYS directory) were on the new card.
I had planned on reinstalling from scratch (reinstall KEXECBOOT, etc) but even after the new partitioning of the SD / CF adapter, the KEXECBOOT install script tells me the microdrive is not found. Suxxor.
I'll continue with it some time next week. I don't know much about Arch Linux (avid OpenBSD user) so I'll have to learn the ecosystem. It's different enough for me to not know how to do a majority of the stuff I'd like to.
Glad you finally gave it a go, but sorry to hear of your issues.....
Regarding your 64GB card issue......wondering if either
a. Issue with system recognizing such a large card
or
b. Issue with system dealing with an adapter with card in it?
Arch is definitely different than using OBSD.....but with your background in it plus the info and resources here and on Arch Wiki pages, I'm sure you'll make the transition pretty quickly......
Keep us posted.....
-
Got Arch reinstalled on Zaurus 32GB CF card internal drive....
Did pacman -Syu and it installed systemd-3.2 and it works OK....
Have reinstalled most of the programs I needed....
So, for the moment all is good....
Still would like to get X working though....
Started a separate thread for it, but no one has posted.....
I know some of you are not that interested in having it.....
But for a few apps it would be good to have the option....
-
Good to hear you've decided to give ALARM a go teh.sean!
As Mark has already said, we don't know if the Z can handle cards larger than 32GB and it doesn't help that you're using an adapter. I've not had good experiences with SD card adapters so that doesn't bode well for CF to SD adapters in my eyes.
I'd rather leave my install guide recommending at least a 1GB card. Note that I say at least, not "it must be a 1GB card card". This lowers the barriers to entry a little bit and I didn't intend for people to use the install card for anything other than preparing the internal drive, extracting the rootfs and for performing recovery operations.
I will cetainly contribute to the X thread when I have something useful to add but thats a bit of an afterthought to me. I mainly just want to get wifi working so I can use SSH in more locations and situations and I want to get directfb working so that MAME runs better and we can run Quake.
Don't worry - daal is still alive but he's too busy to dedicate any time to the Z right now. I've just been talking to him in #ALARMZ. He has given me some tips on using directfb on the Z and says he will return to the forum next week with any luck.
-
I'm surprised its took me so long to check but it seems acpi is broken or the required kernel module isn't being loaded or isn't included as a kernel module so I don't know of any way to check the battery status. `acpi -b` and `acpi -i` both say:
No support for device type: power_supply
-
Good to hear you've decided to give ALARM a go teh.sean!
As Mark has already said, we don't know if the Z can handle cards larger than 32GB and it doesn't help that you're using an adapter. I've not had good experiences with SD card adapters so that doesn't bode well for CF to SD adapters in my eyes.
I'd rather leave my install guide recommending at least a 1GB card. Note that I say at least, not "it must be a 1GB card card". This lowers the barriers to entry a little bit and I didn't intend for people to use the install card for anything other than preparing the internal drive, extracting the rootfs and for performing recovery operations.
I will cetainly contribute to the X thread when I have something useful to add but thats a bit of an afterthought to me. I mainly just want to get wifi working so I can use SSH in more locations and situations and I want to get directfb working so that MAME runs better and we can run Quake.
Don't worry - daal is still alive but he's too busy to dedicate any time to the Z right now. I've just been talking to him in #ALARMZ. He has given me some tips on using directfb on the Z and says he will return to the forum next week with any luck.
Understand about 1GB card as a minimum size......just think it good to point out that having a 4GB card or larger, will allow one ot have an Arch install on it plus a rootfs and a few other files that someone may want to have to save time if those files are needed. My 2GB card is virtually full with the rootfs and a few other files....plus a few apps installed...
Glad to hear that you would be willing to assist with X at some point....
[EDIT] The key thing I think is to first get X to rotate the display (tried with xrandr command but no change when I did it.....). At least then you can start to use it....then build from there....does that make sense?
And good that daal is still alive and hopefully well......and providing input...
I'm surprised its took me so long to check but it seems acpi is broken or the required kernel module isn't being loaded or isn't included as a kernel module so I don't know of any way to check the battery status. `acpi -b` and `acpi -i` both say:
No support for device type: power_supply
Will be great if this gets working sometime.....
-
I'm surprised its took me so long to check but it seems acpi is broken or the required kernel module isn't being loaded or isn't included as a kernel module so I don't know of any way to check the battery status. `acpi -b` and `acpi -i` both say:
No support for device type: power_supply
Hi,
charging is broken on the Z. I guess acpi is part of that issue. The current kernel does not offer a ACPI as an option for the PXA27x platform
Your Z still charges, but slow. I have not found a solution to this yet.
Cheers!
-
Hi all,
just to let you know. The systemd issue is resolved. ALARM repositories changed the systemd version already (downgrade)
It is safe to do a "pacman -Syu" at the moment.
Good Luck
Cheers!
-
daal:
In that case I think you should update the OP and maybe the github notes for the kernel to note that we have no way to check the battery status.
It is a shame about the current kernels lack of ACPI for PXA270 but that seems to be about the only thing thats not working under ALARMZ. In every other way its light years ahead of every other distro and OS I've tried for the C3000.
Did you see my post about the C1000? I presume your kernel should work for C1000 users too right?
-
WIFI UPDATE
Back in post #179 on p12 of this thread, daal suggested it might be worth me trying to get a PLANEX GW-CF54G wifi if I wanted 802.11g as they are supposed to work with the Z. I looked into those cards and it turns out they use the same Libertas chipset as used in my SparkLAN WCFM-100.
A bit of searching uncovered this page:
http://nokamoto.blogspot.co.uk/2008/01/zau...x-gw-cf54g.html (http://nokamoto.blogspot.co.uk/2008/01/zaurus-sl-c3100-with-planex-gw-cf54g.html)
Which claims my wifi chipset should work under "Debian" (which version they didn't say) with the Yonggun kernel with the firmware they provide a link to. I tried their supposedly working firmware with 4.2.3 under Arch first but it worked even less than the previous firmware I've been trying so I've just spent most of the day installing Debian Wheezy which was the last Debian release to use sysv by default. I expect it could be tricky to use Jessie or later without a recent kernel as it uses systemd by default and I'm trying to use a 2.6 kernel here, which I can't use with the sysd-based Arch, of course. I installed Wheezy by following the OmegaMoon guide:
http://www.omegamoon.com/blog/static.php?page=ZaurusDebian (http://www.omegamoon.com/blog/static.php?page=ZaurusDebian)
and I've been trying to get it to boot using the Yonggun kernel and modules from here:
http://yonggun.tistory.com/68 (http://yonggun.tistory.com/68)
but all I'm getting when I try to boot is:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(3,2)
I have tried setting root=/dev/hda2 and root=/dev/sda2 in boot.cfg only to get the same error. I believe it was still /dev/hda2 under 2.6.
You're dual-booting your Z with Debian aren't you daal? Which version of Debian? What kernel are you using and what APPEND= paramaters do you use in your Debian boot.cfg? Are you using an ext3 or ext4 Debian root?
The company I bought my wifi card off have offered to refund me if I return it soon but if I can get it working under an older kernel (under a different distro) and prove its not a hardware fault then I'll hold onto it and boot into Debian when I want to use SSH.
All the guides I've found for installing Debian on the Z and the Yonggun kernel seem to presume you're using the SHARP bootloader. Maybe that's why I'm having no luck or maybe I should've installed to ext3 instead of ext4?
-
WIFI UPDATE
Back in post #179 on p12 of this thread, daal suggested it might be worth me trying to get a PLANEX GW-CF54G wifi if I wanted 802.11g as they are supposed to work with the Z. I looked into those cards and it turns out they use the same Libertas chipset as used in my SparkLAN WCFM-100.
A bit of searching uncovered this page:
http://nokamoto.blogspot.co.uk/2008/01/zau...x-gw-cf54g.html (http://nokamoto.blogspot.co.uk/2008/01/zaurus-sl-c3100-with-planex-gw-cf54g.html)
Which claims my wifi chipset should work under "Debian" (which version they didn't say) with the Yonggun kernel with the firmware they provide a link to. I tried their supposedly working firmware with 4.2.3 under Arch first but it worked even less than the previous firmware I've been trying so I've just spent most of the day installing Debian Wheezy which was the last Debian release to use sysv by default. I expect it could be tricky to use Jessie or later without a recent kernel as it uses systemd by default and I'm trying to use a 2.6 kernel here, which I can't use with the sysd-based Arch, of course. I installed Wheezy by following the OmegaMoon guide:
http://www.omegamoon.com/blog/static.php?page=ZaurusDebian (http://www.omegamoon.com/blog/static.php?page=ZaurusDebian)
and I've been trying to get it to boot using the Yonggun kernel and modules from here:
http://yonggun.tistory.com/68 (http://yonggun.tistory.com/68)
but all I'm getting when I try to boot is:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(3,2)
I have tried setting root=/dev/hda2 and root=/dev/sda2 in boot.cfg only to get the same error. I believe it was still /dev/hda2 under 2.6.
You're dual-booting your Z with Debian aren't you daal? Which version of Debian? What kernel are you using and what APPEND= paramaters do you use in your Debian boot.cfg? Are you using an ext3 or ext4 Debian root?
The company I bought my wifi card off have offered to refund me if I return it soon but if I can get it working under an older kernel (under a different distro) and prove its not a hardware fault then I'll hold onto it and boot into Debian when I want to use SSH.
All the guides I've found for installing Debian on the Z and the Yonggun kernel seem to presume you're using the SHARP bootloader. Maybe that's why I'm having no luck or maybe I should've installed to ext3 instead of ext4?
I use a custom build 2.6.36-rc3 kernel under Debian. This kernel has not build in the prism or libertas drivers unfortunately and I am not sure I still have the source for this one.
The younggun kernel should work with Debian, at least it did when I moved to Debian ages ago.
It is /dev/hdaX with the 2.6 kernels and you will need ext3 very likely. No special APPEND parameters.
LABEL=Debian
KERNEL=/boot/zImage-2.6.36-rc3
APPEND=console=ttyS0,115200n8 root=/dev/hda1 rootfstype=ext3 console=tty1 noinitrd fbcon=rotate:1 debug dyntick=enable
If your WiFi card works with a 2.6 kernel, it does not mean it will work under 4.2 etc.
The current linux kernel on github shows these firmware files matched to certain models of the libertas chipset.
If your issues are firmware related you may find some clue what files you need to match your model.
static const struct lbs_fw_table fw_table[] = {
{ MODEL_8305, "libertas/cf8305.bin", NULL },
{ MODEL_8305, "libertas_cs_helper.fw", NULL },
{ MODEL_8381, "libertas/cf8381_helper.bin", "libertas/cf8381.bin" },
{ MODEL_8381, "libertas_cs_helper.fw", "libertas_cs.fw" },
{ MODEL_8385, "libertas/cf8385_helper.bin", "libertas/cf8385.bin" },
{ MODEL_8385, "libertas_cs_helper.fw", "libertas_cs.fw" },
{ 0, NULL, NULL }
};
MODULE_FIRMWARE("libertas/cf8305.bin");
MODULE_FIRMWARE("libertas/cf8381_helper.bin");
MODULE_FIRMWARE("libertas/cf8381.bin");
MODULE_FIRMWARE("libertas/cf8385_helper.bin");
MODULE_FIRMWARE("libertas/cf8385.bin");
MODULE_FIRMWARE("libertas_cs_helper.fw");
MODULE_FIRMWARE("libertas_cs.fw");
Hope that helps.
-
Thanks daal!
Sounds like I will have to re-install to ext3 then as I just tried mounting the drive as ext3 instead but now it says it can't mount due to "unsupported optional features".
The libertas firmware is named differently (and has a slightly different filesize) under 2.6 vs 4.x.
There are a couple of things wrong or missing from OmegaMoon's guide which I'll ask him to correct once I've got Debian booting but before I return to Debian I want to try out daal's hacked SDL!
-
Why did you decide to build your own 2.6 kernel? I might be interested in trying to re-build it for the same reasons but wth Libertas support and, if you didn't enable it already, ext4 support which was marked stable in 2.6.28.
Which release of Debian are you running? Also, if you could answer my Qs from a few posts back (#324) daal that'd be great!
Cheers!
EDIT
I just noticed you've updated the OP re ACPI - good stuff!
-
Did you see my post about the C1000? I presume your kernel should work for C1000 users too right?
It may work. Just need someone to test it ?
-
Why did you decide to build your own 2.6 kernel? I might be interested in trying to re-build it for the same reasons but wth Libertas support and, if you didn't enable it already, ext4 support which was marked stable in 2.6.28.
Which release of Debian are you running? Also, if you could answer my Qs from a few posts back (#324) daal that'd be great!
Cheers!
EDIT
I just noticed you've updated the OP re ACPI - good stuff!
I do not really remember why I build a custom kernel back then.
Probably because of the need of some modules that where not included in the yonggun kernel.
Also there were some udev issues with the younggun kernel 6 years ago : https://www.oesf.org/forum/index.php?s=&...st&p=183225 (https://www.oesf.org/forum/index.php?s=&showtopic=26807&view=findpost&p=183225)
Ext4 was new back then, ext3 was the standard I guess. For testing your WiFi card your file system will not matter.
As mentioned, I do not think I have source and patches for this kernel anymore, it was just to long ago and has suffered from bit-rott.
I am still running Wheezy/Sid and did not do a apt-get update for about 5 years. Not sure the repos are still active, I thought armel debian is dead already.
-
Reading your earlier post again daal you did say you were not sure you had those kernel sources anymore but I interepreted this as you might still have them so at least we've cleared that up.
Of course I realise the fs has no impact on wifi drivers - I'm not that clueless! I was just hoping to juice every last bit of performance out of the old girl.
armel is still supported under Debian, or at least it is under Jessie, the current stable release. It is supposedly possible to run Jessie with sysv but I've got enough support pitfalls to be dealing with without that.
-
Reading your earlier post again daal you did say you were not sure you had those kernel sources anymore but I interepreted this as you might still have them so at least we've cleared that up.
Of course I realise the fs has no impact on wifi drivers - I'm not that clueless! I was just hoping to juice every last bit of performance out of the old girl.
armel is still supported under Debian, or at least it is under Jessie, the current stable release. It is supposedly possible to run Jessie with sysv but I've got enough support pitfalls to be dealing with without that.
Kernel Source for 2.6 series : I do not believe I still have it. I have checked all my Z stuff that has been archived, also not on my Debian partition I did not use github back then.
All the effort to get Debian running to test your WiFi card ?
I will be not much of help there, as I will focus more on Arch as you can understand.
In regards to the card, I would approach developers etc to see what they have to say or check some IRC channels.
It feels to me to be a firmware issue, as the card basically works but then fails to keep the connection ?
I could help to trouble shoot but I do not have this kind of card. I guess it was pretty rare even back in the active days at OESF ?
-
WIFI UPDATE
After god-knows how many hours in total which has recently grown to include trying to install multiple versions of Debian and even Gentoo on my Z, I have finally made some real progress with my libertas wifi card. It essentially works at the expected speed under Andromeda (yonggun Lenny) Debian ( http://yonggun.tistory.com/77 (http://yonggun.tistory.com/77) ) by using the latest yonggun 2.6 kernel and following these instructions ( http://nokamoto.blogspot.co.uk/2008/01/zau...x-gw-cf54g.html (http://nokamoto.blogspot.co.uk/2008/01/zaurus-sl-c3100-with-planex-gw-cf54g.html) ) but not perfectly as it prints the warning (or error?):
libertas: tx watch dog timeout
To the console every 10 to 15s when the wifi card is in use but not when its simply plugged in. That does not break the connection but it's a bit annoying. I'm sure it'd be simple to patch it out as it doesn't seem to be necessary in my experience downloading a Linux ISO with wget over wifi with it.
daal offered to try and get this card working under the ALARMZ kernel after I'd proved to myself its not a hardware fault so I think I'll take you up on that offer please daal! It'd be good for everyone here to know we have at least one (or two if you count the PLANEX card with the same chipset) option for 802.11g without removing the internal drive.
Send me your address in a PM or whatever and I'll get it posted to you ASAP!
Thanks daal!
-
Excellent progress, danboid!....
Would be great to have option for a faster WiFi card.....
Meanwhile, trying to get some apps installed, but there are some issues.....
Will post in a separate thread....
Keep up the great work, guys!
-
Hello all!
First, thank you so much guys for bringing this OS to the Zaurus Cx00 series!
I installed ALARM linux-4.2.3-c3x00 a week ago but I still have troubles setting wifi up. I have a cisco dlink cf adapter that works under cacko, zgrom, angstrom, ubuntu and all OS's I have tried out on my C3000.
Here is the dmesg output when I insert the card:
[ 567.070709] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 567.096931] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 567.400027] orinoco_cs 0.0: Hardware identity 801b:0000:0001:0000
[ 567.409546] orinoco_cs 0.0: Station identity 001f:0002:0001:0008
[ 567.427363] orinoco_cs 0.0: Firmware determined as Intersil 1.8.2
[ 567.436772] orinoco_cs 0.0: Ad-hoc demo mode supported
[ 567.450806] orinoco_cs 0.0: IEEE standard IBSS ad-hoc mode supported
[ 567.476727] orinoco_cs 0.0: WEP supported, 104-bit key
[ 568.034483] eth0: New link status: Connected (0001)
/etc/netctl/linksys
Description='A simple WEP encrypted wireless connection'
Interface=eth0
Connection=wireless
Security=wep
IP=dhcp
ESSID='linksys'
Key=\"0f***dd
I get this error after running 'netctl enable linksys':
Job for netctl@linksys.service failed because the control process exited with error code. See ... for details.
Here are the details from systemctl:
* netctl@linksys.service - Networking for netctl profile linksys
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-10-23 06:18:03 UTC; 1min 17s ago
Docs: man:netctl.profile(5)
Process: 1122 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 1122 (code=exited, status=1/FAILURE)
Oct 23 06:18:02 alarm systemd[1]: Starting Networking for netctl profile linksys...
Oct 23 06:18:03 alarm network[1122]: Starting network profile 'linksys'...
Oct 23 06:18:03 alarm network[1122]: The interface of network profile 'linksys' is already up
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 06:18:03 alarm systemd[1]: Failed to start Networking for netctl profile linksys.
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Unit entered failed state.
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Failed with result 'exit-code'.
I'm running the OS from the internal 4GB compact flash card alongside with zgrom and OE using kexecboot.
Thank you in advance for all help you can give me.
-
Hello all!
First, thank you so much guys for bringing this OS to the Zaurus Cx00 series!
I installed ALARM linux-4.2.3-c3x00 a week ago but I still have troubles setting wifi up. I have a cisco dlink cf adapter that works under cacko, zgrom, angstrom, ubuntu and all OS's I have tried out on my C3000.
Here is the dmesg output when I insert the card:
[ 567.070709] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 567.096931] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 567.400027] orinoco_cs 0.0: Hardware identity 801b:0000:0001:0000
[ 567.409546] orinoco_cs 0.0: Station identity 001f:0002:0001:0008
[ 567.427363] orinoco_cs 0.0: Firmware determined as Intersil 1.8.2
[ 567.436772] orinoco_cs 0.0: Ad-hoc demo mode supported
[ 567.450806] orinoco_cs 0.0: IEEE standard IBSS ad-hoc mode supported
[ 567.476727] orinoco_cs 0.0: WEP supported, 104-bit key
[ 568.034483] eth0: New link status: Connected (0001)
/etc/netctl/linksys
Description='A simple WEP encrypted wireless connection'
Interface=eth0
Connection=wireless
Security=wep
IP=dhcp
ESSID='linksys'
Key=\"0f***dd
I get this error after running 'netctl enable linksys':
Job for netctl@linksys.service failed because the control process exited with error code. See ... for details.
Here are the details from systemctl:
* netctl@linksys.service - Networking for netctl profile linksys
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-10-23 06:18:03 UTC; 1min 17s ago
Docs: man:netctl.profile(5)
Process: 1122 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 1122 (code=exited, status=1/FAILURE)
Oct 23 06:18:02 alarm systemd[1]: Starting Networking for netctl profile linksys...
Oct 23 06:18:03 alarm network[1122]: Starting network profile 'linksys'...
Oct 23 06:18:03 alarm network[1122]: The interface of network profile 'linksys' is already up
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 06:18:03 alarm systemd[1]: Failed to start Networking for netctl profile linksys.
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Unit entered failed state.
Oct 23 06:18:03 alarm systemd[1]: netctl@linksys.service: Failed with result 'exit-code'.
I'm running the OS from the internal 4GB compact flash card alongside with zgrom and OE using kexecboot.
Thank you in advance for all help you can give me.
Hi dmarschal,
thanks for your feedback and good to know that you are running ALARM on your Zaurus !
In regards to your WiFi issues, it would be helpful to have more details about the card you are using.
Just for a test, can you please try with the 3.11.3 kernel, too ? This would help to narrow down if it is 4.x a kernel issue or not.
Also please let us know what exact CF card you have, model and version.
Your card may require a specific firmware ?
[ 567.427363] orinoco_cs 0.0: Firmware determined as Intersil 1.8.2
Is this correct ? What does a dmesg say on zgrom etc ?
Troubleshooting WiFi issues is quite hard for me as I do not have the card you own.
Happy to help,
Cheers!
-
daalnroti, thank you.
The card I have is a linksys 'instant wireless' wireless flash card 2.4Ghz 802.11b.
dmesg on zgrom says:
pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
hostap_cs: setting Vcc=33 (constant)
hostap_cs: Registered netdevice wifi0
prism2_hw_init: initialized in 200 ms
wifi0: NIC: id=0x801b v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.2
wifi0: registered netdevice wlan0
I'm testing the 3.11.3 kernel...
-
I got the same error message under 3.11.3. kernel. )-:
What cards reported to work?
-
Welcome to the club, dmarschal!
My AmbiCom WL1100C-CF works.....
-
daalnroti, thank you.
The card I have is a linksys 'instant wireless' wireless flash card 2.4Ghz 802.11b.
dmesg on zgrom says:
pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 201)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
hostap_cs: setting Vcc=33 (constant)
hostap_cs: Registered netdevice wifi0
prism2_hw_init: initialized in 200 ms
wifi0: NIC: id=0x801b v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.2
wifi0: registered netdevice wlan0
I'm testing the 3.11.3 kernel...
You may need to blacklist the module "orinoco_cs" (https://wiki.archlinux.org/index.php/Kernel_modules)
It seems the 4.2.3 loads the orinoco modules instead of hostap and prism.
-
it worked. thank you daalnroti!
netctl did't work. i installed wireless-tools and configured the connection from the command line using ifconfig and iwconfig. now i'm updating the os. (-:
thank you!!!
edit: daalnroti, how hard is it to compile kernels for the SL-C860/760 series?
-
edit: daalnroti, how hard is it to compile kernels for the SL-C860/760 series?
Probably not too hard, but I do not have any of these and focus only on C3x00 series, although C1000 should work too.
-
Sudip Mukherjee sudipm.mukherjee@gmail.com via lists.infradead.org
12:32 PM (2 hours ago)
to Kalle, netdev, linux-wireless, linux-kernel, libertas-dev
We were dereferencing cmd first and checking for NULL later. Lets first
check for NULL.
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
---
drivers/net/wireless/marvell/libertas/cfg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/libertas/cfg.c b/drivers/net/wireless/marvell/libertas/cfg.c
index 8317afd..e38ad1d 100644
--- a/drivers/net/wireless/marvell/libertas/cfg.c
+++ b/drivers/net/wireless/marvell/libertas/cfg.c
@@ -1108,7 +1108,7 @@ static int lbs_associate(struct lbs_private *priv,
size_t len, resp_ie_len;
int status;
int ret;
- u8 *pos = &(cmd->iebuf[0]);
+ u8 *pos;
u8 *tmp;
lbs_deb_enter(LBS_DEB_CFG80211);
@@ -1117,6 +1117,7 @@ static int lbs_associate(struct lbs_private *priv,
ret = -ENOMEM;
goto done;
}
+ pos = &cmd->iebuf[0];
/*
* cmd 50 00
-
Hmmm.....pretty quiet here lately.....
everyone busy with other things or just nothing to report?
Meanwhile, a question please....
Have a feeling that this was address somewhere among the past 20+ pages....
but would appreciate knowing if there's a way to disable the amber indicator light.
Having it flicker all the time, especially when I leave the Z on, but unattended, seems a waste of use of it.....
Thanks.
-
Hi all,
many thanks for porting Arch Linux, I'll try it on my Z as soon as I have some free time. Has anybody tried it on a C1000?
Varthall
-
Hi all,
many thanks for porting Arch Linux, I'll try it on my Z as soon as I have some free time. Has anybody tried it on a C1000?
Varthall
Don't think so......
Think you will be the first.....
Think daalnroti has said in some posts that he thinks it should work OK.....
-
Hmmm.....pretty quiet here lately.....
everyone busy with other things or just nothing to report?
Meanwhile, a question please....
Have a feeling that this was address somewhere among the past 20+ pages....
but would appreciate knowing if there's a way to disable the amber indicator light.
Having it flicker all the time, especially when I leave the Z on, but unattended, seems a waste of use of it.....
Thanks.
Hi ArchiMark,
the orange LED indicates the CPU heartbeat. Slow blinking means idle, faster blinking busy CPU.
This is patched at kernel level since the charging LED indicator is broken.
Cheers
-
Sudip Mukherjee sudipm.mukherjee@gmail.com via lists.infradead.org
12:32 PM (2 hours ago)
to Kalle, netdev, linux-wireless, linux-kernel, libertas-dev
We were dereferencing cmd first and checking for NULL later. Lets first
check for NULL.
Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
---
drivers/net/wireless/marvell/libertas/cfg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/libertas/cfg.c b/drivers/net/wireless/marvell/libertas/cfg.c
index 8317afd..e38ad1d 100644
--- a/drivers/net/wireless/marvell/libertas/cfg.c
+++ b/drivers/net/wireless/marvell/libertas/cfg.c
@@ -1108,7 +1108,7 @@ static int lbs_associate(struct lbs_private *priv,
size_t len, resp_ie_len;
int status;
int ret;
- u8 *pos = &(cmd->iebuf[0]);
+ u8 *pos;
u8 *tmp;
lbs_deb_enter(LBS_DEB_CFG80211);
@@ -1117,6 +1117,7 @@ static int lbs_associate(struct lbs_private *priv,
ret = -ENOMEM;
goto done;
}
+ pos = &cmd->iebuf[0];
/*
* cmd 50 00
Hi danbiod,
I must have missed this post. What is this about ? You want me to patch ?
Cheers!
-
Hi all,
many thanks for porting Arch Linux, I'll try it on my Z as soon as I have some free time. Has anybody tried it on a C1000?
Varthall
Hi Varti,
The C1000 "should" work, but please give it a go and report back if you succeed or face any issues.
Cheers!
-
It's really good to see a distro being updated for the Zaurus. I just read this long thread for 3 hours.
Is ArchLinux really much different than Debian and its offshoots?
I have one main question before I try ArchLinux. I'll boot it from an SD card like I did with Zubuntu.
I already have kexec installed and have used it with Zubuntu.
Do I really need to install the recommended kexec mentioned here, or can I boot ArchLinux with my current kexec version?
The reason I'm asking this is because I modified my SL-C3100 to dual booting Angstrom + Cacko.
I don't use Angstrom anymore, but I still need its kexec-tools, (or maybe I'm using kexec from Zubuntu, not quite sure at the moment).
My main concern is that I want to continue to use Cacko, and Cacko is installed in an unusual manner.
A cold boot boots Angstrom then I use kexec within Angstrom to boot Cacko.
BTW, I have an Ambicom WL1100C-CF Wifi card like ArchiMark. This card works in all Zaurus distros.
I also have a Socket 10/100 Rugged CF Ethernet card, but the Rugged designation makes it different and it has never worked in any Zaurus distro.
It was an expensive card and would like to see it work.
I also have a Belkin USB to Ethernet device, but I think it uses too much power for newer kernels. It works in Cacko and pdaxii13
I also have a Linksys USB200M USB to Ethernet adapter that has not worked in any Zaurus distro either.
Thank you for reading this. I really want to try ArchLinux on my C3100, but will have to wait till tomorrow. (It is 4 AM here)
Jon
-
It's really good to see a distro being updated for the Zaurus. I just read this long thread for 3 hours.
Is ArchLinux really much different than Debian and its offshoots?
Hey Jon, good to see you here.......
Others may chime in with other points, but to me, the main difference with Arch is that it is a 'rolling release' that means it is constantly updated....but up to you whether install the updates. While Debian and offshoots use a periodic release approach.
I have one main question before I try ArchLinux. I'll boot it from an SD card like I did with Zubuntu.
I already have kexec installed and have used it with Zubuntu.
Do I really need to install the recommended kexec mentioned here, or can I boot ArchLinux with my current kexec version?
daalnroti or danboid can chime in, but I think you need the one mentioned here, but I could be wrong.....
The reason I'm asking this is because I modified my SL-C3100 to dual booting Angstrom + Cacko.
I don't use Angstrom anymore, but I still need its kexec-tools, (or maybe I'm using kexec from Zubuntu, not quite sure at the moment).
My main concern is that I want to continue to use Cacko, and Cacko is installed in an unusual manner.
A cold boot boots Angstrom then I use kexec within Angstrom to boot Cacko.
BTW, I have an Ambicom WL1100C-CF Wifi card like ArchiMark. This card works in all Zaurus distros.
Yep, this card has never let me down....
I also have a Socket 10/100 Rugged CF Ethernet card, but the Rugged designation makes it different and it has never worked in any Zaurus distro.
It was an expensive card and would like to see it work.
Yeah, I have non-Rugged version and it always works with everything I've tried on Zaurus....
I also have a Belkin USB to Ethernet device, but I think it uses too much power for newer kernels. It works in Cacko and pdaxii13
I also have a Linksys USB200M USB to Ethernet adapter that has not worked in any Zaurus distro either.
Thank you for reading this. I really want to try ArchLinux on my C3100, but will have to wait till tomorrow. (It is 4 AM here)
Jon
Give ALARMZ a try and let us know how it goes or if you have questions.....
Mark
-
It's really good to see a distro being updated for the Zaurus. I just read this long thread for 3 hours.
Is ArchLinux really much different than Debian and its offshoots?
I have one main question before I try ArchLinux. I'll boot it from an SD card like I did with Zubuntu.
I already have kexec installed and have used it with Zubuntu.
Do I really need to install the recommended kexec mentioned here, or can I boot ArchLinux with my current kexec version?
The reason I'm asking this is because I modified my SL-C3100 to dual booting Angstrom + Cacko.
I don't use Angstrom anymore, but I still need its kexec-tools, (or maybe I'm using kexec from Zubuntu, not quite sure at the moment).
My main concern is that I want to continue to use Cacko, and Cacko is installed in an unusual manner.
A cold boot boots Angstrom then I use kexec within Angstrom to boot Cacko.
BTW, I have an Ambicom WL1100C-CF Wifi card like ArchiMark. This card works in all Zaurus distros.
I also have a Socket 10/100 Rugged CF Ethernet card, but the Rugged designation makes it different and it has never worked in any Zaurus distro.
It was an expensive card and would like to see it work.
I also have a Belkin USB to Ethernet device, but I think it uses too much power for newer kernels. It works in Cacko and pdaxii13
I also have a Linksys USB200M USB to Ethernet adapter that has not worked in any Zaurus distro either.
Thank you for reading this. I really want to try ArchLinux on my C3100, but will have to wait till tomorrow. (It is 4 AM here)
Jon
Hi Jon_J!
ALARM vs Debian : most have the impression that ALARM is faster, pacman is way faster than apt-get, but I guess you check for yourself.
KEXECBOOT : there is no real need to update your kexecboot, one thing to keep in mind is that the boot.cfg syntax has changed a bit between kexeboot releases. You may need to adopt the boot.cfg from ALARM to fit to your kexecboot version.
WiFi / Ethernet USB Cards : best to boot Debian or Arch and provide more info (lsusb or lspcmcia). If the driver is not included in the current kernel but does exists, I can recompile and add the modules needed.Full model number, product code etc would help too. Keep in mind I can add a kernel module but not troubleshoot or test as I do not have this kind of hardware.
Cheers!
-
It's really good to see a distro being updated for the Zaurus. I just read this long thread for 3 hours.
Is ArchLinux really much different than Debian and its offshoots?
I have one main question before I try ArchLinux. I'll boot it from an SD card like I did with Zubuntu.
I already have kexec installed and have used it with Zubuntu.
Do I really need to install the recommended kexec mentioned here, or can I boot ArchLinux with my current kexec version?
The reason I'm asking this is because I modified my SL-C3100 to dual booting Angstrom + Cacko.
I don't use Angstrom anymore, but I still need its kexec-tools, (or maybe I'm using kexec from Zubuntu, not quite sure at the moment).
My main concern is that I want to continue to use Cacko, and Cacko is installed in an unusual manner.
A cold boot boots Angstrom then I use kexec within Angstrom to boot Cacko.
BTW, I have an Ambicom WL1100C-CF Wifi card like ArchiMark. This card works in all Zaurus distros.
I also have a Socket 10/100 Rugged CF Ethernet card, but the Rugged designation makes it different and it has never worked in any Zaurus distro.
It was an expensive card and would like to see it work.
I also have a Belkin USB to Ethernet device, but I think it uses too much power for newer kernels. It works in Cacko and pdaxii13
I also have a Linksys USB200M USB to Ethernet adapter that has not worked in any Zaurus distro either.
Thank you for reading this. I really want to try ArchLinux on my C3100, but will have to wait till tomorrow. (It is 4 AM here)
Jon
Socket Rugged 10/100 : from the user manual "Note: The Rugged CF 10/100 Card is NOT NE2000 compliant" but the card uses the AX88790 chip.
this card may be supported, but better you try by booting the latest kernel 4.2.3 into alarm and check !
The Belkin and Linksys also use ASIX chipsets and may be supported. I have a AX88772 based USB to Ethernet that does work without powered USB hub.
Other chips need more power and may not work without a powered hub. Also, you will need to test.
Cheers!
-
I don't have Arch linux ARM running yet. Here's what I tried.
I first installed Arch kexec and unpacked "linux-4.2.3-c3x00-v0.3.tar.xz" to a SD card.
I used the instructions under post #117 because when I tried Danboid's instructions,
the above archive unpacked onto the hard drive on my desktop PC instead of SD card.
Following the instructions at post #117, I got stumped when I was told to copy files to /boot
Also some further instructions mentioned copying files to /lib/modules.
My problem is that I only have one directory on my SD card called "4.2.3-c3x00"
No other directories exist, and I am not sure if I should go about creating these directories. Or I have downloaded the wrong archive.
I think I had it partially running when I booted the SD card using Arch kexec.
I didn't write down the error messages, but I was getting 1 or 2 kernel panics, and it stopped booting.
Arch kexec wouldn't allow me to boot any other SD cards, (I tried Cacko on an SD card).
So I reflashed my Z with cortez's kexec which was released with zubuntu, and it allowed me to boot Cacko once again.
I also tried formatting to ext3 my SD card that I was using for Arch linux ARM because cortez's kexec would not recognize ext4.
Arch linux ARM is not visible on that SD card booting with cortez's kexec.
That is where I am at right now.
Next I'm going to try to unpack "linux-3.11.3-borzoi" to a SD card and try that with cortez's kexec.
OK, now some information on my 3 Ethernet cards:
On my laptop running MX14 (Debian kernel 3.14)
====================
lsusb
Linksys USB200M 10/100 Ethernet Adapter
Device 006 ID 13b1:0018
driver, Asix
====================
lsusb
Belkin Components F5D5050 100Mbps Ethernet
Device 002 ID 050d:0121
driver not listed.
====================
Both the above USB to Ethernet adapters worked on my laptop, which is a Dell mini1010 netbook with an Atom processor.
I was unable to use "lspcmcia" with my Socket CF ethernet adapter. I tried in pdaxii13 and Cacko, but the command is not available.
Below is a whole lot of information that I have gathered over the last 8 years on the Socket Rugged CF 10/100 Ethernet Card
cardctl ident
Socket 0:
product info: "Socket", "CF 10/100 Ethernet Card", "Revision B", "05/11/06"
manfid: 0x0104, 0x02d2
function: 6 (network)
----------------------------
cardctl info
PRODID_1="Socket"
PRODID_2="CF 10/100 Ethernet Card"
PRODID_3="Revision B"
PRODID_4="05/11/06"
MANFID=0104,02d2
FUNCID=6
----------------------------
dmesg output for Socket card:
eth0: NE2000 Compatible: io 0xf6000300, irq 135, auto xcvr, hw_addr 00:C0:1B:07:D5:3A
----------------------------
The Rugged CF 10/100 card utilizes the Asix AX88790 L 10/100BASE 3-in-1 PCMCIA Fast Ethernet Controller.
----------------------------
From ethernet vender codes page: http://www.cavebear.com/archive/cavebear/Ethernet/vendor.html
00C01B Socket CommunicationsI pasted "AX88790 L phy workaround..txt" to this post, but it takes too much space, I attached it as a *.zip file instead.
I do not understand it, but it pertains to someone trying to get a driver working for the Socket Rugged CF Ethernet card.
I would prefer to use the CF Ethernet card because it must have better thoroughput than the USB devices because the Zaurus USB is only version 1.1
-
I now have ArchlinuxARM started, but still am getting kernel panic.
Kernel panic - not syncing: No init found. Try passing init= option to kernelThe display is in portrait mode.
I'm using the kexec from zubuntu. I renamed "boot.cfg" to "kernel-cmdline" and renamed "zImage-3.11.3-c3x00" to just "zImage"
Renaming to "zImage" allowed this version of kexec to display the SD card selection on the boot screen which enabled me to select it.
I still have no "proper" linux directory structure. I created the directories mentioned in post #117
Is there another download that I need? Such as "Spitz-root-addition" as required in zubuntu, this creates the directory structure.
I also forgot to mention, I formatted my SD card to ext3 filesystem since I didn't think this older kexec would recognize ext4.
Thank you,
Jon
-
I just reflashed my C3100 with arch-kexecboot and have Cacko working.
I used the contents of kernel-cmdline that works on my other SD card, and placed it boot.cfg as a second entry.
I used an "example boot.config" found in this thread to determine how to do this.
When I select ArchLinuxARM from the boot menu, I'm still gettingKernel panic - not syncing: No init found. Try passing init= option to kernel.It does, however display in landscape mode like it should. I just don't know how to pass an init= option to the kernel.
Edit
I finally got ArchLinuxARM to boot completely, and logged in! I also have Cacko booting from the menu.
I thought I was missing the file structure, and just stumbled upon this important archive. "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz"
I had previously tried "linux-4.2.3-c3x00-v0.3.tar.xz" and "linux-3.11.3-c3x00.tar.xz", but these archives are missing the filesystem.
Each of the above 2 archives are about 5.5MB and unpacked in 2-3 seconds.
Unpacking "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz" took at least 10 minutes, and it is 129MB.
I think it should be posted clearly somewhere that one needs the archive with "rootfs" in the filename.
This leads to another question. Do I need either of these 2 archives? "linux-4.2.3-c3x00-v0.3.tar.xz" or "linux-3.11.3-c3x00.tar.xz"
Thank you
Jon
-
I just reflashed my C3100 with arch-kexecboot and have Cacko working.
I used the contents of kernel-cmdline that works on my other SD card, and placed it boot.cfg as a second entry.
I used an "example boot.config" found in this thread to determine how to do this.
When I select ArchLinuxARM from the boot menu, I'm still gettingKernel panic - not syncing: No init found. Try passing init= option to kernel.It does, however display in landscape mode like it should. I just don't know how to pass an init= option to the kernel.
Edit
I finally got ArchLinuxARM to boot completely, and logged in! I also have Cacko booting from the menu.
I thought I was missing the file structure, and just stumbled upon this important archive. "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz"
I had previously tried "linux-4.2.3-c3x00-v0.3.tar.xz" and "linux-3.11.3-c3x00.tar.xz", but these archives are missing the filesystem.
Each of the above 2 archives are about 5.5MB and unpacked in 2-3 seconds.
Unpacking "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz" took at least 10 minutes, and it is 129MB.
I think it should be posted clearly somewhere that one needs the archive with "rootfs" in the filename.
This leads to another question. Do I need either of these 2 archives? "linux-4.2.3-c3x00-v0.3.tar.xz" or "linux-3.11.3-c3x00.tar.xz"
Thank you
Jon
Hi Jon,
the minimal rootfs includes already kernel linux-4.2.3-c3x00. So you will not need the other archives.
I thought https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install) covers the install process pretty much in detail.
Let us know what steps were not clear and I am sure danboid or me can modify the instructions.
Cheers!
-
Hi Jon,
the minimal rootfs includes already kernel linux-4.2.3-c3x00. So you will not need the other archives.
I thought https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install) covers the install process pretty much in detail.
Let us know what steps were not clear and I am sure danboid or me can modify the instructions.
Cheers!
I think my problem was I started with the instructions in post 117. Installing to SD card. The archive linked in that post doesn't have the full directory structure. "ArchLinuxARM-armv5-latest.tar.gz"
I got confused and started looking around and then found the other 2 archives mentioned above, which I now realize only contain kernels and modules.
It was awhile later that I found "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz" with the complete filesystem, then everything worked as expected.
Thanks for putting up with me, I get things confused sometimes.
Thank you,
Jon
-
Hi Jon,
the minimal rootfs includes already kernel linux-4.2.3-c3x00. So you will not need the other archives.
I thought https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install) covers the install process pretty much in detail.
Let us know what steps were not clear and I am sure danboid or me can modify the instructions.
Cheers!
I think my problem was I started with the instructions in post 117. Installing to SD card. The archive linked in that post doesn't have the full directory structure. "ArchLinuxARM-armv5-latest.tar.gz"
I got confused and started looking around and then found the other 2 archives mentioned above, which I now realize only contain kernels and modules.
It was awhile later that I found "alarm-zaurus-c3x00-minimal-rootfs-october2015.tar.xz" with the complete filesystem, then everything worked as expected.
Thank you,
Jon
No worries,
good to have another user here. Welcome!
Are your CF/USB network devices recognized correctly under ALARM ?
Cheers!
-
Hi daalnroti,
My 2 USB to ethernet adapters both work in ArchLinuxARM
====================
Linksys USB200M 10/100 Ethernet Adapter
Device 006 ID 13b1:0018
driver, Asix
Needs a powered hub, I tried with and without powered hub.
====================
Belkin Components F5D5050 100Mbps Ethernet
Device 002 ID 050d:0121
driver (dmesg shows driver is Pegasus)
This one works fine without a powered hub. It just lit up as soon as I logged in.
====================
I haven't got my Socket Rugged 10/100 card working yet. It seems to be using pcnet_cs and spits out a lot of errors in dmesg.
In dmesg it says it is NE2000 compliant, but we know it is not. I 'll try to copy the dmesg errors to a file and post them here.[ 61.099123] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 61.102534] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 61.530586] pcnet_cs 0.0 eth0: NE2000 Compatible:
[ 61.530650] io 0xc4860300, irq 217, auto xcvr, hw_addr 00:c0:1b:07:d5:3a
[ 61.920598] NET: Registered protocol family 17
[ 62.249062] ------------[ cut here ]------------
[ 62.249182] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x200/0x28c()
[ 62.249204] NETDEV WATCHDOG: eth0 (pcnet_cs): transmit queue 0 timed out
[ 62.249219] Modules linked in: af_packet pcnet_cs 8390 ads7846 pxaficp_ir sch_fq_codel ip_tables x_tables ipv6 autofs4
[ 62.249346] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.3-c3x00 #1
[ 62.249362] Hardware name: SHARP Borzoi
[ 62.249460] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 62.249513] [] (show_stack) from [] (warn_slowpath_common+0x84/0xac)
[ 62.249551] [] (warn_slowpath_common) from [] (warn_slowpath_fmt+0x2c/0x3c)
[ 62.249589] [] (warn_slowpath_fmt) from [] (dev_watchdog+0x200/0x28c)
[ 62.249644] [] (dev_watchdog) from [] (call_timer_fn.isra.33+0x20/0x94)
[ 62.249683] [] (call_timer_fn.isra.33) from [] (run_timer_softirq+0x1e4/0x264)
[ 62.249725] [] (run_timer_softirq) from [] (__do_softirq+0xdc/0x214)
[ 62.249762] [] (__do_softirq) from [] (irq_exit+0x84/0xec)
[ 62.249799] [] (irq_exit) from [] (__handle_domain_irq+0x98/0xcc)
[ 62.249835] [] (__handle_domain_irq) from [] (ichp_handle_irq+0x28/0x30)
[ 62.249872] [] (ichp_handle_irq) from [] (__irq_svc+0x40/0x6c)
[ 62.249894] Exception stack(0xc0597f68 to 0xc0597fb0)
[ 62.249928] 7f60: 00000001 60000093 c05a4048 60000013 c0596000 c0598090
[ 62.249965] 7f80: c05a3774 c0598020 c058341c c3ffcac0 a05821c4 00000000 00000000 c0597fb0
[ 62.249991] 7fa0: c000aa8c c000aa98 60000013 ffffffff
[ 62.250028] [] (__irq_svc) from [] (arch_cpu_idle+0x2c/0x34)
[ 62.250079] [] (arch_cpu_idle) from [] (cpu_startup_entry+0xec/0x154)
[ 62.250156] [] (cpu_startup_entry) from [] (start_kernel+0x2f0/0x350)
[ 62.250178] ---[ end trace 757a62bf32918edd ]---
Jon
-
Hi daalnroti,
My 2 USB to ethernet adapters both work in ArchLinuxARM
====================
Linksys USB200M 10/100 Ethernet Adapter
Device 006 ID 13b1:0018
driver, Asix
Needs a powered hub, I tried with and without powered hub.
====================
Belkin Components F5D5050 100Mbps Ethernet
Device 002 ID 050d:0121
driver (dmesg shows driver is Pegasus)
This one works fine without a powered hub. It just lit up as soon as I logged in.
====================
I haven't got my Socket Rugged 10/100 card working yet. It seems to be using pcnet_cs and spits out a lot of errors in dmesg.
In dmesg it says it is NE2000 compliant, but we know it is not. I 'll try to copy the dmesg errors to a file and post them here.[ 61.099123] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 61.102534] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 61.530586] pcnet_cs 0.0 eth0: NE2000 Compatible:
[ 61.530650] io 0xc4860300, irq 217, auto xcvr, hw_addr 00:c0:1b:07:d5:3a
[ 61.920598] NET: Registered protocol family 17
[ 62.249062] ------------[ cut here ]------------
[ 62.249182] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x200/0x28c()
[ 62.249204] NETDEV WATCHDOG: eth0 (pcnet_cs): transmit queue 0 timed out
[ 62.249219] Modules linked in: af_packet pcnet_cs 8390 ads7846 pxaficp_ir sch_fq_codel ip_tables x_tables ipv6 autofs4
[ 62.249346] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.3-c3x00 #1
[ 62.249362] Hardware name: SHARP Borzoi
[ 62.249460] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 62.249513] [] (show_stack) from [] (warn_slowpath_common+0x84/0xac)
[ 62.249551] [] (warn_slowpath_common) from [] (warn_slowpath_fmt+0x2c/0x3c)
[ 62.249589] [] (warn_slowpath_fmt) from [] (dev_watchdog+0x200/0x28c)
[ 62.249644] [] (dev_watchdog) from [] (call_timer_fn.isra.33+0x20/0x94)
[ 62.249683] [] (call_timer_fn.isra.33) from [] (run_timer_softirq+0x1e4/0x264)
[ 62.249725] [] (run_timer_softirq) from [] (__do_softirq+0xdc/0x214)
[ 62.249762] [] (__do_softirq) from [] (irq_exit+0x84/0xec)
[ 62.249799] [] (irq_exit) from [] (__handle_domain_irq+0x98/0xcc)
[ 62.249835] [] (__handle_domain_irq) from [] (ichp_handle_irq+0x28/0x30)
[ 62.249872] [] (ichp_handle_irq) from [] (__irq_svc+0x40/0x6c)
[ 62.249894] Exception stack(0xc0597f68 to 0xc0597fb0)
[ 62.249928] 7f60: 00000001 60000093 c05a4048 60000013 c0596000 c0598090
[ 62.249965] 7f80: c05a3774 c0598020 c058341c c3ffcac0 a05821c4 00000000 00000000 c0597fb0
[ 62.249991] 7fa0: c000aa8c c000aa98 60000013 ffffffff
[ 62.250028] [] (__irq_svc) from [] (arch_cpu_idle+0x2c/0x34)
[ 62.250079] [] (arch_cpu_idle) from [] (cpu_startup_entry+0xec/0x154)
[ 62.250156] [] (cpu_startup_entry) from [] (start_kernel+0x2f0/0x350)
[ 62.250178] ---[ end trace 757a62bf32918edd ]---
Jon
Hi Jon,
good news!
In regards to the Rugged one, try to blacklist the pcnet_cs module and do a reboot. This way it might pick up the right driver.
https://wiki.archlinux.org/index.php/Kernel...es#Blacklisting (https://wiki.archlinux.org/index.php/Kernel_modules#Blacklisting)
Cheers!
-
Hi daalnroti,
My 2 USB to ethernet adapters both work in ArchLinuxARM
====================
Linksys USB200M 10/100 Ethernet Adapter
Device 006 ID 13b1:0018
driver, Asix
Needs a powered hub, I tried with and without powered hub.
====================
Belkin Components F5D5050 100Mbps Ethernet
Device 002 ID 050d:0121
driver (dmesg shows driver is Pegasus)
This one works fine without a powered hub. It just lit up as soon as I logged in.
====================
I haven't got my Socket Rugged 10/100 card working yet. It seems to be using pcnet_cs and spits out a lot of errors in dmesg.
In dmesg it says it is NE2000 compliant, but we know it is not. I 'll try to copy the dmesg errors to a file and post them here.[ 61.099123] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 61.102534] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
[ 61.530586] pcnet_cs 0.0 eth0: NE2000 Compatible:
[ 61.530650] io 0xc4860300, irq 217, auto xcvr, hw_addr 00:c0:1b:07:d5:3a
[ 61.920598] NET: Registered protocol family 17
[ 62.249062] ------------[ cut here ]------------
[ 62.249182] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x200/0x28c()
[ 62.249204] NETDEV WATCHDOG: eth0 (pcnet_cs): transmit queue 0 timed out
[ 62.249219] Modules linked in: af_packet pcnet_cs 8390 ads7846 pxaficp_ir sch_fq_codel ip_tables x_tables ipv6 autofs4
[ 62.249346] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.3-c3x00 #1
[ 62.249362] Hardware name: SHARP Borzoi
[ 62.249460] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 62.249513] [] (show_stack) from [] (warn_slowpath_common+0x84/0xac)
[ 62.249551] [] (warn_slowpath_common) from [] (warn_slowpath_fmt+0x2c/0x3c)
[ 62.249589] [] (warn_slowpath_fmt) from [] (dev_watchdog+0x200/0x28c)
[ 62.249644] [] (dev_watchdog) from [] (call_timer_fn.isra.33+0x20/0x94)
[ 62.249683] [] (call_timer_fn.isra.33) from [] (run_timer_softirq+0x1e4/0x264)
[ 62.249725] [] (run_timer_softirq) from [] (__do_softirq+0xdc/0x214)
[ 62.249762] [] (__do_softirq) from [] (irq_exit+0x84/0xec)
[ 62.249799] [] (irq_exit) from [] (__handle_domain_irq+0x98/0xcc)
[ 62.249835] [] (__handle_domain_irq) from [] (ichp_handle_irq+0x28/0x30)
[ 62.249872] [] (ichp_handle_irq) from [] (__irq_svc+0x40/0x6c)
[ 62.249894] Exception stack(0xc0597f68 to 0xc0597fb0)
[ 62.249928] 7f60: 00000001 60000093 c05a4048 60000013 c0596000 c0598090
[ 62.249965] 7f80: c05a3774 c0598020 c058341c c3ffcac0 a05821c4 00000000 00000000 c0597fb0
[ 62.249991] 7fa0: c000aa8c c000aa98 60000013 ffffffff
[ 62.250028] [] (__irq_svc) from [] (arch_cpu_idle+0x2c/0x34)
[ 62.250079] [] (arch_cpu_idle) from [] (cpu_startup_entry+0xec/0x154)
[ 62.250156] [] (cpu_startup_entry) from [] (start_kernel+0x2f0/0x350)
[ 62.250178] ---[ end trace 757a62bf32918edd ]---
Jon
Hi Jon,
good news!
In regards to the Rugged one, try to blacklist the pcnet_cs module and do a reboot. This way it might pick up the right driver.
https://wiki.archlinux.org/index.php/Kernel...es#Blacklisting (https://wiki.archlinux.org/index.php/Kernel_modules#Blacklisting)
Cheers!
I blacklisted pcnet_cs and it appears no modules are loaded when inserting the Socket Rugged 10/100 card.
only 2 lines in dmesgpcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot0
pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
lsmod
module Size Used by
ads7046...........8594 0
pxaficp_ir.........8038 0
sch_fq_codel......7637 1
ip_tables..........9163 0
x_tables..........11037 1 ip_tables
ipv6..............267238 16
autofs4............23501 2Here is a photo of the Socket Rugged 10/100 CF card if anyone is interested in seeing that is different than the other Socket card with similar name.
1rst pic is Socket Rugged 10/100 CF card.
2nd pic is Socket 10/100 CF card (no "Rugged" in the name).
-
Hi Jon,
it seems the required module would be axnet_cs. This was not included in the 4.2.3-c3x00-v0.3 release.
You can try the 4.2.3-c3x00-v0.4 release : https://github.com/greguu/linux-4.2.3-c3x00...leases/tag/v0.4 (https://github.com/greguu/linux-4.2.3-c3x00/releases/tag/v0.4)
I have added the following options :
[*] National Semi-conductor 8390 devices
Asix AX88190 PCMCIA support
ASIX AX88796 NE2000 clone support
[*] ASIX AX88796 external 93CX6 eeprom support
NE2000 compatible PCMCIA support
Try also with keeping the pcnet_cs blacklisted.
Cheers!
-
Hi Jon,
it seems the required module would be axnet_cs. This was not included in the 4.2.3-c3x00-v0.3 release.
You can try the 4.2.3-c3x00-v0.4 release : https://github.com/greguu/linux-4.2.3-c3x00...leases/tag/v0.4 (https://github.com/greguu/linux-4.2.3-c3x00/releases/tag/v0.4)
I have added the following options :
[*] National Semi-conductor 8390 devices
Asix AX88190 PCMCIA support
ASIX AX88796 NE2000 clone support
[*] ASIX AX88796 external 93CX6 eeprom support
NE2000 compatible PCMCIA support
Try also with keeping the pcnet_cs blacklisted.
Cheers!
Thank you including this module.
I don't have it working yet.
This is what I tried. I updated my SD card with ArchlinuxARM with the above archive and copied the 4.2.3-c3x00 directory
to /lib/modules/ and the updated zImage-4.2.3-c3x00 to /boot. I double checked the /lib/modules dir and made sure the new files were copied over.
I then booted my Zaurus into Arch with my Socket card inserted. There was no connection, I pinged google with no results.
I made sure that pcnet_cs was still blacklisted. I checked dmesg and got the same results as in my last post.
Then I used "lsmod" and "axnet_cs" was not listed.
I then used "modprobe axnet_cs" and it loaded but under lsmod, it is not being used by anything.
I then unplugged my Socket ethernet card and plugged it back in, "axnet_cs" is still loaded.
I then tried "ifconfig eth0 up" eth0 not found
I used ifconfig -a and I get 3 entries
lo
irda
lo
BTW, after unplugging the ethernet card and plugging it back in, and issuing modprobe axnet_cs again and ifconfig, my dmesg output remains the same.
pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot0
pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
lsmodmodule Size Used by
axnet_cs.........12090 0
ads7046...........8594 0
pxaficp_ir.........8038 0
sch_fq_codel......7637 1
ip_tables..........9163 0
x_tables..........11037 1 ip_tables
ipv6..............267238 16
autofs4............23501 2
Thank you,
Jon
-
Hi Jon,
it seems the required module would be axnet_cs. This was not included in the 4.2.3-c3x00-v0.3 release.
You can try the 4.2.3-c3x00-v0.4 release : https://github.com/greguu/linux-4.2.3-c3x00...leases/tag/v0.4 (https://github.com/greguu/linux-4.2.3-c3x00/releases/tag/v0.4)
I have added the following options :
[*] National Semi-conductor 8390 devices
Asix AX88190 PCMCIA support
ASIX AX88796 NE2000 clone support
[*] ASIX AX88796 external 93CX6 eeprom support
NE2000 compatible PCMCIA support
Try also with keeping the pcnet_cs blacklisted.
Cheers!
Thank you including this module.
I don't have it working yet.
This is what I tried. I updated my SD card with ArchlinuxARM with the above archive and copied the 4.2.3-c3x00 directory
to /lib/modules/ and the updated zImage-4.2.3-c3x00 to /boot. I double checked the /lib/modules dir and made sure the new files were copied over.
I then booted my Zaurus into Arch with my Socket card inserted. There was no connection, I pinged google with no results.
I made sure that pcnet_cs was still blacklisted. I checked dmesg and got the same results as in my last post.
Then I used "lsmod" and "axnet_cs" was not listed.
I then used "modprobe axnet_cs" and it loaded but under lsmod, it is not being used by anything.
I then unplugged my Socket ethernet card and plugged it back in, "axnet_cs" is still loaded.
I then tried "ifconfig eth0 up" eth0 not found
I used ifconfig -a and I get 3 entries
lo
irda
lo
BTW, after unplugging the ethernet card and plugging it back in, and issuing modprobe axnet_cs again and ifconfig, my dmesg output remains the same.
pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot0
pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 217)
lsmodmodule Size Used by
axnet_cs.........12090 0
ads7046...........8594 0
pxaficp_ir.........8038 0
sch_fq_codel......7637 1
ip_tables..........9163 0
x_tables..........11037 1 ip_tables
ipv6..............267238 16
autofs4............23501 2
Thank you,
Jon
try a "modprobe 8390" before axnet_cs. Also I would it give it a go without the blacklisting, just in case.
-
Hi daalnroti,
I tried modprobe 8390" before axnet_cs. I also removed the blacklisting from pcnet_cs
lsmod showslsmodmodule Size Used by
axnet_cs.........12090 0
pcnet_cs..........25233 0
8390.................6954 1 pcnet_cs
ads7046...........8594 0
pxaficp_ir.........8038 0
sch_fq_codel......7637 1
ip_tables..........9163 0
x_tables..........11037 1 ip_tables
ipv6..............267238 16
autofs4............23501 2I think I may have found the cause for the troubles with this card.
There was a bug in the driver or the chip (ax88790) in this card.
http://www.mail-archive.com/linux-pcmcia@l...g/msg00051.html (http://www.mail-archive.com/linux-pcmcia@lists.infradead.org/msg00051.html)
It looks like I'll need to compile a module for this card, but am not sure where to start.
Thank you,
Jon
-
Hi daalnroti,
I tried modprobe 8390" before axnet_cs. I also removed the blacklisting from pcnet_cs
lsmod showslsmodmodule Size Used by
axnet_cs.........12090 0
pcnet_cs..........25233 0
8390.................6954 1 pcnet_cs
ads7046...........8594 0
pxaficp_ir.........8038 0
sch_fq_codel......7637 1
ip_tables..........9163 0
x_tables..........11037 1 ip_tables
ipv6..............267238 16
autofs4............23501 2I think I may have found the cause for the troubles with this card.
There was a bug in the driver or the chip (ax88790) in this card.
http://www.mail-archive.com/linux-pcmcia@l...g/msg00051.html (http://www.mail-archive.com/linux-pcmcia@lists.infradead.org/msg00051.html)
It looks like I'll need to compile a module for this card, but am not sure where to start.
Thank you,
Jon
Hi Jon,
unfortunately this patch is 9 years old and was made for kernel 2.6.15. It does not work with the kernel in use (4.2.3)
Also looking at the source of linux/drivers/net/ethernet/8390/axnet_cs.c of the current kernel it seems it already has support for the AX88790 chipset.
There are no recent reports of this card working with newer kernels. You may have some luck playing around with the modules I compiled.
Try 8390 and axnet_cs without the pcnet_cs. The module should at least find the card and show something in dmesg. If not, then it is not supported (anymore) I guess.
Cheers.
-
Hi ALARMZers!
I hope you've had a good xmas daal and everyone else reading this!? I did eventually see your messages on IRC, daal, about the new kernels etc! It's good to hear stuff is still happening with ALARMZ! As you all may have guessed I've not been messing with the Z much recently but I did buy a new USB wifi adapter for it on xmas eve that I've still not tried yet. It was only £3 and claimed to support Linux on the box so I figured it was too good not to buy at that price. I expect it won't work without being plugged into a powered hub but even if so it'll still be useful to have. In "computer land" I've mainly been testing the MusE DAW for Linux and the excellent Budgie desktop, which I run under Arch on my laptop now. It's essentially GNOME 3 done properly and much more lightweight! It uses about the same amount of RAM as MATE but with more features like integrated menu search, compositing and better app/desktop preview icons etc and a base that is current with / based upon the latest GNOME 3.
Today was my second day at my new job so that ensures that not only do I now have much less time for messing wth the Z but much less time for (non-work) life in general. At least I won't be sinking into debt any more!
The main reason I decided to post is to notify everyone here that there has recently been some significant work on the Linux libertas wifi driver - a series of 6 patches for the libertas driver has just been posted to the Linux wireless ML. Hopefully these will fix my CF wifi probs under modern kernels. Seeing as 4.4.0 is almost upon us I suspect it may not make it in time for that but hopefully it'll make it into 4.4.1.
Best wishes for 2016!
-
Happy New Year!
Like Danboid my work load has increased significantly so my Z time has dropped, well to zero really. Long story short we are a 4 man department, one position was eliminated, one person retired, and the other besides myself is now on long term medical leave due to back issues.
My next 6 months is pretty well scheduled at this point and I don't see a ton of free time so my participation is going to be slim to none.
I'll keep an eye here and try to do updates when possible.
-
Hi All,
Happy new Year 2016 !
the Z still alive and I will upload shortly a new kernel for testing as well as a new rootfs for SD card.
Hope you find some time to play with it and give some feedback in the corresponding threads.
Cheers!
-
Happy New Year to you all!
Glad to see everyone's still around if not too busy going into 2016.....
Hopefully, we can all have more fun with our little Z's this year. But like others, work and life seems to be getting more in the way than I'd like......but will try to keep up with what's going on here...
Will certainly want to test out the new kernel and rootfs when it's available......thanks, daalnroti....
All the best,
Mark
-
Happy New Year to you all!
Glad to see everyone's still around if not too busy going into 2016.....
Hopefully, we can all have more fun with our little Z's this year. But like others, work and life seems to be getting more in the way than I'd like......but will try to keep up with what's going on here...
Will certainly want to test out the new kernel and rootfs when it's available......thanks, daalnroti....
All the best,
Mark
Hi Mark,
no worries, hope you find time to play with your Z. I aim to use the 4.4.x series kernel for a long term ALARM base.
I try to dedicate some of my free time to this project and keep it going. As always, any feedback and support is very welcome.
Cheers!
-
Happy New Year to you all!
Glad to see everyone's still around if not too busy going into 2016.....
Hopefully, we can all have more fun with our little Z's this year. But like others, work and life seems to be getting more in the way than I'd like......but will try to keep up with what's going on here...
Will certainly want to test out the new kernel and rootfs when it's available......thanks, daalnroti....
All the best,
Mark
Hi Mark,
no worries, hope you find time to play with your Z. I aim to use the 4.4.x series kernel for a long term ALARM base.
I try to dedicate some of my free time to this project and keep it going. As always, any feedback and support is very welcome.
Cheers!
Hi Daalnroti,
Thanks, sounds good.....
Will provide feedback once I've installed and used your new release....
Just let someone else know about ALARMZ.....hopefully, they will check it out....
Regards,
Mark
-
Hi all,
I was able to install ALARM on my C3200, which is pretty exciting. And it looks like suspend works by hitting "On/Off", which is cool as hell. Out of curiosity, what kinds of functionality are folks still trying to get working?
-
Hi all,
I was able to install ALARM on my C3200, which is pretty exciting. And it looks like suspend works by hitting "On/Off", which is cool as hell. Out of curiosity, what kinds of functionality are folks still trying to get working?
Hi Volt,
first, great to have another user. Thanks for giving ALARM a go on your C3200.
Well, we try to keep the C1000/C3200 alive with an up to date kernel and hope to maintain most of the core functionality.
Personally, I do not have the time to get a fully customised distribution going with a graphical interface and all the apps.
Arch lets you do that easily if you dig through their Wiki and Forum. However, Xorg is pretty demanding on RAM and hardly usable imho.
Using clever console apps like tmux etc you can get much productivity as a SSH client due to the good keyboard.
The C3x00 hardware is pretty well supported, there are a few glitches and some features need testing.
Outstanding issues are at this stage:
- C1000 support - There are still issues with kexecboot,backlight init and other things.
- Framebuffer console blanking causes a white screen the first time, the following blanks are "off" and black.
- Official kernel 4.7+ support, currently there are SPI issues and other things not working in mainline, current kernels are patched with backports from 4.6.7
- Kernel 4.12 introduced a minor keymapping issue. (you need to use left or right shift keys to get all uppercase letters)
What does work on C3x00:
- Ext4 and F2FS for OS
- NTFS, FAT for storage if needed
- USB storage and HID
- SD cards
- CF cards
- WiFi on USB and CF for supported cards
- CF card LAN works for supported cards
- Suspend / Resume
- Online charging (you need to re-plug the power cord after a boot)
- ALSA (Sound)
well, we are only a few users , so your feedback and testing is welcome.
Feel free to ask for help here in the forum or join the IRC channel.
Cheers,
Greguu
-
TOUCHSCREEN : I guess we need to port the touch screen calibration tool from pdaxroom. It was outdated back then already, maybe there is another way to calibrate now.
I am working with my old Gentoo 2010 stage4-armv5tel-softfloat-gnueabi, and I have recently developed a raw and wield application that directly access /dev/input/event1 in order to extract (x,y) points from the touchscreen.
/dev/input/event0
/dev/input/event1 <---------------- I am using this, at the low level
/dev/input/mice
/dev/input/mouse0
Coordinates are so noisy that I added an iterative mean-value filter to have more stable values.
I don't anything about the calibration tool, never used it, but yesterday I added this to my overlay
x11-libs/tslib v1.0
SDL-v1 can be compiled with support tslib, and tslib comes with some applications
/usr/bin/ts_test
/usr/bin/ts_calibrate <---------------- this one looks interesting
/usr/bin/ts_print
/usr/bin/ts_print_raw
/usr/bin/ts_harvest
/usr/bin/ts_finddev
/usr/bin/inputattach