This is how I do it all

Ehwaz · 08-24-2006, 11:45 AM

Wow, I just have to find some time to read all that info. Post #1 & #15 are found and put into a nice little text file with KWrite, so it's time to settle myself with some coffee and start reading. I do have a slackware box running, but just the basic, nothing fancy.

shilo · 08-24-2006, 02:08 PM

Just keep in mind that the SWareT section is wrong. I would recommend either skipping it, or setting the version to the current running version of Slackware (not "current")and not adding the LinuxPackages.net repo.

tamtam · 09-02-2006, 09:57 AM

Wish that I had read the last page before I read the first Shilo. Swaret just confused the system, luckily enough no damage done. I downloaded Droplink Gnome and followed your directions and when running Gnome I get the following error messages although it runs okay but with some graphics not working.

Code:

There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not work correctly.

The Settings Daemon restarted too many times.

The last error message was:

System exception: IDL:Bonobo/GeneralError:1.0 : Child process did not give an error message, unknown failure occurred

GNOME will still try to restart the Settings Daemon next time you log in.

and

Code:

The panel encountered a problem while loading "OAFIID:GNOME_MixerApplet".

tamtam · 09-03-2006, 11:17 AM

sorted dropline by doing the full install instead of basic.

What is the general view on using swaret and the config file. Have it installed but it doesnot seem to download any updates.

katayamma · 10-01-2006, 12:55 PM

Has swaret.org changed? It looks like your average "abandoned domain advert site" now.

Where on the site is the software?

katayamma · 10-01-2006, 01:09 PM

Ahh. I found it It's moved to http://swaret.sourceforge.net

18thBronzeman · 10-19-2006, 11:00 AM

Shilo is there a section on getting your network up? thanks.

my.dying.bride · 11-07-2006, 10:53 AM

Almost laughing...

Sorry for my english. Not a native. It is the second place I ever bothered filling out the "become member" scheme (yah lazy dogg...) thanks to this thread. Btw I notice that this thread already has produced some offsprings :=)
Went to your site Shilo. Nice and easy summed up what I would have loved to know some time ago. My opinion, but one of linux's major threats is unfortunately all this people with no clue about what goes on, but still throwing advices out everywhere and , hence wasting my time as a reader and make the famous "linux society" appear to be nothing more than a joke and a scene for some few exhibitionists. This was my problem when converting to linux. Back in those days, apart from own curiousity , what still kept me playing with linux was that occasionaly i stumbled over threads like this one. Informative threads, where the author does not become a pretentious know-it-all.
I send my thanks to Shilo and conclude with a well-meant and small advice to some people posting earlier in this thread: Virtualization is a gift (and wow... it even comes free (qemu)), especially when one is struggling with kernel compiling at its most basic. Even thought you later on will need to fine tune your hardware due to the fact that the virtual machines normally simulates different ones, the root file system is still the same

) And if you happen to not change the local version or using a different kernel source, all you need to do is untar your backup of your virtual harddisk and you'll be back on track

User Name. · 11-17-2006, 08:07 PM

I followed shilo's guide to installing a new kernel, but with a 2.6.17.1 kernel in stead of a 2.6.5 kernel. But the guide works for all kernels if you replace the kernel number.

I did everything correctly, or so it seemed until I rebooted. I reboot, and select Slackware, the selection with the 2.6 kernel, and then it loads for a second, and the screen is black for a while. I end up having to take out the battery from the hp dv5000t laptop to turn it off.

Any ideas?

resaguk · 11-18-2006, 07:00 AM

Quote:

Originally Posted by User Name.

I followed shilo's guide to installing a new kernel, but with a 2.6.17.1 kernel in stead of a 2.6.5 kernel. But the guide works for all kernels if you replace the kernel number.

[...]

Any ideas?

This sounds like it may be a problem with your video drivers - are you booting to a GUI or CLI?

User Name. · 11-19-2006, 02:02 PM

Quote:

Originally Posted by resaguk

This sounds like it may be a problem with your video drivers - are you booting to a GUI or CLI?

I boot to CLI all the time. Thats the way slackware starts; and you type startx if you want GUI.

resaguk · 11-19-2006, 02:06 PM

Quote:

Originally Posted by User Name.

I boot to CLI all the time. Thats the way slackware starts

Well it's certainly the defualt - you can change that though which is why I asked.

Anyway, at what point does the screen go blank?

(Are you using a frame-buffer at boot?)

duryodhan · 11-24-2006, 09:28 AM

Hey Shilo,
The links section of the site seems to be dated. Many links , (linuxguides, Slackcare et. al) don't work. How bout updating that section?

Eternal_Newbie · 12-02-2006, 09:10 AM

Quote:

Originally Posted by resaguk

Well it's certainly the defualt - you can change that though which is why I asked.

Anyway, at what point does the screen go blank?

(Are you using a frame-buffer at boot?)

It does sound like you forgot to include the framebuffer drivers.

I find that it is easiest to do a 'make oldconfig' on a .config file you know works (like the one that comes with the 2.6.17.13) and then make any adjustments from there with xconfig or menuconfig. It is easier remove extra stuff from a .config than build one from scratch, even following a step by step guide.

EDIT: It's just my 2c worth and I'm sure it's been mentioned before

pdw_hu · 01-02-2007, 10:07 AM

/etc/lilo.conf : use vga=normal.
post back if it still happens.