VectorLinux

Cooking up the Treats => Distro development => Topic started by: nightflier on December 24, 2008, 12:41:07 pm

Title: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 24, 2008, 12:41:07 pm
Please post your comments and bug reports regarding the Light B1 release.

Happy Holidays!
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: EyesOnly on December 27, 2008, 08:53:28 am
Hi Nightflier,

I haven't tried this (yet anyway) but I am curious about something and would love to ask: Why was the LXDE desktop exchanged out in favour for the IceWM window manager this time around? I imagine this has already been discussed but I haven't seen it anywhere. At any rate, that was the big calling card for me in regards to VL-5.9 Light, which I currently use approximately 80% of the time now over the 6 installed distros on this rig. :)

I hope I haven't given offense, nor caused any upset by asking this question? I also like IceWM, and when it comes to JWM, IMHO only VectorLinux has been able to do it right---and this coming from a PuppyLinux user at that. (First thing I change in Puppy is JWM, one of the ones I use the most after LXDE in VL-Light!)

Thank you for your time Nightflier and others!

Amicalement/Cheers!

Eyes-Only
"L'Peau-Rouge"
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 27, 2008, 09:39:21 am
Hi EyesOnly

No offense whatsoever! Thank you for your feedback.  :)

LXDE is not included in Light because it is already an option in VL Standard. You can install it in Light using gslapt. Search for "lxde" and install those packages, To complete the setup, install Openbox as well.

Roy
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: EyesOnly on December 28, 2008, 06:43:35 am
Thanks Nightflier for taking the time to explain that as it's much appreciated! :) Yes, I never gave it a thought -slap head!-  that LXDE could be installed from GSlapt. duh! And besides, it only takes a few seconds/minutes at that.

Looks like I'll have to get my second computer fixed so I can place VL-6.0 Light on that. I'd replace my current 5.9 Light but I've highly-customised it to the point that it's become a "very good friend". ;)

Thanks once again Nightflier for the info!

Amicalement/Cheers!

Eyes-Only
"L'Peau-Rouge"
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: sparkyhall on December 28, 2008, 01:51:43 pm
Installed VL6.0 light B1 on an old IBM thinkpad 600 I have. Install went fine but I have noticed that the CPU load is very high (40% to 100%) with this install, obviously not good for battery life and I never had this issue with VL5.9 light.

After a little investigation I found that the problem is associated with ifplugged and if I kill the ifplugged daemon CPU load drops to around 3-4%. I should point out that this laptop has no network connection so it may be this that is causing ifplugged problems although being a laptop I would have thought the lack of network connection highly likely.

As a trial I installed VL6.0 standard RC1 to see how that performed on the same machine. This time the CPU load was 70% to 100% until I killed ifplugged at which point it dropped to around 14%. So it seems to be an issue with VL6.0 in general. For the record my IBM thinkpad 600 has a P2 300MHz CPU with 384M of memory.

If I find anything else I'll let you know,

Chris





Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 28, 2008, 06:15:49 pm
I remember having some trouble with ifplugd in my VL 5.8, so this is not unheard of. In VL 6 I have not seen this behavior on any of my machines, including a laptop, whether connected or not. Try disabling ifplug using vasm and see how that works (I usually disable inetd also).

If you haven't already done so, please post your findings in the Std. bug thread as well.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 28, 2008, 07:34:39 pm
Where can I find it?
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 28, 2008, 07:40:32 pm
Where can I find it?

Found it. The location used to be mentioned on this thread or not?
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 29, 2008, 12:21:36 am
hosted iso installation did not install kernel. Did it manually then.

Cannot configure my printer since Device 'unknow' absent in cups configuring, localhost:631.
It was there in Alpha-0.14 which is now my working linux box.

Dillo behaving properly. This post goes out with it.


Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: sparkyhall on December 29, 2008, 04:19:11 am
Try disabling ifplug using vasm and see how that works (I usually disable inetd also).

