headers
Dexter Filmore | 1 Jan 2006 18:52
Picon
Picon

Re: AsRock, the 3rd

> Hmmm... Interesting. Thanks for that information. My boss actually
> wanted to buy ASRock-based servers the other day ("Hey, that's cheap!").

Well, maybe you should let him buy them so he learns the hard way that
"cheap" means "crud".

(BTW since when does Asrock make server boards? Who would buy an Asrock board
for a mission critical production system? Apart from your boss (who is in
dire need for proper IT consulting.))

snip
> 
> Well, I have heard VIA chipsets actually work well... As long as
> they are used with a VIA mobo, and a VIA CPU, such as the C5. I
> have some good experience with VIA chipsets in the past, but I do
> agree their reputation is spotty, to say the least.

Thing is, VIAs chipset drivers for Windows straighten out most flaws in their
chips. With Linux you get what the kernel hackers were able to dig up, and
for some Distros they provide kernel patches, I think. Could be precompiled
kernel modules as well, not sure here. So - maybe since kt266a situation
might have lightened a bit, still I'd favor intel or nForce.

And consumer leftovers don't belong in a server. You need a server - buy
server hardware. What you save in consumer hardware you'll loose twice in the
long run in servicing burnt-out machines and compensating data loss etc.
Permalink | Reply | 1 comment |
headers
Dexter Filmore | 1 Jan 2006 18:56
Picon
Picon

Re: From 10.0 to 10.2.iso


/usr/bin/writeiso :

#!/bin/bash
cdrecord -v -dao -eject speed=<whatever> gracetime=3 dev=/dev/≤yourwriter>
driveropts=burnfree -data "$1"

pass iso name as an argument.
chmod +x ofc.
Permalink | Reply | 0 comments |
headers
Gil Andre | 2 Jan 2006 01:09
Picon

Re: AsRock, the 3rd


Hi Dexter,

(Happy New Year for 2006!!)

On Sun, 1 Jan 2006 18:52:48 +0100 Dexter Filmore <Dexter.Filmore <at> gmx.de> wrote:

> > Hmmm... Interesting. Thanks for that information. My boss actually
> > wanted to buy ASRock-based servers the other day ("Hey, that's cheap!").
> Well, maybe you should let him buy them so he learns the hard way that
> "cheap" means "crud".

No, because that would mean that *I* am stuck with servers made with crud.
I work long enough as it is, so I told him "Thanks, but no thanks" and 
explained the reasons why. Including the story about the exploding Windows
mobo, which convinced him not to buy the so-called "servers".

> (BTW since when does Asrock make server boards? Who would buy an Asrock board
> for a mission critical production system? Apart from your boss (who is in
> dire need for proper IT consulting.))

Which is why I advised him *not* to buy that machine. ASRock does not
make server mobo -- it was some cheap & dumb company that actually
offered servers based on ASRock motherboards. Yes, it's true. And yes,
I will never, ever, buy *any* of their products, servers or workstation.

> And consumer leftovers don't belong in a server. You need a server - buy
> server hardware. What you save in consumer hardware you'll loose twice in the
> long run in servicing burnt-out machines and compensating data loss etc.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gil Andre | 2 Jan 2006 01:23
Picon

Re: Dissatisfaction with Slackware - OMG!!!!


Hi Larry!

(Happy New Year!)

On Fri, 30 Dec 2005 18:53:06 -0600 Larry Alkoff <labradley <at> mindspring.com> wrote:
> Gil I read man lilo and man lilo.conf but found nothing about 
> configuring a "failsafe".
> 
> Could you tell me where to find info or tell me how to do it?
> Sounds like a very good idea.

Yes, it is. Except that I just checked the lilo.conf man page, and
it's not called a "fail safe", it's called a "fallback". Sorry, my
bad!

This is from "man 5 lilo.conf":

----------- 8< ----- Cut here ----- 8< -------------

fallback=<command-line>
Specifies a string that is stored as the default command line if
the current image is  booted.  This  is useful  when  experimenting
with kernels which may crash before allowing interaction with the system.
If using the fallback option, the next reboot (e.g.  triggered by a
manual reset or by  a  watchdog  timer) will  load  a different
(supposedly stable) kernel.

The command line stored by the fallback mechanism is cleared by
removing or changing the default command line with the -R option,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Larry Alkoff | 2 Jan 2006 03:13
Picon

Re: Dissatisfaction with Slackware - OMG!!!!

Gil Andre wrote:
> Hi Larry!
> 
> (Happy New Year!)
> 
> On Fri, 30 Dec 2005 18:53:06 -0600 Larry Alkoff <labradley <at> mindspring.com> wrote:
> 
>>Gil I read man lilo and man lilo.conf but found nothing about 
>>configuring a "failsafe".
>>
>>Could you tell me where to find info or tell me how to do it?
>>Sounds like a very good idea.
> 
> 
> Yes, it is. Except that I just checked the lilo.conf man page, and
> it's not called a "fail safe", it's called a "fallback". Sorry, my
> bad!
> 
> This is from "man 5 lilo.conf":
> 
> ----------- 8< ----- Cut here ----- 8< -------------
> 
> fallback=<command-line>
> Specifies a string that is stored as the default command line if
> the current image is  booted.  This  is useful  when  experimenting
> with kernels which may crash before allowing interaction with the system.
> If using the fallback option, the next reboot (e.g.  triggered by a
> manual reset or by  a  watchdog  timer) will  load  a different
> (supposedly stable) kernel.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Emon | 2 Jan 2006 18:50

