Re: non-install report
On Thu, 02 Dec 2004 14:15:44 +0100, Goswin von Brederlow [EMAIL PROTECTED] wrote: Hank Barta [EMAIL PROTECTED] writes: ./get-packages ??? Uploaded. What should go in my soures.list.udeb? At present I have: deb http://debian.uchicago.edu/debian/ testing main non-free contrib deb http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free deb ftp://ftp.debian.org/debian testing main/debian-installer (which is little more than a guess.) I think it is incomplete: ... Reading Package Lists... Done Building Dependency Tree... Done E: Couldn't find package libreiserfs0.3-udeb thanks, hank -- Beautiful Sunny Winfield
Re: non-install report
Hank Barta [EMAIL PROTECTED] writes: On Thu, 02 Dec 2004 14:15:44 +0100, Goswin von Brederlow [EMAIL PROTECTED] wrote: Hank Barta [EMAIL PROTECTED] writes: ./get-packages ??? Uploaded. What should go in my soures.list.udeb? At present I have: deb http://debian.uchicago.edu/debian/ testing main non-free contrib deb http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free deb ftp://ftp.debian.org/debian testing main/debian-installer (which is little more than a guess.) deb http://debian-amd64.alioth.debian.org/pure64 sid main or any of its mirrors. I think it is incomplete: ... Reading Package Lists... Done Building Dependency Tree... Done E: Couldn't find package libreiserfs0.3-udeb thanks, hank MfG Goswin
Re: non-install report
Hank Barta [EMAIL PROTECTED] writes: On Wed, 01 Dec 2004 11:52:32 +0100, Goswin von Brederlow Have any spare parts around? Another cpu, different MB. Unfortunately this the only XMD64 hardware I have. I've just ordered a new LAN card (Intel) to replace the ancient Tulip based card. I should consider Video too. My concern is that old hardware may not perform correctly with faster processors. I know design specs say it should, but if the design is marginal, it may depend on CPU behavior that was typical with hardware 'back in the day', ;) http://debian-amd64.alioth.debian.org/tools/make-cd.sh Thank you. ./get-packages ??? Uploaded. Maybe compile your own 2.8.9 or even more recent kernel? I saw some reports about APIC bugs getting patches and maybe you have the same problem. I'm testing now with APIC off. But I'm confused a bit by how to do this. In varrious places I see 'apic=off' or 'noapic' and 'nolapic' as it is recommended in the Ubuntu boot help for Via chip sets. Never had to care about it. thanks, hank MfG Goswin
Re: non-install report
Hank == Hank Barta [EMAIL PROTECTED] writes: Hank I'm testing now with APIC off. But I'm confused a bit by how to Hank do this. In varrious places I see 'apic=off' or 'noapic' and Hank 'nolapic' as it is recommended in the Ubuntu boot help for Via Hank chip sets. The best way to turn it off is in the kernel configuration options. That is if you are compiling a kernel. Otherwise read the documentation that explains all of this in detail. It is in the linux kernel source tree. /usr/src/linux/Documentation/x86_64/boot-options.txt is the correct file. I have had real problems with apic with strange lockups. apci seems more stable in 2.6.10-rc[12] releases. Good luck, Alan
non-install report
I've been trying to install some flavor of Debian AMD-64 to a system I upgraded last night with little success. Hardware Abit AV8 with VIA K8T800 Pro/ VT8237 chipset SATA/RAID (not in use yet) VT8237 IDE Audio (AC-97?) 3400+ processor 512MB/1GM RAM (recycled hardware) Some year+ old Seagate ATA drive - 130GB Ancient #9 video card (S3968) Ancient Tulip Ethernet card IDE CDROM burner Trying any of the ISOs that looked like they made sense (anything save the netboot) the system was horribly unstable. It ranged from rebooting instantly when hitting return from the boot prompt to locking up while loading modules from the CD or partitioning and formatting the hard drive. It did not recognize the on board LAN so I put the Tulip card in. It recognized that but DHCP did not work and manual configuration resulted in lots of error messages to the console. (Incidentally, it was not clear which ISO I should be using. I typically do a network install since I'm on cable Internet. The HOW-TO points to two sites for boot images and there are a variety of ISOs with no description save the name to explain what they are. Puzzling to me, the directory http://debian-amd64.alioth.debian.org/debian-installer/current/cdrom/ contains no CDROM nor any indication if I am supposed to build one from the files found there.) The machine was so horribly unstable - crapping out ad a different place nearly each try - that I thought that there was some problem with the hardware. I tried booting a recent Knoppix CD and it seemed to work a *lot* better, though it was not without problem. It recognized the on board LAN and sound with no problem, but configured my serial mouse systems mouse as a PS/2 mouse. (There is probably a boot option to fix that, but I didn't bother. A text console was fine with me.) It did also report once that KDE could not start due to insufficient RAM (with 1GB available. ;) and once when running a command at the shell prompt, I got a bus error. I ran the Knoppix memory test since last night and it reported no errors. I'm in the process of installing Sarge i386 and have just finished rebooting. So far it is running flawlessly. So, I'm wondering how to go about installing one of the 64 bit Debian flavors. do I identify my hardware and build a kernel with only support for it? I presume that some driver that doesn't belong is leading to the instability. then it's DFS for the rest, right? Suggestions and comments welcomed! back to my ia32 install :( thanks, hank -- Beautiful Sunny Winfield
Re: non-install report
Hank Barta [EMAIL PROTECTED] writes: I've been trying to install some flavor of Debian AMD-64 to a system I upgraded last night with little success. Hardware Abit AV8 with VIA K8T800 Pro/ VT8237 chipset SATA/RAID (not in use yet) VT8237 IDE Audio (AC-97?) 3400+ processor 512MB/1GM RAM (recycled hardware) Some year+ old Seagate ATA drive - 130GB Ancient #9 video card (S3968) Ancient Tulip Ethernet card IDE CDROM burner Trying any of the ISOs that looked like they made sense (anything save the netboot) the system was horribly unstable. It ranged from rebooting instantly when hitting return from the boot prompt to locking up while loading modules from the CD or partitioning and formatting the hard drive. It did not recognize the on board LAN so I put the Tulip card in. It recognized that but DHCP did not work and manual configuration resulted in lots of error messages to the console. Can you check your hardware please (yes I saw below). From the hardware data the board sounds just like an Asus K8V which many of us have running perfectly so crashes sound strange. (Incidentally, it was not clear which ISO I should be using. I typically do a network install since I'm on cable Internet. The HOW-TO points to two sites for boot images and there are a variety of ISOs with no description save the name to explain what they are. Puzzling to me, the directory http://debian-amd64.alioth.debian.org/debian-installer/current/cdrom/ contains no CDROM nor any indication if I am supposed to build one from the files found there.) The names and meaning of the images is the same across all architectures and described in Debian-Installer somewhere. If you have a spare minute to dig into it, a patch to the FAQ or a small webpage for the directory would be welcome. In Short: /debian-installer/current contains the daily build D-I images, which does not include a cdrom iso. The cdrom directory contains the files needed to build a cdrom with debian-cd. I also wrote a script (far simpler than debian-cd) that uses the same files to build a netinst cd and I do that iregulary from time to time. The script is in the tools directory (make-cd) if you want a newer image. The machine was so horribly unstable - crapping out ad a different place nearly each try - that I thought that there was some problem with the hardware. I tried booting a recent Knoppix CD and it seemed to work a *lot* better, though it was not without problem. It recognized the on board LAN and sound with no problem, but configured my serial mouse systems mouse as a PS/2 mouse. (There is probably a boot option to fix that, but I didn't bother. A text console was fine with me.) It did also report once that KDE could not start due to insufficient RAM (with 1GB available. ;) and once when running a command at the shell prompt, I got a bus error. It does sound like hardware. I ran the Knoppix memory test since last night and it reported no errors. I have a dual PIII-666 system that never runs longer than 5 minutes, except when running memtest (which runs flawless without trouble). If something like the pci dma is broken and sometimes writes to the wrong memory or something the system won't run long but memtest can't find such errors. It can also just need a bios upgrade or something. I'm in the process of installing Sarge i386 and have just finished rebooting. So far it is running flawlessly. So, I'm wondering how to go about installing one of the 64 bit Debian flavors. do I identify my hardware and build a kernel with only support for it? I presume that some driver that doesn't belong is leading to the instability. then it's DFS for the rest, right? Suggestions and comments welcomed! Try installing the 64bit kernel-image-2.6.9-amd64-k8 (from i386) on your system and boot it. Does it still work then (guessing not). But if it does you can create a 64bit chroot and see if any of the binaries trigger the instability and so on. back to my ia32 install :( thanks, hank MfG Goswin
Re: non-install report
Am Montag, den 29.11.2004, 22:13 -0600 schrieb Hank Barta: I've been trying to install some flavor of Debian AMD-64 to a system I upgraded last night with little success. Hardware Abit AV8 with VIA K8T800 Pro/ VT8237 chipset SATA/RAID (not in use yet) VT8237 IDE Audio (AC-97?) 3400+ processor 512MB/1GM RAM (recycled hardware) Some year+ old Seagate ATA drive - 130GB Ancient #9 video card (S3968) Ancient Tulip Ethernet card IDE CDROM burner Trying any of the ISOs that looked like they made sense (anything save the netboot) the system was horribly unstable. It ranged from rebooting instantly when hitting return from the boot prompt to locking up while loading modules from the CD or partitioning and formatting the hard drive. Hmm -- to me this doesn't sound like an debian-amd64-related problem. Have you tried another memory module. Or try clocking your memory slower. I've expierenced similar errors on an ia32-machine. Clocking down the memory solved the problem. [...]
Re: non-install report
Thanks all for the help. On Tue, 30 Nov 2004 11:14:37 +0100, Goswin von Brederlow [EMAIL PROTECTED] wrote: Can you check your hardware please (yes I saw below). From the hardware data the board sounds just like an Asus K8V which many of us have running perfectly so crashes sound strange. How to check? memtest is the only thing I see offhand. I know that a 'no error' from that is not conclusive, but if it did detect errors, that would be conclusive. Debian i386 seems to do fine except for not noticing the built in ethernet. It works fine with the Tulip card. In Short: /debian-installer/current contains the daily build D-I images, which does not include a cdrom iso. The cdrom directory contains the files needed to build a cdrom with debian-cd. I also wrote a script (far simpler than debian-cd) that uses the same files to build a netinst cd and I do that iregulary from time to time. The script is in the tools directory (make-cd) if you want a newer image. I'm still clueless here. I can't find the tools directory or make-cd. I'm sure this is documented somewhere, but I cannot find it. The link on the HOW-TO points to the section on the installer describing how to partition a hard drive. It does sound like hardware. I can't rule that out at this point, but I do get different results with different S/W. Try installing the 64bit kernel-image-2.6.9-amd64-k8 (from i386) on your system and boot it. Does it still work then (guessing not). But if it does you can create a 64bit chroot and see if any of the binaries trigger the instability and so on. I could not find that kernel image. I did install kernel-image-2.6.8-9-amd64-k8 and it does not work with the Tulip card. dhclient reports checksum errors trying to establish the connection. I think that via-rhine is the correct module for the on board ETH and that does not load (Gentoo liveCD can load it, but ifconfig etho reports no such device, but I don't know Gentoo and I may be leaving something else out.) thanks, hank -- Beautiful Sunny Winfield
