Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
> btw: is anyone working on additional WiFi firmware (for example atheros) > support? right now i don't think so. ath5k and ath9k would likely be welcome, but all newer atheros stuff seems not worth it (say some important linux wifi driver people, they complained about non-documented stuff and binay blobs, and are thus trying to avoid atheros/qualcomm iirc). i am not aware of any more modern wifi hardware that is both well documented and available, so unless somebody is willing to do good old ath5k or ath9k, i'd wait it out a bit more...
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Den sön 5 maj 2019 16:15 skrev: > > I have a fun issue where 9front resolution depends on EFI boot method. > Via > > firmware interface, I get 1600x900 but via bootloader (EFI file copied to > > esp) I get low resolution. > > not so surprising. pure EFI without legacy CSP does not have a VESA BIOS. > all you get is what the bootloader could figure out about the framebuffer > that the firmware set up for us. thats is what we have to work with until > you invoke a native driver to set up a proper mode. > > > I can not set resolution via aux/vga so the resolution at boot is the one > > that sticks. > > what graphics card is this? when its intel, we have a native driver. it > might just not know about your specific card yet. > http://sysinfo.9front.org/src/269/body so amd/radeon > > btw: is anyone working on additional WiFi firmware (for example atheros) > > support? > > not that i know of. > > -- > cinap > >
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
On 5/5/19, cinap_len...@felloff.net wrote: > type !rc at the bootargs prompt to get a shell, then run: > > grep '^02' '#$/pci/'*ctl > > which prints the pci information for all network cards. that > should get us closer to why the probing code fails. > I've been using a handful of those adapters for a long time, the legacy etherelnk3.c for i386 works flawlessly with them. I'd rather redirect the effort to document the ethernet adapters that have been proven to work. Down here, the challenge isn't antiquated adapters, it is bad quality ones, that are cheap, but even Linux, sometimes Windows doesn't support them. And it's all you get. What I'm suggesting is that we keep the supported hardware list up to date and provide some details of where it can or could be sourced. It would certainly make my life a lot simpler (so would moving back to Europe, but that's a bit less achievable). That said, I'll see what I can do about the PCI details. I'll probably have to copy them manually. Lucio.
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
type !rc at the bootargs prompt to get a shell, then run: grep '^02' '#$/pci/'*ctl which prints the pci information for all network cards. that should get us closer to why the probing code fails. -- cinap
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
On 5/5/19, cinap_len...@felloff.net wrote: > > you can try to add the etherelnk3 line to the pc64 config and > rebuild. > I tried that, but I suspect there is more to it: no errors are reported on compiling or booting, but the device is still not identified. Well, that's not entirely true. I built 9pc64 with elnk3 uncommented, then discovered the instructions to build 9ants64, so I took that path. That's where compiling and booting reported no errors (unless a missing device is considered an error). When I tried to boot the 9pc64 I built earlier, booting failed. But in a 9ants context, that may be unrelated. Unfortunately, the diagnostics that may reveal the nature of the problem flash past far too quickly. The days of capturing such diagnostics through a serial port seem to be in the past. Lucio.
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
> Next plan9.ini's "rootdir". It is no longer documented in > plan9.ini(8), but the little code that uses it in bootrc is odd as > well as at odds with the legacy documentation. yes! we got it all wrong! it all makes sense in the /lib/namespace what should happen, but bootrc does it wrong. > My hope was to give it "9front" as a value and have Fossil serve > that as the root for a diskless 9front workstation, as in > bind -b $rootdir / > Instead, I find "mount -c /srv/boot $rootdir" which is definitely not > it. you are absolutely correct. this is wrong. here is the fix: http://code.9front.org/hg/plan9front/rev/1209e04a3af9 > I'm not sure under what circumstances one target a different > location for the ROOT directory, I would be interested to hear. Of > course, this conflict needs to be resolved. > This is starting to get interesting. yeah. thank you very much! :-) > Lucio. -- cinap
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
> I have a fun issue where 9front resolution depends on EFI boot method. Via > firmware interface, I get 1600x900 but via bootloader (EFI file copied to > esp) I get low resolution. not so surprising. pure EFI without legacy CSP does not have a VESA BIOS. all you get is what the bootloader could figure out about the framebuffer that the firmware set up for us. thats is what we have to work with until you invoke a native driver to set up a proper mode. > I can not set resolution via aux/vga so the resolution at boot is the one > that sticks. what graphics card is this? when its intel, we have a native driver. it might just not know about your specific card yet. > btw: is anyone working on additional WiFi firmware (for example atheros) > support? not that i know of. -- cinap
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Gotcha, it is amd64, so I will look at that and report back. Next plan9.ini's "rootdir". It is no longer documented in plan9.ini(8), but the little code that uses it in bootrc is odd as well as at odds with the legacy documentation. My hope was to give it "9front" as a value and have Fossil serve that as the root for a diskless 9front workstation, as in bind -b $rootdir / Instead, I find "mount -c /srv/boot $rootdir" which is definitely not it. I'm not sure under what circumstances one target a different location for the ROOT directory, I would be interested to hear. Of course, this conflict needs to be resolved. This is starting to get interesting. Lucio. PS: Thanks a bunch for the support, both you and Hiro. On 5/5/19, cinap_len...@felloff.net wrote: >> It's the 3Com that baffles me. I suspect the two-stage boot (I know >> dangerously little about 9front's boot process) somehow fails to pick >> up a supported device (3c905b - etherelink3). > > is this the amd64 kernel or 386 one? the amd64 one does not include > the etherelnk3 driver. the reason is that the amd64 kernel shares its > drivers with the pc kernel, but not all drivers might be ready for > 64 bit pointers. so we only include what we can test and verify. > > you can try to add the etherelnk3 line to the pc64 config and > rebuild. > > if you have this issue with the 386 kernel, then knowing the pci > device id would be a start. > > the boot process is nothing special. we have a bootloader that loads > the kernel. the loader uses BIOS/EFI calls to get the kernel from the > boot media so that it does not need drivers. once the kernel > is taking over, it needs a driver. > > -- > cinap > > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Den sön 5 maj 2019 14:34 skrev: > > the boot process is nothing special. we have a bootloader that loads > the kernel. the loader uses BIOS/EFI calls to get the kernel from the > boot media so that it does not need drivers. once the kernel > is taking over, it needs a driver. > I have a fun issue where 9front resolution depends on EFI boot method. Via firmware interface, I get 1600x900 but via bootloader (EFI file copied to esp) I get low resolution. I can not set resolution via aux/vga so the resolution at boot is the one that sticks. btw: is anyone working on additional WiFi firmware (for example atheros) support?
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
> It's the 3Com that baffles me. I suspect the two-stage boot (I know > dangerously little about 9front's boot process) somehow fails to pick > up a supported device (3c905b - etherelink3). is this the amd64 kernel or 386 one? the amd64 one does not include the etherelnk3 driver. the reason is that the amd64 kernel shares its drivers with the pc kernel, but not all drivers might be ready for 64 bit pointers. so we only include what we can test and verify. you can try to add the etherelnk3 line to the pc64 config and rebuild. if you have this issue with the 386 kernel, then knowing the pci device id would be a start. the boot process is nothing special. we have a bootloader that loads the kernel. the loader uses BIOS/EFI calls to get the kernel from the boot media so that it does not need drivers. once the kernel is taking over, it needs a driver. -- cinap
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
mycroftiv is using venti+fossil from 9front. i'm sure there is a way :)
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
The Atheros is just not supported, it seems. It's the 3Com that baffles me. I suspect the two-stage boot (I know dangerously little about 9front's boot process) somehow fails to pick up a supported device (3c905b - etherelink3). Lucio. PS: It bothers me that I can't serve a 9front workstation from a 9legacy fossil server: the jig-saw puzzle pieces are very subtly incompatible. Maybe I ought to remind myself what exactly goes wrong when trying to netboot a 9front kernel and from there pick a 9front tree to be served. Naturally, I don't want to have two distinct file servers and it is way too early for me to feel I should migrate to 9front. I need to point out that (unless I mis-remember) it is in the Bell Labs distribution that the gears begin to slip. On 5/5/19, hiro <23h...@gmail.com> wrote: > are there any drivers on other plan9 for your unsupported devices that > we missed pulling in? > > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
are there any drivers on other plan9 for your unsupported devices that we missed pulling in?
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Well, I installed all of 9ants (thanks, microftiv), it proved irresistible, but the Atheros 2414 ethernet adapter isn't supported and, mysteriously, a 3com 509B isn't detected by the bootstrap process. It is seen as a PCI device at run time... And the main goal, really, was TLS/SSH, with quick and slick text exchanges as a bonus. Lucio.
Re: [9fans] user interface questions
It looks like exp/shiny (a tentative, multi-platform graphics API native in the Go language) is getting some dusting off right at this moment. I had a look at the most recent copy I have in hand of Dave MacFarlane's devdraw shiny driver, but the immediate absence I picked up was a missing interface method (texture filling?). I couldn't find a description of the missing method, only implementations in other drivers and at that level my comprehension is minimal, so unless someone points me at some documentation I can understand, I'll have to wait for someone else to fill that gap. Which is a crying shame: exp/shiny shows such promise... Lucio. On 4/27/19, Jens Staal wrote: > Den lör 27 apr. 2019 08:21Lucio De Re skrev: > >> On 4/26/19, Kurt H Maier wrote: >> > >> > It's here now: https://bellard.org/TinyGL/ >> > >> > khm >> > >> Let me add this correction to that document, this is where my >> curiosity found VReng: >> >> http://www.vreng.enst.fr/ >> >> Thank you, Kurt. >> >> Lucio. >> > >> >> >> >> If I remember correctly, there is an SDL port on Plan9, and there is a >> tinygl-on-sdl so perhaps it is already possible. >> >> >> -- >> Lucio De Re >> 2 Piet Retief St >> Kestell (Eastern Free State) >> 9860 South Africa >> >> Ph.: +27 58 653 1433 >> Cell: +27 83 251 5824 >> FAX: +27 58 653 1435 >> >> > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Oh! A pact with Tux is far better for instant gratification ;-). On 5/5/19, hiro <23h...@gmail.com> wrote: > that's not my problem lucio. my deal with glenda has been made and i > am promised great low latency 9p fileservers in my afternamespaces. > > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
> then read and write from /n/chat/chat in whatever manner you please. i guess just that `chat` script is located and thus provided by a hubfs install...
Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
that's not my problem lucio. my deal with glenda has been made and i am promised great low latency 9p fileservers in my afternamespaces.
Re: [9fans] strange propogation paths in 9fans mail?
I've seen it too. On Sat, May 4, 2019, 11:20 PM wrote: > Hi. > > Is this happening for anyone else? > > Relatively recently, it's happened that I see the replies before the > originals, with delays in between of *days*. > > This has happened in the past with 9fans, but not recently, and now > it's started again... > > Thanks, > > Arnold > >
Re: [9fans] strange propogation paths in 9fans mail?
> Is this happening for anyone else? Yeah, I've noticed it on and off also.
[9fans] strange propogation paths in 9fans mail?
Hi. Is this happening for anyone else? Relatively recently, it's happened that I see the replies before the originals, with delays in between of *days*. This has happened in the past with 9fans, but not recently, and now it's started again... Thanks, Arnold