MPlayer problem


Hi all

I am a newbie running Slackware10.2.
Recently I installed the pkg "Mplayer-1.0pre7" but when I try to
play a video from my HDD It gives me the following error

*********
Fatal error!
Error opening/initializing the selected video_out (-vo) device.
*********

but "gxine" can play the video.

mp3s are not giving me any trouble though, they run fine on both
of them.

So... can anyone please tell me what is it that I am doing
wrong.

Thanks
Emon
Permalink | Reply | 8 comments |
headers
Emon | 2 Jan 2006 19:18

arch & cpu number confusion


Hi all

I am a newbie

I read some where that Slackware packages are compiled with the
following options..

arch=486,cpu=686

I am very confused about the architecture & CPU number, where
can I read more to clear up my concept??

Thanks
Emon
--

-- 
Gllug mailing list  -  Gllug <at> gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug
Permalink | Reply | 16 comments |
headers
Martin Lefebvre | 2 Jan 2006 19:16
Picon

Re: MPlayer problem

Emon wrote:
> Hi all
>
> I am a newbie running Slackware10.2.
> Recently I installed the pkg "Mplayer-1.0pre7" but when I try to
> play a video from my HDD It gives me the following error
>
> *********
> Fatal error!
> Error opening/initializing the selected video_out (-vo) device.
> *********
>   
which interface are you using?

if using gmplayer, go in the settings, and set the video device (x11 or 
something, I thing the default is mga)
if using mplayer on the command line, use 'mplayer -vo x11' or something 
(use -vo help to see the available video out devices/drivers)
Permalink | Reply | 7 comments |
headers
Union Pivo | 3 Jan 2006 01:40
Picon

Re: Drivers for Nvidia

On 12/31/05, Geoff <capsthorne <at> yahoo.co.uk> wrote:
> On Sat, 31 Dec 2005 04:59:07 -0500
> Allen <slackwarewolf <at> comcast.net> wrote:
>
> > Hi list,
> >
> > I'm just wondering what everyone's experiences with the
> > Nvidia driver for their boxes.
> >
> > I installed it a minute ago and had no problems, and it
> > said it was done successfully so when I loaded X again I
> > saw the Nvidia screen, now is there anything left to do?
> >
>
> You can tweak a few settings by running "nvidia-settings"
> which brings up a nice little gui, and you have some
> options you can set in xorg.conf/XF86Config - I use
> Optio "NoLogo" to kill the splash screen.
>
> The Readme really is very good.
>
> http://download.nvidia.com/XFree86/Linux-x86/1.0-8178/README/index.html
>
> As to possible problems, well, I may be unique but from the
> day I started to use nVidia cards on this box (about 2 1/2
> years ago), I have suffered occasional hard lockups -
> screen mouse and kbd frozen, - impossible to ssh in - not
> even a ping response.  This generally happens when I am
> loading multiple images in a browser.
>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Krzysztof Chojnowski | 3 Jan 2006 04:18
Picon

Re: Drivers for Nvidia

Hi

2006/1/3, Union Pivo <union.pivo <at> gmail.com>:
> b) I do sometimes get hard freezes like GEOFF described, that i know
> are related to nvidia since they don't happen on free x drivers.
> Problem basically is when you open a lot of large pictures in multiple
> tabs in browsers (tested on firefox 9.x -> 1.5, and Konqeror kde
> 3.2-3.4.2) I think i tracked down problem to X server basically, bot
> konq and firefox store image data on server insted of clientside
> pixbuf, there were some discussions on kde that they will move this to
> clientside, I am not sure for mozilla. Symptoms, everything slows down
> even mosecursor becomes jerky, if you are lucky you have enough time
> to kill the window, if not everything freezes and not even
> ctr+alt+backspace work (nothing works relay, not even caps etc.). You
> hear have disk usage (swapping). I once left it for almost 12 hrs,
> that didn't help. The only solution, hard reboot.    Permanent
> solution, wait for kde to implement clientside image buffering in
> konq, and maybe also firefox. And don't open many tabs white large
> images inside.

I think this is a quite well-known nvidia-driver issue (for more info:
http://www.nvnews.net/vbulletin/showthread.php?t=31858 ). Some people
on that forum wrote that driver relase 8168 resolve this problem.
Unfortunately I can't check this, cause support for my GF2Ti ended at
version 7174 :(

--
Krzysztof Chojnowski
Permalink | Reply | 1 comment |

Gmane