VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 2 3 [4] 5 6 ... 10
 31 
 on: February 09, 2016, 05:04:48 am 
Started by M0E-lnx - Last post by sidoko
OK...
'install' is named 'linux' for text-mode/manual install
vasm is cut down
vxconf gives me a way to use the graphics, but the resolution stays at 1024 x 786 :-(
I try to use my correct charset (de/850) on login, y/z are changed vice versa, afterwards it works
update disables ANY input device!

Tell me what to do to give you the necessary information.

EDIT
missed one question:
Is it possible to add a preset for the clock-quickhelp?
%A, %d. %B %Y

 32 
 on: February 09, 2016, 12:34:26 am 
Started by M0E-lnx - Last post by sidoko
I just installed ALPHA 3.6, first boot was OK, but after update keyboard and mouse was disabled and I couldn't login...


EDIT
32bit, HP rp5000, P4 2,6 GHz, 1024 Mb RAM, 250 Gb HDD, onboard Intel graphics, # and checksum OK
!!graphical installer goes 'out of range' on 16:9 full HD VGA monitor!!
!!'install' leads to 'kernel-image not found'!!
!!console on 1, 2 and 4 keeps staying blank!!
!!manual install via 'noapic nogui' works fine!!

 33 
 on: February 08, 2016, 09:14:34 pm 
Started by Megamieuwsel - Last post by rbistolfi
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [    2.180221] i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
Feb  5 13:36:52 vlocity kernel: [    2.180227] i8042: If AUX port is really absent please use the 'i8042.noaux' option
Is more annoying; Why the hell does it want to shut down the AUX-port? Is that a security-thingy?

Nop, not all the vendors implement the protocol fully and the system does some checks. The kernel is just probing different things and checking the results from the device, in this case a keyboard or a mouse. You can safey ignore this if your devices are working fine.

Quote
Still no biggies, but THIS is grating me:
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [    7.004873] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [    8.024923] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [    9.044976] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   10.065006] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   11.085055] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   12.105086] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   13.125132] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   14.145179] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   15.165208] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   16.185255] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   16.205277] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
Feb  5 13:36:52 vlocity kernel: [   16.225324] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1).
Seems to be a bug in radeon that has been around for some time, check https://bugzilla.kernel.org/show_bug.cgi?id=71891
Some people reported that passing radeon.dpm=0 at boot fixes it.
 
Quote
I think this is also the cause of the Catalyst-Software for the GPU barking about the kernel-headers....

Do you have the kernel headers and kernel src packages installed? Sounds like you are trying to install software that depends on those packages.

Quote
And finally:
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [   23.594018] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM controlIs this an issue?
If so: How and what to do about it?

It is not, similar as before, this is a power management feature in some wireless devices, do you have on of those?

In my opinion, the output you are seeing comes just from using a generic kernel which is trying to support a wide range of hardware, if you dont have an specific issue related to these devices, just let it go :)

 34 
 on: February 08, 2016, 02:17:22 pm 
Started by Megamieuwsel - Last post by M0E-lnx
The important question is... Are you suffering any performance or having any kind of problems? Things not working, etc.

 35 
 on: February 08, 2016, 02:02:07 pm 
Started by Locator - Last post by nightflier
After KDE is installed, you choose it from the login manager. Look for "sessions", select KDE.

 36 
 on: February 08, 2016, 01:42:53 pm 
Started by Locator - Last post by macondo
I don't use kde, this is a shot in the dark...
Have you tried editing your .xinitrc?
Code: [Select]
exec startkde

# reboot

 37 
 on: February 08, 2016, 01:40:40 pm 
Started by Locator - Last post by nightflier
Use gslapt and install package "kde4-meta".

 38 
 on: February 08, 2016, 12:07:48 pm 
Started by Locator - Last post by Locator
Is there a way to get VectorLinux 7.0 to boot to KDE mode, and if so, how do I go about doing it?

 39 
 on: February 08, 2016, 10:32:32 am 
Started by Megamieuwsel - Last post by Megamieuwsel
System: AMD E350 Mini-ITX with 8 Gig RAM, 500 and 164 Gig HDDs (Seagate and Hitachi respectively) and a DVD-rewriter.
Everything else is on the mainboard (Gigabyte GA-E350N WIN8 M-ITX )
All in a nice, glossy package

Installed 7.1std right when I got the li'l bugger in and it runs pretty ok, but during boot I get the following.....
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [   2.117099] esas2r: driver will not be loaded because no ATTO esas2r devices were foundThrough GoogleI learned I can safely ignore this as , indeed , my system does NOT have a RAID-controller.
(Unless someone explains to me otherwise)
To get rid of it, however, I'd need to re-compile the Kernel (I think) and it's not worth that much hassle.

Now this:
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [    2.180221] i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
Feb  5 13:36:52 vlocity kernel: [    2.180227] i8042: If AUX port is really absent please use the 'i8042.noaux' option
Is more annoying; Why the hell does it want to shut down the AUX-port? Is that a security-thingy?

Still no biggies, but THIS is grating me:
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [    7.004873] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [    8.024923] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [    9.044976] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   10.065006] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   11.085055] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   12.105086] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   13.125132] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   14.145179] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   15.165208] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   16.185255] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset the VCPU!!!
Feb  5 13:36:52 vlocity kernel: [   16.205277] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
Feb  5 13:36:52 vlocity kernel: [   16.225324] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1).
The E350 has the GPU in it; does that have anything to do with it?
Unfortunately; the MB only has a PCI(NOT: PCI-e!) expansion-slot, else I'd have stuck my trusty Geforce EN8400GS Silent in it and be done with that Radeon-GPU.
I think this is also the cause of the Catalyst-Software for the GPU barking about the kernel-headers....

And finally:
Code: [Select]
Feb  5 13:36:52 vlocity kernel: [   23.594018] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM controlIs this an issue?
If so: How and what to do about it?

 40 
 on: February 08, 2016, 05:55:14 am 
Started by sidoko - Last post by sidoko
I'm afraid, I have something to loose, despite my honor as a IT-professionist... ;)
I never did things with linux but I want to learn!
How can I follow that 'procedure'? I already installed a second CQ56 with bcm4313 (14e4:4727) on VL7.2, but screen resolution is everytime out of range... :'(

Pages: 1 2 3 [4] 5 6 ... 10