Re: 2.6 kernel on pws433au
Uwe Schindler wrote: Could it be that there is some SCSI termination problem that is not detected by the old qlogicisp driver in 2.4? Thanks. it seems it is the SCSI termination. If I put a correctly terminated external disk on the bus then then problems go away. I checked the internal terminator and it seems OK. It's a bit of a faff to have an external box hanging around but it's better than being stuck on a 2.4 kernel! I'll try to find a neater solution sometime. Thanks to everyone for your help. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6 kernel on pws433au
Uwe Schindler wrote: > At 16:03 13.01.2006, Patrick Caulfield wrote: > >> Jaakko Linnosaari wrote: >> > Patrick Caulfield wrote: >> > >> >>Has anyone got a recentish 2.6.x kernel to work on a pws433au box ? >> > >> > >> > Yes. My PWS433au box runs fine with 2.6.15. The kernel package is now >> > available at http://testoapina.tky.hut.fi/kernel/ if you want to take a >> > look. >> > >> >> Thanks very much for that - much quicker than compiling a new kernel! >> >> But that kernel won't boot either. I just get tons of I/O errors >> scrolling on >> the display. >> >> Maybe the disk really is shot and only 2.6 can see the problem ? (2.4 is >> fine). Maybe I'll try and dig out a different disk sometime. > > > We do not know which type of scsi controller your machine has. If it is > the mentioned QLogic ISP1020/1040 then the following could be the problem: > * Linux 2.4 uses the "isp1020" module for this controller > * Linux 2.6 had isp1020 until version 2.6.9 (in Debian until 2.6.8-1, > later Norbert backported the modified qla1280 from 2.6.10 to debian > stable 2.6.8-2). Since then the new driver "qla1280" is used. isp1020 is > no longer in use because of a missing error handler and no maintainer > that supported that module. In recent kernels I think it is completely > removed! > > So I exspect the following: > * The old isp1020 driver has no or only minor error handling, so the > errors do not appear on Linux 2.4 > * Linux 2.6 uses now qla1280 with correct error handling -> errors are > detected and are displayed (I guess the errors with your disk are no > fatal ones...) > > I have seen the follwing with my Alphastation because at first it missed > a terminator at the outside end of the SCSI card. Linux 2.4 didn't see > this. Linux 2.6<=2.6.8-1 showed a error message at boot about missing > error handling in qlogicisp. When I then updated to the new kernel > driver (about one year ago) the scsi driver showed sometimes some > non-fatal errors. I terminated the bus and since then all is OK. Before > I also had some serious file system corruption in EXT3 because of the > missing error handling. > > Could it be that there is some SCSI termination problem that is not > detected by the old qlogicisp driver in 2.4? > Yes, it is the Qlogic. Hmm quite possible. I'll investigate. VMS seems to run fine which is odd but I have been inside the box to move scsi bits around so it's possible that something has been knocked out. Thanks very much -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6 kernel on pws433au
Jaakko Linnosaari wrote: > Patrick Caulfield wrote: > >>Has anyone got a recentish 2.6.x kernel to work on a pws433au box ? > > > Yes. My PWS433au box runs fine with 2.6.15. The kernel package is now > available at http://testoapina.tky.hut.fi/kernel/ if you want to take a > look. > Thanks very much for that - much quicker than compiling a new kernel! But that kernel won't boot either. I just get tons of I/O errors scrolling on the display. Maybe the disk really is shot and only 2.6 can see the problem ? (2.4 is fine). Maybe I'll try and dig out a different disk sometime. -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.6 kernel on pws433au
Has anyone got a recentish 2.6.x kernel to work on a pws433au box ? All the latest Debian kernels get as far as identifying the SCSI disks then start kicking out IO errors and SCSI reset messages. To make matters worse they seem to corrupt the superblock of the root FS too so I have to boot the installer (which runs 2.4 and seems to be fine) and e2fsck it before it will boot off that disk again. That's with the the Debian kernels 2.6.10 & 2.6.11. When I tried to compile my own 2.6.14.4 kernel it failed to link :( -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Please test new kernel-image-2.6.10-alpha packages
On Wed, Jan 26, 2005 at 02:17:58PM +, Tim Cutts wrote: > On 26-Jan-05, Carcharoth wrote: > > At last a 2.6.10 kernel works fine on my Machines (Miata 500au and > > Digital Server 3000). No more red screens on startup. > > The qla1280 driver works now flawlessly, too. > > Boots flawlessly on my LX164, but the PS/2 mouse doesn't work for some > reason, but does with my home-built 2.6.6 kernel. I'll diagnose when I > have the time... probably just a simple configuration error. Similar results here on a pws433 (Miata) machine. Boots and runs fine but no ps/2 mouse. It seems to get detected at startup (according to dmesg) but it doesn't move. cat /proc/psaux or /proc/input/mice produces nothing either. Also, CD-burning doesn't work with this SCSI driver (it didn't work with the old qlogicisp driver either, that just crashed), it did with the feral driver under 2.4. I can post the SCSI errors if anyone's interested. -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.8-1-generic kernel on Alphastation 500/500 still without EXT3, mm/slab.c bug, no LVM
On Wed, Dec 15, 2004 at 03:35:25PM +0100, Uwe Schindler wrote: > c) LVM 1 volume groups did not start. "/etc/init.d/lvm start" displays that > module "lvm" is not found. Do I have to update to lvm2 after installing > kernel 2.6 ? yes, "apt-get install lvm2" should be enough. -- patrick
Re: Miata & Kernel 2.6.x
On Thu, Jun 17, 2004 at 02:42:50PM +0200, Ralf Pelzl wrote: >Hello, >i have a strange problem with my debian installation. > >Hardware: Personell Workstation 600au (Miata), Systemdisk 9,1 GB @ SCSI >QLogic ISP1020 >Software: Debian 3.0r2 unstable, installed on an EXT3 filesystem > >the 2.4.x kernel runs fine. no problems at all. i configured a 2.6.x >kernel (tested with 2.6.1 - 2.6.6) i get a driver error that means that >there is no error handling on the qlogic driver. ok, the machine can load >the os and i can work. after some hours and some reboots the filesystem is >corrupt, the journaling repairs at each boot some errors. after some >reboots the filesystem is broken so the machine is never booting. with the >2.4.x kernel i dont have problems. but i want to use the newer kernel. my >question now: do you have any experience with that, is it a problem of the >ext3-driver (never tested with ext2), a qlogicisp driver problem or >whatever ? i read in this list about a driver from www.feral.com, but i >cant open that website. can anyone send me that driver ? I don't know why you are seeing corruption in 2.6. Provided I don't put any serious load on the qlogicisp driver is seems to work OK. As soon as you put some real work into it (or just a cdrecord!) it will hang though. The feral driver works fine but I haven't seen it ported to 2.6 yet - certainly the version I have won't compile under 2.6. FWIW - here's a copy: http://people.debian.org/~patrick/isp_dist.tgz -- patrick
Re: Kernel panic & qlogicisp module
On Tue, Nov 25, 2003 at 12:11:21PM -0600, Kelledin wrote: > &scoring > > Ulrich Harttig said: > > I have a problem with what I believe is the qlogicisp SCSI driver module. > > Under certain conditions = when copying large files > 50 MB from sda to > > sdb is in progress, the kernel panics: > > If you head over to http://www.feral.com/isp.html , you can get an > alternative driver for QLogic ISP controllers. It has the advantage of > being a unified driver (it can drive pretty much the entire QLogic line of > SCSI/FC-ALcontrollers), and it supports things like SCSI disconnect that > the stock kernel drivers don't support. I've used it briefly to drive an > ISP1080 card, but not long enough to attest to its stability. Agreed. The stock isp driver in Linux is unusable as far as I can tell. I've been using the feral one for ages and it seems very stable in my pws433au -- patrick
Re: Powerstorm 300
On Mon, Nov 03, 2003 at 01:38:28PM -0500, Jay Estabrook wrote: > On Mon, Nov 03, 2003 at 08:46:35AM -0800, MC wrote: > > > > That's not totally true: the powerstorm 4D10T in my Rawhide (AS1200) > > works fine, as it is a Permedia 2 based card. Not sure about any other > > Powerstorm cards, though apparently your Powerstorm 300 is not supported > > by XFree86. > > Here's a (hopefully) complete table of PowerStorm options: > > PowerStorm Actual > Model Hardware > -- > > 3D10S3 Trio64 (NT only) > 3D30TGA2 8-plane > 4D10T ELSA Gloria Synergy 8 > 4D20TGA2 24-plane > 4D40T Intergraph Cateye > 4D50T Intergraph Cateye > 4D51T Intergraph Cateye > 4D60T Intergraph Cateye > > 300 Evans and Sutherland REALimage > 350 Evans and Sutherland REALimage > > AFAIK, only 3D10, 3D30, 4D10T and 4D20 have XFree86 support. > What I did was get an old Trio64V+ card off Ebay for very little money (5ukp I think). That card works fine in Linux and VMS - IFF you put it in the right slot on a pws433au :) -- patrick
Re: compiler errors: md needed for hardware raid?
On Wed, Jul 16, 2003 at 12:18:31PM +0200, Lars Oeschey wrote: > Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: > > > LVM works fine on Alpha, though personally I'm using LVM2 now :-) > > Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you > > need to set up md and /then/ LVM > > hm, I just wanted to remove md support from the kernel, but that > deactivates LVM also... > In xconfig it's under the option "Multi device support (Raid and LVM)", > and when I remove the "Multiple devices driver support (RAID and LVM)", > the option "LVM support" gets greyed out... That's right "Multiple devices driver support (RAID and LVM)" is just a general thing that covers md and LVM1, there's no actual code involved. To disable md simply don't select any of the RAID options on that menu. The options are only grouped together cos they do similar things, not because they share code. -- patrick
Re: compiler errors: md needed for hardware raid?
On Tue, Jul 15, 2003 at 04:18:54PM +0200, Falk Hueffner wrote: > Lars Oeschey <[EMAIL PROTECTED]> writes: > > > Am Dienstag, 15. Juli 2003 15:19 schrieb Falk Hueffner: > > mh, ok... But I found that I need some kind of software raid, I have > > several partitions on external cabinets (that old mylex controllers > > support partitions only up to 32Gb) and I want to combine those to one > > big drive. > > I took a look ant md and LVM now, but what I didn't find is, does LVM > > need md? or is it more of a replacement for it? > > Cause then I could just use LVM... > > I think LVM2 can do at least raid0 on its own. I don't know whether it > is well-tested on Alpha, though, I've never used it :) LVM works fine on Alpha, though personally I'm using LVM2 now :-) Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you need to set up md and /then/ LVM -- patrick
Re: Alternative to qlogic scsi card for 550au
On Sat, Jun 07, 2003 at 04:56:33PM +0200, Andrew Maier wrote: > Hi, > > I have a PWS 550au with a (standard?) QLogic ISP1020 card. I have now > tried to attach an old Exabyte 8200 to the this host adapter and had > several kernel panics. After some search I finally discovered that the > qlogic card "does not support disconnect/ reconnect, which makes using > it with tape drives impractical." (Quote from the kernels > README.qlogicisp) > > So I am looking to replace/add another scsi host adapter to my box > which will support tape drives better. Are there any recommendations > for which card I should get? > > Also would you recommend adding another card just for the tape or to > completely replace the qlogic card? You could try the ISP driver a www.feral.com/isp.html. I don't know whether is supports disconect/reconnect but it's a MUCH better driver than the standard linux one so its worth a try. -- patrick
Re: Sound on Miata 433
On Tue, Mar 04, 2003 at 03:01:43PM -0500, Ron Murray wrote: >I have a Miata (pws 433u) running sarge, which works well except > for sound. The sound chip is apparently an ES1888 on 0x220, irq5, dma > 1 & 5. > >I could never get OSS sound running on it, but I'd rather get ALSA > working anyway. I can get ALSA running with the sb8 driver -- but > that's only 8-bit, of course. The correct driver should be es18xx, but > earlier versions of ALSA wouldn't load that module, claiming that the > opl3 port wasn't at 0x220. The current (sarge?) version of > alsa-drivers does load the es18xx module, but pcm doesn't work when I > try it (saytime gives out one syllable, then hangs). (Actually, the > sb8 module in the current alsa-modules doesn't work either, but that's > another story). > >Has anyone successfully got 16-bit sound going on one of these > boxes? Hey, this question hasn't come up for nearly 3 months now :-) I've never tried ALSA but OSS works fine on my pws433. I have the following in /etc/modutils/sound (which was copied from this list and then reposted to it at least once). options sb esstype=1868 io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x320 post-install sb /usr/bin/aumix -L alias sound-slot-0 sb alias sound-service-0-3 sb alias sound sb patrick
Re: Debian on Digital 3305
On Wed, Feb 12, 2003 at 07:07:40PM -0600, Richard Fillion wrote: > I was never able to get any kernels to boot unless i marked them as > Generic Alpha in menuconfig. "cat /proc/cpuinfo" would say it was a > Noritake though. I literally tried all of the options in menuconfig, > none worked except the Generic one. > > The burner was a Yamaha 4x2x6 scsi burner. It would burn, but then the > box would come to a haltwhile fixating the disk. So i had to decide > what mattered more to me, uptime or a cd every time i wanted to burn. I > had similar problems with an IDE burner i put in, only it would crash as > soon as the burn started. I know nothing about that particular machine but I had a very similar problem burning CDs on my pws433 and it turned out to be a bug in the ISP SCSI driver. I replaced it with the one at http://www.feral.com/isp.html and now it works fine. -- patrick
Re: Xfree86 on Trio64v+
On Tue, Nov 05, 2002 at 08:05:26PM +, Patrick Caulfield wrote: > On Tue, Nov 05, 2002 at 08:55:02PM +1100, Robert Reid wrote: > > I have XFree86 4.2 installed on my AlphaStation 500. I have 3 various > > Trio64 based PCI cards lying around, 1 worked, 2 didn't. I didn't try > > with XFree86 3.3, the current card that works is: > > 00:0b.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] > > (rev 54) > > That's interesting. > > I've got another card arriving via eBay so I might give that a try when it > arrives. I really bought it as a spare incase I blew the current one up too. > > SVGATextMode and twin are now working so I can get large terminal windows > (which is the point of X-windows anyway isn't it?) so that's a start :-) Very late reply but I've now got it working. The trick (for me) seems to have been to install the card in a 64bit PCI slot which is, presumably, the "right" side of the bridge. patrick
