Slackware 13.1 BETA1

smoooth103 · 05-07-2010, 07:42 PM

I'm real impressed with the 13.1beta current update. It's really nice and everything seems to work very flawlessly together. Great update guys.

willysr · 05-07-2010, 07:43 PM

Yup, it works fine here without any problems so far

hitest · 05-07-2010, 09:26 PM

I'm loving Slackware 13.1 BETA 1, I'm running it on two units. All is well.

mlangdn · 05-08-2010, 12:32 AM

Been away for a couple of days and just did the upgrade. All went well with no errors.
I have been running current without incident since x86_64 was born. Most of my problems have been self-inflicted,
except for the libpng thingy, which may now be resolved.

brodo · 05-08-2010, 03:45 AM

Quote:

Originally Posted by linus72

After upgrades this morning xfce4 wont load on 2 of my installs

heres xsession errors as X crashes

Code:

<stdin>:1:3: error: invalid preprocessing directive #Those
<stdin>:2:3: error: invalid preprocessing directive #or
<stdin>:3:3: error: invalid preprocessing directive #Xft
<stdin>:4:3: error: invalid preprocessing directive #Xft
xrdb:  "Xft.hinting" on line 9 overrides entry on line 6
xrdb:  "Xft.hintstyle" on line 11 overrides entry on line 7
/etc/X11/xinit/xinitrc.xfce: line 134: ck-launch-session: command not found

anyone else get this?

Just make sure you installed all these packages that appear listed
on ChangeLog.txt dated 6th of May.
Initially, I missed some of them and I got the same
"ck-launch-session: command not found" error.
Now I'm fine :-)

johnny23 · 05-08-2010, 06:34 AM

If you're using Slackpkg, don't forget `slackpkg install-new' ...

hitest · 05-08-2010, 08:03 AM

Quote:

Originally Posted by johnny23

If you're using Slackpkg, don't forget `slackpkg install-new' ...

Yep

# slackpkg update

# slackpkg install-new

# slackpkg upgrade-all

Chuck56 · 05-08-2010, 08:09 AM

Quote:

Originally Posted by johnny23

