Hi, At Mon, 6 Dec 2004 04:03:23 -0500, Joey Hess wrote: > > - This machine needs CATS image to boot up. There is image for Woody, > > but isn't for Sarge. I built tftp image on other machine using > > catsboot, but it is better to provide official cats boot image. > > Hmm, d-i manual said there was > > /debian/dists/sarge/main/installer-arm/current/cats/tftpboot.img, > > but there wasn't. > > Is this build system issue? > > I'm afraid it's a manual outdatedness issue, there's no cats stuff in > the build system.
Hmm. Creating tftpboot.img for cats is easy. Just doing 'catsboot tftpboot.img netwinder-kernel-file gzipped-initrd file' on arm machine (other architecture can do by taking binary glue code from catsboot_arm.deb). > > - This machine has S3 Trio64, but VGA16FB shows broken screen (shows > > green vertical bar only). I added video=vga16:off, but it causes > > empty screen. I tried to change video card to S3 968, but result is > > same. > > Woody installer (it hasn't FB) can show me colorful normal screen. > > Finally I used serial cable (console=ttyS0) and English locale. > > It's not so big problem, but is VGA16FB really needed for arm machines? > > Did you try debian-installer/framebuffer=false? Yes. But it goes black screen. Framebuffer driver is not module, but is embedded in kernel. > > - DECchip 21140 won't be found by discover. I choose 'tulip' by hand, > > then it was detected... but tulip driver seems buggy. I tried DHCP > > or static IP, but I couldn't connect other hosts. Additional NIC, > > RTL8139 is found and works (unfortunatelly CATS couldn't boot up > > from this NIC...). > > FYI, de4x5 driver (this driver isn't included in d-i) works > > partially, but this driver is buggy also. Connection often down > > with silence. > > Netwinder kernel problem? > > It seems to be about 50/50 whether tulip or de4x5 will work on a given > architecture. FWIW as of a few days ago if the initrd includes de4x5 and You're right. I can remember same experience on i386 old days ago :-) > not tulip then the installer will make sure to load de4x5 even if > discover tells it to load tulip. Hmm, also 10110009 is recognised by > discover as being driven by de4x5. If de4x5 is added to the arm kernel > image (there already) and/or udebs it will be loaded. Yes, de4x5 is loaded automatically by discover in 2nd stage. THanks, -- Kenshi Muto [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]