Re: [9fans] Building a Raspberry Pi image / Keyboard support
I'm using 20 Sharp LC-20E90 with HDMI cable, then I got 1184x624 display size (sigh). Any idea to exand this? I got it. I changes the line of disable_overscan=1 to uncommented of the file CONFIG.TXT in /n/9fat directory, and rebooted. Then, now I have 1280x720 display. Why you named /dev/sdM0/dos not /dev/sdM0/9fat? I prefer the latter, because it is accordant with other cpus. Kenji
[9fans] Having trouble connecting to sources
Hi 9fans, I seem to be having trouble connecting to the sources server. My Plan 9 VM tells me timeout and Mac9P tells me no permission. I was able to access fine the other morning by Mac9P. Is there an outage at the moment, or have I botched something in my config? Many thanks! Shane.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
disk/fdisp -p Oops, disk/fdisk is what I meant to type.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Why you named /dev/sdM0/dos not /dev/sdM0/9fat? I prefer the latter, because it is accordant with other cpus. This is standard Plan 9 behaviour of disk/fdisp -p, on any cpu. The convention is that dos is the name for a primary dos partition, and 9fat is the name for a dos subpartition at the start of a plan9 partition. Perhaps you are thinking of one of the forks which does it differently? If you prefer different naming, you can change it yourself with a 'part' command to /dev/sdM0/ctl - /cfg/$sysname/termrc would be a sensible place to do this.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
Thanks Richard. The convention is that dos is the name for a primary dos partition, and 9fat is the name for a dos subpartition at the start of a plan9 partition. Then, I'll follow your decision. By the way, how I can arrage the correct time in this system? I don't mean the /adm/timezone/local, because in the usual PC, we can change it at BIOS screen. Kenji
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
By the way, how I can arrage the correct time in this system? I don't mean the /adm/timezone/local, because in the usual PC, we can change it at BIOS screen. Unlike a PC, the raspberry pi doesn't have a battery-backed real time clock. If you configure a kernel without the 'fakertc' device, it will prompt you to enter the time and date when you power on. For me this was too annoying, which is why I made the fakertc device. With a network connection, the time should be corrected by aux/timesync soon after booting.
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
there are RTC modules for the pi (talk over i2c, based on DS1307 or DS3231). i use them with linux distro's and they seem to work fine. On Mon, Jul 7, 2014 at 6:59 AM, Richard Miller 9f...@hamnavoe.com wrote: By the way, how I can arrage the correct time in this system? I don't mean the /adm/timezone/local, because in the usual PC, we can change it at BIOS screen. Unlike a PC, the raspberry pi doesn't have a battery-backed real time clock. If you configure a kernel without the 'fakertc' device, it will prompt you to enter the time and date when you power on. For me this was too annoying, which is why I made the fakertc device. With a network connection, the time should be corrected by aux/timesync soon after booting.
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
On one RPi I am using a GPS module. I need to add support for its PPS signal for more accurate time keeping. On Jul 7, 2014, at 7:39 AM, Skip Tavakkolian skip.tavakkol...@gmail.com wrote: there are RTC modules for the pi (talk over i2c, based on DS1307 or DS3231). i use them with linux distro's and they seem to work fine. On Mon, Jul 7, 2014 at 6:59 AM, Richard Miller 9f...@hamnavoe.com wrote: By the way, how I can arrage the correct time in this system? I don't mean the /adm/timezone/local, because in the usual PC, we can change it at BIOS screen. Unlike a PC, the raspberry pi doesn't have a battery-backed real time clock. If you configure a kernel without the 'fakertc' device, it will prompt you to enter the time and date when you power on. For me this was too annoying, which is why I made the fakertc device. With a network connection, the time should be corrected by aux/timesync soon after booting.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
I attached my Japanese keyboard program here, which deals with multibyte sequence of key codes. Base is same as Gorka's (probably) program. This is the same one which I sent to eric. If anyone want to modify this for your language, don't warry about lisense etc. i think i added this to usb/kb in 9atom. see the -j option. - erik
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Sat Jul 5 19:46:36 EDT 2014, an...@kix.in wrote: Thanks for the suggestions. The keyboard + mouse work fine with Linux. In fact they work on Plan 9 together, but only for a few seconds before I get: kb: /dev/usb/ep6.1: read: i/o error kb: exiting usbotg: ep5.1 error intr 0082 usb/kb... kb: exiting i see these sometimes, too. a formerly working apple full sized wired keyboard has stopped working with these errors. i assume it's something tricky. however, 9atom has some keyboard/mouse fixes that might be worth checking up on. the original version asked for pretty big descriptors from the device, and many devices generate transaction errors, or otherwise do bad things™ when asked for a descriptor bigger than they envisioned. the solution is to ask for the minimum size descriptor plus enough space to get the descriptor length, then ask again with the device-provided length. - erik
Re: [9fans] Revo L80
Acer Revo l80 CPU: Intel Duel-Core 4-Thread i3-2377M (I would still use 32bit plan9) USB: both 2.0 and 3.0 ports Ethernet: Atheros AR5B22 Wireless Graphics: Intel-graphics 4000 I'm aware wireless can be a problem but I've got a wireless to Ethernet bridge I picked up for the pi that I can use. Haven't yet found out the the wired Ethernet cards model. My main concern is the graphics, it looks like it's using the CPU onboad graphics processor. I don't know myself what problems (if any) are associated with driving the CPU/GPU hybrids. the graphics should work with the vesa driver, but the wireless will not. - erik
Re: [9fans] 2014 hardware overview
I've tried booting from usd cdrom, usb stick both 9labs and 9legacy. it does not recognize them. this is ICH9R that's claimed to be supported. I'm going to try one that has IDE support and ICH9R so it can boot from cdrom and hopefully then recognize the sata chipset, like this one: http://www.supermicro.com/products/motherboard/Xeon3000/3210/X7SBi.cfm that machine should boot from the 9atom usb stick no problems. - erik
Re: [9fans] 2014 hardware overview
On Sun Jun 29 14:21:20 EDT 2014, cinap_len...@felloff.net wrote: 1) UEFI bios I know that 9load and friends can't handle UEFI bios, but I'm guessing if it's possible to use GRUB and chainload Plan9 when the bios is UEFI. Is that possible ? yes, this is possible. the plan9 kernel can be made a multiboot image and loaded by any multiboot loader like grub. some changes are needed for labs plan9 for this to work tho, mainly moving the data segment on page boundary when called from multiboot entry point and using the multiboot memory map and plan9.ini as initrd module. this works out of the box with 9front. alternately a bios boot with uefi firmware will work. :-) detection should be automatic. - erik
[9fans] Seiki 4k + RPi + Plan9
Given that the Seiki 39 4k (3840x2160) display prices have come down quite a bit (now $329 @ amazon) I wanted to see if I can use it with the RPi plan9 as well. 1. You will need one plan9 fix: % diffy /sys/src/9/bcm/mmu.c 307c307 cachedwbse(pte0, pte - pte0); --- cachedwbse(pte0, (pte - pte0)*sizeof(PTE)); 2. You will need to upgrade firmware to at least June 18 version (/sources seems down at the moment but the image Richard put up at /n/sources/contrib/miller/9pi.img.gz has it). Or follow instructions from the RPi website. 3. You will need to fiddle with config.txt. gpu_mem=64 framebuffer_width=3840 framebuffer_height=2160 hdmi_group=2 hdmi_mode=87 hdmi_cvt 3840 2160 15 max_framebuffer_width=3840 max_framebuffer_height=2160 hdmi_pixel_freq_limit=4 disable_overscan=1 I also needed config_hdmi_boot=4 to boost the hdmi signal. You may not. That is it! Some caveats: Its screen feels huge! I sit about 30 from it. It may be too big for a small or shallow office. It may be hard on your eyes or neck or back. I still haven't found the right height for it and may end up installing it on a wall. I have used it for a couple of weeks with a MBP but hardly at all as a plan9 terminal. I can run it at 30Hz at 4k resolution with a recent MBP but this resolution does not work with a late 2011 MBP. At 30hz some people find its cursor to be laggy. Didn't bother me. As per a RPi forum thread this pixel clock should work upto 24Hz. For 24Hz change the hdmi_cvt line to hdmi_cvt 3840 2160 24 The setting I used is for 15Hz and the cursor is a bit laggy. You will probably need to install new firmware on the Seiki and change some of its default settings.
Re: [9fans] Cross-compiling Plan 9
Hi, I was able to cross compile Plan9 from MacOS which is probably quite similar to cross compiling from Linux. The first thing was to compile the plan9 C compilers on MacOS. I used https://code.google.com/p/ken-cc/ because this fork of the Plan9 C compilers are easier to compile on non-plan9 OSes. Then I installed plan9port which contained a few utilities that are used when compiling the plan9 kernel (/bin/rc, /bin/mk). Then I setup a few symlinks at the root e.g. /lib - /home/pad/plan9/root/lib /386 - /home/pad/plan9/root/386 /sys - /home/pad/plan9/sys Finally I have a env.sh that I source that contains important environment variables: export KENCC=/home/pad/kencc # need to modify plan9/src/cmd/mk/shell.c and put rcshell as default shell export PLAN9=/usr/local/plan9 export PATH=$PLAN9/bin:$KENCC/bin:$PATH #for 8._cp to be found and called PATH=$PATH:. export objtype=386 #export objtype=arm export cputype=386 Then I did a few modifications to plan9 Labs and was able to compile and run everything under qemu. My forks: https://github.com/aryx/fork-kencc https://github.com/aryx/fork-plan9 On Jul 5, 2014, at 7:02 AM, Charles Forsyth charles.fors...@gmail.commailto:charles.fors...@gmail.com wrote: On 5 July 2014 14:13, Aleksandar Kuktin akuk...@gmail.commailto:akuk...@gmail.com wrote: Are there any pointers or short instructions or a HOWTO or something similar on the art of cross-compiling Plan 9 from Linux? It would be easier to compile using 9vx under Linux, or a virtual plan 9 machine in qemu under Linux. It is possible to cross-compile directly, but I've only built and used that environment twice myself (once for Solaris, once for Linux), and it isn't any longer in any distributable shape. It might reappear as a side effect of some work on the compiler suite. It's similar to the way Inferno's kernel is cross compiled using the Plan 9 compilers hosted by some other OS, but needs a few special twists to deal with the Plan 9 source tree.
Re: [9fans] Cross-compiling Plan 9
this is an interesting exercise; however, it is much harder than it needs to be. perhaps you have other reasons for doing it the hard way. i posit that bringing up plan9 on qemu and compiling /sys/src is faster than compiling on macos: kencc+p9p+cross compile plan9 and bring up plan9 on qemu. i would be happy to be proven wrong. On Mon, Jul 7, 2014 at 10:41 AM, Yoann Padioleau p...@fb.com wrote: Hi, I was able to cross compile Plan9 from MacOS which is probably quite similar to cross compiling from Linux. The first thing was to compile the plan9 C compilers on MacOS. I used https://code.google.com/p/ken-cc/ because this fork of the Plan9 C compilers are easier to compile on non-plan9 OSes. Then I installed plan9port which contained a few utilities that are used when compiling the plan9 kernel (/bin/rc, /bin/mk). Then I setup a few symlinks at the root e.g. /lib - /home/pad/plan9/root/lib /386 - /home/pad/plan9/root/386 /sys - /home/pad/plan9/sys Finally I have a env.sh that I source that contains important environment variables: export KENCC=/home/pad/kencc # need to modify plan9/src/cmd/mk/shell.c and put rcshell as default shell export PLAN9=/usr/local/plan9 export PATH=$PLAN9/bin:$KENCC/bin:$PATH #for 8._cp to be found and called PATH=$PATH:. export objtype=386 #export objtype=arm export cputype=386 Then I did a few modifications to plan9 Labs and was able to compile and run everything under qemu. My forks: https://github.com/aryx/fork-kencc https://github.com/aryx/fork-plan9 On Jul 5, 2014, at 7:02 AM, Charles Forsyth charles.fors...@gmail.com wrote: On 5 July 2014 14:13, Aleksandar Kuktin akuk...@gmail.com wrote: Are there any pointers or short instructions or a HOWTO or something similar on the art of cross-compiling Plan 9 from Linux? It would be easier to compile using 9vx under Linux, or a virtual plan 9 machine in qemu under Linux. It is possible to cross-compile directly, but I've only built and used that environment twice myself (once for Solaris, once for Linux), and it isn't any longer in any distributable shape. It might reappear as a side effect of some work on the compiler suite. It's similar to the way Inferno's kernel is cross compiled using the Plan 9 compilers hosted by some other OS, but needs a few special twists to deal with the Plan 9 source tree.
Re: [9fans] Cross-compiling Plan 9
On 7 July 2014 19:21, Skip Tavakkolian skip.tavakkol...@gmail.com wrote: i posit that bringing up plan9 on qemu and compiling /sys/src is faster than compiling on macos: kencc+p9p+cross compile plan9 and bring up plan9 on qemu. i would be happy to be proven wrong. yes, i think it might. on linux I use 9vx (not sure about MacOS). also, when i originally did cross compilation from Solaris (which it was) I wasn't allowed to change the system by adding symbolic links but that makes it easier than having to add parameters to mkfiles.
Re: [9fans] Cross-compiling Plan 9
On 7 July 2014 18:41, Yoann Padioleau p...@fb.com wrote: The first thing was to compile the plan9 C compilers on MacOS. I used https://code.google.com/p/ken-cc/ because this fork of the Plan9 C compilers are easier to compile on non-plan9 OSes. I'm (slowly, as usual) bringing those up to date, and will include arm64.
Re: [9fans] Cross-compiling Plan 9
Hi, Thx a lot Charles for https://code.google.com/p/ken-cc/https://urldefense.proofpoint.com/v1/url?u=https://code.google.com/p/ken-cc/k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0Ar=%2FN9d7W2LRwZks3eyFNLr8Q%3D%3D%0Am=kAvsCQ2h%2FsxAGKi2jv2IOZ6RdU94%2FThwCj1BUwwuHa8%3D%0As=6cc3a6fec9ae89696979739db03eef1df62ed849f99cc320c993d3897fc22f09 The main issues I had were related to Rune incompatibilities. See: https://github.com/aryx/fork-kencc/commit/67149c8a19d3dcccb303d9d8de4e679384ca1bf6 https://github.com/aryx/fork-kencc/commit/c0877323424a28e86352bbe172c5dad431441c53 https://github.com/aryx/fork-kencc/commit/160e42f7db33acc7b48e89d5999f5ec3a9c49993 ... On Jul 7, 2014, at 11:34 AM, Charles Forsyth charles.fors...@gmail.commailto:charles.fors...@gmail.com wrote: On 7 July 2014 18:41, Yoann Padioleau p...@fb.commailto:p...@fb.com wrote: The first thing was to compile the plan9 C compilers on MacOS. I used https://code.google.com/p/ken-cc/https://urldefense.proofpoint.com/v1/url?u=https://code.google.com/p/ken-cc/k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0Ar=%2FN9d7W2LRwZks3eyFNLr8Q%3D%3D%0Am=kAvsCQ2h%2FsxAGKi2jv2IOZ6RdU94%2FThwCj1BUwwuHa8%3D%0As=6cc3a6fec9ae89696979739db03eef1df62ed849f99cc320c993d3897fc22f09 because this fork of the Plan9 C compilers are easier to compile on non-plan9 OSes. I'm (slowly, as usual) bringing those up to date, and will include arm64.
Re: [9fans] Cross-compiling Plan 9
On 7 July 2014 19:47, Yoann Padioleau p...@fb.com wrote: The main issues I had were related to Rune incompatibilities. See: An annoying change to get not much (have a look at some of the crud they stuff into that enlarged space), but that will also be changed to match the current versions.
[9fans] Revo L80
Status update for anyone interested: Revo successfully boots from 9atom USB stick! You just need to force USB mode to hard drive in the BIOS. With a wireless bridge the Ethernet works out of the box. Tested by pinging 8.8.8.8. Actual install hits a snag with mbr: no default/data haven't looked into it but will do so tomorrow.
Re: [9fans] Building a Raspberry Pi image / Keyboard support
i think i added this to usb/kb in 9atom. see the -j option. I expected to manage it to use without recompilation for Japanese user. Your change still need to recompile the kernel, because usbd is included in the boot components. If so, my original version is simpler, I think. sorry... Kenji
Re: [9fans] Seiki 4k + RPi + Plan9
Would you please to explain more about the meaning of: hdmi_group=2 hdmi_mode=87 config_hdmi_boot=4 Kenji
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
real time clock. If you configure a kernel without the 'fakertc' Thanks Richard. Yes, I wondered what is this when compiling 9pi.☺ fakertc device. With a network connection, the time should be corrected by aux/timesync soon after booting. I made over a LAN to wireless bridge yesterday. When it'd be arrived, I can try it. Your 9pi is very nice Plan 9 terminal, indeed. I'm now considering to make a box by myself. This is because I don't feel them charm than pi itself, which we can get from the market now. All them are too plasticy and boxy to me. If could have a time of course. Kenji
Re: [9fans] Seiki 4k + RPi + Plan9
On Tue, 08 Jul 2014 08:22:29 +0900 kokam...@hera.eonet.ne.jp wrote: Would you please to explain more about the meaning of: hdmi_group=2 hdmi_mode=87 These magic numbers were gleaned from http://www.raspberrypi.org/forums/viewtopic.php?f=38t=79330 config.txt is documented at http://elinux.org/RPi_config.txt Not sure how complete it is as they add more stuff for new firmware capabilities etc. hdmi_mode=87 is brand new and not yet in the above document. Somre more details at http://www.raspberrypi.org/forums/viewtopic.php?t=5851 There are two commands under Raspbian, tvservice and edidparser. Together they can be used to dump out what a display returns in terms of the modes it supports etc. config_hdmi_boot=4 Sorry, this should be config_hdmi_boost=4 It boosts the HDMI signal strength. Normal signal strength may not be enough if the hdmi cable is long.
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
raspberry pi boxes and discussions about them are as varied and entertaining as program editors. On Mon, Jul 7, 2014 at 4:53 PM, kokam...@hera.eonet.ne.jp wrote: real time clock. If you configure a kernel without the 'fakertc' Thanks Richard. Yes, I wondered what is this when compiling 9pi.☺ fakertc device. With a network connection, the time should be corrected by aux/timesync soon after booting. I made over a LAN to wireless bridge yesterday. When it'd be arrived, I can try it. Your 9pi is very nice Plan 9 terminal, indeed. I'm now considering to make a box by myself. This is because I don't feel them charm than pi itself, which we can get from the market now. All them are too plasticy and boxy to me. If could have a time of course. Kenji
Re: [9fans] Building a Raspberry Pi image / Keyboard support
On Mon Jul 7 19:12:32 EDT 2014, kokam...@hera.eonet.ne.jp wrote: i think i added this to usb/kb in 9atom. see the -j option. I expected to manage it to use without recompilation for Japanese user. Your change still need to recompile the kernel, because usbd is included in the boot components. If so, my original version is simpler, I think. sorry... this is incorrect. -j is a flag to usb/kb. this obviously does not require a recompile, just the addition of kbargs=-j to your plan9.ini. - erik
Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
raspberry pi boxes and discussions about them are as varied and entertaining as program editors. oh, editors have a 40 year head start. rpi can't possibly have reached that level of tedium yet, can they have? - erik
Re: [9fans] Seiki 4k + RPi + Plan9
Sharp's manual says it can also use 1920x1080, which may be too small character to my old eyes.☺ why not just use a bigger font? - erik
