The FreeBSD Installer is not detecting my Hard Drive.

Seph64 · 11-30-2003, 04:52 PM

1. I installed FreeBSD when I turned off detection of the 2nd drive in the BIOS, FreeBSD successfully installed itself on the 2nd HDD but I can not boot off the second drive using my boot loader (grub setup to boot FreeBSD), it says that the drive does not exist, thus I need to turn the HDD back on in the BIOS, and in which case it freezes at the same point.

2. I've tried booting with single user moder, and I still can not get past the HDD detection process in FreeBSD.

RJW · 11-30-2003, 05:04 PM

Oh, sorry. My crystall ball must have been playing games with me. How dare it tell me lies! =|

So, the only way for you to boot FreeBSD is with a bootloader that is located on the primary HD?

Seph64 · 11-30-2003, 05:10 PM

I don't remember metioning anything of the sort. I can't access FreeBSD at all, if I try to boot FreeBSD using grub while the 2nd HDD is turned off in the BIOS, I can't access the drive (although I could in the installation). If I try to boot FreeBSD when the 2nd HDD is turned on in the BIOS, it'll start the boot process, but get stuck at the boot screen.

Maybe I should turn off the first HDD in the bios, make the change, then turn first HDD back on?

RJW · 11-30-2003, 05:17 PM

No, you're right, you didn't mention anything of the sort... I'm trying to work out your problem for you.

Quote:

Maybe I should turn off the first HDD in the bios, make the change, then turn first HDD back on?

If you can boot from the FreeBSD drive alone, then yes, that is a great idea. =)

Seph64 · 11-30-2003, 05:20 PM

Turning off the first HDD doesn't work either. Maybe Chort is right and FreeBSD doesn't like the second HDD. Hmmm.

Seph64 · 11-30-2003, 06:21 PM

Quote:

Originally posted by RJW
Place the following in your `/boot/loader.conf' file:

Code:

hw.ata.ata_dma="0" hw.ata.atapi_dma="0"

I finally got my FreeBSD partition up and running properly, and adding those options to my /boot/loader.conf file did the trick. I am in FreeBSD right now.

Will the "ZAxisMapping" Option work in FreeBSD's MouseSystem mouse protocol? I'd like to get my mouse wheel to work.

Also, I need to install some things that I forgot to install when I installed FreeBSD, how can I do that? Something like sysinstall but I can not remember where.

Seph64 · 11-30-2003, 07:11 PM

NM I found sysinstall...

Now I got a new problem...

FreeBSD crashed when I tried to load the sound module for my computer. Now when I try to access KDE when I am a user, it'll exit X stating that it couldn't load knotify, it most likely crashed. I KNOW it crashed, can't you just boot KDE anyway?

KDE works in root though, which ticks me off since I do not want to be in root.

And it doesn't appear that the ZAxisMapping option doesn't work in FreeBSD.

RJW · 11-30-2003, 07:44 PM

Quote:

I finally got my FreeBSD partition up and running properly, and adding those options to my /boot/loader.conf file did the trick. I am in FreeBSD right now.

So what was the problem, and how did you over come it? BTW, you're welcome.

Quote:

Also, I need to install some things that I forgot to install when I installed FreeBSD, how can I do that? Something like sysinstall but I can not remember where.

You can install additional applications from `/usr/ports', providing you installed them. if not, then CVSUP the ports collection to build it.

Quote:

FreeBSD crashed when I tried to load the sound module for my computer. Now when I try to access KDE when I am a user, it'll exit X stating that it couldn't load knotify, it most likely crashed. I KNOW it crashed, can't you just boot KDE anyway?

Are you sure FreeBSD crashed? How about posting the log before jumping to conclusions. Also, post your `~/.xinitrc' file while you're at it.

Quote:

And it doesn't appear that the ZAxisMapping option doesn't work in FreeBSD.

ZAxisMapping does work with FreeBSD. Try `man xf86config' for help.

Seph64 · 11-30-2003, 07:51 PM

1) I figured out how to mount my FreeBSD partition in Linux.

2) Which log file do you mean? And my .xinitrc for my regular user is:

Code:

exec startkde

RJW · 11-30-2003, 07:56 PM

The log to watch is `/var/log/messages'. Also, what is the output from X to stdout?

Seph64 · 11-30-2003, 08:10 PM

The /var/log/messages file is too big to fit in a post. Will try to upload it.

http://seph64.hypermart.net/messages.txt

Hope this is of some help.

chort · 11-30-2003, 08:17 PM

Wouldn't it be better to startx | tee /tmp/xout.log
That way you would have the output from the Xserver logged.

RJW · 11-30-2003, 08:18 PM

Or just post the necessary logs.

Seph64 · 11-30-2003, 08:29 PM

I fixed it, somehow my user name (seph64 as with all of my login names for all Operatin Systems) got screwed up or something. I deleted the user name, and rebuilt it. And my problem was solved.

Thanks for all the suggestions, now I am one happy FreeBSD user (along with Linux).

Seph64 · 12-01-2003, 12:20 PM

I've got more problems. I can't login as root, the password I chose for it will no longer work. It must've got screwed up when I used kuser (KDE's User config program) to re-build my regular user account. I tried booting in with Single-User, but it mounts the FS read only so I can't make any changes to anything.

Anyone got any suggestions?