antiX-15-beta1 to beta2 patch available - Page 4

Jon_J · posted: 2015-04-19 06:23

BitJam wrote:
Jon_J wrote:There is an error on boot. It didn't seem to be very serious.
The error is similar to this: fsck cannot run on this drive. no such file or directory. I'll have to write the exact error down and post it later.
Is the error in red? Do you remember if it comes before or after it says"The initrd init program took xx.xx seconds"? I've attached a screen shot which shows this message.

It comes before"The initrd init program took xx.xx seconds"
It is displayed early in large white text before the screen resolution changes.
I managed to copy it by watching it boot several times.

Code: Select all

checking root file system fsck util-linux.2.25.2
fsck error 2 (no such file or directory) while executing fsck ext4 for /dev/sda7 
exited with status code 8
Warning filesystem check failed but did not find any errors

BitJam · posted: 2015-04-19 08:59

Edit: I didn't realize this was on an installed system. You could try booting the live media again and then run:

Code: Select all

sudo e2fsck /dev/sda7

With some LiveUSBs the names"sda" and"sdb" will be swapped so you might need to run:

Code: Select all

sudo e2fsck /dev/sdb7

instead. I doubt both /dev/sda7 and /dev/sdb7 will exist so running either command should be fine.

I sometimes have power outages; the automatic check at boot time has been extremely useful. It would be good if we got it working for you but I don't know how to fix this problem in the installed system. I usually just work with the live system.

pcpavnz · posted: 2015-04-19 11:31

BitJam wrote:We created a special vbox mode for making the xorg.conf file when we detect we are running in Virtual Box. The 1280x1024 resolution works well for both anti and me in Virtual Box.

Replaced the initrd.gz and its md5sum and added the xrta.tgz in the B2 ISO using ISOMaster and saved it as a new iso, booted virtualbox up with it and no change to resolution, still at 1280x1024. Not sure your updated file would have addressed that, but it's not a major because a simple grub edit takes care fo the resolution running live.

BitJam wrote:I believe selecting"Save Video Mode" from the main bootloader menu will bring you down to 1024x768 inside of Virtual Box

the F8 save option is not available through virtualbox as the iso is treated like a read-only cdrom.

BitJam wrote:Some of this may be broken. My latest initrd.gz is available .... You don't need the tarball but it provides a few nice extra features

Didn't see any extra features at the grub screen in virtualbox, what should I be looking for?

anticapitalista · posted: 2015-04-19 12:08

the fsck error is easily fixed.

update-initramfs -u -t (in root terminal) followed by reboot.
This is fixed for next test release.

Jon_J · posted: 2015-04-19 13:06

anticapitalista wrote:the fsck error is easily fixed.

update-initramfs -u -t (in root terminal) followed by reboot.
This is fixed for next test release.

It looks like the fsck error is gone.
It booted so fast through that section, I could hardly see the information about"checking root file system"
I did get these errors below when I ran"update-initramfs -u -t" in a root terminal.
This is on an installed system.
I haven't used my ethernet yet as WiFi just worked out of the box on this machine. (Dell Inspiron mini 1010)

Code: Select all

Password: 
root@antix15:/home/bill# update-initramfs -u -t
update-initramfs: Generating /boot/initrd.img-3.19.1-antix.1-486-smp
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda7
cryptsetup: WARNING: could not determine root device from / etc/fstab
root@antix15:/home/bill#

Jon_J · posted: 2015-04-19 13:21

BitJam wrote:Edit: I didn't realize this was on an installed system. You could try booting the live media again and then run:
Code: Select all
sudo e2fsck /dev/sda7
With some LiveUSBs the names"sda" and"sdb" will be swapped so you might need to run:
Code: Select all
sudo e2fsck /dev/sdb7
instead. I doubt both /dev/sda7 and /dev/sdb7 will exist so running either command should be fine.

I sometimes have power outages; the automatic check at boot time has been extremely useful. It would be good if we got it working for you but I don't know how to fix this problem in the installed system. I usually just work with the live system.

This is probably irrelevant since the fsck error was on an installed system, but I wanted to reply to BitJam's post.
I don't get that error about"checking root file system" when I boot my Live media.
sda7 or sdb7 are not mounted.

Code: Select all

demo@antiX1:~
$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb1       1.9G  700M  1.2G  38% /live/boot-dev
/dev/loop0      685M  685M     0 100% /live/linux
tmpfs           785M  3.1M  782M   1% /live/aufs-ram
/live/aufs      785M  3.1M  782M   1% /
tmpfs            10M     0   10M   0% /media
tmpfs           100M  568K  100M   1% /run
tmpfs            10M  3.3M  6.8M  33% /live
devtmpfs        497M     0  497M   0% /dev
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           609M     0  609M   0% /run/shm
demo@antiX1:~
$

kmathern · posted: 2015-04-19 14:35

Jon_J wrote:

Code: Select all

root@antix15:/home/bill# update-initramfs -u -t
update-initramfs: Generating /boot/initrd.img-3.19.1-antix.1-486-smp
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda7
cryptsetup: WARNING: could not determine root device from / etc/fstab
root@antix15:/home/bill#

Upgrading the firmware-realtek package to the 0.43.3 version from the Siduction fixes/non-free repo (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://packages.siduction.org/fixes/pool/non-free/f/firmware-nonfree/firmware-realtek_0.43.3_all.deb"
linktext was:"http://packages.siduction.org/fixes/poo ... .3_all.deb"
====================================
) gets rid of the"W: Possible missing firmware ..." messages on my system.

BitJam · posted: 2015-04-19 19:42

