VectorLinux

Cooking up the Treats => Distro development => Topic started by: vector on October 08, 2011, 11:47:42 pm

Title: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 08, 2011, 11:47:42 pm
 Please post bug reports, suggestions, and comments for VECTORLINUX 7.0 RC3.4 here.  Thanks..
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: |nic| on October 09, 2011, 04:36:11 am
Installed it on my Samsung N110 netbook.
Installation went without problems. Everything is working out of the box ( wireless, touchpad,..)
Using VL Quickpicks makes it very easy to install frequently used programs.
The only bug i'm having at the moment is when I try to set up screensaver. Xscreensaver is saying the deamon is not running and when clicking ok to activate, I get the following error :
Code: [Select]
The xscreensaver daemon did not start up properly.Please check your $PATH and permissions.
That's all for now.

greets

nicdm
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: scififry on October 09, 2011, 09:49:57 am
Tried installing on the Athlon. Froze up using the graphical installer at 5% and using the text installer also at 5% when installing the kernel modules, with the difference that I'm not getting a debugging output on the kernel panic in the text installer anymore.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: MikeCindi on October 09, 2011, 09:43:05 pm
Installed in a VBox VM and all has gone very smoothly so far. My test machine is DOA and has been for a while...hope to have real hardware to test on soon.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: j.a.watson on October 10, 2011, 05:46:34 am
I have downloaded and installed (or tried to install) on a couple of my netbooks.

Good news: I was able to create a bootable USB stick with Unetbootin, and then only had to make one small change to the USB stick in order to boot and install from it.  In the isolinux directory, rename init.lz to init.gz.  That's it.  Then boot the stick and install.  Very nice.

Other News: On my laptops with 1366x768 displays, the GUI installer will not come up with auto-detect resolution, and the only resolution which works is so low that when the installer gets to asking for the root password, the window is too small and there are no scroll bars, so the input fields are lost off-screen somewhere.

Not so good news: When installed on my netbooks which have a Broadcom 4313 WiFi adapter, the driver is not found.  This seems a bit strange to me - I am SURE that I installed RC2 and the brcm80211 driver was included.  However, I have searched under /lib/modules and I can find no trace of either the brcm80211 driver nor the newer brcmsmac driver.  Have these really been omitted on purpose?

Thanks for any advice or solutions.

jw

Update: This is even a bit stranger than I thought.  I just installed RC3.4 on my HP Pavilion dm1-3105ez, and the Ralink 5390 WiFi adapter in it works just fine, with the rt2800pci driver.  Ok, this is because the Ralink driver is included in the 3.0 kernel, but still, this has to mean the omission of the Broadcom brcm driver was an oversight, doesn't it?

Thanks,

jw
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 10, 2011, 10:43:07 am
Just downloaded and installed RC 3.4 today, on a 2001 Compaq PIII desktop with 512 MB of RAM.

It looks good (cool dark blue theme, wallpaper etc.) and so far it works well except - the problem I had before with installing X11 keymaps hasn't been sorted out yet.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 10, 2011, 01:31:49 pm
Quote
Not so good news: When installed on my netbooks which have a Broadcom 4313 WiFi adapter, the driver is not found.  This seems a bit strange to me - I am SURE that I installed RC2 and the brcm80211 driver was included.
Yup looks like it was left out of our last kernel build. Thanks for finding that we will get it in our next kernel.

Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 10, 2011, 01:41:35 pm
Quote
the problem I had before with installing X11 keymaps hasn't been sorted out yet.
Colonel Panic when you do the install are you choosing the uk keyboard on the first screen of the gui installer?
I tried an install that way and worked for me. The vasm keyboard setup might be broken have to look at that.
You can look in your $HOME / .bash_profile and should see something like setxkbmap -model uk. If its set for US than you did not do the keyboard selection from the gui installer. Check those things and let us know ok.

Thanks,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 10, 2011, 03:21:36 pm
Ah, should have been clearer in what I said. I use the text-based installation procedure as my computer has hung before when trying to set the video (resolution + colour depth) automatically in the gui (graphics-based) one. Perhaps I should have reported that as a bug in the past, but didn't think to. Sorry for the confusion.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 10, 2011, 08:30:17 pm
Installed on my desktop PC with vinstall.

Seems all is working w/o me doing much,
-- internet,
-- sound,
-- resolution,
-- printers detected, usb:/unknown, my old Epson impact printer and is  printing,
-- usb flashdrive detected.

I am burning a CD now and will see if it can install on HP-2133 netbook which previous versions of VL7 could not.

Edit:

The problem remains when trying to install to HP-2133. The gui installer
doe not get the correct resolution for the screen. It is too large, letters and windows overlap.
When installing on my PC it first shows possible resolution settings and asks for the right one.
This is absent on the HP netbook.
Nothing is being asked before gui installer opens.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 11, 2011, 12:51:45 am
Quote
Ah, should have been clearer in what I said. I use the text-based installation procedure as my computer has hung before when trying to set the video (resolution + colour depth) automatically in the gui (graphics-based) one.
Colonel panic.............we are working on the vasm keyboard routine but in the meantime heres a neat trick.Just copy /usr/share/X11/xorg.conf.d/90-layout-keyboard.conf to /etc/X11/xorg.conf.d then change XKBLayout from us to uk in the 90-layout file and restart X and you should be good to go

Cheers,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: GrannyGeek on October 11, 2011, 12:42:47 pm
I installed RC3.4 on my Athlon 64 X2. No problems at all so far. I was able to use the monitor's native 1600x1200 during installation and it autoidentified everything in VASM. I'm using the nouveau driver for my NVidia GeForce card.

Alas, it seems Scribus is not included. I would compile it myself but at this time I don't have the energy.<g> I hope the latest Scribus will be in the repos. It's something of a moving target, as I think the latest is Release Candidate 5 and another one will probably be available soon.

I added several third-party programs and they are all working properly.

If I feel well enough after tomorrow's chemo treatment, I'll install on my Sempron computer and report on how that goes.
--GrannyGeek
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: uelsk8s on October 11, 2011, 12:46:38 pm
Colonel panic
new vkeymapset is here: http://vectorlinux.osuosl.org/Uelsk8s/vkmapset.new
copy it to /sbin and run it as root
let us know how it works for you.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 11, 2011, 01:15:34 pm
Quote
Alas, it seems Scribus is not included. I would compile it myself but at this time I don't have the energy.<g> I hope the latest Scribus will be in the repos.
Granny the latest scribus is in the testing repo you can get it there via gslapt. We ran into space problems so something had to go............sorry about that!

Cheers,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 11, 2011, 03:39:35 pm
Colonel panic
new vkeymapset is here: http://vectorlinux.osuosl.org/Uelsk8s/vkmapset.new
copy it to /sbin and run it as root
let us know how it works for you.

Hi. Sorry to be the bearer of bad news, but it doesn't, unfortunately. I changed to "uk" and still ended up with the same (wrong) keystrokes that I had before.

I also copied /usr/share/X11/xorg.conf.d/90-layout-keyboard.conf to the /etc/X11/xorg.conf.d subdirectory, and then changed XKBLayout from "us" to "uk" in the 90-layout file as you suggested. On rebooting (which would have restarted X), I ended up with no keyboard in X at all.

Sorry but I'd rather tell you the truth than not; there's no point in pretending that everything's hunky dory when it isnt, especially in a "Bugs" development thread.

Cheers,
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 11, 2011, 08:11:05 pm
Quote
Hi. Sorry to be the bearer of bad news, but it doesn't, unfortunately. I changed to "uk" and still ended up with the same (wrong) keystrokes that I had before.
colonel panic ok thanks for testing our first two efforts please try number three.................:)
download and install this package: http://vectorlinux.osuosl.org/vec7/vlkbdset-0.1-noarch-vl70.txz
then run vasm and let us know if any success or failure.
Fingers crossed!!

