Re: FreeBSD 7.0 SATA Controller
the livefs cd links are 7.0-RELEASE ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/7.0/7.0-RELEASE-i386-livefs.iso 7-STABLE ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200804/7.0-STABLE-200804-i386-livefs.iso i tried these in vmware and on another computer and neither one drops me into a shell. they both put me in the sysinstall program and i have to activate the livefs from the fixit menu then go to virtual terminal 4 (alt+f4). problem is i cant get the livefs shell to start on my system. works fine in vmware, qemu, and my sisters computer so i know there isnt something wrong with the cds. Im really not too concerned about the bios bug. i just figured it might be a side effect of freebsd not being able access the disks. just out of curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic device supposed to do? as for not being able to mount any media from any freebsd 7.0 system. this includes when i rebuilt the kernel and world from 6.2 to 7.0 with the generic kernel. when i tried booting it was not able to find the root partition. the install and livefs cds can also not find the hard disks nor can you use the livefs utilities as stated above. On Sat, May 3, 2008 at 12:09 AM, Rick C. Petty < [EMAIL PROTECTED]> wrote: > On Fri, May 02, 2008 at 11:53:04PM -0400, Shaun Sabo wrote: > > the livefs cds do not drop you into a shell. they drop you into the same > > screen you see when you insert an installation cd. try it on qemu or > another > > virtualization program or even boot one up if you have a spare cd rom. > in > > order to access the livefs shell you need to navigate to the fixit menu > and > > then go to the livefs CD/DVD option. > > Please explain where you obtained said "livefs" CD. Every livefs CD I've > tried (in qemu) has dropped me to a shell. Every "fixit" CD I've tried > brings me to sysinstall and from there I drop to the shell after > navigating > the menus. > > > as for the apic vc acpi that was a typo > > due to exhaustion, sorry bout that. > > Sure, but which one do you mean? I assume you mean booting with or > without > ACPI, which is an option in the boot loader. > > > > > motherboard so i couldnt even boot the debian installer cd. i also > tried > > > > booting the freebsd installer disks without apic but the same > problem > > > occurs > > > > so i dont think its hanging because of the power managment. > > ACPI isn't just power management-- it's advanced _configuration_ and power > interface. My understanding is that if present, FreeBSD talks to the ACPI > on the BIOS to allocate IRQs and other resources. There have been bugs in > the past when dealing with ACPI which caused the FreeBSD devs to include a > boot option to disable it. If your system breaks w/o ACPI, then there's > certainly a BIOS firmware problem. > > Have you tried the following test? Cold boot (from power off) to FreeBSD > CD, disable ACPI from the menu, boot the kernel, then do a warm reboot and > see if the problem exists. My sense is that if your first attempt from a > cold start has ACPI enabled, the problem will persist for every subsequent > warm reboot. > > -- Rick C. Petty > ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 SATA Controller
> Im really not too concerned about the bios bug. i just figured it might be a > side effect of freebsd not being able access the disks. just out of > curiosity though, before i upgrade 6.2 to 7.0 again, what is the atpic > device supposed to do? My understanding is that atpic is the old way of mapping interrupts, and apic is the new way. If apic doesn't work for whatever reason, you need atpic. I was was getting lots of errors like Could not allocate irq attach returned 6 no driver attached Can't map interrupt -> can't attach driver -> can't talk to disks -> can't mount root ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 SATA Controller
On Fri, May 02, 2008 at 11:03:16PM +0100, Dieter wrote: > > > > > the next step im going > > > > > to take is installing 6.2 and remaking the world but adding device > > > > > aptic to the kernel. > > > > > > > > I think you mean "device apic" to the kernel? > > > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to add > > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to try. > > > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > > /usr/src on our RELENG_6 box and found absolutely no trace of said > > device. You are thinking of "apic". > > Typo. Should be "device atpic". Ah yes. That would be the classic AT-style PIC used for interrupt handling. That makes much more sense. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 SATA Controller
so does that mean i need to disable the apic? and are we talking about apic now or acpi? im getting all these devices confused now. i realize that acpi is dissabled when you press number 2 at the boot menu but are we talking about that or apic? On Sat, May 3, 2008 at 1:34 PM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Fri, May 02, 2008 at 11:03:16PM +0100, Dieter wrote: > > > > > > the next step im going > > > > > > to take is installing 6.2 and remaking the world but adding > device > > > > > > aptic to the kernel. > > > > > > > > > > I think you mean "device apic" to the kernel? > > > > > > > > No, it is "device aptic". It was in 6 but removed from 7. I had to > add > > > > aptic to get my nforce4-ultra board to boot 7. Given that 6 runs on > > > > Shaun's machine and 7 doesn't, adding aptic is a useful thing to > try. > > > > > > There is no "aptic" device on RELENG_6. I just did a grep -ri "aptic" > > > /usr/src on our RELENG_6 box and found absolutely no trace of said > > > device. You are thinking of "apic". > > > > Typo. Should be "device atpic". > > Ah yes. That would be the classic AT-style PIC used for interrupt > handling. That makes much more sense. :-) > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7.0 SATA Controller
On Sat, May 03, 2008 at 09:15:24PM -0400, Shaun Sabo wrote:
> so does that mean i need to disable the apic? and are we talking about apic
> now or acpi? im getting all these devices confused now. i realize that acpi
> is dissabled when you press number 2 at the boot menu but are we talking
> about that or apic?
ACPI: Commonly used for system configuration data (stored/controlled by
BIOS), power management, and a couple other things. Unrelated
to APIC and ATPIC.
APIC: Advanced interrupt routing IC; more or less used to extend
interrupt limitations of old PIC-based interrupts. Originally
there were 16 IRQs, most taken up by system necessities. An APIC
extends that to 256 IRQs, providing each device with its own IRQ,
assuming the OS supports APICs, otherwise it'll resort to
classic 16 IRQ behaviour (sharing of IRQs, etc.)
http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller
ATPIC: Classic 8259 PIC ("AT PIC"), 16 IRQ limitation, etc.
http://en.wikipedia.org/wiki/8259
Hope this clears things up for you.
I've never seen a system made in the past 7-8 years which demands the
use of atpic. Most present-day systems, even uni-processor systems,
have an APIC, and most of the time those work without issue.
If you want to disable the APIC, you can do so by booting FreeBSD
in "safe mode". It should be a menu item; I forget which number.
"Safe mode" will disable the following things:
* Disable use of ACPI
* Disable APIC
* Disable DMA capability on ATA devices (does not apply to SATA)
* Disable DMA capability on ATAPI device (CD/DVD-ROMs, etc.)
* Disabled hard disk write caching
* Disables kbdmux(4)
* Does something with hw.eisa_slots, which I don't quite understand.
Only "easy" reference I can find is to old Adaptec controllers
requiring hw.eisa_slots="12".
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
