Slackware/Gentoo/Debian - they all sound nice...but what would YOU recommend?

MasterC · 01-13-2003, 02:56 PM

I will be back and forth for a while now, so if you don't get an immediate response from me, hopefully someone else is following this thread and will help.

For now, I'd worry about getting networking up, then we will go onto the new kernel to get your mouse and other things running smoothly.

In the meantime, here's something for you to read over regarding PPPoE (Point to Point Protocol over Ethernet

):
http://www.tldp.org/HOWTO/PPP-HOWTO/c1609.html

Cool

MasterC · 01-13-2003, 02:58 PM

he he he, I love it when I post a thread only to see it's been covered in the meantime

You might look at the roaring penguin link from the link above.

Cool

MasterC · 01-13-2003, 03:00 PM

A quote from the Roaring Penguin website:

Quote:

Before you download this software, check whether or not you really need it. If your ISP uses PPPoE, but has given you a router, you may not need a PPPoE client on your Linux box. DHCP may work fine.

However, if you have a DSL "modem" and your provider uses PPPoE, you need a PPPoE client.

Since you used something like this in RH, I'm assuming you'll need it again now.

Cool

Faeroon · 01-13-2003, 04:16 PM

Let it got... it's of no use...
Just extracted all the tar.gz that Moses send me from his
own slackware 8.1 and tried to start maya..... guess what...
Error 6.... as usual....

I think this is it - if there's no miracle in the next hours I'm going to let go of Linux and go back to Windows....

MasterC · 01-13-2003, 04:46 PM

Damn! Hmmm, That's too bad then.. Get ahold of Moses, maybe he did a few things special that he could help you out with.

Whatever you decide, you can optionally have a dual boot just to play around with and use linux every so often if you'd like. I wish this maya thing would work out better for you!

Is there any alternative options, maybe some other equivilent software that you can try?

Oh well, good luck, and if you decide you want to give a go again, I will be here to help with the slack thing.

Cool

Faeroon · 01-13-2003, 05:34 PM

No.... I'm not willingly changing back to Windows...
I've done a bit research on this strange Signal 6 Error
and I got this:

Signal 6 is SIGABRT, which means that cc1 called abort(). It's a bug in gcc.

Ok... maybe it's a bug in gcc BUT after a long search I found THIS in the official AW Maya board:

I had exactly the same problem with RedHat 8.0.
After many try ... i finded that is the color depth the problem...
X-Windows must be set to 32 bits(or 24 bits). So, go to yours XF86Config
files and change de depth value to 24.

I had the same problem.
After browsing through this discussion forum
it seems a lot of people have had similar problems.
I had to make a change in the XF86Config-4 file.
Changing the depth from 16 to 24 in the screen section did the trick.

THAT could really be the problem!
I've got a GeForce4 from MSI and yet I've not managed to get anything else then 16bit.
32bit gives me:

Code:

(EE) VESA(0): Weight given (000) is inconsistent with the depth (32)

Code:

24bit gives me this:
(EE) VESA(0): No matching modes

I think it has something to do with the non-nvidia drivers at this moment. under windows I've got 1600x1200/32bit with no prob!

Soooo... I've got this tutorial how to install the newest nvidia drivers
for Redhat - maybe someone can tell me how to the same
install (with other file types - obviously not src.rpm but tar.gz) on slackware!

Maybe this will solve it!!!!
*has new hope*

macewan · 01-13-2003, 06:06 PM

debian

apt-get install firestarter
apt-get install etherape
apt-get install whatever

it's too easy

Faeroon · 01-13-2003, 06:11 PM

@macewan:

Hehe, yeah, maybe

But I'm not working with debian right now - I'm working with slackware 8.1 :-/
I've never worked with that before and maybe I've to do
something special with this new packagesystem or something like that.

I don't want to f*** up my system right now - I need to do this clean and good to the Maya a last time.

MasterC · 01-13-2003, 06:36 PM

First, do this:
uname -a
And check to make sure you have the kernel sources for that kernel in /usr/src

If so then:
ln -sf /usr/src/linux-2.4.19 /usr/src/linux
Replacing 2.4.19 with the actual kernel source directory. Now check to make sure the symlink works:
cd /usr/src/linux
You should now be in the directory /usr/src/linux-2.4.19

If you didn't install the kernel source, no biggie, just pop in your Slack CD, mount the cdrom:
mount -t iso9660 /dev/cdrom /mnt/cdrom

Change to the directory:
cd /mnt/cdrom/slackware/k
And then install the package:
installpkg kernel-source-2.4.18-noarch-4.tgz

Now make the symlink

Get this:
http://download.nvidia.com/XFree86_4....0-4191.tar.gz

And this:
http://download.nvidia.com/XFree86_4....0-4191.tar.gz

