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.
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?
Here goes the problem: I have a Amilo M7400 notebook with an Intel 82852/82855 GME video card, and X is a bit uncompatible with it.I've tried using the vesa driver in the xorg.conf, but when i start Xserver, it hangs hard in a blank screen. I can't open a new terminal and control+alt+backspace won't work.
what can i do? is there a log file for X which details the initialization of it?
When i checked last time couple months back glx gears gave me 1400 frames around now i get
Code: glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate.
21 frames in 6.6 seconds = 3.160 FPS 2 frames in 5.6 seconds = 0.359 FPS 84 frames in 5.8 seconds = 14.362 FPS 149 frames in 5.0 seconds = 29.724 FPS 300 frames in 5.0 seconds = 59.814 FPS and everything is running slow im wondering where the problem might be? code....
I am using the most recent -current (that fixes the libpng "ratness" described in the ChangeLog 8-) and the Intel Framebuffer setup is annoying me. I specify vga=normal in LILO and to my knowledge I am not asking Intel Framebuffer modules to load at boot (and intelfb is blacklisted).
It's annoying because it makes the text microscopic. However, the machine works great in -Current so I can't complain. Graphics work fine and so does X, it's just annoying.
This is my Sony Vaio VGN-C140G detailed here: url
I had tried previously blacklisting inteldrmfb as well (the -Current release right before the libpng fix) and that made no difference.
I found all binaries with "intel" in their name and read the manual pages but didn't find anything useful for possibly manually setting the mode back to something equivalent to vga=normal.
I just bought a new Dell Studio Laptop with Intel i5 64 bit processor with Windows 7. I installed ubuntu with in my Windows 7 through CD and also tried to run it by installing it on Pen drive. But it just boots perfectly but get stuck with blank screen after that.
I have just received my new laptop - a Thinkpad x121e, with Intel (Core i3).
I am trying to put ubuntu on it, but i am having some problems with the 64 bit live USB.
When i run the USB i get i get a GRUB-looking screen, with options to:
Quote:
1. Try Ubuntu without installing 2. Install Ubuntu 3. Check the disk for errors
Wanting to repartition my hard drive (using GParted) so that i can dual boot, i Quote:
Try Ubuntu without Installing
, at which point the screen goes blank and nothing happens. I am then forced into a hard reboot. I get the exact same result when i pick
Quote:
Check the disk for errors
from the GRUB-like screen
To check the live USB, i tried it on my old laptop (32bit, Celeron M). When i did so i got a purple screen with an image of what looks like a keyboard and a man at the bottom, and then a message telling me to try a kernel which matches with my machine's architecture.
I then tried a live USB with 32 bit ubuntu and the live USB works fine - i am sending this email from this live instance running on my new Thinkpad. The same can be said for a 32 bit Mint live usb which also worked on the Thinkpad.
So i am not sure what is going on. If anyone could tell me why the 64bit live USB is not working, it would be great as i'd like to get it up and running. The only thing i could think of was that i have downloaded the amd64.iso, and this is an intel machine. Having said that i see that all the sites on the web suggest that this shouldn't make a difference (if it does, where might i get an 64 bit version for intel). In addition i am not sure why, if this was the problem, my old celeron laptop brings up the error message while the new machine just hangs.
I have a new Dell Latitude e5510 with Intel integrated graphics processor in I3, the model should be something like HD mobile Intel GMA integrated graphics (not able to find more precise details even under Windows using everest).
Trying to install Ubuntu 10.04 from livecd this returns me a black screen after I choose to try ubuntu. I already tried to use options as well nolapci nomodeset but without results. The screen lights up the backlight is on and I go into kernel panic because starting to cycle on and off repeatedly icons keypad lock and block number.
I've been trying to install 5.5 here for the past few days, first from USB and now from the CDs, with no success. The problem occurs when I reboot after installing. After the BIOS has done it's thing I'm faced with a blank screen with a blinking cursor at the top left of the screen.
Initially I assumed that this was due to the intel driver problem which is reported in the release notes as a known issue, and the PC I'm installing on has intel graphics. However I have now done a text install and still have the same issue. I'm able to boot up the system using the CentOS live CD, which encounters no issues, and it mounts the local system no problem. After unmounting and remounting to get write access I'm able to change the device entry in /etc/X11/xorg.conf to have the Option "DDC" "false" entry. I can also see that the runlevel is set to 3 in /etc/inittab, still I get the blank screen on attempting to boot.
Any ideas on what might be wrong here? It really sounds like the intel driver problem people have described, and yet I can't even boot in text mode so that doesn't seem to be the case here. Could there be something wrong with the bootloader?
I have a new laptop, I first installed Debian stable, but the wifi card didn't work, and the screen was 1024x768. So I installed kernel up to 3.16 with wheezy-backports, but after the boot, the screen become blank. The only way to see the screen is set "nomodeset" in /etc/default/grub, but It's impossible to see the screen beyond 1024x768 resolution.
I also tried to install linux-image deb packet from [URL] .... , because it worked for someone in internet, but not for me.
I've downloaded 10.04 desktop (twice) and server (once). The server install will boot fine, but the desktop install goes to a blank screen (and the monitor goes to sleep) after leaving the Live CD menu (Run from CD, Install, Check Files, Boot 1st HD, etc.).My first try at downloading the desktop CD was using BitTorrent, and appeared to go OK. Burned the .iso image, booted, and when I got the blank screen I suspected the Intel D101GGC motherboard using the Radeon Xpress 200 chipset had problemsI tried adding boot options (F6) such as vga=711 and xforcevesa and text. No joyOthers seemed to have gotten a successful install so I turned may attention to the CD, suspecting it was a bad download/burn, and downloaded 10.04 desktop again from mirror.pnl.gov/releases/. The two .iso images compared equal, so I used a different CD burner, with different media and got CDs which compare identical. Both CDs fail. Then I downloaded the server CD from PNL and it ran! I could select the "test CD" function, which ran in a text mode and said the server CD was OK. I started the install, and it went OK.
I bought a Intel DQ45CB LGA Q45 Micro ATX Motherboard and I am installing the 64 bit version of centos.
The install of Centos goes just fine. However when I first try to boot up, after post is done, I get a blank screen. I do not even get on the Grub screen. No access to any of the ttys. No access to anything, files, folders. I only get a blkinking cursor, no command prompt, nothing.
This happened with Centos 5.2 and 5.3
Just for the hell of it, I installed XEN Xitrix and I have no issues like that.
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 have been unable to get both opensuse 11.2 and 11.3 32 bit versions work properly on my DELL Latitude E6410 laptop. With both 11.2 and 11.3 KDE Live CDs I get no graphical display when I attempt to boot into the Live system. VESA mode does not help either, only text mode works. So I installed the system in text mode but during the first boot the screen went blank again.
One peculiar thing is that 11.1 installs and boots fine, what gives? Is this even supported or I shouldn't even try to bother getting this setup to work? Has anyone been able to run opensuse 11.3 on a Core i7 integrated Intel graphics system with X system working?
I have a clean install of slackware 13.37, downloaded today from slackware64current. On boot, I get a black screen - not just black, but no video signal out of the video card, or at least nothing that the monitor recognizes. Fortunately, I can ssh into the box from another machine. If I do, I can startx and xfce starts up and appears as expected. lspci shows:
01:05.0 VGA compatible controller: ATI Technologies Inc Device 9714 02:00.0 VGA compatible controller: ATI Technologies Inc Device 6898
I have an onboard video chipset with a monitor connected to it, and an ATI 5970 in a pcie slot with a monitor also connected to it. xfce appears on the pcie card (the 5970) as expected, as this is (supposedly) the primary monitor, and the monitor connected to the onboard video output is blank - no signal, also as expected as I have not yet installed the ATI drivers. So the question is - how do I get the terminal output on bootup to appear on one of my monitors? I'm not sure where it is going, and this is out out of my area of expertise.
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.
When she wants to log into xfce, there is only a blank screen. The cursor shows, but there is no way to go any further. No panel, buttons or background.
However, she is able to log in using XDMPC from a local computer without a problem.
There are the processes active under both settings.
Questions: What may have caused xfce not to load some modules on log in? How to fix it, to allow a normal login? How to prevent this problem in the future?
Slack 13.0 X sometimes fails to start after boot about 50% of the time. linux says "starting X11 session" then I get a blank screen with a flashing cursor and absolutely nothing else. I can <ctrl>-<alt>-<F7> and get a text prompt, log in, and startx from a command prompt. After that, I can reboot once or twice and still get a graphic login, but will soon revert to the dumped condition. I have reinstalled X and KDE twice now as well as deleting my .kde folder. This condition started when I inadvertently ran out of disk space on my /home drive. Since then I have migrated /home to a larger drive and watch it's disk space very carefully.
Just upgraded my system from 13.0 to 13.1 Most things went pretty smoothly, but I tried 'startx' before the post-upgrade/config reboot and the system hung - "time to upgrade my video drivers", I thought. Upgraded to Nvidia 195.36.15*. X works perfectly, and a modprobe shows the 'nvidia' module loaded. So far so good.
However, when I try to use any vesa modes in lilo, I get a blank screen after the BIOS check and the system hangs - even toggling numlock on or off won't work... So I can only boot up in text mode. This makes me unhappy, partially because I like penguins, but also because it is an absolute insult to my new (old) monitor. I thought this could be to do with the nouveau conflicts reported by -current users some days ago, but the respective blacklist file is present so I'm stuck as to what to do... *I've tried 195.36.15, 195.36.24 and the latest 2xx beta drivers. All exhibit the same behaviour.
EDIT - forgot to post my video card specs. It's an 8500gt w/ 256mb, 128-bit DDR3.
I am having the same problem, as soon as X tries to load my screen just goes blank. I have an ATI Radeon 9550. At first I tried switching between VGA and DVI as well but upon ruling that out, I switch to my on-board video card and that is working thus far, but I'm trying very hard to figure out a way to be able to switch back. Anyways I'll check back in later on if I have any new information I will post.
When i use my computer (whether it's going online, typing, playing a flash game, or coding) I get these "Black Flashes" that are becoming longer and more frequent. A "Black Flash" is when my computer screen turns blank (but you can still see the backlight) and i have to press the NUMpad ENTER button, shake my mouse furiously, or click my mouse, which sometimes causes undesired actions, but gets me my screen back. sometimes the Black Flashes last a milisecond or 5 seconds or i have to hold the power button and restart because it won't come back on.
I am running Lucid Lynx and have only noticed this problem in the past couple weeks. Before Lucid I ran Jaunty & Karmic on this same box, although I installed Lucid as a clean install. My problem is that up to 5 or 6 times per minute my networking card drops its connection and then has its connection re-established. I have an integrated Intel 82566DC gigabit card on an Intel Motherboard DG35EC connected to a 10/100 network and am running the 64-bit version of Lucid. I've done some considerable searching on this problem and although I've seen many references to similar problems dating back several years, I have found none that seem to have any solutions that do anything for me. I never had this problem under any prior version of Linux on this box (all prior versions were also 64-bit).
In short, this block of messages repeats in my messages log:
May 18 20:18:50 mark-desktop kernel: [10121.062129] e1000e: eth0 NIC Link is Down May 18 20:18:52 mark-desktop kernel: [10122.730873] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX May 18 20:18:52 mark-desktop kernel: [10122.730876] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
Most of the time I don't even see that the connection has gone down. Sonetimes everything seems to be operating fine for a half-hour or more, although it could be dropping out and coming back really quickly all of the time. Sometimes it goes out for 10 seconds.Sometimes it goes out for many minutes and I can get networking back by killing disabling networking and then re-enabling it. It's quite annoying.
I'm sorry if I'm duplicating an existing issue on this forum, but I can't find this exact problem anywhere. Does anyone have any clever ideas about how to fix this?
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
Installpkg will no longer work, complaining that the rev command is not found. The problem hit with the removal of util-linux-ng. I cp'd util-linux to ~/. Extracted with tar and executed the doinstall. Fixed.
after update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element err:alsa:wine_snd_pcm_recover underrun occurred err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
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??
