Bug#284417: installation-reports: [ARM] netwinder install success with serial console
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]
Bug#284417: installation-reports: [ARM] netwinder install success with serial console
Kenshi Muto 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. > - 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? > - 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 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. -- see shy jo signature.asc Description: Digital signature
Bug#284417: installation-reports: [ARM] netwinder install success with serial console
Package: installation-reports Severity: normal I bought ARM machine to improve Sarge release progress. Finally I succeeded to install Sarge on this machine, and it already works as personal buildd (I'd like to join official buildd network). Debian-installer-version: sarge rc2 uname -a: Linux arm 2.4.27-netwinder #1 Fri Aug 20 01:24:32 BST 2004 armv4l GNU/Linux Date: 2004-12-05 Method: network boot (boot de0:) *comment Machine: ARM (netwinder) evaluation board with CATS firmware. Processor: StrongARM-110 rev 4 (v4l) Memory: 256MB Root Device: IDE (/dev/hda) Root Size/partition table: hda1 (/boot), hda2 (/), hda5 (swap) Output of lspci and lspci -n: :00:00.0 I2O: Digital Equipment Corporation StrongARM DC21285 (rev 03) :00:08.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV] (rev c3) :00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22) :00:0b.0 VGA compatible controller: S3 Inc. 86c775/86c785 [Trio 64V2/DX or /GX] (rev 16) :00:11.0 IDE interface: ALi Corporation M5229 IDE (rev c1) :00:12.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU] :00:15.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) :00:00.0 0e00: 1011:1065 (rev 03) :00:08.0 0601: 10b9:1533 (rev c3) :00:09.0 0200: 10ec:8139 (rev 10) :00:0a.0 0200: 1011:0009 (rev 22) :00:0b.0 0300: 5333:8901 (rev 16) :00:11.0 0101: 10b9:5229 (rev c1) :00:12.0 0680: 10b9:7101 :00:15.0 0c03: 10b9:5237 (rev 03) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] *comment Configure network HW: [O] *comment Config network: [O] *comment Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[ ] *comment Reboot: [O] Comments/Problems: - 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? - 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? - 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? - There is no description/structure about booting from CATS. I did things by hand: Run shell, chroot /target, apt-get install catsboot, catsboot /boot/cats.bin /boot/vmlinuz-2.4.27-netwinder. It is better to include catsboot in install-packages. It is best to create cats boot binary on d-i boot-loader menu. - This machine often hung-up, but it becomes good after I enabled IDE DMA. Thanks, -- Kenshi Muto [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
