Re: framebuffer console on old ATI

2024-05-07 Thread Riccardo Mottola
Hi, John D. Baker wrote: > As you have seen, the "radeon*" and "radeondrmkmsfb*" drivers do not > attach on "r100" class devices. They have been explicitly excluded > because early in the DRMKMS integration in NetBSD, they exhibited the > "(almost) black-on-black" video problem described in: I

Re: framebuffer console on old ATI

2024-05-07 Thread John D. Baker
As you have seen, the "radeon*" and "radeondrmkmsfb*" drivers do not attach on "r100" class devices. They have been explicitly excluded because early in the DRMKMS integration in NetBSD, they exhibited the "(almost) black-on-black" video problem described in:

Re: Intel Wireless fatal error

2024-05-07 Thread Riccardo Mottola
Hi, Martin Husemann wrote: > The message is bogus, it has nothing to do with autoconfiguration. Misleading.. I was wondering what autoconfiguration had to be done after everything was connected. > > "Fatal error" is a bit in the interrupt cause register of the intel > chipset. The driver can

Re: framebuffer console on old ATI

2024-05-07 Thread Riccardo Mottola
Hi Michael, Michael wrote: > > Yeah, I fixed a few problems there, xrender support was broken for r1xx> > Sun's xvr-100 card is a rebadged rv100... Wonderful... eager to test. >> How do I enable radeonfb? Can I do it through configurations or do I >> need to compile my own kernel to try? > >

Re: Intel Wireless fatal error

2024-05-07 Thread Ramiro Aceves
El mar, 7 may 2024 a las 11:13, Martin Husemann () escribió: > > On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote: > > [ 3574.054462] iwi0: autoconfiguration error: fatal error > > The message is bogus, it has nothing to do with autoconfiguration. > > "Fatal error" is a bit in the

Re: Intel Wireless fatal error

2024-05-07 Thread Martin Husemann
On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote: > [ 3574.054462] iwi0: autoconfiguration error: fatal error The message is bogus, it has nothing to do with autoconfiguration. "Fatal error" is a bit in the interrupt cause register of the intel chipset. The driver can not do

Re: framebuffer console on old ATI

2024-05-07 Thread Michael
Hello, On Tue, 7 May 2024 08:19:33 + Riccardo Mottola wrote: > > Radeonfb should Just Work(tm) - it's used mainly on macppc and sparc64 > > but I'm pretty sure it's been run on at least some little endian hw > > before. > > according to radeon manpage, mine would have an R100, the

Re: i386 - 10.0 gecko browsers

2024-05-07 Thread Benny Siegert
According to the latest bulk build data (https://releng.netbsd.org/bulktracker/build/724/www/), Firefox 123 failed to build, Firefox 115 also failed to build but Firefox 102 was OK. So in principle, there should be a firefox102 package. The firefox115 and firefox error is the same:

Re: framebuffer console on old ATI

2024-05-07 Thread Riccardo Mottola
Hi Michael, Michael wrote: > Radeonfb should Just Work(tm) - it's used mainly on macppc and sparc64 > but I'm pretty sure it's been run on at least some little endian hw > before. according to radeon manpage, mine would have an R100, the earliest supported on X11. How do I enable radeonfb? Can

Re: Intel Wireless fatal error

2024-05-07 Thread Riccardo Mottola
Hi, Riccardo Mottola wrote: > dmesg | grep iwi0 > [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN > 2200BG Mini-PCI Adapter (rev. 0x05) > [ 1.005536] iwi0: interrupting at irq 11 > [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59 > [ 3574.054462] iwi0:

Intel Wireless fatal error

2024-05-07 Thread Riccardo Mottola
Hi, I upgraded my trusty Thinkpad to T30 to 10.0 and now most rough edges have been sorted out. Yesterday I connected it via WiFi, connected remotely to it, then went to bed. Today I see the connection dropped and a green message on the console. Ifconfig says network down. dmesg | grep iwi0 [