VectorLinux

Cooking up the Treats => Distro development => Topic started by: vector on March 21, 2011, 12:20:27 am

Title: VectorLinux 7 Beta2 bugs and observations
Post by: vector on March 21, 2011, 12:20:27 am
Please report bugs, comments and anything of use to help us get to vector7 final here . Please only reports from a full installation of the current beta2 should go here.

Thanks,
Vec
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 21, 2011, 03:35:08 pm
I downloaded the ISO, checked the md5sum, and burned a CD. I installed on my two desktops: Athlon 64 X2 with ATI Radeon Xpress 200 graphics and Sempron LE-1300 with NVidia GeForce 6150SE graphics. Installation went fine on both systems, although I had to use 1024x768 in order to get a screen that didn't extend beyond the bezel of the monitors (1600x1200 and 1280x1024).

Alas, I cannot start X and get a graphical desktop, no way, no how, on either system. I've tried all the options in VASM. It could be that I need to use the proprietary ATI and NVidia drivers, but you wouldn't think that X would not start at all with open source drivers, even VESA. And yet that is the case.

So I can't do any testing of beta 2 until I can get X to start. I'm writing this from VL7 b1.8.

startxfce4 is no longer available, only startx.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 21, 2011, 04:26:37 pm
Grannygeek,

Can you try the text installer and see if you get different results?
I have startxfce4 in /usr/bin on Beta2, so it should be there.


Thanks,
Uelsks8s
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: nightflier on March 21, 2011, 05:52:47 pm
No problems using hosted ISO install. Nice job cleaning up the boot process, no errors behind splash screen on my machine.   :)
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 21, 2011, 06:23:17 pm
I'll try the text installer tomorrow and report the results.

I just now checked and there is only startx, not startxfce4 in my /usr/bin directory.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 21, 2011, 08:13:13 pm
Beta-2 installed with vinstall.

init 2
unable to start fluxbox

xinit: Unable to run program "/us/bin/startfluxbox": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.

ls /usr/bin/startfluxbox
/usr/bin/startfluxbox

startfluxbox
xmodmap:  unable to open display ''
Error: Couldn't connect to XServer

In /etc/X11/xinit there is no xinitrc.fluxbox

startxfce4 in init 2 flash drives cannot be opened by user  :'(

Opening programs (abiword, gnumeric, shotwell, etc) from terminal one gets:
/home/user/.gtkrc-2.0:15: Unable to find include file: "~/.gtkrc-2.0.mine"

In xwmconfig there is no fluxbox!
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 21, 2011, 08:52:39 pm
I did a text install from the CD and had the same problem.  Can't start X. If I type startxfce4 I get
-bash:startxfce4: command not found.
There is no startxfce4 command in /usr/bin.

startx does not start X. I looked at the Xorg log but most of it I don't understand and couldn't see what makes X unable to start.

My md5sum was fine but I burned the CD with xfburn. Would it be worth switching to my VL6 SOHO Deluxe partition and burning with K3B?
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: vector on March 21, 2011, 09:11:11 pm
Granny something is definitely wrong try k3b see if it goes better......... ;D

cheers,
Vec
 
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 21, 2011, 11:10:15 pm
Beta-2 installed with vinstall.

init 2
unable to start fluxbox

xinit: Unable to run program "/us/bin/startfluxbox": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.

ls /usr/bin/startfluxbox
/usr/bin/startfluxbox

startfluxbox
xmodmap:  unable to open display ''
Error: Couldn't connect to XServer

In /etc/X11/xinit there is no xinitrc.fluxbox

startxfce4 in init 2 flash drives cannot be opened by user  :'(

Opening programs (abiword, gnumeric, shotwell, etc) from terminal one gets:
/home/user/.gtkrc-2.0:15: Unable to find include file: "~/.gtkrc-2.0.mine"

In xwmconfig there is no fluxbox!

Did some tweaking. From console startx will now either start fluxbox or xfce.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: j.a.watson on March 22, 2011, 02:04:15 am
I have started installing Beta2 on the variety of laptop and netbook systems I own.  So far two done, one ok and one not.

Fujitsu Lifebook S6510 - Graphic installation successful.  Very nice installer, congratulations.

Samsung NF310 - This is a netbook, with a 1366x768 display.  When running the graphic installer, I had to choose 1024x768 to get everything to fit on the screen.  When it got to user account setup, the first screen where I should put in the root account password did not fit in the window, the password entry areas were off the screen, there was no scroll bar and I could not get the arrow or page key to work, so I could not enter the root password.  I finally gave up, aborted that installation, and I am now running the text installer on this system.  That looks like it is going to work, of course.

Overall, congratulations the new release is looking good despite this minor glitch.  I know all too well from experience that netbooks with strange/small displays can be a pain.  If you are interested here, I can provide results for various other such systems, some of which have a rather unusual collection of screens, touchpads and network interfaces.

jw
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Joe1962 on March 22, 2011, 06:47:49 am
Sorry to ask "retro" questions, but I can't download and install anywhere near fast enough to keep up and I have read nothing here regarding the following issue: Has the NTFS external drive mounting via udisk been fixed? I am currently on Beta1 and it still mounts read-only, not using ntfs-3g. I have read a lot about udisk, policy-kit, console-kit, etc, etc, and have still not found a published fix. I rolled my own xfce-4.8, udisk, upower and stuff back in the first alphas, which didn't have those yet, and had the same problem.

Another thing, has sleep and hibernation been worked on? I notice there is no tuxonice for 2.6.38 and the one for 2.6.37 is supposedly unfinished. I have found a lot regarding fixing this issue, but nothing has worked for me yet. I can sleep the notebook with "echo "mem" > /sys/power/state", though it sometimes seems to wake itself up without pressing the power switch (this never happened with VL6 SOHO on the same notebook).
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 22, 2011, 05:15:40 pm
I burned a new CD, this time with K3B in VL 6 SOHO Deluxe. This time the installation on the Sempron went fine. I think the last CD medium was defective or the burn was bad.

I'm getting 1280x1024 and didn't have to do any tweaking. Everything I've tried so far has worked. I'm having a bit of a display problem for some text on programs running under Wine. The text sometimes bounces a bit and may disappear for a few seconds. I haven't tried any tweaking yet.

The video driver in xorg.conf is this:
Driver      "modesetting"

The onboard video is NVidia GeForce 6150SE.

I'm happy that Tuxcards is included. That's a "must have" program for me. I'd love to have K3B included, as it's my favorite CD burning program for any operating system. In the past I've added K3B without adding all of KDE.

I also installed on my Athlon 64 X2 with Radeon Xpress 200 graphics. Oh dear. That didn't go so well. X won't start if I use the radeon or ati driver. I have to use the vesa driver to get X running and the maximum resolution I can get is 800x600. On a 1600x1200 screen, it looks awful.

The Athlon 64 X2 computer has had problems with VL7 before. I was unable to get X started on a late alpha of VL 7. VL6 SOHO Deluxe runs perfectly with the xorg radeon driver.

Beta 2 seems much improved over the last beta I installed (1.8).
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: vector on March 22, 2011, 06:28:36 pm
Quote
I also installed on my Athlon 64 X2 with Radeon Xpress 200 graphics. Oh dear. That didn't go so well. X won't start if I use the radeon or ati driver. I have to use the vesa driver to get X running and the maximum resolution I can get is 800x600. On a 1600x1200 screen, it looks awful.
Granny can you try that machine with no xorg.conf file see how it goes.............just name /etc/xorg.conf to xorg.conf.bak or something. Let us know if anything changes.

Thanks,
Vec
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 23, 2011, 03:06:23 pm
I renamed xorg.conf and did startxfce4. Alas, it didn't work. No X. I did save the Xorg.0.log file and will post it later.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 23, 2011, 03:52:39 pm
I renamed xorg.conf and did startxfce4. Alas, it didn't work. No X. I did save the Xorg.0.log file and will post it later.
--GrannyGeek
can you try booting that same computer with "nomodeset" added to the kernel commandline?
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: jon on March 23, 2011, 10:52:44 pm
couple observations from quick tire-kick in vbox only:

version no. in installer README needs updating

rc.firewall
   IPT="/usr/sbin/iptables..."  ->  IPT="/sbin/iptables..."

ffox version -> 3.6.16 / 4.X


all in all, pretty much fun and nice work to all!
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 24, 2011, 12:36:48 am
Beta-2.0

/etc/rc.d/rc.S: line 237: /sys/power/tuxonice/do_resume: No such file or directory

exaile not playing audio CD.
No URI handler implemented for "cdda".

gnome-player open with Audio-Disk-File-Manager will not play.
Error Failed to open cdda://sr0/Track%208.wav.

opening gnome-player from Menu will play, however, does not react properly 
to controls.

Clicking on CD icon Eject Volume: Failed to eject "Audio Disc" Not Authorized

firefox reports on terminal:
(firefox:3952): libgnomevfs-WARNING **: Deprecated function. 
User modifications to the MIME database are no longer supported.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 24, 2011, 05:45:28 pm
can you try booting that same computer with "nomodeset" added to the kernel commandline?

If I did it right, I got the worst results ever. I boot from the installation CD and used this line:
linux root=/dev/sdb11 ro nomodeset

When that proved to be a disaster, I tried
linux root=/dev/sdb11 ro -nomodeset

The results were the same as the previous try.

I was going to copy the error message but I've decided to try a completely new installation just in case there was some glitch the first time. If I continue to have the same problem, I'll report the error messages.

I downloaded the proprietary ATI driver from amd.com but it won't install; it doesn't like the version of X.

I'll continue to pursue this if the fresh installation doesn't help. Meanwhile, it works only with the vesa driver and at 800x600.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 24, 2011, 05:50:35 pm
I downloaded and installed the proprietary NVidia driver on the Sempron with GeForce 6150SE.  So far things are much better. I was already getting 1280x1024 with an xorg open source driver but mouse scrolling was jerky, some edits were slow, and glxgears scores were wretched.

All fixed with the NVidia driver and glxgears scores are the fastest I've ever had.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 25, 2011, 02:35:20 pm
I did more installing and configuring on the Sempron computer. I cannot get j-pilot to hotsync with my Sony Clie. I'm researching the error message with Google but so far, no joy. I didn't have problems getting it to work on VL7b1.8, but on beta 2, I can't do it as root or user. Either way, I always get a "Exiting with status SYNC_ERROR_BIND" message. /dev/ttyUSB0 and /dev/ttyUSB1 exist and are set so any user can read, write, and execute.

I easily played an audio CD with Gnome MPlayer and Xine, but couldn't figure out how to play an audio CD with Exaile or MPlayer.

I wanted to install a Windows program using Wine (Family Origins--worked in earlier releases of VL), but I can't figure out how to access or run a data CD as user and you have to be user to install Wine programs.

As has been reported, automounting CDs, flash drives, etc. as user is not working in XFce. In the case of the Family Origins CD, I couldn't mount it even as root because dmesg didn't report that a CD had been inserted and I didn't know what to call the /dev so I could mount it somewhere. It kept telling me it was a read-only file system. Automounting of drives hasn't been working since the alpha stage. I get a "Permission denied" any time I try to do it as user.

There seem to be major changes in udev. Maybe they have something to do with my inability to hotsync with my Clie and to automount removable drives.

That's all for now.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: vector on March 25, 2011, 06:39:16 pm
Quote
There seem to be major changes in udev. Maybe they have something to do with my inability to hotsync with my Clie and to automount removable drives.
Granny as user either just do startx (not startxfce4) from tui boot method or use the gdm login manager this invokes some special consolekit directives needed so a user has correct permissions to automount and such. The hotsync problem not sure about but will research too.

Cheers,
Vec
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 25, 2011, 11:22:23 pm
Quote
There seem to be major changes in udev. Maybe they have something to do with my inability to hotsync with my Clie and to automount removable drives.
Granny as user either just do startx (not startxfce4) from tui boot method or use the gdm login manager this invokes some special consolekit directives needed so a user has correct permissions to automount and such. The hotsync problem not sure about but will research too.

Cheers,
Vec

I have reported this problem several Alpha versions back that a user cannot
mount flash drives, camera, etc. when in runlevel 2. Startx will not do it.
Now GrannyGeek apparently dislikes just as myself gdm or other display managers.
So a better solution has to be found for those using xfce4 and like to work in runlevel 2.