Cheers,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: scififry on October 12, 2011, 09:21:25 am
Installed successfully onto the Duron, now posting from it.
New Kernel works great and increased the operating speed a lot! :)
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: hata_ph on October 12, 2011, 09:02:45 pm
Installed it on my Samsung N110 netbook.
Installation went without problems. Everything is working out of the box ( wireless, touchpad,..)
Using VL Quickpicks makes it very easy to install frequently used programs.
The only bug i'm having at the moment is when I try to set up screensaver. Xscreensaver is saying the deamon is not running and when clicking ok to activate, I get the following error :
Code: [Select]
The xscreensaver daemon did not start up properly.Please check your $PATH and permissions.
That's all for now.

greets

nicdm

there is a new xscreensaver-5.15 available in the testing repo. Pls test it see does it have the same problem or not...thanks :)
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 13, 2011, 11:23:40 am
Quote
Hi. Sorry to be the bearer of bad news, but it doesn't, unfortunately. I changed to "uk" and still ended up with the same (wrong) keystrokes that I had before.
colonel panic ok thanks for testing our first two efforts please try number three.................:)
download and install this package: http://vectorlinux.osuosl.org/vec7/vlkbdset-0.1-noarch-vl70.txz
then run vasm and let us know if any success or failure.
Fingers crossed!!

Cheers,
Vec

Thanks, I will.

Best,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: tictacPoc on October 13, 2011, 01:54:15 pm
I installed on Mini Laptop LT30 Gateway amd ( 2 go de ram, 250go drive, video x1280amd chipset, proco amd athlon LT110 ) on 2 different hard drive. One SSD kington 60 go and other regular drive.  Other config: AMD quadcore black edition, graphic card 4670 hdmi, 3 hard drive, two screen ( one 22 and one 24 po ) 2 keyboard one blutooth logitech X5000 mouse and keyboard and other regular.

Not problem with all config. run perfectly.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: aryr100 on October 13, 2011, 04:03:59 pm
Found ach-makepkg 3.5.4 depends on fake root for the update
*Grabbed the  fake root package from slackbuilds using sbopkg then upgraded arch without a problem*
Found Gslapt has extra enabled could cause problem with upgrading python from 2.7.1 to 2.7.2
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 13, 2011, 04:58:46 pm
Found ach-makepkg 3.5.4 depends on fake root for the update
*Grabbed the  fake root package from slackbuilds using sbopkg then upgraded arch without a problem*
Found Gslapt has extra enabled could cause problem with upgrading python from 2.7.1 to 2.7.2


fakeroot is in the testing repo. Seems we still have quite a few in testing that haven't moved out to extra or packages.

Why would extra repo cause problems upgrading python?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 13, 2011, 05:58:03 pm
On booting there is still the error message that in
/lib/udev/rules.d/56-hpmud_support.rules SYSFS has still not been changed to ATTR.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on October 13, 2011, 06:35:00 pm
Bonjour!

Vl7stdrc3.4 installation went smoothly on sharp mebuis PC-GP10-BE laptop ,once booting into system,laptop keyboard and mouse still occasionally go dummy due to the design flaw of S3 savage twistter graphic chips embeded with MB(which was contracted to cunny taiwanese company, manufactured in EVIL RED CHINA'S SWEATSHOP MANUAFACTURE BASE -SHENZHEN CITY -hk'S RED OUTSHIRTS),IT'S JUST DESTESTING experiences,even charity ORGs and NGOs don't accept this laptop .....

Ralink3370 chip based  wifi usb still not working at all, pls. put the ralink 3370 driver on VL mirrror ASAP!

idnkit package still missing  with vl7stdrc34, then nslookup won't work,had to download it frcom slackware 's mirror.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: GrannyGeek on October 13, 2011, 08:22:41 pm
I don't have an option to shut down or log out in XFce, just log out.

There was an easier one-command way to start an nfs network, but I don't remember what it was and I had to do my usual five or so rpc commands to get the network started. I'm having a problem. though. and will see if it persists through a reboot.

I installed Scribus--glad to see it's in the repos. I'm  perfectly content to download it but I do hope it will updated regularly.

Tomorrow I'm hoping to install on the Sempron.
--GrannyGeek
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on October 13, 2011, 08:44:02 pm
Quote
Ralink3370 chip based  wifi usb still not working at all, pls. put the ralink 3370 driver on VL mirrror ASAP!
Vincent....the rt2800usb module is supposed to cover that is that module not being loaded? Please reply asap

Thanks,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on October 14, 2011, 02:14:00 am
Quote
the rt2800usb module is supposed to cover that is that module not being loaded? Please reply asap
modprobe rt2800 with no problem....
but ralink 3370 wifi won't work still, still had to download the driver from ralink website and then install then ralink 3370 works.....
while as  you claimed , there's built-in driver with the kerne-3.0.4, but till it doesn't work
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 14, 2011, 08:40:07 pm
Yes for user in xfce4 clicking on panel "Log Out Dialog" it goes straight to login
display. No dialog, however, for root there is the usual dialog.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: GrannyGeek on October 15, 2011, 08:01:00 am
I've installed RC3.4 on the Sempron computer. My LCD monitor runs at 1280x1024 and that resolution has never worked in the graphical installer. I always give it a try with a new release and at least this time I got a picture instead of a monitor disappearance with a "Non Optimum Resolution" or "Non Optimum Refresh Rate" that required a computer shutdown. The picture I got was distorted, however, and I couldn't get to the boxes on which to click. So I restarted at 1024x768 and that worked fine for installation, as it always has. Once I do the autosetup without xorg the proper 1280x1024 res at 60 Hz is properly identified and working. I'm using the nouveau driver.

I have the same problem with exiting as I have on my Athlon computer. The only choice is Logout; Shutdown and Restart are grayed out. The Hibernate, etc., options don't appear. I don't care about those as I never use them. This is running as user. I've never tried to log out or shut down as root.

I've rebooted twice, maybe. On my Athlon the DNS server was wrong after a reboot. I fixed it in /etc/resolv.conf but need to reboot to see if it holds this time. I didn't encounter this problem on the Sempron. Will see what happens with a reboot.

There is still much I haven't done. I'm having an nfs problem on my network that I haven't tried hard to track down. If I can't figure it out I'll ask.

On the whole, quite satisfactory.
--GrannyGeek
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: nightflier on October 15, 2011, 09:42:08 am
Got the opportunity to try 3.4 on some real hardware, one with a GeForce GT 240 and another with a Radeon X800. I was pleasantly surprised to see how far the open source video drivers have come. On both machines, tuxracer was playable!
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 15, 2011, 12:33:12 pm
Quote
Hi. Sorry to be the bearer of bad news, but it doesn't, unfortunately. I changed to "uk" and still ended up with the same (wrong) keystrokes that I had before.
colonel panic ok thanks for testing our first two efforts please try number three.................:)
download and install this package: http://vectorlinux.osuosl.org/vec7/vlkbdset-0.1-noarch-vl70.txz
then run vasm and let us know if any success or failure.
Fingers crossed!!

Cheers,
Vec

Hi. I've tried it again, but sadly with the same result; the keyboard won't change over from the US one.

- CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 15, 2011, 07:31:38 pm
Did you log out of X or restart the computer after the change? I don't believe it is expected to make the change "live".

Also, can you please confirm that you're using RC3.4 here and not an older one? Xorg had problems with this in some older releases. `cat /etc/vector-version`
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 17, 2011, 03:57:26 pm
Thanks for replying.

Did you log out of X or restart the computer after the change?

Yes I did, twice (three times if you count today).

And still the problem remains, unfortunately. On holding down the shift key and typing across the top from left to right, I get the following;

~!@#$%^


 I don't believe it is expected to make the change "live".

True.

Also, can you please confirm that you're using RC3.4 here and not an older one? Xorg had problems with this in some older releases. `cat /etc/vector-version`

