Re: Please test new kernel-image-2.6.10-alpha packages

2005-02-08 Thread Tyson Whitehead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On January 23, 2005 09:23 am, Norbert Tretkowski wrote:
 With the latest upload of kernel-source-2.6.10 I was finally able to
 create working (for me) kernel-image-2.6.10-alpha packages. Please
 test them, especially when you're using a Qlogic ISP1020/1040 SCSI
 controller, which is now supported by the qla1280 driver. You also
 need to update initrd-tools if you want to use the qla1280 driver with
 your ISP1020/1040 controller.

The kernel image works fine on my box (a PWS 500au with a QLogic Corp. ISP1020 
Fast-wide SCSI (rev 05)).  Thanks for the work.  It's great to feel like your 
SCSI controller is being supported again.  *grin*

- -T

- -- 
 Tyson Whitehead  (-twhitehe at uwo.ca -- WSC-)
 Computer EngineerDept. of Applied Mathematics,
 Graduate Student- Applied MathematicsUniversity of Western Ontario,
 GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCCUeSRXbLmIoqtdgRAmwrAKCvW0Iuu0yqGEJgaMcd8AtsE4oJ5gCeOPxh
q0UX1XHlJY7Y/JlaWntcWGk=
=RFUc
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



hung DS10 - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Toni L. Harbaugh-Blackford [Contr]
On Sun, 23 Jan 2005, Norbert Tretkowski wrote:

   With the latest upload of kernel-source-2.6.10 I was finally able to
   create working (for me) kernel-image-2.6.10-alpha packages. Please
   test them, especially when you're using a Qlogic ISP1020/1040 SCSI
   controller, which is now supported by the qla1280 driver. You also
   need to update initrd-tools if you want to use the qla1280 driver with
   your ISP1020/1040 controller.

I installed the generic kernel and the initrd-tools, but upon reboot my
DS10 hangs.  This system contains two scsi cards, an NCR 53C895 and a
Qlogic 1020 (DEC originals, I don't remember the part numbers).  Here
are details of the devices attached to the scsi cards, from 'show config':

Bus 00  Slot 14: NCR 53C895
  pka0.7.0.14.0 SCSI Bus ID 7
  dka100.1.0.14.0COMPAQ BB018122B7
  dka200.2.0.14.0COMPAQ BB01813467
  dka300.3.0.14.0RZ1DF-CB
  dka400.4.0.14.0RZ1DB-CA
  dka500.5.0.14.0RZ1DB-CA
  dka600.6.0.14.0RZ1CB-CS
Bus 00  Slot 15: QLogic ISP10x0
  pkb0.7.0.15.0 SCSI Bus ID 7
  dkb0.0.0.15.0  COMPAQ BD036659CC


I was running kernel 2.6.8-1 (generic) without problem.

Here is the console log up to the hang:

b dka500 -fl 0
(boot dka500.5.0.14.0 -flags 0)
block 0 of dka500.5.0.14.0 is a valid boot block
reading 171 blocks from dka500.5.0.14.0
bootstrap code read in
base = 20, image_start = 0, image_bytes = 15600(87552)
initializing HWRPB at 2000
initializing page table at 3ff3
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
aboot: Linux/Alpha SRM bootloader version 0.9b
aboot: switching to OSF/1 PALcode version 1.90
aboot: booting from device 'SCSI 0 14 0 5 500 0 0'
aboot: valid disklabel found: 8 partitions.
aboot: loading uncompressed vmlinuz...
aboot: loading compressed vmlinuz...
aboot: zero-filling 234628 bytes at 0xfc624524
aboot: loading initrd (6414336 bytes/6264 blocks) at 0xfc003f80a000
aboot: starting kernel vmlinuz with arguments ro  root=/dev/sde5 console=ttyS0
Linux version 2.6.10-1-generic ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 
1:3.3.5-6)) #1 Wed Jan 26 19:44:07 UTC 2005
Booting GENERIC on Tsunami variation Webbrick using machine vector Webbrick 
from SRM
Major Options: LEGACY_START MAGIC_SYSRQ
Command line: ro  root=/dev/sde5 console=ttyS0
memcluster 0, usage 1, start0, end  256
memcluster 1, usage 0, start  256, end   130967
memcluster 2, usage 1, start   130967, end   131072
freeing pages 256:384
freeing pages 817:130967
reserving pages 817:819
Initial ramdisk at: 0xfc003f80a000 (6414336 bytes)
2048K Bcache detected; load hit latency 20 cycles, load miss latency 90 cycles
Built 1 zonelists
Kernel command line: ro  root=/dev/sde5 console=ttyS0
PID hash table entries: 4096 (order: 12, 131072 bytes)
HWRPB cycle frequency bogus.  Estimated 462428619 Hz
Using epoch = 1952
Console: colour dummy device 80x25
Dentry cache hash table entries: 262144 (order: 8, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 7, 1048576 bytes)
Memory: 1024128k/1047736k available (1886k kernel code, 21176k reserved, 536k 
data, 312k init)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 8192 bytes)
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like 
an initrd
Freeing initrd memory: 6264k freed
NET: Registered protocol family 16
EISA bus registered
pci: enabling save/restore of SRM state
Linux Plug and Play Support v0.97 (c) Adam Belay
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 8192 bytes)
devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
Initializing Cryptographic API
Activating ISA DMA hang workarounds.
isapnp: Scanning for PnP cards...
isapnp: No Plug  Play device found
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 36 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
mice: PS/2 mouse device common for all mice
atkbd.c: keyboard reset failed on isa0060/serio1
atkbd.c: keyboard reset failed on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 131072 bind 65536)
NET: Registered protocol family 8
NET: 

