Re: Unable to mount ext2fs partition
Hi Rahul, The mount capability has to be included as a kernel option in a custom build kernel. I forget exactly what it's called (I'm writing in another OS on the system, so I can't check it right now), but I think it's something like this: option EXT2FS Have you included that in your kernel build? /Paul Rahul Siddharthan wrote: Paul A. Mayer wrote: I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a real linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes Not a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
On Sun, 5 Jan 2003, Paul A. Mayer wrote: Thanks for this info. It's way beyond my technical understanding (which is truely minimal!), but I think I get the idea. What would this look like as a series of commands? Or better yet, what's the right way to share data between FreeBSD -current/coming and linux in a dual boot situation? ... Which is the real objective, (not playing with e2fs! ;.-) Well, what I do in practice is only mount ext2fs partitions as needed (mostly ro), so that most crashes don't leave them dirty. This works well enough since I only need them occasionally. Booting Linux to run e2fsck is easiest. I used the ext2fs utilities mainly to run fs benchmarks starting with clean file systems. Booting Linux to run mke2fs and e2fsck for every stage is not so easy. Unfortunately my shell script for doing this hasn't been updated to work with non-block devices. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Hi, I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes or the mount is uncleanly shut down. Then I have to use a linux livecd to repair the partition as the freebsd e2fsck often isn't able to clean up the mess. Regards, Paul Rahul Siddharthan wrote: I decided to bump my laptop up to 5.0-CURRENT today. All seems to have gone well and all my old binaries work fine, it looks very nice. However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Did something change when I install new bootblocks, and how do I fix it? Below, output from fdisk and disklabel. I don't remember anything unusual before the upgrade. Thanks, Rahul --- # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 13912227 (6793 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 865/ head 254/ sector 63 The data for partition 2 is: sysid 131 (0x83),(Linux native) start 13912290, size 5719140 (2792 Meg), flag 0 beg: cyl 866/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED # disklabel -r /dev/ad0s2 # /dev/ad0s2: type: ESDI disk: ad0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 356 sectors/unit: 5719140 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 5719140 13912290unused0 0 # (Cyl. 866 - 1221) e: 5719140 139122904.2BSD 1024 819216 # (Cyl. 866 - 1221) partition c: offset past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition e: offset past end of unit partition e: partition extends past end of unit To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
In message [EMAIL PROTECTED], Paul A. Mayer writes: Hi, I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes or the mount is uncleanly shut down. Then I have to use a linux livecd to repair the partition as the freebsd e2fsck often isn't able to clean up the mess. The kernel should probably printf a warning about this if it rejects the mount because the filesystem is dirty. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Hi Poul-Henning, I does printf, but it doesn't initiate the e2fsck. Using the ports e2fsck has not shown itself to be the way to do restore order. (I get et hav of ata unaligned access errors and lots of other garbage.) It's easier to boot up a Gentoo LiveCD and do it right.) Thanks, Paul [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Paul A. Mayer writes: Hi, I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes or the mount is uncleanly shut down. Then I have to use a linux livecd to repair the partition as the freebsd e2fsck often isn't able to clean up the mess. The kernel should probably printf a warning about this if it rejects the mount because the filesystem is dirty. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
On Sun, 5 Jan 2003, Paul A. Mayer wrote: I does printf, but it doesn't initiate the e2fsck. Using the ports It prints essentially the same mount failure message as ufs. e2fsck has not shown itself to be the way to do restore order. (I get et hav of ata unaligned access errors and lots of other garbage.) It always worked for me until block devices were axed. Apparently it still depends on random accesses to non-block boundaries and sizes working. It's easier to boot up a Gentoo LiveCD and do it right.) Or upgrade to FreeBSD-3 to get unaxed block devices :-. The ext2fs utilites work on regular files (better than ffs ones), so they can be used (very slowly and with muttering about axes) directly under FreeBSD by copying partitions to regular files, fixing them there, and copying them back. This is least painful for mke2fs since you can start with a sparse file instead of a copy of a partition. [Context lost to top posting] Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Hi Bruce, Thanks for this info. It's way beyond my technical understanding (which is truely minimal!), but I think I get the idea. What would this look like as a series of commands? Or better yet, what's the right way to share data between FreeBSD -current/coming and linux in a dual boot situation? ... Which is the real objective, (not playing with e2fs! ;.-) /Paul Bruce Evans wrote: On Sun, 5 Jan 2003, Paul A. Mayer wrote: I does printf, but it doesn't initiate the e2fsck. Using the ports It prints essentially the same mount failure message as ufs. e2fsck has not shown itself to be the way to do restore order. (I get et hav of ata unaligned access errors and lots of other garbage.) It always worked for me until block devices were axed. Apparently it still depends on random accesses to non-block boundaries and sizes working. It's easier to boot up a Gentoo LiveCD and do it right.) Or upgrade to FreeBSD-3 to get unaxed block devices :-. The ext2fs utilites work on regular files (better than ffs ones), so they can be used (very slowly and with muttering about axes) directly under FreeBSD by copying partitions to regular files, fixing them there, and copying them back. This is least painful for mke2fs since you can start with a sparse file instead of a copy of a partition. [Context lost to top posting] Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Paul A. Mayer wrote: I had to install the e2fstools port before I could access my e2fs partitions after installing -current. Thereafter everything has been fine. No problems with the disk, etc. Hm, didn't know about this port.. but it still doesn't include a mount program, and I still can't mount the partition even after installing the port. I don't want to fsck it and risk screwing it up: it's a real linux system (ie, a dual-boot machine) and the linux continues to boot perfectly nicely. But here's what I get with an e2fsck -n : # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? The only thing that is a problem is if your e2fs partion(s) are mounted and your system crashes Not a problem for me (it's likely to be mounted read-only anyway, and I can always boot into linux to fix it if it's dirty) - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
In message [EMAIL PROTECTED], Rahul Siddharthan writes: # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? Can you send us the output of sysctl -b kern.geom.conftxt please ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
[EMAIL PROTECTED] wrote: # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? Can you send us the output of sysctl -b kern.geom.conftxt please ? 0 DISK ad0 10056130560 512 hd 16 sc 63 1 MBR ad0s2 2928199680 512 i 1 o 7123092480 ty 131 1 MBR ad0s1 7123060224 512 i 0 o 32256 ty 165 2 BSD ad0s1e 6816876032 512 i 4 o 306184192 2 BSD ad0s1c 7123060224 512 i 2 o 0 2 BSD ad0s1b 201326592 512 i 1 o 104857600 2 BSD ad0s1a 104857600 512 i 0 o 0 - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
In message [EMAIL PROTECTED], Rahul Siddharthan writes: [EMAIL PROTECTED] wrote: # e2fsck -n /dev/ad0s2 e2fsck 1.27 (8-Mar-2002) The filesystem size (according to the superblock) is 714892 blocks The physical size of the device is 0 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/ad0s2: clean, 136602/357632 files, 456658/714892 blocks So what does that mean? Any way to fix it? Can you send us the output of sysctl -b kern.geom.conftxt please ? 0 DISK ad0 10056130560 512 hd 16 sc 63 1 MBR ad0s2 2928199680 512 i 1 o 7123092480 ty 131 1 MBR ad0s1 7123060224 512 i 0 o 32256 ty 165 2 BSD ad0s1e 6816876032 512 i 4 o 306184192 2 BSD ad0s1c 7123060224 512 i 2 o 0 2 BSD ad0s1b 201326592 512 i 1 o 104857600 2 BSD ad0s1a 104857600 512 i 0 o 0 Hmm, I can't see anything wrong here. I'm not an EXT2 specialist, and I don't really intend to become one, so I hope somebody else can help you out... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
[EMAIL PROTECTED] said on Jan 6, 2003 at 00:14:15: I'm not an EXT2 specialist, and I don't really intend to become one, so I hope somebody else can help you out... As posted earlier, there seems to be funny stuff on my ufs disklabel too: # disklabel -r /dev/ad0s1 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 204800 634.2BSD0 0 0 # (Cyl.0*- 12*) b: 393216 204863 swap# (Cyl. 12*- 37*) c: 13912227 63unused0 0 # (Cyl.0*- 865*) e: 13314211 5980794.2BSD0 0 0 # (Cyl. 37*- 865*) Warning, partition c doesn't start at 0! Warning, partition c doesn't cover the whole unit! Warning, An incorrect partition c may cause problems for standard system utilities Should I worry about that? As for the ext2fs partition: I can probably live with it. But it may bite more people after the -RELEASE Not sure whether this information is relevant, but the ext2 partition was originally a UFS partition. A few months ago I changed it to ext2 with freebsd 4.x's fdisk and then newfs'd with the linux mke2fs binary under linux emulation (FreeBSD 4.x, again). I then wrote a gentoo bootstrap filesystem to it and was able to boot it via grub. It's worked fine since then (I haven't messed with it again under freebsd, and it's mostly been mounted read-only). - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Unable to mount ext2fs partition
I decided to bump my laptop up to 5.0-CURRENT today. All seems to have gone well and all my old binaries work fine, it looks very nice. However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Did something change when I install new bootblocks, and how do I fix it? Below, output from fdisk and disklabel. I don't remember anything unusual before the upgrade. Thanks, Rahul --- # fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19485 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 13912227 (6793 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 865/ head 254/ sector 63 The data for partition 2 is: sysid 131 (0x83),(Linux native) start 13912290, size 5719140 (2792 Meg), flag 0 beg: cyl 866/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED # disklabel -r /dev/ad0s2 # /dev/ad0s2: type: ESDI disk: ad0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 356 sectors/unit: 5719140 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 5719140 13912290unused0 0 # (Cyl. 866 - 1221) e: 5719140 139122904.2BSD 1024 819216 # (Cyl. 866 - 1221) partition c: offset past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition e: offset past end of unit partition e: partition extends past end of unit To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
However, I can no longer mount my linux partition: when I try, I get # mount -t ext2fs /dev/ad0s2 /mnt ext2fs: /dev/ad0s2: No such file or directory Here's the ata/geom related parts of the dmesg output: - Rahul atapci0: VIA 82C686 ATA66 controller port 0x1420-0x142f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1420 ata0: mask=03 ostat0=50 ostat2=00 ata0-slave: ATAPI 00 00 ata0-master: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=50 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1428 ata1: mask=03 ostat0=50 ostat2=01 ata1-master: ATAPI 14 eb ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=00 stat1=01 ata1-slave: ATA 24 a5 ata1: devices=06 ata1: at 0x170 irq 15 on atapci0 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it ad0: success setting UDMA4 on VIA chip GEOM: new disk ad0 ar: FreeBSD check1 failed ad0: TOSHIBA MK1517GAP/A1.04 H ATA-5 disk at ata0-master ad0: 9590MB (19640880 sectors), 19485 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=5 cblid=1 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting UDMA2 on VIA chip acd0: LG DVD-ROM DRN-8080B/3.10 DVD-ROM drive at ata1 as master acd0: 512KB buffer, UDMA33 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc GEOM: Configure ad0s1, start 32256 length 7123060224 end 7123092479 GEOM: Configure ad0s2, start 7123092480 length 2928199680 end 10051292159 GEOM: Add ad0s1 hot[0] start 512 length 276 end 787 GEOM: Configure ad0s1a, start 0 length 104857600 end 104857599 GEOM: Configure ad0s1b, start 104857600 length 201326592 end 306184191 GEOM: Configure ad0s1c, start 0 length 7123060224 end 7123060223 GEOM: Configure ad0s1e, start 306184192 length 6816876032 end 7123060223 Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to mount ext2fs partition
Craig Rodrigues said on Jan 4, 2003 at 22:41:50: You truncated too much stuff, can you repost the whole dmesg output, not just the parts you think are relevant. OK, here it is at the bottom. Also, what do you get when you do the following: file - /dev/ad0s1a standard input: x86 boot sector, system, BSD disklabel file - /dev/ad0s1b standard input: Unix Fast File system (little-endian), last mounted on /usr2, last written at Fri Jan 11 13:34:17 2002, clean flag 1, number of blocks 6853713, number of data blocks 6642013, number of cylinder groups 210, block size 8192, fragment size 1024, minimum percentage of free blocks 8, rotational delay 0ms, disk rotational speed 60rps, TIME optimization file - /dev/ad0s1c standard input: x86 boot sector, system, BSD disklabel file - /dev/ad0s1e standard input: Unix Fast File system (little-endian), last mounted on /usr, last written at Sat Jan 4 22:46:06 2003, clean flag 0, number of blocks 6657105, number of data blocks 6451453, number of cylinder groups 204, block size 8192, fragment size 1024, minimum percentage of free blocks 8, rotational delay 0ms, disk rotational speed 60rps, TIME optimization And for file - /dev/ad0s2, it gives standard input: x86 boot sector, BSD disklabel HTH - Rahul --- Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sat Jan 4 13:49:25 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLUERONDO_CURRENT Preloaded elf kernel /boot/kernel/kernel at 0xc054. Preloaded elf module /boot/kernel/acpi.ko at 0xc05400a8. Calibrating clock(s) ... TSC clock: 799980311 Hz, i8254 clock: 1193294 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 799914775 Hz CPU: Pentium III/Pentium III Xeon/Celeron (799.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 129957888 (123 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00567000 - 0x07be7fff, 124260352 bytes (30337 pages) avail memory = 120438784 (114 MB) bios32: Found BIOS32 Service Directory header at 0xc00f74f0 bios32: Entry = 0xfd720 (c00fd720) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd720+0x11e pnpbios: Found PnP BIOS data at 0xc00f7540 pnpbios: Entry = f:a2f9 Rev = 1.0 pnpbios: OEM ID 1500110e Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06011106) Using $PIR table, 5 entries at 0xc00fdf70 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded09A 0x02 11 embedded09B 0x03 9 embedded0 11A 0x05 11 embedded07A 0x01 9 embedded07B 0x02 11 embedded07C 0x03 9 embedded07D 0x05 11 embedded01A 0x01 9 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 1, max = 6, width = 6 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 3, width = 3 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.PIB_.LNKA irq 9: [ 9 11 12] low,level,sharable 0.1.0 \\_SB_.PCI0.PIB_.LNKA irq 9: [ 9 11 12] low,level,sharable 0.7.0 \\_SB_.PCI0.PIB_.LNKB irq 11: [ 9 11 12] low,level,sharable 0.7.1 \\_SB_.PCI0.PIB_.LNKC irq 9: [ 9 11 12] low,level,sharable 0.7.2 \\_SB_.PCI0.PIB_.LNKD irq 11: [ 9 11 12] low,level,sharable 0.7.3 \\_SB_.PCI0.PIB_.LNKD irq 11: [
