Page: 1, 2  Next

liquorix kernel 3.6 hangs on Cold-start
ringo32
Status: New User - Welcome
Joined: 01 Dec 2012
Posts: 1
Location: België
Reply Quote
after some try´s i can use liquorix kernel in my LMDE but on Coldstart of my pc it hangs and get different screen then i used be, is reads most of them find usb or something..

at first i change the grub and the startup screen to 640*480 and i removed the plymouth mayby gives some problem...

at cold start is hangs i must do then pc button of and then start again...

i have mayby a idea but i dont want make a mess..

can it be that i must put off the ACPI mode or something?
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1135
Reply Quote
Can you show us the output of inxi -bxx? Make sure to run inxi -U first to update the script.

And last, what happens when you try the 3.4 kernel in the past repository? You can access this branch by appending past to your liquorix sources line.
Back to top
djohnston
Status: Interested
Joined: 13 Dec 2012
Posts: 10
Location: Edmond, OK
Reply Quote
:: damentz wrote ::
Can you show us the output of inxi -bxx? Make sure to run inxi -U first to update the script.

And last, what happens when you try the 3.4 kernel in the past repository? You can access this branch by appending past to your liquorix sources line.


damentz,

I have the same problem with version 3.6.0-10. The boot sequence hangs. When I do a CTRL-ALT-DEL at the hang, the boot sequence goes back to the GRUB2 boot screen. nVidia drivers are loaded using packages from the Debian testing repo. I have /etc/default/grub configured as shown here: techpatterns.com/forums/about1516-10.html. The CPU is a 2gHz P4.

I installed the older 3.4.0-23 kernel and it's working. Where do I find the inxi script? The last few lines of dmesg from a failed boot attempt of 3.6.0-10 are shown below.

:: Code ::
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
loop: module loaded
smsc47m1: Found SMSC LPC47M10x/LPC47M112/LPC47M13x
ACPI Warning: 0x00000684-0x00000684 SystemIO conflicts with Region \RNTR 1 (20120711/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
NET: Registered protocol family 10
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
NET: Registered protocol family 17
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).


That's where it hangs.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
for inxi click the link in my signature
Back to top
djohnston
Status: Interested
Joined: 13 Dec 2012
Posts: 10
Location: Edmond, OK
Reply Quote
[root@DebLXDE32 ~]# inxi
CPU~Single core Intel Pentium 4 CPU (-UP-) clocked at 1993.559 Mhz Kernel~3.4.0-23.dmz.1-liquorix-686 i686 Up~12:45 Mem~368.9/2023.9MB HDD~520.1GB(9.0% used) Procs~118 Client~Shell inxi~1.8.24
[root@DebLXDE32 ~]#
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
no, show the full inxi: inxi -bxx

that gives any relevant system information that might be useful.
Back to top
djohnston
Status: Interested
Joined: 13 Dec 2012
Posts: 10
Location: Edmond, OK
Reply Quote
Okay.

:: Code ::
darrel@DebLXDE32:  10 items 208Kb -> inxi -bxx
System:    Host: DebLXDE32 Kernel: 3.4.0-23.dmz.1-liquorix-686 i686 (32 bit, gcc: 4.6.3)
           Desktop: LXDE (Openbox 3.5.0) dm: lightdm Distro: Debian GNU/Linux wheezy/sid
Machine:   System: Dell product: DIM4500 Chassis: type: 6
           Mobo: Intel model: D845EPT2 version: AAA83422-107 Bios: Intel version: A02 date: 05/22/2002
CPU:       Single core Intel Pentium 4 CPU (-UP-) clocked at 1993.559 MHz
Graphics:  Card: NVIDIA NV44A [GeForce 6200] bus-ID: 01:00.0 chip-ID: 10de:0221
           X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@50.0hz
           GLX Renderer: GeForce 6200/AGP/SSE2 GLX Version: 2.1.2 NVIDIA 173.14.35 Direct Rendering: Yes
Network:   Card: Intel 82541PI Gigabit Ethernet Controller
           driver: e1000 ver: 7.3.21-k8-NAPI port: dc00 bus-ID: 02:02.0 chip-ID: 8086:107c