Re: hung DS10 - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Norbert Tretkowski
* Toni L. Harbaugh-Blackford [Contr] wrote:
 ERROR: SCSI host `isp1020' has no error handling
 ERROR: This is not a safe way to run your SCSI host
 ERROR: The error handling must be added to this driver
 fc00015d7df8  fffc0038c500 fffc0035e920
fffc0035e920 fc003fe0c000 fffc0035e920 fc003fe0c000
fc00 fc00015d7e40 fc00015d7e40 fc003fe0c000
fc5a4500 fc003fe0c000 fffc0035208c fffc0035e920
fc5a4500 fffc0035e920 fffc002ec04c fffc0035e920
fc5a4500 fffc0035e9f0 fc5a4500 fc5a48e8
 Trace:
 [fc34e0c4] sys_init_module+0x284/0x3e0
 [fc310b34] entSys+0xa4/0xc0

Could you please retry it again with the qla1280 driver? This should
fix that problem.

Norbert


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: hung DS10 - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Jay Estabrook
On Fri, Feb 04, 2005 at 06:01:28PM +0100, Norbert Tretkowski wrote:
 * Toni L. Harbaugh-Blackford [Contr] wrote:
  ERROR: SCSI host `isp1020' has no error handling
  ERROR: This is not a safe way to run your SCSI host
  ERROR: The error handling must be added to this driver
  fc00015d7df8  fffc0038c500 fffc0035e920
 fffc0035e920 fc003fe0c000 fffc0035e920 fc003fe0c000
 fc00 fc00015d7e40 fc00015d7e40 fc003fe0c000
 fc5a4500 fc003fe0c000 fffc0035208c fffc0035e920
 fc5a4500 fffc0035e920 fffc002ec04c fffc0035e920
 fc5a4500 fffc0035e9f0 fc5a4500 fc5a48e8
  Trace:
  [fc34e0c4] sys_init_module+0x284/0x3e0
  [fc310b34] entSys+0xa4/0xc0
 
 Could you please retry it again with the qla1280 driver? This should
 fix that problem.

It alread DID try the qla1280 driver (look at the log again).

I think the problem may be that the /etc/modules.conf still has the
qlogicisp driver required, and it gets loaded and causes problems
because the device has already been claimed by the qla1280 driver.

 --Jay++

---
Jay A EstabrookHPTC - LINUX support
Hewlett-Packard Company - ZKO2-3/N30   (603) 884-0301
110 Spit Brook Road, Nashua NH 03062   [EMAIL PROTECTED]
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: hung DS10 - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Toni L. Harbaugh-Blackford [Contr]

On Fri, 4 Feb 2005, Jay Estabrook wrote:

   On Fri, Feb 04, 2005 at 06:01:28PM +0100, Norbert Tretkowski wrote:
* Toni L. Harbaugh-Blackford [Contr] wrote:
 ERROR: SCSI host `isp1020' has no error handling
 ERROR: This is not a safe way to run your SCSI host
 ERROR: The error handling must be added to this driver
 fc00015d7df8  fffc0038c500 fffc0035e920
fffc0035e920 fc003fe0c000 fffc0035e920 
fc003fe0c000
fc00 fc00015d7e40 fc00015d7e40 
fc003fe0c000
fc5a4500 fc003fe0c000 fffc0035208c 
fffc0035e920
fc5a4500 fffc0035e920 fffc002ec04c 
fffc0035e920
fc5a4500 fffc0035e9f0 fc5a4500 
fc5a48e8
 Trace:
 [fc34e0c4] sys_init_module+0x284/0x3e0
 [fc310b34] entSys+0xa4/0xc0
   
Could you please retry it again with the qla1280 driver? This should
fix that problem.
  
   It alread DID try the qla1280 driver (look at the log again).
  
   I think the problem may be that the /etc/modules.conf still has the
   qlogicisp driver required, and it gets loaded and causes problems
   because the device has already been claimed by the qla1280 driver.

I have no references to any scsi drivers in my /etc/modules.conf.  Norbert
suggested a change to mkinitrd and rebuild my initrd.img, which I did
but this did not work.

This section of the log actually looks almost exactly like my *good* boot
on 2.6.8-1, except that the 2.6.8-1 boot keeps on going.

  
--Jay++
  
   ---
   Jay A EstabrookHPTC - LINUX support
   Hewlett-Packard Company - ZKO2-3/N30   (603) 884-0301
   110 Spit Brook Road, Nashua NH 03062   [EMAIL PROTECTED]
   ---
  
  
   --
   To UNSUBSCRIBE, email to [EMAIL PROTECTED]
   with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
  

---
Toni Harbaugh-Blackford   [EMAIL PROTECTED]
System Administrator
Advanced Biomedical Computing Center (ABCC)
National Cancer Institute
Contractor - SAIC/Frederick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: hung DS10 - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Jay Estabrook
On Fri, Feb 04, 2005 at 09:23:54AM -0500, Toni L. Harbaugh-Blackford [Contr] 
wrote:

 qla1280: QLA1040 found on PCI bus 0, dev 15
 scsi(1:0): Resetting SCSI BUS
 scsi1 : QLogic QLA1040 PCI to SCSI Host Adapter
Firmware version:  7.65.00, Driver version 3.25
   Vendor: COMPAQModel: BD036659CCRev: 3B00
   Type:   Direct-Access  ANSI SCSI revision: 03
 scsi(1:0:0:0): Sync: period 10, offset 12, Wide, Tagged queuing: depth 255

The above are indication that the qla1280 driver has found the controller
and recognized the disk on the bus. It sees the chipset as 1040, which is
the most common found installed on factory DS10s.

 ERROR: SCSI host `isp1020' has no error handling
 ERROR: This is not a safe way to run your SCSI host
 ERROR: The error handling must be added to this driver
 fc00015d7df8  fffc0038c500 fffc0035e920
fffc0035e920 fc003fe0c000 fffc0035e920 fc003fe0c000
fc00 fc00015d7e40 fc00015d7e40 fc003fe0c000
fc5a4500 fc003fe0c000 fffc0035208c fffc0035e920
fc5a4500 fffc0035e920 fffc002ec04c fffc0035e920
fc5a4500 fffc0035e9f0 fc5a4500 fc5a48e8
 Trace:
 [fc34e0c4] sys_init_module+0x284/0x3e0
 [fc310b34] entSys+0xa4/0xc0

These messages are triggered by invocation of the old qlogicisp driver;
they are meant to nag the author into providing a driver with the
requested level of error handling, which will most likely never happen
since there is no longer an author, or one who wishes to do so... :-\

 qlogicisp : new isp1020 revision ID (5)
 scsi2 : QLogic ISP1020 SCSI on PCI bus 00 device 78 irq 39 I/O base 0x8400

Obviously the qlogicisp driver is attempting to probe/scan for controllers
it handles, and it has found a 1040 (aka a 1020 rev 5 chip).