Untar each file:
tar xvzf NVIDIA_GLX(then press TAB)
tar xvzf NVIDIA_kernel (TAB)

Now you are gonna have to kill X to do the rest of this... To kill X:
CTRL ALT BACKSPACE
This should put you back at a command prompt with the user you have logged in with.

Make sure you are NOT booting into X after a restart (if you have edited this in /etc/inittab, change it back so you boot into a console only).

Now:
cd NVIDIA_kernel
then type:
make install
cd ../NVIDIA_GLX
make install

Now we need to edit your /etc/X11/XF86Config file, locate the section where it says either nv or vesa for the graphics driver and replace it with:
nvidia

At the beginning of the file, in the modules section, make sure you have this entry, and it's uncommented:
Load "glx"
And comment out these lines if they aren't already:
Load "dri"
Load "GLcore"
(to comment something means to place a # in front of it)

Ok, go ahead and go down for a reboot, and then when you come back up, you'll be at a login prompt, login and then try:
startx

Cool

Faeroon · 01-13-2003, 06:46 PM

Ok, have written it all down and going to try it now.
Wish me luck

MasterC · 01-13-2003, 07:19 PM

Good Luck! FYI, you don't have to write these things down, you could save it as a text file, then after the reboot just access the win partition and read the file with any text editor.

Cool

Faeroon · 01-13-2003, 07:41 PM

YEEEEEEEEEEEEEEEEEEEEEEES!!!!!!!!!!!!!!!!!
YEEEEEEEEAHA!!!!! I DIDN'T GIVE UP AND IN THE END IT'S WORKING!!!
MAYA 4.5 IS WORKING

All the time it was just my faulty display driver, running with 16bit!
Damn... who could have know ...Signal 6 Unknown Signal... Signal my ASS!

I'm going to post this all over the various boards to help all the
others that suffered from the same strange error.

Thank you SO much MC!

BUT: The race isn't over yet

Still I got this problems, before I can say I've got a fully functional system:

1.) System boots into black screen if I choose Linux from LILO

Here's the content of lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 800x600x256
vga = 771
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
  label = DOS
  table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hdb3
  label = Linux
  read-only
# Linux bootable partition config ends

2.) DSL
Gonna try the Roaring pinguin tomorrow

3.) USB Mouse Logitech MX500 with ALL buttons (is this possible?)
Still haven't got the mouse up and running - I'm using the
PS/2 adapter right now, but I guess I've got to recompile the kernel
for this?

4.) ALT Button's not working in Maya
In Maya you use the ALT Button to move /rotate/and pan around
in the scene (f.ex.: holding ALT and left mouse will pan the viewport)
but at the moment the ALT Button just let me move the maya interface window
(the entire application window) and that's not what I'm after.
Any ideas what I've to do?

So... that's it for the moment

I'm going to write the maya post and after that it's bedtime for me,
because it's again nearly 3 in the morning *yawns* but this time I can
sleep in peace

LINUX ROCKZ

Faeroon · 01-14-2003, 05:37 AM

Ok - once again a new day's here.
Any suggestions yet for the above shown probs?

Faeroon · 01-14-2003, 06:16 AM

Just worked a bit on the shell, changed the runlevel id
back to 3 yesterday and I experience something strange:

As I exit KDE there's some kind of error:
(unfortunately I only saw one screen of the log)

Code:

Mutex destroy failure: Device or resource busy
KDirWatch : removeDir couldn't handle '/usr/other-hd'

(PS: '/usr/other-hd' is where I mount the other windows/linux partitions)

Code:

Mutex destroy failure: Device or resource busy
ICE default IO error handler doing an exit() , pid = 215 , errno = 0
kdeinit : Fatal IO error: client killed
	*
	*
	*
	* (Stuff with no errors)
waiting for x-server to shut down
kdeinit: sending SIGTERM to children

And that's it - he waits and waits and waits, and nothing's happening.
I've killed that with STRG + C , but I would like to know what's going on
there.
I only get this error if I'm on runlevel 3, startx and try to reboot after
that - if I boot into runlevel 4 and reboot everything's fine
*scratches his head*

Grim Reaper · 01-14-2003, 06:42 AM

May i ask what is Maya?

Also, yes, your on the right track with roaring penguin...thats how you'll get online with PPPOE...

umm, what other issues were there...ah, the LILO stuff...

Ok, I think its the problem of the 'Lilo is being installed after the 1024th cylinder' problem...you can fix this by stuffing around in the BIOS, but that takes a fair few reboots...

One thing I'm wondering is how you getting into Windows...do you select it from the Lilo bootlist...
I'm a bit confused here at this bit...If LILO isn't working, then you shouldn't even be able to boot into Windows...so LILO must be working, and your able to choose either Windows or Linux from the bootlist, and when you select Linux it is giving you the black screen?..