Bug 329878

Summary: wrong disk geometry for FUJITSU MHT2040AT
Product: [openSUSE] openSUSE 10.3 Reporter: michel munnix <michel.munnix>
Component: BasesystemAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: jkosina
Version: RC 1   
Target Milestone: ---   
Hardware: x86   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log
hwinfo --log hwinfo.log --disk
hwinfo --log hwinfo.log92 --disk on suse9.2

Description michel munnix 2007-10-01 16:59:35 UTC
Created attachment 175797 [details]
/var/log

parted unable to change partition table during install
SUSE 9.2 has no problem to access whole disk
Comment 1 michel munnix 2007-10-01 17:00:44 UTC
Created attachment 175798 [details]
hwinfo --log hwinfo.log --disk
Comment 2 michel munnix 2007-10-01 17:01:37 UTC
Created attachment 175800 [details]
hwinfo --log hwinfo.log92 --disk on suse9.2
Comment 3 michel munnix 2007-10-02 09:04:29 UTC
I think the problem is here in boot.log, the wrong size is choosen on the line with HPA unlocked: 11031296 instead of 71037938 


<6>scsi0 : ata_piix
<6>scsi1 : ata_piix
<6>ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x00011860 irq 14
<6>ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x00011868 irq 15
<6>ata1.00: HPA unlocked: 71037938 -> 11031296, native 78140160
<6>ata1.00: ATA-6: FUJITSU MHT2040AT, 8431, max UDMA/100
<6>ata1.00: 11031296 sectors, multi 16: LBA
<6>ata1.00: configured for UDMA/100
<6>ata2.00: ATAPI: HL-DT-STCD-RW/DVD DRIVE GCC-4241N, 0202, max UDMA/33
<6>ata2.00: configured for UDMA/33
<5>scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHT2040A 8431 PQ: 0 ANSI: 5
<5>sd 0:0:0:0: [sda] 11031296 512-byte hardware sectors (5648 MB)
Comment 4 michel munnix 2007-10-02 14:05:43 UTC
flashed latest bios, no change

when changing "IBM Predesktop Area" from normal to disabled -> no more HPA
-> full disk seen. But that's only a workaround.
Comment 5 Jiri Kosina 2007-10-02 16:22:02 UTC

*** This bug has been marked as a duplicate of bug 325552 ***