It identifies the controller it has found as device 78; the 78 is
really a (hex) device/function pair, constructed via:

#define PCI_DEVFN(slot,func)slot)  0x1f)  3) | ((func)  0x07))

and thus we can see, the slot it is in is 0x0f or decimal 15, so it is
the SAME device that the qla1280 driver has already claimed!

This, I believe, it the cause of the hang, as you've now got 2 drivers
laying claim to the same device...

Now, I believe both the qla1280 and qlogicisp driver must be coming
from the INITRD, as already suggested; do you have a log of what
drivers were placed into the INITRD when you rebuilt it?

Regardless, you've got to find a way to prevent both drivers from
being present.

Good luck.

 --Jay++

---
Jay A EstabrookHPTC - LINUX support
Hewlett-Packard Company - ZKO2-3/N30   (603) 884-0301
110 Spit Brook Road, Nashua NH 03062   [EMAIL PROTECTED]
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



loadmodules file in initrd.img contains 'modprobe qlogicisp' - WAS: Please test new kernel-image-2.6.10-alpha packages (fwd)

2005-02-04 Thread Toni L. Harbaugh-Blackford [Contr]
Norbert-

On Fri, 4 Feb 2005, Norbert Tretkowski wrote:

  
   - s/^isp1020$/qlogicisp/; t
   + s/^isp1020$/qla1280/; t
  
   So, it's just replacing 'qlogicisp' with 'qla1280', then rebuild the
   initrd[0] and reboot.
  
   Norbert
  
   [0]: mkinitrd -o /boot/initrd-2.6.10-1-generic 
/lib/modules/initrd-2.6.10-1-generic/
  

I mounted the image to the loopback device, and found that the 'loadmodules'
file *still* contains qlogicisp:

fchelp:/mnt/tmp# cat loadmodules
modprobe -k  tgafb  /dev/null 21
modprobe -k  fbcon 2 /dev/null
modprobe -k  unix 2 /dev/null
modprobe -k  sym53c8xx
modprobe -k  qla1280
modprobe -k  qlogicisp
modprobe -k  sd_mod

Could this be what is causing the problem?

Can I remove it by-hand from the 'loadmodules' file (via loopback), or will
this break things?

---
Toni Harbaugh-Blackford   [EMAIL PROTECTED]
System Administrator
Advanced Biomedical Computing Center (ABCC)
National Cancer Institute
Contractor - SAIC/Frederick


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



loadmodules file was part of problem, but qlogicisp 'detected' during boot - WAS: Please test new kernel-image-2.6.10-alpha packages

2005-02-04 Thread Toni L. Harbaugh-Blackford [Contr]
Folks-

The loadmodules file in the initrd.img was causing the hang.  I modified
/usr/sbin/mkinitrd to change qlogicisp to qla1280 before writing out
the file.  This put two qla1280 entries in the file, but it seemed ok.

However, I am not out of the woods yet.  qlogicisp rears it's ugly
head again later, which puts the disk on that card offline.  Below is
the key section in the log; note the line about 'Detecting hardware',
where the qlogicisp is loaded *again*.  Now how do I stop the qlogicisp
from being detected during boot?  This must be coming from a file, but
it is not in my /etc/modules.conf.  Where should I look for the reference?

