Slackware :: Kernel 2.6.35.7 Mouse/screen Freezes In -current?
Sep 30, 2010
so, I compiled the 2.6.35.7 kernel yesterday and used the config from 2.6.35.6 doing make oldconfig,etc
its the vanilla kernel with BFS, BFQ[*], Tuxonice, aufs2, & squashfs-lzma patches after compiling and rebooting I have noticed that the mouse freezes whenever the pc cpu is running high cpu % this didnt happen before with any other kernel and as I said, I used the 2.6.35.6 config Has anyone else had issues with 2.6.35.7 kernel? hardware is amd athlon64 3300+ 2.4ghz 1GB RAM, on 32bit Slackware -current I am going to compile the vanilla kernel now and see what happens.
I have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards.
I'm running slackware-current in a virtual machine on virtualbox 4, 512 mb ram, 1gb swap.Everything works fine, except the x11 mouse. Xfce will start up fine, and show the 'tips and tricks' dialog, and then freeze. I can't change to a TTY, or click. The mouse moves, but doesn't click.
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
So it's a beautiful day and I'll be happily using my computer when I realise that the screen is no longer showing that I'm typing or moving my mouse (or finger across a touch-pad). I can leave my computer in this frozen/crashed state for hours. My only recourse is to drain the battery or hold down the power button until the computer shuts down. The computer is a Dell Inspiron 6400 laptop/notebook. As my memory serves, it has an ATI graphics thingy. Radeon 1400, maybe. But I've had the computer for years and this behaviour has emerged only the past couple of months, with seemingly increasing frequency.
The OS is # uname -a Linux polaris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux (aka Squeeze?)
Sometimes this happens within minutes of turning the computer on and logging into Gnome. Sometimes this happens only hours after I've started using the computer (mainly just surfing the web). Sometimes it is preceded by a loud boop sound and the following if I have console open, sometimes not. So maybe that's unrelated. But that happened just now so I thought I'd throw it in.
One weird thing: Usually this happens within an hour of starting to use the computer, but one occasion I noticed I had not had the problem for several hours. On that occasion, the only thing I noticed I was doing that was also unusual: I had turned on and forgotten about a kvm virtual machine. After I shut down the vm, I had about only a minute before the freeze. I'm surprised now that it hasn't frozen since I started typing thing. Maybe I should always keep this forum open in a browser window.
I am trying to install fedora 10, 64 bit on computer with the following specification but the installation stops during installation (mouse , keyboard, screen freezes). Motherboard Gigabyte GA-MA790GP-ud4h rev.1.0 processor AMD phenom ii 940 I have updated the bios to the latest version.
I installed SalixOS on my laptop just to play with when I'm bored. My laptop is nothing special, it's a couple of years old has a pentium dual core t2390 at 1.86Ghz and 3 GB ddr2 RAM with Intel video.
I then have a beast i7 920 clocked to 3331Mhz 6GB RAM, and an NVIDIA GT220. Full screen ..... at 720p is fine unless I move the mouse, then the whole picture freezes. Persistant mouse movement will freeze the screen for a few minutes. This machine runs both slack64 current and slack13 32 bits.
The slack box does much better with 32 bit flash than 64, but it still doesn't do nearly as well as the laptop.
With Salix and Slack being so close to each other supposedly I can't figure out why the hardware seems to be irrelevant. The only thing I can think of would be the video codecs installed by Salix, whereas I built a bunch of codecs myself for Slack.
Sometimes, (the most when I'm making changes in something, like the pager, appearance, theme, etc), the screen freezes completely (but mouse is moving) and I have to restart the system.
I just upgraded my Slackware64-current version to the latest kernel 2.6.32.3. Almost everything works just fine, except that I have no sound on the command line and in web browsers, anymore. I don't get any sound out of the command line program play and Flash.
For example, I have a few .wav files, that I can play with Kaffeine and Amarok, but when I try to play them with play on the command line, the program runs and displays that it plays the file, but I don't hear any sound. The same happens with XMMS, too: It displays the usual graphics showing the dynamics and the progress, but my speakers remain silent.
Also, alsaconf doesn't detect my audio hardware, anymore. I have onboard sound and a Creative X-Fi PCI card. Usually both were "seen" by alsaconf. Now it tells me, that it can't identify any audio cards.
On the other hand, when I go into the multimedia section of the KDE system settings, I can "Test" the audio hardware, and the onboard sound works great and I can hear the KDE welcome sound. I have already remove all packages withe 'alsa' in their name and re-installed them, including their compat32 peers, and rebooted several times. Up to now to no avail. Does anyone have a clue, what the problem is caused by?
My screen is frequently freezing and even the keyboard or mouse doesn't work. I've been told to read the logs, But I don't know where thy are or what to look for?
I keep starting up the computer and I'm not able to get far (although it's not always at the same time) before my screen will go black, except it shows the mouse/cursor - but it's frozen, and then the caps-lock light starts blinking and I can't do anything or get it to recover. It ONLY occurs after I log in to wireless network. Using a wired connection, this problem never occurs.How do I stop this and diagnose this?I've tried, in the boot-startup to choose an older kernel version, but the same thing occurs! And this was working for months and now is not.
I am running Slackware64-current(multi-lib) and I have stumbled across something that I don't fully understand.I have read that the kernel-headers should not be updated as glibc is compiled against them and therefore requires that set of kernel headers. Recently the kernel version has been bumped a couple of times but glibc has stayed the same.Should glibc be re-compiled each time there is a kernel update?
Perhaps someone can explain, in very simple terms, the relationship between the kernel, the kernel headers, the kernel modules and glibc.
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is: /sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current. What i missing in kernel?
After all the package upgrading, removing obsolete packages, running lilo etc, I rebooted and I was really taken by surprise. Apparently, this certain intel graphics card doesn't work right with KMS. The boot process starts, I get to see the two tux twins and a few lines of boot messages, but as soon as KMS kicks in, everything goes completely blank. It doesn't crash or freeze or anything, the boot process continues, but it's all blank.
What's completely weird is that I have another laptop, which reports exactly the same graphics card, but KMS works fine there with current!
Anyway, I did some google search and I found that it's a common problem. There was a suggestion to remove any vga=... lines from lilo.conf, but that didn't help at all. Adding nomodeset to my boot options, disabled KMS, and I was able to boot to init 3, just like in 13.0. The problem was that then, it wasn't possible to launch X, because the intel driver that is included in current requires KMS to work!
So, after trying out a few different versions of the intel driver, I found that anything from 2.8.x and down wouldn't compile and that anything after and including 2.10.x require KMS. The only versions that would work are 2.9.0 and 2.9.1, which seem to have an identical effect here. They both work, but I have artifacts using my favorite mouse cursor theme, I get a black box instead of the mouse cursor. Not a big deal and choosing another theme fixed that too.
What I'm thinking is that probably more people will have the same problem and nothing is more frustrating than a completely blank screen. Maybe it would be a good idea to keep the 2.9.x versions of the driver in /extra. That and perhaps also add a note in the UPGRADE docs about adding nomodeset if you have an intel graphics card and you get a blank screen.
New build of Slackware 13.1 x86_64 in Dell E4310 laptop. The stock install works fine barring a few bits of hardware but after recompiling the kernel X loads and immediately freezes, whence I need to soft power down (I cannot switch back to a console). On capturing stderr from the command line, when executing startx I get various warnings including:(polkit-gnome-authentication-agent-1:2368): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failedCan't really tell if the above is relevant... Sorry I can't dump the lot because the machine isn't on the net yet.
There is nothing errorwise in the Xorg log after a reboot. The very last line relates to a video mode with modeline info etc. I have compiled either into the kernel, or as modules everything I think I need though unfortunately I seem to have to load them all manually, so I hav no idea of I've missed something important. This includes all the Intel drivers i915, drm, intel_agp etc.Googling suggests bugs with polkit and I don't know why gnome has anything to do with my system in any case.Other thing that I find annoying is that xorg.conf no longer exists and I am relying on the HAL daemon, about which I know nothing. It took me ages to find how to change the X keyboard map - very frustrating. How do I confirm which video driver etc.?
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
A while ago, I was applying the new kernel updates (I guess 2.6.32-24, or the one after it.. well, the latest generic update) and accidentally powered off my laptop. And now it wont come up. It comes to the logon page, and neither the keyboard, nor the mouse work. Cant even switch to the TTYs. When I boot with the recovery mode, I just see a black screen (probably the TTYs dont work) but after "processing" some time, nothing happens. Not sure if the keyboard works, as I cannot turn on/off the capslock switch, but ctrl+alt+del works
I have Fed 12, running on kernel 2.6.31.5-127.fc12.i686 I have newer kernels installed, but they will not boot into X.
The updater installed the kernel 2.6.32.21-166.fc12.i686. I can boot into runlevel 3. But if I then give the command startx, I almost get an x-window, I can see the top and bottom, ermm, wadjecallems, beams, but the screen is blank, and then the machine freezes. I can only switch off.
Some program's like Adobe Reader, Open Office and some other, when opening them, the screen is not readable an attachment )My hardware is:Code:00:02.0 VGA compatible controller:Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)It did not happen on the same hardware with OpenSuse or rhel5 installed
I installed Slackware 13.1 a little bit ago, played around with it, performed an upgrade with Slackpkg, messed around with some settings, and chose a new theme. I had set the runlevel to 4 and when I rebooted after choosing a new login theme the screen just went black at the point where the login prompt should have appeared. I couldn't even get into the CLI. Using a LiveCD, I set the run level to 3 again and was able to log in, but when I try to start X the screen goes black and freezes again, so I believe my new login theme is the culprit. Is there a way to change to the default login theme from the CLI?
I've upgraded from Slackware 11 to 12.2 and now my mouse cursor just sits there in the middle of the screen! I've managed (using the keypad to move the mouse cursor) to edit the /etc/X11/XF86Config config file, but all to no avail. I've googled for an answer but I don't understand all the talk about "blacklist". I've got a Pentium 4, 101 keyboard, ps 2 mouse.
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it.
I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect.
I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try?
I just recently installed Slackware onto a virtual machine(I'm planning on buying a new disc drive and 1 TB HDD with-in the next couple of months and plan on Slackware being my primary OS[right now Mac OS X 10.6 is]), and everything went great.
I then went onto edit the /etc/inittab file in emacs and changed the run-level to 4. I don't know why it's decided that I'd want to boot into KDE when XFCE is installed and in the configuration I selected XFCE but it's not really relevant(I have a WM guide thing open in another tab and will probably be able to change it).
The problem is, as the vague title may suggest, is that it basically freezes when I'm at the log-in screen. The input field for the username is highlighted and blinking, and the cursor it self is visible in the centre of the screen, but it simply doesn't pick up on any input from my keyboard or mouse.
I tried booting up the install CD and logging in as root, mounting sda4(which is the root partition) and editing said file but sudo isn't installed(to my knowledge) on the install disc and when I do the command,
Full install of slackware. then i use these instructions to install drivers:
Quote:
Install nvidia driver in Slackware Linux
Before begin the nvidia driver installation, you must make a copy of the original /etc/X11/xorg.conf as a backup. Use the copy command example below:
If you choose to install the nvidia driver that you download from nvidia website, you must close kde or x-window and install the driver from Linux command line terminal.
Copy the driver to the directory that you placed all third party software such as /usr/local/src. This is not necessary, just a good habit. To install the driver, run the nvidia driver with the sh command like in the example below.
Now, you just need to answer all the questions to configure nvidia driver and the nvidia installation program will do the driver and kernel installation for you.
When i startx the computer freezes with an underscore in the top left hand of screen and i can't switch between tty's.
I know the pc and card work fine with other linux and win os's.
slackware and am infact running Vector Linux which is slackware based. I used to use fedora on my old laptop got a new on and tried vector. The mouse on the new one doesn't seem to want to work properly, it jumps alot and usually ends up at the end of the screen unable to move, however does manage to click almost every icon on the screen and change desktops.A USB mouse works fine its just the touchpad.It's a Zoostorm Freedom and I can't even find the windows drivers for it let alone what i need for this. I tried editing the xorg.conf to stop the tab button, which doesn't do anything, installed the latest synaptics and still nothing, tried using what someone else uses and still nothing, I cant even find out what kind of mouse it is!?