Yep disabling ifplugd in vasm fixes it. One thing I noticed is that ifplugd calls modprobe every other second and this seems to coincide with the CPU load going from 40% to 100%. When I say this laptop has no network connection I mean it has no nic installed so perhaps this is related. Time permitting I will try installing on another box with removable nic.

If you haven't already done so, please post your findings in the Std. bug thread as well.

Will do.

Chris
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Joe1962 on December 29, 2008, 08:22:24 am
You really need configure ifplugd to only control the interfaces you have/want/need. Also, wireless interfaces are notorious system hogs when they are out of range, or at the limit of the range of an AP.  As an example, whenever I boot to Windows XP for some gaming, I find that it is totally unusable way beyond the point when everything has loaded and right up to the moment when the "WiFi is not connected" popup shows. At this exact point, the CPU use drops from aprox. 100% to the usual 1 to 2%. The first time I figured out that the wifi was a hog was while trying to work at the limit of an outdoors AP at a sugar plant, when the realtime comms server program I was developing kept delaying the log scrollbox every second or so and then catching up! Finally figured that it all coincided with the wifi dropping connection and trying to reestablish it again. Since then, I tend to use ifplugd only for my wired ethernet and controlling the wifi manually, something I wish I could (as easily) do for Windows too.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 29, 2008, 06:51:19 pm
Burned a CD with vburn. Installation went smooth w/o any hick-ups.

This time I tried to connect a parallel printer to parallel port on mobo with cups
and get the Error after I enter Epson as my printer:
Unknown operation "{op}"!

In JWM mplayer still hangs desktop.

Now a question for my VL-6-A0.14-Light-pita working box.
As reported I have a small problem there with the sound, 'at' command as user will
not give sound, sometimes sound is gone and can be brought back with "sudo play file.wav"

Now I read in VL-6-STD-feedback that a new alsa driver is available:
http://vectorlinux.osuosl.org/veclinux-6.0/packages/drivers/alsa-driver-1.0.18a_2.6.27.10-i586-1vl60.tlz

If I will install that in my box could that solve my problem w/o creating more even so it is ment for kernel 2.6.27.10?

Regards
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on December 29, 2008, 07:13:24 pm
To use that ALSA package you must have kernel-2.6.27.10-i686-3vl60 installed.  The ALSA driver package is very much kernel specific.  Installing one against the wrong kernel is sure to break things.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 29, 2008, 07:32:54 pm
And don't forget the kernel modules:
http://vectorlinux.osuosl.org/veclinux-6.0/kernels/kernel-modules-2.6.27.10-i686-3vl60.tlz

The kernel sources are optional, but you will need them to install proprietary video drivers:
http://vectorlinux.osuosl.org/veclinux-6.0/kernels/kernel-src-2.6.27.10-i686-3vl60.tlz

I did a kernel plus alsa upgrade upgrade on B1. Looks good so far, and I see that Caitlyn is running 2.6.27.10 as well.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 29, 2008, 08:04:15 pm
Installed the whole set 2.6.27.10 and get again:

# /etc/rc.d/rc.inet1 start
Starting network eth0 using a DHCP server...
FAILED

I did a netconfig and same error.

With this I am at a loss what to do.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on December 29, 2008, 08:18:03 pm
You need to check to see if the module for your NIC is being loaded.  What type of ethernet card or chipset do you have?  Do you know what module it uses?  If so, check it with:

lsmod | grep <module name>

If it's not loadinging try, as root:

modprobe <module>

and try restarting your network again. 

If you don't know what card/chipset your system uses please post the output of lspci.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 29, 2008, 09:01:25 pm
 /sbin/lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 651 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 04)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

 /sbin/lsmod|grep sis
sis900                 20224  0
mii                     5376  1 sis900
i2c_sis96x              5124  0
i2c_core               21268  1 i2c_sis96x
sis_agp                 7936  1

I have a generic ethernet card called PRO200 from CNet. On the users' guide there is nothing
about modules. With all the various kernels there was never a problem for the last 12 or more
months.