Yep, I did that and got this;

7.0 STD RC3.4 built on OCT-01-2001

So it is the current one.

Best,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: uelsk8s on October 17, 2011, 04:01:07 pm
Colonel Panic,

can you install this pkg: http://vectorlinux.osuosl.org/Uelsk8s/vlkbdset-0.1-noarch-2vl70.txz
It should let you set the keymap so that it works in terminal and X upon reboot. let us know if it works for you.

Thanks,
Uelsk8s
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 17, 2011, 04:03:07 pm
Thanks. Yes, I'll try that - 'twill have to be tomorrow though as it's very late here in the UK now.

Thanks again for your trouble,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: uelsk8s on October 17, 2011, 04:07:12 pm
Thanks. Yes, I'll try that - 'twill have to be tomorrow though as it's very late here in the UK now.

Thanks again for your trouble,

CP .

This maybe a dumb question, but I really dont know. Is there a difference between the gb and uk keymaps?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 17, 2011, 06:00:41 pm
Thanks. Yes, I'll try that - 'twill have to be tomorrow though as it's very late here in the UK now.

Thanks again for your trouble,

CP .

This maybe a dumb question, but I really dont know. Is there a difference between the gb and uk keymaps?


Well according to setxkbmap there is no such thing as uk map, however, there is a gb map.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 17, 2011, 06:07:47 pm
Why is "at" not anymore included in the services of VectorLinux? One has to copy it first from /etc/rc.d/init.d/sample to ../init.d. Then run services. Is it that no one is using "at" anymore? I use it all the time. It's fast and easy. Other distros have it still as a standard.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 18, 2011, 11:58:37 am
Colonel Panic,

can you install this pkg: http://vectorlinux.osuosl.org/Uelsk8s/vlkbdset-0.1-noarch-2vl70.txz
It should let you set the keymap so that it works in terminal and X upon reboot. let us know if it works for you.

Thanks,
Uelsk8s

Hi,

I installed the new package today. Still isn't happening I'm afraid;

~!@#$%^&

Wish I could say otherwise.

Thanks anyway,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 18, 2011, 01:37:11 pm
I installed the new package today. Still isn't happening I'm afraid;

Check your ~/.bash_profile for anything like "setxkbmap". Also make sure your ~/.Xmodmap file is empty.

I discovered just today that my .bash_profile had a line put in it by the installer that was preventing keyboard setting from working as expected.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 18, 2011, 11:53:09 pm
Thanks for your advice. I'm in Vector 6.0 KDE Classic (still a good distro) at the moment but will try that the next time I'm in 7.0.

Best,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 03:02:19 pm
Flawless installation. Didn't even have to pause the boot at GRUB to add rootdelay=10 which I thought was rather sweet.

One issue found so far, and that's the lack of .fdi files for policies. Wanted to set things up to disable my touchpad, but the required policy file is non-existent with this version. >.<

Will play around some more with it. So far, liking what I see. Very polished and looking GOOD!
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 03:49:59 pm
Looking at vcpufreq. powernow-K8 is still standard. K10 should be included for the newer CPUs.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 04:57:22 pm
Installed it on my Samsung N110 netbook.
Installation went without problems. Everything is working out of the box ( wireless, touchpad,..)
Using VL Quickpicks makes it very easy to install frequently used programs.
The only bug i'm having at the moment is when I try to set up screensaver. Xscreensaver is saying the deamon is not running and when clicking ok to activate, I get the following error :
Code: [Select]
The xscreensaver daemon did not start up properly.Please check your $PATH and permissions.
That's all for now.

greets

nicdm

Got the same thing on my Toshiba notebook.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 05:06:49 pm
What is debug (/var/log/debug) used for and why is it getting larger every second?

File is at 4.5MB and climbing. Here's a sample of what it's filling with.

Oct 19 21:28:37 Bodacious kernel: [12470.588424] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638759] <3>1f 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638763] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638766] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638769] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638772] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638775] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638778] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Oct 19 21:28:37 Bodacious kernel: [12470.638781] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................

Edit.. Some more clues in the debug file...

Code: [Select]
root:# cat debug | more
Oct 19 18:01:08 Bodacious kernel: [    6.242816] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 19 18:01:08 Bodacious kernel: [    6.345128] sr 6:0:0:0: Attached scsi CD-ROM sr0
Oct 19 18:01:08 Bodacious kernel: [    8.207581] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
Oct 19 18:01:08 Bodacious kernel: [   13.684745] sky2 0000:04:00.0: setting latency timer to 64
Oct 19 18:01:08 Bodacious kernel: [   13.684892] sky2 0000:04:00.0: irq 44 for MSI/MSI-X
Oct 19 18:01:08 Bodacious kernel: [   14.180411] ACPI: acpi_idle registered with cpuidle
Oct 19 18:01:08 Bodacious kernel: [   14.329882] Registered led device: mmc0::
Oct 19 18:01:08 Bodacious kernel: [   14.726290] ath5k 0000:02:00.0: setting latency timer to 64
Oct 19 18:01:08 Bodacious kernel: [   14.804906] HDA Intel 0000:01:05.2: irq 45 for MSI/MSI-X
Oct 19 18:01:08 Bodacious kernel: [   14.868788] checking generic (f0000000 1000000) vs hw (f0000000 8000000)
Oct 19 18:01:08 Bodacious kernel: [   15.226898] ath: EEPROM regdomain: 0x65
Oct 19 18:01:08 Bodacious kernel: [   15.226901] ath: EEPROM indicates we should expect a direct regpair map
Oct 19 18:01:08 Bodacious kernel: [   15.226906] ath: Country alpha2 being used: 00
Oct 19 18:01:08 Bodacious kernel: [   15.226908] ath: Regpair used: 0x65
Oct 19 18:01:08 Bodacious kernel: [   15.227055] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Oct 19 18:01:08 Bodacious kernel: [   15.500635] <3>1f 07 07 07 07 07 0f 07 07 07 07 07 07 07 0f 07  ............
....
Oct 19 18:01:08 Bodacious kernel: [   15.500638] <3>07 07 07 0f 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:08 Bodacious kernel: [   15.500641] <3>07 07 07 07 07 07 07 07 0f 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:08 Bodacious kernel: [   15.500643] <3>07 07 07 07 07 0f 07 07 07 07 07 07 07 0f 07 07  ............

Code: [Select]
Oct 19 18:01:20 Bodacious dhcpcd[2722]: eth0: using hwaddr 00:23:8b:7d:be:20
Oct 19 18:01:20 Bodacious dhcpcd[2722]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
Oct 19 18:01:20 Bodacious dhcpcd[2722]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Oct 19 18:01:21 Bodacious dhcpcd[2722]: eth0: using hwaddr 00:23:8b:7d:be:20
Oct 19 18:01:21 Bodacious dhcpcd[2722]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Oct 19 18:01:21 Bodacious dhcpcd[2722]: eth0: sending DISCOVER (xid 0x95c17e13), next in 3.50 seconds
Oct 19 18:01:21 Bodacious dhcpcd[2722]: eth0: sending REQUEST (xid 0x95c17e13), next in 4.56 seconds
Oct 19 18:01:21 Bodacious dhcpcd[2722]: eth0: sending ARP probe (1 of 3), next in 1.09 seconds
Oct 19 18:01:22 Bodacious dhcpcd[2722]: eth0: sending ARP probe (2 of 3), next in 1.15 seconds
Oct 19 18:01:23 Bodacious kernel: [   36.759689] <3>1f 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:23 Bodacious kernel: [   36.759692] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:23 Bodacious kernel: [   36.759696] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....