.
.
.
rtc: Digital UNIX epoch (1952) detected
Real Time Clock Driver v1.12
System time was Fri Feb  4 19:44:03 UTC 2005.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Fri Feb  4 19:44:05 UTC 2005.
Calculating module dependencies... done.
Loading modules...
ide-cd
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide-detect
FATAL: Module ide_detect not found.
sd_mod
All modules loaded.
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: [EMAIL PROTECTED]
Creating device-mapper devices...done.
Starting crypto disks:.
Checking all file systems...
fsck 1.35 (28-Feb-2004)
/dev/sde4: clean, 41/32256 files, 34548/129024 blocks
/home: clean, 60/932064 files, 247345/1863321 blocks (check in 5 mounts)
/tmp: clean, 13/62592 files, 11998/125000 blocks
/dev/sde6: clean, 2310/131072 files, 80622/262144 blocks
Setting kernel variables ...
... done.
Mounting local filekjournald starting.  Commit interval 5 seconds
systems...
EXT3 FS on sdd6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdd4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sde6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
/dev/sde4 on /boot type ext2 (rw)
/dev/sdd6 on /home type ext3 (rw)
/dev/sdd4 on /tmp type ext3 (rw)
/dev/sde6 on /var type ext3 (rw)
Cleaning /tmp /var/run /var/lock.
Detecting hardware: tulip ncr53c8xx qlogicisp
Loading tulip module.
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) 
block.
tulip0:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) 
block.
tulip0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
tulip0:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) 
block.
eth0: Digital DS21143 Tulip rev 65 at fd01fc008800, 08:00:2B:86:71:2D, IRQ 
29.
tulip1:  EEPROM default media type Autosense.
tulip1:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) 
block.
tulip1:  Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) 
block.
tulip1:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
tulip1:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) 
block.
eth1: Digital DS21143 Tulip rev 65 at fd01fc008880, 08:00:2B:86:71:2C, IRQ 
30.
Skipping unavailable/built-in ncr53c8xx module.
Loading qlogicisp module.
ERROR: SCSI host `isp1020' has no error handling
ERROR: This is not a safe way to run your SCSI host
ERROR: The error handling must be added to this driver
fc003f0fbdf8 fc003ebf7ec0 fffc0038c500 fffc004b4920
   fffc004b4920 fc003fe0c000 fffc004b4920 fc003fe0c000
   fc00 fc003f0fbe40 fc003f0fbe40 fc003fe0c000
   fc5a4500 fc003fe0c000 fffc004a808c fffc004b4920
   fc5a4500 fffc004b4920 fffc0038204c fffc004b4920
   fc5a4500 fffc004b49f0 fc5a4500 fc5a48e8
Trace:
[fc34e0c4] sys_init_module+0x284/0x3e0
[fc310b34] entSys+0xa4/0xc0

qlogicisp : new isp1020 revision ID (5)
scsi2 : QLogic ISP1020 SCSI on PCI bus 00 device 78 irq 39 I/O base 0x8400
qla1280: Status Entry invalid handle
scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 0 
lun 0
qla1280: Status Entry invalid handle
scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 1 
lun 0
qla1280: Status Entry invalid handle
scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 2 
lun 0
qla1280: Status Entry invalid handle
scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 3 
lun 0
qla1280: Status Entry invalid handle
.
.
.

The system continues up, but attempts to work with the drive cause
a kernel panic.

How do I stop the qlogicisp from being detected?

Thanks again,
Toni

---
Toni Harbaugh-Blackford   [EMAIL PROTECTED]

Re: loadmodules file in initrd.img contains 'modprobe qlogicisp' - WAS: Please test new kernel-image-2.6.10-alpha packages (fwd)

2005-02-04 Thread Tyson Whitehead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On February 4, 2005 02:12 pm, Toni L. Harbaugh-Blackford [Contr] wrote:
 I mounted the image to the loopback device, and found that the
 'loadmodules' file *still* contains qlogicisp:

 fchelp:/mnt/tmp# cat loadmodules
 modprobe -k  tgafb  /dev/null 21
 modprobe -k  fbcon 2 /dev/null
 modprobe -k  unix 2 /dev/null
 modprobe -k  sym53c8xx
 modprobe -k  qla1280
 modprobe -k  qlogicisp
 modprobe -k  sd_mod

 Can I remove it by-hand from the 'loadmodules' file (via loopback), or will
 this break things?

Jumping into the middle of things here.  How about if you just list the 
modules you need in /etc/mkinitrd/modules (i.e. sd_mod, qla1280, and 
whatever your root filesystem is) and set ROOT= and MODULES=dep in 
/etc/mkinitrd/mkinitrd.conf (disables auto determination of the modules) 
and then reinstall the kernel image (i.e., rebuild the initrd file).

- -T

- -- 
 Tyson Whitehead  (-twhitehe at uwo.ca -- WSC-)
 Computer EngineerDept. of Applied Mathematics,
 Graduate Student- Applied MathematicsUniversity of Western Ontario,
 GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCA9qXRXbLmIoqtdgRAjB6AJ47ElHFGtekDq9jV9fO7/mmU6XJHwCg6wF0
T2Ym7WTLYinKwo+A9efmeig=
=ALxD
-END PGP SIGNATURE-


-- 
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

2005-02-03 Thread Michael Christy

I have tested these packages on UP2000 SMP with the following results:

1)  SMP kernel panics and boot and it looks like modules can not be loaded
for some reason.

2)  generic kernel boots and (almost )all hardware seems to work,
including my GTH raid controller, emu10k sound card, and Voodoo3 card in
DRI (great!).  Unfortunately, I also have no ps2 mouse at boot and must
insmod a ps2 module by hand to get my mouse working.  Additionally, the
onboard USB gets recognized but gives an error that irq 255 can not be
assigned.

This is the first 2.6 kernel that I have ever been able to boot on these
machines so that is progress.  However, without SMP this is not so useful
to me at the moment.  If I can get and SMP kernel runing I will be very
happy.  Thanks to those working on this.


-Eric



On Fri, 28 Jan 2005, Patrick Caulfield wrote:

 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]




-- 
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

2005-01-28 Thread Patrick Caulfield
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: Please test new kernel-image-2.6.10-alpha packages

2005-01-26 Thread Carcharoth
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.

Thanks,


-- 
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

2005-01-26 Thread Tim Cutts
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.

Tim

-- 
Dr Tim Cutts
Informatics Systems Group
Wellcome Trust Sanger Institute, Hinxton, Cambridge, CB10 1SA, UK


-- 
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

2005-01-26 Thread Jim Crilly
Norbert Tretkowski wrote:
With the latest upload of kernel-source-2.6.10 I was finally able to
create working (for me) kernel-image-2.6.10-alpha packages. Please
test them, especially when you're using a Qlogic ISP1020/1040 SCSI
controller, which is now supported by the qla1280 driver. You also
need to update initrd-tools if you want to use the qla1280 driver with
your ISP1020/1040 controller.
,[ sources.list ]
| deb http://people.debian.org/~nobse/kernel/alpha/kernel-image-2.6.10-alpha/ ./
| deb http://people.debian.org/~nobse/kernel/initrd-tools/ ./
`
My patch for initrd-tools isn't perfect currently, you aren't able to
build a new initrd for a 2.4 kernel when running a 2.6 kernel with the
qla1280 driver. I'll provide a better patch soon.
Norbert