Wrong, forgot I am plugged now into the mobo eth port for which I have no specs.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 30, 2008, 05:30:39 am
Does "ifconfig" show eth0? Can you bring it up with "ifconfig eth0 up"?
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on December 30, 2008, 05:56:05 pm
Surprise. This morning when I read your post to test your suggestion I
booted in to B1 and there I am connected.

I have tried several times with 2.6.27.10 both in A15 and A14 and in B1 and always got the FAILURE
message when trying to connect.

Beats me what did the trick that it worked now.
My old boss would have said: I'll be darn
Hope I can make it work in A14-pita.

HAPPY NEW YEAR

Edit:

Sigh, I just printed my first page!!!!!!

Next Edit:

Now I know what did the trick. It is the kernel version ..3vl60.tlz.
I had changed to it late last night and did not boot anymore.
I put this kernel now into my box VL6-A014-Light-pita and it too works there.
So kernel-2.6.27.10-i686-2vl60.tlz and its modules was not suitable or had a bug.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: sparkyhall on December 31, 2008, 06:18:34 am
When you insert an audio cd it does not mount. If I then try to mount manually I get the following message:

root:# mount /mnt/cdrom
mount: wrong fs type, bad option, bad superblock on /dev/hdc,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

The above is also true in VL6.0 std RC1 on a different box so I have reported this in the RC1 bug thread also.

I have to say I was more than a little dissapointed to find LXDE dropped from light but I have to say that now I am finding my way around icewm I rather like it.

Chris
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 31, 2008, 07:43:17 am
That behavior is normal, as there is no real file system on an audio cd to mount. Some applications may present the audio tracks as some kind of files, but they're not directly accessible. The tracks need to be ripped to an audio file before they can be copied or edited. You normally access an audio CD with a music player or a ripper.

LXDE is available in Standard or through gslapt, but I'm glad you are giving IceWM a chance. It is eminently customizable and capable. :)

Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: sparkyhall on December 31, 2008, 09:12:33 am
That behavior is normal, as there is no real file system on an audio cd to mount.

OK...Im just used to VL5.9 where the xmms player is started when an audio cd is inserted and I'm faily certian other distros auto start a player too. Obviously windows converts will expect a player to auto start when inserting an audio cd.

Chris
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on December 31, 2008, 03:13:32 pm
Obviously windows converts will expect a player to auto start when inserting an audio cd.

I agree with you there. Light is not a suitable drop-in replacement for Windows, nor was it intended as such. One of it's reasons to be is that it leaves more control in the hands of the user. Polling daemons and services are kept at a minimum. There will always be trade-offs.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: EyesOnly on January 04, 2009, 07:41:28 am
Quote from: nightflier
"One of it's reasons to be is that it leaves more control in the hands of the user. Polling daemons and services are kept at a minimum."

Aha! You hit the nail right on the head and described exactly why---out of the six distros I have installed on this rig---I keep coming back to VL-5.9 Light and why I've made it my "default distro". I've been trying to find the words to describe the "why" to people when telling them about this brilliant distro. Now thanks to you nightflier I have them!

This truly IS a rare gem in the ocean of distros. Most of them I've had to spend several days setting up to the way I like in order to be productive. When I installed this one (VL-5.9 Light that is) it was ready for me to work. I just needed to add Blackbox and a few more themes/gtk2 engines. ;) 6.0 is going to have to work pretty hard to top this so I'm really looking forward to it!

Thanks for allowing me a moment to express my thoughts.

Amicalement/Cheers!

Eyes-Only
"L'Peau-Rouge"
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: gamfa on January 04, 2009, 02:29:24 pm
I agree completely with EyesOnly. Light seems to follow the KISS way of doing things. This is why 6.0 Light has been my distro of choice since A14. I have found the replacement for Puppy.