Code: [Select]
Oct 19 18:01:23 Bodacious dhcpcd[2722]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
Oct 19 18:01:25 Bodacious dhcpcd[2722]: eth0: adding IP address 192.168.1.16/24
Oct 19 18:01:25 Bodacious dhcpcd[2722]: eth0: adding route to 192.168.1.0/24
Oct 19 18:01:25 Bodacious dhcpcd[2722]: eth0: adding default route via 192.168.1.1
Oct 19 18:01:25 Bodacious dhcpcd[2722]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Oct 19 18:01:25 Bodacious dhcpcd[2722]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Oct 19 18:01:25 Bodacious dhcpcd[2722]: forking to background
Oct 19 18:01:25 Bodacious dhcpcd[2916]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
Oct 19 18:01:27 Bodacious dhcpcd[2916]: eth0: sending ARP announce (2 of 2)
Oct 19 18:01:33 Bodacious kernel: [   47.146786] <3>1f 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:33 Bodacious kernel: [   47.146789] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Oct 19 18:01:33 Bodacious kernel: [   47.146792] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ............
....
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 05:31:36 pm
Imported my songs from another drive into Exaile. It plays one song then locks up. Will investigate further and see if there are any reports logged.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 19, 2011, 06:10:01 pm
Also getting a TON of these in syslog.

Oct 19 21:22:59 Bodacious kernel: [12132.719022] Raw EDID:
Oct 19 21:22:59 Bodacious kernel: [12132.719055]
Oct 19 21:22:59 Bodacious kernel: [12132.719060] radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid.
Oct 19 21:22:59 Bodacious kernel: [12132.719064] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID

Did a bit of a search on the Interwebz and it seems to be a common problem. The syslog file is already at 1.5MB and climbing.

Edit - Found a possible fix here:

http://ubuntuforums.org/showthread.php?t=1607778

OP in that thread is using the same model notebook that I use.

Edit 2 - I don't think installing the fglrx driver will work as this is a pretty old card that isn't supported any longer. The driver works up to xorg 7.4, and I think we're way beyond that now, correct?

Edit 3 - Yeah. Got this error when I tried to install the driver.

Quote
which: no XFree86 in (/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/X11/bin:/usr/local/games:/usr/games:/usr/lib/java/bin:/opt/kde3/lib/qt3/bin:/opt/kde3/bin:/usr/lib/qt/bin:/usr/local/sbin:/usr/sbin:/sbin)

Error: ./default_policy.sh does not support version
default:v2:i686:lib::none:3.0.4; make sure that the version is being
correctly set by --iscurrentdistro

Removing temporary directory: fglrx-install.JGtHtU

**cry**

More info:

Code: [Select]

root:# lspci -v
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64
Kernel modules: ati-agp

00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 00009000-00009fff
Memory behind bridge: f8000000-f81fffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f7ffffff
Capabilities: [44] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [b0] Subsystem: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
Kernel modules: shpchp

00:04.0 PCI bridge: ATI Technologies Inc Device 7914 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: f8200000-f82fffff
Prefetchable memory behind bridge: 00000000f9200000-00000000f93fffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Subsystem: Toshiba America Info Systems Device ff50
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Virtual Channel
Kernel driver in use: pcieport
Kernel modules: shpchp

00:05.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: f8e00000-f8ffffff
Prefetchable memory behind bridge: 00000000f9000000-00000000f91fffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Subsystem: Toshiba America Info Systems Device ff50
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Virtual Channel
Kernel driver in use: pcieport
Kernel modules: shpchp

00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: f8300000-f83fffff
Prefetchable memory behind bridge: 00000000f8c00000-00000000f8dfffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Subsystem: Toshiba America Info Systems Device ff50
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Virtual Channel
Kernel driver in use: pcieport
Kernel modules: shpchp

00:07.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 3) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=06, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: f8800000-f89fffff
Prefetchable memory behind bridge: 00000000f8a00000-00000000f8bfffff
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [b0] Subsystem: Toshiba America Info Systems Device ff50
Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
Capabilities: [100] Virtual Channel
Kernel driver in use: pcieport
Kernel modules: shpchp

00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 22
I/O ports at 8440 [size=8]
I/O ports at 8434 [size=4]
I/O ports at 8438 [size=8]
I/O ports at 8430 [size=4]
I/O ports at 8400 [size=16]
Memory at f8709000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [60] Power Management version 2
Kernel driver in use: ahci

00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
Memory at f8504000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at f8505000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
Memory at f8506000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
Memory at f8507000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
Memory at f8508000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19
Memory at f8709400 (32-bit, non-prefetchable) [size=256]
Capabilities: [c0] Power Management version 2
Capabilities: [e4] Debug port: BAR=1 offset=00e0
Kernel driver in use: ehci_hcd

00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: 66MHz, medium devsel
I/O ports at 8410 [size=16]
Capabilities: [b0] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: piix4_smbus
Kernel modules: i2c-piix4, sp5100_tco

00:14.1 IDE interface: ATI Technologies Inc SB600 IDE (prog-if 8a [Master SecP PriP])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 8420 [size=16]
Kernel driver in use: pata_atiixp

00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, slow devsel, latency 64, IRQ 16
Memory at f8500000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, 66MHz, medium devsel, latency 0

00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, medium devsel, latency 64
Bus: primary=00, secondary=09, subordinate=09, sec-latency=64
Memory behind bridge: f8400000-f84fffff

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel
Capabilities: [f0] Secure device <?>
Kernel driver in use: k8temp
Kernel modules: k8temp

01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, fast devsel, latency 64, IRQ 18
Memory at f0000000 (64-bit, prefetchable) [size=128M]
Memory at f8100000 (64-bit, non-prefetchable) [size=64K]
I/O ports at 9000 [size=256]
Memory at f8000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled]
Capabilities: [50] Power Management version 2
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit+
Kernel driver in use: radeon
Kernel modules: radeon

01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, fast devsel, latency 64, IRQ 19
Memory at f8110000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel

02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Subsystem: AMBIT Microsystem Corp. AR5007EG 802.11bg NIC
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f8200000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [60] Express Legacy Endpoint, MSI 00
Capabilities: [90] MSI-X: Enable- Count=1 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Kernel driver in use: ath5k
Kernel modules: ath5k

04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040T PCI-E Fast Ethernet Controller (rev 12)
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f8300000 (64-bit, non-prefetchable) [size=16K]
I/O ports at a000 [size=256]
Capabilities: [48] Power Management version 3
Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [c0] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [130] Device Serial Number 20-be-7d-ff-ff-8b-23-00
Kernel driver in use: sky2
Kernel modules: sky2

09:01.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, stepping, medium devsel, latency 64, IRQ 5
Memory at f8400000 (32-bit, non-prefetchable) [disabled] [size=4K]
Memory at f8402000 (32-bit, non-prefetchable) [disabled] [size=2K]
Capabilities: [60] Power Management version 2

09:01.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02) (prog-if 01)
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: bus master, slow devsel, latency 64, IRQ 20
Memory at f8402800 (32-bit, non-prefetchable) [size=256]
Capabilities: [a0] Power Management version 2
Kernel driver in use: sdhci-pci
Kernel modules: sdhci-pci

09:01.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
Subsystem: Toshiba America Info Systems Satellite P305D-S8995E
Flags: slow devsel, IRQ 5
Memory at f8401000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [a0] Power Management version 2
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 20, 2011, 07:12:57 am
Here's the message log.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 20, 2011, 08:14:59 am
Added "nomodeset" to the boot options in grub. Seems to have killed the debug and messages spam. Not sure if it's killed anything as a result. Will test things out to double check.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 20, 2011, 11:32:33 am
Installed Banshee and still run into the same problem. Queue up an album, first song plays, and then the player locks up. Nothing in the logs, either.  ???

Edit - DeaDBeeF works perfectly.

Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: cry_baby on October 20, 2011, 04:48:37 pm
Had the same problems with music players in VL 7.0... I'll try with daedbeef now.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Joe1962 on October 20, 2011, 05:24:50 pm
Looking at vcpufreq. powernow-K8 is still standard. K10 should be included for the newer CPUs.

I had a look at the kernel 3.0.4 config and you can only build modules for powernow-K6, K7 and K8.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on October 20, 2011, 11:44:35 pm
Bonjour!

Now running skype 2.2.0.35 on vl7stdrc34, mic sound still quite choppy not very clear, while i can hear the recipient voice very clearly.
any code or command to fix up sound quality and choppy mic?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on October 21, 2011, 06:52:51 am
I had a look at the kernel 3.0.4 config and you can only build modules for powernow-K6, K7 and K8.

Hmmmm. I'm still getting the following during bootup.

Quote
[   20.236318] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141

Perhaps I misunderstood my earlier searches about that error and what the fix was. I'll do some more digging. :)
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 21, 2011, 08:51:45 am
I installed the new package today. Still isn't happening I'm afraid;

Check your ~/.bash_profile for anything like "setxkbmap". Also make sure your ~/.Xmodmap file is empty.

I discovered just today that my .bash_profile had a line put in it by the installer that was preventing keyboard setting from working as expected.

I tried that, and unfortunately with the same result, i.e. I got the US keyboard once again despite the fact there wasn't any such line in my bash_profile file and the ~/.Xmodmap file was indeed empty.

The only thing which does work is typing setxkbmap gb in a terminal, but I don't want to have to do this every time I boot up. Is there a way of automating the process?

Thanks in advance,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on October 21, 2011, 06:40:06 pm
I tried that, and unfortunately with the same result, i.e. I got the US keyboard once again despite the fact there wasn't any such line in my bash_profile file and the ~/.Xmodmap file was indeed empty.

The only thing which does work is typing setxkbmap gb in a terminal, but I don't want to have to do this every time I boot up. Is there a way of automating the process?

Thanks in advance,

CP .

Try as launcher on the panel or if you are using fluxbox in the startup.



Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: nightflier on October 23, 2011, 10:22:34 am
May want to try ~/.bashrc and/or ~/.xinitrc
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 24, 2011, 05:17:41 am
Thanks for the suggestions, I'll try these when I'm next in Vector.

Cheers,

CP .
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 24, 2011, 01:25:24 pm
Colonel Panic,
XFCE includes a keyboard configurator in the control panel. This can be used to graphically select the keyboard layout on a per-user basis.

Have you tried creating a new user account to see if the vlkbdset changes properly reflect there? I would recommend opening vasm up again and making sure that your keyboard selection is still "remembered" in vasm, then creating a new user account from vasm. Login to xfce as that new user and see if the keyboard settings are in effect.

NOTE, unlike commandline, the Xorg keyboard layout is called "gb". However the vasm selection dialog displays it as "uk" for familiarity and silently handles the name change for Xorg in the background.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 26, 2011, 03:46:45 pm
Thanks for the suggestion. Changing the keyboard to the UK one from the XCFCE control panel does bring about the desired change but I'll probably have to wait until the weekend to have the time to experiment with user accounts etc.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: solex on October 26, 2011, 05:09:53 pm
Will this version be update-able through gslapt and future fixes and updates in the 7 series?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: sledgehammer on October 26, 2011, 10:06:38 pm
Vincent2 said
Quote
Now running skype 2.2.0.35 on vl7stdrc34, mic sound still quite choppy not very clear, while i can hear the recipient voice very clearly.
any code or command to fix up sound quality and choppy mic?

I haven't moved to RC3.4 (sorry, but time requires that I wait for VL 7 and my RC version of VL7 works quite well).  However on Google Call (gmail), google voice, twinkle, linphone and ekiga, I get poor sound about half the time.   Usually I can hear better than the callee.  Until I saw your post, I assumed the problem was with either my internet speed or with diamondcardus.  I would like to reduce reliance on my landlines.  Does anyone think it (poor voice quality) might be an operating system problem?

John
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on October 27, 2011, 04:06:53 am
Quote
Quote
Now running skype 2.2.0.35 on vl7stdrc34, mic sound still quite choppy not very clear, while i can hear the recipient voice very clearly.
any code or command to fix up sound quality and choppy mic?

I haven't moved to RC3.4 (sorry, but time requires that I wait for VL 7 and my RC version of VL7 works quite well).  However on Google Call (gmail), google voice, twinkle, linphone and ekiga, I get poor sound about half the time.   Usually I can hear better than the callee.  Until I saw your post, I assumed the problem was with either my internet speed or with diamondcardus.  I would like to reduce reliance on my landlines.  Does anyone think it (poor voice quality) might be an operating system problem?

Bonjour!
with same laptop Booting to Mandriva , skype voice quality 's always good even on some occasion when internet speed's low at peak hours of the day.
booting into Knoppix , sound qulity remains poor with skype.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 27, 2011, 09:59:07 am
Colonel Panic,
XFCE includes a keyboard configurator in the control panel. This can be used to graphically select the keyboard layout on a per-user basis.

Have you tried creating a new user account to see if the vlkbdset changes properly reflect there? I would recommend opening vasm up again and making sure that your keyboard selection is still "remembered" in vasm, then creating a new user account from vasm. Login to xfce as that new user and see if the keyboard settings are in effect.

NOTE, unlike commandline, the Xorg keyboard layout is called "gb". However the vasm selection dialog displays it as "uk" for familiarity and silently handles the name change for Xorg in the background.

Hi. A brief update; I did create a new user account and carry out the tests you suggest, and the answer, unfortunately, is no - it doesn't transfer the changes I make in my root account to a new user account. I couldn't get it to recognise vlkbdset from the new user account either.

I was however able to change the keyboard from the XFCE system menu, and the changes were preserved when I next booted Vector up and logged in as root.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Colonel Panic on October 27, 2011, 10:01:48 am

Sorry, but I'm bailing from this distro testing cycle.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 27, 2011, 10:11:40 pm
If a wireless pcmcia card is not present at bootup time, wicd does not detect the hotplug. If you hotplug a pcmcia wifi card after bootup, then wicd settings must manually be configured under General Settings and in the Wireless Interface field. Once this field is set to wlan0, wicd starts functioning properly for the hotplugged card.

I wonder if this also the case for inserting a USB wifi or ethernet device after the computer is booted up...
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on October 27, 2011, 10:21:08 pm
Kdenlive listed in vlQwikPicks won't install due to dependencies. It needs deps from the testing repo which of course is not enabled by default.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: sledgehammer on October 28, 2011, 12:14:53 am
I wrote: "... I get poor sound about half the time. ..."  Today was good example.  Twinkle via Diamondcard was fussy all day, requiring me to use landline, but I had to work tonight and Twinkle via Diamondcard worked perfectly for hours tonight. 
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: scififry on October 28, 2011, 09:43:32 am
Installed on ThinkPad R40 last night, installation only took about 15 minutes and now I'm posting from somewhere else with it  ;D

Keyboard setting through the XFCE-Keyboard set up works, setting the TUI keyboard works; however setting the keyboard used at graphical login (the X keyboard) doesn't work.
Playing mp3s (I downloaded for fun to test it using ClipGrab) in Exaile works.

EDIT: Suspend doesn't work, and Thunar is bugging around; it already did in RC2.1 .
EDIT2: Thunar works now absolutely flawless. Mayhaps it has something to do with this startup check which was noted here some time ago.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: |nic| on October 29, 2011, 01:41:28 pm
suspend doesn't work for me either...Is there a way to enable this?

greets
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 01, 2011, 10:11:52 am
The install (on /dev/sda1) went smoothly until the very end.  It did not want to install LILO, so I installed GRUB.  (Both to MBR) Also, it did not seem to detect previous users in the home directory.  When I rebooted to finish the configuration, GRUB seemed to work, but after UDEV loaded the screen turned all pixelated almost like in the days when a bad xorg.conf file would burn up your monitor.  Trying to boot to tui resulted in the same thing.  My attempts to boot to the previously installed system (VL 6.0 SOHO) on /dev/sda2 resulted in a login screen but no mouse or keyboard.  (Very weird!).  Attempting to reinstall LILO instead seemed to bork everything and all devices seemed to show that the kernels were not valid ELF files.