pcpavnz wrote:
BitJam wrote:We created a special vbox mode for making the xorg.conf file when we detect we are running in Virtual Box. The 1280x1024 resolution works well for both anti and me in Virtual Box.
Replaced the initrd.gz and its md5sum and added the xrta.tgz in the B2 ISO using ISOMaster and saved it as a new iso, booted virtualbox up with it and no change to resolution, still at 1280x1024.

Yes, this is as designed. That is why I suggested you use"Safe Video Mode" (sorry for the typo). It should give you 1024x768 in Virtual Box.

Didn't see any extra features at the grub screen in virtualbox, what should I be looking for?

"Safe Video Mode" in the main menu. This should work now. Alternatively, you could try the boot parameter"xorg=1024x768".

The other fix is that we delay even further when video modules (such as nouveau, i915, radeon, etc) are loaded. This was a safe work-around around a bug kathern found when we load the radeon module earlier. We added a udev rule and changed the splash-set script so the console decoration doesn't disappear when udev loads video modules that change the framebuffer driver.

rokytnji · posted: 2015-04-20 00:23

Fresh install on the Dell T3400 after I worked on hardware all day.

Code: Select all

harry@tramp:~
$ inxi -Fxz
System:    Host: tramp Kernel: 3.19.1-antix.1-486-smp i686 (32 bit gcc: 4.9.2)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-beta2-V_386-full Killah P 11 April 2015
Machine:   System: Dell product: Precision WorkStation T3400
           Mobo: Dell model: 0TP412 Bios: Dell v: A09 date: 06/04/2009
CPU:       Dual core Intel Core2 Duo E7400 (-MCP-) cache: 3072 KB
           flags: (lm nx pae sse sse2 sse3 sse4_1 ssse3) bmips: 11163
           clock speeds: max: 2790 MHz 1: 2790 MHz 2: 2790 MHz
Graphics:  Card: NVIDIA G71 [GeForce 7900 GS] bus-ID: 01:00.0
           Display Server: X.Org 1.16.4 driver: nouveau
           Resolution: 1280x1024@60.02hz
           GLX Renderer: Gallium 0.4 on NV49
           GLX Version: 2.1 Mesa 10.3.2 Direct Rendering: Yes
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: ALSA v: k3.19.1-antix.1-486-smp
Network:   Card-1: Broadcom NetXtreme BCM5754 Gigabit Ethernet PCI Express
           driver: tg3 v: 3.137 bus-ID: 04:00.0
           IF: eth0 state: down mac: <filter>
           Card-2: Realtek RTL8191SU 802.11n WLAN Adapter
           driver: r8712u usb-ID: 001-002
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 160.0GB (4.5% used)
           ID-1: /dev/sda model: ST3160812AS size: 160.0GB
Partition: ID-1: / size: 7.6G used: 2.9G (40%) fs: ext4 dev: /dev/sda5
           ID-2: /home size: 16G used: 87M (1%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 35.0C mobo: N/A gpu: 59.0
           Fan Speeds (in rpm): cpu: 40950 mobo: 34650
Info:      Processes: 116 Uptime: 18 min Memory: 246.8/2018.0MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.2.19

Too tired to continue so that is all for today. For starters. I had a password bios locking me out before I could even start changing graphics card and scrounging up a hard drive for this thing.

Jon_J · posted: 2015-04-20 22:42

kmathern wrote:
Jon_J wrote:
Code: Select all
root@antix15:/home/bill# update-initramfs -u -t
update-initramfs: Generating /boot/initrd.img-3.19.1-antix.1-486-smp
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
cryptsetup: WARNING: failed to detect canonical device of /dev/sda7
cryptsetup: WARNING: could not determine root device from / etc/fstab
root@antix15:/home/bill# 
Upgrading the firmware-realtek package to the 0.43.3 version from the Siduction fixes/non-free repo (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://packages.siduction.org/fixes/pool/non-free/f/firmware-nonfree/firmware-realtek_0.43.3_all.deb"
linktext was:"http://packages.siduction.org/fixes/poo ... .3_all.deb"
====================================
) gets rid of the"W: Possible missing firmware ..." messages on my system.

That did fix my"missing firmware" errors. I also connected with my home router through an ethernet cable and it connected fine. Thank you.
Now I need to google those other 2 errors.
cryptsetup: WARNING: failed to detect canonical device of /dev/sda7
cryptsetup: WARNING: could not determine root device from / etc/fstab

kmathern · posted: 2015-04-20 23:07

Jon_J wrote:That did fix my"missing firmware" errors. I also connected with my home router through an ethernet cable and it connected fine. Thank you.

The"missing firmware" errors didn't really affect my ethernet connection, it was working even with the errors, I upgraded the firmware to the 0.43.3 version mainly because I got tired of seeing them.

rokytnji · posted: 2015-04-20 23:15

I got tired of seeing them

While me, Being married with kids and gradkids and 6 dogs.
I ignore bitching errors unless they effect something.
Too used to complaints, crying, screaming, and barking I guess.

coyotito · posted: 2015-04-21 09:28

ignore such kernel messages unless they affect smth. Hey, try Systemd I believe it does not print them __{{emoticon}}__

Roky, maybe you can fix that bios password using the reset pin on mb? I forget what those pins are called dont use them anymore.

rokytnji · posted: 2015-04-21 12:00

Roky, maybe you can fix that bios password using the reset pin on mb? I forget what those pins are called dont use them anymore.

Thanks Coyoto for the suggestion.

Figured out default bios bios reset before I whined about it.
It was simple. Just pull Cmoas battery and press power button for 10 seconds then reinsert the battery.

Waiting on some parts now that are due in a couple of weeks or so. More or less.

fatmac · posted: 2015-04-21 12:16

rokytnji wrote: While me, Being married with kids and gradkids and 6 dogs.
I ignore bitching errors unless they effect something.
Too used to complaints, crying, screaming, and barking I guess.

__{{emoticon}}__ __{{emoticon}}__