There is a utility that Puppy has that I wish Light had. Pmount or Mut. I like to mount drives when "I" want them mounted. It is nice to use one of those instead of a console.

Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 04, 2009, 07:18:17 pm
I agree completely with EyesOnly. Light seems to follow the KISS way of doing things. This is why 6.0 Light has been my distro of choice since A14. I have found the replacement for Puppy.

There is a utility that Puppy has that I wish Light had. Pmount or Mut. I like to mount drives when "I" want them mounted. It is nice to use one of those instead of a console.



I am using fluxbox with xfce4-panel and there is an applet for mounting devices.
You can as well setup gkrellm for this purpose which is included in the LIGHT package.

And YES VL-6-LIGHT is THE distro. I new from the first alpha and mentioned it then.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 06, 2009, 07:34:07 pm
I have made VL-6-A014-Light my working Linux box fully running to my needs,
except one problem 'at' and 'cron' jobs will not play sound when commanded
by user.
This problem is present as well in slackware-12.1/2 from where I guess it was
inherited originally.

Now in the Beta version of light 'at' and 'cron' jobs do play sound when commanded
by user.

After having moved house I do not feel inclined to do it again just because of this problem.
I am therefore asking if a solution can be found for my present VL-6-Light box.

The error I get when trying to play sound with 'at' or cron is:

ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:3985:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM default
sox: Failed writing default: cannot open audio device

Would I have to copy just some files from Beta over to my box and which one?

Help much appreciated.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on January 06, 2009, 07:53:08 pm
Pita, did you run "alsaconf" again after installing the new kernel and modules? If not, give it a shot.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 06, 2009, 08:12:46 pm
Pita, did you run "alsaconf" again after installing the new kernel and modules? If not, give it a shot.

I think I did. Did it again now. Rebooted. Unmounted my working /home directory. Tried it.
Tried it in another users /home. Nothing doing. ???

BTW the other sound problem reported that sound suddenly would not play as user was solved.
It was an error in root crontab. Since sound in user crontab will not play I moved the commands
into root cron where it said "play sound in ./sound" when there is no such directory in root.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on January 06, 2009, 10:05:13 pm
alsa-driver is kernel specific.  Since you loaded the 2.6.27.10-3 kernel you need the matching alsa-driver package which Uelsk8s built.  If you found the post with the kernel you'll see that the alsa-driver package is also listed there.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 06, 2009, 10:35:53 pm
alsa-driver is kernel specific.  Since you loaded the 2.6.27.10-3 kernel you need the matching alsa-driver package which Uelsk8s built.  If you found the post with the kernel you'll see that the alsa-driver package is also listed there.

In an earlier post I mentioned that I installed the whole set, kernel, modules and alsa-driver.
That then made me configure my printer in Beta and connect to the internet.
There was no more such problem in A015 and in Beta iregardless what kernel/alsa-driver used.
Some hidden bug somehwere. (is it compliments of slackware?, and why)

The problem might not be with alsa it might be with some permission settings of at/cron.

Command "at now"
                    "play file.wav"
will not play and gives the above error.

Command "sudo at now"
                    "play file.wav"
will play the file and no errors.

This is naturally just for testing. I use 'at' with xmessage commands and sound to alert me
for things to do.

~:$ ls -l /usr/sbin/atd
-rwxr-xr-x 1 root root

:$ ls -l /var/spool/atjobs
-rwx------ 1 heisspf daemon
-rwx------ 1 heisspf bin

atjobs is set to 777.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: rbistolfi on January 07, 2009, 10:14:15 am
Pita:

I believe the problem is about permissions, but not in the /var/spool directory.
the at command is owned by daemon and the group is bin. That means the command is ran under another user id, i.e. daemon, instead your own. Probably, you would need to add the daemon user to the audio group to allow at to play sounds. I am over ssh now, I can check permissions but I can't check soundcard output, but you could give it a try.

HTH, Rodrigo
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 07, 2009, 08:33:58 pm
Pita:

