Opened 15 years ago
Last modified 5 weeks ago
#4502 closed bug
Haiku won't boot "device still expects data transfer" — at Version 15
Reported by: | paavo | Owned by: | marcusoverhagen |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Disk/ATA | Version: | R1/Development |
Keywords: | boot-failure | Cc: | meanwhile |
Blocked By: | Blocking: | #4535, #4558, #7665 | |
Platform: | x86 |
Description (last modified by )
Alpha iso won't boot with my hardware. Hangs on ata 1 error : Device still expects data transfer. System loads but even after several minutes nothing happens.
Screenshots and output of fdisk and lspci attached
Change History (41)
by , 15 years ago
by , 15 years ago
by , 15 years ago
by , 15 years ago
by , 15 years ago
by , 15 years ago
by , 15 years ago
comment:1 by , 15 years ago
Owner: | changed from | to
---|
comment:2 by , 15 years ago
I got the same error. Downloaded ISO from another site and burned to CD again. Same error. Played around with DMA settings in BIOS, didn't help. Will attach some more screenshots, hope they help. (error is a bit different now)
by , 15 years ago
Attachment: | 15092009392.jpg added |
---|
by , 15 years ago
Attachment: | 15092009393.jpg added |
---|
by , 15 years ago
Attachment: | 15092009394.jpg added |
---|
by , 15 years ago
Attachment: | 15092009395.jpg added |
---|
comment:3 by , 15 years ago
It shouldn't matter where you download the alpha iso from (all our mirrors are in sync, and we have not released different versions)...
Thus, if you obtained another file and got different results, either you are not using an official mirror, or you are experiencing issues during the CD burn (bad software, bad drive, bad media, etc.)
If you're concerned about the version of alpha zip you downloaded, we do provide md5sums here: : http://haiku-os.org/get-haiku
follow-up: 7 comment:4 by , 15 years ago
The same error? Are you serious? Did you try disabling DMA or using a non broken CD?
atapi 1-0 error: device indicates transfer error after dma
by , 15 years ago
comment:6 by , 15 years ago
Same error at boot on the live CD
I added the last page since should i add it all? I'm not use to debug stuff so i prefer to know before loading all the 12 images.
comment:7 by , 15 years ago
Replying to marcusoverhagen:
The same error? Are you serious? Did you try disabling DMA or using a non broken CD?
atapi 1-0 error: device indicates transfer error after dma
First I got the same error, but because it was nagging about DMA I started fiddling with the DMA settings in the BIOS, even disabling it. Posted screenshot of altered BIOS settings, my bad. Both CDs I've tried work fine in other systems, and other CDs (XP, Ubuntu) in this drive have no problems installing (in the past). This evening I'll try other BIOS settings trying to reproduce initial error and confirm other CDs boot fine.
by , 15 years ago
Attachment: | TVBios.jpg added |
---|
by , 15 years ago
Attachment: | TVyesDMA1.jpg added |
---|
by , 15 years ago
Attachment: | TVyesDMA2.jpg added |
---|
by , 15 years ago
Attachment: | TVyesDMA3.jpg added |
---|
by , 15 years ago
Attachment: | TVyesDMA4.jpg added |
---|
by , 15 years ago
Attachment: | TVyesDMA5.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA1.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA2.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA3.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA4.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA5.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA6.jpg added |
---|
by , 15 years ago
Attachment: | TVNoDMA7.jpg added |
---|
comment:8 by , 15 years ago
The TVyesDMA pictures are with only the "Enable on screen debug output" option enabled, the TVNoDMA pictures are with also the "Disable IDE DMA" option enabled. Last scenario reproduces the error. The BIOS is set to automatic, which boils down to PIO:4, U-DMA:2. One thing I noticed, my motherboard is recognized as a TUSL2-C, but in fact it is a CUSL2-C. To my knowledge they are identical aside from the Coppermine/Tualatin support. The other thing is that sorting out the added pictures I left the system hung up on endles "device still expects data transfer" errors. After 20 minutes or so it booted. I am now installing Haiku, but the progress bar indicates I need large amounts of coffee.
comment:9 by , 15 years ago
Me too after letting it run a long time, it finally load but was terribly slow. I did succeed to load the installer and since i had dd a raw image into the first partition of my first drive, i could make it bootable with the installer.
So now i can use it with no problem at boot but my cdrom is not usable.
I'll add the syslog.
by , 15 years ago
comment:10 by , 14 years ago
Cc: | added |
---|
comment:12 by , 13 years ago
Blocking: | 7665 added |
---|
comment:13 by , 13 years ago
The trouble still remain in alpha 3 on my old Asus F7400 (PentiumIII@500)
comment:14 by , 13 years ago
Installed alpha 3 on the same motherboard as before, now without problems. Used a different CD drive, I no longer have the old one, so it's not actually a valid test.
comment:15 by , 13 years ago
Cc: | added; removed |
---|---|
Component: | - General → Drivers/Disk |
Description: | modified (diff) |
Version: | R1/alpha1 → R1/Development |
It seems that I have the same problem with my iRU Stilo 3314 COMBO in hrev43690.
ata 1 error : device still expects data transfer Last message repeated 509 times. bfs: mounted "Haiku" (root node at 131072, device = /dev/disk/atapi/1/maaster/0) Mounted boot partition: /dev/disk/atapi/1/maaster/0 ata 1 error : device still expects data transfer Last message repeated 2549 times. bfs: volume reports 189607 used blocks, correct is 189608 ata 1 error : device still expects data transfer
I think that the reason for this problem isn't included in the images, it should be some ata error between image 2 and 3.