Any wisdom on restoring a MBR?  I would prefer to use LILO since I'm used to it, but I know everyone else seems to be moving towards GRUB.  I have attempted to use the install disk to boot, and although I don't get the ELF errors, I do get the same original problems cited above (pixelation on one count and no mouse/keyboard on another).  

[Update:  Did a reinstall, except I tried installing GRUB first instead of LILO.  This seemed to work.  I didn't get a pixelated screen and the boot process proceeded.  I got to vlconf and managed to get everything set up.  In order to get the cairo-dock working, I had to copy settings from the root directory into my home directory after deleting the original config files.  I wasn't prompted to use a clean config as I have been in the past.  I have not yet tried to get into my prior install of VLSOHO-6.0, but the release candidate seems to be working just fine at this point now that it's installed.  Thanks for all the work!]
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 03, 2011, 11:14:13 am
One other thing... In VL6.0, I never had any printer issues, especially with my HP PSC 2110.  In fact, I seem to recall it being discovered by HAL automatically without me having to configure CUPS except for sharing.  With the upgrade to 7.0, the printer is not found automatically, and I needed to use hp-setup (as root) to get it installed.  However, it would not print test pages.  All printing seemed to pause after throwing an error: [Paused - "/usr/lib/cups/backend/hp failed" ].  Resuming the printer, restarting CUPS, and cursing colorfully had no effect.  Interestingly CUPS can't find the printer on USB when doing a search.  I know that ideally, it should be run via hplip and hp-setup, but in the past, it would function as a printer without hp-setup. 

So... is this a known issue with either cups-1.4.6 or hplip?  Should I recompile hplip or cups, or am I missing some obvious config option?

Thanks!
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 03, 2011, 11:21:31 am

Edit 2 - I don't think installing the fglrx driver will work as this is a pretty old card that isn't supported any longer. The driver works up to xorg 7.4, and I think we're way beyond that now, correct?

Edit 3 - Yeah. Got this error when I tried to install the driver.

Quote
which: no XFree86 in (/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/X11/bin:/usr/local/games:/usr/games:/usr/lib/java/bin:/opt/kde3/lib/qt3/bin:/opt/kde3/bin:/usr/lib/qt/bin:/usr/local/sbin:/usr/sbin:/sbin)

Error: ./default_policy.sh does not support version
default:v2:i686:lib::none:3.0.4; make sure that the version is being
correctly set by --iscurrentdistro

Removing temporary directory: fglrx-install.JGtHtU

**cry**


My desktop has a Radeon HD 2400 card which needed a proper fglrx install because I needed the split screen/video out capability afforded by the proprietary driver.  I tried using ati-driver-installer-10-7 which I had in my downloads cache and got the same error.  I had to download the latest/greatest from AMD/ATI and compile to get it to work.  Anyhow, I think you are out of luck if your card is older.  Ahhh.... progress!
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: retired1af on November 03, 2011, 03:30:57 pm
Yeah. The notebook has an x1250 in it.

Looking to snag another contract so I can pay for a new notebook. **sigh**
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on November 04, 2011, 12:44:57 am
Quote
So... is this a known issue with either cups-1.4.6 or hplip?  Should I recompile hplip or cups, or am I missing some obvious config option?
Niiler did you try system-config-printer its the print option in menu under system heading or you can run from terminal system-config-printer see if you have any better luck. Let me know to see if I still need to play with printing sub system some............... ???

Cheers,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: roarde on November 04, 2011, 11:15:56 am
Elinks can't read its own homepage. If it's downloaded to local disk by ff or wget, elinks'll display it; just can't retrieve-and-display. There are many other pages like this, but I figure this one's the most embarrassing.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 04, 2011, 09:25:38 pm
Quote
So... is this a known issue with either cups-1.4.6 or hplip?  Should I recompile hplip or cups, or am I missing some obvious config option?
Niiler did you try system-config-printer its the print option in menu under system heading or you can run from terminal system-config-printer see if you have any better luck. Let me know to see if I still need to play with printing sub system some............... ???

Cheers,
Vec
Hi Vec,

I've been doing some research on this (still no joy) and have found answers ranging from

1) starting avahidaemon before starting cupsd (starting with cups 1.4)
2) blacklisting usblp starting with cups 1.3
3) clearing out /var/spool/cups when upgrading
4) using a new /etc/cups/cupsd.conf file when upgrading.   

I have used hp-setup/hp-toolbox to clean the print heads successfully.  I can likewise do this using system-config-printer and the cups web interface. 

So the printer is detected and installable, and I can even check the ink levels, but I just can't print to the darn thing!

I'll keep plugging away this weekend.  With luck, my printer will change back from a paper-weight.

Thanks,
Tim N.
(P.S.  On all other fronts, VL7.0 sparkles.  Very nice work!)
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Scott271 on November 06, 2011, 10:16:38 am
Howdy all,

Giving this a try on a Toshiba laptop that's already running Slackware 13.37. Using the graphic installer, when I get to the format step and try to choose "Other" to recognize the Slack install the screen goes completely gray. The only thing I can do is right click and choose to reboot. Using the text installer, there is not "Other" option. LILO did detect it and add it to lilo.conf, but I haven't had a chance to boot into it yet as I'm playing around with this.

I'm also having some touchpad issues with regards to scrolling.

Scott
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 06, 2011, 10:46:18 am
Quote
So... is this a known issue with either cups-1.4.6 or hplip?  Should I recompile hplip or cups, or am I missing some obvious config option?
Niiler did you try system-config-printer its the print option in menu under system heading or you can run from terminal system-config-printer see if you have any better luck. Let me know to see if I still need to play with printing sub system some............... ???

Cheers,
Vec
Hi Vec,

I've been doing some research on this (still no joy) and have found answers ranging from

1) starting avahidaemon before starting cupsd (starting with cups 1.4)
2) blacklisting usblp starting with cups 1.3
3) clearing out /var/spool/cups when upgrading
4) using a new /etc/cups/cupsd.conf file when upgrading.    

I have used hp-setup/hp-toolbox to clean the print heads successfully.  I can likewise do this using system-config-printer and the cups web interface.  

So the printer is detected and installable, and I can even check the ink levels, but I just can't print to the darn thing!

I'll keep plugging away this weekend.  With luck, my printer will change back from a paper-weight.

Thanks,
Tim N.
(P.S.  On all other fronts, VL7.0 sparkles.  Very nice work!)