I believe the problem is about permissions, but not in the /var/spool directory.
the at command is owned by daemon and the group is bin. That means the command is ran under another user id, i.e. daemon, instead your own. Probably, you would need to add the daemon user to the audio group to allow at to play sounds. I am over ssh now, I can check permissions but I can't check soundcard output, but you could give it a try.

HTH, Rodrigo

Thanks! How do I add the daemon user to the audio group?

Edit:

I just found it. It is in the /etc/group and surely on audio: my user name is missing.
Copied the /etc/group file of Beta over to my box and 'at' sound command came
roaring to live as well as the sound commands in user crontab.
Big sigh! :)  I have for me again the ultimate Linux Box, VL-6-LIGHT.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on January 09, 2009, 11:28:46 pm
I'm waiting for Beta 2 (or will it be rc1?) based on VL 6.0 Standard rc2.  I need the new kernel and new alsa-drivers for it to work correctly on my netbook and the new vxconf for it to work correctly on the old Toshiba.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Witek Mozga on January 10, 2009, 03:21:33 pm
Why is old version of Tcl/Tk included? There is a newer one which according to its website "8.5 now runs 10% faster than 8.4 with bytecode improvements, object caching and reduced memory usage." Furthermore it "Now uses anti-aliased text under X11".
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 10, 2009, 05:28:32 pm
Why is old version of Tcl/Tk included? There is a newer one which according to its website "8.5 now runs 10% faster than 8.4 with bytecode improvements, object caching and reduced memory usage." Furthermore it "Now uses anti-aliased text under X11".

You can find in slackware package browser.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Witek Mozga on January 10, 2009, 05:34:25 pm
You can find in slackware package browser.

Of course I can, I can compile myself too, but why not to include these files by default?
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Pita on January 10, 2009, 07:08:46 pm
You can find in slackware package browser.

Of course I can, I can compile myself too, but why not to include these files by default?

Search me. Must be the time lag.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: gamfa on January 10, 2009, 08:15:26 pm
Since VL 6.0 is based on Slackware 12.1, low and behold that's the version Slack 12.1 uses.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on January 11, 2009, 12:19:18 am
Yep, but we build our own packages and go with newer versions all the time.  I've put 8.5 on my to do list.  Witek Mozga is right.  We should have it.  Heck, our kernel in VL6 Std rc2 is newer than Slack 12.2 has.
Title: launching Opera from desktop ... accept/decline vanishes
Post by: Windozer on January 11, 2009, 10:14:17 am
fresh install of vl6 l. b1, no frills set up, just click and go.

Had rebooted to to b1 several times, but that's not necessarily specific to the following (?) ...

Clicked on either help/doc browser icons on desktop, which launches the initial legal disclaimer "accept/decline".

However, before I can get the mouse to it, the window vanishes. Clicking (desktop) browser icons repeats same. And am also unable to launch Opera from start menu option or manually from a terminal.

No other users created, logged in as root for all above.

Further info /testing if you need it.

(I like the looks, feel, and speed of this one, btw!)

ciao
- H
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on January 11, 2009, 01:22:31 pm
@Windoze:
When you try to launch opera from a terminal, do you see any error messages?

New Tcl/Tk? Thanks for pointing that out, will check on it.

Caitlyn, considering the new kernel, next version will be B2. Working on it ;)
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: caitlyn on January 11, 2009, 03:02:44 pm
Uelsk8s is building the new tcl/tk packages for VL6 and they will be in Standard Gold.  The 64-bit package is already in the repo.  I don't know if he's got a 32-bit version done yet.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Windozer on January 12, 2009, 11:29:09 am
When you try to launch opera from a terminal, do you see any error messages?

Nothing in the terminal -- just returned to the prompt after a quick second. htop shows opera start and stop ... too fast to catch each time ... so I assume something's crashing.

Should I look at specific /var/log file? Or did the TK thing above make this moot?

ciao
- H
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on January 12, 2009, 12:09:15 pm
Don't think Tcl/Tk should affect Opera, which uses qt. Would you delete the ".opera" folder in your home directory and try to launch opera (from a terminal) again?
 

