M12 11.9.92
Hi Jerry,
I uploaded 11.9.92.
I fixed the CD init to use Plymouth.
Also did some minor tweaks so 32 and 64 have the same installed packages.
Best,
Warren
Hi Jerry,
I uploaded 11.9.92.
I fixed the CD init to use Plymouth.
Also did some minor tweaks so 32 and 64 have the same installed packages.
Best,
Warren
Code: Select all
root@mepis:~# inxi -Fr
System: Host: mepis Kernel: 3.9-1-mepis64 x86_64 (64 bit) Desktop: KDE 4.8.4 Distro: MEPIS 12.0 wheezy
Machine: System: HP Pavilion 061 product: PX181AV-ABA d4100y version: 0qn1211CT101LITHI00 serial: MXG52500B9 NA531
Mobo: ASUSTek model: LITHIUM version: 1.04 serial: MB-1234567890 Bios: Phoenix version: 3.07 date: 08/29/2005
CPU: Dual core Intel Pentium D CPU (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3)
Clock Speeds: 1: 2800.00 MHz 2: 2800.00 MHz
Graphics: Card: NVIDIA NV43 [GeForce 6600]
X.org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) tty size: 99x23 Advanced Data: N/A for root
Audio: Card: Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture ver: k3.9-1-mepis64
Network: Card: Intel NM10/ICH7 Family LAN Controller driver: e100
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:1.10:75
Drives: HDD Total Size: 164.0GB (3.3% used) 1: id: /dev/sda model: ST3160023AS size: 160.0GB
2: USB id: /dev/sdb model: Cruzer size: 4.0GB
Partition: ID: / size: 2.7G used: 253M (10%) fs: rootfs ID: /boot size: 3.9G used: 3.7G (97%) fs: ext4
ID: /home size: 3.9G used: 3.7G (97%) fs: ext4 ID: /usr size: 3.9G used: 3.7G (97%) fs: ext4
ID: /var size: 3.9G used: 3.7G (97%) fs: ext4
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list.d/debian.list
deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free
Active apt sources in file: /etc/apt/sources.list.d/mepis.list
deb http://mepis.mirrorcatalogs.com/packages/mepis/ mepis-12.0 main
Info: Processes: 131 Uptime: 3:26 Memory: 651.0/3018.7MB Client: Shell (bash) inxi: 1.9.12
To get the Mepis 12 plymouth splash to show up when the proprietary nvidia driver is installed, I need to add the vga=xxx cheatcode (vga=791 in my case).Jerry3904 wrote:... I installed sgfxi and an Nvidia driver.
As with 11.9.91, the new driver seems to block plymouth somehow, so I get a minimal Debian screen during boot.
I did some searching around and found that the 3.5 kernel packages are still available on the mirrorservice.org mirror: http://mirrorservice.org/sites/ftp.mepi ... n/l/linux/ They don't appear to be in the package lists though so you can't install them with apt-get or Synaptic, you would need to manually download the packages and then install them with dpkg or gdebi.rschaffter wrote:Just installed on my HP 8510p notebook. The HP suspend/resume fan bug ( related to this one... https://bugzilla.kernel.org/show_bug.cgi?id=56591 and is fixed in 3.10 ) is of course present, but to my horror the 3.5 kernel, which works, has apparently been removed from the Mepis Repository. :mad:
Code: Select all
linux-headers-3.5-1-common_3.5.2-1_amd64.deb
linux-headers-3.5-1-mepis64_3.5.2-1_amd64.deb
linux-image-3.5-1-mepis64_3.5.2-1_amd64.deb
linux-kbuild-3.5_3.5-1_amd64.deb (in the ...pool/main/l/linux-tools/ directory)
Code: Select all
linux-headers-3.5-1-common_3.5.2-1_i386.deb
linux-headers-3.5-1-mepis_3.5.2-1_i386.deb
linux-image-3.5-1-mepis_3.5.2-1_i386.deb
linux-kbuild-3.5_3.5-1_i386.deb (in the ...pool/main/l/linux-tools/ directory)
The 3.9 kernel isn't in Sid anymore, the 3.10 kernel is. I haven't checked if the 3.10 Sid kernel is installable in M12/Wheezy or not (and it's not really a good idea to mix stable (Wheezy) and sid).rschaffter wrote:...does anyone know if there is a repo with the 3.10 kernel? It was still 3.9 in Sid last I checked.
That did work, though the resulting splash is very low resolution. I had some trouble finding the correct code for my 2048x1152 monitor, but finally found a way: install hwinfo, then run as root:kmathern wrote:To get the Mepis 12 plymouth splash to show up when the proprietary nvidia driver is installed, I need to add the vga=xxx cheatcode (vga=791 in my case).Jerry3904 wrote:... I installed sgfxi and an Nvidia driver.
As with 11.9.91, the new driver seems to block plymouth somehow, so I get a minimal Debian screen during boot.
Edit the /etc/default/grub file and add the vga=xxx cheat to either the GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT line. Run update-grub afterward.
Code: Select all
hwinfo --framebuffer | grep "Mode"
Code: Select all
oot@BondDekstop:/home/jb# hwinfo --framebuffer | grep "Mode"
process 4201: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file ../../dbus/dbus-errors.c line 282.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
Model: "Build 061010.3
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Mode 0x0352: 2048x1536 (+8192), 24 bits
root@BondDekstop:/home/jb#
Oops, I did mix them up. The first number's the width, 2048 pixels in your case.Jerry3904 wrote:Left and right seemed right, but the smaller number must be the height, right? Top and bottom could have lost something in all that darkness that I would not have noticed.
Thanks for the suggestion. I tried that but no joy :(
The command below might help your proofreading, I think it displays most of the messages that come up during the install.Utopia wrote:A few more corrections for the help and tips in the installer:
Fonts in Mepis Linux: The "Font installer" is now called "Font management" in System Settings.
"When in doubt, ask for advice at mepiscommunity.org", should be more useful if changed to forum.mepiscommunity.org
Henry
Code: Select all
strings /usr/sbin/minstall | grep -e '<p><b>' -e '</span>'| sed 's|<p><b>|\n|g;s|</b><br/>|\n|g;s|</p><p>|\n|g;s|</p>|\n|g;s|<p>|\n|g;s|</b>||g' | cut -f3 -d\> | cut -f1 -d\<
This might show the "missing parts". It will also show other strings for the cli commands and python/qt4 code mingled in. With the 'grep -v' command at the end I've tried to filter out the most commonly occurring strings that make the output look like nonsense.Utopia wrote:Thanks, it's working for most parts of the text. The missing parts is where I think the errors are. They're probably added later.
Henry
Code: Select all
strings /usr/sbin/minstall | sed 's|<p><b>|\n|g;s|</b><br/>|\n|g;s|</p><p>|\n|g;s|</p>|\n|g;s|<p>|\n|g;s|</b>||g' | cut -f3 -d\> | cut -f1 -d\< | grep -v -e ^_ -e ^D[$] -e ^UWVS -e ^t[$] -e ^[[,#,@,+,\\,\(,\),\|,\&,\^,\%] -e '()'$ -e QProcess
I noticed that. With my ponderous DSL, it takes over two hours to download so I decided to pass on this one and wait for more substantive changes.Utopia wrote: This is some kind of vacation release, not much changed and it's not getting very much testing.
Henry
.This might show the "missing parts"
I'll ask, thanks.Utopia wrote:A reference to http://www.mepis.org/source, a page that doesn't exist. Does it mean the source code can't be downloaded anymore? Or has it moved?
Henry
Code: Select all
strings /usr/sbin/minstall | sed 's|<p><b>|\n|g;s|</b><br/>|\n|g;s|</p><p>|\n|g;s|</p>|\n|g;s|<p>|\n|g;s|</b>|\n|g' | grep -v -e ^D[$] -e ^UWVS -e '()'$ -e QProcess -e MeInstall -e MMain -e MInstall -e MeMain -e '/mepis/' -e '/mnt/' -e 'rm ' -e 'cp -' -e 'mv -' -e'/dev/' -e 'bin/' -e '/usr/' -e mkdir -e white-space -e ^'Step_' -e '(bool)' -e WStackPage | sed 's/<[^>]\+>//g' | grep -e ^[A-Z] -e ^[0-9] -e ^' ' | sed 's/[[:space:]]*$//' | sed 's|[.]$|.\n|;s|[?]$|?\n|;s|[\!]|\!\n|;s|source$|source\n|;s|Time$|Time\n|;s|gov/$|gov/\n|' | grep root -A999
Sort of on the same topic, the MEPIS32_12.0 (Safe Mode) boot option includes a 'xmodule=vesa' cheatcode.Utopia wrote:Without "F1 for help" at the GRUB screen, how is anyone supposed to figure out which cheatcodes can be used in M12? Couldn't find a text file either, was looking for Kernel-boot-parameters.txt or similar names. Is this something that can added to the summary for Warren?
Henry
I don't see a OSX folder with the "SimplyMEPIS Assistant.app.zip" file in a loop mounted ISO file, or on my LiveUSB key.Custom Install on Existing Partitions
MEPIS will be installed on the existing partitions you choose. If the disk isn't already partitioned appropriately, you can modify the partitions now with PartitionManager. If you modify the partitions, it is best to reboot the system before continuing with the installation. Do NOT use a Linux partioning tool if you are installing on an Apple computer boot drive. Instead you must setup your partitions and boot manager in OSX before installing MEPIS. The SimplyMEPIS Assistant is an OSX application available on the MEPIS DVD to help you prepare your OSX boot volume for MEPIS Linux.
http://forum.mepiscommunity.org/viewtop ... 29#p321229Jerry3904 wrote:Of what, exactly? Not following you here.
@rschaffter,rschaffter wrote:I found 3.10.5 in Unstable. On installation it gripes about missing firmware, but I have video and wireless, at least, and it sleeps and resumes properly.
EDIT: Thanx, kmathern. I have the 32 bit versions of those, so I'll grab the 64-bit ones...
deb http://ftp.us.debian.org/debian/ wheezy-backports main contrib non-free
No, I didn't even see it. Usually I can spot very small errors, but sometimes can't see the big ones.Not sure if Utopia has mentioned this before.
Thanx for this! I had to update GRUB2 manually when I installed it, but it works just fine. :)kmathern wrote:@rschaffter,rschaffter wrote:I found 3.10.5 in Unstable. On installation it gripes about missing firmware, but I have video and wireless, at least, and it sleeps and resumes properly.
EDIT: Thanx, kmathern. I have the 32 bit versions of those, so I'll grab the 64-bit ones...
Just noticed this message on the debian-backports-changes list, the 3.10.5 kernel has been accepted to be added to the wheezy-backports repo: http://lists.debian.org/debian-backport ... 00028.html
This is the backport repo sources.list entry (you can use a different locale than 'us')deb http://ftp.us.debian.org/debian/ wheezy-backports main contrib non-free
Yes and Mint will welcome you doing so,Jerry3904 wrote:Can't say that ever occurred to me!
KMplayer isn't installed in M11.9.92 from what I can see (I'm not running in it right now). Are you still using the Mepis 11.0 install that you upgraded?smilliken wrote:Is it possible to have KMplayer not installed as the default media player and use VLC Media player instead? Like no KMplayer on the live disk.
Just thinking out the final product and not the fact that it can be changed. I just find that KMplayer does not meet my needs and more often than not, it will not work on a lot of video/audio files, at least for me, whereas VLC does.
kmathern wrote:KMplayer isn't installed in M11.9.92 from what I can see (I'm not running in it right now). Are you still using the Mepis 11.0 install that you upgraded?smilliken wrote:Is it possible to have KMplayer not installed as the default media player and use VLC Media player instead? Like no KMplayer on the live disk.
Just thinking out the final product and not the fact that it can be changed. I just find that KMplayer does not meet my needs and more often than not, it will not work on a lot of video/audio files, at least for me, whereas VLC does.
Code: Select all
su
rmmod hid-logitech-dj
modprobe hid-logitech-dj
Just saw this and it may or may not have any bearing on what I'm dealing with.timkb4cq wrote:I've seen some threads about problems with that keyboard & debian. In a terminal, tryIt seems to be a timing problem where the driver tried to initialize the receiver before it's ready. If the above commands fix the issue you can put them in a script with an appropriate sleep command between to let the receiver settle.Code: Select all
su rmmod hid-logitech-dj modprobe hid-logitech-dj
Okay, that says I need the psmouse-elantech package, which is a tar.gz. I've downloaded and extracted it, but have no idea what to do with it.timkb4cq wrote:A little research indicates that Laptop has an Elantech touchpad. This page at Arch Linux may have the answer - it's being detected as a ps/2 mouse instead of a touchpad...
I have a simialr situation with my Acer V5-572G, except the touchpad does not work at all.uncle mark wrote:Okay, that says I need the psmouse-elantech package, which is a tar.gz. I've downloaded and extracted it, but have no idea what to do with it.timkb4cq wrote:A little research indicates that Laptop has an Elantech touchpad. This page at Arch Linux may have the answer - it's being detected as a ps/2 mouse instead of a touchpad...
Thanks for your interest, Tim, but that stuff is above my pay grade.timkb4cq wrote:I've found a newer thread on this. Fixes for some elantech touchpad issues have been accepted into the mainline 3.11 kernel. Ubuntu kernels (and headers) with the relevant patches have been built for Precise (3.2), Quantal (3.5) , Raring (3.& Saucy (3.10). Could be worth a try.
https://bugs.launchpad.net/ubuntu/+sour ... mments/100
The problem is not distro related but kernel related. I have it in Kubuntu 13.04. I tried that kernel but had the same problem. UM you just install the debs and update-grub. I also installed a 3.10 kernel and no fix.uncle mark wrote:Thanks for your interest, Tim, but that stuff is above my pay grade.timkb4cq wrote:I've found a newer thread on this. Fixes for some elantech touchpad issues have been accepted into the mainline 3.11 kernel. Ubuntu kernels (and headers) with the relevant patches have been built for Precise (3.2), Quantal (3.5) , Raring (3.& Saucy (3.10). Could be worth a try.
https://bugs.launchpad.net/ubuntu/+sour ... mments/100
Niece is getting a load of Mint KDE 15. (Mint KDE 13 LTS had the same problem.) Posting from it now. I've been impressed with it before, and did in fact use it for a new desktop build I did for a paying customer recently. Yes, I'd prefer to use MEPIS or even straight Debian, but sometimes you gotta do what you gotta do. At least with Linux we've got a lot of good choices.
I get that. All I can tell you is Wheezy and Mint 13 have the problem; Mint 15 does not. (Odd that Kub 13.04 has it, since Mint 15 is based of Ub 13.04.)richb wrote: The problem is not distro related but kernel related. I have it in Kubuntu 13.04.
(...)
EDIT: Actually probably kernel/driver/xorg or evdev related.
What kernel and xorg server is Mint 15 using? Does it have an xorg.conf file? And is there an options.conf file in etc/modeprobe.d? I was able to get basic functions (cursor movement and clicks) to work by adding an options.conf file to /etc/modprobe.d with the line "options psmouse proto=imps". It causes the clickpad to be recognized as a mouse.uncle mark wrote:I get that. All I can tell you is Wheezy and Mint 13 have the problem; Mint 15 does not. (Odd that Kub 13.04 has it, since Mint 15 is based of Ub 13.04.)richb wrote: The problem is not distro related but kernel related. I have it in Kubuntu 13.04.
(...)
EDIT: Actually probably kernel/driver/xorg or evdev related.
I checked for the file, and it is there (assuming %2520 is coding for the space) with the following content:Unable to run the command specified. The file or folder file:///home/jb/.local/share/applications/LibreOffice%25204.desktop does not exist.
Code: Select all
[Desktop Entry]
Comment=
Exec=/opt/libreoffice4.1/program/soffice
GenericName=Office suite
Icon=libreoffice4
Name=LibreOffice 4.1
NoDisplay=false
Path[$e]=
StartupNotify=true
Terminal=0
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=
I installed the kdeaccessiblity package to see it that helps, but instead of the time, I get a voice telling me that i have voice synthesis working and to read some log file.GDixon wrote:I found the problem with boot and install times with the sandisk cuzer blade 8g flash key..
Do not use unetbootin to make a bottable key.
After getting everything working and working very well indeed on this new system I popped the key in and re did it using the Mepis usb key maker and problem solved.
bootable key times are now as one would expect in both booting and installing.
Has anyone try the talking clock yet? It seems jovie still has unresolved bugs?
Lookss as tho there is a missing package that Arch has. Pacman? All I get is the game.Danum wrote:smilliken wrote:but I was trying to set up konsole and there was a post sometime a go by Brook, I think, that shows you how to make the text red when you change from normal user to su. Tried to search the forums, but I'm coming up with a blank./quote]
https://wiki.archlinux.org/index.php/Color_Bash_Prompt
Open Dolphin as root,smilliken wrote:Lookss as tho there is a missing package that Arch has. Pacman? All I get is the game.Danum wrote:smilliken wrote:but I was trying to set up konsole and there was a post sometime a go by Brook, I think, that shows you how to make the text red when you change from normal user to su. Tried to search the forums, but I'm coming up with a blank./quote]
https://wiki.archlinux.org/index.php/Color_Bash_Prompt
Code: Select all
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
I thought it was in the Wiki - might have been in the old forums - I couldn't find it either.smilliken wrote:This doesn't have anything to do with the beta, but I was trying to set up konsole and there was a post sometime a go by Brooko, I think, that shows you how to make the text red when you change from normal user to su. Tried to search the forums, but I'm coming up with a blank.
Not sure if it still works the same - I have no MEPIS install any more to test. I was waiting for 12 to show some signs of going final before trying it in vbox - but I've given up waiting. This current 'cycle' unfortunately reinforces to me the state of MEPIS. It's a pity really - he had offers of plenty of help from a lot of people when I was still around. He chose not to take advantage of them. It's no wonder so many people left, and so many others are using a different distro.2. As root navigate to /root folder and create new file .bashrc
Add following line -This makes my root text red in a konsole.Code: Select all
export PS1="\[\e[1;31m\]\u[\w]\\$ \[\e[m\] "
3. Create new file .bashrc in your own /home/yourusername directory
Add following line -This makes my text green (as normal user) in konsoleCode: Select all
export PS1="\e[1;32m\u[\w]\\$ \e[m "
I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.richb wrote:Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..
I did edit the original by adding the one line.Danum wrote:I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.richb wrote:Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..
Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,richb wrote:I did edit the original by adding the one line.Danum wrote:I do hope you have backed up the original bashrc files, because at some time the system will/may need to implement what is in it, which is why you edit the original one, not make a new one, and that applies to Kununtu and Debian.richb wrote:Just tried your console suggestion in Kubuntu and it works, so it should be distro neutral..
Code: Select all
2. As root navigate to /root folder and create new file .bashrc
3. Create new file .bashrc in your own /home/yourusername directory
Add following line -
No I did not since there was already a bashrc I felt it prudent not to overwrite it.Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,
Code: Select all
2. As root navigate to /root folder and create new file .bashrc 3. Create new file .bashrc in your own /home/yourusername directory Add following line -
I hate it when that happens.BurtHulland wrote:My 64-bit Google Earth problem is solved! The USB key Ihad used to install the OS on all 3 of my systems was failing. It did not create any errors I found except the one in GE. Then I started to wonder if it could be the problem, so I rewrote the key - and was greeted with several errors. I have now bought a new key and written M11.9.92_64 on it. When I used this to reinstall the 64bit M12 OP system, it would then run GE! (I filed the key I had been using in the circular file.)
Funny, in my home folder .bashrc in Kubuntu, I found this:richb wrote:No I did not since there was already a bashrc I felt it prudent not to overwrite it.Then you did not follow Brooko's post, because if you create a new .bashrc file it will over write the original one,
Code: Select all
2. As root navigate to /root folder and create new file .bashrc 3. Create new file .bashrc in your own /home/yourusername directory Add following line -
Code: Select all
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi
export PS1="\e[1;32m\u[\w]\\$ \e[m "
Which is a typical Mepis 12 way of doing it, (I know yours is from Kubuntu)richb wrote:What was in mine below. I only added the last line.
Uncle mark, this is the first time a key has gone bad on me. It is much easier and quicker as I see it to use a USB key (assuming I have one available) than to burn a disk. I only do that when I can't use a USB key for some reason.uncle mark wrote: I hate it when that happens.
I love it when a bootable USB is working properly, but for me anyway it's easier most of the time to burn a disk.
Why? Because I was too dumb to do any different.Danum wrote:Which is a typical Mepis 12 way of doing it, (I know yours is from Kubuntu)richb wrote:What was in mine below. I only added the last line.
what you are doing is letting the original script setup a color, and then resetting it again, Why? set it up from within the original script then it works as it should, without an extra action,
It is doing things like this that make booting from a Mepis 12 DVD as slow as it is, plus it takes more resources because the system is going round in circles before it finds out just what it should be doing.
Burt, my wife teaches photography and burns through USB keys like nobody's business...the kid's all use them to take their photos home and they get heavy use.BurtHulland wrote:Uncle mark, this is the first time a key has gone bad on me. It is much easier and quicker as I see it to use a USB key (assuming I have one available) than to burn a disk. I only do that when I can't use a USB key for some reason.uncle mark wrote: I hate it when that happens.
I love it when a bootable USB is working properly, but for me anyway it's easier most of the time to burn a disk.
That's the difference - I only use them (with one exception) for ISO files to install vaious distributions. So they don't get erased very often; that is what kills flash ROM's.pcallahan80 wrote:Burt, my wife teaches photography and burns through USB keys like nobody's business...the kid's all use them to take their photos home and they get heavy use.
richb wrote:What was in mine below. I only added the last line.
That fixed the problem. Strange though that I never had to load thisDBeckett wrote:
Sorry if this has been brought up already, but has anyone mentioned this?
http://packages.debian.org/wheezy/libwine-print
Is the beta now supported with the necessary repositories and updates?Jerry3904 wrote: M12 is a long time coming, but I am now set up with. 11.9.92 as my production system, so no waiting for me.
Warren's M12 repo, the M12 CRs, and the Debian Wheezy repos have all been up and running for some time now. See: http://www.mepis.org/docs/en/index.php? ... t_MEPIS_12joany wrote:Is the beta now supported with the necessary repositories and updates?Jerry3904 wrote: M12 is a long time coming, but I am now set up with. 11.9.92 as my production system, so no waiting for me.
JBoman wrote:Had another crash today but different than the previous and only the browser crashed not a full system lockup like before. This time I was logged in to ebay with 2 tabs open... 1st tab was "my ebay" 2nd tab was viewing search results... at one point when clicking to view an item the browser crashed me back to my desktop. ... This is starting to look like an issue with iceweasel but I want to be sure it's not drivers or kernel related or other unknown. Iceweasel is 19.0.2
You might also update the flash plugin because M11.9.92 comes with the 11.2.202.275 version, the current version is 11.2.202.310.lucky9 wrote:I'd suggest upgrading IceWeasel no matter what.
Code: Select all
su -c 'update-flashplugin-nonfree --install --verbose'
I saw your other thread (in the 64-bit section) about the Wine printing problem. Several years ago I installed the 64-bit version of SM 8.0 (upgrading from SM 6.5) and immediately ran into several problems with Wine I couldn't resolve. I quickly ditched the 64-bit version of MEPIS and installed 32-bit as my production OS. If Wine is one of your mission-critical applications, you might want to consider using 32-bit instead. I know there many proponents of 64-bit in these forums, but I've always found 32-bit to be rock solid in every aspect. The main downside is that it's slower when running heavy number-crunching applications, such as DVD authoring. But for day-to-day use, its speed is certainly adequate, and I think you'll find it has fewer software issues overall.beckwith wrote: That fixed the problem. Strange though that I never had to load this
library before. Thanks.
- - - Spoke too soon! After a few minutes using a Wine app the system
now "hangs" - dead! I have to reboot.
"glabels" comes close to what I've been using under Wine, but it doesn't
have the capabilties of even a ancient Windoze app (PDG)
- - - Spoke even much too soon! The Wine app will actually crash the
system and return to the login screen - which fails! Reboot!
Sigh!
Do you by chance have an nVidia card? I have that happen constantly on my openSUSE machine with an nVidia card, but no issues at all on my Mepis 12 machine with a Radeon card...JBoman wrote:Had another crash today but different than the previous and only the browser crashed not a full system lockup like before. This time I was logged in to ebay with 2 tabs open... 1st tab was "my ebay" 2nd tab was viewing search results... at one point when clicking to view an item the browser crashed me back to my desktop. ... This is starting to look like an issue with iceweasel but I want to be sure it's not drivers or kernel related or other unknown. Iceweasel is 19.0.2
Would be nice to have it as the rolling version, if those are the words, to be able to have the newest version available much like the beta set up. If one doesn't want to upgrade, don't. But I've been running the on update channel with no problems so far. Some are on version 25.lucky9 wrote:I'd suggest upgrading IceWeasel no matter what.
I'm doing this already. Would like to see Mepis 12 ship with it.lucky9 wrote:The version that Firefox has on their site can be set to auto-update, or inform, or not. Your choice. Look for kmathern's Firefox script. I put stuff like that on a USB FlashDrive/MemoryKey for portability.
Interesting. I wonder if the old goat has been working on UEFI compatibility all this time...lucky9 wrote:mepis-install is at .94 and mepis-system is at .96 also. So there is work going on. Plus I note that grub-efi is there.
Likely. Getting the system to boot simply and easily has been a priority for Warren.uncle mark wrote:Interesting. I wonder if the old goat has been working on UEFI compatibility all this time...lucky9 wrote:mepis-install is at .94 and mepis-system is at .96 also. So there is work going on. Plus I note that grub-efi is there.
Those aren't new:lucky9 wrote:mepis-install is at .94 and mepis-system is at .96 also. So there is work going on. Plus I note that grub-efi is there.
The large number of updates might be coming from the http://security.debian.org/ repo. I think they're planning on doing an update from Debian 7.1 -> 7.2 in the next week or two. The updates usually appear in the security repo or the wheezy-updates repo (what used to be 'volatile') before a point update.namida12 wrote:Amazing, not many updates recently, and today 100 updates... Restarted system and everything appears good on restart. Though this was significant enough to post...
JR
Code: Select all
Commit Log for Sat Sep 28 11:36:52 2013
Upgraded the following packages:
amd64-microcode (1.20120910-2) to 2.20120910-1~bpo70+1
desktop-file-utils (0.20-0.1) to 0.21-1~bpo70+1
devscripts (2.12.6) to 2.13.2~bpo70+1
file (5.11-2) to 1:5.14-2~bpo70+1
firmware-atheros (0.36+wheezy.1) to 0.39~bpo70+1
firmware-brcm80211 (0.36+wheezy.1) to 0.39~bpo70+1
firmware-intelwimax (0.36+wheezy.1) to 0.39~bpo70+1
firmware-ipw2x00 (0.36+wheezy.1) to 0.39~bpo70+1
firmware-iwlwifi (0.36+wheezy.1) to 0.39~bpo70+1
firmware-libertas (0.36+wheezy.1) to 0.39~bpo70+1
firmware-linux-nonfree (0.36+wheezy.1) to 0.39~bpo70+1
firmware-ralink (0.36+wheezy.1) to 0.39~bpo70+1
firmware-realtek (0.36+wheezy.1) to 0.39~bpo70+1
fonts-opensymbol (2:102.2+LibO4.0.3-2~bpo70+1) to 2:102.3+LibO4.1.0-5~bpo70+3
gettext (0.18.1.1-9) to 0.18.3-1~bpo7+1
gettext-base (0.18.1.1-9) to 0.18.3-1~bpo7+1
git (1:1.7.10.4-1+wheezy1) to 1:1.8.4~rc3-1~bpo70+1
git-man (1:1.7.10.4-1+wheezy1) to 1:1.8.4~rc3-1~bpo70+1
intel-microcode (1.20130222.1) to 2.20130808.1~bpo70+1
irqbalance (1.0.3-3) to 1.0.6-2~bpo70+1
libarmadillo3 (1:3.2.3+dfsg-1) to 1:3.900.2+dfsg-1~bpo70+2
libasprintf0c2 (0.18.1.1-9) to 0.18.3-1~bpo7+1
libgeoip1 (1.4.8+dfsg-3) to 1.5.0-3~bpo70+1
libgettextpo0 (0.18.1.1-9) to 0.18.3-1~bpo7+1
libgpgme11 (1.2.0-1.4) to 1.4.3-0.1~bpo70+1
libgps20 (3.6-4+deb7u1) to 3.9-3~bpo70+1
libmagic1 (5.11-2) to 1:5.14-2~bpo70+1
libsmbclient (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
libwbclient0 (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
libxapian22 (1.2.12-2) to 1.2.15-2~bpo70+1
lintian (2.5.10.4) to 2.5.19~bpo70+1
module-assistant (0.11.4) to 0.11.6~bpo70+1
openssh-client (1:6.0p1-4) to 1:6.2p2-6~bpo70+1
python-debian (0.1.21) to 0.1.21+nmu2~bpo70+1
python-twisted-bin (12.0.0-1) to 13.0.0-1~bpo70+1
python-twisted-core (12.0.0-1) to 13.0.0-1~bpo70+1
samba-common (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
smbclient (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
Installed the following packages:
gnupg-agent (2.0.19-2)
gnupg2 (2.0.19-2)
iucode-tool (1.0-1~bpo70+1)
libassuan0 (2.0.3-1)
libfile-basedir-perl (0.03-1)
libksba8 (1.2.0-2)
libtevent0 (0.9.16-1)
libtext-levenshtein-perl (0.06~01-1)
pinentry-gtk2 (0.8.1-1)
python-six (1.1.0-2)
python3 (3.2.3-6)
python3-minimal (3.2.3-6)
python3.2 (3.2.3-7)
python3.2-minimal (3.2.3-7)
t1utils (1.37-1)
Code: Select all
Commit Log for Sat Sep 28 08:10:55 2013
Upgraded the following packages:
mepis-config (11.9.94) to 11.9.96
Commit Log for Sat Sep 28 08:12:19 2013
Upgraded the following packages:
amd64-microcode (1.20120910-2) to 2.20120910-1~bpo70+1
bind9-host (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
curl (7.26.0-1+wheezy2) to 7.26.0-1+wheezy3
davfs2 (1.4.6-1.1) to 1.4.6-1.1+deb7u1
dbus (1.6.8-1) to 1.6.8-1+deb7u1
dbus-x11 (1.6.8-1) to 1.6.8-1+deb7u1
devscripts (2.12.6) to 2.13.2~bpo70+1
dnsutils (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
file (5.11-2) to 1:5.14-2~bpo70+1
firmware-atheros (0.36+wheezy.1) to 0.39~bpo70+1
firmware-brcm80211 (0.36+wheezy.1) to 0.39~bpo70+1
firmware-intelwimax (0.36+wheezy.1) to 0.39~bpo70+1
firmware-ipw2x00 (0.36+wheezy.1) to 0.39~bpo70+1
firmware-iwlwifi (0.36+wheezy.1) to 0.39~bpo70+1
firmware-libertas (0.36+wheezy.1) to 0.39~bpo70+1
firmware-linux-nonfree (0.36+wheezy.1) to 0.39~bpo70+1
firmware-ralink (0.36+wheezy.1) to 0.39~bpo70+1
firmware-realtek (0.36+wheezy.1) to 0.39~bpo70+1
fonts-opensymbol (2:102.2+LibO4.0.3-2~bpo70+1) to 2:102.3+LibO4.1.0-5~bpo70+3
gettext (0.18.1.1-9) to 0.18.3-1~bpo7+1
gettext-base (0.18.1.1-9) to 0.18.3-1~bpo7+1
gnupg (1.4.12-7) to 1.4.12-7+deb7u1
gpgv (1.4.12-7) to 1.4.12-7+deb7u1
icedtea-6-plugin (1.3.2-1) to 1.4-3~deb7u1
icedtea-netx (1.3.2-1) to 1.4-3~deb7u1
icedtea-netx-common (1.3.2-1) to 1.4-3~deb7u1
icedtea-plugin (1.3.2-1) to 1.4-3~deb7u1
imagemagick (8:6.7.7.10-5) to 8:6.7.7.10-5+deb7u2
imagemagick-common (8:6.7.7.10-5) to 8:6.7.7.10-5+deb7u2
intel-microcode (1.20130222.1) to 2.20130808.1~bpo70+1
irqbalance (1.0.3-3) to 1.0.6-2~bpo70+1
libasprintf0c2 (0.18.1.1-9) to 0.18.3-1~bpo7+1
libbind9-80 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libcurl3 (7.26.0-1+wheezy2) to 7.26.0-1+wheezy3
libcurl3-gnutls (7.26.0-1+wheezy2) to 7.26.0-1+wheezy3
libdbus-1-3 (1.6.8-1) to 1.6.8-1+deb7u1
libdns88 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libgcrypt11 (1.5.0-5) to 1.5.0-5+deb7u1
libgeoip1 (1.4.8+dfsg-3) to 1.5.0-3~bpo70+1
libgettextpo0 (0.18.1.1-9) to 0.18.3-1~bpo7+1
libgl1-mesa-dri (8.0.5-4+deb7u1) to 8.0.5-4+deb7u2
libgl1-mesa-glx (8.0.5-4+deb7u1) to 8.0.5-4+deb7u2
libglapi-mesa (8.0.5-4+deb7u1) to 8.0.5-4+deb7u2
libglu1-mesa (8.0.5-4+deb7u1) to 8.0.5-4+deb7u2
libgpgme11 (1.2.0-1.4) to 1.4.3-0.1~bpo70+1
libgps20 (3.6-4+deb7u1) to 3.9-3~bpo70+1
libgssapi-krb5-2 (1.10.1+dfsg-5) to 1.10.1+dfsg-5+deb7u1
libisc84 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libisccc80 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libisccfg82 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libk5crypto3 (1.10.1+dfsg-5) to 1.10.1+dfsg-5+deb7u1
libkrb5-3 (1.10.1+dfsg-5) to 1.10.1+dfsg-5+deb7u1
libkrb5support0 (1.10.1+dfsg-5) to 1.10.1+dfsg-5+deb7u1
liblwres80 (1:9.8.4.dfsg.P1-6+nmu2) to 1:9.8.4.dfsg.P1-6+nmu2+deb7u1
libmagic1 (5.11-2) to 1:5.14-2~bpo70+1
libmagickcore5 (8:6.7.7.10-5) to 8:6.7.7.10-5+deb7u2
libmagickwand5 (8:6.7.7.10-5) to 8:6.7.7.10-5+deb7u2
libmodplug1 (1:0.8.8.4-3) to 1:0.8.8.4-3+deb7u1+git20130828
libreoffice-base-core (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-calc (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-common (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-core (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-draw (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-help-en-us (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-impress (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-kde (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-style-oxygen (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libreoffice-writer (1:4.0.3-2~bpo70+1) to 1:4.1.0-5~bpo70+3
libsmbclient (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
libwbclient0 (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
libxapian22 (1.2.12-2) to 1.2.15-2~bpo70+1
lintian (2.5.10.4) to 2.5.19~bpo70+1
module-assistant (0.11.4) to 0.11.6~bpo70+1
openjdk-6-jre (6b27-1.12.5-1) to 6b27-1.12.6-1~deb7u1
openjdk-6-jre-headless (6b27-1.12.5-1) to 6b27-1.12.6-1~deb7u1
openjdk-6-jre-lib (6b27-1.12.5-1) to 6b27-1.12.6-1~deb7u1
openssh-client (1:6.0p1-4) to 1:6.2p2-6~bpo70+1
python-debian (0.1.21) to 0.1.21+nmu2~bpo70+1
samba-common (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
smbclient (2:3.6.6-6) to 2:3.6.18-1~bpo70+1
tzdata (2013c-0wheezy1) to 2013d-0wheezy1
tzdata-java (2013c-0wheezy1) to 2013d-0wheezy1
uno-libs3 (4.0.3-2~bpo70+1) to 4.1.0-5~bpo70+3
ure (4.0.3-2~bpo70+1) to 4.1.0-5~bpo70+3
Installed the following packages:
gnupg-agent (2.0.19-2)
gnupg2 (2.0.19-2)
iucode-tool (1.0-1~bpo70+1)
libassuan0 (2.0.3-1)
libfile-basedir-perl (0.03-1)
libksba8 (1.2.0-2)
libtevent0 (0.9.16-1)
libtext-levenshtein-perl (0.06~01-1)
pinentry-gtk2 (0.8.1-1)
python-six (1.1.0-2)
python3 (3.2.3-6)
python3-minimal (3.2.3-6)
python3.2 (3.2.3-7)
python3.2-minimal (3.2.3-7)
t1utils (1.37-1)
Code: Select all
Package: *
Pin: release v=12.0,o=MEPIS,a=mepis,n=mepis-12.0,l=MEPIS
Pin-Priority: 902
Package: *
Pin: release o=Mepis community repository, n=mepis11cr
Pin-Priority: 901
Package: *
Pin: release o=Debian,l=Debian-Security
Pin-Priority: 801
Package: *
Pin: release o=Debian,n=wheezy*,l=Debian
Pin-Priority: 800
Package: *
Pin: release a=wheezy-backports
Pin-Priority: 800
Package: *
Pin: release o=Ubuntu
Pin-Priority: 400
Namida's update to Chrome 30 wasn't from Warren's M12 repo or the Debian Wheezy repos, it came from the dl.google.com repoJerry3904 wrote:Hmmm. I just checked, and I have no update. Do you have something other than the M12 repositories listed in the Wiki?
Code: Select all
deb http://dl.google.com/linux/chrome/deb/ stable main
Code: Select all
kent@mepis1:~$ apt-cache policy google-chrome-stable
google-chrome-stable:
Installed: (none)
Candidate: 30.0.1599.66-1
Version table:
30.0.1599.66-1 0
500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages
kent@mepis1:~$
The version of libnss3 in the Wheezy repos is currently the 3.14.3-1 version: http://packages.debian.org/wheezy/libnss3, actually "2:3.14.3-1" -- but I don't think it checks the "2:" part. The google-chrome-stable package wouldn't have been installable/upgradeable if that version wasn't in the repos.namida12 wrote:Green451@mepis1:~$ /opt/google/chrome/google-chrome %U
[3976:4004:1002/140204:FATAL:nss_util.cc(396)] NSS_VersionCheck("3.14.3") failed. NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
Aborted
* * *
Here is link I found searching: http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b
Somebody please check and correct me if i am wrong: Apparently there are some security updates in the newer version: 3.14.3 contains a number of important security fixes, and support for older systems is no longer desirable.
Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still ships 4.9.2 on stable, so this is the lower bound. I looked for libnspr in synaptic, libnspr4 2:4.9.2-1 <---could this be the reason?kmathern wrote:The version of libnss3 in the Wheezy repos is currently the 3.14.3-1 version: http://packages.debian.org/wheezy/libnss3, actually "2:3.14.3-1" -- but I don't think it checks the "2:" part. The google-chrome-stable package wouldn't have been installable/upgradeable if that version wasn't in the repos.namida12 wrote:Green451@mepis1:~$ /opt/google/chrome/google-chrome %U
[3976:4004:1002/140204:FATAL:nss_util.cc(396)] NSS_VersionCheck("3.14.3") failed. NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
Aborted
* * *
I'm not sure why it's complaining about the libnss3 version, it looks correct to me.
I wonder if maybe the Wheezy libnspr4 version is the problem? It's at version 4.9.2-1 {actually 2:4.9.2-1}.> Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still
> ships 4.9.2 on stable, so this is the lower bound.
The sid/jessie versions aren't installable on M12/Wheezy because of a "libc6 (>= 2.15)" dependency, M12/Wheezy uses libc6 2.13. It needs to be backported to be installable. Put in a request for it to be added to the M12 CRs.namida12 wrote:How would I use apt-get to try the upgrade NSPR 4.9.5
kmathern wrote:From your first link http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b
> Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still
> ships 4.9.2 on stable, so this is the lower bound.
I will wait for fix as I can not believe i am the only Google browser Mepis user that would like the latest security updates in their web browser.I wonder if maybe the Wheezy libnspr4 version is the problem? It's at version 4.9.2-1 {actually 2:4.9.2-1}.
Maybe Tim or Stevo could backport the sid/jessie version for the CR repo, it's currently at 4.10-1 {actually 2:4.10-1}
It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.namida12 wrote:I will wait for fix as Ii can not believe i am the only Google browser mepis user that would like the latest security updates in their web browser.
That is part of testing a beta, I hope...
JR
Being treated like the bastard stepchild does get kinda old, doesn't it?kmathern wrote:It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.
* *kmathern wrote:It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.namida12 wrote:I will wait for fix as Ii can not believe i am the only Google browser mepis user that would like the latest security updates in their web browser.
That is part of testing a beta, I hope...
JR
Back in April their update to Chrome 26 broke it on stock Squeeze installs, but Squeeze was more than 2 years old at that time, it's only been 5 months since Wheezy's release.
What version is your libnspr4richb wrote:Just got GC Version 30.0.1599.66 today and it runs fine in Kubuntu 13.04. As I recall I downloaded an earlier version and it just keeps upgrading when newer ones come out. None have been a problem. So it does not appear to be a widespread problem. I should not say that as I can only speak for my system.
nspr (2:4.9.5-1ubuntu1) http://packages.ubuntu.com/source/raring/nsprnamida12 wrote:What version is your libnspr4richb wrote:Just got GC Version 30.0.1599.66 today and it runs fine in Kubuntu 13.04. As I recall I downloaded an earlier version and it just keeps upgrading when newer ones come out. None have been a problem. So it does not appear to be a widespread problem. I should not say that as I can only speak for my system.
JR
Code: Select all
Package: google-chrome-stable
Version: 30.0.1599.66-1
Architecture: i386
Maintainer: Chrome Linux Team <chromium-dev@chromium.org>
Installed-Size: 145775
Pre-Depends: dpkg (>= 1.14.0)
Depends: gconf-service, libasound2 (>= 1.0.23), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.11), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.2.14), libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.3.9), libgcc1 (>= 1:4.1.1), libgconf-2-4 (>= 2.31.1), libgcrypt11 (>= 1.4.5), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.18.0), libgtk2.0-0 (>= 2.24.0), libnspr4 (>= 1.8.0.10), libnss3 (>= 3.14.3), libpango1.0-0 (>= 1.22.0), libstdc++6 (>= 4.6), libudev0 (>= 147) | libudev1 (>= 198), libx11-6 (>= 2:1.4.99.1), libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxrender1, libxss1, ca-certificates, libcurl3, lsb-base (>= 3.2), xdg-utils (>= 1.0.2), wget
Code: Select all
apt-get install libnss3 -t wheezy
Code: Select all
Selecting previously unselected package google-chrome-stable.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 105882 files and directories currently installed.)
Unpacking google-chrome-stable (from .../google-chrome-stable_current_amd64.deb) ...
Setting up google-chrome-stable (30.0.1599.66-1) ...
update-alternatives: using /usr/bin/google-chrome to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
Processing triggers for man-db ...
Processing triggers for menu ...
Code: Select all
apt-cache policy libnss3 libnss3-1d
The mepis-config update from last week enabled the wheezy-backports repo. The new kernels you're seeing are from it, Warren didn't build a new kernel.smilliken wrote:I see there are some new kernels and headers in the repos.
kmathern wrote:Run the following and post the resultsCode: Select all
apt-cache policy libnss3 libnss3-1d
Code: Select all
Green451@mepis1:~$ apt-cache policy libnss3 libnss3-1d
libnss3:
Installed: 2:3.14.2-1
Candidate: 2:3.14.2-1
Version table:
2:3.14.3-1 0
800 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
*** 2:3.14.2-1 0
902 http://mepis.mirrorcatalogs.com/packages/mepis/ mepis-12.0/main amd64 Packages
100 /var/lib/dpkg/status
libnss3-1d:
Installed: 2:3.14.2-1
Candidate: 2:3.14.2-1
Version table:
2:3.14.3-1 0
800 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
*** 2:3.14.2-1 0
902 http://mepis.mirrorcatalogs.com/packages/mepis/ mepis-12.0/main amd64 Packages
100 /var/lib/dpkg/status
Green451@mepis1:~$
Run the following (as root)namida12 wrote:kmathern wrote:Run the following and post the resultsCode: Select all
apt-cache policy libnss3 libnss3-1d
Code: Select all
Green451@mepis1:~$ apt-cache policy libnss3 libnss3-1d libnss3: Installed: 2:3.14.2-1 Candidate: 2:3.14.2-1 Version table: 2:3.14.3-1 0 800 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages *** 2:3.14.2-1 0 902 http://mepis.mirrorcatalogs.com/packages/mepis/ mepis-12.0/main amd64 Packages 100 /var/lib/dpkg/status libnss3-1d: Installed: 2:3.14.2-1 Candidate: 2:3.14.2-1 Version table: 2:3.14.3-1 0 800 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages *** 2:3.14.2-1 0 902 http://mepis.mirrorcatalogs.com/packages/mepis/ mepis-12.0/main amd64 Packages 100 /var/lib/dpkg/status Green451@mepis1:~$
Code: Select all
apt-get install libnss3 libnss3-1d -t wheezy
That would help, but I think the Google folks should fix the dependency.Stevo wrote:I can confirm both the problem, and that installing Wheezy's version of libnss3 will correct it.
So...I guess the older MEPIS version can be considered deprecated, and Warren should purge it from the repo?
You're using the 64bit package which seems to have installed okay for you.namida12 wrote:Just got a new update to Google Stable: Version 30.0.1599.101
I can confirm it is much faster, than the previous version i had troubles getting to run, before libnss3 was installed...
Again thanks Kmathern & Stevo for the knowledge & fix in the latest beta 11.2.92...
Code: Select all
Version 31.0.1650.16 beta
Depends: lib32gcc1 (>=1:4.1.1) but it is not installable
Depends: lib32stdc++6 (>=4.6) but it is not installable
Depends: libc6-i386 (>=2.11) but it is not installable
Patience is needed till Google-Chrome devs spit out another corrected update.kmathern wrote:You're using the 64bit package which seems to have installed okay for you.namida12 wrote:Just got a new update to Google Stable: Version 30.0.1599.101
I can confirm it is much faster, than the previous version i had troubles getting to run, before libnss3 was installed...
Again thanks Kmathern & Stevo for the knowledge & fix in the latest beta 11.2.92...
It does look like the 32bit package has some problems though according to this forums.debian.net thread: http://forums.debian.net/viewtopic.php? ... 75#p515575, because they included some 64bit dependencies in the 32bit package.
At the boot screen in GRUB typerobert1 wrote:Hi All
I am in the process of fixing up a fairly recent PC that i aquired. it is almost 5 years old. i plan on using it to replace the older Dell that i am currently using. it was a custom built box with a MSI MS-7529 Motherboard with a Intel 82G33/G31 Express Integrated Graphics Controller onboard. the kernel driver is i915. the problem is that i cannot get Mepis M12 11.9.92 to boot into a graphical screen. splashy does work, but i found that the boot process was extremely slow. id the i915 driver excluded from Mepis?
i know that usually on most linux distributions, there were usually no issues with Intel Graphics chipsets.
after splashy disappears, all there is is just a black screen with a little flashing curser in the top left corner.
They fixed the dependencies of the 32bit google-chrome-stable package yesterday (or two days ago). It's now at version 30.0.1599.114-1 and no longer has the 64bit depends for lib32gcc1, lib32stdc++6 & libc6-i386.golden45 wrote:Found this on google chrom site
Steps to reproduce the problem:
1. Add to /etc/apt/sources.list
deb http://dl.google.com/linux/chrome/deb/ stable main
2. Try to install (or upgrade from 30.0.1599.66) google-chrome-beta
3. The dependecies cannot be met, hence disallowing to cleanly install (or upgrade) the package.
What is the expected behavior?
All dependencies should be met.
What went wrong?
The dependecies cannot be met due to unavailable libraries, which are specific to 64-bit repos:
lib32gcc1
lib32stdc++6
libc6-i386
Did this work before? Yes 30.0.1599.66
Chrome version: 31.0.1650.11 Channel: beta
OS Version: Ubunu 12.04
Flash Version: Shockwave Flash 11.2 r202
What is interesting, the DEB for 64-bit version is working correcly, and even the mentioned packages are not dependants.
Maybe the build script wrongly puts dependencies not in the right arch (32 vs. 64)?
Code: Select all
apt-cache show google-chrome-stable
Package: google-chrome-stable
Version: 30.0.1599.114-1
Architecture: i386
Maintainer: Chrome Linux Team <chromium-dev@chromium.org>
Installed-Size: 145811
Pre-Depends: dpkg (>= 1.14.0)
Depends: gconf-service, libasound2 (>= 1.0.23), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.11), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.2.14), libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.8.0), libfreetype6 (>= 2.3.9), libgcc1 (>= 1:4.1.1), libgconf-2-4 (>= 2.31.1), libgcrypt11 (>= 1.4.5), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.18.0), libgtk2.0-0 (>= 2.24.0), libnspr4 (>= 1.8.0.10), libnss3 (>= 3.14.3), libpango1.0-0 (>= 1.22.0), libstdc++6 (>= 4.6), libudev0 (>= 147) | libudev1 (>= 198), libx11-6 (>= 2:1.4.99.1), libxcomposite1 (>= 1:0.3-1), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxrender1, libxss1, ca-certificates, libcurl3, lsb-base (>= 3.2), xdg-utils (>= 1.0.2), wget
Conflicts: google-chrome
Replaces: google-chrome
Provides: google-chrome, www-browser
Section: web
Priority: optional
Filename: pool/main/g/google-chrome-stable/google-chrome-stable_30.0.1599.114-1_i386.deb
Size: 42193880
SHA1: 140bf3da921a63463af141773a9383116e02ac91
MD5sum: 825385d4a671ea47d820eba0e314348c
Description: The web browser from Google
Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.
Description-md5: a2d34067fc33f1c87253c33b9fd975f0
The rest of us are wondering too.golden45 wrote:I'm wondering when the next beta is going to be released .I know warren is busy but I how know many of us is patiently waiting.john
Code: Select all
$ google-chrome-stable
/usr/bin/google-chrome-stable: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.14.3' not found (required by /usr/bin/google-chrome-stable)
Code: Select all
deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free
# deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free
deb http://ftp.us.debian.org/debian/ wheezy-backports main contrib non-free
# deb http://www.deb-multimedia.org wheezy main non-free
Code: Select all
apt-get install libnss3 libnss3-1d -t wheezy
Kent, you are amazing. Nice catch!!kmathern wrote:I think the "2:" epoch number for Warren's libnss3 & libnss3-1d packages is causing the problem. It make's apt think that the "2:3.14.2-1" version fulfills the libnss3 (>= 3.14.3) dependency.
Try installing the Wheezy version of libnss3 & libnss3-1d (Wheezy is currently at version 2:3.14.5-1)Code: Select all
apt-get install libnss3 libnss3-1d -t wheezy
New install and had to perform this to get google to work...kmathern wrote:I think the "2:" epoch number for Warren's libnss3 & libnss3-1d packages is causing the problem. It makes apt think that the "2:3.14.2-1" version fulfills the libnss3 (>= 3.14.3) dependency.
Try installing the Wheezy version of libnss3 & libnss3-1d (Wheezy is currently at version 2:3.14.5-1)Code: Select all
apt-get install libnss3 libnss3-1d -t wheezy
Code: Select all
apt-get install libnss3 libnss3-1d -t wheezy
Code: Select all
nouveau.modeset=0 nomodeset
You obviously want to follow Tim's instructions first, but afterwards you may want/need to run sgfxi to get the graphics set up fully. Might need to run it twice.GregB wrote:I have the 32-bit M12 on a flash drive made using UNetbootin, and have been trying to get it to run on an older PC. I have been able to get it to load, and the splash screen looks normal. When it gets to the point where the desktop GUI is supposed to appear the monitor displays a blank screen. I've tried a lot of different cheatcodes making different xdrvr and xres selections and the like. The most that will appear on the screen is a blinking underline cursor in the upper left corner of the screen, and a small white block cursor when the mouse is moved. The PC has an NVIDIA 7300GT AGP video card that is feeding an Acer S231 widescreen flat panel monitor via VGA. This same setup runs MEPIS 11 OK. Any advice will be appreciated.
I wasn't thinking clearly that you were talking about running live, not already installed.GregB wrote:Thanks for the replies. I tried using the nouveau.modeset=0 nomodeset cheatcodes by selecting the safe mode selection and editing the part after the fromhd to read only the two suggested cheatcodes. The monitor displays a square box saying Input Not Supported. After a little while the blank screen with the blinking cursor and the block mouse cursor is displayed. I can Alt-F1 to a text mode console to do a user login. Will sgfxi permanently alter the Live version on the flash drive? Once the Live version on the flash drive is working OK I can try a test install to the hard drive on the PC.
M12 has aufs enabled by default, I don't know if there's a way (a cheatcode) to disable it.lucky9 wrote:...I'm not too sure that aufs is included with the Beta...
M12 uses the Xorg KMS drivers by default including the nouveau driver for nvidia video cards, so you shouldn't need to do anything to enable it.lucky9 wrote:...Specifying nouveau should not be necessary either.
A lot of those cheatcodes (video related cheats) aren't included in M12.lucky9 wrote:...See here: http://www.mepis.org/docs/en/index.php?title=Cheatcodes
The /var/log/Xorg.0.log file has diagnostic value. One way to post it would be to install the pastebinit packageGregB wrote:So far no joy. Is there any combination of cheatcodes that can aid in doing a diagnostic as to why X11 is failing to establish a valid GUI screen? I tried doing startx from a text mode console. It produces a log file in /var/log. If this log file has diagnostic value, is there any way that this log file can be saved to a permanent file so that I can post a copy of it?
Code: Select all
apt-get update
apt-get install pastebinit
This assumes you have a viewable terminal screen while in cli mode, and a working internet connection.
Code: Select all
[ 110.204]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 110.204] X Protocol Version 11, Revision 0
[ 110.204] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian
[ 110.204] Current Operating System: Linux mepis 3.9-1-mepis-pae #1 SMP MEPIS 3.9.8-1 i686
[ 110.204] Kernel command line: initrd=/ubninit quiet splash fromhd BOOT_IMAGE=/ubnkern
[ 110.204] Build Date: 17 April 2013 11:13:16AM
[ 110.204] xorg-server 2:1.12.4-6 (Julien Cristau <jcristau@debian.org>)
[ 110.204] Current version of pixman: 0.26.0
[ 110.204] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 110.204] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 110.205] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 28 19:11:57 2013
[ 112.366] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 112.938] (==) No Layout section. Using the first Screen section.
[ 112.938] (==) No screen section available. Using defaults.
[ 112.938] (**) |-->Screen "Default Screen Section" (0)
[ 112.938] (**) | |-->Monitor "<default monitor>"
[ 112.944] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 112.944] (==) Automatically adding devices
[ 112.944] (==) Automatically enabling devices
[ 113.302] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 113.303] Entry deleted from font path.
[ 113.311] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[ 113.312] Entry deleted from font path.
[ 113.312] (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist.
[ 113.312] Entry deleted from font path.
[ 113.312] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 113.312] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 113.312] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 113.312] (II) Loader magic: 0xb77a25a0
[ 113.312] (II) Module ABI versions:
[ 113.312] X.Org ANSI C Emulation: 0.4
[ 113.312] X.Org Video Driver: 12.1
[ 113.312] X.Org XInput driver : 16.0
[ 113.312] X.Org Server Extension : 6.0
[ 113.313] (--) PCI:*(0:1:0:0) 10de:02e2:107d:20af rev 162, Mem @ 0xce000000/16777216, 0xb0000000/268435456, 0xcd000000/16777216, BIOS @ 0x????????/131072
[ 113.316] (II) Open ACPI successful (/var/run/acpid.socket)
[ 113.316] (II) LoadModule: "extmod"
[ 113.445] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 113.990] (II) Module extmod: vendor="X.Org Foundation"
[ 113.990] compiled for 1.12.4, module version = 1.0.0
[ 113.990] Module class: X.Org Server Extension
[ 113.990] ABI class: X.Org Server Extension, version 6.0
[ 113.990] (II) Loading extension SELinux
[ 113.990] (II) Loading extension MIT-SCREEN-SAVER
[ 113.990] (II) Loading extension XFree86-VidModeExtension
[ 113.990] (II) Loading extension XFree86-DGA
[ 113.990] (II) Loading extension DPMS
[ 113.990] (II) Loading extension XVideo
[ 113.990] (II) Loading extension XVideo-MotionCompensation
[ 113.990] (II) Loading extension X-Resource
[ 113.990] (II) LoadModule: "dbe"
[ 113.990] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 114.555] (II) Module dbe: vendor="X.Org Foundation"
[ 114.556] compiled for 1.12.4, module version = 1.0.0
[ 114.556] Module class: X.Org Server Extension
[ 114.556] ABI class: X.Org Server Extension, version 6.0
[ 114.556] (II) Loading extension DOUBLE-BUFFER
[ 114.556] (II) LoadModule: "glx"
[ 114.556] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 115.647] (II) Module glx: vendor="X.Org Foundation"
[ 115.649] compiled for 1.12.4, module version = 1.0.0
[ 115.649] ABI class: X.Org Server Extension, version 6.0
[ 115.650] (==) AIGLX enabled
[ 115.770] (II) Loading extension GLX
[ 115.770] (II) LoadModule: "record"
[ 115.770] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 115.905] (II) Module record: vendor="X.Org Foundation"
[ 115.905] compiled for 1.12.4, module version = 1.13.0
[ 115.905] Module class: X.Org Server Extension
[ 115.905] ABI class: X.Org Server Extension, version 6.0
[ 115.905] (II) Loading extension RECORD
[ 115.905] (II) LoadModule: "dri"
[ 115.905] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 116.600] (II) Module dri: vendor="X.Org Foundation"
[ 116.600] compiled for 1.12.4, module version = 1.0.0
[ 116.600] ABI class: X.Org Server Extension, version 6.0
[ 116.600] (II) Loading extension XFree86-DRI
[ 116.600] (II) LoadModule: "dri2"
[ 116.601] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 116.606] (II) Module dri2: vendor="X.Org Foundation"
[ 116.606] compiled for 1.12.4, module version = 1.2.0
[ 116.606] ABI class: X.Org Server Extension, version 6.0
[ 116.607] (II) Loading extension DRI2
[ 116.607] (==) Matched nouveau as autoconfigured driver 0
[ 116.607] (==) Matched nv as autoconfigured driver 1
[ 116.607] (==) Matched vesa as autoconfigured driver 2
[ 116.607] (==) Matched fbdev as autoconfigured driver 3
[ 116.607] (==) Assigned the driver to the xf86ConfigLayout
[ 116.607] (II) LoadModule: "nouveau"
[ 116.612] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 117.368] (II) Module nouveau: vendor="X.Org Foundation"
[ 117.368] compiled for 1.12.4, module version = 1.0.1
[ 117.368] Module class: X.Org Video Driver
[ 117.368] ABI class: X.Org Video Driver, version 12.1
[ 117.368] (II) LoadModule: "nv"
[ 117.375] (WW) Warning, couldn't open module nv
[ 117.375] (II) UnloadModule: "nv"
[ 117.375] (II) Unloading nv
[ 117.375] (EE) Failed to load module "nv" (module does not exist, 0)
[ 117.375] (II) LoadModule: "vesa"
[ 117.381] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 118.302] (II) Module vesa: vendor="X.Org Foundation"
[ 118.302] compiled for 1.12.1, module version = 2.3.1
[ 118.302] Module class: X.Org Video Driver
[ 118.302] ABI class: X.Org Video Driver, version 12.0
[ 118.302] (II) LoadModule: "fbdev"
[ 118.303] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 119.275] (II) Module fbdev: vendor="X.Org Foundation"
[ 119.275] compiled for 1.12.1, module version = 0.4.2
[ 119.275] ABI class: X.Org Video Driver, version 12.0
[ 119.275] (II) NOUVEAU driver Date: Fri Jul 6 16:23:50 2012 +1000
[ 119.275] (II) NOUVEAU driver for NVIDIA chipset families :
[ 119.276] RIVA TNT (NV04)
[ 119.276] RIVA TNT2 (NV05)
[ 119.276] GeForce 256 (NV10)
[ 119.276] GeForce 2 (NV11, NV15)
[ 119.276] GeForce 4MX (NV17, NV18)
[ 119.276] GeForce 3 (NV20)
[ 119.276] GeForce 4Ti (NV25, NV28)
[ 119.276] GeForce FX (NV3x)
[ 119.276] GeForce 6 (NV4x)
[ 119.276] GeForce 7 (G7x)
[ 119.276] GeForce 8 (G8x)
[ 119.276] GeForce GTX 200 (NVA0)
[ 119.276] GeForce GTX 400 (NVC0)
[ 119.276] (II) VESA: driver for VESA chipsets: vesa
[ 119.276] (II) FBDEV: driver for framebuffer: fbdev
[ 119.276] (++) using VT number 8
[ 119.282] drmOpenDevice: node name is /dev/dri/card0
[ 119.283] drmOpenDevice: open result is 8, (OK)
[ 119.283] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 119.283] drmOpenDevice: node name is /dev/dri/card0
[ 119.283] drmOpenDevice: open result is 8, (OK)
[ 119.283] drmOpenByBusid: drmOpenMinor returns 8
[ 119.283] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 119.283] (II) [drm] nouveau interface version: 1.1.0
[ 119.283] (WW) Falling back to old probe method for vesa
[ 119.283] (WW) Falling back to old probe method for fbdev
[ 119.283] (II) Loading sub module "fbdevhw"
[ 119.283] (II) LoadModule: "fbdevhw"
[ 119.283] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 119.733] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 119.733] compiled for 1.12.4, module version = 0.0.2
[ 119.733] ABI class: X.Org Video Driver, version 12.1
[ 119.733] (II) Loading sub module "dri"
[ 119.733] (II) LoadModule: "dri"
[ 119.733] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 119.733] (II) Module dri: vendor="X.Org Foundation"
[ 119.733] compiled for 1.12.4, module version = 1.0.0
[ 119.733] ABI class: X.Org Server Extension, version 6.0
[ 119.733] (II) NOUVEAU(0): Loaded DRI module
[ 119.733] drmOpenDevice: node name is /dev/dri/card0
[ 119.734] drmOpenDevice: open result is 9, (OK)
[ 119.734] drmOpenDevice: node name is /dev/dri/card0
[ 119.734] drmOpenDevice: open result is 9, (OK)
[ 119.734] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 119.734] drmOpenDevice: node name is /dev/dri/card0
[ 119.734] drmOpenDevice: open result is 9, (OK)
[ 119.734] drmOpenByBusid: drmOpenMinor returns 9
[ 119.734] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 119.734] (II) [drm] DRM interface version 1.4
[ 119.734] (II) [drm] DRM open master succeeded.
[ 119.734] (--) NOUVEAU(0): Chipset: "NVIDIA NV4b"
[ 119.734] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 119.734] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 119.734] (==) NOUVEAU(0): RGB weight 888
[ 119.734] (==) NOUVEAU(0): Default visual is TrueColor
[ 119.734] (==) NOUVEAU(0): Using HW cursor
[ 119.734] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 119.734] (==) NOUVEAU(0): Page flipping enabled
[ 119.734] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 119.800] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[ 119.832] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 119.888] (II) NOUVEAU(0): Output TV-1 has no monitor section
[ 119.948] (II) NOUVEAU(0): EDID for output DVI-I-1
[ 119.980] (II) NOUVEAU(0): EDID for output VGA-1
[ 119.980] (II) NOUVEAU(0): Manufacturer: ACR Model: 1a6 Serial#: 292613006
[ 119.980] (II) NOUVEAU(0): Year: 2011 Week: 17
[ 119.980] (II) NOUVEAU(0): EDID Version: 1.3
[ 119.980] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 119.980] (II) NOUVEAU(0): Sync: Separate
[ 119.980] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 51 vert.: 29
[ 119.980] (II) NOUVEAU(0): Gamma: 2.20
[ 119.980] (II) NOUVEAU(0): DPMS capabilities: Off; RGB/Color Display
[ 119.980] (II) NOUVEAU(0): Default color space is primary color space
[ 119.980] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 119.980] (II) NOUVEAU(0): redX: 0.646 redY: 0.343 greenX: 0.321 greenY: 0.612
[ 119.980] (II) NOUVEAU(0): blueX: 0.147 blueY: 0.066 whiteX: 0.313 whiteY: 0.329
[ 119.980] (II) NOUVEAU(0): Supported established timings:
[ 119.980] (II) NOUVEAU(0): 720x400@70Hz
[ 119.980] (II) NOUVEAU(0): 640x480@60Hz
[ 119.980] (II) NOUVEAU(0): 640x480@67Hz
[ 119.980] (II) NOUVEAU(0): 640x480@72Hz
[ 119.980] (II) NOUVEAU(0): 640x480@75Hz
[ 119.980] (II) NOUVEAU(0): 800x600@56Hz
[ 119.980] (II) NOUVEAU(0): 800x600@60Hz
[ 119.980] (II) NOUVEAU(0): 800x600@72Hz
[ 119.980] (II) NOUVEAU(0): 800x600@75Hz
[ 119.980] (II) NOUVEAU(0): 832x624@75Hz
[ 119.980] (II) NOUVEAU(0): 1024x768@60Hz
[ 119.980] (II) NOUVEAU(0): 1024x768@70Hz
[ 119.980] (II) NOUVEAU(0): 1024x768@75Hz
[ 119.980] (II) NOUVEAU(0): 1280x1024@75Hz
[ 119.980] (II) NOUVEAU(0): 1152x864@75Hz
[ 119.980] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 119.980] (II) NOUVEAU(0): Supported standard timings:
[ 119.980] (II) NOUVEAU(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 119.980] (II) NOUVEAU(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 119.980] (II) NOUVEAU(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 119.980] (II) NOUVEAU(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 119.980] (II) NOUVEAU(0): #4: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 119.980] (II) NOUVEAU(0): #5: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 119.980] (II) NOUVEAU(0): Supported detailed timing:
[ 119.980] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 510 x 287 mm
[ 119.980] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 119.980] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 119.980] (II) NOUVEAU(0): Ranges: V min: 55 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 165 MHz
[ 119.981] (II) NOUVEAU(0): Serial No: LNZ080214204
[ 119.981] (II) NOUVEAU(0): Monitor name: Acer S231HL
[ 119.981] (II) NOUVEAU(0): EDID (in hex):
[ 119.981] (II) NOUVEAU(0): 00ffffffffffff000472a6018eeb7011
[ 119.981] (II) NOUVEAU(0): 1115010368331d782e77c5a557529c25
[ 119.981] (II) NOUVEAU(0): 115054bfef8081c08140714f81808100
[ 119.981] (II) NOUVEAU(0): d1c001010101023a801871382d40582c
[ 119.981] (II) NOUVEAU(0): 4500fe1f1100001e000000fd00374b1e
[ 119.981] (II) NOUVEAU(0): 5010000a202020202020000000ff004c
[ 119.981] (II) NOUVEAU(0): 4e5a3038303231343230340a000000fc
[ 119.981] (II) NOUVEAU(0): 00416365722053323331484c0a20009a
[ 119.981] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 119.981] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 119.981] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 119.981] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 119.981] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 120.036] (II) NOUVEAU(0): EDID for output TV-1
[ 120.036] (II) NOUVEAU(0): Output DVI-I-1 disconnected
[ 120.036] (II) NOUVEAU(0): Output VGA-1 connected
[ 120.036] (II) NOUVEAU(0): Output TV-1 disconnected
[ 120.036] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 120.036] (II) NOUVEAU(0): Output VGA-1 using initial mode 1920x1080
[ 120.036] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 120.036] (--) NOUVEAU(0): Virtual size is 1920x1080 (pitch 0)
[ 120.036] (**) NOUVEAU(0): Driver mode "1920x1080": 148.5 MHz (scaled from 0.0 MHz), 67.5 kHz, 60.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 120.036] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1280x800": 83.5 MHz (scaled from 0.0 MHz), 49.7 kHz, 59.8 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 120.036] (**) NOUVEAU(0): Mode "1280x720": 74.4 MHz (scaled from 0.0 MHz), 44.7 kHz, 60.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 120.036] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 120.036] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 120.036] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 120.037] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 120.037] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 120.037] (++) NOUVEAU(0): DPI set to (96, 96)
[ 120.037] (II) Loading sub module "fb"
[ 120.037] (II) LoadModule: "fb"
[ 120.037] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 120.880] (II) Module fb: vendor="X.Org Foundation"
[ 120.880] compiled for 1.12.4, module version = 1.0.0
[ 120.880] ABI class: X.Org ANSI C Emulation, version 0.4
[ 120.880] (II) Loading sub module "exa"
[ 120.880] (II) LoadModule: "exa"
[ 120.881] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 121.930] (II) Module exa: vendor="X.Org Foundation"
[ 121.930] compiled for 1.12.4, module version = 2.5.0
[ 121.930] ABI class: X.Org Video Driver, version 12.1
[ 121.930] (II) Loading sub module "shadowfb"
[ 121.930] (II) LoadModule: "shadowfb"
[ 121.931] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 122.253] (II) Module shadowfb: vendor="X.Org Foundation"
[ 122.253] compiled for 1.12.4, module version = 1.0.0
[ 122.253] ABI class: X.Org ANSI C Emulation, version 0.4
[ 122.253] (II) UnloadModule: "vesa"
[ 122.253] (II) Unloading vesa
[ 122.253] (II) UnloadModule: "fbdev"
[ 122.253] (II) Unloading fbdev
[ 122.254] (II) UnloadSubModule: "fbdevhw"
[ 122.254] (II) Unloading fbdevhw
[ 122.254] (--) Depth 24 pixmap format is 32 bpp
[ 122.254] (II) NOUVEAU(0): Opened GPU channel 0
[ 122.263] (II) NOUVEAU(0): [DRI2] Setup complete
[ 122.263] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 122.263] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 124.194] (II) EXA(0): Driver allocated offscreen pixmaps
[ 124.194] (II) EXA(0): Driver registered support for the following operations:
[ 124.194] (II) Solid
[ 124.194] (II) Copy
[ 124.194] (II) Composite (RENDER acceleration)
[ 124.194] (II) UploadToScreen
[ 124.194] (II) DownloadFromScreen
[ 124.194] (==) NOUVEAU(0): Backing store disabled
[ 124.195] (==) NOUVEAU(0): Silken mouse enabled
[ 124.195] (II) NOUVEAU(0): [XvMC] Associated with NV40 texture adapter.
[ 124.195] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 124.195] (==) NOUVEAU(0): DPMS enabled
[ 124.195] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 124.208] (--) RandR disabled
[ 124.208] (II) Initializing built-in extension Generic Event Extension
[ 124.208] (II) Initializing built-in extension SHAPE
[ 124.208] (II) Initializing built-in extension MIT-SHM
[ 124.208] (II) Initializing built-in extension XInputExtension
[ 124.208] (II) Initializing built-in extension XTEST
[ 124.208] (II) Initializing built-in extension BIG-REQUESTS
[ 124.208] (II) Initializing built-in extension SYNC
[ 124.208] (II) Initializing built-in extension XKEYBOARD
[ 124.208] (II) Initializing built-in extension XC-MISC
[ 124.208] (II) Initializing built-in extension SECURITY
[ 124.208] (II) Initializing built-in extension XINERAMA
[ 124.208] (II) Initializing built-in extension XFIXES
[ 124.208] (II) Initializing built-in extension RENDER
[ 124.208] (II) Initializing built-in extension RANDR
[ 124.208] (II) Initializing built-in extension COMPOSITE
[ 124.208] (II) Initializing built-in extension DAMAGE
[ 124.208] (II) SELinux: Disabled on system
[ 152.478] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 152.478] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 152.478] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 152.478] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 152.479] (II) AIGLX: Loaded and initialized nouveau
[ 152.479] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 152.482] (II) NOUVEAU(0): NVEnterVT is called.
[ 152.483] (II) NOUVEAU(0): Setting screen physical size to 507 x 285
[ 152.483] resize called 1920 1080
[ 169.466] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 169.466] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 169.466] (II) LoadModule: "evdev"
[ 169.466] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 170.320] (II) Module evdev: vendor="X.Org Foundation"
[ 170.320] compiled for 1.12.1, module version = 2.7.0
[ 170.320] Module class: X.Org XInput Driver
[ 170.320] ABI class: X.Org XInput driver, version 16.0
[ 170.320] (II) Using input driver 'evdev' for 'Power Button'
[ 170.320] (**) Power Button: always reports core events
[ 170.320] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 170.320] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 170.320] (--) evdev: Power Button: Found keys
[ 170.320] (II) evdev: Power Button: Configuring as keyboard
[ 170.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 170.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 170.320] (**) Option "xkb_rules" "evdev"
[ 170.320] (**) Option "xkb_model" "pc105"
[ 170.320] (**) Option "xkb_layout" "us"
[ 170.322] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 170.322] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 170.322] (II) Using input driver 'evdev' for 'Sleep Button'
[ 170.322] (**) Sleep Button: always reports core events
[ 170.322] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[ 170.322] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 170.322] (--) evdev: Sleep Button: Found keys
[ 170.322] (II) evdev: Sleep Button: Configuring as keyboard
[ 170.322] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1"
[ 170.322] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 170.322] (**) Option "xkb_rules" "evdev"
[ 170.322] (**) Option "xkb_model" "pc105"
[ 170.322] (**) Option "xkb_layout" "us"
[ 170.332] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 170.332] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 170.332] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 170.332] (**) AT Translated Set 2 keyboard: always reports core events
[ 170.332] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 170.332] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 170.332] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 170.332] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 170.332] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 170.332] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
[ 170.332] (**) Option "xkb_rules" "evdev"
[ 170.332] (**) Option "xkb_model" "pc105"
[ 170.332] (**) Option "xkb_layout" "us"
[ 170.334] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event4)
[ 170.334] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 170.334] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
[ 170.334] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
[ 170.334] (**) evdev: ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event4"
[ 170.334] (--) evdev: ImPS/2 Logitech Wheel Mouse: Vendor 0x2 Product 0x5
[ 170.334] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
[ 170.334] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
[ 170.334] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found relative axes
[ 170.334] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
[ 170.334] (II) evdev: ImPS/2 Logitech Wheel Mouse: Configuring as mouse
[ 170.334] (II) evdev: ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
[ 170.334] (**) evdev: ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
[ 170.334] (**) evdev: ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 170.334] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
[ 170.334] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 9)
[ 170.334] (II) evdev: ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
[ 170.335] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
[ 170.335] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
[ 170.335] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
[ 170.335] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
[ 170.335] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
[ 170.337] (II) No input driver specified, ignoring this device.
[ 170.337] (II) This device may have been added with another device file.
[ 170.337] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 170.338] (II) No input driver specified, ignoring this device.
[ 170.338] (II) This device may have been added with another device file.
[ 170.344] (II) config/udev: Adding input device ACPI Virtual Keyboard Device (/dev/input/event5)
[ 170.344] (**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall"
[ 170.344] (II) Using input driver 'evdev' for 'ACPI Virtual Keyboard Device'
[ 170.344] (**) ACPI Virtual Keyboard Device: always reports core events
[ 170.344] (**) evdev: ACPI Virtual Keyboard Device: Device: "/dev/input/event5"
[ 170.344] (--) evdev: ACPI Virtual Keyboard Device: Vendor 0 Product 0
[ 170.344] (--) evdev: ACPI Virtual Keyboard Device: Found keys
[ 170.344] (II) evdev: ACPI Virtual Keyboard Device: Configuring as keyboard
[ 170.344] (**) Option "config_info" "udev:/sys/devices/virtual/input/input5/event5"
[ 170.344] (II) XINPUT: Adding extended input device "ACPI Virtual Keyboard Device" (type: KEYBOARD, id 10)
[ 170.344] (**) Option "xkb_rules" "evdev"
[ 170.344] (**) Option "xkb_model" "pc105"
[ 170.345] (**) Option "xkb_layout" "us"
[ 170.535] (II) evdev: Power Button: Close
[ 170.535] (II) UnloadModule: "evdev"
[ 170.535] (II) evdev: Sleep Button: Close
[ 170.535] (II) UnloadModule: "evdev"
[ 170.535] (II) evdev: AT Translated Set 2 keyboard: Close
[ 170.535] (II) UnloadModule: "evdev"
[ 170.535] (II) evdev: ImPS/2 Logitech Wheel Mouse: Close
[ 170.535] (II) UnloadModule: "evdev"
[ 170.535] (II) evdev: ACPI Virtual Keyboard Device: Close
[ 170.543] (II) UnloadModule: "evdev"
[ 170.546] (II) NOUVEAU(0): NVLeaveVT is called.
[ 170.546] (II) NOUVEAU(0): Closed GPU channel 0
[ 170.577] Server terminated successfully (0). Closing log file.
Code: Select all
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
Current Operating System: Linux mepis1 2.6.36-1-mepis-smp #1 SMP Thu Mar 31 17:07:18 CDT 2011 i686
Kernel command line: root=/dev/sda8 nomce quiet splash vga=788
Build Date: 17 December 2013 08:26:59PM
xorg-server 2:1.7.7-18 (Julien Cristau <jcristau@debian.org>)
Current version of pixman: 0.21.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 28 20:42:09 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0x81eccc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7
(--) PCI:*(0:1:0:0) 10de:02e2:107d:20af nVidia Corporation G73 [GeForce 7300 GT] rev 162, Mem @ 0xce000000/16777216, 0xb0000000/268435456, 0xcd000000/16777216, BIOS @ 0x????????/131072
(II) Open ACPI successful (/var/run/acpid.socket)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 260.19.21 Thu Nov 4 20:52:05 PDT 2010
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 260.19.21 Thu Nov 4 20:26:43 PDT 2010
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) Dec 28 20:42:12 NVIDIA(0): Enabling RENDER acceleration
(II) Dec 28 20:42:12 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) Dec 28 20:42:12 NVIDIA(0): enabled.
(II) Dec 28 20:42:13 NVIDIA(0): NVIDIA GPU GeForce 7300 GT (G73) at PCI:1:0:0 (GPU-0)
(--) Dec 28 20:42:13 NVIDIA(0): Memory: 262144 kBytes
(--) Dec 28 20:42:13 NVIDIA(0): VideoBIOS: 05.73.22.61.68
(II) Dec 28 20:42:13 NVIDIA(0): Detected AGP rate: 4X
(--) Dec 28 20:42:13 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Dec 28 20:42:13 NVIDIA(0): Connected display device(s) on GeForce 7300 GT at PCI:1:0:0
(--) Dec 28 20:42:13 NVIDIA(0): Acer S231HL (CRT-1)
(--) Dec 28 20:42:13 NVIDIA(0): Acer S231HL (CRT-1): 400.0 MHz maximum pixel clock
(II) Dec 28 20:42:13 NVIDIA(0): Assigned Display Device: CRT-1
(==) Dec 28 20:42:13 NVIDIA(0):
(==) Dec 28 20:42:13 NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) Dec 28 20:42:13 NVIDIA(0): will be used as the requested mode.
(==) Dec 28 20:42:13 NVIDIA(0):
(II) Dec 28 20:42:13 NVIDIA(0): Validated modes:
(II) Dec 28 20:42:13 NVIDIA(0): "nvidia-auto-select"
(II) Dec 28 20:42:13 NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(++) Dec 28 20:42:13 NVIDIA(0): DPI set to (96, 96); computed from -dpi X commandline option
(==) Dec 28 20:42:13 NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) Dec 28 20:42:13 NVIDIA(0): Initialized AGP GART.
(II) Dec 28 20:42:13 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) Dec 28 20:42:13 NVIDIA(0): Initialized OpenGL Acceleration
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) Dec 28 20:42:13 NVIDIA(0): Initialized X Rendering Acceleration
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
SELinux: Disabled on system, not enabling in X server
(II) Initializing extension GLX
(II) config/udev: Adding input device Power Button (/dev/input/event2)
(**) Power Button: Applying InputClass "evdev keyboard catchall"
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.7.6.901, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device Sleep Button (/dev/input/event1)
(**) Sleep Button: Applying InputClass "evdev keyboard catchall"
(**) Sleep Button: always reports core events
(**) Sleep Button: Device: "/dev/input/event1"
(II) Sleep Button: Found keys
(II) Sleep Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
(**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
(II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event4)
(**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
(**) ImPS/2 Logitech Wheel Mouse: always reports core events
(**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event4"
(II) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
(II) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
(II) ImPS/2 Logitech Wheel Mouse: Found relative axes
(II) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
(II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
(**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
(**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE)
(II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
(II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device PC Speaker (/dev/input/event3)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device ACPI Virtual Keyboard Device (/dev/input/event5)
(**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall"
(**) ACPI Virtual Keyboard Device: always reports core events
(**) ACPI Virtual Keyboard Device: Device: "/dev/input/event5"
(II) ACPI Virtual Keyboard Device: Found keys
(II) ACPI Virtual Keyboard Device: Configuring as keyboard
(II) XINPUT: Adding extended input device "ACPI Virtual Keyboard Device" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "us"
It looks like X is starting okay with the nouveau driver, I don't see any errors (EE) or warnings (WW) related to it. There is a 28 second gap in the timestamps (124.208 -> 152.478) that I'm not sure of. There's another 17 second gap a few timestamps later. When I use the nouveau driver on my system the first AIGLX line has a timestamp that's only about .4 seconds after the SELinux line.GregB wrote:Here are the Xorg.0.log files:
M12 Xorg.0.log using default boot option:Code: Select all
<snip> [ 120.036] (II) NOUVEAU(0): EDID for output TV-1 [ 120.036] (II) NOUVEAU(0): Output DVI-I-1 disconnected [ 120.036] (II) NOUVEAU(0): Output VGA-1 connected [ 120.036] (II) NOUVEAU(0): Output TV-1 disconnected [ 120.036] (II) NOUVEAU(0): Using exact sizes for initial modes [ 120.036] (II) NOUVEAU(0): Output VGA-1 using initial mode 1920x1080 [ 120.036] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [ 120.036] (--) NOUVEAU(0): Virtual size is 1920x1080 (pitch 0) [ 120.036] (**) NOUVEAU(0): Driver mode "1920x1080": 148.5 MHz (scaled from 0.0 MHz), 67.5 kHz, 60.0 Hz </snip> <snip> [ 124.208] (II) SELinux: Disabled on system [ 152.478] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 152.478] (II) AIGLX: enabled GLX_INTEL_swap_event [ 152.478] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 152.478] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 152.479] (II) AIGLX: Loaded and initialized nouveau [ 152.479] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 152.482] (II) NOUVEAU(0): NVEnterVT is called. [ 152.483] (II) NOUVEAU(0): Setting screen physical size to 507 x 285 [ 152.483] resize called 1920 1080 [ 169.466] (II) config/udev: Adding input device Power Button (/dev/input/event2) </snip>
Code: Select all
video=VGA-1:e
Code: Select all
video=VGA-1:D
Code: Select all
video=VGA-1:1920x1080@60e
Code: Select all
video=VGA-1:1920x1080@60D
Code: Select all
video=VGA-1:1920x1080R@60D
That's your whole problem. The latest MEPIS needs a bare minimum of 768MB with a practical minimum of 1024MB.GregB wrote:The PC has half a GB of RAM.
I agree with Uncle Mark that a half GB of RAM might be kind of low, but I'm curious are you able to run M11 on the same PC? I don't really find M12's RAM usage to be much different than M11's . The difference might be that M12 doesn't automatically use swap, where I think M11 did.GregB wrote:The PC has half a GB of RAM.
Code: Select all
swapon $(blkid | grep swap | cut -f1 -d:)
Code: Select all
cat /proc/swaps
Code: Select all
service kdm start
The SolydK Business Edition is a very nice KDE implementation of Debian stable. The Home Edition is testing based, but very well done, too.trainman4422 wrote: 4. Comment, not a question: I am beginning to look for alternatives to Mepis, staying with Debian and KDE. I am taking a close look at SolydK as a possible replacement for Mepis.
My take:trainman4422 wrote:I have been using Mepis since the "Simply Mepis" book was published (2003 I think) and have been totally satisfied. I prefer KDE and the Debian base so Mepis is a good fit. It appears, however, that development of M12 is not really progressing. I don't see any news updates or postings to the contrary. The last post I saw with any comment in this regard stated that Warren was busy with projects that actually generate revenue for his company, and that is certainly understandable. Still, Debian 7 was released last May and it is beginning to look like Debain 8 could be released before M12 is released. This raises some questions in my mind:
1. Is a final stable release of M12 expected any time in the foreseeable future?
2. Is there any way to have a stable M11 with Wheezy repositories?
3. Would it be possible for someone to post regular progress updates in the forum or on mepis.org?
4. Comment, not a question: I am beginning to look for alternatives to Mepis, staying with Debian and KDE. I am taking a close look at SolydK as a possible replacement for Mepis.
I looked at KWheezy, which is pretty good, but decided to stick with Mepis because it uses the actual Debian repositories and it used less memory. I'm not familiar with SolydK. There's also ZEVENOS Neptune, but it's a bit too cutting edge for my Kids' machines...trainman4422 wrote:I
4. Comment, not a question: I am beginning to look for alternatives to Mepis, staying with Debian and KDE. I am taking a close look at SolydK as a possible replacement for Mepis.
SolydK uses the Debian repositories as well.rschaffter wrote:I looked at KWheezy, which is pretty good, but decided to stick with Mepis because it uses the actual Debian repositories...
trainman4422 wrote: 4. Comment, not a question: I am beginning to look for alternatives to Mepis, staying with Debian and KDE. I am taking a close look at SolydK as a possible replacement for Mepis.
I simply went with Debian. CrunchBang (Wheezy-based) for when I want a quicker installation. By the way, Wheezy KDE might not be as quick and easy to install as Mepis, and not as nice out-of-the-box, but it isn't that difficult to get everything set up like you want it, and then it's about as nice as Mepis ever was, in my opinion. One cool thing about Mepis, kinda makes Debian easier. Mostly the same thing, in the end. I still like dropping in here and posting sometimes, though. Can't see any real reason for moving away from this community after all this time. Looking forward to MepisantiX, and I do hope that we'll see "Mepis 13" sometime before the year 2015.uncle mark wrote:I too am disappointed at the lack of any further MEPIS development, but it is what it is. Moving to another distro at some future point is not that big a deal for me, but moving away from the Community and all that it entails will be a tough pill to swallow.
Although I have Mepis on all my machines, I moved away from it as my daily driver midway through M11 due to unresolvable issues, and moved to Debian. Having said that, most all of the things I've learned here apply equally to pure Debian, as do packages from the Mepis CRs. I have SolydK HE on a new build, and the same can be said for it too, my point being that this community is still very relevant for me.uncle mark wrote:I too am disappointed at the lack of any further MEPIS development, but it is what it is. Moving to another distro at some future point is not that big a deal for me, but moving away from the Community and all that it entails will be a tough pill to swallow.
I am not a Mepis (or KDE) user but the Mepis CRs are a great resource. I have installed a few packages to get apps running on Debian that aren't available elsewhere. So I do want to be part of this community and support the work that Mepis contributes.DBeckett wrote:Having said that, most all of the things I've learned here apply equally to pure Debian, as do packages from the Mepis CRs.
First I do not use SolydXK, but if you had taken the trouble to look you would have found in Plain English.muskt wrote:I still belong to the "I don't know squat about Linux" crowd; however, I feel that I am learning (although darned slowly).
I read a large percentage of the posts here in order to glean some tidbits of knowledge without asking hundreds of questions.
As for the development cycle, I don't really care. I still play with M11 and have 2 installs of M12B3 64 on my desktop box.
I was intrigued by the mention of SolydXK BE. Since I have a few extra partitions available, I downloaded the 64 bit version and burned it to disk. The burn, run, and install went rather smoothly, and the conversion to GRUB (legacy) wasn't bad either. Getting it to run from boot was a bit rocky, but I was successful.
"Where the heck is he going with this?"
Well, documentation (a huge pet peeve with me) for SolydXK seems to be virtually nonexistent.
Jerry in Anchorage
Code: Select all
kdesu dbus-launch dolphin
A more easily understood way is here: http://www.debianadmin.com/enable-and-d ... sword.htmlWhat I do to create the root on ubuntu: first I do this
sudo -i
then
passwd
as @Zignd mentioned the classical messages will appear:
Type new UNIX password: [Type the root password you want]
Retype new UNIX password: [Retype the root password you chosen before]
passwd: password updated successfully
then I can use the su as a normal root acount...
Just FYI it's a real good idea to use kdesu (or gtksu if using Gnome) for all GUI programs to get root privileges. You can use su for non-GUI programs and regular Command Line commands.Ubuntu is one of the few Linux distributions out there that will not enable the root account.If you want to do something with root permission on the console you have to type sudo before the command.
sudo" means superuser do. "sudo" will prompt for "Password:". Please specify user password
As you have noticed during the Ubuntu installation there was no question about the root password, as you might have been used to see during other Linux distribution installation process.Because of this your root account is inactive.
If you want to enable root account (which is not recommended) enter the following command.
$sudo passwd root
This will prompt for a new root password and once you confirm it, you can start using the root account to login.
If you want to disable root account in ubuntu you need to lock the root account by using the following command
$sudo passwd -l root
If you want to work on a root console you'd better use the following command
$sudo -i
Oh, don't worry, you aren't gonna be rid of me any time soon.DBeckett wrote:Although I have Mepis on all my machines, I moved away from it as my daily driver midway through M11 due to unresolvable issues, and moved to Debian. Having said that, most all of the things I've learned here apply equally to pure Debian, as do packages from the Mepis CRs. I have SolydK HE on a new build, and the same can be said for it too, my point being that this community is still very relevant for me.uncle mark wrote:I too am disappointed at the lack of any further MEPIS development, but it is what it is. Moving to another distro at some future point is not that big a deal for me, but moving away from the Community and all that it entails will be a tough pill to swallow.
When setting up a machine I always log into the gui as root to set everything up. It's hard to move your home directory with sudo. I've done far more damage as root at a console than I ever did logged into KDE as root...lucky9 wrote: As for the sudo, su debate, I prefer not to have to enter a password multiple times when needing root privileges. Just a choice.
Nothing has changed here: go to mepis.org, click on Get Mepis tab, select direct download link, and download the correct one for your system.I've been a bit lost trying to locate the current M12 install but unsure of the correct url but ideally a dvd iso...
Since it's a beta, M12 is version #11.9.92. In Warren's versioning system, the number approaches the final number but doesn't get numbered with the final version number until it's declared stable.tascoast wrote:I've been a bit lost trying to locate the current M12 install but unsure of the correct url but ideally a dvd iso...
<http://www.mepis.org/node/176>A new test release of MEPIS 12, version 11.9.86, is available for testing.
NOOO!!!tascoast wrote:So essentially, it looks like a minor revision is available for me in 32 bit based on the Mepis pages and I've been looking for something called 'Mepis 12.x ' but this isn't the case until the beta becomes, well, no longer beta., I take it, as a newly enlightened student of linux, hopefully. Perhaps these things are a little confusing for newbies![]()
Aye, I suppose my current M11.x (xp dual boot) install might be named as 'latest stable' or something similar in other distros. I am currently downloading SimplyMEPIS-1.5G_11.9.92_32.iso with FDM in xp which I take to be the latest beta for M12. As for differences in Debian/KDE I'll get a virtual run initially to experience it. Hope that's got things right way up and all. I don't even begin to understand the marvellous innards of the little powerhouse M11 is or the differences between linux streams but stand in awe nonetheless.uncle mark wrote:NOOO!!!tascoast wrote:So essentially, it looks like a minor revision is available for me in 32 bit based on the Mepis pages and I've been looking for something called 'Mepis 12.x ' but this isn't the case until the beta becomes, well, no longer beta., I take it, as a newly enlightened student of linux, hopefully. Perhaps these things are a little confusing for newbies![]()
You have the latest stable version of MEPIS 11.
Technically, MEPIS 12 doesn't exist -- but there have been a couple betas. Version 11.9.x is the latest beta for M12. Version 11.0.x (that you have) is M11. They are vastly different, beginning with their Debian bases and KDE versions.
In System>Processor, tick the PAE box. This is found in the VM VirtualBox Manager.tascoast wrote:Well, out of interest, in both M11 and xp under VirtualBox, I get a live cd screen and options per usual using the latest M12 Beta live DVD *.iso (SimplyMEPIS-1.5G_11.9.92_32.iso) but are then informed that:
This kernel requires the following features not present on your CPU:
pae
Unable to boot - please use a kernel appropriate for your CPU
I'm not desperate to get it running and just awaiting M12 generally, so will check that I did in fact download the correct 31 bit beta version and all that, so just noting this apparent glitch for reference since I expected VirtualBox at least to be tolerant enough and virtualise hardware besides.
kindly
Mick
Not sure. Have you tried other options i.e. use full drive.tascoast wrote:"In System>Processor, tick the PAE box. This is found in the VM VirtualBox Manager."
Worked a treat thanks. I encountered another glitch in install where the partitioning and preparation of the drive fails and reverts to the previous screen for some reason, possibly a VB related issue?
You need to fire up GParted and put a partition table on the VBox drive first,richb wrote:Not sure. Have you tried other options i.e. use full drive.tascoast wrote:"In System>Processor, tick the PAE box. This is found in the VM VirtualBox Manager."
Worked a treat thanks. I encountered another glitch in install where the partitioning and preparation of the drive fails and reverts to the previous screen for some reason, possibly a VB related issue?
The "bpo70+1" in the version number means the upgrades are backports, you might need to temporarily set the prefered distro to wheezy-backports to get the upgrades to go thru.Frank_v7 wrote:namida12 wrote:New updates today!
Commit Log for Mon Jan 20 06:37:43 2014
Upgraded the following packages:
google-chrome-stable (31.0.1650.63-1) to 32.0.1700.77-1
lintian (2.5.20~bpo70+1) to 2.5.21~bpo70+1
Installed the following packages:
libavcodec54 (6:9.10-1~bpo70+1)
libavformat54 (6:9.10-1~bpo70+1)
libavutil52 (6:9.10-1~bpo70+1)
libchromaprint0 (1.1-1~bpo70+1)
libfreerdp1 (1.0.1-1.1+deb7u2)
libgnutls28 (3.2.8.1-2~bpo70+1)
libhogweed2 (2.7.1-1~bpo70+1)
libproxy-tools (0.3.1-6)
libtasn1-6 (3.4-2~bpo70+1)
Synaptic still shows there are three updates. updating, there is no more updates to install...
Synaptic error, or something not right with my repositories? This is a vanilla flavor except the addition of Google Chrome web browser.
Looking in Synaptic screen there is a classification: installed (upgradable) something i have never noticed before.
It lists:
libvic5 version 2.0.3.5 latest version 2.1.2-2-bpo70+1
Vlc Version 2.0.3-5 Latest version 2.1.2.2-bpo70+1
Vlc-nox Version 2.0.3.5 Latest version 2.1.2.2-bpo70+1
but this does not show up when I mark Upgrades, what am I doing wrong?
JR[/quote
]I just upgraded and those three vlc packages were "left over" and when I try to mark them for upgrade I get the red mark indicating removal. They are marked as upgradeable, but can't be upgraded.
It's not a bug report, but I do see a message about it on the debian-backports list: https://lists.debian.org/debian-backpor ... 00062.htmlStevo wrote:Wheezy-backports is missing the vlc-data package that should have been created with the others--there's no bpo vlc-data at all, and that's holding up the other upgrades. It's been three days, I'm going to see if anyone filed a bug report about that.
It may also uninstall phonon-backend-vlc, even the CR version, for no good reason. but it should be able to be reinstalled afterwards.
Danum wrote:You need to fire up GParted and put a partition table on the VBox drive first,richb wrote:Not sure. Have you tried other options i.e. use full drive.tascoast wrote:"In System>Processor, tick the PAE box. This is found in the VM VirtualBox Manager."
Worked a treat thanks. I encountered another glitch in install where the partitioning and preparation of the drive fails and reverts to the previous screen for some reason, possibly a VB related issue?
and that is a fault with the Mepis installer, not VBox
System Settings >Power Management > Uncheck "Screen Energy Saving" or extend the time.namida12 wrote:I do not see an answer for watching youtube videos. My computer monitor will go black after a while. JR
Danum wrote:System Settings >Power Management > Uncheck "Screen Energy Saving" or extend the time.namida12 wrote:I do not see an answer for watching youtube videos. My computer monitor will go black after a while. JR
Those cheats don't exist for M12.lucky9 wrote:First try xdrvr=vesa confx at the GRUB boot screen. See here for a howto: http://www.mepis.org/docs/en/index.php?title=Cheatcodes
If you get to a logon screen we may modify this cheatcode to use an open 3D video driver.
Don't count on it.malspa wrote:Is there any M12 development going on that anyone's aware of?
lucky9,lucky9 wrote:First try xdrvr=vesa confx at the GRUB boot screen. See here for a howto: http://www.mepis.org/docs/en/index.php?title=Cheatcodes
If you get to a logon screen we may modify this cheatcode to use an open 3D video driver.
The xdrvr=vesa confx cheats lucky9 posted are from Mepis 11, they won't do anything in Mepis 12. Warren never added the code/scripts to M12 that processes those cheats.KrispyKritter wrote:lucky9,lucky9 wrote:First try xdrvr=vesa confx at the GRUB boot screen. See here for a howto: http://www.mepis.org/docs/en/index.php?title=Cheatcodes
If you get to a logon screen we may modify this cheatcode to use an open 3D video driver.
I tried the cheat code and it got past the installation of cupsd. It appears after that there is a video setting change occur and I every thing goes black and it finally comes back with a blinking cuser. I even tried in safe mode. The screen resoulution was different and the results where the same. I did notice that in both cases there is a resolution change about half way to the point of black screen. This is a 2009 vintage Toshiba Laptop with a ATI motherboard (ATI Video card)
Steve
Did you try the "Safe Mode" boot option?KrispyKritter wrote:Well, I guess that is why it really didn't help. Got any more Ideas?
Steve
When you say "installation of cupsd", are you talking about some about message that mentions cupsd that flys by on the screen during the boot process?KrispyKritter wrote:Yes, The Screen Resolutions where different, but when it did what ever it does to the video after the installation of cupsd I got the same results.
Steve
Code: Select all
lspci -vnn | grep VGA
Code: Select all
cat /proc/cmdline
With the roadblock install, the nomodeset video=uvesafb:mode_option=640x480-24,mtrr=3,scroll=ywrap items are cheats, the Kubuntu install isn't using any though. I wonder if that video=blahblah cheat works with M12?KrispyKritter wrote:...No cheats needed...
oopsJerry3904 wrote:kernel is 3.12 in B2
The default Mepis kernel is 3.9.8-1 not 3.12,kmathern wrote:oopsJerry3904 wrote:kernel is 3.12 in B2
I tried that cheat code and it didn't work. I would expect this problem if I had a NVIDA card, but not with ATI. I am also surprised that the NVIDA people have not had any problems. If memory again serves me right the black screen usually would appear when the DVD first started loading and you could not even get to the boot screen.kmathern wrote:With the roadblock install, the nomodeset video=uvesafb:mode_option=640x480-24,mtrr=3,scroll=ywrap items are cheats, the Kubuntu install isn't using any though. I wonder if that video=blahblah cheat works with M12?KrispyKritter wrote:...No cheats needed...
I see that see the Kubuntu install is using a 3.11 kernel, have you tried MX-14? It also uses a 3.11 kernel.
I'm a bit confused (sorry if I have missed some important announcement that explains it all, but I have tried and looked around): does that mean that M12 has been abandoned and replaced with MX-14? Will there be a KDE version of MX-14? Or is there hope and we should just lie low and wait for the real McCoy? Again, sorry if this is completely obvious to the oldtimers, but I have been waiting for the new version for what feels like a very long time...uncle mark wrote:Don't count on it.malspa wrote:Is there any M12 development going on that anyone's aware of?
Warren has communicated that Mepis Linux is not dead. At the present time he is involved in time consuming activities like making a living. He will from time to time publish package updates, but when a final release will be issued is unsure.pindar wrote:I'm a bit confused (sorry if I have missed some important announcement that explains it all, but I have tried and looked around): does that mean that M12 has been abandoned and replaced with MX-14? Will there be a KDE version of MX-14? Or is there hope and we should just lie low and wait for the real McCoy? Again, sorry if this is completely obvious to the oldtimers, but I have been waiting for the new version for what feels like a very long time...uncle mark wrote:Don't count on it.malspa wrote:Is there any M12 development going on that anyone's aware of?
Thank you, that explains the status. So I will patiently wait and see if M12 gets released, sooner or later...richb wrote: Warren has communicated that Mepis Linux is not dead. At the present time he is involved in time consuming activities like making a living. He will from time to time publish package updates, but when a final release will be issued is unsure.
In the mean time several users are using the latest M12 beta as their daily OS.
You can install KDE on it with a single click, but there are no plans (and no interest AFAIK) to do a dedicated KDE version.Will there be a KDE version of MX-14?
kmathern wrote:With the roadblock install, the nomodeset video=uvesafb:mode_option=640x480-24,mtrr=3,scroll=ywrap items are cheats, the Kubuntu install isn't using any though. I wonder if that video=blahblah cheat works with M12?KrispyKritter wrote:...No cheats needed...
I see that see the Kubuntu install is using a 3.11 kernel, have you tried MX-14? It also uses a 3.11 kernel.
It's been out longer than that, the 11.9.92 isos were released on Aug. 10th, and the 3.9 kernel was added to Warren's repo in July.KrispyKritter wrote:It is strange that with this being out since October that no one has encountered this before me.
Steve
Please read this.johnnyhop wrote:Prepared usb stick with unetbootin. No problems booting in live mode and connecting to legacy wireless pci wireless adapter. Successfully tested software I routinely use and all hardware did fine. Then shut down, removed the wireless adapter and plugged in a much faster USB wireless adapter which needed a 3.x... kernal, booted up again and all was well connecting to wireless. Then installed to my 14gb test partition. After about two weeks was so pleased with the 12 beta performance the I decided to delete it from the test partition and install into the partition formerly running M11. After the fact noticed swap wasn't running after the install, swapon remidied that. I've had no crashes or other issues and wonder when 12 is expected to be updated to RC. I've yet to see any news on that subject, maybe haven't looked in the right place.
You already have MX-14 and M11 installed, but M11 is getting a little long in the tooth. Since you're having problems installing M12 beta, you would like an alternative OS (preferably with KDE) replace your aging M11. Am I correct?tascoast wrote:Just a brief query on M12 (SimplyMEPIS-1.5G_11.9.92_32.iso).
I have M11 and MX-14 dual booting just fine (Firefox update hanging in MX-14 but otherwise OK) and running VirtualBox for XP legacy purposes and previewing other distributions.
I have an additional 20GB partition prepared for a third OS but found the M12 disc responds very slowly, sometimes not even loading correctly to the login. While the 'live' features work fine when it is running, trying 'install' initially looks like it is loading but then nothing happens for many minutes and then, the install dialogue just seems to hang forever so I've ceased trying for now. I can't see any obvious answer here though I've had M12 running under VB before without problems. That said and still pondering another OS to install....(although I shan't be too worried if M12 doesn't want to install for now)
I would like to know if there's any news on M12 other than noted in this thread already, suspecting it might be a matter of patience, but further, any opinion re: if M12 would offer much else given the current setup noted above? My recent look at other linux distributions was less than encouraging in a search for a third system to install.
kindly
Mick
The fact there "could" be a place for desktop Linux isn't exactly a ringing endorsement. Maybe he thinks the days of desktop Linux and desktop computing in general are numbered, and mobile devices will take over.Warren wrote: "On the other hand, Windows 8 is biggest pile of crap operating system I have ever used. So, I’d say there could be a place for desktop Linux in the future, if we can figure out the new installation issues."
... and the MEPIS tools also. Without question, Warren led the pack with an easy-to-install and easy-to-maintain Linux system for the masses.uncle mark wrote: Note the multiple references to "installation". That was always a hallmark for MEPIS, and a point of pride for Warren.
The inspiration behind the MX tools!... and the MEPIS tools also
Firefox update hanging in MX-14 but otherwise OK
The only person who knows the answer to this question with any certainty is Warren.Dieselrider wrote:With the other projects in the works, is the final release of M 12 dead in the water now?
Our current development focuses on the exciting MX Linux, described below. Development of MEPIS itself is on indefinite hold, yet many users nonetheless run some form of MEPIS as their standard OS, and continue to find support and a friendly reception on the Community Forum.
Hey, someone asked... :lipsrsealed:Jerry3904 wrote:> SuSE Forum, right?