v1.1 won't boot into "always fresh", v1.0 will

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
nickh
Black ninja
Black ninja
Posts: 45
Joined: 07 Mar 2011, 20:56
Location: UK

v1.1 won't boot into "always fresh", v1.0 will

Post#1 by nickh » 06 Feb 2012, 17:01

I have an odd problem on one of my PC's. I can boot v1 successfully into KDE or always fresh mode. I cannot boot v1.1 into "always fresh", but I can boot v1.1 into KDE as long as a save.dat has been created (clearly on another PC). I have attached a psinfo if it will help. The problem is not particularly urgent as it is now booting.

Code: Select all

----------------------
Output from psinfo
----------------------
script by jayflood
.
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: i686
Kernel: 2.6.38.8-porteus
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz
Base Board Information
	Manufacturer: Intel Corporation              
	Product Name: D865PERL                       
MemTotal:        1031392 kB
MemFree:          252264 kB
Bootparam: root=/dev/ram0 ramdisk_size=6666 rw initrd=/boot/initrd.xz vga=791 autoexec=xconf;telinit~4 changes=/porteus/save.dat toroot BOOT_IMAGE=/boot/vmlinuz 
.
===== SOUND INFO =====
Sound card:  0 [ICH5           ]: ICH4 - Intel ICH5
                      Intel ICH5 with AD1985 at irq 17
 1 [Bt878          ]: Bt87x - Brooktree Bt878
                      Brooktree Bt878 at 0xf4000000, irq 17
Sound driver: Advanced Linux Sound Architecture Driver Version 1.0.23.
.
===== PARTITION INFO =====
Porteus is on: /mnt/sdb1
.
Partitions: 
sda
sda1
sda2
sda3
sdb
sdb1
.
Mounted: 
/dev/sda1      fuseblk   74G   24G   51G  32% /mnt/sda1
/dev/sda2      fuseblk  198G   46G  152G  23% /mnt/sda2
/dev/sda3      fuseblk  196G  2.3G  194G   2% /mnt/sda3
/dev/sdb1      vfat     7.6G  3.1G  4.5G  42% /mnt/sdb1
.
===== OPTICAl DRIVE =====
sr1
.
===== USB INFO =====
Removables: U3
Removable status: sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd7:0:0:0:[sdc]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd11:0:0:0:[sdc]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd11:0:0:0:[sdc]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd0:0:0:0:[sda]Protect
sd10:0:0:0:[sdb]Protect
sd2:0:0:0:[sda]Protect
sd4:0:0:0:[sdb]Protect
.
lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0781:5406 SanDisk Corp. Cruzer Micro U3
Bus 002 Device 002: ID 062a:0003 Creative Labs 
Bus 003 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
.
===== SCREEN INFO =====
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
.
===== MODULES LOADED =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
003-lxde.xzm
004-kde.xzm
005-kdeapps.xzm
006-koffice.xzm
007-devel.xzm
008-firefox.xzm
ekiga-3.2.7-i486-njh.xzm
iproute2--2.6.35--0.1.3.xzm
kvpnc--0.9.6--0.1.3.xzm
openvpn--2.1.3-2--0.1.3.xzm
.
===== NETWORK INFO =====
eth2      Link encap:Ethernet  HWaddr 00:0E:0C:DC:C7:6F  
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::20e:cff:fedc:c76f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:21 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2050 (2.0 Kb)  TX bytes:1824 (1.7 Kb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
.
# Generated by dhcpcd from eth2, eth0, eth1, wlan0
# /etc/resolv.conf.head can replace this line
search howitts.lan
nameserver 192.168.2.1
nameserver 208.67.222.222
nameserver 208.67.220.220
# /etc/resolv.conf.tail can replace this line
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
	Subsystem: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface
	Kernel driver in use: agpgart-intel
	Kernel modules: intel-agp
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
	Kernel modules: shpchp
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: uhci_hcd
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: uhci_hcd
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: uhci_hcd
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: uhci_hcd
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
	Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
	Kernel modules: intel-rng
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: ata_piix
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
	Subsystem: Intel Corporation D865PERL mainboard
	Kernel driver in use: Intel ICH
	Kernel modules: snd-intel8x0
01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1)
	Subsystem: nVidia Corporation Device 030c
	Kernel driver in use: nouveau
	Kernel modules: nouveau, nvidiafb
02:01.0 Communication controller: Conexant Systems, Inc. HCF 56k Data/Fax/Voice Modem (rev 08)
	Subsystem: Conexant Systems, Inc. HCF 56k Data/Fax/Voice Modem
02:02.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
	Subsystem: Hauppauge computer works Inc. WinTV Series
	Kernel driver in use: bttv
	Kernel modules: bttv
02:02.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
	Subsystem: Hauppauge computer works Inc. WinTV Series
	Kernel driver in use: Bt87x
	Kernel modules: snd-bt87x
02:03.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
	Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
	Kernel driver in use: e1000
	Kernel modules: e1000
02:04.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 04)
	Subsystem: Agere Systems FW322/323
	Kernel driver in use: firewire_ohci
	Kernel modules: firewire-ohci
.
.
===== LOGS INFO =====
dmesg | tail 
.
[   52.161407] [drm] nouveau 0000:01:00.0: allocated 1280x1024 fb: 0x49000, bo edc35c00
[   52.161613] fbcon: nouveaufb (fb0) is primary device
[   52.161898] Console: switching to colour frame buffer device 160x64
[   52.161915] fb0: nouveaufb frame buffer device
[   52.161919] drm: registered panic notifier
[   52.161935] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[   56.184972] [drm] nouveau 0000:01:00.0: 0xD2C1: Parsing digital output script table
[   56.235031] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on tmds encoder (output 2)
[   56.235038] [drm] nouveau 0000:01:00.0: Output DVI-I-1 is running on CRTC 0 using output A
[  113.978820] start_kdeinit (2798): /proc/2798/oom_adj is deprecated, please use /proc/2798/oom_score_adj instead.
.
.
cat /var/log/messages | tail
.
Feb  6 15:49:14 (none) kernel: [   51.986704] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on tmds encoder (output 2)
Feb  6 15:49:14 (none) kernel: [   51.986734] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on TV encoder (output 3)
Feb  6 15:49:15 (none) kernel: [   52.161407] [drm] nouveau 0000:01:00.0: allocated 1280x1024 fb: 0x49000, bo edc35c00
Feb  6 15:49:15 (none) kernel: [   52.161613] fbcon: nouveaufb (fb0) is primary device
Feb  6 15:49:15 (none) kernel: [   52.161915] fb0: nouveaufb frame buffer device
Feb  6 15:49:15 (none) kernel: [   52.161919] drm: registered panic notifier
Feb  6 15:49:15 (none) kernel: [   52.161935] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
Feb  6 15:49:19 (none) kernel: [   56.184972] [drm] nouveau 0000:01:00.0: 0xD2C1: Parsing digital output script table
Feb  6 15:49:19 (none) kernel: [   56.235031] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on tmds encoder (output 2)
Feb  6 15:49:19 (none) kernel: [   56.235038] [drm] nouveau 0000:01:00.0: Output DVI-I-1 is running on CRTC 0 using output A
..

User avatar
fanthom
Site Admin
Site Admin
Posts: 4548
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#2 by fanthom » 07 Feb 2012, 02:36

does this info really come from Porteus-1.1? if yes then your installations are mixed up somehow as we have kernel-3.1.8 in 1.1 while i see 2.6.38.8 (the one from 1.0) in psinfo output.
Please add [Solved] to your thread title if the solution was found.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#3 by brokenman » 07 Feb 2012, 11:30

Yes it looks to me as though you only replaced the 'Porteus' folder and left the older 'boot' folder from v1.0. There were substantial changes between the two versions and you shouldn't mix and match them.

Please try again using the 'porteus' and 'boot' folder ONLY from the v1.1 ISO.
How do i become super user?
Wear your underpants on the outside and put on a cape.

nickh
Black ninja
Black ninja
Posts: 45
Joined: 07 Mar 2011, 20:56
Location: UK

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#4 by nickh » 07 Feb 2012, 13:16

No. The information comes from 1.0 as at the time it was the only way I could boot the PC and I produced it while I was fiddling with 1.1 on my laptop to set up it's save.dat. Only after that could I start the PC with 1.1 but I did not think to produce the hwinfo report again. If you want, I can run it again from 1.1 when I get home but I would not have thought it would change the hardware info.


[edit]
I now cannot get the PC to boot into v1.1 at all so perhaps I was mistaken yesterday when I said it would boot into 1.1 when the save.dat had been created. I cannot, therefore, produce a v1.1 psinfo report.
[/edit]

User avatar
fanthom
Site Admin
Site Admin
Posts: 4548
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#5 by fanthom » 07 Feb 2012, 22:06

hello nickh,
I now cannot get the PC to boot into v1.1 at all so perhaps I was mistaken yesterday when I said it would boot into 1.1 when the save.dat had been created.
that makes sense now.
I cannot, therefore, produce a v1.1 psinfo report.
please provide following info:
a) at what stage booting stops (i'm interested in the last line printed on the screen)
b) where your porteus installation is located. i need to know full path to 'porteus-1.1-i486.sgn' file (like /mnt/sdb1/porteus/porteus-1.1-i486.sgn)
c) cheatcodes you are using for porteus-1.1 (/boot/porteus.cfg uploaded to pastebin.com would be handy)
Please add [Solved] to your thread title if the solution was found.

nickh
Black ninja
Black ninja
Posts: 45
Joined: 07 Mar 2011, 20:56
Location: UK

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#6 by nickh » 07 Feb 2012, 22:17

a) It stops at the stage "Triggering udev events: /sbin/udevadmin trigger --action=add"
b) It would be /mnt/sdb1/porteus/porteus-v1.1-i486.sgn assuming the PC's hard disk is sda
c) porteus.cfg

User avatar
fanthom
Site Admin
Site Admin
Posts: 4548
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#7 by fanthom » 07 Feb 2012, 22:32

ok so your setup is fine, just kernel gives a usual headache while loading modules.
please give a try to new kernel (3.2.4) which i compiled for 32bit arch:
http://porteus.org/forum/viewtopic.php? ... 1024#p7796
(make a backup of all files which you are replacing first)

if that wont help then please go back to original 1.1 setup and boot to text mode. you will get "/sbin/udevadmin trigger" hang once again so please wait couple minutes (up to five) till it moves on.
once you reach login prompt please login and save /var/log/dmesg somewhere and upload on pastebin.com when you get back to Windows.

we need to hunt down kernel module which is causing troubles and kill it in fire.
Please add [Solved] to your thread title if the solution was found.

nickh
Black ninja
Black ninja
Posts: 45
Joined: 07 Mar 2011, 20:56
Location: UK

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#8 by nickh » 08 Feb 2012, 20:02

The new kernel will not boot either, but booting into KDE after the line "Triggering udev events: /sbin/udevadmin trigger --action=add" once I got a further error message:

Code: Select all

udevd-work[1845]: '/sbin/modprobe -bv acpi:PNP0400:' unexpected exit with status 0x0009
The spacing on the "acpi:PNP0400:" bit may be a bit wrong as my handwritten notes are not good enough. Another time I got no error message and the third time I got:

Code: Select all

udevd-work[1783]: '/sbin/modprobe -bv pci:v00008086d0000107Csv00008086sd00001376bc02sc00i00' unexpected exit with status 0x0009
The new kernel did not manage boot into text mode after 10+ minutes, nor did the old one.

HTH

Nick

[edit]
Using cheatcode acpi=off allowed v1.1 to boot. I don't know what it messes up.
[/code]

[edit2]
It messes up power-save mode and the PC only halts at the end and does not power off :(
[/edit2]

User avatar
fanthom
Site Admin
Site Admin
Posts: 4548
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#9 by fanthom » 08 Feb 2012, 22:55

bad luck i'm afraid. acpi issues are known for ages in linux world.
example:
https://bugzilla.redhat.com/show_bug.cgi?id=751060

i have one PC here which hangs during reboot with 32bit 3.2.4 kernel (surprisingly 64bit works ok while both are based on the same config).
please try to experiment with acpi= cheats:
http://redsymbol.net/linux_boot_parameters/
especially i would try acpi=force or acpi_osi=Linux

if that wont help then i would advise you to stay with Porteus-1.0 for now and try newer versions from time to time...
Please add [Solved] to your thread title if the solution was found.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: v1.1 won't boot into "always fresh", v1.0 will

Post#10 by brokenman » 09 Feb 2012, 23:53

Some things to try ... cheats
noapic
acpi=debug

Other things:
blacklist nouveau
look for acpi option in bios
upgrade (flash bios)

Buggy as hell this acpi
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply