The previously mentioned Ubuntu repository problem seems to have resolved itself. I am finally able to upgrade my Samba packages.

Popularity: 30% [?]

Comments(0)

This has been happening all day every time I attempt to do apt-get dist-upgrade:

The following packages will be upgraded:
  libsmbclient samba samba-common smbclient smbfs
5 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.0MB of archives. After unpacking 4096B will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Err http://security.ubuntu.com feisty-security/main smbfs 3.0.24-2ubuntu1.3
  403 Forbidden
Err http://security.ubuntu.com feisty-security/main smbclient 3.0.24-2ubuntu1.3
  403 Forbidden
Err http://security.ubuntu.com feisty-security/main samba 3.0.24-2ubuntu1.3
  403 Forbidden
Err http://security.ubuntu.com feisty-security/main samba-common 3.0.24-2ubuntu1.3
  403 Forbidden
Err http://security.ubuntu.com feisty-security/main libsmbclient 3.0.24-2ubuntu1.3
  403 Forbidden
E: Failed to fetch

http://security.ubuntu.com/ubuntu/pool/main/s/samba/smbfs_3.0.24-2ubuntu1.3_i386.deb:

403 Forbidden

Popularity: 28% [?]

Comments(0)

Seen on a work email list. A possible solution to the problem where files downloaded through apt-get on Ubuntu at work (where we have a squid HTTP proxy) periodically get corrupted.

Put the following in apt.conf:

Acquire::http::Pipeline-Depth "0";

Quote from man apt.conf:

One setting is provided to control the pipeline depth in cases where the remote server is not RFC conforming or buggy (such as Squid 2.0.2) Acquire::http::Pipeline-Depth can be a value from 0 to 5 indicating how many outstanding requests APT should send. A value of zero MUST be specified if the remote host does not properly linger on TCP connections - otherwise data corruption will occur. Hosts which require this are in violation of RFC 2068.

Popularity: 30% [?]

Comments(0)

It seem that some of the newer Linux kernel versions (2.6.21 and 2.6.22) don’t like the LSI SCSI adapter emulation in some of VMware’s products. I myself ran into this when I upgraded the kernel on a Gentoo VM (VMware ESX Server 3.0.1) to 2.6.22. After rebooting, the system could not find the root partition.

It took a bit of searching to figure out what the problem was, but the solution was simple. Change the VM to use the BusLogic SCSI adapter instead of the LSI.

Some references:

• forums.gentoo.org: 2007.0 on vmware: “cannot open root device sda3…”
• VMTN Discussion Forums: VMware 5.5.4 + Kernel 2.6.21.3: LSI …

Popularity: 19% [?]

Comments(0)

Installing gentoo-livecd-i686-installer-2007.0.iso into a VM on a VMware ESX Server 3.0.1 host.

Flickr photoset

Popularity: 20% [?]

Comments(0)

On my Asus S-presso I’ve got suspend to disk working but not suspend to RAM.

In an effort to get s2ram working, I upgraded the BIOS to version 1008.003.

Last time, I upgraded the BIOS, I used the HP USB Disk Storage Format Tool and HP’s boot files (both of which I found in a post on aaltonen.us) to format my SanDisk Cruzer Mini as a DOS-bootable disk.

This time, the links seemed to be broken, but I managed to find them in other spots, so I made my own copies:

• HPUSBFW_BOOTFILES.zip

• SP27213.exe

I used these to boot off an SD card into DOS and then used Asus’s afudos utility to backup the current BIOS and upgrade to the new version:

afudos /i1008.003 /o1007.002

Unfortunately it didn’t help a lick with s2ram.

By the way, nice work, Asus:

$ sudo s2ram
Machine is unknown.
This machine can be identified by:
sys_vendor   = "To Be Filled By O.E.M. by More String"
sys_product  = "To Be Filled By O.E.M."
sys_version  = "To Be Filled By O.E.M."
bios_version = "1008.003"

"To Be Filled By O.E.M." — ha ha. Oops.

(sudo s2ram -f doesn’t work either — it sort of looks like it’s suspending and then it immediately wakes up).

Popularity: 16% [?]

Comments(1)

As previously mentioned, I was trying to get suspend to RAM and/or suspend to disk working on my Asus S-presso box with Ubuntu feisty.

Well, I got it to work. The problem was lame - for some reason when I installed uswsusp and it regenerated the initrd, it only did the 2.6.20-16-generic file and I was running the 2.6.20-16-386 kernel. I just had to do a mkinitramfs -u -k $(uname -r) and that updated the proper initrd for my kernel of choice.

Now I suspend to disk by doing sudo s2disk and then later when I power on the machine and choose the relevant item in the grub menu, the newly generated initrd will automatically resume by reading from my /dev/sda5 swap partition.

I also played with s2ram, but haven’t had too much luck there yet. My machine is not in the whitelist and I tried forcing it with -f and other options. What seems to happen is the machine attempts to suspend to RAM but then gets immediately woken up and goes right to the GNOME screensaver password prompt. I also tried upgrading to the latest version of uswsusp (0.7 [2007-09-03] instead of the 0.3 version that is in Ubuntu Feisty). No dice. Heck, perhaps my machine has a broken ACPI implementation. From what I hear, the ACPI spec is quite complex and is often poorly implemented.

I’d like to get s2ram working (any ideas?), but at least now I have s2disk working.

Popularity: 21% [?]

Comments(2)