If you're using Slackpkg, don't forget `slackpkg install-new' ...

And don't forget:

slackpkg clean-system

but be very careful to select only the packages that are listed as "removed" in the changelog. Otherwise you'll remove packages that you added to customze Slackware

sjampoo · 05-08-2010, 04:00 PM

*grumbz*

During upgrade from 13 to -current (or 13.1b) the kernel changes my disk from hda2 to sda2.
after
slackpkg update, clean system, install-new, update-all
The thing will boot to a kernelpanic

I noticed sda being mentioned instead of hda.
rebooted, <TAB> at lilo,
boot: Linux root=/dev/sda2 rdinit= ro

makes it a bit further, than gives me the option to go either in maintenance mode,or reboot (CTRL-d => reboot). In maintenance mode I get a read-only file system error when I try to change/save the /etc/lilo.conf

GrzmlbL! (being the opposite of ^grin^ )

It's ok for the Kernel to pickup my HDD as 'sda' instead of 'hda', and this change normally couldn't be less important.. but now, as a total newbee, I ones more am left with a nicely borked system, that I can only repair with either your help or a re-installation. (stupid me to want to shift to -current since the changelog states /extra/xf86-video-intel-alternative removed

hitest · 05-08-2010, 04:06 PM

Quote:

Originally Posted by sjampoo

*grumbz*

During upgrade from 13 to -current (or 13.1b) the kernel changes my disk from hda2 to sda2.
after
slackpkg update, clean system, install-new, update-all
The thing will boot to a kernelpanic

I noticed sda being mentioned instead of hda.
rebooted, <TAB> at lilo,
boot: Linux root=/dev/sda2 rdinit= ro

makes it a bit further, than gives me the option to go either in maintenance mode,or reboot (CTRL-d => reboot). In maintenance mode I get a read-only file system error when I try to change/save the /etc/lilo.conf

GrzmlbL! (being the opposite of ^grin^ )

It's ok for the Kernel to pickup my HDD as 'sda' instead of 'hda', and this change normally couldn't be less important.. but now, as a total newbee, I ones more am left with a nicely borked system, that I can only repair with either your help or a re-installation. (stupid me to want to shift to -current since the changelog states /extra/xf86-video-intel-alternative removed

Check out this link:

http://rlworkman.net/howtos/libata-switchover

afreitascs · 05-08-2010, 04:38 PM

Very good !!!

Many palms developers to Slackware !

many thanks

rworkman · 05-08-2010, 11:28 PM

Quote:

Originally Posted by sjampoo

*grumbz*

During upgrade from 13 to -current (or 13.1b) the kernel changes my disk from hda2 to sda2.
after
slackpkg update, clean system, install-new, update-all
The thing will boot to a kernelpanic

I noticed sda being mentioned instead of hda.
rebooted, <TAB> at lilo,
boot: Linux root=/dev/sda2 rdinit= ro

makes it a bit further, than gives me the option to go either in maintenance mode,or reboot (CTRL-d => reboot). In maintenance mode I get a read-only file system error when I try to change/save the /etc/lilo.conf

GrzmlbL! (being the opposite of ^grin^ )

It's ok for the Kernel to pickup my HDD as 'sda' instead of 'hda', and this change normally couldn't be less important.. but now, as a total newbee, I ones more am left with a nicely borked system, that I can only repair with either your help or a re-installation. (stupid me to want to shift to -current since the changelog states /extra/xf86-video-intel-alternative removed

hitest pointed you to my libata-switchover link, and that's good -- however, please let me know if it needs some further clarification and such; I wrote that mostly from a theoretical viewpoint (as in, rather than actually *doing* the upgrade, I wrote what I *think* will occur)

There was some feedback from several other people involved (including actual error messages and such), and I made some edits based on that feedback, but to make a long story short, that howto might not be perfect. Since it *needs* to be perfect before 13.1 is released, any pushes in that direction will be appreciated.

sjampoo · 05-09-2010, 04:30 AM

Mothersday today,. so won't be able to get (any)thing(s) done.

Will be providing feedback on your how to. Will be monday probably. Will boot with a 12.2 installation cd, edit the files you mentioned in the how-to,. and see if I can modify lilo.conf and run lilo. (PS: Is it necessary to change lilo? it boots windows *spit* fine, and starts booting Linux/Slackware okay.. (until things get errorous).

PS: Do you want the actual errors? How can I 'get them' in digital form? (I can allways take a picture @ kernel panic, if that's okay with you)

sjampoo · 05-09-2010, 03:14 PM

Okay.. here's the deal

I had a fresh, working and new 13.0 running,
Hardware:
Acer TM240
Celeron Mobile 2,4 GHz, 750MB memm, 30 Gb hdd
hda1 -> Win32
hda2 -> /
hda5 -> /home
hda6 -> ntfs
hda7 -> swap

Updated with slackpkg.
After two slackpkg sequences (update, clean-system, install-new, upgrade-all clean-system, install-new, upgrade all) and a lilo boot (asked for during these upgrades, due to new kernel)

Quote:

Originally Posted by typed over from screen, when kernel says panic

bla bla
usb 4-1: new full speed USB device using uhci_hcd and address 2
VFS: Cannot open root device "302" or unknown-block(3,2)
Please append a correct "root=" boot option; here are the available partitions:
0800 29302560 sda driver: sd
0801 10241406 sda1
0802 9277537 sda2
0803 1 sda3
0804 8032 sda4
0805 5373711 sda5
0806 2939863 sda6
0807 1461883 sda7
0b00 1048575 sr0 driver: sr
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,2)
Pid: 1, comm: swapper Not rainted 2.6.33.3-smp #2
Call Trace:
[<c1951edc>] ? printk+0x1d/0x1f
[<c1951e16>] panic+0x48/0xf1
[<c1c60ca2>] mount_block_root+0x1d3/0x26c
[<c1002932>] ? do_signal+0x402/0xa90
[<c10eb56c>] ? sys_mknow+0x2c/0x30
[<c1c60dd7>] mount_root+0x9c/0xa2
[<c1c60f2b>] prepare_namespace+014e/0x192
[<c10de925>] ? sys_access+0x25/0x30
[<c1c60372>] kernel_init+0x0/0x16e
[<c1c60213>] ? kernel_init+0x0/0x16e
[<c100363e>] kernel_thread_helper+0x6/0x10

(errors caused by me typing from writen notes

)

I reboot, pushing <TAB> at lilo to get prompt and enter:

Code:

Linux root=/dev/sda2 rdinit= ro

Things scroll fast enough over the screen while booting, things I see are about Ext3 (where / and /home are formatted to Ext4), but can't record the exact words/lines.

The screen ' flashed ' to black, and comes back

Quote:

Originally Posted by typed over from screen, when kernel says panic

...
Setting systemtime from the hardware clock (localtime).
Checking root filesystem status: read-only filesystem
Checking root filesystem:
fsck from util-linux-ng 2.17.2
/sbin/e2fsck: No such file or directory while trying to pen /dev/hda2
/dev/hda2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8192 <device>

***********************************************************
*** An error occurred during the root filesystem check. ***
*** You will now be given a chance to log into the ***
*** system in single-user mode to fix the problem. ***
*** ***
*** If you are using the ext2 filesystem, running ***
*** 'e2fsck -v -y <partition>' might help. ***
***********************************************************

Once you exit the single-user shell, the system will reboot.

Type control-d to proceed with normal startup,
(or give root password for system maintenance): XXXROOTPWDXXX
Entering System Maintenance Mode

root@(none):/# _

When I try to mount /dev/sda2 to anywhere I get following error:

Quote:

Originally Posted by mount /dev/sda2 /mnt/

mount: /dev/sda2 already mounted or /mnt busy

Quote:

Originally Posted by mount

/dev/root on / type ext4 (rw,barrier=1,data=ordered)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)

mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
It's possible that information reported by mount(8) is not
up to date. For actual information about system mount points
check the /proc/mounts file

Quote:

Originally Posted by cat /proc/mounts

rootfs / rootfs rw 0,0
/dev/root / ext4 ro,relatime,barrier=1,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=373628,nr_inodes=93407,mode=755 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode620 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0

I can't edit /etc/lilo.conf since it's read-only filesystem.
When I reboot with a slackware 12.2 cd-rom, the drives are in-accessable, since 12.2 doesn't support ext4.
When I reboot with a slackware 13.0 dvd (which the machine supports, but sometimes refuses to), I can edit the /etc/lilo.conf, where I change every hda to sda ( boot = /dev/sda , and further down, other = /dev/sda1 for windows and root= /dev/sda2 for Linux )

When I try to run lilo it gives following errors:

When booted from disk, in maintenance mode:

Quote:

Warning: LBA32 addressing assumed
Fatal: creat /boot/map~: Read-only file system

So this doesn't change anything.

When booted from the Slackware 13.0 dvd, with the changed lilo.conf from hda* to sda*

[quote]
mount /dev/hda2 /mnt
cd /mnt/etc
lilo -C lilo.conf
Warning: LBA32 addressing assumed
Fatal: raid_setup: stat("/dev/sda")

So not really an option on changing lilo I guess?
or can I override this Fatal with a -ignore? Don't think so.

Giving up on the lilo part.. where actually lilo ' works ' as in: it does 'boot'

Let's see how far this ( http://rlworkman.net/howtos/libata-switchover ) takes me.

-----

1: The updating part: Done
2: /etc/fstab
editing (while booted from 13.0 dvd and mounted /dev/hda2 under /mnt) all hda to sda
and removing udev cdrom rule:
# rm -f /mnt/etc/udev/rules.d/70-persistent-cd.rules
3: the lilo part I have to skip for now
4: reboot, with <tab> I will append Linux root=/dev/sda2 rdinit= ro
5: fixing lilo.conf -> Check, already done so

I just couldn't run lilo yet.

-----
Success!

Quote:

yadayada
/dev/sda2: clean..
Remounting root device with read-write enabled
/dev/sda2 on / type ext4 (rw)

Welcome to Linux 2.6.33.3-smp (tty1)

suikerstroop login: root
Password: XXXXXXX
lilo
Warning: LBA32 addressing assumed
Added Windows *
Added Linux
One warning was issued

SUCCES!

metrofox · 05-09-2010, 03:52 PM

if you can fix that LBA32 warning just adding:

Code:

lba32

in the first section, for example under "boot = /dev/xyz".