I did build and test tcl/tk 8.5.6. It caused problems with a version of aMSN that ran fine using the old 8.4.18. I'll wait until I get Uel's packages and see how that goes.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Windozer on January 12, 2009, 07:50:40 pm
Oh, sorry, Nightflier,

looks like I may have dorked this one  :-[ ... something's amiss in my network setup. Think I clicked the wrong  option during install. Dillo, HV3, also bomb - and ifconfig is bizarre looking --- when it even comes up that is ???. 

Am posting this reply now on the same machine, same net, using firefox on a VL6 rc1 partition - so the hardware's OK.

hmmm. I'd say not to worry about this one for now.  ::) ;D

thanks,
Howard in FL
~~~~~~~~
ERROR #2: Q.A. Testor dozing on keyboardddddddddddddddddddddddddddddddddddddd.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Windozer on January 13, 2009, 06:39:24 pm
Well, maybe there's an issue or two here after all (or I don't know what I'm doing ... which is more likely  :P)

1. After slicking the partition and doing a full reinstall, autoconfig didn't recognize the NIC on the machine. (The NIC does work - and both VL 5.9 and 6 rc1 installed on the same machine spotted it.)  Back in Light B1, from VASM, I then tried to autoconfig again for the network. In both instances, (install and reconfig), attempting to add an inet showed no NIC's, just the dummy0.

When it was trying to do this, including selecting dummy, the underlying terminal showed errors about modprobe not finding a library ... sorry, I will learn this better at some point ... I don't know how to grab that screen again to see what it actually says. Yes, I did note the mention in the inet set up that modules may have to be loaded with autoconfig, or manually.

Am I missing a module for my NIC, and if so, please accept my apologies for being a noob trying to troubleshoot when maybe I should hang around in the vectorbee part of the forum a while longer! ::)

would a /var/log show what's happening here?

BTW, when I tried this under JWM, the accept/decline window didn't vanish, I could click "accept" - and opera ran showing a network problem ... as we would expect.  MWM's pager didn't seem to function (or had undefined items) as the right click menu's were blank, but the menu box itself was visable. Had to hit the panic button to get out of that one.

2. Just noticed an odd glitch as I was posting this from another machine: I left B1 running as root at init level s, and had done a simple 'ls' ---  after several minutes, the screen blanked out all the white-lettered items, but left the blue colored one's showing... weird...  I had not selected the powersave stuff at install

thanks
- Howard in FL
(trying to be helpful)
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: bigpaws on January 13, 2009, 06:53:40 pm
In order to help can you please let us know what the name and model
of your NIC card? Without that it is hard to start.

If you are not sure as root in a terminal type:

lspci

and look for a reference to your NIC card.

Bigpaws
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Windozer on January 13, 2009, 07:44:30 pm
Hi Bigpaws,

thanks for being so ready to help --- what would we do without you?  ;D

OK, here's what lspci says re the onboard NIC:

Code: [Select]
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
BTW, I literally *just* installed VL 6, RC2 ... and it failed to spot this NIC, whereas VL6, RC1 did before!

thanks
- H
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: bigpaws on January 13, 2009, 09:30:26 pm
There is an RC 3.

You can check to see if the module is loaded. In a console as root type:

lsmod | grep rtl8139

If there is no return try this in the same console:

modprobe rtl8139

Then check again to see if it is loaded with the first command. If it is then activate the NIC:

ifconfig eth0 up

Now you should be able to use VASM to configure the card.

HTH

Bigpaws
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: EyesOnly on January 15, 2009, 03:42:45 am
Quote from: Windoze
"thanks for being so ready to help --- what would we do without you?"

Windoze wrote that in regards to BigPaws, and I have to agree whole-heartedly!

