You are not logged in.
yep. wine-0.9.21 is the one I'm using
Offline
Testing. I also had installed the latest current xorg-server (not testing), and so I got "No screens found". My forgetting to disable the testing repository now also happens to have me testing the nvidia driver. LOL.
Seems fine so far. Can play games. That's good. I manually removed mkinitrd. But I'm thinking something else might can be removed. Not that it matters. I wasn't using mkinitrd, and it wasn't taking up any space don't imagine.
Cool. Kernel 2.6.18, I'm the envy of...maybe one or two people. HA! There seems like udev introduces new tweaking possibilities I probably won't get to for some time. Sounds cool, though, but I don't exactly know what it means.
Offline
I'm also getting nothing but "Segmentation fault" out of wine since the testing update. Both with my own wine-0.9.21 package and with the official 0.9.19 package.
Jarsto
Offline
I got wine working now but under the beyond-2.6.17 kernel.
I did the latest test update of 2.6.18-3 and the image built fine but it will not boot.
crc error
system halted
Offline
crc errors sound like a broken boot partition or image
Offline
the beyond image is on the same partition.
the image builds!!!
lilo updates fine.
how do I fix or trouble shoot that?
Offline
also check if your /boot is not full, due too many other initrds from other kernels
Offline
with 2.6.18 i get a message durin boot i did not get before. i would not care since this is likely to happen, but i get it with "quiet" in the kernel line in the menu.lst too, so i noticed it:
IP-Config: no devices to configure
anybody knows what this is? my network devices work fine though...
Offline
more a cosmetical error you can ignore this safely, phrak any idea how to patch kinit to avoid this message?
Offline
more a cosmetical error you can ignore this safely, phrak any idea how to patch kinit to avoid this message?
Yeah, I'll look at that - the testing releases are up to 1.4.29, so something similar may have been done. I'll check it out
Offline
ah phrak and while at it i think it would a good idea to shutup md messages too, while using quiet
Offline
somethings wrong with wine and kernel-2.6.18.
just updated the latest 2.6.18-4.
that booted but wine only works with kernel 2.6.17beyond.
I have the latest wine-0.9.21.
Offline
ah phrak and while at it i think it would a good idea to shutup md messages too, while using quiet
not really about the kernel, but startup messages from the ppp daemon are also printed with quiet.
Offline
tpowa wrote:ah phrak and while at it i think it would a good idea to shutup md messages too, while using quiet
not really about the kernel, but startup messages from the ppp daemon are also printed with quiet.
Once the machine hits /sbin/init it no longer worries about the quiet parameter.
Offline
baze wrote:tpowa wrote:ah phrak and while at it i think it would a good idea to shutup md messages too, while using quiet
not really about the kernel, but startup messages from the ppp daemon are also printed with quiet.
Once the machine hits /sbin/init it no longer worries about the quiet parameter.
that explains it of course
thx
Offline
All this talk about the switch to mkinitcpio sounds so ominous. Before I try a test image, I want to ask a simple question:
If my current image is nothing special; that is that it's still the default image that Arch installed previously, is there anything for me to worry about? Should the new default image just work out of the box?
Offline
If my current image is nothing special; that is that it's still the default image that Arch installed previously, is there anything for me to worry about? Should the new default image just work out of the box?
No and yes.
Offline
Here all Ok.
Kernel 2.6.18-4, Nvidia 1.0.8774-2, XGL ( Danimoth repo), Kde 3.5.4.
My linuxbox is happy
Offline
so far got 3
1. sometime reboot, kernel check 1st HD with hde, sometime hda.
2. power can not off when shutdown.
3. group crash, so re-pacman shadow again.
same problem here, 18-4
Offline
1. http://wiki.archlinux.org/index.php/Con … controller
2. sounds like an acpi issue
3. should not happen if root is mounted correctly
Offline
Eh, here's a new one... If I use autodetection for my initcpio image, I get this little message during boot just after it prints out what the filesystem is:
777: process does not exist
Doesn't seem to cause any trouble though.
Offline
Well I updated the kernel and change GRUB to point to the mkinitcpio image thingie and now when it boots my system hardlocks. I am posting this from Vista since Linux is broken. Any idea of why this would happen? o.o
Offline
this too less information to solve this we need exact error messages, and your boot prompt command, hardware setup etc.
Offline
I cannot give error messages, as I am given none. I can give hardware and boot command stuffs though.
menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/hda1 vga=792 splash quiet ro
initrd /boot/kernel26.img
I have an MSI K7N2 Delta-ILSR motherboard with the nForce2 chipset, an AMD AthlonXP 2800+, geForce3 Ti200 for video, and 512MB of RAM. I am not sure if any of that hardware info will really help though but there it is. o.o
Oh and here are some lines of rc.conf that might be important.
MODULES=(!jfs !xfs evdev ath_pci forcedeth nvsound joydev)
...
DAEMONS=(syslog-ng !pcmcia network httpd crond hal mpd)
Please help me find out what is going on. ;_;
Offline
please remove quiet and splash from boot to see what really happens during boot.
other option would be to try the kernel26-fallback.img initrd image
Offline