[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240932: (fwd) RE: ide troubles



On Tuesday 11 January 2005 20:19, you wrote:
> I did see a progress bar that displays all directory names under
> /pool/*/*.

Hmmm. The log does not really tell us anything new.

Here's a few more things to try. For both I advice you to boot the 
installer with 'linux debconf/priority=medium'.

1. Check if DMA is enabled for the CD drive and disable it.
From vt2, check dmesg for something like:
PCI: Setting latency timer of device 00:01.1 to 64
    ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
hdc: QEMU CD-ROM, ATAPI CD/DVD-ROM drive

Also check:
cat /proc/ide/hd?/settings for value of using_dma

If the CD-drive is showing dma after BIOS settings and proc is also 
showing dma, try disabling it with 'echo -n "using_dma:0" >settings'.

2. See what's really going on in cdrom-detect.
From vt2, 'nano /var/lib/dpkg/info/cdrom-detect.postinst'; uncomment the 
'set -x' command, switch back to vt1 and run cdrom-detect.

Check what's in the syslog.
For the directory scan, you should see a lot of:
+ db_subst cdrom-detect/scanning_progress_step DIR /cdrom/pool/main/a 
+ echo SUBST cdrom-detect/scanning_progress_step DIR /cdrom/pool/main/a
(I removed the date and stuff)

After doing 'z', you should see this:
+ find /cdrom/pool/main/z/ 
+ db_progress STEP 1 
+ echo PROGRESS STEP 1 
+ local IFS= 
 
+ local _LINE 
+ read -r _LINE 
+ RET=OK 
+ return 0 
+ db_progress STOP 
+ echo PROGRESS STOP 
+ local IFS= 
 
+ local _LINE 
+ read -r _LINE 
+ RET=OK 
+ return 0 
+ relfile=/cdrom/dists/stable/Release 
+ [ -e /cdrom/dists/stable/Release ] 
+ sed -n s/^Suite: *//p /cdrom/dists/stable/Release 
+ suite=testing 
+ log Detected CD with 'testing' distribution 
+ logger -t cdrom-detect Detected CD with 'testing' distribution 
+ db_set mirror/suite testing 
+ echo SET mirror/suite testing 
+ local IFS= 

You could try adding commands in the script at the point where it fails to 
see if you, for instance can read other files.

BTW. Did you try the 2.6 kernel? Just boot the installer with linux26.



Reply to: