Page: 1, 2, 3, 4  Next

Liquorix failed on netbook
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 292
Location: South Florida
Reply Quote
Installed Wheezy on netbook Acer Aspire One.
Installed from nightly build business card CD.
Everything OK, did basic install, then installed smxi OK.
Proceeded to install liquorix, made it default.
Complete fail on boot, had to boot into Debian kernel OK.
Reinstalled liquorix from smxi, same problem, complete failure after second line: module unix not found.
This is normal because Debian kernel also does that, but it continues whereas liquorix does not.
I will continue investigating this in the evening, gotta go now.
In the meantime, please let me know all the info you need: dmesg, lshw, etc.
Will post everything you need to troubleshoot issue.
Thanks.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 292
Location: South Florida
Reply Quote
Installed latest kernel on said netbook.
3.2.0-4.dmz.1-liquorix-i686.
Same old, kernel crashes after second line, no boot.
Had to revert to Debian kernel, OK there.
Purged liquorix kernel and sources, set default to Debian.
Still no answer...
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
He needs to see: inxi -Fx

to see everything in the system, that's always the case, no exceptions. Also don't ever expect anyone to remember a system from some other posting, ie, always post this data so that damentz knows everything he needs to know about your hardware.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 292
Location: South Florida
Reply Quote
:: Code ::

root@littledeb:/home/ckosloff# inxi -Fx
System:    Host: littledeb Kernel: 3.1.0-1-686-pae i686 (32 bit, gcc: 4.6.2)
           Desktop: KDE 4.6.5 (Qt 4.7.4) Distro: Debian GNU/Linux wheezy/sid
Machine:   System: Acer product: AOA150 version: 1 serial: LUS050B225906049632547
           Mobo: Acer model: N/A Bios: Acer version: v0.3310 date: 10/06/2008
CPU:       Single core Intel Atom CPU N270 (-HT-) cache: 512 KB flags: (nx sse sse2 sse3 ssse3) bmips: 3191.96
           Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics:  Card: Intel Mobile 945GME Express Integrated Graphics Controller bus-ID: 00:02.0
           X.org: 1.11.3.901 drivers: intel (unloaded: fbdev,vesa) tty size: 80x35 Advanced Data: N/A for root
Audio:     Card: Intel N10/ICH 7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture ver: 1.0.24
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
           driver: r8169 ver: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) driver: ath5k bus-ID: 03:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 160.0GB (-) 1: /dev/sda Hitachi_HTS54321 160.0GB 40C
Partition: ID: / size: 146G used: 3.7G (3%) fs: rootfs ID: / size: 146G used: 3.7G (3%) fs: ext4
           ID: swap-1 size: 1.50GB used: 0.00GB (0%) fs: swap
Sensors:   System Temperatures: cpu: 57.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 150 Uptime: 51 min Memory: 283.5/996.5MB Runlevel: 5 Gcc sys: 4.6.2 Client: Shell inxi: 1.7.28
root@littledeb:/home/ckosloff#

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
thanks, forgot for public posting requires the -z to filter out data that shouldn't be public, ie: inxi -Fxz

but I edited your output so that's fine.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1117
Reply Quote
What happens when you boot to the liquorix kernel? All you explained was that it failed, which doesn't provide me any information at all, other than it's the opposite of working. If you're getting no screen output, try booting with the nomodeset kernel parameter.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 292
Location: South Florida
Reply Quote
"Reinstalled liquorix from smxi, same problem, complete failure after second line: module unix not found."
Posted feb 3., please read in its entirety.
Tried to post a dmesg with error, but could not find any after booting into Debian kernel.
I really don't know how to help since I cannot take a screenshot of a computer that does not boot and will eventually go into a prompt like this:
initramfs>
Please post instructions as to how to boot with nomodeset kernel parameter.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1117
Reply Quote
Well, nomodeset won't help here. It looks like linux can't find your root partition. From a working kernel, can you show us the output of /boot/grub/grub.cfg? Output from /etc/fstab would help us too.
Back to top
ckosloff
Status: Contributor
Joined: 21 Dec 2011
Posts: 292
Location: South Florida
Reply Quote
:: Code ::

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
  insmod part_msdos
  insmod ext2
  set root='(hd0,msdos2)'
  search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
  set locale_dir=($root)/boot/grub/locale
  set lang=
  insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.1.0-1-686-pae ...'
   linux   /boot/vmlinuz-3.1.0-1-686-pae root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro  quiet
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.1.0-1-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 3.1.0-1-686-pae (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
   insmod gzio
   insmod part_msdos
   insmod ext2
   set root='(hd0,msdos2)'
   search --no-floppy --fs-uuid --set=root 9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9
   echo   'Loading Linux 3.1.0-1-686-pae ...'
   linux   /boot/vmlinuz-3.1.0-1-686-pae root=UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 ro single
   echo   'Loading initial ramdisk ...'
   initrd   /boot/initrd.img-3.1.0-1-686-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda2 during installation
UUID=9e1d76a5-c1b1-4caa-ae19-7b36d95c7dd9 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda1 during installation
UUID=6baa93cc-2bd5-4f0e-9ffb-5d104447a148 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Let's see: inxi -plu

just to confirm that the partitions match, although they'd really have to match for it to boot, but let's see.

That unix error you can ignore, I see that on some recent test installs, second line, like you say, so I don't think that''s related.

I don't believe that kernel logging is running at this point of the boot process, so you won't see anything in the kernel or dmesg logs.
Back to top
Display posts from previous:   
Page: 1, 2, 3, 4  Next
All times are GMT - 8 Hours