RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:32 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: [snip] I haven't had DOS for ages!! I really don't want to go that way. I will have to make DOS bootable CD-ROM, etc.. You've got to have it if only for the hibernation file. (Hibernation is worth it IMHO.) From memory, hibernation on the 600 doesn't have BIOS support. It works under Win9x with an extra program, but doesn't work under Windows 2000. I'm happy to be corrected though. I have a DOS partition on my ThinkPad 600, but never managed to get it working. -- | Matthew N. Dodd Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:09 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. That's useful. I shall try this. BTW, if you're not using CardBus cards, the OLDCARD functionality works fine. ie. comment out the cbb, cardbus and pccard devices in your kernel config and add the card and pcic devices. From my dmesg: cbb0: TI1251 PCI-CardBus Bridge mem 0x50102000-0x50102fff irq 9 at device 2.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1251 PCI-CardBus Bridge mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 The 600 uses a TI1250 instead of a TI1251. -- | Matthew N. Dodd Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problem with RC3
On Wed, 15 Jan 2003, Chris Knight wrote: It works under Win9x with an extra program, but doesn't work under Windows 2000. I'm happy to be corrected though. I have a DOS partition on my ThinkPad 600, but never managed to get it working. Hibernation should work on ALL thinkpads, probably back as far as the 701. I've got it working on a 560E as well. Just create a DOS filesystem sized say 16 megs larger than your system memory size and use the ps2 utility to create the hibernation file. 'ps2 hfile c' for example would create the file on C drive. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problem with RC3
hi all, firstly, hats off, great stuff! so far i have 2 problems to report: 1- I managed to boot of the cd, but later stage of the install refuses to recognize the cd. 2- tried to install over the net, 'em' is not in generic danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 2003-01-15 at 09:43, Danny Braniss wrote: hi all, firstly, hats off, great stuff! so far i have 2 problems to report: 1- I managed to boot of the cd, but later stage of the install refuses to recognize the cd. Which later stage, and what is the CDROM, and the machine? -- Ian Watkinson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 2003-01-15 at 09:43, Danny Braniss wrote: hi all, firstly, hats off, great stuff! so far i have 2 problems to report: 1- I managed to boot of the cd, but later stage of the install refuses to recognize the cd. Which later stage, and what is the CDROM, and the machine? when it wants to install, it asks from where, but choosing cd gives some error - cd not found or something. 4.7-stable acd0: CDROM CD-224E at ata1-master PIO4 danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 2003-01-15 at 11:06, Danny Braniss wrote: On Wed, 2003-01-15 at 09:43, Danny Braniss wrote: hi all, firstly, hats off, great stuff! so far i have 2 problems to report: 1- I managed to boot of the cd, but later stage of the install refuses to recognize the cd. Which later stage, and what is the CDROM, and the machine? when it wants to install, it asks from where, but choosing cd gives some error - cd not found or something. Can you access the CD in another OS, and does the bios see it ok? 4.7-stable acd0: CDROM CD-224E at ata1-master PIO4 So 4.7 sees it fine? What's the brand of the CDROM, and the model number? How is it connected? IDE? Scsi? PCMCIA? -- Ian Watkinson Systems Administrator EHS Brann To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Problem with RC3
Howdy, -Original Message- From: Matthew N. Dodd Sent: Wednesday, 15 January 2003 18:09 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Problem with RC3 On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. [snip] Hmm, ps2 doesn't specifically show a cardbus device. It does however have a PCIIRQ, which I set to 11,9,7,5 after disabling the parallel port and the sound. Same error crops up as mentioned above. cbb only gets an irq on my TP600 when acpi is loaded, so I'm going back to using OLDCARD. Interestingly, loader ignores my hint.acpi.0.disable=1 and acpi_load=NO settings in /boot/loader.conf and tries loading it anyway - even when manually setting them. Renaming the acpi module fixed it. Running current as of 20 hours ago. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, Jan 15, 2003 at 01:06:01PM +0200, Danny Braniss wrote: when it wants to install, it asks from where, but choosing cd gives some error - cd not found or something. 4.7-stable acd0: CDROM CD-224E at ata1-master PIO4 Try setting CD_ROM to slave mode. I have same problem with one Sony CD-ROM and one Acer. After setting CD-ROM to salve all works fine. -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
From: Chris Knight [EMAIL PROTECTED] Interestingly, loader ignores my hint.acpi.0.disable=1 and acpi_load=NO settings in /boot/loader.conf and tries loading it anyway - even when manually setting them. Renaming the acpi module fixed it. That should be: hint.acpi.0.disabled=1 Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problem with RC3
Hello all, I'm trying to install the new RC3 release on a laptop Toshiba SP6000. Problem is that Boot kernel from install CD (mini) hangs whith this message : ... acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE63 Using $PIR table, 7 entries at 0xc00f01d0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 o, pci0 and system hangs forever at this point. Not being really expert in boot, I don't know how to manage this. It was already the case with FreeBSD-RC2 but not with DP1, something happened inbetween. Sorry if this error has already been pointed, I am quite new to this mailing list and didn't read all previous mails (you bet...)**Thanx for any advice concerning this problem. Regards To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
Some typo in first message, here is a complete message btw : FreeBSD 5.0-RC3 #0: Fri Jan 10 23:09:54 GMT 6003 root@cypress\M-:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0aab000. Preloaded mfs_root /boot/mfsroot at 0xc0aab0a8. Preloaded elf mod\M-ule /boot/kernel/acpi.ko at 0xc0aab0ec\M-. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 995965111 Hz CPU: Pentium III/Pentium III Xeon/Celeron (995.97-mHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR,SSE real memory = 116785152 (111 MB) avail memory = 102088704 (97 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support(enabled md0: Preloaded$image /boot/mfsroot 4423680 bytes at 0xc062675c npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE0Block0 defined as GPE0 to GPE63 Using $PIR table, 7 entries at 0xc00f01d0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_dATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU on acpm0 acpi_tz0: thermal zone on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 regards - Original Message - From: Coercitas Temet'Nosce [EMAIL PROTECTED] To: FreeBSD current users [EMAIL PROTECTED] Sent: Tuesday, January 14, 2003 1:17 PM Subject: Problem with RC3 Hello all, I'm trying to install the new RC3 release on a laptop Toshiba SP6000. Problem is that Boot kernel from install CD (mini) hangs whith this message : ... acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE63 Using $PIR table, 7 entries at 0xc00f01d0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 o, pci0 and system hangs forever at this point. Not being really expert in boot, I don't know how to manage this. It was already the case with FreeBSD-RC2 but not with DP1, something happened inbetween. Sorry if this error has already been pointed, I am quite new to this mailing list and didn't read all previous mails (you bet...)**Thanx for any advice concerning this problem. Regards 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: Problem with RC3
On Tue, 14 Jan 2003, Coercitas Temet'Nosce wrote: I'm trying to install the new RC3 release on a laptop Toshiba SP6000. Problem is that Boot kernel from install CD (mini) hangs whith this message ... acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE63 Using $PIR table, 7 entries at 0xc00f01d0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 o, pci0 and system hangs forever at this point. Not being really expert in boot, I don't know how to manage this. It was already the case with FreeBSD-RC2 but not with DP1, something happened inbetween. At boot prompt, unset acpi_load. Has anyone documented this option? It should be in the release notes in flashing red as nearly all install complaints seem to be related to poor ACPI data. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
I wonder if it might be even better to disable it by default. Nothing turns people off like an OS that doesn't install. On 14 Jan 2003, Nate Lawson wrote: On Tue, 14 Jan 2003, Coercitas Temet'Nosce wrote: I'm trying to install the new RC3 release on a laptop Toshiba SP6000. Problem is that Boot kernel from install CD (mini) hangs whith this message ... acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE63 Using $PIR table, 7 entries at 0xc00f01d0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device .0 o, pci0 and system hangs forever at this point. Not being really expert in boot, I don't know how to manage this. It was already the case with FreeBSD-RC2 but not with DP1, something happened inbetween. At boot prompt, unset acpi_load. Has anyone documented this option? It should be in the release notes in flashing red as nearly all install complaints seem to be related to poor ACPI data. -Nate 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: Problem with RC3
Date: Tue, 14 Jan 2003 10:05:22 -0800 From: Francis Barnhart [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I wonder if it might be even better to disable it by default. Nothing turns people off like an OS that doesn't install. It should CERTAINLY be turned off on the install CDs and floppies! It was VERY frustrating to boot the CD on my laptop and have it crash after a few minutes. Kinda hard to get a crash dump, either. APM was never on by default in the past. Why should we have ACPI on on the install disks? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
On Tue, 14 Jan 2003, Kevin Oberman wrote: From: Francis Barnhart [EMAIL PROTECTED] I wonder if it might be even better to disable it by default. Nothing turns people off like an OS that doesn't install. It should CERTAINLY be turned off on the install CDs and floppies! It was VERY frustrating to boot the CD on my laptop and have it crash after a few minutes. Kinda hard to get a crash dump, either. The issue is, ACPI is needed to route interrupts for certain computers (namely, laptops). Without it being on, many laptops could not install the OS. I personally would prefer it being off by default with a recommendation to laptop users to enable it during the install in the install notes. But before the conversation gets off topic, I want to know where acpi disabling is documented so I can point people to the doc instead of answering the same question over and over. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
On Tue, Jan 14, 2003 at 11:10:03AM -0800, Nate Lawson wrote: But before the conversation gets off topic, I want to know where acpi disabling is documented so I can point people to the doc instead of answering the same question over and over. It's documented in loader(8), device.hints(5), and INSTALL.TXT. From INSTALL.TXT 4.2.1. My system hangs while probing hardware during boot, or it behaves strangely during install, or the floppy drive isn't probed. FreeBSD 5.0 and above makes extensive use of the system ACPI service on the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: set.hw.acpi.0.disabled=1 This is reset each time the system is booted, so it might be necessary to set it permanently in the file /boot/loader.conf. More inforation about the boot loader can be found in the FreeBSD Handbook. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
That is where this issue is documented. However, it is incorrect. The proper hint is in fact: hint.acpi.0.disabled While other ways exist, one way to solve the problem is: To allow the install to boot, at the boot prompt type unset acpi_load Then, after the install, add hint.acpi.0.disabled=1 to /boot/device.hints The way I understand it, setting the above hint to 1 disables acpi. If acpi_load is set and the above hint is not equal to 1, acpi will be loaded. So acpi_load is an abstraction of the hint (less typing). I also prefer that Those With Laptops have to deal with a more difficult install. (Are they a smaller user base?) Either way, the documentation should be probably be updated. If someone with the power to change the docs contacts me I'd be happy to submit an update. Francis Barnhart [EMAIL PROTECTED] http://francisbarnhart.com/ On 14 Jan 2003, Steve Kargl wrote: On Tue, Jan 14, 2003 at 11:10:03AM -0800, Nate Lawson wrote: But before the conversation gets off topic, I want to know where acpi disabling is documented so I can point people to the doc instead of answering the same question over and over. It's documented in loader(8), device.hints(5), and INSTALL.TXT. From INSTALL.TXT 4.2.1. My system hangs while probing hardware during boot, or it behaves strangely during install, or the floppy drive isn't probed. FreeBSD 5.0 and above makes extensive use of the system ACPI service on the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: set.hw.acpi.0.disabled=1 This is reset each time the system is booted, so it might be necessary to set it permanently in the file /boot/loader.conf. More inforation about the boot loader can be found in the FreeBSD Handbook. -- Steve 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: disabling ACPI in default install [was: Problem with RC3]
[[ Courtesy wrap of long lines. ] On Tue, Jan 14, 2003 at 11:42:58AM -0800, Francis Barnhart wrote: That is where this issue is documented. However, it is incorrect. The proper hint is in fact: hint.acpi.0.disabled Yes, you are correct. INSTALL.TXT should be updated. While other ways exist, one way to solve the problem is: To allow the install to boot, at the boot prompt type unset acpi_load Then, after the install, add hint.acpi.0.disabled=1 to /boot/device.hints Either way, the documentation should be probably be updated. If someone with the power to change the docs contacts me I'd be happy to submit an update. Grab INSTALL.TXT, make your changes, and post a diff -u. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
On Tue, 14 Jan 2003, Francis Barnhart wrote: That is where this issue is documented. However, it is incorrect. The proper hint is in fact: hint.acpi.0.disabled I think we can get by fine with: set hint.acpi.0.disabled=1 at the boot prompt. This keeps what we tell users to type consistent with what they add to device.hints. Scott, since you put the original message in INSTALL.TXT, could you correct the acpi disabling advice as shown above? The set command has invalid syntax (extra .) and there's a typo, inforation. Thanks, -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
Attached (and below my sig) is a diff of ACPI changes to INSTALL.TXT. Francis Barnhart [EMAIL PROTECTED] http://francisbarnhart.com/ --- /stand/help/INSTALL.TXT Fri Jan 10 18:21:12 2003 +++ INSTALL.TXT Tue Jan 14 15:34:00 2003 @@ -891,13 +891,14 @@ the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by - setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: + setting the ``hint.acpi.0.disable'' hint in the third stage boot loader: - set.hw.acpi.0.disabled=1 + set hint.acpi.0.disabled=1 - This is reset each time the system is booted, so it might be necessary to - set it permanently in the file /boot/loader.conf. More inforation about - the boot loader can be found in the FreeBSD Handbook. + This is reset each time the system is booted, so it is necessary to + permanently add hint.acpi.0.disabled=1 in the file /boot/device.hints. + More information about the boot loader can be found in the FreeBSD + Handbook. 4.2.2. My legacy ISA device used to be recognized in previous versions of FreeBSD, but now it's not. What happened? On 14 Jan 2003, Steve Kargl wrote: [[ Courtesy wrap of long lines. ] On Tue, Jan 14, 2003 at 11:42:58AM -0800, Francis Barnhart wrote: That is where this issue is documented. However, it is incorrect. The proper hint is in fact: hint.acpi.0.disabled Yes, you are correct. INSTALL.TXT should be updated. While other ways exist, one way to solve the problem is: To allow the install to boot, at the boot prompt type unset acpi_load Then, after the install, add hint.acpi.0.disabled=1 to /boot/device.hints Either way, the documentation should be probably be updated. If someone with the power to change the docs contacts me I'd be happy to submit an update. Grab INSTALL.TXT, make your changes, and post a diff -u. -- Steve --- /stand/help/INSTALL.TXT Fri Jan 10 18:21:12 2003 +++ INSTALL.TXT Tue Jan 14 15:34:00 2003 @@ -891,13 +891,14 @@ the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by - setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: + setting the ``hint.acpi.0.disable'' hint in the third stage boot loader: - set.hw.acpi.0.disabled=1 + set hint.acpi.0.disabled=1 - This is reset each time the system is booted, so it might be necessary to - set it permanently in the file /boot/loader.conf. More inforation about - the boot loader can be found in the FreeBSD Handbook. + This is reset each time the system is booted, so it is necessary to + permanently add hint.acpi.0.disabled=1 in the file /boot/device.hints. + More information about the boot loader can be found in the FreeBSD + Handbook. 4.2.2. My legacy ISA device used to be recognized in previous versions of FreeBSD, but now it's not. What happened?
Re: disabling ACPI in default install [was: Problem with RC3]
On Tue, 14 Jan 2003, Francis Barnhart wrote: --- /stand/help/INSTALL.TXT Fri Jan 10 18:21:12 2003 +++ INSTALL.TXT Tue Jan 14 15:34:00 2003 @@ -891,13 +891,14 @@ the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by - setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: + setting the ``hint.acpi.0.disable'' hint in the third stage boot loader: - set.hw.acpi.0.disabled=1 + set hint.acpi.0.disabled=1 - This is reset each time the system is booted, so it might be necessary to - set it permanently in the file /boot/loader.conf. More inforation about - the boot loader can be found in the FreeBSD Handbook. + This is reset each time the system is booted, so it is necessary to + permanently add hint.acpi.0.disabled=1 in the file /boot/device.hints. ^^^ to + More information about the boot loader can be found in the FreeBSD + Handbook. Other than that, looks great. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
Hello Again, Thanx all for your messages, I think I start to figure how it is handled. Problem still exists, system still hangs at agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 but I think it is in this way I may find a solution. Is there by chance anyway to see what will be load or not simply hitting SPACEBAR at prompt ? I didn't find any place where it is discussed nor a way to see the set variables that will be used to boot. Thanx for your messages :o) - Original Message - From: Kevin Oberman [EMAIL PROTECTED] To: Francis Barnhart [EMAIL PROTECTED] Cc: Nate Lawson [EMAIL PROTECTED]; Coercitas Temet'Nosce [EMAIL PROTECTED]; FreeBSD current users [EMAIL PROTECTED] Sent: Tuesday, January 14, 2003 7:10 PM Subject: Re: Problem with RC3 Date: Tue, 14 Jan 2003 10:05:22 -0800 From: Francis Barnhart [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] I wonder if it might be even better to disable it by default. Nothing turns people off like an OS that doesn't install. It should CERTAINLY be turned off on the install CDs and floppies! It was VERY frustrating to boot the CD on my laptop and have it crash after a few minutes. Kinda hard to get a crash dump, either. APM was never on by default in the past. Why should we have ACPI on on the install disks? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: disabling ACPI in default install [was: Problem with RC3]
On Tue, Jan 14, 2003 at 12:48:47PM -0800, Nate Lawson wrote: On Tue, 14 Jan 2003, Francis Barnhart wrote: --- /stand/help/INSTALL.TXT Fri Jan 10 18:21:12 2003 +++ INSTALL.TXT Tue Jan 14 15:34:00 2003 @@ -891,13 +891,14 @@ the i386 platform to aid in system configuration if it's detected during boot. Unfortunately, some bugs still exist in both the ACPI driver and within system motherboards and BIOS. The use of ACPI can be disabled by - setting the ``hw.acpi.0.disable'' hint in the third stage boot loader: + setting the ``hint.acpi.0.disable'' hint in the third stage boot loader: ^^^ d - set.hw.acpi.0.disabled=1 + set hint.acpi.0.disabled=1 - This is reset each time the system is booted, so it might be necessary to - set it permanently in the file /boot/loader.conf. More inforation about - the boot loader can be found in the FreeBSD Handbook. + This is reset each time the system is booted, so it is necessary to + permanently add hint.acpi.0.disabled=1 in the file /boot/device.hints. ^^^ to + More information about the boot loader can be found in the FreeBSD + Handbook. Other than that, looks great. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Tue, Jan 14, 2003 at 09:52:10PM +0100, Coercitas Temet'Nosce wrote: Thanx all for your messages, I think I start to figure how it is handled. Problem still exists, system still hangs at agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 but I think it is in this way I may find a solution. Is there by chance anyway to see what will be load or not simply hitting SPACEBAR at prompt ? I didn't find any place where it is discussed nor a way to see the set variables that will be used to boot. lsdev and lsmod show the devices that can be loaded and the deviced currently loaded, respectively. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
Ok, problem solved... Thanx for your notes, it helped a lot. For thse who may wonder, I simply changed 2 parameters : hw.pci.enable_io_modes Enable PCI resources which are left off by some BIOSes or are not enabled correctly by the device driver. Tunable value set to ON (1) by default, but this may cause problems with some peripherals. hw.pci_allow_unsupported_io_range Allow the PCI bridge to pass through an unsupported memory range assigned by the BIOS. Tunable value set to OFF (0) by default. can't say exactly which one prevented me from crash (surely 1st one but didn't tried any further). Dunno if it would be possible to prevent such things to happen by simply test it, I guess testing it will crash the whole system too. Thanx all btw, I learn, I learn :o) - Original Message - From: Steve Kargl [EMAIL PROTECTED] To: Coercitas Temet'Nosce [EMAIL PROTECTED] Cc: Francis Barnhart [EMAIL PROTECTED]; Kevin Oberman [EMAIL PROTECTED]; Nate Lawson [EMAIL PROTECTED]; FreeBSD current users [EMAIL PROTECTED] Sent: Tuesday, January 14, 2003 9:55 PM Subject: Re: Problem with RC3 On Tue, Jan 14, 2003 at 09:52:10PM +0100, Coercitas Temet'Nosce wrote: Thanx all for your messages, I think I start to figure how it is handled. Problem still exists, system still hangs at agp0: Ali Generic host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 but I think it is in this way I may find a solution. Is there by chance anyway to see what will be load or not simply hitting SPACEBAR at prompt ? I didn't find any place where it is discussed nor a way to see the set variables that will be used to boot. lsdev and lsmod show the devices that can be loaded and the deviced currently loaded, respectively. -- Steve 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: Problem with RC3
Francis Barnhart [EMAIL PROTECTED] writes: Have you tried disabling ACPI? If not try hitting space at the boot prompt and typing: unset acpi_load OK, this works for me, but then PCMCIA does not seem to work. -- Alexander Pohoyda [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On 15 Jan 2003, Alexander Pohoyda wrote: OK, this works for me, but then PCMCIA does not seem to work. The installer only supports NEWCARD (ie, PCI CARDBUS) devices. Do you have an ISA or PCMCIA only PCI based system? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
OK, this works for me, but then PCMCIA does not seem to work. The installer only supports NEWCARD (ie, PCI CARDBUS) devices. Do you have an ISA or PCMCIA only PCI based system? No idea, sorry. This is an IBM ThinkPad 600 notebook. If ACPI is disabled, no PC Cards are found at the boot time and inserting one later does not have any effect for the system. If ACPI is enabled, however, cards are detected, but removing them out of the tray brings the system in the state, where I can switch terminals (Alt+F1), I can turn off NumLock, but no other keys work. Same thing is happening if I insert some card. No beeps at all. So, if ACPI is enabled, I keep having Fatal traps 12... (acpi_thermal). If disabled -- no fun without peripherals :-) I have just installed 5.0-RC3. What else to try? Anyway, thanks to all developers for the great work!! -- Alexander Pohoyda [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 15 Jan 2003, Alexander Pohoyda wrote: If ACPI is disabled, no PC Cards are found at the boot time and inserting one later does not have any effect for the system. Set this fromt the loader: hw.cbb.start_memory=536870912 And disable ACPI. Anyway, thanks to all developers for the great work!! My 600E has real issues with ACPI; it works fine without (using APM). -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
If ACPI is disabled, no PC Cards are found at the boot time and inserting one later does not have any effect for the system. Set this fromt the loader: hw.cbb.start_memory=536870912 And disable ACPI. Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... The result -- no PCMCIA hardware detected. Inserting/removing a card has no effect, but system does not lock, at least! Should I type in whole dmesg here? My 600E has real issues with ACPI; it works fine without (using APM). Yes, that notebook worked great with 4.7-RC3, APM and there were no problems with PCMCIA. -- Alexander Pohoyda [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 15 Jan 2003, Matthew N. Dodd wrote: On Wed, 15 Jan 2003, Alexander Pohoyda wrote: If ACPI is disabled, no PC Cards are found at the boot time and inserting one later does not have any effect for the system. Set this fromt the loader: hw.cbb.start_memory=536870912 And disable ACPI. Anyway, thanks to all developers for the great work!! My 600E has real issues with ACPI; it works fine without (using APM). This is becoming a faq, add to ERRATA? -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Done. System is up and running. While booting I got messages: apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. From my dmesg: cbb0: TI1251 PCI-CardBus Bridge mem 0x50102000-0x50102fff irq 9 at device 2.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1251 PCI-CardBus Bridge mem 0x50101000-0x50101fff irq 11 at device 2.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at 1.2 ... ccb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 ... You'll need to use the 'ps2' utility to tell the system which IRQ to use for the cardbus bridge. Where do I get this utility? I had a Windows XP preinstalled , and it told me that PCMCIA uses IRQ 9. I'll try to put this into /boot/device.hints: hint.ccb.0.irq=9 I'll write back if this solves the issue. Thanks for your help! -- Alexander Pohoyda [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Where do I get this utility? Download it from IBM. Its part of the DOS management utils. You'll need to have a DOS partition setup so that hibernate works. I had a Windows XP preinstalled , and it told me that PCMCIA uses IRQ 9. I'll try to put this into /boot/device.hints: hint.ccb.0.irq=9 This won't work. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
Where do I get this utility? Download it from IBM. Its part of the DOS management utils. Well. This is not easy. I don't have a floppy drive, and I don't have DOS. I have, however, a second HDD with FreeBSD 4.7, where everything works allright. Can't I just get values from there? You'll need to have a DOS partition setup so that hibernate works. I haven't had DOS for ages!! I really don't want to go that way. I will have to make DOS bootable CD-ROM, etc.. I had a Windows XP preinstalled , and it told me that PCMCIA uses IRQ 9. I'll try to put this into /boot/device.hints: hint.ccb.0.irq=9 This won't work. Pity. Is there a reason why not!? -- Alexander Pohoyda [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem with RC3
On Wed, 15 Jan 2003, Alexander Pohoyda wrote: Well. This is not easy. I don't have a floppy drive, and I don't have DOS. I have, however, a second HDD with FreeBSD 4.7, where everything works allright. Can't I just get values from there? Nope. You can try to burn a windows/dos boot CD. In 4.7 you were using the cardbus bridge in compatibility mode without an assigned interrupt. You'll need to have a DOS partition setup so that hibernate works. I haven't had DOS for ages!! I really don't want to go that way. I will have to make DOS bootable CD-ROM, etc.. You've got to have it if only for the hibernation file. (Hibernation is worth it IMHO.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
