If the doudou-installer program has an errror saying that there are no available writable drives, it must be modified to accept additional buses. To add ‘pci’ to the list of valid buses do the following:
If the doudou-installer program has an errror saying that there are no available writable drives, it must be modified to accept additional buses. To add ‘pci’ to the list of valid buses do the following:
- boot on a live DouDou CD
- go to the “Whole DoudouLinux” activity
- go to the “Accessories” activity
- run the “LxTerminal”
- cd /usr/bin
- sudo vi doudou-installer
- locate the line containing “ide”, “scsi”
- add “pci” to the list
- save the edited version
- sudo doudou-installer
Thanks for the tip. 
I followed these directions and still have problems, can someone help please?
the doudou-installer finds my 60gb hdd and then presents me with the following popup msg…
“This tool can install DoudouLinux definitively on your computer. It does not let you backup any previous existing data. It does not let you keep your previously installed system along with DoudouLinux neither. In short it destroys all your computer data… Do you really want to continue?”
*I hit the OK button"
Then the popup goes away, the terminal script looks for Live USB disk and cannot find it… and this new popup msg displays…
“No DoudouLinux Live USB was found among the connected devices and no USB disk was found with the Live image file. Please be sure to have plugged the USB device correctly and restart the installation process.”
I’m trying to install to my hdd via a burned CD … please help!
Most likely something went wrong, probably when detecting your disk configuration. Our installer is not yet designed to detect errors and may tell that it has completed the job while indeed it has not… We know there are troubles with disk partition reporting, especially on the development version. What version of DoudouLinux are you using? Could you copy/paste the text that is displayed in the console when running the installation tool?
Most likely something went wrong, probably when detecting your disk configuration. Our installer is not yet designed to detect errors and may tell that it has completed the job while indeed it has not… We know there are troubles with disk partition reporting, especially on the development version. What version of DoudouLinux are you using? Could you copy/paste the text that is displayed in the console when running the installation tool?
Sorry this took so long … here’s the installer log:
tux@doudoulinux:/usr/bin$ sudo doudou-installer
SanDisk Cruzer [8.0 GB USB]
/dev/sda1 vfat (8.0 GB)
IC25N060ATMR04-0 [60 GB IDE]
/dev/hda3 ext3 (58 GB) [live-rw]
/dev/hda2 swap (370 MB)
/dev/hda1 vfat (740 MB) [DoudouLinux]
INFO: cannot find the Live USB disk…
find '/mnt/sda1' -name 'doudoulinux-*.img'
/mnt/sda1/doudoulinux-gondwana-1.2-en.img
Selected disk: IC25N060ATMR04-0 [60 GB IDE]
dd if='/mnt/sda1/doudoulinux-gondwana-1.2-en.img' of=/dev/hda
mlabel -i /dev/hda1 ::DoudouLinux
dd: reading `/mnt/sda1/doudoulinux-gondwana-1.2-en.img': Input/output error
846712+0 records in
846712+0 records out
433516544 bytes (434 MB) copied, 55.144 s, 7.9 MB/s
echo '90,45,L' | LANG=EN_us.UTF-8 sfdisk --no-reread -N 2 /dev/hda
sfdisk --change-id /dev/hda 2 82
mkswap /dev/hda2
Disk /dev/hda: 7296 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 0 - 0 0 0 Empty
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
New situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 83 Linux
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
Successfully wrote the new partition table
Re-reading the partition table ...
BLKRRPART: Device or resource busy
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)Done
/dev/hda2: Device or resource busy
echo '135,7161,L' | LANG=EN_us.UTF-8 sfdisk --no-reread -N 3 /dev/hda
mkfs.ext3 -L live-rw /dev/hda3
mount -t vfat /dev/hda1 /mnt
WARNING: unable to find file '/mnt/syslinux/live.cfg'
hda1
hda3
sda1
umount /mnt
Disk /dev/hda: 7296 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 82 Linux swap / Solaris
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
New situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 82 Linux swap / Solaris
/dev/hda3 135 7295 7161 57520732+ 83 Linux
/dev/hda4 0 - 0 0 0 Empty
Successfully wrote the new partition table
Re-reading the partition table ...
BLKRRPART: Device or resource busy
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
tux@doudoulinux:/usr/bin$ sudo doudou-installer
SanDisk Cruzer [8.0 GB USB]
/dev/sda1 vfat (8.0 GB)
IC25N060ATMR04-0 [60 GB IDE]
/dev/hda3 ext3 (58 GB) [live-rw]
/dev/hda2 swap (370 MB)
/dev/hda1 vfat (740 MB) [DoudouLinux]
INFO: cannot find the Live USB disk…
find '/mnt/sda1' -name 'doudoulinux-*.img'
/mnt/sda1/doudoulinux-gondwana-1.2-en.img
Selected disk: IC25N060ATMR04-0 [60 GB IDE]
dd if='/mnt/sda1/doudoulinux-gondwana-1.2-en.img' of=/dev/hda
mlabel -i /dev/hda1 ::DoudouLinux
dd: reading `/mnt/sda1/doudoulinux-gondwana-1.2-en.img': Input/output error
846712+0 records in
846712+0 records out
433516544 bytes (434 MB) copied, 55.144 s, 7.9 MB/s
echo '90,45,L' | LANG=EN_us.UTF-8 sfdisk --no-reread -N 2 /dev/hda
sfdisk --change-id /dev/hda 2 82
mkswap /dev/hda2
Disk /dev/hda: 7296 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 0 - 0 0 0 Empty
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
New situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 83 Linux
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
Successfully wrote the new partition table
Re-reading the partition table ...
BLKRRPART: Device or resource busy
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)Done
/dev/hda2: Device or resource busy
echo '135,7161,L' | LANG=EN_us.UTF-8 sfdisk --no-reread -N 3 /dev/hda
mkfs.ext3 -L live-rw /dev/hda3
mount -t vfat /dev/hda1 /mnt
WARNING: unable to find file '/mnt/syslinux/live.cfg'
hda1
hda3
sda1
umount /mnt
Disk /dev/hda: 7296 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 82 Linux swap / Solaris
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
New situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 89 90- 722893+ 83 Linux
/dev/hda2 90 134 45 361462+ 82 Linux swap / Solaris
/dev/hda3 135 7295 7161 57520732+ 83 Linux
/dev/hda4 0 - 0 0 0 Empty
Successfully wrote the new partition table
Re-reading the partition table ...
BLKRRPART: Device or resource busy
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)mke2fs 1.41.3 (12-Oct-2008)
/dev/hda3 is mounted; will not make a filesystem here!mount: /dev/hda1 already mounted or /mnt busy
mount: according to mtab, /dev/hda1 is mounted on /mnt/hda1umount: /mnt: not mounted
tux@doudoulinux:/usr/bin$
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)mke2fs 1.41.3 (12-Oct-2008)
/dev/hda3 is mounted; will not make a filesystem here!mount: /dev/hda1 already mounted or /mnt busy
mount: according to mtab, /dev/hda1 is mounted on /mnt/hda1umount: /mnt: not mounted
tux@doudoulinux:/usr/bin$
dd: reading `/mnt/sda1/doudoulinux-gondwana-1.2-en.img': Input/output error 846712+0 records in 846712+0 records out 433516544 bytes (434 MB) copied, 55.144 s, 7.9 MB/s
I think this is the error that is not detected: only 434 MB are copied from the image instead of around 700 MB. Unfortunately I can’t tell why this happened. This may be an issue with the image file *.img, with the USB disk or with the target disk. Have you checked the SHA1 sum of the image file before and after having copied it on the USB disk?
I think this is the error that is not detected: only 434 MB are copied from the image instead of around 700 MB. Unfortunately I can’t tell why this happened. This may be an issue with the image file *.img, with the USB disk or with the target disk. Have you checked the SHA1 sum of the image file before and after having copied it on the USB disk?
I have not done this, how would I check the SHA1 sum of the image file?
Hi Kat,
with SHA1 sum you can confirm that the image you have downloaded is not corrupted. First check SHA1 checksum on DouDou Linux website . Now use shasum command to generate your own SHA1 checksum against the image you have downloaded.
For example:
$ shasum doudoulinux-gondwana-1.2-en.iso
f3d15b2229ef240722f0d4c903fc9854b84af123 doudoulinux-gondwana-1.2-en.iso
Both numbers must match !
Hope it helps…
Lubos
I did shasum on the USB img I had on my flash drive when trying to install via the cd and every umber matched up as far as i can tell…
English doudoulinux-gondwana-1.2-en.img 713 MB d848a4109bd55df7f4aacba01ed218ddc564e94a
$ shasum doudoulinux-gondwana-1.2-en.img
d848a4109bd55df7f4aacba01ed218ddc564e94a doudoulinux-gondwana-1.2-en.img
Mmmm, I’m sorry I can’t see what else could make the disk copy fail… The only possible explanation I can find is that there would be some hardware error. Unfortunately I looked at the man pages and didn’t find a verbose mode for “dd” so we can’t know more about its failure. Is your hardware recent or quite old?
Mmmm, I’m sorry I can’t see what else could make the disk copy fail… The only possible explanation I can find is that there would be some hardware error. Unfortunately I looked at the man pages and didn’t find a verbose mode for “dd” so we can’t know more about its failure. Is your hardware recent or quite old?
Its a Toshiba psa60u-02k015, not horribly old but technically obsolete hardware.
I know the bios is very limited and cannot boot from USB Flash.
Hi Kat,
Before we start blaming your laptop would it be possible that you try the same installation process again but using different USB drive/stick? If you get the same or similar error then we can start thinking about what is wrong with your laptop.
Lubos
Hi Kat,
Before we start blaming your laptop would it be possible that you try the same installation process again but using different USB drive/stick? If you get the same or similar error then we can start thinking about what is wrong with your laptop.
Lubos
This was it … for some reason the 8GB SanDisk was producing the missing data and a smaller 1GB Kingston copied everything over with no errors… thanks everyone for their help! I hope anyone who has this issue in the future finds this thread!
Good news! lrendek got it, it’s true that most of issues are due to support media that behave weirdly, he found the missing test. Have a good DoudouLinux! Hem, your children of course ;).