This HP printer issue is bugging me too.  I can set-up and print as cups only just fine, even can set up scan with a little tinkering, but cups quality of print is not satisfactory for pictures so I would like to us hplip.  However, as mentioned above any attempt to use hplip fails.


Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: roarde on November 06, 2011, 10:05:51 pm
There's no 'whois' command.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 07, 2011, 04:09:25 am
[
This HP printer issue is bugging me too.  I can set-up and print as cups only just fine, even can set up scan with a little tinkering, but cups quality of print is not satisfactory for pictures so I would like to us hplip.  However, as mentioned above any attempt to use hplip fails.

Made this vid to show...
http://www.youtube.com/watch?v=r4EHh5EDPN8 (http://www.youtube.com/watch?v=r4EHh5EDPN8)


Hi stretchedthin, your screencast demonstrates EXACTLY what I have been encountering only I never got things to print initially.  I have even compiled hplip-3.10.11 with vlpackager using several different config options (it looks like hpijs is completely deprecated at this point unless you use some VERY arcane config options).  I have also recompiled cups (1.4.6 and 1.5.0) using vlpackager and using slackbuild scripts.  Vlpackager doesn't work on this nor does src2pkg or a more recent version of checkinstall.  The first two create a mostly empty package after compiling most everything indicating a nonstandard 'make install' command in cups.  The last gets everything, but seems to point to device nodes instead of file names.  Very weird.  The slackbuild scripts DO work, and give a running version of cups which passes all tests.  I would test it with another printer, only I've just donated a lot of my older hardware. 

In any case, with apparently working packages of both my creation as well as the originals, I am unable to print anything using HPLIP or cups in general although all the functionality but the printing seems to be there. 

Since you were originally able to get your printer working, it gives me hope that the issue is entirely with hplip.  I do wonder if hplip is fully compatible with the new linux kernel, but I haven't followed that rabbit down the hole yet.  At this point, so long as I can get the printer working, even if the color isn't so good and the output looks like dot-matrix, I'll be happy.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: nightflier on November 07, 2011, 04:10:06 am
On two different machines, valsaconf does not find the sound card (Intel HDA). However, the sound mixer sees it and sound works.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 07, 2011, 01:16:28 pm
@niiler

Not sure how much you have changed on your system, but try the following.

as root delete the following files... (use the wildcard to get rid of .new or .default ones as well.

/etc/cups/cupsd.conf*
/etc/cups/printers.conf*
/etc/cups/snmp.conf*
/etc/hp/hplip.conf

Then (still as root)
removepkg /var/log/packages/hplip*
removepkg /var/log/packages/cups-1.*

In gslapt install cups version 1.4.6

Download this new hplip that vector made ... and install it.
http://vectorlinux.osuosl.org/vec7/hplip-3.11.7-i586-2vl70.txz (http://vectorlinux.osuosl.org/vec7/hplip-3.11.7-i586-2vl70.txz)

You should now have some new drivers for your printer
Code: [Select]
/usr/share/ppd/HP/hp-laserjet_2100_series-hpijs-pcl3.ppd.gz
/usr/share/ppd/HP/hp-laserjet_2100-ps.ppd.gz
/usr/share/ppd/HP/hp-laserjet_2100_series-ps.ppd.gz
/usr/share/ppd/HP/hp-laserjet_2100-hpijs.ppd.gz

as root do
lsmod | grep usblp
is you see the module then good. You need it, with this cups version.  I think it was configured to use it. Without it, it will not see usb.
If you do not see it then... (also as root)
Make sure you have not blacklisted it.  Then...
modprobe usblp

To set up the printer use "Manage Printing" in the system menu. It will start the cups interface and under the administration tab you can add a printer.
About the thrid step in you can select the ppd. You may have to play with a couple different ones for best result but for me it was the one of the ones with hpijs in the title.




Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 07, 2011, 03:33:40 pm
@niiler

Not sure how much you have changed on your system, but try the following.
...


Hi stretchedthin,

Did as directed and... first time, no go.  I unplugged and replugged the printer to see if udev would find it, but this didn't seem to help.  I then repeated the process, this time also deleting all files in /etc/cups/ppd/.  On this attempt, the printer was listed as USB rather than via hplip resulting in a final setup like this:

Description:   HP PSC 2100 Series
Location:   Local Printer
Driver:   HP PSC 2100 Series hpijs, 3.11.7 (color, 2-sided printing)
Connection:   usb://HP/PSC%202100%20Series?serial=MY35KF555F0F

The printer test page came out fine.  Now on to ensuring that I can scan without breaking printing!    Thanks folks!

[update]
Scanning works fine.  I have not messed with the hplip stuff at all, and xsane seemed to just find the scanner:

hpaio:/usb/PSC_2100_Series?serial=MY35KF555F0F

Just out of curiousity, do we know where the printing was going wrong? 
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Scott271 on November 07, 2011, 05:29:29 pm
So..... I can't get my laptop touchpad to scroll. I've edited xorg.conf like so:

Code: [Select]
Section "InputDevice"
 Identifier    "Synaptics Touchpad"
 Driver        "synaptics"
 Option        "SendCoreEvents"    "true"
 Option        "Device"            "/dev/psaux"
 Option        "Protocol"          "auto-dev"
 Option        "SHMconfig"         "true"
 Option        "HorizScrollDelta"  "1"
 Option        "VertEdgeScroll"  "1"
 Option        "HorizEdgeScroll"  "1"
 Option        "TapButton1"  "1"
EndSection

am I missing something? I have no vert or horiz scroll, or double-tap to grab a window. Any/all help is appreciated.

TIA,
Scott
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 07, 2011, 07:17:16 pm
@niiler
Quote
Just out of curiousity, do we know where the printing was going wrong? 

Couple areas.  First and formost was hplip selection of ppd's in the default package.  It was minimal at best.  Other printer users, canon, epson, etc would not be effected by this but hp users where.

Second is the hplip application itself.  I've tested out a number of distro's other than VL that have simply scrapped hp-toolkit and hp-setup executables and the .desktop file and notifier and only make use of the ppd's that hplip provide.

I'm thinking that there must be some issues with it for them to have taken that step.  However, it would be a nice issue to solve as ink levels, aligning, and cleaning are some things hp-toolbox can do that cups can not.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 08, 2011, 11:20:27 am
@niiler, @rxMokka, @oMasta
or any hp printer user.

Would like help testing a fix.  There is a new hplip-3.11.10-i586-5vl70 in the gslapt repositories.

Remove whatever printers you have set-up already.

Remove the old and install the new.

Then either reboot or unplug/plug you printer.

This is only a hplip rebuild so if you have made wierd changes to cups along the way and it is not working this will not help.

*What this is...
This build contains over 870 ppd's for hp printers so everyone should be covered, except perhaps an unlucky few.
There are no duplicates of hpijs, or cups ppd's so config-system-printing should get it right the first time everytime.
There is no gui application. I scrapped hp-toolbox, seemed to be more trouble than it was worth.
There is a fix in this build so all hp scanners should be detected now.


PS, there is a 64bit version in the repositories as well.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: sledgehammer on November 08, 2011, 08:41:33 pm
Stretchedthin: 
Quote
Would like help testing a fix.  There is a new hplip-3.11.10-i586-5vl70 in the gslapt repositories.

This printer discussion is most appreciated.  I will do my best to give it a try this weekend.  I am not yet on RC3.4 but suspect that won't matter.  I haven't been able to print on my office hp laserjet for months (since I moved from VL 6).  USB port on VL7 doesn't see it, either because of change in VL or change in CUPS.  But I can print wireless to our big and very fast Xerox copier/scanner, using the proper ppd.  Probably save a lot on ink, too, as I print a lot.

That (printing to Xerox) is cool.  Might not have tried it but for the trouble, so I guess there is a silver lining in every cloud.

John
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 12, 2011, 07:54:41 pm
@niiler, @rxMokka, @oMasta
or any hp printer user.

Would like help testing a fix.  There is a new hplip-3.11.10-i586-5vl70 in the gslapt repositories.

Right... I'll try it this weekend if I can get my wife off the computer.  :-P
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: sledgehammer on November 12, 2011, 08:21:35 pm
Stretchedthin,

I followed the instructions in your November 7 1:16 pm email (above) and it installed fine.  I then removed Vector's hplip 3.11.7 and installed hplip 3.11.10 from the repository and got the error "hplip: Depends: avahi >= 0.6.30."    Most likely this is because I haven't updated to the latest VL 7 beta.  Anyway, my son has the car so I can't try it now on my office hp.  But I hope to tomorrow.  I have reinstalled hhplip 3.11.7.   I bet it works.

John
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: niiler on November 13, 2011, 12:47:18 pm
@niiler, @rxMokka, @oMasta
or any hp printer user.

Would like help testing a fix.  There is a new hplip-3.11.10-i586-5vl70 in the gslapt repositories.


Hey stretchedthin,

It works like a charm.  Everything's good on this end of things.  Thanks for the extra effort!

Cheers,
Tim  N.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 13, 2011, 01:55:48 pm


Hey stretchedthin,

It works like a charm.  Everything's good on this end of things.  Thanks for the extra effort!

Cheers,
Tim  N.

Awesome, thanks for testing.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on November 13, 2011, 02:16:05 pm
@niiler, @rxMokka, @oMasta
or any hp printer user.

Would like help testing a fix.  There is a new hplip-3.11.10-i586-5vl70 in the gslapt repositories.

...

PS, there is a 64bit version in the repositories as well.

Confirmed good for HP 2575v on 64 and 32bit.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: mylesg on November 13, 2011, 11:34:04 pm
I just installed rc3.4 in virtualbox and all went well except for some weirdness with mouse control during the install. I'm using the vbox install right now and everything works quite well, including said mouse. All in all this looks to be a sweet release... I just wish I could put this on my hardware   :-\
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 14, 2011, 10:29:31 am
... I just wish I could put this on my hardware   :-\

What's the hold back, something in the distribution not working.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: sledgehammer on November 14, 2011, 11:06:39 am
stretchedthin, I tried your printing suggestion (mostly):


Quote
I followed the instructions in your November 7 1:16 pm email (above) and it installed fine.  I then removed Vector's hplip 3.11.7 and installed hplip 3.11.10 from the repository and got the error "hplip: Depends: avahi >= 0.6.30."    Most likely this is because I haven't updated to the latest VL 7 beta.  ... I have reinstalled hhplip 3.11.7. 


but it didn't work, for me, using this older version of VL7 (see signature below).  The problem, since VL6, has been this:  I use a laptop (see signature below).  I have to connect to my HP Laserjet 4mplus via the usb port.  Cups doesn't see the printer.  I suppose if I knew the ppd and all that I could get past this point.  But in VL6, I didn't have to do anything other than ask cups to find a new printer and cups came up with an option to select usb.  I would select that option, and continue, which eventually brought me to a page with all sorts of printers.  I would find the hp section, scroll down to my printer and install.  I can't do that and have never been able to do it.  As I put VL7 on this new laptop some months back, I can't really say whether its a samsung problem or a cups problem or a VL problem.  I just know it doesn't see the printer.  If I had a parallel port, I am sure it would work.

But thanks much for your and Vector's efforts.

I strongly suspect that it is something different in cups that is causing my problem.

Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 14, 2011, 02:00:34 pm
@sledgehammer
as root in a terminal could you...
lsmod | grep usblp

If you don't see it listed as a module try this (also as root)...
modprobe usblp

Then go into System>>Printing and see if you still can't see your computers usb connection listed.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: roarde on November 19, 2011, 07:43:28 pm
Has the kernel version for final release been decided?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on November 19, 2011, 08:22:49 pm
Quote
Has the kernel version for final release been decided?
hope Vector can consider latest stable kernel 3.0.9 or kernel 3.1.1 for xmas /new year final release, we 're happy to test it :-\
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vector on November 19, 2011, 08:49:49 pm
Quote
Has the kernel version for final release been decided?
we are going with 3.0.8 seems stable does all thats expected.

cheers,
Vec
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: vincent2 on November 20, 2011, 07:23:12 pm
Quote
we are going with 3.0.8 seems stable does all thats expected.
i grabed rc4.3 installed on sharp mebuis laptop
-----------------------------------------
http://vectorlinux.osuosl.org/vec7/VL7.0-STD-RC4.3.iso
-----------------------------------------
rc4.3 works fine  with kernel 3.0.8 and very stable and didn't go dummy yet since saturday...
saw rc4.4 released today, what's change from rc4.3?rc4.4 in kernel3.0.9/3.1.1.? do inform us!
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: brokndodge on November 21, 2011, 06:43:17 am
During attempted install of rc 3.4, never actually got to the installer.  Boot froze at "attempting to unpack rootfs as initramfs" or something like that.  Tried several times with same result.  VL Light 6.0 currently installed on same machine. Likely my system is the culprit but figured I'd post.

my machine: AMD Sempron 2600+, 128mb ram (32 carved off for a integrated video card I can't seem to disable) 80gb ide hd, dvd burner of unknown speed, nvidia graphics.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: stretchedthin on November 21, 2011, 08:33:54 am
@brokendodge
Good to see you back.  First though is bad burn, but before you commit to reburning 3.4 I think Vector will be announcing 4.4 shortly.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: nitehawk on November 21, 2011, 03:10:53 pm
I think Vector will be announcing 4.4 shortly.
whoot! (does this mean it may be close to final?)
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on November 21, 2011, 04:08:46 pm
During attempted install of rc 3.4, never actually got to the installer.  Boot froze at "attempting to unpack rootfs as initramfs" or something like that.  Tried several times with same result.  VL Light 6.0 currently installed on same machine. Likely my system is the culprit but figured I'd post.

my machine: AMD Sempron 2600+, 128mb ram (32 carved off for a integrated video card I can't seem to disable) 80gb ide hd, dvd burner of unknown speed, nvidia graphics.

I just did some testing in VirtualBox on several ram amounts. Seems that inorder to decompress the initramfs, you will need 224MB of free ram. To use 32MB of video ram you would need 256MB of total system ram. This is most likely due to the overhead of decompressing xz/lzma.


I wonder if it is possible to exclude usage of the init.xz at the boot prompt?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: nightflier on November 21, 2011, 06:50:21 pm
On low RAM system, try using the text installer. Type "install" on first screen. This will install everything. With 128 mb of memory, you'd probably need to run fluxbox instead of xfce.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: pierce.jason on November 21, 2011, 08:48:37 pm
Running the text installer by typing "install" at the bootup prompt doesn't make any difference for me while testing in VirtualBox. The memory limit is still hit at the same size for decompressing the init image. It takes 224MB to boot to text installer, 216MB won't cut it.

Checking the isolinux/isolinux.cfg file on the cdrom, both "install" and "gui" use the same init.lz. So changing to text installer won't help any with a resource problem at this early stage in bootup.

Looks like unless the initrd has its compression changed before final, then we're looking at a bare minimum hardware requirement of 224MB ram.
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Pita on November 22, 2011, 01:03:37 am
Jumped the line to RC4.4, Sorry, but may be what I report can be corrected before the final release:
Installed on desktop PC with GUI installer up to entering root and user name/password.
Root PW was apparently not registered since when loging-in the PW was a blank.
User name and user PW was not accepted during installation which was then aborted on its own at that point. Did the lilo bid separately in another box.

When booting then into RC4.4 there was an error message that /usr/lib/liblber.* could not be found.

User name and user PW could be entered with vasm correctly as well as root PW.


Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Scott271 on November 22, 2011, 12:40:44 pm
Still not able to get my mouse to scroll - either in a browser or through desktops. I've tried tweaking xorg.conf and xorg.conf.d - no luck. Also, when I start the computer the bootsplash gets to Starting UDEV and goes to the scrolling words startup. When I do finally get logged in there is two instances of cairo-dock running.

I did an md5check so I know I have a good burn. Any thoughts?

Scott
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: hata_ph on November 22, 2011, 07:20:22 pm
The verbose bootsplash screen after UDEV is due to old bootsplash that maybe not compatible with certain video card such as intel...there is suggestion to change to plymouth but it is too late to change that.  Maybe will replace bootsplash with plymouth in VL7.x...  :-\

About the cairo-dock...how many instance of cairo-dock in your autostart folder? or did you enable save session from your xfce logout screen?
Title: Re: Vectorlinux7 RC3.4 bug reports and comments
Post by: Joe1962 on November 24, 2011, 02:26:45 pm
I had a look at the kernel 3.0.4 config and you can only build modules for powernow-K6, K7 and K8.

Hmmmm. I'm still getting the following during bootup.

Quote
[   20.236318] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141

Perhaps I misunderstood my earlier searches about that error and what the fix was. I'll do some more digging. :)

According to the help during kernel menuconfig:
Quote
CONFIG_X86_POWERNOW_K8:
This adds the CPUFreq driver for K8/K10 Opteron/Athlon64 processors.