Menu
▾
▴
linux-apus-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
| 2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
| 2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
| 2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Geert U. <ge...@li...> - 2000-07-06 21:02:26
|
On 6 Jul 2000, Jes Sorensen wrote:
> >>>>> "Geert" == Geert Uytterhoeven <ge...@li...> writes:
>
> Geert> Aha, arch/ppc/config.in does `source drivers/scsi/Config.in',
> Geert> while arch/m68k/config.in has the whole list of Amiga supported
> Geert> SCSI cards. Someone needs to move them to
> Geert> drivers/scsi/Config.in, since they depend on CONFIG_ZORRO
> Geert> and/or CONFIG_AMIGA anyway.
>
> Just irritates me that every user has to deselect a pile of
> unsupported ISA/PCI drivers.
These should be inside CONFIG_{ISA,PCI}, or done using
`dep_{bool,tristate} * $CONFIG_{ISA,PCI}'. Anyone volunteering to do the clean
up?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Jes S. <je...@li...> - 2000-07-06 17:12:11
|
>>>>> "Geert" == Geert Uytterhoeven <ge...@li...> writes: Geert> Aha, arch/ppc/config.in does `source drivers/scsi/Config.in', Geert> while arch/m68k/config.in has the whole list of Amiga supported Geert> SCSI cards. Someone needs to move them to Geert> drivers/scsi/Config.in, since they depend on CONFIG_ZORRO Geert> and/or CONFIG_AMIGA anyway. Just irritates me that every user has to deselect a pile of unsupported ISA/PCI drivers. Jes |
|
From: Michel <da...@re...> - 2000-07-06 15:15:10
|
Geert Uytterhoeven wrote: > > > > > Now I only need a driver for the GVP-II, and I shall switch to 2.3 > > > > > :-)) > > > > > > > > I thought we've had a driver for that card since ages? > > > > > > Sure, for 2.2.x. It does not seem to have made it into the 2.3 tree, yet. > > > > At least in Documentation/Configure.help, there's an entry for it... > > > > Maybe you'll have to edit the Makefile or Configure.in in drivers/scsi, or > > maybe you need to import some stuff from the latest m68k diffs... > > Aha, arch/ppc/config.in does `source drivers/scsi/Config.in', while > arch/m68k/config.in has the whole list of Amiga supported SCSI cards. > Someone needs to move them to drivers/scsi/Config.in, since they depend on > CONFIG_ZORRO and/or CONFIG_AMIGA anyway. Thanks for the hint Geert, this might bring back some drivers to APUS I guess :) Whoever does this should post the patch to the m68k list. Michel PS: Geert, could you somehow propagate APUS stuff to bitkeeper? -- Death is just Nature's way of saying, "Hey! You're not alive anymore!" ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Michel <da...@re...> - 2000-07-06 15:07:27
|
Glenn Hisdal wrote: > > Get the latest pppd, IIRC 2.3.11 is needed for 2.4 . > > I got 2.3.10-3 which was the latest I could find on ftp.linuxppc.org. > pppd now recognizes the ppp support, but is not able to access /dev/ttySx, > so I can't communicate with the modem. (Unable to access /dev/ttyS0 : No > such device). You either haven't compiled in serial port support or haven't loaded the module (amiserial.o). Michel -- There's no place like ~ ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Geert U. <ge...@li...> - 2000-07-06 14:32:26
|
On Thu, 6 Jul 2000, Michel Dänzer wrote:
> Frank Petzold wrote:
> > > > Now I only need a driver for the GVP-II, and I shall switch to 2.3
> > > > :-))
> > >
> > > I thought we've had a driver for that card since ages?
> >
> > Sure, for 2.2.x. It does not seem to have made it into the 2.3 tree, yet.
>
> At least in Documentation/Configure.help, there's an entry for it...
>
> Maybe you'll have to edit the Makefile or Configure.in in drivers/scsi, or
> maybe you need to import some stuff from the latest m68k diffs...
Aha, arch/ppc/config.in does `source drivers/scsi/Config.in', while
arch/m68k/config.in has the whole list of Amiga supported SCSI cards.
Someone needs to move them to drivers/scsi/Config.in, since they depend on
CONFIG_ZORRO and/or CONFIG_AMIGA anyway.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Glenn H. <gh...@c2...> - 2000-07-06 14:17:58
|
Hello, On 06-Jul-2000, Michel wrote: >> - I can't use the cybervision64 driver. It compiles without problems but >> it is not used by the kernel when I boot. >> bootstrap line: bootstrap --apus -k vmlinux root=/dev/hda7 >> video=cyber:800x600-8 60nsram debug=mem > ^^^^^ > Maybe the the name has changed or it isn't initialized (correctly) by the > upper fbdev layer anymore. Check drivers/video/fbcon.c (IIRC). I took a look, but I didn't understand much of it. Guess I'll have to leave this to someone that knows what to look for :) >> - pppd say that the kernel does not have PPP support although I did... > Get the latest pppd, IIRC 2.3.11 is needed for 2.4 . I got 2.3.10-3 which was the latest I could find on ftp.linuxppc.org. pppd now recognizes the ppp support, but is not able to access /dev/ttySx, so I can't communicate with the modem. (Unable to access /dev/ttyS0 : No such device). It works fine with kernel 2.2.10 of course... - glenn |
|
From: Michel <da...@re...> - 2000-07-06 09:07:52
|
Glenn Hisdal wrote:
> - I can't use the cybervision64 driver. It compiles without problems but it
> is not used by the kernel when I boot.
>
> bootstrap line: bootstrap --apus -k vmlinux root=/dev/hda7
> video=cyber:800x600-8 60nsram debug=mem
^^^^^
Maybe the the name has changed or it isn't initialized (correctly) by the
upper fbdev layer anymore. Check drivers/video/fbcon.c (IIRC).
> - pppd say that the kernel does not have PPP support although I did compile
> ppp support into the kernel. (My pppd version is 2.3.7, is it to old ?).
> It looks from the dmesg output that ppp support is there...
Get the latest pppd, IIRC 2.3.11 is needed for 2.4 .
> - I can't mount AFFS partitions.
> The system hangs when I try to do this.
Others have reported that as well - seems like the "fixed" AFFS only works on
i386 so far :-/
Michel
--
The computer revolution is over. The computers won.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
|
|
From: Michel <da...@re...> - 2000-07-06 08:58:36
|
Frank Petzold wrote: > > > Now I only need a driver for the GVP-II, and I shall switch to 2.3 > > > :-)) > > > > I thought we've had a driver for that card since ages? > > Sure, for 2.2.x. It does not seem to have made it into the 2.3 tree, yet. At least in Documentation/Configure.help, there's an entry for it... Maybe you'll have to edit the Makefile or Configure.in in drivers/scsi, or maybe you need to import some stuff from the latest m68k diffs... Michel -- True programmers never die, they just branch to an odd address. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Frank P. <fp...@zu...> - 2000-07-06 07:59:49
|
On Wed, Jul 05, 2000 at 02:36:06PM +0200, Geert Uytterhoeven wrote: > On Wed, 5 Jul 2000, Frank Petzold wrote: > > On Wed, Jul 05, 2000 at 09:50:05AM +0200, Michel Dänzer wrote: > > > Frank Petzold wrote: > > > > Now I only need a driver for the GVP-II, and I shall switch to 2.3 :-)) > > > > > > You first :) > > > > > > Please excuse my ignorance, is it a disk interface or what? > > > > I meant the GVP Series II SCSI controller card. My ZIP and Scanner are attached > > to it. > > I thought we've had a driver for that card since ages? Sure, for 2.2.x. It does not seem to have made it into the 2.3 tree, yet. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: Glenn H. <gh...@c2...> - 2000-07-05 20:39:47
|
Hi, I have tried to compile and boot the 2.4.0-test2 kernel. It compiles and boots, but there are some problems. I don't know if it's caused by wrong config or bugs in the kernel. Here's my problems: - I can't use the cybervision64 driver. It compiles without problems but it is not used by the kernel when I boot. bootstrap line: bootstrap --apus -k vmlinux root=/dev/hda7 video=cyber:800x600-8 60nsram debug=mem - pppd say that the kernel does not have PPP support although I did compile ppp support into the kernel. (My pppd version is 2.3.7, is it to old ?). It looks from the dmesg output that ppp support is there... - I can't mount AFFS partitions. The system hangs when I try to do this. Otherwise things seem ok so far. I will do some more testing later. Hopefully some of you can give me some help with my current problems. I won't be of much help when it comes to programming as my c knowledge is very limited. I've included the dmesg output and my .config file: Searching for SAVEKMSG magic... Found 3883 bytes at 0x001e0008 >>>>>>>>>>>>>>>>>>>> parse_bootinfo: unknown tag 0x8008 ignored parse_bootinfo: unknown tag 0x8009 ignored Total memory = 64MB; using 256kB for hash table (at c0200000) Linux version 2.4.0-test2 (ro...@gu...d) (gcc version 2.95.2 19991024 (release/franzo)) #5 Wed Jul 5 20:59:31 GMT 2000 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: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda7 video=cyber:800x600-8 60nsram debug=mem amiga_enable_irq: Trying to enable auto-vector IRQ 1 amiga_enable_irq: Trying to enable auto-vector IRQ 3 amiga_enable_irq: Trying to enable auto-vector IRQ 4 amiga_enable_irq: Trying to enable auto-vector IRQ 5 amiga_enable_irq: Trying to enable auto-vector IRQ 7 amiga_enable_irq: Trying to enable auto-vector IRQ 2 amiga_enable_irq: Trying to enable auto-vector IRQ 6 APUS: BATs=1, BUS=66MHz, RAM=60ns, PCI bridge=0 time_init: decrementer frequency = 990000000/60 Console: colour dummy device 80x25 Calibrating delay loop... 460.39 BogoMIPS Memory: 61188k available (1208k kernel code, 540k data, 80k init) [c0000000,c4000000] Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) kmem_create: Poisoning requested, but con given - bdev_cache Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) kmem_create: Poisoning requested, but con given - inode_cache POSIX conformance testing by UNIFIX Zorro: Probing AutoConfig expansion devices: 3 devices Linux NET4.0 for Linux 2.3 Based upon Swansea University Computer Society NET3.039 kmem_create: Poisoning requested, but con given - skbuff_head_cache NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 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 4096 bind 4096) Starting kswapd v1.6 amiga_insert_irq: Warning: dev_id of fb vertb handler is zero Console: switching to colour frame buffer device 80x25 fb0: Amiga AGA frame buffer device, using 1280K of video memory pty: 256 Unix98 ptys configured request_module[parport_lowlevel]: Root fs not mounted lp: driver loaded but no devices found RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: registered device at major 7 loop: enabling 8 loop devices Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide0: Gayle IDE interface (A4000 style) hda: probing with STATUS(0x50) instead of ALTSTATUS(0xe0) hda: WDC AC313000R, ATA DISK drive hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: CRD-8240B, ATAPI CDROM drive ide0 at 80dd2020 on irq 0x0000000c hda: 25429824 sectors (13020 MB) w/512KiB Cache, CHS=25228/16/63 hdb: ATAPI 24X CD-ROM drive, 128kB Cache Uniform CD-ROM driver Revision: 3.11 Partition check: hda: RDSK hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 Amiga mouse installed. PPP generic driver version 2.4.1 DMA sound driver installed, using 4 buffers of 32k. kmem_create: Forcing size word alignment - nfs_fh VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 80k init Warning: unable to open an initial console. nfs warning: mount version older than kernel amiga_disable_irq: Trying to disable auto-vector IRQ 0 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 nfsd: terminating on signal 9 Restarting system. <<<<<<<<<<<<<<<<<<<< /glenn |
|
From: Alan B. <al...@ms...> - 2000-07-05 16:18:44
|
hi, > But I don't think that we should encourage people to use the test kernels for > installing, should we? :-) of course not - but I will do the same for the non-test (ie the installer) kernel. alan |
|
From: Michel <da...@re...> - 2000-07-05 14:50:06
|
Sven LUTHER wrote: > > BTW what's the fs type of root.bin supposed to be? I can't mount it here. > > root.bin is just a compressed ext2 root image. > > dbootstrap does some gunzip & piping magic to mount it, but mv root.bin > root.bin.gz && gunzip root.bin.gz will do also. Aaah it worked now, thanks. > Do you have the same problem as me with the mounting of the rescue.bin image > (it is a vfat image) ? I can only test it on the i386 SuSE 6.4 here at work, and it mounts without problems. Michel -- It's not a bug, it's tradition! ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Sven L. <lu...@dp...> - 2000-07-05 14:39:08
|
On Wed, Jul 05, 2000 at 02:53:48PM +0200, Michel Dänzer wrote: > Sven LUTHER wrote: > > > i give the corrct place in the requester, and dbootstrap tries to loop mount > > the rescue.bin image to fetch the kernel and the modules, and fail. > > Should drivers.tgz be in rescue.bin? It's not. No it is supposed to be in driver-1.bin. > If the config.gz in rescue.bin is the config of the kernel you use, it does > indeed include the loopback device and vfat. thought so also, ... > > Now the strange thing, is that when i continue the installation stuff and > > reboot with the same kernel on the partition just installed from the base > > tarball, i can mount the rescue.bin image with the exact command given > > above. > > > > Thus i suspsect the problem lie with the root.bin image. or maybe the > > dbootstrap mount command. > > That's a strong indication. BTW what's the fs type of root.bin supposed to be? > I can't mount it here. root.bin is just a compressed ext2 root image. dbootstrap does some gunzip & piping magic to mount it, but mv root.bin root.bin.gz && gunzip root.bin.gz will do also. Do you have the same problem as me with the mounting of the rescue.bin image (it is a vfat image) ? Friendly, Sven LUTHER |
|
From: Michel <da...@re...> - 2000-07-05 14:36:23
|
Iain, I'm forwarding this to the Linux/APUS development list - let's hope the patch applies to our 2.2.10 (or 2.4.0-test2) as well and wait for some interesting results... Michel -- So many Christians, so few lions. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Geert U. <ge...@li...> - 2000-07-05 13:24:23
|
On Wed, 5 Jul 2000, Frank Petzold wrote:
> On Wed, Jul 05, 2000 at 09:50:05AM +0200, Michel Dänzer wrote:
> > Frank Petzold wrote:
> > > Now I only need a driver for the GVP-II, and I shall switch to 2.3 :-))
> >
> > You first :)
> >
> > Please excuse my ignorance, is it a disk interface or what?
>
> I meant the GVP Series II SCSI controller card. My ZIP and Scanner are attached
> to it.
I thought we've had a driver for that card since ages?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Geert U. <ge...@li...> - 2000-07-05 13:23:53
|
On Tue, 4 Jul 2000, Giorgio Terzi wrote:
> 2) Buddha IDE driver has a problem on my computer: when reboot
> it locks the process of restart and i must switch off the machine
> and then (naturally) on. This problem is described in its docs in
> the kernel's source block devices directory, but i wish to know
> if there is someone that is improving it.
> I have tried to remove the $FC0 write instruction because ,as of
> that docs, it is used only with buggy hardware. The driver ignored
> my modify continuing to work normally after the new kernel's
> compilation and bootstrap, but the reboot problem still remains.
> Do you know something about ?
> Any suggestion ?
All I know is in the README. I wrote the driver according to the README, and
that's it (I don't have a Buddha or Catweasel).
I think you best ask the manufacturer of the Buddha. His email is somewhere in
the README.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Geert U. <ge...@li...> - 2000-07-05 13:23:50
|
On Tue, 4 Jul 2000 fh...@at... wrote:
> Actually my last name is "Heitkamp". I have yet to get the driver to
> pass the cache test. I am not sure what is wrong, but Ken seems to think
> the CPU cache is getting in the way. I have let the pieces that reserve
> the I/O space alone. The driver uses check_region/request_region to
> reserve I/O space for the kernel, but that doesn't seem to allow the SCSI
> chip to access memory properly. What I plan to do next is use the bits
> out of the 53C7xx driver to see if that makes any difference, unless
> someone has a better idea.
{check,request}_region() just mark that that region is in use by a driver, it
doesn't allow access itself.
Since you're speaking about request_region(), this sounds like the chip uses
PCI I/O space? And to access PCI I/O space you have to know where PCI (ISA) I/O
space is mapped (isa_io_base). AFAIK, it doesn't exist on APUS.
Now forget the previous paragraph, since the 53c7xx is not for PCI! AFAIK it's
meant to be connected directly to the CPU bus. Hence you should not use
request_region() at all, but request_mem_region(). And to make everything I
said above even more useless: you don't need request_mem_region() to get
anything to work neither (but you do want request_mem_region() later).
> Yes the code is written in a completely different style from that of the
> 53c7xx driver but it appears to be a close cousin of the driver used in
> the sym53c8xx driver, which is used for a number of cards for the PC.
> Alas they are all ISA or PCI cards. I am trying to find someone who can
> tell me the major differences between
Not only on the PC. I have a plain sym53c875 PCI card in my CHRP box, which
works fine (17 MB/s on my Quantum Viking II).
> accessing cards on the Amiga vs. the PC. If the driver ever does get to
On PC, the sym53c8xx driver can use both PCI I/O space and PCI memory space,
configurable through a CONFIG_* option. On some platforms only one of them
work fine.
On Amiga, you should just read/write to the correct memory addresses.
> work, I would eventually like to see it combined with the sym53c8xx.c in
> order to take advantage of the active development. If that's all possible
> of course.
Should be possible, since 53c7xx and 53c8xx are close cousins.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Michel <da...@re...> - 2000-07-05 12:58:51
|
Sven LUTHER wrote: > i give the corrct place in the requester, and dbootstrap tries to loop mount > the rescue.bin image to fetch the kernel and the modules, and fail. Should drivers.tgz be in rescue.bin? It's not. If the config.gz in rescue.bin is the config of the kernel you use, it does indeed include the loopback device and vfat. > Now the strange thing, is that when i continue the installation stuff and > reboot with the same kernel on the partition just installed from the base > tarball, i can mount the rescue.bin image with the exact command given > above. > > Thus i suspsect the problem lie with the root.bin image. or maybe the > dbootstrap mount command. That's a strong indication. BTW what's the fs type of root.bin supposed to be? I can't mount it here. Michel -- Apologies are so hard to give. Would you accept some potatoes instead? ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Sven L. <lu...@la...> - 2000-07-05 11:15:27
|
Hello, ... This is a call for help, i am totally lost here, and if nobody helps me out on this, i am afraid the apus boot floppies will chip as is, without working properly. This is not so big a deal, because it is possible to do a full install in the current state of things, but still it would be nicer if this was fixed before the potato release, ... this morning i did try 2.2.15, and the problem still is there. The problem (already described in bug 64500, 43 days old as of today) is the following. Everything works fine, but when i come to the step where i would normally do : * install os kernel & modules i give the corrct place in the requester, and dbootstrap tries to loop mount the rescue.bin image to fetch the kernel and the modules, and fail. I then tried testing by hand, with : $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt Mounting rescue.bin on /mnt failed : block device required well, i think i found the cause of this error, ... Now the strange thing, is that when i continue the installation stuff and reboot with the same kernel on the partition just installed from the base tarball, i can mount the rescue.bin image with the exact command given above. Thus i suspsect the problem lie with the root.bin image. or maybe the dbootstrap mount command. I have tested to see if loop device is modular or not, (i built the kernel with loops included) and got : $ grep loop /proc/ksyms c016a084 loops_per_ser c0161278 loopback_dev c00aeeac loop_register_transfer c00aeee4 loop_unregister_transfer this should be ok, since i get the same symbols on my i386 2.3.99-pre8 kernel here at work. also i did test the loop0 device : from the root.bin image : $ ls -l /dev/loop0 brw-r--r--r 1 root root 7, 0 Jun 6 21:50 /dev/loop0 (didn't change when i chmoded it to be 666 either :((() from the base installed system : $ ls -l /dev/loop0 brw-rw---- 1 root disk ... Any idea of what is going wrong here ? Anything else i could test here ? In particular i would like other apus user to test this (with various kernels) and report to me about it. It can be tested in an non partition damaging way by : 1) booting with the latest debian root.bin image as ramdisk. 2) respond only to the keyboard question once it has booted. 3) switch to console 2 4) type enter to get a prompt 5) try : $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt And see if it can be mounted ... Not so difficult isn't it, but if nobody can be worried to confirm on this, i guess it is not worth for me to waste my time on this, isn't it, anyway, _I_ can install debian without problem with the current boot floppies, ... Friendly, Svne LUTHER |
|
From: Michel <da...@re...> - 2000-07-05 10:23:36
|
Michel Dänzer wrote: > > :-) btw, is there any chance of us seeing .16 ? what issues are there > > with the later 2.2.11/16 yada range? > > 2.2 is still based on m68k and thus: no new m68k version, no new m68k > version. That should of course be: no new m68k version, no new APUS version. ;) Michel -- I'm so hungry, I could almost eat health food. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Michel <da...@re...> - 2000-07-05 10:12:54
|
Alan Buxey wrote:
> > Yes Alan, I think it would be very nice if you could build the latest 2.2
> > CVS (with pending patches applied as well) on a regular basis for the test
> > module.
>
> this I will do.
Thanks a lot.
> i was thinking....now 2.3 'works', should I also make a 2.3 test kernel
> for the masses to use?
Have a go please, user feedback is always very welcome - but lots of things
still don't work. (Put a *REALLY BIG FAT* warning there ;)
> > - Please put the files into a subdirectory which is named like the
> > archives
>
> ..could you explain?
If the archive is calles vmapus-test-[date].{tar.gz,lha}, put the files in a
directory calles vmapus-test-[date] . That way the testers don't get all the
files cluttered in one directory.
> thanks for the .config tips - I've been collecting 'wants and needs' from
> people who have booted up and found no support for their required pieces -
> and you also alerted me to 3 oversights (i cant believe it, but yes, silly
> things did slip through - I'll be updating the 'standard 2.2.10' as well -
That would be very nice, thanks.
> > - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems
> > for us and isn't needed anyway as we're stuck with 2.2.10 ;)
>
> :-) btw, is there any chance of us seeing .16 ? what issues are there
> with the later 2.2.11/16 yada range?
2.2 is still based on m68k and thus: no new m68k version, no new m68k version.
Besides, I've read somewhere that performance didn't exactly improve very much
after 2.2.10 ;)
> as a general rule, local services that are needed to get the machien to
> boot and install etc i compile in. 'Exotics' and things that you use once
> you are booted (sound, serial, joystick, parallel) I try to make as
> modules.
That's a very good concept IMHO.
But I don't think that we should encourage people to use the test kernels for
installing, should we?
Michel
--
True programmers never die, they just branch to an odd address.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
|
|
From: Alan B. <al...@ms...> - 2000-07-05 09:52:47
|
hi, > Yes Alan, I think it would be very nice if you could build the latest 2.2 CVS > (with pending patches applied as well) on a regular basis for the test module. this I will do. i was thinking....now 2.3 'works', should I also make a 2.3 test kernel for the masses to use? > - Please put the files into a subdirectory which is named like the archives ..could you explain? > For the config: thanks for the .config tips - I've been collecting 'wants and needs' from people who have booted up and found no support for their required pieces - and you also alerted me to 3 oversights (i cant believe it, but yes, silly things did slip through - I'll be updating the 'standard 2.2.10' as well - especially as HFS is needed to be in the kernel for people to install LinuxPPC 2000 - i need a LinuxPPC 2k CD to test this out the new installer when it arrives (soon!) myself) > - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems for us > and isn't needed anyway as we're stuck with 2.2.10 ;) :-) btw, is there any chance of us seeing .16 ? what issues are there with the later 2.2.11/16 yada range? > - Set CONFIG_SOUND_OSS and CONFIG_SOUND_SOFTOSS (it's a software synthesizer > for MIDI stuff) okay > - Finally, set CONFIG_MAGIC_SYSRQ ..now that it can compile and work :-) > I leave to you what you build into the kernel and what as modules. In general, > Stuff which isn't needed at boot time (before modules can be loaded) should be > a module so the kernel isn't bloated too much. as a general rule, local services that are needed to get the machien to boot and install etc i compile in. 'Exotics' and things that you use once you are booted (sound, serial, joystick, parallel) I try to make as modules. After all, it has been known for the device type and rootfilesystem type to be compiled as modules...ouch! ;-) alan |
|
From: Michel <da...@re...> - 2000-07-05 09:40:06
|
Alan Buxey wrote: > to all: If you make diffs, please use the patch manager, i can then grab > these and apply them to the sources I use to make the boot kernels - > looking forward to being able to supply people the latest serial drivers > as modules 8-) Yes Alan, I think it would be very nice if you could build the latest 2.2 CVS (with pending patches applied as well) on a regular basis for the test module. A few suggestions: - Please put the files into a subdirectory which is named like the archives For the config: - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems for us and isn't needed anyway as we're stuck with 2.2.10 ;) - Set CONFIG_PCI and CONFIG_PCI_OLD_PROC - You have set CONFIG_PARPORT and CONFIG_PARPORT_AMIGA, but IIRC only CONFIG_M68K_PRINTER works (comments?) - CONFIG_BLK_DEV_IDEFLOPPY: Are there IDE floppies for Amigas? - Set CONFIG_BLK_DEV_IDESCSI (at least as a module) - Set CONFIG_BLK_DEV_BUDDHA - Set CONFIG_FILTER and CONFIG_SYN_COOKIES - Set CONFIG_A2091_SCSI, CONFIG_GVP11_SCSI, CONFIG_CYBERSTORM_SCSI, CONFIG_CYBERSTORMII_SCSI, CONFIG_BLZ2060_SCSI, CONFIG_BLZ1230_SCSI, CONFIG_FASTLANE_SCSI and CONFIG_OKTAGON_SCSI - Set CONFIG_APNE - Set CONFIG_SLIP_COMPRESSED, CONFIG_SLIP_SMART and CONFIG_SLIP_MODE_SLIP6 - Set CONFIG_FONT_SUN12x22 - Don't set CONFIG_NVRAM, but you might set CONFIG_RTC - Set CONFIG_HFS_FS, CONFIG_MSDOS_FS, CONFIG_VFAT_FS and maybe CONFIG_ROMFS_FS - Set CONFIG_SOUND_OSS and CONFIG_SOUND_SOFTOSS (it's a software synthesizer for MIDI stuff) - Finally, set CONFIG_MAGIC_SYSRQ I leave to you what you build into the kernel and what as modules. In general, Stuff which isn't needed at boot time (before modules can be loaded) should be a module so the kernel isn't bloated too much. TIA Michel -- Men are from Earth. Women are from Earth. Deal with it. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Frank P. <fp...@zu...> - 2000-07-05 09:24:35
|
On Wed, Jul 05, 2000 at 09:50:05AM +0200, Michel Dänzer wrote: > Frank Petzold wrote: > > Now I only need a driver for the GVP-II, and I shall switch to 2.3 :-)) > > You first :) > > Please excuse my ignorance, is it a disk interface or what? I meant the GVP Series II SCSI controller card. My ZIP and Scanner are attached to it. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: Alan B. <al...@ms...> - 2000-07-05 09:06:22
|
hi, > Sign up at SourceForge and apply for developer status directly to me. Believe > me, the process isn't hard *grin* :-) > In the meantime, you could upload the patch to the Patch Manager (Put the > readme on top of it) and maybe upload the modules to the FTP incoming > directory so we can put them in contrib or something? to all: If you make diffs, please use the patch manager, i can then grab these and apply them to the sources I use to make the boot kernels - looking forward to being able to supply people the latest serial drivers as modules 8-) alan |
107 messages has been excluded from this view by a project administrator.
