From m-lists at biscuit.org.uk Wed Aug 1 07:41:04 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Aug 2007 08:41:04 +0100 (BST) Subject: [armedslack] Risc PC + zImage patch In-Reply-To: <1185799002.8729.21.camel@localhost> References: <1185799002.8729.21.camel@localhost> Message-ID: > Have you tried to integrate Jim Hawkins patch into the mainstream kernel > to fix the compressed kernel unloading problems ?? Yep - http://www.spinics.net/lists/arm-kernel/msg33782.html It was rejected: http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3532/1 Jim didn't understand what he was getting at. From m-lists at biscuit.org.uk Wed Aug 1 08:17:41 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Aug 2007 09:17:41 +0100 (BST) Subject: [armedslack] Risc PC + zImage patch In-Reply-To: References: <1185799002.8729.21.camel@localhost> Message-ID: > Jim didn't understand what he was getting at. ..and you're more than welcome to resubmit it :-) I also want to get the RapIDE patch upstream - especially after what Russel said about changing the IDE subsystem. -- Stuart Winter www.armedslack.org From alanh at fairlite.demon.co.uk Wed Aug 1 08:26:45 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 01 Aug 2007 09:26:45 +0100 Subject: [armedslack] Risc PC + zImage patch In-Reply-To: References: <1185799002.8729.21.camel@localhost> Message-ID: <1185956805.8662.4.camel@localhost> On Wed, 2007-08-01 at 09:17 +0100, Stuart Winter wrote: > > Jim didn't understand what he was getting at. > > ..and you're more than welcome to resubmit it :-) > > I also want to get the RapIDE patch upstream - especially after > what Russel said about changing the IDE subsystem. I'm looking at the way Russell described now. Hopefully I'll redo the patch soon. I could possibly take a look at the RapIDE later, but I don't have a card to test it. Alan. From m-lists at biscuit.org.uk Wed Aug 1 10:16:13 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Aug 2007 11:16:13 +0100 (BST) Subject: [armedslack] Risc PC + zImage patch In-Reply-To: <1185956805.8662.4.camel@localhost> References: <1185799002.8729.21.camel@localhost> <1185956805.8662.4.camel@localhost> Message-ID: > Hopefully I'll redo the patch soon. Cool. > I could possibly take a look at the RapIDE later, but I don't have a > card to test it. The driver works as is with Linux 2.6.22.1 - it's just a case of whether RMK likes it. I asked him on the armlinux list for feedback after he commented about submitting armedslack's patches upstream, but didn't get any feedback. I might submit it to the arm-kernel list and see whether he takes it. From psychicistnonconformist at gmail.com Wed Aug 1 10:52:27 2007 From: psychicistnonconformist at gmail.com (Sunil Amitkumar Janki) Date: Wed, 01 Aug 2007 12:52:27 +0200 Subject: [armedslack] Risc PC + zImage patch In-Reply-To: References: <1185799002.8729.21.camel@localhost> <1185956805.8662.4.camel@localhost> Message-ID: <46B065EB.7040608@gmail.com> Stuart Winter wrote: > The driver works as is with Linux 2.6.22.1 - it's just a case > of whether RMK likes it. I asked him on the armlinux list for feedback > after he commented about submitting armedslack's patches upstream, but > didn't get any feedback. > > I might submit it to the arm-kernel list and see whether he takes it. Is there a RiscPC emulator for Linux that Armedslack can be installed on? Maybe a QEMU target for the RiscPC could be added. I have packages of Softgun and Skyeye installed but those are probably also only for newer ARM platforms. I have also had a look at the Iyonix patch on Castle's website but even that one looks way to messy to be of any value. Is it possible to send some thorough information on pci devices and necessary drivers to this list or to my private e-mail? A QEMU target for the Iyonix would be very convenient as well. Sunil From alanh at fairlite.demon.co.uk Wed Aug 1 10:26:08 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 01 Aug 2007 11:26:08 +0100 Subject: [armedslack] Risc PC + zImage patch In-Reply-To: References: <1185799002.8729.21.camel@localhost> <1185956805.8662.4.camel@localhost> Message-ID: <1185963968.8662.13.camel@localhost> On Wed, 2007-08-01 at 11:16 +0100, Stuart Winter wrote: > > Hopefully I'll redo the patch soon. > > Cool. I've redone the patch, just rebuilding now to test. > > I could possibly take a look at the RapIDE later, but I don't have a > > card to test it. > > The driver works as is with Linux 2.6.22.1 - it's just a case > of whether RMK likes it. I asked him on the armlinux list for feedback > after he commented about submitting armedslack's patches upstream, but > didn't get any feedback. > > I might submit it to the arm-kernel list and see whether he takes it. O.k. Alan. From alanh at fairlite.demon.co.uk Wed Aug 1 11:32:05 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 01 Aug 2007 12:32:05 +0100 Subject: [armedslack] kernel patches Message-ID: <1185967925.8662.25.camel@localhost> Where's the current list of kernel patches for ARMedslack ?? I need to get back to the clock fixes too for RiscPC. Alan. From m-lists at biscuit.org.uk Wed Aug 1 15:06:02 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Aug 2007 16:06:02 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1185967925.8662.25.camel@localhost> References: <1185967925.8662.25.camel@localhost> Message-ID: > Where's the current list of kernel patches for ARMedslack ?? > There's only 3 there: ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches > I need to get back to the clock fixes too for RiscPC. Will this ever work? the RTC doesn't work in QEMU either. I know RMK says RTC works for him on his RPC but perhaps he has different clock hardware or something! From alanh at fairlite.demon.co.uk Wed Aug 1 15:21:07 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 01 Aug 2007 16:21:07 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> Message-ID: <1185981667.8662.36.camel@localhost> On Wed, 2007-08-01 at 16:06 +0100, Stuart Winter wrote: > > Where's the current list of kernel patches for ARMedslack ?? > > > > There's only 3 there: > ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches Thanks. > > I need to get back to the clock fixes too for RiscPC. > > Will this ever work? the RTC doesn't work in QEMU either. > I know RMK says RTC works for him on his RPC but perhaps he has > different clock hardware or something! If it works for RiscOS, then we should be able to fix it for Linux. Alan. From m-lists at biscuit.org.uk Wed Aug 1 16:57:38 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 1 Aug 2007 17:57:38 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1185981667.8662.36.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1185981667.8662.36.camel@localhost> Message-ID: > > different clock hardware or something! > > If it works for RiscOS, then we should be able to fix it for Linux. Thats great news. I was seriously thinking of adding a final installer script asking the user if they want to turn off fsck checks because whenever you boot, as you've noticed, the last mount was a gazillion years ago and you need an fsck ;-) From jawkins at armedslack.org Wed Aug 1 17:02:52 2007 From: jawkins at armedslack.org (Jim Hawkins) Date: Wed, 1 Aug 2007 18:02:52 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1185981667.8662.36.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1185981667.8662.36.camel@localhost> Message-ID: On Wed, 1 Aug 2007, Alan Hourihane wrote: > On Wed, 2007-08-01 at 16:06 +0100, Stuart Winter wrote: > > I know RMK says RTC works for him on his RPC but perhaps he has > > different clock hardware or something! > > If it works for RiscOS, then we should be able to fix it for Linux. I did have a cursory glance over the RTC code ages ago, but I couldn't see what was wrong with it. I tend to use NTP to get the time any way. Cheers, Jim From alanh at fairlite.demon.co.uk Wed Aug 1 20:41:35 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 01 Aug 2007 21:41:35 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> Message-ID: <1186000895.8662.44.camel@localhost> On Wed, 2007-08-01 at 16:06 +0100, Stuart Winter wrote: > > Where's the current list of kernel patches for ARMedslack ?? > > > > There's only 3 there: > ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches Looking at the acornfb3.diff I think the only part which is worth getting in is the disabling of INTERLACE & DOUBLESCAN modes. The 24bpp support is bogus. It does exactly what 32bpp support is. Is there a problem with starting X without this ?? And returning a multi-sync monitor instead of SVGA these days, is probably a bad idea too. We can always override this on the command-line anyway. Alan. From m-lists at biscuit.org.uk Thu Aug 2 08:41:57 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 2 Aug 2007 09:41:57 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1186000895.8662.44.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> Message-ID: > The 24bpp support is bogus. It does exactly what 32bpp support is. Is > there a problem with starting X without this ?? It was to do with resolution and colours: " > I can get the RiscPC to display in 1280x1024 at 60Hz but only in 8bpp. > I can get it to display at 800x600 in 16bpp but that's it :-( > The machine has 2MB of VRAM so it should be able to display 1024x768 > in 16bpp at least (I think!). You are definitely right. You can try it with the program fbset in the console. Presently it seems that there are 2 problems: (1) The VIDC20 framebuffer driver needs also to accept 24bpp as a request for 32bpp due to a change in the X server. So 24bpp can not work currently. (2) Another problem is the screen mode enumeration of Xorg. Maybe it checks first mode 800x600-{anything above 56), sees that this doesn't work, and concludes that all 800x600 modes are not possible. If I have time I will try to fix it. IIRC, you can overcome the problem by specifying your own modes in xorg.conf, they are tested first then. It should help to include these lines into xorg.conf: Section "Modes" Identifier "Whatever" Modeline "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync EndSection . . . Section "Monitor" . . . UseModes "Whatever" EndSection But as I said, 24bpp can not work currently." > And returning a multi-sync monitor instead of SVGA these days, is > probably a bad idea too. We can always override this on the command-line > anyway. Agreed. From alanh at fairlite.demon.co.uk Thu Aug 2 08:56:58 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Thu, 02 Aug 2007 09:56:58 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> Message-ID: <1186045018.8653.15.camel@localhost> On Thu, 2007-08-02 at 09:41 +0100, Stuart Winter wrote: > > The 24bpp support is bogus. It does exactly what 32bpp support is. Is > > there a problem with starting X without this ?? > > It was to do with resolution and colours: > > " > > I can get the RiscPC to display in 1280x1024 at 60Hz but only in 8bpp. > > I can get it to display at 800x600 in 16bpp but that's it :-( > > The machine has 2MB of VRAM so it should be able to display 1024x768 > > in 16bpp at least (I think!). > > You are definitely right. You can try it with the program fbset in the > console. Presently it seems that there are 2 problems: > > (1) The VIDC20 framebuffer driver needs also to accept 24bpp as a request > for > 32bpp due to a change in the X server. So 24bpp can not work currently. > > (2) Another problem is the screen mode enumeration of Xorg. Maybe it > checks > first mode 800x600-{anything above 56), sees that this doesn't work, and > concludes that all 800x600 modes are not possible. If I have time I will > try > to fix it. IIRC, you can overcome the problem by specifying your own modes > in > xorg.conf, they are tested first then. It should help to include these > lines > into xorg.conf: > > Section "Modes" > Identifier "Whatever" > Modeline "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync > +vsync > ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 > -hsync -vsync > EndSection > . > . > . > Section "Monitor" > . > . > . > UseModes "Whatever" > EndSection > > But as I said, 24bpp can not work currently." Still seems bogus. You can start X with the the -fbbpp flag or modify the xorg.conf file to start X at 32bpp. I'll load X up on my RiscPC and try it out. Stuart - do you want to send the INTERLACED/DOUBLESCAN part off to Russell's bug tracker ?? Alan. From alanh at fairlite.demon.co.uk Thu Aug 2 08:57:58 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Thu, 02 Aug 2007 09:57:58 +0100 Subject: [armedslack] Risc PC + zImage patch In-Reply-To: <1185963968.8662.13.camel@localhost> References: <1185799002.8729.21.camel@localhost> <1185956805.8662.4.camel@localhost> <1185963968.8662.13.camel@localhost> Message-ID: <1186045078.8653.18.camel@localhost> On Wed, 2007-08-01 at 11:26 +0100, Alan Hourihane wrote: > On Wed, 2007-08-01 at 11:16 +0100, Stuart Winter wrote: > > > Hopefully I'll redo the patch soon. > > > > Cool. > > I've redone the patch, just rebuilding now to test. I've uploaded it to Russell's bug tracker and it's ID is 4540. I'm sure it'll need fixing up for Russell's requirements, but the basic fix is there now. Alan. From alanh at fairlite.demon.co.uk Thu Aug 2 13:21:29 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Thu, 02 Aug 2007 14:21:29 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1185981667.8662.36.camel@localhost> Message-ID: <1186060889.8653.33.camel@localhost> On Wed, 2007-08-01 at 17:57 +0100, Stuart Winter wrote: > > > different clock hardware or something! > > > > If it works for RiscOS, then we should be able to fix it for Linux. > > Thats great news. I was seriously thinking of adding a final > installer script asking the user if they want to turn off fsck > checks because whenever you boot, as you've noticed, the > last mount was a gazillion years ago and you need an fsck ;-) Actually, looking at 2.6.21 the acorn clock code has been fixed. The code in drivers/i2c/busses/i2c-acorn.c and drivers/rtc/rtc-pcf8583.c are all that's needed and off we go ! Just enable those two options..... long pause....... Just tried it, and it works here. Alan. From m-lists at biscuit.org.uk Thu Aug 2 17:49:50 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 2 Aug 2007 18:49:50 +0100 (BST) Subject: [armedslack] Risc PC + zImage patch In-Reply-To: <46B065EB.7040608@gmail.com> References: <1185799002.8729.21.camel@localhost> <1185956805.8662.4.camel@localhost> <46B065EB.7040608@gmail.com> Message-ID: > Is there a RiscPC emulator for Linux that Armedslack can be installed on? Not sure about for Linux but there was something called Red Squirrel or similar for Windows. > Maybe a QEMU target for the RiscPC could be added. I have packages of > Softgun and Skyeye installed but those are probably also only for newer > ARM platforms. Maybe although I do not know how it works. To boot a RiscPC you need the images from the PROMs -- which are easy enough to rip -- but you then have to supply them. I'd sure like a RPC target although I can't imagine it being *that* popular :-) > I have also had a look at the Iyonix patch on Castle's website but even > that one looks way to messy to be of any value. Is it possible to send > some thorough information on pci devices and necessary drivers to this > list or to my private e-mail? I asked Peter who said "I do, but he's ging to have to be a lot more specific. His best bet is to ask for specific information, either on usenet csa.programmer or csa.hardware. There's _some_ stuff on http://riscos.info too." Or you could ask Castle -- perhaps they'd give you a machine if you would make a 2.6 port. The thing is that I am not sure how popular their hardware would be anymore, especially with QEMU around -- we had that discussion about the usefulness of ARM boards before. However, even though QEMU is a great tool, the tests still have to be performed on the real hardware to satisfy me. -- Stuart Winter www.armedslack.org From m-lists at biscuit.org.uk Thu Aug 2 17:51:37 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 2 Aug 2007 18:51:37 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1186060889.8653.33.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1185981667.8662.36.camel@localhost> <1186060889.8653.33.camel@localhost> Message-ID: > The code in drivers/i2c/busses/i2c-acorn.c and drivers/rtc/rtc-pcf8583.c > are all that's needed and off we go ! > > Just enable those two options..... long pause....... great - I have added those two -- and removed a tonne of the other RTC devices -- to the RPC kernel config and I'm rebuilding the kernel package. It looks as if it'd have worked already if I'd have compiled I2C into the kernel rather than as a module! I'll remove the RiscPC checks from the sysvinit scripts that prevent the clock being set from the RTC. From m-lists at biscuit.org.uk Fri Aug 3 15:39:38 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 3 Aug 2007 16:39:38 +0100 (BST) Subject: [armedslack] New updates In-Reply-To: <46A9AF73.2000304@gmail.com> References: <46A9AF73.2000304@gmail.com> Message-ID: > So you have almost caught up to Slackware 12.0 :-). Almost. I've just started KDE building -- we'll know whether it works in about 4 days :-) > MIPS minus a few packages that didn't build but I see you have patches > for them. Now I'm building extra software and catching up with x86 in > that respect. I do? I have some stuff but usually I find a later version and build that, or I'll spend a while trawling gentoo and debian. > I still have to build an installer though but I think I can reuse much of > your procedure. Hopefully -- if you make any improvements let me know! It started off as quite a nice script but is looking a bit hairy now. Still, it works and I cannot think of a better way. > I bought a Sun Enterprise 250 server a few days ago and I will gradually > port Slackware 12.0 to it over the coming month(s). Splack seems stuck > at 10.2 but I will ensure that the latest Slackware will run on the > architecture. Splack has been abandoned -- it's mentioned on the web site. Shame really. I had grand ideas of updating Splack but it just takes too much time to do a good job -- at least for me: I did try some of these meditation techniques to make you only need a few hours of sleep, but it did not work yet and I got grumpy ;-) > to longer term if I can get hold of the hardware so Slackware will go to all > architectures that Debian has gone to and beyond :-). Good luck! From m-lists at biscuit.org.uk Wed Aug 8 07:23:54 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 8 Aug 2007 08:23:54 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1186045018.8653.15.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> Message-ID: > You can start X with the the -fbbpp flag or modify the xorg.conf file to > start X at 32bpp. > > I'll load X up on my RiscPC and try it out. Did you get this to work as expected? If so, can I have your xorg.conf file? :-) > Stuart - do you want to send the INTERLACED/DOUBLESCAN part off to > Russell's bug tracker ?? I can do - I just need to re-read the discussions to understand exactly what to write in the patch statement. I have submitted the RapIDE driver. -- Stuart Winter www.armedslack.org From alanh at fairlite.demon.co.uk Wed Aug 8 08:05:00 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 08 Aug 2007 09:05:00 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> Message-ID: <1186560300.8685.0.camel@localhost> On Wed, 2007-08-08 at 08:23 +0100, Stuart Winter wrote: > > You can start X with the the -fbbpp flag or modify the xorg.conf file to > > start X at 32bpp. > > > > I'll load X up on my RiscPC and try it out. > > Did you get this to work as expected? If so, can I have your xorg.conf > file? :-) Yes, it works at 32bpp just fine without those patches. Attached. Alan. -------------- next part -------------- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/share/X11/rgb" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/misc" EndSection Section "Module" Load "extmod" Load "dbe" Load "record" Load "xtrap" Load "glx" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "gb" Option "XkbModel" "pc105" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" EndSection Section "Monitor" Identifier "Monitor0" VendorName "HP" ModelName "LP2065" Option "DPMS" EndSection Section "Device" Identifier "Card0" Driver "fbdev" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection From m-lists at biscuit.org.uk Wed Aug 8 08:37:37 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 8 Aug 2007 09:37:37 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1186560300.8685.0.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> Message-ID: > > Did you get this to work as expected? If so, can I have your xorg.conf > > file? :-) > > Yes, it works at 32bpp just fine without those patches. Thanks - so there's no need to apply the patch? Thanks for the file - I'll go through it and put it into the xskel package. From alanh at fairlite.demon.co.uk Wed Aug 8 08:57:17 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 08 Aug 2007 09:57:17 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> Message-ID: <1186563437.8685.3.camel@localhost> On Wed, 2007-08-08 at 09:37 +0100, Stuart Winter wrote: > > > Did you get this to work as expected? If so, can I have your xorg.conf > > > file? :-) > > > > Yes, it works at 32bpp just fine without those patches. > > Thanks - so there's no need to apply the patch? It works fine without the patch, but I think the doublescan/interlace part is still probably good. I'm not sure though as I haven't checked what VIDC is capable of. Alan. From m-lists at biscuit.org.uk Sat Aug 18 13:25:20 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 18 Aug 2007 14:25:20 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1186563437.8685.3.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> Message-ID: Hi > > Thanks - so there's no need to apply the patch? > > It works fine without the patch, but I think the doublescan/interlace > part is still probably good. I'm not sure though as I haven't checked > what VIDC is capable of. OK - I've left only the doublescan/interlace part in the patch, and upgraded to Linux 2.6.22.3. The only thing now is that X isn't working -- attached is the log file. I tried using your xorg.conf and my original one. Do you have any ideas? -------------- next part -------------- _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/zaden:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Slackware 12.0 Slackware Linux Project Current Operating System: Linux zaden 2.6.22.3-riscpc #1 Fri Aug 17 19:48:43 BST 2007 armv4l Build Date: 02 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Aug 18 10:13:32 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (WW) The directory "/usr/share/fonts/local/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/extra/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/CID/" does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/OTF/, /usr/share/fonts/TTF/, /usr/share/fonts/Type1/, /usr/share/fonts/Speedo/, /usr/share/fonts/75dpi/:unscaled, /usr/share/fonts/100dpi/:unscaled, /usr/share/fonts/75dpi/, /usr/share/fonts/100dpi/, /usr/share/fonts/cyrillic/ (**) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) No APM support in BIOS or kernel (II) Loader magic: 0x1af070 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (--) using VT number 7 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension RECORD (II) LoadModule: "xtrap" (II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so (II) Module xtrap: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DEC-XTRAP (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "freetype" (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 1.3.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/lib/xorg/modules/fonts//libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.5 (II) Loading font Type1 (II) LoadModule: "fbdev" (II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so (II) Module fbdev: vendor="X.Org Foundation" compiled for 1.3.0, module version = 0.3.1 ABI class: X.Org Video Driver, version 1.2 (II) LoadModule: "mouse" (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) LoadModule: "kbd" (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) FBDEV: driver for framebuffer: fbdev (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 1.3.0, module version = 0.0.2 ABI class: X.Org Video Driver, version 1.2 (II) FBDEV(0): using default device (II) Running in FRAMEBUFFER Mode (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32 (==) FBDEV(0): RGB weight 888 (==) FBDEV(0): Default visual is TrueColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: Acorn (video memory: 2048kB) (II) FBDEV(0): checking modes against framebuffer device... (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 640x480 (pitch 640) (**) FBDEV(0): Built-in mode "current": 25.2 MHz, 31.5 kHz, 59.9 Hz (II) FBDEV(0): Modeline "current" 25.17 640 656 752 800 480 491 493 525 -hsync -vsync -csync (==) FBDEV(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (**) FBDEV(0): using shadow framebuffer (II) Loading sub module "shadow" (II) LoadModule: "shadow" (II) Loading /usr/lib/xorg/modules//libshadow.so (II) Module shadow: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.3 (==) Depth 24 pixmap format is 32 bpp (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 From m-lists at biscuit.org.uk Sat Aug 18 13:26:51 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 18 Aug 2007 14:26:51 +0100 (BST) Subject: [armedslack] New updates Message-ID: Hi KDE 2.5.7 and basically Slackware 12.0 + patches. There's mainly extra/ and a few others to finish. And then I want to stabalise the distribution as much as possible. It's *going* to get released as version 12.0 :-) -- Stuart Winter www.armedslack.org From alanh at fairlite.demon.co.uk Sun Aug 19 13:12:32 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Sun, 19 Aug 2007 14:12:32 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> Message-ID: <1187529152.8766.1.camel@localhost> On Sat, 2007-08-18 at 14:25 +0100, Stuart Winter wrote: > Hi > > > > Thanks - so there's no need to apply the patch? > > > > It works fine without the patch, but I think the doublescan/interlace > > part is still probably good. I'm not sure though as I haven't checked > > what VIDC is capable of. > > OK - I've left only the doublescan/interlace part in the patch, > and upgraded to Linux 2.6.22.3. The only thing now is that > X isn't working -- attached is the log file. > > I tried using your xorg.conf and my original one. > > Do you have any ideas? That's basically saying that FBDev had to modify the mode from what was passed in. What does 'fbset' say about the current mode ? Alan. From jawkins at armedslack.org Sun Aug 19 14:33:09 2007 From: jawkins at armedslack.org (Jim Hawkins) Date: Sun, 19 Aug 2007 15:33:09 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1187529152.8766.1.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> Message-ID: On Sun, 19 Aug 2007, Alan Hourihane wrote: > On Sat, 2007-08-18 at 14:25 +0100, Stuart Winter wrote: > > OK - I've left only the doublescan/interlace part in the patch, > > and upgraded to Linux 2.6.22.3. The only thing now is that > > X isn't working -- attached is the log file. > > > > I tried using your xorg.conf and my original one. > > > > Do you have any ideas? > > That's basically saying that FBDev had to modify the mode from what was > passed in. > > What does 'fbset' say about the current mode ? Stuart ran up a kernel with some debug in for me - yres_virtual is getting modified. Looks like the acornfb driver is increasing it to support ypan for accelerated text scrolling. Cheers, Jim From alanh at fairlite.demon.co.uk Sun Aug 19 19:48:37 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Sun, 19 Aug 2007 20:48:37 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> Message-ID: <1187552917.8766.2.camel@localhost> On Sun, 2007-08-19 at 15:33 +0100, Jim Hawkins wrote: > On Sun, 19 Aug 2007, Alan Hourihane wrote: > > > On Sat, 2007-08-18 at 14:25 +0100, Stuart Winter wrote: > > > OK - I've left only the doublescan/interlace part in the patch, > > > and upgraded to Linux 2.6.22.3. The only thing now is that > > > X isn't working -- attached is the log file. > > > > > > I tried using your xorg.conf and my original one. > > > > > > Do you have any ideas? > > > > That's basically saying that FBDev had to modify the mode from what was > > passed in. > > > > What does 'fbset' say about the current mode ? > > Stuart ran up a kernel with some debug in for me - yres_virtual is getting > modified. Looks like the acornfb driver is increasing it to support ypan > for accelerated text scrolling. Has something changed in acornfb then ? I wouldn't have thought so to cause this. Stuart - are you saying that applying the original patch makes things work ? Alan. From m-lists at biscuit.org.uk Sun Aug 19 21:18:45 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 19 Aug 2007 22:18:45 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1187552917.8766.2.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> Message-ID: > > Stuart ran up a kernel with some debug in for me - yres_virtual is getting > > modified. Looks like the acornfb driver is increasing it to support ypan > > for accelerated text scrolling. > > Has something changed in acornfb then ? I wouldn't have thought so to > cause this. I don't know - I didn't check. The most recent things I did without immediate testing were when I rebuilt all of Xorg, and upgrading to Linux 2.6.22.3 > Stuart - are you saying that applying the original patch makes things > work ? No - Jim thought the original patch was the cause of the problem which motivated me to cut that stuff out of the patch. Jim is going to look at how to fix it. X.org works inside QEMU though so at least it works somewhere ;-) -- Stuart Winter www.armedslack.org From m-lists at biscuit.org.uk Tue Aug 28 08:41:26 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 28 Aug 2007 09:41:26 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1187552917.8766.2.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> Message-ID: > Stuart - are you saying that applying the original patch makes things I've uploaded some updates now, including a new Kernel with Jim's patch to acornfb which makes X work. Jim was concerned that it'd cause a slowdown on the console framebuffer but I haven't really noticed any difference. I have one more bug to look at with X where fc-cache complains that it cannot write to the font dirs, and after that and a few other tidy ups, I will begin looking at making ISOs so we can get something released :-) From alanh at fairlite.demon.co.uk Tue Aug 28 09:00:38 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Tue, 28 Aug 2007 10:00:38 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> Message-ID: <1188291638.8971.5.camel@localhost> On Tue, 2007-08-28 at 09:41 +0100, Stuart Winter wrote: > > Stuart - are you saying that applying the original patch makes things > > I've uploaded some updates now, including a new Kernel with Jim's > patch to acornfb which makes X work. > Jim was concerned that it'd cause a slowdown on the console framebuffer > but I haven't really noticed any difference. Is the patch available anywhere ? Alan. From m-lists at biscuit.org.uk Tue Aug 28 09:07:39 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 28 Aug 2007 10:07:39 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1188291638.8971.5.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> Message-ID: > Is the patch available anywhere ? ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches/acornfb_ypan.patch It's applied after the acornfb3.diff (interlace & doublescan patch). From alanh at fairlite.demon.co.uk Tue Aug 28 09:48:30 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Tue, 28 Aug 2007 10:48:30 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> Message-ID: <1188294510.8971.9.camel@localhost> On Tue, 2007-08-28 at 10:07 +0100, Stuart Winter wrote: > > Is the patch available anywhere ? > > ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches/acornfb_ypan.patch > > It's applied after the acornfb3.diff (interlace & doublescan patch). Can you reverse that patch and then try changing the line that says... if (var->accel_flags & FB_ACCELF_TEXT) { to this... if (((var->activate & FB_ACTIVATE_MASK) != FB_ACTIVATE_TEST) && (var->accel_flags & FB_ACCELF_TEXT)) { Alan. From alanh at fairlite.demon.co.uk Tue Aug 28 20:06:29 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Tue, 28 Aug 2007 21:06:29 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> Message-ID: <1188331589.8971.44.camel@localhost> On Tue, 2007-08-28 at 10:07 +0100, Stuart Winter wrote: > > Is the patch available anywhere ? > > ftp://ftp.armedslack.org/armedslack/armedslack-current/source/k/sources/linux-2.6/patches/acornfb_ypan.patch Actually, I'm pretty sure this is a bug in X. The test has since been modified to handle xres_virtual >=, and I think yres_virtual should be the same. Or we should remove the test for xres_virtual/yres_virtual. I'm just querying that with another developer now, and should be able to make the change to X tomorrow. But looking at acornfb.c some more, shows that it's a little old. Relying on the older ACCELF_TEXT flag whereas the new fbdev API removes that. I'm looking at this now. Alan. From jawkins at armedslack.org Tue Aug 28 21:30:14 2007 From: jawkins at armedslack.org (Jim Hawkins) Date: Tue, 28 Aug 2007 22:30:14 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1188331589.8971.44.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188331589.8971.44.camel@localhost> Message-ID: On Tue, 28 Aug 2007, Alan Hourihane wrote: > I'm pretty sure this is a bug in X. I was debating myself whether this was a bug in X or not. I just threw that patch together to check it was the cause of X not starting. And to stop Stuart hassling me about fixing it :) > The test has since been modified to handle xres_virtual >=, and I think > yres_virtual should be the same. Or we should remove the test for > xres_virtual/yres_virtual. I'd agree with that. > I'm just querying that with another developer now, and should be able to > make the change to X tomorrow. Cool. > But looking at acornfb.c some more, shows that it's a little old. > Relying on the older ACCELF_TEXT flag whereas the new fbdev API removes > that. I'm looking at this now. I noticed this as well. My suspicions were piqued by "#define STUPID_ACCELF_TEXT_SHIT" in fb.h ;) Jim From m-lists at biscuit.org.uk Wed Aug 29 08:19:26 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 29 Aug 2007 09:19:26 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1188294510.8971.9.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188294510.8971.9.camel@localhost> Message-ID: > if (((var->activate & FB_ACTIVATE_MASK) != FB_ACTIVATE_TEST) && > (var->accel_flags & FB_ACCELF_TEXT)) { I've done that -- X doesn't start: (II) FBDEV(0): using default device (II) Running in FRAMEBUFFER Mode (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32 (==) FBDEV(0): RGB weight 888 (==) FBDEV(0): Default visual is TrueColor (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) (II) FBDEV(0): hardware: Acorn (video memory: 2048kB) (II) FBDEV(0): checking modes against framebuffer device... (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (II) FBDEV(0): mode "1280x1024" test failed (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (II) FBDEV(0): mode "1280x960" test failed (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (II) FBDEV(0): mode "1152x864" test failed (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (II) FBDEV(0): mode "1024x768" test failed (II) FBDEV(0): mode "800x600" ok (II) FBDEV(0): mode "640x480" test failed (II) FBDEV(0): checking modes against monitor... (--) FBDEV(0): Virtual size is 800x600 (pitch 800) (**) FBDEV(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz (II) FBDEV(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (==) FBDEV(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (**) FBDEV(0): using shadow framebuffer (II) Loading sub module "shadow" (II) LoadModule: "shadow" (II) Loading /usr/lib/xorg/modules//libshadow.so (II) Module shadow: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.3 (==) Depth 24 pixmap format is 32 bpp (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 From alanh at fairlite.demon.co.uk Wed Aug 29 08:34:24 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 29 Aug 2007 09:34:24 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188294510.8971.9.camel@localhost> Message-ID: <1188376464.7963.0.camel@localhost> On Wed, 2007-08-29 at 09:19 +0100, Stuart Winter wrote: > > if (((var->activate & FB_ACTIVATE_MASK) != FB_ACTIVATE_TEST) && > > (var->accel_flags & FB_ACCELF_TEXT)) { > > I've done that -- X doesn't start: > > (II) FBDEV(0): using default device > (II) Running in FRAMEBUFFER Mode > (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32 > (==) FBDEV(0): RGB weight 888 > (==) FBDEV(0): Default visual is TrueColor > (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) > (II) FBDEV(0): hardware: Acorn (video memory: 2048kB) > (II) FBDEV(0): checking modes against framebuffer device... > (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) FBDEV(0): mode "1280x1024" test failed > (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) FBDEV(0): mode "1280x960" test failed > (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) FBDEV(0): mode "1152x864" test failed > (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) FBDEV(0): mode "1024x768" test failed > (II) FBDEV(0): mode "800x600" ok > (II) FBDEV(0): mode "640x480" test failed > (II) FBDEV(0): checking modes against monitor... > (--) FBDEV(0): Virtual size is 800x600 (pitch 800) > (**) FBDEV(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), > 35.2 kHz, 56.2 Hz > (II) FBDEV(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 > 625 +hsync +vsync > (==) FBDEV(0): DPI set to (75, 75) > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/lib/xorg/modules//libfb.so > (II) Module fb: vendor="X.Org Foundation" > compiled for 1.3.0, module version = 1.0.0 > ABI class: X.Org ANSI C Emulation, version 0.3 > (**) FBDEV(0): using shadow framebuffer > (II) Loading sub module "shadow" > (II) LoadModule: "shadow" > (II) Loading /usr/lib/xorg/modules//libshadow.so > (II) Module shadow: vendor="X.Org Foundation" > compiled for 1.3.0, module version = 1.1.0 > ABI class: X.Org ANSI C Emulation, version 0.3 > (==) Depth 24 pixmap format is 32 bpp > (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode > (EE) FBDEV(0): mode initialization failed > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 O.k. I think we need to fix X here. Alan. From alanh at fairlite.demon.co.uk Wed Aug 29 08:43:48 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 29 Aug 2007 09:43:48 +0100 Subject: [armedslack] kernel patches In-Reply-To: <1188376464.7963.0.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188294510.8971.9.camel@localhost> <1188376464.7963.0.camel@localhost> Message-ID: <1188377028.7963.8.camel@localhost> The patch to fix X, rather than acornfb. Alan. -------------- next part -------------- A non-text attachment was scrubbed... Name: fbdevhw.c.patch Type: text/x-patch Size: 566 bytes Desc: not available URL: From m-lists at biscuit.org.uk Wed Aug 29 18:56:18 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 29 Aug 2007 19:56:18 +0100 (BST) Subject: [armedslack] kernel patches In-Reply-To: <1188377028.7963.8.camel@localhost> References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188294510.8971.9.camel@localhost> <1188376464.7963.0.camel@localhost> <1188377028.7963.8.camel@localhost> Message-ID: > The patch to fix X, rather than acornfb. Thanks Alan! I've rebuilt the xorg-server packages and that works. There's screen corruption (fuzzy colours) for about 15 seconds or so, but it corrects itself. I'll upload the new packages in the next few days. Cheers s. From alanh at fairlite.demon.co.uk Wed Aug 29 20:58:42 2007 From: alanh at fairlite.demon.co.uk (Alan Hourihane) Date: Wed, 29 Aug 2007 21:58:42 +0100 Subject: [armedslack] kernel patches In-Reply-To: References: <1185967925.8662.25.camel@localhost> <1186000895.8662.44.camel@localhost> <1186045018.8653.15.camel@localhost> <1186560300.8685.0.camel@localhost> <1186563437.8685.3.camel@localhost> <1187529152.8766.1.camel@localhost> <1187552917.8766.2.camel@localhost> <1188291638.8971.5.camel@localhost> <1188294510.8971.9.camel@localhost> <1188376464.7963.0.camel@localhost> <1188377028.7963.8.camel@localhost> Message-ID: <1188421122.7963.32.camel@localhost> On Wed, 2007-08-29 at 19:56 +0100, Stuart Winter wrote: > > The patch to fix X, rather than acornfb. > > Thanks Alan! > > I've rebuilt the xorg-server packages and that works. > There's screen corruption (fuzzy colours) for about 15 seconds or so, but > it corrects itself. There shouldn't be. I'll see if I can look closer sometime in the next week or two. Alan.