I haven't tried these packages myself yet, but I'm wondering if anyone has 
tested USB with this kernel? I know it didn't work for me with 
2.6.8-1-generic but it works fine with 2.4.27-1-generic. The box is a 
PWS600au and the USB controller is :

:00:07.3 USB Controller: Contaq Microsystems 82c693 (prog-if 10 [OHCI])
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at 09a74000 (32-bit, non-prefetchable) [size=4K]
--
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

2005-01-25 Thread Uwe Schindler
if ext3 is working without oops I could make a test when I have time.
At 15:23 23.01.2005, you wrote:
With the latest upload of kernel-source-2.6.10 I was finally able to
create working (for me) kernel-image-2.6.10-alpha packages. Please
test them, especially when you're using a Qlogic ISP1020/1040 SCSI
controller, which is now supported by the qla1280 driver. You also
need to update initrd-tools if you want to use the qla1280 driver with
your ISP1020/1040 controller.
,[ sources.list ]
| deb 
http://people.debian.org/~nobse/kernel/alpha/kernel-image-2.6.10-alpha/ ./
| deb http://people.debian.org/~nobse/kernel/initrd-tools/ ./
`

My patch for initrd-tools isn't perfect currently, you aren't able to
build a new initrd for a 2.4 kernel when running a 2.6 kernel with the
qla1280 driver. I'll provide a better patch soon.
Norbert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de - http://www.schindlers-software.de
eMails: [EMAIL PROTECTED] (private); [EMAIL PROTECTED] (company)
Tel./Fax: +49 700 PCLATEIN (+49 700 72528346)
Schindlers Software - Home of Schindlers PC-LATEIN 3.10
DIE Software zum Lateinlernen!  

--
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

2005-01-25 Thread Norbert Tretkowski
* Uwe Schindler wrote:
 if ext3 is working without oops I could make a test when I have time.

It's working without oops on my machines, and I already got positive
feedback about the new kernel-images.

Norbert


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]