You are not logged in.
I install the latest arch. Everything goes well. I boot into my new system and "pacman -Syu". I reboot and I'm greeted with a completely white screen.
Manufacturer Samsung
Model name Q1 Ultra
Model id Q1U-CMXP
CPU type Intel A110 (Stealey)
CPU speed 800 Mhz
Graphics Intel GMA 950
Display Size 7" 1024 X 600
RAM 2048 MB
Offline
What is the version of your kernel?
Offline
Have you tried disabling kernel mode setting?
Add "nomodeset" to your kernel's bootline. That way you can at least boot the machine and probably use it, so you can solve the problem. Or try to disable early KMS and switch to late KMS, read the wiki for that one.
I don't have a machine near me with an GMA950, so I cannot try anything or know he specific stuff. But I do know that the Intel driver is being rebuilt for a great deal and can sometimes vomit.
Offline
kernel26 2.6.32.7-1, basically the initial install kernel works fine but an -Syu borks the whole system to unusability.
I've been reading solutions to 855 problems and was about to give the nomodeset option a try. From my research it seems to be an upstream patch to the kernel itself causing the problems hence all of the x won't start threads. I was thinking that perhaps an lts kernel could be the solution but then when it gets updated I'm back to square one.
Stay tuned. I won't be able to work on this until the weekend.
Offline
Can you post your menu.lst?
Offline
If this is a NEW system as in brand new.. X wouldnt be set up since X doesnt come with arch core! Unless you created a custom iso with X and your associated drivers. If this is the case.. wouldnt he need to re run depmod -a to update his modules for 7-1? I purposely disable upgrading my kernel after the first full system upgrade when installing arch because of module issues. Im still running .32-2-1..
Registered User number: 496613. Show your Tux Pride!
http://counter.li.org
Offline
This is a new system as in brand new. Nothing set up but the install. If I do not upgrade the kernel, everything is good. If I -Syu and reboot with the stock kernel I get the white screen. I have temporarily solved the issue by booting into an installed lts kernel. I've managed to get a usable openbox running with the touchscreen actually working last night. I'm not going to mark this solved as the stock kernel still exhibits the bad behavior. I'm going to work on this more this weekend and see if disabling kernel mode setting does anything. I'm still suspicious of a patch that was merged and is giving everyone with 855 chips fits. I haven't often compiled my own kernels but in this case I believe it might be appropriate given the specialized nature of this particular device.
Offline
Weird.. cause in a base system install you dont have X.. i wonder why it would have an issue getting you to TTY7? Have u tried switching to other TTYs?
Registered User number: 496613. Show your Tux Pride!
http://counter.li.org
Offline
I don't have X at the time but it doesn't matter. This happens before or after I install X on the system if I update the system. X has nothing to do with this one whatsoever, I'm fairly sure it's a kernel issue of some sort.
Offline
Weird.. cause in a base system install you dont have X.. i wonder why it would have an issue getting you to TTY7? Have u tried switching to other TTYs?
With KMS, it doesn't matter if he has X or not. X and the console use the same graphics modes when KMS is used.
Offline