RE: Mandatory locking?
All the files under Tandem's NSK has mandatory locking. The file cannot be opened if another process has it opened. some thing like * if the file is opened for reading, any one can open it for reading but opening for writing gives error * if the file is open for writing, it can't be opened for read/write * if the process holding the file is killed, the lock is gone * it is possible to get the pid of the process(es) which has a given file open (like which process has file "xyz" open? kind of query). btw, is there any way to get this info now in FBSD? Also, file need not be explicitly locked. Opening a file puts proper lock. A file which is open can't be deleted also ;) This kind of locking will solve most of the problems which are pointed out. Mandatory locking on a part of the file is in no way better than advisory locking. All the files need not have this option. there must be a way to specify that "this file needs mandatory locking" to the kernel. I don't know what all changes are needed in the kernel.. but I'm thinking about dup() and fork().. What is the fate of the lock if the process does a fork()? I hope this makes sense.. -Biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Mandatory locking?
This isn't locking, it's access exclusion. It's also not correct for NSK. what is the difference between locking and access exclusion? i was thinking both are same (locking implies access exclusion). in other words, My idea of mandatory locking is same as exclusive access to the file. are we in sync? else tell me what exactly u mean by "Mandatory locking". NSK's OPEN procedure allows the following possibilities: - shared access. Any process can open the file unless another process has it opened with a different access. - exclusive access. Only this process can open the file. If it's already open, the open call will fail. - protected access. Only this process can have the file open for write. If it's already open for writing, the open call will fail. Fine. This is true. i didn't want to give too much details. What i want to tell is, there need not be a special call for lock. Combining lock/access exclusion with open will be better. Also, file need not be explicitly locked. Opening a file puts proper lock. I'm not sure what you're saying here. Opening a file doesn't lock it. same as above. put lock in open, not after getting fd. open should fail if file is locked. This will help programs unaware of locking to behave better. This kind of locking will solve most of the problems which are pointed out. Mandatory locking on a part of the file is in no way better than advisory locking. Again, I'm not sure how much of this you understand. I was thinking of doing something like NSK's LOCKREC function. LOCKREC locks records only. The problem is: processes A B. B doesn't know about locking (like 'cat') 1. A opened file 2. It locked some part of the file 3. B opens and starts to write 4. B reached the region which is lockd and write blocks 5. A releases lock 6. B's write is unblocked. Here, how mandatory locking of a region help? isn't this same as advisory locking? If opening itself fails coz of lock, the programs unaware of mandatory locking will be forced to start from begining. -Biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Mandatory locking?
All the files under Tandem's NSK has mandatory locking. The file cannot be opened if another process has it opened. some thing like * if the file is opened for reading, any one can open it for reading but opening for writing gives error * if the file is open for writing, it can't be opened for read/write * if the process holding the file is killed, the lock is gone * it is possible to get the pid of the process(es) which has a given file open (like which process has file xyz open? kind of query). btw, is there any way to get this info now in FBSD? Also, file need not be explicitly locked. Opening a file puts proper lock. A file which is open can't be deleted also ;) This kind of locking will solve most of the problems which are pointed out. Mandatory locking on a part of the file is in no way better than advisory locking. All the files need not have this option. there must be a way to specify that this file needs mandatory locking to the kernel. I don't know what all changes are needed in the kernel.. but I'm thinking about dup() and fork().. What is the fate of the lock if the process does a fork()? I hope this makes sense.. -Biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: Mandatory locking?
This isn't locking, it's access exclusion. It's also not correct for NSK. what is the difference between locking and access exclusion? i was thinking both are same (locking implies access exclusion). in other words, My idea of mandatory locking is same as exclusive access to the file. are we in sync? else tell me what exactly u mean by Mandatory locking. NSK's OPEN procedure allows the following possibilities: - shared access. Any process can open the file unless another process has it opened with a different access. - exclusive access. Only this process can open the file. If it's already open, the open call will fail. - protected access. Only this process can have the file open for write. If it's already open for writing, the open call will fail. Fine. This is true. i didn't want to give too much details. What i want to tell is, there need not be a special call for lock. Combining lock/access exclusion with open will be better. Also, file need not be explicitly locked. Opening a file puts proper lock. I'm not sure what you're saying here. Opening a file doesn't lock it. same as above. put lock in open, not after getting fd. open should fail if file is locked. This will help programs unaware of locking to behave better. This kind of locking will solve most of the problems which are pointed out. Mandatory locking on a part of the file is in no way better than advisory locking. Again, I'm not sure how much of this you understand. I was thinking of doing something like NSK's LOCKREC function. LOCKREC locks records only. The problem is: processes A B. B doesn't know about locking (like 'cat') 1. A opened file 2. It locked some part of the file 3. B opens and starts to write 4. B reached the region which is lockd and write blocks 5. A releases lock 6. B's write is unblocked. Here, how mandatory locking of a region help? isn't this same as advisory locking? If opening itself fails coz of lock, the programs unaware of mandatory locking will be forced to start from begining. -Biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. but this is done in steps of 1MB. Once it reaches out of memory, malloc should return NULL. Since there is no checking for NULL in this code, it should hit a signal, isn't it? Why that is not happening? -biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Well, yeah, that's becuase you're running it out of swap by trying to allocate a gigabyte of memory. but this is done in steps of 1MB. Once it reaches out of memory, malloc should return NULL. Since there is no checking for NULL in this code, it should hit a signal, isn't it? Why that is not happening? -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Odd, all of the machines that I've seen shipped lately have their CDROMs on a secondary IDE controller as SLAVE with no master. Works great, and the FreeBSD drivers work well when hacked to not require a master fo there to be a slave i commented out one line in wd.c, wdprobe() and it works fine... The funny thing is it checks for slave, its signature etc if ATAPI is defined and then returns a 0 saying "drive 0 error" !! (In this case du-dk_error is 0x7f) -biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Odd, all of the machines that I've seen shipped lately have their CDROMs on a secondary IDE controller as SLAVE with no master. Works great, and the FreeBSD drivers work well when hacked to not require a master fo there to be a slave i commented out one line in wd.c, wdprobe() and it works fine... The funny thing is it checks for slave, its signature etc if ATAPI is defined and then returns a 0 saying drive 0 error !! (In this case du-dk_error is 0x7f) -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Because it's wrong. If you don't believe me, buy a copy of the spec. Why should we waste valuable developer time trying to support mis-configured hardware? The box was shipped to me this way.. i'm no a hardware expert to know the IDE specs. As far as i know, it work for Windows (no flames) which i have been using for long. Suddenly if some one says that the PC is mis-configured... OK, i went to net and got this page (http://www.mit.edu/afs/sipb.mit.edu/project/linux/docs/faq/ATAPI-FAQ) there also they say it should be MASTER. Problem is not with me. The vendor didn't follow the specs. PC never followd specs i think ;) Some one please put this in an FAQ (if it is not already said) to avoid any future problem? thanks, -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
OK, i went to net and got this page (http://www.mit.edu/afs/sipb.mit.edu/project/linux/docs/faq/AT API-FAQ) there also they say it should be MASTER. Problem is not with me. The vendor didn't follow the specs. PC never followd specs i think ;) Some one please put this in an FAQ (if it is not already said) to avoid any future problem? second thought.. I have not seen a PC with CD at any other configuration... Cant this config be supported? Many like me are not good in opening the box and fixing the problem like other hackers. (But don't say i should not use FBSD with CD ;). any thoughts? -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Because it's wrong. If you don't believe me, buy a copy of the spec. Why should we waste valuable developer time trying to support mis-configured hardware? The box was shipped to me this way.. i'm no a hardware expert to know the IDE specs. As far as i know, it work for Windows (no flames) which i have been using for long. Suddenly if some one says that the PC is mis-configured... OK, i went to net and got this page (http://www.mit.edu/afs/sipb.mit.edu/project/linux/docs/faq/ATAPI-FAQ) there also they say it should be MASTER. Problem is not with me. The vendor didn't follow the specs. PC never followd specs i think ;) Some one please put this in an FAQ (if it is not already said) to avoid any future problem? thanks, -biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
OK, i went to net and got this page (http://www.mit.edu/afs/sipb.mit.edu/project/linux/docs/faq/AT API-FAQ) there also they say it should be MASTER. Problem is not with me. The vendor didn't follow the specs. PC never followd specs i think ;) Some one please put this in an FAQ (if it is not already said) to avoid any future problem? second thought.. I have not seen a PC with CD at any other configuration... Cant this config be supported? Many like me are not good in opening the box and fixing the problem like other hackers. (But don't say i should not use FBSD with CD ;). any thoughts? -biju To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Regardless, you have to have 1 master and 0 or 1 slaves one every IDE controller. You can't run a controller with just a slave. I dont think it should be a problem.. Since other OSs can work with this configuration without any problem, why FBSD should refuse this configuration? When i was using 2.2.7-stable, FBSD used to recognize my CDROM *sometimes* as slave, not always. -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 3:39 PM To: [EMAIL PROTECTED] Subject: IDE quirk in 3.2-STABLE kernel ? Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is "not found" However when I boot up under a 3.1-RELEASE "generic" kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 4:28 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: IDE quirk in 3.2-STABLE kernel ? Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
hi, I tried yesterday to make the kernel understand my CD ROM drive.. but it refused. Here is the dmesg (of boot -v)... is my config wrong or i missed something? The drive is Acer 32X and connected as secondary slave. It is seen by Win98 and BIOS. Can someone help? And what does "ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set" mean? -biju Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #0: Tue Aug 3 22:06:49 IST 1999 root@bash:/usr/src/sys/compile/bash Calibrating clock(s) ... TSC clock: 233886023 Hz, i8254 clock: 1193298 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 CPU: Pentium/P55C (233.87-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 16777216 (16384K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00285000 - 0x00ffdfff, 14127104 bytes (3449 pages) avail memory = 14139392 (13808K bytes) Found BIOS32 Service Directory header at 0xc00fae60 Entry = 0xfb2e0 (0xc00fb2e0) Rev = 0 Len = 1 PCI BIOS entry at 0xb310 DMI header at 0xc00f5cc0 Version 2.0 Table at 0xf1000, 25 entries, 557 bytes Other BIOS signatures found: ACPI: $PnP: 000fbf30 Preloaded elf kernel "kernel" at 0xc0274000. VESA: information block 56 45 53 41 02 01 6d 27 00 c0 00 00 00 00 14 00 00 01 10 00 03 01 04 01 00 01 01 01 05 01 11 01 14 01 10 01 13 01 02 01 06 01 12 01 7c 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 13 mode(s) found pci_open(1):mode 1 addr port (0x0cf8) is 0x8074 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) Probing for devices on PCI bus 0: found- vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Host to PCI bridge (vendor=1039 device=5597) rev 0x02 on pci0.0.0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 found- vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 ide_pci0: PCI IDE controller (busmaster capable) rev 0xd0 int a irq 14 on pci0.1.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 04 from port: 4002 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 400a found- vendor=0x1039, dev=0x7001, revid=0x10 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e200, size 12 found- vendor=0x1013, dev=0x00b8, revid=0x45 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 3, range 32, base e000, size 25 map[1]: type 1, range 32, base e2001000, size 12 map[2]: type 1, range 32, base e2002000, size 12 vga0: Cirrus Logic GD5446 SVGA controller rev 0x45 on pci0.9.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0x Comp ID: @@@ [0x] Called nullpnp_probe with tag 0x0001, type 0x3642630e port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 mss_attach CS42361 at 0x530 irq 5 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 flags 0x2 on isa sc0: fb0 kbd0 sc0: VGA color 16 virtual consoles, flags=0x2 ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d psm0: current command byte:0047 kbdc: TEST_AUX_PORT status: kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID: psm: status 00 02 64 psm: status 90 02 3c psm: status 90 02 3c psm: status 90 02 3c psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on
RE: IDE quirk in 3.2-STABLE kernel ?
Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju -Original Message- From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-hack...@freebsd.org]on Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 3:39 PM To: hack...@freebsd.org Subject: IDE quirk in 3.2-STABLE kernel ? Hi, On my system here, wd0: windoze wd1: FreeBSD wd2: blankdisk When I boot up under a 3.2-STABLE kernel (recently updated), wdc1 is not found However when I boot up under a 3.1-RELEASE generic kernel it sees the drive (wd2) and controller (wdc1) ok. (And yes I do have an entry for wdc1,wd2,wd3 in the config file for the 3.2-STABLE kernel) However, when I plugged in a CDROM drive in place of wd2, both kernels saw it ok. Maybe the wd2 disk has a quirk in it, but how come it works in one version and not in the next ? Any ideas ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju -Original Message- From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-hack...@freebsd.org]on Behalf Of Cillian Sharkey Sent: Tuesday, August 03, 1999 4:28 PM To: b...@wipinfo.soft.net Cc: hack...@freebsd.org Subject: Re: IDE quirk in 3.2-STABLE kernel ? Yes, i'm also facing the same problem in 3.2 stable (wdc1 not found at 0x170). When i put a CD-ROM (ATAPI, secondary slave) sometimes the controller comes up ;) I tried my own kernel (by changing the IDE delay), it didn't work. -biju Normally for my own kernel, I set the IDE delay very low (IDEDELAY=1000 in conf file) to speed up booting..I'll try increasing this for my 3.2-STABLE kernel, reboot and see if it detects wdc1 + wd2...Otherwise there must be something changed between 3.1-RELEASE generic and 3.2-STABLE ?? Cheers, - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
I tried with delay 12000, 6000, 8000 (I admit that i really don't know how this delay helps) but no use... only putting a CD in the drive while booting helps. -biju I just set IDE_DELAY=4000 in my 3.2-STABLE kernel, and now it sees all disks on both controllers. I think the problem was that one of my IDE disks is a Joe IDE device (TM). Depending on which controller it was put would cause that controller to be not found. Great! Ok, my problem is solved - don't know about that ATAPI drive of yours though...Is it only detected at boot time when there's a CD in it ? is it detected ok in other OS's without the need for putting the CD in ? True. The second wd controller is not recognized. Probably i will try with different delay. Even bios detects it as a ATAPI cdrom drive 32X! And yes!! i get a strange message while booting.. Since my box is at home, i cant give the error message.. probably tomorrow i'll be back with more findings cheers, -biju To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
hi, I tried yesterday to make the kernel understand my CD ROM drive.. but it refused. Here is the dmesg (of boot -v)... is my config wrong or i missed something? The drive is Acer 32X and connected as secondary slave. It is seen by Win98 and BIOS. Can someone help? And what does ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set mean? -biju Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #0: Tue Aug 3 22:06:49 IST 1999 r...@bash:/usr/src/sys/compile/bash Calibrating clock(s) ... TSC clock: 233886023 Hz, i8254 clock: 1193298 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 CPU: Pentium/P55C (233.87-MHz 586-class CPU) Origin = GenuineIntel Id = 0x543 Stepping=3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 16777216 (16384K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00285000 - 0x00ffdfff, 14127104 bytes (3449 pages) avail memory = 14139392 (13808K bytes) Found BIOS32 Service Directory header at 0xc00fae60 Entry = 0xfb2e0 (0xc00fb2e0) Rev = 0 Len = 1 PCI BIOS entry at 0xb310 DMI header at 0xc00f5cc0 Version 2.0 Table at 0xf1000, 25 entries, 557 bytes Other BIOS signatures found: ACPI: $PnP: 000fbf30 Preloaded elf kernel kernel at 0xc0274000. VESA: information block 56 45 53 41 02 01 6d 27 00 c0 00 00 00 00 14 00 00 01 10 00 03 01 04 01 00 01 01 01 05 01 11 01 14 01 10 01 13 01 02 01 06 01 12 01 7c 00 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 13 mode(s) found pci_open(1):mode 1 addr port (0x0cf8) is 0x8074 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=55971039) Probing for devices on PCI bus 0: found- vendor=0x1039, dev=0x5597, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Host to PCI bridge (vendor=1039 device=5597) rev 0x02 on pci0.0.0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 found- vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 ide_pci0: PCI IDE controller (busmaster capable) rev 0xd0 int a irq 14 on pci0.1.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 04 from port: 4002 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 400a found- vendor=0x1039, dev=0x7001, revid=0x10 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e200, size 12 found- vendor=0x1013, dev=0x00b8, revid=0x45 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 3, range 32, base e000, size 25 map[1]: type 1, range 32, base e2001000, size 12 map[2]: type 1, range 32, base e2002000, size 12 vga0: Cirrus Logic GD5446 SVGA controller rev 0x45 on pci0.9.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0x Comp ID: @@@ [0x] Called nullpnp_probe with tag 0x0001, type 0x3642630e port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 port 0x0534 0x0388 0x0220 0x irq 5:0 drq 1:3 en 1 mss_attach CS42361 at 0x530 irq 5 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 flags 0x2 on isa sc0: fb0 kbd0 sc0: VGA color 16 virtual consoles, flags=0x2 ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d psm0: current command byte:0047 kbdc: TEST_AUX_PORT status: kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID: psm: status 00 02 64 psm: status 90 02 3c psm: status 90 02 3c psm: status 90 02 3c psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0:
