Menu
▾
▴
linux-apus-devel
|
From: Wilfried C. <wca...@no...> - 2004-06-11 15:52:37
|
Hi,
I try to use the 2.4.25 kernel but at boot time, i have a problem with the
Cyberstorm SCSI controler which works well in 2.4.22 (except for the cdrom).
Here is the dmesg output:
Memory BAT mapping: BAT2=64Mb, BAT3=32Mb, residual: 31Mb
Total memory = 127MB; using 256kB for hash table (at c0300000)
Linux version 2.4.25 (willy@SuperAmiga) (gcc version 2.95.4 20011002 (Debian
prerelease)) #1 ven jun 11 14:09:58 CEST 2004
Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE KEYBOARD
MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3
On node 0 totalpages: 32640
zone(0): 32640 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/sdb2 nobats 60nsram 3
video=clgen:mode:1024x768 debug=mem
ioremap: fffc0000 (00001000) -> fdfff000
ioremap: fffe0000 (00001000) -> fdffe000
APUS: BATs=0, BUS=67MHz, RAM=60ns, PCI bridge=1
time_init: decrementer frequency = 16.670190 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 399.76 BogoMIPS
Memory: 125928k available (1832k kernel code, 688k data, 304k init, 0k
highmem)
Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Memory resource not set for host bridge 0
PCI: Cannot allocate resource region 2 of device 00:01.0
PCI: moved device 00:01.0 resource 2 (200) to e0000000
Zorro: Probing AutoConfig expansion devices: 7 devices
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
parport0: Amiga built-in port using irq
clgen: Driver for Cirrus Logic based graphic boards, v1.9.9.1
clgenfb: couldn't find Cirrus Logic PCI device
Console: switching to colour frame buffer device 80x25
fb0: Amiga AGA frame buffer device, using 1280K of video memory
ioremap: fffc0000 (00001000) -> c801a000
ioremap: fffe0000 (00001000) -> c801c000
ioremap: e0000000 (00800000) -> c801e000
ioremap: ef010000 (00010000) -> c881f000
fb1: CVisionPPC/BVisionPPC (Permedia2), using 8192K of video memory.
pty: 256 Unix98 ptys configured
Amiga-builtin serial driver version 4.30
ttyS00 is the amiga builtin serial port
Amiga mouse installed.
Generic RTC Driver v1.07
FD: probing units
found fd0
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit
encapsulation enabled).
CSLIP: code copyright 1989 Regents of the University of California.
SLIP linefill/keepalive option.
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
No Ariadne II or X-Surf ethernet card found.
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: Gayle IDE interface (A4000 style)
Probing IDE interface ide0...
hda: WDC AC28400R, ATA DISK drive
hdb: IOMEGA ZIP 250 ATAPI, ATAPI FLOPPY drive
ide0 at 0x80dd2020 on irq 12
hda: attached ide-disk driver.
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: host protected area => 1
hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=16383/16/63
hdb: attached ide-floppy driver.
hdb: No disk in drive
hdb: 244736kB, 239/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
Partition check:
hda: RDSK hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11
SCSI subsystem driver Revision: 1.00
ncr53c8xx: 53c770 detected
ncr53c770-0: rev=0x00, base=0xf40000, io_port=0x0, irq=12
ncr53c770-0: using memory mapped IO at virtual address 0x80f40000
ncr53c770-0: ID 7, Fast-20, Parity Checking
ncr53c770-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/c0/21/00/00/04
ncr53c770-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/c0/21/00/00/04
ncr53c770-0: on-chip RAM at 0xf41000
ncr53c770-0: resetting, command processing suspended for 2 seconds
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
scsi0 : ncr53c770-3.4.3-20010212
ncr53c770-0: command processing resumed
Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.01
Type: CD-ROM ANSI SCSI revision: 02
Vendor: IBM Model: DDRS-34560D Rev: DC1B
Type: Direct-Access ANSI SCSI revision: 02
Vendor: IBM Model: DDYS-T09170N Rev: S96H
Type: Direct-Access ANSI SCSI revision: 03
Attached scsi disk sda at scsi0, channel 0, id 8, lun 0
Attached scsi disk sdb at scsi0, channel 0, id 9, lun 0
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sda: 8925000 512-byte hdwr sectors (4570 MB)
sda:<6>ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=31 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
SCSI disk error : host 0 channel 0 id 8 lun 0 return code = 27070000
I/O error: dev 08:00, sector 0
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=36 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
SCSI disk error : host 0 channel 0 id 8 lun 0 return code = 27070000
I/O error: dev 08:00, sector 2
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=41 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
SCSI disk error : host 0 channel 0 id 8 lun 0 return code = 27070000
I/O error: dev 08:00, sector 4
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=47 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
SCSI disk error : host 0 channel 0 id 8 lun 0 return code = 27070000
I/O error: dev 08:00, sector 0
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=52 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<8,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
ncr53c770-0-<8,0>: extended error 15.
ncr53c770-0-<8,0>: COMMAND FAILED (89 0) @c7e80000.
SCSI disk error : host 0 channel 0 id 8 lun 0 return code = 27070000
I/O error: dev 08:00, sector 2
unable to read partition table
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
SCSI device sdb: 17916240 512-byte hdwr sectors (9173 MB)
sdb:<6>ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=61 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
SCSI disk error : host 0 channel 0 id 9 lun 0 return code = 27070000
I/O error: dev 08:10, sector 0
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=66 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
SCSI disk error : host 0 channel 0 id 9 lun 0 return code = 27070000
I/O error: dev 08:10, sector 2
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=71 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
SCSI disk error : host 0 channel 0 id 9 lun 0 return code = 27070000
I/O error: dev 08:10, sector 4
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=77 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
SCSI disk error : host 0 channel 0 id 9 lun 0 return code = 27070000
I/O error: dev 08:10, sector 0
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
scsi0 channel 0 : resetting for second half of retries.
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=82 reset_flags=1 serial_number=0
serial_number_at_timeout=0
ncr53c770-0: resetting, command processing suspended for 2 seconds
scsi0: device driver called scsi_done() for a synchronous reset.
ncr53c770-0: restart (scsi reset).
ncr53c770-0: enabling clock multiplier
ncr53c770-0: Downloading SCSI SCRIPTS.
ncr53c770-0: command processing resumed
ncr53c770-0-<9,*>: WIDE SCSI (16 bit) enabled.
ncr53c770-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
ncr53c770-0-<9,0>: extended error 15.
ncr53c770-0-<9,0>: COMMAND FAILED (89 0) @c7e80800.
SCSI disk error : host 0 channel 0 id 9 lun 0 return code = 27070000
I/O error: dev 08:10, sector 2
unable to read partition table
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "sdb2" or 08:12
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:12
<0>Rebooting in 180 seconds..<<<<<<<<<<<<<<<<<<<<
Is it possible to fix this pb ?
Thanks,
Willy.
|
|
From: Sven L. <sve...@wa...> - 2004-06-11 17:03:59
|
On Fri, Jun 11, 2004 at 05:40:04PM +0200, Wilfried Catteau wrote: > Hi, > > I try to use the 2.4.25 kernel but at boot time, i have a problem with the > Cyberstorm SCSI controler which works well in 2.4.22 (except for the cdrom). > Here is the dmesg output: BTW, are you usingh the debian kernel apckage ? If yes, please fill a bug repor,t if not, well, if you run debian give it a try. Friendly, Sven Luther |
|
From: Wilfried C. <wca...@no...> - 2004-06-11 18:03:00
|
Hi, > > > > I try to use the 2.4.25 kernel but at boot time, i have a problem with > > the Cyberstorm SCSI controler which works well in 2.4.22 (except for the > > cdrom). Here is the dmesg output: > > BTW, are you usingh the debian kernel apckage ? If yes, please fill a > bug repor,t if not, well, if you run debian give it a try. I use the debian woody but not their kernel package: i take the sources from linux-apus cvs repository and compile them. Willy. |
|
From: Sven L. <sve...@wa...> - 2004-06-12 02:09:53
|
On Fri, Jun 11, 2004 at 07:50:26PM +0200, Wilfried Catteau wrote: > Hi, > > > > > > > I try to use the 2.4.25 kernel but at boot time, i have a problem with > > > the Cyberstorm SCSI controler which works well in 2.4.22 (except for the > > > cdrom). Here is the dmesg output: > > > > BTW, are you usingh the debian kernel apckage ? If yes, please fill a > > bug repor,t if not, well, if you run debian give it a try. > > I use the debian woody but not their kernel package: i take the sources from > linux-apus cvs repository and compile them. Bah. another one of those.Would you at least give them a try ( the one in ssid/sarge though, we care little for woody at this point, altough i pass lot of time building security upgrades nobody uses anyway ), and fill bug reports if it doesn't work ? I took over maintainership, but have no apus hardware anymore. Friendly, Sven Luther |
|
From: Wilfried C. <wca...@no...> - 2004-06-13 16:51:29
|
Le Samedi 12 Juin 2004 04:22, Sven Luther a =E9crit : > > > > I try to use the 2.4.25 kernel but at boot time, i have a problem > > > > with the Cyberstorm SCSI controler which works well in 2.4.22 (ex= cept > > > > for the cdrom). Here is the dmesg output: > > > > > > BTW, are you usingh the debian kernel apckage ? If yes, please fill= a > > > bug repor,t if not, well, if you run debian give it a try. > > > > I use the debian woody but not their kernel package: i take the sourc= es > > from linux-apus cvs repository and compile them. > > Bah. another one of those.Would you at least give them a try ( the one > in ssid/sarge though, we care little for woody at this point, altough i > pass lot of time building security upgrades nobody uses anyway ), and > fill bug reports if it doesn't work ? I took over maintainership, but > have no apus hardware anymore. I tried the "kernel-image-2.4.25-apus_2.4.25-2_powerpc.deb" package but i= t=20 doesn't work: i have this message from the bootstrap program: "unable to read exec header from kernel file". Has someone already installed it to know if this pb is relative to my Ami= ga? Willy |
|
From: Sven L. <sve...@wa...> - 2004-06-14 04:14:49
|
On Sun, Jun 13, 2004 at 06:36:04PM +0200, Wilfried Catteau wrote: > Le Samedi 12 Juin 2004 04:22, Sven Luther a écrit : > > > > > > I try to use the 2.4.25 kernel but at boot time, i have a problem > > > > > with the Cyberstorm SCSI controler which works well in 2.4.22 (except > > > > > for the cdrom). Here is the dmesg output: > > > > > > > > BTW, are you usingh the debian kernel apckage ? If yes, please fill a > > > > bug repor,t if not, well, if you run debian give it a try. > > > > > > I use the debian woody but not their kernel package: i take the sources > > > from linux-apus cvs repository and compile them. > > > > Bah. another one of those.Would you at least give them a try ( the one > > in ssid/sarge though, we care little for woody at this point, altough i > > pass lot of time building security upgrades nobody uses anyway ), and > > fill bug reports if it doesn't work ? I took over maintainership, but > > have no apus hardware anymore. > > I tried the "kernel-image-2.4.25-apus_2.4.25-2_powerpc.deb" package but it > doesn't work: i have this message from the bootstrap program: > "unable to read exec header from kernel file". Well, could you fill a (severe i think) bug report about this ? > Has someone already installed it to know if this pb is relative to my Amiga? Well, nobody has even bothered to test it here, despite me asking for this test. Keep in mind that some effort goes into maintaining the debian apus kernels, both for unstable and testing (which should move to 2.4.26 or some common kernel for all arches) as well as security updates of stable, so if nobody uses the debian kernel on apus, it may make sense to remove it. Also, this would mean that there would be no debian-installer support for apus in sarge. There is code, and i made sure the installer is built, but nobody ever tested it, so ... I somehow have the feeling that there are maybe 10 users left or less, and that they don't really care about debian kernel level support, so i wonder if the time spent on it (by me mostly) is worth it. If someone from the apus community would step forward, and work with me to test and fix the kernel, this would be great, and at least test the debian-installer once. Friendly, Sven Luther |
|
From: Krystian <cah...@po...> - 2004-06-14 13:51:44
|
W li=B6cie z pon, 14-06-2004, godz. 06:28, Sven Luther pisze:=20 > On Sun, Jun 13, 2004 at 06:36:04PM +0200, Wilfried Catteau wrote: > > Le Samedi 12 Juin 2004 04:22, Sven Luther a =E9crit : > >=20 > > > > > > I try to use the 2.4.25 kernel but at boot time, i have a p= roblem > > > > > > with the Cyberstorm SCSI controler which works well in 2.4.= 22 (except > > > > > > for the cdrom). Here is the dmesg output: > > > > > > > > > > BTW, are you usingh the debian kernel apckage ? If yes, pleas= e fill a > > > > > bug repor,t if not, well, if you run debian give it a try. > > > > > > > > I use the debian woody but not their kernel package: i take the= sources > > > > from linux-apus cvs repository and compile them. > > > > > > Bah. another one of those.Would you at least give them a try ( th= e one > > > in ssid/sarge though, we care little for woody at this point, alt= ough i > > > pass lot of time building security upgrades nobody uses anyway ),= and > > > fill bug reports if it doesn't work ? I took over maintainership,= but > > > have no apus hardware anymore. > >=20 > > I tried the "kernel-image-2.4.25-apus_2.4.25-2_powerpc.deb" package= but it=20 > > doesn't work: i have this message from the bootstrap program: > > "unable to read exec header from kernel file". >=20 > Well, could you fill a (severe i think) bug report about this ?=20 >=20 > > Has someone already installed it to know if this pb is relative to = my Amiga? >=20 > Well, nobody has even bothered to test it here, despite me asking for > this test. Keep in mind that some effort goes into maintaining the > debian apus kernels, both for unstable and testing (which should move= to > 2.4.26 or some common kernel for all arches) as well as security upda= tes > of stable, so if nobody uses the debian kernel on apus, it may make > sense to remove it. Also, this would mean that there would be no > debian-installer support for apus in sarge. There is code, and i made > sure the installer is built, but nobody ever tested it, so ... I'll try to build it and test it when I get home and I have access to A= PUS hardware. Unfortunately It'll be about the beginning of July. > I somehow have the feeling that there are maybe 10 users left or less= , > and that they don't really care about debian kernel level support, so= i > wonder if the time spent on it (by me mostly) is worth it. If someone > from the apus community would step forward, and work with me to test = and > fix the kernel, this would be great, and at least test the > debian-installer once. I downloaded debian packages kernel-source-2.4.25 and kernel-patch-2.4.25-apus, however I didn't manage to cross compile it. I'll give a second try soon. There was no problem during cross-compiling sources from CVS. Regards Krystian Bac=B3awski |
|
From: Sven L. <sve...@wa...> - 2004-06-14 11:53:16
|
On Mon, Jun 14, 2004 at 09:13:00AM +0200, Krystian Bac?awski wrote: > W li?cie z pon, 14-06-2004, godz. 06:28, Sven Luther pisze: > > On Sun, Jun 13, 2004 at 06:36:04PM +0200, Wilfried Catteau wrote: > > > Le Samedi 12 Juin 2004 04:22, Sven Luther a écrit : > > > > > > > > > > I try to use the 2.4.25 kernel but at boot time, i have a problem > > > > > > > with the Cyberstorm SCSI controler which works well in 2.4.22 (except > > > > > > > for the cdrom). Here is the dmesg output: > > > > > > > > > > > > BTW, are you usingh the debian kernel apckage ? If yes, please fill a > > > > > > bug repor,t if not, well, if you run debian give it a try. > > > > > > > > > > I use the debian woody but not their kernel package: i take the sources > > > > > from linux-apus cvs repository and compile them. > > > > > > > > Bah. another one of those.Would you at least give them a try ( the one > > > > in ssid/sarge though, we care little for woody at this point, altough i > > > > pass lot of time building security upgrades nobody uses anyway ), and > > > > fill bug reports if it doesn't work ? I took over maintainership, but > > > > have no apus hardware anymore. > > > > > > I tried the "kernel-image-2.4.25-apus_2.4.25-2_powerpc.deb" package but it > > > doesn't work: i have this message from the bootstrap program: > > > "unable to read exec header from kernel file". > > > > Well, could you fill a (severe i think) bug report about this ? > > > > > Has someone already installed it to know if this pb is relative to my Amiga? > > > > Well, nobody has even bothered to test it here, despite me asking for > > this test. Keep in mind that some effort goes into maintaining the > > debian apus kernels, both for unstable and testing (which should move to > > 2.4.26 or some common kernel for all arches) as well as security updates > > of stable, so if nobody uses the debian kernel on apus, it may make > > sense to remove it. Also, this would mean that there would be no > > debian-installer support for apus in sarge. There is code, and i made > > sure the installer is built, but nobody ever tested it, so ... > > I'll try to build it and test it when I get home and I have access to APUS hardware. > Unfortunately It'll be about the beginning of July. > > > I downloaded debian packages kernel-source-2.4.25 and > kernel-patch-2.4.25-apus, however I didn't manage to cross compile it. > I'll give a second try soon. > > There was no problem during cross-compiling sources from CVS. Well, we are not running Gentoo, the package don't need compiling, just testing, they are already built. Mmm, maybe the fact that i built them on my pegasos could have some influence. Friendly, Sven Luther |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X