In fact, all you guys and gals (let's not forget Caitlyn & GrannyGeek amongst others!) are really a group of very special people and you don't receive anywhere near the amount of thanks and praise which you so rightly deserve!

Thank you all from the bottom of our hearts for the selfless work and dedication you give to see that VectorLinux is one of the best distros available today, and its support forum IS the best on the net! *thunderous applause for the team!*

Amicalement/Cheers!

Eyes-Only
"L'Peau-Rouge"
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: Windozer on January 15, 2009, 11:56:08 am
*thunderous applause for the team!*

Whistle! Whistle! Clap! Clap!

(Our monitors are shaking from applause vibrations!)

Encore!
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: lm8 on January 16, 2009, 04:29:23 pm
Mouse (actually laptop pad) is working better than in 5.9 Light.  Don't know if it's because I didn't take the default install on X-Windows this time or not.  Before, the drag and drop wasn't working with touchpad.  Seems slower than 5.9 Light.  Tried going into vasm and changing Windows Manager to speed it up.  Does the change not affect root?  I see .xinitrc in /etc directory changed, but root has same settings in /root/.xinitrc.  Wanted to run Fluxbox to see if it would speed things up, but it wasn't installed on the disk and icewm seemed rather slow.  Got as far as testing out video and audio and they worked.  Haven't tested midi sound or USB connections yet.  Everything I tried seems to be working okay so far.  I'm running a pentium MMX 500 MHz, 64 MB RAM and 6 GB hard drive if it helps to know that.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on January 17, 2009, 11:55:59 am
Why is old version of Tcl/Tk included? There is a newer one which according to its website "8.5 now runs 10% faster than 8.4 with bytecode improvements, object caching and reduced memory usage." Furthermore it "Now uses anti-aliased text under X11".

After some pretty extensive testing, we found that upgrading tcl/tk required extensive changes to base system, rebuilds of current tcl/tk packages in repo, and would break compatibility with Slackware 12.1 packages. The decision was made to leave things as they were.
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: nightflier on January 17, 2009, 12:00:32 pm
@lm8:

The vasm script to change window manager is getting a little out of date. The preferred method nowadays is to use GDM or KDM to select your environment. Did you try that?
Title: Re: Vector 6.0 Light B1 feedback and bug reports.
Post by: budulay on January 20, 2009, 06:55:51 am
Hi
Sorry for not posting this before. I know there is Beta2 out, and the first thing I will do today when I will get home is downloading that. Still, I hope maybe this post may help, since I also had this problem in VL6.0-Dynamite0.7, but I had no time to try fixing it.

Anyway, when I installed beta1 on my Dell Dimension XPS(Will give the specs when I get home) with Yamaha video card and booted, it said: "No Screens Found" and refused to start X. I had VL5.9 STD running on the same computer, so the first thing I did  - I got the xorg.conf from the working vl5.9 install and put it there. Still no go(same no screens found message).
During the instalation vxconfig(I hope I remember correctly) refused to configure video, so I switched to vesa, which gave me results mentioned above.
I serched this forum and then tried:
Launching vxconfig from the CLI when I got no screens error and trying to configure video there. It basically gave me the same thing as duging instalation. I also tried switching to the other default driver offered in vxconfig(the one besides vesa). Gave me the same error.
After that I tried X-config(I think I am not spelling that correctly), entering vertical and horisontal Sync from the xorg.conf file taken from the working vl5.9 STD on the same computer. Got the same thing.
I believe that's all I tried to fix that.

Also get no internet configured during install(I have ehrenet-usb adapter connected to computer's usb port and to my router's ethernet port.) launching dhcpcd got it rolling :D
In VL5.9 I had to manually add DNS server to get it working.

I take this back - I had to run dhcpcd sfter each boot to make it work. But after I edited rc.local as nightflier said here (http://forum.vectorlinux.com/index.php?topic=8268.msg56498#msg56498), everything works.

ps. I am sorry for not telling anough about the specs of my computer and misspelling commands, but I am not at home right now and posting this from memory. As soon as I will get home I will revise this post to include that information.

update:
Installed Beta2 and the same thing happens there too, so I will post my more detailed observations in beta2 bug report.