Drives:    HDD Total Size: 520.1GB (9.0% used)
Info:      Processes: 113 Uptime: 22:45 Memory: 192.5/2023.9MB Runlevel: 2 Gcc sys: 4.7.2 alt: 4.6
           Client: Shell (bash 4.2.36) inxi: 1.8.24


Fri Dec 14 11:25:50 PM CST 2012
~
darrel@DebLXDE32: 10 items 208Kb ->
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
you're not using the right nvidia driver, you should be using the 304.64

I cant' say this is the cause, but it's an error, try to fix that then see if the kernel still hangs on boot.

Then nfs will be a question, but try running the correct nvidia driver first. The 173 series is for the 5xxx series of nvidia cards, not the 6xxx/7xxx series, that's the 304 driver.

sgfxi will install the proper one without any extra steps or commands.

if you get a hang with the correct nvidia non free driver, then I'd look at the nfs stuff, I've had some issues with that in the past.

After you install 304.64, you can run: sgfxi -! 40
and that will build modules for each kernel installed, so you don't have to install it to all the kernels. you can run that in X if you manage to boot to the 3.6 kernel.
Back to top
djohnston
Status: Interested
Joined: 13 Dec 2012
Posts: 10
Location: Edmond, OK
Reply Quote
:: techAdmin wrote ::
you're not using the right nvidia driver, you should be using the 304.64

I cant' say this is the cause, but it's an error, try to fix that then see if the kernel still hangs on boot.


You are correct. I installed the 304.48 nVidia drivers from the repo and rebooted to the older liquorix kernel. Then I booted again and selected the newest liquorix kernel. As you can see, it's working like a charm.

:: Code ::
System:    Host: DebLXDE32 Kernel: 3.6.0-10.dmz.1-liquorix-686 i686 (32 bit, gcc: 4.7.2)
           Desktop: LXDE (Openbox 3.5.0) dm: lightdm Distro: Debian GNU/Linux wheezy/sid
Machine:   System: Dell product: DIM4500 Chassis: type: 6
           Mobo: Intel model: D845EPT2 version: AAA83422-107 Bios: Intel version: A02 date: 05/22/2002
CPU:       Single core Intel Pentium 4 CPU (-UP-) clocked at 1993.547 MHz
Graphics:  Card: NVIDIA NV44A [GeForce 6200] bus-ID: 01:00.0 chip-ID: 10de:0221
           X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@85.0hz
           GLX Renderer: GeForce 6200/AGP/SSE2 GLX Version: 2.1.2 NVIDIA 304.48 Direct Rendering: Yes
Network:   Card: Intel 82541PI Gigabit Ethernet Controller
           driver: e1000 ver: 7.3.21-k8-NAPI port: dc00 bus-ID: 02:02.0 chip-ID: 8086:107c
Drives:    HDD Total Size: 520.1GB (9.0% used)
Info:      Processes: 117 Uptime: 6:06 Memory: 296.5/2023.7MB Runlevel: 2 Gcc sys: 4.7.2 alt: 4.6
           Client: Shell (bash 4.2.36) inxi: 1.8.24


I did look up the graphics card on nVidia's website and thought I had the right driver. After looking in Synaptic for the right driver, I noticed the nvidia-detect package which would have recommended the correct driver. Doh! I'm not a new Linux user, but I've only been using Debian for the last couple of months. I decided the try the liquorix kernel on this machine because you guys compile your kernels with ZRAM support. The Debian kernels don't have it enabled.

Thank you. I really appreciate your help. I would mark this thread as SOLVED, but I hijacked the thread instead of starting it.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
As the maintainer of sgfxi gfx installer script, one thing that really bugs me about the debian nvidia maintainers is that they haven't added in a very simple logic to the preinstall to check for the proper card id for the driver. This code is easy to find, it's gpl, and there's no reason not to do that, but they don't. Stubborn I'd guess.

Please note that only the 304 series will work, and there's no promise it will work on newer kernels.

304 already needs a patch to work on 3.7 kernels so be aware that the distro packaged drivers are not going to work as expected in all cases with non distro kernels like like liquorix. This is why I always use the direct driver install, from nvidia via sgfxi, not the debian packages.

By the way, now you can see why we ask to see inxi -bxx
there's no telling what might be happening and that shows the basic system so any obvious glitches can be noted.
Back to top
Display posts from previous:   
Page: 1, 2  Next
All times are GMT - 8 Hours