Since I use fluxbox with xfce4-panel it is not a problem. I have the Mount Devices applet
tweaked that I can easily mount/umount any device with one click. :D
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 26, 2011, 05:23:58 pm
Granny as user either just do startx (not startxfce4) from tui boot method or use the gdm login manager this invokes some special consolekit directives needed so a user has correct permissions to automount and such. The hotsync problem not sure about but will research too.

Thanks. startx worked for me and the removables drives and a CD were automounted for me as user. I don't know why it doesn't work for Pita. I did make XFce my default desktop environment with VASM.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 26, 2011, 05:28:39 pm
I have reported this problem several Alpha versions back that a user cannot
mount flash drives, camera, etc. when in runlevel 2. Startx will not do it.
Now GrannyGeek apparently dislikes just as myself gdm or other display managers.
So a better solution has to be found for those using xfce4 and like to work in runlevel 2.

startx in runlevel 2 does work for me now. Yes, I prefer runlevel 2. The reason is that if I want to be out of X and at a console I can do it simply by exiting XFce. I don't like having to run init 2 or opening another console just to get to an X-free command line.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 26, 2011, 08:16:27 pm
Beta-2.0

Made a new install. Used vasm to put window manager which seems anyhow
set for xfce4 only. Yes, now in runlevel 2 "startx" to start xfce4 user can mount
flash drive. With command startxfce4 user cannot mount flash drives. This
command is shown to be used on opening login.

Opening login screen says "fluxbox: startfluxbox, startfluxbox-desk."
Neither one works.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 27, 2011, 10:11:49 am
I'm seriously trying to get beta 2 working on my Athlon 64 desktop. I did a fresh installation and accepted all defaults (full installation, no Xorg.conf, runlevel 4). Same problem as before, no X.

These are the last two messages before it quits:
gdm-binary[2381]: no suitable security token driver could be found
gdm-binary[2831]: WARNING: Failed to start X server several times in a short time period; disabling display :0

At that point, I have to reboot in order to get a prompt. The keyboard is still responsive and I can get into another console (with Control-Alt-F2, for example).

Do you want to see the end of my xorg log file?  It's a hassle to get it from that computer to this one, but I can do it.

The display works fine in VL6 SOHO Deluxe using the Radeon driver (Radeon Xpress 200 onboard graphics). I can't settle for 800x600 using the vesa driver. It's too awful on a 1600x1200 monitor.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 27, 2011, 12:21:52 pm
I'm writing this with Firefox in the Athlon 64 box. Alas, with the dreaded 800x600 resolution.

I've set up my nfs network and can attach any log or configuration files that might help solve this problem. I looked through several log files (Xorg.0.log, syslog,  messages, debug) but I didn't see anything that could help me figure out what's wrong. But since my understanding of those messages is very poor, maybe somebody else could find some clue.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: jimtib on March 27, 2011, 01:52:29 pm
I finally got vl7 to work on one of my computers with ati graphics.It only works on my newest computer a quad athlon 2
I had pci xpress card installed and I had to use vesa but when I removed the card it recognized my onboard HD ati video.I still cant get it to work on my older comp amd64 with 200xpess onboard video.I installed zenwalk 7 and the video works fine on both my computers.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 27, 2011, 02:13:41 pm
I'm writing this with Firefox in the Athlon 64 box. Alas, with the dreaded 800x600 resolution.

I've set up my nfs network and can attach any log or configuration files that might help solve this problem. I looked through several log files (Xorg.0.log, syslog,  messages, debug) but I didn't see anything that could help me figure out what's wrong. But since my understanding of those messages is very poor, maybe somebody else could find some clue.
--GrannyGeek

Granny,
If you could PM me those files I would like to look at them.
In the meantime, could you try this kernel, and let me know if it changes anything?
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.38.1-4vl70/kernel-2.6.38.1-i686-4vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.38.1-4vl70/kernel-modules-2.6.38.1-i686-4vl70.txz

Thanks,
Uelsk8s
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on March 27, 2011, 02:28:59 pm
I just downloaded beta2 and stupidly accepted the default bootloader (grub).  now when I try to run it, all I get is "grub>."  Do I have to go through a complete reinstall to get lilo back?  Or does someone know what I tell grub?

When loading VL 7 I attempted to load VL7 on / and thought I kept /home for my data. I also think / is on hda2, or so I attempted.

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on March 27, 2011, 06:30:48 pm
so I reinstalled and this time clicked on lilo rather than grub during installation. Got error message "open /boot/vmlinuz  no such file or directory."

Am trying "none" now.

john
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on March 27, 2011, 08:49:03 pm
I'm seriously trying to get beta 2 working on my Athlon 64 desktop. I did a fresh installation and accepted all defaults (full installation, no Xorg.conf, runlevel 4).
Same problem as before, no X.


On the new beta install I could not get into X. So I installed nvidia and X opened with flying colors on my old desktop.
Don't know it this is of any help.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: M0E-lnx on March 28, 2011, 05:28:40 am
so I reinstalled and this time clicked on lilo rather than grub during installation. Got error message "open /boot/vmlinuz  no such file or directory."

Am trying "none" now.

john
Can you not boot the OS with GRUB?
Switching from grub to LILO is easy, just run vliloconf in a terminal as root.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 28, 2011, 06:43:48 am
so I reinstalled and this time clicked on lilo rather than grub during installation. Got error message "open /boot/vmlinuz  no such file or directory."

Am trying "none" now.

john
I am thinking you have a problem with your install.
vmlinuz is installed by the kernel pkg.
can you post the contests of your /boot dir on that partition?
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 28, 2011, 02:16:11 pm
If you could PM me those files I would like to look at them.
In the meantime, could you try this kernel, and let me know if it changes anything?
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.38.1-4vl70/kernel-2.6.38.1-i686-4vl70.txz
http://vectorlinux.osuosl.org/veclinux-7.0/kernels/2.6.38.1-4vl70/kernel-modules-2.6.38.1-i686-4vl70.txz

Thanks. I'll do that as soon as I have time.

Meanwhile, a new wrinkle has developed. Now when I boot and attempt to startx, I got a horrible screen that looks like an old TV whose horizontal hold is not working. There are wide diagonal lines all over, no menu bar, nothing useful at all. Also, I can't get out of X, even with Alt-Control-Backspace. I have to open another console and reboot. I've run vxconf several times and have tried using vesa through VASM and have tried hand editing /X11/xorg.conf to replace the driver with vesa. No luck.

I'll see what happens with the new kernel and report on that. No point in sending the logs at this time.

The console is okay, just the GUI is messed up.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 28, 2011, 03:26:04 pm
Granny, everyone with ATI graphics chipsets and anyone else with graphics woes,
We have a new ISO up with different video drivers that we would like you to test here:
http://vectorlinux.osuosl.org/veclinux-7.0/iso-test/VL7.0-STD-BETA-2.1.iso

let us know how it goes,

Uelsk8s
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: jimtib on March 28, 2011, 05:31:53 pm
I installed Beta 2.1 and ati card finally works! I used first option autoinstall and it worked great.I have tried every alpha and beta release. Using pcixpress card also with onboard radeon 200. I will pull card to test onboard graphics.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: jimtib on March 28, 2011, 05:41:08 pm
I pulled out pcix card and rebooted with onboard atix200 and it worked great.Wireless also works great!Excellent job fixing problem.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 28, 2011, 07:12:10 pm
I pulled out pcix card and rebooted with onboard atix200 and it worked great.

Very interesting! I'll download B2.1 and see if I have similar results with my Radeon Xpress 200. Fingers crossed.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: fogpipe on March 28, 2011, 08:30:00 pm
Granny, everyone with ATI graphics chipsets and anyone else with graphics woes,
We have a new ISO up with different video drivers that we would like you to test here:
http://vectorlinux.osuosl.org/veclinux-7.0/iso-test/VL7.0-STD-BETA-2.1.iso

let us know how it goes,

Uelsk8s

Any goodies on there for intel i915 users? :)
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 28, 2011, 08:37:46 pm
Granny, everyone with ATI graphics chipsets and anyone else with graphics woes,
We have a new ISO up with different video drivers that we would like you to test here:
http://vectorlinux.osuosl.org/veclinux-7.0/iso-test/VL7.0-STD-BETA-2.1.iso

let us know how it goes,

Uelsk8s

Any goodies on there for intel i915 users? :)
Yes, there are some.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on March 28, 2011, 09:25:02 pm
uelsk8s
Quote
I am thinking you have a problem with your install. vmlinuz is installed by the kernel pkg.
can you post the contests of your /boot dir on that partition?

Sorry, I can't get to the point where I can do anything.  I am reloading VL6 on it now.  When time permits, I will try 7 again.

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 29, 2011, 02:46:52 pm
Beta 2.1 did get my ATI Radeon Xpress 200 video working. Thank you, thank you!

All is not well, however. I'm getting odd behavior from my mouse. It's a USB with two buttons and a scroll wheel. If I click on something, the click usually doesn't register and I have to hit Enter to activate whatever I clicked on. Yet it does drag and drop to move things like desktop icons around. If I click on something that has a flyout menu, I have to use the keyboard to go down to whatever I want and then hit Enter. So it works partially but not completely.

I ran the Mouse section of VASM and made the proper selections. So I'm almost there but not quite. Anything else I can try?
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 29, 2011, 03:14:34 pm
Beta 2.1 did get my ATI Radeon Xpress 200 video working. Thank you, thank you!

All is not well, however. I'm getting odd behavior from my mouse. It's a USB with two buttons and a scroll wheel. If I click on something, the click usually doesn't register and I have to hit Enter to activate whatever I clicked on. Yet it does drag and drop to move things like desktop icons around. If I click on something that has a flyout menu, I have to use the keyboard to go down to whatever I want and then hit Enter. So it works partially but not completely.

I ran the Mouse section of VASM and made the proper selections. So I'm almost there but not quite. Anything else I can try?
--GrannyGeek
did you try running without an xorg.conf file?
can you post back the lsusb output?

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on March 29, 2011, 04:02:32 pm
The mouse problem somehow fixed itself. I didn't really do anything, it just started working right.

Maybe it was good gremlins? I usually encounter the bad kind.<g>
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: fogpipe on March 29, 2011, 08:49:10 pm

Any goodies on there for intel i915 users? :)
Yes, there are some.

Ok did an install directly from the iso using the vinstall-iso-ng script (im guessing the "ng" doesnt stand for new and great since i had to boot to my vl6 install to edit the fstab before it would boot :) )

I created a new user, logged in with that uid and did a startx, screen freeze at xfce tips and tricks, this is the last bit of the Xorg :

Quote
[    63.654] (II) intel(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376
  768 769 772 808 +hsync +vsync (68.7 kHz)
[    63.654] (II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 216
0  1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
[    85.258] [mi] EQ overflowing. The server is probably stuck in an infinite lo
op.
[    85.259]
Backtrace:
[    85.259] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e72fb]
[    85.259] 1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80e675b]
[    85.259] 2: /usr/bin/X (xf86PostMotionEventP+0xd2) [0x80c2772]
[    85.259] 3: /usr/bin/X (xf86PostMotionEvent+0x6b) [0x80c28fb]
[    85.259] 4: /usr/lib/xorg/modules/input/mouse_drv.so (0xb7329000+0x61bc) [0x
b732f1bc]
[    85.259] 5: /usr/lib/xorg/modules/input/mouse_drv.so (0xb7329000+0x6a1f) [0x
b732fa1f]
[    85.259] 6: /usr/lib/xorg/modules/input/mouse_drv.so (0xb7329000+0x3d9d) [0x
b732cd9d]
[    85.260] 7: /usr/bin/X (0x8048000+0x6815f) [0x80b015f]
[    85.260] 8: /usr/bin/X (0x8048000+0x11e85c) [0x816685c]
[    85.260] 9: (vdso) (__kernel_sigreturn+0x0) [0xffffe400]
[    85.260] 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb7333000+0x23bb8)
 [0xb7356bb8]
[    85.260] 11: /usr/bin/X (0x8048000+0xd75ef) [0x811f5ef]
[    85.260] 12: /usr/bin/X (ValidateGC+0x25) [0x8081995]
[    85.260] 13: /usr/bin/X (0x8048000+0x24507) [0x806c507]
[    85.260] 14: /usr/bin/X (0x8048000+0x27e87) [0x806fe87]
[    85.260] 15: /usr/bin/X (0x8048000+0x1aec5) [0x8062ec5]
[    85.261] 16: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb743cdb6]
[    85.261] 17: /usr/bin/X (0x8048000+0x1aaa1) [0x8062aa1]

and this is the last bit of syslog:

Quote
Mar 29 15:28:59 bunny21 kernel: [    6.060598] ACPI: resource 0000:00:1f.3 [io 
0x1880-0x189f] conflicts with ACPI region SBUS [io 0x1880-0x188f]
Mar 29 15:28:59 bunny21 kernel: [    8.122438] Console: switching to colour fram
e buffer device 80x30
Mar 29 15:29:13 bunny21 avahi-daemon[1971]: WARNING: No NSS support for mDNS det
ected, consider installing nss-mdns!
Mar 29 15:29:43 bunny21 nmbd[2064]: [2011/03/29 15:29:43.403365,  0] nmbd/nmbd_b
ecome_lmb.c:395(become_local_master_stage2)
Mar 29 15:29:43 bunny21 nmbd[2064]:   *****
Mar 29 15:29:43 bunny21 nmbd[2064]:   
Mar 29 15:29:43 bunny21 nmbd[2064]:   Samba name server BUNNY21 is now a local m
aster browser for workgroup MYGROUP on subnet 192.168.1.104
Mar 29 15:29:43 bunny21 nmbd[2064]:   
Mar 29 15:29:43 bunny21 nmbd[2064]:   *****
Mar 29 15:29:52 bunny21 kernel: [   69.224020] render error detected, EIR: 0x000
00010
Mar 29 15:29:52 bunny21 kernel: [   69.224020] [drm:i915_report_and_clear_eir] *
ERROR* EIR stuck: 0x00000010, masking
Mar 29 15:29:52 bunny21 kernel: [   69.224020] render error detected, EIR: 0x000
00010

Stock install of 2.1 no modifications other than the above mentioned edits to /etc/fstab to make it bootable.

Thank you all for your efforts. Im a huge VL fan and look forward to either getting the dev stuff i need to make this hardware work or getting a new video card, either way, i look forward to a solid stable install of VL2 soon. :)

EDIT: I suppose i should mention for the sake of completeness that im booting from lilo installed on /dev/hda to a 2.1 install located on /dev/sdb5 with this lilo entry and kernel commandline:

Quote
image = /boot/vmlinuz-2.6.38.2
root = /dev/hdb5
label = linux-beta2-1
append = "root=/dev/sdb5 ro video=640x480"
read-only
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on March 29, 2011, 09:27:33 pm
can you try:
Code: [Select]
image = /boot/vmlinuz-2.6.38.2
root = /dev/hdb5
label = linux-beta2-1
append = "root=/dev/sdb5 ro nomodeset acpi=off"
read-only
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: fogpipe on March 29, 2011, 09:54:16 pm
can you try:
Code: [Select]
image = /boot/vmlinuz-2.6.38.2
root = /dev/hdb5
label = linux-beta2-1
append = "root=/dev/sdb5 ro nomodeset acpi=off"
read-only

I made the above modifications you suggested so that my lilo.conf looked like:
Quote
image = /boot/vmlinuz-2.6.38.2
root = /dev/hdb5
label = linux-beta2-1
append = "root=/dev/sdb5 ro nomodeset acpi=off "
read-only

and ran lilo and booted to my 2.1 installation. Logged in as root and ran startx. I typed out two of the last pertinent (i thought) lines of output from the screen and saved them to a file:
Quote
FATAL: Error inserting drm_kms_helper (/lib/modules/2.6.38.2/kernel/drivers/gpu/
drm/drm.ko): No such device
(EE) No devices detected.

Last few lines of Xorg.0.log:
Quote
[   434.095]    Module class: X.Org XInput Driver
[   434.095]    ABI class: X.Org XInput driver, version 11.0
[   434.095] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
        965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
        4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
        Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
        Sandybridge, Sandybridge
[   434.096] (--) using VT number 7

[   434.119] (EE) No devices detected.
[   434.120]
Fatal server error:
[   434.120] no screens found
[   434.120]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[   434.120] Please also check the log file at "/var/log/Xorg.0.log" for additio
nal information.
[   434.120]

Last few lines of syslog:

Quote
Mar 29 23:45:03 bunny21 kernel: [    1.875322] VFS: Mounted root (xfs filesystem
) readonly on device 8:21.
Mar 29 23:45:17 bunny21 avahi-daemon[1874]: WARNING: No NSS support for mDNS det
ected, consider installing nss-mdns!
Mar 29 23:45:46 bunny21 nmbd[1967]: [2011/03/29 23:45:46.939959,  0] nmbd/nmbd_b
ecome_lmb.c:395(become_local_master_stage2)
Mar 29 23:45:46 bunny21 nmbd[1967]:   *****
Mar 29 23:45:46 bunny21 nmbd[1967]:   
Mar 29 23:45:46 bunny21 nmbd[1967]:   Samba name server BUNNY21 is now a local m
aster browser for workgroup MYGROUP on subnet 192.168.1.104
Mar 29 23:45:46 bunny21 nmbd[1967]:   
Mar 29 23:45:46 bunny21 nmbd[1967]:   *****
Mar 29 23:55:20 bunny21 nmbd[1967]: [2011/03/29 23:55:20.115410,  0] nmbd/nmbd.c
:71(terminate)
Mar 29 23:55:20 bunny21 nmbd[1967]:   Got SIGTERM: going down...

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on March 30, 2011, 12:16:18 am
While trying to build banshee-1.8.1 from source for VL7, encounter below error

Quote
Making all in libossifer
  CC    ossifer-web-view.o
  CC    ossifer-session.o
  LINK  libossifer.la
/bin/grep: /usr/lib/libgconf-2.la: No such file or directory
/bin/sed: can't read /usr/lib/libgconf-2.la: No such file or directory
libtool: link: `/usr/lib/libgconf-2.la' is not a valid libtool archive
make[5]: *** [libossifer.la] Error 1

I believe it is missing from GConf. Current VL7 Beta 2 come with version 2.32.0. I try compile 2.32.1 and the file is there.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on March 31, 2011, 01:18:05 am
While trying to build banshee-1.8.1 from source for VL7, encounter below error

Quote
Making all in libossifer
  CC    ossifer-web-view.o
  CC    ossifer-session.o
  LINK  libossifer.la
/bin/grep: /usr/lib/libgconf-2.la: No such file or directory
/bin/sed: can't read /usr/lib/libgconf-2.la: No such file or directory
libtool: link: `/usr/lib/libgconf-2.la' is not a valid libtool archive
make[5]: *** [libossifer.la] Error 1

I believe it is missing from GConf. Current VL7 Beta 2 come with version 2.32.0. I try compile 2.32.1 and the file is there.

I have package GConf-dev to install the missing files. Done.  ;D

http://forum.vectorlinux.com/index.php?topic=13525.0
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Lain on March 31, 2011, 03:47:58 pm
So far no problems installing, Yet it is missing the ability to Set Static ip's on installation.

One wierd problem is my Cursor? its squashed and stretched out and looks like 4 pointers, really hard to see and cant change it ive been trying.
otherwise i dont see any other problems as of yet, like the new XFCE style, and that it now supports 1680x1050, Also i think i may have chosen the wrong
at the begining to Probe X, it checked my hardware but didnt install Nvidia drivers, no problem can add those in. Will hunt down more oddities as i come across
them.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Lain on March 31, 2011, 04:33:23 pm
Fixed mouse problem thru Vasm by running Xwindows setup and using Auto2, or possibly disabling gpm fropm my init boots.

Known problem for me, using Vasm to setup Inets they all come up as blank configuration files when done inet2/3/4/5 ect, and attempting
to change/Set new parms to a current makes no changes at all. has to be done manually via /etc/rc.d/ .
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 01, 2011, 09:34:29 pm
One problem with testing new releases is if one wants to test programs not 
included in the iso one can and have them installed later with gslapt.
Comes a new release theoretically one has to install again those programs which
becomes rather time consuming.

My way around this is to make an installation on two different partitions.
Partiton 1 is kept permanently with original install and added programs. 
On partition 2 new releases are installed and then copied over to
partition one with the command "cp -au /mnt/part2/* /mnt/part1".   

This has worked fine for me. May be there is another way or somebody will   
tell that it is not acording to protocol. Who knows.

I have tried "upgradepkg -i /iso/packages/*/*.txz" from a mounted iso. That one
only partially worked.

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Andy Price on April 03, 2011, 08:59:43 am
Installed B2.1 using text installer. My previous attempts to use text installer failed and now I realise why - I didn't read the instructions! To run the text installer in VL6 you typed "linux" at the boot prompt, but that's changed to "install" in VL7 and I hadn't spotted it until recently...

A couple of things missing from the text installer compared to previous versions: the ability to check the CD for errors and the ability to choose packages. Personally I use both of these options and would be happy to see them included.

Whilst most everything worked fine, a couple of things seemd odd to me. Firstly, when I open a terminal the background is initially white and then turns black, so the terminal appears to flash every time I open it. It's especially noticable on an old P3 I use for testing. It happens on both computers I use, though the "flash" is quite fast on the P4.

The second thing is the Wicd applet. I have never used it before as I always set up the network during the install or in VASM, but I opened Wicd just out of interest. I have no wireless network. When I looked at the settings for my ethernet it showed only the host name and domain, vector.linux.net. I have static IP settings but these don't show up. Should they?

I installed a dozeon or so packages and had problems with a few. Since I can't see entries for them in the new packages section I'll list them here.

VLC - won't install, missing mesa>=7.10_84b6857e
Firestarter - installs but won't run "A proper configuration for Firestarter was not found..."
Audacity - installs but won't run "Error while opening shared library libwx_gtk2u_richtext... "

Cheers
Andy
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 03, 2011, 01:38:30 pm
Quote
I installed a dozeon or so packages and had problems with a few. Since I can't see entries for them in the new packages section I'll list them here.

VLC - won't install, missing mesa>=7.10_84b6857e
Firestarter - installs but won't run "A proper configuration for Firestarter was not found..."
Audacity - installs but won't run "Error while opening shared library libwx_gtk2u_richtext... "

Cheers
Andy

VLC should be fixed now.  In gslapt you may need to go to Edit -> Preferences and 'Delete Cached Package files" then update, but it should work after that.

Firestarter, I have pulled that, until it can be rebuilt.

Audacity- installed and ran just fine for me, so I will need some confirmation from other testers, please. 

Thanks Andy, I'll try to fix anything that people make me aware of some please keep the repository testing coming.
Stretch'd
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Andy Price on April 04, 2011, 03:24:07 am
Thanks Stretchedthin, I did as you suggested and tried VLC again; it installs ok now.

I checked for the libwx_gtk2u_richtext library and it's not present in the file system, though libwx_gtk2 is. Could there be a naming problem or are they different libraries?

One other package I tried last night, the latest wine in the repos, 1.3.15. It installs ok and I installed a couple of Windows apps in it too, but when I first ran wine -config it offered to download the Gecko rendering engine which I accepted, but it failed to download correctly. I'm pretty sure this used to work in VL6.

Cheers
Andy
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Joe1962 on April 04, 2011, 01:05:44 pm
Has the NTFS external drive mounting via udisk been fixed?
Ok, so I finally fixed it by adding a 99-ntfs3g.rules file with this udev rule:
Code: [Select]
ENV{ID_FS_TYPE}=="ntfs", ENV{ID_FS_TYPE}="ntfs-3g"
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: kc1di on April 04, 2011, 03:25:23 pm
Installed RC2 today and it's working pretty nicely.  Looks good also. only problem I've had so far is that Gslapt will not download some files.  other download and install fine so I'm wondering a bit about that.

Good work gang it's looking good.
 :)
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 04, 2011, 03:43:13 pm
VLC - won't install, missing mesa>=7.10_84b6857e
Audacity - installs but won't run "Error while opening shared library libwx_gtk2u_richtext... "

I have the same problem with Audacity (VL7 beta2). VLC is running but I haven't used it enough to know if it's running well.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 04, 2011, 07:46:37 pm
Audacious working

VLC working

Gparted working

Frozen-Bubbles working

Firefox-4.0 working

Claws-mail spellckecker was disabled since missing files.
Copied 'de' and 'en-us' over from VL6. Spellchecker now working.

On xfce4-panel applets screenshot cannot be added neither weather-update.
The latter was manually intalled and is version 0.7.2 and working in VL6.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 04, 2011, 07:51:34 pm
VLC - won't install, missing mesa>=7.10_84b6857e
Audacity - installs but won't run "Error while opening shared library libwx_gtk2u_richtext... "

I have the same problem with Audacity (VL7 beta2). VLC is running but I haven't used it enough to know if it's running well.
--GrannyGeek

Problem was wxGTK, if I could get you and Andy to retest after going to GSlapt and clearing the cache in "Edit"->"preferences
Thanks;
Stretched.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on April 04, 2011, 11:47:24 pm
Running VL7B2.1 and notice there is no /etc/bashrc and it also encounter the same problem as mention in B1.

http://forum.vectorlinux.com/index.php?topic=12938.msg81018#msg81018
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Andy Price on April 05, 2011, 05:16:58 am
Quote

Problem was wxGTK, if I could get you and Andy to retest after going to GSlapt and clearing the cache in "Edit"->"preferences
Thanks;
Stretched.


Not sure exactly how you wanted us to test. I cleared the cache then reinstalled Audacity, but it still gave the libwx error. Then I tried to reinstall wxGTK but got an error "Failed to download wxGTK:HTTP response code said error" so I'm not sure what to try next.
Andy
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 05, 2011, 07:21:08 am
Quote
Failed to download wxGTK:HTTP response code said error" so I'm not sure what to try next.
Andy
Sorry I didn't give full instruction. :P
This error would indicate that a cleared cache but may not have updated gslapt afterwards.

I've replaced wxGTK with a rebuilt one in the repositories.  So to properly test, please...
Uninstall, audacity and wxGTK
After clearing the cache, update gslapt.
Reinstall audacity.

I've done the same here with success.  Just want to confirm.
Thanks.

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on April 05, 2011, 07:24:32 am
audacity works here after update

i do get this error on the command line though
Code: [Select]
Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3653
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 05, 2011, 03:24:22 pm
I uninstalled audacity and wxGTK and cleared the cache, then reinstalled. Audacity is now working. I do get Uel's command line error message but I haven't noticed any problem with running the program.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 05, 2011, 03:58:51 pm
I uninstalled audacity and wxGTK and cleared the cache, then reinstalled. Audacity is now working. I do get Uel's command line error message but I haven't noticed any problem with running the program.
--GrannyGeek
Nice. Thanks all.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 06, 2011, 12:58:26 am
audacious opened from command line. Only warning:

** WARNING **
Audacious has detected that your ALSA device has a broken timer.  A workaround
is being used to prevent CPU overload.  Please report this problem to your
Linux distributor or to the ALSA developers.

That is when playing an URL. After some playing:

ALSA lib pcm.c:7316:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7316:(snd_pcm_recover) underrun occurred
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: kc1di on April 06, 2011, 01:59:10 am
RC 2.1 been running quite well here so far. Few things I miss though ,  would really like to have the file compression and uncompress option in the right click menu again.  Also would like a better tool for compressing and uncompressing files. Never really cared for XArchiver. But that's just personal preference. 

Did have a problem with the Xsetup the Auto setup simply did not do for my setup here had to do it manually.  the auto setup would cause the screen to blank about ever 1minute or so. Could be because of my legacy Nvidia card.  I also have notice this on several other Distros newer releases.  wondering if it may have something to do with Nivida's newer drivers.  I was able to fix it but a newbie coming to it the first time would not be able to figure that one out. 

keep up the good work. Looking forward to the finished product.  Oh I also really like the new look.

cheers
dave

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 07, 2011, 07:39:05 pm
VL7-Beta-2.1

Abiword cannot render a .doc file with tables unlike in VL6.

Example:
No.ItemDescriptionPriceVintageType1)AW 19Jinmai  Ancient$33.90
/ 357g2008Raw2)AW 20Manjin  Ancient$32.80 / 357g2008Raw3)AW
91Jinmai  Brick$5.80 / 250g2008Raw4)AW 92Manjin  Brick$5.80 /
250g2008Raw5)AW 15Lanhua$25.80 / 357g2008RawLanhua$25.80 /
357g2007Raw6)AW 16Meihua$23.50 / 357g2007Raw7)AW 17Mijin
$12.50 / 357g2007Raw8)AW 18Mijin Tuocha$3.50 / 100g2007Raw9)
AW11Red Lable$16.50 / 357g2006 Raw10)AW 12Blue Lable$28.40 /

Those are supposed to be 6 columns and numerous lines.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 08, 2011, 11:12:55 pm
On booting, "Setting up modules" takes every time 25 seconds. Is this normal for VL7?

Login with init 4 does not show asking for the password after asking for the login name
just showing the white window to enter password.

Skype-2.2.0.25 working.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 12, 2011, 03:47:29 pm
VL7-Beta-2.1

Abiword cannot render a .doc file with tables unlike in VL6.

Example:
No.ItemDescriptionPriceVintageType1)AW 19Jinmai  Ancient$33.90
/ 357g2008Raw2)AW 20Manjin  Ancient$32.80 / 357g2008Raw3)AW
91Jinmai  Brick$5.80 / 250g2008Raw4)AW 92Manjin  Brick$5.80 /
250g2008Raw5)AW 15Lanhua$25.80 / 357g2008RawLanhua$25.80 /
357g2007Raw6)AW 16Meihua$23.50 / 357g2007Raw7)AW 17Mijin
$12.50 / 357g2007Raw8)AW 18Mijin Tuocha$3.50 / 100g2007Raw9)
AW11Red Lable$16.50 / 357g2006 Raw10)AW 12Blue Lable$28.40 /

Those are supposed to be 6 columns and numerous lines.

Libreoffice does open a .doc file with tables correctly. :D
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 13, 2011, 12:15:00 pm
VL7-Beta-2.1

Every time I restart the PC I get two instances of CairoDock running. When CairoDock is disabled in startup applications after restart it's ok, only one CairoDock appears.

The Sources in the gslapt package manager for http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/ are not correct.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 13, 2011, 01:13:31 pm
Quote
The Sources in the gslapt package manager for http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/ are not correct.

How so?
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 13, 2011, 01:24:16 pm
I installed beta 2.1 on the system where I had previously installed beta2, which had problems getting 1280x1024 screen resolution until I installed the proprietary NVidia driver. I had more oddities on that system so I decided to install beta 2.1 to see if they were fixed.

I'm happy to say that most of the problems vanished with beta 2.1. I switched monitors with my other desktop and now have a 20" 1600x1200 lcd on this system. I used the AUTO (no xorg.conf) option at initial setup and it installed the nouveau driver, which correctly displayed 1600x1200 automatically. All other hardware was correctly identified. Nevertheless, I decided to install the proprietary NVidia driver because I get glxgears scores that are six times higher than those with the xorg driver--not that I do anything where that would make a difference.<g>

I haven't installed printers yet--that's my next task. I run a few Windows programs under Wine. I couldn't install wine through Gslapt, as it isn't where Gslapt says it is. I did find it at ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/testing/ap/ , downloaded the package, and installed it with installpkg. It seems to be working fine--is there some reason the wine package is not where Gslapt thinks it is?

The scanner part of my Canon MP160 doesn't work right. It previews the scan but can't complete the actual scan. I researched the problem on the Web and it's widespread but nobody had a working solution. I'm about to install the proprietary Canon software for the scanner and hope I'll have better luck with that.

For me, beta 2.1 was a big improvement over beta 2. There are still quite a few error messages when starting various programs from a command line, but they don't seem to impact performance.

Opera has a new version (11.10), which I installed and am using without problems. The Flash version in beta 2.1 is not current. I installed the latest flash and it has worked so far in Opera, Firefox, and SeaMonkey. The SeaMonkey version has had two updates. I hope we can get the latest version in the next VL7 release.

I'm very happy with VL7 and am really looking forward to the final release, which I hope isn't too far away.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 13, 2011, 01:39:28 pm
Quote
The Sources in the gslapt package manager for http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/ are not correct.

How so?
The link above is the correct one. I changed the wrong one with it and do not remember what was the default one.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 13, 2011, 05:13:28 pm
Quote
The Sources in the gslapt package manager for http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/ are not correct.

How so?
The link above is the correct one. I changed the wrong one with it and do not remember what was the default one.
defaults are as follows
http://vectorlinux.osuosl.org/veclinux-7.0/packages/
http://vectorlinux.osuosl.org/veclinux-7.0/patches/
http://vectorlinux.osuosl.org/veclinux-7.0/extra/
http://vectorlinux.osuosl.org/veclinux-7.0/testing/

enabling testing will give you access to the most packages as all new apps are going there first, but may or may not be buggy.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 13, 2011, 09:11:16 pm
By default, I mean that the default source for mirror.garr.it after the installation of VL 7.0 in the gslapt package manager is not correct.
For example this source ftp://rmrm.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/packages/ is not correct.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on April 14, 2011, 07:56:50 pm
i just try install VL7B2.1 with the minimum installation option and I cannot login to my user account saying login incorrect. I can log in as root but when i want to use VASM to change my root and user password, it say change password FAILED. Do anyone have this problem?

EDIT: I can change the password using passwd but not VASM thou. Thanks to uelsk8s's advise...

EDIT: Install expect solve the VASM change password problem but now I cannot log on to super VASM in my user account, VASM just hang. Uninstall expect will give me a wrong root password error.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Andy Price on April 14, 2011, 09:53:04 pm
i just try install VL7B2.1 with the minimum installation option and I cannot login to my user account saying login incorrect. I can log in as root but when i want to use VASM to change my root and user password, it say change password FAILED. Do anyone have this problem?

Yes, I had the same problem. Now I know how to get round it  :)
Andy
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on April 14, 2011, 10:32:27 pm
i just try install VL7B2.1 with the minimum installation option and I cannot login to my user account saying login incorrect. I can log in as root but when i want to use VASM to change my root and user password, it say change password FAILED. Do anyone have this problem?

Yes, I had the same problem. Now I know how to get round it  :)
Andy

Did u try run super VASM as normal user?
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 15, 2011, 01:29:47 pm
I have tested all the sources in slapt-getrc for VL 6.0 to find out whether they are still present or no longer available and these are the results:

outdated sources in slapt-getrc.new
Code: [Select]
ftp://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/
http://ftp.chg.ru/pub/Linux/sunsite/distributions/vectorlinux/veclinux-6.0/
ftp://ftp.chg.ru/pub/Linux/sunsite/distributions/vectorlinux/veclinux-6.0/
http://gd.tuwien.ac.at/opsys/Linux/vectorlinux/veclinux-6.0/
ftp://gd.tuwien.ac.at/opsys/Linux/vectorlinux/veclinux-6.0/
http://cesium.di.uminho.pt/pub/vectorlinux/veclinux-6.0/
ftp://cesium.di.uminho.pt/pub/vectorlinux/veclinux-6.0/
http://www.gtlib.gatech.edu/pub/linux/distributions/vectorlinux/veclinux-6.0/
ftp://www.gtlib.gatech.edu/pub/linux/distributions/vectorlinux/veclinux-6.0/
http://slackware.cs.utah.edu/pub/vectorlinux/veclinux-6.0/
ftp://slackware.cs.utah.edu/pub/vectorlinux/veclinux-6.0/
http://ftp.at.gnucash.org/opsys/linux/vectorlinux/veclinux-6.0/
ftp://ftp.at.gnucash.org/opsys/linux/vectorlinux/veclinux-6.0/
http://rmrm.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/
ftp://rmrm.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/
http://www.uk.kernel.org/sites/vectorlinux.com/veclinux-6.0/
ftp://www.uk.kernel.org/sites/vectorlinux.com/veclinux-6.0/
http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-6.0/
ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-6.0/
http://ftp.scarlet.be/pub/slackware/slackware-12.1/
http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-12.1/
http://mirror.mhvlug.org/slackware/slackware-12.1/
http://mirror.etf.bg.ac.yu/slackware/slackware-12.1/
http://slackware.perespim.ru/pub/slackware-12.1/
ftp://dl.xs4all.nl/pub/mirror/slackware/slackware-12.1/
ftp://ftp.cs.stevens-tech.edu/pub/Linux/distributions/slackware/slackware-12.1/
ftp://ftp.edisontel.it/pub/Slackware_Mirror/slackware-12.1/
ftp://ftp.eutelia.it/pub/Slackware_Mirror/slackware-12.1/
ftp://ftp.iasi.roedu.net/mirrors/ftp.slackware.com/slackware-12.1/
ftp://ftp.rdsbv.ro/mirrors/slackware/slackware-12.1/
ftp://ftp.scarlet.be/pub/slackware/slackware-12.1/
ftp://ftp.sh.cvut.cz/MIRRORS/slackware/slackware-12.1/
ftp://ftp.slackware.cz/slackware/slackware-12.1/ ask for password
ftp://ftp.slackware.hu/slackware/slackware-12.1/
ftp://ftp.uoi.gr/mirror/OS/slackware/slackware-12.1/
ftp://ftp.wh8.tu-dresden.de/pub/linux/distributions/slackware/slackware-12.1/
ftp://mirror.etf.bg.ac.yu/slackware/slackware-12.1/
ftp://mirrors.evrocom.net/pub/slackware/slackware-12.1/
ftp://sharon.esrac.ele.tue.nl/pub/slackware/slackware-12.1/
ftp://slackware.perespim.ru/pub/slackware-12.1/
http://www.software-mirror.com/linuxpackages/Slackware-12.1/
http://ftp.scarlet.be/pub/linuxpackages/Slackware-12.1/
ftp://ftp.scarlet.be/pub/linuxpackages/Slackware-12.1/
http://opensys.linuxpackages.net/Slackware-12.1/
ftp://opensys.linuxpackages.net/pub/Slackware-12.1/
http://linuxpackages.reco-systems.de//Slackware-12.1/
http://ftp.de-mirror.org/linuxpackages//Slackware-12.1/
ftp://ftp.de-mirror.org/linuxpackages//Slackware-12.1/
http://lp.slackwaresupport.com/Slackware-12.1/
http://ftp.naist.jp/pub/Linux/linuxpackages/Slackware-12.1/
ftp://ftp.nara.wide.ad.jp/pub/Linux/linuxpackages/Slackware-12.1/
http://linuxpackages.cs.utah.edu//Slackware-12.1/
ftp://mirror.cs.utah.edu/pub/linuxpackages//Slackware-12.1/
http://linuxpackages.inode.at/Slackware-12.1/
ftp://linuxpackages.inode.at/Slackware-12.1/
http://mirrors.unixsol.org/linuxpackages//Slackware-12.1/
ftp://mirrors.unixsol.org/linuxpackages//Slackware-12.1/
http://www2.linuxpackages.net/packages/Slackware-12.1/
ftp://ftp.slackware.hu/linuxpackages/Slackware-12.1/
http://linuxpackages.telecoms.bg/Slackware-12.1/
ftp://linuxpackages.telecoms.bg/Slackware-12.1/
http://slacky.uglyplace.org/repository/slackware-12.1/
http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-12.1/
ftp://darkstar.ist.utl.pt/pub/slackware/addon/slacky/slackware-12.1/

updated slapt-getrc.new
Code: [Select]
WORKINGDIR=/home/ftp/pub/veclinux/packages
EXCLUDE=kernel,kernel-ide,kernel-source,kernel-headers,kernel-modules
#DISABLED=file:///mnt/cdrom/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-6.0/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-6.0/extra/
SOURCE=http://vectorlinux.osuosl.org/veclinux-6.0/patches/:OFFICIAL
#SOURCE=http://vectorlinux.osuosl.org/veclinux-6.0/testing/
SOURCE=http://vectorlinux.osuosl.org/veclinux-6.0/gsb-2.22/
#DISABLED=http://vectorlinux.osuosl.org/veclinux-6.0/unstable/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/packages/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/patches/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/extra/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/testing/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/gsb-2.22/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-6.0/unstable/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/packages/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/patches/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/extra/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/testing/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/gsb-2.22/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-6.0/unstable/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/packages/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/patches/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/extra/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/testing/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/packages/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/patches/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/extra/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-6.0/testing/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/packages/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/patches/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/extra/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/testing/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/packages/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/patches/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/extra/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-6.0/testing/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/packages/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/patches/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/extra/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-6.0/testing/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-12.1/
#DISABLED=http://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=http://darkstar.ist.utl.pt/slackware/slackware-12.1/
#DISABLED=http://ftp.belnet.be/packages/slackware/slackware-12.1/
#DISABLED=http://ftp.gwdg.de/pub/linux/slackware/slackware-12.1/
#DISABLED=http://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-12.1/
#DISABLED=http://ftp.linux.cz/pub/linux/slackware/slackware-12.1/
#DISABLED=http://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=http://ftp.ntua.gr/pub/linux/slackware/slackware-12.1/
#DISABLED=http://ftp.riken.jp/Linux/slackware/slackware-12.1/
#DISABLED=http://ftp.slackware.cz/slackware/slackware-12.1/
#DISABLED=http://gd.tuwien.ac.at/opsys/linux/slackware/slackware-12.1/
#DISABLED=http://mirror.switch.ch/ftp/mirror/slackware/slackware-12.1/
#DISABLED=http://mirrors.dotsrc.org/slackware/slackware-12.1/
#DISABLED=http://mirrors.easynews.com/linux/slackware/slackware-12.1/
#DISABLED=http://mirrors.unixsol.org/slackware/slackware-12.1/
#DISABLED=http://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=http://serghei.net/linux/slackware/slackware-12.1/
#DISABLED=http://slackware.mirrors.pair.com/slackware-12.1/
#DISABLED=http://slackware.mirrors.tds.net/pub/slackware/slackware-12.1/
#DISABLED=http://slackware.oregonstate.edu/slackware-12.1/
#DISABLED=http://www.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-12.1/
#DISABLED=http://www.slackware.at/data/slackware-12.1/
#DISABLED=ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=ftp://ftp.chg.ru/pub/Linux/Slackware/slackware-12.1/
#DISABLED=ftp://darkstar.ist.utl.pt/pub/slackware/slackware-12.1/
#DISABLED=ftp://elektroni.phys.tut.fi/slackware-12.1/
#DISABLED=ftp://ftp.belnet.be/packages/slackware/slackware-12.1/
#DISABLED=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.cerias.purdue.edu/pub/os/slackware/slackware-12.1/
#DISABLED=ftp://ftp.fu-berlin.de/unix/linux/mirrors/slackware/slackware-12.1/
#DISABLED=ftp://ftp.funet.fi/pub/mirrors/ftp.slackware.com/pub/slackware-12.1/
#DISABLED=ftp://ftp.gwdg.de/pub/linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.heanet.ie/mirrors/ftp.slackware.com/pub/slackware/slackware-12.1/
#DISABLED=ftp://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-12.1/
#DISABLED=ftp://ftp.linux.cz/pub/linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=ftp://ftp.man.szczecin.pl/pub/Linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-12.1/
#DISABLED=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-12.1/
#DISABLED=ftp://ftp.ntua.gr/pub/linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.red.telefonica-wholesale.net/slackware/slackware-12.1/
#DISABLED=ftp://ftp.riken.jp/Linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.slackware-brasil.com.br/slackware-12.1/
#DISABLED=ftp://ftp.slackware.lt/pub/Linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.slackware.no/pub/linux/slackware/slackware-12.1/
#DISABLED=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-12.1/
#DISABLED=ftp://mirror.switch.ch/mirror/slackware/slackware-12.1/
#DISABLED=ftp://mirrors.blueyonder.co.uk/sites/ftp.slackware.com/slackware-12.1/
#DISABLED=ftp://mirrors.dotsrc.org/slackware/slackware-12.1/
#DISABLED=ftp://mirrors.unixsol.org/slackware/slackware-12.1/
#DISABLED=ftp://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-12.1/
#DISABLED=ftp://slackware.mirrors.pair.com/slackware-12.1/
#DISABLED=ftp://slackware.mirrors.tds.net/pub/slackware/slackware-12.1/
#DISABLED=ftp://slackware.oregonstate.edu/pub/slackware/slackware-12.1/
#DISABLED=ftp://sunsite.cnlab-switch.ch/mirror/slackware/slackware-12.1/
#DISABLED=ftp://sunsite.icm.edu.pl/pub/Linux/slackware/slackware-12.1/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-12.1/
#DISABLED=http://www.slacky.eu/repository/slackware-12.1/
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on April 15, 2011, 02:24:31 pm
Monfen,
I appreciate your effort on this.
how did you test each source?
I am surprised to see so many mirrors not working.
I did a quick test of ibiblio and found this: http://distro.ibiblio.org/vectorlinux/veclinux-7.0/

Uelsk8s
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 15, 2011, 03:13:47 pm
I tried to get my Canon Pixma MP160 scanner working after installing the Canon scangear driver (two files converted from rpm). No luck. The scanner was working in VL6 Standard Deluxe a couple of years ago and I don't think I ever got around to installing it in newer VLs when it was attached to my now-older desktop (Athlon 64 X2). Now I'm trying to get it working on my VL7 b2.1 on the Sempron computer.

Scangear starts and I've even gotten a preview (once in a while :-(  ) But when it tries to scan, it reaches a certain percentage on the progress bar and then just stops. After 20 minutes I give up and use ps -e to end the process. I start it from a terminal prompt but there are no informative messages at all to give me a hint of what's wrong. The highest percentage of completion it has ever reached is 28%. When it actually does start a scan, it usually stops at 17 or 18%, but it has also stopped at 3%. There is plenty of free space on the hard drive.

I googled but couldn't find anything. Most of the hits were several years old (2007 or 2008) and none of the ones I checked described this problem. The printer works fine (though with very limited options).

VueScan supports this scanner and I may decide to buy it. I'd like to avoid that, if possible. I don't use this scanner for anything but quick and dirty.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 15, 2011, 10:29:07 pm
Monfen,
I appreciate your effort on this.
how did you test each source?
I am surprised to see so many mirrors not working.
I did a quick test of ibiblio and found this: http://distro.ibiblio.org/vectorlinux/veclinux-7.0/

Uelsk8s
I tested each source via Firefox. I have added to the post that these are the sources for VL 6.0, updated sources for VL 7.0 will be available soon.
It is good someone else to check the availability of the sources, too, for sure.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 17, 2011, 01:51:29 pm
Update on the Pixma MP160 scanner--

I did a lot of googling on the problems I was having and concluded that it's a lost cause. xsane won't write the file (working as root doesn't help), scangearmp can't complete a scan or even a preview. Google revealed that these errors are widespread and there is no obvious solution.

The good news is that VueScan didn't have a bit of trouble producing excellent scans. There's just one file to run and no actual installation to do. I downloaded the trial version and was very impressed with the ease of use and quality of scans. So I decided it was worth $40 US to have something that worked. The alternative was to buy a new all-in-one with better Linux support. VueScan was cheaper than that.

Now I have to determine if I can tolerate the CUPS printer driver for the Canon Pixma MP160. It produces okay prints but has very few options (color only, 600x600 dpi only--the printer can actually do quite a bit more than that). TurboPrint has what's supposed to be a better printer driver but at about $40 US I don't know if it's worth it to me.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Vink8 on April 18, 2011, 04:28:44 am
Giving a look inside the mirrored files
http://vectorlinux.osuosl.org/veclinux-7.0/packages/PACKAGES.TXT  05-Apr-2011  511K
http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/packages/PACKAGES.TXT  05-Apr-2011  511K

@Vector (or to whom it may concern)
pay attention to

requiredbuilder-0.16.2-i586-2vl59.txz

directfb-1.4.3-i586-2vl60.txz
gslapt-0.5.3d-i586-1vl60.txz
mingetty-1.08-i586-1vl60.txz
os-prober-1.29-i586-3vl60.txz
pkgtools-tukaani-1.2.5-i586-1vl60.txz
slapt-get-0.10.2g-i586-1vl60.txz
vcpufreq-2.4.2-i586-1vl60.txz
vlart-6.0-noarch-1vl60.txz
vlgui-6.0-noarch-1vl60.txz
vlinit-6.0-noarch-4vl60.txz
xdelta-1.1.4-i586-1vl60.txz

seem intended to Vec5.9 - Vec6

to dep. request of
gambas2-runtime-2.22.0-i586-2vl70.txz
gksu-2.0.2-i586-1vl70.txz
libproxy-0.4.6-i586-1vl70.txz
MPlayer-20101119-i586-1vl70.txz

also @ Kidd and @ rbistolfi
inside
sbbuilder-0.4.12.4-noarch-1vl70.txz
? PACKAGE REQUIRED:  perl >= 5.8.0-i586-1vl59 | perl >= 5.8.0-i586-1vl60

Wishing a clear time to all the men and women of good wish!
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: monfen on April 19, 2011, 11:20:15 am
I have tested the sources in /etc/slapt-get/slapt-getrc for VL 7.0 to find out whether they are still present or no longer available and these are the results:

outdated sources in slapt-getrc
Code: [Select]
ftp://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/
http://ftp.chg.ru/pub/Linux/sunsite/distributions/vectorlinux/veclinux-7.0/
ftp://ftp.chg.ru/pub/Linux/sunsite/distributions/vectorlinux/veclinux-7.0/
http://gd.tuwien.ac.at/opsys/Linux/vectorlinux/veclinux-7.0/
ftp://gd.tuwien.ac.at/opsys/Linux/vectorlinux/veclinux-7.0/
http://cesium.di.uminho.pt/pub/vectorlinux/veclinux-7.0/
ftp://cesium.di.uminho.pt/pub/vectorlinux/veclinux-7.0/
http://www.gtlib.gatech.edu/pub/linux/distributions/vectorlinux/veclinux-7.0/
ftp://www.gtlib.gatech.edu/pub/linux/distributions/vectorlinux/veclinux-7.0/
http://slackware.cs.utah.edu/pub/vectorlinux/veclinux-7.0/
ftp://slackware.cs.utah.edu/pub/vectorlinux/veclinux-7.0/
http://ftp.at.gnucash.org/opsys/linux/vectorlinux/veclinux-7.0/
ftp://ftp.at.gnucash.org/opsys/linux/vectorlinux/veclinux-7.0/
http://rmrm.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/
ftp://rmrm.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/
http://www.uk.kernel.org/sites/vectorlinux.com/veclinux-7.0/
ftp://www.uk.kernel.org/sites/vectorlinux.com/veclinux-7.0/
http://ftp.scarlet.be/pub/slackware/slackware-13.1/
http://gulus.usherbrooke.ca/pub/distro/slackware/slackware-13.1/
http://mirror.mhvlug.org/slackware/slackware-13.1/
http://mirror.etf.bg.ac.yu/slackware/slackware-13.1/
http://slackware.perespim.ru/pub/slackware-13.1/
ftp://dl.xs4all.nl/pub/mirror/slackware/slackware-13.1/
ftp://ftp.cs.stevens-tech.edu/pub/Linux/distributions/slackware/slackware-13.1/
ftp://ftp.edisontel.it/pub/Slackware_Mirror/slackware-13.1/
ftp://ftp.eutelia.it/pub/Slackware_Mirror/slackware-13.1/
ftp://ftp.iasi.roedu.net/mirrors/ftp.slackware.com/slackware-13.1/
ftp://ftp.rdsbv.ro/mirrors/slackware/slackware-13.1/
ftp://ftp.scarlet.be/pub/slackware/slackware-13.1/
ftp://ftp.sh.cvut.cz/MIRRORS/slackware/slackware-13.1/
ftp://ftp.slackware.cz/slackware/slackware-13.1/ ask for password
ftp://ftp.slackware.hu/slackware/slackware-13.1/
ftp://ftp.uoi.gr/mirror/OS/slackware/slackware-13.1/
ftp://ftp.wh8.tu-dresden.de/pub/linux/distributions/slackware/slackware-13.1/
ftp://mirror.etf.bg.ac.yu/slackware/slackware-13.1/
ftp://mirrors.evrocom.net/pub/slackware/slackware-13.1/
ftp://sharon.esrac.ele.tue.nl/pub/slackware/slackware-13.1/
ftp://slackware.perespim.ru/pub/slackware-13.1/
http://www.software-mirror.com/linuxpackages/Slackware-12.1/
http://ftp.scarlet.be/pub/linuxpackages/Slackware-12.1/
ftp://ftp.scarlet.be/pub/linuxpackages/Slackware-12.1/
http://opensys.linuxpackages.net/Slackware-12.1/
ftp://opensys.linuxpackages.net/pub/Slackware-12.1/
http://linuxpackages.reco-systems.de//Slackware-12.1/
http://ftp.de-mirror.org/linuxpackages//Slackware-12.1/
ftp://ftp.de-mirror.org/linuxpackages//Slackware-12.1/
http://lp.slackwaresupport.com/Slackware-12.1/
http://ftp.naist.jp/pub/Linux/linuxpackages/Slackware-12.1/
ftp://ftp.nara.wide.ad.jp/pub/Linux/linuxpackages/Slackware-12.1/
http://linuxpackages.cs.utah.edu//Slackware-12.1/
ftp://mirror.cs.utah.edu/pub/linuxpackages//Slackware-12.1/
http://linuxpackages.inode.at/Slackware-12.1/
ftp://linuxpackages.inode.at/Slackware-12.1/
http://mirrors.unixsol.org/linuxpackages//Slackware-12.1/
ftp://mirrors.unixsol.org/linuxpackages//Slackware-12.1/
http://www2.linuxpackages.net/packages/Slackware-12.1/
ftp://ftp.slackware.hu/linuxpackages/Slackware-12.1/
http://linuxpackages.telecoms.bg/Slackware-12.1/
ftp://linuxpackages.telecoms.bg/Slackware-12.1/
http://slacky.uglyplace.org/repository/slackware-13.1/

updated slapt-getrc
Code: [Select]
WORKINGDIR=/home/ftp/pub/veclinux/packages
EXCLUDE=kernel,kernel-ide,kernel-source,kernel-headers,kernel-modules
#DISABLED=file:///mnt/cdrom/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.0/packages/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.0/extra/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.0/patches/:OFFICIAL
#SOURCE=http://vectorlinux.osuosl.org/veclinux-7.0/testing/
SOURCE=http://vectorlinux.osuosl.org/veclinux-7.0/gsb-2.22/
#DISABLED=http://vectorlinux.osuosl.org/veclinux-7.0/unstable/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/packages/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/patches/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/extra/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/testing/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/gsb-2.22/
#DISABLED=ftp://ftp.osuosl.org/pub/vectorlinux/veclinux-7.0/unstable/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/packages/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/patches/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/extra/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/testing/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/gsb-2.22/
#DISABLED=http://distro.ibiblio.org/pub/linux/distributions/vectorlinux/veclinux-7.0/unstable/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/packages/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/patches/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/extra/
#DISABLED=http://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/testing/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/packages/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/patches/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/extra/
#DISABLED=ftp://ftp.sh.cvut.cz/MIRRORS/vector/veclinux-7.0/testing/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=http://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=ftp://www.mirrorservice.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/packages/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/patches/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/extra/
#DISABLED=http://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/testing/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/packages/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/patches/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/extra/
#DISABLED=ftp://na.mirror.garr.it/mirrors/vectorlinux/veclinux-7.0/testing/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=http://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=ftp://www.gi.kernel.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=http://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=ftp://ftp7.freebsd.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=http://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/packages/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/patches/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/extra/
#DISABLED=ftp://ftp2.uk.vim.org/sites/vectorlinux.com/veclinux-7.0/testing/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-13.1/
#DISABLED=http://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=http://darkstar.ist.utl.pt/slackware/slackware-13.1/
#DISABLED=http://ftp.belnet.be/packages/slackware/slackware-13.1/
#DISABLED=http://ftp.gwdg.de/pub/linux/slackware/slackware-13.1/
#DISABLED=http://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-13.1/
#DISABLED=http://ftp.linux.cz/pub/linux/slackware/slackware-13.1/
#DISABLED=http://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=http://ftp.ntua.gr/pub/linux/slackware/slackware-13.1/
#DISABLED=http://ftp.riken.jp/Linux/slackware/slackware-13.1/
#DISABLED=http://ftp.slackware.cz/slackware/slackware-13.1/
#DISABLED=http://gd.tuwien.ac.at/opsys/linux/slackware/slackware-13.1/
#DISABLED=http://mirror.switch.ch/ftp/mirror/slackware/slackware-13.1/
#DISABLED=http://mirrors.dotsrc.org/slackware/slackware-13.1/
#DISABLED=http://mirrors.easynews.com/linux/slackware/slackware-13.1/
#DISABLED=http://mirrors.unixsol.org/slackware/slackware-13.1/
#DISABLED=http://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=http://serghei.net/linux/slackware/slackware-13.1/
#DISABLED=http://slackware.mirrors.pair.com/slackware-13.1/
#DISABLED=http://slackware.mirrors.tds.net/pub/slackware/slackware-13.1/
#DISABLED=http://slackware.oregonstate.edu/slackware-13.1/
#DISABLED=http://www.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-13.1/
#DISABLED=http://www.slackware.at/data/slackware-13.1/
#DISABLED=ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=ftp://ftp.chg.ru/pub/Linux/Slackware/slackware-13.1/
#DISABLED=ftp://darkstar.ist.utl.pt/pub/slackware/slackware-13.1/
#DISABLED=ftp://elektroni.phys.tut.fi/slackware-13.1/
#DISABLED=ftp://ftp.belnet.be/packages/slackware/slackware-13.1/
#DISABLED=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.cerias.purdue.edu/pub/os/slackware/slackware-13.1/
#DISABLED=ftp://ftp.fu-berlin.de/unix/linux/mirrors/slackware/slackware-13.1/
#DISABLED=ftp://ftp.funet.fi/pub/mirrors/ftp.slackware.com/pub/slackware-13.1/
#DISABLED=ftp://ftp.gwdg.de/pub/linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.heanet.ie/mirrors/ftp.slackware.com/pub/slackware/slackware-13.1/
#DISABLED=ftp://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-13.1/
#DISABLED=ftp://ftp.linux.cz/pub/linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.lip6.fr/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=ftp://ftp.man.szczecin.pl/pub/Linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-13.1/
#DISABLED=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-13.1/
#DISABLED=ftp://ftp.ntua.gr/pub/linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.red.telefonica-wholesale.net/slackware/slackware-13.1/
#DISABLED=ftp://ftp.riken.jp/Linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.slackware-brasil.com.br/slackware-13.1/
#DISABLED=ftp://ftp.slackware.lt/pub/Linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.slackware.no/pub/linux/slackware/slackware-13.1/
#DISABLED=ftp://ftp.sunet.se/pub/Linux/distributions/slackware/slackware-13.1/
#DISABLED=ftp://mirror.switch.ch/mirror/slackware/slackware-13.1/
#DISABLED=ftp://mirrors.blueyonder.co.uk/sites/ftp.slackware.com/slackware-13.1/
#DISABLED=ftp://mirrors.dotsrc.org/slackware/slackware-13.1/
#DISABLED=ftp://mirrors.unixsol.org/slackware/slackware-13.1/
#DISABLED=ftp://mirrors.usc.edu/pub/linux/distributions/slackware/slackware-13.1/
#DISABLED=ftp://slackware.mirrors.pair.com/slackware-13.1/
#DISABLED=ftp://slackware.mirrors.tds.net/pub/slackware/slackware-13.1/
#DISABLED=ftp://slackware.oregonstate.edu/pub/slackware/slackware-13.1/
#DISABLED=ftp://sunsite.cnlab-switch.ch/mirror/slackware/slackware-13.1/
#DISABLED=ftp://sunsite.icm.edu.pl/pub/Linux/slackware/slackware-13.1/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-13.1/
#DISABLED=http://www.slacky.eu/repository/slackware-13.1/
#DISABLED=http://darkstar.ist.utl.pt/slackware/addon/slacky/slackware-13.1/
#DISABLED=ftp://darkstar.ist.utl.pt/pub/slackware/addon/slacky/slackware-13.1/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-12.1/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-12.2/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-13.0/
#DISABLED=ftp://ftp.osuosl.org/pub/slackware/slackware-13.1/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-12.1/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-12.2/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-13.0/
#DISABLED=ftp://ftp.slackware.com/pub/slackware/slackware-13.1/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-12.1/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-12.2/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-13.0/
#DISABLED=ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/slackware/slackware-13.1/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-12.1/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-12.2/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-13.0/
#DISABLED=http://na.mirror.garr.it/mirrors/Slackware/slackware-13.1/
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on April 19, 2011, 09:06:29 pm
Just notice missing lapack-3.3.0 as dependencies for numpy and inkscape...
lapack is not found in the VL7 testing repo...
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Colonel Panic on April 20, 2011, 06:20:09 am
I downloaded and installed Vector 7.0 beta 2 yesterday and unfortunately found two problems;

1 / The X11 keyboard maps seem to be missing, so I can't load the UK keyboard map; the only one available is the US map, so " and @ are transposed in X Windows on my machine.

2 / I had a preexisting installation of 6.0 KDE Classic on my machine. The automatic install of LILO evidently misread my Vector 6.0 KDE Classic boot folder, so I got a "kernel panic" when I tried to boot VL KDE Classic from the LILO boot menu.

Sorry to be the bringer of bad news and all that but you did ask for problems! Also, a couple of apps I've come to rely on in Vector are apparently no longer present; Chestnut Dialer for PPP dialup, and K3B for burning data and ISOs to CD and DVD. Is this intentional?

Regards,

Colonel Panic .
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 20, 2011, 12:29:05 pm
Quote
Sorry to be the bringer of bad news and all that but you did ask for problems! Also, a couple of apps I've come to rely on in Vector are apparently no longer present; Chestnut Dialer for PPP dialup, and K3B for burning data and ISOs to CD and DVD. Is this intentional?

Chestnut dialer is in the testing repo, (you will need to enable it on a fresh install) and k3b is in the works.

If you want k3b now and 70 other applications, you could try the MMBD for vl7.0
http://www.opensourcebistro.com/catalog/product_info.php?products_id=30&osCsid=ccb591d06058b985f37d1adfa97e7050 (http://www.opensourcebistro.com/catalog/product_info.php?products_id=30&osCsid=ccb591d06058b985f37d1adfa97e7050)
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Colonel Panic on April 21, 2011, 09:17:09 am
Thanks for your reply and the info,

CP .
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Pita on April 24, 2011, 08:15:52 pm
Floppy cannot be mounted since there is no /dev/fd0:

@~:$ mount /mnt/floppy
mount: special device /dev/fd0 does not exist

l$ ls /dev/f*         
/dev/fb0  /dev/full  /dev/fuse

Further: category LC_ALL is not supported. That is for Zeroinstall of Rox.

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on April 27, 2011, 10:33:45 pm
Well, I bought a Samsung 511, the only laptop I could find with a sunlight readable lcd (I couldn't find a lenovo laptop with a sunlight readable screen). 

VL 6.0 would not load. It either didn't find the media or didn't find the hard-drive, depending on whether I used the regular or the old installer (linux).  So I tried VL 7 Beta 2 and it loaded fine with the modern installer, but WICD did not find the wireless card.  So, figuring my computer might not have a working wireless card in it (though the box said otherwise) I loaded mint and the wireless worked flawlessly.  So I then tried VL 7 Beta 2 with the old installer (install) and it loaded fine but did not install xfce4 and wicd (via fluxbox) could not find any wireless extensions. Ifconfig didn't show any wireless at all.  That is where I am now.

Does anyone have a suggestion on how I can access the wireless card?  I'm sure mint is fine and all that but don't want to fool with a new operating system.

I am going to hook it up to the wire now and update everything.  I will report if that works.

john
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: uelsk8s on April 27, 2011, 11:15:25 pm
John,
Post the id of your wireless card.
it should be in the output of lspci or possibly lsusb

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: GrannyGeek on April 27, 2011, 11:16:35 pm
I hope you installed VL7 beta 2.1 and not VL7 beta 2. Beta 2.1 fixed some fatal problems I had with beta 2.

Someone else will have to help with your wireless, since that's something I had to flail about with to get it working on my VL6 Light laptop, my only computer with wireless.
--GrannyGeek
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: j.a.watson on April 27, 2011, 11:47:34 pm
Regarding the Samsung 511, although I am not familiar with that specific model I have two other Samsung netbooks (N150 and NF310), and I suspect that the 511 most likely has a Broadcom 4313 wireless adapter.  That requires the brcm80211 driver, which as far as I know is still not included in the VL7B2 distribution.

If it is any consolation, I have tested both of my Samsung sytems with a variety of other Linux distributions which do include the brcm80211 driver, and they work very well.  So hopefully all will be well once the driver makes it into VL.

While it is possible to get the 4313 adapter working with the older "wl" or "broadcom-wl" driver (aka "STA" on Ubuntu), there are serious performance problems with it, and the throughput very low.

jw
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: stretchedthin on April 27, 2011, 11:55:37 pm
@sledgehammer.  Just want you to check one thing. As of the more recent release 2.1 I believe amount them. WICD is not completely configured at install.
You may simply need to click the wicd icon on the panel, click preferences in that window then in the resulting window from that enter
wlan0         
in the Wireless interface box.

if that does not work try
wlan1
To find out for sure as root, in the terminal, type
iwconfig
If it gives you a wlan#, than use that.  If it does not give you a number for wlan then, indeed you have a different problem.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on April 28, 2011, 07:36:25 am
Thanks.   Got model wrong.  Its a Samsung RF511.  Nothing on iwconfig, Stretchedthin.  Yes, j.a.watson, everything but wireless seems to be working.  Not too sure though as I won't bother loading my programs and date til I get wireless working.  My son might do me a favor and load the driver.

john
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: Andy Price on April 28, 2011, 08:24:35 am
With development moving at a good pace I wonder how near VL7 is to freezing features? There are a few things I've noticed and would like to mention. Please forgive any repeats!

The text installer doesn't have an option to check the disk for integrity any more, nor does it allow you to choose which packages to install. It uses LILO by default and there's no option to install GRUB, unlike the GUI installer.

VASM has the option to save the user password but Gslapt, which I use much more, doesn't.

One other thought:
At present the GUI installer offers three options which are (roughly) "everything", "choose not to install some apps" and "minimal system plus X". I tried the latter and is was just a bit too stark (for me) and difficult to build upon. How about an option for "minimal install plus X plus XFCE base"? This would give a nice lean installation with an easy-to-use GUI, to which you could add your own choice of apps. It's not really my idea; I tried Salix recently and this was one of the installation options which I really liked. It's seems far preferable to removing all the stuff that you don't want.

Cheers
Andy
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on April 28, 2011, 09:01:34 am
Quote
I hope you installed VL7 beta 2.1 and not VL7 beta 2. Beta 2.1 fixed some fatal problems I had with beta 2.

Grannygeek,

How do I know which version I installed?

Thanks

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: nightflier on April 28, 2011, 12:18:06 pm
cat /etc/vector-version
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: j.a.watson on April 28, 2011, 01:01:11 pm
One simple way to find out what kind of wireless adapter you have is "lspci" as root.  If you see "Broadcom 4313" in the list, that's what you have, and you need the brcm80211 driver.  If it is some other Broadcom model, or something else entirely (Atheros, Intel or some such), you might have a bit more luck.

jw
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on April 28, 2011, 09:49:18 pm
I now have VL7 Beta 2.1 installed on the Samsung.  Still had trouble getting xfce4 to run.  Removed the installed xfce4, update and reinstall xfce4.

j.a.watson, I think this may be it (I am typing this on the T42 so am copying from the RF511 lspci)

02:00.0 Network controller:  Intel Corporation WiFi Link 1000 series

Not too sure where to go from here.

John

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: j.a.watson on April 29, 2011, 01:05:54 am
Yes, that appears to be it.  I'm afraid I can't be of much more specific help here, because I don't have anything with that adapter in it.  From what I can find with a quick search, it should use the iwlagn driver, which is the same one that the Intel 5300 adapter in my Fujitsu laptop uses.  You can find out if the driver is being loaded with "lspci -v", if there is a driver attached to it it will be listed on the last line of information for that device.  It apparently also needs the firmware from the package "firmware-iwlwifi".  But even with that much information, I can't tell you clearly how to get it working, because I don't have one.  Hopefully someone more expert here that I can help you further.  Good luck.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on April 29, 2011, 09:36:39 am
j.a.watson,

I am at the office now and can't try "lspci -v".  Do you recall what repository you used to get the iwlagn driver? I can try that tomorrow.

thanks

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 01, 2011, 04:29:11 pm
uelsk8s
Quote
Post the id of your wireless card.
it should be in the output of lspci or possibly lsusb

Here goes:

Quote
00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09)
00:01.0 PCI bridge: Intel Corporation Device 0101 (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09)
00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4)
00:1c.3 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b4)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Device 1c49 (rev 04)
00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation Cougar Point 2 port SATA IDE Controller (rev 04)
01:00.0 3D controller: nVidia Corporation Device 0df4 (rev a1)
02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
04:00.0 USB Controller: NEC Corporation Device 0194 (rev 04)
vector://home/johwhi

I noticed the following in the README file, as I attempted to follow along with j.a.watson's suggestion (by downloading the microcode images (iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode)
 from intellinuxwireless.org.  This file apparently has to be somewhere on the system but I don't know where to put it.
:

Quote
1. OVERVIEW

The file iwlwifi-5000-5.ucode provided in this package must be
present on your system in order for the Intel Wireless WiFi Link
AGN driver for Linux (iwlagn) to operate on your system.

The "-5" in the filename reflects an interface/architecture version number.
It will change only when changes in new uCode releases make the new uCode
incompatible with earlier drivers.

On adapter initialization, and at varying times during the uptime of
the adapter, the microcode is loaded into the memory on the network
adapter.  The microcode provides the low level MAC features including
radio control and high precision timing events (backoff, transmit,
etc.) while also providing varying levels of packet filtering which can
be used to keep the host from having to handle packets that are not of
interest given the current operating mode of the device.

2. INSTALLATION

The iwlagn driver will look for the file iwlwifi-5000-5.ucode using the
kernel's firmware_loader infrastructure.  In order to function
correctly, you need to have this support enabled in your kernel.  When
you configure the kernel, you can find this option in the following
location:

        Device Drivers ->
                Generic Driver Options ->
                        Hotplug firmware loading support


You can determine if your kernel currently has firmware loader support
by looking for the CONFIG_FW_LOADER definition on your kernel's
.config.

In addition to having the firmware_loader support in your kernel, you
must also have a working hotplug and udev infrastructure configured.
The steps for installing and configuring hotplug and udev are very
distribution specific.

Once you have the firmware loader in place (or if you aren't sure and
you just want to try things to see if it works), you need to install
the microcode file into the appropriate location.

Where that appropriate location is depends (again) on your system
distribution.  You can typically find this location by looking in the
hotplug configuration file for your distro:

   % grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent

This should give you output like:

   FIRMWARE_DIR=/lib/firmware

If it lists more than one directory, you only need to put the
microcode in one of them.  In the above example, installation is
simply:

   % cp iwlwifi-5000-5.ucode /lib/firmware

You can now load the driver (see the INSTALL and README.iwlwifi provided with
the iwlwifi package for information on building and using that driver.)

Other than the problem I am having getting on the wireless, VL 7 Beta 2.1 seems to work great on my new Samsung RF511 S03.

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 01, 2011, 09:27:33 pm
uelsk8s
Quote
Post the id of your wireless card.
it should be in the output of lspci or possibly lsusb

Here goes:

Quote
00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09)
00:01.0 PCI bridge: Intel Corporation Device 0101 (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09)
00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4)
00:1c.3 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b4)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Device 1c49 (rev 04)
00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04)
00:1f.5 IDE interface: Intel Corporation Cougar Point 2 port SATA IDE Controller (rev 04)
01:00.0 3D controller: nVidia Corporation Device 0df4 (rev a1)
02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
04:00.0 USB Controller: NEC Corporation Device 0194 (rev 04)
vector://home/johwhi

I noticed the following in the README file, as I attempted to follow along with j.a.watson's suggestion (by downloading the microcode images (iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode)
 from intellinuxwireless.org.  This file apparently has to be somewhere on the system but I don't know where to put it.
:

Quote
1. OVERVIEW

The file iwlwifi-5000-5.ucode provided in this package must be
present on your system in order for the Intel Wireless WiFi Link
AGN driver for Linux (iwlagn) to operate on your system.

The "-5" in the filename reflects an interface/architecture version number.
It will change only when changes in new uCode releases make the new uCode
incompatible with earlier drivers.

On adapter initialization, and at varying times during the uptime of
the adapter, the microcode is loaded into the memory on the network
adapter.  The microcode provides the low level MAC features including
radio control and high precision timing events (backoff, transmit,
etc.) while also providing varying levels of packet filtering which can
be used to keep the host from having to handle packets that are not of
interest given the current operating mode of the device.

2. INSTALLATION

The iwlagn driver will look for the file iwlwifi-5000-5.ucode using the
kernel's firmware_loader infrastructure.  In order to function
correctly, you need to have this support enabled in your kernel.  When
you configure the kernel, you can find this option in the following
location:

        Device Drivers ->
                Generic Driver Options ->
                        Hotplug firmware loading support


You can determine if your kernel currently has firmware loader support
by looking for the CONFIG_FW_LOADER definition on your kernel's
.config.

In addition to having the firmware_loader support in your kernel, you
must also have a working hotplug and udev infrastructure configured.
The steps for installing and configuring hotplug and udev are very
distribution specific.

Once you have the firmware loader in place (or if you aren't sure and
you just want to try things to see if it works), you need to install
the microcode file into the appropriate location.

Where that appropriate location is depends (again) on your system
distribution.  You can typically find this location by looking in the
hotplug configuration file for your distro:

   % grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent

This should give you output like:

   FIRMWARE_DIR=/lib/firmware

If it lists more than one directory, you only need to put the
microcode in one of them.  In the above example, installation is
simply:

   % cp iwlwifi-5000-5.ucode /lib/firmware

You can now load the driver (see the INSTALL and README.iwlwifi provided with
the iwlwifi package for information on building and using that driver.)

Other than the problem I am having getting on the wireless, VL 7 Beta 2.1 seems to work great on my new Samsung RF511 S03.

John

try this...should be similar with your 1000 series
check your log files under /var/log/ for any message

http://www.linuxquestions.org/questions/slackware-14/wireless-internet-not-working-intel-corporation-wimax-wifi-link-6050-series-871210/

btw, can u post your lsmod too...
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 02, 2011, 12:09:23 am
Thanks, hata_ph

I looked at the site and tried some of the things mentioned. I need to study it more.  Later.  Getting tired now.

here is lsmod:
Quote
root:# lsmod
Module                  Size  Used by
zd1211rw               34753  0
fuse                   51496  3
rfcomm                 25101  0
l2cap                  29295  3 rfcomm
bluetooth              41358  2 rfcomm,l2cap
snd_seq_dummy           1047  0
snd_seq_oss            21919  0
snd_seq_midi_event      3936  1 snd_seq_oss
snd_seq                36784  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          3978  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            28733  0
snd_mixer_oss          10601  1 snd_pcm_oss
speedstep_lib           2566  0
acpi_cpufreq            4625  1
freq_table              1771  1 acpi_cpufreq
mperf                    953  1 acpi_cpufreq
snd_hda_codec_hdmi     17474  1
snd_hda_codec_realtek   203563  1
i915                  277114  2
drm_kms_helper         19476  1 i915
drm                   126262  3 i915,drm_kms_helper
snd_hda_intel          16338  0
iwlagn                122480  0
snd_hda_codec          50634  3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
iwlcore                44104  1 iwlagn
i2c_algo_bit            3678  1 i915
intel_agp               7950  1 i915
uvcvideo               47304  0
snd_hwdep               4213  1 snd_hda_codec
mac80211              156516  3 zd1211rw,iwlagn,iwlcore
processor              21878  1 acpi_cpufreq
video                   9832  1 i915
intel_gtt               9667  3 i915,intel_agp
snd_pcm                48986  4 snd_pcm_oss,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
videodev               46664  1 uvcvideo
rtc_cmos                7153  0
thermal                 6458  0
fan                     1858  0
r8169                  28956  0
rtc_core               12059  1 rtc_cmos
agpgart                19252  3 drm,intel_agp,intel_gtt
snd_timer              13063  2 snd_seq,snd_pcm
thermal_sys            10226  4 processor,video,thermal,fan
cfg80211              101032  4 zd1211rw,iwlagn,iwlcore,mac80211
rtc_lib                 1547  1 rtc_core
mii                     2838  1 r8169
i2c_i801                6270  0
snd                    36085  12 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
wmi                     6416  0
battery                 8434  0
button                  3869  1 i915
ac                      2485  0
soundcore               3740  1 snd
i2c_core               13669  6 i915,drm_kms_helper,drm,i2c_algo_bit,videodev,i2c_i801
rfkill                 11023  2 bluetooth,cfg80211
snd_page_alloc          5232  2 snd_hda_intel,snd_pcm
sg                     18105  0
evdev                   6678  16
hwmon                   1109  1 thermal_sys
vector://home/johwhi/Downloads
root:#

Don't know if this is relevant or not, but here is locate iwlwifi

Quote
root:# locate iwlwifi
/lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi
/lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko
/lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
/lib/modules/2.6.38.2/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko
/lib/firmware/LICENSE.iwlwifi-3945-ucode
/lib/firmware/README.iwlwifi-3945-ucode
/lib/firmware/iwlwifi-4965-1.ucode
/lib/firmware/iwlwifi-4965.ucode
/lib/firmware/iwlwifi-3945-1.ucode
/lib/firmware/iwlwifi-4965-2.ucode
/usr/src/linux-2.6.38.2/include/config/iwlwifi.h
/home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1-1.tgz
/home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1
/home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/README.iwlwifi-5000-ucode
/home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/iwlwifi-5000-5.ucode
/home/johwhi/Downloads/iwlwifi-5000-ucode-8.83.5.1/LICENSE.iwlwifi-5000-ucode

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 02, 2011, 07:38:46 am
Your lsmod show iwlagn module is loaded. Did you try ifconfig or iwconfig?

Quote
iwlcore                44104  1 iwlagn
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 02, 2011, 10:30:51 am
Here is my ifconfig and iwconfig:

Quote
root:# ifconfig
eth0      Link encap:Ethernet  HWaddr E8:11:32:46:E3:FA 
          inet addr:192.168.2.7  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1842 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1480024 (1.4 Mb)  TX bytes:362682 (354.1 Kb)
          Interrupt:46 Base address:0xc000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vector://home/johwhi
root:# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

vector://home/johwhi
root:#
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 02, 2011, 08:19:23 pm
Have u try to download the 1000 series firmware?
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 02, 2011, 09:42:18 pm
I am trying to figure out how to download the 1000 series firmware. 

Meanwhile, here is lspci -v, which I think was requested earlier.

Quote
root:# lspci -v
00:00.0 Host bridge: Intel Corporation Device 0104 (rev 09)
   Subsystem: Samsung Electronics Co Ltd Device c0a5
   Flags: bus master, fast devsel, latency 0
   Capabilities: [e0] Vendor Specific Information <?>
   Kernel driver in use: agpgart-intel
   Kernel modules: intel-agp

....

02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
   Subsystem: Intel Corporation WiFi Link 1000 Series 1000BGN
   Flags: fast devsel, IRQ 16
   Memory at f6c00000 (64-bit, non-prefetchable) [size=8K]
   Capabilities: [c8] Power Management version 3
   Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [e0] Express Endpoint, MSI 00
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [140] Device Serial Number 8c-a9-82-ff-ff-15-c3-44
   Kernel modules: iwlagn

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
   Subsystem: Samsung Electronics Co Ltd Device c0a5
   Flags: bus master, fast devsel, latency 0, IRQ 46
   I/O ports at b000 [size=256]
   Memory at e2c04000 (64-bit, prefetchable) [size=4K]
   Memory at e2c00000 (64-bit, prefetchable) [size=16K]
   Capabilities: [40] Power Management version 3
   Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [70] Express Endpoint, MSI 01
   Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
   Capabilities: [d0] Vital Product Data
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [140] Virtual Channel <?>
   Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
   Kernel driver in use: r8169
   Kernel modules: r8169

.....
vector://home/johwhi/src/python-dateutil-2.0
root:#

And here is dmesg (which I will delete in whole or part following response as it messes up the thread, in case that is relevant:

Quote
root:# dmesg
...
[   14.198311] HDA Intel 0000:00:1b.0: setting latency timer to 64
[   14.233558] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[   14.233562] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[   14.233615] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   14.233625] iwlagn 0000:02:00.0: setting latency timer to 64
[   14.233656] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[   14.254952] iwlagn 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6
[   14.254956] iwlagn 0000:02:00.0: Device SKU: 0X9
[   14.254958] iwlagn 0000:02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[   14.254970] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
[   14.255057] iwlagn 0000:02:00.0: irq 48 for MSI/MSI-X
[   14.384047] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-3.ucode' failed.
[   14.385385] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-2.ucode' failed.
[   14.386618] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-1.ucode' failed.
[   14.386622] iwlagn 0000:02:00.0: no suitable firmware found!
[   14.386793] iwlagn 0000:02:00.0: PCI INT A disabled
[   14.736188] hda_codec: ALC269VB: BIOS auto-probing.
...
vector://home/johwhi/src/python-dateutil-2.0
root:#

Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 02, 2011, 10:04:35 pm
from your /var/log/messages it say missing iwlwifi-1000-3.ucode. Download it and put it in your /lib/firmware and try again..,

http://www.intellinuxwireless.org/?n=downloads

Quote
[   14.233558] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[   14.233562] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[   14.233615] iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   14.233625] iwlagn 0000:02:00.0: setting latency timer to 64
[   14.233656] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[   14.254952] iwlagn 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6
[   14.254956] iwlagn 0000:02:00.0: Device SKU: 0X9
[   14.254958] iwlagn 0000:02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[   14.254970] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
[   14.255057] iwlagn 0000:02:00.0: irq 48 for MSI/MSI-X
[   14.384047] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-3.ucode' failed.
[   14.385385] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-2.ucode' failed.
[   14.386618] iwlagn 0000:02:00.0: request for firmware file 'iwlwifi-1000-1.ucode' failed.
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 03, 2011, 12:01:31 am
Ha!  It works!  YAAAAAAAAAAAAAAAAAAAAAAAAAAAY!  hata_ph and everyone who helped, thanks a trillion!  Unless I hear otherwise, in the morning I will delete some of the quotes I posted tonight as they are too lengthy and are messing up this thread.

Another comment about VL 7.beta 2.1. I don't see the root (backup) version of grsync.  That was quite helpful.  Now that the wireless is working I plan to move my stuff over and will report further.   I think moving files over would be easier with the root backup grsync program.

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 03, 2011, 12:58:06 am
Ha!  It works!  YAAAAAAAAAAAAAAAAAAAAAAAAAAAY!  hata_ph and everyone who helped, thanks a trillion!  Unless I hear otherwise, in the morning I will delete some of the quotes I posted tonight as they are too lengthy and are messing up this thread.

Another comment about VL 7.beta 2.1. I don't see the root (backup) version of grsync.  That was quite helpful.  Now that the wireless is working I plan to move my stuff over and will report further.   I think moving files over would be easier with the root backup grsync program.

John

Good that it is work. Maybe u can write a How to in the forum for other to follow it :)
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: sledgehammer on May 03, 2011, 11:19:43 pm
dosemu (testing repository) installs as root.  Formerly, I ran it as non-root.

grsync (root backup) is not available.  This is a crucial backup program.

As I have said, I really like VL7

John
Title: Re: VectorLinux 7 Beta2 bugs and observations
Post by: hata_ph on May 03, 2011, 11:32:52 pm
dosemu (testing repository) installs as root.  Formerly, I ran it as non-root.

grsync (root backup) is not available.  This is a crucial backup program.

As I have said, I really like VL7

John

not sure about dosemu but grsync-1.1.1 is in the VL7 testing repo...can you double check?
Title: Re: VectorLinux 7 Beta2 bugs and observations - Cairo-Dock Issues
Post by: Ralph_Ellis on May 04, 2011, 07:51:11 pm
Recently, my normally very fast Vector Linux 7 installation started slowing down to a crawl for long periods. When I ran htop,  I noticed that there were 9 instances of cairo-dock running. I turned off cairo-dock and uninstalled it.  The speed of the operating system improved dramatically. I am running a normal installation with the packages, extra and testing repositories for updates. I have also installed the proprietary Nvidia driver. Clearly, the problem was cairo-dock since everything else is running well.
The cairo-dock is very pretty to look at but perhaps it should not be part of the base installation.
Has anyone else hit this problem?
I should note that cairo-dock was not an issue with the initial installation. Only after I had been running Vector Linux for about two weeks did I run into an ongoing problem. It may have been affected by one of the updates.