---------- Forwarded Message ---------- Subject: Re: Bug#363331: installation-reports Date: Tuesday 18 April 2006 19:38 From: Digby Tarvin <[EMAIL PROTECTED]> To: Frans Pop <[EMAIL PROTECTED]>
Hi Frans, Thanks for acknowledging my report... On Tue, Apr 18, 2006 at 06:23:42PM +0200, Frans Pop wrote: > On Tuesday 18 April 2006 16:12, Digby Tarvin wrote: > > Comments/Problems: > > Initial attempt to install using Etch Beta 2 Install image failed to > > detect the SATA DVD-RAM drive, even following the workaround > > instructions at http://wiki.debian.org/DebianInstaller/SataAtapiHowto > > Strange. Let me know if you want me to investigate further. I am pretty sure I followed the instructions exactly, but it seemed like the file in /etc/modprobe.d was just being ignored and ATAPI stayed disabled.. > > Switching to the latest daily build and following the relevent > > workaround instructions at the above URL resulted in the DVD-RAM > > media being found. > > Good. > > > Install then proceeded to the 'detect network hardare' stage, where > > Debian found: > > eth0: Ethernet or Fast Ethernet > > eth1: Realtek semiconductor co., Ltd. RTL-8139/8139C/8139C+ > > > > The first entry corresponds to a wireless interface which I had been > > successfully using for Lan access from Ubuntu. The Ubuntu detect > > lists: eth0: Realtek semiconductor co., Ltd. RTL-8139/8139C/8139C+ > > eth1: Intel corp. 4223 (wireless) > > which clearly recognises the Intel Wireless hardware and > > prompts for SSID/mode etc. Debian did not, and failed both DHCP and > > manual config attempts. > > Ubuntu is more permissive of supporting hardware that is not fully > supported in official kernels yet or requires non-free firmware. That has certainly been my experience. I suppose I need to figure out what driver is required, and rebuild my kernel with it. > > The Realtek device is a 10/100 UTP interface, which was connected to > > a 10Mb hub, which failed to work also. > > > > It was not till I connected to a 10/100Mb hub that the network > > started to work for the Debian install, so I suspect it was not > > supporting the 10Mb mode properly. > > Sounds like an issue specific to your hardware or network setup. I don't think so - my home 10Mb network works fine with Debian (as it does with all of my other various networked computers) on this hardware once the install has completed. It is only during the install process that it only seems to work if I find a 100Mb network to connect to. It is a 10/100 interface - doesn't that mean I should be able to install with either a 10Mb or 100Mb network? If you like I could try the ubuntu install again to see if it works with the 10Mb UTP. I havn't tried it before because the wireless always worked. > > This I suspect was caused by the fact that the order of the > > partitions in the table was not the same as the order on disk. I had > > used a tool called 'osselector' to shrink the Windows XP partition > > and create, and in installing itself and making partitions seemed to > > produce something that confused the debian partitioner. The problem > > was resolved by deleting all partitions except for the first three > > 'primary' partitions, which were contiguous and sequential. > > The installer is capable of shrinking an NTFS partition too... Ok, I'll try that next time. FDISK partitioning seems like a confused and messy concept anyway. > > After this, the installation completed. Post installation checked > > showed that my wireless i/f was not detected (worked find in ubuntu), > > the DVD-RAM was not detected (libata.atapi_enabled=1 no longer > > recognised), > > This command (executed as root) should fix it: > # echo "libata.atapi_enabled=1" >/etc/modutils.d/local > > This file was supposed to be created by the installer, but there was an > error in the code. Still no luck - are you sure about the directory? I had no /etc/modutils.d exiting on my system prior to doing this. Putting it in modprobe.d just produced a syntax error causing the line to be ignored. dmesg still reports: ata1(0): WARNING: ATAPI is disabled, device ignored. > > and the X server was not working - failing with > > Fatal server error: > > could not optn default font 'fixed'; > > X in unstable is going through a major migration ATM and there are some > known issues. Any issues are outside the scope of the installer. Fair enough. I'll persue that elsewhere. Thanks again, Regards, DigbyT ------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
