 |
| Register | Login | |||||
 |
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
|
| Register | Login | |||||
|
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
| 0 users currently in Hardware / Software. |
| User | Post |
| spiroth10 Posts: 133/145 |
I return with info!
I think it's registering my IDE hard drive (I know, I installed it myself) as an SCSI one <- Bad... anyway, the errors are ACPI: ACPI -0213 *** Error: AcpiLoadTables: AE_AD_CHARACTER and the same for namespace. along with something about non-ascii characters (again, my PC definitely supports ascii -- the hardware detection is screwing up royally.) boot up errors: I get these for da0, da1, da2 and da3 there is a -> pointing to d6 after all of them. its SCSI Status error (of course, I have no SCSI drives!) (da#: umass -sim:0:0:0:3) Not Ready csi-0,aa,55,40 asc: 3a, 0 those funky da#s I stated above are listed at the bottom with a -> da6 after I'm pretty sure it's detecting my IDE Hard drive as an SCSI one for some reason. What I need to know is why this is happening and how to fix it. Could it have been a problem when I installed it, or is it just BSD? |
| FreeDOS + Posts: 1268/1312 |
It's usually that some hotpluggable device (USB, Firewire, etc) hasn't fully initialized yet. But it *would* really help if you listen to Xkeeper's protip. |
| Xkeeper Posts: 5571/5653 |
Originally posted by spiroth10protip: this is the important part |
| spiroth10 Posts: 132/145 |
I'm doing an install of FreeBSD (now that I have DSL, Ports seems really nice to have)
At first, during the install screen, it said ACPI had failed (Don't even know what that is...). So I installed with the "Disable ACPI" option. No problem, right? Wrong. It did install successfully though. I go to boot it up, and it presents me with the installation menu again. Same problem, same solution. It boots to the splash screen. Takes awhile. Then, instead of a login or desktop, it brings me to a console with errors out the wazoo. I *Did* see a login option, but is was quickly covered in errors. they were all errors that something wasn't "ready". Not sure what, but it seemed to be a hardware issue. this is strange, my setup used basic hardware: LG monitor on an Nvidia card (supported) on my secondary 40GB SeaGate ST340810A (should be supported) Keyboard works. it might be something to do with the HD -- I took it out of an old PC and put it in my new one. Is there any reason this could cause issues? if not than whats going on here. I'm clueless... |
