From markinnz at gmail.com Thu Nov 1 04:50:33 2007 From: markinnz at gmail.com (Mark Smith) Date: Thu, 1 Nov 2007 17:50:33 +1300 Subject: [armedslack] Updates In-Reply-To: References: Message-ID: <157C5FE7-BEB3-4A4A-ADB0-780845746248@gmail.com> Cool! I'm looking forward to the ISO image being released :-) On 28/10/2007, at 8:26 PM, Stuart Winter wrote: > > Hi > > I've just uploaded the updates > X.org 7.3 > KDE 3.5.8 > Linux 2.6.23.1 > and everything else which brings it in line with Slackware-current. > > Enjoy! > Stuart > From m-lists at biscuit.org.uk Thu Nov 1 09:30:50 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 1 Nov 2007 09:30:50 +0000 (GMT) Subject: [armedslack] Updates In-Reply-To: <157C5FE7-BEB3-4A4A-ADB0-780845746248@gmail.com> References: <157C5FE7-BEB3-4A4A-ADB0-780845746248@gmail.com> Message-ID: Hi Mark > Cool! I'm looking forward to the ISO image being released :-) You contacted me a while ago about the RiscPC? The thing is that I already created the ISOs - it's easily done. The only sticking point for me was that during the installation, the kernel lock the IRQ that the RapIDE controller is using (my discs are on RapIDE for speed) so the hard disk stopped working. I'll try again soon and see what the error message was. Are the ISOs of any use to non RiscPC users? I can't imagine them being much use for QEMU installations. Most of the ARM installations I'm guessing, would be done over NFS. I'm going on holiday for 2 weeks on Monday; I'll see if I can make some before going away, but if not I'll definitley make some when I get back. If it helps people think about installing ARMedslack on their RiscPC then that's a good start :-) From markinnz at gmail.com Thu Nov 1 19:09:15 2007 From: markinnz at gmail.com (Mark Smith) Date: Fri, 2 Nov 2007 08:09:15 +1300 Subject: [armedslack] Updates In-Reply-To: References: <157C5FE7-BEB3-4A4A-ADB0-780845746248@gmail.com> Message-ID: <60f2066f0711011209w8a6b12ay2c47bf8766d85ec1@mail.gmail.com> On Nov 1, 2007 10:30 PM, Stuart Winter wrote: > > > Cool! I'm looking forward to the ISO image being released :-) > > You contacted me a while ago about the RiscPC? > Yup I've one of those > The thing is that I already created the ISOs - it's easily done. > The only sticking point for me was that during the installation, > the kernel lock the IRQ that the RapIDE controller is using (my discs are > on RapIDE for speed) so the hard disk stopped working. > I'll try again soon and see what the error message was. > What's involved in making a RiscPC bootable ISO ? Not familiar with the process myself. > Are the ISOs of any use to non RiscPC users? I can't imagine them > being much use for QEMU installations. Most of the ARM installations > I'm guessing, would be done over NFS. > I've been messing around via NFS ... but as I had a bit of trouble getting a modern hard disk to work in the RiscPC, I couldn't squeeze the gigabytes of stuff I wanted into a 1.2Gb drive, and the silly Seagate isn't usable with the onboard IDE .. got an old 10GB drive now though, plus I seem to remember someone mentioned that the PowerTec SCSI boards will cause lock ups in Linux so I wouldn't be able to use that (that true ?). > I'm going on holiday for 2 weeks on Monday; I'll see if I can make > some before going away, but if not I'll definitley make some when > I get back. If it helps people think about installing ARMedslack > on their RiscPC then that's a good start :-) > I vote you make ISOs for RiscPCs ;-) Mark From m-lists at biscuit.org.uk Fri Nov 30 21:06:48 2007 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 30 Nov 2007 21:06:48 +0000 (GMT) Subject: [armedslack] Updates In-Reply-To: <60f2066f0711011209w8a6b12ay2c47bf8766d85ec1@mail.gmail.com> References: <157C5FE7-BEB3-4A4A-ADB0-780845746248@gmail.com> <60f2066f0711011209w8a6b12ay2c47bf8766d85ec1@mail.gmail.com> Message-ID: > > You contacted me a while ago about the RiscPC? > > > Yup I've one of those It's amazing that they still go strong even after 16 years or so! Although my main one is starting to play up on me now when booting Linux, unless it's just a bug in GRUB. > What's involved in making a RiscPC bootable ISO ? Not familiar with > the process myself. Not a lot really! It's basically just a case of putting the !SlackBt application into the filesystem, adding the RISC OS filetypes to the filenames (say !Run,ffb for an 'Obey' file), and using a patched mkisofs that translates these file names into RISC OS file types proper. I have scripts to do it, some of which are based on Pat's scripts that he uses to build the real Slackware ISOs, which he doesn't want to release, so I can't release mine either unless I basically rewrite them all. > I've been messing around via NFS ... but as I had a bit of trouble > getting a modern hard disk to work in the RiscPC, I couldn't squeeze > the gigabytes of stuff I wanted into a 1.2Gb drive, and the silly > Seagate isn't usable with the onboard IDE .. No? I will have to have a look at that. I haven't put a large hard disk onto the motherboard IDE for a while now, but I have a 120GB or so sitting around so I will see if it recognises it in RISC OS, and perhaps make a RISC OS partition using !Hform, then see what Linux makes of the disk. > though, plus I seem to remember someone mentioned that the PowerTec > SCSI boards will cause lock ups in Linux so I wouldn't be able to use > that (that true ?). That's true, unfortunately - as soon as the PT driver sees the PT card, it would kernel panic - which is why I do not compile the PowerTec drivers into the Kernel. Unforuntately unless someone a - has a PT card b - knows Linux enough to fix it , and c - cares it's not going to get fixed. > I vote you make ISOs for RiscPCs ;-) I will do soon. I am just bringing -current up to date with slackware-current, including glibc-2.7 and other bits. I would set a date but I know I can't keep it -- life gets in the way, fortunately :-) However, you don't need a Risc PC bootable disc to get going. I wonder if DVD drives work on the RiscPC -- they probably do under Linux. If you can put !SlackBt onto your RISC OS partition, then you could boot into the installer and potentially just install from a DVD, if you make your own DVD of armedslack. I can give you the commands to make a dvd ISO file of it if you want to try -- I don't know if it will work though :-) s.