[9fans] ARM and u-boot
Hello, I have read on the wiki that there is a 5c, for ARM 32bits little-endian, but that there is no flash memory support. Some time ago, I was looking for a NAS (for a client) and was looking for a device that was doing WORM (block deduplication) since, due to user changing metadata (file names) and due to the high necessity to have history for (binary) files, it seemed to me the best. Unfortunately, it happens that in France, for small enterprises (not to say independant worker like me), we are not a worthy target. And the hardware can not be bought directly but only from VAR. (I was looking for example for Coraid products---I don't what put me this name in the head...). So, without answers from VAR contacted, the client went for the simpler (for testing purpose) and cheaper : a Iomega Ix2. To say that the experiment was satisfying will be a big lie... The combination of XFS with RAID1 with the inability to administer wholly (problems of consistency between the two disks, so what does it do when there is a problem? Windows oriented and taking time from whatever Active Directory is telling it something despite its configuration, etc.). The result is that I have retired it and built from scratch a fileserver with a classic incremental backup policy (with NetBSD since I'm not competent enough with Plan9). But I still want to experiment with WORM (more kenfs I think) and I have this ARMv5 thing at disposal. Since it has u-boot installed and that the mapping of the flash is given does one know if one could build a Plan9 kernel, write it (via u-boot) to the flash and be able to boot? Here are the dmesg from the installed Linux kernel (note: it has GbE, but it was accessed through a network with a 100Mb switch, hence the speed reported on the interface): Linux version 2.6.31.8 (s...@bsoho091.lss.emc.com) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 Thu Feb 17 18:15:07 EST 2011 CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 CPU: VIVT data cache, VIVT instruction cache Machine: Feroceon-KW Using UBoot passing parameters structure Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 65536 free_area_init_node: node 0, pgdat c04be8f4, node_mem_map c04e3000 Normal zone: 512 pages used for memmap Normal zone: 0 pages reserved Normal zone: 65024 pages, LIFO batch:15 Built 1 zonelists in Zone order, mobility grouping off. Total pages: 65024 Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0xc@0x0(uboot),0x2@0xa(env),0x30@0x10(zImage),0x30@0x54(initrd),128m@0x0(flash) PID hash table entries: 1024 (order: 10, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 256MB = 256MB total Memory: 245760KB available (4512K code, 315K data, 132K init, 0K highmem) Hierarchical RCU implementation. NR_IRQS:128 Console: colour dummy device 80x30 Calibrating delay loop... 992.87 BogoMIPS (lpj=4964352) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok xor: measuring software checksum speed arm4regs : 866.800 MB/sec 8regs : 684.800 MB/sec 32regs: 668.800 MB/sec xor: using function: arm4regs (866.800 MB/sec) NET: Registered protocol family 16 Feroceon L2: Enabling L2 Feroceon L2: Cache support initialised. CPU Interface - SDRAM_CS0 base , size 256MB SDRAM_CS1 disable SDRAM_CS2 disable SDRAM_CS3 disable PEX0_MEM base e000, size 128MB PEX0_IO base f200, size 1MB PEX1_MEM no such PEX1_IO no such INTER_REGS base f100, size 1MB NFLASH_CS base fa00, size 2MB SPI_CS base f400, size 16MB BOOT_ROM_CS no such DEV_BOOTCS no such CRYPT_ENG base f000, size 2MB Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6281A Soc: 88F6281 A0 LE Detected Tclk 2 and SysClk 3 MV Buttons Device Load Marvell USB EHCI Host controller #0: c8040740 PEX0 interface detected no Link. PCI: bus0: Fast back to back transfers enabled mvPexLocalBusNumSet: ERR. Invalid PEX interface 1 bio: create slab at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb raid6: int32x1 76 MB/s raid6: int32x2 91 MB/s raid6: int32x4 99 MB/s raid6: int32x8 77 MB/s raid6: using algorithm int32x4 (99 MB/s) cfg80211: Calling CRDA to update world regulatory domain NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (no cpio ma
Re: [9fans] Fossil disk usage over 100%?
secconded! my two fossils + venti file servers have been running since 2004. there where problems to do with snapshots which i disabled. That bug is now fixed and it have reenabled them. my only losscame some years ago due to me being paranoid and over-cooling drives, and that was a loss of a one of a mirrored pair, not of real data. -Steve On 1 Jun 2013, at 07:09, Richard Miller <9f...@hamnavoe.com> wrote: >> You misspelled unstable. You have more sack than I could ever say I have for >> putting anything mildly important on fossil. > > Nonsense. > > I've been using fossil on my main system since 2008, and on a thinkpad > which I used daily when working at clients' offices for some years > before that. My professional livelihood depends on the integrity of > those file systems, and I've never lost a file in an active partition > -- apart from two or three "human error" instances like typing 'mv x y' > when I meant 'mv y x', or inadvertently starting two simultaneous > fossils on the same partition. I have had some damage in historical > dumps, but that bug was fixed in March 2012. >
Re: [9fans] ARM and u-boot
> Since it has u-boot installed and that the mapping of the flash is given > does one know if one could build a Plan9 kernel, write it (via > u-boot) to the flash and be able to boot? I'm looking for the answer to this question too. Besides the Sheevaplug, I have a similar ARM gadget that I was planning to enhance by running Plan 9 on it. But before I go there, the Feroceon seems to me to be the same device as the Sheeva's, so you have an advantage there, you may be able to shoehorn the existing "plug" stuff into it without much effort. The ARM world is considerably more complicated, what with dozens of subspecies in existence and 600-page manuals to describe how they work. Personally, I'd be very interested in setting up a Plan 9/ARM Google group in which to discuss what may turn out to be a busy issue. There are many problems I'd like to discuss with similarly minded people and one may want to include the growing Raspberry PI community in such discussions. If anyone is interested, but does not want to use 9fans for this, feel free to mail me at my gmail address (lucio.d...@gmail.com) with ideas. ++L
Re: [9fans] ARM and u-boot
On Sat, Jun 01, 2013 at 10:04:23AM +0200, lu...@proxima.alt.za wrote: > > The ARM world is considerably more complicated, what with dozens of > subspecies in existence and 600-page manuals to describe how they > work. Personally, I'd be very interested in setting up a Plan 9/ARM > Google group in which to discuss what may turn out to be a busy issue. > I'd be interested too in a Plan9/ARM exchange, since a "course" is a path in a domain to tell a student a story (a thread; what today text books have totally forgotten), the ARM "port" would be an interesting Plan9 course (not to mention real world/real need coverage: in DAO/CAO, survey, GIS, mapping etc. there is a need for a "versioning" of binary files without an explosion of the size of data; the WORM addresses this). -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: [9fans] Fossil disk usage over 100%?
On Sat, Jun 01, 2013 at 07:09:41AM +0100, Richard Miller wrote: > Nonsense. > > I've been using fossil on my main system since 2008, and on a thinkpad > which I used daily when working at clients' offices for some years > before that. My professional livelihood depends on the integrity of > those file systems, and I've never lost a file in an active partition > -- apart from two or three "human error" instances like typing 'mv x y' > when I meant 'mv y x', or inadvertently starting two simultaneous > fossils on the same partition. I have had some damage in historical > dumps, but that bug was fixed in March 2012. > > This paragraph has more qualifiers than your average winter olympics
Re: [9fans] ARM and u-boot
> I have read on the wiki that there is a 5c, for ARM 32bits > little-endian, but that there is no flash memory support. i boot my openrd from flash. > Unfortunately, it happens that in France, for small enterprises (not to > say independant worker like me), we are not a worthy target. And the > hardware can not be bought directly but only from VAR. (I was looking > for example for Coraid products---I don't what put me this name in the > head...). i believe alissio (sp) is a reseller in france. you can contact me off list for more information. > But I still want to experiment with WORM (more kenfs I think) and I have > this ARMv5 thing at disposal. > > Since it has u-boot installed and that the mapping of the flash is given > does one know if one could build a Plan9 kernel, write it (via > u-boot) to the flash and be able to boot? > > Here are the dmesg from the installed Linux kernel (note: it has GbE, > but it was accessed through a network with a 100Mb switch, hence the > speed reported on the interface): i have some experience with the marvell ferceron, and they are similar to the plug computers/open rd, but most of the memory mapping will be different. if your want your focus to be on the file server, and not porting to arm, it would be more efficient to use the existing 386 port. - erik
Re: [9fans] ARM and u-boot
On Sat, Jun 01, 2013 at 09:31:29AM -0400, erik quanstrom wrote: > > i have some experience with the marvell ferceron, and they are similar to > the plug computers/open rd, but most of the memory mapping will be > different. > > if your want your focus to be on the file server, and not porting to arm, > it would be more efficient to use the existing 386 port. > Well, the ARM is now ubiquitous and I don't know if there are x86 (whether 32 or 64 bits) without a FPU (now a GPU is even integrated), so ARM is something definitively to consider along x86_* now for uses that don't involve floating point calculus. Fileservers come first to mind, well terminals too for still a significative number of applications not needing high 3D rendering (leaving CPU for... computing). Plus I have the hardware (it was not planned). And finally, if Plan9 could be used as easily as on the Sheevaplug on this kind of Iomega appliance, when it comes to price, with typically two disks of 1, 2 or 4 terabytes, it is an ARM appliance not more expensive than a sheevaplug, and more widely available... (not the same size, and producing---to my taste---a lot of heat; but I had rough times with Iomega software, but if one can get rid of the software and deal with the hardware...). -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
[9fans] PBSR...EI
> "tail -f /dev/kprint" I see, when kprint is open the log isn't sent to the console. Also simply tail or cat /dev/kprint works fine. I need to read more man pages... But now I'm in my installation nightmare! 9atom installation doesn't work, when coping the distribution setting gid and uid fails and files are missing. Can you mail a check sum? I have downloaded the iso twice, but maybe my connection is making a mess. I also tried using 9atom to install the official iso (the installer is the same, doesn't it?), all goes fine but on boot, after selecting the fossil partition: /boot/kfs does not exists I have tried putting the 9atom kernel in 9fat, but things get even worst. Any help will be very appreciated. Regards, trebol. This is the 9atom installer's output: warning: cannot set uid on /n/newfs/adm/secstore warning: cannot set uid on /n/newfs/adm/secstore/store warning: cannot set uid on /n/newfs/adm/secstore/who warning: cannot set uid on /n/newfs/cron/bootes warning: cannot set uid on /n/newfs/cron/bootes/cron warning: cannot set gid on /n/newfs/usr/bootes warning: cannot set uid on /n/newfs/usr/bootes warning: cannot set gid on /n/newfs/usr/bootes/lib warning: cannot set uid on /n/newfs/usr/bootes/lib warning: cannot set gid on /n/newfs/usr/bootes/lib/profile warning: cannot set uid on /n/newfs/usr/bootes/lib/profile warning: cannot set gid on /n/newfs/usr/bootes/tmp warning: cannot set uid on /n/newfs/usr/bootes/tmp warning: cannot set gid on /n/newfs/usr/bootes/bin warning: cannot set uid on /n/newfs/usr/bootes/bin warning: cannot set gid on /n/newfs/usr/bootes/bin/386 warning: cannot set uid on /n/newfs/usr/bootes/bin/386 warning: cannot set gid on /n/newfs/usr/bootes/bin/rc warning: cannot set uid on /n/newfs/usr/bootes/bin/rc warning: cannot set gid on /n/newfs/usr/bootes/bin/rc/kwnvraminit warning: cannot set uid on /n/newfs/usr/bootes/bin/rc/kwnvraminit warning: cannot set gid on /n/newfs/usr/bootes/bin/arm warning: cannot set uid on /n/newfs/usr/bootes/bin/arm warning: cannot set gid on /n/newfs/usr/bootes/bin/amd64 warning: cannot set uid on /n/newfs/usr/bootes/bin/amd64 error: copying /n/newfs/68020/lib/ape: '/n/dist/68020/lib/ape' does not exist error: copying /n/newfs/68020/lib/libc.a: '/n/dist/68020/lib/libc.a' does not exist error: copying /n/newfs/adm/keys: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/adm/keys.who: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/adm/netkeys: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/adm/netkeys.who: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/adm/whois: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/alpha/lib/ape: '/n/dist/alpha/lib/ape' does not exist error: copying /n/newfs/alpha/lib/libc.a: '/n/dist/alpha/lib/libc.a' does not exist error: copying /n/newfs/cron/lock: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/6in4: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/aan: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/acme: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/auth: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/cpu: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/cron: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/cs: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/dns: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/fossil: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/fs: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/ftp: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/httpd/clf: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/httpd/log: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/httpd/pathstat: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/httpd/url: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/imap4d: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/ipboot: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/ipconfig: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/listen: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/mail: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/nfs: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/nfsserver: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/pop3: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/portmapper: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/ppp: '/n/dist/usr/quanstro' does not exist error: copying /n/newfs/sys/log/pptpd: '/n/dist/usr/quanstro' does not exist er
Re: [9fans] ARM and u-boot
On Sat, Jun 01, 2013 at 09:31:29AM -0400, erik quanstrom wrote: > > I have read on the wiki that there is a 5c, for ARM 32bits > > little-endian, but that there is no flash memory support. > > i boot my openrd from flash. > So since it is: Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6281A Soc: 88F6281 A0 LE That is openRD (Marvell 88F6281), it is a starting point for playing with it... -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
[9fans] test(1) -older bug?
Hello, How do you think? I think test is buggy in "older" operation. the test is from 9front. I have not tried bell-labs test. term% ls -l --rw-rw-r-- M 149 arisawa arisawa 3277 Apr 9 23:11 x --rw-rw-r-- M 149 arisawa arisawa 4555 Apr 9 23:12 y term% mtime x 1365516710 x term% mtime y 1365516741 y term% if(test x -ot y) echo OK OK term% if(test x -older 1365516741) echo OK term% if(test x -older 1365516700) echo OK term% term% date -n 1370119926 term% dc 1370119926 1365516710 - p 4603216 term% if(test x -older 4603216) echo OK OK term% if(test x -older 4703216) echo OK term% term% man test f -older t True if file f is older than (modified before) time t. If t is a integer followed by the letters y(years), M(months), d(days), h(hours), m(minutes), or s(seconds), it represents current time minus the specified time. If there is no letter, it represents seconds since epoch. You can also concatenate mixed units. For example, 3d12h means three days and twelve hours ago. Kenji Arisawa
Re: [9fans] test(1) -older bug?
yup. i think it's a bug: /n/sources/patch/older /n/atom/patch/older - erik
Re: [9fans] ARM and u-boot
> Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- > RD-88F6281A Soc: 88F6281 A0 LE > > That is openRD (Marvell 88F6281), it is a starting point for playing > with it... well, good luck. there's a sata driver in 9atom. - erik
Re: [9fans] PBSR...EI
On Sat Jun 1 11:38:56 EDT 2013, trebol55...@aol.com wrote: > But now I'm in my installation nightmare! i'm sorry. > 9atom installation doesn't work, when coping the distribution setting > gid and uid fails and files are missing. Can you mail a check sum? I > have downloaded the iso twice, but maybe my connection is making a > mess. you did install the correct image. those are warnings, so it did not fail to install. but it did do a few things incorrectly. i believe all those changes were subsequently corrected by the updates. i have just pushed out a new image which i hope will have corrected this issue. - erik
Re: [9fans] ARM and u-boot
On Sat, Jun 1, 2013 at 12:19 AM, wrote: > Since it has u-boot installed and that the mapping of the flash is given > does one know if one could build a Plan9 kernel, write it (via > u-boot) to the flash and be able to boot? > It's quite possible. I even have it working. :-) A couple of months ago I submitted a patch to the U-Boot mainline to add formal support for Plan 9 kernels. It has since been accepted. At the same time I also submitted a patch to Geoff which has been gathering dust to add uImage support to 5l (patch/arm-uboot) - a requirement to exist nicely with the loader. The exynos5 port that I am working on (Arndale Board, Samsung Chromebook) relies on this exclusively. If you are familiar with setting up a BSP for U-Boot, it's fairly straightforward to boot a Plan 9 kernel from either a filesystem (ie. FAT, ext2, etc.) or via TFTP. I tend to use TFTP while testing new kernels, though longer lived kernels will likely end up sitting in a FAT - I haven't quite decided yet. Since you seem to be keen console spew, this is what a booted Arndale looks like with the above patches: U-Boot 2013.01.-rc1-2-g67fd7e7-dirty (May 10 2013 - 23:58:01) for ARNDALE5250 CPU: Exynos5250@1000MHz Board: for ARNDALE5250 I2C: ready DRAM: 2 GiB WARNING: Caches not enabled Checking Boot Mode ... SDMMC MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1, EXYNOS DWMMC: 2 In:serial Out: serial Err: serial Net: No ethernet found. (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 0 Waiting for Ethernet connection... done. Using asx0 device TFTP from server 10.0.0.8; our IP address is 10.0.0.10 Filename '/sys/src/9/exynos/9arndale'. Load address: 0x4200 Loading: # ### done Bytes transferred = 1510728 (170d48 hex) ## Booting kernel from Legacy Image at 4200 ... Image Name: 9arndale Image Type: ARM Plan 9 Kernel Image (uncompressed) Data Size:1510664 Bytes = 1.4 MiB Load Address: b100 Entry Point: b100 Verifying Checksum ... OK Loading Kernel Image ... OK OK ## Transferring control to Plan 9 (at address b100) ... Plan 9 from Bell Labs ... Cheers, Steve
Re: [9fans] ARM and u-boot
On Sat, Jun 01, 2013 at 09:06:55PM -0700, Steven Stallion wrote: > > It's quite possible. I even have it working. :-) > > A couple of months ago I submitted a patch to the U-Boot mainline to add > formal support for Plan 9 kernels. It has since been accepted. At the same > time I also submitted a patch to Geoff which has been gathering dust to add > uImage support to 5l (patch/arm-uboot) - a requirement to exist nicely with > the loader. The exynos5 port that I am working on (Arndale Board, Samsung > Chromebook) relies on this exclusively. > Thanks for the tip! I will indeed first test kernels by loading them via TFTP before going any further. Best, -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: [9fans] ARM and u-boot
On Sat, Jun 01, 2013 at 06:10:51PM -0400, erik quanstrom wrote: > > Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- > > RD-88F6281A Soc: 88F6281 A0 LE > > > > That is openRD (Marvell 88F6281), it is a starting point for playing > > with it... > > well, good luck. there's a sata driver in 9atom. As I wrote it will be for me a "course" since hardware driving is an area where my knowledge is nil. I will learn where the border is between machine dependent and machine independent; and for machine dependent, what portion can be written in C and what has to be done in assembly. I don't know how far I will go, but I'm sure to learn a couple of things in the way... -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
