PDA

View Full Version : Freebsd Installed


GhostDawg
January 28th, 2003, 21:42
Well I finally got Free 4.7 installed today. Now i need to get a few things configured, such as getting KDE running, getting my Lucent Winmodem, and a few other issues.

I'm at work now but when I get home, I will be posting error messages as I get them.

Kernel_Killer
January 28th, 2003, 22:43
HELLLLLL YEAH!!!!!!!!!!!!!!!!

Congrats GhostDawg!!!!! Hope you saw that post for KDE. Should help ya out. :D

bsdjunkie
January 28th, 2003, 22:48
sorry to bring this up. but you do know that 5.0-RELEASE cameout the other day? ;) :roll:

GhostDawg
January 29th, 2003, 03:29
Thnx Kernel_killer, I saw your post and I replied also.

Yes I kno, Bsdjunkie, but I have to get someone to burn me copies, since I use dialup at home! What a bummer...

Besides, this is my getting used to Freebsd and hopefully by the time I get a copy of 5.0 I will be good & ready to use Free. :D

GhostDawg
January 29th, 2003, 14:10
Ok i've made the .initrc file and still have errors trying to start KDE.

Here's the error messages Iget:

xsetroot: Unable to open display
xset: Unable to open display

Then it mention something about /tmp/.ICE-Unix should be set to root.

When i look into /tmp directory, everything in there is set to the Wheel group. How can Iset it to Root group?

Maybe this is my problem.

Thnx.

Strog
January 29th, 2003, 15:46
"chown user:group foo" will change ownership of file foo.

You can do "chown :group foo" if you want to change group ownership without changing the user ownership.

I've always had better success with ports than packages but since you are dialup I assume that you are going packages right now. :|

Are you starting it with startkde or startx?

GhostDawg
January 29th, 2003, 16:12
"chown user:group foo" will change ownership of file foo.

You can do "chown :group foo" if you want to change group ownership without changing the user ownership.

I've always had better success with ports than packages but since you are dialup I assume that you are going packages right now. :|

Are you starting it with startkde or startx?
I've tried it with both commands and get same error messages.

I will have to try the change groups i guess.

GhostDawg
January 29th, 2003, 17:20
Oops, I meant to say that when I type the command startkde is when I get those error messages.

I did change the owner of the .ICE-unix to root and now the message, Owner of /tmp/.ICE-unix error is gone, but I still have the other error messages:

Kwin can not connect to Xserver, along with Kpersonalizer can not connect to Xserver. This message continues to scroll down the screen until I press Cntl-C to stop it.

Anymore ideas/suggestions?

v902
January 29th, 2003, 18:37
Are you sure this is KDE not X? Have you tried running another DE/WM before with success?

Kernel_Killer
January 29th, 2003, 19:42
It's definatly trying to start another DE instead. Is it .initrc or .xinitrc that you made? If you have an .xinitrc, and see what it says. If it doesn't have a line saying 'exec startkde', there is your problem. That would be the script that X is running off of.

GhostDawg
January 29th, 2003, 20:15
It's definatly trying to start another DE instead. Is it .initrc or .xinitrc that you made? If you have an .xinitrc, and see what it says. If it doesn't have a line saying 'exec startkde', there is your problem. That would be the script that X is running off of.
Well in the other forum you said make it .xinirc which I did have to create the file, but it should be .xinitrc, so I will change the name to this.

I'll keep you all informed. If I type startx it will start the FVMW or some type of WM instead of KDE or Gnome.

What is the command to start Gnome?

Thnx.

Kernel_Killer
January 29th, 2003, 21:49
The startup command for GNOME is 'gnome-session. You might also see if there is a '.xsession' in your home directory.

GhostDawg
January 30th, 2003, 13:00
Thnx for all the help...I've finally got KDE and the mouse working correctly. I will check out the Gnome .xsession file next. I'm more of a KDE fan then Gnome, but I do like to make sure it's all running smooth! 8)

Next is gettting this PCI Lucent Winmodem working. Someone mention their is a port for the driver but I would need to be online to get it or would it be on the cd disc?

I need to know how to mount my Win98 partition(/dev/hda1) also, then I guess I could get the BSD Lucent driver for the modem.

Thnx.

silverlokk
January 31st, 2003, 05:26
mount -t msdos /dev/hda1mount-point, where mount-point is a directory on your BSD partition.

BTW, /dev/hda1 looks like a Linux-ism. On my PC, my hard drives are /dev/ad0 and /dev/ad2 (no second hard drive on the primary IDE channel so no /dev/ad1).

Regards

GhostDawg
January 31st, 2003, 21:39
So for /dev/hda1 in Freebsd it will be /dev/ad01?

Thnx.

GhostDawg
January 31st, 2003, 21:41
So for /dev/hda1 in Freebsd it will be /dev/ad01? What would my CD Drive be listed as, using Linux its /dev/hdb?

Would it be listed as /dev/ad1?

Thnx.

silverlokk
February 1st, 2003, 00:11
Probably. One way to check would be to issue the mount command from the prompt. The output will show you how your FreeBSD names the partitions. fdisk might also do it. On my PC, my hard drives are /dev/adx, and my CD-ROM drive is /dev/acd0. Might be different on yours.

Regards

GhostDawg
February 1st, 2003, 22:03
Thnx, I'll have to try it and read more on Free...

Kernel_Killer
February 2nd, 2003, 02:25
I don't have a link to it, and I don't have anything but a printed version, but out there is a UNIX/BSD/Linux/Solaris comparison chart of commands and drives. You might look for that to help you in your new venture.

|MiNi0n|
February 2nd, 2003, 11:12
To figure out where devices are look at your dmesg:

blender# grep -i cd /var/run/dmesg.boot
acd0: CDROM <CD-224E> at ata0-master using PIO4

blender# grep 1440 /var/run/dmesg.boot
fd0: <1440-KB 3.5" drive> on fdc0 drive 0

Use the mount command as well as has been suggested already. Though this will only show you mounted items and FreeBSD doesn't automount things lke cd-roms. I prefer df -h as you glean a bit more info.

Remember, if you're looking for a device, dmesg or /var/run/dmesg.boot is your best bet. Even if you have to look at it line by line until you find what you're after.